Need Help nothing will flash model id error - EVO 4G Q&A, Help & Troubleshooting

I installed the eng hboot .76 on an old evo that had the latest hboot 2.16. I wiped everything using fastboot command and had plan on restore everything to stock. but now nothing I will do will flash. I keep getting the "model id Error" every time I try to flash using the RUU utility and through hboot. I tried even using fastboot commands to flash the system.img but it says it's too large to flash through remote. I tried updating the hboot back to 2.16 but gives me the same error. Anyone has any suggestions? What is causing the evo to keep thinking I have the wrong model? thanks

I've never had that happen but make sure you have the right RUU for our phone also make sure you have the correct radios combo for the RUU your flashing.

linsalata28 said:
I've never had that happen but make sure you have the right RUU for our phone also make sure you have the correct radios combo for the RUU your flashing.
Click to expand...
Click to collapse
Unfortunately that didn't help either. I used a RUU image with the exact same radio version and still gives me the model id error
edit: Ok after some more research I found what my problem is but I have not found the solution. The problem is that I flashed an engineering hboot on an evo with the new partition cause other's that had done it are getting the same error messages I am. But I still haven't seen any of them finding a solution to get the evo working again. If anyone has any insight on this issue please help.

I don't think it is fixable now. Look in dev for RA like 3.08 gnm recovery. If you can get that to flash, then u may be able to use it to rewrite the blocks. Read about it in its thread
Support TrevE! Fuh Q CIQ!

I'm just stumped on why you would want to downgrade the Hboot?

{ParanoiA} said:
I don't think it is fixable now. Look in dev for RA like 3.08 gnm recovery. If you can get that to flash, then u may be able to use it to rewrite the blocks. Read about it in its thread
Support TrevE! Fuh Q CIQ!
Click to expand...
Click to collapse
Thanks that didn't seem to work either guess i'm out of luck. The reason I downgraded the Hboot was because I was replacing a broken evo with a blacklisted evo and this was a fast method to do that. But I forgot about the issue with the new hardware version.

HipKat said:
I'm just stumped on why you would want to downgrade the Hboot?
Click to expand...
Click to collapse
HipKat, I downgraded my HBOOT so I could flash a custom splash screen, just sayin'.
Sent from my PC36100 using XDA App

Well, I'm still trying to fix it so I'm going to post my progress just in case someone has any new ideas. First off I did make some progress as I no longer get the model id error and was able to start the flashing process now. But the process never finishes successfully. I started taking a different approach on how to fix the problem. Instead of looking for an EVO fix I research all the fastboot commands and what they can do. I managed to figure out that some how the model ID on my evo was removed and replace with a symbol that looks like a *. This was the cause of my error because it was comparing this to the mode id in the roms and failing. I found the fastboot command to update the model id and was actually able to start the flashing process. But 3/4 into the flashing it failed and gave me an error of "51 partition update fail". Now I can't get into the bootloader anymore and I only see the HTC Logo with 4 Exclamation marks at the corners. I still am able to execute fastboot commands so I'm continuing the research. So hopefully someone has a fix for this new error. thanks

Related

Please tell me i didnt brick my phone

