Related
So after seeing a Jelly Bean rom on here, I decided to download it and flash it. I did a nandroid backup first and then flashed the rom. Wouldn't boot. Basically it would vibrate with the Google screen then reboot over and over again. Tried to do a nandroid RESTORE and it gave me an error about restoring /data. Tried other backups and they gave me the same error. Tried to flash a completely different ROM and bootlooped on the Google screen. I saw that people were having errors with the TOUCH CWM so I reflashed the nontouch Recovery Image and I am getting the same results. I think I ****ed my phone. I have no other ideas so I am turning to the communty for help with this. I'm out of ideas. PLEASE HELP! Thanks!
Might be a stupid question but did you do the wipe/factory reset, wipe cache, wipe dalvik prior to the flash? Just asking...
drew_grant said:
So after seeing a Jelly Bean rom on here, I decided to download it and flash it. I did a nandroid backup first and then flashed the rom. Wouldn't boot. Basically it would vibrate with the Google screen then reboot over and over again. Tried to do a nandroid RESTORE and it gave me an error about restoring /data. Tried other backups and they gave me the same error. Tried to flash a completely different ROM and bootlooped on the Google screen. I saw that people were having errors with the TOUCH CWM so I reflashed the nontouch Recovery Image and I am getting the same results. I think I ****ed my phone. I have no other ideas so I am turning to the communty for help with this. I'm out of ideas. PLEASE HELP! Thanks!
Click to expand...
Click to collapse
I'm guessing you flashed the Vicious Version? Same thing happened to me today except it booted for like an hour then shut itself down and never booted all the back up. I had to flash a factory image through GNex Toolkit. I tried all kinds of things; restore a nandroid of cm9, Aokp, Stock, reflashing, nothing. So I hate to say it but looks like your going to be spending some time with fastboot tonight...
I really hope someone can prove me wrong though, cuz factory img wipes everything including SD.
Mikef3j said:
Might be a stupid question but did you do the wipe/factory reset, wipe cache, wipe dalvik prior to the flash? Just asking...
Click to expand...
Click to collapse
First thing I did.
xIC-MACIx said:
I'm guessing you flashed the Vicious Version? Same thing happened to me today except it booted for like an hour then shut itself down and never booted all the back up. I had to flash a factory image through GNex Toolkit. I tried all kinds of things; restore a nandroid of cm9, Aokp, Stock, reflashing, nothing. So I hate to say it but looks like your going to be spending some time with fastboot tonight...
I really hope someone can prove me wrong though, cuz factory img wipes everything including SD.
Click to expand...
Click to collapse
I'm all out of ideas. I've been spending 2 hours on this. This looks like my only option. Even worse for me, I can't access the GNEX Toolkit because I have a Mac. Do you have the file or the link to the file you flashed?
drew_grant said:
I'm all out of ideas. I've been spending 2 hours on this. This looks like my only option. Even worse for me, I can't access the GNEX Toolkit because I have a Mac. Do you have the file or the link to the file you flashed?
Click to expand...
Click to collapse
Use fastboot.
Sent from my Xoom using xda premium
Has anyone determined why this is happening with the new JB roms? I got stuck in this situation last night and would love to try again if I could just figure out where I went wrong the first go around.
This is srsly the last time I'm posting this.
Code:
adb pull /data/media/ /SDBACKUP/
To get your SD contents back.
Then fastboot flash back to stock.
JB changes the directory that your data resides in...which seems to be why many are having problems.
I, however, have swapped back to an AOKP nandroid just fine.
I really hate to start a new thread but I really can't find a reason/solution to this issue. It's just as the title says. I tried flashing the MIUI ROM just as any ROM and got a failed error. Then went to do my nandroid restore and it just hangs on the splash screen (boot screen). Anyway I thought there could be a bad download so I took out the SD and redownloaded synergy on my laptop, then put it back in the phone and nothing but the nandroid should let me restore. I even tried moving the files to the internal SD and nothing. The only thing I can think of is to Odin back to stock? Is it the same method as rooting? I'm sure I can find that out, but I'm just confused why it seems TWRP doesn't want to work. Thanks for any help, it's 4 a.m. here and I'm dog tired.
Are you on the latest TWRP?
If all else fails you could go back to stock and root again.
DarkManX4lf said:
Are you on the latest TWRP?
If all else fails you could go back to stock and root again.
Click to expand...
Click to collapse
I think so. Yeah, just didn't want to go throught it all, and didn't know why.
jtadak said:
I think so. Yeah, just didn't want to go throught it all, and didn't know why.
Click to expand...
Click to collapse
Can I just reflash recovery from the state I'm in, or do I still need to unroot? I've moved some of my files to the ext SD within recovery but some things won't move and I really don't want to wipe it.
jd14771 said:
Try wiping everything 3X, then go to the reboot menu, and reboot system, wipe both the cache and dalvik cache and try to restore.
Click to expand...
Click to collapse
Do you mean reboot recovery? I can't reboot system. Sorry, not trying to split hairs, just trying to be specific.
Odin back to stock seems like the best option.
Sent from a galaxy note 2 far far away...
are you able to flash a different rom, say a stock rom? It's possible you got a corrupted TWRP download.
Since they just released another update 2.4.3, you might want to try and download the zip file, wipe cashe and davick (may want to do it three times). Reboot back into TWRP 2.4.3 and see if it gives you some better luck.
I've had Nandroid backup that didn't work for whatever reason. I didn't test it prior to needing it, and got burned. It just wouldn't show up in the restore menu.
On a side note, what error did you get when you tried flashing MIUI?
Try rebooting recovery when you are in recovery already once before flashing/restoring anything anything.
mexiking713 said:
Odin back to stock seems like the best option.
Sent from a galaxy note 2 far far away...
Click to expand...
Click to collapse
Yes, that's what I did. I'm just bummed I had to wipe storage. Oh well, it's inevedible... I dig that sig though, with phone line up.
lovekeiiy said:
are you able to flash a different rom, say a stock rom? It's possible you got a corrupted TWRP download.
Since they just released another update 2.4.3, you might want to try and download the zip file, wipe cashe and davick (may want to do it three times). Reboot back into TWRP 2.4.3 and see if it gives you some better luck.
I've had Nandroid backup that didn't work for whatever reason. I didn't test it prior to needing it, and got burned. It just wouldn't show up in the restore menu.
On a side note, what error did you get when you tried flashing MIUI?
Click to expand...
Click to collapse
I tried multiple ROMs, but not a stock one. Hmm, I was on 2.3.2.3. I did'nt get a special error, just said a red message saying failed.
Evo_Shift said:
Try rebooting recovery when you are in recovery already once before flashing/restoring anything anything.
Click to expand...
Click to collapse
Tried that. Did'nt work.
jd14771 said:
no, i meant reboot system, the recovery will warm you that there is no os installed but go fourth with it, it will turn off and reboot back to recovery. at that point in time, wipe cashe/dalvik cache and try to install.
Click to expand...
Click to collapse
Ok, I was'nt sure. I just went back to stock. I just wanted to know what exactly was going on and why.
The only thing different on my phone is I got a 32 gig SD card. I transfed some of my files a couple days before doing anything of this. That's the only thing I can think of. Even after root/unroot it STILL won't do my nandroid restore. I had so much time and work into the apps I set up, games, ect. Really freakin sucks. I even went into the the TWRP backup folder and made sure the backup files were there before doing anything. I never even got to flash many ROMs, I kinda just stayed on Jellybomb.
I had the uTorrent app installed and I noticed that it changed a lot of files with the "u" in front that the uTorrent app has. Anyone know why that is?
Sent from my SPH-L900 using xda app-developers app
This is what it did to a lot of my files. But not the ones I tried to flash.
Sent from my SPH-L900 using xda app-developers app
So I was running CM11 M8 and restored back to stock(Root66) BNC1 on my T999L.Ever since that not one single ROM will boot regardless of which recovery I try to flash it with(CWM,TWRP,PhilZ,Multiboot).I can Odin back to BNC1(Root66 or Straight Stock) with no issues and the ROMS never give any error's while installing they just hang at the boot screen.I've tried factory reset with dalvik and cache after flashing as well and get nothing still.My phone works fine still no issues there just not able to sucessfully boot a flashed ROM.Any advice would be greatly appreciated.
How long did you leave it on the boot screen? It can take a while at times
serio22 said:
How long did you leave it on the boot screen? It can take a while at times
Click to expand...
Click to collapse
Of course I waited. When I install CM 11 it was almost 30 minutes before I said screw it and restored my nandroid.
Have you tried factory resetting from stock recovery? It will wipe internal sd just so you know.
DocHoliday77 said:
Have you tried factory resetting from stock recovery? It will wipe internal sd just so you know.
Click to expand...
Click to collapse
Yes I have also tried that Doc.
Try flashing another rom from recovery. Before trying to reboot, select Copy Log to SD. See if it has any clues. (It'll be towards the end of the file)
You can post it here if you can't find anything.
Aside from that, all I can think to try is flashing with Odin again and select re-partition.
DocHoliday77 said:
Try flashing another rom from recovery. Before trying to reboot, select Copy Log to SD. See if it has any clues. (It'll be towards the end of the file)
You can post it here if you can't find anything.
Aside from that, all I can think to try is flashing with Odin again and select re-partition.
Click to expand...
Click to collapse
Did that as well and looked at the log.Did another restore through Odin to complete stock then to Root66 and that seems to have fixed the issue...hmmm no idea what was wrong.
Sometimesbtheres just no good way to know the cause.
Glad to hear it seems to be ok now! For the next several flashes you do, just kerp an eye on how its acting and copy the log to sd each time, just in case. If it still is working ok after a few times it should be ok to go back to doing things like normal.
I can't install any ROM, gets stuck on no MD5 file found for about 5 minutes then says script succeeded result was [*********************************] then I go to reboot and get red LED flash. Help?
Aiwa said:
I can't install any ROM, gets stuck on no MD5 file found for about 5 minutes then says script succeeded result was [*********************************] then I go to reboot and get red LED flash. Help?
Click to expand...
Click to collapse
What system version are you currently running
Post your steps that you did
itsbighead said:
What system version are you currently running
Post your steps that you did
Click to expand...
Click to collapse
I am on 5.0 running CloudyG3, the only ROM that'll flash..
I booted into Recovery
Wiped data
Installed ROM
hangs on md5 check (sometimes says 'cannot unmount /system; no such volume)
says done with that script successful [*******]
reboot
red LED
I've tried wiping system aswell and everything, tried mounting system etc
Were you running Lollipop or KitKat before you installed TWRP?
itsbighead said:
Were you running Lollipop or KitKat before you installed TWRP?
Click to expand...
Click to collapse
KitKat as I restored to stock then updated to CloudyG3.
I've made some progress but then I get: unmount of /system failed no such volume
even though i'm pretty sure i've mounted system
Aiwa said:
KitKat as I restored to stock then updated to CloudyG3.
I've made some progress but then I get: unmount of /system failed no such volume
even though i'm pretty sure i've mounted system
Click to expand...
Click to collapse
Boot into TWRP
Go into Mount
Untick System
And see if it helps. I used to have this problem along time ago when i was trying to install MIUI on my Nexus 5 and i remember reading that
itsbighead said:
Boot into TWRP
Go into Mount
Untick System
And see if it helps. I used to have this problem along time ago when i was trying to install MIUI on my Nexus 5 and i remember reading that
Click to expand...
Click to collapse
Unticked, still not working!
Aiwa said:
Unticked, still not working!
Click to expand...
Click to collapse
Does this happen with any other roms or when you try to restore a Nandroid or TWRP backup?
itsbighead said:
Does this happen with any other roms or when you try to restore a Nandroid or TWRP backup?
Click to expand...
Click to collapse
Backup restores just fine! It happens on other roms such as fusion.
someone help
Im Having the same issue- On a different phone
m7 sprint. I messed up and had to RUU. Tried the most recent - it didn't work.
Kept going back until I found one that did.
After that Got everything straight installed TWRP/(tried CWM too)
Goes to flash rom and get the unable to unmount /system no such volume error.
Driving me crazy .
Can make and Restore Nandroids no problem.....
Right, so. Managed to unlock and root my M9 successfully, no problems, using a good guide, which included making a Nandroid backup prior to rooting.
So I decide to get rid of LeeDroid and restore my Nandroid backup. All went well. Then TWRP asks if I want to install SuperSU as my device isn't rooted. So swipe yes, and it goes through the usual list, and just as it gets to the last line my phone goes off, and reboots.
I've tried both the stable and beta and always get the same damn crash/reboot, tried the mounting methods, but NOTHING works!
Could anyone shed any light as to why? It's the GSM variant of the M9.
Vesten said:
Right, so. Managed to unlock and root my M9 successfully, no problems, using a good guide, which included making a Nandroid backup prior to rooting.
So I decide to get rid of LeeDroid and restore my Nandroid backup. All went well. Then TWRP asks if I want to install SuperSU as my device isn't rooted. So swipe yes, and it goes through the usual list, and just as it gets to the last line my phone goes off, and reboots.
I've tried both the stable and beta and always get the same damn crash/reboot, tried the mounting methods, but NOTHING works!
Could anyone shed any light as to why? It's the GSM variant of the M9.
Click to expand...
Click to collapse
what exact version of twrp?
Is the backup a system IMAGE backup?
are you entering TWRP in read-only mode?
When you try to restore now, what does the terminal output say?
TWRP version 2.8.7.0
The backup was made using TWRP after flashing it for the first time, which included the usual data, system, etc.
Not sure about TWRP entering read only mode. I read it only does this on unmodified software. Mine is still saying modified even after restoring my nandroid.
Also unsure of what the terminal says without copying the log. Can restore it as many times as I want.
Can't be much more help until I get to a PC.
I'm still S-On, etc. Have a feeling it's to do with the TWRP read only thing...
Vesten said:
TWRP version 2.8.7.0
The backup was made using TWRP after flashing it for the first time, which included the usual data, system, etc.
Not sure about TWRP entering read only mode. I read it only does this on unmodified software. Mine is still saying modified even after restoring my nandroid.
Also unsure of what the terminal says without copying the log. Can restore it as many times as I want.
Can't be much more help until I get to a PC.
I'm still S-On, etc. Have a feeling it's to do with the TWRP read only thing...
Click to expand...
Click to collapse
well, when you go to restore twrp, does it say unable to wipe system/cache, etc?
If so, go into the mount menu and put a check mark in the system read only box, then uncheck it and try to restore again.
If that doesn't work, try updating to the latest twrp, which is 2.8.7.1. http://forum.xda-developers.com/devdb/project/?id=8915#downloads
jollywhitefoot said:
well, when you go to restore twrp, does it say unable to wipe system/cache, etc?
If so, go into the mount menu and put a check mark in the system read only box, then uncheck it and try to restore again.
If that doesn't work, try updating to the latest twrp, which is 2.8.7.1. http://forum.xda-developers.com/devdb/project/?id=8915#downloads
Click to expand...
Click to collapse
I'll have to check, but don't think it does.
I'll try that new version of TWRP and report back.
Many thanks for the help, greatly appreciated.
jollywhitefoot said:
well, when you go to restore twrp, does it say unable to wipe system/cache, etc?
If so, go into the mount menu and put a check mark in the system read only box, then uncheck it and try to restore again.
If that doesn't work, try updating to the latest twrp, which is 2.8.7.1. http://forum.xda-developers.com/devdb/project/?id=8915#downloads
Click to expand...
Click to collapse
Flashed that latest TWRP. Then tried flashing SuperSU. Same thing. Just shuts off completely and reboots back to Android.
In the mount menu, system is unchecked. and the bottom "Only mount system read-only" is also unchecked.
The Terminal log gets to..
"Placing files..."
Restoring files..."
Then shuts off. I'm starting to think I'm going to have to flash a stock RUU and start from scratch.
BTW this is after checking system. It seems to do nothing at all.
EDIT: Would not having an external SD in it matter at all? I originally flashed SuperSU using the internal SD card.
Vesten said:
Flashed that latest TWRP. Then tried flashing SuperSU. Same thing. Just shuts off completely and reboots back to Android.
In the mount menu, system is unchecked. and the bottom "Only mount system read-only" is also unchecked.
The Terminal log gets to..
"Placing files..."
Restoring files..."
Then shuts off. I'm starting to think I'm going to have to flash a stock RUU and start from scratch.
BTW this is after checking system. It seems to do nothing at all.
EDIT: Would not having an external SD in it matter at all? I originally flashed SuperSU using the internal SD card.
Click to expand...
Click to collapse
What happens when you restore your backup and reboot without installing supersu?
jollywhitefoot said:
What happens when you restore your backup and reboot without installing supersu?
Click to expand...
Click to collapse
Will let you know soon. Just restoring again.
When I made the Nandroid backup, there's a new option to backup recovery too, which I did. Could this mean anything? I'm assuming it's backed up TWRP because stock obviously wasn't present when making the backup.
Will try and screenshot the log.
Vesten said:
Will let you know soon. Just restoring again.
When I made the Nandroid backup, there's a new option to backup recovery too, which I did. Could this mean anything? I'm assuming it's backed up TWRP because stock obviously wasn't present when making the backup.
Will try and screenshot the log.
Click to expand...
Click to collapse
Yeah backing up recovery doesn't matter....as you suspected it just backs up twrp, so if you backed up the older version, then updated it, don't restore the old version
jollywhitefoot said:
Yeah backing up recovery doesn't matter....as you suspected it just backs up twrp, so if you backed up the older version, then updated it, don't restore the old version
Click to expand...
Click to collapse
Interesting. There's nothing saying it couldn't write anything..
Just tried opening SuperSU from my restored backup, and hits me with "There is no SuperSU binary installed!" This is a problem, blah, blah, etc.
Then tried check-boxing the 'system' box in the Mount section. Then tried flashing UPDATESuperSu.VsXX and just gave me the usual as said above. Crashed and reboots.
https://www.dropbox.com/s/cvkclw8xuzua4u3/2015-07-20 21.56.37.png?dl=0
Losing the will to live! Ha
What about trying to push SuperSU via ADB?
EDIT: Think I'm getting ahead of myself. Not possible to flash SuperSU via ADB is it..?
Vesten said:
What about trying to push SuperSU via ADB?
EDIT: Think I'm getting ahead of myself. Not possible to flash SuperSU via ADB is it..?
Click to expand...
Click to collapse
The only way I ever do it is by swiping to install as I'm rebooting out of recovery.
jollywhitefoot said:
The only way I ever do it is by swiping to install as I'm rebooting out of recovery.
Click to expand...
Click to collapse
Would you say the nuclear option would be to sit and bide my time until a decent RUU becomes available and start from scratch?
Vesten said:
Would you say the nuclear option would be to sit and bide my time until a decent RUU becomes available and start from scratch?
Click to expand...
Click to collapse
What's your ultimate goal? Stock, rooted? What cid and firmware are you on?
jollywhitefoot said:
What's your ultimate goal? Stock, rooted? What cid and firmware are you on?
Click to expand...
Click to collapse
Well I was going to sell the phone, since it's only 2 weeks old, and obviously for warranty reasons. So back to 100% stock, which includes it saying Software Status: Official and it saying "Locked" instead of re-locked.
CID is HTC__001
Firmware is Lollipop 5.0.2 - Software version 1.40.401.8 (CL549783 release-keys)
Vesten said:
Well I was going to sell the phone, since it's only 2 weeks old, and obviously for warranty reasons. So back to 100% stock, which includes it saying Software Status: Official and it saying "Locked" instead of re-locked.
CID is HTC__001
Firmware is Lollipop 5.0.2 - Software version 1.40.401.8 (CL549783 release-keys)
Click to expand...
Click to collapse
Then yeah, just ruu back to stock and bobs your uncle. You don't have to wait, an ruu is available for 1.40.401
jollywhitefoot said:
Then yeah, just ruu back to stock and bobs your uncle. You don't have to wait, an ruu is available for 1.40.401
Click to expand...
Click to collapse
What about stock recovery? Is that included I take it...?
Still getting used to all this in-depth flashing Android stuff. Managed to convert my M8 to the GP Edition without any trouble.
Vesten said:
What about stock recovery? Is that included I take it...?
Still getting used to all this in-depth flashing Android stuff. Managed to convert my M8 to the GP Edition without any trouble.
Click to expand...
Click to collapse
Yeah. That's included. If you did that then you can get that thing back to stock.
Probably find the ruu here: http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
jollywhitefoot said:
Yeah. That's included. If you did that then you can get that thing back to stock.
Probably find the ruu here: http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Click to expand...
Click to collapse
Wow, thankyou! I've been Googling RUU's all night at work and found nothing like this. Think I'll do that and flash the RUU and start afresh!
Getting a killer 17.4 kbp/s though. 100mb connection wasted. Ha!
jollywhitefoot said:
Yeah. That's included. If you did that then you can get that thing back to stock.
Probably find the ruu here: http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Click to expand...
Click to collapse
Yay it worked! Using a stock image from that link. Something must of been really screwed up. I'm now re-rooted! Many thanks for your help!