Related
Using a viewsonic G Tablet, I had initially loaded the clockwork mod. was working fine. Flashed a few ROMs over the last week. Currently running Cyanogen Mod7 Accidentally wanted to see what the ROM Manager app was about. Went and flashed the Clockword mod. Since then, I'm not able to go back into Clockwork mod. Everytime I try to reboot using the Power and Vol + button, it boots back into CyanogenMod ROM. Has a message related to MRC Erase after it says it detected REcovery Key pressed. I want to go back to using Clockworkmod so that I can flash another ROM. Now my computer doesn't even recognize the g tablet as an external storage so can't even access root. What do I need to do to get back my Clockworkmod to work again and how do I get back to my computer to recognize the g tablet. Appreciate the help. All feedback is welcome.
Sounds like you've reverted to stock recovery. Reinstall ClockworkMod. First part of this thread: http://forum.xda-developers.com/showthread.php?t=865245
Before you do, you might want to check the developers thread for your ROM to make sure there aren't any caveats.
K J Rad said:
Sounds like you've reverted to stock recovery. Reinstall ClockworkMod. First part of this thread: http://forum.xda-developers.com/showthread.php?t=865245
Before you do, you might want to check the developers thread for your ROM to make sure there aren't any caveats.
Click to expand...
Click to collapse
But to install Clockworkmod, I need my computer to recognize the g tab as a external storage device. Something it's not doing. So can't go back to it. CAn I download the clockworkmod on the external SD Card on the computer, put it back in the gtab and let it self recognize it and install clockworkmod? Will that work? And why isn't my computer recognizing my gtab as an external storage device. Is there a way I can mount USB storage without going into clockworkmod?
Have you tried using Rom Manager to flash clockworkmod again? Or used it to flash and older version of Clockworkmod?
If you read the thread it shows there is a method to load CWM from MicroSD card (external). Once you have CWM back on then you can mount internal through it.
I dont know why Your tablet isn't mounting. Mine mounts automatically but my configuration is very different from yours. Perhaps you could check the ROM developers thread for more information.
Double submission. Please ignore/delete.
tcrews said:
Have you tried using Rom Manager to flash clockworkmod again? Or used it to flash and older version of Clockworkmod?
Click to expand...
Click to collapse
I used the ROM Manger to flash clockworkmod. That's what messed up the clockworkmod in the first place. Trying to see how to fix that. May need to get rid of the ROM Manager.
Flash the alternate recovery in Rom Manager and then delete Rom Manager
thebadfrog said:
Flash the alternate recovery in Rom Manager and then delete Rom Manager
Click to expand...
Click to collapse
I can't even flash clockwork mod from the ROM manager. Keeps giving me a message "An Error occured while attempting to run privileged commands". Using clockworkmod was just so much easier. Just touching one button the ROM Manager has caused me headaches. I need some serious help.
Then run nvflash from the development froum
thebadfrog said:
Then run nvflash from the development froum
Click to expand...
Click to collapse
Tried to run NVFlash, but I get through ok till the point where I have to run the .bat script. What am I doing wrong? Where do I run it? Do I just double click? Because it reports an error when I do that. I"m using Windows 7 64 bit on a HP touchsmart. able to download the usb driver. recognizes the APX. but can't run the last command. Am I just supposed to get a black screen when I boot using Power and vol - button? Cos nothing else shows up on it. Appreciate the help.
I am also Unable to get into CWM after doing an update in Rom Manager. Have tried a bunch of things. still no luck. Power>Reboot>Recovery and RomManager just get me the Deterct Recovery Command - Erasing MCS then straight into CM7
Power/+ gets me Recovery Key Detected but then boots right into CM7.
Please let me know how you make out.
Childpsy said:
Tried to run NVFlash, but I get through ok till the point where I have to run the .bat script. What am I doing wrong? Where do I run it? Do I just double click? Because it reports an error when I do that. I"m using Windows 7 64 bit on a HP touchsmart. able to download the usb driver. recognizes the APX. but can't run the last command. Am I just supposed to get a black screen when I boot using Power and vol - button? Cos nothing else shows up on it. Appreciate the help.
Click to expand...
Click to collapse
When the tablet is put into APX mode the screen will go black. I don't use windows so I can't be much help with the rest but it would help if you told us what the error is when you try to start the file.
Thunter75 said:
I am also Unable to get into CWM after doing an update in Rom Manager. Have tried a bunch of things. still no luck. Power>Reboot>Recovery and RomManager just get me the Deterct Recovery Command - Erasing MCS then straight into CM7
Power/+ gets me Recovery Key Detected but then boots right into CM7.
Please let me know how you make out.
Click to expand...
Click to collapse
That's exactly what is happening. Was wanting to load the TNT lite or Vegan to try out a different rom and now I can't do it.
K J Rad said:
When the tablet is put into APX mode the screen will go black. I don't use windows so I can't be much help with the rest but it would help if you told us what the error is when you try to start the file.
Click to expand...
Click to collapse
I will post the error message once I try it again at home. I do get the black screen. Thanks for your help.
Error message when trying NVFlash
K J Rad said:
When the tablet is put into APX mode the screen will go black. I don't use windows so I can't be much help with the rest but it would help if you told us what the error is when you try to start the file.
Click to expand...
Click to collapse
The Message that shows up on the command window
"nvflash.exe" ---bct gtablet.bct ---setbct ---bl bootloader.bin ---configfile gtablet.cfg --create --go
NVFlash Started
NVFlash configuration file error: file not found
Please enter to continue
That's exactly what I see when I double click the nvflash_gtablet Windows batch file
Alright so I tried a few things and it seems like I needed to copy the files rather than the folder to the NVFlash folder. So I did that. NVFlash was successful but now it's stuck in boot loop. Now what do I do?
Ok... if you read any amount of the flashing process threads you would know using rom manager is a quote"****ing bad idea"end quote. Nvflash and a repartition using cwm is your only hope.
Flash cwm as an update.zip and repartition
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
ok so ive had my tf101 rooted since i got the thing over a year and a half ago, i was running the megatron rom which was cm9 based and everything was good. today i tried to flash Eos4 and i got F%$ked out the a$$. so i did my standard procedure which was put the rom and gapps package on my device and then i wiped everything (after making a nandroid) and flash the rom along with its gapps. then i went to reboot it then i got shot back into recovery...so i was like wtf. i then found a way where if i hold the power and volume down for about 10 seconds i could cold boot android and once booted fix this problem with my recovery. unfortunately when i go to boot into android my device just bootloops on the boot animation ( ive left for about ten mins just to make sure) then i was like oh well ill just restore my nandroid, but for some reason clockwork mod touch wont let me use my microsd card, and its also not letting me restore from the backup i made earlier, it says files not found. i tried to connect it to my pc so i could just factory reflash it but unfortunately it will not be picked up by my pc through adb or apx.
so here is my main issue,
i just need to boot into android one time successfully so i can change the location of some ROM files and fix this stupid recovery bull****.
or if i could some how factory reset the tablet completely then that would be fine too
or or i could flash a different recovery that actually worked (currently on CWM 5.8.3.4 installed from rom manager which i realize now to be a huge mistake)
and i've tried ever tool on this forum as well and nothing works because it cannot pick up my device.
*** one other side note i am running windows 8 pro 32bit through Vmware (if this can be problematic)
thanks for any help in advance
To fix this, you will need to get your tablet recognized by your computer via ADB (in recovery) or APX mode.
You could have a bad cable, or it could be the VM causing the detection issues.
Is there a way you can connect it to a computer running Windows natively?
Does your computer make the new hardware sound when connecting?
Once you get it detected via one method or the other, here are my suggestions:
APX - Use the Naked Driver 0.72 and replace whatever driver is being used. Then use EasyFlasher to install TWRP 2.2.1.4 (it blows CWM away, and can read internal AND external memory)
ADB - use the Naked Driver 0.72 and replace whatever driver is being used. Then download the TWRP 2.3.2.3 blob from the TWRP project: http://techerrata.com/browse/twrp2/tf101
Call the downloaded file TWRP.blob.
Then run the following from your computer via ADB:
Code:
adb push TWRP.blob /sdcard/
adb shell
su
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
reboot
Make sure it is a normal reboot to complete the recovery. Then reboot to recovery and you should be able to see the external card (so long as it is formatted for FAT32).
Thanks for the quick response and it probably is because I am using vmware... Unfortunately I don't have access to a windows machine right now. But I will definitely try to find one
Sent from my SAMSUNG-SGH-I747 using xda premium
Ok so now it looks like this... All i did was flash some random ass jb rom I found in my cwm folder... It has been like this for about 15 mins
Sent from my SAMSUNG-SGH-I747 using xda premium
** edit I'm assuming it got stuck boot the apps because now a my directories seem F&#cked up too... It now goes sdcard/0/0/0/(everthing else)
That's because your recovery is not compatible with 4.2.1. TWRP recovery 2.3.2.3 or 2.3.3.x should be fine as federuco said, to fix the sdcard/0/0/... issue.
For the stuck at apps thing, usually it's because you didn't wipe everything when changing rom. Make sure to do a full reset, wipe cache dalvik and system.
Lethe6 said:
That's because your recovery is not compatible with 4.2.1. TWRP recovery 2.3.2.3 or 2.3.3.x should be fine as federuco said, to fix the sdcard/0/0/... issue.
For the stuck at apps thing, usually it's because you didn't wipe everything when changing rom. Make sure to do a full reset, wipe cache dalvik and system.
Click to expand...
Click to collapse
But my problem is I can't flash another recovery... I can't access the memory on my micro sd card... So like idk what to do
Sent from my SAMSUNG-SGH-I747 using xda premium
What happens if you reboot it after it is at the starting apps screen?
If you can get into the OS, install GooManager and install TWRP.
frederuco said:
What happens if you reboot it after it is at the starting apps screen?
If you can get into the OS, install GooManager and install TWRP.
Click to expand...
Click to collapse
I can't get into the os that's the problem... I just clean installed Windows via boot camp on my mac... Gunna try a few tools now... Hopefully I can get it back to stock... I'll update in a little bit
Sent from my SAMSUNG-SGH-I747 using xda premium
Ok so my computer can sort of detect it... I installed the drivers via brks root kit but when I plug it in in apx mode it says unknown device... Tried all my programs and they all failed...
Sent from my SAMSUNG-SGH-I747 using xda premium
Ok so I've tried to to reinstall the drivers... Tried to flash everything in apx and adb but it's not being properly detected By the PC... So I have no idea what to do at this point... If I could somehow either boot into android or flash TWRP
Sent from my SAMSUNG-SGH-I747 using xda premium
Use the Naked Drivers.
Let me find the link to the thread....
Here you go: http://forum.xda-developers.com/showthread.php?t=1514942
Grab the driver pack in the first thread, update the device using the APX driver when in APX mode.
Then you should be good to go. I have used EasyFlasher via APX with great success.
frederuco said:
Use the Naked Drivers.
Let me find the link to the thread....
Here you go: http://forum.xda-developers.com/showthread.php?t=1514942
Grab the driver pack in the first thread, update the device using the APX driver when in APX mode.
Then you should be good to go. I have used EasyFlasher via APX with great success.
Click to expand...
Click to collapse
Not to sound like a complete noob at this point but idk how to install these naked drivers
Sent from my SAMSUNG-SGH-I747 using xda premium
I think I installed the drivers right but idk can someone please like teamviwer or Google + hangout with me
Sent from my SAMSUNG-SGH-I747 using xda premium
Put your device in APX mode. To do so, make sure it's completely powered off (hold the power button 10 seconds), then hold down volume up + power for about 5 seconds. Do that while it's connected through USB. The screen will remain black so you won't see anything on the device, but you will hear a new device found in windows. Go in your device manager and look for either "unkown device" or "NVIDIA boot-recovery driver for mobile devices". If you see the nvidia one, right click and delete it; it should be come unknown. Right click the unknown device, install driver... navigate to where you extracted the naked drivers, and install.
Then use easyflasher.
Lethe6 said:
Put your device in APX mode. To do so, make sure it's completely powered off (hold the power button 10 seconds), then hold down volume up + power for about 5 seconds. Do that while it's connected through USB. The screen will remain black so you won't see anything on the device, but you will hear a new device found in windows. Go in your device manager and look for either "unkown device" or "NVIDIA boot-recovery driver for mobile devices". If you see the nvidia one, right click and delete it; it should be come unknown. Right click the unknown device, install driver... navigate to where you extracted the naked drivers, and install.
Then use easyflasher.
Click to expand...
Click to collapse
Not working... :/ I swear it's not me
Sent from my SAMSUNG-SGH-I747 using xda premium
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've tried installing the TWRP throught Goo Manager, tried disabling DMClient and cleaning the application cache through android's application manager, but when I power down then, press VOL-DOWN + POWER I find myself only 2 opstion, system wipe and android linux cold boot. It's like if I'm in the official Asus TF101 Recovery mode.
I've tried EasyFlasher way, but I don't know how to install the universal naked drivers.. So I tried entering APX mode with the normal windows driver and hitting the flash button on the EasyFlasher for TWRP. But still it won't boot to recover, just the old 2 options screen.
I've tried also the console way, (dd=if whatever...) and when I reboot the tablet it shows a blue loading bar under the EePad logo. But still no recovery at VOL+DOWN + POWER, just the freaking wipe data or cold boot scrren.
I've tried ROM Manager from google play and it says that I have both ClockworkMode and TWRP already installed on the tablet..
What can I do to install a recovery so I can change the ROM installed? The device is already rooted.
Do you have a CWM bootloop where it always boots to CWM recovery?
frederuco said:
Do you have a CWM bootloop where it always boots to CWM recovery?
Click to expand...
Click to collapse
No Sir. I can't boot into recovery.
Ok, Did GooManager ask for root permissions when trying to install the OpenRecovery script?
Also, here is an EasyFlasher tutorial, including how to update the naked drivers: http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html
frederuco said:
Ok, Did GooManager ask for root permissions when trying to install the OpenRecovery script?
Also, here is an EasyFlasher tutorial, including how to update the naked drivers:
Click to expand...
Click to collapse
Yes it asked for root permission when I clicked to install OpenRecovery Script. I just saw your post in another forum right before you post your reply and realized that my ATX driver appears with an exclamation on the device manager, this must be why the EasyFlasher is not working... I must install the naked drivers
If you cannot get the naked drivers to install, it could be an issue with your USB cable. I had my USB cable stop working for data (MTP/PTP/APX/ADB) however it still works to charge using the Asus wall wart. New cable fixed it up straight away.
frederuco said:
If you cannot get the naked drivers to install, it could be an issue with your USB cable. I had my USB cable stop working for data (MTP/PTP/APX/ADB) however it still works to charge using the Asus wall wart. New cable fixed it up straight away.
Click to expand...
Click to collapse
Hey man, do you know how can I discover the SBK from my TF101? My serial number is just... numbers.. no B70... no letters...
Am I looking it in the right place? (Android general configs -> about -> status -> serial number )
It is the sticker by the charging port if you didnt remove it or let it fall off. It is also on the original box if you have that.
I followed the procedure you described in your Guide, turns out my TF101 was SBK2.... It successfully flashed the TWRP and displayed that command prompt message. The naked driver was the key to it. Thank you awesome friend! :laugh::laugh: