Okay heres what happened: I was attempting to flash a ROM. After making a new backup and flashing that new ROM the device would not boot. So like any normal person would do I then went back into recovery and attempted to restore my backup. Upon restoring the backup, halfway through the device just decides to reboot and boot into the ROM (which was a half restored backup). I tried to boot back into recovery and start the process over however now the device will not boot into the recovery at all. It continues to loop the bootloader logo over and over. Is this a soft brick? Either way, all I want at this point is to be able to restore that backup so I can atleast have it working again. All help is much appreciated.
EDIT: okay i managed to get the recovery loaded, what i may end up doing is loading a saved ROM up and starting from scratch there (TWRP continues to Stop my restore halfway through and reboot the recovery --very frustrating tbh). My question then however would be is there a way to get my data back from my backup once I start fresh? Does tibu allow this or something comparable? I really don't want to lose all that data. Thanks again.
Edit 2: managed to fully resolve issue. delete if neccessary.
HarmonyFlame said:
Okay heres what happened: I was attempting to flash a ROM. After making a new backup and flashing that new ROM the device would not boot. So like any normal person would do I then went back into recovery and attempted to restore my backup. Upon restoring the backup, halfway through the device just decides to reboot and boot into the ROM (which was a half restored backup). I tried to boot back into recovery and start the process over however now the device will not boot into the recovery at all. It continues to loop the bootloader logo over and over. Is this a soft brick? Either way, all I want at this point is to be able to restore that backup so I can atleast have it working again. All help is much appreciated.
EDIT: okay i managed to get the recovery loaded, what i may end up doing is loading a saved ROM up and starting from scratch there (TWRP continues to Stop my restore halfway through and reboot the recovery --very frustrating tbh). My question then however would be is there a way to get my data back from my backup once I start fresh? Does tibu allow this or something comparable? I really don't want to lose all that data. Thanks again.
Edit 2: managed to fully resolve issue. delete if neccessary.
Click to expand...
Click to collapse
How did you get back into recovery? I had paranoid android flashed and i did a factory reset like an idiot. Now i cant boot into recovery - "teamwin" logo freezes and reboots into a continuous loop. I can get into the bootloader but nothing works?
sashennaidoo1 said:
How did you get back into recovery? I had paranoid android flashed and i did a factory reset like an idiot. Now i cant boot into recovery - "teamwin" logo freezes and reboots into a continuous loop. I can get into the bootloader but nothing works?
Click to expand...
Click to collapse
I'll tell you what I literally did.
When the device was bootlooping the teamwin logo, I booted into fastboot and powered my device completely off. I then waited an hour as I was a little tired with what was happening to take care of something. After that hour I turned it on and it suddenly booted into teamwin recovery. That's exactly all I did. So what I would do is turn the device off for a little bit then try to see if it boots the recovery. If not you will likely have to use the nexus 10 toolkit to reflash the recovery.
Hope that helps.
HarmonyFlame said:
I'll tell you what I literally did.
When the device was bootlooping the teamwin logo, I booted into fastboot and powered my device completely off. I then waited an hour as I was a little tired with what was happening to take care of something. After that hour I turned it on and it suddenly booted into teamwin recovery. That's exactly all I did. So what I would do is turn the device off for a little bit then try to see if it boots the recovery. If not you will likely have to use the nexus 10 toolkit to reflash the recovery.
Hope that helps.
Click to expand...
Click to collapse
Thanks mate! really appreciate it! I have no clue what i did but on one of the reboots, it booted into TWRP and i re-flashed the paranoid android rom and gapps and it worked.
Thanks for above response. Much appreciated!
Just for future reference, both TiBU and ROM Toolbox will restore from a Nandroid backup.
Sent from my Nexus 10 using Tapatalk HD
bruce7373 said:
Just for future reference, both TiBU and ROM Toolbox will restore from a Nandroid backup.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
So I am in this same boat and will probably have to use some toolkit since I have not been able to boot up TWRP. I know I am on 2.4.4.0 or something for TWRP, not 2.5 but would CWM be a better choice since I have run into this now a couple of times? This is the first where it hasn't stopped the recovery boot loop.
Related
I installed CyanogenMod 5.0 last night and when i was finished flashing and turned the phone back on it stayed on the animation screen for about 15 minutes then i just pulled the battery (usually boots to OS much faster). Is this expected when updating the ROM?
if you can boot up into bootloader, then you are ok...did u do a backup b4 flashing?
Yes i can get into bootloader and I followed every step on.
http://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/
If you can get back into the bootloader then you're fine, make sure you followed the steps correctly, if you did a nandroid backup first like you should have then try recoverying that and see if you can boot. The first time you flash a rom it usually takes a while to boot. Luckily you didn't pull it during the radio flash or you would be SOL.
JoshHart said:
If you can get back into the bootloader then you're fine, make sure you followed the steps correctly, if you did a nandroid backup first like you should have then try recoverying that and see if you can boot. The first time you flash a rom it usually takes a while to boot. Luckily you didn't pull it during the radio flash or you would be SOL.
Click to expand...
Click to collapse
I dont think i did nandroid backup, but i can get into bootloader, should i do the whole process over and do a nandroid backup this time?
Wipe your phone.
Flash the ROM, then flash the google add on in his thread.
Reboot.
Go back to recovery.
Make a nandroid.
Reboot.
david1171 said:
Wipe your phone.
Flash the ROM, then flash the google add on in his thread.
Reboot.
Go back to recovery.
Make a nandroid.
Reboot.
Click to expand...
Click to collapse
Do i flash the recovery image again or just flash the rom.
just the rom...you already have the recovery installed
Well i wiped the phone and rebooted now it works fine. Thanks
glad to hear you are back up and running...
First, I searched and read all relevant threads concerning this issue. The five threads that showed up in the search did not help me solve my issue.
So on to my problem. I can no longer flash any rom onto my device. I attempted to flash the first official CM10 nightly (which I recently found out was not flashing properly for others) and had no success. I simply got a black screen and nothing more. I eventually got back into TWRP (v2.2.1.4) to try and Nandroid restore, but I noticed that /data was not formatting and the restore failed. Every time I would slide the bar across to confirm the restore TWRP would reboot itself. I then flashed CWM (v6.0.1.0) and the same problems were there. After that I flashed an earlier version of TWRP and successfully restored the backup. I'm not 100% sure how it was successful. So I decided to try flashing another ROM and no go. Same problems. Anyone have any ideas? When I was using CWM I got the error message below.
Code:
E: unable to locate volume information
E: unable to open ums lunfile '/sys/devices/platform/usb_mass_storage/lun0/file'
E: unable to format data
I'm running Bugless Beast with Motley #219
I'm having similar, if not identical problems. After flashing TWRP 2.2.1.4, I tried flashing a rom and gapps; the tablet would boot endlessly into recovery. Nothing I did would do anything, so I flashed the stock image to start over. This time, I used CWM 6.0.1.0 touch to make sure that it wasn't the recovery that was causing the problem. However, now after flashing the rom and gapps, instead of booting into recovery, I got stuck at a black screen and had to hold the power button in order to get back to the bootloader.
Now, like you, it seems I can't flash any roms anymore. It's frustrating to say the least.
Sent from my Galaxy Nexus using xda app-developers app
aznxk3vi17 said:
I'm having similar, if not identical problems. After flashing TWRP 2.2.1.4, I tried flashing a rom and gapps; the tablet would boot endlessly into recovery. Nothing I did would do anything, so I flashed the stock image to start over. This time, I used CWM 6.0.1.0 touch to make sure that it wasn't the recovery that was causing the problem. However, now after flashing the rom and gapps, instead of booting into recovery, I got stuck at a black screen and had to hold the power button in order to get back to the bootloader.
Now, like you, it seems I can't flash any roms anymore. It's frustrating to say the least.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
What rom did you attempt to flash?
elementur said:
What rom did you attempt to flash?
Click to expand...
Click to collapse
So do I.I attempted to flash the first official CM10 8.18 nightly and had no success. I just got a black screen.Even more I boot into bootloader and choose to boot into recover but just stay at google logo.I try to flash recover once more,but just can't boot into recover!!
I have the same problem, i flashed the cm10 nightly which I learned would not boot. No I have no backup to boot to, and cannot even push a new rom to the storage to try to install.
Shano56 said:
I have the same problem, i flashed the cm10 nightly which I learned would not boot. No I have no backup to boot to, and cannot even push a new rom to the storage to try to install.
Click to expand...
Click to collapse
Can't boot into recover,does anyone know what is wrong?When it is in android I can use APM boot into recover or via ADB,but unusually when it is in the bootloader I choose to boot into recover,it just stay at google logo!!What it is going wrong?
phiracle said:
Can't boot into recover,does anyone know what is wrong?When it is in android I can use APM boot into recover or via ADB,but unusually when it is in the bootloader I choose to boot into recover,it just stay at google logo!!What it is going wrong?
Click to expand...
Click to collapse
There is a bug with the Nexus 7 where you cannot access the recovery through the bootloader. To fix this, boot up into the bootloader on your nexus 7 and, without doing anything, plug it into the computer you used for rooting it and then select the option Restart bootloader and press the power button. Once it gets you back into the bootloader again select Recovery mode and press the power button. It will now get you into the recovery and once you're in recovery you can unplug your tablet from the computer. Note that this fix is not permanent and you will have to do this every time you wish to access your recovery via the bootloader (and this problem is not relevant to the OP's problem).
android1234567 said:
There is a bug with the Nexus 7 where you cannot access the recovery through the bootloader. To fix this, boot up into the bootloader on your nexus 7 and, without doing anything, plug it into the computer you used for rooting it and then select the option Restart bootloader and press the power button. Once it gets you back into the bootloader again select Recovery mode and press the power button. It will now get you into the recovery and once you're in recovery you can unplug your tablet from the computer. Note that this fix is not permanent and you will have to do this every time you wish to access your recovery via the bootloader (and this problem is not relevant to the OP's problem).
Click to expand...
Click to collapse
Thank You Very Much!!!
I am having much the same problem as the OP. I finally rooted my Nexus 7 using WugFresh's Nexus Root Toolkit. It seemed all went well. I chose to use TWRP in a first attempt to install a ROM (I was on rooted stock), and following the instructions for installing my chosen ROM I went into it to wipe cache, Dalvic Cache and data. Both cache and dalvic cache wiped without issue, but when I attempted to wipe /data TWRP simply reported that it failed. With that failing, I did not attempt to install a rom. I was still able to boot out of recovery, but even with repeated attempts wiping data always failed. Is any one aware of any solution or have any suggestions. Thank you!
I had Mint Jelly2.1 installed and everything was working fine.
it started when I had used the APK Hide It Pro. I was in the process of hiding videos and I noticed that my phone got rebooted and got stock in the Samsung boot up image with the Custom Lock image.
I tried nandroid restore, 2 images, but both also failed to restore / bootup.
I tried re-installing ROM and it was successful but during reboot, it will still get stock on the boot image.
Last step.
I used ODIN to restore the stock ROM and ODIN was able to install and reset. And my phone rebooted but still got stock on the Samsung Logo with CUstom Lock Screen.
What else can I do to fix this?
Thank you.
Boot into recovery and do a factory reset. I assume you now have 3e stock recovery because of ODIN. This might or might not help. If you have any questions about recovery, please use the search function for information. If for some reason you still have a custom recovery (TWRP or CWM), try re-flashing an AT&T ROM and Kernel again. Everything you try is at your own risk. Good luck.
scott14719 said:
Boot into recovery and do a factory reset. I assume you now have 3e stock recovery because of ODIN. This might or might not help. If you have any questions about recovery, please use the search function for information. If for some reason you still have a custom recovery (TWRP or CWM), try re-flashing an AT&T ROM and Kernel again. Everything you try is at your own risk. Good luck.
Click to expand...
Click to collapse
I had tried to restore/flash from recovery before ODIN and it all Failed.
Anyway, the last step ODIN restore and it was still stock at the Samsung Logo with Lock image.
I left the phone to charge the whole night and this morning when I turned it on, it was able to start properly with ODIN stock ROM.
I tried to go to recovery, and can only be done manually, and it was not the TWRP recovery but the stock one, with very small characters.
I tried to install Mint Jell2.1 right away but just reboots.
I realized that I might need to root it again and downloaded the Tool and re-loki'ed/rooted and installed TWRP.
Now, I am able to install Mint Jelly 2.1 and restoring all my apps.
I appreciate the comment.
Thank you.
scott14719 said:
Boot into recovery and do a factory reset. I assume you now have 3e stock recovery because of ODIN. This might or might not help. If you have any questions about recovery, please use the search function for information. If for some reason you still have a custom recovery (TWRP or CWM), try re-flashing an AT&T ROM and Kernel again. Everything you try is at your own risk. Good luck.
Click to expand...
Click to collapse
Yeah, every single time I ODIN back to stock, I get stuck at the splash screen also. And rebooting to 3E (factory) recovery and "restore factory defaults" works great.
CZ Eddie said:
Yeah, every single time I ODIN back to stock, I get stuck at the splash screen also. And rebooting to 3E (factory) recovery and "restore factory defaults" works great.
Click to expand...
Click to collapse
I can confirm this works happened to me yesterday.
leoj85 said:
I can confirm this works happened to me yesterday.
Click to expand...
Click to collapse
I am running out of options. I thought I am already out of this stuck on Samsung Logo with Custom Lock icon.
I had ODIN to stock I337UCUAMDL and reset, Ran Loki patch / installed TWRP, intermittently it will get stuck.
I flashed Shoshock 1.9, was able to reboot and setup basic settings.
I manually reboot to check if it was able to fix the problem, but no.
I am stuck again and don't know what is the next step for trouble shooting it.
any advise will be appreciated.
Thank you.
I got stuck to 1st boot image of Samsung with Lock Custom Icon.
I did format data/factory reset/clear cache/dalvik.. all of the wipe ootions.
I flashed a new ROM, successful, rebooted pass the logo and booted fine. I did not change any settings yet and I rebooted to check if it will get stuck again and sure after reboot, it got stuck again on the 1st image that shows up : Samsung Logo with the Lock Custom Icon.
qwer43 said:
I am running out of options. I thought I am already out of this stuck on Samsung Logo with Custom Lock icon.
I had ODIN to stock I337UCUAMDL and reset, Ran Loki patch / installed TWRP, intermittently it will get stuck.
I flashed Shoshock 1.9, was able to reboot and setup basic settings.
I manually reboot to check if it was able to fix the problem, but no.
I am stuck again and don't know what is the next step for trouble shooting it.
any advise will be appreciated.
Thank you.
Click to expand...
Click to collapse
IMPORTANTwhen using*twrp*recoverydo not choose "format data"(that option will ask you to type "yes")what if i did?rom will not boot past "padlock" boot screen orrom will not boot on second reboot*help!! I did, I did*1. sigh2. d/l odin3. d/l odin stock restore MDL4. let it do its thang5. after its complete it will be stuck at padlock6. should have "rtfm" huh?*7. pull battery8. hold home button, vol-up, power at same time9. when phone vibrates, release power, while still holdingvol-up, and home button10. you will now be in "stock recovery"11. wipe factory reset then wipe cache12. reboot*13. swear you will never "ignore instructions"
It first started this morning when my phone suddenly started rebooting while I was using it. Then I thought it as a ROM issue and flashed a new ROM over it. Everytime I try to flash something on system. TWRP Hangs and the phone restarts itself.
Tried repairing data, system partitions from TWRP, same thing happens. Bootloops when I try to repair data partition
Tried restoring nandroid backup. When it says flashing data, TWRP freezes and the phone starts bootlooping.
Can anyone help?
I have tried doing the EFS flash via adb from PC.
I'm stuck with the exact same problem since months.
CallMeAldy said:
I'm stuck with the exact same problem since months.
Click to expand...
Click to collapse
No luck?
Have you tried Claiming Warranty?
try doing a re flash of recovery, because your issue will be to get your recovery working properly or else you cant remount anything else.
StarRavier said:
try doing a re flash of recovery, because your issue will be to get your recovery working properly or else you cant remount anything else.
Click to expand...
Click to collapse
I flashed TWRP 3.0.2,3.0.2-2,3.0.2-3
Loads of it. Tried doing full stock + unroot from Nexus toolkit. That usually fixed all my problems Everytime I was in dire problems like this.
TJ_bab said:
I flashed TWRP 3.0.2,3.0.2-2,3.0.2-3
Loads of it. Tried doing full stock + unroot from Nexus toolkit. That usually fixed all my problems Everytime I was in dire problems like this.
Click to expand...
Click to collapse
I've never used that toolkit. Since day 1, ive used skipsoft android toolkit. just keep on trying. Does it crash at all when doing backups?
StarRavier said:
I've never used that toolkit. Since day 1, ive used skipsoft android toolkit. just keep on trying. Does it crash at all when doing backups?
Click to expand...
Click to collapse
Doesn't crash during backup but crashes during restore.
TJ_bab said:
Doesn't crash during backup but crashes during restore.
Click to expand...
Click to collapse
Well in your case what I would do is a backup,
Then wipe, flash custom rom. Use phone til reboot.
If reboot, flash stock IMG. Use till reboot
If still rebooting, then come back. I guess I never asked.what rom.your using
StarRavier said:
Well in your case what I would do is a backup,
Then wipe, flash custom rom. Use phone til reboot.
If reboot, flash stock IMG. Use till reboot
If still rebooting, then come back. I guess I never asked.what rom.your using
Click to expand...
Click to collapse
it doesn't boot at all.
It bootloops
I have the exact same problem. Last week upgraded to 7.0, root, stock room, viper4arise audio and EX kernel and that's it. while taking pictures it froze then that boot loop, somehow I managed through a combination of flashing factory image through fastboot, locking, unlocking, reflahsing, to get it to boot normally, then yesterday I was taking pictures again and it refroze then bootloops. Now I am able to fastboot factory images but it doesn't get me out of the bootloops, and in TRWP same as you, I cannot flash anything on data or system. Repairing the file system doesn'T change anything, I did like on other threads also and flashed factury, restored nandroid then flash factory but the restore on TRWP always hangs up.
I was wondering if there is someone knowing the adb dd commands to impose the raw copying back of the restore ? Maybe that would work.
Did you try wiping system under wipe > advanced in TWRP?
In twrp, can you open a terminal and check the results of this (basically, doing a full read-only test of your flash)
Code:
dd if=/dev/block/mmcblk0 of=/dev/null
Hey guys,
i messed up i think, but i hope you can help me out of this...
Today i flashed a SM-G950F with TWRP version 3.3.1-0 using heimdall.
It went without any issues and i can boot into the recovery just fine.
The only reason for this was me wanting to backup the whole phone using adb pull /dev/block/sda.
After i was done with this command i tried rebooting back into the system, but now it is stuck in a bootloop.
The phone turns on, shows the logo, vibrates and the screen turns of again and the cycle repeates.
Does this have anything to do with me flashing the recovery? If so, what can i do now? This is not my phone and i'd like to
prevent any data loss.
For the record:
I messed up, because i did not make an backup of the original recovery since i thought keeping TWRP would be fine. Which was stupid, but what's done is done...
I also cannot easily backup the internal storage, as it is encrypted.
Any help would be highly appreciated.
bakaschwarz said:
Hey guys,
i messed up i think, but i hope you can help me out of this...
Today i flashed a SM-G950F with TWRP version 3.3.1-0 using heimdall.
It went without any issues and i can boot into the recovery just fine.
The only reason for this was me wanting to backup the whole phone using adb pull /dev/block/sda.
After i was done with this command i tried rebooting back into the system, but now it is stuck in a bootloop.
The phone turns on, shows the logo, vibrates and the screen turns of again and the cycle repeates.
Does this have anything to do with me flashing the recovery? If so, what can i do now? This is not my phone and i'd like to
prevent any data loss.
For the record:
I messed up, because i did not make an backup of the original recovery since i thought keeping TWRP would be fine. Which was stupid, but what's done is done...
I also cannot easily backup the internal storage, as it is encrypted.
Any help would be highly appreciated.
Click to expand...
Click to collapse
delete the folder names "Android" on the internal storage in the file manager in TWRP and reboot