Update 9/14/2013
A better solution has been released, please update using it.
http://forum.xda-developers.com/showthread.php?p=45598648
Warning: Don't attempt to use this on a device that isn't Motorola.
Lets break this sub forum open with a good one.
See: http://www.androidpolice.com/2013/09/12/exclusive-how-to-root-moto-x-ultra-mini-and-maxx/ for the story
Bounty payouts or donations can be paypaled to [email protected], or use the donate button to the left. If its for the bounty, please reply below with confirmation number or pm me.
These files are not to be mirrored elsewhere, no included in other packages. Its simple already, no need to repackage it.
Same APK should work for Maxx, Ultra and Mini. If it does not, I just need to rebuild it and need someone to test, it will work.
adb install -r <filename>
Run MotoRoot app
Press Setup
Install Supersu app
Phone will reboot, and you will be rooted as soon as device is fully booted.
Limitations:
Uninstalling the app will disable root until reinstalled
supersu is not able to update su yet, this will be fixed in an update shortly.
su is maintained in a ext4 img at /data/xbin.img and mounted over /system/xbin at BOOT_COMPLETE.
su is not available for the first few seconds of boot, im working on this.
/system is write protected, even with unlocked bootloaders you can not write to it while booted in Android.
Unroot:
Two choices, factory reset, or press the unroot menu option in the app.
Problems:
Run into a problem? try hittung unroot then re-rooting
Credits:
We use two vulns in this app, first being 9695860 to gain system user, then a symlink attack of mine to get root from system.
xIndirect (nick) for assisting me from start to finish
Whoever originally found bug 9695860
Saurik for his description of 9695860
Ryan Welton for his 9695860 tool
Dave Kover for yet another kick butt icon
and Anthony Fox/Droid-Hive for great help with getting the device to me today
Very much appreciated.
PayPal transaction ID 4GK69936510343543.
Ignore everything I said, I will send my donation thank you
jcase said:
/system is write protected, even with unlocked bootloaders you can not write to it while booted in Android.
Click to expand...
Click to collapse
firist off thank you for all your hard work
i do have a question dose this mean we can not install apps on the system/app folder?
jcase said:
su is not available for the first few seconds of boot, im working on this.
Click to expand...
Click to collapse
and dose this mean files cant be pushed with adb as a work around?
Confirmation number: 3FS7579230091290J
Thanks!!
Confirmation 17R58863KC726802C , I didn't pledge on the bounty thread.
Yes!
Worked like a charm!
Been waiting for this since day one. You are a god sir.
TheWhiteChallenger said:
firist off thank you for all your hard work
i do have a question dose this mean we can not install apps on the system/app folder?
and dose this mean files cant be pushed with adb as a work around?
Click to expand...
Click to collapse
No messing with system/app yet, just system/xbin. Will be addressing the rest of it soon, I just got my phone today. Been talking with HashCode and DBHacker about getting custom roms going, it is being looked at now.
adb works fine, su just doesnt get remounted until the BOOT_COMPLETE broadcast is sent, it means poorly written apps that does retry a root command with a delay, MIGHT fail to get root at boot. They should retry. I will be addressing this, soon.
Like I said, just got the phone about 7 hours ago.
Thanks man!
Sent from my XT1080 using XDA Premium 4 mobile app
got adfree working, but you have to do it QUICKLY. remount /system as rw, then immediately press the update button on the adfree app. the changes will remain until reboot, but I hardly ever reboot
busybox mount -o remount,rw /system;
Thanks...didn't expect to have root so soon. Confirmation 7PD1555899342392B - pledged over on the Droid Ultra bounty page
Droid Mini Confirmed! Thank you!
Sent from my XT1030 using xda app-developers app
jcase said:
No messing with system/app yet, just system/xbin. Will be addressing the rest of it soon, I just got my phone today. Been talking with HashCode and DBHacker about getting custom roms going, it is being looked at now.
adb works fine, su just doesnt get remounted until the BOOT_COMPLETE broadcast is sent, it means poorly written apps that does retry a root command with a delay, MIGHT fail to get root at boot. They should retry. I will be addressing this, soon.
Like I said, just got the phone about 7 hours ago.
Click to expand...
Click to collapse
ok kool, i dont mean to sound ungrateful thats just mainly what i use root for is fiddling with stuff of the system folder, so i was just wondering if i was permanently screwed of if was something that is atleast being working on, thanks again ill be sending my donation as soon as i remember my paypal pw, lol
Should USB Debugging be enabled?
is the "Transaction ID" the confirmation number?
Thanks! 8JG23957NE2435454
Posted from http://forum.xda-developers.com/showthread.php?t=2431005
Confirmation number: 4JK07192689429602
Thanks!
So this has to be installed by adb? What if in my haste and excitement, I "accidentally" installed it without ADB? I noticed I can't uninstall it. However, when I do Root Checker, it shows I'm rooted but I can't install SU it says "Installation Failed!"
Every time I start SuperSU the message "The SU binaries needs to be updated. Continue?" comes up, but when "Normal" button is pressed on the next screen (since we dont have custom recoveries) the update fails.
Should we not update SU?
CrazyRussianXDA said:
Every time I start SuperSU the message "The SU binaries needs to be updated. Continue?" comes up, but when "Normal" button is pressed on the next screen (since we dont have custom recoveries) the update fails.
Should we not update SU?
Click to expand...
Click to collapse
I'm getting the exact same thing, if you push cancel it just closes the app.
CrazyRussianXDA said:
Every time I start SuperSU the message "The SU binaries needs to be updated. Continue?" comes up, but when "Normal" button is pressed on the next screen (since we dont have custom recoveries) the update fails.
Should we not update SU?
Click to expand...
Click to collapse
Just don't open SuperSU once it's installed. Reboot one more time and you'll get regular prompts from SuperSU to allow permissions as apps request root.
Related
Indirect is proud to present you with ADB Hijacker
Note: This modification will remove any custom clrbootcount.sh scripts
Alright, what this application does, is hijacks adb using a root version instead which means from now on, you can do "adb remount" and things like that. This comes with all the needed files within the app and it also extracts them so no worries!
After you run the app once and click that magical button then you can reboot and you will have adb autostart as root so you can even uninstall the app afterwards. As of now, we do not have automount killed. However: I learned that adb stays on even while in usb mode.
Download Link:
Here
Screenshots: Uploading
Benefits and change log:
Benefits:
Code:
You can now rerun the rooting script to apply whatever modifications you missed out on
You can now apply any mod using adb instead of file explorer
You can remount your system by just using "adb remount" instead of using a file explorer
Changelog:
Code:
2.0: Included needed files for extract / included busybox installer
1.0: Initial Release
Credits:
Code:
brianf21 for showing me how to extract files from an apk so now you can install directly from the app and nothing else is needed except root.
Nemith for the adb daemon
Myself for the app, hijack method, and testing
puellanivis from IRC for being terrible at communication and also help with a few of the commands
This one is mine as well.
damn you, I am taking this one for video! click comment for video
Firstly,
Thanks Indirect, you make my Nook a joy to use. Many thanks also to Albertwertz - your Youtube videos are helping a noob like me get up to speed with this Android experience.
Can't post this in the Developer thread (still under 10 posts) but there seems to be a problem running the nookandzergy.bat file whilst running the ADB Hijacker. I'm getting a dos error:
"Your device was found to be rooted. Which is bothersome. However: I will see if you happen to have the proper modification installed to continue to use this script:"
followed by
"goto was not expected at this time".
Having a quick look at the bat file I can't see where %adbr% is being set to "yes".
Update: After making sure adb hijack was running, I tweaked the batch file, forcing adbr=yes. The script then worked and allowed me to replace the SystemUI.apk to remove the B&N Home button. Not sure how Indirect intends to set the variable properly, but by adding:
set adbr=yes
above the line:
if %adbr%==yes goto N1
Allowed by to re-run the rest of the root process
Another thing I did notice when testing the script was that by selecting "N" to the "Do you want to replace the systemUI to have a perm back / menu button on status bar and have the N button goto home on first click?" question the script errors with a -N7 not found.
I am having the same problem. I followed the video that albert posted and even opened up the cmd line to double check my adb remout. Everything worked fine till i get:
"Your device was found to be rooted. Which is bothersome. However: I will see if you happen to have the proper modification installed to continue to use this script:"
followed by
"goto was not expected at this time".
I don't know if Nook&Zergy is setup to support the adbd hijack yet. But that is the most likely answer. Or in particular, you might not have the newest N&Z as well.
I also wanted to momentarily divert the thread, and mention that snowball-mod already includes this adb-hijack, so it is unnecessary to run it on snowball-mod. (However, Indirect worked with me to ensure that it wouldn't hose anything if you did.)
Before I ran nz, i downloaded the latest from Indirect's original root thread. If the updated one isn't using that link, then where do I find it?
Indirect and I were up kinda late last night working on this and he made several modification on my nook zergy extraction that he may have forgotten to make when he remade his and uploaded it for everyone. Here is a link to the mod he made of the latest nook zerg on my pc. This may have something that the new one doesnt that he forgot to do. I am sure he will fix the code soon, but until then, download and try this: http://dl.dropbox.com/u/24100179/Nookie/NookandZergy.bat
this is the nook zergy bat file he modified. copy it and replace the bat file in your new nook zergy extraction and see if it runs right with this app
This is only temporary, dont use this after he fixes it
That did the trick! Thanks Albert!
I just got my nook & I don't understand the programming that you are talking about. But if you both were up late working on the root script (assuming). Just an FYI once I finished w/ the driver loads & started loading the root script, my device wouldn't show up, did a factory reset 3 times, as well as removing any usb traces etc... finally got it to take & all the red stopped & never loaded in the gapps, launchers etc... I reloaded it again & it says that I am rooted, but having a heck of a time w/ Titanium doesn't want to accept any of the
devicemanager .apk stuff. Sorry for no tech terms, Indirect & Albert Thank you so much for making this easy. Loved the video, really helped a ton. Just wanted to say thanks & let you know of the glitch.
I got it loaded now it is not recognizing the sd card 4 Titanium. I have done several of your factory reset, as well as the b&n reset still nada even put in 4 different cards. Happy New Year & Thanks for any help
TRI
did this today, easy, took 5 minutes. Grateful for all this
I'm a little bit confused, my nook updated to 1.41, i've tried downloading adb hijacker to my nook, but it won't open, what am I doing wrong?
Edit: What exactly do I need to do to block the updates and allow my nook to use the android market again?
I'm a pathetic no0b, and I tried downloading the ADB hijacker to my nook, but it won't open. What do I need to do to fix this?
Thank you.
ETA the Nook updated the other day.
Indirect said:
Indirect is proud to present you with ADB Hijacker
Note: This modification will remove any custom clrbootcount.sh scripts
Alright, what this application does, is hijacks adb using a root version instead which means from now on, you can do "adb remount" and things like that. This comes with all the needed files within the app and it also extracts them so no worries!
After you run the app once and click that magical button then you can reboot and you will have adb autostart as root so you can even uninstall the app afterwards. As of now, we do not have automount killed. However: I learned that adb stays on even while in usb mode.
Download Link:
Here
Screenshots: Uploading
Click to expand...
Click to collapse
absolutely awesome!
Guys, this doesn't stop updates or is usable on the 1.4.1 update..it's a 1.4.0 modification that hijacks the adb daemon on the device.
Ok, but what do we do if we didn't get to it in time and the stupid thing updated to 1.4.1? Do we have to return the thing to factory settings and lose all our content?
I'm sorry for asking dumb no0b questions, but if there is a guide for what to do in this situation, I can't seem to find it here.
Thanks for all you do, all the experts here!
ETA I found what I was looking for, in the "Nook general" forum. sorry to waste space on this thread.
My mistake, I thought I would be able to apply the update that stops the ota's through this. Which thread has the method to allow me access to market again? (effectivly null n' voiding the 1.41)
nearlyno0b said:
Ok, but what do we do if we didn't get to it in time and the stupid thing updated to 1.4.1? Do we have to return the thing to factory settings and lose all our content?
I'm sorry for asking dumb no0b questions, but if there is a guide for what to do in this situation, I can't seem to find it here.
Thanks for all you do, all the experts here!
ETA I found what I was looking for, in the "Nook general" forum. sorry to waste space on this thread.
Click to expand...
Click to collapse
^^^^^ Quoted for the sake of others ^^^^^
arkraven000 said:
My mistake, I thought I would be able to apply the update that stops the ota's through this. Which thread has the method to allow me access to market again? (effectivly null n' voiding the 1.41)
Click to expand...
Click to collapse
Below is a link to the information as to how to remove B&N 1.4.1 update and restore 1.4.0:
[Stock Firmware]Restore Barnes & Nobel Nook 1.4.0 from SDCard
ENJOY!
https://sites.google.com/site/mophocorner/
Site to help with everything Motorola Photon 4G.
Hoping to help with newbies that want to flash, root, unlock, etc. before they get stuck and have to wait for replies to fix there phone, Hopefully this guide will just work and they wont HAVE to post for help. That is the point of this at least! Let me know if there is anything I can add or change and I will gladly give it some thought!
Thanks!
I have updated the page, just so everyone knows!! Check it out!!! Let me know if I am missing anything.
Sent from my Xoom using XDA
The photon torpedo method is needed to root the 2.3.5 version just released.
Sent from my MB855 using Tapatalk 2
THANKS!
Thank you for that. Added the Torpedo root method! =]
Thanks for putting all that info into one spot! Definitely helps out that much more as it is somewhat easier to refer to rather than bouncing from one post to another here in the forums! I would imagine it'll help out many people (including me!).
I'm still fairly new to some things and some times the added explanation of certain topics and/or issues is what's needed to get the job done!
Also, as far as the *photon-torpedo* root method goes... I used that method without an issue on Android 2.3.4. After updating to Android 2.3.5 the other day, I used that same method again without issue and it worked perfectly! Unfortunately (at least from what I've read), being that I updated to 2.3.5, I won't be able to unlock the bootloader as if right now. Not really something I'm too concerned about, being that I hadn't prior to the update anyway.
Sent from my MB855 using Tapatalk 2
I hate to be that guy but this is certainly relevant to the discussion at hand. I used the Photon Torpedo method originally when it first came out. Since then I have kept it stock and performed the OTA updates as they come. After each update I just run the last two commands:
/data/tmp/photon-torpedo.sh
/data/tmp/install-su.sh
Always worked in the past. I just got updated to the new "2.3.5" and I can't seem to get root back. The photon-torpedo script has multiple errors "libpcprofile.so cannot be loaded as audit interface" and "permission denied". Consequently the install-su script doesn't succeed. Can't mount /system as RW and everything is permission denied.
Worst part is that the SU binary still exists in /system/bin/su but I can't use it. I get permission denied on everything I try.
Am I borked? Is there something I have forgotten?
Jleeblanch, are you using the new update from Motorola from the soak test?
Grep,
To answer your question, yes. The new update unroots your device so you will have to re-root using the photon-torpedo method again.
I was rooted prior to the update with that method and after the update I was un-rooted! Trying to re-root using Terminal Emulator on device wouldn't work. Got "permissions denied" when running the tar command. But, using adb on the computer worked without a problem!
So basically, just redo the torpedo root method from step 1 and you'll successfully get root back guaranteed!!
Hope that helps!
Also, I had the SU binary in place as you did along with other root specific apps. Those apps are pretty much worthless until you gain root again.
It has been confirmed in the "soak" that 2.3.5 update will completely un-root your device...
Sent from my MB855 using Tapatalk 2
nice. should come in handy for others. even me cuz im kind of a noob.... waiting for way around locked bootloader after 2.3.5 ota
Sent from my Motorola Electrify using XDA
Grep_The_Truth said:
I hate to be that guy but this is certainly relevant to the discussion at hand. I used the Photon Torpedo method originally when it first came out. Since then I have kept it stock and performed the OTA updates as they come. After each update I just run the last two commands:
/data/tmp/photon-torpedo.sh
/data/tmp/install-su.sh
Always worked in the past. I just got updated to the new "2.3.5" and I can't seem to get root back. The photon-torpedo script has multiple errors "libpcprofile.so cannot be loaded as audit interface" and "permission denied". Consequently the install-su script doesn't succeed. Can't mount /system as RW and everything is permission denied.
Worst part is that the SU binary still exists in /system/bin/su but I can't use it. I get permission denied on everything I try.
Am I borked? Is there something I have forgotten?
Jleeblanch, are you using the new update from Motorola from the soak test?
Click to expand...
Click to collapse
Sent from my MB855 using Tapatalk 2
Root
You could always use root-keeper from the market if your lazy like me.
the link to the download torpedo is not working
spursrob said:
the link to the download torpedo is not working
Click to expand...
Click to collapse
The Imperium has your back. I will be upping a new guide and Root-Unlock-Relock pack soon but hosting is changing servers so for now torpedo is attached to this post.
Lokifish Marz said:
The Imperium has your back. I will be upping a new guide and Root-Unlock-Relock pack soon but hosting is changing servers so for now torpedo is attached to this post.
Click to expand...
Click to collapse
Clearly, I am retarded....I have studied this post 15 times but I can't find any way to see an attachment. Where is it?
cool old lady said:
Clearly, I am retarded....I have studied this post 15 times but I can't find any way to see an attachment. Where is it?
Click to expand...
Click to collapse
try it now, post 6. Are you on 2.3.4 or 2.3.5? If you're on 2.3.4 then just use the root/unlock/relock pack (the link is at the top of post 6.
OK - I see it now and I've downloaded it - thank you very much. I am on 2.3.5 from the soak test.
Are these still the correct/only instructions? If so I may still be in trouble...my "favorite method....into /data/tmp"? I don't know any method, much less have a favorite.
Instructions:
Use your favorite method to get photon-torpedo.tar into /data/tmp
Install Superuser from the Market
Install Android Terminal Emulator from the Market
Run Android Terminal Emulator
Run cd /data/tmp
Run /bin/tar xf /data/tmp/photon-torpedo.tar
Run /data/tmp/photon-torpedo.sh
Run /data/tmp/install-su.sh
I'm actually on my way to bed. I will write a more detailed walkthrough tomorrow and post it in the Photon Compendium. Eventually I plan to script the entire process but am working on unified webtop stuff right now.
Grep_The_Truth said:
I hate to be that guy but this is certainly relevant to the discussion at hand. I used the Photon Torpedo method originally when it first came out. Since then I have kept it stock and performed the OTA updates as they come. After each update I just run the last two commands:
/data/tmp/photon-torpedo.sh
/data/tmp/install-su.sh
Always worked in the past. I just got updated to the new "2.3.5" and I can't seem to get root back. The photon-torpedo script has multiple errors "libpcprofile.so cannot be loaded as audit interface" and "permission denied". Consequently the install-su script doesn't succeed. Can't mount /system as RW and everything is permission denied.
Worst part is that the SU binary still exists in /system/bin/su but I can't use it. I get permission denied on everything I try.
Am I borked? Is there something I have forgotten?
Jleeblanch, are you using the new update from Motorola from the soak test?
Click to expand...
Click to collapse
Me to, had to used one click Root (20 times)
Navigate to the Android Market and install the “Superuser” application from ChainsDD
Download and extract 22MB Root-Unlock-Relock.zip from the Imperium website
Go to the "rsd drivers" folder located in the Root-Unlock-Relock folder and install the drivers for your system (32bit or 64bit windows)
Download photon-torpedo.tar
Place photon-torpedo.tar in the "AIO Root" folder located in the Root-Unlock-Relock folder
On your phone, in menu/settings/applications/development make sure usb debugging is checked
Connect your phone to your computer and select "charging" mode from the connections options in notifcations
From the "AIO Root" folder, double click the "Command Prompt" shortcut
Type the following commands:
adb push photon-torpedo.tar /data/tmp
adb shell
cd /data/tmp
/bin/tar xf /data/tmp/photon-torpedo.tar
/data/tmp/photon-torpedo.sh
/data/tmp/install-su.sh
Ignore the errors when running torpedo and let the process complete.
Once I get some free time I'll write a single script covering everything from rooting to SBFing back to stock. My goal is to get any given process down to ten keystrokes or less.
Hmph. Well....I think it worked. Root Checker says "congrats" - but wasn't it supposed to wipe all my stuff from the phone or something?
no root doesn't wipe data. (neither does unlock if done right)
Sent from my mopho
hey guys i need some help plz!!!
i had rooted my asus prime.......and my bootloader was still locked, after i rooted my device i also had rootkeeper to protect it incase i update.....to make a long story short, i was so anxious when jelly bean was released i wasnt thinking so i proceeded without temp unroot first before i did the update......so after everything completed i went to restore my root access and it was gone..........was so pissed off, so now from every research i did it says that there is no current root options for the prime jelly bean, anybody knows how to get it back or a way to root again.....im willing to downgrade if i can to get back my root access. please help!!!
You can't downgrade without using the ASUS unlocker tool. Yeah, I know... shocked me too....
There isnt a working root method working as of yet if you are certain you have lost root access.
Some people report having partial root and even having some apps that still retained root. If none of that applies to you then your screwed with the rest of us.
hx4700 Killer said:
You can't downgrade without using the ASUS unlocker tool. Yeah, I know... shocked me too....
There isnt a working root method working as of yet if you are certain you have lost root access.
Some people report having partial root and even having some apps that still retained root. If none of that applies to you then your screwed with the rest of us.
Click to expand...
Click to collapse
yea thanks for replying tho, as far as the partial root goes.....im not sure if im that lucky and i checked system/bin there is no su file and also when i enter adb shell command then su i got the $ sign instead of the #.........but i still have superuser app !
weakenfalls said:
yea thanks for replying tho, as far as the partial root goes.....im not sure if im that lucky and i checked system/bin there is no su file and also when i enter adb shell command then su i got the $ sign instead of the #.........but i still have superuser app !
Click to expand...
Click to collapse
If you don't get # you don't have root.
I actually had an SU in xbin but it wasnt owned by root.
hx4700 Killer said:
If you don't get # you don't have root.
I actually had an SU in xbin but it wasnt owned by root.
Click to expand...
Click to collapse
I get # in ADB but not using Terminal Emulator. What does this mean?
Restorer said:
I get # in ADB but not using Terminal Emulator. What does this mean?
Click to expand...
Click to collapse
Hmmm I will have to try in ADB and see what happens.
If your prompt changes to # in ADB then that means you should have root access. With that you can restore full root properly to your device. You may be one of the lucky ones that just needs to uninstall and reinstall Superuser.
hx4700 Killer said:
If your prompt changes to # in ADB then that means you should have root access. With that you can restore full root properly to your device. You may be one of the lucky ones that just needs to uninstall and reinstall Superuser.
Click to expand...
Click to collapse
Well it did give me hope when I saw that but I can't get past stage 11 in this guide . I just cannot get ADB to mount /system as RW . Also entering su in Terminal Emulator gets "permission denied" and Superuser itself "fails" at updating binary.
Restorer said:
Well it did give me hope when I saw that but I can't get past stage 11 in this guide . I just cannot get ADB to mount /system as RW . Also entering su in Terminal Emulator gets "permission denied" and Superuser itself "fails" at updating binary.
Click to expand...
Click to collapse
What is the error when you issue the remount command? if I type remount I get: "remount: not found"
There is also an executeable that came with one of the 10000 root packages I have tried called fsrw. Pushing it to /data/local/tmp with ADB then running it via the adb shell out of that path should try to perform the remount.
If you are getting "operation denied" then you don't really have root =/
hx4700 Killer said:
What is the error when you issue the remount command? if I type remount I get: "remount: not found"
There is also an executeable that came with one of the 10000 root packages I have tried called fsrw. Pushing it to /data/local/tmp with ADB then running it via the adb shell out of that path should try to perform the remount.
If you are getting "operation denied" then you don't really have root =/
Click to expand...
Click to collapse
I get:
"mount: Operation not permitted" .
There you go, you are not really root
Curious that you get the # logo though. I had an SU in xbin but got no # prompt because its ownership was screwed up.
hx4700 Killer said:
There you go, you are not really root
Curious that you get the # logo though. I had an SU in xbin but got no # prompt because its ownership was screwed up.
Click to expand...
Click to collapse
Sorry, just tried again and now stage 11 is working! But then when I try 12 I get:
"r.apk of=/system/app/Superuser.apk
/data/local/tmp/Superuser.apk:cannot open for read: No such file or directory
1:[email protected]:/#"
re root jellybean
hi, to all those other rookies, i did a bit of reading and finally decided to update to JB from stock ICS .28 which was unlocked and rooted.
As i expected i lost root and have just manged to get it back, i first installed twrp for JB using fastboot method.
http://forum.xda-developers.com/showthread.php?t=1615990
then after trying [ROOT][TOOL]Debugfs automated root [09/18/2012] and SparkyRoot Apk having read this can possible restore root although not in my case, for me i uninstalled super user and re-flashed via twrp,
(version Superuser-3.2-arm-signed.zip from thread http://forum.xda-developers.com/showthread.php?t=1911024)
Then when i rebooted i noticed luckypatcher app requested SU and root access was now working
hx4700 Killer said:
There you go, you are not really root
Curious that you get the # logo though. I had an SU in xbin but got no # prompt because its ownership was screwed up.
Click to expand...
Click to collapse
Whooo! Just got my root back. I hadn't realised there are a couple of typos in the guide there and I was copying and pasting the long lines!
Big thanks to hx4700 Killer for making me wonder I must be doing something wrong :laugh:.
tomtomxp said:
hi, to all those other rookies, i did a bit of reading and finally decided to update to JB from stock ICS .28 which was unlocked and rooted.
As i expected i lost root and have just manged to get it back, i first installed twrp for JB using fastboot method.
http://forum.xda-developers.com/showthread.php?t=1615990
then after trying [ROOT][TOOL]Debugfs automated root [09/18/2012] and SparkyRoot Apk having read this can possible restore root although not in my case, for me i uninstalled super user and re-flashed via twrp,
(version Superuser-3.2-arm-signed.zip from thread http://forum.xda-developers.com/showthread.php?t=1911024)
Then when i rebooted i noticed luckypatcher app requested SU and root access was now working
Click to expand...
Click to collapse
Well.. I believe that everyone who'd not consider unlocking their tablets before the JB update would not unlock after losing root just because of the warranty, probably not because they don't know how but because about half of the forumers don't think it's worth the risk considering the hardware instabilities like the green camera module, light bleed etc.
And since you've already flashed a custom recovery you've unlocked more than just root, why not try a custom ROM based on stock JB?
So I bricked my Kinde Fire HDX by changing the build.prop and not fixing permissions. I have adb access but no root (I don't know why :S). Would a factory reset work? If not, how can I get to fix the build.prop or replace it with the old one? thank very much, I've been a couple hours looking for solution but I couldn't find any.
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
r3pwn said:
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
I used the HDX ToolKit v0.92 to check the root access, and it said "Please grant root on your device"
I've also tried "adb shell", and then "su", but it just returns "su" again. I am new with adb commands so I don't really know what it should show.
Thank you very much for your help
May I ask what version you were on before you bricked?
Sent from my Amazon Tate using Tapatalk
14.3.2.3.2, last update I think.
?
peter_b93 said:
14.3.2.3.2, last update I think.
Click to expand...
Click to collapse
Fixed?
jimyv said:
Fixed?
Click to expand...
Click to collapse
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
well
peter_b93 said:
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
Click to expand...
Click to collapse
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
jimyv said:
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
Click to expand...
Click to collapse
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
well
peter_b93 said:
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
Click to expand...
Click to collapse
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
jimyv said:
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
Click to expand...
Click to collapse
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
peter_b93 said:
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
Click to expand...
Click to collapse
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
jimyv said:
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
Click to expand...
Click to collapse
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
sweet
GSLEON3 said:
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
Click to expand...
Click to collapse
I'm not sure either that's why when I used it I was on a blacklisted unit and I kept the PC and the tablet and airplane mode at all times. Until I was certain I got all the files off of both before I let them go to Wi-Fi Chinese files that is.. But one thing I was very curious about is if you open that tool up the Chinese tool that is an you go to the same page you would hit the anchor to root to your device just below that it says fastboot I'm wondering if they have a fastboot working for also too bad nobody here know Chinese..
How should I go about factory resetting my rooted, HD 7" that's running a different launcher? So that it can go back to as clean as possible and be updatable and used normally without bricking/dying. I heard it's dangerous to just use the native factory reset as it can end up with bricks.
Its running on some older firmware that was rootable not long after it became possible and is running Vire Launcher instead of the typical amazon launcher. I'd like to go back to Stock somehow.
Sorry for the double post but seriously no-one knows how to go back to fully default?
Shadowshinra said:
Sorry for the double post but seriously no-one knows how to go back to fully default?
Click to expand...
Click to collapse
For stock with no root:
Run these commands to unblock OTA:
Code:
adb shell pm unblock com.amazon.dcp and
adb shell pm unblock com.amazon.otaverifier
Also, look for /system/priv-app/deviceSoftwareOTA.apk and make sure the extension is (plain) "apk"
Put OS 5.1.2 onto /sdcard (not inside a folder) and press Update now in Device settings.
For latest stock with root, follow this root guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 without installing Gapps/xposed/makespace. If you're running OS 4.5.3 now you can use 5.2.0_stock_recovery_uboot.zip at step 10.
DoLooper said:
For stock with no root:
Run these commands to unblock OTA:
Code:
adb shell pm unblock com.amazon.dcp and
adb shell pm unblock com.amazon.otaverifier
Also, look for /system/priv-app/deviceSoftwareOTA.apk and make sure the extension is (plain) "apk"
Put OS 5.1.2 onto /sdcard (not inside a folder) and press Update now in Device settings.
For latest stock with root, follow this root guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 without installing Gapps/xposed/makespace. If you're running OS 4.5.3 now you can use 5.2.0_stock_recovery_uboot.zip at step 10.
Click to expand...
Click to collapse
Seems simple enough, the adb commands seemingly worked but I can't seem to rename the APK_ back into APK using ES file explorer, it just says renaming progress and the bar doesn't fill up.. so I haven't done the last step yet.
Shadowshinra said:
Seems simple enough, the adb commands seemingly worked but I can't seem to rename the APK_ back into APK using ES file explorer, it just says renaming progress and the bar doesn't fill up.. so I haven't done the last step yet.
Click to expand...
Click to collapse
Try rebooting and see if it got renamed. Are you sure you're rooted and have root explorer on in es file explorer? Maybe you used JMZ's Fire Tool to block OTA? See if you have it and try that for unblocking. Or, if rooted this command might work:
Code:
adb -d shell "su -c 'mount -o remount,rw /system; cd /system/priv-app/; mv DeviceSoftwareOTA.apk_ DeviceSoftwareOTA.apk'"
If you can't get it renamed, try doing the update. Don't think it'll work, but worth a shot. If it doesn't work, you'll need to boot twrp and install 5.1.1 or 5.1.2 from there: http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
DoLooper said:
Try rebooting and see if it got renamed. Are you sure you're rooted and have root explorer on in es file explorer? Maybe you used JMZ's Fire Tool to block OTA? See if you have it and try that for unblocking. Or, if rooted this command might work:
Code:
adb -d shell "su -c 'mount -o remount,rw /system; cd /system/priv-app/; mv DeviceSoftwareOTA.apk_ DeviceSoftwareOTA.apk'"
If you can't get it renamed, try doing the update. Don't think it'll work, but worth a shot. If it doesn't work, you'll need to boot twrp and install 5.1.1 or 5.1.2 from there: http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
Click to expand...
Click to collapse
Definitely rooted, heck you yourself helped me do it a long time ago, even Root checker says i'm still rooted, I do have JMZ tool, the OTA section is gray though, reboot didn't help, will try the adb command
Edit, upon entering the command CMD appeared to hang/stall/do nothing. Not letting any other commands to be typed afterwards.
Shadowshinra said:
Edit, upon entering the command CMD appeared to hang/stall/do nothing. Not letting any other commands to be typed afterwards.
Click to expand...
Click to collapse
CTRL-C to get out. EDIT @Shadowshinra: Do you get # prompt with "adb shell" "su"?
DoLooper said:
CTRL-C to get out. EDIT @Shadowshinra: Do you get # prompt with "adb shell" "su"?
Click to expand...
Click to collapse
You mean the popup on the kindle? Now you mention it, It hasn't been popping up since I've been attempting this, so somehow I/it semi-unrooted itself despite the rootchecker saying it's fine? Or were the changed we did responsible?
Edit: Oh wait I know what you mean now, the # sign isn't there either, it's a $ so yeah It's unrooted itself somehow or I did something unknowingly, which is odd seeing as the Vire Launcher, root checker and all my apps are still working..
Edit2: Ran supersu, turned it off and on, appears to have fixed it? I was able to rename it aftar that.. it can't have been that simple lol..
Shadowshinra said:
Edit: Oh wait I know what you mean now, the # sign isn't there either, it's a $ so yeah It's unrooted itself somehow or I did something unknowingly, which is odd seeing as the Vire Launcher, root checker and all my apps are still working..
Edit2: Ran supersu, turned it off and on, appears to have fixed it? I was able to rename it aftar that.. it can't have been that simple lol..
Click to expand...
Click to collapse
Yes, there's a twilight-zone state in which root apps partially work but you can't get full superuser access until you update binaries by running superSU app. No idea how you lost su. Anyway, I trust you can update to unrooted stock 5.1.2 now.
DoLooper said:
Yes, there's a twilight-zone state in which root apps partially work but you can't get full superuser access until you update binaries by running superSU app. No idea how you lost su. Anyway, I trust you can update to unrooted stock 5.1.2 now.
Click to expand...
Click to collapse
When I tried to use that update it just says Validating update file, and seemingly loading forever, i'll edit if it ever completes, but if I turn on wifi it will try to download an update from there can that not be used instead or does that cause the bricks I've heard about?
Shadowshinra said:
When I tried to use that update it just says Validating update file, and seemingly loading forever, i'll edit if it ever completes, but if I turn on wifi it will try to download an update from there can that not be used instead or does that cause the bricks I've heard about?
Click to expand...
Click to collapse
The OTA update should be fine. I actually thought the manual method would be faster, but . . .
DoLooper said:
The OTA update should be fine. I actually thought the manual method would be faster, but . . .
Click to expand...
Click to collapse
Ah I see, however another issue has arisen, upon hitting update and it attempting to do so after a reboot, the team win recovery menu shows up instead, If I click reboot from there I'm just taken back to the dashboard on the original rooted firmware, I guess the TWRP is interfering in some manner? Also do I have to reenable the Fire Launcher and uninstall Virelauncher before all of this or will the updating process just do all of that.
Shadowshinra said:
Ah I see, however another issue has arisen, upon hitting update and it attempting to do so after a reboot, the team win recovery menu shows up instead, If I click reboot from there I'm just taken back to the dashboard on the original rooted firmware, I guess the TWRP is interfering in some manner? Also do I have to reenable the Fire Launcher and uninstall Virelauncher before all of this or will the updating process just do all of that.
Click to expand...
Click to collapse
@bibikalka, I totally forgot @Shadowshinra would have TWRP, coming from rooted OS4. Any problem with him following your steps here to restore stock? http://forum.xda-developers.com/fire-hd/general/how-to-restore-stock-fireos-t3164267 Thanks!