tried to run the file located here http://forum.xda-developers.com/showthread.php?t=685835 well during the install it gave me an error saying the file is corupted or can not be opened. well know my phone only display a black screen with htc logo with ! marks inside of triangles in each corrner, i cant get to hboot or recovery. what do i do
You're probably not bricked but I wouldn't know what to do in your situation. I'll leave that for someone more intelligent than I. What possessed you to try and run that file?
it was supposed to take me back to stock
How did you root your phone? did u use unrevoked?
Bslydem said:
it was supposed to take me back to stock
Click to expand...
Click to collapse
That software version in that file is waaaaay outdated. You can try running a RUU from your PC but I'm not sure if it will find your phone when it's in that state. It's worth a shot though.
Download the latest RUU from here, and run it on your computer. Follow the on screen directions and cross your fingers.
he has to have s-on or it wont work right. as far as i know
_MetalHead_ said:
That software version in that file is waaaaay outdated. You can try running a RUU from your PC but I'm not sure if it will find your phone when it's in that state. It's worth a shot though.
Download the latest RUU from here, and run it on your computer. Follow the on screen directions and cross your fingers.
Click to expand...
Click to collapse
4g evo said:
he has to have s-on or it wont work right. as far as i know
Click to expand...
Click to collapse
You could be right but it's worth a shot either way.
yea anything is worth a shot =] iv been there lol
_MetalHead_ said:
You could be right but it's worth a shot either way.
Click to expand...
Click to collapse
yeah i rooted my phone using unrevoked
This happened to me trying to root a hardware 004 Evo, just run the ruu to fix
sent from my Evo on Americans REAL largest 4G network
every ruu i try to run gives me the same error error code 110 unable to open files or its corrupted but it doesn't error until after it deletes everything could it because of the non stock kernel i had it dont understand why ruus wont work ive try like 5 and i always get the same error
you have to flash unrevokedforever s-on before RUU will work.
Bslydem said:
every ruu i try to run gives me the same error error code 110 unable to open files or its corrupted but it doesn't error until after it deletes everything
Click to expand...
Click to collapse
to run that i need custom recovery
You can not get into hboot? If you can, take a look and see if it says S-ON or S-OFF.
If its S-OFF, flash a custom recovery. Then use the S-ON Tool. Then flash the updated RUU.
If it says S-ON. Flash the latest RUU.
If it still doesn't work, come back and I'll try to see if theres something else you can do.
For future reference, make sure you always use the latest info. Don't just flash anything cause it says UNROOT WITH THIS. Make sure its the latest version/method/etc.

[Q] Can I flash PC36IMG.zip from recovery to unroot?

