I was on 4.0.3 and I flashed the zip through AromRa recovery.
Now, when booting up, its stuck at the 4G screen.
The update was the OTA update released to update radios to Global. THIS
It didn't gave any error at all, it said "Reboot to complete installation or update". But when I clicked the reboot option, I saw a line saying something like "Can't write....." then the screen went off and it rebooted. This line was not there, or atleast not visible before I clicked the reboot option.
I am new to rezound and android, so please let me know what I can do. I wasn't able to get a nandroid backup before doing this, had no ext. SD card.
All I did before flashing the zip was flashing the custom recovery. Nothing else. No SU or anything else.
Can I RUU 4.0.3 to fix this problem?
Yes you need to ruu to get it back. I'm assuming your s on. You need to be s off in order to flash radios by themselves.
Sent from my ADR6425LVW using xda app-developers app
Yes, I am s-on and not rooted.
Is there any specific RUU that I should go to? I was thinking of using 4.03.605.2
Thanks
lamborg said:
Yes, I am s-on and not rooted.
Is there any specific RUU that I should go to? I was thinking of using 4.03.605.2
Thanks
Click to expand...
Click to collapse
Yes, that's the latest global RUU.
You need to relock to run it:
fastboot oem lock
Put it on your sd card and it should do it's thing when you reboot. Run it a couple times and make sure it's finished so it will get all the system files. I believe it reboots you once it's done.
Then you can unlock again, flash recovery and root. If you have trouble rooting again search this forum for "super su" and you'll find a version you can flash to gain root.
feralicious said:
Yes, that's the latest global RUU.
You need to relock to run it:
fastboot oem lock
Put it on your sd card and it should do it's thing when you reboot. Run it a couple times and make sure it's finished so it will get all the system files. I believe it reboots you once it's done.
Then you can unlock again, flash recovery and root. If you have trouble rooting again search this forum for "super su" and you'll find a version you can flash to gain root.
Click to expand...
Click to collapse
I relocked but then tried flashing the zip twice.
Here's what comes in cmd:
sending....
OKAY
writing
<bootloader>adopting sig ....
<bootloader>checking sig
failed <remote: not allowed>
finished
After rebooting, it gets stuck on the white HTC screen.
sounds like a bad download, go back to android police and try to get the mirror from Illinois, it worked for me a couple of weeks ago after having the same issue as you.
sent from my rooted SAMSUNG GALAXY NOTE 2...
mike7728 said:
sounds like a bad download, go back to android police and try to get the mirror from Illinois, it worked for me a couple of weeks ago after having the same issue as you.
sent from my rooted SAMSUNG GALAXY NOTE 2...
Click to expand...
Click to collapse
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
lamborg said:
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
Click to expand...
Click to collapse
You have to fastboot oem rebootRUU first
then fastboot flash zip PH98IMG.zip
you may have to flash the zip twice.
Code:
androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
(I can't link yet)
lamborg said:
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
Click to expand...
Click to collapse
You don't flash this in fastboot since it's a zip file.
EDIT: Looks like you can flash in fastboot as mentioned in the above post. Cool, I like that. I would flash it twice as I've read several times that you need to to make sure it gets all the system files.
If htat doesn't work for whatever reason, just put it on the sd card of your phone, detach your phone from your pc and reboot. hboot should find it (it looks for the PH98IMG.zip file) and flash it. Flash it twice to be sure it gets all the system files.
When it's done and you're rebooted use a file explorer and delete the PH98IMG file so it doesn't flash again on the next reboot.
Related
hi all
Forgot to charge my EVO 3D (CDMA) and battery completely drained. Even after using another fully charged battery my phone goes to bootloop - just shows the HTC logo and reboots again and again. Here is what I have:
hboot : 1.5 (S-ON)
radio : 1.06.00.1216
ota : 2_17.651_5
(I am using this phone in India activated on Reliance)
As the phone doesn't boot I can't access it thru adb to give command 'adb reboot bootloader'
I can get bootloader by pressing vol_down+power
When I run the 2_17.651_5 RUU (exe) from my computer while phone is on fastboot, it completes successfully without errors. But still on reboot it just stays at the htc screen and reboots (guess it's becoz stock kernel not getting flashed as the phone is s-on)
kindly help to get back my phone boot again
thanks and regards
ananth
R.I.P
Sent from my HTC.EVO.3D.Xda Premium
Don't listen to the previous guy. Try using fastboot OEM lock and then ruuing. Or, try getting freezas stock kernel and extracting the boot.IMG and flashing it thru fastboot. Or, you could use fastboot flash recover recovery.IMG to get twrp or clockworkmod and do a superwipe and try flashing a new Rom. There are tons of options if you still have fastboot.
Sent from my HTC popout book.
jdeoxys said:
Don't listen to the previous guy. Try using fastboot OEM lock and then ruuing. Or, try getting freezas stock kernel and extracting the boot.IMG and flashing it thru fastboot. Or, you could use fastboot flash recover recovery.IMG to get twrp or clockworkmod and do a superwipe and try flashing a new Rom. There are tons of options if you still have fastboot.
Sent from my HTC popout book.
Click to expand...
Click to collapse
Thanx for responding. As I mentioned earlier,I have already relocked and RUU'd the exe file,but though it runs without errors doesn't solve problem. Again as it is s-on doesn't permit to flash boot.img. Though I am able to flash twrp recovery, not able to get into recovery from fastboot. Thanks again, really appreciate your help.
ananth001 said:
Thanx for responding. As I mentioned earlier,I have already relocked and RUU'd the exe file,but though it runs without errors doesn't solve problem. Again as it is s-on doesn't permit to flash boot.img. Though I am able to flash twrp recovery, not able to get into recovery from fastboot. Thanks again, really appreciate your help.
Click to expand...
Click to collapse
You don't need to relock once you unlock the HTC way. Just unlock the phone then flash via fastboot the boot.img and then ruu if you want.
Sent from my PG86100 using Tapatalk
megabiteg said:
You don't need to relock once you unlock the HTC way. Just unlock the phone then flash via fastboot the boot.img and then ruu if you want.
Click to expand...
Click to collapse
thanks. extracted boot.img from freeza's kernel and flashed from fastboot after unlocking. But still doesnt solve problem. Can you give me a link for boot.img
Pleassssssse HELP !!!!!!
I have the exactly the same problem, a full reboot result in boot loop, and can not fix it by now.
I guest the phone is rooted before OTA, so OTA can not flash kernel successfully because the wrong signature, and the phone will not boot because the wrong kernel.
I have tried ruu, fastboot boot recovery.img and etc, all failed.
The key point is that, the phone is rooted and you tried OTA. HTC OTA must have a stupid bug, it can not recovery from a partial update, or automatically roll back becasuse of the partial update, dem!
Please have a look at the guide/flashing notes in my signature. If u r unlocked u are likely not entering recovery correctly.
If u are trying to flash the Ruu u have to be locked or relocked. If u cant boot to android, run the xhausx's full Ruu zip from bootloader.
Sent from my PG86100 using Tapatalk
mpgrimm2 said:
Please have a look at the guide/flashing notes in my signature. If u r unlocked u are likely not entering recovery correctly.
If u are trying to flash the Ruu u have to be locked or relocked. If u cant boot to android, run the xhausx's full Ruu zip from bootloader.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
1) flashed RUU (exe) after relocking - flash completed without errors
2) ran xhausx's full RUU zip (PG86IMG_2.17.651.5.zip) from bootloader (could get into bootloader by pressing volum_up + power button. adb cannot connect to phone (as phone does not boot), to run 'adb rebooot bootloader')
But still doesn't solve problem and phone keeps rebooting, apparently kernel has not flashed properly.
Please help !!!1
ananth001 said:
1) flashed RUU (exe) after relocking - flash completed without errors
2) ran xhausx's full RUU zip (PG86IMG_2.17.651.5.zip) from bootloader (could get into bootloader by pressing volum_up + power button. adb cannot connect to phone (as phone does not boot), to run 'adb rebooot bootloader')
But still doesn't solve problem and phone keeps rebooting, apparently kernel has not flashed properly.
Please help !!!1
Click to expand...
Click to collapse
You need to use the RUU 2.17 exe after you relock your phone... Then flash a copy of CWM or TWRP on it..
Then adb
fastboot boot recovery.img
Wipe and flash whatever you want
Just noticed u said India & carrier is reliance. Why would u be using a Sprint USA CDMA Ruu? Shouldn't u be using a GSM RUU version?
Sent from my PG86100 using Tapatalk
mpgrimm2 said:
Just noticed u said India & carrier is reliance. Why would u be using a Sprint USA CDMA Ruu? Shouldn't u be using a GSM RUU version?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
I wonder the same thing all I saw was 1.5
Sent from my PG86100 using xda premium
mpgrimm2 said:
Just noticed u said India & carrier is reliance. Why would u be using a Sprint USA CDMA Ruu? Shouldn't u be using a GSM RUU version?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Reliance has both CDMA as well as GSM service in India. Mine is a Reliance CDMA MDN.
thanks and regards
reaper24 said:
You need to use the RUU 2.17 exe after you relock your phone... Then flash a copy of CWM or TWRP on it..
Then adb
fastboot boot recovery.img
Wipe and flash whatever you want
Click to expand...
Click to collapse
Yeah , as I mentioned earlier, I also tried using the RUU 2.17 exe after relocking (RUU completed successfully without errors) , and flashed twrp recovery from fastboot . But still it's a no go.
(Again would like to repeat that I can't boot into bootloader from adb - adb cannot connect as phone doesn't android boot. I get into fastboot by pressing vol_down + power)
thanks all for your responses and help, hope you all will continue guiding me till I get this done.
ananth001 said:
Yeah , as I mentioned earlier, I also tried using the RUU 2.17 exe after relocking (RUU completed successfully without errors) , and flashed twrp recovery from fastboot . But still it's a no go.
(Again would like to repeat that I can't boot into bootloader from adb - adb cannot connect as phone doesn't android boot. I get into fastboot by pressing vol_down + power)
thanks all for your responses and help, hope you all will continue guiding me till I get this done.
Click to expand...
Click to collapse
Have you tried to just run the RUU like you said boot turn debug on .... Then go to hboot flash your recovery...
Then fastboot boot recovery.img.
This should work I have unrooted my phone 3 times already in the past month Trial and Error on my part adb always found my phone...
I am tryin to figure out what is going wrong on the last part with TWRP...
Since you said after you do that it was a no go? What happend ? Adb should still be working since you just flashed the recovery...
Anyways I hope you get it solved man I am tryin to figure this problem out.
Do you have a rom already ready to be flashed on your SD card?
Problem is, since i’m not able to android boot I can't reboot bootloader from adb, as I can't connect adb without the phone normal booting. When I boot it just stays at the HTC white screen.
I have flashed twrp recovery from fastboot, but when I give command 'fastboot boot <twrpxxxxx>.img it just boots back to the HTC splash screen
You can go back to complete stock if you rename the RUU file PG86IMG.zip and load onto the root of sd card. Get into bootloader with [power+volume down] and it will automatically detect and load the zip file. This can only be done if you are relocked. I did this in order to get the latest update. After you get back to stock you can unlock and root again.
Android Cowboy said:
You can go back to complete stock if you rename the RUU file PG86IMG.zip and load onto the root of sd card. Get into bootloader with [power+volume down] and it will automatically detect and load the zip file. This can only be done if you are relocked. I did this in order to get the latest update. After you get back to stock you can unlock and root again.
Click to expand...
Click to collapse
As I mentioned in earlier post, have tried flashing PG86IMG.zip from bootloader, but still phone doesn't boot properly and is in a bootloop.
You've used the following file and done these exact steps and allowed the phone to boot to full stock OS? (assuming 2.17.651.5 is correct version)
OPTION 2 - RUU.zip info:
I prefer the .exe version but xHausx’s “FULL” PG86IMG_2.17.651.5.zip may work for you (must be renamed PG86IMG.zip). Make sure you have plenty of battery/charge left!
- (XDA) Xhausx full PG86IMG.zip RUU images (651.5 zips)
PG86IMG_2.17.651.5.zip http://forum.xda-developers.com/showpost.php?p=21593454&postcount=564
MD5: 8F82C2D8F98C077AF775266064BACB5D
From Scrosler's zip Directions : http://forums.androidcentral.com/htc-evo-3d-rooting-roms-hacks/107641-how-return-100-stock-all-versions.html
Scrosler; said:
USE ONLY FOR EMERGENCY PURPOSES. THIS OVERWRITES EVERYTHING!!!!
**THIS WILL RETURN YOU TO FRESH OUT OF THE BOX**
You will not need any special drivers loaded, etc...
1.Download the stock ROM ZIP image from here: and rename it "PG86IMG.zip"
2.Copy it to SD Card
3.Reboot phone into hboot mode by holding volume down and then press power.
Keep volume down held until you boot into hboot mode.
4.In hboot mode the phone will scan the SD card with the image. Once it finds it will ask you if you want to update. Press "Power" to update.
5.Wait.... For a while. When it gets to "system" it will loop a few times. Its quite nerve wracking actually but after about 5 or 6 times it will complete.
6.Once the entire flash is complete it will prompt you to "press power to reboot." Press power and your phone will reboot to 100% stock ROM.
Click to expand...
Click to collapse
Hello, I am unable to get into recovery or in my rom. I can getting into the bootloader, but cannot get into recovery. I am on 1.50 HBOOT and phone is unlocked. I would like to get back to stock so I can do an OTA update. Any help would be great, please let me know if you need more information.
XcsaS said:
Hello, I am unable to get into recovery or in my rom. I can getting into the bootloader, but cannot get into recovery. I am on 1.50 HBOOT and phone is unlocked. I would like to get back to stock so I can do an OTA update. Any help would be great, please let me know if you need more information.
Click to expand...
Click to collapse
What happend to your recovery? Also you need to fastboot oem lock while in hboot using adb
If you wanna go stock you will need the RUU exe you can find this in footballs post in the dev section...
reaper24 said:
What happend to your recovery? Also you need to fastboot oem lock while in hboot using adb
If you wanna go stock you will need the RUU exe you can find this in footballs post in the dev section...
Click to expand...
Click to collapse
not sure what happened with recovery, just wouldn't boot. will I be able to use the RUU exe while in fastboot?
XcsaS said:
Hello, I am unable to get into recovery or in my rom. I can getting into the bootloader, but cannot get into recovery. I am on 1.50 HBOOT and phone is unlocked. I would like to get back to stock so I can do an OTA update. Any help would be great, please let me know if you need more information.
Click to expand...
Click to collapse
if you have a copy of your boot.img and/or your recovery.img file flash that through your fastboot usb screen and reboot you should be ok pending your /system and /data partitioms are ok... if not follow the rest....
ok im goignt to guess youre new to flashing and the android development... but first thing is first... download the stock recovery zip on the other listed thread and rename it PG86IMG.zip... then reboot into your hboot/bootloader.... this will install a stock rom and recovery AFTER that you must reboot then shut down and reboot into your hboot again and from there go to fastboot and plug in the usb cable so your prompt says fastboot usb and then relock your boot loaderafter that finishes reboot again to the ROM and then run your updates... after you get the updates you want you can unlock again and then reinstall superuser and proceed as you want....
wloftus said:
if you have a copy of your boot.img and/or your recovery.img file flash that through your fastboot usb screen and reboot you should be ok pending your /system and /data partitioms are ok... if not follow the rest....
ok im goignt to guess youre new to flashing and the android development... but first thing is first... download the stock recovery zip on the other listed thread and rename it PG86IMG.zip... then reboot into your hboot/bootloader.... this will install a stock rom and recovery AFTER that you must reboot then shut down and reboot into your hboot again and from there go to fastboot and plug in the usb cable so your prompt says fastboot usb and then relock your boot loaderafter that finishes reboot again to the ROM and then run your updates... after you get the updates you want you can unlock again and then reinstall superuser and proceed as you want....
Click to expand...
Click to collapse
Ok following your instructions I downloaded the RUU (two of them infact) changed the name to PG86IMG.zip, when booting into the bootloader, it starts checking the PG86IMG.zip file, there is a blue status bar on the top right, when it fills completely in, it just starting checking the SD card for files again, and then goes back to the normal bootloader screen with options to select fastboot, factory reset, etc... Is there something I missed? I believe there should be some more options.
EDIT: the football post http://forum.xda-developers.com/showthread.php?t=1334473 only goes to .exe files, I had downloaded a .zip file from a different source with the same name, Should I have changed the .exe to PG86IMG.zip?
After using the command flashboot oem lock
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 66977136 (0x3FDFD70)
FAILED (status read failed (Too many links))
finished. total time: 0.937s
Now showing
*** RELOCKED ***
*** Security Warning ***
XcsaS said:
Ok following your instructions I downloaded the RUU (two of them infact) changed the name to PG86IMG.zip, when booting into the bootloader, it starts checking the PG86IMG.zip file, there is a blue status bar on the top right, when it fills completely in, it just starting checking the SD card for files again, and then goes back to the normal bootloader screen with options to select fastboot, factory reset, etc... Is there something I missed? I believe there should be some more options.
EDIT: the football post http://forum.xda-developers.com/showthread.php?t=1334473 only goes to .exe files, I had downloaded a .zip file from a different source with the same name, Should I have changed the .exe to PG86IMG.zip?
Click to expand...
Click to collapse
no...do not install the exe file at all.... the zip file if it is a trusted source should work...after it loads the files it finishes booting into the hboot screen...from there you can boot into the rom to verify that there is no superuser program and then power down and boot into your hboot again and relock your bootloader then reboot to the rom and update....when you boot back into the rom after installing the zip file it should look like the way it was when you first got it...if not you may have the wrong zip file
Ok I found out there was a zip on that page, I will download that and see where I get. Thank you so much for the help so far.
Ok issue is solved. I guess I needed to be relocked before I could update with PG86IMG.zip. So I guess in the future make sure you are not rooted when trying to update
After attempting s-off my sd card is not recognized. It happened to 2 of them. My computer wont read them and control bear cannot write to them. And now im stuck on juopunutBear logo. ANy help would be great considering I cant use my phone now.
iflawdya said:
After attempting s-off my sd card is not recognized. It happened to 2 of them. My computer wont read them and control bear cannot write to them. And now im stuck on juopunutBear logo. ANy help would be great considering I cant use my phone now.
Click to expand...
Click to collapse
Download this:
http://dl.dropbox.com/u/14779955/jb_hboot.zip MD5: b05336c08f709bf0a909205bcb95b951
but the file in the adb folder where you use cmd
Put the phone in fastboot mode, then run the follwoing commands:
Code:
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
fastboot reboot
iflawdya said:
After attempting s-off my sd card is not recognized. It happened to 2 of them. My computer wont read them and control bear cannot write to them. And now im stuck on juopunutBear logo. ANy help would be great considering I cant use my phone now.
Click to expand...
Click to collapse
You haven't got s-off right? You got stuck there while trying to?
Sent from my HTC Vigor
Andro X said:
You haven't got s-off right? You got stuck there while trying to?
Sent from my HTC Vigor
Click to expand...
Click to collapse
Correct. Not there and screwed up 2 16gb cards in the process.
iflawdya said:
Correct. Not there and screwed up 2 16gb cards in the process.
Click to expand...
Click to collapse
You should only have used the one. It seems others have been able to correct the issue by simply reformatting the card with the phone, not via a USB connection to a computer.
a.mcdear said:
You should only have used the one. It seems others have been able to correct the issue by simply reformatting the card with the phone, not via a USB connection to a computer.
Click to expand...
Click to collapse
How would I reformat the card with the phone? I am stuck at juopunutbear screen. I can only get to fastboot screen. From there it says no image.
iflawdya said:
How would I reformat the card with the phone? I am stuck at juopunutbear screen. I can only get to fastboot screen. From there it says no image.
Click to expand...
Click to collapse
download a kernel, flash it from fastboot. Then reboot, and your ROM will load. Then fix the SDCARD, and try again.
cflo360 said:
Download this:
http://dl.dropbox.com/u/14779955/jb_hboot.zip MD5: b05336c08f709bf0a909205bcb95b951
but the file in the adb folder where you use cmd
Put the phone in fastboot mode, then run the follwoing commands:
Code:
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
fastboot reboot
Click to expand...
Click to collapse
cflo360 when I get to fastboot flash zip jb_hboot.zip it gets an erroe that says failed remote: 99 unknown fail. Any ideas? Would it be possible to just put a rom on another sd card and flash it?
a.mcdear said:
download a kernel, flash it from fastboot. Then reboot, and your ROM will load. Then fix the SDCARD, and try again.
Click to expand...
Click to collapse
sorry I was typing a question and did not see what you wrote before I sent it.
a.mcdear said:
download a kernel, flash it from fastboot. Then reboot, and your ROM will load. Then fix the SDCARD, and try again.
Click to expand...
Click to collapse
I know im asking alot but could you tell me how to flash a kernel from fastboot. I have only done it from the phone.
Thanks
iflawdya said:
I know im asking alot but could you tell me how to flash a kernel from fastboot. I have only done it from the phone.
Thanks
Click to expand...
Click to collapse
Pull your battery.. reinsert and hold volume down and the power button. Make sure phone is plugged in or replug in phone if you took it off to reboot. Should be in Hboot now, press power to select fastboot if it is white lettering over blue background. If it is red background your already in fastboot and if connected should say fastbootusb.
1. open a copy of the rom your on either with 7 zip or since your not adding anything to it unzip it .
2. find the folder that says kernel, now you will either see a PH98IMG.zip or you will see a file that his white with a silver circle called boot. That is the raw boot.img. If it is the ph zip simply unzip it and you will see the boot.img.
3. Now , remove the boot.img and place it in the same folder your fastboot is located , generally the place you unlocked with.
4. Then, bring up a command prompt the same way you did to unlock. change directory if needed by cd c:\thenthenameofthefoldrecontainingfastboot.
5. Simply type fastboot boot boot.img
6. you will see sending " size of img".. receiving "size of img ", then writing .. and it will end and tell you how many seconds it took.
Now, simply use the reboot selection from bootloader or with the command prompt type abd reboot and your phone should reboot and you will be back on your rom.
The reason you keep booting to the jBear screen is because the jBear process replaced your KERNEL. You need to find the kernel img file for YOUR operating system or ROM. If you are on GB, find a GB kernel. If on the ICS Leak, you need to find the ICS Leak kernel. If on a ROM, get that ROM's kernel file.
Then the commands on the PC are:
fastboot flash boot boot.img
fastboot reboot
Another option is to use Hansoon's Rezound All-in-one-kit to flash the stock kernel for you.
Howard
iflawdya said:
I know im asking alot but could you tell me how to flash a kernel from fastboot. I have only done it from the phone.
Thanks
Click to expand...
Click to collapse
no offense, but if you honestly cannot at least search to figure out how to do a fastboot command as simple as fastboot flash, then you should stay clear of s-off...
but that's my opinion.
and I'm really not saying this to be an ass.
just don't want to see you brick your phone.
mjh68 said:
Pull your battery.. reinsert and hold volume down and the power button. Make sure phone is plugged in or replug in phone if you took it off to reboot. Should be in Hboot now, press power to select fastboot if it is white lettering over blue background. If it is red background your already in fastboot and if connected should say fastbootusb.
1. open a copy of the rom your on either with 7 zip or since your not adding anything to it unzip it .
2. find the folder that says kernel, now you will either see a PH98IMG.zip or you will see a file that his white with a silver circle called boot. That is the raw boot.img. If it is the ph zip simply unzip it and you will see the boot.img.
3. Now , remove the boot.img and place it in the same folder your fastboot is located , generally the place you unlocked with.
4. Then, bring up a command prompt the same way you did to unlock. change directory if needed by cd c:\thenthenameofthefoldrecontainingfastboot.
5. Simply type fastboot boot boot.img
6. you will see sending " size of img".. receiving "size of img ", then writing .. and it will end and tell you how many seconds it took.
Now, simply use the reboot selection from bootloader or with the command prompt type abd reboot and your phone should reboot and you will be back on your rom.
Click to expand...
Click to collapse
mjh68 I LOVE YOU MAN!! Thank you so much.
HowardZ said:
The reason you keep booting to the jBear screen is because the jBear process replaced your KERNEL. You need to find the kernel img file for YOUR operating system or ROM. If you are on GB, find a GB kernel. If on the ICS Leak, you need to find the ICS Leak kernel. If on a ROM, get that ROM's kernel file.
Then the commands on the PC are:
fastboot flash boot boot.img
fastboot reboot
Another option is to use Hansoon's Rezound All-in-one-kit to flash the stock kernel for you.
Howard
Click to expand...
Click to collapse
I tried the all in one and it did not work. I was stuck at htc splash screen.
andybones said:
no offense, but if you honestly cannot at least search to figure out how to do a fastboot command as simple as fastboot flash, then you should stay clear of s-off...
but that's my opinion.
and I'm really not saying this to be an ass.
just don't want to see you brick your phone.
Click to expand...
Click to collapse
None taking but if I don't know whats wrong how am I gonna search? Instead of telling me about the search button which yields thousands of threads how about helping me out. As you can see I have been a member for a long time. I didn't just pop on this site because I screwed up. I was up till 4 am trying to figure this out before asking for help.
This phone has never been rooted and has never had s-off. Phone will not boot into recovery or system. Only bootloops HTC logo or hboot. I used hboot and fastboot to get the bootloader unlocked. I have tried stock, ext4, and custom recoveries and none will boot. I have tried every ruu.exe and PG86IMG.zip from 1.17 to 2.89. None will work. I have used fastboot to flash boot and still will not boot up. When I try to run ControlBear it just
======== ControlBear 0.7 beta for JuopunutBear S-OFF ==========
Rebooting from bootloader
Waiting...
...Waiting
Detecting...Starting up......
Connecting to device...
Searching device.....
Connect device and install drivers
Press ENTER to exit.....
Nothing else.
I have seen a couple others with this issue in 1.50 and another with 1.58 but he was LOCKED and hasn't responded to his thread in a couple of days after suggesting having sprint look into it. I unfortunately have a crack in my touchscreen so sprint does nothing to help. Any idea or suggestions would be great.
PS sorry for any double posts or answered questions. I have been looking since 11 and trying different things with nothing working yet.
EDIT: I have looked into trying the unknownforce hboot downgrade but 2.17 will not install since its an older version. 2.89 files I find will load but when it trys to parse the phone just goes back to the bootloader menu.
I suggest you lock the bootloader first and then run the 2.17 ruu.exe. This will put you back to stock GB. Then you can unlock again and get s-off if you choose.
Save the Drama for your Mama with Tapatalk 2
coal686 said:
I suggest you lock the bootloader first and then run the 2.17 ruu.exe. This will put you back to stock GB. Then you can unlock again and get s-off if you choose.
Click to expand...
Click to collapse
I have tried that and I tried it again. Relocked the phone, ran the update and got a bootloader version error and the phone says RUU Update Fail! Going to try to PG86IMG.zip version of the update now and see if its any different.
EDIT: PG86IMG.zip fails with
Main Version is older!
Update Fail!
Press <power> to reboot.
any .zip files I have found with 2.89 will get to parsing then just go straight to bootloader menu.
I have the same issue, I update to ICS with the OTA update, then did the HTC Dev unlock. But with every rom I tried to flash It just stays stuck at the splash screen. If I try to use the RUU, it gives error 140 I believe, If I try to flash PG86IMG It gives me a main version older failure. S-On
Currently phoneless for the past few days :$
TheSeanR said:
I have the same issue, I update to ICS with the OTA update, then did the HTC Dev unlock. But with every rom I tried to flash It just stays stuck at the splash screen. If I try to use the RUU, it gives error 140 I believe, If I try to flash PG86IMG It gives me a main version older failure. S-On
Currently phoneless for the past few days :$
Click to expand...
Click to collapse
Got this from Tribulattifather page :
1st, ReLock Your bootloader.:
1. Enter FASTBOOT, and then connect to your computer (FASTBOOT USB will be shown).
To do this, hold your volume down key while pressing power. when you've seen the bootloader. Then hook up the phone to the computer. Make sure you have android usb drivers installed.
2. Open command prompt in your computer
3. Relock your device by typing "fastboot oem lock", device will reboot.
4. Enter FASTBOOT again (you will see *** RELOCKED ***)
Then get yourself flashed to a stock rom - <--place on sd card
..Download this one:
http://shipped-roms.com/download.ph...08_NV_SPCS_1.31_003_release_208230_signed.exe
Then press the power button on your phone and you should see Fastboot USB. Once you see this, runn the RUU.exe
Let that work it's way through.
Once that is done then it will boot to the rom.
From here, you can accept the OTA'
Read the rest here:
http://forum.xda-developers.com/showthread.php?t=1808332
^^^ Exactly what I said in post 2 but with more detail.
Save the Drama for your Mama with Tapatalk 2
finally past
I was TOTALLY stuck in the same area, Trib's method didn't work because no RUU would run against hboot 1.58.
After 3 hours of searching, I found Gonzo's post here:
http://forum.xda-developers.com/showthread.php?t=1813542
basically, extract the boot.img from the rom you are trying to flash, and use fastboot to flash the img
fastboot flash boot boot.img
this worked for me when NOTHING else would, thanks again to Gonzo320!
kuroyoma said:
This phone has never been rooted and has never had s-off. Phone will not boot into recovery or system. Only bootloops HTC logo or hboot. I used hboot and fastboot to get the bootloader unlocked. I have tried stock, ext4, and custom recoveries and none will boot. I have tried every ruu.exe and PG86IMG.zip from 1.17 to 2.89. None will work. I have used fastboot to flash boot and still will not boot up. When I try to run ControlBear it just
======== ControlBear 0.7 beta for JuopunutBear S-OFF ==========
Rebooting from bootloader
Waiting...
...Waiting
Detecting...Starting up......
Connecting to device...
Searching device.....
Connect device and install drivers
Press ENTER to exit.....
Nothing else.
I have seen a couple others with this issue in 1.50 and another with 1.58 but he was LOCKED and hasn't responded to his thread in a couple of days after suggesting having sprint look into it. I unfortunately have a crack in my touchscreen so sprint does nothing to help. Any idea or suggestions would be great.
PS sorry for any double posts or answered questions. I have been looking since 11 and trying different things with nothing working yet.
EDIT: I have looked into trying the unknownforce hboot downgrade but 2.17 will not install since its an older version. 2.89 files I find will load but when it trys to parse the phone just goes back to the bootloader menu.
Click to expand...
Click to collapse
Try the following steps,
1. go to recovery > wipe & factory reset, wipe cache, wipe dalvik, go to mounts and storage, wipe system, data, cache, sd card... everything u can find there... wipe all..
2. in recovery DO NOT REBOOT, turn off phone
3. go to android development of evo 3d gsm, find a rom, for example mikrunny 1.06, open the archive extract the boot.img from the kernel folder.
4. assuming u have android sdk installed on ur computer, make a new folder and from the android sdk tools copy adb.exe, fastboot.exe, adbwinapi.dll (exact same files u used to unlock bootloader). also in this folder put that boot.img you extracted from the rom
5. put that folder in C:\
6. get back to phone , still DO NOT BOOT UP YET, and power up phone in bootloader mode (vol down & power) and go to fastboot
7. connect phone to pc in fastboot usb mode
8. open command prompt, type cd c:\"folder" ("folder" = folder u created with the sdk tools)
9. type in cmd: fastboot flash boot boot.img
10. after it's completed, go to recovery, still do not boot up phone
11. in recovery go to mounts and storage, usb storage and now copy the whole rom and nothing but the rom on the sd card
12. install zip from sdcard, select rom and let it install, it should boot up automatically
steps were given by SeptimiuB, I am just replying to your query because I've gone through the same mess and recovered as well.
Just unlock your bootloader and install a recovery before trying the above steps.
Cheers.
Yea listen to that dude connect yur phone up fastboot boot boot.img and do the wire trick till it works. It will it takes several times and a lot of cursing but it'll work
EVO 3DIZZLE
S-OFF
HBOOT 1.58
Xsavior said:
I was TOTALLY stuck in the same area, Trib's method didn't work because no RUU would run against hboot 1.58.
After 3 hours of searching, I found Gonzo's post here:
http://forum.xda-developers.com/showthread.php?t=1813542
basically, extract the boot.img from the rom you are trying to flash, and use fastboot to flash the img
fastboot flash boot boot.img
this worked for me when NOTHING else would, thanks again to Gonzo320!
Click to expand...
Click to collapse
After flashing the boot.img, will it be OK to flash the rom from the img it is taken from?
I'm having the same problem as the OP.
---------- Post added at 07:19 PM ---------- Previous post was at 07:09 PM ----------
Xsavior said:
I was TOTALLY stuck in the same area, Trib's method didn't work because no RUU would run against hboot 1.58.
After 3 hours of searching, I found Gonzo's post here:
http://forum.xda-developers.com/showthread.php?t=1813542
basically, extract the boot.img from the rom you are trying to flash, and use fastboot to flash the img
fastboot flash boot boot.img
this worked for me when NOTHING else would, thanks again to Gonzo320!
Click to expand...
Click to collapse
Duuuuude, you totally saved me from minor stress and the headache I was going through. If you had PayPal, I'd send you $1. x-)
Sent from my Xoom using xda app-developers app
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
doctajay said:
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
Click to expand...
Click to collapse
You need to unlock again in order to flash back a custom recovery. You also need to have the stock splash screen before you ruu. Had the exact same issue you had. Stock h-boot, stock splash screen and relock and all should be good.
That is my main problem. All of the unlock methods require me to load load an apk to change the CID. I can't do that in fastboot. Is there another unlock method I'm missing that allows you to do it from the fast boot mode?
Sent from my LG-D800 using Tapatalk
if u have your original unlock code from htc dev I think u can fastboot flash that code to unlock again. its in the forum somewhere just not sure where it is.
try this thread, good luck
http://forum.xda-developers.com/showthread.php?t=2160677
You don't have to run a apk to change the cid just Google change cid commands, you do it through adb change it to 22222222 then redo the HTC dev to get your unlock.bin again if u don't have it.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
doctajay said:
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
Click to expand...
Click to collapse
You device most likely can't downgrade due to having a locked device. Have you tried flashing the 2.07 ruu
Thank you for all of the replies. Actually the change of the CID command might have worked but I didn't see that reply before I had tried another method found in this thread: http://forum.xda-developers.com/showthread.php?t=2570548.
I was truly stuck in fastboot and couldn't flash a custom recovery at all. Well I used the advice from a previous thread and edited the firmware .zip posted in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2314771. I had initially tried to flash the .zip posted but when I tried to boot into the recovery it wouldn't work. So I opened the .zip file without extracting it and removed the recovery.img from the .zip, I then took the TWRP custom recovery and inserted it into the .zip (if you extract the zip this will not work; you need to use software that can edit a zip without extracting it. On the Mac, which I was using, I used Spring). I renamed the TWRP recovery to "recovery.img" to match what I had previously deleted.
Then I flashed this edited firmware.zip by using the following command in usb fastboot mode (here's the link for my edited file):
fastboot oem rebootRUU
fastboot flash zip YOUREDITEDFILE.zip
fastboot reboot
This then allowed me to boot into recovery. I thought I had figured it out and could now sideload a ROM using the "adb sideload" command and flash some type of ROM that would boot. This failed miserably; it would allow me to push the file, but the install would always fail before it completed.
So then I found this thread here: http://forum.xda-developers.com/showthread.php?t=2570548. I first flashed the two .zip files that were posted in post #44. then I flashed the full RUU posted in post #1. This gave me a bootable stock ROM. Praise God!!!
Finally I went back to this thread: http://forum.xda-developers.com/showthread.php?t=2293919, and flashed the following code.
Code:
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Not sure why I had such a terrible time, but I'm glad its over and the DNA is finally sold. Thank you for all your help!
trying to restore my dna back to stock
I got my dna locked again and now I am running the ruu file and i am stuck at 6%. Can someone help please!! Tried it by double clicking the ruu file and running it like that, and i also ran it in administration and both ways i am stuck at 6%