I have rooted my phone successfully, and in the beginning apps that required root access would check for root, and request su access, but now that doesn't happen.
1. Anyone know what happened, and how do I get applications to request root access again?
2. How do I update the SuperSU binary, when it asks?
Rooted using SlapMyMoto, on Android 4.4 Stock.
Make sure you have the latest supersu from the play store but when it asks you to update the SU binary, it should show two options, normal and twrp, since i'm assuming you're locked (plus it's just easier), choose normal. Also, i'm not sure what the process is, but you might need to re-run whatever it is that you use to root (i'm unlocked so i'm not familiar with the process) because it sounds like you don't have system mounted as rw. If this is the result of an OTA, because people are losing rw from taking the verizon OTA, you might be out of luck until a new method is found.
-edit- another fix might be to re flash supersu if you have safestrap installed, and just clarification, it will not ask for root for the same app twice unless you tell it to ask again next prompt.
StATicxTW0T said:
Make sure you have the latest supersu from the play store but when it asks you to update the SU binary, it should show two options, normal and twrp, since i'm assuming you're locked (plus it's just easier), choose normal. Also, i'm not sure what the process is, but you might need to re-run whatever it is that you use to root (i'm unlocked so i'm not familiar with the process) because it sounds like you don't have system mounted as rw. If this is the result of an OTA, because people are losing rw from taking the verizon OTA, you might be out of luck until a new method is found.
-edit- another fix might be to re flash supersu if you have safestrap installed, and just clarification, it will not ask for root for the same app twice unless you tell it to ask again next prompt.
Click to expand...
Click to collapse
Thanks for the reply. I took the OTA to 4.4 from 4.2, and I was still rooted. Something happened with SuperSU, and now the phone is behaving as if it is not rooted, or it's half rooted (if that makes sense).
MyBackupPro would always ask for root access, and then SuperSU would grant it automatically. Now this doesn't happen. Also, I'm trying to use Helium backup as well, and when it tries to ask for root access, it fails. Any app that usually requests root access doesn't even ask.
Thanks.
akhenax said:
Thanks.
Click to expand...
Click to collapse
I wouldn't take my word for it, but i remember reading about a downgrade then upgrade process where you would downgrade to 4.2.2 post cam then root then upgrade again, it might help, no guarantee's though.
StATicxTW0T said:
I wouldn't take my word for it, but i remember reading about a downgrade then upgrade process where you would downgrade to 4.2.2 post cam then root then upgrade again, it might help, no guarantee's though.
Click to expand...
Click to collapse
I always thank replies whether it helps or not.
I am trying to retrace the steps I did to root, but not the entire process. Hope to save time from having to redo everything again.
I fixed it.
I did the following steps (not sure if this did anything but...):
uninstall SuperSU
adb reboot bootloader
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot reboot
adb push su /data/local/tmp/su
adb push install.sh /data/local/tmp/install.sh
adb push rec.sh /data/local/tmp/rec.sh
adb push install-recovery.sh /data/local/tmp/install-recovery.sh
adb push setup.sh /data/local/tmp/setup.sh
adb reboot
adb shell
echo "/data/local/tmp/rec.sh" > /sys/kernel/uevent_helper
<-- THIS FAILS, as expected. It worked when I first rooted the device, but doesn't work any longer, but this is OK.
it returns: /system/bin/sh: can't create /sys/kernel/uevent_helper: Permission denied
Once again, this is OK.
Install SuperSU
DO NOT OPEN IT. JUST INSTALL IT.
Apps now request root permission.
adb shell getprop ro.boot.write_protect
returns a value of:1 which means my bootloader is locked write protection is enabled, but I still have proper root access.
Hope this helps the next guy.
akhenax said:
adb shell getprop ro.boot.write_protect
returns a value of:1 which means my bootloader is locked, but I still have proper root access.
Click to expand...
Click to collapse
This actually means that write protection is enabled.
Did you try to reboot into"recovery" to set write protection off?
nhizzat said:
Did you try to reboot into"recovery" to set write protection off?
Click to expand...
Click to collapse
I don't think I'm versed enough in this to answer this question accurately, for the very reason you quoted "recovery". How would you accomplish such a feat, step by step?
akhenax said:
I don't think I'm versed enough in this to answer this question accurately, for the very reason you quoted "recovery". How would you accomplish such a feat, step by step?
Click to expand...
Click to collapse
power down, hold volume down and power, youll get a black screen with blue letters. use volume down button to naviagte and power to select.
xpsychox said:
power down, hold volume down and power, youll get a black screen with blue letters. use volume down button to naviagte and power to select.
Click to expand...
Click to collapse
The question was: Did you try to reboot into"recovery" to set write protection off?
Do your steps allow one to do this?
akhenax said:
The question was: Did you try to reboot into"recovery" to set write protection off?
Do your steps allow one to do this?
Click to expand...
Click to collapse
ahh, my bad miss read it.. lol... oops
akhenax said:
I don't think I'm versed enough in this to answer this question accurately, for the very reason you quoted "recovery". How would you accomplish such a feat, step by step?
Click to expand...
Click to collapse
When in Android, connect the phone to your PC USB port. I hope you've already installed the Android SDK and Moto drivers. Open a cmd prompt with admin privileges and type "adb devices" to check if your PC recognizes the phone. If so, then type "adb reboot recovery". The phone will reboot just as it normally would, only this time write protection is off. Or do the steps below or type "adb reboot bootloader".
xpsychox said:
power down, hold volume down and power, youll get a black screen with blue letters. use volume down button to naviagte and power to select.
Click to expand...
Click to collapse
Volume up to select, actually.
Related
Hi, I'm hoping someone can help me. I'm running OSX Snow Leopard, using terminal and attempting to gain root access to my new Nexus One. I was able to quickly and easily unlock the boot loader, however, I have made multiple attempts to gain root access for model ERE27 using superboot, but while everything seems to appear normal, I can not flash the recovery-RA-nexus-v1.7.0.1-cyan.img. When I reboot the phone I attempt to run terminal app from market and find I am still denied permission. I've checked every site I could to correct this, but seem to be missing something every time. When attempting to root, I cd to applications/android-sdk-mac_86/tools/superboot. I press enter then chmod +x-install-superboot-mac.sh Then I press enter and key ./fastboot-mac. After processing in terminal and seeing a status bar briefly on the nexus upper right screen of the Nexus, terminal says Okay. I reboot and no root access. PLEASE HELP. Been at this for an embarrassingly long time now...
Have you installed a rooted rom? or just trying to see if you have root access on the stock rom?
Jeremy.Bentham said:
Hi, I'm hoping someone can help me. I'm running OSX Snow Leopard, using terminal and attempting to gain root access to my new Nexus One. I was able to quickly and easily unlock the boot loader, however, I have made multiple attempts to gain root access for model ERE27 using superboot, but while everything seems to appear normal, I can not flash the recovery-RA-nexus-v1.7.0.1-cyan.img. When I reboot the phone I attempt to run terminal app from market and find I am still denied permission. I've checked every site I could to correct this, but seem to be missing something every time. When attempting to root, I cd to applications/android-sdk-mac_86/tools/superboot. I press enter then chmod +x-install-superboot-mac.sh Then I press enter and key ./fastboot-mac. After processing in terminal and seeing a status bar briefly on the nexus upper right screen of the Nexus, terminal says Okay. I reboot and no root access. PLEASE HELP. Been at this for an embarrassingly long time now...
Click to expand...
Click to collapse
Try using the nexus-addon-0.1-signed.zip
http://forum.xda-developers.com/showthread.php?t=636795
I'm just sayin' I hope that we get to see some love and get the CM9 rom for the OB. I would really like to get ICS before the middle of next year. Is there somewhere we can put in some kind of request? or is there a way to use an existing CM9 build to port it to the OB using something from a CM7 build? I've had the phone for about 5 months and getting tired of running 2.2 Froyo just still debating whether to take the plunge and root and put on CM7 or wait it out a little longer. I really have never messed with an android phone before but I read alot on the forum and it seems relatively easy to get the CM7 on there just afraid to root and lose my warranty and something break lol.
Just hack away, don't worry about your warranty. You might get your phone stuck in a bootloop, i've done that several times already, lol. It sucks when it happens, but you can always connect it to your windows pc and restore it to factory settings, unrooted and everything. No one will ever know your phone was rooted
And just to add something, if you can install Android SDK on your computer, you can use ADB Reboot Recovery (if you put recovery on your phone of course). It save me great time.
Sent from my LG-P970 using xda premium
how do u restore the phone? if I know I can unroot it and it won't affect my warrenty ill do it lol I have v10a and have never been able to update higher then that. do I use gingerbreak and the app says it can unroot? like I said if I can unroot it and keep warrenty ill do it
Sent from my LG-P970g using xda premium
I would like Sobralobo to elaborate what he is talking about, sounds like it could save some time after a screwup. However, no matter the condition of your software, you can remove battery, hold vol+ and connect the microusb to your pc. On your pc, you run a LG app, input your imei, and the app will identify your device. It will also tell you if a new software is available. Even if it says it isn't, you can click Options > Recovery (or something like that, i write from my own memory now), and force a update. I'm also pretty sure you'll get V10d or V10e if you do. This process equals to format you phone and install everything from scratch, the way LG intended it to be. All of your personal stuff will be gone, all apps etc. (Obviously, not the stuff you got stored on your sd card, and apps you already bought are linked to your google account and will always follow you
Gingerbreak works for V10a/b afaik, if you get V10c/d/e, you can use this method:
xantaro said:
I got the EU Version of 10c rootet with this method:
1. Download and start SuperoneClick 1.9.5, click Shell Root
2. When it hangs up on a black CMD windows, close this Window. (You should have Shell Root now)
3. Unpack the attached File in your ADB Folder.
4. open a Command Prompt and enter "adb push su /tmp/" & adb push superuser.apk /tmp/"
5. Type "adb shell" ( When Shellroot worked, you should se a "#" on the shell
6. Enter the following commands in shell:
Code:
mount -o rw,remount -t ext3 /dev/block/mmcblk0p8 /system
cat /tmp/su > /system/bin/su
cat /tmp/superuser.apk > /system/app/Superuser.apk
chown root.root /system/bin/su
chmod 06755 /system/bin/su
chown root.root /system/app/Superuser.apk
chmod 0644 /system/app/Superuser.apk
reboot
7. The Phone will now reboot, after reboot it´s rooted again
Click to expand...
Click to collapse
hulkhaugen said:
I would like Sobralobo to elaborate what he is talking about, sounds like it could save some time after a screwup. However, no matter the condition of your software, you can remove battery, hold vol+ and connect the microusb to your pc. On your pc, you run a LG app, input your imei, and the app will identify your device. It will also tell you if a new software is available. Even if it says it isn't, you can click Options > Recovery (or something like that, i write from my own memory now), and force a update. I'm also pretty sure you'll get V10d or V10e if you do. This process equals to format you phone and install everything from scratch, the way LG intended it to be. All of your personal stuff will be gone, all apps etc. (Obviously, not the stuff you got stored on your sd card, and apps you already bought are linked to your google account and will always follow you
Gingerbreak works for V10a/b afaik, if you get V10c/d/e, you can use this method:
Click to expand...
Click to collapse
What Sobralobo said is that just installing Android SDK (Search Google and you get more thousands of tutorials to install SDK and everything you need. Even in O Black section I think there is one with Black drivers and all. Maybe is this one.) you can use "adb reboot recovery" when your Black is in a bootloop or whatever, then you just flash/restore and you are done way faster than reflashing stock firmware. And in certain occasions (for example when you have a certain ROM and you try to flash a modded file in flashable zip that breaks it, you can just flash your ROM without wipe just to fix it and you lose nothing).
PS: You don't even need SDK. There are standalone adb packages, and with LG Black drivers, you can do the same.
This is needed when you mess up with the phone testing all the freaking day like I used to and many others do now.
OK, cool. I'm using adb for rooting and pull/push framework-res.apk and other small mods, didn't know it was compatible with nandroid backups. That can save me a lot of time and trouble next time i mess it up
hulkhaugen said:
OK, cool. I'm using adb for rooting and pull/push framework-res.apk and other small mods, didn't know it was compatible with nandroid backups. That can save me a lot of time and trouble next time i mess it up
Click to expand...
Click to collapse
Well, not directly related to nandroid backups. Just do "adb reboot recovery" (without the "") when you are in trouble. Depending on the situation you will have to input that many times (up arrow and enter fast and many times) if it's bootlooping to find the proper moment when the phone actually receives the command, but it's easy. Once in recovery, you do what you need to do.
aha. so i suppose it won't work with stock bootloader, since LG says "ERROR, LG Security team!!". Still neat that i can restore my backup from bootloader
hulkhaugen said:
aha. so i suppose it won't work with stock bootloader, since LG says "ERROR, LG Security team!!". Still neat that i can restore my backup from bootloader
Click to expand...
Click to collapse
Hmm I think you are partially right. I think in Black bootloader is never changed. When "ERROR, LG Security team!!" is because you really messed up and I believe you have nothing else than flashing. But if you have Clockworkmod recovery (you have if you do nandroid backups), it's worth a try.
I was talking more about bootloops, but maybe when "ERROR, LG Security team!!", if you take the battery off and when put it in again you play with adb reboot recovery, it may work. I can't remember.
antonio1475 said:
Hmm I think you are partially right. I think in Black bootloader is never changed. When "ERROR, LG Security team!!" is because you really messed up and I believe you have nothing else than flashing. But if you have Clockworkmod recovery (you have if you do nandroid backups), it's worth a try.
I was talking more about bootloops, but maybe when "ERROR, LG Security team!!", if you take the battery off and when put it in again you play with adb reboot recovery, it may work. I can't remember.
Click to expand...
Click to collapse
It won't work with adb reboot recovery,I've tried it and failed,won't detect the phone
At least,in my case, it happened when i tried to do a nandroid restore from cm7 to stock (v10a, wiped)
Sent from my heart into yours
So, I followed the guide we all did here:
http://forum.xda-developers.com/showthread.php?t=1818502
And before someone asks: I have deleted the Backup app (IS11LG_SystemBackupTest.signed.apk) we had to install during rooting after the phone was rooted.
The phone then happily ran, rooted. SUpersu was installed/updated, the phones root check said it's all perfect, I was a happy camper. But today I had to reboot it. I can't say if it was the first reboot after rooting, sadly. The phone boots up, arrives at the lockscreen (some colorful defaultthing, before I get to see my GO Locker screen after login), and then stops being responsive, it basically at first feels like it's not reacting at all. Some things are responsive, strngely ... I get accurate sounds when touching the screen for instance. If I then wait, I eventually get to the SIM Unlock ... which is also totally unresponsive, it will maybe show two digits, then freezes up. Strangely, I could type the remaining digits and hit OK and the SIM would unlock ... but the screen no longer showed what I typed. I then arrive at GO locker, can unlock it (sluggish and slow again) and finally am properly logged in, but still totally sluggish and slow. Needles to say it's a pseudobrick that way, unusable.
What's going on and what could I check?
Please try the following:
alexp999 said:
REALLY SLOW AFTER ROOT?
Remove the "SystemBackupTest" app, if you haven't already.
On your phone, go to "Settings -> Developer options" and make sure "USB debugging" is TICKED
Connect your phone via USB to your computer.
Open a command prompt (may need admin privelages, right click, run as administrator)
Type without quotes "cd C:\o4xr" and press enter.
Type without quotes "adb shell rm /data/local.prop" and press enter.
Type without quotes "adb reboot" and press enter.
Click to expand...
Click to collapse
alexp999 said:
Please try the following:
Click to expand...
Click to collapse
Thanks, that fixed it! It's not easy to do, as the scrolling lists do not work, either, and you can't seem to get to the developer options, it won't scroll. Strangely enough "internally" it seems to do things ... if you re-enter the options, they're down to the end of the list, it looks like it doesn't update the screen properly (much like when I had to enter the SIM code).
Anyway, it's fast again, whew ... I was scared. What is the local.prop thing, if I may ask?
voon said:
Thanks, that fixed it! It's not easy to do, as the scrolling lists do not work, either, and you can't seem to get to the developer options, it won't scroll. Strangely enough "internally" it seems to do things ... if you re-enter the options, they're down to the end of the list, it looks like it doesn't update the screen properly (much like when I had to enter the SIM code).
Anyway, it's fast again, whew ... I was scared. What is the local.prop thing, if I may ask?
Click to expand...
Click to collapse
I'm not entirely sure, I just know it gives us temp root for the rest of the root script to run.
Hm, so its' not a systemwide ini file or so, that existed before ... it was created during the above rooting process and was an undesired leftover from it? I'm always a bit worried if I delete something with such an unspecific name in the OS
voon said:
Hm, so its' not a systemwide ini file or so, that existed before ... it was created during the above rooting process and was an undesired leftover from it? I'm always a bit worried if I delete something with such an unspecific name in the OS
Click to expand...
Click to collapse
Its actually created by the SystemBackupTest app.
The script then removes it just before issuing a reboot.
The only way it can come back, is if you accidently open that app again before uninstalling it.
alexp999 said:
Its actually created by the SystemBackupTest app.
The script then removes it just before issuing a reboot.
The only way it can come back, is if you accidently open that app again before uninstalling it.
Click to expand...
Click to collapse
I see, I might have done that ... good to know. Anyway, great that it works again, thanks again
laggy phone
My lg 4x hd is very slow after root...
I just tried to make this few steps above, but I got this message.
Any idea what to do?
Pls help me!
THX
66aaa
66aaaa said:
My lg 4x hd is very slow after root...
I just tried to make this few steps above, but I got this message.
Any idea what to do?
Pls help me!
THX
66aaa
Click to expand...
Click to collapse
It looks like you have either plugged in more than one android device, or you have an android emulator (from the SDK I guess) running. Unplug all USB devices (except keyboard and mouse) and then try again. Good luck!
If you have an emulator running try "adb -d shell rm /data/local.prop"
Edit: To see all adb-devices type "adb devices". This will return a list of all adb-devices connected (emulators + usb devices)
Dexxon said:
If you have an emulator running try "adb -d shell rm /data/local.prop"
Edit: To see all adb-devices type "adb devices". This will return a list of all adb-devices connected (emulators + usb devices)
Click to expand...
Click to collapse
I still don't understand and hope you do it...
THX for your help!
As you can see the same device is listed two times. Restarting the adb server may help. Just type "adb kill-server" and than launch the second command from your screenshot. Maybe this works.
Dexxon said:
As you can see the same device is listed two times. Restarting the adb server may help. Just type "adb kill-server" and than launch the second command from your screenshot. Maybe this works.
Click to expand...
Click to collapse
This is the result...what to do know?
THX
The devices is detected and the command is executed, but the file does not exist. Make sure that there is a file "prop.local" at /data. If not, you may have a different problem.
Maybe you have an emulator running or Bluestacks installed... Uninstall Bluestacks...
I don't think that this is the case as the device shows up with a serial number in the "adb devices" list.
To be sure it is the correct phone you could compare the serial number shown in the list with the serial number of your phone (you might find this information in settings -> about phone).
Dexxon said:
The devices is detected and the command is executed, but the file does not exist. Make sure that there is a file "prop.local" at /data. If not, you may have a different problem.
Click to expand...
Click to collapse
I don't have in the system/data "prop.local" file...sure....
What is emulator and Bluestacks?
I really don't understand this problem I have...
Could you help me pls?
THX
66aaaa said:
I don't have in the system/data "prop.local" file...sure....
What is emulator and Bluestacks?
I really don't understand this problem I have...
Could you help me pls?
THX
Click to expand...
Click to collapse
An emulator is a program which emulates Android so you can execute Android-Apps on your PC. BlueStacks is an emulator. It may show up as an adb devices, but this is not the case here.
Back to your problem: Are you sure the rooting process worked?
Did you reboot your phone after rooting?
I didn't root my phone under ICS so I don't have any experience with this
no one raised this question to confirm or did this info was provided anywhere
What version of ROM? ICS V10x? JB V20x? User could had used the wrong guide.
Best way out is to do a reflash and retry rooting if all fails.
Dexxon said:
An emulator is a program which emulates Android so you can execute Android-Apps on your PC. BlueStacks is an emulator. It may show up as an adb devices, but this is not the case here.
Back to your problem: Are you sure the rooting process worked?
Did you reboot your phone after rooting?
I didn't root my phone under ICS so I don't have any experience with this
Click to expand...
Click to collapse
I dont't have this Bluestacks emulatur, sure...
I have Superuser working properly on JB V20 stock ROM. The only thing it is very slow sometimes, Thats why I tried to make the process above...
I made the root few month ago...and rebooted many times since than...
Any idea what to do now?
THX
So I have done my homework and read tutorial guide and the nexus all in one beginners guide.
It took me a few hours to be able to get my pc to recognize my computer in fastboot mode using sdk and adp. (Hopefully my terminology is on track but doubtfully so).
So now in the command prompt, i can get the pc to recognize the phone in fastboot mode. Now all I really want to do is (this may sound silly) is to be able to use Air Mirror in airdroid... for now. I do like the stock android feel to this phone as I am new to nexus from the touchwiz **** from samsung.
So can i proceed to the commands of:
fastboot oem unlock
then
fastboot reboot
and then be done with it? Proceed to set up my google account and download my previous apps and contacts yada yada?
TIA
Hamm1701 said:
So I have done my homework and read tutorial guide and the nexus all in one beginners guide.
It took me a few hours to be able to get my pc to recognize my computer in fastboot mode using sdk and adp. (Hopefully my terminology is on track but doubtfully so).
So now in the command prompt, i can get the pc to recognize the phone in fastboot mode. Now all I really want to do is (this may sound silly) is to be able to use Air Mirror in airdroid... for now. I do like the stock android feel to this phone as I am new to nexus from the touchwiz **** from samsung.
So can i proceed to the commands of:
fastboot oem unlock
then
fastboot reboot
and then be done with it? Proceed to set up my google account and download my previous apps and contacts yada yada?
TIA
Click to expand...
Click to collapse
yup, make sure you have all data backed up to a pc, OEM Unlock will wipe your internal storage.
you also need to unlock developer settings, by tapping the build multiple times. Once unlocked you need to go into developer settings and click the check box to allow OEM Unlock
Afterwords if you want to run root, don't fastboot reboot you can use chainfires auto root and root-windows.bat and let it do its thing, then it will reboot and you can setup google account and move your files back over
If you want to flash TWRP, download that .img file and either use flashify to flash it from the google market or use fastboot flash recovery recovery.img
so it sounds like if i want root access, to do things such as air mirror from airdroid I need to flash cf's auto root?
Also in the all in one guide in imlicitly states to not skip the fastboot reboot step. Is this just a if you can do it, then do it step?
And yea, everything is backed up into google drive/cloud/plus and so on. So I am hoping once I am done I can setup my google account and everything should sync back as normal?
BTW thanks for the speedy reply.
Hamm1701 said:
so it sounds like if i want root access, to do things such as air mirror from airdroid I need to flash cf's auto root?
Also in the all in one guide in imlicitly states to not skip the fastboot reboot step. Is this just a if you can do it, then do it step?
And yea, everything is backed up into google drive/cloud/plus and so on. So I am hoping once I am done I can setup my google account and everything should sync back as normal?
BTW thanks for the speedy reply.
Click to expand...
Click to collapse
If you want to go the CF Auto root, you can just run root-windows.bat and it will actually perform the OEM Unlock step and complete that process for you, then it will root the phone and youll be back at the setup screen to enter your google account info, I think this will be the easiest route. It will take care of OEM Unlock, Adding Superuser and the binaries so you can run air mirror and any other root required app.
Yup if everything is backed up then once your login to the google account it will resync your apps and you can login to anything that needs credentials.
should I run fastboot reboot after it does its thing?
Hamm1701 said:
should I run fastboot reboot after it does its thing?
Click to expand...
Click to collapse
no, once you execute the root-windows.bat it will do all the fastboot commands, youll just have to hit a key on the CMD prompt after executing, it gives you a warning that OEM Unlock will wipe data, but you are already aware of that.
Basically, download cf-autoroot for shamu
unzip the zip into the same folder you have ADB installed (platform-tools)
get into adb and boot into bootloader mode or if your phone is in android already, adb reboot-bootloader
then root-windows.bat in the cmd window
and it will walk you through it from that point.
Circaflex said:
no, once you execute the root-windows.bat it will do all the fastboot commands, youll just have to hit a key on the CMD prompt after executing, it gives you a warning that OEM Unlock will wipe data, but you are already aware of that.
Click to expand...
Click to collapse
Cool, thanks for dealin with me. So now for the recovery. I downloaded the specified and latest vs of twrp recovery and I am told to rename it to and typed exactly the following after highlighting the file name: recovery.img
how can i verify that I have indeed named it recovery.img and not recovery.img.img
Hamm1701 said:
Cool, thanks for dealin with me. So now for the recovery. I downloaded the specified and latest vs of twrp recovery and I am told to rename it to and typed exactly the following after highlighting the file name: recovery.img
how can i verify that I have indeed named it recovery.img and not recovery.img.img
Click to expand...
Click to collapse
Do you have file extensions turned on for windows?
Depending on your version of windows it is different, but if they are turned on you would see the extensions for all files, if they are not turned on your files will not be showing extensions. If there is no extension rename the file to recovery and that's all if there are extensions youll see two .img's
Place that in your platform-tools folder as well, once autoroot is all installed and does its thing, set your phone up completely and get all the good stuff going
then power down and boot into boot loader or again use adb reboot-bootloader
then fastboot format cache (this wont harm any data or settings)
very important to then boot into recovery and let it load, then use recovery to reboot phone and youll be back in the android system
OR
download Flashify from the play store and select the .img you downloaded and it will flash the file, it works great
Hamm1701 said:
Cool, thanks for dealin with me. So now for the recovery. I downloaded the specified and latest vs of twrp recovery and I am told to rename it to and typed exactly the following after highlighting the file name: recovery.img
how can i verify that I have indeed named it recovery.img and not recovery.img.img
Click to expand...
Click to collapse
Just manually flash it....
fastboot flash recovery whatever-your-file-is-called.img
No need to rename it.
If you're going to remain rooted, it's a good idea to understand adb and fastboot correctly. Please take the time to read my thread.
http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
@Hamm1701 how did it go
Circaflex said:
@Hamm1701 how did it go
Click to expand...
Click to collapse
Yikes, didnt realize my post didnt go through last night. Well it went very well. I'll admit that when the little android guy was staying on "erasing" for a few to 5 ish min i started to panic a little. I was expecting something like erasing then installing then some other imaginative windows installation words.
But I am now trying to figure out why a certain app is not working 100% as it was before the root and unlock procedure. Ill be researching on learning how to provide feedback developers can use to make any neccasry changes. Do you know of any such threads/posts I can read up on in this regard?
Hamm1701 said:
Yikes, didnt realize my post didnt go through last night. Well it went very well. I'll admit that when the little android guy was staying on "erasing" for a few to 5 ish min i started to panic a little. I was expecting something like erasing then installing then some other imaginative windows installation words.
But I am now trying to figure out why a certain app is not working 100% as it was before the root and unlock procedure. Ill be researching on learning how to provide feedback developers can use to make any neccasry changes. Do you know of any such threads/posts I can read up on in this regard?
Click to expand...
Click to collapse
which app is misbehaving? Basically if you have a problem the easiest solution is to pull a catlog that will detail what your phone was doing and show the error. You can do this through ADB or a free program from playstore is called Catlog.
Circaflex said:
which app is misbehaving? Basically if you have a problem the easiest solution is to pull a catlog that will detail what your phone was doing and show the error. You can do this through ADB or a free program from playstore is called Catlog.
Click to expand...
Click to collapse
It was the manual camera app. So I think i figure out how to view and store catlogs. Going to post my question about it over in dev Q&A.
Is there a way to reboot this thing without root. All the apps seen need root. Why isn't it available with the power button anyway? Am I missing something?
PolishPoet said:
Is there a way to reboot this thing without root. All the apps seen need root. Why isn't it available with the power button anyway? Am I missing something?
Click to expand...
Click to collapse
Root access is needed but the only way I know how to do it without root is with a computer via usb connection; install minimal adb and fastboot by shimp 208 and run through command prompt. Make sure you have updated motorola drivers and connect your phone, run command prompt and change directory to wherever you have adb installed; type "adb reboot" (without quotes, you may include -bootloader or -recovery to go into either of those); to install, go here.
http://forum.xda-developers.com/showthread.php?t=2317790
I've just moved to this phone from my S3, and it seems I have been spoiled by CM through the years, as the first thing I noticed about the OS was all the features I frequently used -- including a "reboot" menu item, which I wouldn't have considered a "feature" until now. The best part: when I first turned the thing on, it tried over and over to activate itself but failed, with the error message telling me it would try again the next time I reboot the phone. And how would you suggest I perform that reboot? This one I'm sure is trivial to most by now who have been using this phone for a while, but it just blows my mind.
Is shrimp's adb fastboot accepted as a recommended and reasonable workaround for this?
BTW, what other "features" am I going to notice are missing soon (and any recommended apps/methods to replace them)?
Thanks.
Doesn't just holding the power button a few seconds "reboot" the phone...or is that not really a reboot?
wjdunn3 said:
Doesn't just holding the power button a few seconds "reboot" the phone...or is that not really a reboot?
Click to expand...
Click to collapse
More of a hard power-off and back on than a clean reboot, and you would lose state and cached data, which to me isn't worth the risk.