Related
Followed the guide using adb.
After is says I rooted and restart I get a bunch of artifacts on the screen. Please tell me I didnt brick it or anything
How do I fix it?!
stay calm, u cant just brick ur tf10. What u need to do is the following:
- learn how to boot into apx mode...u proly have this knowledge considering u got this trying to flash.
- go to dev section and search prime 1.8.x thread.
- it contains the NVFlash kit + the rom.
- if u dont like the rom...download the original version 3.2
- Go apx mode and run the script @ prime thread.
I experienced it myself. I belief it happened when i wanted to do the one click root.
good luck!
edit:
here the NVFlash with prime 1.4 http://forum.xda-developers.com/showthread.php?t=1123429
replace the img for 1.8 prime
Theres several download links.. So confused which one. lol.
Not sure what commands i have to run.
Edit: I downloaded the nvflash in the link.. in my control panel "APX" isnt popping up..
but what commands would I have to run and what img do I replace?
Watch video
http://www.youtube.com/watch?v=VMHXeYMgPy4&feature=player_embedded
Okay. I figured I already had the Nvidia USB boot-recovery driver installed from when I first tried to root. So takes care of me not seeing APK appear in my device manager.
My internet is just slow and waiting to finish d/ling Prime.zip.
baseballfanz said:
Watch video
http://www.youtube.com/watch?v=VMHXeYMgPy4&feature=player_embedded
Click to expand...
Click to collapse
Ironic. I just found it through following links in the NVflash thread. Thanks though! waiting on download and then i can proceed
I got the Prime1.8.2.zip where do i extract it? The video is showing Prime 1.4.zip and the files inside are different.
You do not unzip the contents of ROMs you keep them as is...if that is what I am understanding from your text.
Sent from my Transformer TF101 using XDA Premium App
Well in the video linked above the download prime1.4.zip he extracts it to the nvflash folder and then runs the "Download" batch command
Do NOT use the ZIP file for NVFLash,
Download the Prime1.8.tar.bz2 file, extract the files and put it in the NVFlash root folder.
Prime 1.8.tar.bz2 here
http://forum.xda-developers.com/showthread.php?t=1231666
Okay, this is just confusing me now. You give me that link to download the 1.8.tar.bz2
The video has primev1.4.tar.bz2 and in the video it says to go into the prime1.4folder and move the 3 files into the nvflash folder.
The link you give doesnt just have those 3 files so im confused on what to do??
-The 1.8 is just the most up to date version.
-You can use the 1.4 like the video if you like.
Fixed. Im back in business! Thank you all for your help and patience.
Now should I flash the new 1.8.4? Still a little new of how the flashing on here goes. Been so accustomed to my Evo and CWM
I downloaded Rom manager.. shows "install clockworkmod recovery to flash roms..." I dont need to because the NVflash installed it already?
What are some things to install to help improve responsiveness/performance? Dont think ill do any OC'ing yet. Is there an app to do any underclocking/undervolting.. Are we able to flash the V6supercharge script?
ROM Manager is not compatible with the tf as of now and yes if you did everything during nvflash method, you should have
cwm install.
Just download 1.8.4 and put it on the removable micro sd card, boot into cwm recovery
and flash. Steps should be similar to flashing via cwm on your android phone.
Keep in mind, from here on outyou can just use cwm to flash new rom, updates or kernels, ect.
Sent from my Transformer TF101 using Tapatalk
Same thing happened to me (rainbow screen).
All fixed now
This seems to be the norm for every new android device I get these days:
Unpack
Yay!! It's shiny
Crap no root (It's funny how you miss it once you're used to it)
Root and Brick - Crap
Unbrick
Reroot
Custom FW
Overclock
Enjoy ...
tlxxxsracer said:
Fixed. Im back in business! Thank you all for your help and patience.
Now should I flash the new 1.8.4? Still a little new of how the flashing on here goes. Been so accustomed to my Evo and CWM
I downloaded Rom manager.. shows "install clockworkmod recovery to flash roms..." I dont need to because the NVflash installed it already?
What are some things to install to help improve responsiveness/performance? Dont think ill do any OC'ing yet. Is there an app to do any underclocking/undervolting.. Are we able to flash the V6supercharge script?
Click to expand...
Click to collapse
Next time and its really more easier just do it with NVFlash. For new FW and ROMS, just down load the NVFlash version of what ever u want (see DEV section for prime or revolver).
Replace or place the following things in ur NVFlash folder:
recovery.img (CWM i belief)
boot.img (boot conf and sequence)
bootloader.bin (pretty boot visuals)
system.img (the ROM!)
And ur done!
A problem currently exists with newer Xooms when attempts are made to flash ClockworkMod 3.2.0.0 (R4c) (CMW) into the Recovery partition. This issue has been mentioned in several threads with no resolution to date.
This is what the problem seems to be:
- Fact: There was no problem flashing ClockWorkMod (CWM) to older (earlier versions than 3.2.1).
- Fact: The problem occurred with attempts to flash later versions of Android, e.g., 3.2.1 following update via OTA.
- Fact: The OTA has an incompatibility with CWM. Joe Ferreira identified the problem as one of the following files being present that will prevent CWM from working:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
- Fact: The proposed fix involves reverting to an earlier version, i.e., 3.0 and updating to 3.2.1 via OTA. This fix is yet unproven.
- Fact: Owners of newer Xooms are being prevented from achieving root because of this problem (including myself)
To summarize:
1) Recent OTAs which bring the Xoom to 3.2.1 are incompatible with the ClockworkMod 3.2.0.0 (R4c) image (CWM)
2) Once flashed CWM is inaccessible.
This is the problem that needs to be resolved.
Note: Epic118 has suggested reverting to 3.0; updating via OTA to 3.2.1; and rerunning Xoot. I don't understand this since attempting to flash CWM on 3.2.1 updated via OTA will repeat the same issue. Perhaps EPIC118 can provide clarification.
Does anyone have a solution/fix to this problem?
microi said:
A problem currently exists with newer Xooms when attempts are made to flash ClockworkMod 3.2.0.0 (R4c) (CMW) into the Recovery partition. This issue has been mentioned in several threads with no resolution to date.
This is what the problem seems to be:
- Fact: There was no problem flashing ClockWorkMod (CWM) to older (earlier versions than 3.2.1).
- Fact: The problem occurred with attempts to flash later versions of Android, e.g., 3.2.1 following update via OTA.
- Fact: The OTA has an incompatibility with CWM. Joe Ferreira identified the problem as one of the following files being present that will prevent CWM from working:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
- Fact: The proposed fix involves reverting to an earlier version, i.e., 3.0 and updating to 3.2.1 via OTA. This fix is yet unproven.
- Fact: Owners of newer Xooms are being prevented from achieving root because of this problem (including myself)
To summarize:
1) Recent OTAs which bring the Xoom to 3.2.1 are incompatible with the ClockworkMod 3.2.0.0 (R4c) image (CWM)
2) Once flashed CWM is inaccessible.
This is the problem that needs to be resolved.
Note: Epic118 has suggested reverting to 3.0; updating via OTA to 3.2.1; and rerunning Xoot. I don't understand this since attempting to flash CWM on 3.2.1 updated via OTA will repeat the same issue. Perhaps EPIC118 can provide clarification.
Does anyone have a solution/fix to this problem?
Click to expand...
Click to collapse
How about reverting to stock 3.0.1, then OTA updating to 3.2 and then rooting/flashing recovery and custom rom/kernel. I would think the issue is with the 3.2.1 OTA update itself.
I'm not completely sure I understand but if u can try this,
Download the universal root update zip and put it on your xoom
Flash clockwork through fastboot and then reboot into recovery, don't let it boot or the install recovery.sh will delete clockwork!
Flash the universal root.zip and boot up and use a root file manager to delete those two file and clockwork should stick through a reboot
Sent from my ADR6400L using Tapatalk
Hi
I have a UK Xoom and I am interested in putting a custom ICS on it. I have read through all of the pages of the excellent guide to unlocking and rooting etc started by okantomi. Fair play to all involved, its a great source of information.
My Xoom is showing 3.2 as the current version. When I bought it a few months ago it had 3.0 installed. I updated OTA to 3.1 and more recently to 3.2. I then got a small update a few weeks back but Android version is still showing as 3.2. Am I good to go ahead?
bandit197 said:
Hi
I have a UK Xoom and I am interested in putting a custom ICS on it. I have read through all of the pages of the excellent guide to unlocking and rooting etc started by okantomi. Fair play to all involved, its a great source of information.
My Xoom is showing 3.2 as the current version. When I bought it a few months ago it had 3.0 installed. I updated OTA to 3.1 and more recently to 3.2. I then got a small update a few weeks back but Android version is still showing as 3.2. Am I good to go ahead?
Click to expand...
Click to collapse
I'm not sure what update (after the 3.2 update) added the security "fix" that seems to cause the problem, but you might as well try to root. If it doesn't work, at least you have a potential work-around, but hopefully it will be fine.
Good luck.
okantomi said:
I'm not sure what update (after the 3.2 update) added the security "fix" that seems to cause the problem, but you might as well try to root. If it doesn't work, at least you have a potential work-around, but hopefully it will be fine.
Good luck.
Click to expand...
Click to collapse
Cheers, I went ahead with it and it worked out no problems, unlocked, rooted and I can access recovery. Ill post the details in the guide thread to keep everything in the one place.
Superchilpil,
Thank you for your reply.
There are a few points I don't fully understand.
You indicate,
Flash clockwork through fastboot and then reboot into recovery, don't let it boot or the install recovery.sh will delete clockwork!
Click to expand...
Click to collapse
1) Should I reboot into recovery using fastboot or simply reboot the Xoom using "Vol+ and Power"?
2) You indicate, "Don't let it boot". I don't understand; if I initiate a 'reboot', it reboots. How can I prevent it from rebooting???
This is the code I will use to flash Clockwork:
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Click to expand...
Click to collapse
What code should I use to effect your suggested approach?
One last question. The objective of this question is to understand if I can simply flash the "Universal Root Update Zip" to obtain root using the stock Recovery Mode, then install ClockworkMod Recovery; then remove one or the other of two problematic security files which are currently causing a problem. This will theoretically resolve the "Green Bot of !" issue Xoom users with 3.2.1 are currently experiencing.
After unlocking the bootloader, is it possible to:
1) Flash Update.zip (from the MicroSD card) using the stock Recovery Mode
2) Flash ClockworkMod Recovery through fastboot
3) Obtain root from this procedure
Thank you in advance.
Microi
microi said:
Superchilpil,
Thank you for your reply.
There are a few points I don't fully understand.
You indicate,
1) Should I reboot into recovery using fastboot or simply reboot the Xoom using "Vol+ and Power"?
2) You indicate, "Don't let it boot". I don't understand; if I initiate a 'reboot', it reboots. How can I prevent it from rebooting???
This is the code I will use to flash Clockwork:
What code should I use to effect your suggested approach?
One last question. The objective of this question is to understand if I can simply flash the "Universal Root Update Zip" to obtain root using the stock Recovery Mode, then install ClockworkMod Recovery; then remove one or the other of two problematic security files which are currently causing a problem. This will theoretically resolve the "Green Bot of !" issue Xoom users with 3.2.1 are currently experiencing.
After unlocking the bootloader, is it possible to:
1) Flash Update.zip (from the MicroSD card) using the stock Recovery Mode
2) Flash ClockworkMod Recovery through fastboot
3) Obtain root from this procedure
Thank you in advance.
Microi
Click to expand...
Click to collapse
by not letting it boot I mean don't let it boot into the rom, and both of those methods u stated will work just fine to reboot
And flash it using whatever method you desire, but I forgot to mention that you may need to flash clockwork again after you boot and delete those files because the install recovery.sh obviously flashes the stock recovery and the point of my method is to keep a custom recovery on your device
I know for a fact that the stock recovery mode won't flash anything you will find here in the forums that I know of
Sent from my Xoom using Tapatalk
superchilpil said:
I know for a fact that the stock recovery mode won't flash anything you will find here in the forums that I know of
Click to expand...
Click to collapse
Correct, the stock recovery requires that the zip files be signed with keys that only the manufacturers have access to. This is the whole reason why we have to flash a third party recovery to begin with.
teameos said:
Correct, the stock recovery requires that the zip files be signed with keys that only the manufacturers have access to. This is the whole reason why we have to flash a third party recovery to begin with.
Click to expand...
Click to collapse
I'm getting more and more confused the more times I read this.!!
I have done the update then unlocked to find I now have the green bot!!!!!
Someone please send a simple step by step with some file links to revert back to stock 3.2!
Thanks
I was HC stock, locked, unrooted, had accepted all OTA's - and therefore had the problem with the 2 files mentioned in the OP. I updated to ICS just fine. In order to root, I did the following (the differences from the standard instructions are underlined)
unlock
flash recovery
boot into recovery
root
then while still in CWM, no reboot, but instead:
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
reboot with CWM
Only had to flash CWM once.
willysp said:
I was HC stock, locked, unrooted, had accepted all OTA's - and therefore had the problem with the 2 files mentioned in the OP. I updated to ICS just fine. In order to root, I did the following (the differences from the standard instructions are underlined)
unlock
flash recovery
boot into recovery
root
then while still in CWM, no reboot, but instead:
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
reboot with CWM
Only had to flash CWM once.
Click to expand...
Click to collapse
Thanks. This makes a lot of sense. I would like to edit my rooting guide and give this procedure as the preferred approach. Is there anything you would want to add to it?
Just as a Fyi, these files are on all Android os, not something new. You can also flash an insecure boot image, and it will stop these from running.
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Sent from my Nexus S 4G
okantomi said:
Thanks. This makes a lot of sense. I would like to edit my rooting guide and give this procedure as the preferred approach. Is there anything you would want to add to it?
Click to expand...
Click to collapse
Hi,
First - thanks for your rooting guide - I used it with the exception of my underlined steps which were a synthesis of what I saw in a few other places.
Nothing to add - except perhaps really emphasize to keep the USB cable connected, and after rooting, do not reboot, stay in CWM, and use adb to run the 3 commands. You wrote a very detailed guide, so know you'll do a great job writing the expanded version of my short underlined additions. As you obviously know, many of the less technical users need a more detailed explanation of my underlined changes.
Thanks again for the help your guide gave me!
---------- Post added at 07:19 AM ---------- Previous post was at 07:14 AM ----------
bwcorvus said:
Just as a Fyi, these files are on all Android os, not something new. You can also flash an insecure boot image, and it will stop these from running.
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Yes, I saw them mentioned re several devices as I googled.
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.
willysp said:
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.
Click to expand...
Click to collapse
These are a _function_ of the OTA process. When there are kernel or recovery updates required, the stock recovery partition requires patching, hence these files.
ydaraishy said:
These are a _function_ of the OTA process. When there are kernel or recovery updates required, the stock recovery partition requires patching, hence these files.
Click to expand...
Click to collapse
Thanks, that helps explain what they are. So, if an OTA (like 3.2 apparently) wants to patch/replace stock recovery, those are the files that do it on next boot. Would be nice if they deleted themselves when done (from a hacker's POV), but for people running stock, I guess it makes sense for the OS to check the recovery partition at each boot and overwrite it with stock recovery if needed.
willysp said:
Hi,
First - thanks for your rooting guide - I used it with the exception of my underlined steps which were a synthesis of what I saw in a few other places.
Nothing to add - except perhaps really emphasize to keep the USB cable connected, and after rooting, do not reboot, stay in CWM, and use adb to run the 3 commands. You wrote a very detailed guide, so know you'll do a great job writing the expanded version of my short underlined additions. As you obviously know, many of the less technical users need a more detailed explanation of my underlined changes.
Thanks again for the help your guide gave me!
---------- Post added at 07:19 AM ---------- Previous post was at 07:14 AM ----------
Yes, I saw them mentioned re several devices as I googled.
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.
Click to expand...
Click to collapse
I'm no expert, but I will try to put it together based on the info in this thread, but please correct me if I'm wrong.
okantomi said:
I'm no expert, but I will try to put it together based on the info in this thread, but please correct me if I'm wrong.
Click to expand...
Click to collapse
Sure - glad to.
Yes these files were on the stock Xoom. Infact it helped us get some of the dumps. We would flash cwm, then dump, then let the OS rebuild the recovery. We then flashed cwm to boot and dumped the stock recovery.
Sent from my Nexus S 4G
bwcorvus said:
Yes these files were on the stock Xoom. Infact it helped us get some of the dumps. We would flash cwm, then dump, then let the OS rebuild the recovery. We then flashed cwm to boot and dumped the stock recovery.
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Thanks for the info.
Hi there everyone,
I have a huge problem. Last night i bricked my xoom. I was following a tutorial on this forum. and after unlocking the bootloader it told to flash a file called boot.img after doing so and typing fastboot reboot, the device wouldnt start behind the motorola logo. i tried allot of thing and also did flash some other stock android 4.0.4 boot.img files now with the last one mentioned i managed to get the xoom (wifi) to boot a little further. because the ripple movie with the motorola logo is shown. but it stucks at that movie.
Does anyone know if i can flash an image on the xoom that will atleast fix the problem of not rebooting so i can try another tutorial.
I have searched the internet for solutions, many of them linked to threads on this forum. but almost all download links in these tutorials are old and broken.
Can someone please help me unbrick my device? And maybe a link to a good working unroot tutorial for my xoom wifi with android 4.0.4.
Try get back to Stock.
Download from HERE
and do some OTA updates afterwards so everything will be up to date.
Then wipe and try again from scratch..
Worked for me perfectly just a few days ago.
If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.
Cubanluke88 said:
If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.
Click to expand...
Click to collapse
Indeed it worked. i downloaded the official images and flashed them im on android 3.0.1 again and all seems to work just fine now.
Next problem is i cant find a descent tutorial on this forum how to root the xoom. all download links are either removed due to copyright issues or the links are just broken.
How does it work actually?
1. I unlocked the boot loader wich is very easy.
but then? Do i need to flash a rooted image over the existing? i dont really understand how this works. I rooted my Desire HD with a good tutorial in minutes. Not many people seems to really know how to root the Xoom.
Also i would like to know if the different tutorials are for different android versions or can i aply all tutorials of rooting when i stay on android 3.0.1?
I also tried to flash a recovery.img to the recovery partition and press volume down 3 seconds after the moto logo apears but when i do i get an android robot with a big " ! " on his belly and it takes 5 minutes to load the menu. when im in it tells me there is no sdcard present when i try to flash a rooted rom (zip file).
Is there someone reading this thats willin to explain to me how to do a root the easiest way? Please if links are posted be sure everything on that thread is working. Im pretty sure i will pull it off with some push in the right direction.
Thank you!
(edit) omg im stupid, offcourse the sdcard wont work... it never worked at 3.0.1. on the xoom. can i follow this tutorial:
http://rootzwiki.com/topic/451-how-to-root-the-wifi-only-xoom-301/
Could someone read over it and see if this is a good tutorial? last time i flashed a boot.img the whole xoom got stuck... is that because i had the wrong boot.img on the wrong android version? or should boot.img always work?
Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.
Cubanluke88 said:
Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.
Click to expand...
Click to collapse
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
eos 4.1.1 is simply awesome and its also pre rooted' so your bootloader is unlocked, all you gotta do now is install twrp recovery via fastboot ( my preffered recovery) then flash eos via recovery
Sent from my Xoom using XDA Premium App
sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
EOS is a pretty AOSP rom. No theme, though you can apply one if you like and change a few colors. There are various toggle additions you can add that make the user experience much better. It also comes with an overclockable kernel and is very very stable (despite being a nightly) The team has been supporting the Xoom for over a year and is very committed to the Xoom.
---------- Post added at 01:15 PM ---------- Previous post was at 01:11 PM ----------
sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
As for flashing, just gotta make sure your text is good before hitting the enter key. Recovery flash should look something like this:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Some instructions for flashing can be found here
While that page is specifically for locking and flashing to return to stock, the commands are universal for fastboot. Hell, if you wanted to, you could manually restore a nandroid backup via fastboot and flashing images.
Hey everyone. Just wanted to say that I have used these forms a lot in the past with rooting my Droids and phones however I now have the Infinity and I need some advice on how to do the following... I know enough to be Dangerous when dealing with flashing etc on Android so I like to run things by people and get suggestions... So
Currently:
ROOT Original Stock Rom 4.0.3
Kernel - 2.6.39.4
Build - IML74K.US_epad-9.4.5.26-20120720
- Notes: When I first got this when released I used the only rooting option I could find which was some sort of auto command line script.
- I then Installed TWRP via GooManager
- I then UnLocked the Device with the Asus tool they released.
I did that months ago and haven't messed with it since... I have used it more and more lately and its slow in terms or response etc. I see that JB is now out for it. I started to look into CM I believe its called cyanogenmod 10 (it is really that good?) is out. I also see Stock Rooted ROMs.
Here is what I want to do.
1) I have looked and believe that I am able to apply the NVFlash patch so I cant brick my device. What does this actually do and will it mess with my abilities to use Recovery Mangers / Flash Roms / Kernels etc? ... Also if I update the build to a higher number will it take this away?
2) At the time TWRP was the ONLY option for me. How can I remove TWRP and get ClockWork on this? *note I dont care about anything on the device currently.
3) Is installing CM as easy as put the Zip on the SD card and then boot into CWM and install? -- Where can I get the OFFICIAL CM10 download for the infinity?
4) Kernel related - I know that stock kernels dont have the CPU control ability / and also some extras needed for wi-fi tether to fully function does CM come with its own kernel? or Do I have to get it Separately.
5) Basically There are to many guides and posts about what to do its confusing at this point.
I want to Wipe it / Get CWM on there instead of TWRP and Install CM. And if it is safe install the NVFlash.
I will await your guidance. Just past links to what guides to do in order.
Thanks!
bigstack said:
1) I have looked and believe that I am able to apply the NVFlash patch so I cant brick my device. What does this actually do and will it mess with my abilities to use Recovery Mangers / Flash Roms / Kernels etc? ... Also if I update the build to a higher number will it take this away?
Click to expand...
Click to collapse
As long as you don't upgrade your bootloader past 9.4.5.26, you can obtain the required files from your tablet using the procedure described at http://androidroot.mobi/t3_nvflash/ . What it does is described in the dev thread about nvflash - it does not mess with any abilities to flash stuff the normal way.
After you have created your files and stored in a safe place, you can always use them with nvflash, even if you upgraded your bootloader or even if you erased it. It's a nice low-level way to access the internal storage without requiring any installed bootloader, OS or recovery. Don't ever lose your blobs, they are the only way to enable nvflash.
bigstack said:
2) At the time TWRP was the ONLY option for me. How can I remove TWRP and get ClockWork on this? *note I dont care about anything on the device currently.
Click to expand...
Click to collapse
Easiest way: fastboot flash recovery cwm.blob
_that said:
As long as you don't upgrade your bootloader past 9.4.5.26, you can obtain the required files from your tablet using the procedure described at . What it does is described in the dev thread about nvflash - it does not mess with any abilities to flash stuff the normal way.
After you have created your files and stored in a safe place, you can always use them with nvflash, even if you upgraded your bootloader or even if you erased it. It's a nice low-level way to access the internal storage without requiring any installed bootloader, OS or recovery. Don't ever lose your blobs, they are the only way to enable nvflash.
Easiest way: fastboot flash recovery cwm.blob
Click to expand...
Click to collapse
1) So Once I follow that Guide I can update my Bootloader to anything even the newest .30 + and It will still be there and allow be to fall back if necessary.... Im on the last parts of the guide nvflash --resume --rawdeviceread 0 2944 bricksafe.img but do I run that in the FastBoot (hold down volume or) the APX (hold up) It didnt work with up trying down now..... Also is there a guide on how to actually Restore to a non bricked device using this?
2) fastboot flash recovery cwm.blob
--figured this out read next post!
*Of course im guessing that once this NVflash is installed its there no matter what I flash or return to stock ?
1) OK I managed to get NVflash installed and ran the last couple commands... Need to find the files to save off
2) I also managed to run the fastboot flash recovery recovery.img to get CMW touch installed and that works..
3) Right now I have the 4.0.3 Stock Still... with the NVflash installed... The Kernel is: 2.6.39.4 and the Build is: 9.4.5.26-....
If I Download a Jellybean ROM or CM10 (isn't this based of jellybean) and Install it I can assume that I can wipe out all my data (which i want)... As for the Kernel / Bootloader .. What if it gets updated to .30 or above? Or That wont matter now that NVflash is installed... I guess basally is NVflash a 1 off... meaning that as long as u can get it installed it will ALWAYS be there even after the updates above to when you could NOT install it?
bigstack said:
When I run the Line for the NVflash i get
C:\adt-bundle-windows\sdk\platform-tools>nvflash --resume --rawdeviceread 0 2944
bricksafe.img
Nvflash started
[resume mode] (it just sits here forever and i kill it)
^C
Click to expand...
Click to collapse
You must run it in APX mode, and you need to run wheelie with your blob before that line.
_that said:
You must run it in APX mode, and you need to run wheelie with your blob before that line.
Click to expand...
Click to collapse
I literally just updated the post above this.. If you could read that and Let me know If what I have done is correct.
bigstack said:
I literally just updated the post above this.. If you could read that and Let me know If what I have done is correct.
Click to expand...
Click to collapse
First save your files. Make backup copies. Post a list of the files that you saved if you are unsure - after you update, it's too late to get more.
Re-read this thread, the guide and the nvflash thread again, they should answer all your questions about nvflash.
To install a custom ROM that is based on JB (which is pretty much all of them), you need to install the Asus JB firmware first to get the latest bootloader. This will overwrite your custom recovery, but you already know how to restore it. Then you can flash whatever ROM you want.
Ok Files that I saved off are screen shot on the attachment... EDIT apparently im not allow to attach files... soo listed
* Also Added note. The driver pack that I downloaded from there site listed the device as a Samsung device in Device manager. However I was still able to enter APX mode and install NVFlash... Not sure if this is a good thing though.
View attachment 1571433
blob.bin
blob.log
bootloader.ebt
bricksafe.img
create.bct
factort-config.img
recovery.bct
unlock-token.img
I have read multiple NVFlash threads and I found * If you intend to use NvFlash please STAY AWAY from the 9.4.5.30 UPDATE ... Is this only to be able to install it?
If I need to update to the newest Firmware on Asus site wont this be above .30? Also What one on Asus site should I take. I see a ASUS Transformer Pad TF700T Firmware: V10.4.4.23 Only for US SKU (Android 4.1.1) I am in US so I figure that is the right one? Unless someone has a newer one. But will this wipe out NVFlash?
Am I able to update to a JB based rom without losing my NVFlash?
bigstack said:
The driver pack that I downloaded from there site listed the device as a Samsung device in Device manager. However I was still able to enter APX mode and install NVFlash... Not sure if this is a good thing though.
Click to expand...
Click to collapse
Strange, but if it worked, it's good
Just for additional verification, post the content of blob.log, and the file sizes of these 3 files:
bigstack said:
blob.bin
bricksafe.img
unlock-token.img
Click to expand...
Click to collapse
bigstack said:
I have read multiple NVFlash threads and I found * If you intend to use NvFlash please STAY AWAY from the 9.4.5.30 UPDATE ... Is this only to be able to install it?
Click to expand...
Click to collapse
I already wrote:
"After you have created your files and stored in a safe place, you can always use them with nvflash, even if you upgraded your bootloader..."
You also didn't "install" nvflash, you just created files so that you can *use* it when you need it. You will be able to use nvflash as long as you have these files, and as long APX mode works - since this is a very low-level mode, you cannot break it unless you have a hardware defect.
bigstack said:
If I need to update to the newest Firmware on Asus site wont this be above .30? Also What one on Asus site should I take. I see a ASUS Transformer Pad TF700T Firmware: V10.4.4.23 Only for US SKU (Android 4.1.1) I am in US so I figure that is the right one? Unless someone has a newer one.
Click to expand...
Click to collapse
10.4.4.23 is obviously newer than 9.4.5.30, and it's the latest one.
Based on your original version
Build - IML74K.US_epad-9.4.5.26-20120720
Click to expand...
Click to collapse
the US firmware is the right one for you.
_that said:
Strange, but if it worked, it's good
Just for additional verification, post the content of blob.log, and the file sizes of these 3 files:
Click to expand...
Click to collapse
blob.log content:
Generating encrypted EBT file 'bootloader.ebt'...done.
Generating encrypted recovery BCT file 'recovery.bct'...done.
Generating encrypted create BCT file 'create.bct'...done.
Generating blob file 'blob.bin'...done.
Adding create BCT to blob file [wheelie]...done.
Adding recovery BCT to blob file [wheelie]...done.
Adding bootloader to blob file [wheelie]...done.
Adding odmdata to blob file [wheelie]...done.
Adding chip id to blob file [wheelie]...done.
file sizes:
blob.bin - 1.87 MB (1,964,842 bytes)
blob.log ~ 1K
bootloader.ebt - 1.79 MB (1,887,968 bytes)
bricksafe.img - 11.5 MB (12,058,624 bytes)
create.bct - 5.98 KB (6,128 bytes)
factory-config.img - 5.00 MB (5,242,880 bytes)
recovery.bct - 5.98 KB (6,128 bytes)
unlock-token.img - 8.00 MB (8,388,608 bytes)
_that said:
I already wrote:
"After you have created your files and stored in a safe place, you can always use them with nvflash, even if you upgraded your bootloader..."
You also didn't "install" nvflash, you just created files so that you can *use* it when you need it. You will be able to use nvflash as long as you have these files, and as long APX mode works - since this is a very low-level mode, you cannot break it unless you have a hardware defect.
10.4.4.23 is obviously newer than 9.4.5.30, and it's the latest one.
Based on your original version the US firmware is the right one for you.
Click to expand...
Click to collapse
Ok I take this as Its ALWAYS there even if I update to later versions.
Next step if to get that downloaded and installed. ( I assume put onto SD then run the update in CWM ?)
*ALSO can a mod take my account out of this limited mode. I cant post links, or images etc. Thanks
bigstack said:
blob.log content
...
file sizes
...
Click to expand...
Click to collapse
Looks fine. Make safe backups of these files, then you should be able to recover from any software-induced brick in the future.
Ah, btw - you should also make a backup of partition 18, just in case. It contains the GPT and it's 524288 bytes. However that one should be identical on all devices (with the same storage size at least), so in an emergency case you could also use a backup from someone else - in contrast to bricksafe, factory-config and unlock-token which are specific to your device.
bigstack said:
Next step if to get that downloaded and installed. ( I assume put onto SD then run the update in CWM ?)
Click to expand...
Click to collapse
Right.
_that said:
Ah, btw - you should also make a backup of partition 18, just in case. It contains the GPT and it's 524288 bytes.....
.
Click to expand...
Click to collapse
How would I go about doing this? what command do I run and from where?
Also was I correct about being able to Update to any build / firmware no matter what version as I always have the NVflash there because I did it before I was on .30
ISSUE
I downloaded and installed the Firmware update.. Installed it Via CWM it went well device was usable. But now I lost root and When I try to Boot to the recovery manager I it trys but then Fails and I get a Droid guy with a Red Triangle.
FIXED: Flashed CWM and then Installed the 3.1.3 Superuser you can download via CWM when normally booted.
bigstack said:
How would I go about doing this? what command do I run and from where?
Click to expand...
Click to collapse
Same environment as in the official guide (tablet in APX mode, etc.). From your PC, enter these commands:
wheelie --blob blob.bin
nvflash --resume --read 18 gpt.img
bigstack said:
Also was I correct about being able to Update to any build / firmware no matter what version as I always have the NVflash there because I did it before I was on .30
ISSUE
I downloaded and installed the Firmware update.. Installed it Via CWM it went well device was usable. But now I lost root and When I try to Boot to the recovery manager I it trys but then Fails and I get a Droid guy with a Red Triangle.
FIXED: Flashed CWM and then Installed the 3.1.3 Superuser you can download via CWM when normally booted.
Click to expand...
Click to collapse
You need to read more carefully. The first question has already been answered in this thread multiple times. Also the issue with the lost recovery should not have surprised you, because I told you about it before.
Hello, I'm a noob at this so please be kind. I followed the below:
http://forum.xda-developers.com/tra...inners-guide-unlock-custom-rom-tf300-t3061648
I successfully:
Unlocked my TF300T's Bootloader
Installed custom recovery using fastboot
Rooted my tablet
Debloated the Tablet (Titanium Backup)
Backup up my current (OEM) SYSTEM ROM to microSD
So now I'm onto attempting a custom ROM. I'm a bit bored with 4.2.1 and would like to go to the same version of ROM my Note 7 has which is 6.0.1 Marshmallow or even try the new 7.0 Nougat.
I'm a little confused as to what ROM will or will not work. I see a few ROMS worth trying, but there install instructions reference a different Bootloader multiple flashes such as SuperSU or gapps.
Whats the best fool proof method to flash a new ROM with what I have and are there any simple one file ROM/ZIP/ Blob etc.. file that would do what I want?
Thank you.
broderp said:
Hello, I'm a noob at this so please be kind. I followed the below:
http://forum.xda-developers.com/tra...inners-guide-unlock-custom-rom-tf300-t3061648
I successfully:
Unlocked my TF300T's Bootloader
Installed custom recovery using fastboot
Rooted my tablet
Debloated the Tablet (Titanium Backup)
Backup up my current (OEM) SYSTEM ROM to microSD
So now I'm onto attempting a custom ROM. I'm a bit bored with 4.2.1 and would like to go to the same version of ROM my Note 7 has which is 6.0.1 Marshmallow or even try the new 7.0 Nougat.
I'm a little confused as to what ROM will or will not work. I see a few ROMS worth trying, but there install instructions reference a different Bootloader multiple flashes such as SuperSU or gapps.
Whats the best fool proof method to flash a new ROM with what I have and are there any simple one file ROM/ZIP/ Blob etc.. file that would do what I want?
Thank you.
Click to expand...
Click to collapse
Congratulations! Everything you did looks fine. So you are ready to install a custom rom. I would like to suggest one of the best: http://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702 (You may follow up the tread and report there!)
Please take care very exactly on the installation instruction in post #1 given by Timduru. And don't forget that you need Kang TWRP [email protected] Download here: http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. That's mandatory!
Good luck!
ebonit said:
Congratulations! Everything you did looks fine. So you are ready to install a custom rom. I would like to suggest one of the best: http://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702 (You may follow up the tread and report there!)
Please take care very exactly on the installation instruction in post #1 given by Timduru. And don't forget that you need Kang TWRP [email protected] Download here: http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. That's mandatory!
Good luck!
Click to expand...
Click to collapse
Thanks. As simple as the process was, as a noob (first time attempting this) I was really concerned about screwing this up and bricking my tablet.
The one you linked to was one of the ones I was considering and hence my question regarding what works with what I have already done. The noob mind (mine anyways) finds a dozen questions at every turn. In this case I would ask the following:
Q-Do I have to use Kang TWRP?
Q-How is it different than the TWRP I used on my Tablet?
Q-Will I need to constantly change TWRP versions depending on what ROM I want to use?
Q-Is there a danger to switching TWRPs?
Q-Doesn't flashing SuperSU after I flash Gapps overright and erase SuperSU or is there some unique way to flash (push?) both at the same time?
Q-Many more I'm sure!
To the noob, almost all the instructions I read appear to be written for someone who as done this many times. The level of detail needed for the novice is just not there or lost between the jargon used, with many steps not fleshed out because the author assumes a certain level of expertise.
I will definitely read these threads as best I can, but in the interim, is there any ROM that are known to be able to be flashed via the TWRP I currently have? The author of the version I used certainly made it seem like it was that simple, load the ROM/ zip file onto the MicroSD card and when in Custom recovery simply use the INSTALL feature to navigate to the file and press a button to flash and ..."BAM!!" you are running a new ROM.
ebonit said:
...
Please take care very exactly on the installation instruction in post #1 given by Timduru. And don't forget that you need Kang TWRP [email protected] Download here: http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. That's mandatory!
Good luck!
Click to expand...
Click to collapse
That version of KANG appears to be dead, as the thread has been closed and abondoned by the OP. So no new questions or help there....
Can I install that version over the top of my current version of TWRP the same way I did the first time? (change file to TWRP.blob etc.)
broderp said:
That version of KANG appears to be dead, as the thread has been closed and abondoned by the OP. So no new questions or help there....
Can I install that version over the top of my current version of TWRP the same way I did the first time? (change file to TWRP.blob etc.)
Click to expand...
Click to collapse
Please don't brick your tablet. First download Kang TWRP. It isn't dead. Try this https://www.androidfilehost.com/?fid=24052804347781183.
broderp said:
Can I install that version over the top of my current version of TWRP the same way I did the first time? (change file to TWRP.blob etc.)
Click to expand...
Click to collapse
Yes you can.
However Kang TWRP is a xxx.img file. You also can use your current TWRP and flash the image file. Attached you will find an image and a zip version.
ebonit said:
Please don't brick your tablet. First download Kang TWRP. It isn't dead. Try this https://www.androidfilehost.com/?fid=24052804347781183.
Click to expand...
Click to collapse
Sorry, bad choice of words on my part. By dead I meant that the thread was closed and I'm concerned getting answers would be harder as the OP was no longer actively looking there for questions.
ebonit said:
Yes you can.
However Kang TWRP is a xxx.img file. You also can use your current TWRP and flash the image file. Attached you will find an image and a zip version.
Click to expand...
Click to collapse
Ok, so if I read your comment correctly, I can copy the .img file to an SD card, boot into recovery and flash it from there OR I can fire up fastboot and the same steps I originally did to install custom recovery from my PC to accomplish the same thing... either way I should still have custom recovery, but with the KANG version. Right?
THANKS TO BOTH OF YOU FOR RESPONDING TO MY PREVIOUS POST. I appreciate the support.
Oh no....
Well crap. I put the .img file on my SD card and boot the tablet into recovery, I flashed the .img file to the rovery not boot partition. All appeared well....but when I go back to see if I have KANG recovery, it hangs anbd says Booting Failure Unrecoverable bootloader error (0x000000000)
EDIT: After I cleaned my pants, I used abd and fastboot to flash the original Blob file using my PC. This restored the custom recovery. I was freaking out for a few minutes.
I didn't change the file name of the kang .img file. Should I have done something different?
EDIT: Successful recovery to Kang2.8.7.2 !! :good::good: I used adb and my PC to send the .img file (renamed "twrpkang.img" for simplicity) and it worked great. I'm a pro..:silly:
broderp said:
Well crap. I put the .img file on my SD card and boot the tablet into recovery, I flashed the .img file to the rovery not boot partition. All appeared well....but when I go back to see if I have KANG recovery, it hangs anbd says Booting Failure Unrecoverable bootloader error (0x000000000)
Click to expand...
Click to collapse
Bad luck! Could you please describe what does it mean? : "I flashed the .img file to the rovery not boot partition."
ebonit said:
Bad luck! Could you please describe what does it mean? : "I flashed the .img file to the rovery not boot partition."
Click to expand...
Click to collapse
Not sure what I did wrong. I tried to do it within the old recovery menu and it hosed it. It found the file and mounted it successfully, but it seemed weird to be within the partition I was overwriting and writing to it. Kind of like you cant install windows while your using Windows...
The new version is much smoother.... Thanks, not to learn about this gapps super SU and how to flash all of these and in what order along with the ROM..as well as this wipe vs format thing...so confusing...