Related
Hey guys i really need some help here, my phone won't boot up and it won't recognise my sd card. I've only got fastboot and recovery.
I'll explain as best as i can how it got this way;
Firstly i tried to s-off my desire so that i could upgrade to amon recovery 2.0, but it got stuck on 3rd step waiting for flash to complete after sorting that out by flashing a new rom, i proceeded to flash the recovery and that went fine. then i created a nand backup and decided to test the s-off by flashing a custom splash which also went fine but then i rebooted and downloaded leedroid2.2f and transfered it on to my sd card but when i rebooted the phone when into a small bootloop before booting into the phone but it was failing to recognise the sd card so i tested the sd card in my hero and it was working fine. the phone wasn't being recognised by the laptop as it ws asking for certian drivers so i rebooted into recovery and did a full wipe (like an idiot) and now it gets stuck in the boot animation with no logcat output and as it can pick up the sd card i can't flash a rom.
I hope some one can help me get my desire back to stock at least so i can send it off to htc if there is any hardware problem
Can i also add that my desire was orange branded had a slcd screen its original hboot was 0.83 and i don't have a goldcard for it either
Edit: I solved it and my phone is back thanks to guide by shockem on another thread, i'd also like to apologise to any mods for opening a new thread (kinda panicked) i'll look around properly before i open a new thread
hey guys now that my phone is back to stock has it got warranty back? seeing as it's an orange branded phone but it has a stock unbranded rom also its sim unlocked
If Orange takes care of your warranty, I suppose you must flash an Orange branded RUU before submitting it.
Yeah but theres no orange ruu and i can't use my usb port. I only have a goldcard which i made last night so if anyone can create a pb99img.zip for a stock orange rom i'll be grateful or if anyone can tell me another way of flashing a stock orange ruu.
That ZIP can only be extracted from an RUU, it's not something you can 'make up'
I'd go back to HTC direct and see what they say
EddyOS said:
That ZIP can only be extracted from an RUU, it's not something you can 'make up'
I'd go back to HTC direct and see what they say
Click to expand...
Click to collapse
Yeah i realised that, seeing as i got my phone running now i've done some searching and i believe my usb is bricked, theres a guide on modaco to fix it but it requires for me to be rooted, the problem is my phone is slcd and originally had boot loader version 0.83 and the bootloader atm is 0.93. Is there a way for me to root the desire to attempt this fix?
its definitely a usb brick as i've enabled sd card functionality. I jus need a way to root the device now any one help me out?
You can't, unless VISIONary is working on the Desire
If you wanna try a newer ROM and see if that fixes things get the newest PB99IMG off of shipped-ROMs.com - it's the version of 2.29.405.2 and you'll need your gold card to flash it
EddyOS said:
You can't, unless VISIONary is working on the Desire
If you wanna try a newer ROM and see if that fixes things get the newest PB99IMG off of shipped-ROMs.com - it's the version of 2.29.405.2 and you'll need your gold card to flash it
Click to expand...
Click to collapse
Just tried with VISIONary it goes through the motions and su app is there but doesn't seem to have given root as any app requiring root doesn't work. I'll have to pop into local orange shop and see what they say if that doesn't work can you tell me how i would get it back to HTC
You'd send it back to HTC as per the warranty card details I imagine, never had to send anything back to them before
SOLVED
Manage to get it done using this post http://forum.xda-developers.com/showpost.php?p=9056719&postcount=15
make sure usb debugging is ticked and also copy the files to /data/data/jackpal.androidterm/ only, there is no such directory as shared_prefs
Only way to get stock orange ruu on it is go to an orange store and ask them to reflash the phone.
Sent from my HTC Desire using XDA App
ste1164 said:
Only way to get stock orange ruu on it is go to an orange store and ask them to reflash the phone.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Thanks but that would have been hard without a usb but it doesn't matter i've fixed the usb brick and re rooted my phone, fortunately i had made a nand backup just before everything crashed so going to restore that
fezy said:
Thanks but that would have been hard without a usb but it doesn't matter i've fixed the usb brick and re rooted my phone, fortunately i had made a nand backup just before everything crashed so going to restore that
Click to expand...
Click to collapse
Assuming Orange have the RUU it wouldn't have been hard, but they would've needed the SD card working
EddyOS said:
Assuming Orange have the RUU it wouldn't have been hard, but they would've needed the SD card working
Click to expand...
Click to collapse
Thats true but i don't think flashing the RUU would have fixed the usb brick but its all good now i have learned alot over the past 24hours and hopefully i won't come across this situation again but just incase it does happen again, atleast i'll know what to do. But thanks for your input i really appreciate it
ok so i just tried rooting my evo. I used an out dated rooting method not compatible with the version of my phone. I have 3.30, hboot 2.02, and radio 2.15.00.09.01. When i turn the phone on it gets stuck at white htc screen. I can boot into the bootloader. I have tried running the ruu but when i do it doesnt recognize my phone is connected. I have htc drivers installed...i dont know what to, do please help
Does the hboot says s-on or s-off? If your s-off try flashing a rom through recovery or a pc36img ruu through the boot loader.
Sent from my PC36100 using XDA App
Lukez123 said:
ok so i just tried rooting my evo. I used an out dated rooting method not compatible with the version of my phone. I have 3.30, hboot 2.02, and radio 2.15.00.09.01. When i turn the phone on it gets stuck at white htc screen. I can boot into the bootloader. I have tried running the ruu but when i do it doesnt recognize my phone is connected. I have htc drivers installed...i dont know what to, do please help
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Well one, if you can get to the bootloader, you most likely aren't bricked, so breathe! What root method did you try to use? How far in the process did you get? How long did you let it stay at the HTC screen? Sometimes it takes a good long while. If I was in your situation, since your computer won't recognize phone, is take your SD card out of the phone. Download a stock ruu zip. Rename it to PC36IMG.zip. put it on your SD card, put SD card back in phone, and boot into the bootloader. It should find the zip, and you select to flash it. Give that a try.
EDIT: Damn,I'm always too late! And yea, as he said, if you are s off, and did successfully flash a recovery image, try flashing a Rom first. Id be surprised if you are s off with recovery if you used an old method with the 2.02 hboot. What happens when you select recovery from bootloader?
Find and download RUU_SuperSonic_S_Sprint_WWE_3.30.651.2_Radio_2.15.00.09.01_NV_1.77_003_release_154209_signed
That's the one that worked on a hardware 004 Evo I used the old method on
Any luck getting your phone back up?
my s is still on..when i go to recovery it shows the evo with the red exclamation mark. I will try putting the ruu zip on my memory card..i need to go get a usb for my hero as it seems i cannot find it and have no other way to put a file on my sd card. any ideas if that doesnt work? i am a little confused as why it will let me issue adb codes in the command prompt but htc sync does not pick up the phone
Yup your still not rooted. Try to get a way to put a file on your usb card so you can load a PC36IMG.zip ruu of your 3.30 rom so you can get back to stock and start your process over with unrevoked.
http://forum.xda-developers.com/showthread.php?t=884060&highlight=shipped+roms
Lukez123 said:
ok so i just tried rooting my evo. I used an out dated rooting method not compatible with the version of my phone. I have 3.30, hboot 2.02, and radio 2.15.00.09.01. When i turn the phone on it gets stuck at white htc screen. I can boot into the bootloader. I have tried running the ruu but when i do it doesnt recognize my phone is connected. I have htc drivers installed...i dont know what to, do please help
Click to expand...
Click to collapse
I have dealt with this issue before. It is difficult to get an ruu to run but I think it is worth it. Find the right ruu for your phone to get you back to stock. Once you have this get your phone in to bootloader and use the fastboot command I believe it is. This will help your computer recognize your phone. Then run the ruu after you have done this, may take a few tries but im positive it works. Good luck.
Sent from my PC36100 using XDA App
Lukez123 said:
my s is still on..when i go to recovery it shows the evo with the red exclamation mark. I will try putting the ruu zip on my memory card..i need to go get a usb for my hero as it seems i cannot find it and have no other way to put a file on my sd card. any ideas if that doesnt work? i am a little confused as why it will let me issue adb codes in the command prompt but htc sync does not pick up the phone
Click to expand...
Click to collapse
Do you have a card reader? that would also work. Would probably also be cheaper than a usb cable I would think, not sure though. (unless of course you still use the hero and want a new cable anyways)
Thanks guys your awesome...was able to get the stock ruu pc35img on my sdcard..time to give rooting it a second go..with the right procedure this time..haha..thanks again
http://forum.xda-developers.com/showthread.php?t=865204
ok so i wanted to get a custom rom my desire hd 2.3.5
at start i have tryed the old way thats in the sticky but that was for 2.3.4 so that didnt work.
what did work was unlocking the bootloader via htc dev site. after that i was clueless.
I've found AAK to root my phone and downgrade so i had used that, but i forgot that the phone was unlocked and it said it had to be locked.
and now the phone is bricked i've tried all possible ways with wiping data and cache but it doesnt work.
i wanted to relock the bootloader with fastboot.
i had entered this command:
fastboot oem lock
but that gave this error
FAILED (status malformed (1 bytes))
so my phone hangs on the boot screen and i cant do anything?
can you guys please help me?
The fact you can get to the bootloader is a great sign, so don't worry! The only time you need to properly panic is when you can't get anything on the screen or even a charge light.
---Double check with someone else that this is correct, but I think this is what you need to do ---
Do you have a custom recovery (i.e clockworkmod)? Can you boot into recovery? Use the volume keys to select recovery, then press the power button. If you get options like "reboot now" and "install zip from sd card" then flash a rom like Android Revolution HD.
If you get a red triangle, find a zip you want to flash and name it "PD98IMG.zip" then put it on the root of the SD card. Reboot to bootloader and it should flash.
If you truly want to relock the bootloader, flash an RUU and it will restore you to stock.
Tamen said:
If you get a red triangle, find a zip you want to flash and name it "PD98IMG.zip" then put it on the root of the SD card. Reboot to bootloader and it should flash.
If you truly want to relock the bootloader, flash an RUU and it will restore you to stock.
Click to expand...
Click to collapse
Simply renaming a ROM PD98IMG.zip wont work it needs to be formatted in a certain way, but if the phone is S-OFF, which wasn't mentioned there are certainly PD98IMG's about for a variety of ROMs. But I suspect Tamens suggestion of flashing the appropriate RUU and starting from scratch is going to be quickest way to get sorted
I had this same problem with mine it got stuck trying to boot up but I had no boot loader or I couldn't get into recovery.so download a took called ANDROID FLASHER and reflash the radio ect.my desire hd is now fine.
Sent from my HTC Sensation XL with Beats Audio X315e using XDA App
well i have tried to flash the ruu but without succes.
ive loaded the PD98IMG.zip on the sd and let the bootloader use it. nothing happened.
also my phone is s-on and could not find a way to go to s-off in recovery mode or boatloader.
Down load the tool above Android flasher.from the tool u can enable fast boot ect from your PC and loads of other stuff.it is a very simple to use and it has loads of folders for recovery, boot loader ect let it do every thing for u.that was the only thing that worked for me
Sent from my HTC Sensation XL
I've tried it but it doesn't work because my phone is s-on...
the description of that utility said that s-off is essential
i am really running out of options..
in short my phone has a unlocked bootloader and after that i've used AAK.
the result is bricked phone with s-on and unlocked bootloader
i dont know exactly whats happened here, but i've tried to get my WFS sorted with a different rom than the carriers bloated version.
what i've done is updated hboot to 1.08.0099 and unlocked the boot loader sucessfully (hboot has *** UNLOCKED *** across the top; i used the HTCDEV.com process).
i believe i've got permanent root too.
when i attempt to flash CWM (via PG76IMG.zip), it appears to flash ok, but if i reboot the phone and try to access recovery, it just gets stuck on a white HTC screen.
i've redownloaded the CWM file to see if it's a corrupt download, but still the same problem.
CWM isnt a big issue, although it is nice to have.
however i also am unable to flash another rom either via the PG76IMG.zip SD method, or RUU.
i beleive i've done everything right, and i'm not entirely new to unlocking/rooting devices; only did my HTC Desire last week so the general process is still new in my head.
If your rooted install rom manager and flash recovery from there.
I had problems installing cwm from sd, so used the tool from here http://forum.xda-developers.com/showthread.php?t=1431969
previously was this one mediafire.com/?b0bsb4ms4lo714b
just plug the usb in sync and folow the instructions
Let me start by saying this forum has provided me with a ton of support in the past. There is so much information available here that I rarely have to start my own thread. Unfortunately, I have spent the past 18 hours looking for a solution to my current problem and have come up empty handed. I'm hoping some of you are savvy enough to help me out. I will try to provide as much information as possible to help diagnose the issue.
Device
HTC One M8
Carrier: AT&T
CID: CWS_001
Unlocked HTC Bootloader
S-On
I was previously running the stock ROM rooted (based on the above) simply to disable the AT&T bloatware. As of last week, AT&T began pushing the 4.4.4 update and I made the mistake of trying to install it not realizing my custom recovery (TWRP 2.7.1.0) would prevent it. Ever since this occurred, my phone has been doing strange things, i.e. random reboots and the "AT&T" logo in the upper left corner of the task bar would flash and disappear. It eventually got to the point where my phone was stuck in a constant boot loop and the only thing that would fix it was a factory reset from TWRP recovery. The phone would then act normal for about 24 hours and then the boot loop would start again.
I decided to try solving the issue by installing the GPE 4.4.3 ROM. I performed a complete wipe in TWRP (including system) and installed the GPE ROM via ADB/Fastboot. Everything was fine from this point and all apps/data synced after I logged into my Google account. Shortly after the phone booted, I was asked to install the GPE 4.4.4 update. It was at this point that I decided to load the stock recovery image so I could simply install the OTA update. Once again, no problems. Stock recovery flashed fine and I downloaded the 4.4.4 OTA update and rebooted the phone. The phone appeared to finish the install, but failed to boot. Now I cannot get past the HTC splash screen and I do not have a custom recovery.
The factory reset option from stock recovery does not help (still gets stuck at the splash screen) and for some reason my device is no longer recognized in Fastboot which prevents me from flashing a custom recovery. I thought it may have been a driver issue so I uninstalled and reinstalled HTC Sync Manager. I also tried manually uninstalling the drivers from the USB Root Hub, pulled the battery on my laptop, and allowed Windows 7 to auto update the drivers automatically. In each case, the drivers were successfully installed, but the phone is still not recognized in Fastboot (no devices listed). I even did a system restore on my laptop to a few days before the issue and the phone still isn't recognized by HTC Sync Manager or Fastboot.
The stock recovery bootloader displays the following information:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS- (2.12..1700.1)
eMMC-boot 2048MB
Based on all of this, do I have any options or is my phone bricked?
1. Is there anything I can do so my device is recognized by ADB/Fastboot so I can flash a custom recovery?
2. Can I install a ROM from the SD card with the stock recovery? I currently have the GPE 4.4.3 ROM on my SD card, but the zip is not recognized by the stock recovery. Can I rename it to something else so it can be recognized and installed?
3. Because the phone is not recognized by Windows, I cannot use the RUU method. Are there any other ways to return my phone to stock without RUU?
Any help is greatly appreciated.
Swazi Samurai said:
Let me start by saying this forum has provided me with a ton of support in the past. There is so much information available here that I rarely have to start my own thread. Unfortunately, I have spent the past 18 hours looking for a solution to my current problem and have come up empty handed. I'm hoping some of you are savvy enough to help me out. I will try to provide as much information as possible to help diagnose the issue.
Device
HTC One M8
Carrier: AT&T
CID: CWS_001
Unlocked HTC Bootloader
S-On
I was previously running the stock ROM rooted (based on the above) simply to disable the AT&T bloatware. As of last week, AT&T began pushing the 4.4.4 update and I made the mistake of trying to install it not realizing my custom recovery (TWRP 2.7.1.0) would prevent it. Ever since this occurred, my phone has been doing strange things, i.e. random reboots and the "AT&T" logo in the upper left corner of the task bar would flash and disappear. It eventually got to the point where my phone was stuck in a constant boot loop and the only thing that would fix it was a factory reset from TWRP recovery. The phone would then act normal for about 24 hours and then the boot loop would start again.
I decided to try solving the issue by installing the GPE 4.4.3 ROM. I performed a complete wipe in TWRP (including system) and installed the GPE ROM via ADB/Fastboot. Everything was fine from this point and all apps/data synced after I logged into my Google account. Shortly after the phone booted, I was asked to install the GPE 4.4.4 update. It was at this point that I decided to load the stock recovery image so I could simply install the OTA update. Once again, no problems. Stock recovery flashed fine and I downloaded the 4.4.4 OTA update and rebooted the phone. The phone appeared to finish the install, but failed to boot. Now I cannot get past the HTC splash screen and I do not have a custom recovery.
The factory reset option from stock recovery does not help (still gets stuck at the splash screen) and for some reason my device is no longer recognized in Fastboot which prevents me from flashing a custom recovery. I thought it may have been a driver issue so I uninstalled and reinstalled HTC Sync Manager. I also tried manually uninstalling the drivers from the USB Root Hub, pulled the battery on my laptop, and allowed Windows 7 to auto update the drivers automatically. In each case, the drivers were successfully installed, but the phone is still not recognized in Fastboot (no devices listed). I even did a system restore on my laptop to a few days before the issue and the phone still isn't recognized by HTC Sync Manager or Fastboot.
The stock recovery bootloader displays the following information:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS- (2.12..1700.1)
eMMC-boot 2048MB
Based on all of this, do I have any options or is my phone bricked?
1. Is there anything I can do so my device is recognized by ADB/Fastboot so I can flash a custom recovery?
2. Can I install a ROM from the SD card with the stock recovery? I currently have the GPE 4.4.3 ROM on my SD card, but the zip is not recognized by the stock recovery. Can I rename it to something else so it can be recognized and installed?
3. Because the phone is not recognized by Windows, I cannot use the RUU method. Are there any other ways to return my phone to stock without RUU?
Any help is greatly appreciated.
Click to expand...
Click to collapse
There is 2 methods to do an RUU. one is by putting the RUU on your sdcard and booting into the bootloader and waiting a few minutes then accepting the prompt to do it and 2 is the fastboot method. Since you have an SD card you could attempt the first one I listed. Make sure you don't change the name of the RUU and make sure you get the proper one for your phone.
S1L3nTShaDoWz said:
There is 2 methods to do an RUU. one is by putting the RUU on your sdcard and booting into the bootloader and waiting a few minutes then accepting the prompt to do it and 2 is the fastboot method. Since you have an SD card you could attempt the first one I listed. Make sure you don't change the name of the RUU and make sure you get the proper one for your phone.
Click to expand...
Click to collapse
Don't you have to be S-OFF or have a locked bootloader to run a RUU? I am unable to achieve either of those since my phone is not recognized by by ADB/Fastboot.
Also, because my most recent functioning ROM was GPE 4.4.3, would I still be able to run the stock AT&T RUU? I thought the partitions were different? I have the GPE RUU as well, but I don't think I can run that either without changing my CID and locking my bootloader.
Swazi Samurai said:
Don't you have to be S-OFF or have a locked bootloader to run a RUU? I am unable to achieve either of those since my phone is not recognized by by ADB/Fastboot.
Also, because my most recent functioning ROM was GPE 4.4.3, would I still be able to run the stock AT&T RUU? I thought the partitions were different? I have the GPE RUU as well, but I don't think I can run that either without changing my CID and locking my bootloader.
Click to expand...
Click to collapse
S-OFF not so sure about, locked bootloader, no you can have it unlocked. But you can try it anyways, the SD card method.
Yes you would be able to run it, I'm quite sure all you did was flash a GPE ROM. I believe all flashing the ROM does is give you a GPE ROM where as the GPE RUU would change all that and give you GPE phones firmware too.
On the off hand you did do a GPE RUU then I'm not sure.
S1L3nTShaDoWz said:
S-OFF not so sure about, locked bootloader, no you can have it unlocked. But you can try it anyways, the SD card method.
Yes you would be able to run it, I'm quite sure all you did was flash a GPE ROM. I believe all flashing the ROM does is give you a GPE ROM where as the GPE RUU would change all that and give you GPE phones firmware too.
On the off hand you did do a GPE RUU then I'm not sure.
Click to expand...
Click to collapse
I have heard it has to be one or the other. If S-OFF, the bootloader can be unlocked. If S-ON, the bootloader has to be locked.
I did not run the GPE RUU originally; I installed the ROM through custom recovery. I'm assuming that is a good thing based on your feedback.
Regardless, I haven't been able to try the SD method because the zip file I extracted from the RUU exe will not transfer to my SD card. I also tried downloading another user's bootable version and it won't transfer either. I have copied many other files to and from my SD card (even larger file sizes) without any issues. I have no clue what is going on now...
Swazi Samurai said:
I have heard it has to be one or the other. If S-OFF, the bootloader can be unlocked. If S-ON, the bootloader has to be locked.
I did not run the GPE RUU originally; I installed the ROM through custom recovery. I'm assuming that is a good thing based on your feedback.
Regardless, I haven't been able to try the SD method because the zip file I extracted from the RUU exe will not transfer to my SD card. I also tried downloading another user's bootable version and it won't transfer either. I have copied many other files to and from my SD card (even larger file sizes) without any issues. I have no clue what is going on now...
Click to expand...
Click to collapse
I formatted my SD card and was finally able to transfer the RUU. The bootloader begins to run the 0P6BIMG file, but it fails right after it starts parsing. I tried running it several times and the results were the same.
I really wish I could get ADB to recognize my phone so I can flash a custom recovery... When I plug my phone into a USB port, my computer makes a noise, the phone says "USB" next to Fastboot, and HTC Sync Manager begins to load. When HTC Sync Manager comes up, it says "HTC Sync Manager couldn't connect to your phone." Windows Device Manager also does not have anything listed for an Android device.
I've noticed when the phone is not powered on and simply charging from the USB port, an "HTC MTP Device" driver tries to install, but fails. Could this be the problem? I've tried plugging the phone into 3 different computers and they all get the MTP failure.
If you are coming from a GSM variant things get a little bit more complicated to install a GPE RUU, as the GPE HBoot is different from the GSM one and partition sizes are as well.
You have to be S-Off to install the proper firmware and prior to doing this, change the CID as well as the MID to a GPE one.
There is a full guide on this forum to convert your M8 from GSM to GPE, bit as I'm on the train at the moment I can't provide you the link right away.
Sent from my HTC One_M8 using XDA Free mobile app
HTCNerdYoda said:
If you are coming from a GSM variant things get a little bit more complicated to install a GPE RUU, as the GPE HBoot is different from the GSM one and partition sizes are as well.
You have to be S-Off to install the proper firmware and prior to doing this, change the CID as well as the MID to a GPE one.
There is a full guide on this forum to convert your M8 from GSM to GPE, bit as I'm on the train at the moment I can't provide you the link right away.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I'm not specifically trying to install the GPE RUU at the moment. I had the stock GSM recovery installed based on my original CID and I'm trying to load the associated RUU.
I originally loaded GPE 4.4.3 with TWRP and downloaded the 4.4.4 update OTA from Google. Before restarting my phone and installing the update, I flashed the stock GSM recovery for CID CWS_001. This may have been what caused the issue initially when the phone tried to apply the update if it was looking for a GPE recovery.
I know I cannot install the GPE RUU because I'm S-ON and ADB does not recognize my device so I cannot change the MID or CID. At this point, I'm really just trying to get back to stock so I can start fresh.
Is it possible that when the 4.4.4 update tried to run, it associated my recovery with GPE and now that's why it will not install the stock RUU due to a mismatch? I'm really just guessing at this point.
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
3484jacks said:
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
Click to expand...
Click to collapse
I'll give that a try and report back. Thanks for the input.
3484jacks said:
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
Click to expand...
Click to collapse
You are the freakin man!!! I edited the template from the post you suggested, added my MID/CID, and packaged it with the TWRP image. Booted right from the SD and I now have custom recovery! I wish I could buy you a beer!
No problem mate. Glad I could help. :thumbup::thumbup::beer:
Sent from my HTC One_M8 using XDA Free mobile app