Related
I've just followed the guide to rooting the TF101 in One Click, via the Linux Boot method. It really is a brilliant application that was put together with the intention to save one a lot of time, however, although it tells me it has successfully completed and asks that I reboot the unit and to ensure that USB debugging is enabled, when I load Rom Manager it complains that it is not rooted. When I try to access terminal, I get the $, instead of the # and this does not change whether I Su, Sudo Su, Sudo Bash etc. In fact, I get Access Denied. Has anyone any recommendation?
Do you have the app "superuser" installed? If not, go to the market downlod and install it.
Sent from my Revolver powered Asus Transformer
Ah! I have not. There's always something missing Thanks much, I will give it a shot!
No Joy
Ouch...I was certain that that would have done the trick.
...
I think the problem is that the superuser app wants to install an SU update but it fails and tells me that the zip file has been placed on my SD and to flash it, of course, that's kind of counter productive, considering that I need superuser to work, in order to be able to flash the superuser update.
I am trying to root a motorola i886. Its a really wierd nextel iDEN PTT phone that is running (i believe) android 2.0 or 2.1 but has no touchscreen...
Basically I have been able to get a root shell (#) from 'adb shell' by pushing some program called psneuter to the phone and running it. Once I had this I could install apps via adb ok, but it seems like whenever I try to run any apps that require root they error saying they do not have root access.
As far as I can tell pretty much every rooting guide for every other phone has you putting 'su' and sometimes 'busybox' into /system/bin and 'Superuser.apk' into /system/app. I did both of these but still got the same errors about apps not having root. I tried a few different versions of these files I found from different sites to no avail. Running su on a terminal emulator on the phone itself would get the error "operation not allowed" or something like that. Then I found some other guide where you just copy 'sh' to 'su' and chmod su to 4755. When I did that I could get to a # prompt on the phone's terminal emulator app by typing 'su' but still got root errors for apps that need root.
I though maybe someone here would know something that I missed. As far as I can tell, I have applied the correct permissions to all these files or have at least tried every combination I can think of to no avail (shouldn't chmod 777 just make everything work?)
Also, does the phone usually come with a stock version of busybox on it? Do you need a specific version of these files for your device or version of android?
When an app on the phone tries to get root access is it just basically trying to run 'su' internally or something like that?
Also forgot to mention I have tried all the one-click-root apps and they do not work for this stupid phone. (well the super one click one was how I figured out how to get the adb shell root but the regular root button doesn't work...)
I can't help with your specific questions, but there is some info about rooting the i1, another iDEN with Android. Although it looks like the i1 is actually Android, and not the Motorola-altered, not-really-Android, proprietary software that the i886 has.
http://www.howardforums.com/showthread.php/1662431-Motorola-i1-Rooted
http://forum.cyanogenmod.com/topic/5520-ive-rooted-my-i1/
garbb said:
I am trying to root a motorola i886. Its a really wierd nextel iDEN PTT phone that is running (i believe) android 2.0 or 2.1 but has no touchscreen...
Basically I have been able to get a root shell (#) from 'adb shell' by pushing some program called psneuter to the phone and running it. Once I had this I could install apps via adb ok, but it seems like whenever I try to run any apps that require root they error saying they do not have root access.
As far as I can tell pretty much every rooting guide for every other phone has you putting 'su' and sometimes 'busybox' into /system/bin and 'Superuser.apk' into /system/app. I did both of these but still got the same errors about apps not having root. I tried a few different versions of these files I found from different sites to no avail. Running su on a terminal emulator on the phone itself would get the error "operation not allowed" or something like that. Then I found some other guide where you just copy 'sh' to 'su' and chmod su to 4755. When I did that I could get to a # prompt on the phone's terminal emulator app by typing 'su' but still got root errors for apps that need root.
I though maybe someone here would know something that I missed. As far as I can tell, I have applied the correct permissions to all these files or have at least tried every combination I can think of to no avail (shouldn't chmod 777 just make everything work?)
Also, does the phone usually come with a stock version of busybox on it? Do you need a specific version of these files for your device or version of android?
When an app on the phone tries to get root access is it just basically trying to run 'su' internally or something like that?
Also forgot to mention I have tried all the one-click-root apps and they do not work for this stupid phone. (well the super one click one was how I figured out how to get the adb shell root but the regular root button doesn't work...)
Click to expand...
Click to collapse
PM to me,i rooted sucefully, and install many applications with android SDK suite.
Regards.
geminis said:
PM to me,i rooted sucefully, and install many applications with android SDK suite.
Regards.
Click to expand...
Click to collapse
Wow, I can't believe someone found this thread and replied after so long. Thanks, but in the meantime I actually figured out how to root it fully and get root apps to work. I think i just tried different su's and superuser.apk's that I found on the internet until one worked...
Now, if you have figured out how to change the nextel push-to-talk chirp/beep sounds then let me know how you did that. I actually found the .wav files for the PTT sounds in some .apk in /system (phone.apk I think?) but for some reason changing them had no effect on the sound the phone makes when using the push-to-talk feature...
Its been 10 years but do you still have the firmware for this device? I need to flash it, it doesnt finish booting up
I don't have a full ROM .zip file for this phone, only some update .zips. But the first link result for a google search for "motorola admiral stock rom" worked for me for downloading a file.
Wrong phone, sorry.
Sorry but i don't understand. Isn't the Motorola admiral a different device? Does that zip work for the i886? If so, how do I flash it, because the i886 doenst have a recovery mode.
Oh, oops sorry, I was confusing this phone with another one. I looked and I don't have and firmware files for this, sorry.
OK, thanks for replying
Hello guys, as you know, the latest one click root that worked on the Transformer was SparkyRoot. Well, with the newest EeePad update (9.2.1.21), it is impossible to root without PC. Well, I have completely cracked the EeePad code. You will be amazed with the options included in my new one click root app. Try it and see for yourself! (Also works on TF201 and SF101 slide) Here is the download link. http://depositfiles.com/files/jp4hcc5ze
That's great to hear. To bad I'm already rooted so I can't try it.
Should make it easy for those needing to root if it work.
Didn't work set cpu and titanium back up didn't work
Sent from my Transformer TF101 using Tapatalk 2
First off..thanks for giving it a go..
Looking forward to hearing some solid reports.
You might want to put a little more detail into your OP..
As your post count is not up and your other threads are still feely new..
I am looking at picking up a new TF B60 next week and if this works as it should,of course will be willing to give it a go..
Sent from my Transformer TF101 using Tapatalk
Yes, there are problems with it. It seems to give partial root access, but not full root. I am working hard to fix the bugs. For some reason, root apps aren't detecting the root, but I was able to edit system files with no problems. The undetected installation for apps works, and transforming the tablet into Linux and MAC work. For some reason, windows is glitching up. Any ideas on how to get apps to detect root?
When i see partial root usually the su is not getting install to system/xbin but it is in system/bin. See that with the OTA root keeper sometimes.
Any movement or progress on this?
Sent from my SGH-I897 using XDA
baseballfanz said:
When i see partial root usually the su is not getting install to system/xbin but it is in system/bin. See that with the OTA root keeper sometimes.
Click to expand...
Click to collapse
Can you move it manually via terminal from bin to xbin? If so does that get you a full root?
Sent from my PG41200 using Xparent Purple Tapatalk 2
bsoplinger said:
Can you move it manually via terminal from bin to xbin? If so does that get you a full root?
Sent from my PG41200 using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
I don't know how this apps work but with OTA Rootkeeper you can copy su from system/bin to system/xbin and that solved it most of the times.
There is still bugs in this app. I am working hard to fix them. The su is in xbin, but still not full access. I heard undetected installation is known to glitch up and corrupt files. Maybe I need to remove undetected installation and do normal installation. But when you do normal installation for superuser (through app) it says "There was a problem parsing the package". Maybe use an alternative package installer?
Have you gotten any further in developing your app?
Yes, I got the windows transformation working. Few apps are detecting root, though. Screenshot apps detect it, and a few root managers work as well. Most arent detecting it, though. Also, syncing files doesnt work...
I have my one-click done, it's in my sig and called PERI.
Uses symlinking as found by wolf to grant root.
I'll be making an on tf app too soon. This is all completely open source and 100% working on the 3 tf101 based tfs. You can take a look at the code if you like, it's very simple.
Yes, I am familiar with PERI. PERI isnt an app, though. My Asus Root Menu is a one-click from the device-No PC required.
The commands can be run On-Tf, and I'm in progress of developing an app to put on the TF right now. Should work with 100% success. Then finally out of beta. If you need any assistance with building yours too I'm willing to help.
EDIT:
--
And dude, you're running into problems I almost GUARANTEE, because you're using andromo. Those 'make apps no coding required' wysiwyg tools are total junk. Code it the old-fashioned way :]
What method are you using too Root? I couldn't find any actual commands that are run by your app, just a bunch of invoke pages to text with nothing really attached too it except some ads stuff.. I apologize if I missed it.
And how in the world did you get linux/mac and windows 7 on there if the apk is only ~276KB A system image installer for the Ubuntu ARM image mabye, but there isn't an image for windows or mac (and both are closed-source).
--
Superuser needs to be flashed via recovery/bootloader/adb in a non-locked environment. This is probably where the problem parsing package error comes from.
--
Has anyone sides the OP gotten this too work even partially?
Yes, it has partially rooted a few people, and some people got full root. I have recieved many pm's about it. How is your app coming along?
I've read the dedicated thread on rooting the TF700t with DebugfsRoot_v1.9 (http://forum.xda-developers.com/showthread.php?t=1706588&page=48).
I did successfully root a TF700t with 9_4_5_22.
Now I tried the same method after upgrading another TF700t from stock to 9_4_5_26.
Everything works fine during rooting (I've tried both manual and automated DebugfsRoot 1.9) with the following exceptions:
1. during the 3rd stage of rooting, I get
/system/bin/sh: /system/xbin/su: not executable: magic 7F45
2.
Superuser access does not seem to be active after rooting. I did uninstall and re-install Superuser with no superuser access success.
I tried both under XP and 7/32 on the same device, no errors but root does not seem to be active. Between rooting attempts, I restored stock ROM.
Other details:
Asus USB drivers installed (off Asus website)
Asus synch is disabled and prevented from launching.
Security/Unknown sources is checked.
Developer options / USB debugging is ON/checked.
What do you think goes wrong?
Any help is appreciated. Thx
the same..
I have nearly the same problem...
I have updated my rooted .21 to .26, then unlocked it and as it seems have lost root. I dont really know if it happened afted updating or afted unlocking...
None of my R-applications can get root, and so on...
I've tried to use the same method i used to get root on .21 and got this:
Step 2 - Rooting...
debugfs 1.42 (29-Nov-2011)
debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs:
debugfs: debugfs: Allocated inode: 1469
debugfs: debugfs: debugfs: debugfs:
Rebooting...
Testing superuser...
uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),
1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats)
uid and gid should both be 0.
Are they? (y/n):
Click to expand...
Click to collapse
And still no root...
What am i doing wrong? What to do next?
Thanks!
Is it a superuser problem?
EnginesRun said:
2.
Superuser access does not seem to be active after rooting. I did uninstall and re-install Superuser with no superuser access success.
Any help is appreciated. Thx
Click to expand...
Click to collapse
Can't help yet but I am having a similar problem with SU; its presence suggest I have root but it denies everyone else SU permissions...
After rooting, run SuperUser explicitly from the applications menu. Then try your apps that require root access. I noticed that I had the issue of running the DebugFS root batch and then later was not able to properly run Adaway. Ran SuperUser, then everything went smooth.
I think someone already mentioned this in another thread.
alienedd said:
After rooting, run SuperUser explicitly from the applications menu. Then try your apps that require root access. I noticed that I had the issue of running the DebugFS root batch and then later was not able to properly run Adaway. Ran SuperUser, then everything went smooth.
I think someone already mentioned this in another thread.
Click to expand...
Click to collapse
nope. doesnt help in my case..
---------- Post added at 10:17 AM ---------- Previous post was at 09:37 AM ----------
ok, i've solved my problem.
the idea mentioned by alienedd helped me to see that i could have a working root but faulty superuser app.
so i started with installing it from market.
then i ran DebugfsRoot_v1.9.
till it got to this point:
Testing superuser...
uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(m ount),1011(adb),
1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),30 03(inet),3006(net_bw_stats)
uid and gid should both be 0.
Are they? (y/n):
Click to expand...
Click to collapse
then i have cleared all the data held by superuser app through settings\apps, stopped it and uninstalled.
after that i continued with the script and it installed me superuser app again.
after installing i've launched it and then ckecked my root-needed apps. they are ok now.
Ahhh, yeah. Read about that in the DebugFS thread that sometimes one needs to uninstall superuser then reinstall for it to run properly. Didn't think about that. Glad that its all working now for yas.
I have tried all of this with 4 different packages (3 of the automated root from here and 1 from a link in the [RESOURCES] thread in the dev forum. every time, each package says that I have root, but when I check I do now. I followed what masseselev said and it failed as well. I have spent the better part of 5 hours trying to root. I guess I should say that I just got my infinity last night...and like a crackhead applied .26 ota without thinking about it. but I have read where the automated works fine with .26. I am pulling my hair out trying to figure out why I cant get root on this thing. the packages always say that they were successful and that I have root, but I do not. no apps can gain root. terminal emulator still shows $ after trying to enter "su". I have tried several different root checkers and they all say I do not have root. any other ideas? I should also say that I have not unlocked the bootloader.
henbone11 said:
I have tried all of this with 4 different packages (3 of the automated root from here and 1 from a link in the [RESOURCES] thread in the dev forum. every time, each package says that I have root, but when I check I do now. I followed what masseselev said and it failed as well. I have spent the better part of 5 hours trying to root. I guess I should say that I just got my infinity last night...and like a crackhead applied .26 ota without thinking about it. but I have read where the automated works fine with .26. I am pulling my hair out trying to figure out why I cant get root on this thing. the packages always say that they were successful and that I have root, but I do not. no apps can gain root. terminal emulator still shows $ after trying to enter "su". I have tried several different root checkers and they all say I do not have root. any other ideas? I should also say that I have not unlocked the bootloader.
Click to expand...
Click to collapse
What exactly are you doing as its kind of hard to determine what has gone wrong?
DebugFS works with .26 OTA and you don't need an unlocked bootloader for it to work (though having root might cause problems for getting OTAs and the unlocker to work).
alienedd said:
What exactly are you doing as its kind of hard to determine what has gone wrong?
DebugFS works with .26 OTA and you don't need an unlocked bootloader for it to work (though having root might cause problems for getting OTAs and the unlocker to work).
Click to expand...
Click to collapse
just trying to run the debugFS automated tool. it runs fine, and gives all indications that it works successfully. but I still dont have root. its driving me crazy. I have run 2.0, 2.1 and 2.2 packages and all said I was rooted...but I dont think I am. I have installed and uninstalled superuser and rebooted numerous times. I went ahead and unlocked the bootloader and it still wont work. I can open a command prompt from within the package folders (2.0, 2.1 and 2.2) and run adb shell, then su and it shows #. but if I do it from terminal on the infinity it shows $ when i do su. sorry if im vague, im just brain fried at this point and dont know what else to do.
henbone11 said:
just trying to run the debugFS automated tool. it runs fine, and gives all indications that it works successfully. but I still dont have root. its driving me crazy. I have run 2.0, 2.1 and 2.2 packages and all said I was rooted...but I dont think I am. I have installed and uninstalled superuser and rebooted numerous times. I went ahead and unlocked the bootloader and it still wont work. I can open a command prompt from within the package folders (2.0, 2.1 and 2.2) and run adb shell, then su and it shows #. but if I do it from terminal on the infinity it shows $ when i do su. sorry if im vague, im just brain fried at this point and dont know what else to do.
Click to expand...
Click to collapse
Yeah, I understand. Um, I know I've repeated this several other times but I don't see it in your list of things you've done. Were you able to open up the superuser application? It seems that if it opens, you have root, and in some cases might not work until it is opened. It's both fortunate and unfortunate that I did not encounter many problems while rooting so my experience with possible errors isn't that expansive. However, you've run the package(s) completely so it's not a driver issue and you can adb and see su access. It just seems like the tablet isn't recognizing that it does have it.
yeah, I ran superuser immediately after rooting. then rebooted each time. http://forum.xda-developers.com/showpost.php?p=29951628&postcount=494
lol thats everything that I have tried. kinda sucks, but im sure someone will figure it out at some point.
weird thing is, if I run a command prompt from within the package folders I see that its rooted. if I run terminal on the device it says permission denied and prompt is still $. just odd.
I'm sure that sparky can give you help in the main thread as he has a whole lot more knowledge about the possible failings. Also, read over some of the other threads here as there seem to be quite a few people with errors that I don't even understand why they are happening. Maybe a something like simply the drivers? http://forum.xda-developers.com/showpost.php?p=29974269&postcount=9
Other then that, I'm at a loss bud. Do mention the fruits of your research though as I'm sure it would definitely be helpful to others.
alienedd said:
I'm sure that sparky can give you help in the main thread as he has a whole lot more knowledge about the possible failings. Also, read over some of the other threads here as there seem to be quite a few people with errors that I don't even understand why they are happening. Maybe a something like simply the drivers? http://forum.xda-developers.com/showpost.php?p=29974269&postcount=9
Other then that, I'm at a loss bud. Do mention the fruits of your research though as I'm sure it would definitely be helpful to others.
Click to expand...
Click to collapse
yeah, we have been trying to figure it out...no joy. I have seen quite a few people with the same issue. hopefully someone can sort out why its happening soon. even if I cant root, at least knowing why would somewhat appease me.
henbone11 said:
yeah, we have been trying to figure it out...no joy. I have seen quite a few people with the same issue. hopefully someone can sort out why its happening soon. even if I cant root, at least knowing why would somewhat appease me.
Click to expand...
Click to collapse
Perhaps this then?
d14b0ll0s said:
Perhaps this then?
Click to expand...
Click to collapse
Ok, I followed this http://forum.xda-developers.com/showpost.php?p=28519641&postcount=11 and was successful in rooting mine and my gf's infinity's.
one thing though. after manually rooting, after the final reboot, go into the Superuser app. DO NOT UPDATE IT FROM WITHIN THE APP. for some reason, updating from within Superuser borks the app. at least it did for mine and my gf's.
optional:
close Superuser. go to the play store and download busybox installer (needed to run titanium backup), root checker (there are a ton, just pick one of the top ones), adaway, ota rootkeeper and titanium backup. doesnt matter what order. I would run busybox installer first though once you have everything installed. after busybox installs, you can run root checker, adaway or titanium to check root. I say after you install busybox because some apps do require busybox to be installed before they consider you rooted. if you get the superuser prompt to allow/deny, everything is working fine. once you know that you have root and everything is working ok, run ota rootkeeper.
my only question at this point is regarding OTA updates. to my understanding, simply rooting will allow you to continue to receive OTA updates, but unlocking the bootloader will prevent you from getting OTA updates...is this correct?
MOVED/UPDATED for 1.21. Thread saved/closed for any help/assistance/value left in it.
Thanks for posting the updated utility.
Number 4 explained mentions TWRP again instead of CWM though.
killrhythm09 said:
Thanks for posting the updated utility.
Number 4 explained mentions TWRP again instead of CWM though.
Click to expand...
Click to collapse
That's what I get for copy pasting it
Fixed
Nice work Matt
Will this work on the latest OTA 9.16.6? I know the previous version did not and I have been waiting to root my phone. If yes, do I simply do options 6, then 5, and my choice of either 3/4?
helloterence said:
Will this work on the latest OTA 9.16.6? I know the previous version did not and I have been waiting to root my phone. If yes, do I simply do options 6, then 5, and my choice of either 3/4?
Click to expand...
Click to collapse
Yes it will work. The unlock requires root so use Motochopper first to root
Sent from my Galaxy Nexus using Tapatalk 2
took all of 10 minutes to be stock then be re-downloading all my apps on AOKP, great work man!!
sent on the fly from my RAZR HD
I'm so glad I found the original Droid Razr HD Utility. I almost downloaded a rip off utility copied from you by a guy named after an illness that people "shake" from. Begins with a P if you know who I mean.
I love my Razr HD. iPhone 5 and S3 didn't work out for me. Poor WiFi performance. I like the idea of a TWRP so I can make a full backup to my SD card.
Matt,
First, let me say thanks for all your amazing work developing this phone and for the two utilites (I am very grateful for 1.10 and looking forward to using 1.20).
Before I jump into the utility, I want to (as briefly as possible) explain my situation (and now looking back, ask a ton of questions): I have 4.1.1, rooted, and have performed the Wireless Hotspot hack procedure. I am unable to take the 4.1.2 update (most likely due to my hacking of the hotspot app, though I may have done something else that I don't remember). Will I be able to use this utility to upgrade to 4.1.2? And unlock my bootloader? And keep (or re-do) my hotspot hack? What is the correct order for me? I'm thinking since I am rooted, I unlock the bootloader, then install 4.1.2, correct? Does this keep my root intact, or do I need to use VooDoo OTA Rootkeeper to unroot prior to performing the 4.1.2 update in the utility, then re-root?
Finally, is there a way to copy and save my currently installed apps (and pics, etc) so I don't have to re-install them all? Is this the function of Titanium Backup, or is there a different/easier way to do it?
Thanks again!
LifeAsADroid said:
Matt,
First, let me say thanks for all your amazing work developing this phone and for the two utilites (I am very grateful for 1.10 and looking forward to using 1.20).
Before I jump into the utility, I want to (as briefly as possible) explain my situation (and now looking back, ask a ton of questions): I have 4.1.1, rooted, and have performed the Wireless Hotspot hack procedure. I am unable to take the 4.1.2 update (most likely due to my hacking of the hotspot app, though I may have done something else that I don't remember). Will I be able to use this utility to upgrade to 4.1.2? And unlock my bootloader? And keep (or re-do) my hotspot hack? What is the correct order for me? I'm thinking since I am rooted, I unlock the bootloader, then install 4.1.2, correct? Does this keep my root intact, or do I need to use VooDoo OTA Rootkeeper to unroot prior to performing the 4.1.2 update in the utility, then re-root?
Finally, is there a way to copy and save my currently installed apps (and pics, etc) so I don't have to re-install them all? Is this the function of Titanium Backup, or is there a different/easier way to do it?
Thanks again!
Click to expand...
Click to collapse
Unlock your bootloader before you try to do anything, it's the best safeguard to have.
You can go to 4.1.2 with it from 4.1.1 yes.
This is not a rootkeeping utility. If you unlock you can always flash a root.zip like Superuser.zip, SuperSu.zip, etc. in CWM or TWRP to root. You don't need Voodoo anymore.
Backups is up to you. Titanium Works AFAIK.
I think I got all the questions hidden in that blob of text, hopefully
Thanks Matt!
- I've unlocked the bootloader this morning and it worked perfectly (have to find the program in the forum to change the "bootloader unlocked" startup screen now, but I digress).
- After installing 4.1.2 I can always re-root using the utility I'm guessing, yes?
- Will the utility install 4.1.2 and replace a "modified" 4.1.1, or do I have to have a "stock" 4.1.1 ROM for the 4.1.2 to work? By "modified" I mean deleted apps, reconfigured SQLite Edited hotspot app, etc... I only ask since I cannot get the 4.1.2 OTA to install as my phone is currently, and was wondering if it was known if I would run into the same problem using the Utility 1.20. Or if this is the reason for the creation of the Utility 1.20...
- If I have to be stock and the 4.1.2 won't work as my phone is currently, I am thinking I could use the Utility 1.10 to go back to 4.0.4, then up to stock 4.1.1 and 4.1.2 from there (or straight to 4.1.2 from 4.0.4 if possible), then re-delete and re-hack the apps I want to delete and hack (if that all makes sense).
Another blob of text, hopefully broken down a little bit better for you
LifeAsADroid said:
Thanks Matt!
- I've unlocked the bootloader this morning and it worked perfectly (have to find the program in the forum to change the "bootloader unlocked" startup screen now, but I digress).
- After installing 4.1.2 I can always re-root using the utility I'm guessing, yes? Yes... but it's better to flash SuperSu.zip through CWM or TWRP because no doubt in the next update the Motochopper exploit will be patched.
- Will the utility install 4.1.2 and replace a "modified" 4.1.1, or do I have to have a "stock" 4.1.1 ROM for the 4.1.2 to work? By "modified" I mean deleted apps, reconfigured SQLite Edited hotspot app, etc... I only ask since I cannot get the 4.1.2 OTA to install as my phone is currently, and was wondering if it was known if I would run into the same problem using the Utility 1.20. Or if this is the reason for the creation of the Utility 1.20...This Utility will install 4.1.2 using the FXZ files. You won't need to OTA, this brings you there.
- If I have to be stock and the 4.1.2 won't work as my phone is currently, I am thinking I could use the Utility 1.10 to go back to 4.0.4, then up to stock 4.1.1 and 4.1.2 from there (or straight to 4.1.2 from 4.0.4 if possible), then re-delete and re-hack the apps I want to delete and hack (if that all makes sense). I don't understand why you don't just go directly to 4.1.2 using this
Another blob of text, hopefully broken down a little bit better for you
Click to expand...
Click to collapse
Hope I helped...
LifeAsADroid said:
Thanks Matt!
- I've unlocked the bootloader this morning and it worked perfectly (have to find the program in the forum to change the "bootloader unlocked" startup screen now, but I digress).
Click to expand...
Click to collapse
http://www.droidrzr.com/index.php/t...der-unlock-warning-with-1-click/?fromsearch=1
Hi Matt,
Ok, so I attempted using the utility to run options 1 and 2. No dice. Option 1 looked like the below attachment. Ran in AP Fastboot, USB debugging enabled. Tried twice, once rooted, once not, same outcome. Any ideas what's wrong?
Thanks!
Use different USB cable and non-3.0 port.
Sent from my Galaxy Nexus using Tapatalk 2
Tried a few different cables, few different ports on the computer, still no dice. I guess I am destined to have 4.1.1 forever
PS - thanks erj-drvr for the bootloader screen changing url!
Im on 4.1.1 everything working fine I just want to get to 4.1.2 is this the best way to do it or is there an easier way? I am unlocked and rooted if I use the utility it will put me on 4.1.2 still unlocked I will have to get a recovery and root correct? It wont unlock me?
I selected option 5 and tried to do the Motochopper root exploit. Though the exploit in the console showed as successful, when I rebooted and run Root Checker Pro, I see the issues below.
I was on 4.1.1 w/ root, got 4.1.2, which broke root. Per the above, Motochopper showed as working, but that doesn't seem to be the case. Any suggestions?
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 1.25 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/xbin/su:
Result: ---sr---wt root root 91980 2013-04-28 00:36 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwxr-xr-x root shell 380532 2013-01-11 13:48 su
Analysis: Setuid attribute NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your DROID RAZR HD device by Root Checker Pro version 1.3.1 from joeykrim in the Android Market - http://goo.gl/NcnHn
Click to expand...
Click to collapse
Assuming I am BL unlocked, rooted and on 4.1.2 with CWM installed after using the utility, can I then just flash the latest CM 10.1 nightly?
Can I safely remove Safestrap now and just use CWM instead? Thanks.