Related
Hello everyone,
I think this might be my first post here.
Anyways, I have a rather depressing problem. I have my phone rooted running cm 6.1, and when i was about to go to sleep last night, it randomly started to reboot. At first i did not think anything of it because i have had my phone do this several times with cm. But then i became more concerned, it would go into a boot loop at the splash screen (htcEVO4g). Once again, i have had this happen before and i would do a wipe and reinstall the rom, but this time it did not work. I could not get into recovery. I am able to access only the boot loader.
So, i tried to install the stock pc36img. Now when i start my phone, it vibrates 5 times followed by the flashing green led. it also does this when i try to go into recovery. I am still able to get into the bootloader.
i tried doing the ruu thing, and different pc36img
I just got back from the sprint store. After waiting 3 hours, they were not able to fix it. I had told them it was rooted and everything.
If there is no way to fix it, is there at least a way i can turn s-on? That way, i can send it back to sprint.
That is odd. As far as I know, if you used unrevoked forever at any point, the only way to get s on is to flash the unrevoked s on tool, using recovery. But you don't have recovery. If I were you, I would use your computer to format your sd card to fat 32 ( after backing it up, of course) , then put a pc36img on your sd card, and try to flash again using the bootloader. You could also try putting a pc36img of amon ra recovery on your sd card, and flashing that with the bootloader. Maybe you can get recovery back, and flash a rom, or the s on tool. Hope you get it worked out.
Sent from my PC36100 using XDA App
If I were you I would try the newest pc36img.zip and if that does nothing a pc36img.zip of Amon ra. If that doesn't work go to the last link in my sig about splash screens. In that tut I give, I say how to manually run an ruu. Use the pc36img.zip with the fast boot commands from the thread. Hope this helps.
i tried formatting the sc card, and that did not do anything. How can i connect my phone to adb?
marzban123 said:
i tried formatting the sc card, and that did not do anything. How can i connect my phone to adb?
Click to expand...
Click to collapse
Just Download the android SDK and follow the steps. There are some pretty excellent tutorials on XDA and other sites that will walk you through the whole process.
I want to weigh in here for just a moment. There is no way your phone is completely botched, unless it has experienced physical damage (including any overheating). By the way, you running any SBC kernels?
I would look into learning your way around ADB, I think it's a necessary tool for anyone who wants to flash and alter their android phones, unfortunately things have become so easy that many out there haven't had to learn these tools and how to use them.
Seriously, go mess with ADB, I am sure you can get it running again.
Some good info here http://forum.xda-developers.com/showthread.php?t=865204 on using ADB and other methods that may help you.
marzban123 said:
I had told them it was rooted and everything.
Click to expand...
Click to collapse
ouch... they should give you new phone for being honest
ok, so i connect the phone, and in device manager i see "Android Bootloader Interface"
i opened up command prompt, and tried to push a file to the phone and i got this
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Andrew>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb push PC36IMG.zip /sdcard/
error: device not found
C:\android-sdk-windows\tools>
you sure your usb cable is good? id run the RUU to go back to stock & unroot you. then start over from scratch.
i just tried a different cable. No luck
I have already tried a stock ruu, that still does not let me get into recovery or turn s-on
your sorta up ****s creek here if you told sprint you rooted. they probably flagged your account.
is your sd card good? try another, fully formatted for fat32 only. then try the s-on flashable zip. that's all i can think of for you to do. if you need another evo, im sure you can pick one up for cheap on craigslist.
nobody ever took my information
Is there an s-on flashable zip?!?! where can i find it? i have searched before with no luck
first of all, adb doesnt work in bootlaoder. select fastboot, then plug in. you should see fastboot usb come up on the phone. now try using fastboot commands instead. not sure where to download fastboot commands. i have the mac ones if you need them. then do this
with the pc36img.zip ON YOUR COMPUTER:
after flashing s-on tool http://downloads.unrevoked.com/forever/current/unrevoked-forever-son.zip
fastboot oem rebootRUU
you should see a black screen with silver htc lettering
fastboot flash zip pc36img.zip (do this command with the pc36img.zip in the same directory as fastboot)
you should see a green bar appear under htc and a bunch of lines on the comp. make sure it successfully completes, then type:
fastboot reboot
done.
but make triple sure you are s-on first.
thank you very much, that makes things ALOT clearer.
I am still a huge noob to this stuff so i need to ask you some silly questions:
i found out the commands for fastboot in a wiki,
http://wiki.cyanogenmod.com/index.php?title=Fastboot
but i dont really understand how to use them. can someone please give me a little clarification.
well, first check your sdk and see if you have fastboot.exe. i know the mac one doesnt come with it. if you dont google it. if you do, cd to the directory (hold shift and right click in the folder. select open command prompt here) and boot phone into fastboot. make sure it is in fastboot usb mode. then do the commands.
i have the fast boot exe and i am in command prompt.
when i say i am a noob, i really mean it.
for example, when i try a simple command like checking the serial number, i will input
c:\android-sdk-windows\tools>fastboot <-s>
or
c:\android-sdk-windows\tools>fastboot -s
or
c:\android-sdk-windows\tools>fastboot <serial number>
it says
the syntax of the command is incorrect.
i really dont know how to use this stuff
ok forget the last post,
i figured that out
what partition do i want to flash and with what file?
No partition just use the pc36img.zip in ruin more and type fastboot flash zip pc36img.zip.
Sent from my PC36100
C:\android-sdk-windows\tools>fastboot flash zip PC36IMG.zip
sending 'zip' (171727 KB)... OKAY [ 30.475s]
writing 'zip'... FAILED (remote: not allowed)
finished. total time: 30.477s
C:\android-sdk-windows\tools>
Click to expand...
Click to collapse
i researched the "(remote: not allowed)" error message, and everyone says its cause when the phone is set to s-on. However, on my phone it says s-off.
what the heck?
Hey guys,
I'm in desperate need of some help here.
I tried to install the latest build of Coredroid today, installed all the way to start up screen, then saw safe mode sign.
Rebooted phone.
Straight to bootloader (Android skateboarder page).
In bootloader, volume keys do NOT work, thus, I cannot navigate.
I tried several things, my phone will NOT allow me to boot into Clockwork Recovery, no matter what I do.
I have tried renaming several different roms to PD98IMG and then rebooting, bootloader loads the file then takes me here:
Parsing...[SD ZIP]
[1] BOOTLOADER
[2] BOOT
[3] RECOVERY
[4] SYSTEM
[5] SPLASH1
[6] SPLASH2
[7] USERDATA
[8] TP
[9] TP
[10] TP
[11] TP
[12] RADIO_V2
[13] RADIO_CUST
I can't select any of these since my volume keys are unresponsive.
Just so you know, the details at the top of my bootloader screen are as follows:
ACE PVT ENG S-OFF
HBOOT-0.85.2007 (PD981000)
MICROP-0438
RADIO-26.03.02.26
Can you guys please offer some suggestions?
I'm in such desperate need of help!
Kind regards,
- Ric
My volume keys seem to work in boot loader. Strange that it isn't working for you.
What you can do is open up cmd and use adb shell reboot recovery It should reboot into recovery for you.
There's a fair few threads where people report similar things, although there doesn't seem to be a conclusive solution.
I just tried an adb shell reboot recovery in boot loader and it couldn't find the device. Will try a few other things and get back to you.
The command you want is 'fastboot reboot recovery'
Sent from my HTC Vision using XDA Premium App
Mate I seriously appreciate your help!
Someone suggested downloading a RUU but that didn't work for me either?
I kept getting error 170 (usb connection)
philicibine said:
The command you want is 'fastboot reboot recovery'
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Sorry I don't know what this means!
Plug ur phone into ur pc while in bootloader mode... and then on ur pc command prompt type fastboot reboot recovery
Easy
Sent from my HTC Vision using XDA Premium App
philicibine said:
Plug ur phone into ur pc while in bootloader mode... and then on ur pc command prompt type fastboot reboot recovery
Easy
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
So I typed that and received the message:
'fastboot' is not recognized as an internal or external command, operable program or batch file
Could you please elaborate on that?
Kind regards,
- Ric
You have the android sdk?
Sent from my HTC Vision using XDA Premium App
philicibine said:
You have the android sdk?
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I've got it downloading the packages now, am I heading in the right direction?
Kind regards,
- Ric
Yes...
You need to get adb and fastboot working. There are plenty of tutorials on here. They both come with the sdk.
Once you have fastboot working its just a case of using that command.
I would use an ruu as a last resort. I don't know about your phone.. but with mine, I have to switch s-on first. So makes it complicated.
Hope u get it sorted. Simply by having bootloader on your phone it means you are recoverable.
Sent from my HTC Vision using XDA Premium App
philicibine said:
Yes...
You need to get adb and fastboot working. There are plenty of tutorials on here. They both come with the sdk.
Once you have fastboot working its just a case of using that command.
I would use an ruu as a last resort. I don't know about your phone.. but with mine, I have to switch s-on first. So makes it complicated.
Hope u get it sorted. Simply by having bootloader on your phone it means you are recoverable.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Ok, well thanks for the support.
I'll see what I can do.
Hey, So I think I've figured out how to fix your problem. Is your phone unbranded? And the RUU file you have. What steps did you try to get that to work? From what I've read around the forums you can either go into the bootloader. Plug in your USB, and it should come up something like "FASTBOOT USB" on the screen to confirm it. Run the exe and it should take you through the steps. You said you got an error so im assuming thats the steps you tried already.
Failing that, have you got a card reader? If so, you can drop an RUU's pb99img file onto the root of the sd card as Hboot looks for this file when it loads. This will then performs the same action without the need for USB connectivity.
So it's just "pb99img.zip" so delete everything between pb99img and .zip from the filename.
philicibine said:
Yes...
You need to get adb and fastboot working. There are plenty of tutorials on here. They both come with the sdk.
Once you have fastboot working its just a case of using that command.
I would use an ruu as a last resort. I don't know about your phone.. but with mine, I have to switch s-on first. So makes it complicated.
Hope u get it sorted. Simply by having bootloader on your phone it means you are recoverable.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Hello mate, got everything downloaded.
fastboot reboot recovery
Doesn't do a great deal.
After I type it and press enter, the command prompt displays a list of commands and options.
Something along the lines of:
usage: fastboot [ <option> ] <command>
update <filename>
flashall
flash <partition> [ <filename> ]
erase <partition>
and so on...
There doesn't appear to be any interaction with the device itself...
usmaanali said:
Hey, So I think I've figured out how to fix your problem. Is your phone unbranded? And the RUU file you have. What steps did you try to get that to work? From what I've read around the forums you can either go into the bootloader. Plug in your USB, and it should come up something like "FASTBOOT USB" on the screen to confirm it. Run the exe and it should take you through the steps. You said you got an error so im assuming thats the steps you tried already.
Failing that, have you got a card reader? If so, you can drop an RUU's pb99img file onto the root of the sd card as Hboot looks for this file when it loads. This will then performs the same action without the need for USB connectivity.
So it's just "pb99img.zip" so delete everything between pb99img and .zip from the filename.
Click to expand...
Click to collapse
Yes, tried the first part, the RUU didn't detect my phone.
With the second part, how do I find the pb99img file?
Can I just download one?
Could you please point me in the right direction?
Kind regards,
- Ric
I'm still no further forward.
Could you please point me in the direction of one of the tutorials you're talking about?
I have searched extensively but I haven't found anything that seems relevant.
Desperately need my phone!
Kind regards,
- Ric
The RUU file you have, It should be about 150mb or something right? and make sure it is the correct RUU file. It should be zipped up and just rename it so it is "pb99img.zip" and make sure not to put it in any sort of folders onto your sd card.
I'm assuming you have the RUU already as you said you tried it already. If not try this link: http://forum.xda-developers.com/showthread.php?t=824357
usmaanali said:
The RUU file you have, It should be about 150mb or something right? and make sure it is the correct RUU file. It should be zipped up and just rename it so it is "pb99img.zip" and make sure not to put it in any sort of folders onto your sd card.
I'm assuming you have the RUU already as you said you tried it already. If not try this link: http://forum.xda-developers.com/showthread.php?t=824357
Click to expand...
Click to collapse
the rom.zip found in an RUU is usually 250-290mb in size depending on carrier addons. This is what is renamed to PD98IMG.zip
AGAIN, PD98IMG
And why hasnt anyone asked him if HTC Sync has been installed?
If you plug in your USB cable while your DHD is powered off, does it go into offmode charging? (does the charging led turn on after a few seconds?)
If so, you should be able to "adb shell" into your phone
Hello, I have like eight hours of continuous searching for solve this problem.
I installed like two months ago the Android Revolutionary HD 6.1.5 ROM, i did S-off, Radio-off, Root, etc, following the tutorials of XDA. But i installed the actualization of ARHD 6.2.0 and it works very nice but one day later when i was talking by the phone it stopped, then sense was not responding, and it finally restarted alone.
The big problem is it was only showing the HTC logo and then the screen puts black.
I get into HBoot and it searches for PD98IMG.zip
i putted the PD98IMG.zip in the card and it says this:
- Sd checking...
Loading...[PD98DIAG.zip]
No image!
Loading...[PD98DIAG.nhb]
No image or wrong image!
Loading...[PD98img.zip]
I say yes and it shows:
- Image unzipping fail!
Update Fail!
Press <POWER> to reboot
I tried a lot of RUU`s, like 13 and i can´t find one who works, the only who was acepted was ono withe the recovery only. With USB it does not work either.
I sent it to the company who sold me it and they have no idea about...
I hope you can help me, i am a little dissapointed, because i tried all the RUU`s what i founded in the web.
Thank you very much, Freesoft.
Freesoft64 said:
Hello, I have like eight hours of continuous searching for solve this problem.
I installed like two months ago the Android Revolutionary HD 6.1.5 ROM, i did S-off, Radio-off, Root, etc, following the tutorials of XDA. But i installed the actualization of ARHD 6.2.0 and it works very nice but one day later when i was talking by the phone it stopped, then sense was not responding, and it finally restarted alone.
The big problem is it was only showing the HTC logo and then the screen puts black.
I get into HBoot and it searches for PD98IMG.zip
i putted the PD98IMG.zip in the card and it says this:
- Sd checking...
Loading...[PD98DIAG.zip]
No image!
Loading...[PD98DIAG.nhb]
No image or wrong image!
Loading...[PD98img.zip]
I say yes and it shows:
- Image unzipping fail!
Update Fail!
Press <POWER> to reboot
I tried a lot of RUU`s, like 13 and i can´t find one who works, the only who was acepted was ono withe the recovery only. With USB it does not work either.
I sent it to the company who sold me it and they have no idea about...
I hope you can help me, i am a little dissapointed, because i tried all the RUU`s what i founded in the web.
Thank you very much, Freesoft.
Click to expand...
Click to collapse
Try to go into recovery mode. What exactly is the problem. If it is not booting in...go to recovery and select fix permissions... this will solve any problems. If not try to install a rom with full wipe and reboot. If you flash a PD98IMG.zip then once again you need to root, S OFF, etc etc....
Stop what you are doing before you brick your phone.
The PD98 error you are getting happens to all rooted DHD's, and is nothing to worry about (delete it from your sd card). RUU's are for stock devices, or for returning to stock.
Check to make sure you haven't screwed up your root access, and flash a ROM .zip file from the developers thread (in recovery, from your sd card). And always check the checksum before flashing.
Sent from The App that Time Forgot.
JagDave said:
Stop what you are doing before you brick your phone.
The PD98 error you are getting happens to all rooted DHD's, and is nothing to worry about (delete it from your sd card). RUU's are for stock devices, or for returning to stock.
Check to make sure you haven't screwed up your root access, and flash a ROM .zip file from the developers thread (in recovery, from your sd card). And always check the checksum before flashing.
Sent from The App that Time Forgot.
Click to expand...
Click to collapse
Well, actualy, i can`t get into Recovery, it reboots and the screen turns black, the only thing what the phone admits is PD98IMG.zip.
Thank you very much for responding!
Delete that file from your SD card, and check if you can get into recovery. If yes, download superWIPE for ARHD, and ARHD rom and install it ( it's different base i think, so you have to superWipe it )
PD98IMG.zip is the radio, if that's what you need they can all be found here:
http://forum.xda-developers.com/showthread.php?t=996630
Might be worth flashing the latest and seeing if your phone behaves enough afterwards to let you get into recovery.
I take it you are trying from bootloader?
Also does your computer recognize the phone on usb?
Sent from The App that Time Forgot.
Sounds to me your Recovery has an error.
Download and extract Android Flasher http://forum.xda-developers.com/showthread.php?t=794638
Boot into Bootloader & select fastboot
Use AndroidFlasher to install a new Recovery image.
Link to my copy of of the previous 4ext Touch recovery, so it should work.
Extract the image to wherever you extracted AndroidFlasher and make sure you select 'already in fastboot' prior to flashing.
Then you should be able to get into Recovery. Full wipe, install ROM, etc.
Hope this solves your problem.
JagDave said:
Sounds to me your Recovery has an error.
Download and extract Android Flasher http://forum.xda-developers.com/showthread.php?t=794638
Boot into Bootloader & select fastboot
Use AndroidFlasher to install a new Recovery image.
Link to my copy of of the previous 4ext Touch recovery, so it should work.
Extract the image to wherever you extracted AndroidFlasher and make sure you select 'already in fastboot' prior to flashing.
Then you should be able to get into Recovery. Full wipe, install ROM, etc.
Hope this solves your problem.
Click to expand...
Click to collapse
I am trying all this and i think it will work, the problem is my phone is "SHIP S-OFF"
But i don`t know hot to change from Ship to ENG...
Thank you very much for the answer, from now in one week i think my DHD will work again
If memory serves, you only need Eng to change the radio.
But don't quote me on that
Sent from The App that Time Forgot.
I have tried this http://forum.xda-developers.com/showthread.php?t=1396253
The PD98IMG.zip worked, so i am glad my desire is not bricked yet.
I still not having access to recovery, my phone is SHIP S-OFF not ENG S-OFF and i can`t change the Recovery, i can`t install the SDK drivers for bootloader.
I tried too with Android Flasher, and there doesn`t work because my phone is not ENG S-OFF.
My questions are this: how i can change now to ENG S-OFF?
What else i can do for revive the Desire HD?
Thank a lot for responding this post, i don`t know what i`ll do without all of you!
Personally I see no reason to Eng soff. You can still flash radios and recoveries with just regular soff. Just its done in a different way.
In that thread you posted their is a link for cwr in a pd98img. Just follow the directions I wrote.(its the first section)
But if you are set on getting Eng soff in the dev section you can use jkoljo tool.
Your second question confuses me. You said your phone is now working so what do you mean by reviving your phone?
Well, i tried ADB, the problem now is when i installed the drivers, in the command prompt i cant find my phone.
I was trying with this:
C:\adb devices
List of devices attached
In Device Manager it appairs like: Android Phone>Android ADB Interface
What i can do now?
I know I'm a little annoying, but I will really appreciate your help if we make it work!
Anyone can help with ADB with desire hd?
Well to be able to use command prompt on your computers first off would be to add the adb path which is normally C:\Program Files (x86)\Android\android-sdk\platform-tools or in C:\Program Files (x86)\Android\android-sdk\tools
Then you'll be able to use adb commands.
if not while in command prompt, just use the cd command to get in that directory so you can use the adb.exe
per exemple;
cd C:\Program Files (x86)\Android\android-sdk\tools
then you'll be able to use commands has
adb push [the file which should be in the same place] /data/local/tmp
Then if you just want to run command on your cell interface just write
adb shell
if you're in root you should start to write beside a #
it would look
<C:\[path]>adb shell
# [here you'll run command on your cellphone]
because if you run in command prompt right away
<C:\>adb device
without having the file to get the adb.exe
But as for using adb shell, if your device is connected and activated in debugged mode you'll be fine.
earthbrother said:
Well to be able to use command prompt on your computers first off would be to add the adb path which is normally C:\Program Files (x86)\Android\android-sdk\platform-tools or in C:\Program Files (x86)\Android\android-sdk\tools
Then you'll be able to use adb commands.
if not while in command prompt, just use the cd command to get in that directory so you can use the adb.exe
per exemple;
cd C:\Program Files (x86)\Android\android-sdk\tools
then you'll be able to use commands has
adb push [the file which should be in the same place] /data/local/tmp
Then if you just want to run command on your cell interface just write
adb shell
if you're in root you should start to write beside a #
it would look
<C:\[path]>adb shell
# [here you'll run command on your cellphone]
because if you run in command prompt right away
<C:\>adb device
without having the file to get the adb.exe
But as for using adb shell, if your device is connected and activated in debugged mode you'll be fine.
Click to expand...
Click to collapse
I did that, it doesn`t work because it says "error: device not found" i tried reinstalling many times the ADB drivers and another few with the path file, no results. With "adb devices" it says "list of devices attached" then, nothing.
I am really gratefull with all your answers, i hope we can made it work
I have a question more, it`s posible to put it in "debugging mode" from HBOOT?
Thanks a lot!
So, nobody can help me? that who help me will be rewarded!
You said only the recovery pd98 works. Reflash it. After it reboot and hangs take out battery and SD card. Reinsert battery and enter boot. Wait for it to scan, then reinsert sdcard and enter recovery. Wipe and reflash a rom or backup
Edit - still confused, from your pm you suggested that your dhd doesn't work? I need a simple yes it boots or doesn't, before we can go anywhere
Sent from my Desire HD using XDA App
my vision:
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1010000)
MICROP-0425
RADIO-26.10.04.12_M
eMMC-boot
Sep 8 2010, 15:56:38
please a little help...I am trying to upgrade the radio on my phone so that I can use wifi calling.
I tried the PC10IMG zip on the root of sdcard and that will not work...now I am trying to manually push from adb.
I followed instructions for the radio.img perfectly.
I put in fastboot devices in terminal and the device is recognized but when i try to flash the radio it says," error: cannot load 'radio.img'"
current radio: Vision_Radio_12.57.60.25_26.10.04.12
wanted radio: Vision_Radio_12.62.60.27_26.13.04.19
maybe my sim card is too old please help...and know that I posted this in the correct thread just wasnt getting any views because its such an old thread. Thanks!!!
I'm not 100% sure but I think you're getting that error because you don't have an ENG bootloader (it says HBOOT and not ENG-HBOOT), which means you shouldn't be allowed to flash anything with fastboot commands.
I am also trying to upgrade my radio (kind of, actually it's the rcdata.img) and fastboot just isn't detecting my PC10IMG.zip
You need to have engineering bootloader in order to use fastboot flash. Is weird that it isn't picking it up from the root of the SD card. Are you sure in the bootloader you selected the first option with the power button it should immediately begin to load and detect
Sent from my Xoom using xda app-developers app
Ill take some pictures in the morning and look up the guide that I used to flash my engineering bootloader
Sent from my Xoom using xda app-developers app
I went on #g2root and a nice guy named skorgon helped me out with flashing PC10IMG.zip even if your bootloader does not detect it.
Just open a command prompt and change directory to where you have PC10IMG.zip, then
Code:
fastboot oem rebootRUU
your phone will reboot into RUU mode and show an HTC logo on a black background
Code:
fastboot flash zip PC10IMG.zip
it will show a progress bar on both the phone and the command prompt will give a text progress. if you see "error: cannot load 'PC10IMG.zip'", make sure your command prompt is in the same directory as the actual PC10IMG.zip file (using Win7, hold shift, right click, then choose "Open command window here")!
when it's done, just do
Code:
fastboot reboot
done!
c00ller said:
I went on #g2root and a nice guy named skorgon helped me out with flashing PC10IMG.zip even if your bootloader does not detect it.
Just open a command prompt and change directory to where you have PC10IMG.zip, then
Code:
fastboot oem rebootRUU
your phone will reboot into RUU mode and show an HTC logo on a black background
Code:
fastboot flash zip PC10IMG.zip
it will show a progress bar on both the phone and the command prompt will give a text progress. if you see "error: cannot load 'PC10IMG.zip'", make sure your command prompt is in the same directory as the actual PC10IMG.zip file (using Win7, hold shift, right click, then choose "Open command window here")!
when it's done, just do
Code:
fastboot reboot
done!
Click to expand...
Click to collapse
Yo thanks everyone...especially C00ler...def gave me just the information I needed...I love when this stuff happens I remember once again why I visit xda everyday, such a helpful community...thanks guys!!
Got the radio, got the eng hboot and I have my wifi calling working!!!
neither of my desire z's say ENG-HBOOT...
so what have i done wrong?
i followed this guide when rooting http://wiki.cyanogenmod.com/wiki/HTC_Desire_Z:_Rooting
if you followed that guide you should have an engineering hboot, without know exactly what you did I can't say why you don't have it. are you rooted and have s-off? do you have a custom recovery?
if so not a huge deal but I tend to use fastboot a lot and would still recommened getting the eng hboot
Sent from my HTC Vision using xda premium
I have ENG S-OFF as it is in the post at the top of the thread.... I thought that was the engineering hboot?
The posts below are talking about eng-hboot on the hboot screen?
you have an engineering bootloader. spl/hboot/bootloader are referring to the same thing by the way
Sent from my HTC Vision using xda premium
whoop, above two posts are right .. i somehow missed the ENG S-OFF bit
if the error message was "error: cannot load 'radio.img'" then perhaps real problem was that the command line directory wasn't the place with the radio.img
demkantor said:
you have an engineering bootloader. spl/hboot/bootloader are referring to the same thing by the way
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
i think the post above clears up my confusion
My confusion came because it appears I have an older version of the eng bootloader 0.76.2000 so I was confused when I saw the op's 0.89.xxxx version.
Sent from my HTC Vision using xda app-developers app
Boom found the discrepancy.
Desire Z's bootloader is 0.89.xxxx
While my
Tmobile g2 is: 0.72.xxxx
I guess I should have done a little bit more research beforehand.
Keep rocking xda
Sent from my HTC Vision using xda app-developers app
Yesterday I had the excellent idea of rooting my phone and installing a custom ROM. The process was quite easy though it took me like 2 hours. After I was done I found that I didn't really like the Lineage OS on my M8 as it was draining my battery way too fast. So I decided to go back. This is where the problems began. Since being a total noob when it comes to rooting and flashing on Android I had no idea I had to make a backup of my OS(only did one of my data using HTC Sync Manager). I was able to find one online in the end. But when I wanted to update OTA to 6.1.0 it just boots into Recovery Mode. After some research I found out that I also have to flash a stock recovery file. I allegedly did that using a tool I found online (One M8 All in One Kit 2.0). But still I am unable to update OTA. I just want to go back to Marshmallow.
Would really appreciate some help here guys
Thanks.
Tupi311 said:
Yesterday I had the excellent idea of rooting my phone and installing a custom ROM. The process was quite easy though it took me like 2 hours. After I was done I found that I didn't really like the Lineage OS on my M8 as it was draining my battery way too fast. So I decided to go back. This is where the problems began. Since being a total noob when it comes to rooting and flashing on Android I had no idea I had to make a backup of my OS(only did one of my data using HTC Sync Manager). I was able to find one online in the end. But when I wanted to update OTA to 6.1.0 it just boots into Recovery Mode. After some research I found out that I also have to flash a stock recovery file. I allegedly did that using a tool I found online (One M8 All in One Kit 2.0). But still I am unable to update OTA. I just want to go back to Marshmallow.
Would really appreciate some help here guys
Thanks.
Click to expand...
Click to collapse
You could just run an RUU to get back to stock, since you already flashed the stock backup and have lost data now.
What does it say next to "OS" in your bootloader? With that information I can link you to the proper RUU
xunholyx said:
You could just run an RUU to get back to stock, since you already flashed the stock backup and have lost data now.
What does it say next to "OS" in your bootloader? With that information I can link you to the proper RUU
Click to expand...
Click to collapse
6.12.401.4
I don't quite understand how this RUU works. Will it still say in bootloader "Software status:Modified" after I do this? And will I have to unroot it again or how does it work? Cause it still says Unlocked in bootloader.
Tupi311 said:
6.12.401.4
I don't quite understand how this RUU works. Will it still say in bootloader "Software status:Modified" after I do this? And will I have to unroot it again or how does it work? Cause it still says Unlocked in bootloader.
Click to expand...
Click to collapse
The RUU will take you back to stock unrooted.
I forgot to ask if it said S-On or S-Off in your bootloader. I'll give full instructions for both.
Download this RUU.zip and place it into your adb/fastboot folder
Boot to bootloader and plug your phone into your PC, then get into fastboot
If you are S-On, enter fastboot oem lock That will relock your bootloader. If you are S-Off you can skip this step
Then: fastboot oem rebootRUU wait until the phone boots to a black screen with HTC on it
then fastboot flash zip **drag and drop the RUU.zip here**
When the flash is done, fastboot reboot and you'll be back to stock, unrooted
xunholyx said:
The RUU will take you back to stock unrooted.
I forgot to ask if it said S-On or S-Off in your bootloader. I'll give full instructions for both.
Download this RUU.zip and place it into your adb/fastboot folder
Boot to bootloader and plug your phone into your PC, then get into fastboot
If you are S-On, enter fastboot oem lock That will relock your bootloader. If you are S-Off you can skip this step
Then: fastboot oem rebootRUU wait until the phone boots to a black screen with HTC on it
then fastboot flash zip **drag and drop the RUU.zip here**
When the flash is done, fastboot reboot and you'll be back to stock, unrooted
Click to expand...
Click to collapse
This is exactly what I was talking about. I don't understand how to do those "bolded" instructions. Does it have something to do with the Android SDK? I know I read something.
I am on S-ON btw.
Tupi311 said:
This is exactly what I was talking about. I don't understand how to do those "bolded" instructions. Does it have something to do with the Android SDK? I know I read something.
I am on S-ON btw.
Click to expand...
Click to collapse
So there is the main problem with toolkits. I never use them and never recommend them. Reason being: they shortcut the learning process, and teach you just enough to get into trouble. Then you are stuck with no idea how to recover.
Knowing how to use fastboot (at least on a basic level) is absolutely mandatory in order to unlock the bootloader, and flash custom recovery (for the purpose or root or custom ROM). The manufacturers set it up this way, for a reason. Essentially, if a user doesn't know how to use fastboot, they have no business unlocking the bootloader. The makers of the toolkits bypass this requirement with the intent to make it "easier" for folks to root/ flash custom ROM (the toolkit issued fastboot commands, whether you know it or not). But as already mentioned, it's not a good idea to do that.
I don't blame you. You only know what you know, and we all were n00bs at some point, and had to start somewhere. But my advice to you, would be to learn the basics of what fastboot is about, and how to use it. Plus, there is a lot of nuance here. You actually have to use htc_fastboot to flash the RUU (the "generic" Google fastboot can't handle the large file size). You can get it (as well as the RUU) from the following thread:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
From there, you need to open the command prompt from whatever folder/directory htc_fastboot.exe or fastboot.exe (respectively) are located. There is a shortcut for doing this:
1) Open folder in Windows, where fastboot.exe (htc_fastboot.exe) is located. Different fastboot installers will install it to different places, so you will have to find it yourself.
2) Hover mouse over the folder, press Shift+Right mouse button. This will open a menu, from which you want to select "Open command window here"
3) The command prompt window will open, and that is where you want to type your fastboot commands.
Another note (and I know this will probably be confusing), I think that you can use htc_fastboot for all the fastboot commands (no need to flip flop between htc_fastboot and fastboot). You just have to use "htc_" before all the fastboot commands. For instance:
htc_fastboot oem lock
redpoint73 said:
So there is the main problem with toolkits. I never use them and never recommend them. Reason being: they shortcut the learning process, and teach you just enough to get into trouble. Then you are stuck with no idea how to recover.
Knowing how to use fastboot (at least on a basic level) is absolutely mandatory in order to unlock the bootloader, and flash custom recovery (for the purpose or root or custom ROM). The manufacturers set it up this way, for a reason. Essentially, if a user doesn't know how to use fastboot, they have no business unlocking the bootloader. The makers of the toolkits bypass this requirement with the intent to make it "easier" for folks to root/ flash custom ROM (the toolkit issued fastboot commands, whether you know it or not). But as already mentioned, it's not a good idea to do that.
I don't blame you. You only know what you know, and we all were n00bs at some point, and had to start somewhere. But my advice to you, would be to learn the basics of what fastboot is about, and how to use it. Plus, there is a lot of nuance here. You actually have to use htc_fastboot to flash the RUU (the "generic" Google fastboot can't handle the large file size). You can get it (as well as the RUU) from the following thread:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
From there, you need to open the command prompt from whatever folder/directory htc_fastboot.exe or fastboot.exe (respectively) are located. There is a shortcut for doing this:
1) Open folder in Windows, where fastboot.exe (htc_fastboot.exe) is located. Different fastboot installers will install it to different places, so you will have to find it yourself.
2) Hover mouse over the folder, press Shift+Right mouse button. This will open a menu, from which you want to select "Open command window here"
3) The command prompt window will open, and that is where you want to type your fastboot commands.
Another note (and I know this will probably be confusing), I think that you can use htc_fastboot for all the fastboot commands (no need to flip flop between htc_fastboot and fastboot). You just have to use "htc_" before all the fastboot commands. For instance:
htc_fastboot oem lock
Click to expand...
Click to collapse
I followed those steps but when I tried and flash it it gave me this error "target reported max download size of 1826418688 bytes" and I found no real solution to this online.
On a side note I already had the HTC Sync manager installed and I used it to backup some stuff so I can't uninstall it(according to the guide I have to uninstall it, but I guess that's just a suggestion since uninstalling it shouldn't interfere).
Though I feel like I'm close to succeeding.
Tupi311 said:
I followed those steps but when I tried and flash it it gave me this error "target reported max download size of 1826418688 bytes" and I found no real solution to this online.
Click to expand...
Click to collapse
Did you use htc_fastboot? The file size error is usually due to using the wrong fastboot (you need to use htc_fastboot, as the "generic" fastboot can't handle the file size).
Tupi311 said:
On a side note I already had the HTC Sync manager installed and I used it to backup some stuff so I can't uninstall it(according to the guide I have to uninstall it, but I guess that's just a suggestion since uninstalling it shouldn't interfere).
Click to expand...
Click to collapse
I've left HTC Sync installed without any issues. Like you said, it's mostly a suggestion.
Also, just a suggestion:but I would recommend to refrain from quoting someone else's long post (like you quoted my last post). I know it is the default when replying, to include the quote. But just delete what you aren't directly replying to (quote few lines at most) to avoid cluttering up the thread with redundant text.
redpoint73 said:
Did you use htc_fastboot? The file size error is usually due to using the wrong fastboot (you need to use htc_fastboot, as the "generic" fastboot can't handle the file size).
Click to expand...
Click to collapse
Seems like my pc didn't like that I was using those commands and I had to use \.htc_fastboot . It's all good now. Thank you very much. Have a good day.