Stuck in non funtioning RUU Froyo with S-ON - Droid Incredible Q&A, Help & Troubleshooting

Hello. I'm in a bit of a bind which I cannot get myself out of, so I am posting here. I've been around for over a year lingering, updating, trying new things, etc. I came across a free Incredible, which I attempted to root, and install a ROM onto. I rooted the phone with Unrevoked 3, booted into Clockwork mod recovery, made a nandroid, and installed the ROM. The installation was successful, however, on boot after the HTC splash screen the phone vibrates 5 times and the led flashes green constantly. The same thing happened when I tried to boot into recovery.
I found that the phone booted to the Set Up, which crashed, if it was plugged into a computer. I ADB saw the device but I could not push files or execute commands. Unrevoked S-OFF would not work also.
After Googling, I found a 2.2 RUU, which installed successfully, but I get the same boot problems. If the USB is plugged into a computer before the phone is turned on I actually get to Android and can play around. The phone will not recognize any memory, SD or internal; only phone memory is recognized. I tried ADB again with no luck, most likely has to do with the phone not recognizing memory. So I flashed the RUU from HBOOT which flashed fine, but the same problems still persist.
I am out of ideas, which I hope someone has anything I can try.
S-ON
HBOOT 0.92
MICROP-0417
TOUCH PANEL - ATMELC03_16AC
RADIO 2.15.00.07.28
Edit: I tried to be as detailed as possible, so ask any questions if I did not make since.

Check this out
http://pvillecomp.com/?page_id=33

Thank you, trying it now.

cmlusco said:
Check this out
http://pvillecomp.com/?page_id=33
Click to expand...
Click to collapse
I cannot thank you enough.
Edit: Unrevoked gave me s-off. I want to be clear this time before I install any ROM. Do I need to run unrevoked-forever.zip? I am 99.999% positive I do not since I already have s-off. I want to get a new ROM on tonight.

Unrevoked 3 now contains the forever patch, as previous versions did not. So you are good to go flash away, after making a nandroid of course

No need for unrevoked forever if you are s-off

Thanks! On my way to a new ROM.

Related

[Q] Boot loop (no boot image)

Hey guys! I have no idea where to post, so I apologize if I'm in the wrong section.
I'm very new to rooting and I've seem to come into a major problem. (Atleast in my eyes.) To start off I had gotten my HTC Evo 4g & used the method of UNRevoked to root my Evo. I then found out UNRevoked isn't a full nand unlock & all the nitty gritty, so I came upon Toastcfh's guide to rooting the Evo. I performed half the instructions as told and was then in this boot loop. Right before it happened I (think) I erased the Dalvik Cache, but I definitely hard formatted the whole phone/cache. Anyway as told in the instructions I was suppose to flash the PC36IMG.zip to my phone and I did. Once that all configured it rebooted on itself & now the phone is stuck in boot with stock recovery method. I can load into HBOOT and see that in green lettering it says: SUPERSONIC EVT2-2 SHIP S-OFF, HBOOT-0.79.0000, TOUCH PANEL-ATMEL224_16ab, RADIO-1.39.00.04.26. Please help me. I havent used my phone for a whole day now. :\
To add: Before the PC36IMG.zip got added on my phone, I had clockwork mod recovery. Now I have the stock one I'm guessing. I have tried a stock RUU through HBOOT USB, but the RUU either says some error my phone battery is under 30% (when it's fully charged). Or the RUU will say waiting for device to connect. & I tried putting a rom on my sd card then flashing or whatever and my computer wont open my sd card unless, I put it in the disk reader. Please ask questions, I'll answer as best as I can...thanks!
The current Unrevoked does in fact unlock nand, so you should have stopped there. I am not familiar with Toast's rooting method, so I can't say for certain what happened. The good news is, you are probably fine, you just need to reflash a rom. Since you can't get into recovery, the best way to fix this is to flash a rooted stock pc36img from your hboot. Download the file from THIS THREAD, rename it to pc36img, put it on your sd card and boot into hboot. It will find it automatically and then it will take a few minutes to load it. Once it's loaded it will ask if you want to run the update, choose yes and let it do its thing. When it's done you will have the latest rooted stock rom on there and clockwork recovery. Make sure you delete the old pc36img off your sd card before doing this. Good luck and godspeed.
Did what u said there MetalHead. still getting boot loops at the white htc evo 4g screen and can not get into recovery. Do you have anymore suggestions?
I would try it again but use this PC36IMG.zip instead.
http://www.4shared.com/file/5U4M4eVi/PC36IMG.html?cau2=403tNull
This one is completely stock. You will be unrooted after running it, so you will have to root again.
Sent from my HTC EVO 4G with Tapatalk

