Related
http://www.clockworkmod.com/forum/viewtopic.php?f=4&t=179
I created a thread there but i know there are more people active here that will read it.
this is to see how many people this has affected but also a work around if you encounter issues
OK, I have been testing the Unrevoked rc3.21 that comes bundled with clockworkmod
There seems to be an issue with how it does the nandroid backup. I have tested on my own device and another collegues
We are both running stock 2.2 2.10.508.2 hboot .93
flash went fine, rebooted to recovery, did nandroid backup of rom, reboot from recovery = boot loop
on my friends we did the same but this time reapplied clockwork from rom manager, did nandroid backup from rom manager - boot loop
To resolve the issue you simply restore the very same backup you just created
This leads me to believe that there is something going on where the backup process is actually corrupting system files after it has take a backup of it.
as said this has been duplicated and on top of that other people have reported it on unrevoked's bugreport list
I know you are not part of unrevoked but it seems to be clockwork mod with these new versions of desire that is causing a problem
http://git.unrevoked.com/redmine/projects/unrevoked3-testers/issues
Click to expand...
Click to collapse
Rastaman-FB said:
http://www.clockworkmod.com/forum/viewtopic.php?f=4&t=179
I created a thread there but i know there are more people active here that will read it.
this is to see how many people this has affected but also a work around if you encounter issues
Click to expand...
Click to collapse
I can confirm this.
Just did a nandroid backup with the same version of Clockwork Mod - on my Desire running stock 2.2 2.10.508.2 hboot .93
Phone went into boot loop, and I had to pull battery to get back into recovery.
I restored my backup, and phone booted normally again...
gosa said:
I can confirm this.
Just did a nandroid backup with the same version of Clockwork Mod - on my Desire running stock 2.2 2.10.508.2 hboot .93
Phone went into boot loop, and I had to pull battery to get back into recovery.
I restored my backup, and phone booted normally again...
Click to expand...
Click to collapse
was it you i was talking too on freenode yesterday?
what clock work recovery are you on?
i dont have this issue clockwork recovery 2.5.0.7 Hboot .83.001 Personal 2.10 modded rom.
Juggalo_X said:
what clock work recovery are you on?
i dont have this issue clockwork recovery 2.5.0.7 Hboot .83.001 Personal 2.10 modded rom.
Click to expand...
Click to collapse
the very same clockwork and to rule anything out we also reflashed the recovery using rom manager too.
same thing
its to do with the .93 hboots and the ruu version of froyo used i think. clockworks backup borks it lol
Rastaman-FB said:
was it you i was talking too on freenode yesterday?
Click to expand...
Click to collapse
yeah, that was me...
Also on 2.5.0.7 and with recently flashed RUU from HTC.
And btw -
I've seen a lot of incidents ("tickets") on Unrevokeds site about Desires getting stuck in boot loop after backup.
I do not know however we can reach all of them to get more people to verify. Maybe speak with the developers of Unrevoked?
well you would expect they are reading the tickets. its probably a clockwork problem but unrevoked bundle it so should be aware of the pitfalls
Yet to see a reply from the clockwork team
Rastaman-FB said:
well you would expect they are reading the tickets. its probably a clockwork problem but unrevoked bundle it so should be aware of the pitfalls
Yet to see a reply from the clockwork team
Click to expand...
Click to collapse
Could you take a few minutes and try making a backup again? It seems like the next backup you make might not give boot loop...
gosa said:
Could you take a few minutes and try making a backup again? It seems like the next backup you make might not give boot loop...
Click to expand...
Click to collapse
im scared,
im on a custom rom now though so i dont know if that makes a difference?
are you on a custom rom or still on default build?
Rastaman-FB said:
im scared,
im on a custom rom now though so i dont know if that makes a difference?
are you on a custom rom or still on default build?
Click to expand...
Click to collapse
Still on stock.
The reason I'm asking is because I've been emailing Joshua at UNrevoked about this, and when he asked me to give some feedback about the boot loop I went in and made a new backup - and that one didn't put the phone into loop.
I'm going to try to run Unrevoked another time this weekend and see if I can reproduce, but it would be nice if someone else could test to see if the second backup loops the phone or not.
gosa said:
Still on stock.
The reason I'm asking is because I've been emailing Joshua at UNrevoked about this, and when he asked me to give some feedback about the boot loop I went in and made a new backup - and that one didn't put the phone into loop.
I'm going to try to run Unrevoked another time this weekend and see if I can reproduce, but it would be nice if someone else could test to see if the second backup loops the phone or not.
Click to expand...
Click to collapse
im running leedroid now. ill run a backup of it as we speak and see what it does.
i hope its recoverable lol. wish me luck
EDIT:
SUCCESS in backing up leedroid.
so it looks like this maybe a 1st time backup issue?
odd, only way to really prove it would be to completly RUU the device back to full stock with recovery, wiped, and then do the process again.
Rastaman-FB said:
im running leedroid now. ill run a backup of it as we speak and see what it does.
i hope its recoverable lol. wish me luck
EDIT:
SUCCESS in backing up leedroid.
so it looks like this maybe a 1st time backup issue?
odd, only way to really prove it would be to completly RUU the device back to full stock with recovery, wiped, and then do the process again.
Click to expand...
Click to collapse
I'm going to begin with running Unrevoked again to see if I can reproduce. If that doesn't work... well.. Not sure I want to go through the RUU again... but on the other hand - with a good backup I suppose I could try.
gosa said:
I'm going to begin with running Unrevoked again to see if I can reproduce. If that doesn't work... well.. Not sure I want to go through the RUU again... but on the other hand - with a good backup I suppose I could try.
Click to expand...
Click to collapse
aye, can understand that. its up to you really
im surprised clockwork mod havent passed comment on it though on their own forums.
I confirm the same problem
Stuck in boot loop with the first backup after the root process, it worked after restore
i tried an immediate second backup after that and the problem didn't occur
weird, i'll report this to unrevoked, i'm running dbranded stock 2.10 with hboot 0.93
hamdir said:
I confirm the same problem
Stuck in boot loop with the first backup after the root process, it worked after restore
i tried an immediate second backup after that and the problem didn't occur
weird, i'll report this to unrevoked, i'm running dbranded stock 2.10 with hboot 0.93
Click to expand...
Click to collapse
thanks for coming here and reporting this, the more info we get to them about it the quicker theyll try and fix it as if this is about on full release there is gonna be some spammage about bricked desires
Sorry to ask i know this is probably a noob question (actually it is because i am a noob lol)...
The problem you mentioned is ween i try to make a full system back up after the root process with the latest unrevoked right?
priestnot said:
Sorry to ask i know this is probably a noob question (actually it is because i am a noob lol)...
The problem you mentioned is ween i try to make a full system back up after the root process with the latest unrevoked right?
Click to expand...
Click to collapse
yes
10char
But its only for those who have the 0.93? I have a 0.92 do i have to worry?
priestnot said:
But its only for those who have the 0.93? I have a 0.92 do i have to worry?
Click to expand...
Click to collapse
I cant answer that as i dont have .92 and ive not seen anyone report it on .92
Has this been fixed yet??
Hey Guys,
I have s-off and CM7r2 Recovery.
I use this about a month ; now I wanted to flash an other rom but now it is always by the bootscreen.
I tried many other roms but every time the same.
Any body have an idea what I can do ?
JuLiian said:
Hey Guys,
I have s-off and CM7r2 Recovery.
I use this about a month ; now I wanted to flash an other rom but now it is always by the bootscreen.
I tried many other roms but every time the same.
Any body have an idea what I can do ?
Click to expand...
Click to collapse
Have you tried in recovery to complete wipe. Also your SD and then flash the .zip again?
Yes.
Is there an way to reflash the recovery without Pc ?
I only made it this way since today.
JuLiian said:
Yes.
Is there an way to reflash the recovery without Pc ?
I only made it this way since today.
Click to expand...
Click to collapse
There is a way to do that directly in rom. But you cannot start one. So as far as i know, you are answer referring to your current situation is: NO!
suggest
I haven't understand what is your problem, so I reply with 2 problems and relative solutions.
1. If you want to change ROM, you have to verify the necessary hboot. Ex. For AceSmod007 you can use cm7 or stock hboot, but you must flash the right zip.
2. If you want to try flash roms with another recovery you can dowload the last 4Ext recovery (you can find it in development room): there is a version that can be flashed automatically in fastboot, just putting the zip in your SD-card's root.
Hope that I have been usefull. Someone corrects me if I was wrong.
Hey thanks for the answers.
I even turned on my phone and it works (Y)
Magic
But thanks for your help.
Does clockworkmod overwrite the stock recovery? If it does then to me it is not a safe method to root a phone. If something goes wrong while flashing clockwork you will lose the stock recovery and can never reflash anything else. Is my understanding correct? This is why I am hesitant to root my phone. Please advice.
Thanks.
datzstr8 said:
Does clockworkmod overwrite the stock recovery? If it does then to me it is not a safe method to root a phone. If something goes wrong while flashing clockwork you will lose the stock recovery and can never reflash anything else. Is my understanding correct? This is why I am hesitant to root my phone. Please advice.
Thanks.
Click to expand...
Click to collapse
Its fairly safe. You could always flash the recovery thru odin found here:
http://forum.xda-developers.com/showthread.php?t=1332103
Has anyone tried to flash clockwork and failed? What happened afterwards? I assume odin won't work anymore because it requires a recovery partition to work.
I guess what I am still confused about is if clockwork writes over the stock recovery or does it keep the stock recovery in-tacked. I would prefer the later since then you can never break your phone.
With my dilemma would it be best for me to not install clockwork and just use an insecure kernel? Thanks.
It does overwrite the stock recovery i believe. But its very safe to flash. Ive never heard of someone borking a phone installing cwm recovery.
I have literally NEVER had a problem with clockworkmod, it's one of the best pieces of mobile software I've ever used.
kabuk1 said:
I have literally NEVER had a problem with clockworkmod, it's one of the best pieces of mobile software I've ever used.
Click to expand...
Click to collapse
Whole heartedly agree.
Sent from my SGH-T989 using xda premium
datzstr8 said:
Has anyone tried to flash clockwork and failed? What happened afterwards? I assume odin won't work anymore because it requires a recovery partition to work.
I guess what I am still confused about is if clockwork writes over the stock recovery or does it keep the stock recovery in-tacked. I would prefer the later since then you can never break your phone.
Click to expand...
Click to collapse
Odin has NOTHING to do with the recovery partition. ODIN only works in download mode on your phone. You can have a blank recovery partition and it'll still work, as well as the rom, and flashing other things too. The recovery partition stock has one function, to do a factory reset incase of problems. (Not to be confused with the one from inside android, that only formats /data. This one replaces the system partition as well.) CWM is very safe, I really wouldn't worry about it. Just follow the instructions carefully and you'll be fine.
Also, once you get cwm installed on there, I'd suggest doing a backup before you make any changes. Always handy to have your stock image at hand, just incase.
And also, even with stock recovery, you can still break your phone. It's not easy to brick a GS2, but it can be done. Just remember, as long as you can get the phone into download mode, it's not bricked. You can always odin back the stock partitions if you run into issues.
I was a little worried about using it with this phone. No problems to report. Just had to make backup in recovery.
Sent from my SGH-T989 using xda premium
Thanks mstrk242 for the great explanation. I thought the "download" and "recovery" were two states of a single program. It is clear now that they are separate. You just cleared all my worries.
You said "It's not easy to brick a GS2, but it can be done," can you tell me how this can happen? Just curious. Thanks much.
If you're going to be rooting/flashing at all, you'll have to get comfortable with cwm, Odin, and the other tools that are available for the phone.
This is my second Android phone, both have been rooted with custom roms, and at any point I've run into trouble (which is rare) I've found the tools and the help I need on here by searching a little bit. If you're willing to spend the time doing a bit of reading and know your way around a computer a bit, you won't have a problem. Just make sure you're 100% sure whatever you're flashing is for YOUR phone hardware.
It's not nearly as scary as it sounds once you get going on it and there's a lot to benefit from it.
Cheers and good luck.
Sent from my SGH-T989 using xda premium
datzstr8 said:
Thanks mstrk242 for the great explanation. I thought the "download" and "recovery" were two states of a single program. It is clear now that they are separate. You just cleared all my worries.
You said "It's not easy to brick a GS2, but it can be done," can you tell me how this can happen? Just curious. Thanks much.
Click to expand...
Click to collapse
Easiest way is to flash a rom for the wrong phone and mess up the partition table. (IE flash an international version of the gs2 rom, you'll brick.)
As long as you get cwm installed on there, and flash the correct roms, you should really be ok.
You can go back to the stock recovery easily. You can do it through Odin or flash an unroot rom
Sent from my SGH-T989 with ClockworkMod ★Touch★ Recovery 5.8.1.3
Hello all,
I have partially bricked my phone while attempting to root. Admittedly, I am very much so a novice when it comes to rooting android devices, but I have learned a lot while attempting to fix it. My problem is that when I power it up, it hangs at the white HTC splash screen and never boots past that. At first, I tried simply to flash a stock rom. No success. I have also tried using an RUU and a stock clockwork recovery image. No success with either of these. While fiddling around in recovery, however, I have noticed something that might be the cause of the problem. Anytime I attempt to do anything in recovery, most of the time the following messages are returned: "error mounting /data/!" and "error mounting /cache/!"
Now, it is my belief that somehow (and I'm embarrassed to admit I've done such a number on my poor little phone) I deleted or incorrectly formatted the internal partitions, rendering them unusable. I have been reading, and it seems that the solution lies within a tool called sdparted. However, I am very afraid to totally brick my phone, so I came here for some help. Basically, I'm hoping someone can explain it to me like I'm 12 years old, haha.
Anyway, are my assumptions correct, or do I have a totally different kind of problem? Ideally, I would like to just completely return this to stock and bring about the end of this nightmare. Anyone who can help, I'm begging for your expertise!
Here is all the data I could think to give you all about my phone:
S-On
HBoot:0.98.0000
Radio:1.09.01.0312
Recovery-
Build: RA-VIVOW-v3.0.8
Well first mistake was unlocking instead of s-off. Also, try a a newer recovery like 4ext.net
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4 Beta
tylerlawhon said:
Well first mistake was unlocking instead of s-off. Also, try a a newer recovery like 4ext.net
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4 Beta
Click to expand...
Click to collapse
Not sure you can flash 4ext through adb...isn't only an apk that installs the recovery (if I remember correctly). I would try the latest CWM recovery first. And I agree that you need to get S-OFF - try one of the guides (like the one by Prototype).
tylerlawhon said:
Well first mistake was unlocking instead of s-off. Also, try a a newer recovery like 4ext.net
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4 Beta
Click to expand...
Click to collapse
Hmmmm... Just logging in real quick after a hard day of work, will try that tomorrow and let you know the results.
brymaster5000 said:
Not sure you can flash 4ext through adb...isn't only an apk that installs the recovery (if I remember correctly). I would try the latest CWM recovery first. And I agree that you need to get S-OFF - try one of the guides (like the one by Prototype).
Click to expand...
Click to collapse
Ok, I tried flashing several different CWM images. Do you mean install CWM recovery over my current Ra recovery? And then proceed? Because as it stands, after attempting to flash the images through recovery, (and while it goes through most of it while looking successful) it seems to finish too quickly. Then, after rebooting, nothing was changed.
How would I go about installing CWM recovery over my current recovery? Should I bother doing this? Or how can I achieve S-Off from my current state? I vaguely remember coming to the conclusion that I couldn't get to S-off until I just completely flashed it back to stock. But then again, it's been a week since I've played with this phone. And I'm a complete noob. So any further advice would be appreciated.
RRCriswell said:
Hmmmm... Just logging in real quick after a hard day of work, will try that tomorrow and let you know the results.
Ok, I tried flashing several different CWM images. Do you mean install CWM recovery over my current Ra recovery? And then proceed? Because as it stands, after attempting to flash the images through recovery, (and while it goes through most of it while looking successful) it seems to finish too quickly. Then, after rebooting, nothing was changed.
How would I go about installing CWM recovery over my current recovery? Should I bother doing this? Or how can I achieve S-Off from my current state? I vaguely remember coming to the conclusion that I couldn't get to S-off until I just completely flashed it back to stock. But then again, it's been a week since I've played with this phone. And I'm a complete noob. So any further advice would be appreciated.
Click to expand...
Click to collapse
Use prototype's guide in the dev section. Look for the cwm thread and click on the flash instructions through adb command.
Sent from my Ascended Dinc2.
i have the exact same issue with a Inc 1. i have tried everything (including sdparted) with absolutely no luck. tried flashing the stock RUU, even unrooted and nothing worked. never could find anyone to know of a fix. i wish you the best of luck. will be watching this in hopes that you figure something out.
Hi All,
Yesterday I took my Tegra 3 (International) One X back to Stock ICS using RUU. Everything went smoothly after I relocked my bootloader and ran the RUU.
Then I proceeded to get all the OTA updates until I had JellyBean (3.14.707.24) with no further updates pending. Yay for Jellybean! The next thing I did was install CWM recovery and perform a nandroid backup (which didn't seem to restore later, although was created correctly).
At this point, I thought I would try using a CM10 rom to remove sense and I went ahead and installed it, flashing over the boot.img as one normally would, but it wouldn't boot. I later discovered that I needed a modded-boot.img (for new hboot 1.36), but not before I tried running the 3.14.707.24 RUU.
This RUU got stuck at sending.... and did not finish. I didn't leave it more than 20 minutes and tried twice. I also tried my ICS RUU to no avail.
Right now I have no Rom installed (from what I can tell), but I have full fastboot access and would like to know how I should proceed:
1) should I install the CM10 rom again with proper modded-boot.img (for hboot 1.36) and see if it boots? That would at least get me functional.
2) should I try another copy of the RUU for 3.14.707.24 JB? (i found one)
3) should I try a rom like Android Revolution HD which is OK to work with my new HBoot 1.36?
I don't want to do too much too fast since I know what I've done, and used to be really into this. The phone has been sitting a while since I upgraded my device and I'd like to get it working for travelling purposes. I'd be happy with a Stock Rom at this point...
Thanks for any willingness to help me
Adam
Ofcourse if you want CM flash the boot.img that is made for CM..And then flash .zip file..And ofcourse after flashing use
"fastboot erase cache"
Sometimes if you dont clear cache your phone won't boot..
Sent from my Endeavor
As you already said the old boot.img wont work with the new hboot. Just install cm10.1 as usually. Or any other JB Rom that is out there for the One X.
Sent from my HTC One X using xda app-developers app
Thanks for answering
big noob said:
Ofcourse if you want CM flash the boot.img that is made for CM..And then flash .zip file..And ofcourse after flashing use
"fastboot erase cache"
Sometimes if you dont clear cache your phone won't boot..
Sent from my Endeavor
Click to expand...
Click to collapse
Thank you very much for your response!
This brings me to a next question...
Marc199 said:
As you already said the old boot.img wont work with the new hboot. Just install cm10.1 as usually. Or any other JB Rom that is out there for the One X.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks for your answer!! Now I'm curious if I want to use some other ROM, but without any system, how do I get the .zip file for the rom onto my SD card for flashing.
Should I use CWM recovery and enable usb storage, or is there another way?
Thanks again,
Adam
Correct, use the recovery
Yes just mount usb storage in CWM.
Sent from my ProBam by codexc @xda using xda app-developers app
Thanks!
Marc199 said:
Yes just mount usb storage in CWM.
Sent from my ProBam by codexc @xda using xda app-developers app
Click to expand...
Click to collapse
I'll try this later when I have the time. Thanks to everyone who responded. I was nervous I was on the bad road. Seems I'm in healthy shape, just lacking a rom.
Two more questions:
1) Can I still revert to stock? If so, how since RUU seems to get stuck at sending and not actually restore?
2) Any idea why when I tried to restore my stock nandroid backup just after installing CWM (which backed up successfully) it would restore but not boot (hung on One splash screen)? Should I have to wait a seriously long time for it to boot (I never used to have to?)
Thanks in advance!
Adam :angel:
THANKS!
Mr Hofs said:
Correct, use the recovery
Click to expand...
Click to collapse
Thanks so much. I'll see what happens and get back to the thread.
ALL GOOD!!
Thanks Everyone again. I'm Up and Running!
I think I was more freaked out by the RUU not working than just thinking that my phone is fine. Turned out CWM Recovery was still onboard so I just flashed a new rom using USB mounted storage. :good::good::good::cyclops:
adampollack said:
I'll try this later when I have the time. Thanks to everyone who responded. I was nervous I was on the bad road. Seems I'm in healthy shape, just lacking a rom.
Two more questions:
1) Can I still revert to stock? If so, how since RUU seems to get stuck at sending and not actually restore?
2) Any idea why when I tried to restore my stock nandroid backup just after installing CWM (which backed up successfully) it would restore but not boot (hung on One splash screen)? Should I have to wait a seriously long time for it to boot (I never used to have to?)
Thanks in advance!
Adam :angel:
Click to expand...
Click to collapse
1. You just need to find a RUU that will work..
2. Did you flash boot.img from sdcard/CWM/backup/ backup name folder?
Sent from my Endeavor
Hmmm....
big noob said:
1. You just need to find a RUU that will work..
2. Did you flash boot.img from sdcard/CWM/backup/ backup name folder?
Sent from my Endeavor
Click to expand...
Click to collapse
Hey, Thanks for responding!
1. I figured. Thanks for validating. :good:
2. I did not use the boot.img from the nandroid backup. I've never sent a separate boot.img when restoring from Nandroid. Is that something I need to do going forward/have been lucky not having to do until now? Perhaps the ICS builds of roms had a more similar boot.img?
Adam
Yes sir, always flash the corresponding boot.img file :thumbup:
Appreciate the help
Mr Hofs said:
Yes sir, always flash the corresponding boot.img file :thumbup:
Click to expand...
Click to collapse
:highfive:
Thanks! I'm just confused because I've literally NEVER had to do this and have flashed countless roms when I was on ICS builds.
Great tip :highfive::good::highfive: