Sorry to bother, I was to post this last night, then I tried a bit more and failed, I really need help now!
htcdev unlocked Evo 3D GSM(shooteru)
HBOOT shows below:
SHOOTER-U PVT SHIP S-ON RL
H-Boot-1.49.0018
eMMC-boot
I have been through and still in this mess since last afternoon, totally noob at the beginning, so forgive my stupid mistakes please.
1. I tried to use cwm v4.0.1.4 to flash the cm9-20130310-nightly-shooteru.zip (with gapps-ics-20120429-signed.zip)into the phone, and wiped cache and data before install zip. But after the installation, the phone just stuck at the HTC logo screen, fastboot mode and cwm are still available.
2. Flash in the boot.img but no luck.
3. Tried the official RUU_SHOOTER_U_ICS_35_S_htc_Asia_HK... but error 155 was reported.
4. Then I do some google and drag the rom.zip file from the RUU, renamed it to PG86IMG.zip and copied it to my SD card. FASTBOOT loaded the file, but the situation doesn't change a bit.
5. Google again, change my CID according to the android-info.txt extract from the ruu rom, relock the phone, and the RUU installed successfully, at least it looks like that at the moment, but it comes out that it just stay in boot loop.
6. Now I dont even have the official recovey(also boot loop), unlocked it again thru htcdev, tried to flash in the cwm touch v5.8.0.2 for shooteru, did not work. So status right now is unlocked, s-on, hboot 1.53.0007, no recovery, keep rebooting.
7. Exhausted and frustrated, I come here for any help. It's driving me crazy now, 'cause this is a friend(a girl indeed)'s phone.
I really need your help, pls!
Appreciate any relate information and concern in advance!
#################################################
rerun the ruu and set to the factory mode in hboot, problem solved!
forgot to mention
I don't know if this still matter though, I can see the cm9 robot screen after the RUU install failed in the step 3 because of wrong cid, but it stuck about 20 minutes, so I changed to the RUU method.
I think you have to be on an hboot 00007
花、不凋落っ said:
I think you have to be on an hboot 00007
Click to expand...
Click to collapse
thank you, I found out this and solve the problem by reinstall from the ruu, forgot to delete my post.
Related
hi, this is my first thread in xda.
my problem is i can not flash ph85img file through h-boot.
my rom, gb, telus canada
h-boot 1.90.0006
ruby pvt ship s-off(s-offed)
super cid ed.
rooted and recovery installed(stock)
couple of days back while i was trying to flash ics rom my phone got stucked at htc logo, after that i installed a new telus rom after flashing the new rom my h-boot changed from 1.90.0002 to 06.
initially when i was trying to flash the ics rom on h boot 02 it flashed without any porblem. at that time my s-off was juopnutbear s-off.
so whether i have to s-on the device and to get it s-offed using the wire trick to flash the ph85img file?
or do i have to change the h-boot version?
please help me.
It shouldn't matter since you already have s-off, check your cid again, most likely you'll have to super cid again if it's been changed, you can always flash the ENG Hboot instead and proceed doing whatever you wanna do.
thanks for your reply, i tired to flash enghboot but i no success. i got the file from this link
http://forum.xda-developers.com/showthread.php?t=1616472
i will check my super cid once more thanks
I super cid ed it again, went through without any problem, still cannot flash enghboot. zip file....
koottanal said:
thanks for your reply, i tired to flash enghboot but i no success. i got the file from this link
http://forum.xda-developers.com/showthread.php?t=1616472
i will check my super cid once more thanks
I super cid ed it again, went through without any problem, still cannot flash enghboot. zip file....
Click to expand...
Click to collapse
Hit the button lol
By the way, when you try to flash the ENG Hboot, though you don't need to once you're super cid, you need to change the file name of it to PH85IMG, note it has to be in capital letters and do no include the word .zip at the end, it's already there, you've done this before so you should know where to put the file, etc.
Thanks for taking the time. I've been working at fixing this for hours now, and to no avail. I was following the instructions found here (http://forum.xda-developers.com/showthread.php?t=1808332&highlight=reboot) ...but the short of it was I was upgrading my Hboot so that I could flash a JB ROM. Here's where the problem is, I have no recovery. When I try to access my 4EXT from fastboot, it shows a picture of a phone lying down with the app update symbol (an arrow pointing down with two or three, cant remember right now, around it) over it. Then after a short while it is replaced by a picture of a phone with an exclamation in a triangle. When I try to load a new recovery with SDK it says FAILED (remote: not allowed). I also tried loading back to Hboot 1.50, still nothing. If it matters, my phone came with 1.50.
I greatly appreciate any advice. Here's my current setup.
CDMA Evo 3d
Hboot 1.58 locked S-OFF
Radio 1.09.00.0706
Software 2.89.651.2 710RD
I would download the zip from here: http://forum.xda-developers.com/showthread.php?t=1889438
Then lock the bootloader in fastboot using fastboot oem lock. Run the ruu.exe to put your phone at stock (you'll still be s-off). Hopefully phone will boot.
You would then flash whichever hboot and recovery you want and flash a ROM.
No worries, all the stock hboots (if not unlocked using htcdev) won't allow you to use fast boot to flash recovery/boot partition even though you are s-off.
You can use a custom hboot like revolutionary / juopunutbears / eng hboot to use those commands. To flash another hboot, and just download the respective PG86IMG.zip and put it on the root of sdcard.
OR
If you current ROM is rooted, go to 4ext.net and download the free version and use it to install 4ext recovery on your phone or use flash image gui by joeykrim to flash recovery.
Those two apps will work on any hboot but your ROM should be rooted.
Hope this helps...
How did I know Coal would come to my rescue. Well after more work, and your great advice, I got it working again. The trick was I needed a JBear Hboot zip. Thanks again Coal, you are a legend.
Edit: Thanks mnomaanw, we posted that at the same time hahaha.
Hi ,
I have a flyer BB and it was working for several months till now , it is s-off and flashed LeeDrOiD HC V4.3.0
-REVOLUTIONARY-
Flyer PVT SHIP S-OFF RL
hboot-6.11.1111
microp-0950
radio-3809.7.04.06_m
eMMC-boot
Oct 25 2011
But it suddenly went to boot loop and I tried everything from flashing boot or recovery images till different ROMs but no success finally I flashed globatron RUU_US_WIFI_B10.zip via adb and it was succesfull but still boot loop .
I attached the log file from adb flashing and logcat
If anybody could give some advice what else i can do more i appreciate it very much.
Been while since I played with the FLyer.
THe Boot, Kernel and Radio have to match. and I think you have to return to S-ON
Try the steps in this thread.
http://forum.xda-developers.com/showthread.php?t=1346200
DigitalMD said:
Been while since I played with the FLyer.
THe Boot, Kernel and Radio have to match. and I think you have to return to S-ON
Try the steps in this thread.
http://forum.xda-developers.com/showthread.php?t=1346200
Click to expand...
Click to collapse
Thanks for reply but I flashed the globatron's RUU_US_WIFI_B10.zip from http://forum.xda-developers.com/showthread.php?p=19607833 which I assume all Hboot and radio's rom and kernel and so on are matched and flashed to the device , right ? if so can you let me know please what is the point to get back to s-on again ?
the other strange thing is when I flash any HC roms and corresponding boot.img it does not boot to ROM and goes to boot loop but when I flash JB rom from Dexter to boot to lock screen but when I continue to unlock item it re-boot . also I realized that WIFI and BT can be anable and working . I mean it seems they are not source of re-booting.
Anybody can please read the locat and let me know if they see any problem or how can i find the source of re-boot.
I did follow the S-ON procedure and still face with boot loop . now It is S-ON and i am not able to go S-OFF via revolutionary anymore due to boot loops or flash any other roms.
I do not understand why people they know, they do not speak and people they do NOT know much speak and let other persons to more mess with wrong advices !!!!
abifar said:
I did follow the S-ON procedure and still face with boot loop . now It is S-ON and i am not able to go S-OFF via revolutionary anymore due to boot loops or flash any other roms.
I do not understand why people they know, they do not speak and people they do NOT know much speak and let other persons to more mess with wrong advices !!!!
Click to expand...
Click to collapse
If you are now S-ON, then you should go back to the Stock RUU Honeycomb , load that and let stock recovery do the RUU update. Shuld put you back on unrooted, S-ON Honeycomb.
Like I said , I flashed the Stock RUU successfully but since it goes to boot loop a few seconds after booting I am not able to run revolutionary anymore.
I can go to hboot or fast boot but i am not able flash anything due to "FAILED (remote: signature verify fail) " now I am totally stuck
When I run the revolutionary it shows " Waiting for device... "
[Q] Evo 3D that hates me!!! ROOT s-OFF and unlock bootloader cant select yes
Hi all, im a newbie to android rooting etc, so please be patient if I dont understand... XD
I will try to give a backround with a very detailed discription for those who might have the same problem, a similar problem or for those trying to help...
so I bought this beast in Feb with stock software on: this was my 1st root, s-off attempt :
http://forum.xda-developers.com/showthread.php?t=2130585
1st attempt quote from post
Hi there,
Developers, gonna be developers and android noobs
I got a small issue with mu EVO 3d GSM...
Firstly Id like to apologize if this has been asked...
Problem: I need to get past BOOTLOADER BLOCK !!!
Before you carry on reading -
Bought this phone online, from China, Original HTC!!! but with 1 or 2 chinese apps installed, Android 2.3.4...
This was standard when I first entered bootloader (out of the box)
***LOCKED***
SHOOTER_U PVT SHIP S-OFF RH
HBOOT-1.49.0012
RADIO-10.13.9020.08_2M
eMMC-boot
What is suprising is it needed to say Locked and s-on...
So I wanted to root and s-off...
Tried Revolutionary... Everything ran well, after 2nd reboot into bootloader, error - Communications between phone and PC has been interrupted
After that I retried and it said - 'Your device is already s-off' then it wanted to download and install CWM Recovery 4.0.142 Revolutionary...
HTCDEV - Step 13 didnt happen, it just stayed on the normal bootloader screen (in Fastboot USB)
Flashed a earlier version of HBOOT (1.49.007) before Revolutionary ROOT method(revolutionary didnt support HBOOT 1.49.0012), i noticed everytime i 'completed' revolutionary method with error, my HBOOT changed to 1.49.1107 for some reason, IDK
Now my bootloader setup is:
***Revolutionary***
SHOOTER_U PVT SHIP S-OFF RH
HBOOT-1.49.1107
RADIO-10.13.9020.08_2M
eMMC-boot
In CWM Recovery - I flashed SU.zip, it removed /bin and /xbin, and wanted to start copying or rooting file and then showed an error msg 'installation aborted', booted into ROM and SU app requested SU access???
BTW... downloaded and tried 3 RUU's all 3 for 3d of course and all 3 gave the same error - MODEL ID ERROR (i need the correct model) and in fastboot...
Use same Rev code : fastboot flash unlocktoken Unlcok_code.bin
Half the time it is done successfully but with no disclaimer screen (stays on fastboot) and changes hboot to 1107
OR
Gives error (Remote : Partition no avaiblable) or (Remote : not allowed)
Try fastboot oem lock, Doesnt lock and same result as mentioned above and every now and then it says loading custom splash sceen failed, htc disclaimer screen???
If anyone has had this problem or similar, please help, I would really appreciate it
Thnks in advance!!!
END
Now, Ive got a similar problem,
HBoot
1.58.5858 Jpbear
Unlocked
So I flashed the RUU_Shooter_U_TWM_TW_1.23.921.5_Radio_10.55.9020.00_10.13.9020.29_M_release_207920_signed.exe, it was the closest I could find with HBoot 1.49.0012 and gb 2.3.4...
Okay, np it flashed it with no problems... but little did I know, I lost root, bootloader relocked with disclaimer screen and lost s-off... Im buggered
So after messing around including almost bricking my phone, flashing new hboots, trying htcdev unlock with rogers, EMEA and sprint, no luck...
The only result is it showing the disclaimer screen (as mentioned in 1st boot attempt) that i cant select yes...
I tried flashing recovery, however when I flash recovery, it either hangs with HTC screen for a min or two then reboots or just hangs there forever...
Somewhere along the line I tried booting into Android and it jut boot in fastboot, for some unknown reason it also didnt pickup the PG86IMG.zip file I had on, it actually didnt pickup and PG86IMG files???
I also came across writesecureflag 3 in fastboot, gave it a try and it gave me a ***security warning***...
After that, I coud flash a PG86IMG but when I tried the htcdev unlock, I select ye, no response, removed battery and it said ***unlocked***, but when I flash a recovery, it flashes recovery in cmd but cant boot into it or it just doesnt flash onto the phone???
Somehow in between all of this I could get past the "yes" in unlock bootloader which was pure luck of the joy of the moment made me forget what I did before, I also tried flashing these RUU's
RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed
RUU_SHOOTER_U_ICS_35_S_Rogers_WWE_3.28.631.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262715_signed(1)
RUU_SHOOTER_U_ICS_35_S_hTC_Asia_WWE_3.28.707.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_264110_signed
When booted in TWN-TW RUU, I could install Rom manager and flash CWM through that but through fastboot, it didnt boot through it
fastboot flash recovery recovery.img
fastboot boot recovery.img
RESULT: hangs on htc screen for a min or 2 then reboot into OS
Now im currrently on Asia ICS, hboot jbear 1.58.5858, htc recovery...
And in want of root, s-off, and most important able to Unlock Bootloader by selecting yes with a response,
please ANY help would be of use
thnx in advance
Its not much but will have a small paypal reward for those who helped (btw it will prob help others aswel)
[TAGS] : root issue, s-off problem, unlock bootloader cant select yes, evo 3d hboot not detecting PG86IMG, evo 3d bootloop
wow, you got a used or refurbished 3d which was already s-off. if you had posted before doing anything ,all you needed to do was flash a recovery and flash su zip. When you have s-off with custom hboot, like you had, you cannot unlock through htcdev and you don't have to. S-off with custom hboot means you can already flash any hboot ,recovery,Rom ,kernel or any mods.
You never needed HTC dev unlock.
you said.you are s-on with jbear.hboot? I.don't think.that's possible ,.check again if it's s-off or s-on . If it's s-on then it cannot be jbear.
You never lost s-off when you ran the RUU, you lost s-off by running the write secureflag command . It was your luck you were on stock.hboot , if you were on custom one,your evo 3d was dead for sure. Now flash the RUU that is made for your phone. then follow instructions from unlimited.io or ramjet73's thread , flash recovery then su zip. If you want another Rom you can directly flash that Rom without su.
Again, you never needed the htcdev. But now you will need it for the wire trick.
Thnx for responding, u made my day xD
mnomaanw said:
wow, you got a used or refurbished 3d which was already s-off. if you had posted before doing anything ,all you needed to do was flash a recovery and flash su zip. When you have s-off with custom hboot, like you had, you cannot unlock through htcdev and you don't have to. S-off with custom hboot means you can already flash any hboot ,recovery,Rom ,kernel or any mods.
You never needed HTC dev unlock.
you said.you are s-on with jbear.hboot? I.don't think.that's possible ,.check again if it's s-off or s-on . If it's s-on then it cannot be jbear.
You never lost s-off when you ran the RUU, you lost s-off by running the write secureflag command . It was your luck you were on stock.hboot , if you were on custom one,your evo 3d was dead for sure. Now flash the RUU that is made for your phone. then follow instructions from unlimited.io or ramjet73's thread , flash recovery then su zip. If you want another Rom you can directly flash that Rom without su.
Again, you never needed the htcdev. But now you will need it for the wire trick.
Click to expand...
Click to collapse
So, okay, I messed around abit more, not as if I could do any further damage besides bricking LOL
So this is my position and will leave it till next response...
***Relocked*** (can unlock, relock np because of s-on, if s-off, I cant, it just hangs after selecting yes, no response)
HBoot 1.49.0012
I have fastboot and OS access,
cant flash recovery or zip, etc, can change cid
Hboot doesnt read PG86IMG.zip files at all,
Goes through PG86... list, hangs 2 sec on PG86IMG.zip, says checking or parsing PG86IMG.zip for less than a sec then 'cancels', goes to hboot screen
Rev tool does not work
1st attempt - (1st line)Zerging root...
result- Cannot aquire root
for 2nd consecutive to 3,4,5,etc attempt
- goes to 2nd line in rev tool,
result gives error Communications with phone stopped,
When flashing recovery, it flashes perfectly, when fastboot boot recovery.img or hboot>recovery, hangs for a while then reboots
So flashing files through fastboot is a no go (generally gives error > remote:not allowed)
Thus conclusion, im considering the downgrade/unbrick method but It doesnt pickup and PG86IMG files (check exact speeling p.s. have done this alot)
I did a day ago aquire root, 4ext recovery but wanted unlock boot loader, so s-on, the only way to unlock, then got myself to this delema, stupid I know :silly:
So if you have any tricks up your sleeve, let me know please and thnx
Ok, to say up front I forgot to upload the ROM to the phone's storage FIRST.
Here are the steps I took today:
Today I received my new HTC One
I unlocked the Bootloader from HTCdev.com website - everything went smooth
I downloaded a custom ROM and flashed boot.img and 43_twrp_recovery.img
I loaded TWRP recovery and I thought I could mount a drive letter to upload the ROM, Seems I can't do that and these phones doesn't have a external sd card available.
Evidently after the fact I was told I shouldn't of flashed the boot.img and the phone will not boot but instead restarts after a minute or two. (This is my problem, I can enter recovery but I can't get the phone back to a working order)
I was instructed by someone to do the RUU but when I try it connects to the phone, displays the version and I choose to Upgrade the ROM. It reboots the phone into Bootloader with a black background with white htc lettering. From there it does nothing, I left it for over an hour with 5% progress. I unhooked the usb cable and the phone showed a error "loading zip into fail! update fail!"
The RUU I tried to load was this below, the phone is an AT&T HTC One 32GB
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe
I can still get into TWRP recovery, fastboot and bootloader just fine. I tried by recommendation to transfer the file via adb.exe but it keeps showing an error, can't connect to phone.
Here is the info on fastboot screen
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4T.20.3218.13
OpenDSP-v31.120.274.0617
OS-3.17.502.3
eMMC-boot 2048MB
Oct 4 2013,00:49:44.1770
The device is recognized in fastboot using "fastboot.exe devices".
I am seriously at a loss right now and need dire help if anyone has any recommendations.
Thank you in advance for your time in reading this!
cybernine said:
Ok, to say up front I forgot to upload the ROM to the phone's storage FIRST.
Here are the steps I took today:
Today I received my new HTC One
I unlocked the Bootloader from HTCdev.com website - everything went smooth
I downloaded a custom ROM and flashed boot.img and 43_twrp_recovery.img
I loaded TWRP recovery and I thought I could mount a drive letter to upload the ROM, Seems I can't do that and these phones doesn't have a external sd card available.
Evidently after the fact I was told I shouldn't of flashed the boot.img and the phone will not boot but instead restarts after a minute or two. (This is my problem, I can enter recovery but I can't get the phone back to a working order)
I was instructed by someone to do the RUU but when I try it connects to the phone, displays the version and I choose to Upgrade the ROM. It reboots the phone into Bootloader with a black background with white htc lettering. From there it does nothing, I left it for over an hour with 5% progress. I unhooked the usb cable and the phone showed a error "loading zip into fail! update fail!"
The RUU I tried to load was this below, the phone is an AT&T HTC One 32GB
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe
I can still get into TWRP recovery, fastboot and bootloader just fine. I tried by recommendation to transfer the file via adb.exe but it keeps showing an error, can't connect to phone.
Here is the info on fastboot screen
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4T.20.3218.13
OpenDSP-v31.120.274.0617
OS-3.17.502.3
eMMC-boot 2048MB
Oct 4 2013,00:49:44.1770
The device is recognized in fastboot using "fastboot.exe devices".
I am seriously at a loss right now and need dire help if anyone has any recommendations.
Thank you in advance for your time in reading this!
Click to expand...
Click to collapse
Use my encrypted rom.zip here
http://forum.xda-developers.com/showthread.php?t=2695749
clsA said:
Use my encrypted rom.zip here
http://forum.xda-developers.com/showthread.php?t=2695749
Click to expand...
Click to collapse
I'll give this a try as well, Im in the say boat as the Op, but my Hboot is 1.44..
cybernine said:
Ok, to say up front I forgot to upload the ROM to the phone's storage FIRST.
Here are the steps I took today:
Today I received my new HTC One
I unlocked the Bootloader from HTCdev.com website - everything went smooth
I downloaded a custom ROM and flashed boot.img and 43_twrp_recovery.img
I loaded TWRP recovery and I thought I could mount a drive letter to upload the ROM, Seems I can't do that and these phones doesn't have a external sd card available.
Evidently after the fact I was told I shouldn't of flashed the boot.img and the phone will not boot but instead restarts after a minute or two. (This is my problem, I can enter recovery but I can't get the phone back to a working order)
I was instructed by someone to do the RUU but when I try it connects to the phone, displays the version and I choose to Upgrade the ROM. It reboots the phone into Bootloader with a black background with white htc lettering. From there it does nothing, I left it for over an hour with 5% progress. I unhooked the usb cable and the phone showed a error "loading zip into fail! update fail!"
The RUU I tried to load was this below, the phone is an AT&T HTC One 32GB
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe
I can still get into TWRP recovery, fastboot and bootloader just fine. I tried by recommendation to transfer the file via adb.exe but it keeps showing an error, can't connect to phone.
Here is the info on fastboot screen
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4T.20.3218.13
OpenDSP-v31.120.274.0617
OS-3.17.502.3
eMMC-boot 2048MB
Oct 4 2013,00:49:44.1770
The device is recognized in fastboot using "fastboot.exe devices".
I am seriously at a loss right now and need dire help if anyone has any recommendations.
Thank you in advance for your time in reading this!
Click to expand...
Click to collapse
Bootloader needs to be relocked to flash a ruu.exe with s-on
Says
C:\Android>fastboot flash zip Rom.zip
load_file: could not allocate 1556101543 bytes
error: cannot load 'Rom.zip': Not enough space
Dafuq?!
I wanted to give an update on the situation and a resolve to the issue.
I finally got the problem resolved by the help of a friend (wildchild).
I ended up downloading another RUU that matched my current version (3.17.502.3). I locked the bootloader and flashed using RUU in HBOOT. That process went through successfully and got the phone restored back to factory.
I unlocked the bootloader and phone went back to factory again!
I enabled WiFi to do a OTA update to 4.19.1540.9
Once that was completed I transferred the custom ROM to the internal storage of the phone.
Booted into recovery and done a backup using twrp recovery. I copied that to my PC just in case.
Booted back into twrp recovery and wiped the data and installed the custom ROM, took about 10 minutes or less to boot the OS. Finished!
Wanted to thank everyone who posted suggestions and for the help. Basically I took the same road as what cLsA had suggested, I believe either way would have gotten me the same results except I may have taken a longer road. Thanks for the RUU ROM cLsA, I'll save it for later !