[Q] Question on un-rooting

Ok, what should I do? Long story short. I tried to use unrEVOked to root my phone. Didn't work, would not finish the process and hung multiple times. So I re-did my phone back to stock and used Autoroot2.3 which hung also, twice. xHausx game me advice on what to do, but somehow I made it worse and eventually lost 4G and the phone acted erratic. Soooo, I used a stock RUU to try to correct the issues. It solved all of them. HOWEVER, the rooting attempts never fully rooted the phone, but the HBoot states "s-off". I can't "s-on" because I no longer have a recovery tool. What the hell should I do? Root or figure out a way to un-root? Hope this makes sense?! Thanks in advance!
http://www.shipped-roms.com/shipped/Supersonic/
Download the 3.70 RUU, boot into the bootloader and select fastboot, and then run the RUU exe. After that try unrunning unrevoked, but let it run..sometimes it hangs and moves on, you should do 2 reboots with unrevoked.
http://goo-inside.me/evo/stock/ruu/
Follow the instructions at the top of the page. Enjoy.

[Q] Is it possible to Recover my DInc?

I hope someone in this community is able to help. I've already been scouring Google this morning for people with a similar issue and haven't been successful in getting my phone to come back so I suspect there may be a hardware issue.
Here's a summary of the problem:
My phone shutdown this morning while I was listening to a podcast. It got stuck in a boot loop at the splash screen, constantly rebooting itself. A battery pull would not solve the problem. I was able to get it into HBOOT (version 0.92) but when I tried going into recovery from there, It got stuck on the splash screen (no looping). Before all this I had been running Nils Business Gingersense for quite a while and things were working fine, in case anyone needs that detail.
After failing to boot to recovery, here are some of the things I have tried to fix this issue:
1. Factory reset in HBOOT
2. Flashed RUU 2.2 and then tried RUU 2.3.4 through HBOOT. Though neither of these would get the phone to come up, the splash screen reboots stopped and the phone just freezes in splash screen now (over 30 minutes with no change).
3. Tried to reflash CWM 5.0.2.0 through Fastboot. Although the phone is recognized by 'fastboot device', it says 'remote: not allowed' when try to flash the .IMG file.
4. Tried to flash an older CWM recovery from when I originally rooted my phone --same 'not allowed' error
5. Ran the official RUU for Froyo on my PC and it looked promising but I never got past the splash screen afterward a reboot.
6. I don't know a ton about ADB but ADB does not recognize my device even though Fastboot does.
At this point I'm not sure what else to try. It seems promising that I can get into HBOOT and that Fastboot will recognize my phone but what can I do with that now?
Thanks for any ideas you might have.
Have you tried flashing cwm thru hboot as a PB31IMG.zip? http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip. If that dosent work you could try to update hboot to 1.02 and htcdev unlock it. This will allow extended fastboot commands. You can do this on the htcdev website. Or you could downgrade hboot to the 0.77 engineering bootloader http://dinc.does-it.net/Hboots/ENG_Hboot_0.77/PB31IMG.zip which basicly does the same thing, and might be a better option than upgrading. You are s-off right?
Yes, I still have S-OFF. I did try flashing several recoveries through hboot and they all acted like they updated fine but I wasn't able to boot into any of them because I kept getting frozen at the white screen after choosing recovery from hboot. I will try another hboot and see if that makes any difference. Thanks.
Cmlusco, I tried the CWM version you posted with hboot .92 and .77 but had no luck. I also tried walking through the hboot upgrade steps on the htcdev site but I couldn't get the RUU exe to find my phone. This is odd because an older RUU found the phone just fine earlier today.

I'm in a bit of a pickle (GB, S-ON, ADB is broken)

