Database Develop

HELP HTC One wont boot in recover or OS

Hi,
so today I tried flashing ARHD HD40.3 with cwm , so after It installed, it was stuck at the HTC logo with the red warnings on the
bottom.
So I tried booting in to recovery to restore my backup, but when i try to boot in cwm it is stuck for 1 second on a black screen with the version number of cwm on the bottom, and the it reboots..... So my Phone is unable to boot in the OS, AND unable to boot in CWM
Please someone help.
Thanks

pottemans said:
Hi,
so today I tried flashing ARHD HD40.3 with cwm , so after It installed, it was stuck at the HTC logo with the red warnings on the
bottom.
So I tried booting in to recovery to restore my backup, but when i try to boot in cwm it is stuck for 1 second on a black screen with the version number of cwm on the bottom, and the it reboots..... So my Phone is unable to boot in the OS, AND unable to boot in CWM
Please someone help.
Thanks
Click to expand...
Click to collapse
try to boot into the bootloader... then plug it in to your PC
then go to FASTBOOT and wait until it's written: FASTBOOT USB
then type this command:
Code:
fastboot erase cache
then flash a new recovery:
Code:
fastboot flash recovery customrecoveryname.img
Then boot into your recovery...

LibertyMarine said:
try to boot into the bootloader... then plug it in to your PC
then go to FASTBOOT and wait until it's written: FASTBOOT USB
then type this command:
Code:
fastboot erase cache
then flash a new recovery:
Code:
fastboot flash recovery customrecoveryname.img
Then boot into your recovery...
Click to expand...
Click to collapse
OMG first of all, thanks for helping me...
So when putt it in fastboot, it says FASTBOOT in red, not FASBOOTUSB...

LibertyMarine said:
try to boot into the bootloader... then plug it in to your PC
then go to FASTBOOT and wait until it's written: FASTBOOT USB
then type this command:
Code:
fastboot erase cache
then flash a new recovery:
Code:
fastboot flash recovery customrecoveryname.img
Then boot into your recovery...
Click to expand...
Click to collapse
And I don´t now anything about fastboot, adb and stuf.... SO PLEASE HELP ME:crying:

pottemans said:
OMG first of all, thanks for helping me...
So when putt it in fastboot, it says FASTBOOT in red, not FASBOOTUSB...
Click to expand...
Click to collapse
plug the phone into the PC then it changes to fastboot USB
pottemans said:
And I don´t now anything about fastboot, adb and stuf.... SO PLEASE HELP ME:crying:
Click to expand...
Click to collapse
I'll attach the fastboot / adb files, just extract to a folder called fastboot in your c:\
the commands he posted are done from command prompt from the folder where fastboot is
Edit: also did you update to TWRP 2.6.3.3 like the ARHD thread said to ?

clsA said:
plug the phone into the PC then it changes to fastboot USB
I'll attach the fastboot / adb files, just extract to a folder called fastboot in your c:\
the commands he posted are done from command prompt from the folder where fastboot is
Edit: also did you update to TWRP 2.6.3.3 like the ARHD thread said to ?
Click to expand...
Click to collapse
No, Thats the silly thing..... Can you bring me the TWRP 2.6.3.3 ZIP please
thanks

pottemans said:
No, Thats the silly thing..... Can you bring me the TWRP 2.6.3.3 ZIP please
thanks
Click to expand...
Click to collapse
I just posted it here for someone else
http://forum.xda-developers.com/showthread.php?p=48475110#post48475110

clsA said:
I just posted it here for someone else
http://forum.xda-developers.com/showthread.php?p=48475110#post48475110
Click to expand...
Click to collapse
OK, so everything is ready, but it keeps saying WAITING FOR DEVICE

pottemans said:
OK, so everything is ready, but it keeps saying WAITING FOR DEVICE
Click to expand...
Click to collapse
it means you don't have the drivers installed correctly
unplug the phone and try these
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
MD5: e2a21d71954d4164c1a116abb926a363
after install plug in the phone

clsA said:
it means you don't have the drivers installed correctly
unplug the phone and try these
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
MD5: e2a21d71954d4164c1a116abb926a363
after install plug in the phone
Click to expand...
Click to collapse
When I run it nothing happends....
I DO HAVE HTC SYNC INSTALLED

pottemans said:
When I run it nothing happends....
I DO HAVE HTC SYNC INSTALLED
Click to expand...
Click to collapse
dump sync but leave the driver's
what OS you on ?
and what was the last working version of android on your phone

clsA said:
dump sync but leave the driver's
what OS you on ?
and what was the last working version of android on your phone
Click to expand...
Click to collapse
Okay so I uninstalled the drivers and sync, then I installed the drivers you gave me but it still doesn´t find my Phone...
im on windows 8.1 and before i flashed the ARHD 40.3 I was on 31 Or somethng wich was Android 4.3....

pottemans said:
Okay so I uninstalled the drivers and sync, then I installed the drivers you gave me but it still doesn´t find my Phone...
im on windows 8.1 and before i flashed the ARHD 40.3 I was on 31 Or somethng wich was Android 4.3....
Click to expand...
Click to collapse
install the TWRP recovery and flash the rom again
and do the wipe/factory reset

clsA said:
install the TWRP recovery and flash the rom again
and do the wipe/factory reset
Click to expand...
Click to collapse
Uhhmmm.... I cant install TWRP when it still cant find my Phone

pottemans said:
Uhhmmm.... I cant install TWRP when it still cant find my Phone
Click to expand...
Click to collapse
it's a flashable zip flash it the same you do a rom
Edit: Instructions
copy TWRP_2.6.3.3_m7.zip to your fastboot/adb folder
boot phone to recovery wait a few seconds then from PC
adb push TWRP_2.6.3.3_m7.zip /data/media/0
wait for it to copy
now from CWM install zip
find the file you just pushed and install it
next you would reboot back to recovery again (TWRP)
choose install then find your rom
Click to expand...
Click to collapse

