My ota zip update through CWM is failing on the 'debuggerd' file from /system/bin. If someone could pm me with the original 'debuggerd' file from 4.2.2 I would be very grateful. I think the Stickmount app changes or replaces the file so it won't pass the authentication check of the system files. Please don't send me the debuggerd file if you have installed Stickmount. Much thanks in advance. I'm trying to help another forum member with the same problem.
me too, my bak file was from 4.2.1 which has sha1sum of df2e705da097e4d535b4f4d98fab3bd76601e76c
I think 4.3 wants one with a2323a0c8e245e3879d6b8beff6b2c4802045271
o8x8 said:
me too, my bak file was from 4.2.1 which has sha1sum of df2e705da097e4d535b4f4d98fab3bd76601e76c
I think 4.3 wants one with a2323a0c8e245e3879d6b8beff6b2c4802045271
Click to expand...
Click to collapse
I'm having the same problem. (Groid is helping me)
My OTA update failed because of the same issue (/system/bin/debuggerd), once I copied from stock 4.2.2, and try, it failed againm this time was with /system/bin/gzip)
so, thought this was going to be pain, what I did was copied /system/bin/ from stock 4.2.2 files to my N7's /system/bin/ folder (except SuperSU bin file).
once I did, I re-tried OTA update, it worked.
Yes, yes, yes, thank you tiggggr. I downloaded the file you attached to my pc, renamed to just 'debuggerd', copied to my N7, copied file to /system/bin with Root Explorer, booted into CWM recovery, installed zip. After installing, said 'NO' to question about recovery and said 'Yes' to try to keep root. Booting up now. Thank you again. I'll let you know about root after 'Android is updating' finishes.
So, I didn't keep root, as expected, but everything else seems fine. On first boot I got a message like 'process Acore has stopped' or something like that, but it booted up. I waited a couple of minutes and restarted and did not see that message again. Now to check Chainfire's posts about reflashing SuperSu to get root back. If you had the debuggerd error, replacing the file with the one in tiggggr's post did the trick for me.
Screenshot:
Regaining root was more of a pain than I thought. I tried flashing Chainfire's SuperSu 1.43 per his G+ post, but didn't have a recovery to flash it with. Finally used Wugfresh Nexus Root Toolkit, chose Android *.*.* Any, plugged into a back port with the original cable, and chose the Root button with custom recovery checked. I was pretty sure my drivers were all good, so I didn't even install them again first. I wasn't paying attention on the custom recovery part where it said TWRP was selected instead of CWM (you can change that.) I followed the rest of the directions, then booted into TWRP and flashed the SuperSu 1.43 zip from Chainfire. After rebooting, I have root and TWRP recovery. Tested with Root Explorer and Titanium Backup for root and all is well. Whew! Sorry for making 4 straight posts, but I know some other members were in the same circumstances as me.
How do I make a recovery to avoid the issues you ran into regaining root
Sent from my Nexus 7 using Tapatalk 2
Groid any tips on this? I'll try replacing the debuggerd file, but would like it to be as simple as possible to regain root after the update.
Link to Wugfresh Nexus Root Toolkit
http://www.wugfresh.com/nrt/
Link to Chainfire's SuperSu 1.43
http://plus.google.com/+Chainfire/posts/Jkuu84odnx6
Here is what I did and it wasn't really too difficult. Put Chainfire's zip in the root of your sdcard with the OTA zip you have there already. After replacing the 'debuggerd' file I flashed the update through CWM. It worked fine, but I lost root and CWM. Downloaded the Wugfresh NRT and installed it. As stated earlier, I followed the guide in the link and set the device as Android *.*.* and hit the root button with install recovery checked and the original usb cable plugged into a good port. It rooted and installed TWRP recovery and that was fine. After booting up, go into TWRP recovery and flash the SuperSu zip. After booting up again, you should have root and TWRP recovery.
Since you are unlocked and rooted, if your drivers are good, just go to the Root button. You shouldn't have to unlock the bootloader and wipe everything. My update preserved all my programs and data. Follow the guides and watch the videos. My N7 is running great.
tiggggr said:
Glad to hear it helped! For me it was pretty straight forward. I had rooted stock ROM, so flashed CWM, applied zip from CWM, booted, noticed I had lost root, downloaded SuperSu 1.43 zip, booted into CWM, applied zip, booted and was up to 4.3 with root.
Click to expand...
Click to collapse
That's great you didn't lose recovery. I'm not sure why I lost CWM, but I don't think I had updated Rom Manager and that may be why. At least it wasn't hard getting recovery back on with the Wugfresh NRT. TWRP seems like a good recovery, so I will just stick with it.
Mine failed again
I downloaded and replaced the deguggerd file with the one tigggger posted, but still can't get updated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Could anyone help?
coollyjordan said:
I downloaded and replaced the deguggerd file with the one tigggger posted, but still can't get updated.
Could anyone help?
Click to expand...
Click to collapse
Did you make sure to rename the file by removing the .rename.zip? The file you copied to /system/bin should be named simply debuggerd and you should not have tried to unzip it, if you tried. It should have replaced the debuggerd file there unless you renamed the original one first. Since you received the same error, you could try copying it to /system/bin again. You must be rooted to copy into that folder. Are you using a custom recovery? You are installing the OTA zip file, not the official OTA that ends in .tgz right?
Groid said:
Did you make sure to rename the file by removing the .rename.zip? The file you copied to /system/bin should be named simply debuggerd and you should not have tried to unzip it, if you tried. It should have replaced the debuggerd file there unless you renamed the original one first. Since you received the same error, you could try copying it to /system/bin again. You must be rooted to copy into that folder. Are you using a custom recovery? You are installing the OTA zip file, not the official OTA that ends in .tgz right?
Click to expand...
Click to collapse
Yes, I'm pretty sure I renamed the file to debuggerd, didn't unzip it.
I placed the debuggerd file to /system/bin with es file explorer.
I'm using the stock recovery.
I'm not sure what you said about the official OTA ends in .tgz, I just went to settings-about tablet-system updates and pressed the check now button to get OTA.
Groid said:
Link to Wugfresh Nexus Root Toolkit
http://www.wugfresh.com/nrt/
Link to Chainfire's SuperSu 1.43
http://plus.google.com/+Chainfire/posts/Jkuu84odnx6
Here is what I did and it wasn't really too difficult. Put Chainfire's zip in the root of your sdcard with the OTA zip you have there already. After replacing the 'debuggerd' file I flashed the update through CWM. It worked fine, but I lost root and CWM. Downloaded the Wugfresh NRT and installed it. As stated earlier, I followed the guide in the link and set the device as Android *.*.* and hit the root button with install recovery checked and the original usb cable plugged into a good port. It rooted and installed TWRP recovery and that was fine. After booting up, go into TWRP recovery and flash the SuperSu zip. After booting up again, you should have root and TWRP recovery.
Since you are unlocked and rooted, if your drivers are good, just go to the Root button. You shouldn't have to unlock the bootloader and wipe everything. My update preserved all my programs and data. Follow the guides and watch the videos. My N7 is running great.
Click to expand...
Click to collapse
Can root be regained by using [Google Nexus 7 TOOLKIT V5.0.0] - http://forum.xda-developers.com/showthread.php?t=1809195
WUG's toolkit acts weird on my laptop and doesn't seem to run right.
coollyjordan said:
Yes, I'm pretty sure I renamed the file to debuggerd, didn't unzip it.
I placed the debuggerd file to /system/bin with es file explorer.
I'm using the stock recovery.
I'm not sure what you said about the official OTA ends in .tgz, I just went to settings-about tablet-system updates and pressed the check now button to get OTA.
Click to expand...
Click to collapse
Sorry to be confusing. I have a custom recovery (TWRP) and with a custom recovery, the update can be done with the OTA update that was repackaged as a .zip file. Then in recovery, I chose to Install a zip and chose the OTA update zip file. Since you have the stock recovery, and you got the update started, you must have been using the correct update file. Since you got the same error on debuggerd, I wonder if you didn't get it copied correctly into /system/bin. Can you compare file dates or sizes to make sure you got the right one? That debuggerd file did fix the update error for me and for a couple of other people I heard from. I would try again after confirming the debuggerd file. You could check permissions also, but I didn't have to change them. RW, R,R. (just compare to permissions on other files there).
Foxman2k said:
Can root be regained by using [Google Nexus 7 TOOLKIT V5.0.0] - http://forum.xda-developers.com/showthread.php?t=1809195
WUG's toolkit acts weird on my laptop and doesn't seem to run right.
Click to expand...
Click to collapse
Do you still have your custom recovery? If so, you should be able to flash the SuperSu zip and regain root. I lost recovery and the Wugfresh toolkit worked great for me to choose root and install custom recovery. If you try to install the drivers from the toolkit, I think it gives you a way to see if the correct drivers are installed, and install them if necessary. You could try that. Using the original N7 cable is important. I don't know of another way to get root and custom recovery, but there are many in the forum that may be able to help you with Fastboot commands or the ADB push method. I have used those, but only following specific instructions for a specific purpose. In any case, if the debuggerd file works to install the update, you will be able to regain root.
Groid said:
Do you still have your custom recovery? If so, you should be able to flash the SuperSu zip and regain root. I lost recovery and the Wugfresh toolkit worked great for me to choose root and install custom recovery. If you try to install the drivers from the toolkit, I think it gives you a way to see if the correct drivers are installed, and install them if necessary. You could try that. Using the original N7 cable is important. I don't know of another way to get root and custom recovery, but there are many in the forum that may be able to help you with Fastboot commands or the ADB push method. I have used those, but only following specific instructions for a specific purpose. In any case, if the debuggerd file works to install the update, you will be able to regain root.
Click to expand...
Click to collapse
Groid, all is well and thanks for the help! I replace the debuggerd file and then ran the OTA install via ClockWorkMod. This went fine now and the Nexus 7 updated to 4.3
I then reboot and did still have the custom recovery, flashed the SuperSU file and back in business! Thanks again for the help!
Thank U! However I used Nexus 7 Toolkit, reflashed the stock 4.2.2, then got an OTA to 4.3. Though I lost my root and some local data, I've got 4.3!
Anyhow, thank you for helping me out!
Groid said:
Sorry to be confusing. I have a custom recovery (TWRP) and with a custom recovery, the update can be done with the OTA update that was repackaged as a .zip file. Then in recovery, I chose to Install a zip and chose the OTA update zip file. Since you have the stock recovery, and you got the update started, you must have been using the correct update file. Since you got the same error on debuggerd, I wonder if you didn't get it copied correctly into /system/bin. Can you compare file dates or sizes to make sure you got the right one? That debuggerd file did fix the update error for me and for a couple of other people I heard from. I would try again after confirming the debuggerd file. You could check permissions also, but I didn't have to change them. RW, R,R. (just compare to permissions on other files there).
Click to expand...
Click to collapse
Related
this is how i did it anyways. i had to flash the boot.img and update via stock recovery to get the ota to flash. but then no root!
so heres how i got it back:
download the superboot/paulobrien method (http://forum.xda-developers.com/showthread.php?t=882333).
boot phone to fastboot.
Code:
fastboot boot boot.superboot.img
let phone boot, open terminal, su, just to check.
reboot phone.
rooted and ota'd now!
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
The method I used was:
1. Boot into fastboot.
2.
Code:
fastboot flash recovery recovery-clockwork-3.0.0.0-crespo.img
3. Reboot from fastboot directly into recovery (not doing so will cause android to replace CWR).
4. Mount USB, copy su-2.3.6.1-ef-signed.zip to the /sdcard via windows/linux
5. Mount /system
6. Install update from zip (browse to were you put su-2.3.6.1-ef-signed.zip).
7. Install it, and reboot.
8. open root explorer, and rename /etc/install-recovery.sh to install-recovery.sh.old
9. open ROM Manager, reflash CWR.
now you are all done, rooted, w/ CWR
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Luxferro said:
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
Click to expand...
Click to collapse
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
im using stock recovery.
I'm rooted on 2.3.1 but I lose clockwork recovery when I reboot an gota reflash it using rom manager. Anyone having this problem
k0mpresd said:
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
Click to expand...
Click to collapse
Sure it is. But on Android bootup, a script is running somewhere to replace it with stock recovery. They did this on Droid_1 after the first or second update (that's my only other android phone... so my android experience is limited).
edit: I just found the script. It's /etc/install-recovery.sh .... just renamed my to install-recovery.sh.old. gonna reflash CWR and test it now.
edit2: yep, works great now. CWR, and retained my 2.3.1 boot.img
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
chris6278 said:
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
Click to expand...
Click to collapse
No, it's a safety mechanism so you can't lose recovery... It has nothing to do with clockworkmod. Someone can make a root script or app that disables it easily. Or people can just do it themselves manually.
edit: actually, all that needs to be done is add some code to the update script inside su-2.3.6.1-ef-signed.zip so when it installs the update, it renames install-recovery.sh
distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
If u dont mind can u please provide the instructions on how to do it manually. Id really appreciate it. Sorry im a noob lol
Where in root explorer do i need to rename
Where in root explorer do i rename it
plmiller0905 said:
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
Click to expand...
Click to collapse
chmod needs to be done at a # prompt.
chris6278 said:
Where in root explorer do i rename it
Click to expand...
Click to collapse
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Is it just me or does adb remount no longer work?
If I use the old koush rootboot.img it works, but no wifi, if I use the stock boot.img, I get no wifi but am able to remount.
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
chris6278 said:
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
Click to expand...
Click to collapse
do you have root explorer? if not, it's just a file explorer that has root access. by default when you open it you are at /
you need to scroll down to /etc
go in that folder and find the install-recovery.sh
look up top for the button to turn it from read-only to read-write, click it
go back to the file long press it, and then choose rename.
Luxferro said:
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Click to expand...
Click to collapse
Thanks..I already rerooted but thanks anways
I got root explorer an followed ur directions an now everything works great. Thanx for ur help an sorry for being a pain lol
**Disclaimer** If you don't understand what follows, don't attempt this. I'm not responsible for you softbricking your device,
This is a quick guide for how to install the new android without losing anything. You'll need fastboot for this. Also, before doing this, be sure to download the supersu cwm update zip, and have it on your sdcard. Make sure you also already have a custom recovery installed (I did twrp, but i'm sure cwm will work just as well). I would also suggest having a backup done, through titanium backup and through recovery, just incase.
First, download the factory images for the n7 from google's website. Decompress them (if you're in windows, you'll need winrar or something similar.) After you decompress the archive, there'll be another one inside (image-nakasi-jop40c.zip), decompress this one as well. Under here, you'll see the .img files for all the partitions. For now, go up one directory. You'll also see here bootloader-grouper-4.13.img. Once you have all this, reboot into the bootloader.
Once you're in the bootloader, you can update the bootloader to the new version (this step isn't needed, but I did it anyways). Plug into your pc, and type fastboot devices. Make sure it's not blank. If it is, you have to update drivers. If you can see the device, open up a command prompt, and cd to the directory that has the bootloader-grouper file. Type the following:
fastboot flash bootloader-grouper-4.13.img
then, after it's done, type:
fastboot reboot-bootloader
Now, you'll be booted back into the bootloader, it'll say 4.13. On to the rom.
cd into the folder image-nakasi-jop40c (make sure you see the files system.img and boot.img before you continue. If you don't see them, the next steps will do nothing but erase your kernel and system parition.)
now, you see the image files. Type the following (still in the bootloader)
fastboot erase system
fastboot flash system system.img
wait until it completes, then type:
fastboot erase boot
fastboot flash boot boot.img
Once this is done, hit the volume up on the device until it shows recovery mode on the top. When it does, push the power key and you'll boot into your recovery (shouldn't be touched.) Inside here, flash the supersu cwm zip file, which'll flash the superuser binary, and supersu. Once this is done, do a factory reset (removing your data and cache.) Boot into the rom.
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
My first boot got stuck for some reason. if it happens to you, just hold the power button and hard reboot. (I did this on 2 devices, it only happened to one of them, so I figured I'd give you all warning.)
Links:
SuperSu binary: https://docs.google.com/open?id=0B7a8xHNJlpgTR0ZkR1pWZWR2VzA
Google Factory Images: https://developers.google.com/android/nexus/images
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Thanks for this.. Apparently you found out too a clean 4.2 isn't rootable via typical methods.
That SuperSU package did the trick. I have to remember to keep a SuperSU binary on hand for these kinds of situations that SuperUser fails..
jefferson9 said:
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Click to expand...
Click to collapse
Yes. If you do it though cwm, you're not using any exploits, you're just inserting the superuser binary and supersu.apk into the proper places on the rom. On any nexus device, any rom, this will root it.
mstrk242 said:
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place.
Click to expand...
Click to collapse
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
tehSmoogs said:
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
Click to expand...
Click to collapse
Exactly.
If everything goes right we should have an AOSP prerooted build in about *looks at watch* 20 minutes.... Unless there is a compile error or SU error. *laff*
Back to watching the scrolling terminal window
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
kwhee07 said:
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
Click to expand...
Click to collapse
I did this all on linux, just kind of adapted the guide for windows. I figured all the linux users would understand how to do it on their own. Glad to know it's the same for mac as well.
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
rootbrain said:
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
Click to expand...
Click to collapse
Settings - about tablet - build number
push it a few times and it will enable dev options
You have .bat file in the package.
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...gned-nakasi-JOP40C-from-JZO54K.094f6629.zipia
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Here is my method:
1. Download official 4.1.2 from http://forum.xda-developers.com/showthread.php?t=1929270 and 4.2 OTA image from http://forum.xda-developers.com/showthread.php?t=1989188
2. Boot into CWM (i have CWM touch installed)
3. Clear data and install 4.1.2, don't forget to turn on root in the installer
4. reboot check that root is fully working
5. reboot into recovery install 4.2
6. before reboot CWM will ask to disable recovery flash and protect root. Ansver yes to both questions
I'm confused, it says if you are already on a custom rom, just flash as usual.
What makes this different?
I was on stock ROM rooted with some system modifications, and this wwadd the only way I could get the update working...
Sent from my Nexus 7 using xda app-developers app
mstrk242 said:
For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
Click to expand...
Click to collapse
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Ill have to wait until a rooted rom is created, I have no comp.
Sent from my Nexus 7 using XDA Premium HD app
can I install image-nakasi-jop40c.zip directly without upgrading bootloader?
Zuk. said:
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Click to expand...
Click to collapse
Not advisable to move this folder - if it got moved to a new location by the o/s then there's probably a good reason why - maybe like 4.2 introducing multiple users
Each user appears to get their own "home" directory created in /mnt/shell/emulated/
Default user dir is "0"
Second user dir is "10"
Each contain the standard dir's from 4.1 and earlier.
Travelawyer said:
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Click to expand...
Click to collapse
You had two extra characters at the end of your link, but I fixed it above and it's good to go for others in the future. Just flashed it in TWRP, it didn't ask if I wanted to maintain root, hit reboot when it was complete and lost root, so it doesn't work for everyone - good news is that all my data remained intact without having to resort to advanced restoring my data from a backup....
When I tried the SuperSU binary root flash trick, I finally got root back. But don't think it's as easy to get to recovery! I had to obtain the TWRP Recovery one more time since it wiped it and put in place a recovery that did absolutely nothing but reboot the device after a few minutes, so you'll have to
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
to get TWRP back.... Hope that helped everyone!
Hello,
I've unlocked the bootloader on my One, then proceeded to install supersu via zip through clockworkmod recovery.
I rebooted, attempted to gain root access, and was unable to.
I then rebooted into clockworkmod recovery and attempted to install superuser from this thread, rebooted and was unable to gain root. I then installed supersu from the same thread, and was unable to gain root.
Lastly, I attempted to wipe the cache partition and dalvik cache in effort, and still I am not able to gain root.
I'm unsure exactly what to do from here on out, as the process is truly very simple, but just not working.
Should I flash an official recovery and start over?
Thanks,
Matt
Have you opened the su app and updated the binaries?
I used twrp recovery a few days ago when I rooted. try to flash latest version of twrp through adb and wipe, clear cache,and retry.
If you still have trouble, check out wwjoshdew on youtube. I followed his instructions and rooted/unlocked with no hiccups.
BD619 said:
Have you opened the su app and updated the binaries?
Click to expand...
Click to collapse
Thanks for replying quickly.
The state I'm in now is:
- The SuperSu apk is gone.
- Superuser is installed.
- Root Checker, Helium, ES File Explorer's "root explorer" report no root
- Shark reports root (aka starts).
- superuser info reports `su` 3.2.18
- Used ES File Explorer to verify presence of `/system/bin/su`
Any idea on what could be wrong?
Thanks again,
Matt
How about another try on TWRP 2.6.3.0 recovery?
Sure, I will try this, Originally I tried TWRP, but couldn't access my internal storage (don't know why). Attempted sideload and failed, so I install clockwork and was able to install superuser.zip from /sdcard/.
Thanks!
Grabbed TWRP 2.3.6.0 from: http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.3.0-m7wls.img
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
> REBOOT BOOTLOADER
> BOOTLOADER
> RECOVERY
I then located the SuperSu zip and installed. Now I receive "There is no SU binary installed and SuperSu cannot install it. This is a problem!"
Rebooted into recovery and installed SuperUser.
Rebooted the system and attempted to access SuperUser, and it works. Verifies the presence of `/system/bin/su`.
Accessing helium and I don't have root.
So what do I do from here?
(sorry didn't brick my phone)
branded said:
Grabbed TWRP 2.3.6.0 from: http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.3.0-m7wls.img
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
> REBOOT BOOTLOADER
> BOOTLOADER
> RECOVERY
I then located the SuperSu zip and installed. Now I receive "There is no SU binary installed and SuperSu cannot install it. This is a problem!"
Rebooted into recovery and installed SuperUser.
Rebooted the system and attempted to access SuperUser, and it works. Verifies the presence of `/system/bin/su`.
Accessing helium and I don't have root.
So what do I do from here?
(sorry didn't brick my phone)
Click to expand...
Click to collapse
Get the latest version of SuperSU from here
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
I would suggest using it as it is updated more often then superuser as far as I know
Thanks,
I saved the file to my internal storage, restarted in TWRP, installed and erased the caches.
After rebooting... it works! You're the man!
I just got the One and just performed the OTA update the other day, so I am on 4.3. I bet this is what the "problem" was! So the updated SuperSU must be compatible with 4.3.
Thanks again!
Matt
Glad you got it enjoy
So I was having the same problem. I got TWRP recovery installed. I copied the SuperSU zip file to the root, but now when I try to install the SuperSU zip file, I don't see it!
dtracycar said:
So I was having the same problem. I got TWRP recovery installed. I copied the SuperSU zip file to the root, but now when I try to install the SuperSU zip file, I don't see it!
Click to expand...
Click to collapse
... check the extension of the file you downloaded. Recoveries shouldnt oversee zip files ...
Devilish_Angel said:
... check the extension of the file you downloaded. Recoveries shouldnt oversee zip files ...
Click to expand...
Click to collapse
Oh if only it were that easy. It is definitely a zip file with the proper extension. Any other ideas?
dtracycar said:
Oh if only it were that easy. It is definitely a zip file with the proper extension. Any other ideas?
Click to expand...
Click to collapse
... Does it show rest of the files ...
Devilish_Angel said:
... Does it show rest of the files ...
Click to expand...
Click to collapse
It doesn't. I'm baffled, I don't even know what its showing. Attached is a screen shot of the sdcard directory. When I navigate to the sdcard in recovery, it doesn't show anything like that. It has 6 folders, audio, GPU, mms, musicchannel, TWRP, and zchgd. When I browse my phone folders, I can't find any of those! OMG help.
dtracycar said:
It doesn't. I'm baffled, I don't even know what its showing. Attached is a screen shot of the sdcard directory. When I navigate to the sdcard in recovery, it doesn't show anything like that. It has 6 folders, audio, GPU, mms, musicchannel, TWRP, and zchgd. When I browse my phone folders, I can't find any of those! OMG help.
Click to expand...
Click to collapse
... you might want to install TWRP 2.6.3.0.
Get it from here http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.3.0-m7wls.img
this is the .img file so you ought to flash it from fastboot ...
branded said:
Thanks,
I saved the file to my internal storage, restarted in TWRP, installed and erased the caches.
After rebooting... it works! You're the man!
I just got the One and just performed the OTA update the other day, so I am on 4.3. I bet this is what the "problem" was! So the updated SuperSU must be compatible with 4.3.
Thanks again!
Matt
Click to expand...
Click to collapse
4.3 was your problem. You needed to use a different SuperSU and this is the case with anyone else who wants to root 4.3 or 4.4. I believe I used SuperSU v1.65. Glad you got it working!
mHamers since
Devilish_Angel said:
... you might want to install TWRP 2.6.3.0.
Ok, we're making progress! I installed the new TWRP recovery. Then I was able to find the SU zip file and flash it from there. All signs pointed to it working fine! There were no errors that I could see. Rebooted. Tried to open Titanium Backup and it hangs up with a message saying Asking for root rights... I do not find SuperSU anywhere in my apps tray. You've been super helpful so far! Now what?
Click to expand...
Click to collapse
dtracycar said:
Devilish_Angel said:
... you might want to install TWRP 2.6.3.0.
Ok, we're making progress! I installed the new TWRP recovery. Then I was able to find the SU zip file and flash it from there. All signs pointed to it working fine! There were no errors that I could see. Rebooted. Tried to open Titanium Backup and it hangs up with a message saying Asking for root rights... I do not find SuperSU anywhere in my apps tray. You've been super helpful so far! Now what?
Click to expand...
Click to collapse
... might be a bad SU file. download from here and flash from recovery
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip ...
Click to expand...
Click to collapse
Devilish_Angel said:
dtracycar said:
... might be a bad SU file. download from here and flash from recovery
Well, I finally got it to work! Thank you for all your help! Now if I could only get wifi hotspot or foxfi to work. Thats the whole reason I rooted in the first place!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I received a notification to download and install the OTA on my GSM Dev Edition Moto X. I'm rooted with stock 4.4.2 installed and xposed. I disabled xposed. Then tried to install the firmware. My phone rebooted into recovery (TWRP 2.6.3.1) and then the install failed. I look at the terminal and I saw the assert failed that was checking the model type (it was checking some values in the build.prop for "ghost") I checked the build prop, and the values were correct. I can't figure out why it's failing.
[Q] Would it be safe to download the zip currently available, extract the contents, delete the assert, and re-archive, and then flash this one instead?
(Follow-up question) If this is safe, I saw on 7zip there are many options to re-zip a file. At first I chose no compression, but then I tried normal compression and that ended up with a zip that was the same size as the original. Should I just follow a guide on how to create a flashable file?
rsromano said:
I received a notification to download and install the OTA on my GSM Dev Edition Moto X. I'm rooted with stock 4.4.2 installed and xposed. I disabled xposed. Then tried to install the firmware. My phone rebooted into recovery (TWRP 2.6.3.1) and then the install failed. I look at the terminal and I saw the assert failed that was checking the model type (it was checking some values in the build.prop for "ghost") I checked the build prop, and the values were correct. I can't figure out why it's failing.
[Q] Would it be safe to download the zip currently available, extract the contents, delete the assert, and re-archive, and then flash this one instead?
(Follow-up question) If this is safe, I saw on 7zip there are many options to re-zip a file. At first I chose no compression, but then I tried normal compression and that ended up with a zip that was the same size as the original. Should I just follow a guide on how to create a flashable file?
Click to expand...
Click to collapse
Your problem is highlighted in red. All of the guides tell you that you have to flash the stock recovery back in order to accept the OTA. Download the official SBF for your carrier here: http://sbf.droid-developers.org/phone.php?device=0
Now extract the file. You only need 1 file -- recovery.img
Put it in the same folder that has "mfastboot".
Boot the phone into bootloader mode, then type:
mfastboot flash recovery recovery.img
Now you -should- be able to accept the OTA assuming you haven't made further modifications to the system.
When you have successfully updated, you can now flash TWRP back.
Good Luck
I tried downloading stock, but through a different method, and still ran into an error. I will try your method tonight.
Do you have a link to a guide? I was looking and couldn't find one this weekend.
Sent from my XT1053 using Tapatalk
http://mark.cdmaforums.com/MotoX-OTA.html pretty much covers what you need to take an OTA on the X (and most Motos). The same info is scatter throughout the thread talking about the GSM 4.4.3 update.
to flash stock recovery, see the Requirements section, then Option 2 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Before you flash stock recovery, visit this post -> http://forum.xda-developers.com/showpost.php?p=24267797&postcount=1 and download the attached Xposed-Disabler-Recovery.zip, and place it on the emulated SD Card of your X.
Boot into Recovery and install update from SD. Pick the Xposed-Disabler-Recovery.zip, then the flash stock recovery and take the OTA update.
Have done the root process and gotten to the point where I open TWRP and supposed to flash the SuperSu zip to complete the root process... but it's not showing in the file system of TWRP on the phone. But if I connect to my PC and copy the file to the phone root directory- it says it is already installed (I installed it in an earlier step as instructed).
I also have the no-verity-opt-encrypt-5.1.zip and aptX.zip file copied but they are also not showing in TWRP.
Can't figure it out... looking for some guidance... thank you..