Related
the phone keeps coming up with a error. With a picture of a phone with a triangle with a exclamation point inside of it.
I have been searching I hope somebody can tell me.
ravenv12 said:
the phone keeps coming up with a error. With a picture of a phone with a triangle with a exclamation point inside of it.
I have been searching I hope somebody can tell me.
Click to expand...
Click to collapse
That's the stock recovery. If you think that you are rooted with a custom recovery like Amon_RA, it sounds like either you are not, or you were and somehow you restored the stock recovery.
So, are you rooted? Is this the first time that you tried to get into Recovery? What method did you use to root the phone?
Universal 1 Click Eris Root App Apk - No PCs, No Scripts Needed, EASY
I'm not sure what I did wrong. I guess I need to know where I need to start from to restore the phone. So if someone can point me to the right direction that would be great. Also I'm not sure if the phone is Rooted still , I think were I messed up is where, I was installing custom ROM on the phone When it was booting up. It locked up at the loading spring. i installed GSB.v3.0-CM7.0.2-Eris
http://forum.xda-developers.com/showthread.php?t=792026 this will put you back to stock unrooted or download the rootcheck app in the market and check if you have root
if so then dont flash back to stock download rom manger and use that to flash a recovery either clockwork or scroll down and flash amons recovery i recommend amon ra recovery
ravenv12 said:
Universal 1 Click Eris Root App Apk - No PCs, No Scripts Needed, EASY
I'm not sure what I did wrong. I guess I need to know where I need to start from to restore the phone. So if someone can point me to the right direction that would be great. Also I'm not sure if the phone is Rooted still , I think were I messed up is where, I was installing custom ROM on the phone When it was booting up. It locked up at the loading spring. i installed GSB.v3.0-CM7.0.2-Eris
Click to expand...
Click to collapse
Wait, so that sounds like you actually had Amon_RA recovery?
Question: when you installed GSB, did you wipe data/factory reset? And also flash Google apps?
If you start in the bootloader (hold VolDn when you power up), there should be a prompt to press VolUp to start in Recovery. If you press power up, do you get the Amon_RA recovery or do you get the exclamation point with triangle?
I fixed it last night I installed Amon_RA recovery . But I went back to GSB v3.0 where I messed up the first time installed find the second time but my SD card is not recognizing anymore. in the os. Only my 1gb SD card works now.
ravenv12 said:
I fixed it last night I installed Amon_RA recovery . But I went back to GSB v3.0 where I messed up the first time installed find the second time but my SD card is not recognizing anymore. in the os. Only my 1gb SD card works now.
Click to expand...
Click to collapse
Did you ever partition the card for apps2sd on a ROM like xtrROM? If so, you'll need to repartition the card so it has only one partition. (You do this the same way that you partitioned - namely:
- backup the contents of your SD card
- restart in Recovery
- partition SD card menu
- partition SD
- set the options for partition sizes for ext2 and swap to 0 bytes
That will reset the card to a single partition, formatted fresh.
Thanks you guys, it's completely working now.
good news
it sure is good news. But now my friend has one that he's willing to sell me for $10.00 but it does not boot and I've been trying to fix it . I would like to get it for my girlfriend but figure if there's anything that can be done to it I think it's a paperweight. I can get to HBoot and fastboot . But not to recovery.
But for 10 bucks you can't beat it for parts right if I cant fix it
ravenv12 said:
it sure is good news. But now my friend has one that he's willing to sell me for $10.00 but it does not boot and I've been trying to fix it . I would like to get it for my girlfriend but figure if there's anything that can be done to it I think it's a paperweight. I can get to HBoot and fastboot . But not to recovery.
But for 10 bucks you can't beat it for parts right if I cant fix it
Click to expand...
Click to collapse
Well have you tried the same thing for that phone as your phone you just got working? I'm pretty sure if you can get to hboot and faatboot then there's still hope. I just don't know how to fix but I'm sure someone will help you out soon enough
Sent from my Gin-Tazz using Tapatalk
I'm starting to think the phone has hardware issues also so I don't think it's can be fixed I think it's for parts only
I should start by saying ive never posted here before but i am on xda like 4 hours a day, so please bare with me. Im a flashaholic, and recently ive been trying to learn to port/make roms, ive used every tutorial and have managed to fix every error ive been getting when flashing (status 6-7), tho i must admit im not sure specifically what i did to fix them. heres my biggest problem, i get to flashing this rom and it says successful but it doesnt actually install anything...ive tried everything, i cant figure it out, other roms i flash install no problem so it has to be something im doing or missing. Another small problem im having is that pj75img.zip will not flash from bootloader(for whatever reason)...i wont deny im a noob, im running android kitchen on cygwin...i am s-off (lazypanda), using twrp, currently running liquid smooth rom...im desperate for help, maybe a little guidence in what im doing and how to do it...i really wanna learn from the devs here, you guys are genius's please help me!!!!!
johnnyavocado86 said:
I should start by saying ive never posted here before but i am on xda like 4 hours a day, so please bare with me. Im a flashaholic, and recently ive been trying to learn to port/make roms, ive used every tutorial and have managed to fix every error ive been getting when flashing (status 6-7), tho i must admit im not sure specifically what i did to fix them. heres my biggest problem, i get to flashing this rom and it says successful but it doesnt actually install anything...ive tried everything, i cant figure it out, other roms i flash install no problem so it has to be something im doing or missing. Another small problem im having is that pj75img.zip will not flash from bootloader(for whatever reason)...i wont deny im a noob, im running android kitchen on cygwin...i am s-off (lazypanda), using twrp, currently running liquid smooth rom...im desperate for help, maybe a little guidence in what im doing and how to do it...i really wanna learn from the devs here, you guys are genius's please help me!!!!!
Click to expand...
Click to collapse
Can you post your updater-script?
pinky059 said:
Can you post your updater-script?
Click to expand...
Click to collapse
whats up dude, thanks for the help, i attached my updater-script, if u want the whole thing of what im working on ill be more then happy to attach it as well (though i did use the updater script from my liquid smooth rom (im still learning what kind of difference that makes because their like 90% the same))...i zipped up the file so i could attach it
I've had it happen a few times where twrp would just reject the zip file for no apparent reason but if I let it boot normally, then went back into the recovery it would start working again.
Another thing to try would be pulling the log file from the recovery, just have it connected with adb and use 'adb pull /tmp/recovery.log' after it fails and check to see how far it got
xHausx said:
I've had it happen a few times where twrp would just reject the zip file for no apparent reason but if I let it boot normally, then went back into the recovery it would start working again.
Another thing to try would be pulling the log file from the recovery, just have it connected with adb and use 'adb pull /tmp/recovery.log' after it fails and check to see how far it got
Click to expand...
Click to collapse
^^^THIS.....but, make sure you do it before you reboot the phone....while still in recovery after the install fails....
Thanks for the help guys, so i did what you said and it turns out my system is not installing, it installs the partitions and the boot.img but its not installing the system...do you think the problem could be...the system, the zip, the updater-script, the build.prop?.im goin nuts, i had like 4 days with no sleep working on this lol
johnnyavocado86 said:
Thanks for the help guys, so i did what you said and it turns out my system is not installing, it installs the partitions and the boot.img but its not installing the system...do you think the problem could be...the system, the zip, the updater-script, the build.prop?.im goin nuts, i had like 4 days with no sleep working on this lol
Click to expand...
Click to collapse
Try this updater-script and let me know if it works. If not, can you upload the ROM your working on? I'll take a look at it.
All I changed is the way it formats and mounts /system.
I am currently stuck at the recovery screen on my Galaxy Player 4.0. I see plenty of help for people stuck at download screen. I wish I was that lucky. I can't get my computer drivers to recognize the device to use Odin. I have uninstalled and re-installed the Samsung drivers from a location on this sight. Yes I have held the down button and the power button, but it just stays at the Samsung screen. When I let go eventually it simply goes to the "Android system recovery <3e>" screen. None of the blue choices on the screen do anything. About mid-screen there is some yellow lettering including # MANUAL MODE #. Also a small android next to a white triangle with a yellow exclamation point. I am sorry to post a long and most likely ignored question, but I have searched for a long time trying to find help. Any help would be much appreciated.
what where you doing to get you to this point? If flashing ANY ICS the instructions will be different from other suggestions to follow.
have you tried removing the battery then hold power and volume down then while holding then insert the battery?
Am I the only person thinking its a soft brick? Dude try this... oneclickunbrick its a jar file and a charm... give me a day and I'll post a copy here
Sent from my YP-G70 using xda premium
button/battery
daniel644 said:
what where you doing to get you to this point? If flashing ANY ICS the instructions will be different from other suggestions to follow.
have you tried removing the battery then hold power and volume down then while holding then insert the battery?
Click to expand...
Click to collapse
Tried the battery with no luck.
I was trying to get into recovery with ROM Manager. Never got past the open box that turned into a triangle.
oneclick
Evoium said:
Am I the only person thinking its a soft brick? Dude try this... oneclickunbrick its a jar file and a charm... give me a day and I'll post a copy here
Sent from my YP-G70 using xda premium
Click to expand...
Click to collapse
oneclickunbrick failed
Is adb working, normally it should be working in recovery so if you have the sdk installed just go to platforms-tools and then type adb reboot download. This should work, if not, you could try a usb JIG.
adb
ti-pich said:
Is adb working, normally it should be working in recovery so if you have the sdk installed just go to platforms-tools and then type adb reboot download. This should work, if not, you could try a usb JIG.
Click to expand...
Click to collapse
I got "device not found". I guess I will go to the hardware store today and fab a jig. "fingers crossed"
Heimdall is the only place I can get the device recognized, so I have some hope. I get a fail on the pit file and I can't figure out the sector or the needed .dll. Although with the pit file error, I don't think the other two matter until I get that squared away. Thanks for your help. At least I have some guidance to try stuff.
Theodoric47 said:
I got "device not found". I guess I will go to the hardware store today and fab a jig. "fingers crossed"
Click to expand...
Click to collapse
The Galaxy Players are surprisingly robust, so yeah get the jig made and get into download mode. From download mode you should be golden. I've completely blown up my device twice to the point where the only fix was to flash the bootloader and pit then load up the rom(don't do any of this, I'm just explaining how sturdy the Galaxy Player is). Both times were fantastic learning experiences.
download mode
SGP4isokay said:
The Galaxy Players are surprisingly robust, so yeah get the jig made and get into download mode. From download mode you should be golden. I've completely blown up my device twice to the point where the only fix was to flash the bootloader and pit then load up the rom(don't do any of this, I'm just explaining how sturdy the Galaxy Player is). Both times were fantastic learning experiences.
Click to expand...
Click to collapse
OK, got the jig working and can get the device into download mode (whoot). Now I am having trouble getting it back to operational. I use the methods shown in this thread > http://forum.xda-developers.com/showthread.php?t=1531850< . Odin goes through its paces and gives me a pass. The device reboots but will not get past the white SAMSUNG screen. Do you know of a good walk through that will show me what I am doing wrong?
Theodoric47 said:
OK, got the jig working and can get the device into download mode (whoot).
Click to expand...
Click to collapse
Grats! The jig is simply invaluable and I know you probably don't enjoy your device not being functional right now but the fact that it still powers up means that it is recoverable. Getting to Download Mode is a huge win. Anyway, you never answered what it was that put your device into a broken state so it's hard to tell what's wrong. As an example of how I get assistance from the fine people of XDA here is the thread I made when I broke my device.
Were you trying out an ICS rom?
Did you attempt to convert to EXT4?
Were you loading a backup in CWM?
The more information you can give the smart people, the better. Me? I'm not a developer and I barely know anything about android...but they helped me recover my device so anyone can do it. Just give them some information to work with.
info
SGP4isokay said:
Grats! The jig is simply invaluable and I know you probably don't enjoy your device not being functional right now but the fact that it still powers up means that it is recoverable. Getting to Download Mode is a huge win. Anyway, you never answered what it was that put your device into a broken state so it's hard to tell what's wrong. As an example of how I get assistance from the fine people of XDA here is the thread I made when I broke my device.
Were you trying out an ICS rom?
Did you attempt to convert to EXT4?
Were you loading a backup in CWM?
The more information you can give the smart people, the better. Me? I'm not a developer and I barely know anything about android...but they helped me recover my device so anyone can do it. Just give them some information to work with.
Click to expand...
Click to collapse
I was trying to install the IcyFusion ROM when I ran into difficulty. If I was attempting to convert to EXT4, I sure did not know that I was trying to do that. And I was not trying restore a CWM backup. I had unlocked and rooted the device awhile back. I had the "yp-g1cwyxaa.tar" ROM from this thread >http://forum.xda-developers.com/showthread.php?t=1512331< running fine and was enjoying the player in all its rooted glory. But because I can never leave well enough alone, I wanted to try the "IcyFusion_v2.3_GIUEKI8" ROM. To be honest I am not sure what I did wrong in the process.
I see in the instructions that I specified that I have been trying to follow that there are instructions "Special instructions for people coming from CM7". Is this the route I need to take? I have rooted several devices including my Nook Tablet, Nexus 7 and my Galaxy Nexus phone with little or no trouble. This does not include the ugly incident with my TF300T that I did brick. At least Asus put in a new motherboard and she is back in operation. Ouch, that cost me. Like I said, I can never leave well enough alone.
I hope this info helps people help me. Thanks.
Update 1
I followed your link to your thread and guess what.
This is where I am now.
-- Copying media files...
E:failed to mount /dbdata (Invalid argument)
E:copy_dbdata_media:Can't mount /dbdata
your storage not prepared yet, please use UI menu for format and reboot actions
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Successfully applied multi-CSC.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
Looks familiar doesn't it.
I will read what you did and see if it helps, however the way I am going I will probably be back with more questions.
Update 2
Uh-Oh. That is the recovery file and procedure I tried and ended up where I am. I think it is obvious now that I am doing something very wrong.
info part 2
please ignore
info 3
please ignore
Theodoric47 said:
I was trying to install the IcyFusion ROM when I ran into difficulty. If I was attempting to convert to EXT4, I sure did not know that I was trying to do that. And I was not trying restore a CWM backup. I had unlocked and rooted the device awhile back. I had the "yp-g1cwyxaa.tar" ROM from this thread >http://forum.xda-developers.com/showthread.php?t=1512331< running fine and was enjoying the player in all its rooted glory. But because I can never leave well enough alone, I wanted to try the "IcyFusion_v2.3_GIUEKI8" ROM. To be honest I am not sure what I did wrong in the process.
I see in the instructions that I specified that I have been trying to follow that there are instructions "Special instructions for people coming from CM7". Is this the route I need to take? I have rooted several devices including my Nook Tablet, Nexus 7 and my Galaxy Nexus phone with little or no trouble. This does not include the ugly incident with my TF300T that I did brick. At least Asus put in a new motherboard and she is back in operation. Ouch, that cost me. Like I said, I can never leave well enough alone.
I hope this info helps people help me. Thanks.
Click to expand...
Click to collapse
Icy Fusion is a piece of cake and very stable. If something got jacked up during that it was probably a dicey USB connection(as weird as that sounds). I've loaded roms from my laptop and had them fail consistently on one USB port but not on others. Plug headphones into that port? It's fine. Moving on...
I tried EXT4 out and then I loaded up another rom and screwed my device. It sounds like that could be an issue here. The way I fixed it was to flash the bootloader and pit at the same time with repartition checked(in Odin). From there could load the kernel and then rom. Voila! Back to awesome. The only problem is that is you have a pretty good chance of doing irreparable damage(literally cannot come back from, "it's now a paper weight" damage).
You're not sure what you did, so...wait for smart people to show up. If you can remember anything more about the steps you took please add that so folks are better equipped to help you.
close but not quite
SGP4isokay said:
Icy Fusion is a piece of cake and very stable. If something got jacked up during that it was probably a dicey USB connection(as weird as that sounds). I've loaded roms from my laptop and had them fail consistently on one USB port but not on others. Plug headphones into that port? It's fine. Moving on...
I tried EXT4 out and then I loaded up another rom and screwed my device. It sounds like that could be an issue here. The way I fixed it was to flash the bootloader and pit at the same time with repartition checked(in Odin). From there could load the kernel and then rom. Voila! Back to awesome. The only problem is that is you have a pretty good chance of doing irreparable damage(literally cannot come back from, "it's now a paper weight" damage).
You're not sure what you did, so...wait for smart people to show up. If you can remember anything more about the steps you took please add that so folks are better equipped to help you.
Click to expand...
Click to collapse
I used Odin to install the bootloader and pit file successfully.>YP-G1CWYXAA_Bootloader< and >Samsung Galaxy Player 4.0 U.S. 8GB.pit<.
Then I used Odin and installed the kernel >STeVEs-3.0-USA< after it reboots to recovery, I clear the cache, clear the dalvic cache and factory reset. Then I flashed the >yp-g1cwxaa< ROM. She boots up and woohoo I see the Samsung splash screen for the first time in days. However it is now in a bootloop and keeps reloading the splash screen. I tried the same process with >IcyFusion_v2.3_G1UEKI8< and just got a solid Samsung logo. While I am happy to have made this much progress, I am obviously doing something wrong. Sorry if this is long but I was told that the more the info the more the possible help.
Thanks
Theodoric47 said:
I used Odin to install the bootloader and pit file successfully.>YP-G1CWYXAA_Bootloader< and >Samsung Galaxy Player 4.0 U.S. 8GB.pit<.
Then I used Odin and installed the kernel >STeVEs-3.0-USA< after it reboots to recovery, I clear the cache, clear the dalvic cache and factory reset. Then I flashed the >yp-g1cwxaa< ROM. She boots up and woohoo I see the Samsung splash screen for the first time in days. However it is now in a bootloop and keeps reloading the splash screen. I tried the same process with >IcyFusion_v2.3_G1UEKI8< and just got a solid Samsung logo. While I am happy to have made this much progress, I am obviously doing something wrong. Sorry if this is long but I was told that the more the info the more the possible help.
Thanks
Click to expand...
Click to collapse
I think you should use terrasilent kernel instead of steves kernel as this kernel cause bootloop. I think you got it but the problem was caused by steves kernel booting recovery. That's how I bricked my player the first time. Now I always use terrasilent as the only known issue is the data wipe when you mount something in recovery. So you should redo everything using terrasilent. Hope this help.
terrasilent
ti-pich said:
I think you should use terrasilent kernel instead of steves kernel as this kernel cause bootloop. I think you got it but the problem was caused by steves kernel booting recovery. That's how I bricked my player the first time. Now I always use terrasilent as the only known issue is the data wipe when you mount something in recovery. So you should redo everything using terrasilent. Hope this help.
Click to expand...
Click to collapse
Tried the new kernel and I have the same splash screen boot loop. I guess I will try a different bootloader next. Drat so close.
UPDATE
Woot! After a few tries with different pit files and kernels she is now running IcyFusion. I have my player back. Thank you everyone for your tips, links and threads. You helped me recover my device and taught my allot about it at the same time. I only wish I could return the favors, but I think it is obvious that I am a noob at this even after a year of tinkering.
i have the same exact issue, only i was coming from ics and got stuck trying to restore efs and all that. I managed to restore efs but no matter what i flash it leads me right back to the #manual mode#. Any help will be greatly appreciated
EFS
Ayoodannyx said:
i have the same exact issue, only i was coming from ics and got stuck trying to restore efs and all that. I managed to restore efs but no matter what i flash it leads me right back to the #manual mode#. Any help will be greatly appreciated
Click to expand...
Click to collapse
I have no experience with efs at all. I used Odin to restore my device, and I am not completely satisfied with that as it is. But at least it is working. I can try to tell you what I did, but as I said I doubt I can help you with efs.
Theodoric47 said:
I have no experience with efs at all. I used Odin to restore my device, and I am not completely satisfied with that as it is. But at least it is working. I can try to tell you what I did, but as I said I doubt I can help you with efs.
Click to expand...
Click to collapse
i believe i fixed my efs because it no longer gives me errors about efs, but whenever it starts up , it goes straight to manual mode and gets stuck there
Yo.
So nothing whatsoever seems to be able to make this phone boot into recovery. Whether its a soft or hard boot, it just will not happen. It will always boot as normal. I'm so frustrated and completely stumped.
Any ideas?
James Bartlett said:
Yo.
So nothing whatsoever seems to be able to make this phone boot into recovery. Whether its a soft or hard boot, it just will not happen. It will always boot as normal. I'm so frustrated and completely stumped.
Any ideas?
Click to expand...
Click to collapse
How did you install recovery?
How are you trying to boot into recovery?
blueether said:
How did you install recovery?
How are you trying to boot into recovery?
Click to expand...
Click to collapse
Ah man, you've got me. This is all in the hope of installing a custom rom. Installing the recovery was one of a few things I hadn't done before. I think I did it using Fastboot. I've got a head like a sieve. More frustratingly, my own PC died a death a few days ago, so A) I haven't got whatever stuff I downloaded so cant refer to that to see what I did, and B) anything from here on would ideally be done without a computer, although I could probably borrow one if needed. Can you use Fastboot to install a custom recovery? If so, then thats how I did it. I remember downloading a .img file on the PC and doing something from there. Sorry I couldn't be more clear, and thanks for your help buddy.
Sorry, I missed the second question there. I have tried a number of ways to boot into recovery. Holding vol-up or vol-down while powering on, or a handful of apps that have a boot into recovery option. I've tried using CWM's Rom Manager to install the PA rom .img I have saved on the phone, but that is telling me I need to install CW recovery, and then says its not available for my device. Confused as hell about that one. I feel that once I'm in recovery I'm golden. I don't know if this is relevant, but at the minute, I don't have write access to /system, so I guess this would be a half root job.
You still having issues? I can help and yes you will need a computer and you will need to download the android SDK and set that up.. Let me know
A good day to all!
I have had an issue with my S6 edge (SM-G925F, Philippines Globe Carrier Version) for months now wherein it keeps restarting/crashing. The problem persists so randomly, sometimes multiple times a day or sometimes a day or two without it. I've already tried everything I could find in the internet, such as; deleting the cache in recovery, factory wiping the phone, and flashing the newest firmware i found for it on sammobile. Noting seemed to work. This is my last attempt in fixing the phone before I give up. I hope someone can give me good advice about this.
So nobody knows how to fix this? I don't care if it's a hardware problem i just wanna know
yh man,same problem...i cant even boot to the system..is your led flashing blue?
buzzsaw345 said:
So nobody knows how to fix this? I don't care if it's a hardware problem i just wanna know
Click to expand...
Click to collapse
Is the phone currently working?
It sounds like it could be the hardware failing, could be the emmc failing.
The only thing to suggest at this point is to wipe data/cache in recovery and flash a new firmware.
Or try a custom ROM. If it happens on the custom ROM also then it's possibly hardware.
pexluka said:
yh man,same problem...i cant even boot to the system..is your led flashing blue?
Click to expand...
Click to collapse
Mine can actually boot to the system but it always crashes after some time of use.
callumbr1 said:
Is the phone currently working?
It sounds like it could be the hardware failing, could be the emmc failing.
The only thing to suggest at this point is to wipe data/cache in recovery and flash a new firmware.
Or try a custom ROM. If it happens on the custom ROM also then it's possibly hardware.
Click to expand...
Click to collapse
That's EXACTLY what i was thinking although i did not know that was the name of the part. I was just thinking the memory module was maybe defective already. Dang it so the logic board should be replaced right? Because as far as I know the memory is soldered to the board and hard to remove by itself let alone replacing it.
I've already tried the wiping of data/cache and flashed the newest firmware using Odin but the problem still persists.
Also tried the custom ROM and I've tried a lot of them non actually boots to the system. Only flashing the official firmware allows me to boot to the system.
Thank you for the reply I will now just give up on this and just buy a OnePlus 3T.
buzzsaw345 said:
That's EXACTLY what i was thinking although i did not know that was the name of the part. I was just thinking the memory module was maybe defective already. Dang it so the logic board should be replaced right? Because as far as I know the memory is soldered to the board and hard to remove by itself let alone replacing it.
I've already tried the wiping of data/cache and flashed the newest firmware using Odin but the problem still persists.
Also tried the custom ROM and I've tried a lot of them non actually boots to the system. Only flashing the official firmware allows me to boot to the system.
Thank you for the reply I will now just give up on this and just buy a OnePlus 3T.
Click to expand...
Click to collapse
If it's the emmc then only way to fix is to replace the full motherboard, which isn't cheap.
It's a known problem on note 4. Emmc chip fails and eventually completely packs in.
Which custom Roms did you try? Carhd rom is a good one to try very reliable. Also when flashing a custom ROM it can take 20-30 minutes to boot into the system.
callumbr1 said:
If it's the emmc then only way to fix is to replace the full motherboard, which isn't cheap.
It's a known problem on note 4. Emmc chip fails and eventually completely packs in.
Which custom Roms did you try? Carhd rom is a good one to try very reliable. Also when flashing a custom ROM it can take 20-30 minutes to boot into the system.
Click to expand...
Click to collapse
True they are very expensive that's why I'd rather just buy a new phone. I just didn't want to give up such good hardware until I've tried everything.
Oh really? I wonder why that's the case
I actually forgot which ones already but I'm sure I tried Carhd and it didn't boot for more than an hour. But I'll go and check again just to be thorough.
buzzsaw345 said:
True they are very expensive that's why I'd rather just buy a new phone. I just didn't want to give up such good hardware until I've tried everything.
Oh really? I wonder why that's the case
I actually forgot which ones already but I'm sure I tried Carhd and it didn't boot for more than an hour. But I'll go and check again just to be thorough.
Click to expand...
Click to collapse
Yeah it's a shame really. I could be wrong that might not occur on yours. Normally when you get emmc failure, the phone will reboot to download mode and give you an error along the lines of emmc Write fail. And then keep repeating this.
3T is a good choice to go for if that's what you decide
callumbr1 said:
Yeah it's a shame really. I could be wrong that might not occur on yours. Normally when you get emmc failure, the phone will reboot to download mode and give you an error along the lines of emmc Write fail. And then keep repeating this.
3T is a good choice to go for if that's what you decide
Click to expand...
Click to collapse
It's alright I feel like whatever the hardware issue is it'll require the motherboard to be swapped out anyways. I can finally let the phone rest in peace haha thank you very much.
Yeah it's perfect for an android enthusiast. Already ordered one. Good bye and thanks again!
buzzsaw345 said:
It's alright I feel like whatever the hardware issue is it'll require the motherboard to be swapped out anyways. I can finally let the phone rest in peace haha thank you very much.
Yeah it's perfect for an android enthusiast. Already ordered one. Good bye and thanks again!
Click to expand...
Click to collapse
No problem buddy enjoy your one plus 3
thanks guys,i get the same problem,no rom wants to boot,i can install twrp and custom roms ut cant boot the rom..i once managed to oot to i think it was custom rom,but apps still kept crashing and i couldnt finish the welcoming screen
i got it with android m and apps were crashing all the time,and phone was restarting..
so motheroard it is?
pexluka said:
thanks guys,i get the same problem,no rom wants to boot,i can install twrp and custom roms ut cant boot the rom..i once managed to oot to i think it was custom rom,but apps still kept crashing and i couldnt finish the welcoming screen
i got it with android m and apps were crashing all the time,and phone was restarting..
so motheroard it is?
Click to expand...
Click to collapse
Wouldn't say it was motherboard yet. After you flash your rom you need to boot to recovery and wipe data/cache. This will fix the apps crashing
done,cant boot the system.
gave a visit to a few services,they sad around 50e would be reparation,but im student and now dont have cash for that ****..you have any other suggestions? i tried custom roms,at first magisk would always faild,last time it was ok but still couldnt boot
pexluka said:
done,cant boot the system.
gave a visit to a few services,they sad around 50e would be reparation,but im student and now dont have cash for that ****..you have any other suggestions? i tried custom roms,at first magisk would always faild,last time it was ok but still couldnt boot
Click to expand...
Click to collapse
Do not pay for it. Chances are if you can't fix it they can't either.
So have you tried flashing stock firmware?
What Android version do you have and what region? What's full model number g925?
Reduce the cpu frequencies to 1200-800mhz for big and little and userspace governor. This the only fix.
ok,so one more thing,on the glass back of the phone sits one imei that is not correct,and on the battery is another,which reports 64g version,while next to that number is printed 32gb and phone actually has 32gb lool
it is supposed to be g925f,but after i installed some custom rom,pc showed it as g925s? i think it is due to rom signing the wrong model number
the last thing i have done was yesterday,and it was flashing firmware through kies again.
and this is what i get :
s6 edge powered by android,followed by blue screen 'installing system update',and then recovery
in the recovery,i get this :
android recovery
samsung/zeroltexx/zerolte
7.0/NRD90M/G925FXXU5EQBG
user/release-keys
*recovery options*
No suppoer SINGLE-SKU
Supported API: 3
dm-verity error...
i realy dont know what else to try,and i am open to all suggestions..i have read that emmc storage is broken so this kind of problems can occur,so maybe service would do that?
thank you,i know this is confusing and boring problem
i tried with odin once more,and it failed at 25% instaing system update,then i restarted it and it got up to 32% and started erasing and it turned off..tf with this phone?? i guess its broken...
pexluka said:
i tried with odin once more,and it failed at 25% instaing system update,then i restarted it and it got up to 32% and started erasing and it turned off..tf with this phone?? i guess its broken...
Click to expand...
Click to collapse
https://www.sammobile.com/firmwares/galaxy-s6-edge/SM-G925F/VOD/download/G925FXXU5EQBG/125195/
Download and flash that firmwsre through odin before you try anything else. Let me know what happens.
I can tell you it's likely not emmc failure. For this you would get random reboots and it would reboot to download mode. There you would have an error emmc_write_error.
wowo thanks,i just gave up on that phone,i will try again,i will report back!
just one question,why vodafone?
oh,and i did have random reboots on android m,but it would reboot to optimizing android and boot