Related
Ive looked around the internet, and here, and cant really figure something out. Do I have to install CM10 from fastboot or can I just install the zip using TWRP?
I ask because I tried installing the stable version of CM10 using TWRP and when I reboot I just get the spinning Cyanogenmod logo for a long time. Nothing ever happens.
Am I doing something wrong?
Did you make a backup of your stock Rom? Log into that. Get flashimagegui and use on the cm10 zip then boot back into twrp and install the zip.
Or
Open the cm10 zip on your computer. Extract boot.img. put your phone in fastboot. Put the boot.img in your fastboot folder and type fastboot flash boot boot.img
Sent from my HTC One XL using xda app-developers app
area51avenger said:
Did you make a backup of your stock Rom? Log into that. Get flashimagegui and use on the cm10 zip then boot back into twrp and install the zip.
Or
Open the cm10 zip on your computer. Extract boot.img. put your phone in fastboot. Put the boot.img in your fastboot folder and type fastboot flash boot boot.img
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot. I will do that right now. Appreciate the help.
Is flashimagegui an android app? Thats the only reference to it I can find.
Yes it is. There is a donation version on play store. Or there's an xda free version if you search the forums
Sent from my HTC One XL using xda app-developers app
Well, looks like something might have gone wrong and I fear I might be SOL. I used flashimagegui then returned to TWRP to install CM10. I still got the spinning log. I went to restore my backup and I cant boot back into my back up. During bootup a HTC logo comes up with some red text (like its going to go into revocery) and then the screen goes blank. Nothing happens after that. If I turn off the phone and power on again, the same thing happens. I can turn it off then and go through the steps to get back into recovery. I have no idea what do to now. Any recommendations?
JohnnyDanger said:
Well, looks like something might have gone wrong and I fear I might be SOL. I used flashimagegui then returned to TWRP to install CM10. I still got the spinning log. I went to restore my backup and I cant boot back into my back up. During bootup a HTC logo comes up with some red text (like its going to go into revocery) and then the screen goes blank. Nothing happens after that. If I turn off the phone and power on again, the same thing happens. I can turn it off then and go through the steps to get back into recovery. I have no idea what do to now. Any recommendations?
Click to expand...
Click to collapse
what version of hboot is on your device? if it is one of the later ones (1.12+) then you'll need to flash the boot img seperately. If this is the case, (and it sounds like it , as the same thing happened to me and the symptoms where the same).
Extract it from the ROM that you are flashing (open the zip file and drag out the boot.img). Then while TWRP is running, connect the USB cable to your comp and fire up a terminal (you'll need ADB/fastboot set up and working - search google or XDA for how to do it in your operating system).
Once you have adb/fastboot working and TWRP running -> at a terminal (or command prompt on windows) use adb to push the rom onto the sdcard, and then reboot to bootloader and select fastboot.
run "fastboot flash boot boot.img" without the quotes. This should write the kernel image to the boot partition, and then you should be able to load TWRP to (wipe cache/dalvik and then) reflash cyanogen mod.
Good luck
If you can still boot into recovery, you're fine. Manually flash the CM10 boot.img with fastboot, do a full wipe in TWRP and then reinstall the CM10 zip + gapps. Should be good after that.
Thanks for the info, from both of you. Im going to try that right now.
Im trying to flash the boot.img file, but I keep getting an error. Any ideas?
Heres what I get
C:\adt-bundle-windows\sdk\platform-tools>fastboot flash boot boot.img
sending 'boot' (5248 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.016s
Click to expand...
Click to collapse
did you do a factory reset from the bootloader by any chance? this can corrupt the sdcard, and might cause this. only use the factory reset from recovery.
if you did, try this (http://forums.team-nocturnal.com/showthread.php/1050).
---------- Post added at 02:51 PM ---------- Previous post was at 02:28 PM ----------
Check that it says fastboot usb on your phone. You might not be in fastboot mode.
Otherwise, maybe try a different USB port on your computer, I've had issues trying to get it to detect through a usb hub, so plug it directly inot the computer to rule this out.
codeprimate said:
did you do a factory reset from the bootloader by any chance? this can corrupt the sdcard, and might cause this. only use the factory reset from recovery.
if you did, try this (http://forums.team-nocturnal.com/showthread.php/1050).
---------- Post added at 02:51 PM ---------- Previous post was at 02:28 PM ----------
Check that it says fastboot usb on your phone. You might not be in fastboot mode.
Otherwise, maybe try a different USB port on your computer, I've had issues trying to get it to detect through a usb hub, so plug it directly inot the computer to rule this out.
Click to expand...
Click to collapse
I didnt use the factory reset option from the bootloader. Being that I didnt, should I still try the directions on the link you gave?
When I go into fastboot is start off just saying "fastboot". If I press the volume up or down button is changes to "fastboot usb". I didnt even think about trying a different usb port, I will see if that makes a difference.
JohnnyDanger said:
I didnt use the factory reset option from the bootloader. Being that I didnt, should I still try the directions on the link you gave?
When I go into fastboot is start off just saying "fastboot". If I press the volume up or down button is changes to "fastboot usb". I didnt even think about trying a different usb port, I will see if that makes a difference.
Click to expand...
Click to collapse
can you get into TWRP? if you can, go to the mount menu and see if you can unmount and then remount the sdcard. If you can do this, then you have no need to do the team-nocturnal sdcard fix.
I was able to unmount and then remount the sdcard. Actually, when I went into Mount menu in TWRP to begin with it gave me the option to Mount, then unmount. Is that the same thing? Does that mean my sdcard is not mounted and should I mount it in TWRP?
I was finally able to flash the boot.img. I then went into TWRP to install CM10. It installed and now is back into the spinning logo. Im ready to give up on this. Any more suggestions?
Just a thought, should I be removing the boot.img from the CM10 zip Im trying to install?
No don't remove it. Did you wipe data/system before installing. And wipe cache/dalvik after? Also the first boot could take up to 5 minutes sometimes
Sent from my HTC One XL using xda app-developers app
area51avenger said:
No don't remove it. Did you wipe data/system before installing. And wipe cache/dalvik after? Also the first boot could take up to 5 minutes sometimes
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Ive been trying to install the latest stable build of CM10. I decided to try the most recent Nightly now. That seemed to work. The spinning just stopped and Im on the welcome screen. FINALLY! Thank you guys for all the help. Never had such a hard time with installing a custom rom before.
JohnnyDanger said:
Ive been trying to install the latest stable build of CM10. I decided to try the most recent Nightly now. That seemed to work. The spinning just stopped and Im on the welcome screen. FINALLY! Thank you guys for all the help. Never had such a hard time with installing a custom rom before.
Click to expand...
Click to collapse
No worries man, good luck with your One X, I hope the worst is behind you now.
If you are feeling confident, there is a method to downgrade your hboot so you don't need to stuff around flashing the boot image separately. This however does involve bricking and then de-bricking your device, and you'll need a linux computer to pull it off, so this isn't for everyone.
Hey guys, I installed CWM on my buddies HTC one S (ville) and I keep getting a weird problem with CWM. I have successfully flashed CM10 multiple times and have made only one back up. Every time his phone dies and he plugs it in and tries to power it on it boots straight to recovery and after you press reboot phone it boots right back to recovery again and again... The only way it fixes itself is when you restore the back up and then it sets him back to that date. I'm wondering if this is a problem with CWM or something else... I'm new to HTC devices because I have always been on the Galaxy line from Samsung so some of this is a little new to me...
Thanks in advance!!
This is a known glitch with CWM. If you plug it in when its off and try to turn it on, it'll automatically Boot into CWM Recovery. I prefer TWRP personally, had too many problems with CWM and getting into the same exact pain-in-the-neck Bootloop as you're referring to.
As far as I am aware, there isn't a way to get out of the CWM Bootloop unless you just let the phone run out of Battery, get into the Bootloader (Which is somewhat of a challenge with the CWM Bootloop), and then flash a different Recovery from Fastboot. Correct me if i'm wrong on there not being any other way around this.
It's happened to me once, I flashed the.stock boot.img and it worked fine.after that. Not sure if its a fix but it got me outta of it.
echo en Android
Thanks guys I think I'll try TWRP but just to check does CM10 work with TWRP and if so how do I flash a new recovery?
yes cm10 worx with twrp. For flashing recovery, download d appropriate recovery.img for ur device. place this in the fastboot folder or the platform-tools folder.
now, boot into bootloader and enter fastboot then connect phone to PC , it should say fastboot USB .
Now open a command window and use this command---
fastboot flash recovery recoveryname.img.
Sent from my One V
mattytom87 said:
Thanks guys I think I'll try TWRP but just to check does CM10 work with TWRP and if so how do I flash a new recovery?
Click to expand...
Click to collapse
Cyanogenmod 10 does indeed work with TWRP as far as I know. Along with mihirengg19's Reply above, there is also an Alternative way to flashing a new Recovery, and that is to use the HTC One S All-In-One Toolkit. Its the easiest/safest way, if you don't know what you're doing.
yes toolkit is great but manually is best...
Sent from my One V
Well, I was trying to install CM11 and did something wrong... most likely I was flashing with TWRP instead of clockworkmod recovery.
Moreover, shame on me, I did a "wipe data" or similar thing while in the confusion and now I have just the message "the device is unlocked" when booting - no access to TWRP when holding power+volume down, nothing else... am I in a dead-end? any suggestion?
Thanks in advance!
Fastboot
pippolino123 said:
Well, I was trying to install CM11 and did something wrong... most likely I was flashing with TWRP instead of clockworkmod recovery.
Moreover, shame on me, I did a "wipe data" or similar thing while in the confusion and now I have just the message "the device is unlocked" when booting - no access to TWRP when holding power+volume down, nothing else... am I in a dead-end? any suggestion?
Thanks in advance!
Click to expand...
Click to collapse
Does it go into fastboot after you see the unlock device, do you get the three icons you would normally see??
lj50036 said:
Does it go into fastboot after you see the unlock device, do you get the three icons you would normally see??
Click to expand...
Click to collapse
unfortunately not... I don't see the three icons it is stuck with the ASUS logo
nvflash
pippolino123 said:
unfortunately not... I don't see the three icons it is stuck with the ASUS logo
Click to expand...
Click to collapse
Do you have your Blob files from enabling nvflash??
lj50036 said:
Do you have your Blob files from enabling nvflash??
Click to expand...
Click to collapse
sorry don't understand what you mean. Can you please clarify. ..?
nvflash
pippolino123 said:
sorry don't understand what you mean. Can you please clarify. ..?
Click to expand...
Click to collapse
Sorry to say if you don't know what nvflash is or blobs and you don't have fastboot access.. time to send it to asus
You needed to do this first!!!!!
https://www.androidroot.mobi/nvflash-for-tegra3-transformer-tf700t/
lj50036 said:
Sorry to say if you don't know what nvflash is or blobs and you don't have fastboot access.. time to send it to asus
You needed to do this first!!!!!
https://www.androidroot.mobi/nvflash-for-tegra3-transformer-tf700t/
Click to expand...
Click to collapse
yes, I think you are right... didn't know about the nvflash stuff. Thanks either way for your help!
Well if you do send it in... When you get it back look me up... We will get your blobs off it so you can't brick it!!!!!
Sent from my One using XDA Premium 4 mobile app
lj50036 said:
Well if you do send it in... When you get it back look me up... We will get your blobs off it so you can't brick it!!!!!
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sure I will... thanks again and happy holidays
So since I feel like I have a complex problem that I can't seem to search for, I'm piggy backing this thread. It's been a year since I rooted this tablet, and I went on deployment with it. Worst ROM ever, couldn't get YouTube, WiFi was sketchy at best so I came back and it even had the OTA updater to update to a newer version, well that wouldn't load at all.
So I was in the process of trying to kill this crap ROM and upload I think CYA.. eh it's not the issue. So the first thing it asked me to do was this TWRP (which is new to me from a year ago) and I installed v2.5.0.0. When the tablet was working, that program seemed to work just fine, but when I rebooted in to RCK, it's so skewed and off center that I can't see half the screen. So when I tried to update to this new ROM, I kept getting download faults, so I figured I was stuck with this crap ROM because basically I quit trying. Well I tried to restart my tablet and this TWRP thing came up and asked if I wanted to run this (NEWVERSION).zip (I don't want to call out the development team, I'm sure their most recent update is much better) but basically it was the new version of the ROM I was running, so I let TWRP (from the loaded up tablet) to "install new zip" so I of course wiped data, cache and dalvik (I didn't save anything to this tablet, nothing to lose)
Well now, I'm stuck in the bricked mode of ASUS screen. If I hold down volume and power, I get RCK/Android/Wipe Data. I ever get the computer asking me to install new drivers, but of course it won't recognize the TF700 as a disk.
Any suggestions on how to get this thing back?
First the good news:
The page with the three icons is the bootloader menu which means you should have fastboot access to your tablet from your computer.
You can use fastboot to flash a new recovery (TWRP) and once that is installed you can flash the new rom.
So this can be fixed relatively easy, but you have to do some reading before attempting it. Done correctly this is a safe procedure. Done without understanding what you are doing could leave you with a hard brick - right now you're probably just soft bricked.
s14owner95 said:
So I was in the process of trying to kill this crap ROM and upload I think CYA.. eh it's not the issue. So the first thing it asked me to do was this TWRP (which is new to me from a year ago) and I installed v2.5.0.0. When the tablet was working, that program seemed to work just fine, but when I rebooted in to RCK, it's so skewed and off center that I can't see half the screen.
Click to expand...
Click to collapse
I am not sure what happened here. I have used TWRP since version 2.3.x and never had the problem you describe. I suspect you installed a version for a different device - not the one specific for the TF700.
Well I tried to restart my tablet and this TWRP thing came up and asked if I wanted to run this (NEWVERSION).zip (I don't want to call out the development team, I'm sure their most recent update is much better) but basically it was the new version of the ROM I was running, so I let TWRP (from the loaded up tablet) to "install new zip" so I of course wiped data, cache and dalvik.
Click to expand...
Click to collapse
Are you sure you had TWRP installed???
If I understand this correctly, you booted the tablet normally and got a notification to upgrade the STOCK rom to a newer STOCK version? TWRP would not do that - it just doesn't have the functionality to recognize a newer firmware version.
If you say you "let TWRP from the loaded up tablet to install new zip" - do you mean you were booted into Android? You were running the system? That would clinch it: Whatever you were using (and I am afraid it was ROMToolbox or some such) - it was not TWRP. TWRP is your custom recovery. You have to boot into it to use it.
Well now, I'm stuck in the bricked mode of ASUS screen. If I hold down volume and power, I get RCK/Android/Wipe Data. I ever get the computer asking me to install new drivers, but of course it won't recognize the TF700 as a disk.
Any suggestions on how to get this thing back?
Click to expand...
Click to collapse
Question: Did you unlock the tablet? Did you use the Asus Unlock Tool to unlock the bootloader or did you just root it? When you booted it up: Do you remember seeing "This device is unlocked" in tiny script in the upper left?
I assumed you were unlocked, but writing this post I developed doubt. I suspect you just rooted, downloaded ROMToolbox and tried to flash a new rom through it.
That does not work on this device. You have to unlock the bootloader, install a custom recovery and then you can flash a custom rom. Do not use ROMToolbox on this device!
So before I even attempt to explain the fastboot procedure, I have to know if you unlocked your TF700.
If not, you can't use fastboot.
Your last option then would be to pray that the stock recovery still works and flash the stock firmware.
berndblb said:
First the good news:
I am not sure what happened here. I have used TWRP since version 2.3.x and never had the problem you describe. I suspect you installed a version for a different device - not the one specific for the TF700.
Click to expand...
Click to collapse
That's a good possibility since I was trying to locate what I wanted via my phone, my laptop crashed last week, which is really the only reason I busted out this tablet, I borrowed a computer to try to get this fixed
berndblb said:
Are you sure you had TWRP installed???
If I understand this correctly, you booted the tablet normally and got a notification to upgrade the STOCK rom to a newer STOCK version? TWRP would not do that - it just doesn't have the functionality to recognize a newer firmware version.
If you say you "let TWRP from the loaded up tablet to install new zip" - do you mean you were booted into Android? You were running the system? That would clinch it: Whatever you were using (and I am afraid it was ROMToolbox or some such) - it was not TWRP. TWRP is your custom recovery. You have to boot into it to use it.
Click to expand...
Click to collapse
TWRP didn't ask me about the update, the OTA Updater built into the ROM that I installed at the beginning of the year did. After I unsuccessfully tried to install the TWRP and CYNA ROM, I rebooted and the OTA came up saying a newer version was available, once it went to reboot into recovery, TWRP came up
berndblb said:
Question: Did you unlock the tablet? Did you use the Asus Unlock Tool to unlock the bootloader or did you just root it? When you booted it up: Do you remember seeing "This device is unlocked" in tiny script in the upper left?
I assumed you were unlocked, but writing this post I developed doubt. I suspect you just rooted, downloaded ROMToolbox and tried to flash a new rom through it.
That does not work on this device. You have unlock the bootloader, install a custom recovery and then you can flash a custom rom. Do not use ROMToolbox on this device!
So before I even attempt to explain the fastboot procedure, I have to know if you unlocked your TF700.
If not, you can't use fastboot.
Your last option then would be to pray that the stock recovery still works and flash the stock firmware.
Click to expand...
Click to collapse
I know I went to the ASUS website and unlocked the tablet, it does say "This device is unlocked" at the top left once I turn on the computer.. I'm going to try to screen shot from my phone and update what TWRP looks like on the tablet in recovery
Hope this worked
s14owner95 said:
That's a good possibility since I was trying to locate what I wanted via my phone, my laptop crashed last week, which is really the only reason I busted out this tablet, I borrowed a computer to try to get this fixed
TWRP didn't ask me about the update, the OTA Updater built into the ROM that I installed at the beginning of the year did. After I unsuccessfully tried to install the TWRP and CYNA ROM, I rebooted and the OTA came up saying a newer version was available, once it went to reboot into recovery, TWRP came up
I know I went to the ASUS website and unlocked the tablet, it does say "This device is unlocked" at the top left once I turn on the computer.. I'm going to try to screen shot from my phone and update what TWRP looks like on the tablet in recovery
Click to expand...
Click to collapse
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
berndblb said:
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
Click to expand...
Click to collapse
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
berndblb said:
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
Click to expand...
Click to collapse
The ROM I was running had an "OTA Updater" which updated the ROM I was using, I don't want to blast them, but it's just not a good ROM.
So now, I was able to "fastboot devices" and it says 015d25681a481802 fastboot" It let me type the command "fastboot -i 0x05B0 flas recovery twrp.blob
But now I can't flash anything else. Like I said, I can't get the drivers to fully install so I can't mount the tablet like an external drive, I can't even get it passed the "ASUS" title page. Is there a way I can push this 4.2.1 CROMi ROM through fastboot?
s14owner95 said:
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
Click to expand...
Click to collapse
Mmmhh, your tablet may need a little deeper cleaning. Check out buster99's post (#12). His method has helped dozens recover from worse than you have right now.
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
His instructions are for the TF300. naturally you want to flash the blob for the TF700. That would get you back to a healthy stock system. Then you can again flash TWRP and through it a custom rom.
Good luck!
---------- Post added at 05:36 PM ---------- Previous post was at 05:28 PM ----------
s14owner95 said:
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
The ROM I was running had an "OTA Updater" which updated the ROM I was using, I don't want to blast them, but it's just not a good ROM.
So now, I was able to "fastboot devices" and it says 015d25681a481802 fastboot" It let me type the command "fastboot -i 0x05B0 flas recovery twrp.blob
But now I can't flash anything else. Like I said, I can't get the drivers to fully install so I can't mount the tablet like an external drive, I can't even get it passed the "ASUS" title page. Is there a way I can push this 4.2.1 CROMi ROM through fastboot?
Click to expand...
Click to collapse
Are you saying the twrp flash went ok?
You don't flash the rom in fastboot. You boot back into recovery, choose "Install" and select the CROMi-X zip you downloaded.
But before you do that I would seriously suggest you format your data partition. That means you have to have the downlaoded rom zip on your external card (otherwise you will erase it with the format).
So boot into TWRP, choose Wipe > Advanced > Format data
Then go back to TWRP Home, choose Install and navigate to the CromiX zip. Make sure the box "verify zip signature" is checked and flash the rom.
Do this only if you have a working recovery!!! Do not attempt with your busted one!!
You can only access the tablet in MTP (as an external drive) if your system is working. It's not - yet.
OK, so here's the lastest for me. I tried to "adb push ROM.zip ROM.zip/sdcard/" - error: device not found. I also tried "adb sideload" -error: device not found.
Also now, instead of the computer asking me to install drivers for my new device, it's registered as a "android bootloader interface" I tried to download the ASUS android USB drivers and update them, but Windows thinks my drivers are up to date.
s14owner95 said:
OK, so here's the lastest for me. I tried to "adb push ROM.zip ROM.zip/sdcard/" - error: device not found. I also tried "adb sideload" -error: device not found.
Also now, instead of the computer asking me to install drivers for my new device, it's registered as a "android bootloader interface" I tried to download the ASUS android USB drivers and update them, but Windows thinks my drivers are up to date.
Click to expand...
Click to collapse
To use ADB you have to be in your recovery or the Android system needs to run.
If you have a working recovery back - why do you want to mess with ADB unless you are familiar with it? You are treading on thin ice doing stuff without really understanding what you are doing! What's the rush?
The problem is that I don't have a working recovery back. i still have that screwed up screen that only shows a portion of TWRP. It let me push that recovery to it, but I can't see enough of the recovery to actually flash something to it..
I tried to download the drivers and push those manually, but windows doesn't recognize it
s14owner95 said:
The problem is that I don't have a working recovery back. i still have that screwed up screen that only shows a portion of TWRP. It let me push that recovery to it, but I can't see enough of the recovery to actually flash something to it..
I tried to download the drivers and push those manually, but windows doesn't recognize it
Click to expand...
Click to collapse
Your drivers are working. You need different sets of drivers for different modes: fastboot drivers, adb drivers, mtp drivers.
Your tablet shows up as a bootloader interface because it is in fastboot mode - ergo the fastboot drivers are working.
You HAVE to get a working recovery onto the tablet. It will NOT work without a recovery. To push a rom zip to the tablet is useless - the only thing working on your tablet is fastboot mode.
If the recovery flash fails, try buster99's method. That should clean all the crud off your partitions.
But you need to have the Asus firmware blob file for this! You cannot do this with any rom zip!!
Edit: You did push the correct recovery this time, did you?
TeamApexQ is proud to release TWRP (from our OmniToad builds) for general use.
Current release: 2.8.1.0_0001
Raw image (for heimdall/Crazy 'cat'ing):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.img
md5: https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.img.md5sum
update.zip format (Recovery flashable/sideloadable):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.zip
md5: https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.zip.md5sum
ODIN compatible tarball format (ODIN):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.tar.md5
Please let us know of any other issues. Also with any other issues, please include a copy of your recovery.log, and dmesg from the TWRP session.
Thanks for your work TeamApexQ!
Sent from my SGH-T699 using XDA Premium 4 mobile app
falle21 said:
Thanks for your work TeamApexQ!
Sent from my SGH-T699 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nice...Will be building some twrp themes just for the Relay 4G....glad you guys built it as ive been pretty busy
The work around for the "failed" flash. Unmount system in the "mount" menu prior to doing any flashing of zips. Even I have to do this on the G2 with TWRP 2.6.3.4.
Sent from my LG-VS980 using Tapatalk 4
New build posted in the OP!
Will now flash old Android builds (I've tested with every build I could get my hands on.)
I've never used TWRP, how does it differ from CWM for Backups ?
Are my CWM "nandroid" backups cross compatible ? I have Carbon, Omni and CM11 backups ready to switch at any time for testing in .tar format.
No twrp backups differ from cwm...however Philz can handle twrp and cwm backups...however and in my opinion twrp can do a lot more as a recovery than any other recovery...one thing you can do...and is a slight pain...is boot the backup with cwm or philz. flash twrp and re backup that ROM in twrp then delete the old one...repeat for all backups
Sent from my ADR6425LVW using xda app-developers app
REV3NT3CH said:
No twrp backups differ from cwm...however Philz can handle twrp and cwm backups...however and in my opinion twrp can do a lot more as a recovery than any other recovery...one thing you can do...and is a slight pain...is boot the backup with cwm or philz. flash twrp and re backup that ROM in twrp then delete the old one...repeat for all backups
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
hmm yea ... or switch between recoveries restore w/ cwm, install twp, reboot re-create backup .. repeat.
Is there a fix permissions in twrp ? and is usb mounting in windows ? I found I didn't have the functionality of either with the latest CWM
yohan4ws said:
hmm yea ... or switch between recoveries restore w/ cwm, install twp, reboot re-create backup .. repeat.
Is there a fix permissions in twrp ? and is usb mounting in windows ? I found I didn't have the functionality of either with the latest CWM
Click to expand...
Click to collapse
thats what i was refferring too for saving your backups and restorable via twrp....and yes to all the other questions...twrp can do so many things while in recovery...for example..say you downloaded a rom from phone and forgot to put it in root of sdcard...twrp has a file manager with copy and paste functionalities to do so...it supports adb sideloading, mounting for both windows and linux, permissions, much better and clearer wiping method...all touchscreen...very themable for example http://forum.xda-developers.com/showpost.php?p=45122951&postcount=1 i made this theme specifically for my htc rezound as well as many others...which ill more than likely port to the relay as it has to match screen dimensions for resolution...overall it just has a bulk of many great options for a recovery and is very easy to use and get used to
New build posted in the OP. Small bugfixes in this release. (Including some SELinux and settings fixes.)
Did something wrong. How to fix?
Magamo said:
TeamApexQ is proud to release TWRP (from our OmniToad builds) for general use.
Current release: 2.7.0.0_0002
Raw image (for heimdall/Crazy 'cat'ing):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.7.0.0_0002.img
Click to expand...
Click to collapse
I wanted to install this version of twrp on my apexqtmo using heimdall under linux.
I booted into "download" mode, connected my USB table to my linux box, and I then stupidly flashed the wrong twrp module by mistake (for a different phone).
Without realizing my mistake, I then rebooted. I ended up back in my OS, and then, using the Power Menu, I booted into recovery mode. I got the blue text saying RECOVERY BOOTING.... , but after that, the screen remained black.
From then on, I cannot boot into the normal OS, nor into "download" mode.
Even if I remove the battery and then perform a standard boot using the power button alone, I get the blue text saying I'm booting into recovery, and the dead, black screen shows up.
I want to boot into the OS or download mode, but I can no longer do either. No matter what combinations of Volume-Up, Volume-Down, Home, and Power that I press, I always get back to RECOVERY BOOTING...., and I can't get into download mode again, no matter what.
Did I brick my phone?
If not what can i do to fix it?
Thanks for any help.
.
The only way to clear the reboot mode is to either trigger a different mode or complete the boot. If key combinations don't work, you can try to see if the device comes up in adb and then you can "reboot bootloader" failing that you can trigger download mode with a resistor on the usb port. Google galaxy s 3 jig to find out how to make one or buy one
Sent from my Nexus 7 using Tapatalk
Nardholio said:
The only way to clear the reboot mode is to either trigger a different mode or complete the boot. If key combinations don't work, you can try to see if the device comes up in adb and then you can "reboot bootloader" failing that you can trigger download mode with a resistor on the usb port. Google galaxy s 3 jig to find out how to make one or buy one
Click to expand...
Click to collapse
Thank you very much!
... and I fixed it!!!!
Your adb suggestion led me to the solution ...
I tried adb, but it didn't work.
However, after that adb attempt, the usb cable was still plugged into my device from my linux box, and I noticed that the device was in some sort of boot loop. The device kept giving short vibrations every few seconds.
At that point, I tried one more key combination that I hadn't thought of before: with the cable still plugged in, I held down Volume-down and Home without pressing the Power button ... because I guessed that the existence of the boot loop means that power might already be on, which would cause the power key to be unnecessary.
And my guess was correct: I got into Download mode!
I flashed the correct version of TWRP, and now all is well.
Thank you again for providing the suggestion that led me to my solution!
Also, thank you for telling me about the jig. I'm now going purchase one anyway, just in case I screw up again in the future. I think I can get one for $8 or less (I'm too lazy and clumsy to try to make one on my own).
.
It's weird, but I had the same experience with the blue "RECOVERY BOOTING" followed by dead phone as described a couple posts ago... and I was flashing the correct file, the twrp zip in the OP, from recovery (cwm 6.0.3.7). I did it twice and got the same bad result.
To get around the bad dead phone result, I held volume down and power for 15 seconds, got into download mode, and then selected volume down to allow the phone to boot normally. Once it did, I went to the Play store and installed an app that could flash another recovery (cwm 6.0.4.5). Which worked.
I will try flashing the .img file and see if that works, but I'm kinda perplexed why the twrp zip didn't work from recovery...
Sent from my Nexus 5 using Tapatalk
reaper000 said:
I will try flashing the .img file and see if that works, but I'm kinda perplexed why the twrp zip didn't work from recovery...
Click to expand...
Click to collapse
You indeed have to flash the .img file, at least if you're installing from the command line using heimdall.
.
Ended up successfully flashing the .img file with recovery tools app from play store. Thanks all!
Sent from my Nexus 5 using Tapatalk
reaper000 said:
Ended up successfully flashing the .img file with recovery tools app from play store. Thanks all!
Click to expand...
Click to collapse
Glad it worked.
Also, FYI: you can't flash a recovery from within recovery. This is why your earlier attempt to flash the .zip from within recovery didn't work.
As far as I know, you have to be in bootloader mode (also called "download" mode) in order to flash a recovery. You have to boot into that mode and use somthing like heimdall to install the .img file. There are also tools you can use which will flash a recovery from a .zip file, but they actually just extract the .img file from the .zip file and then load that .img file via bootloader mode.
.
HippoMan said:
Glad it worked.
Also, FYI: you can't flash a recovery from within recovery. This is why your earlier attempt to flash the .zip from within recovery didn't work.
As far as I know, you have to be in bootloader mode (also called "download" mode) in order to flash a recovery. You have to boot into that mode and use somthing like heimdall to install the .img file. There are also tools you can use which will flash a recovery from a .zip file, but they actually just extract the .img file from the .zip file and then load that .img file via bootloader mode.
.
Click to expand...
Click to collapse
The .zip file provided here CAN be flashed from within recovery. What likely happened was a bad download.
Magamo said:
The .zip file provided here CAN be flashed from within recovery. What likely happened was a bad download.
Click to expand...
Click to collapse
Yeah, was thinking bad download, but I dl'd it twice. And there was no MD5 checksum that I could see
Sent from my Nexus 5 using Tapatalk
reaper000 said:
Yeah, was thinking bad download, but I dl'd it twice. And there was no MD5 checksum that I could see
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Actually, which version of CWM were you using to attempt to install this from? Likely significantly old versions were not set up to flash recovery properly.
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Click to expand...
Click to collapse
Did you ever try pull out the battery, reinsert, reboot system with 3 buttons combination? I got several fastboot mode as you're facing, and the system works just fine using above method.
I think you got just soft brick. Please, keep the device stay untouched until someone with such expertise to solve the problem will guide you. I think @akiratoriyama can share his bad experience bricking his lovely p500.
Wish you luck.
PS.
You must to press three buttons a bit longer, do not release it, until recovery mode appearing. Otherwise fastboot mode or blank screen showing instead.
Sent from my Optimus One using xda app-developers app
agk.ganesh said:
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Click to expand...
Click to collapse
Two years ago I bricked my phone also after using ROM manger. Though I will never ever use this or similar tools again. But at least, if I remember correctly, I could revive my phone with the "fastboot erase recovery" method http://forum.xda-developers.com/showthread.php?t=1088046. But since you failed is seems to be another problem. I am not a fastboot expert , but since you bricked your phone with ROM manager too, I wanted to share my success story with above mentioned method and installing AmonRa recovery. So maybe you will give it a second try? All I can remember is, that it is extremely important to follow the instructions exactly.
xu3sno said:
Did you ever try pull out the battery, reinsert, reboot system with 3 buttons combination? I got several fastboot mode as you're facing, and the system works just fine using above method.
I think you got just soft brick. Please, keep the device stay untouched until someone with such expertise to solve the problem will guide you. I think @akiratoriyama can share his bad experience bricking his lovely p500.
Wish you luck.
PS.
You must to press three buttons a bit longer, do not release it, until recovery mode appearing. Otherwise fastboot mode or blank screen showing instead.
Sent from my Optimus One using xda app-developers app
Click to expand...
Click to collapse
androidck said:
Two years ago I bricked my phone also after using ROM manger. Though I will never ever use this or similar tools again. But at least, if I remember correctly, I could revive my phone with the "fastboot erase recovery" method http://forum.xda-developers.com/showthread.php?t=1088046. But since you failed is seems to be another problem. I am not a fastboot expert , but since you bricked your phone with ROM manager too, I wanted to share my success story with above mentioned method and installing AmonRa recovery. So maybe you will give it a second try? All I can remember is, that it is extremely important to follow the instructions exactly.
Click to expand...
Click to collapse
Thanks @xu3sno & @androidck
I am also getting help from mukulsoni & others in Official CM11 version 10 thread.
I am able to go into the flash tool (pointed by mukulsoni, http://forum.xda-developers.com/showpost.php?p=49567169&postcount=45)
and able to go 'Select kernel to hotboot' with recovery.img (CWMod-6.4.0.6-Jan16)
But rebooting by HOME+Volume DOWN+POWER --> goes into CWM recovery of v5.0.2.0 (which i installed initially)
I am thinking, what to do next.
I will keep my progress posted here.
Thanks for listening..
agk.ganesh said:
Thanks @xu3sno & @androidck
I am also getting help from mukulsoni & others in Official CM11 version 10 thread.
I am able to go into the flash tool (pointed by mukulsoni, http://forum.xda-developers.com/showpost.php?p=49567169&postcount=45)
and able to go 'Select kernel to hotboot' with recovery.img (CWMod-6.4.0.6-Jan16)
But rebooting by HOME+Volume DOWN+POWER --> goes into CWM recovery of v5.0.2.0 (which i installed initially)
I am thinking, what to do next.
I will keep my progress posted here.
Thanks for listening..
Click to expand...
Click to collapse
Are you sure that you are booting into cwm v5.0.2.0? Version is listed at the top. If that is true, then either the flash tool failed to flash cwm v6.4.0.6, or you have chosen the wrong recovery.img. This can easily happen since they all have the same name. Try to flash it again, but make sure that you use the correct image.
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Edit: Here is a link to cm-10.1.6:
http://jenkins.androidarmv6.org/view/All/job/android/597/
Gapps already included.
Sent from my LG-P509 using Tapatalk 2
ibub said:
Are you sure that you are booting into cwm v5.0.2.0?
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Click to expand...
Click to collapse
+1
CM10.1.6 worked
ibub said:
Are you sure that you are booting into cwm v5.0.2.0? Version is listed at the top. If that is true, then either the flash tool failed to flash cwm v6.4.0.6, or you have chosen the wrong recovery.img. This can easily happen since they all have the same name. Try to flash it again, but make sure that you use the correct image.
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Edit: Here is a link to cm-10.1.6:
http://jenkins.androidarmv6.org/view/All/job/android/597/
Gapps already included.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Thanks @ibub for your helping hand.
I will check why recovery image not upgrading as expected. (I didn't manually download CWM5.xx version to my PC. I got it via ROM manager app, so i hope I haven't chosen wrong image)
Yes, I got CM10.1.6 from your link and installation went successfully and able to boot up..
But, it is very slow. (May be it will take some time?!) I will check it.
Between, @mukulsoni advised to install CWM6.xxx via CWM5.0.2.0. I will check how it goes.
mns123 said:
+1
Click to expand...
Click to collapse
Thanks.
agk.ganesh said:
Thanks @ibub for your helping hand.
I will check why recovery image not upgrading as expected. (I didn't manually download CWM5.xx version to my PC. I got it via ROM manager app, so i hope I haven't chosen wrong image)
Yes, I got CM10.1.6 from your link and installation went successfully and able to boot up..
But, it is very slow. (May be it will take some time?!) I will check it.
Between, @mukulsoni advised to install CWM6.xxx via CWM5.0.2.0. I will check how it goes.
Thanks.
Click to expand...
Click to collapse
Yeah, I chose to post that link only to make sure that your phone is healthy. Now you can install any recovery/rom that you want. If your volume keys are broken, I suggest that you flash to twrp recovery. It's touch driven.
Sent from my LG-P509 using Tapatalk 2
Thanks
ibub said:
Yeah, I chose to post that link only to make sure that your phone is healthy. Now you can install any recovery/rom that you want. If your volume keys are broken, I suggest that you flash to twrp recovery. It's touch driven.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I will try installing now new recovery and then new ROM.
Very glad to see the support from you guys... Thanks ibub and all..
[rant] NEVER EVER USE KDZ. PERIOD. :crying: [/rant]
Best of luck on your ROM journey :good:
Thanks
akiratoriyama said:
[rant] NEVER EVER USE KDZ. PERIOD. :crying: [/rant]
Best of luck on your ROM journey :good:
Click to expand...
Click to collapse
Thanks @akiratoriyama.
I have upgraded CWM recovery 6.xx through CWM 5.0.2.0 and successfully installed MukulSoni's Kitkat ROM.
And enjoying eating kitkat..
Thanks all..