Can I flash PC36IMG.zip from recovery like any other ROM in order to unroot?
HBOOT doesn't recognize PC36IMG.zip and the RUU doesn't recognize my phone. Need to unroot to take my phone in.
Thanks
pipefitter said:
Can I flash PC36IMG.zip from recovery like any other ROM in order to unroot?
HBOOT doesn't recognize PC36IMG.zip and the RUU doesn't recognize my phone. Need to unroot to take my phone in.
Thanks
Click to expand...
Click to collapse
Make sure PC36IMG.ZIP IS ALL CAPS look at my guide all the links needed to unroot
pipefitter said:
Can I flash PC36IMG.zip from recovery like any other ROM in order to unroot?
HBOOT doesn't recognize PC36IMG.zip and the RUU doesn't recognize my phone. Need to unroot to take my phone in.
Thanks
Click to expand...
Click to collapse
Make sure the PC36IMG.zip file doesn't have an additional suffix (exC36IMG.ZIP.zip) which is usually the case when the directions include renaming the original file to PC36IMG.zip. As for flashing it from within recovery, not unless it was designed to be flashed from recovery.
reaper24 said:
Make sure PC36IMG.ZIP IS ALL CAPS look at my guide all the links needed to unroot
Click to expand...
Click to collapse
Just to avoid any confusion for the OP, a quick correction. It's got to be PC36IMG.zip. We don't want the .zip in capitals. Only the PC36IMG is capitals. .zip remains lower case.
To the OP, as has been mentioned, be sure it's spelled correctly. Also, be sure it's on the main directory of your SD card, and not in any folders. If you're sure of both of those things, then double check that the file isn't corrupted. Can you open the zip file on your pc without getting an error?
As a rule of thumb, you don't ever want to flash PC36IMG.zip from recovery. If it won't flash from hboot, then there's something not right with the file (all of the above suggestions are good), but it's pretty much going to be a bad idea to flash that zip from recovery.
BAD PC36IMG.zip
I have downloaded at least 10 PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip files from different sites and EVERY one is bad. The md5 sums check out, but if I try to unzip them on my computer I get "Zip file corrupt" "Possible cause: File transfer error"
Does anyone have a good file that they can post or send me?
Thanks
pipefitter said:
I have downloaded at least 10 PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip files from different sites and EVERY one is bad. The md5 sums check out, but if I try to unzip them on my computer I get "Zip file corrupt" "Possible cause: File transfer error"
Does anyone have a good file that they can post or send me?
Thanks
Click to expand...
Click to collapse
Why are you unzipping the file? If I'm not mistaken, you rename PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip to PC36IMG.zip and flash from the bootloader.
k2buckley said:
Just to avoid any confusion for the OP, a quick correction. It's got to be PC36IMG.zip. We don't want the .zip in capitals. Only the PC36IMG is capitals. .zip remains lower case.
To the OP, as has been mentioned, be sure it's spelled correctly. Also, be sure it's on the main directory of your SD card, and not in any folders. If you're sure of both of those things, then double check that the file isn't corrupted. Can you open the zip file on your pc without getting an error?
Click to expand...
Click to collapse
dougjamal said:
Why are you unzipping the file? If I'm not mistaken, you rename PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip to PC36IMG.zip and flash from the bootloader.
Click to expand...
Click to collapse
Just trying to verify that it is a good download even though the md5 matches. Nobody seems to understand that I know what I'm doing. This is what is happening when i HBOOT:
SUPERSONIC EVT3 SHIP S-ON
MICROCHIO-041f
TOUCH PANEL-ATMELC03_16ac
HBOOT 2.10.0001
RADIO 2.15.00.11.11.19
HBOOT reads as follows
SD Checking...
Loading...[PC36DIAG.zip]
No Image!
Loading...[PC36DIAG.nbh]
No image or wrong image!
Loading...[PC36IMG.zip]
No image!
Loading...[PC36IMG.nbh]
No image or wrong image!
So, I decided to try running RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe from my PC. It starts out fine and says it is rebooting to BOOTLOADER, then it reboots to the HTC screen and goes no farther. The RUU says waiting for BOOTLOADER for abut 45 seconds and then says a connection cannot be established.
pipefitter said:
I have downloaded at least 10 PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip files from different sites and EVERY one is bad. The md5 sums check out, but if I try to unzip them on my computer I get "Zip file corrupt" "Possible cause: File transfer error"
Does anyone have a good file that they can post or send me?
Thanks
Click to expand...
Click to collapse
http://db.tt/gqTAPS1
Here's a link from my dropbox to the 3.70 software PC36IMG.
And by the way, I don't think that anyone assumed you didn't know what you are doing. There is truly know way of knowing someone's level of knowledge on any given subject, when we're all strangers on the internet. It's sometimes better to be sure that all bases have been covered, and that something simple wasn't overlooked. troubleshooting 101: start with the simplest stuff first. No matter what it is that you're troubleshooting. Anyways, hopefully the file from my dropbox will work for you.
have you tried running the RUU from fastboot mode? I see you had a connection error when you tried before. Boot into fastboot, from the bootloader. Or if you have adb setup type "adb reboot bootloader" and that should boot you to fastboot. Then connect your USB and try running the RUU again. It has a better chance of being recognized that way. Good luck.
pipefitter said:
Just trying to verify that it is a good download even though the md5 matches. Nobody seems to understand that I know what I'm doing....
Click to expand...
Click to collapse
Please don't be offended, my friend. Like my good friend, k2buckley stated, we have no idea of the level of knowledge that a person we are trying to help has and personally, every time I assume that a person knows a certain routine or technique, I quickly find that I am mistaken. In addition, I find that people will only post a small portion of what they have actually done and that makes it a tad difficult at times for those of us trying to help. teh roxxorz, k2buckley, HipKat, myself and many others spend a great deal of time in these forums trying to help when we can so please be patient with us.....
SOLVED!
k2buckley said:
http://db.tt/gqTAPS1
Here's a link from my dropbox to the 3.70 software PC36IMG.
And by the way, I don't think that anyone assumed you didn't know what you are doing. There is truly know way of knowing someone's level of knowledge on any given subject, when we're all strangers on the internet. It's sometimes better to be sure that all bases have been covered, and that something simple wasn't overlooked. troubleshooting 101: start with the simplest stuff first. No matter what it is that you're troubleshooting. Anyways, hopefully the file from my dropbox will work for you.
have you tried running the RUU from fastboot mode? I see you had a connection error when you tried before. Boot into fastboot, from the bootloader. Or if you have adb setup type "adb reboot bootloader" and that should boot you to fastboot. Then connect your USB and try running the RUU again. It has a better chance of being recognized that way. Good luck.
Click to expand...
Click to collapse
dougjamal said:
Please don't be offended, my friend. Like my good friend, k2buckley stated, we have no idea of the level of knowledge that a person we are trying to help has and personally, every time I assume that a person knows a certain routine or technique, I quickly find that I am mistaken. In addition, I find that people will only post a small portion of what they have actually done and that makes it a tad difficult at times for those of us trying to help. teh roxxorz, k2buckley, HipKat, myself and many others spend a great deal of time in these forums trying to help when we can so please be patient with us.....
Click to expand...
Click to collapse
Sorry guys, I was getting frustrated. I'm not used to failure. I'm no computer genius, but I pride myself in being able to follow and understand directions. I am officially unrooted!
This is what I did...
1)Uninstalled and reinstalled HTC drivers
2) Flashed a stock, rooted, odexed ROM. I was running Azrael 4.0. Don't know if this made any difference, but I tried the next steps before flashing the stock ROM and had no success.
3) Booted into FASTBOOT
4)Attached USB cable to computer and the phone immediately showed FASTBOOT USB
5) Ran RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe (this RUU matched my HBOOT and Radio)
6)Followed on-screen directions for RUU and 10 minutes later my phone was unrooted, completely stock.
Your success may vary. I had many people respond with the same mantra of "Do A, B, & C and your phone will be unrooted". By now, we should all know that each phone is different and sometimes they just won't cooperate. Don't get frustrated. Just keep at it and eventually you will solve your dilemma. I truly appreciate all the help from everyone on XDA!
Regards,
Mark
pipefitter said:
Sorry guys, I was getting frustrated. I'm not used to failure. I'm no computer genius, but I pride myself in being able to follow and understand directions. I am officially unrooted!
This is what I did...
1)Uninstalled and reinstalled HTC drivers
2) Flashed a stock, rooted, odexed ROM. I was running Azrael 4.0. Don't know if this made any difference, but I tried the next steps before flashing the stock ROM and had no success.
3) Booted into FASTBOOT
4)Attached USB cable to computer and the phone immediately showed FASTBOOT USB
5) Ran RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe (this RUU matched my HBOOT and Radio)
6)Followed on-screen directions for RUU and 10 minutes later my phone was unrooted, completely stock.
Your success may vary. I had many people respond with the same mantra of "Do A, B, & C and your phone will be unrooted". By now, we should all know that each phone is different and sometimes they just won't cooperate. Don't get frustrated. Just keep at it and eventually you will solve your dilemma. I truly appreciate all the help from everyone on XDA!
Regards,
Mark
Click to expand...
Click to collapse
Nice, I'm glad you got it figured out. I understand you getting frustrated, no apology necessary man. Forum troubleshooting isn't always the smoothest!
Also, just to be sure, your bootloader shows S-on now? I just want to be sure, because I didn't see that you had flashed the S on tool prior to running the RUU. If you're taking it to sprint, it's important that your bootloader shows S-on, so just be sure.
k2buckley said:
Nice, I'm glad you got it figured out. I understand you getting frustrated, no apology necessary man. Forum troubleshooting isn't always the smoothest!
Also, just to be sure, your bootloader shows S-on now? I just want to be sure, because I didn't see that you had flashed the S on tool prior to running the RUU. If you're taking it to sprint, it's important that your bootloader shows S-on, so just be sure.
Click to expand...
Click to collapse
+1...........Take care....
posting & replying via the XDA Premium app.
S-ON
k2buckley said:
Nice, I'm glad you got it figured out. I understand you getting frustrated, no apology necessary man. Forum troubleshooting isn't always the smoothest!
Also, just to be sure, your bootloader shows S-on now? I just want to be sure, because I didn't see that you had flashed the S on tool prior to running the RUU. If you're taking it to sprint, it's important that your bootloader shows S-on, so just be sure.
Click to expand...
Click to collapse
Yes, I flashed s-on with no problems. That's why I was getting so frustrated with the rest of the procedure.
Thanks everyone.

