Ok, here's the procedure for returning to stock S-ON after running revolutionary if required for warranty reasons.
Preparation
(Windows): Uninstall HTC Sync and any other sync software ( eg Androsync ) that you have been using.
(Windows) : Install these fastboot drivers
Get fastboot and adb tool for windows here
Get Fastboot and adb for linux here
Download the RUU for your device
Download the downgrade hboot for your device:
Flyer downgrade hboot MD5SUM=6f82c00e2029c4bf3cb00e861789e2f8
View downgrade hboot MD5SUM=d3462b3587564db133c2215127485fe4
Check the mdsum of your download
Check the mdsum of your download
Reboot to to fastboot mode
Flash the downgrade hboot
Flyer:
Code:
fastboot flash hboot flyer_downgrader.nb0
View:
Code:
fastboot flash hboot express_downgrader.nb0
Run the RUU for your device
I can't use adb on recovery mode. Can you upload your fastboot driver?
buidung said:
I can't use adb on recovery mode. Can you upload your fastboot driver?
Click to expand...
Click to collapse
1. Yes, you can use adb in recovery mode if you followed the instructions correctly.
2. Done
an system's update
...can be installed if i use this procedure?
I get an error
C:\Users\Namit>fastboot flash zip RUU_Flyer_BrightstarUS_WWE_2.27.1540.31_R_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204116_signed.zip
sending 'zip' (500195 KB)...
OKAY [ 77.287s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: not allowed)
finished. total time: 157.279s
Click to expand...
Click to collapse
EDIT1: Just moved the zip to sdcard as PG41IMG and went into bootloader. It is working right now; will report on results.
EDIT2: Worked! Flashed Radio and rebooted to finish the rest of the installation.
what is the name of hbbot image file in the "rom.zip"? is that "boot_signed.img"?
chong5379 said:
what is the name of hbbot image file in the "rom.zip"? is that "boot_signed.img"?
Click to expand...
Click to collapse
It is something like hboot_xxxxx.nb0
I try to flash the stock recovery by fastboot on my Htc View but not success. It shows "failed, signature .... Bla bla". My device is still s-on and hangs at htc screen. Hmm, I think its recovery partition was damaged and RUU can't overwrite another recovery.img on it. Can someone help me out ? Thanks
Namit1994 said:
It is something like hboot_xxxxx.nb0
Click to expand...
Click to collapse
*.nb0? isnt that should be *.img? im still confusing about this, i tried to use the "boot_signed.img", bootloader dead now, cannot turn on at all, the power light is blinking
Hello there,
I'm really desperate as I have this problem and I hope someone could help me, I'd be really grateful.
My following problem is :
I have an HTC FLYER and I tried to flash a new hboot FROM HERE ( http://forum.xda-developers.com/showpost.php?p=17481836&postcount=2 ) but mistakenly it was from another device, now my FLYER wont turn on at all.
Can someone help me how to flash a new hboot so my device can finally power up ? Please I really need my HTC FLYER to start working.
I tried running ADB and "adb devices" but my device serial doesn't how in the list of attached devices and i don't know neither how to flash the new hboot through adb.
Please I'm really desperate, I hope someone can help me . I'm really afraid my Htc Flyer is dead.
I'm afraid you worry is valid, if you flash an incorrect hboot and it won't boot then the only recovery is to send it for repair. The best option you have is to say that this happened as a result of the HC upgrade OTA.
hm
globatron said:
I'm afraid you worry is valid, if you flash an incorrect hboot and it won't boot then the only recovery is to send it for repair. The best option you have is to say that this happened as a result of the HC upgrade OTA.
Click to expand...
Click to collapse
yes but its bought in sweden and now i live in balkans so no warranty for me and i was thinking if i can fix it with some box method like jtag jig?
I motion that this thread either be stickied or combined with the S-OFF sticky thread.
hboot_1.11.0003.nb0
chong5379 said:
*.nb0? isnt that should be *.img? im still confusing about this, i tried to use the "boot_signed.img", bootloader dead now, cannot turn on at all, the power light is blinking
Click to expand...
Click to collapse
It was hboot_1.11.0003.nb0 in my case.
It can be either, mostly it will be .nb0 but it can be a .img. The important thing is that it is hboot not boot.
Where i can find RUU for my 3g flyer.
Now I use Leedroid rom i want to go back to official 2.3 to wail for official 3.2.
When or where?
Sent from my HTC Flyer P510e using xda premium
Where is can download RUU for my 3g flyer
^_^
I will correct my post
Thz
hi,
I updated to honeycomb using your method, but my tablet is now slower so I wanted to revert back to gingerbread.
The problem is I can't use ADB commands with it. It responds to fastboot commands but doesn't respond to adb commands. It shows: Error: device not found.
I have tried to put the rom.zip in the sd card, which seems to install gingerbread back, but it won't boot.
What can I do? I am desperate now.
Reflash honeycomb before you run out of battery
Related
Hi!
Yesterday i managed my Flyer to S-off via revolutionary tool.
Today i wanted to update to Honeycomb with this tutorial:
+
Google search: android.modaco.com Installing Honeycomb on your Flyer
Guide from Paul.
i got now stuck after the htcdev bootloader unlock.
i should transfer the cwm recovery file via fastboot into the flyer
command: fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.newhboot.img
Code:
< waiting for device >
sending 'recovery' (4682 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.198s
Why this is failed? i tried to do the next step, getting into clockworkmod recovery but nothing happens.
My Flyer shows now:
Code:
*** RELOCKED ***
*** Security Warning ***
FLYER PUT SHIP S-ON RL
HBOOT-1.11.0006
MICROP-0950
RADIO-3821.08.00.26_M
eMMC-boot
Aug 29 2011, 13:32:02
Fastboot 9v AC (because charging)
VOL UP
VOL DOWN
POWER
Bootloader
reboot
reboot bootloader
power down
What can i do now? any idea?
edit: adb don't work, fastboot works.
I'm going crazy tried to reunlock bootloader via htcdev. When i flash the unlock token i get same error
Code:
C:\Users\h0f1\Desktop\htc\android-sdk_r15-windows\android-sdk-windows\platform-t
ools>fastboot flash untlocktoken Unlock_code.bin
sending 'untlocktoken' (0 KB)...
OKAY [ 0.015s]
writing 'untlocktoken'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.019s
Why in the world would you use the htcdev unlock? Go to flyer development and follow globatron's honeycomb guide. Much better than voiding your warranty.
Sent from my PG86100 using Tapatalk
i did yesterday exactly those steps from globatron for soff and cw recovery.
For getting Honeycomb i used another guide yesterday.. because i found this site today..
I really dont know what to do now
Worst case run ruu of your stock software
Sent from my HTC Flyer P510e using xda premium
somehow it doesnt work
C:\Users\h0f1\Desktop\htc\android-sdk_r15-windows\android-sdk-windows\platform-t
ools>fastboot flash untlocktoken Unlock_code.bin
sending 'untlocktoken' (0 KB)...
OKAY [ 0.013s]
writing 'untlocktoken'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.017s
edit:
made it now with other version of fastboot... this is crazy..
so i unlocked again and now i can go on with the other steps?!
I would return to stock then use globatrons update method. Do you know your stock ruu
Sent from my HTC Flyer P510e using xda premium
is going back to stock via ruu possible when i changed hboot, radio and boot file?
the guide from paul says:
Do NOT under any circumstances run the RUU in it’s entirety nor ‘fastboot flash rom.zip’ – this will make irreversible changes that you don’t want!
Be careful if you flash any RUUs or do anything that could revert you to S-ON on a broken system – this could leave you stuck
i think i will recharge and go through the last 4 points..
im afraid
Try to get a new unlock token.
I can not see why running your ruu to stock.would be an issue but I am not 100% certain. I did a revert last week and the only thing I needed to do prior was relock hboot first which you are already locked.
Sent from my HTC Flyer P510e using xda premium
first i wanna say thanks for your help!
i did today the last two steps after recharging the battery.
last 2 steps are putting the new image onto sdcard via adb and second step was factory reset und dalvik wipe. All two steps worked fine for me, but after restart the flyer is going to a bootloop.
what should i do now?
Should i get back with the RUU?
Can i setup honeycomb after getting back with ruu with the tutorial from globatron?
best regards
tom
did you flash the zip through recovery
Sent from my HTC Flyer P510e using xda premium
^the tutorial say get into clockwork recovery mode and type into command "adb shell mount /sdcard && adb push stock-hc-flyer-system.zip /sdcard/"
this command finished after 3 minutes and i was also lookin at the sd card the file is on the sd card.. after this i wiped dalvik and made a factory reset in the clockwork recovery mode. Afterwards Reboot -> then bootloop
lool is it possible that i have to " install zip from sdcard" ? if yes i'm the dumbest flyer user on the world *g*
edit: i tried now to install the update via recovery, it says E: Can't open /sdcard/stock-hc-flyer-system.zip (bad)
h0f1 said:
lool is it possible that i have to " install zip from sdcard" ? if yes i'm the dumbest flyer user on the world *g*
edit: i tried now to install the update via recovery, it says E: Can't open /sdcard/stock-hc-flyer-system.zip (bad)
Click to expand...
Click to collapse
Re-download, it's corrupt.
ikingblack said:
Re-download, it's corrupt.
Click to expand...
Click to collapse
+1
Sent from my HTC Flyer P510e using xda premium
really i promise i will neveer ever never try to flash/hack/root anything. its just horrible thinking all the time you brick it or anything else xD
i tried to reboot bootloader via adb in the recovery mode, flyer turned off and now nothing happens. cant go into bootloader or something else.. trying to recharge again, maybe battery is low again (i hope..)
well i will go on tomorrow evening.
great work guys anyways, thanks
tom
h0f1 said:
really i promise i will neveer ever never try to flash/hack/root anything. its just horrible thinking all the time you brick it or anything else xD
i tried to reboot bootloader via adb in the recovery mode, flyer turned off and now nothing happens. cant go into bootloader or something else.. trying to recharge again, maybe battery is low again (i hope..)
well i will go on tomorrow evening.
great work guys anyways, thanks
tom
Click to expand...
Click to collapse
I don't know if it's possible to really stop it from booting or displaying anything on the screen. Recharge and once it's done hold power button for a long time.
Good Luck
help fully bricked htc flyer p510e
here is what i did step by step:
bought an htc flyer, then upgraded it officially to honeycomb
i did not like honeycomb so i unlocked bootloader with htc dev method
then flashed recovery and rooted....
changed the misc_version and downgrade back to gingerbread with fastboot flash zip rom.zip
it worked........gta 3 and gta vice city worked.......few months later the gta 3 and vice city started crashing( just like honeycomb)
so i got s-off with revolutionary.....and flashed honeycomb PG41IMG.zip
that worked...........few months later i wanted gta back so i could not take i tried flash back down but did not work...it would get stuck in RUU mode ...so i flashed PG41IMG.zip back and that worked ..i was not bricked...so i tried another method
i flashed fastboot express downgrader.nb0 and
flyer downgrader.nb0
then changed gingerbread rom.zip to PG41IMG.zip and placed it on sd card
went into bootloader and let it flash
the bootloader at this moment:
***security warning***
pvt chip s-on
hboot 1.10.000
..................
it does not show whether the bootloader is locked or unlocked......no recovery.......tablet does not boot.....only to bootloader and fastboot.....
i tried to flash the unlock token for bootloader but get
signature failed error....
i tried to flash the honeycomb PG41IMG.zip but get
checking header failed
remote[signature failed]
cant flash anything because of that ...cant flash recover to even turn off the verification signature check.....
plz help ...whether you help me to fix it back to gb or hc to dont care ..just want it to work
plz help me fast
battery charges but phone goes into fastboot .....
plz help
just ask if u need more information on the situation..
plz anyone
Should probably find a good RUU that is compatible, create a gold card and do a clean re-load of compatible ROM.
The issue
If you flash new 3.15.651.16 JellyBean RUU and it only updates hboot to 2.09, phone might end-up in semi-bricked state.
RUU refuses to flash any other partition (even if bootloader is in locked/relocked state) so its impossible to return phone to stock rom.
Error message from fastboot flash zip is;
Code:
fastboot flash zip RUU.zip
sending 'zip' (659905 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOrom parsing start ...
INFOrom parsing finish ...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 22 loading zip info fail)
What is causing this
Hboot fails to read ruu-info from new encrypted zip after hboot-preupdate and stops flashing process.
Solution
Solution is to flash firmware.zip from JellyBean OTA. Firmware.zip is "old style" zip file, hboot can open this zip and update radio and sbls.
Fix
- Download JB OTA firmware from http://unlimited.io/jewel.htm
- Download fastboot executable (google)
- Put all files in one directory
- Reboot phone into fastboot mode
- Make sure that bootloader is Locked or Relocked. If bootloader is Unlocked, relock it with command fastboot oem lock
- Enter commands
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip jewel_jb_ota_firmware.zip
NOTE:
If you see FAILED (remote: 90 hboot pre-update! please flush image again immediately) text after running fastboot flash zip command you have to run fastboot flash zip command again.
After this flash stock RUU again.
Permanent fix
- S-OFF your phone. With S-OFF phone you can always flash decrypted, unsigned and/or older RUU and get phone working again easily. :good:
Please report any success / failures into this thread. Also tell little bit information about your device, like;
- What hboot you had
- Was radio flashed through recovery
- Was hboot downgraded
- CID
-- Reserved --
Thanks for your work
Sent from my EVO using xda premium
thanks fuses
Wow fuses, this is gonna help A LOT of people. This community is really lucky to have your attention. Thanks. :thumbup::beer:
Sent from my EVO using xda premium
I ran this... Worked to a T. Debating whether or not to s-off...
But, this did in fact update my radios..
Phenomenal. Just to be clear with what I did...
Ran Fuses instructions. Then I did the RUU GUI update in Windows... back to stock, Tampered in bootloader removed. Testing the stock radios and what not, but so far it's perfect.
*** Phone has to be RELOCKED****
I am not sure if I am successful or not right now. Phone is showing HTC black screen with green bar below it. The green bar is not ALL the way across, looks like 95% after running the commands. Not sure what to do so I issued "fastboot reboot"
Phone looks to be in bootloop so I got back into HBOOT.
First I relocked the phone. Rebooted. Then Rebooted into fastboot.
Then ran commands, screen shots are attached.
Seeing this message after running commands:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Changes noticed in Bootloader:
My RADIO updated from 1.02.12.0427 to 1.12.11.1119
OpenDSP updated from OpenDSP-v25.1.0.32.0405 to OpenDSPv31.1.0.45.0815
Update:
Put the phone into fastboot and then ran the windows Jellybean RUU. Looked like the RUU got about 98% thru and then gave me a USB error. Then the phone rebooted and it looks like everything updated. Phone is booting into JellyBean. Should I retry installing the RUU?
Cloves
Rerun the ruu. Just hit the up arrow and then enter
Sent from my EVO using Tapatalk 2
I don't personally have a need for this but I know others do so thanks! Nice to know this is there if needed. :thumbup:
Thanks,
Everything looks good. Phone shows RELOCKED and 4.1 is running. Thanks for the fix!
saved my ass. thanks!
My 4G LTE was on HBOOT 2.09
Tried to S-OFF and downgrade HBOOT by DirtyRacun
Was stuck at a point where the screen went blank for a long time
After that the phone does not power on...
Even the PC does not detect it...
Help please...
Seek out soul shadow . He's usually in the stickied threads in original development. He seems to know a hell of a lot about this phone and bricks/semi bricks
Sent from my EVO using xda premium
aankush said:
My 4G LTE was on HBOOT 2.09
Tried to S-OFF and downgrade HBOOT by DirtyRacun
Was stuck at a point where the screen went blank for a long time
After that the phone does not power on...
Even the PC does not detect it...
Help please...
Click to expand...
Click to collapse
Fastest way to get support for DirtyRacun is to join #unlimited channel on freenode.
Lets keep this thread clean, semi-brick on 3.15.651.16 stock RUU stuff only.
Well guys, time to add some info. If you lock and re-flash the RUU file and you get "SBL VERIFY FAILED" errors (but the RUU still completes) and you can't htcdev unlock (signature failed), you should use this fix. Helped me get my friend's phone S-off using Dirty Racun.
Fuses said:
Permanent fix
- S-OFF your phone. With S-OFF phone you can always flash decrypted, unsigned and/or older RUU and get phone working again easily. :good:
Click to expand...
Click to collapse
is this true?
if we're running stock JB (newer hboot), then we can downgrade it to stock ICS (older hboot) via RUU
un1ocked said:
is this true?
if we're running stock JB (newer hboot), then we can downgrade it to stock ICS (older hboot) via RUU
Click to expand...
Click to collapse
Um,...yes. if fuses posted it and it's about S-off,... it's true.
Sent from my EVO using xda premium
un1ocked said:
is this true?
if we're running stock JB (newer hboot), then we can downgrade it to stock ICS (older hboot) via RUU
Click to expand...
Click to collapse
Yes it is true, but always download full stock RUU and use that. There is some problems with repacked firmwares.
After I typed rebootRUU my screen changed to an HTC screen and stayed there for like 30 min, I tried to flash the zip but my phone wasn't recognized. But ever since that exact moment my computer has f***** up. Does anyone know why this happened
Sent from my EVO using xda premium
Jeffrey4Free said:
After I typed rebootRUU my screen changed to an HTC screen and stayed there for like 30 min, I tried to flash the zip but my phone wasn't recognized. But ever since that exact moment my computer has f***** up. Does anyone know why this happened
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Probably windows dropped fastboot-drivers. Try installing drivers again or use Linux, ubuntu live-cd works just fine.
Hello,
I have tried to flash a custom ROM to my htc desire x but unfortunetly I am a almost complete noob. I have been using Desire_X_All-In-One_Kit_v2.0 in order to complete the action. The problem is that i have never rooted the fone nor i have put in the recovery into it. So basically i unlocked the bootloader and thought it would all work.Well you know yourselfs it didn't.I have been looking all over the place for a way to get my phone fixed and i found one(ima Junior member can't post links yet ( Re-flash stock ROM (RUU) after bricking a rooted device)) .I have done all the steps but in step5 i get an error
C:\rec>fastboot flash recovery recovery_signed.img
sending 'recovery' (4266 KB)...
OKAY [ 0.795s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.323s
and in step 7 i get Error 140 bootloader error during RUU
Any help here would be greatly appreciated
Regards Kuba
First of all write down all you have written in bootloader screen.
It will be easy to fix it.
nlooooo said:
First of all write down all you have written in bootloader screen.
It will be easy to fix it.
Click to expand...
Click to collapse
How do you mean? do you mean whats written when i enter the bootloader or what have I written in in the terminal ( eg. fastboot flash recovery recovery_signed.img)
Thanks a lot for your quick reply
Bootloader screen, when you enter bootloader.
Also, give me the version of RUU that you have.
nlooooo said:
Bootloader screen, when you enter bootloader.
Also, give me the version of RUU that you have.
Click to expand...
Click to collapse
*****RELOCKED********
PROTO PVT SHIP S-ON RL
HBOOT-1.24.0000
RADIO-1.10.40.23
eMMC-boot
Oct 30 2012, 20:09:09
The most recent RUU i have downloaded is RUU_PROTO_U_ICS_40A_HTC_Europe_1.14.401.1_Radio_10.18.40.05U_1.09.45.201_release_284072_signed
But i have read that FAILED <remote: signature verify fail> error that im getting is related to wrong ruu .I guess you know better
There's a newer release 1.18.401.1 there's a link in Index in my signature, try to download that one and run it with phone booted in fastboot and attached to PC. If that doesn't go will try something else.
nlooooo said:
There's a newer release 1.18.401.1 there's a link in Index in my signature, try to download that one and run it with phone booted in fastboot and attached to PC. If that doesn't go will try something else.
Click to expand...
Click to collapse
Great man!! thanks for help!! Could you just make it clear what i need in the folder with the ruu ?. its Adb.exe AdbWinAp.dll fastBoot.exe and the image file? is there anything else i would need? (as you see i know basically nothing about this)
It's not a folder its exe file, just run it from PC.
nlooooo said:
It's not a folder its exe file, just run it from PC.
Click to expand...
Click to collapse
YOUR Fuc**ng Awsome bruf everything back on track !!.....THank a lot
hlick14 said:
YOUR Fuc**ng Awsome bruf everything back on track !!.....THank a lot
Click to expand...
Click to collapse
That's why I'm here and that's what the thanks button stands for...
Hey guys, I need to return my phone to verizon because of a simcard/PUK lock error. I'm on the current OTA update (2.06) but still unlocked, rooted and S-off. I need to go back to bone stock if possible. Can I still follow the guide in this thread to go back to stock??
http://forum.xda-developers.com/showthread.php?t=2017525
Anyone?
scheirere said:
Anyone?
Click to expand...
Click to collapse
You don't have to relock your phone all you have to do is flash the ENG Bootloader then you can run the RUU. Make sure you have all the drivers you need installed first or it WILL fail.
ENG Bootloader:
http://forum.xda-developers.com/showthread.php?t=2156713
Also this won't take away your S-Off the only way to get to S-On is by running a special command. Once S-Off always S-Off.
zone23,
Thanks a million! One more question....I'm not familiar with RUU. Do you have a link to were I might find that file?
Thanks again,
Eric
scheirere said:
zone23,
Thanks a million! One more question....I'm not familiar with RUU. Do you have a link to were I might find that file?
Thanks again,
Eric
Click to expand...
Click to collapse
Yes try here:
http://forum.xda-developers.com/showpost.php?p=37277937&postcount=66
Oh and don't forget to hit thanks on that post.
Ok, now I'm a little confused. I downloaded both files. The modded ENG bootloader and the RUU zip file from the links. But what order. Sorry but I'm not familiar with this stuff and don't want to dig myself into a deeper hole by bricking this thing.
Is this the proceedure?
1. adb reboot bootloader
2. fastboot oem rebootRUU (using the RUU_DLX_WL_JB_45.exe file?)
3. fastboot flash zip ModdedPL832IMG.zip
Anything else I'm missing? Also, what drivers? The same ones I installed when I rooted the phone?
Thanks in advance guys!
scheirere said:
Ok, now I'm a little confused. I downloaded both files. The modded ENG bootloader and the RUU zip file from the links. But what order. Sorry but I'm not familiar with this stuff and don't want to dig myself into a deeper hole by bricking this thing.
Is this the proceedure?
1. adb reboot bootloader
2. fastboot oem rebootRUU (using the RUU_DLX_WL_JB_45.exe file?)
3. fastboot flash zip ModdedPL832IMG.zip
Anything else I'm missing? Also, what drivers? The same ones I installed when I rooted the phone?
Thanks in advance guys!
Click to expand...
Click to collapse
This first:
1. adb reboot bootloader
2. fastboot oem rebootRUU
3. fastboot flash zip ModdedPL832IMG.zip
4. Profit
making sure that the .zip is in the same folder as fastboot
then run the RUU after you reboot the phone.
Yes it should be the same drivers you used when rooting.
Looks like I spoke too soon on those downloaded files. The download of the RUU file bombed out on me and I didn't realize it. When I go back to the site in the link, and try to download the file now, it just sits waiting. I guess the site is down? Any other links or locations?
Downloads working now maybe keep trying they say they are under a DDOS attack. Here it is from hotfile but I can't confirm this as real.
HERE
OK, I got partway thru the steps. everything went well until I tried to fastboot flash the ModdedPL832img file. I get a message "writing 'zip'....FAILED (remote not allowed)"
Any ideas/suggestions?
scheirere said:
OK, I got partway thru the steps. everything went well until I tried to fastboot flash the ModdedPL832img file. I get a message "writing 'zip'....FAILED (remote not allowed)"
Any ideas/suggestions?
Click to expand...
Click to collapse
After step 1, but before step 2, do this:
fastboot devices
If you don't get a device id, then you don't have the proper drivers installed.
If you get a device id, then try step 2 again ...
If that doesn't work, then I don't know
Maybe try a different USB port on your computer also use the OEM cable if you can.
Thanks guys for the suggestions. Unfortunately, still no luck. Same results when flashing the Modded file. I did try adb devices as suggested and got the device ID. So I think the drivers are OK. I also tried another USB port just to see if it helped. No go.
Just because I'm pretty new to this stuff, here's a detailed list of what I'm doing.....
1.) ADB reboot bootloader (from a command prompt)
Phone reboots to bootloader screen with Fastboot USB in red, hightlighted.
The screen no longer displays the "TAMPERED" heading at the top. So it looks like I'm making some progress.
2.) fastboot oem rebootRUU (from a command prompt again)
Phone screen goes from white to black with nothing but a large HTC logo in white.
Nothing else happens at this point. I've let the phone sit for 30 minutes with no apparent change and nothing on the host PC.
I then went thru my computer to the directory were the RUU_DLX.... file resides and executed (double clicked) it. I get an RUU - InstallShield screen and then I go thru the HTC rom update utility steps. After a few steps the utility does it's thing and the phone then reboots.
3.) ADB reboot bootloader again
Phone reboots into bootloader screen
4.) fastboot flash zip ModdedPL832IMG.zip (from a command prompt)
Phone does nothing but the command screen returns:
sending 'zip' (485 KB)...OKAY [ 0.266s]
writing 'zip'...FAILED (remote: not allowed)"
pretty much immediately
Am I doing this correctly?
At this point the bootloader screen no longer says tampered. Can I just relock the bootloader so it's s-on again?
BTW, here's what the bootloader screen shows:
*** UNLOCKED ***
MONARUDO PVT SHP S-OFF
CID-22222222
HBOOT-1.33.0001
RADIO-1.00.00.1023_3
OpenDSP-v4.120.240.0920
eMMC-boot
Oct 23 2012,21:34:05
Or can I just send the phone back as it is?
Bootloader uses a different driver than ADB. My advise is to boot into the bootloader then verify in device manager that the driver is loaded. See attached. Flashing the RUU will not get you S-On you need a command to do that and I don't know what it is off the top of my head I have never used it.
Hi everyone, here is my last attempt to save my desire x.
First : i’m not completely a newbee, i’m use to the devlopment with android i’m owing a TF700 and xperia mini pro, both rooted and running under custom rom.
My problem : This summer my phone used to switched off and on again, once per day. One day, it switched off and i couldn’t start it again (stuck on HTC logo). I did the first operation which came in my mind « factory reset by the bootlader » , same problem !
My second problem, i bought the phone in India were i was studying, HTC France explained me that i should return to the shop where i bought the phone to fix it up…..hahahahaa !
I gave up, now i want fix it by myself
How my phone is actually
HBOOT : 1.24
Access to the bootloader possible
Fastboot command works
Rooted with WIndroid
Why not flashing ?
I tried…First, i rooted sucessfully my phone, installed a ICS recovery but no a single one is working, can’t wipe any cache, ect…and the zip installation failed with CWM, TWRP, Philz….
I get these messages for all recoveries :
- Can’t mount eMMC
- Can’t mount cache
Any attempt to mount the eMMC and the cache is a fail, though the Ext-sd card can be mounted.
I tried the RUU (asia) , I relocked the bootloader with windroid, the RUU failed, it sent the files, and failed at the « signature update », the code error is 155.
Everything which is cited is what i did today, I did many other operations this summer but i couldn’t precisely describe it, i just know that i did a lot, and i’m today without any other solution….thus here is my post !
Thanks for your answers !
hugiz said:
Hi everyone, here is my last attempt to save my desire x.
First : i’m not completely a newbee, i’m use to the devlopment with android i’m owing a TF700 and xperia mini pro, both rooted and running under custom rom.
My problem : This summer my phone used to switched off and on again, once per day. One day, it switched off and i couldn’t start it again (stuck on HTC logo). I did the first operation which came in my mind « factory reset by the bootlader » , same problem !
My second problem, i bought the phone in India were i was studying, HTC France explained me that i should return to the shop where i bought the phone to fix it up…..hahahahaa !
I gave up, now i want fix it by myself
How my phone is actually
HBOOT : 1.24
Access to the bootloader possible
Fastboot command works
Rooted with WIndroid
Why not flashing ?
I tried…First, i rooted sucessfully my phone, installed a ICS recovery but no a single one is working, can’t wipe any cache, ect…and the zip installation failed with CWM, TWRP, Philz….
I get these messages for all recoveries :
- Can’t mount eMMC
- Can’t mount cache
Any attempt to mount the eMMC and the cache is a fail, though the Ext-sd card can be mounted.
I tried the RUU (asia) , I relocked the bootloader with windroid, the RUU failed, it sent the files, and failed at the « signature update », the code error is 155.
Everything which is cited is what i did today, I did many other operations this summer but i couldn’t precisely describe it, i just know that i did a lot, and i’m today without any other solution….thus here is my post !
Thanks for your answers !
Click to expand...
Click to collapse
Have you tried to wipe cache in fastboot? Use the command: ''fastboot erase cache''
Try to flash a Hboot 1.24 recovery after that and factory reset the phone. Then flash the rom of your choice (for 1.24 hboot of course)
So, I used the clear cache tool of the WinDroid, i flashed the TWRP 2.5.0.0 recovery for ICS, reset the phone, the same, can't clear any cache !
hugiz said:
So, I used the clear cache tool of the WinDroid, i flashed the TWRP 2.5.0.0 recovery for ICS, reset the phone, the same, can't clear any cache !
Click to expand...
Click to collapse
Don't use any tool, just do the command yourself
You sure you have hboot 1.24? For me, this looks like the typical hboot mismatch...
Sent from my HTC Desire X using XDA Premium 4 mobile app
dansou901 said:
You sure you have hboot 1.24? For me, this looks like the typical hboot mismatch...
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wait you got a point, can you show us your bootloader screen @hugiz
ok I did the command directly in cmd, it works, i flashed the recovery...same
hugiz said:
ok I did the command directly in cmd, it works, i flashed the recovery...same
Click to expand...
Click to collapse
Show me a pic of your bootloader/fastboot screen
Here is the screen of the BL !
Here is the Fastboot one...same
hugiz said:
Here is the screen of the BL !
Click to expand...
Click to collapse
Now that's interesting... i didn't know that there were different partition layouts in hboot 1.21 as well. But then at least the RUU should work...
Which CID do you have? You are sure your CID is compatible with the RUU?
cid: HTC__038
i took the RUU asia of this link http://www.androidruu.com/?developer=Proto
I guess it's the right one, because when i called htc the guy noticed immediatly that i bought it there !
Ya, indeed this phone is interesting, if we can't fixe it up, i give to xda for science purpose ! :laugh::laugh::laugh:
By the way, the RUU detect the phone and its version,1.18.XXXX but can't restore it !
hugiz said:
cid: HTC__038
i took the RUU asia of this link http://www.androidruu.com/?developer=Proto
I guess it's the right one, because when i called htc the guy noticed immediatly that i bought it there !
Ya, indeed this phone is interesting, if we can't fixe it up, i give to xda for science purpose ! :laugh::laugh::laugh:
By the way, the RUU detect the phone and its version,1.18.XXXX but can't restore it !
Click to expand...
Click to collapse
Relock your bootloader and run the ruu in the bootloader mode (not the fastboot mode)
GtrCraft said:
Relock your bootloader and run the ruu in the bootloader mode (not the fastboot mode)
Click to expand...
Click to collapse
I need an explication here, I did relock the BL ( how can i check if it's really relock ?), so, I should launch the program of the RUU while i'm in the HBOOT USB window and no the FASTBOOT USB one, right ?
hugiz said:
I need an explication here, I did relock the BL ( how can i check if it's really relock ?), so, I should launch the program of the RUU while i'm in the HBOOT USB window and no the FASTBOOT USB one, right ?
Click to expand...
Click to collapse
At the top of the bootloader screen the purple text is showing if it's locked, unlocked or relocked.
I see at the pics you send the bootloader is unlocked so do this:
1. Go to fastboot mode and do this command: ''fastboot oem lock''
2. It will restart after that but as you said it will be stuck at the htc logo so go back to the bootloader.
3. If it says RELOCKED at the top of the screen you are good to go
4. Go into bootloader/hboot mode
5. Connect the phone to the PC and run the RUU again
GtrCraft said:
At the top of the bootloader screen the purple text is showing if it's locked, unlocked or relocked.
I see at the pics you send the bootloader is unlocked so do this:
1. Go to fastboot mode and do this command: ''fastboot oem lock''
2. It will restart after that but as you said it will be stuck at the htc logo so go back to the bootloader.
3. If it says RELOCKED at the top of the screen you are good to go
4. Go into bootloader/hboot mode
5. Connect the phone to the PC and run the RUU again
Click to expand...
Click to collapse
so, i tried 3 times, i get :
(bootloader) lock sucessfully...
FAILED ( status read failes (no such file or directory))
finished. total time 1.027s
reboot, stuck logo....
hugiz said:
so, i tried 3 times, i get :
(bootloader) lock sucessfully...
FAILED ( status read failes (no such file or directory))
finished. total time 1.027s
reboot, stuck logo....
Click to expand...
Click to collapse
Then send it to a htc repaire center or use it as a paperweight
hugiz said:
cid: HTC__038
i took the RUU asia of this link http://www.androidruu.com/?developer=Proto
I guess it's the right one, because when i called htc the guy noticed immediatly that i bought it there !
Ya, indeed this phone is interesting, if we can't fixe it up, i give to xda for science purpose ! :laugh::laugh::laugh:
By the way, the RUU detect the phone and its version,1.18.XXXX but can't restore it !
Click to expand...
Click to collapse
I know the problem why the RUU is not working. Your software version is 1.18.XXXX but RUU software version is 1.14.XXXX. As you can't downgrade your phone with RUU, that won't work.
Take a look at that: http://forum.xda-developers.com/showthread.php?t=2210619&highlight=nandroid
You'll find a restorable nand backup there, which first part is incomplete, so you need to flash the second file as well like explained in the thread. Good luck!
Ok that's look interesting, i followed the step perfectly ,i put on my SD card the files of this folder
- https://drive.google.com/folderview?id=0Bytqvf8J9vnabkhxVWJJMk45dFU&usp=sharing from this link http://forum.xda-developers.com/showpost.php?p=40541546&postcount=102 which match with my CID.
I put the file as indicated in theses folders TWRP/BACKUPS/SERIALNO/2013-03-28--11-51-07
Once in twrp i can mount the sd card put nothing appear in the available backups but i can see the files in the integrated file explorer of TWRP....
You need to replace SERIALNO with the actual Serial number of your phone. If you don't know how to do that, you can do a little trick: Just do a nand backup of your current configuration, the folder with your Serial Number should then be created. After that, paste the files from the link to that folder. Also, do not forget do flash the additional file needed for CID HTC_038 to be completely stock.