clsA said:
it's a flashable zip flash it the same you do a rom
Click to expand...
Click to collapse
Yeah I know, but i cant get into recovery AND the rom itself... SO when i want to boot in recovery, it gives me a black screen and then it reboots and i´m stuck at the HTC quietly brillant screen with the red warnings.... Thats my problem.... If i could boot into recovery, i could easily restore my backup, but it wont boot in recovery...

pottemans said:
Yeah I know, but i cant get into recovery AND the rom itself... SO when i want to boot in recovery, it gives me a black screen and then it reboots and i´m stuck at the HTC quietly brillant screen with the red warnings.... Thats my problem.... If i could boot into recovery, i could easily restore my backup, but it wont boot in recovery...
Click to expand...
Click to collapse
well if that's the case your going to need a windows 7 pc long enough to install twrp from fastboot

clsA said:
well if that's the case your going to need a windows 7 pc long enough to install twrp from fastboot
Click to expand...
Click to collapse
I do have iMac aswell...... any possibility to do this on a mac or something

pottemans said:
I do have iMac aswell...... any possibility to do this on a mac or something
Click to expand...
Click to collapse
sure all the commands are the same
you just need the mac versions of fastboot and adb
http://forum.xda-developers.com/showthread.php?t=2245782

clsA said:
sure all the commands are the same
you just need the mac versions of fastboot and adb
http://forum.xda-developers.com/showthread.php?t=2245782
Click to expand...
Click to collapse
okay so I flashed the TWRP recovery, but when I enter the recovery, it reboots again.... Do I need to install ARHD 31.6 via fast boot?
If so how?

Soft bricked phone need help with side loading

I tried it install a new ROM and something went wrong. When it went wrong it went wrong. I lost all my backups and everything. I can get into TWRP right now. If I try and reboot with out going to TWRP I am just stuck at the white HTC screen. So I think the boot is messed up.
In searching looks like I will need to sideload via TWRP a new ROM to load. I can not find a good DIY for the sideload. I turn on sideloading and my PC sees my phone and loads it as a E drive. I an not get into my phone. I am searching through a lot of posts but with out luck. Just people saying they did it with out saying how.
Thank you for any help.

veener79 said:
I tried it install a new ROM and something went wrong. When it went wrong it went wrong. I lost all my backups and everything. I can get into TWRP right now. If I try and reboot with out going to TWRP I am just stuck at the white HTC screen. So I think the boot is messed up.
In searching looks like I will need to sideload via TWRP a new ROM to load. I can not find a good DIY for the sideload. I turn on sideloading and my PC sees my phone and loads it as a E drive. I an not get into my phone. I am searching through a lot of posts but with out luck. Just people saying they did it with out saying how.
Thank you for any help.
Click to expand...
Click to collapse
What rom did you flashed? What TWRP version are you using?

alray said:
What rom did you flashed? What TWRP version are you using?
Click to expand...
Click to collapse
RENOVATE | Milestone 8.1 | Sense 5.5 | 4.19.401.8
TWRP 2.5.0.0
Thank you

veener79 said:
RENOVATE | Milestone 8.1 | Sense 5.5 | 4.19.401.8
TWRP 2.5.0.0
Thank you
Click to expand...
Click to collapse
4.4 roms need latest twrp to be flashed correctly
either twrp 2.6.6.3 or 2.6.6.4
So download and flash latest version and flash the rom again.

alray said:
4.4 roms need latest twrp to be flashed correctly
either twrp 2.6.6.3 or 2.6.6.4
So download and flash latest version and flash the rom again.
Click to expand...
Click to collapse
OK how do I get the files over. I just found my OTG cable!!! Going to see if I can load on a zip. If not is there a good DIY for how to sideload.

veener79 said:
OK how do I get the files over. I just found my OTG cable!!! Going to see if I can load on a zip. If not is there a good DIY for how to sideload.
Click to expand...
Click to collapse
http://goo.im/devs/OpenRecovery/m7/
http://techerrata.com/browse/twrp2/m7ul
From fastboot
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
in custom recovery, either
adb push <name of rom>.zip /sdcard/
or
adb sideload <name of rom>.zip
Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
From the command line, type adb sideload rom.zip

veener79 said:
OK how do I get the files over. I just found my OTG cable!!! Going to see if I can load on a zip. If not is there a good DIY for how to sideload.
Click to expand...
Click to collapse
flash latest twrp (I assume here you hame the m7_u or m7_ul not a wls variant):
http://techerrata.com/browse/twrp2/m7
Code:
fastboot flash recovery <name_of_file>.img
fastboot erase cache
fastboot reboot-bootloader
then push the rom:
Code:
adb push <name_of_file>.zip /sdcard/
and install from twrp
or adb sideload it:
select sideload in twrp
Code:
adb sideload <name_of_file>.zip

OK nothing wants to work today!!!!!
Opened up the comand promp in the fastboot folder. My phone states Fastboot USB in red.
Getting "Error can not load twrp.img"

veener79 said:
OK nothing wants to work today!!!!!
Opened up the comand promp in the fastboot folder. My phone states Fastboot USB in red.
Getting "Error can not load twrp.img"
Click to expand...
Click to collapse
is the file in your adb/fastboot folder?

veener79 said:
OK nothing wants to work today!!!!!
Opened up the comand promp in the fastboot folder. My phone states Fastboot USB in red.
Getting "Error can not load twrp.img"
Click to expand...
Click to collapse
are you drivers installed correctly ?
what does fastboot devices return ?

