Related
how to unroot and return to stock recovery
this is only until a better method arrives.
step 1-download the stock nandroid restore posted by TGA_Gunnman and follow the instructions he provides( http://forum.xda-developers.com/showthread.php?t=1048274) . this will get your phone back to stock, but you're still rooted and have Titanium Installed and Rom Manager Installed.
you'll also have back any bloatware\tmobile apps you may have deleted.
step 2
you'll need to have nvflash setup properly and the NVidia boot-recovery driver installed. good instructions can be found here http://android.modaco.com/content/l...lash-setup-instructions-drivers-links-active/
step 3- download the stock recovery from here http://mirror.dal.tdrevolution.net/ctso/g2x/part5.img
step 4- place the part5.img in your nvflash folder.
step 4a- download clockwork recovery test2-- http://mirror.dal.tdrevolution.net/ctso/g2x/nvflash-recovery.tgz .
in the folder download of cwm recovery test2, i took all the files except for test2.img and nvflash and put them in my nvflash folder.
step 5- power off your phone. take out the battery. unplug the usb cable from the phone,you can leave the other end plugged in to the pc.
hold down both volume buttons on the phone. while holding them down, plug the usb cable in to your phone. you should hear the windows device connected sound. that's good. you'll see nothing on the phone. you can let go of the volume buttons now.
step 6- hold shift and right click an empty area inside the nvflash folder. select "open command window here".
if you can't do that, cd to your nvflash folder.
now, copy and paste this into the command window...
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 part5.img
press enter. if it gets to "part5.img sent successfully", you are now back to stock recovery. unplug the phone and place the battery back in. holding vol.down and power will format\hard reset your phone now.
don't forget to uninstall titanium and rom manager.
step 8- use superoneclick to unroot your phone.
if anyone would like to elaborate\correct anything on here,please pm me and i'll edit the post. thanks
Did you test this method?
I'm trying it right now, I'll let you know the result.
absolutely, a few times. i would never post something i haven't thoroughly tested.
i forgot to add something to the instructions. in the folder download of cwm recovery test2, i took all the files except for test2.img and put them in the nvflash folder. my bad. try that if it doesn't work. going to edit op now.
crazythunder said:
absolutely, a few times. i would never post something i haven't thoroughly tested.
Click to expand...
Click to collapse
Off topic but have you been able to get adb to recognize your device while in recovery? Is it me or are the LG drivers funky?
jlevy73 said:
Off topic but have you been able to get adb to recognize your device while in recovery? Is it me or are the LG drivers funky?
Click to expand...
Click to collapse
I noticed the same thing today at work but I thought it was my crappy dell PC from work. will test
sstang2006 said:
I noticed the same thing today at work but I thought it was my crappy dell PC from work. will test
Click to expand...
Click to collapse
I think it's the crappy drivers.
jlevy73 said:
Off topic but have you been able to get adb to recognize your device while in recovery? Is it me or are the LG drivers funky?
Click to expand...
Click to collapse
i get ...
adb devices
list of devices
nothing,nada
OK, I get an error.
unknown command: _x8.bct
- I didn't do step 4a. ( is it necessary? lol )
crazythunder said:
i get ...
adb devices
list of devices
nothing,nada
Click to expand...
Click to collapse
Yep that's exactly what I'm getting.
sstang2006 said:
OK, I get an error.
unknown command: _x8.bct
- I didn't do step 4a. ( is it necessary? lol )
Click to expand...
Click to collapse
no space between emmc and _x8.bct
i did the same thing. copy and paste is buggy in command i think
you can try without 4a. that was a "just in case" addon.
adb shell gives an error as well
crazythunder said:
no space between emmc and _x8.bct
i did the same thing. copy and paste is buggy in command i think
you can try without 4a. that was a "just in case" addon.
Click to expand...
Click to collapse
thats what I thought but was scared to try
crazythunder said:
adb shell gives an error as well
Click to expand...
Click to collapse
While in recovery, correct?
jlevy73 said:
While in recovery, correct?
Click to expand...
Click to collapse
yes........
Nvflash started ..... (how long does it usually take?)
sstang2006 said:
Nvflash started ..... (how long does it usually take?)
Click to expand...
Click to collapse
about 20 seconds
you should see part5.img sent successfully
you'll want to see fastboot.bin sent successfully as well. that's why it's in my nvflash folder
crazythunder said:
about 20 seconds
you should see part5.img sent successfully
Click to expand...
Click to collapse
5 minutes and still nada... suggestions??
sstang2006 said:
5 minutes and still nada... suggestions??
Click to expand...
Click to collapse
step 4a
.................
@sstang2006
are you getting ready to do an exchange?
To sum everything up:
1. My rom didn't work so I decided to find a new one :good:
2. I read and understand that it's much easier using fastboot
3. I was flashing the official rom when the antivirus requested a reboot
4. I forgot the flashing, and just clicked on reboot :silly: :crying:
The screen remains black when I try to boot it up :crying:
The only sign of life is when I'm charging the light is lighting and "APX" is showing in the device manager on pc with a yellow triangle, I haven't understand what "APX" stand for yet so please explain
(My bootloader was unlocked and I flashed twrp 2.5.5 just before I did this)
Do you have any tips for me? Or is the device bricked and have to be sent for service?
Please help me :fingers-crossed:
Edit: This is wrong section I know, can anyone move it to the Q&A please?
Moved.
mathiash98 said:
To sum everything up:
1. My rom didn't work so I decided to find a new one :good:
2. I read and understand that it's much easier using fastboot
3. I was flashing the official rom when the antivirus requested a reboot
4. I forgot the flashing, and just clicked on reboot :silly: :crying:
The screen remains black when I try to boot it up :crying:
The only sign of life is when I'm charging the light is lighting and "APX" is showing in the device manager on pc with a yellow triangle, I haven't understand what "APX" stand for yet so please explain
(My bootloader was unlocked and I flashed twrp 2.5.5 just before I did this)
Do you have any tips for me? Or is the device bricked and have to be sent for service?
Please help me :fingers-crossed:
Edit: This is wrong section I know, can anyone move it to the Q&A please?
Click to expand...
Click to collapse
Apx is a method provided by the cpu manufacture for recovery. Due to the way asus has handled locking the unit apx is only available if nvflash is installed while on ICS (4.0).
Reset may be a good option for you. Power on unit. Hold volume down and insert a small paperclip to into into the reset hole. This may get you into the bootloader.
Reset: A small hole about 25mm or 1inch below the sdcard slot.
Note: If this fails you could do the same but hold volume up and hope.
Beyond this running the battery down has worked for some or remove the back cover and disconnect the battery. Leave it disconnected for thirty minutes, then reconnect.
Also see my signature for other methods to get into the bootloader. Don't bother with apx as it is useless for us.
We are looking for any change in the unit. With a change may come use of adb, fastboot, or recovery.
Try do each thing in turn and repeat this sequence twice more.
Thanks for the explanation and fir the tips! I'm going to try this
mathiash98 said:
Thanks for the explanation and fir the tips! I'm going to try this
Click to expand...
Click to collapse
Good Luck!
tobdaryl said:
Good Luck!
Click to expand...
Click to collapse
It doesn't seem that any of the following work, but I haven't tried the battery pull thing, because I see that it's a sticker over the cover that says that the warrenty is void if removed. If I send it for service will the guys know that I have unlocked it, and then void the warranty?
mathiash98 said:
It doesn't seem that any of the following work, but I haven't tried the battery pull thing, because I see that it's a sticker over the cover that says that the warrenty is void if removed. If I send it for service will the guys know that I have unlocked it, and then void the warranty?
Click to expand...
Click to collapse
I understand. If still in warranty I wouldn't remove it either.
I'm sorry that is all I have for your situation.
Lads, let me join your conversation. I've almost same problem, probably different root cause, but same summary:
1. Originally I downloaded JB 4.2 from support.asus.com source
2. Tablet got reflashed & worked as normal, but I lost roots which I had earlier, therefore I decided to get root privs again.
3. So, I went into TWRP web-site & downloaded openrecovery-twrp-2.5.0.0-tf300tg-JB.blob blob file & via ADB was able to flash TWRP 2.5 onto my TF300T, but...
4. ...somehow TWRP doesn't let me to mount neither system, not SD-card, nothing. And currently
5. I think I'm bricked (& my TF300T too). When I press power button - tablet switches on & gets straight into TWRP, where I've only option to power it down or reboot TWRP tells me "are you sure? No OS installed".
6. When I try to switch tablet into bootload (with volume -) writing "The Device is Unlocked" shortly blinks slightly brighter, kind of trying to get into bootloader, but gets into TWRP anyway.
Any help, please! I know how Donate button works!
P.S. Because I very new writer (but really old reader) of XDA - I can't incert outside links...
goldenval said:
Lads, let me join your conversation. I've almost same problem, probably different root cause, but same summary:
1. Originally I downloaded JB 4.2 from support.asus.com source
2. Tablet got reflashed & worked as normal, but I lost roots which I had earlier, therefore I decided to get root privs again.
3. So, I went into TWRP web-site & downloaded openrecovery-twrp-2.5.0.0-tf300tg-JB.blob blob file & via ADB was able to flash TWRP 2.5 onto my TF300T, but...
4. ...somehow TWRP doesn't let me to mount neither system, not SD-card, nothing. And currently
5. I think I'm bricked (& my TF300T too). When I press power button - tablet switches on & gets straight into TWRP, where I've only option to power it down or reboot TWRP tells me "are you sure? No OS installed".
6. When I try to switch tablet into bootload (with volume -) writing "The Device is Unlocked" shortly blinks slightly brighter, kind of trying to get into bootloader, but gets into TWRP anyway.
Any help, please! I know how Donate button works!
P.S. Because I very new writer (but really old reader) of XDA - I can't incert outside links...
Click to expand...
Click to collapse
Which tablet do you have? You show TF300T but using TF300TG twrp.
The bootloader changed again with 4.2 firmware and requires twrp especially for that version. I have been told the openrecovery-twrp-2.5.0.0-tf300t-4.2.blob does not work properly so you should have used openrecovery-twrp-2.4.4.0-tf300t-4.2.blob if you have a tf300t.
We need to break the cycle of going into twrp and only twrp.
Let's try to use twrp for that purpose. While in twrp select reboot while holding volume down.
If that fails to make a change while in twrp type adb reboot bootloader.
If that makes no change type fastboot -i 0x0B05 reboot-bootloader.
If there is still no change try the reset while holding volume down.
Reset: A small hole about 25mm or 1inch below the sdcard slot. Use a small paperclip to insert into the hole and press gently while holding volume down.
Dear Friend! :good: That what makes difference between you - old member & me - amatuer. Yes, I loaded ...TG version of TWRP onto my ..T tablet. Bad words aren't allowed in XDA forum, otherwise I'd call myself with proper name. Anyway,
I tried to reboot from TWRP, held volume - & had no success. It loaded into TWRP again.
Then tried to reboot with command adb reboot bootloader, as you mentioned - my Windows7 PC doesn't see tablet, showing Transformer with yellow ! sign. And I tried fastboot -i 0x0B05 reboot-bootloader command, ADB is saying <waiting for device> forever & nothing happens. so I stopped here so far, waiting for your advise...
We need to break the cycle of going into twrp and only twrp.
Let's try to use twrp for that purpose. While in twrp select reboot while holding volume down.
If that fails to make a change while in twrp type adb reboot bootloader.
If that makes no change type fastboot -i 0x0B05 reboot-bootloader.
If there is still no change try the reset while holding volume down.
Reset: A small hole about 25mm or 1inch below the sdcard slot. Use a small paperclip to insert into the hole and press gently while holding volume down.
No bad words needed. We all make mistakes. I them pointed out for future reference in case you were not aware.
First you need to get your drivers loaded for windows.
[GUIDE] How to install Universal Naked Drivers
Use that guide to get your drivers properly installed and retry the adb and fastboot commands.
goldenval said:
Dear Friend! :good: That what makes difference between you - old member & me - amatuer. Yes, I loaded ...TG version of TWRP onto my ..T tablet. Bad words aren't allowed in XDA forum, otherwise I'd call myself with proper name. Anyway,
I tried to reboot from TWRP, held volume - & had no success. It loaded into TWRP again.
Then tried to reboot with command adb reboot bootloader, as you mentioned - my Windows7 PC doesn't see tablet, showing Transformer with yellow ! sign. And I tried fastboot -i 0x0B05 reboot-bootloader command, ADB is saying <waiting for device> forever & nothing happens. so I stopped here so far, waiting for your advise...
We need to break the cycle of going into twrp and only twrp.
Let's try to use twrp for that purpose. While in twrp select reboot while holding volume down.
If that fails to make a change while in twrp type adb reboot bootloader.
If that makes no change type fastboot -i 0x0B05 reboot-bootloader.
If there is still no change try the reset while holding volume down.
Reset: A small hole about 25mm or 1inch below the sdcard slot. Use a small paperclip to insert into the hole and press gently while holding volume down.
Click to expand...
Click to collapse
Ok...
So, I bricked my tf300t. I ordered a new motherboard off ebay and replaced the bricked one. It works, but it was not factory reset and still has the owners info, etc. It is password protected. I don't know the pw. When I try to boot into the recovery console, I get a dead android. Going into the menu, I have an option to wipe or boot android. How do I get around this?
n3tm0nk said:
So, I bricked my tf300t. I ordered a new motherboard off ebay and replaced the bricked one. It works, but it was not factory reset and still has the owners info, etc. It is password protected. I don't know the pw. When I try to boot into the recovery console, I get a dead android. Going into the menu, I have an option to wipe or boot android. How do I get around this?
Click to expand...
Click to collapse
My suggestion is use stock recovery to replace the encrypted os (probably JB 4.2) with JB 4.1 (10.4.2.20). You can download here [INDEX]25 Apr 2013 - TF300T/TG WITH ALL ASUS ORIGINAL TOOLS-Firmwares-Kernels-Guides-. Look in firmware TF300T. Use the proper sku (ww, us, etc) for your country. Please give philos64 a thanks while there he spent much time creating that post, supporting the downloads, and updating.
Unzip the downloaded file once - rename to EP201_768_SDUPDATE.zip. Place the file on your internal sdcard if possible if not place on your micro sdcard. Boot into the recovery console and make the hungry android happy. This will probably take ten plus minutes.
Dear tobdaryl! Thanks very much for your advice, I had to dissapear for couple of days, so couldn't answer. I followed your link & had no success. When I power on TF300T & connect it to PC, it's being read as Transformer (see my 1st picture), unlike in the guide they are working with Asus Eee pad device (my 2nd picture), so when I'm trying to install drivers from un-zipped folder it says "...couldn't install drivers for your Transformer".
Looking for more help... (
tobdaryl said:
No bad words needed. We all make mistakes. I them pointed out for future reference in case you were not aware.
First you need to get your drivers loaded for windows.
[GUIDE] How to install Universal Naked Drivers
Use that guide to get your drivers properly installed and retry the adb and fastboot commands.
Click to expand...
Click to collapse
goldenval said:
Dear tobdaryl! Thanks very much for your advice, I had to dissapear for couple of days, so couldn't answer. I followed your link & had no success. When I power on TF300T & connect it to PC, it's being read as Transformer (see my 1st picture), unlike in the guide they are working with Asus Eee pad device (my 2nd picture), so when I'm trying to install drivers from un-zipped folder it says "...couldn't install drivers for your Transformer".
Looking for more help... (
Click to expand...
Click to collapse
Right click on the Transformer with the yellow symbol and point to your Universal Naked Drivers inf file. If one inf files fails to install then try the other.
tobdaryl said:
Right click on the Transformer with the yellow symbol and point to your Universal Naked Drivers inf file. If one inf files fails to install then try the other.
Click to expand...
Click to collapse
Tobdaryl, I couldn't find "Donate Me" button in your profile, so give me your paypal account for a little present please! :good: It worked!!! I installed correct driver from given guide, rebooted into bootloader, using ADB comand & got 3 icons: RCK, Android & Wipe Data. I tried Wipe Data, it said "can't mount something", don't remember now what. I rebooted again & clicked on Android & loaded into normal screen. Because of Asus became completely flat I put it on charge now. And after that I will have to come back to original task - to root my TF300T. While it's charging I downloaded Goo manager & tried to install TWRP, it said "No recoveries were found for your device", but in same time file for my device (that's where I made mistake, downloading TF300TG version) does exist, so what's story here? I guess this is may be because my TF300T isn't rooted yet?
Adding later. after digging this & other forums I found that in order to get root & have to have CWM/TWRP on my device & I can't get them until my TF300T is rooted. Am I confused & talking rubbish?
Adding 2 hours later. I rooted the device using XDA guide. Still trouble to reboot device. It always reboots into TWRP, then I have to connect it to PC & reboot with ADB commands. This isn't right...
goldenval said:
Tobdaryl, I couldn't find "Donate Me" button in your profile, so give me your paypal account for a little present please! :good: It worked!!! I installed correct driver from given guide, rebooted into bootloader, using ADB comand & got 3 icons: RCK, Android & Wipe Data. I tried Wipe Data, it said "can't mount something", don't remember now what. I rebooted again & clicked on Android & loaded into normal screen. Because of Asus became completely flat I put it on charge now. And after that I will have to come back to original task - to root my TF300T. While it's charging I downloaded Goo manager & tried to install TWRP, it said "No recoveries were found for your device", but in same time file for my device (that's where I made mistake, downloading TF300TG version) does exist, so what's story here? I guess this is may be because my TF300T isn't rooted yet?
Adding later. after digging this & other forums I found that in order to get root & have to have CWM/TWRP on my device & I can't get them until my TF300T is rooted. Am I confused & talking rubbish?
Adding 2 hours later. I rooted the device using XDA guide. Still trouble to reboot device. It always reboots into TWRP, then I have to connect it to PC & reboot with ADB commands. This isn't right...
Click to expand...
Click to collapse
Go manager does not have the proper twrp for our tablet.
Rooting is no longer required to flash twrp. Motochopper will root with just adb.
I suggest we try to get everything working properly with stock before changing or adding anything.
Go to to this link and download the stock Asus firmware 10.4.2.20. Choose the proper sku for your location (ww, us or whatever). Don't forget to thank philos64 while there. Unzip once and place on your tablet, flash with twrp, if that fails unzip again and place the blob file in the directory with adb and fastboot and flash with fastboot. Verify everything works properly before making any other changes.
Thank you for the donation offer.
I don't have a method to receive donations. A simple click on thanks will be good.
My problem is that because I installed wrong TWRP by mistake - it can't mount anything & I can't install anything from SD or internal memory. So, should I delete existing TWRP somehow &/or replace it by CWM recovery?
tobdaryl said:
Unzip once and place on your tablet, flash with twrp, if that fails unzip again and place the blob file in the directory with adb and fastboot and flash with fastboot
Click to expand...
Click to collapse
goldenval said:
My problem is that because I installed wrong TWRP by mistake - it can't mount anything & I can't install anything from SD or internal memory. So, should I delete existing TWRP somehow &/or replace it by CWM recovery?
Click to expand...
Click to collapse
No don't delete twrp or install cwm. We should have access to adb and or fastboot. We should be able to use either to get sorted.
Go to to this link and download the stock Asus firmware 10.4.2.20. Choose the proper sku for your location (ww, us or whatever). Don't forget to thank philos64 while there. Unzip twice and place the blob file in the directory with adb and fastboot and flash with adb. Verify everything works properly before making any other changes.
adb push blob /sdcard/blob
adb shell
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
exit
adb reboot
May I ask you then? My ROM number is: JOP40D.WW_epad-10.6.1.15.3-20130416 & as I can see from numbers you are offerring me to downgrade (from 4.2 to 4.1). Will this not kill the device? And why can't we re-install existing ROM through ADB? I'm not arguing, just trying to understand.
tobdaryl said:
No don't delete twrp or install cwm. We should have access to adb and or fastboot. We should be able to use either to get sorted.
Go to to this link and download the stock Asus firmware 10.4.2.20. Choose the proper sku for your location (ww, us or whatever). Don't forget to thank philos64 while there. Unzip twice and place the blob file in the directory with adb and fastboot and flash with adb. Verify everything works properly before making any other changes.
adb push blob /sdcard/blob
adb shell
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
exit
adb reboot
Click to expand...
Click to collapse
HI all,
I am VERY new to this custom ROM stuff, and I am a bit confused. I have an ASUS TF300T Transformer Tablet. It has 4.2.1 loaded, build is JOP40D.US_epad-10.6.1.12.3-20130416. If more particulars are needed, I can provide.
I have rooted the tablet (I used motochopper to gain superuser access), thinking that would allow me to load a custom ROM. I was WRONG (as most of you probably know). I want to load a custom ROM (CyanogenMod), and also not use the ASUS preloaded software. I want something with less bloat, is faster, and something I can customize at will.
So....I have read a ton of posts on this, but I can't seem to find a step by step single, simple process to accomplish this daunting task. Simply put, I need step by step instructions that can get me where I want to be. At this point, I'm not so sure I could be more confused! LOL!
Anyone who has done this, or is experienced with this, I could use some major league assistance!
I want a faster, more "open" tablet. I also know I don't want to brick it. I definitely don't need a 300.00 paperweight!
Any help would be greatly appreciated.
Thanks!!
Scar!
robscar said:
HI all,
I am VERY new to this custom ROM stuff, and I am a bit confused. I have an ASUS TF300T Transformer Tablet. It has 4.2.1 loaded, build is JOP40D.US_epad-10.6.1.12.3-20130416. If more particulars are needed, I can provide.
I have rooted the tablet (I used motochopper to gain superuser access), thinking that would allow me to load a custom ROM. I was WRONG (as most of you probably know). I want to load a custom ROM (CyanogenMod), and also not use the ASUS preloaded software. I want something with less bloat, is faster, and something I can customize at will.
So....I have read a ton of posts on this, but I can't seem to find a step by step single, simple process to accomplish this daunting task. Simply put, I need step by step instructions that can get me where I want to be. At this point, I'm not so sure I could be more confused! LOL!
Anyone who has done this, or is experienced with this, I could use some major league assistance!
I want a faster, more "open" tablet. I also know I don't want to brick it. I definitely don't need a 300.00 paperweight!
Any help would be greatly appreciated.
Thanks!!
Scar!
Click to expand...
Click to collapse
You need a custom recovery! download twrp here: http://techerrata.com/browse/twrp2/tf300t
DOWNLOAD THE ONE THAT SAYS "openrecovery-twrp-2.5.0.0-4.2" and flash it with fastboot in cmd " fastboot -i 0x0B05 flash recovery twrp.blob" make sure you rename the blob to "twrp.blob"
*update your info your bootloader is "10.6.1.15.3" instead of "10.6.1.12.3"
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
You can also follow this guide. It explains what you need to do pretty well. But you do need a custom recovery, which i prefer TWRP http://forum.xda-developers.com/showthread.php?t=2187982
I was confused at first too. I think they need to change the wording in the tutorials. They say "If you're on JB bootloader, this twrp, if you're on 4.2 BL, that TWRP" and i was just thinking... WTF, both of them, 4.1 and 4.2 are jellybean.... it should be changed to 4.1 BL and 4.2 BL, none referred to as JB.
Sent from my TF300T using Tapatalk 2
So...does my tablet need to be unlocked first? What do I do once TWRP is loaded on my tablet? When you say "flash it with fastboot in cmd " fastboot -i 0x0B05 flash recovery twrp.blob". What does this mean? This is where it gets very confusing.
robscar said:
So...does my tablet need to be unlocked first? What do I do once TWRP is loaded on my tablet? When you say "flash it with fastboot in cmd " fastboot -i 0x0B05 flash recovery twrp.blob". What does this mean? This is where it gets very confusing.
Click to expand...
Click to collapse
if you installed root on your device you should have adb and fastboot, right?
if you are on windows(pc) press the windows key + the R key and type cmd in the search box, then press enter now navigate to the adb/fastboot directory on your pc by typing "cd <the location of the file>" then plug in your tablet in fastboot and type " fastboot -i 0x0B05 flash recovery twrp.blob" what does this do? this command flashes twrp over the stock recovery, with twrp you can install custom roms! after you have done this download a rom you like (watch out for bootloader versions! if you are on stock 4.2.1 i would reccomend the latest unofficial AOKP or the latest official cm10.1) if you download a rom you can see it is a zip file, place this zip file on your sdcard and power up your tablet in bootloader by holding volume down + power button till icons pop up! now press the volume up key when the RCK icon is blinking! now twrp should start, now click on wipe and then advanced wipe and wipe system data cache(you don't need to wipe your data if you prefer to keep it!) now go back to the main menu of twrp by pressing the home button in the top right corner, now click install and navigate to the directory you have placed the rom in, after install reboot!
I've a TF300TG but I think my question is associated to the title of this thread. Do I have to note the sku of my Pad or isn't that important when I flash a custom Rom?
In the threads of many custom Roms I've read nothing about the sku. So I'm not sure if I have to take care for this.
Sent from my HTC One X using xda app-developers app
noahvt said:
if you installed root on your device you should have adb and fastboot, right?
if you are on windows(pc) press the windows key + the R key and type cmd in the search box, then press enter now navigate to the adb/fastboot directory on your pc by typing "cd <the location of the file>" then plug in your tablet in fastboot and type " fastboot -i 0x0B05 flash recovery twrp.blob" what does this do? this command flashes twrp over the stock recovery, with twrp you can install custom roms! after you have done this download a rom you like (watch out for bootloader versions! if you are on stock 4.2.1 i would reccomend the latest unofficial AOKP or the latest official cm10.1) if you download a rom you can see it is a zip file, place this zip file on your sdcard and power up your tablet in bootloader by holding volume down + power button till icons pop up! now press the volume up key when the RCK icon is blinking! now twrp should start, now click on wipe and then advanced wipe and wipe system data cache(you don't need to wipe your data if you prefer to keep it!) now go back to the main menu of twrp by pressing the home button in the top right corner, now click install and navigate to the directory you have placed the rom in, after install reboot!
Click to expand...
Click to collapse
OK, first, I am on a MAC. I have "terminal" for CMD lines, so, it should find whatever files I need it to find just as the windows CMD block will.
I have "fastboot and ADB" in a folder on my desktop, I have named the folder "android". I also downloaded the TWRP for 4.2.1 (renamed to TWRP.BLOB). I think I have all the files I require, it's just a matter of what steps to take. I also have the CM 10.1. This is the ROM I would like to use.
I was also reading that using TWRP, I am not supposed to wipe. I guess, theoretically, I want to be able to boot to the original ASUS ROM in case anything goes wrong. Otherwise, I wouldn't have a ROM to boot from.
I'm not sure if everything I am saying is correct, again, I am very new to this and trying to undertand exactly what I am doing.
robscar said:
OK, first, I am on a MAC. I have "terminal" for CMD lines, so, it should find whatever files I need it to find just as the windows CMD block will.
I have "fastboot and ADB" in a folder on my desktop, I have named the folder "android". I also downloaded the TWRP for 4.2.1 (renamed to TWRP.BLOB). I think I have all the files I require, it's just a matter of what steps to take. I also have the CM 10.1. This is the ROM I would like to use.
I was also reading that using TWRP, I am not supposed to wipe. I guess, theoretically, I want to be able to boot to the original ASUS ROM in case anything goes wrong. Otherwise, I wouldn't have a ROM to boot from.
I'm not sure if everything I am saying is correct, again, I am very new to this and trying to undertand exactly what I am doing.
Click to expand...
Click to collapse
The fast boot and adb you have are most likely windows files. Not sure if there is fast boot and adb for Mac.
Sent from my TF300T using Tapatalk 2
diesburg said:
The fast boot and adb you have are most likely windows files. Not sure if there is fast boot and adb for Mac.
Sent from my TF300T using Tapatalk 2
Click to expand...
Click to collapse
I got these files from the SDK download for MAC.
robscar said:
I got these files from the SDK download for MAC.
Click to expand...
Click to collapse
Any possibility of kicking this to the top and maybe getting this tablet accomplished tonight? I believe I have all the files I need (for MAC), and I am ready to go. I just need to know exactly what to do.
HELP!! LOL!!
robscar said:
Any possibility of kicking this to the top and maybe getting this tablet accomplished tonight? I believe I have all the files I need (for MAC), and I am ready to go. I just need to know exactly what to do.
HELP!! LOL!!
Click to expand...
Click to collapse
I can TRY to help. I have no mac, never used one, dont know the procedures for getting the drivers and stuff installed on mac. So, im going to assume you have the fastboot drivers installed properly.
NOTE: IF YOU'RE TABLET BREAKS, NEVER TURNS ON AGAIN, OR GOES UP IN SMOKE BECAUSE OF MY DIRECTIONS, IT'S ALL YOUR FAULT AND RESPONSIBILITY NOT MINE. GET OVER IT AND BUY A NEW ONE.....LMAO.... really though, i am helping as best as i can and you always run a risk flashing devices and thats your risk, not mine.... but if you follow my directions exactly, you will be jsut fine and not have a broken device...
First, make sure you're on the latest update from asus. Should be a bootloader ending in 15.3 and android 4.2.1 .
Second, unlock your bootloader. Unlocking the bootloader is quite simple. Download this: http://d-h.st/86c Install it on the tablet and open the app (its a RAR file so it needs extracted first) Follow the directions it gives you, if i remember correctly, you just click yes or something, tablet reboots, and the bootloaders unlocked. If it sucessfully unlocks, when you first turn the tablet on, in the top left corner of the screen, it will say unlocked.
After bootloaders unlocked, turn the tablet off. Power on the tablet by holding the power button and the volume down button at the same time. This will take you into bootloader mode. One quick thing to make sure you are on the latest bootloader. The bootloader screen should have 3 icons to choose from, if it has 4, you are on the old/wrong bootloader and need to go back and update your system before proceeding. If 3 icons, you're good to go, plug the usb cable in the tablet and in your computer.
Download TWRP recovery now. This is the part where you dont wanna screw up, downloading and flashing wrong recovery can equal a broken tablet. Download this exact TWRP recovery: http://diesburg.co/tf300t/twrp/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
Put that file in the folder where fastboot is.
Now in your terminal/command line, go to the directory where fastboot is. With tablet plugged in and in bootloader mode like mentioned above and terminal in the fastboot folder, type: fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob and press enter .... this will flash TWRP recovery to your tablet using fastboot.... if you get something like "waiting for device" in your terminal window after typing this and it never gets past that, thats where i cant help, drivers for fastboot or something isnt right.... if it works, hell yea, onto the next step....
Reboot the tablet, type: fastboot -i 0x0B05 reboot and press enter.... let android fully boot up, copy your ROM to your tablet and dont forget the gapps package for the rom..... now turn the tablet back off......
power the tablet back on like before holding power button and volume down.... once in here, RCK will already be highlighted, if its not, use your volume down key to get it highlighted... once highlighted, hit volume up and this will boot the twrp recovery you flashed......
Once in TWRP, (FIRST DONT FORGET CLICK BACKUP AND MAKE A BACKUP OF YOUR CURRENT ROM!!!) now, make sure you can see your cyanogenmod rom file and gapps by clicking install and going to the ocation where its at, if you see the 2 files, click the back button to the main screen.... on the main screen, click : Wipe, then click factory reset.....after that, go back to the wipe screen, and click system to wipe the system partition..... now go back to the main screen again....
Click install, then click to install the cyanogenmod rom.... after it installs, install the gapps package.... after that, you SHOULD be good to go, reboot the tablet by clicking reboot to system.....
I think that covers everything..... now in the future for flashing other roms, always wipe before flashing and flash the roms the same way you did this one.... just so you know, not ALL roms require gapps package.... most specify whether they do or not....
Any problems, let me know unless its the "waiting for device" thing, i cant help with mac drivers, someone else will have to
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
diesburg said:
I can TRY to help. I have no mac, never used one, dont know the procedures for getting the drivers and stuff installed on mac. So, im going to assume you have the fastboot drivers installed properly.
NOTE: IF YOU'RE TABLET BREAKS, NEVER TURNS ON AGAIN, OR GOES UP IN SMOKE BECAUSE OF MY DIRECTIONS, IT'S ALL YOUR FAULT AND RESPONSIBILITY NOT MINE. GET OVER IT AND BUY A NEW ONE.....LMAO.... really though, i am helping as best as i can and you always run a risk flashing devices and thats your risk, not mine.... but if you follow my directions exactly, you will be jsut fine and not have a broken device...
First, make sure you're on the latest update from asus. Should be a bootloader ending in 15.3 and android 4.2.1 .
Second, unlock your bootloader. Unlocking the bootloader is quite simple. Download this: http://d-h.st/86c Install it on the tablet and open the app (its a RAR file so it needs extracted first) Follow the directions it gives you, if i remember correctly, you just click yes or something, tablet reboots, and the bootloaders unlocked. If it sucessfully unlocks, when you first turn the tablet on, in the top left corner of the screen, it will say unlocked.
After bootloaders unlocked, turn the tablet off. Power on the tablet by holding the power button and the volume down button at the same time. This will take you into bootloader mode. One quick thing to make sure you are on the latest bootloader. The bootloader screen should have 3 icons to choose from, if it has 4, you are on the old/wrong bootloader and need to go back and update your system before proceeding. If 3 icons, you're good to go, plug the usb cable in the tablet and in your computer.
Download TWRP recovery now. This is the part where you dont wanna screw up, downloading and flashing wrong recovery can equal a broken tablet. Download this exact TWRP recovery: http://diesburg.co/tf300t/twrp/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
Put that file in the folder where fastboot is.
Now in your terminal/command line, go to the directory where fastboot is. With tablet plugged in and in bootloader mode like mentioned above and terminal in the fastboot folder, type: fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob and press enter .... this will flash TWRP recovery to your tablet using fastboot.... if you get something like "waiting for device" in your terminal window after typing this and it never gets past that, thats where i cant help, drivers for fastboot or something isnt right.... if it works, hell yea, onto the next step....
Reboot the tablet, type: fastboot -i 0x0B05 reboot and press enter.... let android fully boot up, copy your ROM to your tablet and dont forget the gapps package for the rom..... now turn the tablet back off......
power the tablet back on like before holding power button and volume down.... once in here, RCK will already be highlighted, if its not, use your volume down key to get it highlighted... once highlighted, hit volume up and this will boot the twrp recovery you flashed......
Once in TWRP, (FIRST DONT FORGET CLICK BACKUP AND MAKE A BACKUP OF YOUR CURRENT ROM!!!) now, make sure you can see your cyanogenmod rom file and gapps by clicking install and going to the ocation where its at, if you see the 2 files, click the back button to the main screen.... on the main screen, click : Wipe, then click factory reset.....after that, go back to the wipe screen, and click system to wipe the system partition..... now go back to the main screen again....
Click install, then click to install the cyanogenmod rom.... after it installs, install the gapps package.... after that, you SHOULD be good to go, reboot the tablet by clicking reboot to system.....
I think that covers everything..... now in the future for flashing other roms, always wipe before flashing and flash the roms the same way you did this one.... just so you know, not ALL roms require gapps package.... most specify whether they do or not....
Any problems, let me know unless its the "waiting for device" thing, i cant help with mac drivers, someone else will have to
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
So, no matter what I do, the bootloader has to be unlocked, correct?
robscar said:
So, no matter what I do, the bootloader has to be unlocked, correct?
Click to expand...
Click to collapse
for a custom rom, as far as i know, yes
but for just root on stock rom i believe theres ways to root stock without unlocking the bootloader
Sent from my TF300T using Tapatalk 2
I simply cannot seem to get the MAC to do this. I just don't know what command lines to use in the "terminal". I am amazed that no one has flashed their tablet with a MAC.
Anyone who has done this with a MAC, please drop a line if you can. I would really like to get this done if at all possible.
I am unlocked, I get all the way to the "flash" commands, and then it seems to not want to cooperate.
HELP!
robscar said:
I simply cannot seem to get the MAC to do this. I just don't know what command lines to use in the "terminal". I am amazed that no one has flashed their tablet with a MAC.
Anyone who has done this with a MAC, please drop a line if you can. I would really like to get this done if at all possible.
I am unlocked, I get all the way to the "flash" commands, and then it seems to not want to cooperate.
HELP!
Click to expand...
Click to collapse
It's most likely drivers.
http://forum.xda-developers.com/showthread.php?t=1917237
Maybe that'll help?
Sent from my TF300T using Tapatalk 2
I wanted to close out this thread and thank everyone who jumped in to try to assist me. I was not able to flash my tablet, nor get the Cyanogen mod loaded. Not sure why, but, as I try to load TWRP, I get a "permission denied" error.
Eventually, I will get my hands on a windows computer and give this another shot. But, it should have worked on my MAC as easily as anything else. Not sure exactly what I am doing wrong, but, my tablet is working just fine so, I know I did not "mess" anything up (YAY).
If someone has been able to "flash" and put a custom rom on their ASUS Transformer using a MAC computer, please get with me and let's chat!
Again, thanks everyone for taking some time to walk me thru this! I learned a lot, so your efforts did not go to waste! I great appreciate it!
Scar!
robscar said:
I wanted to close out this thread and thank everyone who jumped in to try to assist me. I was not able to flash my tablet, nor get the Cyanogen mod loaded. Not sure why, but, as I try to load TWRP, I get a "permission denied" error.
Eventually, I will get my hands on a windows computer and give this another shot. But, it should have worked on my MAC as easily as anything else. Not sure exactly what I am doing wrong, but, my tablet is working just fine so, I know I did not "mess" anything up (YAY).
If someone has been able to "flash" and put a custom rom on their ASUS Transformer using a MAC computer, please get with me and let's chat!
Again, thanks everyone for taking some time to walk me thru this! I learned a lot, so your efforts did not go to waste! I great appreciate it!
Scar!
Click to expand...
Click to collapse
not sure exactly how a mac works but i believe its some sort of linux. can you by chance start the terminal with "administrator" priveleges or type "su" in the terminal to get root priveleges? Just my thoughts with a "permission denied" error, you dont have administrator/root access.
In that link i shared above about mac and fastboot, it says to use " ./ " in front of every command. So try the fastboot commands i said above to flash the recovery but do it with ./ infront like this: ./fastboot flash commands
Sent from my TF300T using Tapatalk 2
Well, I used Motochopper to root my tablet, so, I'm not quite sure exactly what you mean. So, I am rooted, my BL is unlocked.
My tablets boots in "fastboot", I just can't seem to get the flash done. At this point, I am not so sure I could be more lost. LOL!
robscar said:
Well, I used Motochopper to root my tablet, so, I'm not quite sure exactly what you mean. So, I am rooted, my BL is unlocked.
My tablets boots in "fastboot", I just can't seem to get the flash done. At this point, I am not so sure I could be more lost. LOL!
Click to expand...
Click to collapse
In the steps I told you above. The part where you do the fastboot commands in the terminal. "fastboot flash 0x(somenumber) recovery twrp.blob"
put a ./ in front of the fastboot command... so its "./fastboot flash 0x(thatnumber) recovery twrp.blob"
Sent from my TF300T using Tapatalk 2
I was following Frederuco's Guide to Root and ROM the TF101 at transformerforums
I download the Universal Naked Drivers, updated apx driver, tried both of these easyflashers as described in this excerpt from above tutorial:
Next, we need to get the EasyFlasher from whitekidney at XDA: EasyFlasher - Install CWM/Root/unbrick in one click! [ALL TF101][NVFLASH] - xda-developers
Quote Originally Posted by Frederuco
UPDATE: The files on the XDA thread for EasyFlasher have not been updated for newer recoveries. I HIGHLY recomend using TWRP. 2.3.2.3 is the latest official version and 2.5.0.0 is the latest unofficial version.
I repacked the files with the two latest versions here:
EasyFlasher with TWRP 2.3.2.3
EasyFlasher with TWRP 2.5.0.0
NOTE - It STILL has the TWRP version listed as 2.2.1.1, but it WILL INSTALL 2.5.0.0. I cannot update this line in the exe file.
Hit sbk1 and got a short line of code with success message after doing easy flash twrp recovery but recovery boot only resulted in the two android wipe data option.
Then I tried the peri tool. - ran as administrator, used dir to confirm files in directory, ran bat- it said press any key to continue. I hit key and nothing happened.
Did you press the VOL UP when the white text is on the screen BEFORE you get to the WIPE and COLD BOOT options?
You will end up at a dead droid (stock recovery) or TWRP when you hit VOL UP at the RCK prompt.
frederuco said:
Did you press the VOL UP when the white text is on the screen BEFORE you get to the WIPE and COLD BOOT options?
You will end up at a dead droid (stock recovery) or TWRP when you hit VOL UP at the RCK prompt.
Click to expand...
Click to collapse
i pressed volume up when I saw the white text over the asus symbol. that took me to the screen with the 2 options. reboot or wipe data
Well, THAT AIN'T RIGHT!
I'd try RCK again. Not sure what else to tell ya.
frederuco said:
Well, THAT AIN'T RIGHT!
I'd try RCK again. Not sure what else to tell ya.
Click to expand...
Click to collapse
RCK?
leif2 said:
RCK?
Click to expand...
Click to collapse
RCK = Recovery
The white text says "Press Vol Up to enter RCK"
frederuco said:
RCK = Recovery
The white text says "Press Vol Up to enter RCK"
Click to expand...
Click to collapse
DO i NEED TO BE RUNNING easy flasher each time I try first?
No, just. Try to boot to recovery.
frederuco said:
No, just. Try to boot to recovery.
Click to expand...
Click to collapse
yes I press vol up before 5 sec. warning. In either case if I press it or not I get taken to the same 2 option data wipe/cold boot screen
Is your USB cable plugged into your PC? If so, try unplugging it and then try booting to recovery.
frederuco said:
Is your USB cable plugged into your PC? If so, try unplugging it and then try booting to recovery.
Click to expand...
Click to collapse
still :crying:not working. Im now noticing since i unplugged tablet from PC, during boot after i let go of vol down/power, im no longer given 5 seconds ro hit volume up. Instead it goes to data wipe screen as soon as i let go of buttons.
If your SBK1 then why not use the old fashioned NV flash method with prime rom and see how that works out for you.
---------- Post added at 08:34 PM ---------- Previous post was at 08:23 PM ----------
Heres the original thread.
Just take your time, youll get there.
If you get things working then id suggest using the Goo apps open recovery script to install TWRP again and then use TWRP to install any of the most up to date roms just to avoid any issues.
okay followed your link and downloaded nvflash zip and prime 1.4. did the following 3 steps:
1 Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
2 (Windows only) Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip
3 Run download.sh (linux) or download.bat (windows)
In step 2 - driver wouldn't take I presume since I already updated driver when using frederuco's guide. Shouild I have uninstalled APX and reinstalled this version?
Anyhow, I completed step 3 allot of messages about partioning and now there is message on my tablet:
entering nv flash recovery mode/nv3p server
chip vid ----
What do I do now- apply prime? How please tell? Thanks
leif2 said:
okay followed your link and downloaded nvflash zip and prime 1.4. did the following 3 steps:
1 Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
2 (Windows only) Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip
3 Run download.sh (linux) or download.bat (windows)
In step 2 - driver wouldn't take I presume since I already updated driver when using frederuco's guide. Shouild I have uninstalled APX and reinstalled this version?
Anyhow, I completed step 3 allot of messages about partioning and now there is message on my tablet:
entering nv flash recovery mode/nv3p server
chip vid ----
What do I do now- apply prime? How please tell? Thanks
Click to expand...
Click to collapse
Did you put the prime file into the same folder that contains the .bat file?
If I recall correctly, once you click on the bat file while in apx then it should be as simple as that aslong as you have the prime rom file in the containing folder.
its been a while since I used nv, infact I only ever used it when I first rooted. Pity the videos gone, it was really helpful to follow
Did you use one of the repacked EasyFlashers that I had done? If so, try the original. I think something may be wrong with my repacked ones. I will test it out in the morning.
http://www.youtube.com/watch?v=HTWNldAErFc&feature=youtube_gdata_player
try this guide.....sounds like you may not be in apx mode but its hard to say.
Sorry, I'd thought I'd posted under Q&A/Help. Not sure if a moderator can move it where it belongs?
My tf300t (ICS v9.3.4.17) is unlocked, rooted, and has TWRP 2.6.3.0 installed. I also have created the nvflash backups so it's currently running on the AndroidRoot v9.4.3.30r01 bootloader. I've stayed with
ICS and not updated anything except TWRP, but was just about to update to either ICS v9.4.3.30 or jump and install the latest JB.
Earlier today I went into Terminal Emulator, typed su and reboot as I've always done. I thought my tablet had shutdown because the screen stayed blank. I tried the power button and nothing so thought
maybe my power button had given out. I then tried plugging in the charging/usb cable which normally would get it to boot and again blank screen. Last I tried connecting to my pc and found it was in
APX mode. I'm able to boot up from nvflash and function normally but I'm stuck once I shut off the tablet from ICS (have to rerun nvflash to boot up again).
When I power off from APX mode, it automatically restarts back into APX mode. I was able to get into TWRP and tried restoring my latest nandroid (System, Data, Recovery, & Boot partitions) but no
change. Also tried a factory reset but same results - booting into APX yet again...
Ack, at this point I'm about ready to punt. I have my backups (TB & Helium) and am thinking of trying to update to v9.4.3.30 to see if this clears up booting into APX mode. To do this, can I just install the single
zip using TWRP & then re-flash TWRP using adb (or fastboot assuming I get it back)? Or do it via nvflash? If by nvflash, are these the correct commands after unpacking the v9.4.3.30 blob:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
Thoughts or ideas are really appreciated!
APX Mode
wha2do said:
My tf300t (ICS v9.3.4.17) is unlocked, rooted, and has TWRP 2.6.3.0 installed. I also have created the nvflash backups so it's currently running on the AndroidRoot v9.4.3.30r01 bootloader. I've stayed with
ICS and not updated anything except TWRP, but was just about to update to either ICS v9.4.3.30 or jump and install the latest JB.
Earlier today I went into Terminal Emulator, typed su and reboot as I've always done. I thought my tablet had shutdown because the screen stayed blank. I tried the power button and nothing so thought
maybe my power button had given out. I then tried plugging in the charging/usb cable which normally would get it to boot and again blank screen. Last I tried connecting to my pc and found it was in
APX mode. I'm able to boot up from nvflash and function normally but I'm stuck once I shut off the tablet from ICS (have to rerun nvflash to boot up again).
When I power off from APX mode, it automatically restarts back into APX mode. I was able to get into TWRP and tried restoring my latest nandroid (System, Data, Recovery, & Boot partitions) but no
change. Also tried a factory reset but same results - booting into APX yet again...
Ack, at this point I'm about ready to punt. I have my backups (TB & Helium) and am thinking of trying to update to v9.4.3.30 to see if this clears up booting into APX mode. To do this, can I just install the single
zip using TWRP & then re-flash TWRP using adb (or fastboot assuming I get it back)? Or do it via nvflash? If by nvflash, are these the correct commands after unpacking the v9.4.3.30 blob:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
Thoughts or ideas are really appreciated!
Click to expand...
Click to collapse
WoW that is an old bootloder..... v9.3.4.17 What is the SKU of that bootloader??
Enter APX mode and bootstrap in, If thats the ways its done.. I don't know because, I did my nvflash after jb came out...Run this command
Code:
nvflash -r --go
It will not reboot your tablet but it is supposed to let the bootloader resume on go which should be the next boot....
Just long hold your power button and let your tablet boot normally... Let me know if this helps at all... Thx lj
O yeah just be aware that the newest version of TWRP is having some issues... Just a FYI
lj50036 said:
WoW that is an old bootloder..... v9.3.4.17 What is the SKU of that bootloader??
Enter APX mode and bootstrap in, If thats the ways its done.. I don't know because, I did my nvflash after jb came out...Run this command
Code:
nvflash -r --go
It will not reboot your tablet but it is supposed to let the bootloader resume on go which should be the next boot....
Just long hold your power button and let your tablet boot normally... Let me know if this helps at all... Thx lj
O yeah just be aware that the newest version of TWRP is having some issues... Just a FYI
Click to expand...
Click to collapse
Thanks for the reply. The bootloader is the original one loaded when I created the nvflash backups. When rebooting from nvflash and holding the vol down button, I see:
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.3.30-20120206"
This had to have been universal for all that ran it way back when, though the SKU on my tablet is US (US_epad-9.4.3.2012...) and no real issues in over the year I've had it.
The nvflash -r --go command is the same as nvflash --resume --go...both reboot the device (nvflash help verifies they're the same).
------> Back to the issue at hand *sigh* <-----
So... I'm still having to reboot from APX mode using nvflash and hold the volume down button. At that point I can either enter TWRP or leave it go and it'll cold boot - no icons
display for fastboot, etc. It just shows:
Platform Pre OS boot configuration...
Cold-booting Linux
And then it will boot into ICS, though found it may just go back into APX mode again. It can take several tries, but it'll finally boot properly.
Sooo...what's my next step? Have noticed TWRP 2.6.3.0 seems to be a bit flaky in the past. Should I try installing US_epad-user-9.4.3.30.zip using TWRP? I have
OTA Rootkeeper installed with SuperSU so root should either remain or be restorable (fingers crossed). Or do I need to use nvflash to flash each partition? Or finally go
back to my original nvflash blobs? I really don't want to move forward and screw up something worse than it is!
Side note: I've tried to install tried & true TWRP v2.3.1.0. Using adb, it appears to flash successfully, I reboot into ICS, and then nvflash boot into TWRP - but I'm still
on v2.6.3.0. Possibly not rebooting smoothly into ICS isn't allowing the img file to take? For now will deal continue using my installed version v2.6.3.0 I guess...
Thanks for direction on where to go next! And if can, spell out my steps to take in detail (sometimes I may be a tad dense and don't mind any eyestrain, lol).
wha2do said:
Thanks for the reply. The bootloader is the original one loaded when I created the nvflash backups. When rebooting from nvflash and holding the vol down button, I see:
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.3.30-20120206"
This had to have been universal for all that ran it way back when, though the SKU on my tablet is US (US_epad-9.4.3.2012...) and no real issues in over the year I've had it.
The nvflash -r --go command is the same as nvflash --resume --go...both reboot the device (nvflash help verifies they're the same).
------> Back to the issue at hand *sigh* <-----
So... I'm still having to reboot from APX mode using nvflash and hold the volume down button. At that point I can either enter TWRP or leave it go and it'll cold boot - no icons
display for fastboot, etc. It just shows:
Platform Pre OS boot configuration...
Cold-booting Linux
And then it will boot into ICS, though found it may just go back into APX mode again. It can take several tries, but it'll finally boot properly.
Sooo...what's my next step? Have noticed TWRP 2.6.3.0 seems to be a bit flaky in the past. Should I try installing US_epad-user-9.4.3.30.zip using TWRP? I have
OTA Rootkeeper installed with SuperSU so root should either remain or be restorable (fingers crossed). Or do I need to use nvflash to flash each partition? Or finally go
back to my original nvflash blobs? I really don't want to move forward and screw up something worse than it is!
Side note: I've tried to install tried & true TWRP v2.3.1.0. Using adb, it appears to flash successfully, I reboot into ICS, and then nvflash boot into TWRP - but I'm still
on v2.6.3.0. Possibly not rebooting smoothly into ICS isn't allowing the img file to take? For now will deal continue using my installed version v2.6.3.0 I guess...
Thanks for direction on where to go next! And if can, spell out my steps to take in detail (sometimes I may be a tad dense and don't mind any eyestrain, lol).
Click to expand...
Click to collapse
Ok so you are 100% sure that you have had a US SKU version bootloader from when you got it new????
Where are you getting the firmware zip file from??
And you think this all started because of a wrong recovery flash???
lj50036 said:
Ok so you are 100% sure that you have had a US SKU version bootloader from when you got it new????
Where are you getting the firmware zip file from??
And you think this all started because of a wrong recovery flash???
Click to expand...
Click to collapse
Thanks for the quick reply... I'm positive on the US SKU - I have a screenshot I took of the SW info when it was brand new - here it is:
http://i1331.photobucket.com/albums...delampSWinfo-2012-11-25-07-29_zps27ba6fc6.jpg
As for the earlier firmware zips I've got, they were provided in one of the XDA posts - possibly this one: http://forum.xda-developers.com/showpost.php?p=33883254&postcount=3
Nope, it just suddenly started while using the tablet normally. No flashing, restoring nandroids, etc in at least a week or two. I was playing one of my games on the tablet and sometimes the graphics will act
funny or it'll fc on me. So I either do a cold restart or reboot using Terminal Emulator to get the behaving normally again. In this case I rebooted using Android Terminal and suddenly only had a black
screen. Finally realized it wasn't powered down but was going into APX mode... Sorry, just tried flashing the older version of TWRP I'd always used since v2.6.3.0 has been flaky off and on. V2.6.3.0 was
originally flashed about 2-3 weeks ago and I'll just stick with it while working on fixing this!
The only thing I can think which may be unrelated. My daughter loaded a non-market game that was tagged as having Android:Fujacks by Avast! Being non-market, maybe foolishly? I let Avast
uninstall it. But I'm almost positive I rebooted a few times after without any issues. Also restoring an earlier nandroid didn't help, so don't think it's the system or data partitions messed up. Could it
be the boot partition that's gone funky?
That's why I'm wondering if an "upgrade" to v9.4.3.30 would clear this up - and if so, best/safest way to do it? Hope that helps fill in a little more!
wha2do said:
Thanks for the quick reply... I'm positive on the US SKU - I have a screenshot I took of the the SW info when it was brand new - here it is:
http://i1331.photobucket.com/albums...delampSWinfo-2012-11-25-07-29_zps27ba6fc6.jpg
As for the earlier firmware zips I've got, they were provided in one of the XDA posts - possibly this one: http://forum.xda-developers.com/showpost.php?p=33883254&postcount=3
Nope, it just suddenly started without having done any flashing or restoring nandroids. I was playing one of my games on the tablet and sometimes the graphics will act
funny or it'll fc on me. So I either do a cold restart or reboot using Terminal Emulator to get it back to normal. In this case I rebooted using Android Terminal and suddenly
a black screen. Finally realized it wasn't powered down but was going into APX mode.
The only thing I can think which may be unrelated. My daughter loaded a non-market game that was tagged as having Android:Fujacks by Avast! Being non-market, maybe
foolishly? I let Avast uninstall it. But I'm almost positive I rebooted a few times after without any issues. Also restoring an earlier nandroid didn't help, so don't think it's the system
or data partitions messed up. Could it be the boot partition that's gone funky?
That's why I'm wondering if an "upgrade" to v9.4.3.30 would clear this up - and if so, best/safest way to do it? Hope that helps fill in a little more!
Click to expand...
Click to collapse
Ok the .30 zip from them what is inside the zip??
lj50036 said:
Ok the .30 zip from them what is inside the zip??
Click to expand...
Click to collapse
It's the normal Stock v9.4.3.30 update from ASUS. It's the "US_epad-user-9.4.3.30.zip" which in turn contains the META-INF folder and the blob file. The blob file contains:
blob.APP ; system img
blob.EBT ; bootloader.bin
blob.LNX ; boot img
blob.PT ; partition table I presume
blob.SOS ; stock recovery img
The blob names are exact and I think I have each identified as to their purpose going from old notes. EBT, APP, and LNX are the three that I believe could/would be flashed using nvflash
if necessary (if can't just install the full update zip & reinstall TWRP over the stock recovery)...
Is that what you're looking for?
wha2do said:
It's the normal Stock v9.4.3.30 update from ASUS. It's the "US_epad-user-9.4.3.30.zip" which in turn contains the META-INF folder and the blob file. The blob file contains:
blob.APP ; system img
blob.EBT ; bootloader.bin
blob.LNX ; boot img
blob.PT ; partition table I presume
blob.SOS ; stock recovery img
The blob names are exact and I think I have each identified as to their purpose going from old notes. EBT, APP, and LNX are the three that I believe could/would be flashed using nvflash
if necessary (if can't just install the full update zip & reinstall TWRP over the stock recovery)...
Is that what you're looking for?
Click to expand...
Click to collapse
Ok so it just a blob binary and a META-INF folder in the zip??
lj50036 said:
Ok so it just a blob binary and a META-INF folder in the zip??
Click to expand...
Click to collapse
Yep...standard update zip inside a zip that comes from ASUS.
wha2do said:
Yep...standard update zip inside a zip that comes from ASUS.
Click to expand...
Click to collapse
We need to get to fastboot and verify that we can see your devices boot into the bootloader screen.. As I recall you should have a
usb icon you must select to enable fastboot... Can you get to this point??
lj50036 said:
We need to get to fastboot and verify that we can see your devices boot into the bootloader screen.. As I recall you should have a
usb icon you must select to enable fastboot... Can you get to this point??
Click to expand...
Click to collapse
No, the icons one normally sees are missing/not available to be selected. When I reboot from nvflash & hold the vol down button, I only have two options. Volume up to enter TWRP as expected, or it begins cold booting. Guess that got lost in my lengthy message above:
So... I'm still having to reboot from APX mode using nvflash and hold the volume down button. At that point I can either enter TWRP or leave it go and it'll cold boot - no icons
display for fastboot, etc. It just shows:
Platform Pre OS boot configuration...
Cold-booting Linux
And then it will boot into ICS, though found it may just go back into APX mode again. It can take several tries, but it'll finally boot properly.
Click to expand...
Click to collapse
So unfortunately, no fastboot - only ADB, APX, and Recovery (TWRP) modes available.
wha2do said:
No, the icons one normally sees are missing/not available to be selected. When I reboot from nvflash & hold the vol down button, I only have two options. Volume up to enter TWRP as expected, or it begins cold booting. Guess that got lost in my lengthy message above:
So unfortunately, no fastboot - only ADB, APX, and Recovery (TWRP) modes available.
Click to expand...
Click to collapse
Ok well we need a different version of twrp than what your on now I would highly recommend a version older that what your on now.. as the newer twrps are buggy 2.5.5.0 is a solid one... Make sure you get the one for your tablet...as there are a few different versions... Than rename it
Code:
twrp.blob
Make sure you don't rename it twrp.blob.blob as windows is good at doing still stuff like that.....
Move your twrp.blob to the root of your c drive than open a command window as admin and type
Code:
cd /
This will move you to the root of your c drive in your command window than type
Code:
dir
This will list all the files and folder in the root of your c drive make sure you see the twrp.blob if so your ready
Boot your tablet into APX mode bootstrap into nvflash mode and type
Code:
nvflash -r --download 5 twrp.blob
The output of this will look something like this
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
Than
Code:
nvflash -r --go
Then try to enter recovery...
Let me know
lj50036 said:
Ok well we need a different version of twrp than what your on now I would highly recommend a version older that what your on now.. as the newer twrps are buggy 2.5.5.0 is a solid one... Make sure you get the one for your tablet...as there are a few different versions... Than rename it
Code:
twrp.blob
Make sure you don't rename it twrp.blob.blob as windows is good at doing still stuff like that.....
Move your twrp.blob to the root of your c drive than open a command window as admin and type
Code:
cd /
This will move you to the root of your c drive in your command window than type
Code:
dir
This will list all the files and folder in the root of your c drive make sure you see the twrp.blob if so your ready
Boot your tablet into APX mode bootstrap into nvflash mode and type
Code:
nvflash -r --download 5 twrp.blob
The output of this will look something like this
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
Than
Code:
nvflash -r --go
Then try to enter recovery...
Let me know
Click to expand...
Click to collapse
Ok - picked up v2.5.0.0 (don't see a v2.5.5.0 on the TWRP website) and successfully installed the .blob file but... As soon as I hit the volume up button it went to cold boot instead. I remembered with the Prime that for some reason, the TWRP img file format needed to be used when on the AndroidRoot bootloader. So long story short, got the img file installed and I have TWRP 2.5.0.0 running at the moment.
So where to next? And thanks so far
wha2do said:
Ok - picked up v2.5.0.0 (don't see a v2.5.5.0 on the TWRP website) and successfully installed the .blob file but... As soon as I hit the volume up button it went to cold boot instead. I remembered with the Prime that for some reason, the TWRP img file format needed to be used when on the AndroidRoot bootloader. So long story short, got the img file installed and I have TWRP 2.5.0.0 running at the moment.
So where to next? And thanks so far
Click to expand...
Click to collapse
So you can get into recovery now??? if so, take the double zipped firmware......unzip it one time and the zip that is made move to.....O
Do you have a way to put that zip on an sdcard so we can get it on your tablet?? If not no big deal.... Just let me know if you can make that happen.....
lj50036 said:
So you can get into recovery now??? if so, take the double zipped firmware......unzip it one time and the zip that is made move to.....O
Do you have a way to put that zip on an sdcard so we can get it on your tablet?? If not no big deal.... Just let me know if you can make that happen.....
Click to expand...
Click to collapse
Sorry, I get over wordy (lol)... Yes, I have TWRP 2.5.0.0 installed and was able to get in. I'd already prepared for this - have the unzipped (once) file sitting in my tablet's root folder (/sdcard). Checked and checksum matched so it transferred without errors (used Airdroid, in case wondering).
Took a few extra minutes - wanted double check all was there as I thought. So yes, have the v9.4.3.30 zipfile (containing META files & blob) on tablet's "root" directory. Currently in TWRP v2.5.0.0 and ready to install it (figuring that's the next step)...
Just give me the greenlight, lol
One thing doing quickly is making a nandroid - never can be too safe, heh! Should be about another 5 minutes...
wha2do said:
One thing doing quickly is making a nandroid - never can be too safe, heh! Should be about another 5 minutes...
Click to expand...
Click to collapse
No worries at all you take your time.... Let me know....
lj50036 said:
No worries at all you take your time.... Let me know....
Click to expand...
Click to collapse
Good to go!
wha2do said:
Good to go!
Click to expand...
Click to collapse
??????
Still here - at this point have the zipfile unzipped once, on the tablet's root directory, and TWRP v2.5.0.0 installed. I assume going to install the zip file via TWRP Install? Tablet's got plenty of battery charge so good to go - just let me know!