Stuck at bootloader, can't access recovery

After flashing cm7r2 hboot in order to flash a new rom I got stuck at bootloader and lost access to recovery... I flashed hboot through fastboot, it got done without obvious errors... So I tried flashing a new recovery but I end up every time in the same situation... It just hangs on why so serious screen after vibrating for more than 5 times... I tried flashing differerent hboots, recoveries but that doesn't solve anything... I'm not sure if this is any clue, I tried flashing radio and I get updating error in fastboot...
In the end I tried flashing a ruu (RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed) but I can't go through with it because I'm not in Android or whatever, it says error 170... Maybe if someone can tell me how to get around that ruu's android check I could finish ruu install...
Any help is welcome
I have the same problem, stuck on the white screen with htc logo in it and can't access recovery, tried creating a gold card and ran a RUU exe file, however I always get a customer id error. Hoping someone here can help us both. :-/
@OP boot into fastboot (turn off, hold back & power) and then use the RUU.
@ericbangug your goldcard evidently doesn't work - try again or try using a different SD-Card
To you both. Try read through my troubleshooting guide maybe you'll find some help there if you're still stuck
Thanks for replies and link to your very extensive thread... I'm not through reading it, so maybe i missed something that can be helpful... In the mean time I had a very busy afternoon trying many RUUs. None of them worked except the latest one, the infamous gingerbread one... But not even that one worked fully... After multiple attempts I'm stuck now again on bootloader, and RUU install is incomplete... It fails at radio flash (it says fail-pu) and partition update fails ergo the whole update fails... Unfortunate thing is that the device is not S-OFF anymore... So if someone has some idea how to finish RUU update in some other way please point me in the right direction...
since it's failed on radio you might be totally screwed. Using gingerbread one was so stupid. Should've just made a goldcard and used a 2.2 WWE RUU
Yeah, well since none of the other RUU (tried many versions both wee and branded) installations didn't complete with goldcards (i tried with multiple sdcards) I tried with the gingerbread one and when that one failed I knew I'd have to send phone to support service... hope they will find some solution... I'm still very confused with situation because I'm not completely sure what went wrong... I presume that partition went to hell... :/
Anyways thanks for feedback

