Related
Posted this issue in the [RECOVERY][NONTOUCH][JB] ClockWorkMod Recovery v6.0.1.4 thread. (See quotes.) No need to spam that thread further, so i'll move it here :fingers-crossed:
Failed to flash CWM-touch via fastboot. Tried to reboot and now I'm stuck on boot screen. I can't boot into recovery,only fastboot.
Tried to re-flash official cwm-recovery, but it stopped right after the progress bar came up..
Click to expand...
Click to collapse
Found out i can also access recovery mode (CWM 6.0.1.3) via the 'wipe data' option.
I have tried to restore backup from recovery, and re-flash rom, but when rebooting it stops at ASUS (Inspiring Innovation...) boot screen.
Click to expand...
Click to collapse
I managed to flash the 6.0.1.4 CWM recovery zip-file. Then i flashed the .30 update with no errors.
I'm still stucked at the bootscreen.
Click to expand...
Click to collapse
Installed new ASUS firmware (10.4.4.16) from CWM recovery, everything seemed fine while flashing.
Stopped at boot screen...
Click to expand...
Click to collapse
So, no matter what i do it won't boot.
I have the nvflash files stored.
Can someone please point me in the right direction?
Just commenting to say that I am having the same problem. In fact this problem has got me so stumped I actually decided to register instead of lurk around hoping to find the answer. My problem may be slightly different however, while apparently stuck at the boot screen, my Transformer is actually entering fastboot mode directly from boot. Finally, I will add I place the blame on myself because I didn't read the original thread to see that the 6.0.1.4 recovery is for JB systems.
Well, something similar happened to me. Didn't read enough and installed CWM 6.0.1.3, try to do a factory reset through the wipe data in fastboot, and now my tablet only boots into CWM 6.0.1.3 which doesn't even work - Vol+ and Vol- buttons don't help me move through the menu.
If you have any ideas please let me know - and no, I don't have a nvflash backup, only a normal CWM one which I don't know how to restore :|
I wanted to post that I finally got my tf700 working. I don't know which steps are necessary but I'm going to post all I did.
1. Download latest jb build from ASUS
2. From Recovery wipe system data and cache
3. From Recovery flash the jb rom US_epad-user-10.4.4.16.zip
4. Reboot into fastboot
5. Download stock jb kernel from http://forum.xda-developers.com/showthread.php?t=1919961
6. Extract blob file from zip
7. Run this command
Code:
fastboot -i 0x0b05 flash boot blob
8. System rebooted automatically and said it recognized the signature and flashed the kernel. At this point the boot screen show "Device is unlocked" again. And holding down power and volume let me get to recovery directly
9. From Recovery flash the jb rom US_epad-user-10.4.4.16.zip (I had to do this step again)
10. Reboot system and it booted into jb
chronoquestion said:
I wanted to post that I finally got my tf700 working. I don't know which steps are necessary but I'm going to post all I did.
1. Download latest jb build from ASUS
2. From Recovery wipe system data and cache
3. From Recovery flash the jb rom US_epad-user-10.4.4.16.zip
4. Reboot into fastboot
5. Download stock jb kernel from http://forum.xda-developers.com/showthread.php?t=1919961
6. Extract blob file from zip
7. Run this command
Code:
fastboot -i 0x0b05 flash boot blob
8. System rebooted automatically and said it recognized the signature and flashed the kernel. At this point the boot screen show "Device is unlocked" again. And holding down power and volume let me get to recovery directly
9. From Recovery flash the jb rom US_epad-user-10.4.4.16.zip (I had to do this step again)
10. Reboot system and it booted into jb
Click to expand...
Click to collapse
my tab is stuck too. Still locked, and I only have stock recovery. I tried the soft brick fix in the "All in one guide". Didn't work. Any help please?
redheadplantguy said:
my tab is stuck too. Still locked, and I only have stock recovery. I tried the soft brick fix in the "All in one guide". Didn't work. Any help please?
Click to expand...
Click to collapse
Give us some more info about your setup, what version you're on (.26, .30, JB), can you access stock recovery? How did you try to recover?
chronoquestion said:
Just commenting to say that I am having the same problem. In fact this problem has got me so stumped I actually decided to register instead of lurk around hoping to find the answer. My problem may be slightly different however, while apparently stuck at the boot screen, my Transformer is actually entering fastboot mode directly from boot. Finally, I will add I place the blame on myself because I didn't read the original thread to see that the 6.0.1.4 recovery is for JB systems.
Click to expand...
Click to collapse
Perhaps you could try to fastboot flash the TWRP 2.2.2.2 recovery for your Infinity (either 32GB or 64GB model). I'm pretty sure it says it can be used with ICS and JB bootloaders.
---------- Post added at 03:47 PM ---------- Previous post was at 03:41 PM ----------
chronoquestion said:
I wanted to post that I finally got my tf700 working. I don't know which steps are necessary but I'm going to post all I did.
1. Download latest jb build from ASUS
2. From Recovery wipe system data and cache
3. From Recovery flash the jb rom US_epad-user-10.4.4.16.zip
4. Reboot into fastboot
5. Download stock jb kernel from http://forum.xda-developers.com/showthread.php?t=1919961
6. Extract blob file from zip
7. Run this command
Code:
fastboot -i 0x0b05 flash boot blob
8. System rebooted automatically and said it recognized the signature and flashed the kernel. At this point the boot screen show "Device is unlocked" again. And holding down power and volume let me get to recovery directly
9. From Recovery flash the jb rom US_epad-user-10.4.4.16.zip (I had to do this step again)
10. Reboot system and it booted into jb
Click to expand...
Click to collapse
Or at the last step, instead of reflashing the ASUS JB update, you could flash the CleanROM v1.3 and you will have rooted, stock-based JellyBean with everything working!
okantomi said:
Perhaps you could try to fastboot flash the TWRP 2.2.2.2 recovery for your Infinity (either 32GB or 64GB model). I'm pretty sure it says it can be used with ICS and JB bootloaders.
---------- Post added at 03:47 PM ---------- Previous post was at 03:41 PM ----------
Or at the last step, instead of reflashing the ASUS JB update, you could flash the CleanROM v1.3 and you will have rooted, stock-based JellyBean with everything working!
Click to expand...
Click to collapse
I will add that prior to getting it working I tried flashing all the available recoveries trying to get my tablet working again. In the end it seems that the important steps to getting my tablet working were flashing stock jelly bean and then the stock kernel separately. Once I had done those 2 steps probably could have flashed any available ROM. Fortunately at this point I'm pretty good at flashing recoveries through fastboot so I have no doubt I'll be able to get custom ROM working again.
First off I am sorry for posting this, however I DID use the search tool. I recently got a USA spec Wifi only Xoom. It came with 4.1.1 preinstalled. I have sucessfully unlocked the bootloader.
My problem is this. I cannot gain root or even get CWM installed. I have tried oneclick, i have tried cmd prompt. I have followed every guide I can find to a "T". Is there something missing, is it an issue with Jellybean being preinstalled?
Use http://forum.xda-developers.com/showthread.php?t=1468298 to get CWM installed (and when you reboot from fastboot flashing the recovery image, and this is very important, DO NOT LET IT FULLY REBOOT INTO THE OS. You have to get into recovery in the next boot or the OS will just overwrite it with the stock recovery and you will just have to go back into fastboot and flash the recovery again.
http://forum.xda-developers.com/showpost.php?p=30464067&postcount=408 has the root once you get CWM installed.
airesch said:
Use http://forum.xda-developers.com/showthread.php?t=1468298 to get CWM installed (and when you reboot from fastboot flashing the recovery image, and this is very important, DO NOT LET IT FULLY REBOOT INTO THE OS. You have to get into recovery in the next boot or the OS will just overwrite it with the stock recovery and you will just have to go back into fastboot and flash the recovery again.
http://forum.xda-developers.com/showpost.php?p=30464067&postcount=408 has the root once you get CWM installed.
Click to expand...
Click to collapse
Thanks for the reply, however this is one of the utilities I have tried,..
Here is a bit more info.
I am running windows 7 64bit if it makes a difference. Whenever I get the device into fastboot and try to flash anything, it just hangs at the original fastboot screen. I have let it sit there from 3 hours and eventually I have to reboot it. The Lord AIO Tool you linked just gives me and error message that the device is not a 2.2/2.3 device. If I were at home I would take a screenshot.
Could my bootloader be corrupt? The device still boots up and runs jellybean fine, but I am not loving the stock experience thus far...
Thanks again for the links!
Actually sounds like your drivers aren't right. I will look them up and link them when I get home
Try installing the driver from http://developer.motorola.com/tools/usb_drivers/, rebooting your pc, and try fastboot again. If that still doesn't work, then there may be something wrong with your pc setup OR your Xoom, not sure at that point.
Sent from my SPH-D710 using xda premium
Thanks a million, I am going to try it fresh on my pc at work. Thanks!
That did the trick THANKS A BUNCH!!!!!
Hellooooooooooooooooooooooooooooooooo!!!
this is my first thread in this forum, mi name is Nicolas and i ve a very big problem with my new tablet.
I was trying to install the new Jelly Bean (OS_Acer_RV09RC08.WW.GEN1_A41J_A) and everything was OK
I unlocked the bootloader .......and....
I try to root and just bricked....
Everytime i turn on the tablet i can see the "Acer logo" and the line: Bootloader Version JB-653b3d3 (Unlock Mode)
I cant get into the recovery mode.....
Sorry for my bad english....i need your help ppl!!!!
Thanks for ur time.
Nicolas.
May you can get into Fastboot mode and reflash the recovery.
Give it a try =)
Do you have a androids of your original ROM?
I did the exact same thing just yesterday...
If you have a JB image to work from, get it in fastboot mode and look at the thread on CWM Recovery 6.0.1.5...
Sent from my A700 using xda premium
thks for the replies.....
i downloaded the stock rom from the Acer web page
i tried with:
"adb reboot-bootloader" and NOTHING.....i ve the line: <waiting for the device> ....and ....5 min later nothing.
then:
tried to get the fastboot mode (vol + & PWR) and the tablet just get the same boot = nothing.
:crying:
freejack84 said:
thks for the replies.....
i downloaded the stock rom from the Acer web page
i tried with:
"adb reboot-bootloader" and NOTHING.....i ve the line: <waiting for the device> ....and ....5 min later nothing.
then:
tried to get the fastboot mode (vol + & PWR) and the tablet just get the same boot = nothing.
:crying:
Click to expand...
Click to collapse
To get into fastboot mode, it's the following combination;
- Press [vol-] + [power]
- As soon as the tablet vibrates, let go [power] then cycle your rotation lock button left and right till you see the the text start to appear.
Unless you;re going to try and fastboot a system image setup or recovery image or another boot.img, not sure what you wish to accomplish.
I would guess you would be better off installing maybe the GB full version JellyBean update.
Also, I understand there,s a a700 ICS service rom out there somewhere. That might help you also.
But these are just guesses at this point.
What would help, is to know exactly what you did to get yourself into this situation. Like What root procedure from what post? If you tried one of the ICS Boot.image flashes, when you had JB updated, well, no wonder it borked up. If that's the case, it's simple just to fastboot a JB Boot.img back in.
So which thread did you get the root procedure from EXACTLY?
One more thing, this thread belongs in Q&A Forum, so I put in a request to have it moved.
MD
Moscow Desire said:
To get into fastboot mode, it's the following combination;
- Press [vol-] + [power]
- As soon as the tablet vibrates, let go [power] then cycle your rotation lock button left and right till you see the the text start to appear.
Unless you;re going to try and fastboot a system image setup or recovery image or another boot.img, not sure what you wish to accomplish.
I would guess you would be better off installing maybe the GB full version JellyBean update.
Also, I understand there,s a a700 ICS service rom out there somewhere. That might help you also.
But these are just guesses at this point.
What would help, is to know exactly what you did to get yourself into this situation. Like What root procedure from what post? If you tried one of the ICS Boot.image flashes, when you had JB updated, well, no wonder it borked up. If that's the case, it's simple just to fastboot a JB Boot.img back in.
So which thread did you get the root procedure from EXACTLY?
One more thing, this thread belongs in Q&A Forum, so I put in a request to have it moved.
MD
Click to expand...
Click to collapse
Thks MD for ur instant reply.
Sorry for dont put my thread into the Q&A Forum. It was a mistake. Sorry again
My situation is: "like i remember" i tried to make the root with the "flash-ICS-patchedBoot.bat".....i know that BAT is for ICS and not for JB but i take that mistake doing the thing really fast. :angel:
Ok...i need them to get the fastboot with the JB Boot.img like you said.
The JB Boot.img is into the Rom??? because i saw the boot.img into the JB update.zip
Can u tell me the command to get that flash? Is "fastboot flash boot boot.img"?
Thks for ur patience
freejack84 said:
Thks MD for ur instant reply.
Sorry for dont put my thread into the Q&A Forum. It was a mistake. Sorry again
My situation is: "like i remember" i tried to make the root with the "flash-ICS-patchedBoot.bat".....i know that BAT is for ICS and not for JB but i take that mistake doing the thing really fast. :angel:
Ok...i need them to get the fastboot with the JB Boot.img like you said.
The JB Boot.img is into the Rom??? because i saw the boot.img into the JB update.zip
Can u tell me the command to get that flash? Is "fastboot flash boot boot.img"?
Thks for ur patience
Click to expand...
Click to collapse
It's no problem.
So you fastbooted an ICS boot.img on a JB rom
So, you need to see if you can manually get it into fastboot mode with the procedure I pointed out above (note it will probably wipe your user data, but who cares)
If you get it in fastboot mode, verify via windows device manager, then just put a JB Boot image in there. I have a little package in my Boot.image thread Full /System RW-Root. Don't use the boot mage in it, as it's for a 701. Just copy your JB boot.image in there and fastboot it. You have the correct command.
Verboth has a new rom, that contains an unsecure boot.img for the 700 JB. You can use that one also. It's what you were trying to do originally, just with a wrong image (ICS)
The reason ADB doesn't see it, is because the system isn't running. The newer CWM recoveries should have adb enabled through CWM, but I don't think you put that in yet.
Hopefully you'll get it fastbooted.
MD
Moscow Desire said:
It's no problem.
So you fastbooted an ICS boot.img on a JB rom
So, you need to see if you can manually get it into fastboot mode with the procedure I pointed out above (note it will probably wipe your user data, but who cares)
If you get it in fastboot mode, verify via windows device manager, then just put a JB Boot image in there. I have a little package in my Boot.image thread Full /System RW-Root. Don't use the boot mage in it, as it's for a 701. Just copy your JB boot.image in there and fastboot it. You have the correct command.
Verboth has a new rom, that contains an unsecure boot.img for the 700 JB. You can use that one also. It's what you were trying to do originally, just with a wrong image (ICS)
The reason ADB doesn't see it, is because the system isn't running. The newer CWM recoveries should have adb enabled through CWM, but I don't think you put that in yet.
Hopefully you'll get it fastbooted.
MD
Click to expand...
Click to collapse
Okay, so since I just did this, I'm going to try and give you a "how to" on how I fixed it...
MD and pawitp both are the authorities on this, but I think this will help and I a, sure they will correct me where I go wrong.
First, use the manual process for getting your A700 in fastboot.. power button + down vol, wait for the first buzz then release only the power button, wait for the second buzz then press the up volume button. Your tab should now be in fastboot mode.
Connect it to your computer.
Get a copy of the proper recovery image "recovery-a700-6015" and the following ROM ( http://forum.xda-developers.com/showthread.php?t=1952124) and save them to a directory where you can find it easily.
Pull the SD card from your tab and put the ROM from above in the base directory and put it back in your tab.
From the c prompt on your computer use the following fastboot command:
Fastboot devices
----#make sure that the computer sees your a700
Fastboot boot <save directory>recovery-a700-6015.img
----#your tab will reboot into CMR Recovery
In recovery format system, data, cache, dalvik
Still in recovery install the ROM from your external SD card.
The Aroma Installer will guide you through it, but make sure you tell it to install the new firmware.
Reboot.
You should be on the stock rooted ACER Great Britain release.
From there you can download and install CM10 (which is what I did), or any other ROM you would like.
Sent from my A700 using xda premium
well.......30 minutes with the tablet and:
I put the tablet in Recovery state with the last instructions.....but now i ve too much errors lines:
Important: all this error are "before" flash again the recovery
The recovery cant:
mount /cache/recovery/command
mount /cache/recovery/log
mount /cache/recovery/last_log
cant open cache/recovery/log
and.....
cant mount SDCARD, EXTERNALSD, SYSTEM, CACHE, etc etc...
when i try to flash again the recovery: <waiting the device> and nothing......i cant put the tablet in fastboot mode.
i have the same problem before. 無得整的, 要上acer換底版的
NEWS:
Finally i get the fastboot mode (Vol - & PWR and then CYCLE THE ROTATION LOCK). :good:
First: reflash the recovery and DONE
All the errors just gone.
Now.....install again the JB.....and DONE
My Acer go back to normally conditions. :victory:
Thks for ur support. :laugh:
freejack84 said:
NEWS:
Finally i get the fastboot mode (Vol - & PWR and then CYCLE THE ROTATION LOCK). :good:
First: reflash the recovery and DONE
All the errors just gone.
Now.....install again the JB.....and DONE
My Acer go back to normally conditions. :victory:
Thks for ur support. :laugh:
Click to expand...
Click to collapse
Uhmmmm.... didn't I state that the other day?
Glad you got it going Mate :good:
MD
thks ppl
freejack84 said:
NEWS:
Finally i get the fastboot mode (Vol - & PWR and then CYCLE THE ROTATION LOCK). :good:
:
Click to expand...
Click to collapse
I didnt have the same exact issue like the other users BUT this key combination to finally get back into fastboot during a hanging ACER logo bootup with a red failure msg at the corner was the LIFE SAFER!!!!!
VOL - (left button with two knobs) & PWR and then CYCLE THE ROTATION LOCK
tattoo this on your arms!!! :laugh:
LukeRG said:
I didnt have the same exact issue like the other users BUT this key combination to finally get back into fastboot during a hanging ACER logo bootup with a red failure msg at the corner was the LIFE SAFER!!!!!
VOL - (left button with two knobs) & PWR and then CYCLE THE ROTATION LOCK
tattoo this on your arms!!! :laugh:
Click to expand...
Click to collapse
LOL
pls step step explain ı recovery my tablet but ı want to back syock rom tablet internal storage not ready in pc ı cant see internal storage ı see only sc card camera dont workk how back to syock rom pls help..
thank's man
freejack84 said:
NEWS:
Finally i get the fastboot mode (Vol - & PWR and then CYCLE THE ROTATION LOCK). :good:
First: reflash the recovery and DONE
All the errors just gone.
Now.....install again the JB.....and DONE
My Acer go back to normally conditions. :victory:
Thks for ur support. :laugh:
Click to expand...
Click to collapse
Thank's... you just safe my problem today
u welcome .......
Hello everybody,
I think I have NOT exactly the same problem but very similar.
Let me explain how I got there:
I had JB bootloader and CM11 installed for long and working fine.
Last days I tried out the CM12.1 unofficial rom with successful installation.
I noticed that the camera focus was not working. Usually I never use the camera and was not sure if it worked before. So I went back to CM11 to look if it is rom dependent. In CM11 it still was not working and I went back to stock. The stock rom I found was Android 4.0.4 and I tried to make OTA update what showed me a “not allowed to your device” –error.
However, at this moment I was quite sure that the camera focus is a hardware defect and wanted to go on testing the new CM12.1. I installed it again from CWM recovery and it was not booting anymore.
The problem is, that the stock rom flashed an ICS bootloader which is not compatible anymore. I also cannot boot into recovery anymore but fastboot is working.
Power-On:
shows Bootloader Version ICS-MR1-a055314 (Unlock Mode) and nothing more
Power-On + Vol.Down:
Bootloader Version ICS-MR1-a055314 (Unlock Mode)
Erasing Cache before SD update…
SD update cnd: recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Then for just a second CWM is shown:
CWM-based Recovery v6.0.5.1
Finding update package
E:unknown volume for path [SDCARD:update.zip]
E:Can't mount SDCARD:update.zip
Installation aborted.
Rebooting...
Then it holds on Bootloader Version ICS-MR1-a055314 (Unlock Mode)
I could not find any button combination to boot something else.
What I tried and what did not make any changes:
Flashing the recovery.img again
Erase userdata, cache, system
Please help me to boot up recovery again and flash a JB bootloader and new rom.
Thanks and kind regards,
Gandlz
Well, in between I found a solution and can answer my own question now:
The trick is to flash the CWM Recovery not to the recovery partition but to the boot partition. (fastboot flash boot recovery.img)
After restarting the tablet it boots directly into CWM Recovery.
I found a newer stock rom with jelly bean android and installed it to come back to JB-Bootloader. Now I could install CM10.2 CM11 or CM12.1 again.
The stock rom is from a german forum:
android-hilfe.de/thema/a700-zurueck-aufs-deutsche-stock-rom-flashen-anleitung-imagefile.329590
By the way: I’m running CM10.2.1 and it is very much faster than CM11 or CM12.1. I don’t need the newer features and like the old design even more. And also the camera focus is working now, so it is definitely a software issue with newer CM versions.
Best regards,
Gandlz
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?
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..