OK so today I wanted to revert my hox+ to stock so i get an RUU from AndroidRUU.com
Everything runs fine until the RUU says error.
So I read some posts on the internet that my bootloader needed to be locked so I relock my phone bootloader with ToolKit .
After I relocked the bootloader it shows some red lines in the bootscreen and takes me into the HBOOT and cannot reboot into system...
I tried to flash the RUU again and it still gets the error 131
What should I do ? Please help, thanks:crying::crying::crying:
Hi,
You have HOX+ AT&T? or International.
Remember to choose well the correct RUU.
Related
Currently I am Hboot 1.5 S-ON and trying to downgrade to HBoot 1.4 S-OFF. When trying to brick my phone on the PG86IMG.zip update it doesn't brick, at least I don't think so. I can enter HBoot, flash a rom, and all that stuff. I believe my problem is because I am presently on RUU 2.17 flashing a 2.17 update and I need to downgrade to RUU 1.13. However, when I try to run RUU 1.13 EXE with a relocked HBoot I get an error message part way through the utility.
ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
First of all, do I need to downgrade to RUU 1.13 to brick my phone on the PG86IMG update? And second, if that being so, how do I downgrade?
IXKastling said:
Currently I am Hboot 1.5 S-ON and trying to downgrade to HBoot 1.4 S-OFF. When trying to brick my phone on the PG86IMG.zip update it doesn't brick, at least I don't think so. I can enter HBoot, flash a rom, and all that stuff. I believe my problem is because I am presently on RUU 2.17 flashing a 2.17 update and I need to downgrade to RUU 1.13. However, when I try to run RUU 1.13 EXE with a relocked HBoot I get an error message part way through the utility.
ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
First of all, do I need to downgrade to RUU 1.13 to brick my phone on the PG86IMG update? And second, if that being so, how do I downgrade?
Click to expand...
Click to collapse
You need to be relocked/have 2.17 firmware on your phone.
Once you press (UP) to update does your device turn off right away?
I am relocked and have 2.17 firmware. When I press (UP) for the update it updates with a series of purple and black updating sequences. But I am trying to brick it and I can't seem to do so cause I am pulling out the power cord with no battery but I see no dim red light on the top of the phone. Like I said, everything boots as normal and I even can run the 2.17 RUU EXE and boot up that. I saw that the "HBoot downgrade tutorial" said...
If you're already S-OFF, but on 1.50, you can do one of two things... I have attached the PG86IMG.zip with the 1.40 bootloader on it, download it copy to sd card and flash via bootloader.
The other option is to simply re-run 1.13 RUU, this will downgrade it as well, but this will also erase all data in the process.
Now I assume that means if I am 2.17 and S-ON, which I am, I need to downgrade to 1.13 to have the 2.17 PG86IMG.zip update properly so I can pull the plug and brick it. Do I need to do that or am I just needing to repeat the bricking process until it works?
IXKastling said:
Currently I am Hboot 1.5 S-ON and trying to downgrade to HBoot 1.4 S-OFF. When trying to brick my phone on the PG86IMG.zip update it doesn't brick, at least I don't think so. I can enter HBoot, flash a rom, and all that stuff. I believe my problem is because I am presently on RUU 2.17 flashing a 2.17 update and I need to downgrade to RUU 1.13. However, when I try to run RUU 1.13 EXE with a relocked HBoot I get an error message part way through the utility.
ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
First of all, do I need to downgrade to RUU 1.13 to brick my phone on the PG86IMG update? And second, if that being so, how do I downgrade?
Click to expand...
Click to collapse
I downgraded yesterday. This is what I did. I downloaded this hbootdowngrade217.zip along with another download zip file that contained the 1.13 ruu and I downloaded a 2.08.zip file as well. I relocked my phone and ran the 2.17 ruu thats in that hbootdowngrade217.zip file. Then I rename the 2.08.zip file to PG86IMG.zip onto the root on my sd card. Booted into bootloader let it read the file. Once it read n I had to update. I plugged in the charger from the laptop to the phone then took the battery out. let it sit for a min then hit up on sp it can begin the update n right after it said UNZIPPING n said Updating I counted to 5 n took the charger out on 5. If u did this before it went to the next step you have bricked your device correctly. You can check this by going into the control panel>view devices<manage devices n u put the battery back in hold down the down volume button then plug your phone back up n u will see something saying: Qualcomm MMC Storage but it should change to QSUSB_ (something) that means have bricked it correctly. If u didnt then its gone read unknown device. Just continue trying to brick it. Hope this works for you.
[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
Hello folks,
i got hold of a HTC Flyer which is tmobile branded(-> i cant flash WWE Roms).
When I tried to root it, it was possible to do by flashing superuser.zip and installing a new recovery (via ADB), but I could not get any rom working.
Most of them require S-OFF.
And here is the problem: I can't turn it S-OFF, because I am not able to flash a Gingerbread RUU (which is required to get revolutionary working. it requires hboot version 1.11.003, I have 1.11.011)
When trying to downgrade with the WWE RUU I either get the error 131 or 155 (either wrong image or consumer failure).
So I read a lot and eventually found out, that I need a goldcard to flash any RUU (because I have a tmobile branded device) - it didnt work out either.
After reading more, I found SuperCID (which basically let me install through any RUU i want) - but I did not work - it didnt change the CID.
So my main problem is - how can I get the GB WWE RUU working, in order to S-OFF the device (it is already unlocked via HTCunlock)
I hope you get my point I would be very happy for any tips.
I need help with this too. Please let me know if you are able to find the ROM. Thanks
Downgrade RUU
I too am having trouble will putting on ROMs and downgrading the RUU to GB.
I downloaded from here
The GB RUU - RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204108_signed.exe
as my current RUU was - RUU_Flyer_HC_S_HTC_WWE_3.55.405.1_Radio_20.4801.30.0822U_3822.10.08.07_M_release_226690_signed.exe
The followed the instructions on the there here but the RUU exe fails to install. it semi bricks the device and stalls the RUU installation at 16%
Hey all,
so I've been running ARHD on firmware 127.538.8 for awhile. I saw the RUU come out for 4.3 on Tmob, so obviously I was all like, **** yeah! So I flashed a stock ROM (based on 127.538.11) and then tried to run the RUU. Unlocked, S-OFF. For some reason, the RUU flashed Hboot (I'm currently stuck at 1.55.00) and then decided to throw an error 155 at me. So I tried relocking the bootloader, with a command I found browsing the forums that sets the status to Locked. Flashing the RUU here didn't work either. Re-unlocked the bootloader (I have no user data at all... it's sad). I realized, okay, I'm Unlocked and have a custom recovery installed (TWRP). Even if I relock, the RUU doesn't flash. My idea right now is to flash the 127.538.11 RUU to get Hboot 1.44, as well as a working non-hacked firmware. I'm not sure if that RUU will work, though I'm hoping it does. If it does, then I can OTA update without a problem.
Do any of you have any ideas as to how to do this? I can RUU to 127.538.11, then downgrade to x.8 and use revone to lock my bootloader and attempt an OTA. I'm not sure what to do here... I can also reflash ARHD 30 and stick with that for awhile. I can do basically anything recommended, as I have S-OFF and TWRP.
Thanks!
I don't mind being stuck on stock, however I do want to be able to warranty my phone in the future -- will having hboot 1.55.00 with 127.538.8 firmware be a problem? Can I downgrade my hboot since I'm S-Off? Any help here would be absolutely wonderful...
Converted an M7ATT to GPE - the owner wants it back to stock. I don't know how (probably an OTA) but S-ON got re-enabled and bootloader is locked. I tried unlocking it via HTCDev but it won't take.
-AT&T M7
-GPE fastboot/bootloader
-GPE Recovery
-Bootlooping as soon as it hits Android
-S-On / Locked(tampered) bootloader
When I try an RUU exe, it just says device not found. When I try it via rom.zip / commandline, it just says FAILED (status read failed (Too many links)).
Any suggestions?
K.AuthoR said:
Converted an M7ATT to GPE - the owner wants it back to stock. I don't know how (probably an OTA) but S-ON got re-enabled and bootloader is locked. I tried unlocking it via HTCDev but it won't take.
-AT&T M7
-GPE fastboot/bootloader
-GPE Recovery
-Bootlooping as soon as it hits Android
-S-On / Locked(tampered) bootloader
When I try an RUU exe, it just says device not found. When I try it via rom.zip / commandline, it just says FAILED (status read failed (Too many links)).
Any suggestions?
Click to expand...
Click to collapse
Have you tried to re s-off?
I believe the firewater and romrunner tools in the int. One forums should be able to s-off that hboot.
I haven't personally gone s-off, but my understanding is that once s-off you can change your sid (super sid maybe?) And run just about any ruu.
Search up on that stuff.
Sent from my HTC One using xda app-developers app
K.AuthoR said:
Converted an M7ATT to GPE - the owner wants it back to stock. I don't know how (probably an OTA) but S-ON got re-enabled and bootloader is locked. I tried unlocking it via HTCDev but it won't take.
-AT&T M7
-GPE fastboot/bootloader
-GPE Recovery
-Bootlooping as soon as it hits Android
-S-On / Locked(tampered) bootloader
When I try an RUU exe, it just says device not found. When I try it via rom.zip / commandline, it just says FAILED (status read failed (Too many links)).
Any suggestions?
Click to expand...
Click to collapse
you will have to s-off to repair the phone or hope for a new GPE RUU
whats the fastboot getvar all results (minus the serial no and IMEI )
I see a few mistakes. First, never go S-On and/or lock the bootloader once they've been unlocked. There's no reason for this unless returning to stock for warranty purposes. And if you do, ensure the phone has the software it's supposed to (AT&T in this case).
Secondly, if you have GPE, you must downgrade to hboot 1.44 first. And to do this, you must be S-Off.
Since the phone is currently S-On, the course of action depends on what is on the phone. If your CID is currently GOOGL001 or 11111111, try flashing the latest GPE RUU to restore the phone to working condition. Then go to HTCDev and unlock the bootloader. After that, you can use Firewater to S-Off.
Assuming all is successful, search for and flash hboot 1.44, then change the CID to CWS__001 (that's two underscores) and flash an AT&T RUU. And whatever you do, don't go S-On or lock the bootloader again. There's nothing to be gained by doing this.
If you're returning the phone to AT&T software because the person didn't like GPE (which I don't blame them), use the Dev Edition. By far the best choice to get the same Sense version of Android without all of the AT&T sh*tware. And things like AT&T Visual Voicemail work, along with any other AT&T app if the person wanted to download it from the Play Store for free.
Good luck.