Related
I returned my original transformer that I rooted and installed Revolver on because of a bad touchscreen. Now on my new one I can't get to recovery. I rooted using razorclaw again, but when I try to get into recovery I get the android with an exclamation point. Any help would be appreciated.
Did you install CWM recovery?
Razorclaw only root. RecoveryInstaller
http://forum.xda-developers.com/showthread.php?p=19319421
Yeah, I found my mistake moments after I posted this. I was thinking there was a stock recovery to install CWM from. I forgot about the installer. Thanks for setting me straight. Back in business now.
I believe this is my first post on these forums. I just did the nachoroot mod today per
[ROOT] NachoRoot - supporting all firmware jan 3rd 2-118
and
[Update: Works On The OG Transformer, Too!] Exclusive: 'NachoRoot' Brings Root Access To The Transformer Prime, Even With The Newest Firmware:
on my TF101 B80 32 gb.
I did the procedure per the second link above. I've been able to verify root with Root Check Basic from the Android Market.
I've never rooted an Android device before and am quite concerned about unrooting, in case I ever need to return my unit to Asus.
I've heard I need cwm, the clockwork recovery mod, in order to unroot. I hope it is ok to do this after the initial rooting procedure.
Please pardon me if this has been asked before, as it my first time, and I find a lot of the documentation a bit cryptic.
Thanks in advance...
Yes the procedure to unroot with your build number required flashing a repacked stock ROM via CWM recovery. For TF with older SBK they can use NVFlash.
You can flash CWM anytime with RecoveryInstaller
http://forum.xda-developers.com/showthread.php?t=1346180
To unroot
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
Thanks fire the response!
I've managed to browse parts of the file system previously blocked. Otherwise, I haven't made another changes to my system. Its nice to finally where some of my apps have been storing data.
I am curious about cwm which I've installed. It enables recovery mode to restore the stock ROM. It is one of the two options presented after holding the power and volume down buttons together. One option is cold boot and the other is recovery. The recovery option was there before nachoroot and the cwm installations. What is different about the recovery option now versus before?
skallal said:
Thanks fire the response!
I've managed to browse parts of the file system previously blocked. Otherwise, I haven't made another changes to my system. Its nice to finally where some of my apps have been storing data.
I am curious about cwm which I've installed. It enables recovery mode to restore the stock ROM. It is one of the two options presented after holding the power and volume down buttons together. One option is cold boot and the other is recovery. The recovery option was there before nachoroot and the cwm installations. What is different about the recovery option now versus before?
Click to expand...
Click to collapse
Are you sure you have flashed CWM recovery? You should have a lot more options.
After installing RecoveryInstaller, did you open the app and click on "flash CWM recovery" tab?
I didn't click on the flash tab because I don't intend do recovery at this time. To be clear I understand what recovery is, I think it means to return my TF101 back to an unrooted state with the current ota release, which is .23, and also wipe out all my data. If this is incorrect, please let me know.
You said I should see more options than just the flash tab. What else should I see? And when should I see it?
Now that I've successfully rooted, my main objective is to learn how to return my device back to its unrooted state in order be ready for the ICS ota update when it arrives. If that means I'll also wipe out my data in the process, then I'll need to learn how to backup and restore.
Please do let me know if I understand the process or not. I still have have a reading and learning ahead.
Recovery lets you flash packages, ROM patches, and complete ROMs that require very deep (i.e. low level) system access.
If you don't intend to flash any custom ROMs (e.g. Revolver) or install things that need low level system access (e.g. a USB to Ethernet adapter) you won't need to flash CWM.
One of the admins on Transformer Forums gave me the impression I need cwm to unroot my TF101. That is the only reason I downloaded it.
If I don't need cwm to unroot, then I'll focus my reading on unrooting link listed earlier in this thread.
I don't have any interest in other roms, at least not for now. My concern, for now, is unrooting when it comes time for the ICS update...
baseballfanz said:
Yes the procedure to unroot with your build number required flashing a repacked stock ROM via CWM recovery. For TF with older SBK they can use NVFlash.
You can flash CWM anytime with RecoveryInstaller
http://forum.xda-developers.com/showthread.php?t=1346180
To unroot
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
Click to expand...
Click to collapse
The second link above (theunlockr.com) refers to old firmware (repacked-8.2.3.13_US_without_SU_app.zip).
Is that file already outdated?
Perhaps a newer version for .21?
Well it all depends on your serial number. Early builds (B60 and earlier plus some B70) you can use NVFlash to get back to totally stock.
If you have B80(and some B70) and above you'll need cwm recovery to get back to stock following the link i posted above.
I finally watched the video from your earlier post and it answered a quite a few questions.
Bottom line: when it comes time to update to ICS, do I need to unroot first?
The ICS update is my main reason for unrooting. I read for some users lost root after the last ota update to .21. I don't have any immediate need to unroot other than to prepare for the ICS update when yet comes.
And there's also a long term need unroot when and if I ever send the unit back to Asus for service.
So, my brand new Transformer came yesterday (From Amazon) and it has an SBK v2 bootloader (sbk detect under mac, serial is BC0KAS), here is what I understood, and ask for questions, after many reading, can you please confirm or correct?
1- SBK v1 can be rooted, put custom roms, return back to stock, unbrick in case something goes wrong with nvflash. [CONFIRMED]
2- SBK v2 can be rooted? (some say B70 can, or is it just B70 with SBK v1?) [CONFIRMED]
3- SBK v2 can have custom roms? (depends on point 2)? [CONFIRMED]
4- SBK v2 cannot have ClockWorkMod? [Wrong, SBKv2 CAN have ClockWorkMod]
5- SBK v2 does NOT support nvflash, so if you softbrick you cannot recover (I am certain of this one, I guess). [CONFIRMED, if you damage ROM & clockworkmod = BRICK]
What can be done then with an SBK v2 device? wait for developers to find the ways to crack it (as sbkv1), or have an nvflash working?
Is there some petition open to tell Asus to unblock the bootloader as they did with the Transformer Prime?
currently (after 1 day), I am already thinking of returning it back.
I know i might be asking a lot of questions, but information is not easily available in 1 thread.
Update:
New question: with SBKv2 is it possible to return back to stock (Stock ROM, unrooted with stock recovery)?
Thanks in advance...
SBK doesn't keep you from rooting from what I understand, the firmware version does (current 8.6.5.21 has been cracked and can be rooted by nachoroot, or if not can be firmware upgraded to 8.6.6.19 and rooted with razorclaw)
SBK2 simply keeps you from using NVFlash to recover, as far as I know, once you are rooted, you can install CWM recovery on any SBK version.
Just alot of SBK2 owners have not rooted or installed CWM if they did root for fear of losing their recovery (if you bungle the recovery, you may be able to flash your recovery through the ROM, if you mess up your ROM, you can flash another ROM through CWM or stock recovery, BUT if your recovery img is corrupted AND your ROM stops working, SBK1 can flash both via NVFlash, SBK2 is effectively bricked)
EDIT: SBK2 USED to keep you from being able to root when NVFlash was the only method available for rooting and installing superuser and busybox, see here
http://forum.xda-developers.com/archive/index.php/t-1347388.html
I was going to say I will try to NVFlash my device and tell you if it is SBK1 or 2, I assumed it would be SBK2 because it is B70, but lo and behold it was SBK1..I would have been lucky a few months ago before the razorclaw app was developed and SBK2 was rooted, but I didn't get my TF until after that..
So, SBK1 here have gone to stock many times, but cannot confirm the procedure for SBK2 tablets, though I assume it is possible. Thought for sure I was going to be able to come back and say my TF was SBK2 and had been to stock, but nope haha
EDIT: considering you can backup your entire setup via CWM, recovery mage and all, and flash it wthin CWM (like restoring the backup) is evidence to me that you can no doubt unroot an SBK2 as long as you have a working recovery image.
From what I understand, the first thing to do on a new device is to have root (with the tools you mentioned), once you have this (stock ROM with root), you can install CWM, and with CWM you can install custom and stock roms.
but how can I bring back the standard Stock recovery? when I have stock unrooted ROM I can't flash Recovery partition from the Android itself, and nvflash doesn't work on SBK2. can CWM be used to flash a stock recovery over itself?
Is there any chance that Asus will unlock the TF101 when it releases the tool to unlock the Transformer Prime (in February, as promissed)? in case they both use same blocking technology?
mcbyte_it said:
From what I understand, the first thing to do on a new device is to have root (with the tools you mentioned), once you have this (stock ROM with root), you can install CWM, and with CWM you can install custom and stock roms.
but how can I bring back the standard Stock recovery? when I have stock unrooted ROM I can't flash Recovery partition from the Android itself, and nvflash doesn't work on SBK2. can CWM be used to flash a stock recovery over itself?
Is there any chance that Asus will unlock the TF101 when it releases the tool to unlock the Transformer Prime (in February, as promissed)? in case they both use same blocking technology?
Click to expand...
Click to collapse
Yes you can flash stock recovery over cwm from within cwm, you have to have the file..i found it and have it on my hard drive, but can't remember where i got it from..the same procedure as going stock on sbk1 tablets
The proof that you can flash recovery while in recovery mode is that you can install higher versions or different developer's versions of recoveries from cwm. Im sure when running cwm it is being read from ram so flashing the recovery partition will only affect your recovery after you reboot (i.e. Can technically go into cwm, flash recovery partition first and then flash stock rom, but i believe packages are available to flash both at once, and there would be no reason to do it in this order, but im pretty sure it could be done)
Somewhere on here is a guide how to return to stock to prepare for the ics update, it should contain the odd bits and links to fill in my sparse knowledge.
Getting back to stock ROM and recovery
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
That's the one!
8329 recovery.zip.. Btw it should be noted that the recovery image is not region-branded, that should mean it will work with any region, while you will need to make sure to get the region-specific firmware..
And i did the procedure in reverse from that thread, not to confuse, but i:
Placed both files (recovery and firmware) into my sd card root
Booted into cwm and flashed stock recovery, wipe everything before powering down
Rebooted into recovery again and flashed the firmware with stock recovery.
I think it will work either way, i left my rooted rom in place so i could install cwm if the recovery flash failed, i suppose the alternative is leaving your recovery in place in case the stock rom flash fails..i just like knowing on the first reboot whether my first flash was successful and not flashing blind imo.
Bump.
This post suggest new Transformers can be nvflashed too.
http://forum.xda-developers.com/showthread.php?t=1518552
Waiting for answer from OP to see what he has to say.
Anyone else got any news?
josteink said:
Bump.
This post suggest new Transformers can be nvflashed too.
http://forum.xda-developers.com/showthread.php?t=1518552
Waiting for answer from OP to see what he has to say.
Anyone else got any news?
Click to expand...
Click to collapse
SBK v2 is still not nvflash compatible
josteink said:
Bump.
This post suggest new Transformers can be nvflashed too.
http://forum.xda-developers.com/showthread.php?t=1518552
Waiting for answer from OP to see what he has to say.
Anyone else got any news?
Click to expand...
Click to collapse
That thread is full of bad information and garbage. I would forget it exists.
I was under the impression from reading different Asus statements that the sbk for TF-101 was going to be released with ICS the way it was with TF-201, did Asus not keep their word on this?
Cheers!
-M
Xda member since 2007
dragon_76 said:
I was under the impression from reading different Asus statements that the sbk for TF-101 was going to be released with ICS the way it was with TF-201, did Asus not keep their word on this?
Cheers!
-M
Xda member since 2007
Click to expand...
Click to collapse
That would be news to me. If you could find a source for this statement, I would be interested.
From what I understood reading (this forum and other sites), the story is different between TF101 and TF201: the Prime has the bootloader locked/encrypted, and with it locked you can't even install the CWM recovery, while with sbkv2 you can do everything except nvflash, so i doubt that asus will release anything for the sbkv2 transformers.
anyway, i am not following the subject, but does the new Prime unlocker allow something like nvflash to work?
mcbyte_it said:
5- SBK v2 does NOT support nvflash, so if you softbrick you cannot recover (I am certain of this one, I guess). [CONFIRMED, if you damage ROM & clockworkmod = BRICK]
Click to expand...
Click to collapse
What can I do with brick? Only waiting for some solution?
Did Asus could repair it for a fee?
RMA
Thinking about calling ASUS to ***** about this tablet being locked and demanding the opportunity to either downgrade to sbk1 or upgrade to a prime. I'll let y'all know my findings.
Styxiak said:
What can I do with brick? Only waiting for some solution?
Did Asus could repair it for a fee?
Click to expand...
Click to collapse
Until a solution is found, you can use a bricked device as a very nice door stop.
Sent from my Transformer TF101 using Tapatalk 2
A solution has been found
http://forum.xda-developers.com/showthread.php?t=1688447
nvflash for sbk v2,finally ?
android root .mobi has a released a a solution, i am going to try it, will post results when done
The revival of the thread from the dead! -dun dun dun-!
Anyway, yes 'Wheelie!' Nvflash for Sbkv2 devices has been released, and works very well on my b70 Sbkv2
it only works on the tf101 though, not the G or Slider.
I'm about to buy used Eee Pad Transformer TF101, with dock/keyboard. It has serial number starting with B90KAS and latest firmware update (ICS).
What is the current status of bootloader unlocking craft? Would I be able to install Ubuntu/OpenSUSE and/or use custom kernels with latest KatKiss ROMs?
I can get into recovery but after that then to android with red exclamation or usb fastboot screen or fdr screen cold boot. Once I get to red x andy I can go no further. Tried all combo of button pushes and will not go to blue menu for clear cache partition fdr or re start. I am trying to clean cache . It just sits at Andy then after about 5 Min's tab reboots by itself. Have tried about 6 times same thing happens each time, Any idea what is happening or what I am doing wrong or is recovery clean cache partition gone? Thanks
Other wise JB install went smooth no problems and tab is working well . seems smoother . Also kept root with voodoo.
Same here...
I had this same issuethis once, after update with the same intention, was considering either clear cache or to do a full wipe from that level as opposed to doing it through settings. Almost had a stroke u I saw the animated android with the famous (or rather infamous red triangle) Ended up using the one in Backup and Restore in system settings. Think I will try this again, since this concerns me. Anyone else seeing this? If recovery is broken in JB, we have another wait on out hands. Sigh
ditto, starting to see a trend...
Same here, I've had no luck getting past the initial stock recovery screen. Not good.
When you flash OTA update you lose custom recovery.
i have custom recovery installed on JB but it is useless. nothing wants to mount.
ultramegaman963 said:
i have custom recovery installed on JB but it is useless. nothing wants to mount.
Click to expand...
Click to collapse
Same here. Seems as though mount points changed and I can't seem to get adb in twrp...
What is different?
cmdrdredd said:
When you flash OTA update you lose custom recovery.
Click to expand...
Click to collapse
I am using Asus stock recovery. When I got tablet it was on .22 rooted tab everything ok. got ota for .26 kept root all ok still could get into recovery got .30 ota kept root again with voodoo. everything o k got into recovery wiped cache no problem. got JB ota everything ok tried to get into recovery and my above post happened? I am confused as to how jb is now custom recovery versus all other otas. What has turned from stock recovery to custom recovery
Tomv5314 said:
I am using Asus stock recovery. When I got tablet it was on .22 rooted tab everything ok. got ota for .26 kept root all ok still could get into recovery got .30 ota kept root again with voodoo. everything o k got into recovery wiped cache no problem. got JB ota everything ok tried to get into recovery and my above post happened? I am confused as to how jb is now custom recovery versus all other otas. What has turned from stock recovery to custom recovery
Click to expand...
Click to collapse
I kept root with OTA Root Keeper. So I was able to reflash TWRP from Goomanager. But anyway it cannot mount either the internal storage nor the microSD card. There seems to be no working recovery for JB, yet.
FreakyPriest said:
I kept root with OTA Root Keeper. So I was able to reflash TWRP from Goomanager. But anyway it cannot mount either the internal storage nor the microSD card. There seems to be no working recovery for JB, yet.
Click to expand...
Click to collapse
That's not entirely accurate... if you mount /system in twrp, you will see externalSD is mounted instead. Kind of goofy. Messed me up good, since I expected to install supersu through recovery. Now I have no root and no useful recovery! Anyone know the mount point cure?
Sent from my ASUS Transformer Pad TF700T using xda premium
still nothing
xfinrodx said:
That's not entirely accurate... if you mount /system in twrp, you will see externalSD is mounted instead. Kind of goofy. Messed me up good, since I expected to install supersu through recovery. Now I have no root and no useful recovery! Anyone know the mount point cure?
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
Has anyone been able to get past red exclamation point andy in recovery mode yet?
http://forum.xda-developers.com/showthread.php?t=1886901
This recovery works with the JB Kernel. Flash it using fastboot.
FineWolf said:
http://forum.xda-developers.com/showthread.php?t=1886901
This recovery works with the JB Kernel. Flash it using fastboot.
Click to expand...
Click to collapse
I like a few others was stuck at the infamous red triangle with no way to get into TWRP. Lost custom recovery. Did the above mentioned in fastboot and was able to flash CWM and then was able to flash Supersu via CWM. Got me out of a jam, unfortunately missed the opportunity to NVFLASH on .26, had already upgaded to .30
merge thread?
amaury48 said:
I like a few others was stuck at the infamous red triangle with no way to get into TWRP. Lost custom recovery. Did the above mentioned in fastboot and was able to flash CWM and then was able to flash Supersu via CWM. Got me out of a jam, unfortunately missed the opportunity to NVFLASH on .26, had already upgaded to .30
Click to expand...
Click to collapse
Could one of the moderators merge this thread with Red triangle in locked stock recovery ? They are both concerning the same thing thanks Tom
I just bought a new Infinity today to replace my Prime. I never bothered unlocking/rooting/etc the Prime but given I'm starting from scratch thought I'd go that route out of the box on the Infinity.
I've been carefully reading all of the guides, etc and have used the unlock tool, then created the nvflash backup files (which involves a custom bootloader first).
I then decided I'd take a stab at trying CleanROM Inheritance. One of the first notes indicates that the latest JB Bootloader is required, so I went ahead and downloaded the US JB Bootloader from the link and flashed as described. Now I can't boot up anymore. I can still get to recovery, etc, but I don't know what I should do next. Was this the wrong thing to do? Or did it not flash right?
What should I do next? I'm not new to flashing but w/ my Galaxy Nexus things have always gone pretty smoothly.
Thanks in advance.
EDIT: Note I tried the initial steps for custom bootloader when setting up for nvflash ( http://androidroot.mobi/t3_nvflash/ ) but it doesn't work this time around...
From the link:
"Now that you are in fastboot mode please run the following command to flash the AndroidRoot bootloader:-
$ fastboot -i 0x0b05 flash staging ebtblob.bin"
But this has no effect....
ALSO,
I had not accepted the software update from Asus yet so I was still on ICS. Does that have anything to do w/ my problem? What should I do?
Kidd_Funkadelic said:
I then decided I'd take a stab at trying CleanROM Inheritance. One of the first notes indicates that the latest JB Bootloader is required, so I went ahead and downloaded the US JB Bootloader from the link and flashed as described. Now I can't boot up anymore. I can still get to recovery, etc, but I don't know what I should do next. Was this the wrong thing to do? Or did it not flash right?
What should I do next?
Click to expand...
Click to collapse
Simply boot to recovery and install CROMI.
Kidd_Funkadelic said:
EDIT: Note I tried the initial steps for custom bootloader when setting up for nvflash ( http://androidroot.mobi/t3_nvflash/ ) but it doesn't work this time around...
From the link:
"Now that you are in fastboot mode please run the following command to flash the AndroidRoot bootloader:-
$ fastboot -i 0x0b05 flash staging ebtblob.bin"
But this has no effect....
Click to expand...
Click to collapse
Are you on Windows? The "$" sign is not used under Windows -- have you tried typing "fastboot -I.... " ?
_that said:
Simply boot to recovery and install CROMI.
Click to expand...
Click to collapse
Are you suggesting that the JB bootloader is not the issue? I would think if I get stuck at the asus screen then it doesn't matter what the ROM is.
Either way I'm stuck at the moment w/out adb and no SD card. I'm running out on my lunch break to pick one up, which should be all I need to get working again. To be safe I'm going to go back to the .30 ICS stock image first. Once I know that worked, I'll take another stab at CROMI.
Kidd_Funkadelic said:
Are you suggesting that the JB bootloader is not the issue? I would think if I get stuck at the asus screen then it doesn't matter what the ROM is.
Click to expand...
Click to collapse
My train of thought was this: You said you can still get to recovery. TWRP supports adb, so you can send the CROMI zip via adb (or use a microSD card if you have one), then install it. CROMI is based on JB, so it is compatible with the JB bootloader, and should boot fine after installation.
_that said:
My train of thought was this: You said you can still get to recovery. TWRP supports adb, so you can send the CROMI zip via adb (or use a microSD card if you have one), then install it. CROMI is based on JB, so it is compatible with the JB bootloader, and should boot fine after installation.
Click to expand...
Click to collapse
Gotcha. I didn't realize TWRP supported adb. Anyway I was able to get back up and running w/ my nvflash backups, though I have to say finding info on actually using the backup files took a ton of digging and some trial and error... Now to try again at CROMI!
I did something very similar and am not sure how to proceed. I have the latest version of twrp and my infinity is rooted + unlocked. It was running ics. I then found what was likely the same US jb bootloader link under a thread that gave instructions for installing cromi. After flashing the jb bootloader via recovery, I got a loading bar, then while attempting to boot is got stuck on the Asus screen. Rebooting leads to a reboot loop. I can still access twrp recovery. Flashing cromi or reflashing the same bootloader yields an error message.
I never did anything with nvflash.
What should I do next? Still kind of fresh to this.
SilentOrchestra said:
Flashing cromi or reflashing the same bootloader yields an error message.
Click to expand...
Click to collapse
And now we are supposed to guess what error message you saw?
The next step is to set up an adb connection from a computer to your TWRP. This way you can get more detailed info what went wrong.
SilentOrchestra said:
I did something very similar and am not sure how to proceed. I have the latest version of twrp and my infinity is rooted + unlocked. It was running ics. I then found what was likely the same US jb bootloader link under a thread that gave instructions for installing cromi. After flashing the jb bootloader via recovery, I got a loading bar, then while attempting to boot is got stuck on the Asus screen. Rebooting leads to a reboot loop. I can still access twrp recovery. Flashing cromi or reflashing the same bootloader yields an error message.
I never did anything with nvflash.
What should I do next? Still kind of fresh to this.
Click to expand...
Click to collapse
To me that sounds like an incompatible bootloader, e.g. ICS bootloader trying to load JB ROM. Could you check the bootloader version?
FordPrefect said:
To me that sounds like an incompatible bootloader, e.g. ICS bootloader trying to load JB ROM. Could you check the bootloader version?
Click to expand...
Click to collapse
I agree, it seems you never updated to a JB rom. A JB boot loader needs a JB Rom, It seems the JB boot loader wont boot ICS. Just flash Cromi and you should be good.
Tylor
Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: CleanRom Inheritance 3.4.4 Odex
Kernal: Hundsbuah V2.0 OC 1.75 GHz
Theme: Timberwolf's Blues & Jazz Theme V1.9