So I was running a cm 10.2 nightly (late december) and today decided to try the new CM11 ones.
I download it and try to install it through the standard cm updater, when it reboots to CWM I get the famous "status 7" error.
I didn't think much of it and selected reboot now, then was presented with the "root permisions possibly lost want to fix now" message, I hit go back.
Ever since then, my device has been on a boot loop. After I re entered CWM I selected the option to fix the root permissions and after some attempts to start the phone again I did a factory reset&wipe cache which didn't help at all.
I have a backup on my computer of stock 4.1 rom but I don't know if/how I can use adb push while on CWM or bootloop to transfer it to the phone. I may be able to use a card reader to put it on the micro SD card and will try it tomorrow because I have to sleep now.
My CWM version is 6.0.3 and not 6.0.4, not sure if that caused the problem but I read that to update to CM11 you need the 6.0.4 version.
Any help to unbrick my phone would be greatly appreciated.
You've answered your own question as to the cause. People on here don't normally say things like "CWM v6.0.4.4 or newer required" just for fun.
As for getting the phone back, search and read.
Yeah I read that after I had bricked my phone, trying to load my backup to external sd right now.
Related
2 nights ago I thought I would have a go at installing ULTIMATE ROM 3.0. I have flashed many Roms on my Galaxy S before and not had a problem yet. I have ClockworkMod Recovery 2.5.1.0 installed.
However, this time- something went wrong. I don't think the installation completed properly. When I tried to reboot the system (to go back into my previous ROM) I wasn't able to. The Samsung logo appeared before the phone booted back into Recovery mode.
I tried to re-flash my previous working update.zip but had problems. I wasn't able to properly re-flash as the Installation would abort for various reasons. After doing cache clearing and data/factory reset I still had no luck. I resorted to reformatting the sdcard. Still didn't solve the flashing problem.
Throughout the whole time I was able to adb into the phone, browse the file system and I could push files on to it and take files off. But Kies wouldn't recognise the phone and Odin isn't able to complete a transfer to the phone (not sure why).
Today, I am able to successfully flash update.zip files (at least, that's what it looks like) but the phone ALWAYS boots into ClockwordMod recovery.
I am fast running out of ideas. Does anyone have any suggestion?
How can I tell if my ROMs are really 'there' but I can't access them because ClockworkMod is preventing them from booting?
hmmm... me too.. stuck in a loop, that keeps going back to the CWM recovery menu, and no matter what i do, keeps going back to it... cant even get to the download screen to flash (again).... here i was thinking no matter what happens when installing custom roms, i can always flash to my stable secure rom, but not this time... need some software that can perform surgical operations, any suggestions?
bradels said:
2 nights ago I thought I would have a go at installing ULTIMATE ROM 3.0. I have flashed many Roms on my Galaxy S before and not had a problem yet. I have ClockworkMod Recovery 2.5.1.0 installed.
However, this time- something went wrong. I don't think the installation completed properly. When I tried to reboot the system (to go back into my previous ROM) I wasn't able to. The Samsung logo appeared before the phone booted back into Recovery mode.
I tried to re-flash my previous working update.zip but had problems. I wasn't able to properly re-flash as the Installation would abort for various reasons. After doing cache clearing and data/factory reset I still had no luck. I resorted to reformatting the sdcard. Still didn't solve the flashing problem.
Throughout the whole time I was able to adb into the phone, browse the file system and I could push files on to it and take files off. But Kies wouldn't recognise the phone and Odin isn't able to complete a transfer to the phone (not sure why).
Today, I am able to successfully flash update.zip files (at least, that's what it looks like) but the phone ALWAYS boots into ClockwordMod recovery.
I am fast running out of ideas. Does anyone have any suggestion?
How can I tell if my ROMs are really 'there' but I can't access them because ClockworkMod is preventing them from booting?
Click to expand...
Click to collapse
myrobelle said:
hmmm... me too.. stuck in a loop, that keeps going back to the CWM recovery menu, and no matter what i do, keeps going back to it... cant even get to the download screen to flash (again).... here i was thinking no matter what happens when installing custom roms, i can always flash to my stable secure rom, but not this time... need some software that can perform surgical operations, any suggestions?
Click to expand...
Click to collapse
Thats too bad guys,and i m sorry to hear that news.I would like to havean answer but i dont...
The fact is that since most people in this forum use some custom roms,and all of us think the same,that we can always go back,so it would be great if you give some more details about what happened to you,and mybe why it went wrong,and it would be even better if one of the BIG guys would give some explanation about this...
I already thinking of not updating my rom anymore,dot want to end up in looping too,so lets see if someone will find something.Good luck guys..
By the way,i didnt get it right,CWM recovery cannot load your backup????
I just got an idea,but not sure if or how it would work or not.
Since you can push file with ADB,if soeone made a clean backup with his CWM (o e mail,contacts,setting saved) and send it to you,so that you log in with CWM recovery and flash that ???
Just an idea..maybe stupid dont know...
Its not very clear if youve tried this already but cant you just boot into recovery through adb? or does that not work either?
Currently I am running nookie froyo 0.6.8 from the internal rom but I am having the following problem even when I had eclair with autonooter. When I am turning off my nook for the night, in the morning I am stuck at the "Touch the future..." screen and I can only boot through clockwork recovery and choose reboot. I think that it started when I flashed clockwork for the first time, but I am not sure. Any ideas?
aposva said:
Currently I am running nookie froyo 0.6.8 from the internal rom but I am having the following problem even when I had eclair with autonooter. When I am turning off my nook for the night, in the morning I am stuck at the "Touch the future..." screen and I can only boot through clockwork recovery and choose reboot. I think that it started when I flashed clockwork for the first time, but I am not sure. Any ideas?
Click to expand...
Click to collapse
I am searching the forums to find an answer to the same problem. I am running stock eclair that has been autonootered. I don't have clockwork installed. I can always boot with the sdcard to Honeycomb.. sometimes I can then reboot back into Eclair.
i had this one time, i try the 8 failed boot's to restore, didn't restore but rebooted to eclair!
arf, i'm having the same problem after all..
I had the same thing happen to me had to reformat cache if I wanted to boot into froyo,its a great system but that one problem did me in went back to stock and rooted the NC and plan on staying this way I just give up flash.Looked all over for fix or someone to explain why but never did get an answer sorry i couldnt help you but if i find answer will let you know
ok will look forward when i have time
At this point i can boot by pressing power + n for 30s, it boot to recovery, then i choose "reboot"
Yes that's right, this is the only way I can boot too (power but. + n).
when rebooted i lower setcpu to 1ghz max. it seems to help to boot ..
There are some really good unbricking//"my nook won't boot" sort of threads to be found in the developers section; but this one should be more than enough to fix your issues:
http://forum.xda-developers.com/showthread.php?t=949699
Additionally, I find that reflashing to a stock ROM or restoring a previous working backup image from CWM is the best way to go about it. Good luck!
I have the same problem too. Just remove the SD card on power on (reboot with software is OK)
Looking for better fix.
Taeseong said:
There are some really good unbricking//"my nook won't boot" sort of threads to be found in the developers section; but this one should be more than enough to fix your issues:
http://forum.xda-developers.com/showthread.php?t=949699
Additionally, I find that reflashing to a stock ROM or restoring a previous working backup image from CWM is the best way to go about it. Good luck!
Click to expand...
Click to collapse
Thx, I'll take a look at that if I ever have booting issues.
Think this is caused by the recovery image. Upgrade your recovery to the latest version 3.0.1.0 and see if that fixes it.
http://forum.xda-developers.com/showthread.php?t=971197
Going to try that today ..I just looked and i do have an older recovery file so maybe that is the problem will report back later on it.
Did the update, I will shut it off for the night and will check it in the morning.
Sent from my Nook Color
I also read CWR does not get along with 1.1..I just updated CWR and it still did the same thing what Im going to do now is clean restore then custom froyo then after setup go to market get rom manager install reboot into recovery and then install the remove crw with root file.
I downloaded the restore to stock zip file. Put it on the sd card. Then used the power and "n" to get to the butloader. Chose install from sd card and it installed. Back to operational!
I need help badly. I was trying to do a FULL system wipe from CWM including SDcard and then sideload my install from adb. But something went horribly wrong because as soon as I hit format sdcard the phone shut down and now has NO access to the SDCard so I can't install any roms or anything because as soon as the installer tried to access the SDcard the phone crashes and reboots. I don't know what to do. Am I screwed or is there some way of recovering the SDCard again in this phone?
Also this is a Rogers HTC One and afaik there is NO RUU for this phone yet. Need help urgently.
gamehawk55 said:
I need help badly. I was trying to do a FULL system wipe from CWM including SDcard and then sideload my install from adb. But something went horribly wrong because as soon as I hit format sdcard the phone shut down and now has NO access to the SDCard so I can't install any roms or anything because as soon as the installer tried to access the SDcard the phone crashes and reboots. I don't know what to do. Am I screwed or is there some way of recovering the SDCard again in this phone?
Also this is a Rogers HTC One and afaik there is NO RUU for this phone yet. Need help urgently.
Click to expand...
Click to collapse
I did this last night been up all night researching .
http://forum.xda-developers.com/showthread.php?t=2318497
mooty86 said:
I did this last night been up all night researching .
http://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
Dude that's not going to help me. Read what I wrote. The SDcard is screwed up and as soon as anything tries to read or write the sdcard the phone crashes....I have no problem sideloading a zip to the phone it's when it tried to install that the phone crashes EVERY TIME.
Also TWRP recovery does NOT work on this phone now because TWRP tries to access the sdcard when it loads. CWM will load up but cant install a rom because the SDcard is somehow bricked and I need to know if theres a way to fix it.
Ok and now I apologize because it turns out sideloading DID work after all BUT. I had to sideload a NON aroma installer ROM (cyanogenmod) to the phone. Cyanogenmod was able to finish the install somehow without crashing the phone mid-way through the install and once it was booted up the SDcard portion of the phone was no longer corrupted and crashing the phone. I am able to access it in CWM and TWRP again without crashing .
So if anyone else out there has this same problem where they clicked "format SDcard" in CWM or TWRP and all of a sudden your phone constantly crashes when it does ANYTHING to access the SD card. Try sideloading cyanogenmod onto the phone and THEN go back and wipe again to install the ROM you wanted (in my case ViperOne). I thought for SURE my phone was a goner. I couldn't do anything but then finally decided to try sideloading CM 10.1.3 just for shi*s and giggles and it WORKED my phone is saved
I was trying to install this: http://forum.xda-developers.com/showthread.php?t=2097731
because my tablet kept having soft reboots. I updated everything it told me to and now I have cyanoboot. I forgot to download the updated rom from:
http://forum.xda-developers.com/showthread.php?t=2063968
to my NookHD and I'm stuck at the bootloader like an idiot. I tried to adb-push the rom but no luck. I tried a tutorial but it wanted me to adb push to sdcard which I'm very sure it doesn't have enough space. I tried removing the micro sdcard to and see if it'll boot me back to stock but instead it tries to boot to cm which is not on the tablet anymore. Help me please.
My moto g xt1063 keeps rebooting but I can't figure out why. Sometimes it goes to the home screen and works fine for a few minutes before rebooting again, most of the times it gets stuck on the bootloader warning screen and reboots. I can access recovery though.
I had planned to install cyanogenmod on it a couple of months ago but I got stuck on an "Error updater binary in zip" so I just gave up. The device is running Official Rom provided by Telcel (México) and has SuperUser on it too, I had a notification about the binary but updating didn't fixed the problem.
I have a backup on my computer (mac) but since I can't get the phone to sync by usb I was wondering how to copy it via recovery (clockworckmod v6.0.4.7) or if it's best to buy a micro sd and try to install from there.
Any help would be greatly appreciated.
First try a factory reset.
Use an sdcard yo retore backup
If fail return to stock rom
If you have a recovery installed try to make a backup from there and save it in some place like a sd card.
After that I suggest you install CM 12.1 21/05/2015 and look how it works.
Or if you prefer then reinstall the stock rom.