Related
I have officialy given up on repairing my phone. Looks like it's not possible to fix this thing. Just spent the better part of 3 pays (4hours of sleep a night) trying to get my phone fixed. My sister bought this EVO through some work deal and gave me it on Christmas. I rooted it that night, and bricked it 30mins later, because of the newer partition scheme it is currently impossible to get this phone back working...
This is what I have now. A EVO 4G that boots normally to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
A Vol Down + Power Boot boots to this screen. ftp://eto.homeip.net/shared/IMAG0004.jpg
I can also navigate to this screen. ftp://eto.homeip.net/shared/IMAG0005.jpg
Because of the S-OFF it is obvious to those in the know that I rooted my phone.
I'm just wondering if you guys think this scenaro will work.
_________________________________________________________________
Walk into a Sprint Repair Store, tell them my sister just bought the phone new (about a week ago) and gave it to me as a X-Mas gift. I chose to do the latest OTA-Update, and after it stopped booting and only went to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
Where I'd have to pull the battery to turn it off.
They will probably try VolDown+Power and might comment on S-OFF (which I will say I don't know what that is).
Hope they give me a new/refurbished EVO for free or less then $50.
===============================
Questions
* Should I go to a Sprint Store I've never been to? (There are stores within 20miles of me) (Closest knows I root phones, then other I've been into a bunch of times and may have given up on me)
* Should I get the receipt from my sister, who I don't want to tell I rooted/bricked phone
* Also please give me suggestions of anything that will help
BTW
* Am well within 30days of buying phone, though I'm not sure if my sister bought it through Sprint or not (Think she did though)
* I have pin/name/number on account and can easily activate a different phone they give me.
* Would rather not tell my sister or even get the receipt from her room to keep her from suspecting anything, but can if need be
Thanks for your suggestions, wanted to get this done by the end of the week before I head back down to San Luis Obispo for college. (Where there are fewer Sprint Stores to spam)
The Good news: If you're screen is turning on (using ANY method) you're Evo isn't bricked.
The Bad news: I don't know what you did. I would suggest trying the unroot method and seeing if you can get yourself out of this pickle that way. My first rooitng experience everything went horribly array, and I ended up just accepting an OTA to get out of it.
http://forum.xda-developers.com/showthread.php?t=884060
Pick which ever one you like and put it on the root of the sdcard. I couldnt tell you because if you didnt record what software you started with niether could I.
LaloHigh said:
http://forum.xda-developers.com/showthread.php?t=884060
Pick which ever one you like and put it on the root of the sdcard. I couldnt tell you because if you didnt record what software you started with niether could I.
Click to expand...
Click to collapse
What do you mean record what software I started with? I had 2.02, now have 0.76 (But my screen says 2.10). I've tried both the exe and the PC36IMG.zip that you've linked.
Using .exe gives me a Error 170 (Not recognizing my phone is plugged in)
Putting PC36IMG.zip on sd and using hboot gives me Failed-PU, Partition Update Fail! for every category but Radio_V2. BTW I'm supposed to use the first two files from that link
SUPERSONIC EVT1 ENG S-OFF
HBOOT-2.10.0001 (PC36*****)
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Mar 30 2010,11:24:04
Greenfieldan said:
The Good news: If you're screen is turning on (using ANY method) you're Evo isn't bricked.
The Bad news: I don't know what you did. I would suggest trying the unroot method and seeing if you can get yourself out of this pickle that way. My first rooitng experience everything went horribly array, and I ended up just accepting an OTA to get out of it.
Click to expand...
Click to collapse
Well what I did was messup the way it sees my partition. I have a nwer partition scheme i believe but the 0.76 software thinks I have the older partition settup.
If you mean unroot method from this post http://forum.xda-developers.com/showthread.php?t=829045 the one I rooted with then I can't do it cause I have no recovery. I can't get to it cause bad partition settup.
I know I can run fastboot erase commands, do you guys think I should run
Code:
fastboot erase boot
to create an unbootable system. One that doesn't even have the screen turn on?
*Which if any partition can I delete in order to never have the phone even turn the screen on?
Here's the choices (wimax, misc, recovery, boot, system, cache, userdata)
if your getting error 170, the RUU can't communicate with the phone.\
Can you get Hboot USb on? IF so, the RUU may run with it.
Drivers installed on computer?
Otherwise, you mave have blown out USB port, like I did.
Try putting the RUU, rom.zip (rename rom.zip to PC36IMG.zip) to your sd card, and see if that saves your a$$.
If that don't work, better run it over with a car or something and take it back.
The good news is you are still in your 30 day warranty. The solution I would suggest is try to flash the bootloader back to hboot 2.10. I would find a pc36 with 2.10 and flash away. Maybe even fastboot erase every partition except boot and hboot first. Don't do radio or wimax either or it will brick your radio and wimax. Then flash a full pc36. Other than that, manually brick. I would erase hboot and boot to brick.
Good luck
If you erase boot.img, it will still go to hboot. Erase the touchpanel image. That way they cant see it. By the time your phone gets to its repair destination, "they" wont be looking for that type of thing. They will just repartition. Also, it wont let you erase hboot
What error are you seeing when you select recovery from the bootloader menu?
The RUU that you tried, what version was it? You MUST use the 3.70.651.1 RUU because your phone thinks you are on hboot 2.10. Do not try an older RUU.
--------------------------------
Try the following
1) Download File PC36IMG_Recovery.zip and Rename to PC36IMG.zip.
copy to the root of your SDCard and power off phone
2) Power your phone back on into the boot loader by holding power and vol-down until your presented with a white screen. It will read the pc36img.zip and as you if you want to flash. Say yes. Then it will ask if you want to reboot, VOL+UP for yes.
3) If your rom gets tossed in the process. Reboot your phone into bootloader select recovery, and reflash your rom....DONE
4) Once in recovery, flash HBoot 2.10 zip
6) Now try RUU 3.70.651.1
-----------------------------------------------
If that does not work then try the following:
1) Download the img file for the modified Amon_Ra Recovery
2) Put evo-test.img on the root of your sdcard
3) Put the phone in fastboot mode
4) fastboot boot evo-test.img
5) Once in recovery, flash HBoot 2.10 zip
6) Now try RUU 3.70.651.1
Update
thanks to some help I have gotten farther on this issue. Can get past USB Erro 170. Now get to Error 171 when trying to flash image. When i run RUU.exe it tries flashes then reboots into stuck image of 3 androids skating. Which I alwasy need to battery pull to fix. Heres the log
ftp://eto.homeip.net/shared/RUU_101228T160722.log
__________________________________________
So how could I remove touchpanel img? thanks
josh4trunks said:
Update
thanks to some help I have gotten farther on this issue. Can get past USB Erro 170. Now get to Error 171 when trying to flash image. When i run RUU.exe it tries flashes then reboots into stuck image of 3 androids skating. Which I alwasy need to battery pull to fix. Heres the log
ftp://eto.homeip.net/shared/RUU_101228T160722.log
__________________________________________
So how could I remove touchpanel img? thanks
Click to expand...
Click to collapse
But if you can't flash a RUU.exe, then you can probably flash a zip file of a ROM.
This can or be or is not correct, I am just curious how this well happened to you.
nope tried flashing ROM through hboot, fastboot... Tried 'fastboot erase boot' didn't do anything. I'm gonna update the OP on the current situation, giving up...
Are you able to use the bootloader to flash only the custom recovery amon RA zip? If you can get into custom recovery you will be fine. Once in recovery you can flash hboot radio etc 1 at a time with a reboot in between each flash. After that you can flash a custom rom and be happy.
i think he said multiple times that he was totally screwed and his partitions were messed up so he either needs a total memory reflash or god's private java code
illogos said:
Are you able to use the bootloader to flash only the custom recovery amon RA zip? If you can get into custom recovery you will be fine. Once in recovery you can flash hboot radio etc 1 at a time with a reboot in between each flash. After that you can flash a custom rom and be happy.
Click to expand...
Click to collapse
Can't flash through bootloader. Get Fail-PU
Which is a Partition Update Error
PLEASE, HELP!!!
I HAD:
OXIGEN 2.1.6, AlphaRev Sense HBOOT S-OFF
after attempt to repair the speaker in service center of HTC, my Desire hangs on splash screen. (nothing was repaired, changed etc., but as far as I understand, they tried to flash something)
SO, NOW I HAVE:
Desire of the same phisical condition, but:
If normally to boot - I've seen only splash screen.
If to boot into bootloader - it's started, fastboot working, but option RECOVERY doesn't work - if to choose it, phone goes to reboot and hangs on splash screen again.
I tried to root the phone again, but step2 doesnt work, because "device not found" (although all the drivers are installed and are working normally)
After that 1st step of rooting, the normal boot goes directly to bootloader.
I tried to re-flash Recovery with fastboot-windows, but got the error:
FAILED (remote: siignature verify fail)
So, as far as I understand, phone not dead yet, but I can't call it alive as well.
PLEASE, help!
AndrewMe said:
PLEASE, HELP!!!
I HAD:
OXIGEN 2.1.6, AlphaRev Sense HBOOT S-OFF
after attempt to repair the speaker in service center of HTC, my Desire hangs on splash screen. (nothing was repaired, changed etc., but as far as I understand, they tried to flash something)
SO, NOW I HAVE:
Desire of the same phisical condition, but:
If normally to boot - I've seen only splash screen.
If to boot into bootloader - it's started, fastboot working, but option RECOVERY doesn't work - if to choose it, phone goes to reboot and hangs on splash screen again.
I tried to root the phone again, but step2 doesnt work, because "device not found" (although all the drivers are installed and are working normally)
After that 1st step of rooting, the normal boot goes directly to bootloader.
I tried to re-flash Recovery with fastboot-windows, but got the error:
FAILED (remote: siignature verify fail)
So, as far as I understand, phone not dead yet, but I can't call it alive as well.
PLEASE, help!
Click to expand...
Click to collapse
My guess is that they've tried to install stock ROM and it failed because I suspect you have custom hboot partitions.
The safest way would be to bring your phone to stock and then try re-rooting, custom Hboot and Rom.
Good luck !
AndrewMe said:
PLEASE, HELP!!!
I HAD:
OXIGEN 2.1.6, AlphaRev Sense HBOOT S-OFF
after attempt to repair the speaker in service center of HTC, my Desire hangs on splash screen. (nothing was repaired, changed etc., but as far as I understand, they tried to flash something)
SO, NOW I HAVE:
Desire of the same phisical condition, but:
If normally to boot - I've seen only splash screen.
If to boot into bootloader - it's started, fastboot working, but option RECOVERY doesn't work - if to choose it, phone goes to reboot and hangs on splash screen again.
I tried to root the phone again, but step2 doesnt work, because "device not found" (although all the drivers are installed and are working normally)
After that 1st step of rooting, the normal boot goes directly to bootloader.
I tried to re-flash Recovery with fastboot-windows, but got the error:
FAILED (remote: siignature verify fail)
So, as far as I understand, phone not dead yet, but I can't call it alive as well.
PLEASE, help!
Click to expand...
Click to collapse
Bring your phone back to stock rom:
1.) Create goldcard: http://android.modaco.com/content/software/308798/pc-application-goldcardtool/
2.) Put this in your desire
3.) Download latest stock ruu: RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe
4.) Boot your phone into fastboot mode and run exe on your computer
5.) If this does not work, extract pb99img from the ruu:
http://forum.xda-developers.com/showpost.php?p=9036922&postcount=2
6.) Put this on your goldcard and boot your desire into bootloader
7.) Follow the instructions
paul.c said:
My guess is that they've tried to install stock ROM and it failed because I suspect you have custom hboot partitions.
The safest way would be to bring your phone to stock and then try re-rooting, custom Hboot and Rom.
Good luck !
Click to expand...
Click to collapse
Thank you for reply, I tried it as well - device not found...
MatDrOiD said:
Bring your phone back to stock rom:
1.) Create goldcard: http://android.modaco.com/content/software/308798/pc-application-goldcardtool/
2.) Put this in your desire
3.) Download latest stock ruu: RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe
4.) Boot your phone into fastboot mode and run exe on your computer
5.) If this does not work, extract pb99img from the ruu:
http://forum.xda-developers.com/showpost.php?p=9036922&postcount=2
6.) Put this on your goldcard and boot your desire into bootloader
7.) Follow the instructions
Click to expand...
Click to collapse
Thanks for your reply, start to try the 2nd variant..
MatDrOiD said:
Bring your phone back to stock rom:
1.) Create goldcard: http://android.modaco.com/content/software/308798/pc-application-goldcardtool/
2.) Put this in your desire
3.) Download latest stock ruu: RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe
4.) Boot your phone into fastboot mode and run exe on your computer
5.) If this does not work, extract pb99img from the ruu:
http://forum.xda-developers.com/showpost.php?p=9036922&postcount=2
6.) Put this on your goldcard and boot your desire into bootloader
7.) Follow the instructions
Click to expand...
Click to collapse
It worked.. a bit by the other way - first placed stock hboot from AlphaRev's site, then booted into bootloader, then normal flashing of stock RUU went well.
Thanks once again!
It worked.. a bit by the other way - first placed stock hboot from AlphaRev's site, then booted into bootloader Can you explain please!! I am not as expert as you are...
it worked actually!! the phone's has been ROMed but I still have the same original problem!! it goes off by itself and the camera doesn't work??
Any Ideas??
HTC_DeSiRe_83 said:
it worked actually!! the phone's has been ROMed but I still have the same original problem!! it goes off by itself and the camera doesn't work??
Any Ideas??
Click to expand...
Click to collapse
Sounds like an hardware issue. You are back on stock ruu, so you can give htc a ring.
First of all, hello to all forum members!
I had not been particularly active here in the forum,
but I read a lot here and build some knowledge.
so far I have solved all my problems due to browse and read.
But now I am facing a problem, where I need help.
I got a desire from a friend with wrong nexus one blackrose hboot.
I managed to install alpharev hboot on it, but its not booting the rom, neither the recovery.
I decided to get a ruu on it, to reflash boot, system, recovery, etc.
After i did:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <rom.zip>
the phone is stuck in fastboot RUU mode. No matter if I pull the battery and power on with vol-, vol+ or back, the fastboot RUU mode starts (Black screen with htc logo in the middle and 4 exclamation marks in the corners).
What Ive done so far:
Tried different RUUs(Europe, WWE) via fastboot. Most of them fail while writing radio image.
Tried to flash the radio image via fastboot. Most of them stuck while writing.
Asked a friend with exactly matching hardware to send me his working nand backup, his hboot is CM7 r2, so I flashed it
to match his nand backup.
I flashed his boot/recovery/system/cache and the latest radio, matching the nand backup.
The latest radio was flashed successfully.
The recovery in his nand backup was 4EXT Touch 1.0.0.3
So, after flashing boot, recovery, system, cache and even misc and userdata (AND erasing them prior on second try), the behaviour stays the same, the phone wont boot the rom or recovery and no matter what buttons I press on power on, it boots at fastboot RUU mode.
I tried
Code:
fastboot oem boot
, but that keeps stucking in the white htc splash1
If I plug in the usb cable and pull it out again, I see the hboot infos:
AlphaRev CM7 r2
BRAVO PVT1 SHIP S-OFF
HBOOT-6.92.1002
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
<date>
RUU
After a lot of research, Ive found several opinions:
-its a brick (sure it is ;D)
-its a radio brick (ive sucessfully flashed the newest radio, so I doubt it)
Almost all users wo tried it hardly, and havent given up after the second try,
recovered their phone from this fastboot RUU mode.
I can run all fastboot extended commands, and flash RUUs over it.
So: what have I done wrong? Is there anything missing?
Can someone who knows what he says please take a look over it?
Thank you really much
criestr
After "a lot" of research you still haven't looked at my guide, well done.
Sure Ive looked at your guide,
I work with linux, and I hate flashing tools.
S-OFF
[STEP1]- download "Bravo Stock" from Alpharev
[STEP2]- download Android Flasher
[STEP3]- use android flasher to flash "Bravo Stock"
[STEP4]- run the RUU again and wait for it to finish
Click to expand...
Click to collapse
Is it any difference to use
Code:
fastboot flash hboot bravo_alphaspl.img
instead of using Android Flasher?
I dont think so, and Ive already done the steps in your guide, except using Android Flasher to flash the AlphaRev stock version.
Or is there another point in your guide that Im missing?
If so, then I am sorry for wasting your time.
I know, I am "new" here, so thats the standard answer for all newbs from you.
Thats ok. But Ive fixed a lot of phones without open even one thread, just with hours of research. But after google search for about 8 hours, several tries and following several guides and tips I didnt find an answer yet.
New update: Ive managed to push and boot the 4EXT Recovery image.
Fair enough, but the guide was meant to be made as easy to use as possible.
All you had to do was flash the stock hboot, or the downgrader, and then try a RUU.
The reason for it being stuck, is because alpharev hboots have write protection (meaning they won't be overwritten until you use the downgrader), and since you had the cm7r2 partition flashed, there was not enough space in /system for the stock ROM.
Hi again,
thanks for your answer.
I had the right stock hboot whilst flashing the RUU, so that wasnt the problem.
The RUU always failed to write the radio. A few hours ago i figured out that
the problem was because of a faulty battery. I changed the battery, loaded it
half an hour, and voila! the RUU was running quite fine.
The stock rom wasnt booting yet, but from then it was possible to go into the HBOOT/Fastboot, so it was making progress ;D
After another research I found out that my misc partition was screwed, maybe because the blackrose hboot, maybe because of the pre-owner.
Fixed the misc partition with cid, kernel commandlines & rom version.
After that I wiped cache and data, and did fastboot oem boot.
The rom was booting, but did random reboots/crashes after about 3-5 mins.
After 3 or 4 reboots the phone is now stuck at htc splash1, and isnt booting anymore.
For now I will try to flash the nand backup again, see if that works out.
Anyone has an better idea?
Thanks alot
criestr
New update:
The phone switched randomly between bootable and non-bootable bootloop/stuck in splash1.
I tried different radios, different boot & system.img from RUUs.
I can flash a new recovery, tried 4 different ones, none of them is booting,
not over hboot->recovery and also not over
Code:
fastboot oem gencheckpt
.
The only thing that worked was to erase cache and immediatly do
Code:
fastboot boot recovery.img
,
so after the stock rom randomly reboots, I decided to install a custom rom for CM7 r2 hboot. So I flashed the CM7 r2 hboot again, erased cache, booted the recovery and flashed rom.
The rom was booting! But again, after fiddling with flashing a new recovery with 4EXT Updater, the rom rebooted into splash1 and stuck there.
After this first time, it has yet never rebooted again. So I twist my fingers that it was a custom rom bug on first boot.
Flashing the recovery via 4EXT Updater worked for me, despite of none of the recoverys flashed via fastboot had booted before.
Anyway, thanks for the help.
Hopefully it helps someone with the same problem,
but I doubt there are many people dumb enough to flash blackrose hboot on a desire
Cheers
criestr
I had a similar problem with my old Magic. I have Desire now but never had that problem. I hope not.
Anyways, the way I solved it was to flash the right radio.img. I supposed you can try to fastboot flash radio radio.img. Make sure you use the right radio.img. That is what I did if I recall correctly and it worked for me on Magic. I don't know if it is will work on Desire that way.
The other thing is when Ruu failed at radio, I think it is because the lower version of radio.
I hope this helps.
Try it and let me know.
bortak said:
After "a lot" of research you still haven't looked at my guide, well done.
Click to expand...
Click to collapse
link please
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 downgraded my hboot to 0.97 in the hopes that I would be able to get S-OFF with revolutionary. I used tacoroot to gain root access, misctool to modify the misc_version so I can downgrade, and flashed the 2.3.3 Gingerbread RUU through hboot. Everything seemed fine so I went to use revolutionary to get S-OFF. After gaining root access my device was rebooted into fastboot where i got an error and revolutionary terminated. Now my phone gets stuck in boot loop. It gets to slide to unlock screen, but reboots seconds later. A factory reset temporarily solves the boot loop problem and the phone doesn't automatically reboot, but once I power down or reboot the phone the boot loop problem returns.
While looking through the forums I noticed that in several threads about boot loops members suggested updating the radio. So I tried flashing the .0312 radio. First I tried through hboot. It checks the zip like normal, but never provides me with the option to install or not. Next I tried through fastboot, but I get this: sending 'radio' <13225 KB>... FAILED <command write failed <Unknown error>>
I'm not sure if I'm doing something wrong or not. If it is indeed the radio that is the issue what am I doing wrong and if it's not does anyone have any ideas as to what wrong and how I can go about fixing it? Any and all help is greatly appreciated. Thanks.
kioji86 said:
I downgraded my hboot to 0.97 in the hopes that I would be able to get S-OFF with revolutionary. I used tacoroot to gain root access, misctool to modify the misc_version so I can downgrade, and flashed the 2.3.3 Gingerbread RUU through hboot. Everything seemed fine so I went to use revolutionary to get S-OFF. After gaining root access my device was rebooted into fastboot where i got an error and revolutionary terminated. Now my phone gets stuck in boot loop. It gets to slide to unlock screen, but reboots seconds later. A factory reset temporarily solves the boot loop problem and the phone doesn't automatically reboot, but once I power down or reboot the phone the boot loop problem returns.
While looking through the forums I noticed that in several threads about boot loops members suggested updating the radio. So I tried flashing the .0312 radio. First I tried through hboot. It checks the zip like normal, but never provides me with the option to install or not. Next I tried through fastboot, but I get this: sending 'radio' <13225 KB>... FAILED <command write failed <Unknown error>>
I'm not sure if I'm doing something wrong or not. If it is indeed the radio that is the issue what am I doing wrong and if it's not does anyone have any ideas as to what wrong and how I can go about fixing it? Any and all help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
try typing this (in fastboot menu)
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip (name of zip)
kioji86 said:
I downgraded my hboot to 0.97 in the hopes that I would be able to get S-OFF with revolutionary. I used tacoroot to gain root access, misctool to modify the misc_version so I can downgrade, and flashed the 2.3.3 Gingerbread RUU through hboot. Everything seemed fine so I went to use revolutionary to get S-OFF. After gaining root access my device was rebooted into fastboot where i got an error and revolutionary terminated. Now my phone gets stuck in boot loop. It gets to slide to unlock screen, but reboots seconds later. A factory reset temporarily solves the boot loop problem and the phone doesn't automatically reboot, but once I power down or reboot the phone the boot loop problem returns.
While looking through the forums I noticed that in several threads about boot loops members suggested updating the radio. So I tried flashing the .0312 radio. First I tried through hboot. It checks the zip like normal, but never provides me with the option to install or not. Next I tried through fastboot, but I get this: sending 'radio' <13225 KB>... FAILED <command write failed <Unknown error>>
I'm not sure if I'm doing something wrong or not. If it is indeed the radio that is the issue what am I doing wrong and if it's not does anyone have any ideas as to what wrong and how I can go about fixing it? Any and all help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
Did you check the md5 for the radio? Did you rename it to EXACTLY PG32IMG.ZIP? if using windows, make sure there's no extra .zip at the end. What did hboot say when it "checked" the file?
Give me some more info. We'll get you going.
Sent from my vivow using xda app-developers app
having the same issue
Ok so I'm a complete noob at this. I ran everything and it seemed fine up until i went to run revolutionary. Rev kept waiting for the device I let it sit for ten minutes. then I had the bright idea to program my phone with my number, thinking that might help. it then rebooted and started bootlooping. It's been constantly looping since. Please help.
*similar* issue
kioji86 said:
I downgraded my hboot to 0.97 in the hopes that I would be able to get S-OFF with revolutionary. I used tacoroot to gain root access, misctool to modify the misc_version so I can downgrade, and flashed the 2.3.3 Gingerbread RUU through hboot. Everything seemed fine so I went to use revolutionary to get S-OFF. After gaining root access my device was rebooted into fastboot where i got an error and revolutionary terminated. Now my phone gets stuck in boot loop. It gets to slide to unlock screen, but reboots seconds later. A factory reset temporarily solves the boot loop problem and the phone doesn't automatically reboot, but once I power down or reboot the phone the boot loop problem returns.
While looking through the forums I noticed that in several threads about boot loops members suggested updating the radio. So I tried flashing the .0312 radio. First I tried through hboot. It checks the zip like normal, but never provides me with the option to install or not. Next I tried through fastboot, but I get this: sending 'radio' <13225 KB>... FAILED <command write failed <Unknown error>>
I'm not sure if I'm doing something wrong or not. If it is indeed the radio that is the issue what am I doing wrong and if it's not does anyone have any ideas as to what wrong and how I can go about fixing it? Any and all help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
I downgraded to 2.3.3 using the tacoroot method. Everything was acting fine after the reboot and I was about to run Revolutionary, but I got a bright idea to confirm I had gained a .97hboot so I shut the phone off and went into the bootloader screen. Yup I have .97hboot. Restarted phone. Boots normally but as others mention it restarts its self after a couple seconds on the lock screen. Hoping this isn't a permanent brick.
zombolt said:
Hoping this isn't a permanent brick.
Click to expand...
Click to collapse
Doubtful that it's bricked. Have you tried flashing a custom rom?
Sent from my Incredible 2 using xda app-developers app