First of all, I gotta give props to Albinoman for getting the Incredible to where he has (Jellybean, on the Incredible!... wow!)
http://forum.xda-developers.com/showthread.php?t=1778190
I've been following Albinoman's progress and while I was trying to troubleshoot the "low space notification" we're all too familiar with, I made a HUGE mistake.... I was using Albinoman's Beta 2, which worked great, but I tried restoring a nandroid backup and it failed, due to a corrupt SD card. Then, I tried restoring to another backup, which also failed. I then set out to run a scandisk on the SD card, so I shut off my phone thinking I could just boot back into recovery no problem right?!? WRONG!
After fixing the SD card, I was unable to even boot into recovery, I was getting the scary 5 vibrates of death, and I found this thread, which was half-helpful:
[HOW-TO] Fix 5 vibrate and black screen
http://forum.xda-developers.com/showthread.php?t=1110865
It was able to get my SD card working (previously it didn't at all), but I still cannot boot without having a USB cable plugged in (otherwise I get the 5 vibrates and a blank screen).
The thread suggested using z4root to gain temporary root but when I try that, it just sits there for a very long time and times out.
Here's where my biggest problems come in...
I'm currently running Gingerbread 2.3.4, S-ON, and ADB is BROKEN on my phone
My HBoot is version 1.07.0000 (I was 0.92.0000, but now I flashed cmlusco's newer HTC rom, so it changed)
What I currently have to work with (what works):
Wifi, SD Card (new one of course), 3G, and I'm able to boot, and I got my bootloader unlocked!
I cannot find any way to root my phone based on my current situation.
I have found plenty of ways to root (I'm used unrevoked plenty of times but it wont help me now because ADB wont work with my phone because it's broken, but I can't fix ADB, because I can't get root, it's really a sad situation)
I've tried HTC's RUU official root method, other RUU's, and Unrevoked, but they all don't work because my ADB is messed up
Also, I don't know if this helps, I can use fastboot, and I was able to flash an image using fastboot commands, but it's been awhile since I've tried that, and I don't know of anything I can flash via fastboot to help my situation.
My main goal is, I just need to get rooted again so that I can re-flash Albinoman's sweet Beta 3 ROM which I've been unable to even try
Thanks for the help you guys are amazing!
UPDATE: It's FIXED!!!! Here's the short version of how (in case it happens to anyone else)
To start, my phone A: Would not boot B: Would not read the SD card, or EMMC, EVEN in recovery C: all USB was broken including ADB (but fastboot worked) and D: I managed to lose root by flashing like mad in hopes of fixing AB and C
Step 1: I flashed cmlusco's ROM that he suggested which got my hboot up to date etc...
Step 2: I went to http://htcdev.com/bootloader/ and unlocked my bootloader (BUT I skipped straight to step 8 (the fastboot part, since everything before that was a waste of my time since my USB/ADB was hosed))
Step 3: I flashed this recovery image and ran "fastboot flash recovery recovery.img"
Step 4: I downloaded superuser and loaded it through recovery, now that my SD card worked
Step 5: I then was able to do the following in order to fix the USB/ADB problem:
using this file and this file and running them in an android emulator app I downloaded from google play (since my USB was broken)
Terminal emulator & ADB commands:
Code:
su
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd-eng.img > /data/mtd-eng.img
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd-eng.img
reboot
(credits for this to this thread)
Step 6: I was now fixed, so I just wiped my phone and flashed Albinoman's Jellybean ROM because it rocks!
Thanks to tiny4579 and cmlusco for both of your help!
Two quick questions:
1. Does USB mass storage work? (do your sdcard and emmc get recognized as drive letters when it boots) - if it doesn't there MAY be a problem but question 2's suggestion may fix it.
2. Did you try uninstalling and reinstalling the adb drivers?
This is just off the top of my head. Oh, now I see that fastboot works so basic USB communication works so it may be a driver issue.
Oh, since fastboot works you should be able to flash CWM recovery and a superuser zip to root unless it says not allowed. But if you can flash and boot recovery at that point no point on rooting, just flash a rooted ROM like jellybean beta3.
meadowsjared said:
First of all, I gotta give props to Albinoman for getting the Incredible to where he has (Jellybean, on the Incredible!... wow!)
http://forum.xda-developers.com/showthread.php?t=1778190
I've been following Albinoman's progress and while I was trying to troubleshoot the "low space notification" we're all too familiar with, I made a HUGE mistake.... I was using Albinoman's Beta 2, which worked great, but I tried restoring a nandroid backup and it failed, due to a corrupt SD card. Then, I tried restoring to another backup, which also failed. I then set out to run a scandisk on the SD card, so I shut off my phone thinking I could just boot back into recovery no problem right?!? WRONG!
After fixing the SD card, I was unable to even boot into recovery, I was getting the scary 5 vibrates of death, and I found this thread, which was half-helpful:
[HOW-TO] Fix 5 vibrate and black screen
http://forum.xda-developers.com/showthread.php?t=1110865
It was able to get my SD card working (previously it didn't at all), but I still cannot boot without having a USB cable plugged in (otherwise I get the 5 vibrates and a blank screen).
The thread suggested using z4root to gain temporary root but when I try that, it just sits there for a very long time and times out.
Here's where my biggest problems come in...
I'm currently running Gingerbread 2.3.4, S-ON, and ADB is BROKEN on my phone
What I currently have to work with (what works):
Wifi, SD Card (new one of course), 3G, and I'm able to boot
I cannot find any way to root my phone based on my current situation.
I have found plenty of ways to root (I'm used unrevoked plenty of times but it wont help me now because ADB wont work with my phone because it's broken, but I can't fix ADB, because I can't get root, it's really a sad situation)
I've tried HTC's RUU official root method, other RUU's, and Unrevoked, but they all don't work because my ADB is messed up
Also, I don't know if this helps, I can use fastboot, and I was able to flash an image using fastboot commands, but it's been awhile since I've tried that, and I don't know of anything I can flash via fastboot to help my situation.
My main goal is, I just need to get rooted again so that I can re-flash Albinoman's sweet Beta 3 ROM which I've been unable to even try
Any help anybody could offer me would be GREAT! Thanks XDA, you guys are amazing!
Click to expand...
Click to collapse
What hboot version are you on? Have you tried an ruu thru hboot?
I would try an ruu thru hboot first. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip
If that dosent let you boot, use the htcdev site to unlock your bootloader. And then fastboot flash cwm recovery, and then superuser thru cwm. Then you will be rooted and can try to wipe everything and flash a rom.
tiny4579 said:
Two quick questions:
1. Does USB mass storage work? (do your sdcard and emmc get recognized as drive letters when it boots) - if it doesn't there MAY be a problem but question 2's suggestion may fix it.
2. Did you try uninstalling and reinstalling the adb drivers?
This is just off the top of my head. Oh, now I see that fastboot works so basic USB communication works so it may be a driver issue.
Oh, since fastboot works you should be able to flash CWM recovery and a superuser zip to root unless it says not allowed. But if you can flash and boot recovery at that point no point on rooting, just flash a rooted ROM like jellybean beta3.
Click to expand...
Click to collapse
1st of all, thanks for getting back to me so quickly Tiny, you're amazing, and I appreciate all the work you've done with the Dinc, thanks for being so active!
1. No, mass storage doesn't work (I assume you mean plugging in the phone and having it mount the SD card as a drive on the computer)
However, I am able to now use both my SD card from within Gingerbread, and the recovery, but only after doing the "fastboot oem enableqxdm 0" trick
2. I haven't tried uninstalling and reinstalling the ADB drivers, but only because.... I'm a developer, and sometimes I develop on my home computer, and sometimes I develop at work, and they both exhibit the same behavior, so I don't think it can be that both computers, just happened to get messed up at the exact same time, right when my phone got hosed?
Also, I've used ADB plenty in the past, on both computers, so I'm certain they're set up right, just between having two computers to work with, AND the extensive use I've made of ADB in the past (I'm the office Root-er, I've rooted most of my co-worker's phone for them, so I've had quite a bit of experience (and should have known better than to turn off my phone when I did which got me in this pickle ))
Just to be clear though, basic USB communication works, but only in HBOOT, NOT from Gingerbread, actually, having the phone plugged into USB (whether or not USB debugging is turned on on the phone), WILL lock up my computer until I unplug it, and as soon as I unplug, my computer snaps back to normal So I think somehow something in the phone got hosed so the ADB is broken, however, I can't fix it because I can't get my root back because I'm stuck in the horrible stock gingerbread (no offense to anyone that likes it )
Also, yes, I've tried a ton of times to flash a superuser zip to root and it says it's not allowed/bad signature or whatever, because it's still S-ON
cmlusco said:
What hboot version are you on? Have you tried an ruu thru hboot?
I would try an ruu thru hboot first. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip
If that dosent let you boot, use the htcdev site to unlock your bootloader. And then fastboot flash cwm recovery, and then superuser thru cwm. Then you will be rooted and can try to wipe everything and flash a rom.
Click to expand...
Click to collapse
@cmlusco
I didn't even know you could use RUU's through hboot, I'll try that, as well as using the HTC unlocker RUU with hboot.
I'd already tried those things normally, but with by USB being hosed, it didn't help much. :-\
I'll post back when I've given them a try
cmlusco said:
What hboot version are you on? Have you tried an ruu thru hboot?
I would try an ruu thru hboot first. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip
If that dosent let you boot, use the htcdev site to unlock your bootloader. And then fastboot flash cwm recovery, and then superuser thru cwm. Then you will be rooted and can try to wipe everything and flash a rom.
Click to expand...
Click to collapse
I'm on HBoot 0.92.0000
and it seems to only allow me to flash newer, or the same version as what I've got (because I've tried downgrading)
I just tried the RUU from HTC to root my phone.
I ran the RUU, put the phone in hboot, and it sat and said "verifying phone information" or something like that and said "error 170, usb connection error"
I also put the phone in "fastboot" and tried again, it didn't seem to make a difference.
Now regarding flashing an RUU through hboot, how would I go about doing that? I'm assuming you're talking about throwing the PB31IMG.zip on my SD and booting into Hboot. Now that DOES work however, I'm still S-ON, so unless it's a factory image, it ain't gonna like it
That is, unless there's some kind of fastboot voodoo that can be done to get something on there to exploit it and get my back my root I once had and loved!
meadowsjared said:
I'm on HBoot 0.92.0000
and it seems to only allow me to flash newer, or the same version as what I've got (because I've tried downgrading)
I just tried the RUU from HTC to root my phone.
I ran the RUU, put the phone in hboot, and it sat and said "verifying phone information" or something like that and said "error 170, usb connection error"
I also put the phone in "fastboot" and tried again, it didn't seem to make a difference.
Now regarding flashing an RUU through hboot, how would I go about doing that? I'm assuming you're talking about throwing the PB31IMG.zip on my SD and booting into Hboot. Now that DOES work however, I'm still S-ON, so unless it's a factory image, it ain't gonna like it
That is, unless there's some kind of fastboot voodoo that can be done to get something on there to exploit it and get my back my root I once had and loved!
Click to expand...
Click to collapse
That PB31IMG.zip i posted is 4.08.605.15, the latest android version for our phone. It is official and signed by htc, so it should flash even if your s-on. Just place it on your sd in no folders and hboot should find it.
cmlusco said:
That PB31IMG.zip i posted is 4.08.605.15, the latest android version for our phone. It is official and signed by htc, so it should flash even if your s-on. Just place it on your sd in no folders and hboot should find it.
Click to expand...
Click to collapse
Yes, you're right, I was able to flash that image using hboot, but sadly... the adb is STILL broken and doing all the same things it was before (it doesn't work, and when I plug it into my computer, it freaks out my computer and the computer freezes until I unplug the phone, then everything is fine again)
It seems that all these images write everything to the phone... BUT what I need. I've found some things that "should" fix my problem, but they are all unsigned, and therefore they require root. Is there a chance that now with this newest RUU you gave me "z4root" will work cmlusco? (the reason I ask is, I'm hoping that an app that roots the phone without the computer will work, since every time I plug into a computer, it doesn't work, and just freaks out the computer)
Also, regarding the official HTC way to root, I tried running their "PB3120000_Incredible_C_hboot_1.02.0000_4.08.605.2.exe" file, however, that didn't work in the slightest (because it uses adb commands to talk to the phone). Is it possible that there's a way to extract the PB31IMG.zip file from that exe file and therefore I would be able to flash that using hboot, and the phone would like it because it's signed by HTC (I'm assuming)?
By the way, ever since I flashed that newer PB31IMG.zip ROM, now when I go into hboot, at the top it says "*** LOCKED ***", and it never said that before, I don't know if that matters at all? :-\
Also, if it helps any, here's what the update looked like....
*** LOCKED ***
INCREDIBLE XC SHIP S-ON
HBOOT-1.07.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.12.20
Apr 24 2012,22:58:40
HBOOT
Parsing... [SD ZIP]
[1] RADIO_V2 - OK
[2] BOOT - OK
[3] RECOVERY - OK
[4] SYSTEM - OK
[5] SPLASH1 - OK
Update Complete...
Then, after running the update, it asked me if I wanted to reboot, it showed the picture of the phone with the arrows in a circle around it, then when it wen to reboot, it did the usual (for me lately), and gave me the 5-vibrates of death and a black screen, the only way to get out of it is to do a battery pull. Then, after doing that, if I just plug in the cable, I can boot into the new rom just fine, but if the cable isn't plugged in, I just get the 5 vibrates of death, like this guy....
[HOW-TO] Fix 5 vibrate and black screen
http://forum.xda-developers.com/show....php?t=1110865
But sadly, in order to completely fix myself, I need root, and I can't seem to even get temporary root? :-\
I'm hoping maybe something there might help y'all to help me? :-\
tiny4579 said:
Two quick questions:
1. Does USB mass storage work? (do your sdcard and emmc get recognized as drive letters when it boots) - if it doesn't there MAY be a problem but question 2's suggestion may fix it.
2. Did you try uninstalling and reinstalling the adb drivers?
This is just off the top of my head. Oh, now I see that fastboot works so basic USB communication works so it may be a driver issue.
Oh, since fastboot works you should be able to flash CWM recovery and a superuser zip to root unless it says not allowed. But if you can flash and boot recovery at that point no point on rooting, just flash a rooted ROM like jellybean beta3.
Click to expand...
Click to collapse
@tiny4579
To be more clear, the basic USB communication doesn't work, the only way I can get anything that uses USB to work, is by booting into fastboot, and I have been able to do fastboot commands (like "fastboot oem enableqxdm 0"). So it seems that fastboot's USB works just fine (I've tested this on multiple computers), but anything after that, like trying to use the USB from the operating system, is totally broken. So I'm guessing that internally, the phone's drivers for USB are separate for hboot, and therefore still work, however, the phone's USB drivers for Gingerbread, are completely broken, even though I've been able to flash 2 different versions of signed gingerbread from HTC, they still don't seem to fix my USB problem even though it's writing the entire system all over again. Is it possible that there's a signed HTC zip that will fix my USB, that would fix me... the only question is.... does a signed HTC zip exist that will fix my USB??? :-\
Ok, I've got great news, I was able to finally unlock my bootloader! so now when I go into HBOOT, it says at the top "UNLOCKED", however, it still says S-ON, and I still don't have root, but I think we're getting there!
So now that my bootloader is unlocked, I'm assuming I should be able to either load a custom recovery (like clockworkmod), however, I still can't use ADB to do anything so things like unrevoked wont work for me sadly
Do you guys have any advice on what I can now do that my bootloader is unlocked? (I'm a little unclear about what the whole bootloader thing does for me). I think I understand rooting, at least enough, and I thought I understood the bootloader, and the unlocking. But now that my bootloader is unlocked, it still wont let me load anything like CM7.1, or clockworkmod (I tried both of those by going into recovery and trying to flash the update.zip).
Either way, I'm very encouraged by the fact that my bootloader is unlocked, I'm assuming it should help me to acheive my goal of rooting and eventually gettting Albioman's Jellybean on there?
meadowsjared said:
Ok, I've got great news, I was able to finally unlock my bootloader! so now when I go into HBOOT, it says at the top "UNLOCKED", however, it still says S-ON, and I still don't have root, but I think we're getting there!
So now that my bootloader is unlocked, I'm assuming I should be able to either load a custom recovery (like clockworkmod), however, I still can't use ADB to do anything so things like unrevoked wont work for me sadly
Do you guys have any advice on what I can now do that my bootloader is unlocked? (I'm a little unclear about what the whole bootloader thing does for me). I think I understand rooting, at least enough, and I thought I understood the bootloader, and the unlocking. But now that my bootloader is unlocked, it still wont let me load anything like CM7.1, or clockworkmod (I tried both of those by going into recovery and trying to flash the update.zip).
Either way, I'm very encouraged by the fact that my bootloader is unlocked, I'm assuming it should help me to acheive my goal of rooting and eventually gettting Albioman's Jellybean on there?
Click to expand...
Click to collapse
Now you need to fastboot flash cwm. Download this file http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, and place it on your pc in the same folder as the fastboot.exe file.
Open a cmd prompt on your pc to where fastboot.exe and recovery.img are. Type the folowing:
Code:
fastboot flash recovery recovery.img
If you get no errors, go to the maim hboot menu and select recovery. You should now be in cwm recovery.
Download superuser http://dinc.does-it.net/Superuser/SuperUser_3.0.7.zip, and place it on your sdcard by going to mounts and storrage and selecting mount usb storrage. If it freezes up the phone or the pc, you will need to take the sd out and use a card reader to put it on the sd with a pc.
Then flash it thru recovery like you would a rom. Now you will be rooted. Then flash a rom of your choosing and hope it boots.
Might as well load the ROM when you load superuser. But flashing superuser is silly if you're going to flash a ROM with root right after it but it's probably still a good zip to keep on your sdcard.
tiny4579 said:
Might as well load the ROM when you load superuser. But flashing superuser is silly if you're going to flash a ROM with root right after it but it's probably still a good zip to keep on your sdcard.
Click to expand...
Click to collapse
Yeah i guess it is pointless to flash su, then wipe it, then flash a rooted rom.
Thank you both of you, you were a HUGE HELP!!!!! I'm FIIIIIIXED!!!!!!!!!!!!!!
I'm going to update the original post to detail how I got fixed (the short version is, I just did what cmlusco said, and as soon as I had root, I followed this and it worked!!!!)
tiny4579 said:
Might as well load the ROM when you load superuser. But flashing superuser is silly if you're going to flash a ROM with root right after it but it's probably still a good zip to keep on your sdcard.
Click to expand...
Click to collapse
I wound up loading superuser like cmlusco suggested, only because I wanted to have everything fixed and perfect before loading Albinoman's new ROM, just in case there were issues, that way I'd know that it was the ROM or my phone, especially since my SD Card freaked out on me and that's how I got into this mess
....But, you are right, the only problem is, I'm super paranoid, and I like to be super-thorough
meadowsjared said:
I wound up loading superuser like cmlusco suggested, only because I wanted to have everything fixed and perfect before loading Albinoman's new ROM, just in case there were issues, that way I'd know that it was the ROM or my phone, especially since my SD Card freaked out on me and that's how I got into this mess
....But, you are right, the only problem is, I'm super paranoid, and I like to be super-thorough
Click to expand...
Click to collapse
Glad its working for you.
Sent from my Galaxy Nexus using Tapatalk 2

[SOLVED] Bootloop with no access to recovery (S-OFF)

SOLVED. THE PHONE IS BROKEN AKA HARDWARE FAILURE
Hi,
My old Desire had been sitting in my desk for about a year since i bought myself a Galaxy S2. Today, I decided to try it out. Charged the battery first and then tried to boot it. Well, I got stuck in the splash screen. The phone had been working normally the last time i used it (maybe 6 months ago?) so i thought it was weird. Then I tried to boot it into recovery, and got again stuck in the splash screen. HBOOT came up normally but after pressing the recovery button the phone just made the boot vibration multiple times and then was stuck in the splash screen.
What I have:
- Alpharev S-OFF HBOOT: bravo_alphaspl-oxygenr2.img
- Oxygen rom (don't remember the version but i have the zip on my computer): update-oxygen-2.1.6-signed.zip
- My current HBOOT screen shows the following:
--- AlphaRev ---
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
- AFAIK the phone is the older AMOLED version (if that matters)
- I have a working ADB
- I dont have a goldcard
What I did after noticing the problem:
1. Read the sticky which told me to reflash my recovery.
2. Flashed the CWM 2.5.0.7 recovery via Android flasher. The program said it was successful but my phone was in a bootloop again without access to recovery.
3. Flashed the Amon Ra recovery via Android flasher. The program again said it was successful but the bootloop persisted.
4. Flashed both of the recoveries (one at time of course) via the adb fastboot command. Again, it was supposed to be successful, but the phone STILL was in the bootloop.
I thought the sticky explained my situation perfectly but apparently this is not the case
I have also a RUU lying around:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release
But I was hesitant to use it as I have the custom Alpharev HBOOT which might cause problems.
So what should I do now? I appreciate all advice.
Re: Bootloop with no access to recovery (S-OFF)
In my sig you'll find a thread with how to install 4ext recovery through pb99img. Check it out.
I DL'd the PB99IMG.zip file for the recovery and put it on my SD by moving the SD to my other phone and connecting it to my PC.
However, when the HBOOT searches for the PB99IMG.zip, it only says "No Image!".
Re: Bootloop with no access to recovery (S-OFF)
Are you sure you didn't put it in any folder?
Then, again in my sig, you'll find a partitioning guide. The first part of the guide will help you install a recovery. Try it.
Yes, I put it right in the root of the sd card.
The partitioning thread in your sig has a few methods of installing the recovery. But i have already tried them and for some reason they fail. I have now tried the Android flasher method, the ADB + Fastboot method and the PB99IMG.zip method. I have no clue why these should fail like i have described.
EDIT: Looks like I cannot run the RUU either. It says it failed to detect the device. What on earth could be going on when EVERY possible way of reinstalling the recovery fails? I was starting to think that maybe there was something wrong with my USB connection/drivers or ADB so I made a test and flashed another alpharev HBOOT (their bravo stock one: bravo_alphaspl.img) and the flashing procedure worked. So at least my ADB is working. Still no idea why the PB99IMG.zip just won't work... looks like my phone defies all these guides available here.
Update:
I downloaded the 2.3 GB RUU from the sticky topic. Suprisingly enough I could run it, it detected my device and went throught the whole RUU process without a single error. I booted the phone - and was again stuck in a bootloop. Went to HBOOT, chose recovery (the RUU should have flashed the stock recovery) but no, I could not get into the recovery. Instead the phone was again stuck in a bootloop. So I still cannot get into the recovery. The only thing that changed was the splash screen I was stuck on... (I had a custom splash, now it's the stock one)
I then formatted my SD, put the 4ext recovery PB99IMG.zip there and booted into HBOOT. This time It found the PB99IMG.zip. It asked if I wanted to update, I pressed yes and it went through it without any error. When it asked if i wanted to reboot, i pressed no, navigated into recovery and pressed the power button. This should have taken me to the 4ext recovery i just flashed successfully. And guess what? Bootloop again...
So after all this, I still do not have access to the recovery. I just get the bootloop every time. I've whacked around with android phones (mostly Galaxy S2 though) quite a lot but this far have never seen such a persistent problem which just evades all (for other people) working attempts to fix it. The procedures work exactly as described and give me no errors, but in the end the issue still persists: I cannot access the recovery because of the bootloop.
I was starting to wonder if it could be hardware failure causing this? Just a wild guess but the phone has been sitting in my desk for almost a year... I didn't change anything in the software. The only thing that comes to my mind is that the memory where the recovery and rom are stored is somehow corrupt. This would explain why I cannot get into the recovery even though i have reflashed it successfully multiple times. I also can change my HBOOT and splash screen.
Does anyone have any ideas left?
Re: Bootloop with no access to recovery (S-OFF)
Are you s-on now?
Yep,
At the moment i'm S-ON with the 2.3 RUU from your sig. Bootloader is 1.02.0001. I flashed the RUU from the PB99IMG. No errors. Still cannot get to recovery.
I then opened the phone and removed the mainboard but i could not see any damage at all. No burns, marks of water damage etc.
Re: Bootloop with no access to recovery (S-OFF)
As weird as it sounds, try putting the phone in the freezer without the battery for 10 minutes, then try to boot.
You are pretty good, man.
CASE CLOSED
Explanation: after putting the phone into the freezer for some time, I tried to boot. It booted normally to the ROM. Wifi worked, I could use internet, setup my settings etc. After 10 minutes the phone rebooted into a bootloop. This proves that the problem always was a hardware one, and this is why any software fixes couldn't solve the issue. Because i don't have a freezer in my pocket I can safely say the phone is broken and I can throw it away.
Thank you!

Categories

Resources