Root tool debugsroot won't work anymore after updating....i forgot to use rootkeeper after a factory reset so no restore option. Any ideas?
Sent from my ASUS Transformer Pad TF700T using xda premium
maverickmarc said:
Root tool debugsroot won't work anymore after updating....i forgot to use rootkeeper after a factory reset so no restore option. Any ideas?
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
me too, i had use rootkeeper, after update lost root, can not root again
I also lost root with rootkeeper. WW version
maverickmarc said:
Root tool debugsroot won't work anymore after updating....i forgot to use rootkeeper after a factory reset so no restore option. Any ideas?
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
I too lost root but with the US .30 version...even using rootkeeper. Was able to run debugfs, however, to re-root.
houtx2 said:
I too lost root but with the US .30 version...even using rootkeeper. Was able to run debugfs, however, to re-root.
Click to expand...
Click to collapse
I lost root in WW .30 version. I couldn't restore with rootkeeper. I reran the debugfs rooting method to get root back.
Like last time though I had to open up command prompt as admin and run the bat file manually instead of just right clicking it and running as admin.
rmkbow said:
I lost root in WW .30 version. I couldn't restore with rootkeeper. I reran the debugfs rooting method to get root back.
Like last time though I had to open up command prompt as admin and run the bat file manually instead of just right clicking it and running as admin.
Click to expand...
Click to collapse
How did you know you lost root? I just did the update, ran Titanium Backup and a few other apps and they all report that root is still functional?
spinaldex said:
How did you know you lost root? I just did the update, ran Titanium Backup and a few other apps and they all report that root is still functional?
Click to expand...
Click to collapse
for one, voodoo told me my device wasn't rooted. I would fail to restore root (supersu popup message kept saying voodoo was allowed access, maybe every 20 seconds or so but keep repeating)
supersu complained that it failed if i even tried to disable SU from the menus
I didn't lose root, with WW version. After update I normally restored root with ota rootkeeper. All went fine.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
zabih107 said:
I didn't lose root, with WW version. After update I normally restored root with ota rootkeeper. All went fine.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
Same here
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
zabih107 said:
I didn't lose root, with WW version. After update I normally restored root with ota rootkeeper. All went fine.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
technically you did lose root, but restored it via ota rootkeeper.
Lost root but restored with Voodoo.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
after ww update restored via voodo ota rootkeeper and all went fine and work as expected...
maverickmarc said:
Root tool debugsroot won't work anymore after updating....i forgot to use rootkeeper after a factory reset so no restore option. Any ideas?
Click to expand...
Click to collapse
I used rootkeeper, though it didn't really helped me, lost root after manual update to ww.30.
I re-run debugfs (ran cmd. exe as admin and then executed the debugfs).
Although debugfs complained that rooting failed, root was actually succeeded, it did however required another reboot to properly kick in.
Lost also Root, but after the unroot action with RootdebugFS it is back again
I was able to root. 30 I went from. 26 to a manual flash of the full . 30 update. I lost root and the root method worked fine for me US sku
Sent from my Nexus 7 using Tapatalk 2
Try the same with SuperSU instead of Superuser app, guys. It's a different management app, but a different "su" as well. Anyway, with SuperSU I was able to preserve root, so it might be the reason (I switched to it as a means of the JB preperations, after some TF300 users have reported it was the only way for them to keep root after the JB firmware update).
I updated and my root held, I didn't have to install any apps or anything.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
i think we could change WW SKU to US SKU maybe can get root back ?!!!!! tried it
I just updated to the US .30 update and not only did i lose root, but my tablet is no longer recognized in ADB. two days ago i was able to use ADB and fastboot to flash the new clockwork recovery just fine. When I try to root with Debugsfs i get a weird error that says 'find' is not a recognized command just after the "waiting for device to be detected". I could use any help that anyone can give.
Might look like a stupid question, but are you sure you had USB debugging enabled in system settings while trying this?
Related
I've already root my device and i'm currently using the prime 1.3 rom. I'm wondering if i want to apply the official 3.1 update do i need to unroot my device? If not what should i do? Thanks helping.....
Follow these instructions and you will be fine. No need to unroot.
http://asustransform.com/2011/05/29...r-honeycomb-3-1-update-leaked-yours-to-enjoy/
Sent from my Transformer TF101 using Tapatalk
ayman07 said:
Follow these instructions and you will be fine. No need to unroot.
http://asustransform.com/2011/05/29...r-honeycomb-3-1-update-leaked-yours-to-enjoy/
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Thanks for that link, I just followed the directions for rooted users, and everything went perfectly!
awesome! glad to hear everything worked out
Sent from my Transformer TF101 using Tapatalk
grumble grumble, I jumped the gun and installed official, thus losing root. I'm wonder can't I just adb push the rooted 3.1 blob?
No, since you don't have root access so you can't push anything to /system/ or any of the folders outside /mnt. You need to downgrade back to stock .9 and re-root or wait for a new way to root.
You can try going into recovery to see if you still got CWM, then you can just flash this with CWM.
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
Topic says it all, has it worked for you guys?
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Does for some, not for others :/
Apparently having SuperSU installed before the upgrade helps when restoring root.
It seems that it's necessary to install SuperSU and run it at least once, then backup your root with VooDoo OTA RootKeeper.
Trimis de pe ASUS Transformer Pad TF300T
Don't do a data wipe, or you will most likely break it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
worked for me
Worked for me and i needed to do dataswipe because 1 app was rebooting my tablet and i didnt know what app it was.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
By data wype you mean.?
Sent from my ASUS Transformer Pad TF300T
Crap we needed to have superSU before?
Sent from my SAMSUNG-SGH-T989 using xda premium
I restored root using OTA rootkeeper with Superuser (not SuperSu) installed. This didnt work for everyone. There is an option in the Superuser settings with a checkbox that says "OTA survival" (or something like that). I had it checked. This seems to be the difference with others who lost root with Superuser.
to be clear.
-I had superuser installed
-i had ota rootkeeper installed
-i checked the 'ota survival' box (in superuser)
-i was able to restore root no problem after JB OTA update.
Worked for me with superuser (not supersu) and I didn't have any "ota survival" checked in superuser. Just used voodoo root keeper.
Also UNINSTALL ezoverclock. It crashes JB on boot over and over.
thesuzukimethod said:
I restored root using OTA rootkeeper with Superuser (not SuperSu) installed. This didnt work for everyone. There is an option in the Superuser settings with a checkbox that says "OTA survival" (or something like that). I had it checked. This seems to be the difference with others who lost root with Superuser.
to be clear.
-I had superuser installed
-i had ota rootkeeper installed
-i checked the 'ota survival' box (in superuser)
-i was able to restore root no problem after JB OTA update.
Click to expand...
Click to collapse
mine worked, but i didnt change any settings in superuser , so can't be purely that that's stopping it working for some
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I got a samsung s3 I747 and that sucks. I would need to unroot my device before accepting OTA update in this case? Thanks in advance and sorry if I'm not doing something the right way
I am rooted and locked. My 4.2 update resulted in a dead Android with a red triangle and exclamation point. I was able to cold boot back into 4.1 but the 4.2 update will not download again. What's my next step?
Thanks,
BTrack said:
I am rooted and locked. My 4.2 update resulted in a dead Android with a red triangle and exclamation point. I was able to cold boot back into 4.1 but the 4.2 update will not download again. What's my next step?
Thanks,
Click to expand...
Click to collapse
make a full backup with Titanium then use manual update with dlpkgfile method. Make sure you use the right SKU (ww or us).
Thanks, but I'm not versed on the method you suggest. Could you elaborate please?
Sent from my ASUS Transformer Pad TF700T using xda premium
BTrack said:
Thanks, but I'm not versed on the method you suggest. Could you elaborate please?
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
This method is complicated, I don't think you should try, just wait until tomorrow, sdbags will release the new cromi version of 4.2 and the update twrp patch and you just flash them. Done,safe, quick and easy.
buhohitr said:
This method is complicated, I don't think you should try, just wait until tomorrow, sdbags will release the new cromi version of 4.2 and the update twrp patch and you just flash them. Done,safe, quick and easy.
Click to expand...
Click to collapse
On a locked tablet?
_that said:
On a locked tablet?
Click to expand...
Click to collapse
You have a point there, I thought I'm talking to another guy!
Btrack, I was confused you with another guy...sorry! Yours is rooted but still LOCKED.
You can find the info here for manual update http://forum.xda-developers.com/showthread.php?t=1803090
Basically, you need to create a file called "command" (no file extension and no quote) with this information inside the file:
--update_package=/cache/dlpkgfile
Then copy this file to this location /cache/recovery
Then download the correct SKU version (US, WW etc..) and copy it to this location /cache/
Boot into stock recovery and wait 10 sec, it should auto update for you.
Thank you.
Sent from my ASUS Transformer Pad TF700T using xda premium
And before doing all that, make sure all files touched by the update are present and in their original condition, or it will fail again.
annnnnnd make sure you read up on how to keep root with the 4.2 update. Not familiar with the method buhohitr posted, but i know some people are losing root with this update
buhohitr said:
make a full backup with Titanium then use manual update with dlpkgfile method. Make sure you use the right SKU (ww or us).
Click to expand...
Click to collapse
I have not been abble to find the dlpkgfile posted anywhere, does anyone know where it is? Thanks
zachspda said:
I have not been abble to find the dlpkgfile posted anywhere, does anyone know where it is? Thanks
Click to expand...
Click to collapse
Which one you need? US or WW?
BTrack said:
I am rooted and locked. My 4.2 update resulted in a dead Android with a red triangle and exclamation point. I was able to cold boot back into 4.1 but the 4.2 update will not download again. What's my next step?
Thanks,
Click to expand...
Click to collapse
Using my PC I downloaded the 4.2.1 US update to my micro SD card. Did a Titanium backup, and defrosted all the bloatware, and backed up root using Voodoo. Did a factory reset and inserted the SD card. Update failed again.
BTrack said:
Using my PC I downloaded the 4.2.1 US update to my micro SD card. Did a Titanium backup, and defrosted all the bloatware, and backed up root using Voodoo. Did a factory reset and inserted the SD card. Update failed again.
Click to expand...
Click to collapse
Make sure you changed the name correctly, caps and all, and unzipped it once.
Tylor
Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: Stock 4.2.1 Rooted.
UPDATE FOR TF700 USERS!!! AND THE 4.2.1 UPDATE http://forum.xda-developers.com/showthread.php?t=2204100
Hello all,
I just got a TF300T and set it up, and with hindsight rather stupidly, OTA'd it to 10.6.1.27.5 (4.2.1)
I have spent quite a while on this forum deciding what ROM's to get etc
and i was going to follow the guides and realised that they are for 10.6.1.27.1 latest and that motochopper doesn't work for that firmware
Just generally, what can I do?
I don't really want to install loads of stuff and get settled in to my tf300t if im just going to wipe it when i root and flash
Will i need to unlock the bootloader?
Are there any other questions i should be asking instead?
Cheers, any help would be appreciated
--jr--
--jr-- said:
Hello all,
I just got a TF300T and set it up, and with hindsight rather stupidly, OTA'd it to 10.6.1.27.5 (4.2.1)
I have spent quite a while on this forum deciding what ROM's to get etc
and i was going to follow the guides and realised that they are for 10.6.1.27.1 latest and that motochopper doesn't work for that firmware
Just generally, what can I do?
I don't really want to install loads of stuff and get settled in to my tf300t if im just going to wipe it when i root and flash
Will i need to unlock the bootloader?
Are there any other questions i should be asking instead?
Cheers, any help would be appreciated
--jr--
Click to expand...
Click to collapse
I've read the motochopper root method doesn't work on 27 versions. So either downgrade to 15 and use motochopper or unlock the bootloader. Unlocking makes things much easier to achieve and maintain, and you can run the latest version with root easily.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
funnel71 said:
I've read the motochopper root method doesn't work on 27 versions. So either downgrade to 15 and use motochopper or unlock the bootloader. Unlocking makes things much easier to achieve and maintain, and you can run the latest version with root easily.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
If I unlock am I able to lock again? I am asking as I would prefer not to void my warranty. Also is downgrading from .27 known to work at all?
Thanks for replying!
--jr-- said:
If I unlock am I able to lock again? I am asking as I would prefer not to void my warranty. Also is downgrading from .27 known to work at all?
Thanks for replying!
Click to expand...
Click to collapse
- no you can't relock
- yes it is possible to downgrade, however unlike upgrade, downgrading deletes all of your data (so back up first and then downgrade)
I have the latest update on my tf300t and I have it unlocked. However, no method I've tried will allow me to install a custom recovery or get root access. I'm at a loss as what to do. I've tried the motochopper method and I've tried several that have me download files to my sd and try to flash them through recovery. All I get there is a little dead android with an exclamation point. Asus Sync won't even work, so any method that uses that is useless to me...
nooktablet said:
- no you can't relock
- yes it is possible to downgrade, however unlike upgrade, downgrading deletes all of your data (so back up first and then downgrade)
Click to expand...
Click to collapse
As previously stated....... you need to downgrade your system. The latest OTA will not allow you to use motochopper. Boot into fastboot, install universal drivers, download ( and verify md5 ) an older 4.2 build, fastboot -i 0x0B05 flash system ( the blob file unpacked ) THEN use motochopper.
Sent from my SGH-T889 using xda app-developers app
pyraxiate said:
As previously stated....... you need to downgrade your system. The latest OTA will not allow you to use motochopper. Boot into fastboot, install universal drivers, download ( and verify md5 ) an older 4.2 build, fastboot -i 0x0B05 flash system ( the blob file unpacked ) THEN use motochopper.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
I think the new root method mentioned in the motochopper thread will root this version. Others are claiming success. I can't confirm because I'm unlocked and don't need it.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
---------- Post added at 01:04 PM ---------- Previous post was at 01:01 PM ----------
Here's the newer method.
http://forum.xda-developers.com/showthread.php?p=46412336
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
I've tried downgrading. But whenever I enter the command prompt it says device not found. The tablet shows up in my drives list and I can view and transfer files. I've updated SDK, checked the drivers and even tried just installing a downgrade through RDK. I even tried using a terminal emulator as well, to no avail.
Sent from my SCH-I545 using xda app-developers app
funnel71 said:
I think the new root method mentioned in the motochopper thread will root this version. Others are claiming success. I can't confirm because I'm unlocked and don't need it.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
---------- Post added at 01:04 PM ---------- Previous post was at 01:01 PM ----------
Here's the newer method.
http://forum.xda-developers.com/showthread.php?p=46412336
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Are you trying while the factory rom is up and running? If so, You need to be in fastboot mode ( power on holding vol down ). Then try fastboot. You should have asus fastboot come up as a device inside of your device manager.
Sent from my SGH-T889 using xda app-developers app