Hey all,
So tonight I attempted to install the Unofficial AOKP Jelly Bean posted here: http://forum.xda-developers.com/showthread.php?t=1862156
Before doing that, I followed the instructions to Unlock, Recovery, and Root my One S here: http://forum.xda-developers.com/showthread.php?t=1583427
After following those instructions, I then followed the instructions for AOKP Jelly Bean however my sdcard couldn't be mounted and the phone was in a boot loop if I didn't boot into fastboot by holding down the volume - and power buttons.
I attempted these instructions below however I couldn't get a stock recovery flashed.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Click to expand...
Click to collapse
Still caught in the reboot loop, I relocked and tried to run an RUU file found here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html
I was able to successfully re-lock the phone however every time I try to run the RUU file it comes back with an error about 3-5 minutes into the process.
At this point, my phone boots into fastboot. At the top I have "Tampered, Relocked, Security Warning." My HBOOT is 1.14.0004 and my Radios is 1.08ts.50.02.16
I would appreciate any help if there is a solution. Thank you for your time!
Update: Not sure if this is helpful or not, but whenever I try to do something with The All in one toolkit the cmd window says device not found. Also, when I try to boot into recovery from fastboot, I get a green downward and circular arrows before getting the red triangle and exclamation point.
Update: Running the RUU mentioned above fails at the Signature stage and the cmd prompt when trying to write recovery returns "signature verify fail"
Are you s4 or s3? what kind of computer you got? The drivers need to be installed. then read up how to use android SDK. Then retry to flash the stock recovery using the same steps in your quote.
Sent from my HTC One S using xda app-developers app
whozilla said:
Are you s4 or s3? what kind of computer you got? The drivers need to be installed. then read up how to use android SDK. Then retry to flash the stock recovery using the same steps in your quote.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I am pretty sure I am S4 (tmobile USA). I am on a windows 7 home build, and the drivers should be installed (at least, I could use HTC sync before all of this). I'll definitely try again tonight. If anyone has any other suggestions they would be much appreciated!
Make sure HTC sync is NOT active on your pc. Try searching for the original version of one s all in one toolkit. It has the stock recovery. I'm pretty sure this unbrick method works for all hboot versions but don't take my word for it. Focus on your goal. Get stock recovery flashed. You can also try unlocking your boot loader again and using the all in one to reflash cwm. In some cases like mine. The unofficial cwm touch is the only successful flash I got. Ps. Try having your phone in fastboot. Plug in USB and see if it says "fastboot USB" then type your android SDK directory for your fastboot folder. For example open cmd
cd\
cd androidsdk\tools
androidsdk\tools fastboot devices.
Fastboot devices command will tell you if your drivers are working.
You can also type in adb devices instead of fastboot devices.
Hope this helps. But you probably already know this
Sent from my HTC One S using xda app-developers app
whozilla said:
Make sure HTC sync is NOT active on your pc. Try searching for the original version of one s all in one toolkit. It has the stock recovery. I'm pretty sure this unbrick method works for all hboot versions but don't take my word for it. Focus on your goal. Get stock recovery flashed. You can also try unlocking your boot loader again and using the all in one to reflash cwm. In some cases like mine. The unofficial cwm touch is the only successful flash I got. Ps. Try having your phone in fastboot. Plug in USB and see if it says "fastboot USB" then type your android SDK directory for your fastboot folder. For example open cmd
cd\
cd androidsdk\tools
androidsdk\tools fastboot devices.
Fastboot devices command will tell you if your drivers are working.
You can also type in adb devices instead of fastboot devices.
Hope this helps. But you probably already know this
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help!
Here are my results:
HTC Sync is not running. Fastboot devices returns a device ID so that seems good. When trying to flash a stock recovery (that I got on this forum somewhere, but can't remember where) it sends it ok but I still get "remote: signature verify fail"
I unlocked the device and flashed TWRP 2.2.2.0 with the all in one tool kit. This put me back into the boot loop mentioned above. Once I manually got back into the bootloader and selected recovery, I was able to get into the TWRP recovery. At this point, I am kind of worried about doing anything. I would like to be able to push AOKP Unofficial JB if at all possible. Any further guidance would be appreciated!
Please, please don't use the toolkit. It makes people find problems later on and not know a thing about what to do.
Sent from my locked, tampered ville
---------- Post added at 08:24 AM ---------- Previous post was at 08:23 AM ----------
Oh well, flash AOKP through TWRP and then reboot into bootloader and flash the boot.IMG.
Sent from my locked, tampered ville
usaff22 said:
Please, please don't use the toolkit. It makes people find problems later on and not know a thing about what to do.
Sent from my locked, tampered ville
---------- Post added at 08:24 AM ---------- Previous post was at 08:23 AM ----------
Oh well, flash AOKP through TWRP and then reboot into bootloader and flash the boot.IMG.
Sent from my locked, tampered ville
Click to expand...
Click to collapse
It is clear to me that I didn't do enough research before getting into this. I thought my experience with putting custom roms on my galaxy S (a phone I really disliked) would give me the appropriate background. Clearly I was wrong! I'm a little unsure how to flash AOKP through TWRP when AOKP is not on my SD card. In fact, when I look at the SD card in TWRP, the only file on it is "TWRP."
I think I need to flash TWRP 2.3.0 (rather than the 2.2.2.0 I have), because it supports ADB Sideload (talked about here on their site which I can't yet link to). Can I do that through the Android SDK like I have been doing? I don't need to do anything to the TWRP 2.2.2.0 before trying to flash 2.3.0 do I? It seems if I do that, I could send AOKP to my phone through adb when it is in recovery.
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Thanks again!
You have to fastboot push the AOKP zip through the bootloader I think.
Sent from my locked, tampered ville
Veritas327 said:
It is clear to fme that I didn't do enough research before getting into this. I thought my experience with putting custom roms on my galaxy S (a phone I really disliked) would give me the appropriate background. Clearly I was wrong! I'm a little unsure how to flash AOKP through TWRP when AOKP is not on my SD card. In fact, when I look at the SD card in TWRP, the only file on it is "TWRP."
I think I need to flash TWRP 2.3.0 (rather than the 2.2.2.0 I have), because it supports ADB Sideload (talked about here on their site which I can't yet link to). Can I do that through the Android SDK like I have been doing? I don't need to do anything to the TWRP 2.2.2.0 before trying to flash 2.3.0 do I? It seems if I do that, I could send AOKP to my phone through adb when it is in recovery.
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Thanks again!
Click to expand...
Click to collapse
Just like the post above mine says, you have to adb push the file onto the sd card. I'm not to familiar with TWRP (using it actually got me into a bit of a dilemma) so I only know the process for CWM. If TWRP is anything like CWM then you have to be in recovery to adb push and have sdcard and system set to "unmont". It's pretty easy and there's a couple threads explaining how to do it. The command basically is :: adb push romname.zip /sdcard/romname.zip:: Note the space before "/sdcard" I'dpn't know if this ill help you or if you've solved your problem already but this is just my 2 cents, good luck!
Sorry for my late reply; I was rushed to the ER last night in excruciating pain. Looks like I'll be dealing with a kidney stone over the next few days.
So far, I have tried to push AOKP through fastboot. ADB says "no devices found" and when I type adb devices, I get "List of devices attached" and nothing under it. However, when I type fastboot devices, I do get a device ID. As of now, I am downloading the TWRP 2.3 recovery and will try to sideload with adb with that.
Update:
I was able to successfully install TWRP 2.3 and adb sideload the AOKP zip file. The phone then went back into a reboot loop, and I was able to get into recovery to install the .zip. The phone then rebooted, showed the HTC with red text screen very briefly, went to black, showed the HTC with red text screen again, went black, and now the aokp boot animation is repeating over and over. It has been doing so for about 5-7 minutes. I haven't yet installed gapps as mentioned in the AOKP post (I'm honestly not even sure what that is). Where should I go from here?
As a side note, the phone is plugged into power though the LED is not lighting up. It was at 98% when I flashed the .zip, but I obviously don't want it to die on me. Should I turn the phone off or is it still charging?
Veritas327 said:
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Click to expand...
Click to collapse
The newer hboot versions (1.13 and up) don't let you flash boot images in recovery, even if it reports success.
So there is technically no difference, except fastboot always works and recovery depends on hboot version.
Did you fastboot flash the boot image that comes with your rom?
-Jobo
Edit to add: So it seems that following the recipe in your post #1 did in fact make your sdcard mountable again, or did you do something else as well for that?
Fixed!
I ended up flashing the boot.img with fastboot and then going into recovery, factory resetting and then re-installing the rom (and gapps which I now know stands for google apps). I'll be playing around with the ROM but at least I have a working phone again!
I think, in the end, it came down to my sd card not being mounted and my lack of knowledge about how to fix it.
Related
Something went wrong which I am not gonna explain too much.
Now My phone doesn't have an OS.
I have Unlocked Bootloader,
I have CWM installed. However, the USB storage Mount isn't working. "No UMS error"
I can still use CWM, but I don't have any rom in the SDCARD.
I can boot into boot loader, I can see fastboot USB.
I want to install a rom, any rom for now. but I don't have access to the SDcard. I couldn't mount it.
Is there a way to write a file or put a rom on the SDCard?
of course the SDCARD is build-in so yea....
Please help~!!!
i could be wrong, but if you can get to fastboot, cant you flash via RUU? i mean its obviously not a custom rom, but a hell of a lot better than a brick.
most RUU is exe file...
I can flash a stock rom. but I need a .zip rom.
I tried using the one of the custom rom. but it says something about a .txt file missing.
Right, RUUs are exe files intended to be flashed via windows. I thought that you could plug your phone in when in fastboot mode, or maybe its after you select bootloader, and then run the RUU and it would flash the phone. Is that not the case? Those are just my thoughts so i could be wrong. This is my first real HTC experience so i may be way off base.
boot into recovey
flash use.adb
adb push rom.zip /sdcard/rom.zip
Sent from my Galaxy Nexus using XDA
niceppl said:
boot into recovey
flash use.adb
adb push rom.zip /sdcard/rom.zip
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
When u say boot into recovery do you mean CWM?
sorry i am so new this
I have try using ADB to push it.
But seems like without an OS already install... and WHEN I AM IN CWM, ADB doesn't recognize the phone.
The only thing that seem to recognize the phone is FAstboot,
jzhang0818 said:
I have try using ADB to push it.
But seems like without an OS already install... and WHEN I AM IN CWM, ADB doesn't recognize the phone.
The only thing that seem to recognize the phone is FAstboot,
Click to expand...
Click to collapse
flash this cwm
http://forum.xda-developers.com/showthread.php?t=1677304
if you are on windows, make sure you have the adb driver installed for the phone...check the device manager...make sure it's not a question mark
I have flashed the new CWM you gave me.
ADB works now.
but the weird thing is. Afert i did
adb push rom.zip /sdcard/rom.zip
I reboot to recovery
and try using install zip from sdcard. There was no file in it.
I am not sure what went wrong.
Please HELP.
I am using a MAC...
jzhang0818 said:
I have flashed the new CWM you gave me.
ADB works now.
but the weird thing is. Afert i did
adb push rom.zip /sdcard/rom.zip
I reboot to recovery
and try using install zip from sdcard. There was no file in it.
I am not sure what went wrong.
Please HELP.
I am using a MAC...
Click to expand...
Click to collapse
...good mac
try this..
adb push rom.zip /sdcard/Download/rom.zip
or
adb push rom.zip /sdcard/download/rom.zip
IT all works now...
Thank you very much.
I learn so much from this error.
Thank you very very much
jzhang0818 said:
IT all works now...
Thank you very much.
I learn so much from this error.
Thank you very very much
Click to expand...
Click to collapse
nice..lol...
A very similar problem
Hi all,
I've gotten myself into a very similar problem, but the solution posted here hasn't fixed my issue.
I have an HTC One X 2.20 on AT&T. I used the X-Factor exploit to root my phone successfully. I have TWRP 2.3.1 recovery. I have a Mac.
While in TWRP recovery, I pressed "Factory Reset", "Wiped System", and wiped "External Storage." My phone now doesn't have an OS.
I tried the listed solution "adb push rom.zip /sdcard/Download/rom.zip" and the newly flashed ROM would be on my SDcard, but as soon as I rebooted, it would disappear. ALSO, when I tried to "Install" the ROM before rebooting, I get "Failed- unable to mount /sdcard".
Any advice on how to proceed?
Thanks so much!
ayhindot said:
While in TWRP recovery, I pressed "Factory Reset", "Wiped System", and wiped "External Storage." My phone now doesn't have an OS.
Click to expand...
Click to collapse
Well, wiping /system = wiping the OS, so that is logical.
Doing factory reset in recovery means you need to reformat your SD card before doing anything else.
ayhindot said:
Hi all,
I've gotten myself into a very similar problem, but the solution posted here hasn't fixed my issue.
I have an HTC One X 2.20 on AT&T. I used the X-Factor exploit to root my phone successfully. I have TWRP 2.3.1 recovery. I have a Mac.
While in TWRP recovery, I pressed "Factory Reset", "Wiped System", and wiped "External Storage." My phone now doesn't have an OS.
I tried the listed solution "adb push rom.zip /sdcard/Download/rom.zip" and the newly flashed ROM would be on my SDcard, but as soon as I rebooted, it would disappear. ALSO, when I tried to "Install" the ROM before rebooting, I get "Failed- unable to mount /sdcard".
Any advice on how to proceed?
Thanks so much!
Click to expand...
Click to collapse
Can you get into TWRP? If so, just mount the USB via TWRP and put the ROM on your SD card and install it.
pside15 said:
Can you get into TWRP? If so, just mount the USB via TWRP and put the ROM on your SD card and install it.
Click to expand...
Click to collapse
I'm having the same problem with no OS being installed and I am unable to get to either the bootloader or recovery. When rebooting I can't get past the HTC quietly brilliant splash screen. I've been using the tool here: http://forum.xda-developers.com/showthread.php?t=1952426 but it can't reach the phone. What are my options now?
ltjska04 said:
I'm having the same problem with no OS being installed and I am unable to get to either the bootloader or recovery. When rebooting I can't get past the HTC quietly brilliant splash screen. I've been using the tool here: http://forum.xda-developers.com/showthread.php?t=1952426 but it can't reach the phone. What are my options now?
Click to expand...
Click to collapse
Have you successfully unlocked your bootloader using that tool?
---------- Post added at 04:14 PM ---------- Previous post was at 04:08 PM ----------
ayhindot said:
Hi all,
I've gotten myself into a very similar problem, but the solution posted here hasn't fixed my issue.
I have an HTC One X 2.20 on AT&T. I used the X-Factor exploit to root my phone successfully. I have TWRP 2.3.1 recovery. I have a Mac.
While in TWRP recovery, I pressed "Factory Reset", "Wiped System", and wiped "External Storage." My phone now doesn't have an OS.
I tried the listed solution "adb push rom.zip /sdcard/Download/rom.zip" and the newly flashed ROM would be on my SDcard, but as soon as I rebooted, it would disappear. ALSO, when I tried to "Install" the ROM before rebooting, I get "Failed- unable to mount /sdcard".
Any advice on how to proceed?
Thanks so much!
Click to expand...
Click to collapse
I think you need to uncheck "Unmount sdcard" under "Mount" in TWRP recovery.
Tried everything... still not working
niceppl said:
nice..lol...
Click to expand...
Click to collapse
Hi, Brand new Noob here, but hoping someone can help…I’ve had a good scour around and can’t find the answer. We have a Htc one x from orange uk (cid orang001) stuck at “quietly brilliant” screen following an attempt to load ViperX 2.6.0. After downloading, the MAC unzipped the ROM so this was just rezipped back up and transferred over to the SD card, without any special conditions. ( I’ve since read somewhere that this might cause issues)
USB debugger was enabled but its not possible to enable it now.
Fastboot works ok, and we’ve flashed the boot ok, but ADP isn’t working, so it isn’t possible to push the correct ROM.ZIP to the SDcard. CWM is installed.
We’ve seen the post for an updated CWM with ADP enabled on this here but that states its only for at&t models. If we could get ADP working we’d be able to push the correct ROM over, so this would seem the easiest way if possible.
I wanted to avoid doing a RUU in case the phone would end up bricked, but I can’t get the correct version anyway.
Command ./fastboot getvar version-main returns
version-main: 3.16.61.6 and the noob guide at
http://forum.xda-developers.com/showthread.php?t=1859714 says we can’t use a lower version….the nearest RUU I can find is 1.29.061.11 (released on 31/01/2013).
Any ideas on how best to recover this phone? The issue might not be anything to do with the zipping of the ROM, but then I have no idea why its not working…I’m hoping it’s a simple procedure, but I fear it may not be! Please Help!
LiamKenny said:
Hi, Brand new Noob here, but hoping someone can help…I’ve had a good scour around and can’t find the answer. We have a Htc one x from orange uk (cid orang001) stuck at “quietly brilliant” screen following an attempt to load ViperX 2.6.0. After downloading, the MAC unzipped the ROM so this was just rezipped back up and transferred over to the SD card, without any special conditions. ( I’ve since read somewhere that this might cause issues)
USB debugger was enabled but its not possible to enable it now.
Fastboot works ok, and we’ve flashed the boot ok, but ADP isn’t working, so it isn’t possible to push the correct ROM.ZIP to the SDcard. CWM is installed.
We’ve seen the post for an updated CWM with ADP enabled on this here but that states its only for at&t models. If we could get ADP working we’d be able to push the correct ROM over, so this would seem the easiest way if possible.
I wanted to avoid doing a RUU in case the phone would end up bricked, but I can’t get the correct version anyway.
Command ./fastboot getvar version-main returns
version-main: 3.16.61.6 and the noob guide at
http://forum.xda-developers.com/showthread.php?t=1859714 says we can’t use a lower version….the nearest RUU I can find is 1.29.061.11 (released on 31/01/2013).
Any ideas on how best to recover this phone? The issue might not be anything to do with the zipping of the ROM, but then I have no idea why its not working…I’m hoping it’s a simple procedure, but I fear it may not be! Please Help!
Click to expand...
Click to collapse
Wrong forum. This is for the S4 One XL. You have a Tegra 3 One X. Anything you flash from here may brick your phone.
iElvis said:
Wrong forum. This is for the S4 One XL. You have a Tegra 3 One X. Anything you flash from here may brick your phone.
Click to expand...
Click to collapse
oops, sorry :/
Hi Everyone,
So i followed all the steps to temp root 2.20 including successfully installing TWRP (Team Win Recovery Project). I then downloaded the CM10 rom and extracted the boot.img as per posts and rebooted into the bootloader and flashed the boot.img from CM10 via Fastboot. However after doing then rebooting to Recovery mode in order to flash the ROM, i get stuck in the red text where it gives you a warning about it being in development mode or something.
I am able to successfully boot into the bootloader via Power+down volume. Additionally I am able to boot into the TWRP recovery just fine, however I am lost and have no clue how to restore my phone to either the CM10 ROM or most importantly at least to stock working condition.
When i got to mount the SDCARD via twrp normally i would get a pop up on my screen and allow me to access my SD card, now i get a pop up just telling me that i need to format my SD card first. I'm afraid some how my SD card got wiped or something.
Can someone please walk me through the steps on how to restore my phone. Please if possible i would appreciate using LAME terms as i do not have any experience as you can tell i screwed up :/ Can you please listed step by step instructions including commands for Fastboot/adb etc etc if needed. Thank you very much for your help and support.
I've typed and retyped a response to help. I'm so tired and my brain is mush. (More so than normal) if you can't find any resolution by morning? Pm me and I'll try and help. Something about pluggin the USB in The back of your pc something something....... snore
Sent from my One X using xda premium
subarudroid said:
I've typed and retyped a response to help. I'm so tired and my brain is mush. (More so than normal) if you can't find any resolution by morning? Pm me and I'll try and help. Something about pluggin the USB in The back of your pc something something....... snore
Sent from my One X using xda premium
Click to expand...
Click to collapse
I know you tried to help, but it appears now I have bricked the phone. Hopefully i can fix it as i still have access to Bootloader and TWRP recovery. I'll PM you in the morning, thank you.
dont factory reset in bootloader. only factory reset in twrp. sometimes evita has a hard time getting into recovery from bootloader. just keep trying to get into recovery from bootloader. also even if your phone doesn't boot all the way adb sometimes still works. so try "adb reboot recovery" while its trying to boot.
if you did corrupt your sdcard try this method to get it fixed without having to run ruu.
[How to] Fix corrupt/unmountable internal storage on the HTC One X/XL
when you get your sdcard fixed remember to wipe everything and then copy cm10 and gapps to your sdcard and flash. since boot.img is already flashed you shouldn't need to do it again.
you did flash boot.img as "fastboot flash boot boot.img"? i made the mistake of flashing boot.img to recovery instead of boot. i was freaking out. just to make sure flash recovery again "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img"
DvineLord said:
dont factory reset in bootloader. only factory reset in twrp. sometimes evita has a hard time getting into recovery from bootloader. just keep trying to get into recovery from bootloader. also even if your phone doesn't boot all the way adb sometimes still works. so try "adb reboot recovery" while its trying to boot.
if you did corrupt your sdcard try this method to get it fixed without having to run ruu.
[How to] Fix corrupt/unmountable internal storage on the HTC One X/XL
when you get your sdcard fixed remember to wipe everything and then copy cm10 and gapps to your sdcard and flash. since boot.img is already flashed you shouldn't need to do it again.
you did flash boot.img as "fastboot flash boot boot.img"? i made the mistake of flashing boot.img to recovery instead of boot. i was freaking out. just to make sure flash recovery again "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img"
Click to expand...
Click to collapse
Yes i did fastboot flash boot boot.img from within the Bootlader. FYI that boot.img was from inside the CM10 zip file. I belive my SD card is corrupt i will check out that link. FYI I am able to get into Recovery mode form the Boatloader if i chooser recovery. However since the SD card seems messed up i can't access it currently. Also I tried to use the method to install the CM10.zip file using TWRP recovery. That recovery has a GUI and you can click on the INSTALL button and choose the zip file you want to install, however it errors out.
What is the proper way to flash a rom when i am in the TWRP recovery? Can you provide me with the commands/steps? Thanks for all your support guys.
movadoevo8 said:
Yes i did fastboot flash boot boot.img from within the Bootlader. FYI that boot.img was from inside the CM10 zip file. I belive my SD card is corrupt i will check out that link. FYI I am able to get into Recovery mode form the Boatloader if i chooser recovery. However since the SD card seems messed up i can't access it currently. Also I tried to use the method to install the CM10.zip file using TWRP recovery. That recovery has a GUI and you can click on the INSTALL button and choose the zip file you want to install, however it errors out.
What is the proper way to flash a rom when i am in the TWRP recovery? Can you provide me with the commands/steps? Thanks for all your support guys.
Click to expand...
Click to collapse
install/install from zip/browse to your zip/slide to flash (they really should patent that)
now most of us, to do a clean flash, we'd go into the "wipe" menu in TWRP before flashing , factory reset, wipe cache, wipe dalvik cache, wipe system. then we flash our rom.
hope that cleared it up!
Sent from my One X using xda premium
You won't be able to flash anything until you fixed your sdcard using the method in that link.
Ptesmoke where have you been? DvineLord is the only one been helping here. The Q&A thread is a mess. where is edditsync chongo, rohan and the other superhero's. I feel like Hawkeye trying to shoot sh#@ down with a bow and arrow. Waiting for ironman, hulk, Thor and the other avengers to get real sh#@ done. I'm tired going to sleep now.
Sent from my One X using xda premium
ptesmoke said:
install/install from zip/browse to your zip/slide to flash (they really should patent that)
now most of us, to do a clean flash, we'd go into the "wipe" menu in TWRP before flashing , factory reset, wipe cache, wipe dalvik cache, wipe system. then we flash our rom.
hope that cleared it up!
Sent from my One X using xda premium
Click to expand...
Click to collapse
I tried to fixed corrupted SD card as per video. however after flashing the recovery.img via fastboot when it wants me to do a factory reset instead of doing the factory reset it just goes back to the HTC brilliant screen with the red warning text and sits there. If i go to twpr recovery and click on install i can't access me zip currently due to sd card issues.
Is there a way to format via PC since it lets me as long as I am in twpr and just put stock files/folders onto the SD card? Or is it possible to install the 2.20 ruu again? I re-downloaded it form HTC's site while I am in twrp however I cannot install it won't detect my phone. Thanks for your help.
"fastboot oem lock" then run ruu. ruu gets run in fastboot.
after the ruu, reunlock bootloader and flash twrp, copy cm10 and gapps to your sdcard, flash boot.img in fastboot, wipe everything except for external storage in twrp, flash cm10 and gapps in twrp, then reboot.
If you can get into twrp and go to mount, mount usb storage and connect your phone windows should prompt you to format the SD card.
Once that's done you can drag and drop the rom you want to flash then boot into fastboot and flash the boot.img.
If you want to run the ruu you need to relock the bootloader first.
To do that you must go into fastboot usb and then type fastboot oem lock.
Sent from my HTC One XL using xda premium
DvineLord said:
"fastboot oem lock" then run ruu. ruu gets run in fastboot.
after the ruu, reunlock bootloader and flash twrp, copy cm10 and gapps to your sdcard, flash boot.img in fastboot, wipe everything except for external storage in twrp, flash cm10 and gapps in twrp, then reboot.
Click to expand...
Click to collapse
I'm sorry i'm not too tech savy. Can you clarify how to Fastboot OEM lock. Assuming i just need to be in fastboot mode and run a command in command prompt?
Also once that is done how can i run RUU via fastboot? Right now i have HTC RUU for 2.20 from august that i downloaded from their site and not sure how i can have it detect my phone. If you could clarify and explain those steps in Lame terms i would greatly appreciate it, thanks in advance.
movadoevo8 said:
I'm sorry i'm not too tech savy. Can you clarify how to Fastboot OEM lock. Assuming i just need to be in fastboot mode and run a command in command prompt?
Also once that is done how can i run RUU via fastboot? Right now i have HTC RUU for 2.20 from august that i downloaded from their site and not sure how i can have it detect my phone. If you could clarify and explain those steps in Lame terms i would greatly appreciate it, thanks in advance.
Click to expand...
Click to collapse
That's the command you do and the ruu is an exe file so get into fastnoot on your phone from bl and run the ruu after you've locked the bootloader
Thank you both will try that now.
Hey guys thanks for all your help and your support it worked. I had the wrong CM10 file instead of Evita i had the other one :/ That was the issue all along ugh... but all resolved could of not have done it without your support. Thanks!! I can now finally go to bed.. been at it since 10pm, now 3:11am
Maybe you can help me . I'm having the same problem. The problem is, everytime I try to use any fastboot commands, it'll say "waiting for device". I'm stressing out.
marcur12 said:
Maybe you can help me . I'm having the same problem. The problem is, everytime I try to use any fastboot commands, it'll say "waiting for device". I'm stressing out.
Click to expand...
Click to collapse
Make sure you have the right drivers installed, download the latest htc sync from htc's website.
Install HTC sync connect phone and let the drivers install, then make sure you close htc sync from the system tray and try again.
Like DvineLord said below make sure you're in the bootloader then select Fastboot once selected it should say in red writing Fastboot USB.
fastboot only works in bootloader btw
Hit the thanks button for the people helping you fix your boo boos.
If you can type it, click it for them, least you can do in return.
WR
Sent from my HTC One X
Sent from my HTC One XL using Tapatalk 2
Phone: HTC ONE XL
Carrier: Rogers LTE
Hey guys,
I have a problem that hopefully someone can help me with. Any help is much appreciated. I got my phone a year ago and I rooted it and unlocked it immediately. I removed the stock ROM and put Clean Rom 4.5 on it. Today, I realized my phone could be manually updated to jelly bean, so i wanted to install CM 10.1.
During installation, I just put the boot.img of the Rom in my folder that contained adb, fastboot, etc and I was at the step of loading recovery to install the rom, my phone could not get into the recovery and just kept restarting over and over again. I can still get into the bootloader. I read online to try and type "fastboot erase cache", but that isnt working because my computer can no longer recognize the phone. When I go into bootloader and into fastboot, my computer makes the sound like the USB is recognized but when I type the command "adb devices", no device is showing up.
I'm guessing that my first step to hopefully solving this issue is to find a way to have my device show up when I type "adb devices" but my attempts so far have been futile.
Key Points:
- Can't get past HTC boot screen (keeps looping)
- can still access bootloader
- no device seen when command "adb devices" has been typed.
Any help is greatly appreciated.
EDIT: I should add that when this occured (the looping), I tried to flash "recovery clockwork touch 5.8.2.7" and I was accidentally following a guide meant for the European HTC One X. The recovery image that I should have used (and did use to flash Clean Rom) is "TWRP 2.2.0 evita".
Cheruksr said:
Phone: HTC ONE XL
Carrier: Rogers LTE
Hey guys,
I have a problem that hopefully someone can help me with. Any help is much appreciated. I got my phone a year ago and I rooted it and unlocked it immediately. I removed the stock ROM and put Clean Rom 4.5 on it. Today, I realized my phone could be manually updated to jelly bean, so i wanted to install CM 10.1.
During installation, I just put the boot.img of the Rom in my folder that contained adb, fastboot, etc and I was at the step of loading recovery to install the rom, my phone could not get into the recovery and just kept restarting over and over again. I can still get into the bootloader. I read online to try and type "fastboot erase cache", but that isnt working because my computer can no longer recognize the phone. When I go into bootloader and into fastboot, my computer makes the sound like the USB is recognized but when I type the command "adb devices", no device is showing up.
I'm guessing that my first step to hopefully solving this issue is to find a way to have my device show up when I type "adb devices" but my attempts so far have been futile.
Key Points:
- Can't get past HTC boot screen (keeps looping)
- can still access bootloader
- no device seen when command "adb devices" has been typed.
Any help is greatly appreciated.
EDIT: I should add that when this occured (the looping), I tried to flash "recovery clockwork touch 5.8.2.7" and I was accidentally following a guide meant for the European HTC One X. The recovery image that I should have used (and did use to flash Clean Rom) is "TWRP 2.2.0 evita".
Click to expand...
Click to collapse
ADB is a program that gives you control of your phone "terminal" or "command line" remotely. It requires you to be booted into your ROM with USB debugging turned on so ofcourse it won't show any devices while in bootloader.
There are at least 20 threads that ask this same question. How do I know? I've answered at least that amount just myself. Please use the search function in the future prior to asking. I'm so tired of wasting time answering the same questions over and over.
Download TWRP 2.3.3.1 <- latest version that works properly without any issues with any ROMs
Check MD5 <- If you don't have an md5 checker google and download one. This will verify the download is good.
Put your phone in bootloader/fastboot
fastboot flash recovery recoveryfilename.img
fastboot erase cache
fastboot reboot-bootloader
Select recovery from bootloader menu
Flash your rom from recovery.
exad said:
ADB is a program that gives you control of your phone "terminal" or "command line" remotely. It requires you to be booted into your ROM with USB debugging turned on so ofcourse it won't show any devices while in bootloader.
There are at least 20 threads that ask this same question. How do I know? I've answered at least that amount just myself. Please use the search function in the future prior to asking. I'm so tired of wasting time answering the same questions over and over.
Download TWRP 2.3.3.1 <- latest version that works properly without any issues with any ROMs
Check MD5 <- If you don't have an md5 checker google and download one. This will verify the download is good.
Put your phone in bootloader/fastboot
fastboot flash recovery recoveryfilename.img
fastboot erase cache
fastboot reboot-bootloader
Select recovery from bootloader menu
Flash your rom from recovery.
Click to expand...
Click to collapse
Hey, thanks for the reply. Yeah, I read up on ADB after i posted the thread. I learnt that you can't use ADB commands in the bootloader. I've been trying to flash the recovery but i keep getting "waiting for device". (regardless of what command i try). I don't think its the USB drivers because I downloaded the latest HTC drivers (in fact there is a thread about the latest USB drivers for HTC, which is where I downloaded from) and there isn't any exclamation points in device manager. Not really sure what the issue is, any additional help would be appreciated.
Thanks.
EDIT:
Originally Posted by DvineLord
try using this application if you think your device drivers are dirty but installed correctly for usb devices
USBDeview just uninstall whatever devices you want reinitialized especially since they can change even with rom changes so it is good to clear some old ones out by sorting them based on Last Plug/Unplug Date.
Found that in another thread, going to try that. Hopefully that will work.
Cheruksr said:
Hey, thanks for the reply. Yeah, I read up on ADB after i posted the thread. I learnt that you can't use ADB commands in the bootloader. I've been trying to flash the recovery but i keep getting "waiting for device". (regardless of what command i try). I don't think its the USB drivers because I downloaded the latest HTC drivers (in fact there is a thread about the latest USB drivers for HTC, which is where I downloaded from) and there isn't any exclamation points in device manager. Not really sure what the issue is, any additional help would be appreciated.
Thanks.
EDIT:
Originally Posted by DvineLord
try using this application if you think your device drivers are dirty but installed correctly for usb devices
USBDeview just uninstall whatever devices you want reinitialized especially since they can change even with rom changes so it is good to clear some old ones out by sorting them based on Last Plug/Unplug Date.
Found that in another thread, going to try that. Hopefully that will work.
Click to expand...
Click to collapse
I just install the latest HTC sync. It installs the latest driver.
Also, try to avoid using a USB hub if you are.
Make sure HTC Sync isn't running when you are using fastboot/adb
Worst case scenario, you could always create a VM or something to get it going.
exad said:
I just install the latest HTC sync. It installs the latest driver.
Also, try to avoid using a USB hub if you are.
Make sure HTC Sync isn't running when you are using fastboot/adb
Worst case scenario, you could always create a VM or something to get it going.
Click to expand...
Click to collapse
I can now run the fastboot commands, but in the twrp recovery I can't access my SD card. I'm currently following a guide to see if I can fix it, but yeah thats where I am at. Also, a window popped up in my windows 8 saying "You need to format the disk...". Should I do that or what, Im not exactly sure.
Thanks
Yes format it.
Sent from my HTC One X using xda app-developers app
Am I capable of running CM10.1 Nightlies?
exad said:
Yes format it.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Alright, following a video tutorial (http://forums.team-nocturnal.com/showthread.php/1050) and factory reset the phone. My SD card is wiped clean but I can mount it through the TWRP recovery. Since I don't have a ROM now, I'm debating what I should do: a) Go back to Clean ROM 4.5, b) Install CM 10.1 Nightlies or c) Install Clean ROM 6.5.
***TAMPERED***
***UNLOCKED***
S-ON
HBOOT 1.11.0000
Is there anything I should know before attempting to flash CM 10.1/Clean ROM 6.5 or should I return to Clean ROM 4.5.
Thanks for the helps. Really appreciate it.
Either should work fine. Cleanrom will have somewhat bettery battery life.
Sent from my HTC One X using xda app-developers app
exad said:
Either should work fine. Cleanrom will have somewhat bettery battery life.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
another good tip is that when you are in fastboot mode and write "adb devices" not will work because adb will just work when your phone is turned on inside the android, and fastboot not will work if you arent in mode fastboot
I'm posting this in a single thread to minimize clutter.
I recently ran Easy Ace Root tool as instructed on my inspire. The bootloader unlocked, CWM flashed, but there was an error during superuser flash.
After a reflash of superuser things looked okay, but superuser began not responding. I re-flashed superuser twice in attempt to fix it using the Easy Ace Root Tool.
EDIT: I have discovered that superuser will only function with "USB debug mode" enabled. I've tried it on and off several times, and each time it malfunctions but function returns without a problem.
The backup I have been restoring seems to work because it was created with the debug mode enabled. Took a while to see it.
Second, CWM started to exhibit the "power off, charge" recovery bug where CWM opens.
Last, I attempted to install/flash 4ext Recovery Touch twice to address the CWM bug. Both times it hung at "flashing recovery" (approx 20 mins. both times). Eventually, it indicated that 4ext was installed. However, booting into recovery shows that I still have CWM. I used two different versions (RC8 & RC 7) in the attempt.
I'm now using the restored and working ROM. Solutions to the superuser debug issue I haven't seen posted
The failure to flash 4ext is troubling.
Questions
1. Could these issues be related? Or, what should I be looking for?
2. The recovery issue seems to be the most important. What might be the cause of 4ext to fail in this manner?
3. Can the Easy Ace Root Tool be rerun on the unlocked bootloader, and would that fix anything?
4. Is there reason to worry about flashing with CWM?
I see a number of possible solutions, the main one is to flash a new ROM, which I have already downloaded a couple, but doesn't adress the recovery problems.
The issue with CWM and 4ext leave me less than confident in using it to flash with, although CWM seems okay. The other item is that some ROMs indicate that S-off in required, but many of the threads are a couple years old.
5. Is it correct that S-off is not required to flash ROMs (I read it somewhere)?
I found an answer: NO, YOU DON'T NEED S-OFF TO FLASH ROMS....
Solving the issues are good lessons
Stock AT&T ROM
Android 2.3.5, Sense 3.0
Bootloader screen indicates-
UNLOCKED
S_ON
I know that's a lot for one thread but I'm just looking for a direction and I'll do the search.
If anyone has suggestions, directions, or ideas fire away.
Thanks
I think the fact that you are still S-ON is causing problems with the recovery flashing, since S-ON basically means that the recovery partition is not-writeable.
Have you tried using fastboot to flash a new recovery? Plug your phone into a computer, get into the bootloader, select "fastboot" (if not already selected), wait for "FASTBOOT USB" to appear, and then run the following on the computer:
Code:
fastboot flash recovery <path to recovery.img>
However that S-ON still worries me. You might have to do things manually:
Code:
androidforums.com/desire-hd-all-things-root/702100-how-manually-achieve-s-off-simunlock-supercid-inspire-4g-dhd.html
(Sorry for the broken URL - I had to disguise it. Blargh, I hate being a n00b.)
Evil_ryan said:
I think the fact that you are still S-OFF is causing problems with the recovery flashing, since S-OFF basically means that the recovery partition is not-writeable.
Have you tried using fastboot to flash a new recovery? Plug your phone into a computer, get into the bootloader, select "fastboot" (if not already selected), wait for "FASTBOOT USB" to appear, and then run the following on the computer:
Code:
fastboot flash recovery <path to recovery.img>
However that S-OFF still worries me. You might have to do things manually:
Code:
androidforums.com/desire-hd-all-things-root/702100-how-manually-achieve-s-off-simunlock-supercid-inspire-4g-dhd.html
(Sorry for the broken URL - I had to disguise it. Blargh, I hate being a n00b.)
Click to expand...
Click to collapse
Thanks, I think you meant to say the fact that I am still S-ON? The S_ON part shouldn't be an issue from all that I've gathered. In fact, that's how I have CWM. The Easy Ace Root Tool does CWM, with an unlocked bootloader S_ON. Nothing I have come across states that S_OFF is required to flash 4ext recovery.
Other noobs might find this other thread useful as there is some info and links to recovery images. http://forum.xda-developers.com/showthread.php?p=22489317#post22489317
No I haven't tried the fastboot yet. That is an option, I've got it and adb setup on my computer already. I have looked at AAHK, but as it says its no longer supported, and I don't think I need of S_OFF. Taking it slow to sort out the problems so I don't do sumthin stooopid.
How are you flashing 4ext? From fastboot?
Right, S-ON, that's what I get for writing this at 12 AM.
Don't bother with AAHK, it's discontinued, and even if you still had a copy it couldn't download the necessary files.
bananagranola said:
How are you flashing 4ext? From fastboot?
Click to expand...
Click to collapse
bananagranola,
I used the 4Ext Recovery Updater for both attempts. As I said in the OP, both attempts hung at "flashing recovery" approx 20 mins, and eventually indicated that 4ext was installed. In Recovery Updater it listed/highlighted the version I thought I had installed, but CWM was still the recovery that booted.
Cremnomaniac said:
bananagranola,
I used the 4Ext Recovery Updater for both attempts. As I said in the OP, both attempts hung at "flashing recovery" approx 20 mins, and eventually indicated that 4ext was installed. In Recovery Updater it listed/highlighted the version I thought I had installed, but CWM was still the recovery that booted.
Click to expand...
Click to collapse
Try doing it from fastboot.
bananagranola said:
Try doing it from fastboot.
Click to expand...
Click to collapse
I thought that would be next.
Can you confirm for me that the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=1848846 are correct for the Inspire 4G?
It's the EVO 3D forum. And I have some other links to using fastboot I'll check before doing it.
Yes, those instructions will work. If you can't boot into fastboot through the GUI, you can also power on the phone while holding the volume down button, and that will get you into the bootloader.
Evil_ryan said:
Yes, those instructions will work. If you can't boot into fastboot through the GUI, you can also power on the phone while holding the volume down button, and that will get you into the bootloader.
Click to expand...
Click to collapse
Okay, great. This is the only recovery .img that I have found 4EXT-recovery-2.2.7_RC5.img - 3.33 MB
If I install the 4ext recovery Updater after flashing it should work okay?
And, Will I be able to update once I have flashed it (assuming it works) and have installed the recovery Updater?
Cremnomaniac said:
If I install the 4ext recovery Updater after flashing it should work okay?
Click to expand...
Click to collapse
Probably. But I don't think it really matters, since if you can flash a recovery using fastboot, you can do everything that 4ext updater otherwise would.
Cremnomaniac said:
And, Will I be able to update once I have flashed it (assuming it works) and have installed the recovery Updater?
Click to expand...
Click to collapse
See above.
If 4ext doesn't work, you can also try CWM and TWRP (TeamWin Recovery Project). I use the latter with my Inspire 4g.
I strongly advise you use the app to download the recovery, unzip, and then flash it from fastboot.
bananagranola said:
I strongly advise you use the app to download the recovery, unzip, and then flash it from fastboot.
Click to expand...
Click to collapse
I'll take "strongly" as more than a suggestion. Thanks, it had not occurred to me to get the recovery.img from the updater.
I had actually found several other images and was trying to figure out what was what. That saved me some time, but I did read a lot about 4ext.
I was considering trying the Recovery Updater one more time. Bad Idea?
Cremnomaniac said:
I'll take "strongly" as more than a suggestion. Thanks, it had not occurred to me to get the recovery.img from the updater.
I had actually found several other images and was trying to figure out what was what. That saved me some time, but I did read a lot about 4ext.
I was considering trying the Recovery Updater one more time. Bad Idea?
Click to expand...
Click to collapse
I have a hunch that if you are S-On, you can only write to the recovery partition from fastboot.
bananagranola said:
I have a hunch that if you are S-On, you can only write to the recovery partition from fastboot.
Click to expand...
Click to collapse
I am S-ON. Does that present an issue with fastboot of the recovery.img?
I'm just going to overwrite the current recovery. Nothing else needs to be done does it?
Cremnomaniac said:
I am S-ON. Does that present an issue with fastboot of the recovery.img?
I'm just going to overwrite the current recovery. Nothing else needs to be done does it?
Click to expand...
Click to collapse
No.
bananagranola said:
No.
Click to expand...
Click to collapse
Solved the 4EXT flashing issue. Looks like 4ext flashed okay with fastboot, and the 4EXT Recovery Control works. Rebooted into recovery a couple times just to be sure. That kills 2 birds the CWM bug and the recovery flash.
Thanks for the help and suggestions all.
Some notes from a noobs experience -
Setting up ADB and Fastboot is very easy.
If your cautious as I am run some basic commands in ADB and Fastboot that won't do damage [devices, reboot, reboot-bootloader, etc.]
If you get "error: cannot load 'recovery.img" make sure you navigate to folder that recovery.img is located. Then run "Fastboot flash recovery [Filename]." Even though I set system variables on my desktop to point to adb and fastboot, it won't find the recovery image if you start from the wrong directory in terminal (i.e., C:\)
If you're in ADB and you use the command "adb reboot-bootloader" it will boot the device straight to "Fastboot USB".
Don't forget that each time you flash a ROM from recovery, you still need to fastboot flash its boot.img separately.
bananagranola said:
Don't forget that each time you flash a ROM from recovery, you still need to fastboot flash its boot.img separately.
Click to expand...
Click to collapse
Thanks for the reminder. I just spent an hour looking at 4EXT "smartflash no available". I hav some links for doing fastboot flash of the boot.img. I think I'm good there.
One question from my OP remains. Superuser only works (i.e., grants root access) when I have USB debug mode selected. When it's off superuser says the app (e.g., Titanium BU) is granted permission but just hangs until I force close it and re-enable USB debug. i can't find anything on this problem.
Is it an issue to run my phone in USB debug mode all the time? Or, any clue to the problem?
I'd like to know how to update my TWRP from v 2.4.4.0 to a later version. This version doesn't seem to allow flashing of an img file on external sd card. I have tried without success on 2 computers to get windows to recognise this android, so I'm hoping there is another way. Eventually I'd like to install Katkiss,Gapps and SU on this android. At present it has no rom.
Secondly, I tried to install Cromi X and all goes well up until I reboot and it continually spools on the opening screen so I don't know what that is about but hoping with a later TWRP I may be able to set the partitioning better which may or may not be part of the cause.
Reboot recovery twrp.
Go to install.
Click on install image.
Search downloaded recovery.
Select recovery.
And install.
Done
sent from moto g2014 with cm13
---------- Post added at 03:12 AM ---------- Previous post was at 03:11 AM ----------
Ot use flashify app.
It requires root.
sent from moto g2014 with cm13
There is no 'install image' on v2.4.4.0 and that version of TWRP does not seem to recognise .img files on the external sd card. On a later version of TWRP your solution would work.
If you want to flash the recovery in recovery it has to be inside a flashable zip (except for the latest versions).
You can use the Kang TWRP 2.8.x from post 2 here: http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
You can flash Katkiss with it no problem, and it supports the dock SD which the official TWRP does not do.
Somewhere there's also a thread where some dude keeps posting TWRP 3.x in a flashable zip, but I can't think of where right now.
That CROMi-X does not boot can have a number of reasons:
You did not format data before flashing the rom
You are on an outdated bootloader
Something is physically wrong with your emmc.
Your problem to get the tablet recognized in Windows is almost certainly a driver problem an you should get that fixed. At minimum it sucks not to have fastboot access to the tablet. And it easily could be lethal. For the tablet - not for you
Could also be a problem with a cheap knock-off replacement USB cable. If you are not using the original Asus cable that's worth investigating. And if you are using the original it may become worn. Mine is starting to allow a connection only in certain positions... Age....
Make sure the device drivers are installed and try the Google Universal Naked drivers. Minimal ADB and fastboot is an excellent tool that shimp208 still keeps current after all this time, and if none of those work try the 15 second adb installer if you are on Win 7 or earlier (just google it).
Hello my old friend. Well I have finally managed to get an adb connection and am going over to old posts of previous help you gave me with this device. Although the device is now recognised I can't get any commands to work e.g. fastboot devices simply returns me to the c:/adb prompt and adb reboot bootloader just takes the flashing underline symbol to the next line and nothing happens. I have hope that I will be able to get this working OK now I have adb access. How do I know if I am on an outdated bootloader? thanks
plato2 said:
Hello my old friend. Well I have finally managed to get an adb connection and am going over to old posts of previous help you gave me with this device. Although the device is now recognised I can't get any commands to work e.g. fastboot devices simply returns me to the c:/adb prompt and adb reboot bootloader just takes the flashing underline symbol to the next line and nothing happens. I have hope that I will be able to get this working OK now I have adb access. How do I know if I am on an outdated bootloader? thanks
Click to expand...
Click to collapse
This is not the same device you helped me with earlier...it now purrs beautifully.... this is a new challenge.
plato2 said:
Hello my old friend. Well I have finally managed to get an adb connection and am going over to old posts of previous help you gave me with this device. Although the device is now recognised I can't get any commands to work e.g. fastboot devices simply returns me to the c:/adb prompt and adb reboot bootloader just takes the flashing underline symbol to the next line and nothing happens. I have hope that I will be able to get this working OK now I have adb access. How do I know if I am on an outdated bootloader? thanks
Click to expand...
Click to collapse
Thought you looked familiar..... :cyclops:
Time to re-read this I think http://forum.xda-developers.com/showthread.php?t=2688891
Boot into the bootloader and read the small script. The last bootloader for this tablet is 10.6.1.14.10.
Yes, that is the bootloader I have. Typing fastboot devices takes me back to the/adb prompt and then typing
fastboot -i 0x0B05 flash recovery <name-of-file>
I get a <waiting for device> but nothing happens.
plato2 said:
Yes, that is the bootloader I have. Typing fastboot devices takes me back to the/adb prompt and then typing
fastboot -i 0x0B05 flash recovery <name-of-file>
I get a <waiting for device> but nothing happens.
Click to expand...
Click to collapse
Yeah, so you have a driver problem. This is nothing you have to do now. Just download the flashable zip of Kang TWRP and flash it in your current recovery.
But when you have some time to kill open Device Manager and connect and disconnect the cable to the tablet. It should give you SOME change in device manager. If it doesn't, reboot both tablet and PC and try again.
Then try a different cable.
Still nothing? This could take longer. Driver problems suck in Windows....
So - you got yourself another TF700? Had just too much fun getting Katkiss to work on the last one, eh?
berndblb said:
Yeah, so you have a driver problem. This is nothing you have to do now. Just download the flashable zip of Kang TWRP and flash it in your current recovery.
But when you have some time to kill open Device Manager and connect and disconnect the cable to the tablet. It should give you SOME change in device manager. If it doesn't, reboot both tablet and PC and try again.
Then try a different cable.
Still nothing? This could take longer. Driver problems suck in Windows....
So - you got yourself another TF700? Had just too much fun getting Katkiss to work on the last one, eh?
Click to expand...
Click to collapse
Just download the flashable zip of Kand TWRP and flash it in your current recovery.
I don't know what you mean here.... how do I 'flash it in my current recovery' I have v 2.4.4.0 and it doesn't see img files on external sd.
plato2 said:
Just download the flashable zip of Kand TWRP and flash it in your current recovery.
I don't know what you mean here.... how do I 'flash it in my current recovery' I have v 2.4.4.0 and it doesn't see img files on external sd.
Click to expand...
Click to collapse
If you downloaded from the second link, the flashable zip, you will see a zip file, not an img file.
Just hit Install, select the zip and swipe the button. Reboot when the flash is finished
All good so far. Up to the wiping data bit before converting to f2fs but this guide is missing, not sure why. I recall it was only a short set of instructions: Once that is done follow this guide to convert internal data to f2fs: http://forum.xda-developers.com/tran...p-2-8-t3073471. Can you recall that part? thanks
Got it, found it or rather another post of yours here: tf700/help/how-to-update-twrp-withoput-adb-t3437702/post68163144#post68163144 so did that and successfully installed Katkis, Gapps pico and SU....another beautiful TF700T purring...many thanks yet again...