alray said:
is the file in your adb/fastboot folder?
Click to expand...
Click to collapse
Yes
clsA said:
are you drivers installed correctly ?
what does fastboot devices return ?
Click to expand...
Click to collapse
How can I tell if something is off? When I plug in my phone it will state Fastboot and then after I hear it conect to my laptop it will go back to fastboot USB in red.
Typed in fastbood devices and get ht344w910402 fastboot

veener79 said:
Yes
How can I tell if something is off? When I plug in my phone it will state Fastboot and then after I hear it conect to my laptop it will go back to fastboot USB in red.
Typed in fastbood devices and get ht344w910402 fastboot
Click to expand...
Click to collapse
can you post a screanshot of your cmd prompt when it fail plz

alray said:
can you post a screanshot of your cmd prompt when it fail plz
Click to expand...
Click to collapse
Will do. I have to get something done this morning and I am running way late. So I have to get going. Thank goodness I have a old phone laying around. When I get home in about 5 hours will post back up. Thank you all so much for your help!!!!!!

alray said:
4.4 roms need latest twrp to be flashed correctly
either twrp 2.6.6.3 or 2.6.6.4
So download and flash latest version and flash the rom again.
Click to expand...
Click to collapse
clsA said:
http://goo.im/devs/OpenRecovery/m7/
http://techerrata.com/browse/twrp2/m7ul
From fastboot
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
in custom recovery, either
adb push <name of rom>.zip /sdcard/
or
adb sideload <name of rom>.zip
Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
From the command line, type adb sideload rom.zip
Click to expand...
Click to collapse
alray said:
flash latest twrp (I assume here you hame the m7_u or m7_ul not a wls variant):
http://techerrata.com/browse/twrp2/m7
Code:
fastboot flash recovery <name_of_file>.img
fastboot erase cache
fastboot reboot-bootloader
then push the rom:
Code:
adb push <name_of_file>.zip /sdcard/
and install from twrp
or adb sideload it:
select sideload in twrp
Code:
adb sideload <name_of_file>.zip
Click to expand...
Click to collapse
veener79 said:
OK nothing wants to work today!!!!!
Opened up the comand promp in the fastboot folder. My phone states Fastboot USB in red.
Getting "Error can not load twrp.img"
Click to expand...
Click to collapse
veener79 said:
Yes
How can I tell if something is off? When I plug in my phone it will state Fastboot and then after I hear it conect to my laptop it will go back to fastboot USB in red.
Typed in fastbood devices and get ht34xxxxxxxxx fastboot
Click to expand...
Click to collapse
Sorry guys ( @clsA and @alray), I don't know why I keep getting the urge to bug in
M7U/UL TWRP:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
verify MD5, that site does not play nice with download managers
Typed in fastbood devices and get ht34xxxxxxxxx fastboot
Click to expand...
Click to collapse
-> means your device is in fastboot
go ahead, as suggested
Code:
fastboot flash recovery <name_of_file>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery
then as suggested
Code:
adb push <name_of_file>.zip /sdcard/
and install from twrp
or use sideload, whatever makes you happy
sorry again guys
i'll bug out now
PS: "cannot load" = the filename is wrong!! that's all

Ok got home and I tried a different USB port. I did a sideload of a older version on the ROM that I knew was good and phone is back up and working. Thank you all! Thanks are given out!

[SOLVED] [Q] [HELP]Bricked HTC One (stuck in bootloop, green htc log)o

