I'm at my wit's end here. I've tried searching around (I rarely, if ever, post) and I can't find a solution to my problem so I'm gonna try here.
First thing's first, Device Specs (HTC Evo 4G):
SUPERSONIC EVT2-3 ENG S-OFF
HBOOT-0.76.2000 (PC3610000)
MICROP-041f
TOUCH PANEL-ATMELC03-16ac
RADIO-2.15.00.11.19
Mar 30 2010,11:24:04
Rooted with unrevoked3
Second, what I was running:
Cyanogenmod 7.0 happily running for about a week
What I was doing (at time of crash): Getting coffee... I left my phone on top of my computer (installed Go SMS Pro about 10 minutes prior), came back and it was boot looping from htc evo 4g screen to htc evo 4g screen to etc...
I have tried everything to get this thing running. All I have is fastboot and the bootloader, I can flash recovery using fastboot but they will not load up... I have tried the 3.7 RUU annd it will only detect my device while in fastboot, it runs through the update and acts like it was successful but it goes back to boot looping. I have also tried to do a nandroid restore using fastboot and I can flash every partition (system, userdata, recovery, cache) EXCEPT boot, where I get a FAILED (remote: image update error) message.
Also, I have tried using the eng-pc36img.zip file and the normal PC36img.zip file and, something interesting, it will update all of the files , radio v2, bootloader, system etc.. etc.., but when it gets to "boot" it will immediately shut off, boot back into the bootloader, reload the zip file and continue where it left off... Is it supposed to do that?
Anyways, that is my plight. I hope I've been descriptive enough. Please help and thanks you!
n00barmy said:
I'm at my wit's end here. I've tried searching around (I rarely, if ever, post) and I can't find a solution to my problem so I'm gonna try here.
First thing's first, Device Specs (HTC Evo 4G):
SUPERSONIC EVT2-3 ENG S-OFF
HBOOT-0.76.2000 (PC3610000)
MICROP-041f
TOUCH PANEL-ATMELC03-16ac
RADIO-2.15.00.11.19
Mar 30 2010,11:24:04
Rooted with unrevoked3
Second, what I was running:
Cyanogenmod 7.0 happily running for about a week
What I was doing (at time of crash): Getting coffee... I left my phone on top of my computer (installed Go SMS Pro about 10 minutes prior), came back and it was boot looping from htc evo 4g screen to htc evo 4g screen to etc...
I have tried everything to get this thing running. All I have is fastboot and the bootloader, I can flash recovery using fastboot but they will not load up... I have tried the 3.7 RUU annd it will only detect my device while in fastboot, it runs through the update and acts like it was successful but it goes back to boot looping. I have also tried to do a nandroid restore using fastboot and I can flash every partition (system, userdata, recovery, cache) EXCEPT boot, where I get a FAILED (remote: image update error) message.
Also, I have tried using the eng-pc36img.zip file and the normal PC36img.zip file and, something interesting, it will update all of the files , radio v2, bootloader, system etc.. etc.., but when it gets to "boot" it will immediately shut off, boot back into the bootloader, reload the zip file and continue where it left off... Is it supposed to do that?
Anyways, that is my plight. I hope I've been descriptive enough. Please help and thanks you!
Click to expand...
Click to collapse
Well that certainly sounds no good man. It kind of sounds like your boot partition may be corrupted, so it's unable to write to that partition. You have already tried everything I would have suggested (RUU, RUU from fastboot, RUU from PC36IMG, tried reflashing recovery, etc). Your situation sounds identical to what people were experiencing in this thread, http://forum.xda-developers.com/showthread.php?t=1009672, and unfortunately no one ever found a solution, other than replacing the phone. I wish you luck, and hope you're able to recover with one of the available RUU's or PC36IMG.
Oh well...
k2buckley said:
Well that certainly sounds no good man. It kind of sounds like your boot partition may be corrupted, so it's unable to write to that partition. You have already tried everything I would have suggested (RUU, RUU from fastboot, RUU from PC36IMG, tried reflashing recovery, etc). Your situation sounds identical to what people were experiencing in this thread, http://forum.xda-developers.com/showthread.php?t=1009672, and unfortunately no one ever found a solution, other than replacing the phone. I wish you luck, and hope you're able to recover with one of the available RUU's or PC36IMG.
Click to expand...
Click to collapse
Well, shucks . I really wanted to be able to figure this out. I've tried and tried and tried and nothing seems to work. Oh, well thanks for putting my mind at ease. Sprint is already replacing it tomorrow. I just wanted to see if I could get this fixed now and be able to pass the information on to others who might be in the same situation. At least I was able to figure out how to downgrade from 2.10 to 0.76!
You don't know of any way of zeroing out the phone's partitions do you? Sorry if that is an odd request but I'm just brainstorming.
n00barmy said:
Well, shucks . I really wanted to be able to figure this out. I've tried and tried and tried and nothing seems to work. Oh, well thanks for putting my mind at ease. Sprint is already replacing it tomorrow. I just wanted to see if I could get this fixed now and be able to pass the information on to others who might be in the same situation. At least I was able to figure out how to downgrade from 2.10 to 0.76!
You don't know of any way of zeroing out the phone's partitions do you? Sorry if that is an odd request but I'm just brainstorming.
Click to expand...
Click to collapse
I apologize for the sour news, and wish there was a way for you to recover (maybe there is, but I'm just not aware of it). As far as zeroing out, or erasing all of the partitions, I'm not positive. I know you can do that using fastboot commands ( i beleve), but I don't have a ton of experience with fastboot, other than running an RUU. I'm sure someone else will chime in here and give you the fastboot commands to do that. It would be something like 'fastboot erase recovery', for example if you wanted to erase your recovery partition. I would google up on that a little bit, and see what all you can erase by using fastboot.
k2buckley said:
I apologize for the sour news, and wish there was a way for you to recover (maybe there is, but I'm just not aware of it). As far as zeroing out, or erasing all of the partitions, I'm not positive. I know you can do that using fastboot commands ( i beleve), but I don't have a ton of experience with fastboot, other than running an RUU. I'm sure someone else will chime in here and give you the fastboot commands to do that. It would be something like 'fastboot erase recovery', for example if you wanted to erase your recovery partition. I would google up on that a little bit, and see what all you can erase by using fastboot.
Click to expand...
Click to collapse
It's all good. Like I said, they're replacing it anyways, just more for my curiosity. Thanks for showing me that thread. Out of all the threads I looked at I, somehow, missed that one. I see y'all have been at this for a while and I will certainly be watching it even after I get my replacement. I guess I'll have to pull my battery doing a radio install...
Sucks to hear about your phone For my curiosity could you please answer a question or two. A lot of people are chalking this up as a "user error" while others are thinking its CM7 (i dont). Then there is the logical one, to much flashing. I see you do not post often, but you know what to do to get out of a jam, most anyway. Did you flash your phone often, like every time a new rom comes out you would try it? Or more of a moderate flasher, stick to a main rom and flash updates, not counting nightlies. Nightlies would be extreme flashing, lol. Thats all, I am just curious on flashing habits, you did say up downgraded Hboot. I am assuming you did this after the bootloops to gain fastboot access, correct? Downgrading Hboot with the new larger partitions will brick a Evo real quick! Personally I am thinking the reason for the new partitions is related to this problem starting to emerge. If there is a way to "erase" everything and write new partitions via fastboot, those of us with older partitions can avoid this sudden death loop, and fix them for those who catch it...
Just a thought
Thanks
n00barmy said:
Well, shucks . I really wanted to be able to figure this out. I've tried and tried and tried and nothing seems to work. Oh, well thanks for putting my mind at ease. Sprint is already replacing it tomorrow. I just wanted to see if I could get this fixed now and be able to pass the information on to others who might be in the same situation. At least I was able to figure out how to downgrade from 2.10 to 0.76!
You don't know of any way of zeroing out the phone's partitions do you? Sorry if that is an odd request but I'm just brainstorming.
Click to expand...
Click to collapse
When did your problem begin? Was it after you downgraded from hboot 2.10? That is a tricky and dangerous feat in and if itself. Can you get to the bootloader screen?
UPDATE: If you can get to the bootloader, try reflashing amon RA v2.3. If you're successful, I would then reflash all of the radios including hboot 2.10 and then a rom...in that order.
posting & replying via the XDA Premium app.
dougjamal said:
When did your problem begin? Was it after you downgraded from hboot 2.10? That is a tricky and dangerous feat in and if itself. Can you get to the bootloader screen?
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
My problem began last friday and no, I only tried the downgrading bit after it started looping. I wanted to be able to use the fastboot commands. Oddly enough, though. I just tried to run the eng-pc36img.zip again and now it did not immediately reset when trying to update "boot" but rather went through the whole thing... It still loops though...
Woah!
Now able to write to boot using fastboot flash boot boot.img...
n00barmy said:
Now able to write to boot using fastboot flash boot boot.img...
Click to expand...
Click to collapse
Forward progress is good. So you were able to do that after the last RUU ran? You said it didn't skip over writing the boot.img that time?? However it still loops? Where is it looping at? THe splash screen, correct?
k2buckley said:
Forward progress is good. So you were able to do that after the last RUU ran? You said it didn't skip over writing the boot.img that time?? However it still loops? Where is it looping at? THe splash screen, correct?
Click to expand...
Click to collapse
Yes, at the splash screen. It seems I can only manually write this one boot.img in my tools folder. Everything else gets a image update error in fastboot. I was not able to do that after the RUU because it changed my hboot to 2.10 (I think, don't quote me on that).
sucks
Damn im sorry to hear about this..i hope that as mentioned above it isnt from too much flashing!! Cause i am what i would call an extreme flasher..lol i flash just about every new rom that drops to try it out
n00barmy said:
Yes, at the splash screen. It seems I can only manually write this one boot.img in my tools folder. Everything else gets a image update error in fastboot. I was not able to do that after the RUU because it changed my hboot to 2.10 (I think, don't quote me on that).
Click to expand...
Click to collapse
I see. And yes, running the most recent RUU would indeed 'upgrade' your bootloader to 2.10.
k2buckley said:
I see. And yes, running the most recent RUU would indeed 'upgrade' your bootloader to 2.10.
Click to expand...
Click to collapse
I have a little more info. It seems that the only boot.img that flashes successfully through fastboot is the one located in the eng-pc36img.zip file. I cannot flash any from my nandroid backups from rom manager pro. I have not tried any other boot.img files from any other actual pc36img.zip files. I have another but that will set my hboot to 0.97.
Also, I doubt it is from too many writes. I am still fresh to rooting and I am not flash happy by any means...
n00barmy said:
I have a little more info. It seems that the only boot.img that flashes successfully through fastboot is the one located in the eng-pc36img.zip file. I cannot flash any from my nandroid backups from rom manager pro. I have not tried any other boot.img files from any other actual pc36img.zip files. I have another but that will set my hboot to 0.97.
Also, I doubt it is from too many writes. I am still fresh to rooting and I am not flash happy by any means...
Click to expand...
Click to collapse
I also doubt it's from writes. That would be a very hard sell on me. I have flashed hundreds of things I'm sure, between roms, kernels, mods, themes, etc. Probably more than hundreds, lol. I just dont see that causing it.
Keep in mind, that whatever hboot you were on when you created a nandroid backup, is the one you'd also need to be on when restoring it. Therefore, if you're using a boot.img from a nandroiid backup, then I'm fairly certain that you'd need to be on the same hboot as when you created the nandroid backup. I discovered this a few weeks ago, lol. Every nandroid backup I had made was created on .93 hboot. I then downgraded to the ENG. 76 hboot, and got careless and tried to restore a backup from when I was on .93 hboot. That did not go well, and resulted in me only being able to get to fastboot. Fortunately I still had recovery, so I had no problem recovering from that.
Anyways, I'm not sure what to suggest next, unfortunately. I will continue trying to come up with suggestions for ya, but for now I think it's pretty much trial and error for ya. I guess if you already have a new phone coming, you don't have much to lose by messing around with that one. I'm just not sure where to take it from there. I've been down that road, and I failed, lol. I just have no idea what prevents the RUU from running successful. Or even if it appears to be successful, it still yields boot loops. So I'm at a loss on what the actual cause of that may be.
k2buckley said:
I also doubt it's from writes. That would be a very hard sell on me. I have flashed hundreds of things I'm sure, between roms, kernels, mods, themes, etc. Probably more than hundreds, lol. I just dont see that causing it.
Keep in mind, that whatever hboot you were on when you created a nandroid backup, is the one you'd also need to be on when restoring it. Therefore, if you're using a boot.img from a nandroiid backup, then I'm fairly certain that you'd need to be on the same hboot as when you created the nandroid backup. I discovered this a few weeks ago, lol. Every nandroid backup I had made was created on .93 hboot. I then downgraded to the ENG. 76 hboot, and got careless and tried to restore a backup from when I was on .93 hboot. That did not go well, and resulted in me only being able to get to fastboot. Fortunately I still had recovery, so I had no problem recovering from that.
Anyways, I'm not sure what to suggest next, unfortunately. I will continue trying to come up with suggestions for ya, but for now I think it's pretty much trial and error for ya. I guess if you already have a new phone coming, you don't have much to lose by messing around with that one. I'm just not sure where to take it from there. I've been down that road, and I failed, lol. I just have no idea what prevents the RUU from running successful. Or even if it appears to be successful, it still yields boot loops. So I'm at a loss on what the actual cause of that may be.
Click to expand...
Click to collapse
Yeah, It's getting replaced so if you have any suggestions, go ahead. I'll try anything, I've got nothing to lose at this point. Maybe we can find a solution before I have to turn it in (hopefully). Thanks for the info on the hboot versions, I didn't know that. It makes sense though. I wonder if I can just switch the hboot from .97 to .76 in that one PC36img file I have and maybe it will run... Don't know but anyways...
Oh, I forgot to mention. I flashed an AmonRA v1.8 recovery earlier and while it didn't load it got farther than ANY other recovery I flashed. After the device shut down it said AmonRA v1.8 at the bottom of the black screen, for a split second, before it would go back into the HTC splash loop. It's not much farther but it worked "better" none the less... Anyways, just some food for thought
n00barmy said:
Yeah, It's getting replaced so if you have any suggestions, go ahead. I'll try anything, I've got nothing to lose at this point. Maybe we can find a solution before I have to turn it in (hopefully). Thanks for the info on the hboot versions, I didn't know that. It makes sense though. I wonder if I can just switch the hboot from .97 to .76 in that one PC36img file I have and maybe it will run... Don't know but anyways...
Oh, I forgot to mention. I flashed an AmonRA v1.8 recovery earlier and while it didn't load it got farther than ANY other recovery I flashed. After the device shut down it said AmonRA v1.8 at the bottom of the black screen, for a split second, before it would go back into the HTC splash loop. It's not much farther but it worked "better" none the less... Anyways, just some food for thought
Click to expand...
Click to collapse
That is very interesting that you saw the RA recovery 1.8 at the bottom of the screen for a second. What hardware version is your phone? I believe 1.8.0 is only for phones with the older erase block size, which is hardware 002, and some 003. Some of the later 003 models were the new erase block size, which is 0040000. The old size is 0020000. If you're 0040000, 1.8.0 wouldn't work anyways.
As far as changing hboots go, if you're on 2.02 or 2.10 currently, you can't easily downgrade. If you're on something other than those, you should be able to switch hboots easily.
Sent from my PC36100 using XDA App
irishgreen said:
Damn im sorry to hear about this..i hope that as mentioned above it isnt from too much flashing!! Cause i am what i would call an extreme flasher..lol i flash just about every new rom that drops to try it out
Click to expand...
Click to collapse
Same here. Sorry for asking in here but does anyone know is there limit?.... and if yes how many time you can flash it, or may just go randomly?
k2buckley said:
That is very interesting that you saw the RA recovery 1.8 at the bottom of the screen for a second. What hardware version is your phone? I believe 1.8.0 is only for phones with the older erase block size, which is hardware 002, and some 003. Some of the later 003 models were the new erase block size, which is 0040000. The old size is 0020000. If you're 0040000, 1.8.0 wouldn't work anyways.
As far as changing hboots go, if you're on 2.02 or 2.10 currently, you can't easily downgrade. If you're on something other than those, you should be able to switch hboots easily.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'm actually not sure how to check that . But, As for the hboots, I have successfully downgraded from 2.10 to .076 three times as of right now. I have a few things I'm going to try in succession and I'll post the results .
n00barmy said:
I'm actually not sure how to check that . But, As for the hboots, I have successfully downgraded from 2.10 to .076 three times as of right now. I have a few things I'm going to try in succession and I'll post the results .
Click to expand...
Click to collapse
The only way to check that (that I know of) is issuing a command from a shell. it would be something like cat /proc/mtd.
Is this the method you've been using to downgrade hboot?? http://forum.xda-developers.com/showthread.php?t=883548&highlight=downgrade+hboot ? Otherwise, I'm not sure... As far as I always understood, if you had the newer erase block size (some 003 and all 004 hardware) then downgrading from 2.02/2.10 hboot was not even possible (without making a brick). If you had hboot 2.02/2.10 on the older erase block size then you would be able to successfully downgrade. Anyhow, good luck with your efforts and please post your results.
Hi, ive just tried s-off and rooting my HTC desire so that I can flash custom ROM's, this is my first time doing this ever and ive been studying it for weeks, I cant say I was calm about doing it, in fact I was bricking myself all the way through, however it seems to have gone well other than one slight thing.
After careful study I decided to go with a video and step-by-step insturctions on the unlockr site, including links to all the required files.
I have the Revo Stock hboot now and also have clockworkmod on my phone, I followed the root instructions to the letter as well as follow the video, however decided to use clockworkmod first to make a backup and restore image to my sdcard first incase anything went wrong, I then installed the superuser.zip file, it said this all went fine and installed successfully and enjoy, after a reboot of the phone, I have no superuser in the apps menu ?
Tried installing it again, once again it said successful and enjoy, but still no superuser in the apps menu ?
If I wanted to just root my phone again now, im not sure which way to do it as I now have a strange hboot version on my phone ?
Im also new to these forums and wasnt sure if this was the right place to post this, any help would be greatly appreciated.
hi, post all info from hboot/fastboot screen
-Revolutionary-
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.14
Aug 10 2010, 17:52:10
HBOOT
(VOL UP ETC..............)
If is not working via recovery try to download it from market or push it manually(adv, qtadb)
Sent from my HTC Desire using XDA Premium App
Thanks, I had a look on market and was gonn ask if that was the same superuser, so although I dont have the app yet am I pretty much still routed ?
I was gonna run unrevoked 3 last night to try and root a different way but thought i'd wait for a reply on this thread first, should I try that or is there no need ?
Just tried downloading superuser onto my phone then thought I test it, so I downloaded titanium backup too, when I ran titanium it said unable to gain root access, this program will not work, any clues anyone ? My info is above, and suggests that I'm rooted.
After using Revolutionary you have to flash this superuser.zip from recovery to get root access (you didn't do this, did you?:
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efgh-signed.zip
So uninstall superuser and Titamnium Backup, boot into recovery, flash the superuser.zip and then try again.
Yes I did do this, my first post clearly states I tried this twice, then rebooted the phone, went into the apps menu and no superuser, so I tried to manually download superuser from market.
Although it says its installed and completed successful / enjoy, its like the root part of the whole process isn't taking effect ?
You may not have enough free space on the /system partition and although the .zip reports a successfull installation, it may not install.
Seanie280672 said:
Yes I did do this, my first post clearly states I tried this twice, then rebooted the phone, went into the apps menu and no superuser, so I tried to manually download superuser from market.
Although it says its installed and completed successful / enjoy, its like the root part of the whole process isn't taking effect ?
Click to expand...
Click to collapse
Okay sorry missed that. I recommend to ask Revolutionary in their IRC channel.
Sent from Sandvold's ICS using Transparent XDA App
TVTV said:
You may not have enough free space on the /system partition and although the .zip reports a successfull installation, it may not install.
Click to expand...
Click to collapse
Ok, how would I free up space on this partition, I take it you mean the phone rather than the SDcard ? I have most of my apps moved to the SDcard now, well the apps I can move anyway, some dont allow it.
I installed quick system info from market, it would appear out of the 250mb supplied I only have 70kb left, god knows where all this space has gone, but now im in catch 22, it would appear the reason I cant root is beacuse I dont have enough system space, but I cant delete any system apps cos im not rooted, any idea's anyone ?
Tried a reset of the phone but it didnt change anything in the system folder or available space.
Well, in layman's terms, the Desire has three user-visible partitions, excluding the SD card. Those are:
1) Data (/data): this is the partition where all your apps, app data, contacts and settings reside. This is also where the Dalvik-cache lives;
2) Cache (/cache): this partition is, as the name states, a cache partition;
3) System (/system): this is where your ROM resides. This is the partition where the .zip you're installing from Recovery is trying to copy its contents to, namely "Superuser.apk" and "su". In order for this procedure to succeed, you must have at least 900 kB free on this partition (Superuser.apk + su = ~860 kB, if you're trying to install Superuser 3.0.7).
If you're saying that you've checked the free space on your /system partition with a tool and it reports that you only have 70 kB free, that might be your problem. You can free up some space on the /system partition by deleting some files (which are safe to delete, namely some ringtones, a couple of wallpapers), but i must know what ROM are you using, first. Can you please provide that info?
P.S. - The above-mentioned procedure requires you to use ADB shell, so if you're not familiar with that or you just don't wanna mess with stuff like that, you can always install a pre-rooted ROM of your choice.
Hi, thanks for the info, it was very helpful, the ROM details are below, to me its just the stock Froyo ROM, but ive since unlocked the phone, S-OFF'd it and installed CWM, the HBOOT has also changed.
Andriod version 2.2
BB version: 32.48.00.32U_5.11.05.14
Kernal version: 2.6.32.15-ge2c73db
[email protected]#1
Build number: 2.22.351.3 CL283825 release-keys
Software number 2.22.351.3
Browser version Webkit 3.1
Hope this helps
I was also thinking of installing a pre-rooted ROM to get past this, As this would be my first time doing this I wasnt too sure which one to go for, the one I fancied is called PyramidMod007_v11_b-STOCK, would this go straight on ? the radio required is pretty much the same as my existing radio.
As mentioned earlier, I have a strange HBOOT version on my phone now, those details are as follows:
-Revolutionary-
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.14
Aug 10 2010, 17:52:10
HBOOT
(VOL UP ETC..............)
Nothing strange about your HBOOT. That's how it's supposed to "look" after using Revolutionary.
So you're running stock HTC FroYo. The way i see it, you shouldn't even bother rooting your current ROM, as FroYo is obsolete and you should move to Gingerbread. Browse through the development section, pick a ROM that you like and install it via Recovery (you don't need root for that). Mind you, you need to carefully read the requirements for each ROM. For example, some are made for the stock /system size (250 MB), some are made for the Data++ /system size (180 MB) etc. Also, some ROMs will not work without an EXT 3/4 partition on the SD card.
Thanks, I proceeded to try a couple of rom's out, tried the pyramid one first, but my phone was very very laggy with it, next I flashed the revolution rom, absolutly loving this rom, gonna stick with it for a bit I think, battery is much better on it, its nice as smooth, and boot times are amazing compared to the stock rom as well as now being rooted too.
I went for the apps2sd+ version of this rom, working fine on my current radio, I created a 1gb EXT3 partition on my SDcard prior to flashing using clockwork mod just incase, it said it required it.
Thanks for all your help guys, was so scared of bricking my phone through all of this, everything goes on about the risks all the time, but it was no where near as bad as that, guess they have to inform you though.
Well, the most dangerous procedures for your phone are when you're writing radios or HBOOTs. When you power up your phone, it first "boots" the Radio partition, then HBOOT and only afterwards it boots the kernel, OS etc. So if happen to frack up either one of these two partitions, Radio or HBOOT, you'll end up with a brick. Flashing ROMs or kernels, on the other hand, is perfectly safe.
Enjoy your "new" phone!
Have you tried unrevoked 3? It's work fine for me. I just ad to update superuser form the market after.
Hello all,
I realize that this is a common problem and that searching the forum SHOULD lead me to a viable solution, but alas this problem keeps rearing it's ugly head.
Ever since I initially rooted my phone, my phone will bootloop regardless of the ROM I flash to it. I am currently using the GBSense ROM.
In HBOOT, I am showing -
VIVO_W XB SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-1.09.01.0622
eMMC-boot
I am using Revolutionary CWM v4.0.14
Any of this information provide clues to what could be causing my bootloop problem? Clearing the cache and Dalvik SOMETIMES works, but not always. Many times I am forced to do a factory reset, reload the image, restore from backup, and then pray that I don't lose battery or power down for any reason. :laugh:
Any help would be greatly appreciated.
Thanks!
You could always try using a different recovery. 4ext is a great option. As well as twrp. Twrp can be found in the development section. And the 4ext can be found by Google.
Sent from my Incredible 2 using Tapatalk 2
shniggens said:
Hello all,
I realize that this is a common problem and that searching the forum SHOULD lead me to a viable solution, but alas this problem keeps rearing it's ugly head.
Ever since I initially rooted my phone, my phone will bootloop regardless of the ROM I flash to it. I am currently using the GBSense ROM.
In HBOOT, I am showing -
VIVO_W XB SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-1.09.01.0622
eMMC-boot
I am using Revolutionary CWM v4.0.14
Any of this information provide clues to what could be causing my bootloop problem? Clearing the cache and Dalvik SOMETIMES works, but not always. Many times I am forced to do a factory reset, reload the image, restore from backup, and then pray that I don't lose battery or power down for any reason. :laugh:
Any help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
It's most likely the radio. Take a look at the radios thread in development and you will likely want the .0312 radio. Pay close attention to the instructions.
gtdtm said:
It's most likely the radio. Take a look at the radios thread in development and you will likely want the .0312 radio. Pay close attention to the instructions.
Click to expand...
Click to collapse
Well that appears to be the case! Thanks! I was on the verge of trying that, but I needed confirmation first. Once I changed the radio, it booted up no problem. Let's hope it stays that way!
shniggens said:
Well that appears to be the case! Thanks! I was on the verge of trying that, but I needed confirmation first. Once I changed the radio, it booted up no problem. Let's hope it stays that way!
Click to expand...
Click to collapse
No problem. Make sure to rename or move that file or every time you hit your bootloader you will be stuck in an endless loop where it tries to re-install that file.
Hello, all.
I have an Evo 4G that is rooted with MikG3.11, which has been an awesome and stable ROM for...2 full years now?
Anyway, I've never had any trouble, and I haven't installed or changed anything in weeks...but last night while I slept, gremlins invaded my phone and tampered with it. When I woke up (a lucky thing in itself since I use my phone for an alarm clock), my phone was hung at the android animation screen. I pulled the battery and rebooted, but it kept bootlooping...which has never happened before.
Here are the specs:
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00
I can still get into Recovery, which is ClockWorkMod v2.6.0.1.
Here are the steps I've performed/tried so far:
Performed a Nandroid backup from within CWM recovery
Successfully executed "mount USD storage" and pulled everything I could get access to from the device down to my Win7 PC
Wiped the Cache partition
Wiped the Dalvik Cache
Tried rebooting again after clearing the caches, but (as before) when it gets to the end of the boot animation, it loops rather than fully loading the ROM/presenting the unlock screen, and I have to pull the battery and start over
Unfortunately, that's about the extent of my expertise, as I'm pretty much a noob at this phone hackery business and was wondering if there's a recommended way to try to restore access to my phone without potentially losing some or all of my data. (I'm not 100% confident that the Nandroid backup is going to capture all of my contacts, calendar events, and misc app data. And it's been several months since I ran a Titanium backup from "within" the phone's OS.)
I do have adb access set up on my Win7 PC, but I didn't see anything there that was a clear "next move".
Is it possible to restore the boot or system image without touching the data? Or is a full wipe in my future?
I look forward to any advice from the experts...
- Vassoom
This happens. You're probably just going to have to clean flash and start over. Before you do that, however, switch to a more reliable recovery (Amon_RA's, or preferably, smelkusMOD).
Captain_Throwback said:
This happens. You're probably just going to have to clean flash and start over. Before you do that, however, switch to a more reliable recovery (Amon_RA's, or preferably, smelkusMOD).
Click to expand...
Click to collapse
Agreed. While CWM is a great recovery for most Android devices, it's known to have issues on the EVO 4G. Do as Captain Throwback suggested and swap to a recovery that's Amon_Ra-based. The Smelkus recovery he's referring to is a great one and I used it on the various EVO's I once owned. It has a few extra features built in to it and you can't go wrong with it.