Related
So im running 3.1 rooted with the 1.4.4 Tiamat Kernel. I had this weird force closing issue where gapps would force close whenever i tried to connect to wifi. I powered down, turned on, and am now stuck in a boot animation loop. I can hold down the Vol Down button and it says "Starting Fastboot Protocol Support." but nothing changes. Is there anything I can do it fix it/turn it off until i get home to my computer with the SDK? On another note I did install the wpa supplicant (sp?) files to allow it to connect to an adhoc wifi source (eris tether). Please and thank you
EDIT: I have booted into recovery, but I am unable to mount any of the drive locations or wipe them. I did a factory data reset (as much as it could I guess?), but im still at the boot loop.
Hook it up to computer while its in fastboot and open a command prompt from the folder you have fastboot. Type "fastboot reboot-bootloader" and you should get adb to recognize, then push stock images or root images and recovery.
What recovery were you using? Did you flash the one from ROM manager?
I am using the CM from the ROM manager the latest one I think that it is version 4 something. does this make a difference? I have backups from my previous flash but when I tried to recover it won't take them. where can I get the root image? I might have it already since I rooted using adb, I will have to look on my laptop when I get home. Any other info you have will help. Thank you,,,,
razor532 said:
I am using the CM from the ROM manager the latest one I think that it is version 4 something. does this make a difference? I have backups from my previous flash but when I tried to recover it won't take them. where can I get the root image? I might have it already since I rooted using adb, I will have to look on my laptop when I get home. Any other info you have will help. Thank you,,,,
Click to expand...
Click to collapse
You will need to flash a good recovery, I suggest you you use the .img file in this thread through adb when you get to your laptop:
http://forum.xda-developers.com/showthread.php?t=1074979
The recovery version you updated to won't look at your external sdcard, so you can't flash from it until you re-install a good recovery.
Can't we get a pinned warning about this issue?
Thanks everyone, sorry for the delay. I ended up fixing it with a fastboot oem unlock command. However after countless flashes unable to get it to boot again i realized i was flashing the tiamat rom and then a different tiamat kernel boot.img, most likely the culprit in my boot loop. The minute i did a factory reset, updated cwr and only flashed the rom, everything works fine. Thanks for everyones help
Sent from my Eris using XDA App
So glad you were able to fix it!
I accepted the latest over the air update and I need to know if that messed up my chances of obtaining root. I tried photon torpedo and could not get it to work. My device says it is unlocked but I can not boot into recovery. I have flashed several recoveries using sdk-tools but I cannot erase any recoveries. I receive an error. I have tried several things and am at a loss to as what is the most recent way if there is one. Looking for someone with more experience then I to guide me. I previously rooted my EVO 4g and EVO 3d and was away from internet for about 9 months so I mistook the old Motorola Photon for the Photon Q. Didn't realize till way later that I was trying some rooting techniques intended for the old photon on my photon q. Anyways I feel a bit lost. Any help would be greatly appreciated. I can provide any information requested. Will be monitoring this thread all day today and will provide quick responses. Cheers!
Uhm... You tried the rooting steps for the Photon?
I really hope you didn't brick your device - that is a SURE fire way to do it tho.
Anyhoo, why haven't you just tried the official unlock from Moto?
arrrghhh said:
Uhm... You tried the rooting steps for the Photon?
I really hope you didn't brick your device - that is a SURE fire way to do it tho.
Anyhoo, why haven't you just tried the official unlock from Moto?
Click to expand...
Click to collapse
I did try that first. And successfully as far as I know because my bootloader says unlocked. I then went to install supersu and It won't install su binary. Tried to force install su binary and that did not work either. Any ideas? I joined the military so I was busy for 9 months straight. Honestly I'm usually more up to date than that. I think it's an understandable mistake and I understand the risks behind rooting. I bricked my first phone 7 years ago and brought it back using putty.
sent17inel said:
I did try that first. And successfully as far as I know because my bootloader says unlocked. I then went to install supersu and It won't install su binary. Tried to force install su binary and that did not work either. Any ideas? I joined the military so I was busy for 9 months straight. Honestly I'm usually more up to date than that. I think it's an understandable mistake and I understand the risks behind rooting. I bricked my first phone 7 years ago and brought it back using putty.
Click to expand...
Click to collapse
You didn't truly brick the device if you were able to bring it back using putty...
Regardless, you should always be careful with anything you do. Why are you trying to install the SuperSU binary right after unlocking? You need to flash a custom recovery first.
Or do you already have a custom recovery? I'm kinda lost here, you seemed to indicate you were unable to get a custom recovery flashed, but you're trying to force SuperSU without a custom recovery...?
arrrghhh said:
You didn't truly brick the device if you were able to bring it back using putty...
Regardless, you should always be careful with anything you do. Why are you trying to install the SuperSU binary right after unlocking? You need to flash a custom recovery first.
Or do you already have a custom recovery? I'm kinda lost here, you seemed to indicate you were unable to get a custom recovery flashed, but you're trying to force SuperSU without a custom recovery...?
Click to expand...
Click to collapse
Soft bricked . . . I tried to flash a custom recovery. I Tried 2. CW and another one that I can't remember at the moment. They both said they flashed successfully but I was unable to boot into any of them. I got the android with an exclamation mark. I tried to erase them and it gave me an error. Some kind of permission error. I did this all a few days ago. Decided to take a break. Honestly "you should always be careful with anything you do" . . did that really need to be said?
sent17inel said:
Honestly "you should always be careful with anything you do" . . did that really need to be said?
Click to expand...
Click to collapse
Hey, I'm not trying to force SuperSU to apply without a custom recovery here... one step at a time is all I'm trying to say.
Let's get on with it...
sent17inel said:
Soft bricked . . . I tried to flash a custom recovery. I Tried 2. CW and another one that I can't remember at the moment. They both said they flashed successfully but I was unable to boot into any of them. I got the android with an exclamation mark. I tried to erase them and it gave me an error. Some kind of permission error. I did this all a few days ago. Decided to take a break.
Click to expand...
Click to collapse
So you haven't been able to flash a custom recovery. When you flash, it says successful? Perhaps try again. Follow the directions carefully.
arrrghhh said:
Hey, I'm not trying to force SuperSU to apply without a custom recovery here... one step at a time is all I'm trying to say.
Let's get on with it...
So you haven't been able to flash a custom recovery. When you flash, it says successful? Perhaps try again. Follow the directions carefully.
Click to expand...
Click to collapse
I did try again about 5 minutes ago. It says that it won't unlock because it's already unlocked.
I got into the stock recovery. adb reboot recovery and then it will display a green android laying down with a red exclamation point. From there I hit both volume keys and it brings up the stock recovery menu. I should be able to go from here. I think the Update I did changed some things that caused the CW recovery to not flash right or to be rewritten before I can boot into it. I should be good now. Thank you for your help.
sent17inel said:
I got into the stock recovery. adb reboot recovery and then it will display a green android laying down with a red exclamation point. From there I hit both volume keys and it brings up the stock recovery menu. I should be able to go from here. I think the Update I did changed some things that caused the CW recovery to not flash right or to be rewritten before I can boot into it. I should be good now. Thank you for your help.
Click to expand...
Click to collapse
So you managed to flash custom recovery? I didn't mean to say you should try to unlock again - I meant you should try flashing recovery again (CWM, TWRP).
arrrghhh said:
So you managed to flash custom recovery? I didn't mean to say you should try to unlock again - I meant you should try flashing recovery again (CWM, TWRP).
Click to expand...
Click to collapse
With the over the air update it installs a shell script that forces the install of the stock recovery. When you reboot into the stock recovery you are presented with an image that looks like it has failed (android laying down with stomach open and a red exclamation point over it.) it will not do anything from here and eventually time out and reboot itself. If when it is at this image you press both volume keys you will be presented with a Recovery menu. I can take it from here. Thank you.
sent17inel said:
With the over the air update it installs a shell script that forces the install of the stock recovery. When you reboot into the stock recovery you are presented with an image that looks like it has failed (android laying down with stomach open and a red exclamation point over it.) it will not do anything from here and eventually time out and reboot itself. If when it is at this image you press both volume keys you will be presented with a Recovery menu. I can take it from here. Thank you.
Click to expand...
Click to collapse
Ok... Good luck.
Thread moved. Please post in the correct forum sections in future. All questions belong here in Q&A.
Thanks
AvRS
unlocking nd rooting visuals
can someone who owns Photon Q 4G LTE do a visual on rooting nd unlocking the bootloader cause was thinking bout getting this phone & dont wanna brick the phone i have read the guide's nd done tons of reseaching but found no visual's on how to do it can someone help pls?
thanks in advance
1300 said:
can someone who owns Photon Q 4G LTE do a visual on rooting nd unlocking the bootloader cause was thinking bout getting this phone & dont wanna brick the phone i have read the guide's nd done tons of reseaching but found no visual's on how to do it can someone help pls?
thanks in advance
Click to expand...
Click to collapse
Well, I was going to ask you where you are stuck in the process, but it sounds like you haven't even purchased the device yet...
I wouldn't worry about unlocking and rooting until the device is in your hands. We can help out a lot easier when you actually have the thing, hahaha.
To answer your question, I don't think there's any visuals because it's not a very visual thing. fastboot is anything but visually-appealing, and the process is rather dry. Just follow the steps carefully and you'll be fine. It's very straightforward.
Plus you must decide if you prefer to keep the bootloader LOCKED or UNLOCKED and still have root access. Research the differences in the two.
The only thing simple is the belief in simplicity.
Similar problem
Hey, I have similar problem here
I tried to root my phone using howtos on internet, but when I flash cwm img (first try from howtos, second try from CWM page), it take only a second (in every howto is it should take few minutes). But it returns that cwm was flashed sucessfully. Still.... its weird.
Then - when I want to reboot to CWM, I can see only that dead poor green thing. I tried to upload the superuser zip from here, but it returns "signature verification failed".
I still belive, there IS CWM recovery, because img was flashed sucessfully (or am I wrong?) so i tried to reboot to CWM via adb.
And another problem has appeared. ADB doesn`t recognise my phone. I installed the newest drivers from moto pages (USB drivers bit 4.7.1 and DeviceManager 2.3.4) have USB debugging mod ON, restarted my computer (win7 64bit), tried stand on my head, kill black ****.... it still returns "device not found".
Any ideas how to get to the next step? Functional adb would be great...
How long took you to flash cwm image?
Thx
D.Eternity said:
Hey, I have similar problem here
I tried to root my phone using howtos on internet, but when I flash cwm img (first try from howtos, second try from CWM page), it take only a second (in every howto is it should take few minutes). But it returns that cwm was flashed sucessfully. Still.... its weird.
Then - when I want to reboot to CWM, I can see only that dead poor green thing. I tried to upload the superuser zip from here, but it returns "signature verification failed".
I still belive, there IS CWM recovery, because img was flashed sucessfully (or am I wrong?) so i tried to reboot to CWM via adb.
And another problem has appeared. ADB doesn`t recognise my phone. I installed the newest drivers from moto pages (USB drivers bit 4.7.1 and DeviceManager 2.3.4) have USB debugging mod ON, restarted my computer (win7 64bit), tried stand on my head, kill black ****.... it still returns "device not found".
Any ideas how to get to the next step? Functional adb would be great...
How long took you to flash cwm image?
Thx
Click to expand...
Click to collapse
Let's take a step back here.
If you DON'T have ADB, you're NOT going to be able to flash CWM.
Make sure you establish an ADB connection BEFORE trying to flash again.
Good luck.
arrrghhh said:
Let's take a step back here.
If you DON'T have ADB, you're NOT going to be able to flash CWM.
Make sure you establish an ADB connection BEFORE trying to flash again.
Good luck.
Click to expand...
Click to collapse
Ok, but when I ask for fastboot devices, it returns my device (and I can work with fastboot commands). When I type adb device, it returns empty list. How is it possible?
D.Eternity said:
Ok, but when I ask for fastboot devices, it returns my device (and I can work with fastboot commands). When I type adb device, it returns empty list. How is it possible?
Click to expand...
Click to collapse
fastboot and adb are kind of separate things...
You can't access adb when the phone is in fastboot mode, and you can't access fastboot when the phone is in recovery or booted into a ROM. However, in recovery or when booted adb should work. If it's still failing make sure you're using the factory USB cable. Also, try a different port or computer.
Good luck.
arrrghhh said:
fastboot and adb are kind of separate things...
You can't access adb when the phone is in fastboot mode, and you can't access fastboot when the phone is in recovery or booted into a ROM. However, in recovery or when booted adb should work. If it's still failing make sure you're using the factory USB cable. Also, try a different port or computer.
Good luck.
Click to expand...
Click to collapse
I know fastboot and adb are separate things, this is why I assumed cwm recovery image was flashed succesfully (despite it took only a few seconds). Now I`m trying to get into CWM, but when my phone is plugged (standard mode), adb reboot recovery returns Device not found. I haven`t the original cable here, but in the office (where I have motorola cable) it was the same. Truth is both my computers are Win7 64bit. Is it possible adb has problem with 64bit system?
Thank you for helping me
Hi guys,
So this is my first post but I've been on XDA for a long time. I've been looking for an answer to this problem, and I haven't been successful in finding a post that regards to my situation...
Ok so I just got my tablet today. I upgraded to JB and then I unlocked it using the asus unlocker. I attempted to install TWRP, but when I use .blob files and attempt to load into recovery it didn't work. Anyway, I looked around and I installed CWM recovery instead.
I installed v5.5.0.4 following this guide:
http://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
Now, I notice it's written back in may of 2012 aka before jelly bean... anyway so I installed this using fast boot, and booted into recovery and it worked. I believe I installed the ICS version of CWM. I tried to install Clean Rom v3.3 and I just get bootloops. I can still boot into fastboot and clockwork mod fine.
I tried to install v6.0.1.4 via this thread http://forum.xda-developers.com/showthread.php?t=1846554
But once again if I boot into recovery it just does nothing and reboots after a few seconds.
I re-installed v5.5.0.4 and I can wipe data/install everything just as I normally would, and I still have access to Fastboot. Can I get some help on how I can 1 install the correct CWM and 2 install a working rom? I don't think I bricked my device just yet since I can still flash in fastboot etc.
Thanks guys!
You cant't wipe data from bootloader menu, If you do that, you will get unrecoverable brick.
Sorry I believe I mislead you -> I wiped data from within CWM.
Anyway, I used this thread:
http://forum.xda-developers.com/showthread.php?t=1757077
I went back to stock and I think i'll stay there for a little while longer, this process made me nervous (I've rooted my thunderbolt, droid DNA, galaxy tab 2 7" and my friends phones) so anyway I believe I installed the wrong CWM and that caused errors trying to install a JB rom on a ICS CWM... If you have any insight let me know...
undergfx said:
Hi guys,
So this is my first post but I've been on XDA for a long time. I've been looking for an answer to this problem, and I haven't been successful in finding a post that regards to my situation...
Ok so I just got my tablet today. I upgraded to JB and then I unlocked it using the asus unlocker. I attempted to install TWRP, but when I use .blob files and attempt to load into recovery it didn't work. Anyway, I looked around and I installed CWM recovery instead.
I installed v5.5.0.4 following this guide:
http://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
Now, I notice it's written back in may of 2012 aka before jelly bean... anyway so I installed this using fast boot, and booted into recovery and it worked. I believe I installed the ICS version of CWM. I tried to install Clean Rom v3.3 and I just get bootloops. I can still boot into fastboot and clockwork mod fine.
I tried to install v6.0.1.4 via this thread http://forum.xda-developers.com/showthread.php?t=1846554
But once again if I boot into recovery it just does nothing and reboots after a few seconds.
I re-installed v5.5.0.4 and I can wipe data/install everything just as I normally would, and I still have access to Fastboot. Can I get some help on how I can 1 install the correct CWM and 2 install a working rom? I don't think I bricked my device just yet since I can still flash in fastboot etc.
Thanks guys!
Click to expand...
Click to collapse
My suggestion is to flash the latest stock JB blob.
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
Once you get it sorted then flash the latest twrp for jb.
Now, when I try flashing blobs and I go to boot into RCK (I believe that's the term...) it just reboots the tablet instead of booting into recovery.
Android software is out of my element, if this was some C (somewhat similar to C) or Matlab I would better understand (I'm a senior Mechanical Engineer in college)
Edit:
Ah didn't see your post. I did what you recommended, and actually, while my device said it was on 4.1.1 JB, when I hold pwr/vol down I see a completely different menu now than last time, so I wonder if perhaps my OTA didn't correctly load everything from the firmware update hmm...
undergfx said:
Now, when I try flashing blobs and I go to boot into RCK (I believe that's the term...) it just reboots the tablet instead of booting into recovery.
Android software is out of my element, if this was some C (somewhat similar to C) or Matlab I would better understand (I'm a senior Mechanical Engineer in college)
Click to expand...
Click to collapse
The same way you flashed cwm.
Windows? Start - in search type cmd - press enter
In the cmd window cd to the directory with fastboot.
Hook cable between tablet and usb port on computer.
On tablet hold power and volume down till you see the bootloader menu.
Down volume till you are at the usb symbol - then volume up.
This should put you into fastboot mode - use the commands above.
Wait till the first command completes before you give the second command.
[INDEX][04 Feb 2013]TF300T & TG-INDEX of Roms/Dev Guides/Kernels/Recoveries/etc. You will find the stock firmware here as well as most other needs.
You will have to unzip to get the blob which you should place in the directory with fastboot.
Thank you very much.
So after flashing the most resent blob, I successfully installed CWM recovery and successfully flashed a rom. I'm not sure what the issue was before. Thank you for the help! much appreciated.
undergfx said:
Thank you very much.
So after flashing the most resent blob, I successfully installed CWM recovery and successfully flashed a rom. I'm not sure what the issue was before. Thank you for the help! much appreciated.
Click to expand...
Click to collapse
You're welcome.
Good Luck!
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?
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
nexus_5_ said:
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
Click to expand...
Click to collapse
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Thank you very much for the reply, I really do have no idea as to how to flash the factory image because i am very new in this area. Could you please recommend software and which factory image i should download, please ?? thanks very much.
:good:
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Also, you mentioned a 'special kernel' what does that mean. All i want to do to my device is install cyanogenmod 12 and for that i believe it needs to be rooted, so i am really confused. What should I do know
I'm having this same problem, and unfortunately, when I start the phone on fastboot, I can not access the recovery mode in order to upload a factory image of nexus 5.
I used the new tool available her for quick flash, and now, I don't have a phone.
First, don't panic. Your phone is still very easy to recover. Unfortunately I can't get you a complete walkthrough here (for now at least), so I'll give you the main idea and you'll have to do your homework (as maybe you should have done before).
1. You need to get fastboot working on your computer. It's included in the Android sdk package, but there might be some easier way to get it. Google it. You might need drivers for your pc too. Google it as well.
2. Then you need to get into fastboot mode on your phone. To do it, hold down power button AND volume down button until it gets into fastboot mode. You will see an android on his back with the cover open. At this point, connect your phone to your pc, open a terminal on your pc and type "fastboot devices" without the quotes "". It should find your phone if fastboot is working. If it doesn't work go back to step 1.
3. Download TWRP recovery on your pc and place the img file in the same folder as your fastboot executable (not mandatory but easier). It can be found here https://dl.twrp.me/hammerhead/
4. Always in fastboot mode, type "fastboot flash recovery twrp-2.8.7.1-hammerhead.img" assuming you downloaded that file, which you should have by the way. It should install fine. If you haven't placed the file in the same directory as your fastboot executable, you will need to provide the path to your img file as well.
5. Then use the volume rocker to switch between modes and choose reboot recovery.
6. You should now be in TWRP recovery. At this point, download a custom kernel (anyone found on xda for hammerhead should do) and push it to your phone. It should be fairly simple with TWRP. Then flash your new kernel using install. It should help you get your phone booting normally. Alternatively, you can download a custom ROM like cm12.1 and flash it altogether. It will install everything needed for your phone to boot up too. Beware if flashing a ROM though, I strongly advice you to do a factory reset before flashing it. You will find that option in the wipe menu.
Hope it helps, let me know if you need further assistance.
Yesterday, I have tried everything to have my computer to recognize the "fastboot" command, and I installed like 2 or 3 different programs for that. With my old Windows 7, I have been able to push a flashed image to fix this issue, using the fastboot command, but with Windows 10, it's always telling me it's not a valid command. I'll keep trying it, otherwise, i'll have to "resurrect" my old Windows XP computer.
Also, I noticed now that, while trying to install the fastboot, as per some files that I could download, but no file has been copied into my computer, not even if I run it as admin.
fixed. but no RECOVERY mode options....
Hi Guys,
Thank you very much for the help, I have finally recovered the phone and running android 6.0 MRA58N but it is not rooted. Now if you don't mind could you teach me how to root because i have checked lots of videos and tuts but none worked for me...
IMPORTANT:
when i am in recovery mode why cannot I access options even when i press volume up + power button and release them at the same time...????
Thanks in advance.
Just flash a custom recovery via fastboot. Just make sure your bootloader is unlocked. Can't link though.
hi guys i have used nexus 5 mobile with cyanogenmod 14.1 .It worked properly in 1 year. after that suddenly switched off and it not properly boot up .i try to switch on my mobile , first it show google with unlock logo properly and when it show cyanogenmod logo it stuck and again show google with unlock logo....i try recovery mode to wipe and flash the same rom ....the process is interrupt at middle stage and again show the google..i try lots of time . after few try that process finished completely without interrupt. then use my mobile 1 day same as i used first time root. after that same problem occur on my mobile ..so help me guys
@[email protected], possible power button problem?