hi i tried rooting my tf300t using this method http://forum.xda-developers.com/showthread.php?p=26435786#post26435786 i got to the part where you have to flash the root signed.zip and i did flash it but then when i press reboot system now it asks me "root access possibly lost. Fix? THIS CAN NOT BE UNDONE" then it gives me options no , yes-fix root (/system/xbin/su), ******go back*****. anyone know what i should do. iv tried all 3 then going into root checker it says you do not have proper root access but i do have super user in my apps list and titanium backup will not work.
anybody know what to do?
Try using twrp recovery for flashing instead of cwm.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I agree. TWRP is the way to go. Also, if you are going to flash a custom ROM that is already rooted, don't even worry about rooting it with the root zip because it's not needed. The rooted ROM will take care of rooting it for you.
thanks
thanks twrp worked.
Thanks, got it rooted. But now I installed an app that gives me a black screen of death when it boots (LCD MODDER). I am int he process right now of recovering a backup.
Related
While troubleshooting another issue I did a factory reset. I'm running stock JB. I rooted on ICS and kept root via ota root keeper. Anyway, after the factory reset none of my apps can gain root. /system/bin/su is there. I tried installing Superuser app and SuperSU but that didn't help.
What am I doing wrong?
Thanks.
EvoXOhio said:
While troubleshooting another issue I did a factory reset. I'm running stock JB. I rooted on ICS and kept root via ota root keeper. Anyway, after the factory reset none of my apps can gain root. /system/bin/su is there. I tried installing Superuser app and SuperSU but that didn't help.
What am I doing wrong?
Thanks.
Click to expand...
Click to collapse
You had to have installed SuperSU and Superuser prior to updating to Jelly Bean. If you had the SuperSU binary, and backed up your root with Voodoo OTA Rootkeeper prior to updating.... you will be able to fully restore your root access after the Jelly Bean update.
If you only had Superuser prior to updating and backed up using Voodoo, you will most likely have lost your root, like several other TF300T users.
Ongoing discussion here:
THREAD
TDMVP73 said:
You had to have installed SuperSU and Superuser prior to updating to Jelly Bean. If you had the SuperSU binary, and backed up your root with Voodoo OTA Rootkeeper prior to updating.... you will be able to fully restore your root access after the Jelly Bean update.
If you only had Superuser prior to updating and backed up using Voodoo, you will most likely have lost your root, like several other TF300T users.
Ongoing discussion here:
THREAD
Click to expand...
Click to collapse
I did have super user installed before the JB update. Oh well I think my other issue is hardware so.I'm going to get a replacement tablet anyway.
EvoXOhio said:
I did have super user installed before the JB update. Oh well I think my other issue is hardware so.I'm going to get a replacement tablet anyway.
Click to expand...
Click to collapse
I said SuperSU, not just Superuser. You need to have both installed... at least that's what I've heard works perfectly so far.
TDMVP73 said:
I said SuperSU, not just Superuser. You need to have both installed... at least that's what I've heard works perfectly so far.
Click to expand...
Click to collapse
My issue is different than what you linked to. I updated to JB and restored root just fine. That's what that thread is about. My issue is a factory reset killed root
EvoXOhio said:
My issue is different than what you linked to. I updated to JB and restored root just fine. That's what that thread is about. My issue is a factory reset killed root
Click to expand...
Click to collapse
Oh, okay, sorry I misread. Doh!
Yeah, you're right, factory reset shouldn't break root. That is strange!
EvoXOhio said:
My issue is different than what you linked to. I updated to JB and restored root just fine. That's what that thread is about. My issue is a factory reset killed root
Click to expand...
Click to collapse
yes a factory reset usually kills root, at least that's how i unroot my old-broken nook tablet 6 months ago.
I have a thread on this too. Basically you can't use the debugfs method anymore because you can't symlink /data/local anymore. So if you restore normally after the job update, you're fine, but if you do a wipe, it doesn't work anymore despite such being in /system/xbin.
I'm going to assume we'll just have to wait for these awesome devs to come up with another exploit. Either that or unlock the bootloader and go the custom ROM route.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
I have a thread on this too. Basically you can't use the debugfs method anymore because you can't symlink /data/local anymore. So if you restore normally after the job update, you're fine, but if you do a wipe, it doesn't work anymore despite such being in /system/xbin.
I'm going to assume we'll just have to wait for these awesome devs to come up with another exploit. Either that or unlock the bootloader and go the custom ROM route.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I guess right now bootloader is unlocked.
Because I didn't use unlock app from Asus, but I can get access to fastboot usb download protocol.
if you press vol down + power you'll get acces to a lot of functionality. Maybe it can help to get root back
PS: I lost my root too... And right now I'm trying to get it back.
neo_u said:
I guess right now bootloader is unlocked.
Because I didn't use unlock app from Asus, but I can get access to fastboot usb download protocol.
if you press vol down + power you'll get acces to a lot of functionality. Maybe it can help to get root back
PS: I lost my root too... And right now I'm trying to get it back.
Click to expand...
Click to collapse
No bootloader is not unlocked. I think that is a result of the update. I have not tried it but perhaps it could be used to flash .30 back on it? Care to try?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
No bootloader is not unlocked. I think that is a result of the update. I have not tried it but perhaps it could be used to flash .30 back on it? Care to try?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I can't try it right now, because I need to leave from the office.
But, I assume that we use fastboot -i 0x0B05 flash recovery twrp.blob this function to update recovery because bootloader is now accessible
I can try it only tomorrow morning. Maybe some else can try it faster and write here the result.
neo_u said:
I can't try it right now, because I need to leave from the office.
But, I assume that we use fastboot -i 0x0B05 flash recovery twrp.blob this function to update recovery because bootloader is now accessible
I can try it only tomorrow morning. Maybe some else can try it faster and write here the result.
Click to expand...
Click to collapse
I don't know about the exact command structure but I did see a sample listing of command formats, similar to what you'd see if you typed adb with no arguments.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I have a strange problem. A while ago I successfully unlocked my infinity. That was before the jb update. I also successfully flashed custom recoveries and several roms. Didn't ran into any problems. When the official jb update came out, I restored original recovery and flashed a stock ics Rom, and after that successfully applied the jb update. The second update .30 also went smooth. I used the update file from Asus servers. Now I want to flash a custom recovery again in order to flash cleanrom. In adb I see my device and I can reboot with fastboot and stuff. So I think my drivers are ok. However as soon as I start to flash recovery.img it just says sending recovery and that's it. It just hangs there. Nothing happens. I tried everything, from changing usb ports and uninstalling drivers... It just can't send the recovery img. I use Scott's script to flash the recovery.blob. any ideas?
Sent from my HTC One X using xda app-developers app
might try the GOOManager in the play store
hillyard said:
might try the GOOManager in the play store
Click to expand...
Click to collapse
I can't use it because it needs root, and as long as I don't have a custom recovery I'm unable to root my stock jellybean Rom. Or is there already another way to root?
Sent from my HTC One X using xda app-developers app
glenner05 said:
I can't use it because it needs root, and as long as I don't have a custom recovery I'm unable to root my stock jellybean Rom. Or is there already another way to root?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Are you saying you can not get TWRP or CWM installed ? or are you saying you do have one installed but no root ?
If it is the latter then can't you just flash a custom rom that has root built in ( like Baked ) then go back to twrp and now with root you can wipe and flash stock. ? I am sorry if I am miss understanding your question. But at least you get a free 'bump'
Thibor69 said:
Are you saying you can not get TWRP or CWM installed ? or are you saying you do have one installed but no root ?
If it is the latter then can't you just flash a custom rom that has root built in ( like Baked ) then go back to twrp and now with root you can wipe and flash stock. ? I am sorry if I am miss understanding your question. But at least you get a free 'bump'
Click to expand...
Click to collapse
He said he has no root (why he couldn't use Goomanger) and he can't flash recovery.
buhohitr said:
He said he has no root (why he couldn't use Goomanger) and he can't flash recovery.
Click to expand...
Click to collapse
Thats correct, i am trying to get custom recovery, after that root is no problem.
Edit: i just installed a clean windows 8 installation. So no old drivers left behind or other weird stuff. I put my transformer in fastboot mode, driver is automatically installed, i see it under device manager. Stillno luck.... it hangs saying sending recovery.... no error messages. My previous attempt was under win7.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
glenner05 said:
Thats correct, i am trying to get custom recovery, after that root is no problem.
Edit: i just installed a clean windows 8 installation. So no old drivers left behind or other weird stuff. I put my transformer in fastboot mode, driver is automatically installed, i see it under device manager. Stillno luck.... it hangs saying sending recovery.... no error messages. My previous attempt was under win7.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
Click to expand...
Click to collapse
Glenner, did you make sure you have the img file in the same folder as you fastboot/adb command files?
If it says "sending recovery", I'd assume that it found the local file.
I don't use Windows, but I always read about driver issues in Windows. Maybe the auto-installed driver is wrong? Does "fastboot devices" return question marks or nothing?
i'm happy to report that finally it worked! seemed something strange with drivers/USB ports after all. Despite i already changed USB ports under my win 7 installation, i tried it again under win8, and suddenly it worked. I didn't reinstall the drivers or something, all went automatically. So the strange issues are driver issues for sure. Anyway, currently happy running cleanrom 2.3
thanks for all your suggestions and thinking along.....
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
I have Jelly Bean 10.4.2.17 installed with 4.1.1 Android~ Im trying to root the device and tried by: Unlocking the bootloader and flashing onto the tablet cwm. From there, I Tried installing the root-signed.zip file from http://forum.xda-developers.com/showthread.php?t=1668173~ After installing and trying to reboot, I get a message from cwk saying "you may lose root if you restart" something along those lines. After reboot, I try using root checker but no pop up comes up from superuser. Anybody have any ideas on rooting this device?
ttareen said:
I have Jelly Bean 10.4.2.17 installed with 4.1.1 Android~ Im trying to root the device and tried by: Unlocking the bootloader and flashing onto the tablet cwm. From there, I Tried installing the root-signed.zip file from http://forum.xda-developers.com/showthread.php?t=1668173~ After installing and trying to reboot, I get a message from cwk saying "you may lose root if you restart" something along those lines. After reboot, I try using root checker but no pop up comes up from superuser. Anybody have any ideas on rooting this device?
Click to expand...
Click to collapse
I recommend using twrp to flash, not cwm. Follow step 3 of this guide. http://forum.xda-developers.com/showthread.php?p=30516010
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I have modified the part 3 of this guide and you will find here:
Small guide for Install recovery and rooting when you are already to JB
Confirmation of TWRP on virgin 10.4.2.17
philos64 said:
I have modified the part 3 of this guide and you will find here:
Small guide for Install recovery and rooting when you are already to JB
Click to expand...
Click to collapse
Thanks for the guide. I have a tf300t on version 10.4.2.17. It has never been rooted/unlocked. I'm too scared to try the guide (which is very clear), since I cannot find any references of anybody with a clean slate 10.4.2.17 who installed TWRP. I bricked a phone before, so please have some understanding...
Can somebody please confirm that they have executed this successfully?
Thanks alot!
Just read around development forum
Sent from my HOX between sky and earth and using Tapatalk
I have repeatedly. I say repeatedly because every time Asus releases an update, it wipes out root and recovery when I do a full system install, so I put it right back. I did it on v10, v13, and now v17.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
drakeSW said:
Thanks for the guide. I have a tf300t on version 10.4.2.17. It has never been rooted/unlocked. I'm too scared to try the guide (which is very clear), since I cannot find any references of anybody with a clean slate 10.4.2.17 who installed TWRP. I bricked a phone before, so please have some understanding...
Can somebody please confirm that they have executed this successfully?
Thanks alot!
Click to expand...
Click to collapse
The guide assumes you are unlocked, otherwise everything is spot on.
Copy and save the terminal commands - good to have in your bag of tricks once you are rooted.
I'm pretty confused at the moment. I just unlocked my device using the ASUS app but now I can't find a thread on what to do now so I can start flashing roms. This is what I've gathered so far and correct me if I'm wrong on any of this. So I flash CWM using adb then flash su through recovery then I'm ready to go with stock root without a wipe right?
I'm on version 10.4.4.20 if that helps at all.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
The next step after unlocking is to install a custom recovery. If you are already rooted, you can use some app and do it on the device (Goo Manager or ROM Manager?). In any case, you can use fastboot from a PC to flash a blob.
Flashing su is only useful if you don't plan to flash another ROM afterwards.
_that said:
The next step after unlocking is to install a custom recovery. If you are already rooted, you can use some app and do it on the device (Goo Manager or ROM Manager?). In any case, you can use fastboot from a PC to flash a blob.
Flashing su is only useful if you don't plan to flash another ROM afterwards.
Click to expand...
Click to collapse
Nope not already rooted. I'm 100% stock minus the unlocked bootloader. No blobs. I'm really just looking for root permissions on this device, flashing custom roms will come but probably not until Google fixes a few issues with 4.2. I guess what I'm really trying to ask is at this point, do I just fastboot flash the CWM recovery.img, then obtain root privileges by flashing superuser? If it's really that simple this is the easiest device I've ever rooted.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
markalyea2 said:
Nope not already rooted. I'm 100% stock minus the unlocked bootloader. No blobs. I'm really just looking for root permissions on this device, flashing custom roms will come but probably not until Google fixes a few issues with 4.2. I guess what I'm really trying to ask is at this point, do I just fastboot flash the CWM recovery.img, then obtain root privileges by flashing superuser? If it's really that simple this is the easiest device I've ever rooted.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Follow the link below and start with section 2 for flash recovery twrp and use twrp to flash root.
http://forum.xda-developers.com/showthread.php?p=32825557
markalyea2 said:
I'm really just looking for root permissions on this device, flashing custom roms will come but probably not until Google fixes a few issues with 4.2. I guess what I'm really trying to ask is at this point, do I just fastboot flash the CWM recovery.img, then obtain root privileges by flashing superuser?
Click to expand...
Click to collapse
Yes, to root your current stock ROM, that's it.
Ah, almost - the recovery must be in NVidia blob format for the TF700's fastboot implementation. The bootloader only accepts signed blobs for flashing, but after unlocking does not require the signature to match, or even to be actually present.
buhohitr said:
Follow the link below and start with section 2 for flash recovery twrp and use twrp to flash root.
http://forum.xda-developers.com/showthread.php?p=32825557
Click to expand...
Click to collapse
Do not follow that guide blindly - at least, use a current version of TWRP. Version 2.2 is not compatible with the JB bootloader and may brick your device if you select "wipe data" from the bootloader menu.
My S3 is rooted with TWRP 2.5.0.0 installed and working fine. I want to upgrade to 2.6, but I'm having trouble. Stuck...
I tried GooManager using the "Install OpenRecoveryScript" menu item. It recognizes my device correctly, shows me the file it's going to download (openrecovery-twrp-2.6.3.1-d2vzw.imp) and proceeds to the download page. I get no progress or activity messages from here on until it's all over. After 5 seconds or so (less probably) a system message appears at the bottom that the recovery was installed. The message is in the same style as the hovering message that acknowledges an app attains root priv.
But when I boot into recovery, I'm still on 2.5.0.0. Anybody else have this problem?
(About me: I'm familiar and comfortable with most of the operations for flashing ROMs but I'm not deeply technical with Android...so I don't really know what needs to happen when you mess with a recovery image.)
Thanks,
David
Go to the official twrp website, search for our device (d2vzw), and download the latest img under "Download-Recovery Image Method (DD)," and download Flashify from the Play Store. Next, open Flashify, press "Recovery Image" and find the img file that you downloaded, and flash away.
Your advice worked. But I had to jump a few extra hoops that are probably worth documenting.
When I installed and ran Flashify, it told me I had lost root -- which would explain a lot. And YES, my SU app was gone.
So I researched how to get back root and found a post that recommended I confirm that I had really lost root. It recommended I install SuperSU app.
And they were right. SuperSUinstalled and obtained root. It could then grant root to Flashify AND I successfully flashed / upgraded TWRP to 2.6.3.1
I run SlimRom. I wonder what happened to their SU app...
Thanks again!
Sent from my SCH-I535 using xda app-developers app
davidb1835 said:
Your advice worked. But I had to jump a few extra hoops that are probably worth documenting.
When I installed and ran Flashify, it told me I had lost root -- which would explain a lot. And YES, my SU app was gone.
So I researched how to get back root and found a post that recommended I confirm that I had really lost root. It recommended I install SuperSU app.
And they were right. SuperSUinstalled and obtained root. It could then grant root to Flashify AND I successfully flashed / upgraded TWRP to 2.6.3.1
I run SlimRom. I wonder what happened to their SU app...
Thanks again!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Cool! I'm using SlimKat and when I'm on AOSP, I don't usually have SuperSU since root is enabled in Developer Settings. I had to do the same on SlimBean as well. Of course, it doesn't matter now but it's there for future reference.
Sent from my SCH-I535 using Tapatalk 4
That's what is so weird. I had enabled Root in Dev Options a while ago. But the app or system process or whatever seems to have stopped fishing out root. Installing a new SU app has brought things back to normal.
Glad to hear you're playing with SlimKat. That was the main reason I wanted to upgrade TWRP. I read you should be on a 2.6 version to flash SlimKat.
Sent from my SCH-I535 using xda app-developers app
I meant "dishing" out root... Funny how a typo gives you the opposite sometimes...
Sent from my SCH-I535 using xda app-developers app
This phone can cause some weird bugs from time to time haha and yea, you need TWRP 2.6.3.1 to flash any KitKat rom. SlimKat is pretty smooth, just missing a lot of features while they make sure its stable.