Cannot access recover mode

So I've been trying to root my dads old Desire for a while now, with no success - it is locked to o2 and I'm on Orange. I didn't really want to pay to unlock it, and rooting it would have been nice. I've done two phones before, so I figured it shouldn't be too bad. Eventually I discovered it was HBOOT 1.03, and this was the problem, so the solution was to backdate the software to an earlier version (the phone is still S-ON and I cannot get this thing to take ANYTHING)
I was trying to roll back from Froyo to 2.1.
The current problem is that now the phone will not boot. With a simple turn-on it just sits at the white HTC screen, or if you go into Hboot it tries (what I assume is) 'fastboot' and checks the PB99IMG.zip file on the SD card. If I say I don't want to update and go to 'recovery' it loads the screen with the exclamation mark in a triangle in it. The problem here is that pressing up+power does nothing. I've tried a quick press, and a long hold multiple times, and with no result except the first time. Unfortunately I didn't go through the proceedure the first time, assuming it'd work again. Damn!
If I start the update it says 'can not roll back the hboot version'. It also fails on the radio_v2.
Any help will be much appreciated, and if you need any details (I've probably missed something) please ask!
Thanks
papercutout said:
So I've been trying to root my dads old Desire for a while now, with no success - it is locked to o2 and I'm on Orange. I didn't really want to pay to unlock it, and rooting it would have been nice. I've done two phones before, so I figured it shouldn't be too bad. Eventually I discovered it was HBOOT 1.03, and this was the problem, so the solution was to backdate the software to an earlier version (the phone is still S-ON and I cannot get this thing to take ANYTHING)
I was trying to roll back from Froyo to 2.1.
The current problem is that now the phone will not boot. With a simple turn-on it just sits at the white HTC screen, or if you go into Hboot it tries (what I assume is) 'fastboot' and checks the PB99IMG.zip file on the SD card. If I say I don't want to update and go to 'recovery' it loads the screen with the exclamation mark in a triangle in it. The problem here is that pressing up+power does nothing. I've tried a quick press, and a long hold multiple times, and with no result except the first time. Unfortunately I didn't go through the proceedure the first time, assuming it'd work again. Damn!
If I start the update it says 'can not roll back the hboot version'. It also fails on the radio_v2.
Any help will be much appreciated, and if you need any details (I've probably missed something) please ask!
Thanks
Click to expand...
Click to collapse
If it fails with Radio_v2, then it's a radio brick, and that's the reason it won't boot. I'm afraid you can't do much, due to the hboot version.
abaaaabbbb63 said:
If it fails with Radio_v2, then it's a radio brick, and that's the reason it won't boot. I'm afraid you can't do much, due to the hboot version.
Click to expand...
Click to collapse
I'm not too worried about getting a different rom on it, or rooting it or anything any more, currently I'd like to just put it back into a working state, as it was, probably locked to o2, if you've any suggestions on how to do that?
papercutout said:
I'm not too worried about getting a different rom on it, or rooting it or anything any more, currently I'd like to just put it back into a working state, as it was, probably locked to o2, if you've any suggestions on how to do that?
Click to expand...
Click to collapse
First, try this:
http://forum.xda-developers.com/showthread.php?t=1564644
abaaaabbbb63 said:
First, try this:
http://forum.xda-developers.com/showthread.php?t=1564644
Click to expand...
Click to collapse
The one step here I'm halted by is producing a Goldcard - the link to the website on the tool doesn't work any more (I've scoured t'internet, and that's the general consensus). Any idea where else I can input the CID to get a Goldcard Image?
Also how do I run the RUU on my computer? What file is it in the HTC Desire Android Upgrade folder I need to run? Afterall, there's no file titled 'RUU.exe'
Thanks
papercutout said:
The one step here I'm halted by is producing a Goldcard - the link to the website on the tool doesn't work any more (I've scoured t'internet, and that's the general consensus). Any idea where else I can input the CID to get a Goldcard Image?
Also how do I run the RUU on my computer? What file is it in the HTC Desire Android Upgrade folder I need to run? Afterall, there's no file titled 'RUU.exe'
Thanks
Click to expand...
Click to collapse
Just realized that it wouldn't work, because you have to boot your phone for the downgrader tool.
You could try something else. Unlock your bootloader using the HTC Dev site :http://www.htcdev.com/bootloader, and then try installing a custom recovery.
abaaaabbbb63 said:
Just realized that it wouldn't work, because you have to boot your phone for the downgrader tool.
You could try something else. Unlock your bootloader using the HTC Dev site and then try installing a custom recovery.
Click to expand...
Click to collapse
I've unlocked the bootloader (although obviously I'm still S-ON and HBOOT 1.03), so how would I go about installing a custom recovery?
Everything I can find online implies I need to do it starting with the phone up and running...
Thanks
papercutout said:
I've unlocked the bootloader (although obviously I'm still S-ON and HBOOT 1.03), so how would I go about installing a custom recovery?
Everything I can find online implies I need to do it starting with the phone up and running...
Thanks
Click to expand...
Click to collapse
You download this:
http://forum.xda-developers.com/showthread.php?p=28277117
You extract the recovery.img from it.
You then use fastboot to flash it:
fastboot flash recovery recovery.img
abaaaabbbb63 said:
You download this:
http://forum.xda-developers.com/attachment.php?attachmentid=1631968&d=1357780284
You extract the recovery.img from it.
You then use fastboot to flash it:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
That worked spot on! Have you got anything you'd recommend I put on there now? (factory reset didn't do anything, didn't really expect it to)
I tried cyangenmod7 for the desire, but with no luck. File 'BAD' or somethign when tried to read it from the SD card.
papercutout said:
That worked spot on! Have you got anything you'd recommend I put on there now? (factory reset didn't do anything, didn't really expect it to)
I tried cyangenmod7 for the desire, but with no luck. File 'BAD' or somethign when tried to read it from the SD card.
Click to expand...
Click to collapse
Try a MildWild ROM. Maybe the CM7 download was somehow faulty.
Can ya post the link to the thread and not just post the PB99IMG file? Thanks
jmcclue said:
Can ya post the link to the thread and not just post the PB99IMG file? Thanks
Click to expand...
Click to collapse
Sorry jmc. Will do
abaaaabbbb63 said:
Try a MildWild ROM. Maybe the CM7 download was somehow faulty.
Click to expand...
Click to collapse
You're getting good at this
So, that's on and working, but it's still locked to the carrier, o2. I've just tried 'HTC Desire unlock v0.9.5' but that didn't work (despite the program telling me it went flawlessly).
Any more suggestions?
papercutout said:
You're getting good at this
So, that's on and working, but it's still locked to the carrier, o2. I've just tried 'HTC Desire unlock v0.9.5' but that didn't work (despite the program telling me it went flawlessly).
Any more suggestions?
Click to expand...
Click to collapse
Try using a different USB port.
abaaaabbbb63 said:
Try using a different USB port.
Click to expand...
Click to collapse
Nope, nada. I tried v0.94 too. Nothing again. I guess I'll need to get a key. Damn that hboot 1.03!
At least the phone is actually WORKING now though, thanks to you, appreciated.

[Q] Did some searches, spent more than four hours looking..

Hello,
My adb devices is not showing my device.
I'm pretty sure I forgot to activate developer mode and turn on USB debugging. I can not flash any room and I'm stuck in a boot loop or just using TWRP. I'm completely lost in a way to get beyond this. I've been searching XDA for 4.5 hours straight and it seems some people have 80% of my problem but not 100%. I decided initially to follow a Youtube video that didn't mention anything about USB debugging so I'm wondering if that's the main issue in all of this. I've tried going back to stock RUU, through Hasoon2000's allinone but I keep getting failures. Just at a loss and would appreciate any help. I'm trying to go to the Skydragon Rom, but I'm willing to go back to stock to work my way back up. I've initially rooted this type of phone before, but I didn't follow the same method as last time(which was Hasoon's) as I thought it would work the same, I used this Youtube video, youtube/watch?v=_yo4eoCfxmE. (sorry link is weird cause I can't post links yet, add a .com after youtube!) I do not have S-Off. I just wanna know what I can do to get back to Skydragon or at least back to stock before my girlfriend beats my ass for messing up her phone
Valkalkas said:
Hello,
My adb devices is not showing my device.
I'm pretty sure I forgot to activate developer mode and turn on USB debugging. I can not flash any room and I'm stuck in a boot loop or just using TWRP. I'm completely lost in a way to get beyond this. I've been searching XDA for 4.5 hours straight and it seems some people have 80% of my problem but not 100%. I decided initially to follow a Youtube video that didn't mention anything about USB debugging so I'm wondering if that's the main issue in all of this. I've tried going back to stock RUU, through Hasoon2000's allinone but I keep getting failures. Just at a loss and would appreciate any help. I'm trying to go to the Skydragon Rom, but I'm willing to go back to stock to work my way back up. I've initially rooted this type of phone before, but I didn't follow the same method as last time(which was Hasoon's) as I thought it would work the same, I used this Youtube video, youtube/watch?v=_yo4eoCfxmE. (sorry link is weird cause I can't post links yet, add a .com after youtube!) I do not have S-Off. I just wanna know what I can do to get back to Skydragon or at least back to stock before my girlfriend beats my ass for messing up her phone
Click to expand...
Click to collapse
haha... Love :victory:
Now back to issue.
If you're in the bootloader you don't need USB Debugging enabled, you can still use the fastboot command regardless of USB debugging mode. Check
Code:
fastboot devices
not
Code:
adb devices
.
Make sure all the drivers are still fine on the PC, reinstall if you must.
On a side note, try not to use all-in-one toolkits as you really don't get to learn from using something like that. If you did it manually you'd already have a pretty good understanding on which command gets used in which instance i.e bootloader vs in-system.
I actually didn't use a all-in-one this time around but as soon as I unlocked boot loader and rooted I had issues installing the custom rom. I've used both phil z and twrp but it still gets stuck when I install the sky dragon, or viper for that matter to test and make sure it wasn't just a bad download. Earlier when I did fast boot devices it did show something but now it's just a blank space. I'm in bed now I would double check again to make sure but like I said it's been a few hours and now it's 4:38 am and I'm tired. I'll double check in the morning but I appreciate your response and I'll double check. Drivers should be good from last time but I will double check and make sure. Again thanks for responding!
Alright, now after some rest I've checked the fastboot devices and it does show up.
Tried flashing to latest SkyDragon again and it just sits on the HTC screen before boot looping.
The device is S-On, unlocked and says tampered. I've tried flashing the boot.img in bootloader after flashing the rom but still no dice.
Valkalkas said:
Alright, now after some rest I've checked the fastboot devices and it does show up.
Tried flashing to latest SkyDragon again and it just sits on the HTC screen before boot looping.
The device is S-On, unlocked and says tampered. I've tried flashing the boot.img in bootloader after flashing the rom but still no dice.
Click to expand...
Click to collapse
Latest skydragon, ARHD, InsertCoin and many more are meant for hboot 3.18 and above. If you boot to bootloader and see your hboot is 3.16, these ROMs won't work properly for you.
So check your hboot no.
Next ... check your CID and MID
If possible the OS version no. on bootloader too
You may need to revert to your stock ROM ... then check any OTA for your device
ckpv5 said:
Latest skydragon, ARHD, InsertCoin and many more are meant for hboot 3.18 and above. If you boot to bootloader and see your hboot is 3.16, these ROMs won't work properly for you.
So check your hboot no.
Next ... check your CID and MID
If possible the OS version no. on bootloader too
You may need to revert to your stock ROM ... then check any OTA for your device
Click to expand...
Click to collapse
Alright yeah, my hboot is 3.16. Tried looking up ways to update the fastboot but all I've seen is requiring S-Off.
CID is CWS____001
MID is 0P6B12000
The OS is blank, just says OS- (blank space)
Gonna try flashing stock recovery again.
Valkalkas said:
Alright yeah, my hboot is 3.16. Tried looking up ways to update the fastboot but all I've seen is requiring S-Off.
CID is CWS____001
MID is 0P6B12000
The OS is blank, just says OS- (blank space)
Gonna try flashing stock recovery again.
Click to expand...
Click to collapse
Yours is At&T (if I'm not wrong as I'm not familiar with this Sprint, Verizon and AT&T)
And there are RUU for both 4.4.2 and 4.4.3 (hboot 3.16 and 3.18) ... it's best for you to head over AT&T forum for better guidance.
http://forum.xda-developers.com/showthread.php?t=2757462
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
ckpv5 said:
Yours is At&T (if I'm not wrong as I'm not familiar with this Sprint, Verizon and AT&T)
And there are RUU for both 4.4.2 and 4.4.3 (hboot 3.16 and 3.18) ... it's best for you to head over AT&T forum for better guidance.
http://forum.xda-developers.com/showthread.php?t=2757462
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Click to expand...
Click to collapse
Alright, thank you for your help. I relocked and I tried the second link you posted, but the ruu messes up after I accept the EULA and just keeps popping up boxes. Downloading the RUU from the first link now and gonna try that. I just run the RUU in fastboot usb right?
Again thanks, I had no idea to check for hboot versions when rooting/flashing in the time I've rooted some devices so guess I'm learning something the hard way.
Edit: Same thing with the first link. I feel like I'm in the wrong place trying to run the RUU in fastboot usb?
Alright, tried running the RUU's again on the black screen with the silver HTC letters as suggested by someone else and the program still acts up after the EULA.
Alright, I was able to find a nandroid backup and restore it through there, so now I'm back in business. Thanks for the help!

Categories

Resources