Related
Hi.
I have a rooted s-off desire using alpha rev 1.8.
I'm currently trying to resize the nand partitions using the method on the alpharev.nl site, without a pc. I'm running cm6.1 rom, so I downloaded the n1table zip ready to flash. Its renamed to pb99img.zip on root of sdcard. I've reboot into hboot using volume+down and I'm not quite sure where to go from here. I tried going into recovery and installing zip from SD but it doesnt seem to have worked as when I reboot into rom and check SD storage, it remains the same as before.
I know I must be missing something basic. Anyone know what I'm doing wrong? Cheers.
Sent from my HTC Desire using XDA App
Do NOT continue with what you're doing. Have you even read the instructions on the AlphaRev site? You flash a new MTD table using the fastboot commands of adb:
1) Nandroid backup in recovery.
2) Verify the MD5SUM of the file you downloaded against the one in the table.
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl.img' (change into the correct filename for the HBOOT you downloaded)
4) 'Fastboot reboot-bootloader'
5) 'Fastboot erase cache'
6) Boot recovery, wipe everything and restore
It´s also working with HBOOT...but I think you have to rename it to PB99IMG.zip (case Sensitiv)
If you have it in your / Filesystem on your SD Card, you will be asked after booting to Bootloader if you want to update.
Answer with "Volume up" or "down"
YOU DO NOT RENAME AN ALPHAREV HBOOT MOD TO PB99IMG
That is for Zip versions of the RUUs and NOTHING to do with AlphaRev
Seriously, read up before you brick your phone
From the Aplha Rev HP:
You can also download the corresponding PB99IMG zipfile, put it on your sdcard, and rename it to PB99IMG.zip. Then start the phone in HBOOT mode (VolDown+POWER) to flash the HBOOT without a PC.
Sorry, if I don´t understand this right...but that´s a fact from his Page
I´m sure Fastboot is the better way...but I tried it like this and it worked
I stand corrected, didn't see they had that option now. My apologies
In which case, you'd download the relevent ZIP file, rename it PB99IMG.zip (not PB99IMG.zip.zip) and put it on the root of our SD card (root - not in any folders)
Then, when you boot into HBOOT it should just pick it up and ask if you want to flash it - you don't go into recovery
no Probs
I never got asked if i wanted to flash the hBOOT
I'm running a rooted HTC desire and i'm trying to load flash the hboot to the oxygen variety
I haven't s-off my phone yet but wanted to use the no PC method outlined above
When i go into hBoot the phone picks up the PB99IMG.zip (saying "checking PB99IMG.zip......") but doen't give me the option to flash the hboot
Am i missing something? Do i have to s-off it the long way first?
Any help would be really appreciated
=]
Yes, you have to S-OFF first before you can change the MTD. It does say on the website:
"If you are already S-OFF, you can get our newest patched HBOOTs from here. (without going through the entire procedure again).
Please read the entire table and pick the partition table with the correct sizes for your ROM. One easy way to switch partition tables, is to nandroid backup,
and verify that the sizes of your backup are indeed the ones listed in the table (or smaller), and restore after flashing hboot."
Any idea if i can choose the Oxygen variation when i use the AlphaRev 1.8 HBOOT reflash utility or will i need to do it again with a PB99IMG.zip after?
the.draconian said:
Any idea if i can choose the Oxygen variation when i use the AlphaRev 1.8 HBOOT reflash utility or will i need to do it again with a PB99IMG.zip after?
Click to expand...
Click to collapse
Do the Alpharev 1.8 Flash first.
Then connect your phone, boot into Fastboot mode, and run the foll:
1) Nandroid backup in recovery.
2) Verify the MD5SUM of the file you downloaded against the one in the table.
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl.img' (change into the correct filename for the HBOOT you downloaded)
4) 'Fastboot reboot-bootloader'
5) 'Fastboot erase cache'
6) Boot recovery, wipe everything and restore.
Click to expand...
Click to collapse
Again a quote from their site
Edit: Alpharev seems to have taken down the Pb99img method
EddyOS said:
Do NOT continue with what you're doing. Have you even read the instructions on the AlphaRev site? You flash a new MTD table using the fastboot commands of adb:
1) Nandroid backup in recovery.
2) Verify the MD5SUM of the file you downloaded against the one in the table.
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl.img' (change into the correct filename for the HBOOT you downloaded)
4) 'Fastboot reboot-bootloader'
5) 'Fastboot erase cache'
6) Boot recovery, wipe everything and restore
Click to expand...
Click to collapse
Of course I have read the instructions thoroughly. I would never do anything without reading several times over. As another member pointed out, you can in fact flash from .zip
However it would not work for me, probably a lot of others too, as another member mentioned it has been removed from site.
I have now switched to miui and am not encountering any storage space issues as yet, so I think ill leave it alone for awhile. Thanks for everyone's input and help.
Cheers.
Sent from my HTC Desire using XDA App
Anyone got this to work? Ive tried following the instructions (I have s-off and have repartitioned my HBOOT previously with ADB) and it just says no image found when I load into fastboot
When I try to do it from the SD card on mine, it finds the PB99IMG.zip file but then says "Model ID invalid. Update Fail!" then asks if I want to reboot or not. Rebooting just performs a normal reboot with no changes.
jordan.harris01 said:
When I try to do it from the SD card on mine, it finds the PB99IMG.zip file but then says "Model ID invalid. Update Fail!" then asks if I want to reboot or not. Rebooting just performs a normal reboot with no changes.
Click to expand...
Click to collapse
Obviously, you're trying to install a file meant for another device! That's a very dangerous thing to do!
It's the PB99IMG.zip for the Oxygen HBOOT. How can it be for the wrong device? I'm s-off, running Oxygen RC7.
jordan.harris01 said:
It's the PB99IMG.zip for the Oxygen HBOOT. How can it be for the wrong device? I'm s-off, running Oxygen RC7.
Click to expand...
Click to collapse
At least that's what the error code means anyway..Is there a reason why you cant fastboot flash the img?
Yea, I assumed that. I can't seem to get fastboot working again on my machine. It was working but I haven't had much time to look into what happened. ADB devices brings up the serial number but fastboot won't detect the phone. I was just trying to do this while I was at work and I don't have access to fastboot here.
jordan.harris01 said:
Yea, I assumed that. I can't seem to get fastboot working again on my machine. It was working but I haven't had much time to look into what happened. ADB devices brings up the serial number but fastboot won't detect the phone. I was just trying to do this while I was at work and I don't have access to fastboot here.
Click to expand...
Click to collapse
Adb and fastboot detect the phone at different phases. If one detects, at that point, the other wouldnt.
Are u sure you're trying out fastboot in fastboot mode (poweroff, Back key+Power On)? At that point fastboot should work..Even most severely damaged phones are detected in fastboot
Yes, the phone is in fastboot when I'm trying this. I'm wondering if something happened to the fastboot driver or something. Either way, I'll look into it at some point.
Hello everyone,
I think this might be my first post here.
Anyways, I have a rather depressing problem. I have my phone rooted running cm 6.1, and when i was about to go to sleep last night, it randomly started to reboot. At first i did not think anything of it because i have had my phone do this several times with cm. But then i became more concerned, it would go into a boot loop at the splash screen (htcEVO4g). Once again, i have had this happen before and i would do a wipe and reinstall the rom, but this time it did not work. I could not get into recovery. I am able to access only the boot loader.
So, i tried to install the stock pc36img. Now when i start my phone, it vibrates 5 times followed by the flashing green led. it also does this when i try to go into recovery. I am still able to get into the bootloader.
i tried doing the ruu thing, and different pc36img
I just got back from the sprint store. After waiting 3 hours, they were not able to fix it. I had told them it was rooted and everything.
If there is no way to fix it, is there at least a way i can turn s-on? That way, i can send it back to sprint.
That is odd. As far as I know, if you used unrevoked forever at any point, the only way to get s on is to flash the unrevoked s on tool, using recovery. But you don't have recovery. If I were you, I would use your computer to format your sd card to fat 32 ( after backing it up, of course) , then put a pc36img on your sd card, and try to flash again using the bootloader. You could also try putting a pc36img of amon ra recovery on your sd card, and flashing that with the bootloader. Maybe you can get recovery back, and flash a rom, or the s on tool. Hope you get it worked out.
Sent from my PC36100 using XDA App
If I were you I would try the newest pc36img.zip and if that does nothing a pc36img.zip of Amon ra. If that doesn't work go to the last link in my sig about splash screens. In that tut I give, I say how to manually run an ruu. Use the pc36img.zip with the fast boot commands from the thread. Hope this helps.
i tried formatting the sc card, and that did not do anything. How can i connect my phone to adb?
marzban123 said:
i tried formatting the sc card, and that did not do anything. How can i connect my phone to adb?
Click to expand...
Click to collapse
Just Download the android SDK and follow the steps. There are some pretty excellent tutorials on XDA and other sites that will walk you through the whole process.
I want to weigh in here for just a moment. There is no way your phone is completely botched, unless it has experienced physical damage (including any overheating). By the way, you running any SBC kernels?
I would look into learning your way around ADB, I think it's a necessary tool for anyone who wants to flash and alter their android phones, unfortunately things have become so easy that many out there haven't had to learn these tools and how to use them.
Seriously, go mess with ADB, I am sure you can get it running again.
Some good info here http://forum.xda-developers.com/showthread.php?t=865204 on using ADB and other methods that may help you.
marzban123 said:
I had told them it was rooted and everything.
Click to expand...
Click to collapse
ouch... they should give you new phone for being honest
ok, so i connect the phone, and in device manager i see "Android Bootloader Interface"
i opened up command prompt, and tried to push a file to the phone and i got this
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Andrew>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb push PC36IMG.zip /sdcard/
error: device not found
C:\android-sdk-windows\tools>
you sure your usb cable is good? id run the RUU to go back to stock & unroot you. then start over from scratch.
i just tried a different cable. No luck
I have already tried a stock ruu, that still does not let me get into recovery or turn s-on
your sorta up ****s creek here if you told sprint you rooted. they probably flagged your account.
is your sd card good? try another, fully formatted for fat32 only. then try the s-on flashable zip. that's all i can think of for you to do. if you need another evo, im sure you can pick one up for cheap on craigslist.
nobody ever took my information
Is there an s-on flashable zip?!?! where can i find it? i have searched before with no luck
first of all, adb doesnt work in bootlaoder. select fastboot, then plug in. you should see fastboot usb come up on the phone. now try using fastboot commands instead. not sure where to download fastboot commands. i have the mac ones if you need them. then do this
with the pc36img.zip ON YOUR COMPUTER:
after flashing s-on tool http://downloads.unrevoked.com/forever/current/unrevoked-forever-son.zip
fastboot oem rebootRUU
you should see a black screen with silver htc lettering
fastboot flash zip pc36img.zip (do this command with the pc36img.zip in the same directory as fastboot)
you should see a green bar appear under htc and a bunch of lines on the comp. make sure it successfully completes, then type:
fastboot reboot
done.
but make triple sure you are s-on first.
thank you very much, that makes things ALOT clearer.
I am still a huge noob to this stuff so i need to ask you some silly questions:
i found out the commands for fastboot in a wiki,
http://wiki.cyanogenmod.com/index.php?title=Fastboot
but i dont really understand how to use them. can someone please give me a little clarification.
well, first check your sdk and see if you have fastboot.exe. i know the mac one doesnt come with it. if you dont google it. if you do, cd to the directory (hold shift and right click in the folder. select open command prompt here) and boot phone into fastboot. make sure it is in fastboot usb mode. then do the commands.
i have the fast boot exe and i am in command prompt.
when i say i am a noob, i really mean it.
for example, when i try a simple command like checking the serial number, i will input
c:\android-sdk-windows\tools>fastboot <-s>
or
c:\android-sdk-windows\tools>fastboot -s
or
c:\android-sdk-windows\tools>fastboot <serial number>
it says
the syntax of the command is incorrect.
i really dont know how to use this stuff
ok forget the last post,
i figured that out
what partition do i want to flash and with what file?
No partition just use the pc36img.zip in ruin more and type fastboot flash zip pc36img.zip.
Sent from my PC36100
C:\android-sdk-windows\tools>fastboot flash zip PC36IMG.zip
sending 'zip' (171727 KB)... OKAY [ 30.475s]
writing 'zip'... FAILED (remote: not allowed)
finished. total time: 30.477s
C:\android-sdk-windows\tools>
Click to expand...
Click to collapse
i researched the "(remote: not allowed)" error message, and everyone says its cause when the phone is set to s-on. However, on my phone it says s-off.
what the heck?
I have an Incredible that has Cyanogenmod 7 on it. A couple weeks ago it stopped working in that it would just reboot after the white HTC incredible screen. I can get it to go to Hboot, but if I try to go into Recovery it just reboots immediately.
I flashed a new Hboot successfully, but once it reboots I get stuck in the loop again.
Both Clear Storage and Factory Reset start the boot loop as well.
Anyone have an idea of what I can do or does this sound like a hardware issue? My computer recognizes it, but I'm not sure what good that does me since I can't get it to boot or go into Recovery.
Here's the info from Hboot in case it's helps
Code:
INCREDIBLEC XC SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL24_16ab
RADIO-2.15.00.07.28
Jul 23 2010, 18:06:51
GreyhoundX said:
I have an Incredible that has Cyanogenmod 7 on it. A couple weeks ago it stopped working in that it would just reboot after the white HTC incredible screen. I can get it to go to Hboot, but if I try to go into Recovery it just reboots immediately.
I flashed a new Hboot successfully, but once it reboots I get stuck in the loop again.
Both Clear Storage and Factory Reset start the boot loop as well.
Anyone have an idea of what I can do or does this sound like a hardware issue? My computer recognizes it, but I'm not sure what good that does me since I can't get it to boot or go into Recovery.
Here's the info from Hboot in case it's helps
Code:
INCREDIBLEC XC SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL24_16ab
RADIO-2.15.00.07.28
Jul 23 2010, 18:06:51
Click to expand...
Click to collapse
I would flash an ruu thru hboot and then do a factory rest from hboot. Then if it boots fine flash cwm recovery thru hboot and then the su binaty thru recovery to regain root. Once you have recovery working again then flash back to cm7 or another rom of your choice thru recovery.
Or you could try to just reflash cwm recovery thru hboot, and then if you can access recovery wipe everything in mounts and storage except sdcard and emmc, and then restore a nandroid or flash a new rom.
RUU's - http://pvillecomp.com/?page_id=22
Latest cwm recovery - http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
Latest su binary - http://dinc.does-it.net/SuperUser/SuperUser_3.0.7.zip
How to flash with hboot - http://pvillecomp.com/?page_id=79
You may also want to upgrade to the newest radio 2.15.10.07.07 - http://pvillecomp.com/?page_id=18
I flashed the PB31IMG from here (wasn't the newest): http://pvillecomp.com/?page_id=22
The flash seemed to work, but once it rebooted it went into the loop again. All the options in Hboot just throw it into the same white-screen loop, including Factory Reset and Recovery.
The only thing I see different in Hboot is my radio is now 2.15.10.07.07
GreyhoundX said:
I flashed the PB31IMG from here (wasn't the newest): http://pvillecomp.com/?page_id=22
The flash seemed to work, but once it rebooted it went into the loop again. All the options in Hboot just throw it into the same white-screen loop, including Factory Reset and Recovery.
The only thing I see different in Hboot is my radio is now 2.15.10.07.07
Click to expand...
Click to collapse
Try flashing the recovery and then see if you can access it.
If you have adb setup and have fastboot, you can try to erase the recovery partition by typing " fastboot erase recovery " without quotes into a cmd prompt on your pc. And then flash the recovery from above. Sounds like something is either messed up with your boot or recovery partition or img.
You can also try to use fastboot to erase the boot partition " fastboot erase boot " and then try an ruu again.
I tried both Clockwork 5 and Stock HTC from here: http://pvillecomp.com/?page_id=28
They both boot-looped after flashing.
When I try to go into Recovery now, I get the white screen then a quick flash of a phone image with a red triangle on top.
GreyhoundX said:
I tried both Clockwork 5 and Stock HTC from here: http://pvillecomp.com/?page_id=28
They both boot-looped after flashing.
When I try to go into Recovery now, I get the white screen then a quick flash of a phone image with a red triangle on top.
Click to expand...
Click to collapse
That red triangle is the stock recovery, try to do a factory reset now or try the sugestions i added to the post above.
Factory reset doesn't work. It shows me a phone with a green circle then goes into the boot loop.
I'll try the ADB stuff later today when I'm back from work. I've never used it before. Thanks so much for helping.
How do I connect to the phone via ADB when it's in Hboot? I just get "error: device not found" Every tutorial I found requires the phone to be booted to use ADB.
GreyhoundX said:
How do I connect to the phone via ADB when it's in Hboot? I just get "error: device not found" Every tutorial I found requires the phone to be booted to use ADB.
Click to expand...
Click to collapse
Adb will not work in hboot but fastboot will. You can use adb in recovery though, not just booted to the os. The error device not found is probably because you were trying adb from hboot, or because you dont have the correct drivers on your pc. Adb and fastboot are 2 different programs, fastboot is not an adb command. If you need the fastboot.exe file or the drivers you can get them here. http://dinc.does-it.net/ADB/ADB-Fastboot-USB-Drivers_v4_(x86)(x64).zip
I ran "fastboot erase boot" and it said "erasing 'boot'...FAILED (remote: not allowed)". Can I try running or flashing something else?
If I run "fastboot devices" it shows my device ID with fastboot next to it so I know it's connecting.
Thanks for putting up with this, can't imagine what caused this.
Hmm not sure, seems it may be some sort of hardware issue or disk failure. If you cant get it to boot after an ruu, and you cant factory reset or access a custom recovery or get fastboot to erase or flash, im not sure what else you could do. My only other sugestion would be to try the ruu.exe that you do from your pc with the phone connected. Flash the stock recovery PB31IMG.zip first before doing so as i believe its required for the ruu.exe. It may work and it may not im not exactly sure how the ruu.exe works as i have never used one, but i believe you just boot into hboot and then run the exe on your pc.
I haven't flashed through Fastboot because I don't know how. I tried flashing a few of the stock images, but I get errors everytime like "whoops: didn't find expected signature" or "archive does not contain android-info.txt".
Is there something I'm doing wrong?
GreyhoundX said:
I haven't flashed through Fastboot because I don't know how. I tried flashing a few of the stock images, but I get errors everytime like "whoops: didn't find expected signature" or "archive does not contain android-info.txt".
Is there something I'm doing wrong?
Click to expand...
Click to collapse
Take a PB31IMG.zip ruu ( http://pvillecomp.com/?page_id=22 ) and rename it update.zip
Put the update.zip file on your pc in the same folder as the fastboot.exe file. (Where adb is installed)
Boot into hboot with the phone pluged in to the pc. Make sure it says fastboot in red at the top of the hboot screen.
Open a cmd prompt to the directory where fastboot.exe is (eg C:\ADB\)
Type without quotes " fastboot update update.zip " and hit enter.
Here is some good info on fastboot.
http://wiki.cyanogenmod.com/wiki/Fastboot
Should I be able to open the zip on my computer? All the ones I download from that site are invalid according to Windows. This is the one I tried (3rd link on that page): http://pvillecomp.com/wp/wp-content/uploads/Images/Gingerbread-Stock_PB31IMG.zip
I did exactly what you said and got a similar result to before.
Code:
C:\adb>fastboot update update.zip
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in 'ö╓°ÑAa.òo♥Gûl╔←☺☼‼6«T▀ésαu*z¿♥M╦▌‼A←4,<Lσ╡≥↕ ªº─ ΦSÉ╢t↕←Θ■√╣F'
GreyhoundX said:
Should I be able to open the zip on my computer? All the ones I download from that site are invalid according to Windows. This is the one I tried (3rd link on that page): http://pvillecomp.com/wp/wp-content/uploads/Images/Gingerbread-Stock_PB31IMG.zip
I did exactly what you said and got a similar result to before.
Code:
C:\adb>fastboot update update.zip
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in 'ö╓°ÑAa.òo♥Gûl╔←☺☼‼6«T▀ésαu*z¿♥M╦▌‼A←4,<Lσ╡≥↕ ªº─ ΦSÉ╢t↕←Θ■√╣F'
Click to expand...
Click to collapse
Use 7-zip, winzip and winrar dont work the best for android files.
Think I'm just going to give up on this one since the flashing doesn't work...what a hassle. I wish there was some diagnostics tool that would just tell me if the phone is physically broken.
Help. My phone is stuck in a boot loop. No recovery, won't take one even when I flash multiple ways. Won't take a rom. S-off. Was rooted with Revolutionary, but since it wouldn't take a ROM or recovery I tried to unroot. Was able to remove the "Revolutionary" watermark, change hboot from 6.16 to 2.16.0001. Tried installing ruu which is what removed the Revolutionary and changed back hboot.
Here's what I have now:
Supersonic evt2-3 ship s-off
hboot 2.16.0001
Radio 2.15.00.0808
Any help! Thanks.
Looks you might have to get a PC36IMG.zip on your sdcard and then flash that through bootloader
Ideally, put on a froyo PC36IMG so that rerooting is easier if you want to do it again
So what happens when you try to select Recovery from Hboot?
The advice is free....the bandwidth, not so much
Still boot looping...
CNexus said:
Looks you might have to get a PC36IMG.zip on your sdcard and then flash that through bootloader
Ideally, put on a froyo PC36IMG so that rerooting is easier if you want to do it again
Click to expand...
Click to collapse
Already tried that...
FinZ28 said:
So what happens when you try to select Recovery from Hboot?
The advice is free....the bandwidth, not so much
Click to expand...
Click to collapse
All I get is the white "HTC EVO 4G" boot screen. When I flash a custom recovery, everything goes as expected, but still can't access recovery.
You will have to go through all the bootloader ruu's till you find the one that works. Good luck I had the same issue and ended up selling it on eBay and the buyer finally got it working.
Sent from my PC36100 using xda app-developers app
jlmancuso said:
You will have to go through all the bootloader ruu's till you find the one that works. Good luck I had the same issue and ended up selling it on eBay and the buyer finally got it working.
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
Ok. I tried every ruu I could find. Problem remains. Also, s-off never turns to s-on. Tried flashing contents of stock rom separately. Everything appears to flash ok, but same result: no recovery, no rom. Any ideas?
What I think I need is a method to nand unlock via fastboot or hboot. Anyone know of such a thing? Anyone have any other ideas? Besides what I've already done? Thanks...
mabulok said:
What I think I need is a method to nand unlock via fastboot or hboot. Anyone know of such a thing? Anyone have any other ideas? Besides what I've already done? Thanks...
Click to expand...
Click to collapse
S-off is nand-unlocked...run an ruu (any version), as soon as it opens, press windowsKey+R and type "%temp%" then *enter
Now sort the files by date modified and search in the most recent folders for a file called "rom.zip", as soon as you find that copy it to your desktop
Rename the rom.zip to "PC36IMG.zip" and place it on the root of your phones sdcard (you may need to reformat your sdcard to FAT32, make a backup if you need to do this)
Now put the sdcard in your phone, pull out the battery and go into bootloader (VolDown+Power) , the bootloader should find it and commence the update process back to stock unrooted, follow the prompts and press power when necessary
Okay, tried that...
CNexus said:
S-off is nand-unlocked...run an ruu (any version), as soon as it opens, press windowsKey+R and type "%temp%" then *enter
Now sort the files by date modified and search in the most recent folders for a file called "rom.zip", as soon as you find that copy it to your desktop
Rename the rom.zip to "PC36IMG.zip" and place it on the root of your phones sdcard (you may need to reformat your sdcard to FAT32, make a backup if you need to do this)
Now put the sdcard in your phone, pull out the battery and go into bootloader (VolDown+Power) , the bootloader should find it and commence the update process back to stock unrooted, follow the prompts and press power when necessary
Click to expand...
Click to collapse
Tried your method using the rom from an ruu. Still s-off, although everything appeared to have updated. I've done this previously, but not extracting the rom.zip from an ruu. Each time the hboot updates, or downgrades, depending on the ruu, but s-off remains. No rom, no recovery...
Next...
Sometimes the problem is solved by wiping the recovery partition first, and then re-flashing it. To do that, you would need a Hboot where you could run fastboot commands, since you cannot boot into a Rom.
You can try upgrading your Hboot, then unlocking the bootloader using the Htcdev site, so that you can run the fastboot commands. If it fails on the new Hboot, then it can probably be flashed back to whatever Hboot you have, since you're S-OFF.
I've included the Hboot file that you would need for the upgrade. You would first run the PC36IMG file throught the bootloader, then reboot the phone. If the Hboot changes, then you should go to the Htcdev site and try to unlock the bootloader.
There are some other steps that follows, but there's no point of giving them to you now and complicating things unless the initial steps work first.
Update
shortydoggg said:
Sometimes the problem is solved by wiping the recovery partition first, and then re-flashing it. To do that, you would need a Hboot where you could run fastboot commands, since you cannot boot into a Rom.
You can try upgrading your Hboot, then unlocking the bootloader using the Htcdev site, so that you can run the fastboot commands. If it fails on the new Hboot, then it can probably be flashed back to whatever Hboot you have, since you're S-OFF.
I've included the Hboot file that you would need for the upgrade. You would first run the PC36IMG file throught the bootloader, then reboot the phone. If the Hboot changes, then you should go to the Htcdev site and try to unlock the bootloader.
There are some other steps that follows, but there's no point of giving them to you now and complicating things unless the initial steps work first.
Click to expand...
Click to collapse
Ok. This didn't work. I was able to flash the hboot, but fastboot commands did not work. I can unlock, and relock the bootloader, flash any ruu, but s-off remains, and still unable to flash a rom or recovery.
Try this and see what happens: Unzip the fastboot.zip file in side a folder on your computer and place the recovery.img file in that same folder on your computer, then open a command prompt from that folder (shift + right click+"open command window here"). From the FASTBOOT USB menu on the phone (Hboot + click on FASTBOOT): type
fastboot erase recovery <ENTER>
fastboot flash recovery recovery.img <ENTER>
fastboot reboot-bootloader <ENTER>
shortydoggg said:
Try this and see what happens: Unzip the fastboot.zip file in side a folder on your computer and place the recovery.img file in that same folder on your computer, then open a command prompt from that folder (shift + right click+"open command window here"). From the FASTBOOT USB menu on the phone (Hboot + click on FASTBOOT): type
fastboot erase recovery <ENTER>
fastboot flash recovery recovery.img <ENTER>
fastboot reboot-bootloader <ENTER>
Click to expand...
Click to collapse
That didn't work either...
Well after about 20+ hours spent looking online and tinkering with my phone I have arrived at this point. I have been trying to install a custom rom with no success. I have rooted and S-OFF my phone with revolutionary. I have installed 4ext recovery. I have been trying to install the cm 10.1 rom and/or the paranoidandroid rom. No success on either one, I always got the status 7 error. After looking online I found that status 7 relates to the wrong HBOOT, so I flashed the the stock HBOOT from alpharev.nl and now my phone's screen won't turn on for any mode(normal boot, hboot, fastboot) it's just a black screen. The phone does "turn on" because my pc can see that it's there and it vibrates. I can also send fastboot commands to the phone.
Does anyone know of this problem and how to fix it? I've tried to flash different HBOOTS and ROMS and Recovery but with no success, it always says "out of memory" or a different error. Also I tired doing SUU but it always says I have the wrong model phone.
I just tried fastboot flash hboot bravo_downgrade.img(from alpharev.nl)
fastboot reboot-bootloader
fastboot erase cache
then I ran RUU from shipped-roms.com it was the HTC_Desire_Android_2.3_Upgrade.exe
gives me "error 130 model id error"
Anyone?
cree125 said:
I just tried fastboot flash hboot bravo_downgrade.img(from alpharev.nl)
fastboot reboot-bootloader
fastboot erase cache
then I ran RUU from shipped-roms.com it was the HTC_Desire_Android_2.3_Upgrade.exe
gives me "error 130 model id error"
Click to expand...
Click to collapse
the downgrader isn't actually an hboot, it's just a way of 'unlocking' an hboot like cm7r2 which can't be overwritten by RUU.
flash the stock hboot again, then run the 2.3.3 RUU.
I repeated the same process as in the previous post except replacing the downgrader with the stock boot and received the error. The RUU starts to work and the progress bar at the top says "sending" but then just stops and gives the error. I am not very knowledgeable about android OS so basically I am out of ideas at this point.
cree125 said:
I repeated the same process as in the previous post except replacing the downgrader with the stock boot and received the error. The RUU starts to work and the progress bar at the top says "sending" but then just stops and gives the error. I am not very knowledgeable about android OS so basically I am out of ideas at this point.
Click to expand...
Click to collapse
Can you boot into bootloader and confirm what it says on the top line please?
Have you tried the 2.3.3 RUU by PB99IMG.zip method?
Try bortak's troubleshooting guide, step 7, ignore the bit about goldcard for now. You basically need to extract the rom from your RUU, rename it to PB99IMG.zip, and put it on the root of your sd card to run from bootloader.
eddiehk6 said:
Can you boot into bootloader and confirm what it says on the top line please?
Have you tried the 2.3.3 RUU by PB99IMG.zip method?
Try bortak's troubleshooting guide, step 7, ignore the bit about goldcard for now. You basically need to extract the rom from your RUU, rename it to PB99IMG.zip, and put it on the root of your sd card to run from bootloader.
Click to expand...
Click to collapse
Sorry I have been really busy with work! Hopefully I can try this with in the next couple days, thanks a lot for the advice!