I rooted using viperMOD PrimeTime v4.5 today without any problems. Then I installed Rootkeeper via the market, unlocked the bootloader, and installed CWM using viperMOD PrimeTime v4.5. Everything worked flawlessly.
So then I noticed an Asus firmware update was available. I wanted to install it and then give rootkeeper a try to make sure I kept root.
During the Asus firmware update, the android symbol on the screen fell over on his back and had I think an X on him.
Apparently, something went wrong with the firmware update. Everything froze, so I pushed the power button.
Now, when the device turns on, it goes straight into CWM.
Since everything went haywire before I backed up the ROM, I have nothing to restore.
Also, now my device is not recognized by Windows.
I downloaded the [ROM][S Series] Virtuous Prime Beta 1 .zip file with the intent to install this custom ROM, but since I cannot get my Prime recognized by Windows, I cannot move the .zip file over to my Prime to install the ROM.
If anyone could help me through what to do next to possibly reinstall the stock ROM, get my device recognized by Windows, etc. It would be appreciated. I am totally lost now.
How can you have done this when development section clearly says don't try to apply OTA updates after unlocking prime? Its a guaranteed brick just waiting to happen. That's why you have to always read thoroughly everything involved. Obvious you didn't because you tried to apply update. SMH
You should be able to flash stock back with this info:
http://forum.xda-developers.com/showpost.php?p=22743057&postcount=119
It has worked for others who soft bricked prime. It should work n allow you to flash back stock rom.
Lesson to be learned here: Do not unlock device if you haven't researched it thoroughly. And never, ever ever ever try to apply an OTA update from Asus after unlocking device. It won't work and will brick your device almost 100% of the time. Once you unlocked device, say goodbye to OTA updates. They no longer will work. If you concerned with OTA updates then you have no business unlocking device. I hope you know you completely voided your warranty also by unlocking. Asus has proof as your serial number and device info was sent to Asus while you unlocked. Be glad xda is here and has solutions.
I have the same problem which i dont know how to fix
shinichikey said:
@demandaring: what exactly should I do? download the file, rename it, then put to removable sdcard, then boot using power+ volume down?
I don't think I cant do it because it's will lead into CWM...
Here are my case also: if you can help
I don't know what I did but after install the CWM successfully using PrimeTime 4.5, I couldn't get back into the system, but instead it keep boot back into Recovery mode after every single reboot. I have tried everything within my knowledge include: install the original zip file extracted from US_epaduser9_4_2_14UpdateLauncher.zip using recovery mod, and it stated successfully, but yeah still in a recovery loop; then I tried to install the Virtuous Prime Beta 1 through the CWM, it was also successfully but, guess what, still in the loop again, so I hope if anyone out there has this problem or know the solution, please help me, I am really appreciated... (I can get in to use adb in recovery mode also)...
Click to expand...
Click to collapse
" flashed today the file from this post (US Full OTA .14): http://forum.xda-developers.com/show...&postcount=387
Use this Method: EP201_SDUPDATE.ZIP (Rename extracted ZIP-File)
CONFIRM: Works ONLY with MicroSD CARD (REMOVABLE - ROOT).
Inernal Memory FAILURE - Search only for REMOVABLE RECOVERY
HOW TO:
-Shutdown Device
-HOLD LOWER VOL. + POWER
-CONFIRM within 5 Seconds with HIGHER VOL. "
when i hold the power+ lower volume, It went straight to CWM, what I am suppose to do in there?
Apparently, I screwed up. I saw the link that you mentioned.
http://forum.xda-developers.com/showpost.php?p=22743057&postcount=119
I downloaded the zip file, but since my prime is not recognized by Windows, how I can I get this zip file over to my Prime to install this zip file?
I renamed the zip file as instructed to below.
I have my prime plugged in. I power off using CWM. Then I hold lower volume and power, it turns on. Then I hold volume up. It goes back into CWM. So I don't know what to do next.
I'm not sure how to proceed from here or exactly if there's some kind of method to "confirm" that I am unaware of.
Yes, I'm aware that I voided my warranty. I'm hoping that someone at XDA can walk me through fixing this.
Thanks for anyone who is willing to help.
@all
flashed today the file from this post (US Full OTA .14):
http://forum.xda-developers.com/show...&postcount=387
Use this Method:
EP201_SDUPDATE.ZIP (Rename extracted ZIP-File)
CONFIRM:
Works ONLY with MicroSD CARD (REMOVABLE - ROOT).
Inernal Memory FAILURE - Search only for REMOVABLE RECOVERY
HOW TO:
Shutdown Device
HOLD LOWER VOL. + POWER
CONFIRM within 5 Seconds with HIGHER VOL.
Works perfect...think with this method you can flash every FULL OTA - FW from EVERY SKU (without ROOT ???)
shinichikey said:
when i hold the power+ lower volume, It went straight to CWM, what I am suppose to do in there?
Click to expand...
Click to collapse
Try pointing it to the location where you put the stock rom file at. Then flash it. I added some stuff in your thread if you can't get it to work.
you supposed to put the zip file into the removable microsd card, so you just need to use an adapter or somehow put the file into the microsd card, but yeah, i tried it, but it did nothing...
---------- Post added at 01:06 AM ---------- Previous post was at 01:03 AM ----------
I did try to locate and install the zip file using CWM, it stated successfully but after reboot, it went straight into CWM again
I stuck a microsd card in the slot, but my Prime is not recognized by Windows. So I can't copy and paste the zip file onto the microsd card to install the zip. Any ideas how to apply this fix given my situation. Thanks again to anyone who is willing to help.
Both of you post your issue in this thread http://forum.xda-developers.com/showthread.php?t=1510983
They can help you in there. We had someone earlier who had same problem and was walked through what to do.. you can also pm Doltaplex(misspelled) or Diamondback. They can help.
use an adapter so you can connect your microsd card without the tablet, or you can use adb to push the file into the memory card, that's how i did, but even if you can get the file into the tablet, you cant still fix the problem, that's my case...
richteratmosphere said:
I stuck a microsd card in the slot, but my Prime is not recognized by Windows. So I can't copy and paste the zip file onto the microsd card to install the zip. Any ideas how to apply this fix given my situation. Thanks again to anyone who is willing to help.
Click to expand...
Click to collapse
He means use your computer to put the file on root of microsd card. Then put card inside of prime. Then do those previous steps. Prime doesn't need to be hooked up to PC for this. Microsd card need to go inside prime with the stock rom file on root of it.
---------- Post added at 01:19 AM ---------- Previous post was at 01:11 AM ----------
I posted in that new thread I linked you to. They should know you on the way. State your issues in thatthread. Someone there will get your primes back running again.
I think I found this solution that doktaphex posted in this thread:
http://forum.xda-developers.com/showthread.php?t=1511839&page=5
"kmdm: it'll clear the headers for the blob update from the staging partition
kmdm: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
kmdm: remove the boot-recovery command
kmdm: right so, I'd reboot now
doktaphex: You sir are a f#cking genius"
Unfortunately, I don't know how to implement this. If someone could help, it would be appreciated.
I have less than 10 posts, so I can't post in the ClockworkMod Recovery 5.5.0.4 for TFP developer thread.
richteratmosphere said:
I have less than 10 posts, so I can't post in the ClockworkMod Recovery 5.5.0.4 for TFP developer thread.
Click to expand...
Click to collapse
Guy in other similar thread in this section fixed his prime n got out of CWM loop. Check that other thread. I told him you probably need his help.
My Transformer crashes also during the .14 update and I have not unlocked the bootloader, there are some other users on swedroid also having these problem. Does anyone have a clue about what could be wrong?
Sent from my Transformer Prime TF201 using Tapatalk
Uppenberg said:
My Transformer crashes also during the .14 update and I have not unlocked the bootloader, there are some other users on swedroid also having these problem. Does anyone have a clue about what could be wrong?
Sent from my Transformer Prime TF201 using Tapatalk
Click to expand...
Click to collapse
There's a new update coming that should fix your issue. There's a thread on it in general section. People are testing out a beta fix now. Everything goes well n they will release it asap.
richteratmosphere said:
I think I found this solution that doktaphex posted in this thread:
http://forum.xda-developers.com/showthread.php?t=1511839&page=5
"kmdm: it'll clear the headers for the blob update from the staging partition
kmdm: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
kmdm: remove the boot-recovery command
kmdm: right so, I'd reboot now
doktaphex: You sir are a f#cking genius"
Unfortunately, I don't know how to implement this. If someone could help, it would be appreciated.
Click to expand...
Click to collapse
I ran into the same problem - here is what I did (on Linux mind you) to use this info to fix.
1. Download and extract the Android SDK from Google. You will need the file "adb" which is located in the platform-tools folder when you extract the sdk
2. Boot into CWM Recovery
3. Connect your prime to your PC via the USB cord that came with it (make sure no other android devices are plugged in)
4. Open Terminal on your PC and go to the platform-tools folder that you extracted with the SDK.
5. Enter the command
Code:
sudo ./adb start-server
- you'll get a message telling you its connected or whatever
6. Next, enter the command
Code:
adb devices
- you should see the prime listed as "recovery" or somethign along those lines
7. Enter the command
Code:
adb shell
- this will put you into command line for your prime
8. Now you can start entering in the commands from the post.
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
then press enter.
9. Next,
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
then press enter again.
10. Now you can unplug the prime and reboot your prime through "Reboot Now" in CWM
See if that helps. It worked for me.
If you have no idea what unlocking the bootloader and rooting your tablet does, you probably shouldn't do it. I mean, that's why HTC gives a big legal warning because there are too many people that just click on **** and wonder why things break.
If you still want OTA update, you can do that with just root. If you unlock the bootloader, there is no more OTA for you. You have to learn to flash custom roms and what caches to clean. There is a plethora of information on XDA on how to do this stuff.
Not trying to sound like an ass, but before I ever rooted / unlocked my phone, I talked to a friend who knew what they were doing and did a lot of reading up on it.
teknomar7 said:
If you have no idea what unlocking the bootloader and rooting your tablet does, you probably shouldn't do it. I mean, that's why HTC gives a big legal warning because there are too many people that just click on **** and wonder why things break.
If you still want OTA update, you can do that with just root. If you unlock the bootloader, there is no more OTA for you. You have to learn to flash custom roms and what caches to clean. There is a plethora of information on XDA on how to do this stuff.
Not trying to sound like an ass, but before I ever rooted / unlocked my phone, I talked to a friend who knew what they were doing and did a lot of reading up on it.
Click to expand...
Click to collapse
I agree. I will say, however, that I never attempted to do OTA after unlocking my bootloader so I'm not sure what happened. Freaked me out a bit, but glad the solution was the same for me as for those who attempted OTA after unlocking.
Related
This post is just my attempt to help less savvy users go from a fully locked/unrooted Rezound to unlocked, rooted, and running Ziggy's kernel. Really, this is just a list of links that should be followed in order (and maybe a few extra notes for clarification). Be sure to thank the respective devs for their efforts.
As of the time I'm writing this, there is no way to get the phone back to "Locked" once you've "Unlocked" it. The phone will show "Re-locked" if you relock it so know that until someone figures something out, Verizon WILL KNOW that you've unlocked your phone once you do it IF they bother to check and know how. It's your gamble, but to date, I've not heart of Verizon detecting root/unlock and refusing service to one person I can confirm. Said another way, you can "un-root" your phone (remove su and SuperUser), but that won't hide the more important fact that you've unlocked it. Consider this before continuing. Unlocking VOIDS YOUR WARRANTY. You accept responsibility for following this guide. Myself and other devs only provide information.
In general, here is what you will be doing:
Using the HTCDev.com site to submit your phones key and get an unlock.bin that you can use with fastboot to unlock your phone. NOTE: This WILL WIPE YOUR PHONE. I suggest using a temp-root method to first install Titanium or similar app, and do a app/data backup. This way when you're done, you can restore apps/data and be just about where you were when you started, only better.
Use the zergrush perm-root method to obtain permanent root and install SuperUser.
Install a customer recovery that will allow you to do a nandbackup and then install other roms/kernels (needed for the next step also).
Install Ziggys custom kernel which addresses some important issues for this phone and provides some other nice features.
NOTE: If you intend on flashing one of the newer ROMs ("newer" as of 2012-03-24) that require the 3.11.602.22 firmware, use Scott's directions HERE then come back and continue.
Now for the actual steps:
UNLOCKING - First visit THIS post for detailed instructions on how to unlock your device. This is required for permanent root and just about everything else following. This WILL VOID your warranty as the post says. This will also WIPE your device so again, I suggest first using THIS temp-root method so you can install an app like Titanium Backup to backup your apps/data.
PREPARING ADB - Once you have unlocked and your phone has rebooted, hit the home key to skip HTC Setup (no point doing it just yet really). Now hit, menu, settings, Applications, and check "Unknown Sources" (for good measure), then "Development" and check the box "USB debugging". I recommend then backing up a screen and un-checking "Start automatically", but that's my preference, not a requirement.
CONFIRMING ADB - At this point, I'm going to assume you already have ADB installed and known how to invoke the command because there are at least 9,999,999 tutorials online explaining this. Go ahead and open a cmd prompt and run "adb kill-server" and then "adb devices" and ensure that your device (if you see one, then you should be fine) shows up.
ROOTING - Now visit THIS thread and hit the less-than-obvious link titled "Download - OneClickRoot" to download the zip containing the tool. Follow the directions in that thread to permanently root your phone.
Boot fully into Android before proceeding.
RECOVERY
PREPARE RECOVERY.IMG - Visit THIS thread and download the attachment. Extract "recovery.img" from the zip and place it in a folder from which you can successfully run ADB. NOTE: If you haven't already, putting the adb.exe files folder in your PATH will let you run adb from anywhere. Same goes for fastboot. This makes life with Android tweaking/hacking MUCH easier.
FLASH RECOVERY 1/2 - Now "CD" into the folder (HERE you can find more about the CD command) with recovery.img and run the following command: "adb reboot bootloader". Once the phone has rebooted into the bootloader (a white screen with text menu, should say "*** UNLOCKED ***" at the top now). In white with a red background you should see "FASTBOOT USB". If so continue, if not, ask for help
FLASH RECOVERY 2/2 - The moment you run the following command, you should see a vertical bar on the upper-right hand corner of your phones screen. If so, it's working as expected. In your CMD window, run the following command "Now "CD" into the folder with recovery.img and run the following command: "fastboot flash recovery recovery.img"
REBOOT TO RECOVERY - If you have't touched the volume keys, "BOOTLOADER" is selected and pressing power will take you to the bootloader where you can then use the arrow keys to select "RECOVERY" and again press the power button to get into recovery. Otherwise, reboot any way you see fit and once running, use "ADB reboot recovery" to get into recovery easily.
KERNEL
DOWNLOAD FILES - First download the two files from THIS post (NOTE: The OP most may end up with more updated files, but as of the time I'm writing this, these are the way I suggest).
PUSH FILEs 1/2 - If you haven't already rebooted into recovery, review the previous steps and get your phone into recovery ("ADB reboot recovery" is my preference). Now "CD" into the folder containing the two files downloaded in the previous post. From here, I will use the file names as they were when I downloaded. Yours could be slightly different so adjust accordingly. In the recovery use the volume keys to navigate to the "Mounts" menu and then "Mount /sdcard". Use the Power button each time to select the menu option.
PUSH FILEs 2/2 - Now from your CMD window (the one in the folder containing the two kernel files), run the following commands: "adb push FlashMeInRecovery.zip /sdcard/" and then "adb push PH98IMGZIGGYUNSIGNED.zip /sdcard/PH98IMG.zip".
FLASH FILE 1/2 - Now use the back arrow (the capacitive one) to go back to the main menu and then select "Flash zip menu" and then "Choose zip from sdcard". You'll then get a list of sdcard contents. The file is likely toward the bottom. Select "FlashMeInRecovery.zip" and follow the directions to confirm flashing.
FLASH FILE 2/2 - Select the "Return" menu option, then "Developer Menu" and then "Reboot to bootloader". By default "BOOTLOADER" is already highlighted and you just need to use the power button to select it. The phone will now scan the SDCARD for "PH98IMG.zip" and when it finds it, you will be prompted to Press "<VOL UP> Yes" to flash the files.
If you get the notorious "MainVer Error", use one of the following guides to get past the error. NOTE: Neither of these are for the faint-of-heart and the first I consider easier, does carry some real danger if done incorrectly.
Option 1 - Follow the guide HERE <-- Requires the use of a HexEditor and one is recommended if you don't have a preferred one yet.
Option 2 - Follow the guide HERE <-- Requires modification of the PH98IMG.zip you're trying to flash and sometimes this can be problematic. Either way, it provides an excellent description of why the error occurs.
FINISH - Once the 2nd kernel file is flashed and you're prompted, press power to reboot. After your phone is running again, use the following command to rename the kernel file so it doesn't cause you trouble later in the bootloader (but still keep it handy): "adb mv /sdcard/ext_sd/PH98IMG.zip /sdcard/ext_sd/PH98IMGZIGGYUNSIGNED.zip"
If this guide has helped you and you want to show thanks, just hit the "Thanks" button at the bottom of this post. It's not a donation or anything like that, just a counter used here on XDA
I will try to keep this post refreshed as newer files become available, as things get easier, or things change. If you see an error/typo/concern with these directions, PLEASE PM me and don't muddy up the thread. If YOU will do this, "I" will not only try to maintain the post, but I will also try to add/maintain an FAQ post as needed.
Btw, in case you recognize me and are wondering why I've posted here, it's because my site is dead due to childish drama, I still want to help the community and this seems the most reasonable way to do so for now.
EDITS:
20111230_1804 - Added a hint and link about the "CD" command for users who aren't familiar with "DOS" like commands.
20120101_1923 - Added a direction to boot into Android after rooting.
20120101_2325 - Added warning about unlock/relock and warranty in BIG RED text.
20120208_1709 - Added instructions on how to handle the "MainVer" error.
20120324_1636 - Added note about using 3.11.602.22 based ROMs and linked to Scott's (CleanROM) directions.
Great guide, thanks! Worked just fine and wow this thing is fast as BALLS
Using SetCPU to tweak and monitor, any clue on what the best governor is for this kernel?
EDIT: Reading original post about kernel from Ziggy, "lagfree" governor is available, using that now.
Thanks!!!!!
may i flash kernels on custom rom
or has to be stock rooted?
qudwis said:
may i flash kernels on custom rom
or has to be stock rooted?
Click to expand...
Click to collapse
this kernel is based off of the one made for gingerbread, so as long as the ROM you're running is a Gingerbread ROM, you can, or should be able to use this kernel with it.
*EDIT* I believe it may matter whether the ROM is Sense or AOSP based as well. currently we only have sense roms so it doesnt much matter, but it will down the road.
one more question.
i have cwm for recovery. since cwm don't have developer menu,
do i need to change to Amon Ra recovery?
and if i do, how do i change?
The guide is clear, succinct, and accurate. Everything worked perfectly - thanks so much.
I could've got so much more work done over the last two days if I had a tutorial like this! Untold hours have been spent combing these boards to piece together this whole process. Thanks for taking the time to do this for everyone.
Seemed to work!
I only did the recovery / kernel part since I had done the rest previously. For some reason it partially wiped my phone storage and SD card. Directories are there, but nothing is in them. No idea what happened, but oh well.
At least now I can start messing with stuff.
How do you unroot from the HTCdev method? I need to return my Rezound and get a different one tomorrow. Can someone please point to the correct guide or tutorial? Thank you very much!
-brett
bal1985 said:
How do you unroot from the HTCdev method? I need to return my Rezound and get a different one tomorrow. Can someone please point to the correct guide or tutorial? Thank you very much!
-brett
Click to expand...
Click to collapse
Unrooting is just a matter of deleting "su" and uninstalling SuperUser, but it will hardly matter since your device will still be marked as "re-locked" if you use fastboot to relock it. There's no way at this point to hide that it's been tampered with and that's why I and most other devs have made such a point of clarifying that your warranty will be void one you unlock.
On the other hand, I can tell you that out of the 15,000+ users on my site and years in the Android community, I've never ONCE heard of Verizon saying "your device is rooted so we won't...."
Just uninstall SuperUser and do a factory reset/wipe and hope for the best. It's hardly worth their time to check and in the stores, more reps are too ignorant to know to check, let alone how to do it or if they do, they're likely unmotivated to do so since a warranty return won't go against them (unlike a return).
rainabba said:
This post is just my attempt to help less savvy users go from a fully locked/unrooted Rezound to unlocked, rooted, and running Ziggy's kernel. Really, this is just a list of links that should be followed in order (and maybe a few extra notes for clarification). Be sure to thank the respective devs for their efforts.
FLASH FILE 1/2 - Now use the back arrow (the capacitive one) to go back to the main menu and then select "Flash zip menu" and then "Choose zip from sdcard". You'll then get a list of sdcard contents. The file is likely toward the bottom. Select "FlashMeInRecovery.zip" and follow the directions to confirm flashing.
FLASH FILE 1/2 - Select the "Return" menu option, then "Developer Menu" and then "Reboot to bootloader". By default "BOOTLOADER" is already highlighted and you just need to use the power button to select it. The phone will now scan the SDCARD for "PH98IMG.zip" and when it finds it, you will be prompted to Press "<VOL UP> Yes" to flash the files.
Click to expand...
Click to collapse
This looks very clear and helpful. I'm not ready to use it yet, still need to study up on all this root stuff but thanks for posting.
Just wanted to point out that there may be a small and not so important typo. Both flash files are 1/2, shouldn't the second one be 2/2?
I have downloaded both files into my sd card, flashmeinrecovery.zip worked fine. The pmhimg.zip keeps saying aborted. I am running cwm, should I be running a different rom? What can I do to get the pmh zip to work?
I downloaded them via the qr codes, and they are in the download folder on my sd card. I did change the name on the second zip.
You have to put the ph zip in the root of the sd card. Not in a folder
sent from my newly unlocked Rezound
pwned3 said:
You have to put the ph zip in the root of the sd card. Not in a folder
sent from my newly unlocked Rezound
Click to expand...
Click to collapse
Ok, I did that. Now when I get into hboot, it just asks if I want to update, if I do, it updates, what I dont know, then wants me to reboot, and if I boot back into hboot, it wants me to update again. But I can power up normally. Is this correct or am I missing something?
Just reboot normally after flashing
sent from my cm7 rooted fire
And move the file. It will read it every time you go into the bootloader
sent from my cm7 rooted fire
Followed instructions and kernel would not flash. All steps completed without errors and still has same kernel. Any advice?
rainabba said:
Unrooting is just a matter of deleting "su" and uninstalling SuperUser, but it will hardly matter since your device will still be marked as "re-locked" if you use fastboot to relock it. There's no way at this point to hide that it's been tampered with and that's why I and most other devs have made such a point of clarifying that your warranty will be void one you unlock.
On the other hand, I can tell you that out of the 15,000+ users on my site and years in the Android community, I've never ONCE heard of Verizon saying "your device is rooted so we won't...."
Just uninstall SuperUser and do a factory reset/wipe and hope for the best. It's hardly worth their time to check and in the stores, more reps are too ignorant to know to check, let alone how to do it or if they do, they're likely unmotivated to do so since a warranty return won't go against them (unlike a return).
Click to expand...
Click to collapse
so I just unistall SU from the Market? Or do I have to go in with Root Explorer and delete the file? once that is done don't I have to lock the bootloader using that htcdev guide again?
remmy5r said:
Ok, I did that. Now when I get into hboot, it just asks if I want to update, if I do, it updates, what I dont know, then wants me to reboot, and if I boot back into hboot, it wants me to update again. But I can power up normally. Is this correct or am I missing something?
Click to expand...
Click to collapse
Following step 7 specifically prevents you from having to deal with that. So long as the PH file exists in your sdcard root, when you go into bootloader, you will be prompted. Once your running normally, just go follow step 7 and you'll be good to go.
I just went through the unlock and root it is fresh in the mind. These directions ASSUME AN SD CARD IS INSTALLED to the tablet and a WINDOWS OS!
Downloads, get them and put them in a folder on your computer:
Asus Unlock Tool download link from ASUS:
http://support.asus.com/Download.as...ck_Device_App_V6.apk#UnLock_Device_App_V6.apk
Fastboot EXE:
I got fastboot.exe when I downloaded Ultimate Backup Tool from here:
http://goo.gl/iOUwe
Unzip it so you have fastboot.exe
TWRP:
Get TWRP for TF201Jellybean, here is their page I have posted the download link below:
TWRP Page
On that page are instructions including a download link.THIS LINK IS FOR TF201 RUNNING JB BOOTLOADER ONLY! DO NOT USE IT IF YOU ARE NOT SURE WHAT YOU ARE RUNNING STOP NOW!
TWRP Download for TF201 running STOCK JellyBean OS:
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.1.0-tf201-jb.blob
MD5 Checker:
When TWRP is downloaded you can compare the MD5 hash of what you downloaded to confirm it is the a good download. If you don' do this and flash a bad copy of TWRP your tablet is now garbage. You can find something like winMD 5 generator:
http://www.winmd5.com/download/winmd5free.zip
Unzip the above download and run WinMD5.exe to generate an MD5 hash of the TWRP file you downloaded. Compare it to what it says the files MD5 hash is on the download web page. If I remember correctly I had to manually type in the MD5 hash from the page because it was an image I couldnt just copy. Or you can just visually verify with the one generated by winmd5.
Once the MD5 is verified rename the TWRP you downloaded to TWRP.blob just to shorten the name for scripts later and copy it to where you have fastboot unzipped.
ADB command:
I got ADB from several sources but this "root method" http://forum.xda-developers.com/showthread.php?t=1886460 from bin4ry is what I have been using: (And no, it doesnt work for the prime because the exploit he uses to run the device in emulator mode doesnt work for us)
Download bin4ry's root tool to get the ADB file
SuperSU:
Finally download SuperSU zip file from:
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
How To Use The Downloads:
Unlock Device:
First we need to unlock the device. Copy the unlocker APK to the root of your SD card for your tablet via the USB cable or putting the SDCARD in to your computer directly or with the ADB PUSH command if you know how to do that. Run the built in file explorer on our tablet and browse to the SD card (/Removable/MicroSD). Tap the Unlock APK to install. Once installed run the Icon for the unlocker and follow directions. There are several warnings etc.. You will need wifi connected and it will unlock your device and VOID YOUR WARRANTY!.
The unlock will take a few minutes and reboot one or more times. When it is successfull you will see a notice on device boot up that says the device is unlocked.
Flash TWRP:
Once unlocked, power it off. Once off power it on by holding BOTH volume down and power buttons. When you see the menu appear the first option is RCK. press Volume Down to change the cursor to be over the USB logo (two presses of the button) and press volume up. This puts your device in fastboot mode
Back on your computer you should hopefully see a successfull driver install for fastboot. I got all my drivers from downloading and installing the Android SDK so you may or may not need to do that. Android SDK
If all is prepared and you are in fastboot with drivers loaded:
On your computer hold shift and right click on the folder where fastboot and the twrp.blob file are and you will see a context menu. Click on "Open Command Window Here" (Vista + only or if you installed powertools on 2000/XP)
If you don't get the command window here option then you will have to open a command prompt. Open the run dialog and type CMD and hit enter. This will get a dos command windows. Use the change directory (CD) command to change the current folder in the DOS window to where your fastboot file and TWRP.blob are.
In the command window copy and paste the following line:
fastboot -i 0x0b05 flash recovery twrp.blob
and hit enter
Let it runs its course. When done I had a black screen with ASUS in the middle and a blue-ish bar across the bottom that was filled. I had to hold power until it rebooted. ( I waited about 5 minutes with that blue bar filled before looking up onilne to power off. I would recommend waiting a couple of minutes to be sure/safe)
Install SuperSU:
Once I confirmed my Stock OS loaded I copied the Super SU zip file we downloaded above over to the device via the USB cable to the root of my SD card, or by inserting SDCARD in to my computer and copy it over to ROOT of card or with ADB PUSH. Once the copy completes shutdown the device again.
Once off, power it on and press and hold both the power buttons and volume down again. When the menu appears you should already have RCK (recovery) highlighted so press volume up to load TWRP recovery.
OPTIONAL - BACKUP IF YOU WANT TO:
In TWRP there is a backup option. I chose to backup to my SD CARD and made sure to backup everything and generate an MD5. It takes a While but you can flash this back ANYTIME to put your device back to the STOCK JB OS without root. You can use the backup anytime you like to preserve your devices COMPLETE STATE. Just use the restore option in TWRP to put it back.
To flash root, once TWRP loads, the top left option is "Install" tap that.
You will see a few choices, select the radio button to install from SD card (external source it may say). Tap the super su zip file: Superuser-3.1.3-arm-signed.zip to choose it.
Slide the slider at the bottom to the right.
This will flash superSU to your device. When successfully done, reboot (flash should only take a few seconds).
When you boot up SuperSU is installed.
To test root with ADB:
Your tablet must be plugged in to the USB port of the computer of course.
If you installed the SDK tools ADB is there or use the one from bin4ry's root tool as follows:
Unzip the downloaded root tool from bin4ry mentioned above. Use the shift and right click method in explorer on the "STUFF" folder for the unzipped files or use the command windows to change directory of the unzipped folder and further in to the "STUFF" folder.
In the command windows type:
adb shell
<hit enter>
after a few seconds you should see a $ prompt and your are in to the console of your tablet.
Type:
su root
<hit enter>
Superuser will prompt you to grant root permissions and I set the setting so it doesnt prompt me every time.
Your prompt will change to # and thats it, you are root.
I don't seem to have the command sudo on my tab so every time I want root in a terminal I type that su root to get the # prompt.
Any apps that need root can now ask for it, you will get that same "Grant" prompt and do so if that is what you want.
ADB will now yield Root when you type: SU root and hit enter (grant root privs in the popup)etc...
Final thoughts:
There are other ways to copy content to the device such as using ADB PUSH etc... and I am sure this could be mostly if not all scripted but now that my tablet is rooted I am not going to write one and flash SuperSU over and over and possibly screw up my device. Follow the directions above and you will be successfull. If someone wants to write a script based on the above knock yourself out.
I HIGHLY recommend checking ALL MD5 hashes of downloads to confirm you got what you were supposed to. This will help prevent bricks.
Nice to see another guide on unlocking and flashing TWRP
McJesus15 said:
Nice to see another guide on unlocking and flashing TWRP
Click to expand...
Click to collapse
I was thinking a "how to root without unlock" one should be next....
hx4700 Killer said:
I was thinking a "how to root without unlock" one should be next....
Click to expand...
Click to collapse
Haha we have to wait for the amazingly smart people here to find an exploit for Jelly Bean. Although unlocking and flashing a custom rom is the way to go
Sent from my Zio using xda app-developers app
McJesus15 said:
Haha we have to wait for the amazingly smart people here to find an exploit for Jelly Bean. Although unlocking and flashing a custom rom is the way to go
Sent from my Zio using xda app-developers app
Click to expand...
Click to collapse
Yeah, the How to was going to be:
Step1) You can't.
So you finally did it... Did your warranty run out or did the frustration finally get to you?
I'm still holding off for now. In a way its a good thing an exploit hasn't been found, it means google have made the system fairly secure.
Next weekend I'm going to give finding an exploit one last red hot go. Failing that (and I'm sure i will) I'll be joining you.
abazz said:
So you finally did it... Did your warranty run out or did the frustration finally get to you?
I'm still holding off for now. In a way its a good thing an exploit hasn't been found, it means google have made the system fairly secure.
Next weekend I'm going to give finding an exploit one last red hot go. Failing that (and I'm sure i will) I'll be joining you.
Click to expand...
Click to collapse
I wanted to flash the Energy rom because of the near double quadrant scores people were posting. Little did I (or the chef) know that the Kernel was set to 1.8GHZ and constantly running 1.6. CPU throttling did little to inhibit that and even if you set it back to 1.4 it still ran 1.6 when max CPU was needed The back cover temp went from 90 deg while playing an interactive game for 20 minutes to 108.5 deg when playing the same game for 20 minutes. I had to think that was compromising stability and longevity as well as battery life so I flashed back my stock backup I made via TWRP and rooted as above.
I wouldnt mind going back when the kernel is more controllable. I'm actually playing with backtrack 5 now that I am rooted and EDS with mounts to truecrypt volumes so glad I am rooted, would have rather not voided the warranty
I think the policy should be that if you unlock things like the screen and wireless etc.. should still be covered but since they can't control overclocking etc... those kinds of issues are not.
Between 3 kids events, Holiday stuff I barely have the time to do the things I want to do let alone invest time in hacking this device =/
Thanks for the guide. Picked up a second hand Prime + Dock online with a locked boot loader. Following your guide I had it unlocked, rooted, and with CM10 in about half an hour or less.
Thanks!
Sent from my One X using xda premium
jetpackjeff said:
Thanks for the guide. Picked up a second hand Prime + Dock online with a locked boot loader. Following your guide I had it unlocked, rooted, and with CM10 in about half an hour or less.
Thanks!
Sent from my One X using xda premium
Click to expand...
Click to collapse
Glad it was helpful.
I guess I need to go look in to CM10, I see plenty of people using it and talking about it.
hx4700 Killer said:
Glad it was helpful.
I guess I need to go look in to CM10, I see plenty of people using it and talking about it.
Click to expand...
Click to collapse
As far as I know the kernel issue is fixed. Androwook never had the issue. It'll still get hot but not enough to cause concern
Sent from my Zio using xda app-developers app
worked for me :thumbup:
Sent from my Transformer Prime TF201 using xda app-developers app
And for me, didn't get much easier - or idiot proof
Thanks worked perfectly, I'm on CM10 now
Btw, you should change this line (because it's kinda wrong):
Let it runs its course. When done I had a black screen with ASUS in the middle and a blue-ish bar across the bottom that was filled. I had to hold power until it rebooted. ( I waited about 5 minutes with that blue bar filled before looking up onilne to power off. I would recommend waiting a couple of minutes to be sure/safe)
For this part the blue bar across the bottom did show up but not the ASUS logo, for me the tablet stayed on the same page with the USB logo and the other stuff and the blue bar across the bottom (not the Asus logo).
wrong thread
I have always been locked, and RMAed previously. I was able to successfully do this last night, thanks for the links.
Yay! After reading the forums and triple checking every thing I finaly got ROOT!
Thanks! Now I'm off to install the Energy Rom and hopefully enjoy GTA on a 42" TV with a USB controller
Fail
Doesn't work for me. I'm trying to switch to TWRP from an ever flakier CWM that won't do a backup. I'm already unlocked and rooted but still with stock ROM (which won't update any more because I'm rooted.)
The fastboot flash finishes ok but when I try to boot into recovery I get the message that it is loading the recovery kernel and then it just boots into Android. I have no recovery at all now which is kind of scary.
(God I hate this device for noodling with. Whenever you miss a beat you're looking at a 5 minute uninteruptable boot/shutdown cycle to try again. Everything outside of the Andorid zone itself is so baroque, archaic and intricate that feels like Windows 1.0. More than once mine has come within a nat's ass of being introduced to the wall at high velocity.)
---------- Post added at 11:59 PM ---------- Previous post was at 11:28 PM ----------
DonGateley said:
Doesn't work for me.
Click to expand...
Click to collapse
Oh, how utterly silly of me. Because I rooted long ago I didn't get the JB upgrade OTA so I'm still with ICS. The blob I needed was
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.3.0-tf201-ICS.blob
(At least I determined that flashing the JB blob onto ICS is not catastrophic.)
Maybe I'm not the only one in this state. It might be a good idea in the text to tell others of the ICS option.
The reason I'm here is that I want to install CM10 so I wanted to back up first. When I do that upgrade I assume this ICS TWRP will cease working and I will then need to fastboot flash the JB blob, right? Or might I have a "Can't get there from here" kind of problem?
Thanks for the links and write up.
2 questions.
Do I need an SD card or is the internal storage ok to use.
And, what part of this process roots the device?
Thanks!
**EDIT**
Never mind, I am a bonehead. I had my prime replaced due to a camera defect, so they shipped me a new one running JB.
So I have been away from teh forum a couple of months...didn't realize a way to get around locked, un-rooted, JB had been found.
Thanks again!
Sent from my Transformer Prime TF201 using xda app-developers app
Thanks for writing this up, I can't thank you enough. About a month ago I hard bricked my prime and had to send it in to Asus to have it repaired (thankfully I didn'y get charged). I tried installing twrp but didn't check the md5; this was well written. Wish I could give you a hug.
I know maybe some people will think I'm dumb now or something... But I want to ask before I begin and maybe brick it
So this really WORKS with the LATEST OTA update from Asus? I searched everywhere for days/weeks/months already and found this today so I'm a little bit sceptic, hope you understand me.
Hi guys, over the past few weeks, I have noticed that many people are having problems rooting their Jetstreams. So because of this, I thought I would put together an all in one guide to help alleviate everyone's problems.
So what this will show you how to do:
Unlock the bootloader
Flash a custom recovery
Grant root access
Prepare the device for S-OFF
Included files:
HTC Drivers
ADB
Fastboot
TWRP 2.4.1.0
SuperSU 1.51
Note: This guide is for windows only
Ok, so lets begin:
Download attached zip
http://www.mediafire.com/download/ao1ykdpx5jn2uni/Root_HTC_Jetstream.zip
Extract the zip to an appropriate place on your computer
Install the HTC drivers
Do so by double clicking the HTCDriver_4.2.0.001.exe from the zip
Run the RUU if needed
I am assuming you are on a completely stock HTC Jetstream with no modifications what so ever. I am also assuming you are on the latest software 1.30.502.1 for AT&T users or 1.26.631.4 for Rodgers users. If you are not, please download and run the latest RUU from the following website:
http://forum.xda-developers.com/showthread.php?t=2094375
Please note that running the RUU will completely WIPE your device of all personal data, so backup accordingly
To run the RUU, make sure the Jetstream is turned on and is fully booted into Android
Make sure "USB Debugging" is enabled under development settings
Make sure "Fastboot" is disabled under power settings
Simply attach the Jetstream to your computer with the appropriate USB cord
Double click on the downloaded RUU .exe file to run the program
If for some reason you cannot boot into Android, you can do the following:
With the device turned off, hold the volume down button and simple press the power button for a second or two
The device will boot into the bootloader, from there use the volume buttons to navigate to fastboot and the power button to select
Once in fastboot, connect the device to the computer with the USB cord and then double click the downloaded RUU .exe
Now lets unlock the bootloader
Please note that unlocking the bootloader will also WIPE your device
Go to http://www.htcdev.com/
Create an account if you do not already have one
Click on "Unlock Bootloader" and then "Get Started"
In the drop down box, select "HTC Jetstream"
Agree to all the legal terms
Follow all the instructions to obtain your unlock token
To easily do this:
Make sure "USB Debugging" is enabled under development settings
Make sure "Fastboot" is disabled under power settings
Connect the device to the computer with the USB cable
Navigate to the extracted folder of the attached zip
Hold the shift key and right click in the folder, then select "Open Command Window Here"
Type the following in the command window
Code:
adb reboot bootloader
Once the device has booted into fastboot, type the following in the command window
Code:
fastboot oem get_identifier_token
Copy the appropriate text according to the website and submit it
You will then be emailed an "Unlock_code.bin" and a link to continue the unlock process
Download the "Unlock_code.bin" and place it in the extracted folder from earlier
Now type the following in the command window
Code:
fastboot flash unlocktoken Unlock_code.bin
On the device you will be prompted to unlock the device, use the volume keys to navigate to "Yes" and use power to select
The device will reboot back into Android
Now lets flash a custom recovery
Connect the device to the computer with the USB cable
In the extracted folder open a command window by holding the shift key, right clicking, and selecting "Open Command Window Here"
Type the following in the command window
Code:
adb reboot bootloader
Once the device has booted into fastboot, type the following into the command window
Code:
fastboot flash recovery htc_jetstream_twrp_recovery_2.4.1.0.img
Once the custom recovery has been successfully flashed, type the following into the command window
Code:
fastboot reboot
The device will then boot back into android
Now lets get root
Connect the device to the computer with the USB cable
Copy the "SuperSU-v1.51.zip' to the root of you SD card
Go to the extracted folder, hold the shift key, right click, and select "Open Command Window Here"
Now type the following into the command window
Code:
adb reboot recovery
While at the recovery main menu, select the wipe option and wipe cache and dalvik cache
Next go back to the main menu and select install
Navigate to the SuperSU zip we placed on the SD card and flash the zip
Once it flashes, go back to the main menu and reboot back into system
The device will boot back into Android and the device will now be rooted!
So what now?
After completing the step above, you device should have an unlocked bootloader, and custom recovery installed, and also have root access. After having all of this you may now go on to install any custom ROMs you may want, however, I would recommend obtaining S-OFF to give yourself full control over your device.
This following link should help to explain what S-OFF is exactly:
http://forum.xda-developers.com/showpost.php?p=42455824&postcount=1
This next link is to the JuopunutBear S-OFF method:
http://forum.xda-developers.com/showthread.php?t=1906353
People I would like to thank:
DoomLoRD - for his initial work with rooting the HTC Jetstream
jmz - for giving us a custom recovery and hosting all the RUUs for us
TeamWin - for TWRP
Chainfire - for his amazing work with Android and SuperSU
Fuses and the rest of Team Unlimited - for giving us an S-OFF method
Disclaimer:
Just to be clear, unlocking and rooting your HTC Jetstream voids your warranty, so anything you do to it is your decision and I am in no way responsible for anything that happens to your device
great work!
@DNarsingh
Windows 8 64 finally can ADB to Jetstream and Sensation XL.
Thanks for driver file HTCDriver_4.2.0.001.exe containing within the zip you attached. The driver within htc_sync_setup_3.3.10.exe couldn't seem to get through.
Did a factory reset on my jetstream, and lost root. When I used CWM for recovery, I tried re-rooting using the guide in this thread. After another factory reset, root was still there, so I handed the jetstream to its new owner. However, the new owner has told me that the pen icon doesn't show up when using the pen. He did another factory reset (which took longer than usual), but still nothing. Anyone know what went wrong?
Notontherugman said:
Did a factory reset on my jetstream, and lost root.
Click to expand...
Click to collapse
I've never heard of a factory reset breaking root. The components that enable root usually exist on the /system partition and it is untouched by a factory reset.
The other root method (that I am unfamiliar) with is an insecure kernel. I don't know how this works, but I am pretty sure that a factory reset should not break it.
finniest said:
I've never heard of a factory reset breaking root. The components that enable root usually exist on the /system partition and it is untouched by a factory reset.
The other root method (that I am unfamiliar) with is an insecure kernel. I don't know how this works, but I am pretty sure that a factory reset should not break it.
Click to expand...
Click to collapse
I'm not a dev, and have just been following how-tos on XDA up to now (from back in the days of HTC HD2); therefore, I can't give details since I am inexperienced.
After the factory reset, Titanium Backup was denied SU, I could not browse the root directories/folders and all the software that needed root to work would not.
My question still stands: the pen icon won't show up. Anyone know what went wrong or what he may be doing wrong? In desperate need for help.
Notontherugman said:
After the factory reset, Titanium Backup was denied SU, I could not browse the root directories/folders and all the software that needed root to work would not.
Click to expand...
Click to collapse
Did you try to install the superuser app that you were formerly using from the market? My guess is that you lost the /data/app/su.apk that manages superuser, but that the binary is still in your /system/xbin/su directory somewhere. You probably removed the seemingly redundant /system/app/su.apk while using Titanium Backup, but are now left without a copy of it.
Notontherugman said:
My question still stands: the pen icon won't show up. Anyone know what went wrong or what he may be doing wrong? In desperate need for help.
Click to expand...
Click to collapse
If you are using Hive ROM then the pen icon will not appear, but the pen will still work with most apps. If you are using a different ROM then I really have no idea why the pen icon is not working. Are you certain that the pen battery still has a charge?
finniest said:
If you are using Hive ROM then the pen icon will not appear, but the pen will still work with most apps. If you are using a different ROM then I really have no idea why the pen icon is not working. Are you certain that the pen battery still has a charge?
Click to expand...
Click to collapse
Not using any ROMs.
I had removed most of the bloatware when I was using it, but the pen icon was there and I could use it just fine (before the factory reset).
Now, after the factory reset and the root method above, he tried his Flyer's pen on the Jetstream as well, so the battery is not a problem.
Notontherugman said:
I had removed most of the bloatware when I was using it, but the pen icon was there and I could use it just fine (before the factory reset).
Click to expand...
Click to collapse
Try using logcat to diagnose the problem. I suspect something will show up during boot or when you press where the pen icon should be.
http://www.xda-developers.com/android/help-your-developers-pull-a-logcat-when-issues-arise
I got the Jetstream back today.
I had managed to make a backup before using Clockwork Mod.
After the above rooting method, CWM is gone, and I can't use the backup files to restore using TWRP.
The link for CWM is gone. This is becoming extremely frustrating.
Notontherugman said:
I got the Jetstream back today.
I had managed to make a backup before using Clockwork Mod.
After the above rooting method, CWM is gone, and I can't use the backup files to restore using TWRP.
The link for CWM is gone. This is becoming extremely frustrating.
Click to expand...
Click to collapse
I have a copy of the CWM recovery.img. When I get home tonight, I will upload it for you.
I would recommend redoing your backup in TWRP afterward. In my experience, this recovery is a bit more up to date..
DNarsingh said:
I have a copy of the CWM recovery.img. When I get home tonight, I will upload it for you.
I would recommend redoing your backup in TWRP afterward. In my experience, this recovery is a bit more up to date..
Click to expand...
Click to collapse
Definitely.
And thank you!
EDIT: found CWM on an old hard disk. Managed to get ADB working. Restoring should fix most of the problems.
Thanks very much for the post
Sent from my SGH- I317M (Note II) running CM 11 using XDA Mobile App
every thing is ok
my device is fully rooted with twrp recovery and unlocked bootloader
but I have a problem.
I have sim card signal Icon but my device can not confirm simcard
what can I do?
Thanks!
Since I have rooted my device I can no longer access downloads from the google play store. I constantly get RPC:S-7:AEC-0 or -7 errors. I have tried all the tricks on various
forums but have had no luck. Do you have any fixes related to the jetstream?
Thanks, Mike
GROTEU said:
Since I have rooted my device I can no longer access downloads from the google play store. I constantly get RPC:S-7:AEC-0 or -7 errors. I have tried all the tricks on various
forums but have had no luck. Do you have any fixes related to the jetstream?
Thanks, Mike
Click to expand...
Click to collapse
It doesn't sound related to rooting. I would suggest a backup (there are many means of accomplishing this) and then a factory restore. If that doesn't work then install a custom ROM.
rooting issues
i have been trying to root my jetstream so i can get some lift out of it but when i get to the fast boot the system just hangs there any suggestions please if you know a complete way to root a htc from rogers i would love the support thanks
I have a Nabi 2 tablet that I've rooted, installed TWRP, and flash the gapps and a few other tweaks to. It's about to go in for an RMA since the USB and charging ports are both broken. The problem in the USB port is that one of the pins got bent - I don't know how, it looks like the conductor somehow got peeled back off of the plastic. The point is, I have no USB access to the device.
In order to pass the inspection for the RMA, I need to have it stock I can flash the stock ROM by putting it on the SDCard in my laptop then transferring that to the device and flashing it through TWRP. The question I have, though, is whether I can flash the stock recovery with ADB access to it. Every thread I've been able to uncover so far about flashing a recovery requires ADB access to issue the "adb fastboot flash" command. Is there another way to do this?
If the ROM your going to return it with (stock) has the flash image binary then you can use a terminal emulator but I doubt this will work as most often stock ROMs don't. But maybe worth a shot
Otherwise depending on how the tablet and recovery are set up possibly flash the stock recovery through twrp
Would need to know a lot more about your tablet to say for sure how to do it
Sent from my Nexus 4 using Tapatalk 2
Yes. Sometimes I have seen recovery-from-boot.p and install-recovery.sh restore it on first boot after you have restored stock ROM.
If not...
Copy a stock recovery.img to your external SDcard
After restoring your Nabi ROM.
Use TWRP "mount" tab and make sure external_sdcard is checked
Use TWRP "Terminal Command"
dd if=/external_sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
I forget when TWRP add terminal command, if you have an older version you'll have to update it first.(same idea as flashing stock, just get the 2.6.0.0 TWRP image and put on external SD) There are some other methods but I think this is easiest without a functioning USB
aicjofs, thanks!
It could just be my current sleep-deprived state, but this line confused me:
aicjofs said:
Yes. Sometimes I have seen recovery-from-boot.p and install-recovery.sh restore it on first boot after you have restored stock ROM.
Click to expand...
Click to collapse
The way my brain interpreted it says that once the stock ROM is restored, it will automatically restore the recovery on first boot.
I have some part of my brain screaming "NO!" though, so I'm not sure what you were trying to say there. Care to enlighten me?
oh, and I've got TWRP 2.2.2.1, and it does have a terminal emulator, but it's clunky at best.
Dan in SA said:
aicjofs, thanks!
It could just be my current sleep-deprived state, but this line confused me:
The way my brain interpreted it says that once the stock ROM is restored, it will automatically restore the recovery on first boot.
I have some part of my brain screaming "NO!" though, so I'm not sure what you were trying to say there. Care to enlighten me?
Click to expand...
Click to collapse
Yes some have claimed it returned them to stock recovery. That file is only like 300kb though so it can't be the full image as the kernel alone is 4MB+. Maybe it's just the ramdisk, but its too large for that. I can't imagine it works but that's what people have claimed, probably shouldn't have said I have seen because I haven't personally seen it, just heard. I would do the method I talked about and dd the image from TWRP.
All can be recovered without USB port as long as you can boot either Android or TWRP just don't lose both at same time
Ok, thanks I'll try and get it charged tonight, and flash the stock ROM tomorrow and see what happens.
One more quick question - I don't have a recovery.img file. I have recovery.emmc.win and mmcblk0p1.img - they're both 8,192kb. I'm assuming I would either rename the first to recovery.img, or use the second and dd it into /dev/block/platform/sdhci-tegra.3/mmcblk0p1
Am I on the right track?
Dan in SA said:
Ok, thanks I'll try and get it charged tonight, and flash the stock ROM tomorrow and see what happens.
One more quick question - I don't have a recovery.img file. I have recovery.emmc.win and mmcblk0p1.img - they're both 8,192kb. I'm assuming I would either rename the first to recovery.img, or use the second and dd it into /dev/block/platform/sdhci-tegra.3/mmcblk0p1
Am I on the right track?
Click to expand...
Click to collapse
Yes on the first but No on second. The way you have it won't work but you are close. for dd the "if" = input file, and the "of" = output file. Both are your input file. recovery.emmc.win = mmcblk0p1.img and an image of recovery partition basically a different name for the same thing.(the same as boot.emmc.win = mmcblk0p2.img an image of boot partition) In this case the input is either of those 2 files, and the output is the recovery partition.
So you could use any of the following it's just changing the name of the input
dd if=/external_sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS (if you renamed one of the two files to recovery.img)
dd if=/external_sdcard/recovery.emmc.win of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
dd if=/external_sdcard/mmcblk0p1.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Just use the above...but to confuse you more you could be using mmcblk naming convention in the output file as you stated. Tegra renames the mmcblk block format, think of it as a symlink so you can call a single location 2 different names.
so /dev/block/platform/sdhci-tegra.3/by-name/SOS is the same as /dev/block/mmcblk0p1 and is the recovery partition itself
another example /dev/block/platform/sdhci-tegra.3/by-name/LNX is the same as /dev/block/mmcblk0p2 and is the boot partition
knowing that you could take the first example from above
dd if=/external_sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
and write it as
dd if=/external_sdcard/recovery.img of=/dev/block/mmcblk0p1
and accomplish the same thing, so you were close just no "/platform/sdhci-tegra.3" Hopefully I didn't come across as offensive as I imagine you already know some of the above
I knew that (DUH! :cyclops: ) I told ya I was sleep deprived.
I'm going to flash it this afternoon and see what falls out.
Thanks bunches!
Ok, first step finally done.
Got the JmzNabi2Stock_OLD.zip loaded. Got the dreaded "turning wifi on" error, but skipped that step to move on. Currently waiting for "Please wait while your nabi device is being initialized. This might take a few minutes."
It has been at least 5 minutes, but to be honest this is going faster than the FC17 to FC19 upgrade I have going on on the system next to it. It's had a blank screen with the disk spinning since I started this about 30 minutes ago.
WooHoo! as I was typing that last para, the setup screen showed up. I'll go through som rudimentary things just to check and make sure this image isn't rooted, then I'll try to reload the stock recovery.
edit: crap, this wasn't the "stock" image. Now I need to head off and try to find that......
Whelp, that didn't work. One of the ROM flashes broke the recovery and lost root. Without ADB, I can't do anything more
Dan in SA said:
Whelp, that didn't work. One of the ROM flashes broke the recovery and lost root. Without ADB, I can't do anything more
Click to expand...
Click to collapse
If the recovery doesn't boot I doubt they will even look deeper then that and think you messed it up.
If you still want to attempt it you have to use an exploit to gain root again(Android still boots right?) Unfortunately most exploits are using ADB as a means to that end. ADB restore bug, elevating ADB shell to root via local.prop edit, for example. I would think the Android master key exploit would work on this device but the only good tool I have seen for it is Cydia Impactor. GUI that's compiled so its not easy to short cut and do locally without following the write up and manually doing everything(In short no one click that will work without USB). I think memdroid or something like that only worked up until 4.0.2 or something so I think Nabi is patched against it. It can be done I just don't know if you want to go to the effort. Should have used the Nabilab full stock ROM and stock recovery to restore as they are matched set.
aicjofs said:
Should have used the Nabilab full stock ROM and stock recovery to restore as they are matched set.
Click to expand...
Click to collapse
I did, but when I booted that up after I loaded the ROM, SuperSU was installed implying that the image was rooted already.
Too late now, it's in the box going back to Nabi tomorrow.
Evening all,
Hoping someone can help me with the following please? Please be as technical as you like, I'm fairly tech-savvy (I have CFW on my PSP, I build my own computers and have flashed/cfw various devices in the past) if I don't understand I can google it, but I need to know WHAT to google first and I'm a bit lost...! :good:
I have stock TF201 which is getting pretty painful despite a recent re-install. I've noticed that there is still no real idea as to if/when KitKat will be rolled out for it and was rather p!ssed off to see my missus's Nexus 7 (2012 version!) get 4.4.3 today!
I've done a lot of googling and forum reading but I'm a little confused as to the best route to go...
Having come across the "one-click method to root" using motochopper (and/or other methods) would it then be possible to install 4.4.2 for example using CM11 and a guide such as this (google "Install Android 4.4.2 KitKat on Asus Transformer Prime TF201" as I can't post URLs) - or will this only work for OFW release like 4.2?
In summary, am I missing the point (I get the feeling I may need to be unlocked as well to have a custom recovery?), THEN root etc...
Long and short is I'm not after doing anything crazy other than getting my TF201 to the latest STABLE(ish) version of Android. I understand the risks of bricking, CFW/OFW & OTA etc. I guess I'm basically after a simple list of steps (or pointing at the relevant thread) to achieve this - from the guides I've seen I have to unlock, root and then go down the CM11 route but I want to know if I can get there more easily/safely using one-click root or another method for example?
All advice gratefully received!
Mark
mistral_blue said:
Evening all,
Hoping someone can help me with the following please? Please be as technical as you like, I'm fairly tech-savvy (I have CFW on my PSP, I build my own computers and have flashed/cfw various devices in the past) if I don't understand I can google it, but I need to know WHAT to google first and I'm a bit lost...! :good:
I have stock TF201 which is getting pretty painful despite a recent re-install. I've noticed that there is still no real idea as to if/when KitKat will be rolled out for it and was rather p!ssed off to see my missus's Nexus 7 (2012 version!) get 4.4.3 today!
I've done a lot of googling and forum reading but I'm a little confused as to the best route to go...
Having come across the "one-click method to root" using motochopper (and/or other methods) would it then be possible to install 4.4.2 for example using CM11 and a guide such as this (google "Install Android 4.4.2 KitKat on Asus Transformer Prime TF201" as I can't post URLs) - or will this only work for OFW release like 4.2?
In summary, am I missing the point (I get the feeling I may need to be unlocked as well to have a custom recovery?), THEN root etc...
Long and short is I'm not after doing anything crazy other than getting my TF201 to the latest STABLE(ish) version of Android. I understand the risks of bricking, CFW/OFW & OTA etc. I guess I'm basically after a simple list of steps (or pointing at the relevant thread) to achieve this - from the guides I've seen I have to unlock, root and then go down the CM11 route but I want to know if I can get there more easily/safely using one-click root or another method for example?
All advice gratefully received!
Mark
Click to expand...
Click to collapse
Man your asking for alot
Shoot me a PM lets see if we can point you in the right direction.....
Thx Josh
mistral_blue said:
(I get the feeling I may need to be unlocked as well to have a custom recovery?), THEN root etc...
Click to expand...
Click to collapse
Yep, that's the only route to custom ROM and vital you make NVFlash backups:
1. Unlock device using the official tool from Asus website - its says "for ICS" but works fine on JB.
2. Assuming you are on the latest official stock JellyBean (Asus v 10.4.2.18) then go get the latest TWRP 2.6 for TF201 JB from the bottom of this page: http://techerrata.com/browse/twrp2/tf201 Flash that blob using fastboot following the instructions in the section titled "Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader)" on this page: http://teamw.in/project/twrp2/93.
3. Follow the instructions in the tutorial here for making NVFlash backups: http://matthill.eu/android/transform...ybean-nvflash/
4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/showthread.php?t=2773812. You will get plenty of help here from people who know about the tf201. Read the whole thread but pay particular attention to post #4 where Josh has written a step by step guide for people starting from scratch.
Finally, though you are pretty safe now with your NVFlash backups and even though you are well experiences at flashing, follow all the instructions to the letter and avoid the sadly well tested routes to brick. I don't believe there is another android device in current use that is so easy to brick as the prime.
1. Use only TWRP recoveries. Steer completely clear of CWM and ROM Manager. They never did produce an official recovery for JB on the prime and installing the last one from their site onto the JB bootloader will most certainly land you with a brick. The flatline process leaves behind its own version of CWM but has been made compatible. However, you probably won't be able to see your external SD card with it and it is based on a clunky non-touch version so best advice would be to ditch it straight away for TWRP 2.6 even though you will be upgrading that shortly anyway,
2. Always check you are flashing the correct version of TWRP for your current bootloader and ROM
3. Never, ever press that Wipe Data button on the fastboot screen - that too will kill your tablet.
Oh, and have fun!
EDIT: just seen Josh has offered to hold your hand - don't let go and you'll be fine
Thanks for the quick replies gents... Restorer, I'll read up on the methods you suggest (thanks for the detailed list with links, exactly what I was after) and then Josh I'll be in touch to check I've not missed anything before I start following the Yellow BRICK road:laugh:
Taking The Plunge!
Restorer said:
Yep, that's the only route to custom ROM and vital you make NVFlash backups:
1. Unlock device using the official tool from Asus website - its says "for ICS" but works fine on JB.
2. Assuming you are on the latest official stock JellyBean (Asus v 10.4.2.18) then go get the latest TWRP 2.6 for TF201 JB from the bottom of this page: http://techerrata.com/browse/twrp2/tf201 Flash that blob using fastboot following the instructions in the section titled "Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader)" on this page: http://teamw.in/project/twrp2/93.
3. Follow the instructions in the tutorial here for making NVFlash backups: http://matthill.eu/android/transform...ybean-nvflash/
4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/showthread.php?t=2773812. You will get plenty of help here from people who know about the tf201. Read the whole thread but pay particular attention to post #4 where Josh has written a step by step guide for people starting from scratch.
Finally, though you are pretty safe now with your NVFlash backups and even though you are well experiences at flashing, follow all the instructions to the letter and avoid the sadly well tested routes to brick. I don't believe there is another android device in current use that is so easy to brick as the prime.
1. Use only TWRP recoveries. Steer completely clear of CWM and ROM Manager. They never did produce an official recovery for JB on the prime and installing the last one from their site onto the JB bootloader will most certainly land you with a brick. The flatline process leaves behind its own version of CWM but has been made compatible. However, you probably won't be able to see your external SD card with it and it is based on a clunky non-touch version so best advice would be to ditch it straight away for TWRP 2.6 even though you will be upgrading that shortly anyway,
2. Always check you are flashing the correct version of TWRP for your current bootloader and ROM
3. Never, ever press that Wipe Data button on the fastboot screen - that too will kill your tablet.
Oh, and have fun!
EDIT: just seen Josh has offered to hold your hand - don't let go and you'll be fine
Click to expand...
Click to collapse
Restorer thanks for the instructions...like the title I am about to take the "plunge" and flash this Prime and I want to got to KK. Just one thing.. below you state: "4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/show....php?t=2773812. " but when I go to the link it says that I must be on Hairybean and the bootloader 4.2.1. I am currently on the stock 10.4.2.18 and downloaded the unlock v6 .apk file from Asus to do the bootloader "unlocking" Just for the sake of clarity...I am new to this...should I still unlock using the Asus util and once done then do the Hairybean update? which will in turn upgrade the bootloader (10.6.1.27.1)?
Tim
tim2min said:
Restorer thanks for the instructions...like the title I am about to take the "plunge" and flash this Prime and I want to got to KK. Just one thing.. below you state: "4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/show....php?t=2773812. " but when I go to the link it says that I must be on Hairybean and the bootloader 4.2.1. I am currently on the stock 10.4.2.18 and downloaded the unlock v6 .apk file from Asus to do the bootloader "unlocking" Just for the sake of clarity...I am new to this...should I still unlock using the Asus util and once done then do the Hairybean update? which will in turn upgrade the bootloader (10.6.1.27.1)?
Tim
Click to expand...
Click to collapse
Yes, you can't flash anything until the device is unlocked and you have installed a TWRP recovery.
But make sure to then make your NVFlash backups and once you have those files safely stored go straight on to follow Josh's step-by-step guide for in post #4 of the ROM thread. His guide was written specifically for TF201 people coming from stock. Follow it to the letter but be sure to ask if there is something you don't understand.
Good Luck!
Taking The Plunge!
Restorer said:
Yep, that's the only route to custom ROM and vital you make NVFlash backups:
1. Unlock device using the official tool from Asus website - its says "for ICS" but works fine on JB.
2. Assuming you are on the latest official stock JellyBean (Asus v 10.4.2.18) then go get the latest TWRP 2.6 for TF201 JB from the bottom of this page: http://techerrata.com/browse/twrp2/tf201 Flash that blob using fastboot following the instructions in the section titled "Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader)" on this page: http://teamw.in/project/twrp2/93.
3. Follow the instructions in the tutorial here for making NVFlash backups: http://matthill.eu/android/transform...ybean-nvflash/
4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/showthread.php?t=2773812. You will get plenty of help here from people who know about the tf201. Read the whole thread but pay particular attention to post #4 where Josh has written a step by step guide for people starting from scratch.
Finally, though you are pretty safe now with your NVFlash backups and even though you are well experiences at flashing, follow all the instructions to the letter and avoid the sadly well tested routes to brick. I don't believe there is another android device in current use that is so easy to brick as the prime.
1. Use only TWRP recoveries. Steer completely clear of CWM and ROM Manager. They never did produce an official recovery for JB on the prime and installing the last one from their site onto the JB bootloader will most certainly land you with a brick. The flatline process leaves behind its own version of CWM but has been made compatible. However, you probably won't be able to see your external SD card with it and it is based on a clunky non-touch version so best advice would be to ditch it straight away for TWRP 2.6 even though you will be upgrading that shortly anyway,
2. Always check you are flashing the correct version of TWRP for your current bootloader and ROM
3. Never, ever press that Wipe Data button on the fastboot screen - that too will kill your tablet.
Oh, and have fun!
EDIT: just seen Josh has offered to hold your hand - don't let go and you'll be fine
Click to expand...
Click to collapse
Restorer said:
Yes, you can't flash anything until the device is unlocked and you have installed a TWRP recovery.
But make sure to then make your NVFlash backups and once you have those files safely stored go straight on to follow Josh's step-by-step guide for in post #4 of the ROM thread. His guide was written specifically for TF201 people coming from stock. Follow it to the letter but be sure to ask if there is something you don't understand.
Good Luck!
Click to expand...
Click to collapse
Sorry just one more question, since I have a TF201 and and want to use this ROM, it seems I am essentially turning my Prime into aTF300, which is ok, now right after unlocking the boot loader and then running TWRP (2.7 TF300) it is at this point I flash the hairybean update or do the creation & backing up for NVFlash first then the hairybean?...sorry for the elemental question...just want to be sure!
Tim
tim2min said:
now right after unlocking the boot loader and then running TWRP (2.7 TF300)
Click to expand...
Click to collapse
No you're not a TF300 yet! Unlock then flash the latest TWRP version for TF201 from the page I linked to (still 2.6). Then do your NVFlash backups. Then you can pick up Josh's guide again where you flash "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". It's just the guide assumes you already have your backups .
Taking The Plunge!
Restorer said:
No you're not a TF300 yet! Unlock then flash the latest TWRP version for TF201 from the page I linked to (still 2.6). Then do your NVFlash backups. Then you can pick up Josh's guide again where you flash "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". It's just the guide assumes you already have your backups .
Click to expand...
Click to collapse
Hey restorer this can all be done on a non-root device correct? Should root first if so what is the best way you suggest ...read a little something about motochopper.?
Taking The Plunge!
tim2min said:
Hey restorer this can all be done on a non-root device correct? Should root first if so what is the best way you suggest ...read a little something about motochopper.?
Click to expand...
Click to collapse
Have a possible issue when trying to after renaming the original file flat_tf201 (image file) to twrp.blob it looks like on the windows 7 side it sent it fine but on the tablet I did not see the "blue bar". So worried it did not send I tried it again and got the "error cannot open twrp.blob" when I did a dir of the fastboot directory it is there but noticed is the command prompt after renaming (per instructions from TWRP) the full file name was twrp.blob.img should not matter but renamed it (from command prompt) w/o the .img extension still would not send.
I am thinking eventhough it initially looked like it did send (based on output in command prompt initially) is it possible I missed the blue bar on the tablet?... Should I have seen it? Does it take awhile?
The tablet shows "starting Fastboot USB download protocol"
any help what be appreciated
tim2min said:
Have a possible issue when trying to after renaming the original file flat_tf201 (image file) to twrp.blob it looks like on the windows 7 side it sent it fine but on the tablet I did not see the "blue bar". So worried it did not send I tried it again and got the "error cannot open twrp.blob" when I did a dir of the fastboot directory it is there but noticed is the command prompt after renaming (per instructions from TWRP) the full file name was twrp.blob.img should not matter but renamed it (from command prompt) w/o the .img extension still would not send.
I am thinking eventhough it initially looked like it did send (based on output in command prompt initially) is it possible I missed the blue bar on the tablet?... Should I have seen it? Does it take awhile?
The tablet shows "starting Fastboot USB download protocol"
any help what be appreciated
Click to expand...
Click to collapse
Why rename the the .img file to a .blob file ?
Not really the best thing you could do .....
Just boot to fastboot and run the command
Code:
fastboot flash recovery flatline_tf201.img
The blue bar will show up and fill on the write part of the command ...
Once that is done do this command .....
Code:
fastboot reboot-bootloader
Let the tablet reboot into bootloader and VOL up on RCK
Now your golden ......
Make sure you understand what need to be done in flatline ...
Thx Josh
tim2min said:
Hey restorer this can all be done on a non-root device correct? Should root first if so what is the best way you suggest ...read a little something about motochopper.?
Click to expand...
Click to collapse
No need to root first - the custom ROM you will be installing will be rooted.
---------- Post added at 08:09 AM ---------- Previous post was at 07:59 AM ----------
tim2min said:
Have a possible issue when trying to after renaming the original file flat_tf201 (image file) to twrp.blob it looks like on the windows 7 side it sent it fine but on the tablet I did not see the "blue bar". So worried it did not send I tried it again and got the "error cannot open twrp.blob" when I did a dir of the fastboot directory it is there but noticed is the command prompt after renaming (per instructions from TWRP) the full file name was twrp.blob.img should not matter but renamed it (from command prompt) w/o the .img extension still would not send.
I am thinking eventhough it initially looked like it did send (based on output in command prompt initially) is it possible I missed the blue bar on the tablet?... Should I have seen it? Does it take awhile?
The tablet shows "starting Fastboot USB download protocol"
any help what be appreciated
Click to expand...
Click to collapse
Sounds like you have downloaded (and renamed) the .img file and not the .blob file! "openrecovery-twrp-2.6.3.0-tf201-JB.blob" is the one you want if you are follwoing the instructions on the TWRP page I linked you too. The blob file Josh refers to is the one in this zip file and has a shorter name. You can either use Josh's instructions or TWRP's but not a mixture of the two
@lj50036 I think he referring to the instructions from TWRP on the downloads page which say to rename the file to a shorter form.
@tim2min don't let this renaming stuff confuse you - TWRP are only suggesting it because their full names are so long and prone to error when you are typing them out!
EDIT: Sorry, I hadn't realised Josh had already prepared and renamed the files for you. Just use all 3 of his files contained in his zip and not from my links or you may get further confused.
Restorer said:
No need to root first - the custom ROM you will be installing will be rooted.
---------- Post added at 08:09 AM ---------- Previous post was at 07:59 AM ----------
Sounds like you have downloaded (and renamed) the .img file and not the .blob file! "openrecovery-twrp-2.6.3.0-tf201-JB.blob" is the one you want if you are follwoing the instructions on the TWRP page I linked you too. The blob file Josh refers to is the one in this zip file and has a shorter name. You can either use Josh's instructions or TWRP's but not a mixture of the two
@lj50036 I think he referring to the instructions from TWRP on the downloads page which say to rename the file to a shorter form.
@tim2min don't let this renaming stuff confuse you - TWRP are only suggesting it because their full names are so long and prone to error when you are typing them out!
EDIT: Sorry, I hadn't realised Josh had already prepared and renamed the files for you. Just use all 3 of his files contained in his zip and not from my links or you may get further confused.
Click to expand...
Click to collapse
Does no one use auto-complete any more ......
Thx Josh
lj50036 said:
Does no one use auto-complete any more ......
Thx Josh
Click to expand...
Click to collapse
Haha, yes. Why do command windows have to be so primitive .
Restorer said:
No you're not a TF300 yet! Unlock then flash the latest TWRP version for TF201 from the page I linked to (still 2.6). Then do your NVFlash backups. Then you can pick up Josh's guide again where you flash "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". It's just the guide assumes you already have your backups .
Click to expand...
Click to collapse
Just an observation Restorer I note that you said never to select "Wipe Data" in the boot menu but in Josh step by step he suggested to do that which can take a while. In this case it ok to do it since we are putting on a new ROM. I have my backups (blob files) as well as the NVFlash file
Tim
tim2min said:
Just an observation Restorer I note that you said never to select "Wipe Data" in the boot menu but in Josh step by step he suggested to do that which can take a while. In this case it ok to do it since we are putting on a new ROM. I have my backups (blob files) as well as the NVFlash file
Tim
Click to expand...
Click to collapse
How is this saying anything about wiping from bootloader ?
I am sure it say NOW ENTER RECOVERY ....
But maybe I missed something or maybe you did ....
lj50036 said:
Now enter recovery....
Make sure its verison 2.7.1.0
Go to Wipe////Format Data////Type yes
This can take up to 90 mins to format
DO NOT INTERRUPT THE FORMAT !!!!!!!
Click to expand...
Click to collapse
Thx Josh
Taking The Plunge!
lj50036 said:
How is this saying anything about wiping from bootloader ?
I am sure it say NOW ENTER RECOVERY ....
But maybe I missed something or maybe you did ....
Thx Josh
Click to expand...
Click to collapse
Man it was going so well until my computer could no longer see my tablet via USB! so I can now longer use FASTBOOT because the device is not found. This happen right after flashing Hariybean and I was about to run"
Interesting my Win7 computer says that it sees the Asus device:but fastboot does not see it. Also initially the it saw it as an APX device but no longer so I can not do the next step which is to adb reboot-bootloader and then do flash @ne0zone75 TWRP recovery per the instuctions. I have tried re-pointing to the Universal Naked drivers trying to select a diffrent drvier but to no avail. looks like the tablet can no longer communicate to the computer. I will copy the contents of the fastboot directory to another computer and see if that will work
any ideas?
Tim
tim2min said:
Man it was going so well until my computer could no longer see my tablet via USB! so I can now longer use FASTBOOT because the device is not found. This happen right after flashing Hariybean and I was about to run"
Interesting my Win7 computer says that it sees the Asus device:but fastboot does not see it. Also initially the it saw it as an APX device but no longer so I can not do the next step which is to adb reboot-bootloader and then do flash @ne0zone75 TWRP recovery per the instuctions. I have tried re-pointing to the Universal Naked drivers trying to select a diffrent drvier but to no avail. looks like the tablet can no longer communicate to the computer. I will copy the contents of the fastboot directory to another computer and see if that will work
any ideas?
Tim
Click to expand...
Click to collapse
Sounds like another windows driver issue .....
I really cant help much here as I dont use windows ...
But there is a short term solution at least to get you booted up ....
@ne0zone75's flashable zip twrp
Download this and move it into your folder that contains the fastboot.exe ... Then rename it to twrp.zip
Then boot into the recovery and run this command from CMD window
Code:
adb push twrp.zip /sdcard
Let that happen should not take long, find the zip file under install and flash it .....
YOU MUST DO A REBOOT AFTER THIS NOT JUST A REBOOT INTO BOOTLOADER ...
So lets run this command ....
Code:
adb reboot
Let it fully boot into a bootloop then with the buttons get back to the bootloader screen and enter RCK ...
then once you have done that continue on your way ....
Let me know this works for you ....
Thx Josh
tim2min said:
Just an observation Restorer I note that you said never to select "Wipe Data" in the boot menu but in Josh step by step he suggested to do that which can take a while. In this case it ok to do it since we are putting on a new ROM. I have my backups (blob files) as well as the NVFlash file
Tim
Click to expand...
Click to collapse
Josh has answered you. But this is another fine example of why people here keep banging on about reading things carefully and then following instructions to the letter .
Taking the Plunge
Well, after some "trying" moments I got this ROM on the Prime!...must say extremely excited seems like my TF201 has more than just a "heartbeat" left in her, shoot she may be able to run hard a little longer!. I must admit some EXTREME anxiety occured and I really got scared when after flashing hairybean/bootloader my computer could not find/see my tablet AT ALL!!. This lost of connection was madddding especially when Windows would add the tablet in device manager and you would hear the computer chime every time I connected/disconnect the USB cable from the computer while the other end was in the tablet. I had to fuss around with Android APD Interface/Android APX drivers until my computer settled on one that actually worked after running c:\fastboot>fastboot devices 50x's and if finally saw my tablet I literally shedded a tear, this is definetely not for the faint of heart...lol Needless to say I hurried up and finished going down the instructions just for fear my computer might "inexplicably " loose connection again!....lol
Many thanks to Restorer for chiming in with my question also Josh (especially for the step by step instructions) also to the whole team that made this ROM!
Just a question though: If you wanted to change the color theme on boot up (which now shows in blue "CROMBi-KK") how would I go about that?
Tim