So I was running a custom rom for months now for my N910T without issue but yesterday the phone suddenly rebooted by itself while I was using it and would keep rebooting roughly every 3min.
I backed up everything in TWRP and wiped everything to reboot into a clean rom like factory reset but that didn't work as everything was still there and nothing was wiped. So I tried to flash a new rom but it failed and gave an error E: cannot execute upgrade binary.
I'm on TWRP 2.8.1.1 so I can't flash a TWRP update (have to be on 2.8.4 or above) and thought my recovery was too old. I then plugged phone in download mode and used ODIN to flash a new TWRP. It would write fail every time, no matter what I changed. I tried to install different versions of recovery and used different versions of ODIN with no success.
I also changed different cables and ports. I then tried to flash a stock rom through ODIN but it also says write fail. Basically I tried everything and searched on XDA and google and tried every method I came across. Anyone have this issue or suggestions?
tldr: Phone N910T reboots from home screen, write fail flash from ODIN and fail flash from TWRP recovery. Can't use phone because it would boot to home screen for a few min then just reboot again. Help!
tiskewlio said:
So I was running a custom rom for months now for my N910T without issue but yesterday the phone suddenly rebooted by itself while I was using it and would keep rebooting roughly every 3min.
I backed up everything in TWRP and wiped everything to reboot into a clean rom like factory reset but that didn't work as everything was still there and nothing was wiped. So I tried to flash a new rom but it failed and gave an error E: cannot execute upgrade binary.
I'm on TWRP 2.8.1.1 so I can't flash a TWRP update (have to be on 2.8.4 or above) and thought my recovery was too old. I then plugged phone in download mode and used ODIN to flash a new TWRP. It would write fail every time, no matter what I changed. I tried to install different versions of recovery and used different versions of ODIN with no success.
I also changed different cables and ports. I then tried to flash a stock rom through ODIN but it also says write fail. Basically I tried everything and searched on XDA and google and tried every method I came across. Anyone have this issue or suggestions?
tldr: Phone N910T reboots from home screen, write fail flash from ODIN and fail flash from TWRP recovery. Can't use phone because it would boot to home screen for a few min then just reboot again. Help!
Click to expand...
Click to collapse
have you tried doing a factory reset/data wipe
xnknown said:
have you tried doing a factory reset/data wipe
Click to expand...
Click to collapse
Yes I tried every wipe option possible. Wipe system, boots right into rom. Wipe internal, everything still there. Wipe data, factory reset, everything still there.
tiskewlio said:
Yes I tried every wipe option possible. Wipe system, boots right into rom. Wipe internal, everything still there. Wipe data, factory reset, everything still there.
Click to expand...
Click to collapse
Then something I'm your phones been corrupted probably, your going to have to rma for a new device
has anybody come up with a solution to this problem im having serious boot and loading issues. i have flashed many roms and have never had a problem. i odin flashed the cog2 firmware then twrp flashed the tekxodus rom. something happened changing permissions with the built in setting with the rom and twrp was lost and i cant get back to a usable phone. odin flashed everything i can find for my phone and its not working everything either falis or goes to loop.
You probably corrupted your partition doing something wrong
Related
Hi folks,
I tried updating my S plus to ICS today by following the instructions listed here:
theandroidsoul.com/galaxy-s-plus-i9001-ice-cream-sandwich-update-install-cyanogenmod-9-cm9-pretty-good-and-working-rom
I read through the instructions and it looked pretty simple. I successfully installed Team Win recovery, performed a backup, wiped, and then installed the CM9 rom.
After the installation, the phone just boots back into Team Win recovery. I tried reverting to the backup, but it still just boots to recovery every time.
Now that I'm stuck in TeamWin recovery, I'm at a loss on what to try next .
Does anyone have any insight on how I can fix the problem?
Thanks,
Evan
Sometimes when you flash new Recovery (usually when replacing stock recovery with modified recovery for the first time) you get stuck at bootloop. It means /boot partition was damaged. After flashing TWRP did you restart your phone and it booted correctly, or did you install everything (TWRP, got backup, wipe and install new ROM) at once?
There is a guide for i9001 bootloops
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001#Boot-loop
divibyzero said:
Sometimes when you flash new Recovery (usually when replacing stock recovery with modified recovery for the first time) you get stuck at bootloop. It means /boot partition was damaged. After flashing TWRP did you restart your phone and it booted correctly, or did you install everything (TWRP, got backup, wipe and install new ROM) at once?
There is a guide for i9001 bootloops
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001#Boot-loop
Click to expand...
Click to collapse
So is reflashing in Odin what you are suggesting? Sorry if I'm misunderstanding.
And yes, after I flashed TWRP it booted fine, the 2nd time I went into recovery, performed the backup, wiped, then flashed the rom. I've tried wiping both the cache's with no success. I've also tried reflashing the rom, wiping the cache's, restoring with the backup, wiping cache's again... nothing seems to be working
What would be different if I had installed everything (TWRP, backup, wipe, rom) at the same time?
*Edit* Reflashed through Odin and it worked great! Thanks for the help, I'm a little scared to start messing with the phone again, but ICS is tempting...
Got the rom working with a fresh backup after fixing the bootloop. Thanks again for the link divibyzero, the troubleshooting steps solved the problem, whatever it was, and now its running ICS
These Samsungs S+'s seem to be a little more finiky than my HTC.
I am still stuck in CWM Recovery mod ! When I start Download mode, I dont have ODIN option ..only Download mod start screen! Can anybody help me?
Dapper SRB said:
I am still stuck in CWM Recovery mod ! When I start Download mode, I dont have ODIN option ..only Download mod start screen! Can anybody help me?
Click to expand...
Click to collapse
What do you mean by "don't have ODIN option"?
Is bootloader.tar which used to repair bootloop problem usable on ICS roms for SGS+??
alireza7991 said:
Is bootloader.tar which used to repair bootloop problem usable on ICS roms for SGS+??
Click to expand...
Click to collapse
yup, you can use bootloader or http://forum.xda-developers.com/showpost.php?p=32655216&postcount=17 CWM with AriesVe.ops
evan8683 said:
Hi folks,
I tried updating my S plus to ICS today by following the instructions listed here:
theandroidsoul.com/galaxy-s-plus-i9001-ice-cream-sandwich-update-install-cyanogenmod-9-cm9-pretty-good-and-working-rom
I read through the instructions and it looked pretty simple. I successfully installed Team Win recovery, performed a backup, wiped, and then installed the CM9 rom.
After the installation, the phone just boots back into Team Win recovery. I tried reverting to the backup, but it still just boots to recovery every time.
Now that I'm stuck in TeamWin recovery, I'm at a loss on what to try next .
Does anyone have any insight on how I can fix the problem?
Thanks,
Evan
Click to expand...
Click to collapse
Hello guys,
I think have the same problem, this morning I installed the Team Win recovery and after a reboot my phone come into recovery mode and even after a furthr reboot I'm blocked in a bootloop that leads me always on Team Win recovery.
I tried to wipe cache, dalvik cache, factory reset and even a wipe of the system but nothing happen.
I reinstalled rom but without success.
There is a way to fix this through adb?
Advanced thanks for help
Max.
krisslake said:
Hello guys,
I think have the same problem, this morning I installed the Team Win recovery and after a reboot my phone come into recovery mode and even after a furthr reboot I'm blocked in a bootloop that leads me always on Team Win recovery.
I tried to wipe cache, dalvik cache, factory reset and even a wipe of the system but nothing happen.
I reinstalled rom but without success.
There is a way to fix this through adb?
Advanced thanks for help
Max.
Click to expand...
Click to collapse
You didn't specify, so I'll assume you have an i9001, if this is not the case, you probably shouldn't follow these instructions
Just reflash the bootloader as explained here (http://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330) and you'll be fine. I had the exact same problem when I had installed CWM on my own device. It's not with adb, but it's not like you have to do a lot of effort to get Odin or anything and it will fix your device.
Marshian said:
You didn't specify, so I'll assume you have an i9001, if this is not the case, you probably shouldn't follow these instructions
Just reflash the bootloader as explained here (http://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330) and you'll be fine. I had the exact same problem when I had installed CWM on my own device. It's not with adb, but it's not like you have to do a lot of effort to get Odin or anything and it will fix your device.
Click to expand...
Click to collapse
Luckily I found a windows system
Istructions you report was perfect for my case...seem I solved my problem...thanks again.
There is some i need to do for report I solved my problem ?
Bye Max.
[Boot-Loop] Can I use dd to flash bootloader?
Guys, has anyone tried to use dd to flash bootloader partition?
I assume dd if=boot.img of=/dev/block/mmcblk0p8 bs=512 should work
Can somebody attach boot.img taken with dd so I could test?
error - can t acces system csc/cnx/system
hello. I have a problem. I had installed on the phone cm10. Now I switched to cm 9 but since we locked in botloader and I returned with odin. recowery mode now you did not have the option install from sd / card only update. My problem is that now go phone but I can not install gapps. ie install it says the installation is complete, restart give when I see me many times with yellow writing including my error appears so: can t access system csc / CNX / system. and after I start the application from google. to say you've tried many variations and if you try recovery-clockwork-5.5.0.4-phone crashes every time. Please help ... (I tried many variations of gapps). thanks in advance.back with another caveat: any clockwork I try to install say installation aborted. and in the recovery mode screen down to write I / / / status = 0 / / /
evan8683 said:
So is reflashing in Odin what you are suggesting? Sorry if I'm misunderstanding.
And yes, after I flashed TWRP it booted fine, the 2nd time I went into recovery, performed the backup, wiped, then flashed the rom. I've tried wiping both the cache's with no success. I've also tried reflashing the rom, wiping the cache's, restoring with the backup, wiping cache's again... nothing seems to be working
What would be different if I had installed everything (TWRP, backup, wipe, rom) at the same time?
*Edit* Reflashed through Odin and it worked great! Thanks for the help, I'm a little scared to start messing with the phone again, but ICS is tempting...
Click to expand...
Click to collapse
Hi Evan which release of Odin did you use I am also facing the same problem for the past 28 hours and not been able to resolve it. The problem is thay the Com Port does not pop up basically the phone is not being recognised by the computer.
Please help.
sunbaj said:
The problem is thay the Com Port does not pop up basically the phone is not being recognised by the computer. Please help.
Click to expand...
Click to collapse
You must properly install Samsung mobile drivers on your PC, kill Samsung Kies process (or even better: uninstall Kies) and enable USB debugging on your phone. Then it will work.
tetakpatak said:
You must properly install Samsung mobile drivers on your PC, kill Samsung Kies process (or even better: uninstall Kies) and enable USB debugging on your phone. Then it will work.
Click to expand...
Click to collapse
The problem was that I was using Windows 8. I was able to resolve the issue after doing it on Windows XP.
I have an S5830D that I flash an CM7 rom to (APOCALYPSE-FINAL), I'm now looking at getting back to stock. I'm having trouble getting my CWM restore back. Now after doing some searching I realized I would need to flash a stock firmware version through odin. I went out and found what i believe is the correct firmware version for this Koodo model (the name is S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4_HOME.tar.md5) and tried to flash it.
Everything in odin goes through fine up to the point where it restarts the phone, Ill attach a screenshot of what shows up for me. After the screen shows up is when I get stuck in a bootloop where the phone model shows, then the koodo bootanimation shows followed by the samsung logo. I should note though I still have complete access to recovery, the downloader mode, and even the CM rom when i restore that backup. The fact I have access to all those gives me hope as I'm sure this could be reversed.
Any advice on how I can restore this phone to stock would be greatly appreciated. I'm not very familiar with samsung devices so please try to be patient with me as I realize I have gotten into something over my head.
PS Sorry about the glare on the image its the best I could do as it disappears quickly.
Jeklund said:
I have an S5830D that I flash an CM7 rom to (APOCALYPSE-FINAL), I'm now looking at getting back to stock. I'm having trouble getting my CWM restore back. Now after doing some searching I realized I would need to flash a stock firmware version through odin. I went out and found what i believe is the correct firmware version for this Koodo model (the name is S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4_HOME.tar.md5) and tried to flash it.
Everything in odin goes through fine up to the point where it restarts the phone, Ill attach a screenshot of what shows up for me. After the screen shows up is when I get stuck in a bootloop where the phone model shows, then the koodo bootanimation shows followed by the samsung logo. I should note though I still have complete access to recovery, the downloader mode, and even the CM rom when i restore that backup. The fact I have access to all those gives me hope as I'm sure this could be reversed.
Any advice on how I can restore this phone to stock would be greatly appreciated. I'm not very familiar with samsung devices so please try to be patient with me as I realize I have gotten into something over my head.
PS Sorry about the glare on the image its the best I could do as it disappears quickly.
Click to expand...
Click to collapse
If you have complete access to recovery mode, try wiping data and cache after flashing with Odin. That does the trick for me when I have a bootloop after flashing with Odin.
ImSoBored said:
If you have complete access to recovery mode, try wiping data and cache after flashing with Odin. That does the trick for me when I have a bootloop after flashing with Odin.
Click to expand...
Click to collapse
Agreed... reboot into recovery and clear cache and dalvik cache and then reboot.
So I've just completed a new flash with odin, I went in and flashed cwm then proceeded to factory reset, wipe cache, wipe dalvik, and I even do battery reset. Every wipe goes fine except for when I attempt to do the factory reset I received the following error:
Code:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
Even after those wipes it still bootloops but thats most likely as the factory reset didn't work.
Jeklund said:
So I've just completed a new flash with odin, I went in and flashed cwm then proceeded to factory reset, wipe cache, wipe dalvik, and I even do battery reset. Every wipe goes fine except for when I attempt to do the factory reset I received the following error:
Code:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
Even after those wipes it still bootloops but thats most likely as the factory reset didn't work.
Click to expand...
Click to collapse
Try not using CWM, or your SD card may be corrupt and you have to format it, I'm not sure though.
ImSoBored said:
Try not using CWM, or your SD card may be corrupt and you have to format it, I'm not sure though.
Click to expand...
Click to collapse
That did it, for some reason I had this thought in my head I had to flash cwm right away and clear stuff that way. Once odin finished I went in recovery and wiped data and cache through the stock recovery and it booted right up. Thanks for the help really appreciate it.
Hallo together,
I seem to have done something wrong while trying to flash the rom "RazRi_JB_X-2014-Jul-16".
Here is what i did:
- Unlocked to bootloader using official Motorola homepage
- Flashed CWM (non-touch) recovery using "Recovery Flasher by LeBobo v1.7", USB-Debugging was on
- Rebooted into bootloader and flashed "RAZRiRoot2" to prevent Stock-ROM from overwriting the recovery
- Tried to install the Custom ROM using CWM, but it fails to wipe cache (stuck on line "Formatting /cache")
Because it didn't work, i tried to reset everything as it was before to be able to try again - flashed stock-recovery using the Recovery Flasher by LeBobo, booted into bootloader and selected "Factory". The cell is now just showing the "Warning bootloader unlocked" warning and nothing else happens.
When i try to select the recovery in the bootloader menu, an image of a Android laying on its back with an opened hatch and a red warning symbol showing a "!" appears and nothing else happens.
I seem to have bricked my device, because i cant't really do anything now - is there any solution?
I read through different topics but could not find a real solution to this particular problem...
Thank you so much in advance for your help!
It's not bricked
At the moment u enter stock recovery with that android and red warning sy,bol, u need to press bot volume up + downp. Than it will enter stock recovery mode.
Those are the following things u can do to get custom rom,
1. Flash another recovery, cwm touch, cwm non-touch, twrp. They all work a little different.
2. Flash the custom rom and wipe everything, The wip can take some time. sometimes it will be seconds, sometimes it will take a couple of minutes. Every recovery behaves different, and every flash/wipe too.
3. enjoy
If u really want to go back to stock, flash your stock JB firmware by RSD-Lite.
Thank you very much for your answer. I restored the stock rom using RSD Lite and did a clean install of TWRP.
Then I did a Factory Reset and started to install the custom ROM.
The TWRP is now stuck at "Flashing File 1 of 1 /external_sd/RazRi_JB_X-2014-Jul-16.zip".
Is it normal that it takes more than five minutes or is something going wrong here? Is there something i forgot?
StarGeneral said:
Thank you very much for your answer. I restored the stock rom using RSD Lite and did a clean install of TWRP.
Then I did a Factory Reset and started to install the custom ROM.
The TWRP is now stuck at "Flashing File 1 of 1 /external_sd/RazRi_JB_X-2014-Jul-16.zip".
Is it normal that it takes more than five minutes or is something going wrong here? Is there something i forgot?
Click to expand...
Click to collapse
5 minutes is a bit too much. But that's the problem with this device. Every device behaves different and we haven't found out a solution too it.
At the moment i can't do much for you. I can only say try to wipe the partitions mannualy. Wipe system, data and cache. and mount system. And then try to install it. Maybe if that doesnt do the trick try again another recovery.
This from KTR-ROM
Code:
- Enter in TWRP or CWM
- Wipes required: data, system, cache y dalvik
*In CWM mount system must format before (Mount and storage -> Mount system)
Thanks again - that was it.
For some reason, TWRP did not automatically wipe the system-partition. It had to be mounted + wiped manually.
Not the custom ROM is up and running well. Installation took 35 minutes for some reason though...
Thank you so much for your help!
StarGeneral said:
Thanks again - that was it.
For some reason, TWRP did not automatically wipe the system-partition. It had to be mounted + wiped manually.
Not the custom ROM is up and running well. Installation took 35 minutes for some reason though...
Thank you so much for your help!
Click to expand...
Click to collapse
nice, glad that it worked
I have had several roms, over several devices, over several years. I have never had issues before.
I have Note 4 T-Mobile running 4.4.4. I rooted, installed TWRP and am trying to install cm-12.1-20150509-UNOFFICIAL-temasek-trltetmo
I tried installing a different ROM last night and the same things happen.
When I wipe Cache it removes the TWRP
I install TWRP app, then install TWRP 1.8.6 or whatever using the TWRP app
Reboot into recovery
Flash the ROM and Gapps
Wipe, wipe again just to be safe
Reboot
It goes through the CM logo to where it initializes apps, goes through them all, reboots and does it all again. 2 different ROMs did exactly the same thing. I dont know what im doing wrong. I tried installing TWRP With ADB but it hangs on "waiting for device" When I adb devices my hone shows and I have USB debug turned on. After I finally quit and pulled the battery It said no OS available so I had to DL and reflash stock image.
I am beyond frustrated now,
Any ideas? What info do you need from me?
monkeny said:
I have had several roms, over several devices, over several years. I have never had issues before.
I have Note 4 T-Mobile running 4.4.4. I rooted, installed TWRP and am trying to install cm-12.1-20150509-UNOFFICIAL-temasek-trltetmo
I tried installing a different ROM last night and the same things happen.
When I wipe Cache it removes the TWRP
I install TWRP app, then install TWRP 1.8.6 or whatever using the TWRP app
Reboot into recovery
Flash the ROM and Gapps
Wipe, wipe again just to be safe
Reboot
It goes through the CM logo to where it initializes apps, goes through them all, reboots and does it all again. 2 different ROMs did exactly the same thing. I dont know what im doing wrong. I tried installing TWRP With ADB but it hangs on "waiting for device" When I adb devices my hone shows and I have USB debug turned on. After I finally quit and pulled the battery It said no OS available so I had to DL and reflash stock image.
I am beyond frustrated now,
Any ideas? What info do you need from me?
Click to expand...
Click to collapse
You've got a nightmare. Head back to stock with Odin. Start fresh something with your base is off. Either wrong baseband orkernel but something off
BACARDILIMON said:
You've got a nightmare. Head back to stock with Odin. Start fresh something with your base is off. Either wrong baseband orkernel but something off
Click to expand...
Click to collapse
I just flashed stock, used kies to update to latest and ill try re-rooting and re installing TWRP and doing it all again. this blows.
monkeny said:
I just flashed stock, used kies to update to latest and ill try re-rooting and re installing TWRP and doing it all again. this blows.
Click to expand...
Click to collapse
updated to 5.0.1
Odin flashed CF Auto Rooter
Flashify the TWRP
Rebooted Flashed the above posted ROM and GAPPS
Wiped Data
Rebooted
Stuck in the damn initializing apps boot loop again.
I have no idea what could be the issue. I quit
monkeny said:
updated to 5.0.1
Odin flashed CF Auto Rooter
Flashify the TWRP
Rebooted Flashed the above posted ROM and GAPPS
Wiped Data
Rebooted
Stuck in the damn initializing apps boot loop again.
I have no idea what could be the issue. I quit
Click to expand...
Click to collapse
Which rom u trying
few thoughts.
First verify the MD5 of your download of the rom. make sure it wasn't corrupt. Second. Flash just the rom only and boot, then flash gapps and boot.
nosympathy said:
few thoughts.
First verify the MD5 of your download of the rom. make sure it wasn't corrupt. Second. Flash just the rom only and boot, then flash gapps and boot.
Click to expand...
Click to collapse
I think flashing just the ROM and then gapps did the trick. Seems to be up and stable. Man Ive never had so many issues before blah.
monkeny said:
I think flashing just the ROM and then gapps did the trick. Seems to be up and stable. Man Ive never had so many issues before blah.
Click to expand...
Click to collapse
I have not messed with CM since I had the Note 2, which was until the Note 3 came out. Was a different carrier too. Generally the rule was flash CM then boot then reboot and flash GAPPS. I haven't looked but I would assume it is still the same.
Glad it worked
So I've been attempting to install a rom, ANY rom on my phone and the results always seem to be the same. I boot into TWRP, wipe then install the rom. On reboot, the phone loads up the initial (black) samsung screen. Then buzzes twice and reboots. It will do this infinitely. It happens with any rom I've tried flashing. It has to be something I am missing or doing wrong. Does anyone have an idea what it is? I've even gone as far as completely wiping, odin in a stock image and then adding TWRP again. I just can't seem to figure it out.
re: bootloops
Tharkys said:
So I've been attempting to install a rom, ANY rom on my phone and the results always seem to be the same. I boot into TWRP, wipe then install the rom. On reboot, the phone loads up the initial (black) samsung screen. Then buzzes twice and reboots. It will do this infinitely. It happens with any rom I've tried flashing. It has to be something I am missing or doing wrong. Does anyone have an idea what it is? I've even gone as far as completely wiping, odin in a stock image and then adding TWRP again. I just can't seem to figure it out.
Click to expand...
Click to collapse
You need to ODIN flash the stock original official COG2
firmware & odin flash cf-autoroot and the twrp recovery
before flashing the zip file rom.
Once that's done you can flash any N910T zip file rom in
twrp recovery without any issues.
Make sure to do a full wipe in twrp before you flash any
zip file rom to avoid bootloops and or getting stuck on
the samsung boot logo screen and be sure to do a full
and complete wipe which includes:
"System, Data, Cache, Dalvik Cache and last but not
least do a factory reset.
Good luck,
Have a great day!
Tharkys said:
So I've been attempting to install a rom, ANY rom on my phone and the results always seem to be the same. I boot into TWRP, wipe then install the rom. On reboot, the phone loads up the initial (black) samsung screen. Then buzzes twice and reboots. It will do this infinitely. It happens with any rom I've tried flashing. It has to be something I am missing or doing wrong. Does anyone have an idea what it is? I've even gone as far as completely wiping, odin in a stock image and then adding TWRP again. I just can't seem to figure it out.
Click to expand...
Click to collapse
i dont know if we are having the same problem but try installing the original firmware via odin and see if that works. if it does not then we have the same problem and i dont know how to fix it, now i am stuck with my S4 wait for help from someone to help me fix my note 4