First of all I would like to apologize if I posted this in the wrong forum or section. I just registered this account to ask for help regarding my bricked HTC One (m7ul). I am not a newbie to XDA as I have visited this site more than once to learn the fundamentals of rooting android phone and so on. I unlocked my bootloader via HTCDev and rooted it using CWM Touch Recovery 6.0.4.5. 3 weeks ago I flashed my HTC One to Probam (AOSB) custom rom, no problems were present, everything ran smoothly and perfectly. Then, 2 weeks ago, I decided to flash ElementalX kernel, being ignorant on purpose to the fact that it was meant for Sense Roms. Upom completion through Aroma Installer, I selected reboot system in recovery. Upon exit, the recovery told me that my phone could have possibly lost its root access and prompted me to root it so i just agreed. There came the problem upon reboot, I could not boot into my OS and I was stuck on the HTC screen. (May I add that I bought my HTC this year March. I S-offed it via Firewater as my Hboot version was 1.56 and Rumrunner couldn't help me S-Off. Advice for those who have hboot versions higher than 1.55 and want to S-off, Firewater is my suggestion. Just make sure you follow the guid also here on XDA forums accurately and I assure you can get s-off) As I was saying, as soon as that happened, I looked for solutions. I tried hasson 2000 all in one toolkit, I tried relocking my bootloader and runming RUU.exe file to return to stock firmware, I tried sideloading a rom in recovery, I tried mounting usb storage to copy a .zip rom into my internal storage but nothing happened. I tried flashing directly via fastboot but the cmd keep saying it couldnt run the file. I couldn't enter adb as the recovery said there is no os present. I really have no more idea what else I can do and I think I've tried just about everything. Please help as it's been 2 weeks into the brick and I'm really desperate. Please help
CID: HTC_044
Hboot:1.56
If there is more information needed please ask as I'm really desperate to fix my phone :C

boksquare said:
First of all I would like to apologize if I posted this in the wrong forum or section. I just registered this account to ask for help regarding my bricked HTC One (m7ul). I am not a newbie to XDA as I have visited this site more than once to learn the fundamentals of rooting android phone and so on. I unlocked my bootloader via HTCDev and rooted it using CWM Touch Recovery 6.0.4.5. 3 weeks ago I flashed my HTC One to Probam (AOSB) custom rom, no problems were present, everything ran smoothly and perfectly. Then, 2 weeks ago, I decided to flash ElementalX kernel, being ignorant on purpose to the fact that it was meant for Sense Roms. Upom completion through Aroma Installer, I selected reboot system in recovery. Upon exit, the recovery told me that my phone could have possibly lost its root access and prompted me to root it so i just agreed. There came the problem upon reboot, I could not boot into my OS and I was stuck on the HTC screen. (May I add that I bought my HTC this year March. I S-offed it via Firewater as my Hboot version was 1.56 and Rumrunner couldn't help me S-Off. Advice for those who have hboot versions higher than 1.55 and want to S-off, Firewater is my suggestion. Just make sure you follow the guid also here on XDA forums accurately and I assure you can get s-off) As I was saying, as soon as that happened, I looked for solutions. I tried hasson 2000 all in one toolkit, I tried relocking my bootloader and runming RUU.exe file to return to stock firmware, I tried sideloading a rom in recovery, I tried mounting usb storage to copy a .zip rom into my internal storage but nothing happened. I tried flashing directly via fastboot but the cmd keep saying it couldnt run the file. I couldn't enter adb as the recovery said there is no os present. I really have no more idea what else I can do and I think I've tried just about everything. Please help as it's been 2 weeks into the brick and I'm really desperate. Please help
CID: HTC_044
Hboot:1.56
If there is more information needed please ask as I'm really desperate to fix my phone :C
Click to expand...
Click to collapse
you do realize what you posted is not readable... right? sorry, but i sort of tried reading it, but
break it down into smaller parts.

nkk71 said:
you do realize what you posted is not readable... right? sorry, but i sort of tried reading it, but
break it down into smaller parts.
Click to expand...
Click to collapse
he flashed a sense kernel to an aosp rom and is in bootloop as near as i can tell
he's s-off hboot 1.56 and needs a RUU I assume

boksquare said:
(...)
I unlocked my bootloader via HTCDev and rooted it using CWM Touch Recovery 6.0.4.5.
(...)
I flashed my HTC One to Probam (AOSB) custom rom, no problems were present,
(...)
I decided to flash ElementalX kernel, being ignorant on purpose to the fact that it was meant for Sense Roms.
(...)
I could not boot into my OS and I was stuck on the HTC screen.
(...)
I S-offed it via Firewater
(...)
Click to expand...
Click to collapse
Did you tried to flash an AOSP compatible kernel after you realized you couldn't boot the phone?
boksquare said:
I tried hasson 2000 all in one toolkit
Click to expand...
Click to collapse
You should use fastboot and adb from cmd prompt instead of toolkit.
boksquare said:
I tried relocking my bootloader and runming RUU.exe file to return to stock firmware,
Click to expand...
Click to collapse
Re-locking bootloader to run a ruu.exe is not required when you have S-OFF. Anyway what was the error code when the RUU exe failed? And what was the ruu version?
boksquare said:
I tried sideloading a rom in recovery
Click to expand...
Click to collapse
What happened? What was the error? What rom?
boksquare said:
I tried mounting usb storage to copy a .zip rom into my internal storage but nothing happened.
Click to expand...
Click to collapse
If you can mount your usb storage with your rom.zip on it, you don't need to copy it to your sdcard! Just install the rom from your mounted usb storage... You said ''nothing happened'' Was there any error code?
boksquare said:
I tried flashing directly via fastboot but the cmd keep saying it couldnt run the file.
Click to expand...
Click to collapse
Wait?! You can't flash a rom.zip from fastboot, only from custom recovery. The only thing you can flash from fastboot is a recovery or a ruu/firmware from fastboot RUU mode.
boksquare said:
I couldn't enter adb as the recovery said there is no os present.
Click to expand...
Click to collapse
ADB should work from custom recovery even if you don't have an OS installed.
boksquare said:
(...)
CID: HTC_044
Hboot:1.56
Click to expand...
Click to collapse
post the output of ''fastboot getvar all'' except IMEI. With S-OFF it should be quite easy to make your phone boot again...

clsA said:
he flashed a sense kernel to an aosp rom and is in bootloop as near as i can tell
he's s-off hboot 1.56 and needs a RUU I assume
Click to expand...
Click to collapse
still... if (yes IF) i learned anything in school "run-on" sentences are a NO-NO!! (and i'm not even talking about english schools)

alray said:
Did you tried to flash an AOSP compatible kernel after you realized you couldn't boot the phone?
Click to expand...
Click to collapse
- No, I downloaded and flashed the kernel on my One while I was outstation, so I couldn't do anything when it was stuck on bootloop.
You should use fastboot and adb from cmd prompt instead of toolkit.
Click to expand...
Click to collapse
-I couldn't get into adb through fastboot with the command on cmd "adb reboot bootloader" (attachment below [capture])
Re-locking bootloader to run a ruu.exe is not required when you have S-OFF. Anyway what was the error code when the RUU exe failed? And what was the ruu version?
Click to expand...
Click to collapse
-That's the problem, there was no error code or anything, it just didn't work, nothing happened. [Capture3]
What happened? What was the error? What rom?
Click to expand...
Click to collapse
-It said device not found. [Capture1]
If you can mount your usb storage with your rom.zip on it, you don't need to copy it to your sdcard! Just install the rom from your mounted usb storage... You said ''nothing happened'' Was there any error code?
Click to expand...
Click to collapse
- I believe you and I have a different understanding of usb storage which obviously I'm misinformed. I thought USB Storage is just mounting your CPU storage to your phone.
ADB should work from custom recovery even if you don't have an OS installed.
Click to expand...
Click to collapse
-Not sure, nothing worked.
post the output of ''fastboot getvar all'' except IMEI. With S-OFF it should be quite easy to make your phone boot again...
Click to expand...
Click to collapse
-Capture2 below.
Again I apologize for any inconvenience caused, I'm still new to using XDA forums instead of just reading it for info, thanks and please reply ASAP, desperate and losing hope

boksquare said:
-It said device not found. [Capture1]
Click to expand...
Click to collapse
check you check FAQ #2 in my guide (forget the guide, just the FAQ#2) http://forum.xda-developers.com/showthread.php?t=2541082

nkk71 said:
check you check FAQ #2 in my guide (forget the guide, just the FAQ#2) http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
The problem is, my phone won't even show up in my computer, I've no idea why.

nkk71 said:
check you check FAQ #2 in my guide (forget the guide, just the FAQ#2) http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
I would like to try your method for using the RUU.exe through downgrading hboot all those, but if I downgraded my hboot and everything, and the RUU.exe doesn't work, will my phone go beyond saving? Please advice.

boksquare said:
I would like to try your method for using the RUU.exe through downgrading hboot all those, but if I downgraded my hboot and everything, and the RUU.exe doesn't work, will my phone go beyond saving? Please advice.
Click to expand...
Click to collapse
i think you're rushing things, but since you're s-off, go for ruu.zip method, shows much more information, but beware Win8.1 as mentioned in the FAQs.
(also there's no need to LOCK since you're s-off, and dont even think about S-On, the guide was meant as return to stock for warranty.
i'm sure you can Device Manager fixed, it's probably somewhere there, just needs corrected/updated drivers, and by the way, don't use TWRP 2.7.0.0 it has problems with adb.

nkk71 said:
i think you're rushing things, but since you're s-off, go for ruu.zip method, shows much more information, but beware Win8.1 as mentioned in the FAQs.
(also there's no need to LOCK since you're s-off, and dont even think about S-On, the guide was meant as return to stock for warranty.
i'm sure you can Device Manager fixed, it's probably somewhere there, just needs corrected/updated drivers, and by the way, don't use TWRP 2.7.0.0 it has problems with adb.
Click to expand...
Click to collapse
Okay, I will get to it right away, but before that, I was using CWM Touch 6.0.4.5 but I still can't get adb in cmd. Once I've entered recovery I will automatically find adb through "adb devices" command without having to do anything special? And do I need to remove tampered all those before running RUU.Zip? Or is it just for going back to stock? I am sorry, as there are just a lot of things I'm not clear about or understand. Please advice :/

boksquare said:
I was using CWM Touch 6.0.4.5 but I still can't get adb in cmd. Once I've entered recovery I will automatically find adb through "adb devices" command without having to do anything special?
Click to expand...
Click to collapse
if adb devices doesn't list your device, then you have to check Windows Device Manager and fix the driver problems.
boksquare said:
And do I need to remove tampered all those before running RUU.Zip? Or is it just for going back to stock?
Click to expand...
Click to collapse
You can leave everything as is, tampered doesn't matter in any case, and unlocked won't matter with S-OFF.
DO NOT GO S-ON.
boksquare said:
I am sorry, as there are just a lot of things I'm not clear about or understand. Please advice :/
Click to expand...
Click to collapse
No problem, better to ask before, otherwise you could end up in a worse situation.
But still don't understand why want to go all the trouble of ruu. can you explain (briefly, not a huge paragraph :angel
By the way, if you're stuck in a bootloop because you were flashing a 4.4 ROM using CWM 6.0.4.5, then that would be the problem, you need TWRP 2.6.3.3 or higher.

nkk71 said:
if adb devices doesn't list your device, then you have to check Windows Device Manager and fix the driver problems.
You can leave everything as is, tampered doesn't matter in any case, and unlocked won't matter with S-OFF.
DO NOT GO S-ON.
No problem, better to ask before, otherwise you could end up in a worse situation.
But still don't understand why want to go all the trouble of ruu. can you explain (briefly, not a huge paragraph :angel
By the way, if you're stuck in a bootloop because you were flashing a 4.4 ROM using CWM 6.0.4.5, then that would be the problem, you need TWRP 2.6.3.3 or higher.
Click to expand...
Click to collapse
Don't worry I won't enter S-On.
But before the brick there were no problems with the drivers as I had installed HTC Sync Drivers. After the brick my phone just couldn't be detected in my computer. I just assumed this problem is linked with the brick.
Because I have no idea what other methods can save my phone, please advice if there are other methods beside RUU

boksquare said:
Don't worry I won't enter S-On.
But before the brick there were no problems with the drivers as I had installed HTC Sync Drivers. After the brick my phone just couldn't be detected in my computer. I just assumed this problem is linked with the brick.
Because I have no idea what other methods can save my phone, please advice if there are other methods beside RUU
Click to expand...
Click to collapse
So after reading your first post i see you tried flashing a 4.4 rom using CWM 6.0.4.5, so
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then install the ROM again.

nkk71 said:
So after reading your first post i see you tried flashing a 4.4 rom using CWM 6.0.4.5, so
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then install the ROM again.
Click to expand...
Click to collapse
But the ROM is not in my Htc, how do I move it there? I had no way of moving it there that's why I went for the RUU

boksquare said:
But the ROM is not in my Htc, how do I move it there? I had no way of moving it there that's why I went for the RUU
Click to expand...
Click to collapse
you have 3 choices to get the ROM onto your phone (once you have custom recovery):
1- OTG cable
2- adb sideload
3- adb push
If you don't have OTG cable, I personally like adb push (example below), though many like adb sideload (plenty of guides and how tos around).
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY
Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.

nkk71 said:
you have 3 choices to get the ROM onto your phone (once you have custom recovery):
1- OTG cable
2- adb sideload
3- adb push
If you don't have OTG cable, I personally like adb push (example below), though many like adb sideload (plenty of guides and how tos around).
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY
Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.
Click to expand...
Click to collapse
Okay, I'm downloading the drivers after checking the device manager. You were right, the drivers were gone. I had no idea why. I installed Sync Manager before with all the drivers present, no idea why is it gone now.
Still, once the download is finished I will do as you said and will update you ASAP. Thanks in advance. :good::laugh:

boksquare said:
Okay, I'm downloading the drivers after checking the device manager. You were right, the drivers were gone. I had no idea why. I installed Sync Manager before with all the drivers present, no idea why is it gone now.
Still, once the download is finished I will do as you said and will update you ASAP. Thanks in advance. :good::laugh:
Click to expand...
Click to collapse
No problem, good luck

nkk71 said:
No problem, good luck
Click to expand...
Click to collapse
OMG OMG OMG OMG OMG OMG OMG OMG OMG !!!! It worked !!!! At first I was disappointed as I couldn't fix my drivers by reinstalling HTC Sync Manager. I was going to ask you but I took a look back into your guide at FAQ #2 and followed it exactly and I got it reinstalled )))) I pushed the ROM in and flashed in Recovery and I just booted my phone ! Thanks for all your time and advices, really appreciated it. How I wish I could thank you in person or something. Thanks man, really thanks a lot

boksquare said:
OMG OMG OMG OMG OMG OMG OMG OMG OMG !!!! It worked !!!! At first I was disappointed as I couldn't fix my drivers by reinstalling HTC Sync Manager. I was going to ask you but I took a look back into your guide at FAQ #2 and followed it exactly and I got it reinstalled )))) I pushed the ROM in and flashed in Recovery and I just booted my phone ! Thanks for all your time and advices, really appreciated it. How I wish I could thank you in person or something. Thanks man, really thanks a lot
Click to expand...
Click to collapse
My pleasure glad everything worked out, and xda has a nice little thanks button that you can press when a post is useful
and if you could also edit the main thread title to include [SOLVED] (go to 1st post click EDIT, at the bottom of the edit window click GO ADVANCED, then you can edit the main title), thanks

[Q] Htc One stuck at Htc Logo

Hey,
I have a huge problem and do not know what to do. I write what is in the bootloader:
Locked
M7 UL PVT Ship s-on rh
Hboot 1.57
Factory reset do not work. I did not find anything in the internet. It seems the mobile is not rooted or had a custom rom right?
It is from T mobile and when the T mobile logo appears it is like the graphic card has a problem, then it stucks when the htc logo is there.
anyone an idea? If someone find the problem he/she can have a goodie :crying::crying::crying::crying::crying:

lutoluto said:
Hey,
I have a huge problem and do not know what to do. I write what is in the bootloader:
Locked
M7 UL PVT Ship s-on rh
Hboot 1.57
Factory reset do not work. I did not find anything in the internet. It seems the mobile is not rooted or had a custom rom right?
It is from T mobile and when the T mobile logo appears it is like the graphic card has a problem, then it stucks when the htc logo is there.
anyone an idea? If someone find the problem he/she can have a goodie :crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
your phone looks like to be stock (unmodified) so you should first contact t-mob to repair/replace the phone under warranty. If a factory reset has not solved the issue you'll probably have, at least, to unlock the bootloader and that may void your warranty.
You might also want to try this command from bootloader:
Code:
fastboot erase cache
fastboot reboot
and see if the phone can boot normally, if not ---> claim warranty, if no warranty ---> unlock bootloader a flash a rom to see if the phone can boot with a fresh install, if not ---> probably an hardware defect.

alray said:
your phone looks like to be stock (unmodified) so you should first contact t-mob to repair/replace the phone under warranty. If a factory reset has not solved the issue you'll probably have, at least, to unlock the bootloader and that may void your warranty.
You might also want to try this command from bootloader:
Code:
fastboot erase cache
fastboot reboot
and see if the phone can boot normally, if not ---> claim warranty, if no warranty ---> unlock bootloader a flash a rom to see if the phone can boot with a fresh install, if not ---> probably an hardware defect.
Click to expand...
Click to collapse
no warranty. any good tut for the flash unlock thingg?

lutoluto said:
no warranty. any good tut for the flash unlock thingg?
Click to expand...
Click to collapse
first try to clear cache as it will not wipe any of your data from the phone
Code:
fastboot erase cache
fastboot reboot
then if it doesnt work you can try to unlock the bootloader (will wipe everything) and test if another rom can boot.

alray said:
first try to clear cache as it will not wipe any of your data from the phone
Code:
fastboot erase cache
fastboot reboot
then if it doesnt work you can try to unlock the bootloader (will wipe everything) and test if another rom can boot.
Click to expand...
Click to collapse
I did it. in the cmd it asks if I meant formating this partition, but said ok. but it is stucking on the logo again.
I think it is a hardware thing. but do you know what to do now to unlock it and get a rom on it?

lutoluto said:
I did it. in the cmd it asks if I meant formating this partition, but said ok. but it is stucking on the logo again.
I think it is a hardware thing. but do you know what to do now to unlock it and get a rom on it?
Click to expand...
Click to collapse
first, follow these 2 video tutorials to unlock the bootloader and flash twrp recovery 2.6.3.3

alray said:
first, follow these 2 video tutorials to unlock the bootloader and flash twrp recovery 2.6.3.3
Click to expand...
Click to collapse
I think you forgot to post them !?:crying:

lutoluto said:
I think you forgot to post them !?:crying:
Click to expand...
Click to collapse
yeah sorry http://forum.xda-developers.com/htc-one#root
:laugh:

alray said:
yeah sorry http://forum.xda-developers.com/htc-one#root
:laugh:
Click to expand...
Click to collapse
So I did this and it worked. BUT! I am in Clockwork recovery blabla where I need to select something from sd cardnright? but it is htc one m7 xD there is no sd card or if I cant get the back open. Something is written here in recovery sendingvia sideload!? any idea if there is a way get a file on my phone?

lutoluto said:
So I did this and it worked. BUT! I am in Clockwork recovery blabla where I need to select something from sd cardnright? but it is htc one m7 xD there is no sd card or if I cant get the back open. Something is written here in recovery sendingvia sideload!? any idea if there is a way get a file on my phone?
Click to expand...
Click to collapse
You have flashed cwm recovery? like I said in post #6, you'll need to flash TWRP recovery 2.6.3.3. then you'll be able to adb push or adb sideload a rom to your phone.

alray said:
You have flashed cwm recovery? like I said in post #6, you'll need to flash TWRP recovery 2.6.3.3. then you'll be able to adb push or adb sideload a rom to your phone.
Click to expand...
Click to collapse
Oh ****, I just did what was in the videos. So now I have to download the new cwm and flash it?! Ok wait a minute

lutoluto said:
Oh ****, I just did what was in the videos. So now I have to download the new cwm and flash it?! Ok wait a minute
Click to expand...
Click to collapse
not the new cwm recovery.... TWRP recovery 2.6.3.3.
alray said:
first, follow these 2 video tutorials to unlock the bootloader and flash twrp recovery 2.6.3.3
Click to expand...
Click to collapse
alray said:
You have flashed cwm recovery? like I said in post #6, you'll need to flash TWRP recovery 2.6.3.3. then you'll be able to adb push or adb sideload a rom to your phone.
Click to expand...
Click to collapse
you can flash TWRP recovery 2.6.3.3 the same way you did for cwm, same procedure:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader

lutoluto said:
I think you forgot to post them !?:crying:
Click to expand...
Click to collapse
Hey, it is not opening the 2.6.3.3 I have. you have a link?

lutoluto said:
Hey, it is not opening the 2.6.3.3 I have. you have a link?
Click to expand...
Click to collapse
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img

alray said:
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Click to expand...
Click to collapse
okay and now?

lutoluto said:
okay and now?
Click to expand...
Click to collapse
boot in twrp recovery (bootloader ---> recovery)
when booted in twrp main menu, select "wipe" then wipe everything + format data
download this rom and save it in your adb/fastboot folder on your pc.
with your phone still booted in twrp enter this command:
Code:
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
wait between 5-10 min untill the file is copied to your phone (no progress bar, just wait until you get back the command prompt)
then in twrp select "install" from the main menu then browse the sdcard to find Android_Revolution_HD-One_71.1.zip and select it, swipe to confirm flash, wait until the rom is flashed and reboot phone and hopefully it will boot correctly.

alray said:
boot in twrp recovery (bootloader ---> recovery)
when booted in twrp main menu, select "wipe" then wipe everything + format data
download this rom and save it in your adb/fastboot folder on your pc.
with your phone still booted in twrp enter this command:
Code:
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
wait between 5-10 min untill the file is copied to your phone (no progress bar, just wait until you get back the command prompt)
then in twrp select "install" from the main menu then browse the sdcard to find Android_Revolution_HD-One_71.1.zip and select it, swipe to confirm flash, wait until the rom is flashed and reboot phone and hopefully it will boot correctly.
Click to expand...
Click to collapse
at format data he is unable to mount cache and when wipe he says not succesful. I will continue what you wrote and write then again

alray said:
boot in twrp recovery (bootloader ---> recovery)
when booted in twrp main menu, select "wipe" then wipe everything + format data
download this rom and save it in your adb/fastboot folder on your pc.
with your phone still booted in twrp enter this command:
Code:
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
wait between 5-10 min untill the file is copied to your phone (no progress bar, just wait until you get back the command prompt)
then in twrp select "install" from the main menu then browse the sdcard to find Android_Revolution_HD-One_71.1.zip and select it, swipe to confirm flash, wait until the rom is flashed and reboot phone and hopefully it will boot correctly.
Click to expand...
Click to collapse
When I type in what you said there is just a message saying error: more than one device and emulator.... T_T

lutoluto said:
When I type in what you said there is just a message saying error: more than one device and emulator.... T_T
Click to expand...
Click to collapse
so you have any other android device connected on your pc? if yes disconnect the other device or you can also direct the adb command to the specified device (your htc one)
find the serial number corresponding to your phone and use it with the following command
Code:
adb -s your_serial_number push Android_Revolution_HD-One_71.1.zip /sdcard/
to find your serial number do
Code:
adb devices
lets say your phone sn is HT386W890355
Code:
adb -s HT386W890355 push Android_Revolution_HD-One_71.1.zip /sdcard/

alray said:
so you have any other android device connected on your pc? if yes disconnect the other device or you can also direct the adb command to the specified device (your htc one)
find the serial number corresponding to your phone and use it with the following command
Code:
adb -s your_serial_number push Android_Revolution_HD-One_71.1.zip /sdcard/
to find your serial number do
Code:
adb devices
lets say your phone sn is HT386W890355
Code:
adb -s HT386W890355 push Android_Revolution_HD-One_71.1.zip /sdcard/
Click to expand...
Click to collapse
Okay now a lot of text is ran under the command. I think that is a good sign, I will wait

Issues with flashing TWRP to tablet

I am trying to go through the process of flashing a custom recovery so that I can get off of stock and on to a custom rom. I have gone through the following steps:
1) downloaded the latest drivers
2) downloaded the latest version of fastboot
3) downloaded twrp 2.8.1.0 and checked the MD5 for the program
4) enabled the usb debugging, signed on as an administrator in my pc, and am using a 2.0 usb port
5) have verified the conenction between tablet and PC.
I get the following result:
C:\>fastboot devices
15C3E100910000000XXXXXXXX fastboot (I edited out a few numbers and replaced them with with x's, but got a pure result)
C:\>fastboot -i 0x0B05 flash recovery twrp.blob
target reported max download size of 643825664 bytes
sending 'recovery' (7024 KB)...
OKAY [ 0.964s]
writing 'recovery'...
OKAY [ 0.241s]
finished. total time: 1.213s
C:\>fastboot reboot
rebooting...
finished. total time: 0.021s
The recovery is not actually flashing over to the device. When I attempt the flash I do a fastboot reboot and power down afterwards, then try to boot back up to the recovery and instead I get the bried vision of the android and the blue bar underneath before it's promptly replaced by the dead android. The twrp.blob file is in the same directory as fastboot. I have tried deleting and re-downloading both the blob file and the drivers. I have tried using 2.8.0.1 and 2.8.1.0. Because TWRP wasn't working I tried flashing CWM and got exactly the same result. There doesn't seem to be an issue with the cable, since I can move other forms of data between the devices with no issue. I'm beating my head against the wall here, and am hoping that you guys might be able to provide me with some direction as to what else I might try/look for. Thanks all.

Are you sure you are using the correct recovery for your device? There is no version of TWRP that works with the TF701T.

Sleeepy2 said:
Are you sure you are using the correct recovery for your device? There is no version of TWRP that works with the TF701T.
Click to expand...
Click to collapse
I had been advised that the version for the TF700 would also work with the TF701T. However, I did use a CWM version specific to the TF701T with the same result you saw in the command window in my OP.

talion777 said:
I had been advised that the version for the TF700 would also work with the TF701T. However, I did use a CWM version specific to the TF701T with the same result you saw in the command window in my OP.
Click to expand...
Click to collapse
I am not sure who told you that but it is 100% wrong.
I am also not sure what the commands that you are sending are however you should just be doing
fastboot flash recovery recovery.img
Get the recovery from this link
http://droidbasement.com/asus/tf701t/recovery/

Sleeepy2 said:
I am not sure who told you that but it is 100% wrong.
I am also not sure what the commands that you are sending are however you should just be doing
fastboot flash recovery recovery.img
Get the recovery from this link
http://droidbasement.com/asus/tf701t/recovery/
Click to expand...
Click to collapse
Thanks Sleeepy, but as I mentioned in the OP I did the flash for the CWM recovery already, using exactly the link you sent me, with the exact same commands, and with the same results. No go.
P.P.S. - also tried juggling around the MTP and PTP modes (plug/unplug while on/off) to ensure recognition and it seems fine both ways. Someone else had said they freed up their drivers that way but it made no difference on my end.
P.S. - Here, just so that you see, here are the command window results for th CWM recovery, just for clarity's sake:
C:\adb 2>fastboot devices
15C3E100910000000XXXXXXXX fastboot
C:\adb 2>fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
sending 'recovery' (6646 KB)...
OKAY [ 0.910s]
writing 'recovery'...
OKAY [ 0.230s]
finished. total time: 1.140s
C:\adb 2>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\adb 2>

That's really odd.
I just downloaded the most recent version and tried re-flashing just to make sure and I had no issues...
Can you boot the recovery without flashing it?
fastboot boot recovery.img
Sorry, this defiantly not strong point but I will try to help.

Sleeepy2 said:
That's really odd.
I just downloaded the most recent version and tried re-flashing just to make sure and I had no issues...
Can you boot the recovery without flashing it?
fastboot boot recovery.img
Sorry, this defiantly not strong point but I will try to help.
Click to expand...
Click to collapse
yes, I can boot the recovery. Am I able to use the temp image to install the recovery into the tablet, or to import the files I need to do so?

talion777 said:
yes, I can boot the recovery. Am I able to use the temp image to install the recovery into the tablet, or to import the files I need to do so?
Click to expand...
Click to collapse
The temp image will work just like normal.

Sleeepy2 said:
The temp image will work just like normal.
Click to expand...
Click to collapse
except that I will always need to be connected to my PC to use it. How do I actually make that the default recovery in my tablet? It just seems bizarre to me that I can boot the image but that I can't flash it. Also, assuming I used the image to flash a custom ROM what happens when the temp image is shut off and the recovery reverts to stock? Would the ROM work with a stock recovery?
Was able to use the CWM image to install SuperSU and root the tablet. Still can't get the recovery to flash over.

Wait... what version of bootloader do you have?
You are unlocked and updated to the most recent ASUS version right...

Sleeepy2 said:
Wait... what version of bootloader do you have?
You are unlocked and updated to the most recent ASUS version right...
Click to expand...
Click to collapse
I'm on 11.4.1.17, and yes I'm on the latest ASUS update.

Damn... that was my last guess. You need to get the attention of someone smarter than me like pershoot or berndblb
Sorry I can't help any better.

Thanks Sleeepy, you've already been a big help and I really appreciate the effort!

talion777 said:
Thanks Sleeepy, you've already been a big help and I really appreciate the effort!
Click to expand...
Click to collapse
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.

berndblb said:
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
Click to expand...
Click to collapse
You sir, would appear to be a genius. CWN successfully flashed to the tab. Excellent! Thanks so very much to both you and Sleeepy for your help. This was driving me absolutely bananas!

berndblb said:
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
Click to expand...
Click to collapse
God damn it. You step in with one comment and boom, like magic it works
And @talion777 glad you've got it working now

Sleeepy2 said:
God damn it. You step in with one comment and boom, like magic it works
And @talion777 glad you've got it working now
Click to expand...
Click to collapse
A lucky guess.. LOL
Actually I worked with talion on the Transformer forums on his problem, so it was not quite as magical as it may sound. [emoji56]