The micro USB charging port on my wife's D4 just died. I received the warranty replacement from VZW. I need to return the old D4 to stock.
Battery is dead and can't charge via USB. I bought the D4 inductive charge door from VZW, and will buy a powermat to charge it, so charging it should not be a problem.
I did a search on this, and found various threads for dead USB ports, but not a solution for what I need.
QUESTION: How can I unroot, return to stock ROM and recovery, and re-lock the bootloader without USB access? I know there are various apps I can use to transfer files to the device via wifi, but is there a ZIP file I can flash with Clockworkmod Recovery to re-load stock ROM, unroot, re-lock bootloader, and re-load stock recovery?
SoCalNewb said:
The micro USB charging port on my wife's D4 just died. I received the warranty replacement from VZW. I need to return the old D4 to stock.
Battery is dead and can't charge via USB. I bought the D4 inductive charge door from VZW, and will buy a powermat to charge it, so charging it should not be a problem.
I did a search on this, and found various threads for dead USB ports, but not a solution for what I need.
QUESTION: How can I unroot, return to stock ROM and recovery, and re-lock the bootloader without USB access? I know there are various apps I can use to transfer files to the device via wifi, but is there a ZIP file I can flash with Clockworkmod Recovery to re-load stock ROM, unroot, re-lock bootloader, and re-load stock recovery?
Click to expand...
Click to collapse
Assuming you are successful in getting your D4 charged, following these steps SHOULD get you back to a stock unrooted phone without the use of the USB port. Make sure you have backup up anything you don't want to lose before you do this.
1. Go in to safestrap recovery, delete any ROM slots, and boot back into your stock ROM.
2. Open up the safestrap app and select uninstall recovery.
3. Uninstall the safestrap app.
4. While you are still rooted, use a file explorer and delete any incriminating leftover files (nandroid backups, etc.)
5. Install and run Ginger Unroot from the Play Store (Full disclosure: I have never actually used this app). Costs 99 cents.
6. After Ginger Unroot does it's thing, check to make sure Superuser is not longer installed on the phone.
7. Boot in to stock recovery and perform a factory reset.
Honestly, I would probably just skip step 6 and manually delete superuser. It's pretty unlikely they will really be looking to see if you rooted it since you're returning it for a hardware issue. Also, according to another thread on XDA, rooting the D4 triggers some sort of check that cannot be undone. If true, unrooting your phone won't help.
Good luck!
kwyrt said:
It's pretty unlikely they will really be looking to see if you rooted it since you're returning it for a hardware issue.
Good luck!
Click to expand...
Click to collapse
Do you really think so? As since ics I have not rooted my for as I have bad luck with the ear piece speaker in my past d4...
Sent from my DROID4 using xda app-developers app
dbreezy187 said:
Do you really think so? As since ics I have not rooted my for as I have bad luck with the ear piece speaker in my past d4...
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Just my personal opinion so take it for what it's worth. I've never actually had to return a phone myself. But, I have yet to hear of someone being turned down for a warranty repair/return because their phone was rooted. And I do know someone personally that returned their D4 under warranty for a faulty screen that was rooted and running a custom ROM and they never said a thing. I'm guessing the only reason they would look into it being rooted was if you soft bricked it, wouldn't boot, something like that where they suspect it was something you did to cause it.
Sent from my D4 - AOKP
kwyrt said:
Assuming you are successful in getting your D4 charged, following these steps SHOULD get you back to a stock unrooted phone without the use of the USB port. Make sure you have backup up anything you don't want to lose before you do this.
1. Go in to safestrap recovery, delete any ROM slots, and boot back into your stock ROM.
2. Open up the safestrap app and select uninstall recovery.
3. Uninstall the safestrap app.
4. While you are still rooted, use a file explorer and delete any incriminating leftover files (nandroid backups, etc.)
5. Install and run Ginger Unroot from the Play Store (Full disclosure: I have never actually used this app). Costs 99 cents.
6. After Ginger Unroot does it's thing, check to make sure Superuser is not longer installed on the phone.
7. Boot in to stock recovery and perform a factory reset.
Honestly, I would probably just skip step 6 and manually delete superuser. It's pretty unlikely they will really be looking to see if you rooted it since you're returning it for a hardware issue. Also, according to another thread on XDA, rooting the D4 triggers some sort of check that cannot be undone. If true, unrooting your phone won't help.
Good luck!
Click to expand...
Click to collapse
kwyrt - THANK YOU for your help! I am heading out later today to get a charging mat to use with the inductive charger, then I will try the steps you outlined above.:laugh:
Yes thank you putting it that way I may finally get mine rooted again...
Sent from my DROID4 using xda app-developers app
Update: I have not been able to test the above directions yet because no local stores seem to carry the inductive charging mat (I've tried Verizon Wireless, Sprint, Radio Shack, and Best Buy).
I will buy the charging mat online, then update thread with outcome once it arrives.
Update 2: the PowerMat that I ordered on Amazon arrived today. Unfortunately it is not compatible with the Droid 4 inductive charging case (Droid 4 requires QI, PowerMat is not QI).
I ordered a QI charging mat, and it arrives Monday. I'll report progress then.
kwyrt said:
Assuming you are successful in getting your D4 charged, following these steps SHOULD get you back to a stock unrooted phone without the use of the USB port. Make sure you have backup up anything you don't want to lose before you do this.
1. Go in to safestrap recovery, delete any ROM slots, and boot back into your stock ROM.
2. Open up the safestrap app and select uninstall recovery.
3. Uninstall the safestrap app.
4. While you are still rooted, use a file explorer and delete any incriminating leftover files (nandroid backups, etc.)
5. Install and run Ginger Unroot from the Play Store (Full disclosure: I have never actually used this app). Costs 99 cents.
6. After Ginger Unroot does it's thing, check to make sure Superuser is not longer installed on the phone.
7. Boot in to stock recovery and perform a factory reset.
Honestly, I would probably just skip step 6 and manually delete superuser. It's pretty unlikely they will really be looking to see if you rooted it since you're returning it for a hardware issue. Also, according to another thread on XDA, rooting the D4 triggers some sort of check that cannot be undone. If true, unrooting your phone won't help.
Good luck!
Click to expand...
Click to collapse
So the inductive charger arrived last Monday. It worked! Device is all charged up despite the non-functional USB port.
Rooted device when it was on GB, then the OTA update brought it to ICS (which removed root).
Here's where I'm at:
- no root (but superuser still installed, and can't be removed)
- stock recovery
- broken USB port
Here's what I've tried:
- Ginger Unroot did not work
- Can't remove superuser from Google Play
- Can't remove superuser from settings/apps
- Can't remove superuser with Root Explorer (no longer have root, so I can't acquire root privileges)
- Can't remove superuser with Titanium Backup (no longer have root, so I can't acquire root privileges)
Given lack of USB, and lack of root, any ideas how I can remove Superuser and restore to stock?
SoCalNewb said:
So the inductive charger arrived last Monday. It worked! Device is all charged up despite the non-functional USB port.
Rooted device when it was on GB, then the OTA update brought it to ICS (which removed root).
Here's where I'm at:
- no root (but superuser still installed, and can't be removed)
- stock recovery
- broken USB port
Here's what I've tried:
- Ginger Unroot did not work
- Can't remove superuser from Google Play
- Can't remove superuser from settings/apps
- Can't remove superuser with Root Explorer (no longer have root, so I can't acquire root privileges)
- Can't remove superuser with Titanium Backup (no longer have root, so I can't acquire root privileges)
Given lack of USB, and lack of root, any ideas how I can remove Superuser and restore to stock?
Click to expand...
Click to collapse
Like previously stated, its prolly going to get tossed into a refurb bin where it will under go fresh flash of firmware after some little asian will replace the speaker and usb port. I wouldnt stress it.
wheeliest said:
Like previously stated, its prolly going to get tossed into a refurb bin where it will under go fresh flash of firmware after some little asian will replace the speaker and usb port. I wouldnt stress it.
Click to expand...
Click to collapse
Gotcha. I just want to avoid getting charged the $300 because they see it was rooted. Would be lame since the device's mechanical USB port failure was completely unrelated to the device being rooted.
Has anyone returned a device to VZW that is still rooted? Did they charge you the $299?
I need help please
PLEASE...... I FLASHED MY LG-E739 wit MIUI V4 rom,
Den i decided to run a font.....when i reboot for de font to take effect it refuse to boot..stopped at de miui logo and have
tried everything to gain recovery mode but none seems to be working...
Please if anybody can render help to me i'd be very greatful.
Related
Thanks to this thread http://forum.xda-developers.com/showthread.php?t=1230956
I own one of those XTC Clip's if you are not one of the other 9 people who could get one, My advise if you want to take this phone up a level then purchase one.
First off create the gold card via the XTC Clip, this way it produces 2 files on the micro sd card which are needed for that phone connect the phone to the clip with that gold card in your phone, once done it will flash the phone for you and in one neat package it will also allow you s-off your phone, from that phase you can then download the following file http://www.mediafire.com/?yfsm6wk2lgyxj9s
once your phone is back to normal copy that file to your new gold card and boot into the bootloader and it will install that for you, you should then have custom recovery, now backup your existing rom, otherwise it is a real pain to get back if you don't like the custom firmware you choose after, I know first hand. I will post different roms as i get chance but I am now currently going to start to find a solid way to root the uk firmware
ok well this update includes the chance of an actual root with a stock o2 rom,
after successfully s-off the htc salsa, I installed the custom firmware recovery as above, from there i installed some custom chinese firmware but found it did not support google by any means, I didn't backup my original rom so I had a bit of work to get an o2 rom back onto the phone, From there i installed superuser and then busybox, I found that busybox forces superuser to close, today i have tried the ginger break exploit, again this closes super user, I took out the battery after 15 mins, took out the sd card and replaced with the gold card, at which point i installed the apks via the custom firmware recovery tool, when the phone loaded i ran z4root and chose the temp root, then ran gingerbreak again, this time super user did not close, but it fails, so i have then gone back and retried z4root and put permanent root and it seems to have worked. however after trying to install busybox, it just gives an error saying device not rooted, still in testing but z4 does seem to act like it grants root access, still in testing and will update as soon as this stock rom is rooted
Thanks for the report, mate, it surely helps us a lot. Keep it up ;-)
Sent from my SK17i using XDA Premium App
gdavies08 said:
ok well this update includes the chance of an actual root with a stock o2 rom,
after successfully s-off the htc salsa, I installed the custom firmware recovery as above, from there i installed some custom chinese firmware but found it did not support google by any means, I didn't backup my original rom so I had a bit of work to get an o2 rom back onto the phone, From there i installed superuser and then busybox, I found that busybox forces superuser to close, today i have tried the ginger break exploit, again this closes super user, I took out the battery after 15 mins, took out the sd card and replaced with the gold card, at which point i installed the apks via the custom firmware recovery tool, when the phone loaded i ran z4root and chose the temp root, then ran gingerbreak again, this time super user did not close, but it fails, so i have then gone back and retried z4root and put permanent root and it seems to have worked. however after trying to install busybox, it just gives an error saying device not rooted, still in testing but z4 does seem to act like it grants root access, still in testing and will update as soon as this stock rom is rooted
Click to expand...
Click to collapse
meaning now you had S-off and root access?
to get that recovery i should pay for it? *I don't have a credit card, so online payment a little bit tricky for me *
darma78 said:
meaning now you had S-off and root access?
to get that recovery i should pay for it? *I don't have a credit card, so online payment a little bit tricky for me *
Click to expand...
Click to collapse
i have successful s-off
root on the other hand is a no
Once everything is working and root is sorted i will post my workings, so there is no need to pay for anything, you may need an xtc clip unless you would be happy testing a formatted micro sd card with the files a xtc clip generates in your phone
Z4ROOT shows as if it has rooted the phone but not one root app confirms, when i installed root checker, that confirms the phone is not rooted, but does state that superuser is in the right place, this morning i had to recover from a previous back up too as the clock seems to be playing up and I had noticed some apps not working quite right after the z4root and gingerbreak tests.
gdavies08 said:
i have successful s-off
root on the other hand is a no
Once everything is working and root is sorted i will post my workings, so there is no need to pay for anything, you may need an xtc clip unless you would be happy testing a formatted micro sd card with the files a xtc clip generates in your phone
Z4ROOT shows as if it has rooted the phone but not one root app confirms, when i installed root checker, that confirms the phone is not rooted, but does state that superuser is in the right place, this morning i had to recover from a previous back up too as the clock seems to be playing up and I had noticed some apps not working quite right after the z4root and gingerbreak tests.
Click to expand...
Click to collapse
he maybe thought that xtc clip does the root
very true with the thread been progress with xtc clip.
I do have to say the root on this phone is becoming so what of a head ache trying so many different work arounds but when i am off for a day next i will test some more options
Does the clip require a battery or can I use the USB cable to fit via pc?
Sent from my HTC Salsa C510e using Tapatalk
followed all instructions and still have s-on!
the clip i found seems to work better with a 9v battery
---------- Post added at 08:42 PM ---------- Previous post was at 08:41 PM ----------
i did find i had to mess around with it quite a bit before i got the s-off, still been working on rooting i got close today but then for the short while i thought i had done it as a temp, everything on my phone seemed to freeze or hang up
ok diag screen was running, went into the screen and selected DIAG in red.
goto service DIAG 1.00 screen, hit the fb button on clean S58 and then it takes 10secs till reboot.
then still s-on!
tried numerous of times now with no luck!
BigBearEvo said:
ok diag screen was running, went into the screen and selected DIAG in red.
goto service DIAG 1.00 screen, hit the fb button on clean S58 and then it takes 10secs till reboot.
then still s-on!
tried numerous of times now with no luck!
Click to expand...
Click to collapse
I think when i put the guide together i kinda overlooked just what i did and assumed others would be just as experienced, I am off on thursday so will have a play then and see if i can put something together to cover all the steps.
i got my clip weeks ago but havent had time to play with(mostly cause my gf uses the salsa and doesnt have a secondary phone)
but have some time this week and will work with it and also see if root can be achieved
root can be gained already has been try under the root and recovery thread for it.
Please help. I rooted my Bionic and removed some of the bloatware via Titanium Backup. Not being totally stupid, I did a backup of the apps first. When I tried to load the new OTA, I got an error because it was apparently looking for the IM app (Which I never use). Of course, I had removed it as bloatware. When I tried to reinstall it via Titanium Backup, it just hangs.
I wasn't giving up so easily. So I extracted the apk file from the zip file and tried to reinstall it manually. Unfortunately I get "App not installed".
Any ideas?
I don't have my phone with me at the moment (gasp!) but near the bottom of the main preferences list in TB there is an option for failsafe mode. Make sure this is checked and put it on "indirect" app processing mode. Wording may vary slightly from that but if you set those two options it should work.
88Keys88 said:
Please help. I rooted my Bionic and removed some of the bloatware via Titanium Backup. Not being totally stupid, I did a backup of the apps first. When I tried to load the new OTA, I got an error because it was apparently looking for the IM app (Which I never use). Of course, I had removed it as bloatware. When I tried to reinstall it via Titanium Backup, it just hangs.
I wasn't giving up so easily. So I extracted the apk file from the zip file and tried to reinstall it manually. Unfortunately I get "App not installed".
Any ideas?
Click to expand...
Click to collapse
And for future reference, use the freeze option next time instead f removing them.
MillionManMosh said:
I don't have my phone with me at the moment (gasp!) but near the bottom of the main preferences list in TB there is an option for failsafe mode. Make sure this is checked and put it on "indirect" app processing mode. Wording may vary slightly from that but if you set those two options it should work.
Click to expand...
Click to collapse
I hope you and your phone have been joyously reunited
I triedd your suggestions, but alas no go. Any other ideas?
If you already have everything backed up I'd just go ahead and use RSDLite to set the phone back to stock:
http://forum.xda-developers.com/showthread.php?t=1262540
Just keep in mind you lose root through this, so to be safe you might want to reroot and apply the 'forever root' hack before you update. Although I understand newer root exploits like R3l3as3d work on the newer system as well.
And yes, the battery was joyously reunited with the charger...
It's a little more hard core than I've gone before, but I guess it's my only option. I've flashed ROM's before to my OG, but never had to go this route.
Thanks for your help and wish me luck!
And to johnlgalt - What can I say but I always learn from my mistakes. Monday morning is always the best time to be a quarterback ;-)
The OG DROID had an unlocked everything, so it was easy to do all of this. Because of eFuse and our locked bootloaders, it's most definitely more complicated. Our phones cannot even replace the recovery yet all we can do is use a bootstrap method to bypass the stock recovery and run an alternate recovery - and until we get a disabled eFuse and unlocked bootloader, this ain't gonna change.
I am very sorry for what is certainly a stupid question, but if it is any consolation I DID search and read through threads until my head hurt prior to posting.
1) What is the best way to apply the new OTA 4.2 update for those with rooted Nexus 7 tablet.
With the 4.1.2 update, I blindly installed the OTA update when prompted and didnt realize there was a problem until i tried to access my stickmount USB drive. Luckily the nexus 7 was still unlocked so I didn't need to wipe everything. All i did was re-root it using Nexus Root Toolkit v. 1.5.4. and was back up and running. Is this going to be the same experience with the 4.2 update?
I have installed Voodoo OTA Root keeper v2.0.3 - is this a better route for upgrade instead of re-rooting via the Nexus Toolkit? And if so, how should I use it (do know much about the app).?
2) Is stickmount going to work? And if not, is there a good working alternative for streaming mkv h264 movies to MXPlayer (or other player)?
The main reason I rooted was to access a USB drive for playing movies, TV shows while traveling. We are heading off to Cabo for Thanksgiving and definitely want to be able to access and play movies from my stickmount'ed usb drive. Any suggestions ? Should I just wait to update - and if so is there any way to get the Nexus to stop prompting to install the update all the time?
Thanks in advance to anyone willing to have pity on me...
hinsdale1 said:
I am very sorry for what is certainly a stupid question, but if it is any consolation I DID search and read through threads until my head hurt prior to posting.
1) What is the best way to apply the new 4.2 update for those with rooted Nexus 7 tablet.
With the 4.1.2 update, I blindly installed the OTA update when prompted and didnt realize there was a problem until i tried to access my stickmount USB drive. Luckily the nexus 7 was still unlocked so I didn't need to wipe everything. All i did was re-root it using Nexus Root Toolkit v. 1.5.4. and was back up and running. Is this going to be the same experience with the 4.2 update?
I have installed Voodoo OTA Root keeper v2.0.3 - is this a better route for upgrade instead of re-rooting via the Nexus Toolkit? And if so, how should I use it (do know much about the app).?
2) Is stickmount going to work?
The main reason I rooted was to access a USB drive for playing movies, TV shows while traveling. We are heading off to Cabo for Thanksgiving and definitely want to be able to access and play movies from my stickmount'ed usb drive. Any suggestions ? Should I just wait to update - and if so is there any way to get the Nexus to stop prompting to install the update all the time?
Thanks in advance to anyone willing to have pity on me...
Click to expand...
Click to collapse
1) I just downloaded the OTA 4.2 .zip, copied it to my N7, ran CWM and flashed it. When it asked about keeping recovery and keeping root, I said "yes" and it worked without a problem!
2) Works for me.
volarchico said:
1) I just downloaded the OTA 4.2 .zip, copied it to my N7, ran CWM and flashed it. When it asked about keeping recovery and keeping root, I said "yes" and it worked without a problem!
2) Works for me.
Click to expand...
Click to collapse
Sorry these answers need to be dumb'd down for me
1) If i already have the update downloaded via OTA trying to install itself, is it really easier/necessary to locate the zip you mention, copy it to the N7 (not sure where to copy) and run CWM (not sure what that is or where i get it or how to install it). Is there an easier way to accomplish the update? Perhaps setting the Voodoo Rootkeeper to preserve the root or temporarily unroot.. then just install the downloaded OTA update and then return the root? Or just installing the update and then running the re-root using the Nexus Toolkit (like I did with the 4.1.2 update)?
2) I would like to know more about how you avoided this issue described in this thread here with stickmount not functioning with v4.2 because of the new mulituser framework that causes it no longer to see files in the mounted folders.
Thanks for your help and to anyone else that chimes in... any help is appreciated. Again sorry for being stupid.
hinsdale1 said:
Sorry these answers need to be dumb'd down for me
1) If i already have the update downloaded via OTA trying to install itself, is it really easier/necessary to locate the zip you mention, copy it to the N7 (not sure where to copy) and run CWM (not sure what that is or where i get it or how to install it). Is there an easier way to accomplish the update? Perhaps setting the Voodoo Rootkeeper to preserve the root or temporarily unroot.. then just install the downloaded OTA update and then return the root? Or just installing the update and then running the re-root using the Nexus Toolkit (like I did with the 4.1.2 update)?
Click to expand...
Click to collapse
i tried with OTArootkeeper app. but it don't update.... at restart for installing, it gave a black screen with android in the middle, with a RED icon inside it...... then it restart and 4.1.2 is always there
Perhaps these questions are so rudimentary that they hardly seem worth bothering with - but for some of us, these hacks and the info being thrown around in here are pretty confusing at times. I would be very grateful to anyone with some insight willing to help out?.
i found that this could be a problem with recovery mode... infact if i tr y to restart in recovery, it gave the same error...
i rooted with toolbox, and i'm thinking that it could have removed my recovery... now i'd like to try to recover the stock recovery with the same tool... but i'm not sure about that.
We seem to have veered off topic a bit here (at least for me)... so let me re-post the questions and beg again for mercy from any kind soles who can offer some advice?
1) What is the best way to apply the new OTA 4.2 update for those with rooted Nexus 7 tablet?
With the 4.1.2 update, I blindly installed the OTA update when prompted and didnt realize there was a problem until i tried to access my stickmount USB drive. Luckily the nexus 7 was still unlocked so I didn't need to wipe everything. All i did was re-root it using Nexus Root Toolkit v. 1.5.4. and was back up and running. Is this going to be the same experience with the 4.2 update?
I have installed Voodoo OTA Root keeper v2.0.3 - is this a better route for upgrade instead of re-rooting via the Nexus Toolkit? And if so, how should I use it (do know much about the app).?
2) Is stickmount going to work? And if not, is there a good working alternative for streaming mkv h264 movies to MXPlayer (or other player)?
The main reason I rooted was to access a USB drive for playing movies, TV shows while traveling. We are heading off to Cabo for Thanksgiving and definitely want to be able to access and play movies from my stickmount'ed usb drive. Any suggestions ? Should I just wait to update - and if so is there any way to get the Nexus to stop prompting to install the update all the time?
Thanks in advance to anyone willing to have pity on me...
Bueller...... Bueller...... Bueller?
Hi! Last month I did the 4.1.2 OTA update. I was rooted but on stock. It updated with no problems. I used Voodoo OTA rootkeeper, restored the root, and either renistalled super su, or just updated the binary. Can't remember.....But I did lose my custom recovery. Didn't realize it till tonite when I went to do the 4.2 update.
So to your question. I forced the OTA 4.2 update. And it downloaded. I made sure voodoo rootkeeper was set to save the root. Then let it install. It rebooted. I opened voodoo, restored root, was asked to update super su binary, accepted. Still not rooted till I rebooted.
So far I have root, and am on 4.2 JB. So my goal was to get my custom recovery back on. Install goo manager from market. Open it, go to the settings button top right, it will give you the choice to install open recovery script. TWRP- Then it will ask you twice are you sure you want to do this and reboot? Say yes. Mine did not reboot and it looked like it did nothing. So, I flipped into recovery and Teamwinn recovery was installed. I made a backup, and rebooted.
Good luck!
Thanks for your help. Glad to hear that the OTA 4.2 update should go relatively painlessly (keeping root using voodoo rootkeeper). If you have a minute, I would be grateful if you can just briefly confirm, describe specifically what I need to be checking/configuring in Voodooo (not very familiar with the app) prior to initiating the OS update, I would feel a little more secure before pulling the trigger.
It appears that many apps are still catching up with their own updates, including apparently stickmount (the reason I rooted) to handle the new 4.2 framework so I am thinking best to hold off until after thanksgiving vacation before applying the update.
Thanks again.
hinsdale1 said:
Thanks for your help. Glad to hear that the OTA 4.2 update should go relatively painlessly (keeping root using voodoo rootkeeper). If you have a minute, I would be grateful if you can just briefly confirm, describe specifically what I need to be checking/configuring in Voodooo (not very familiar with the app) prior to initiating the OS update, I would feel a little more secure before pulling the trigger.
It appears that many apps are still catching up with their own updates, including apparently stickmount (the reason I rooted) to handle the new 4.2 framework so I am thinking best to hold off until after thanksgiving vacation before applying the update.
Thanks again.
Click to expand...
Click to collapse
Hi hinsdale,
Have you tried updating to 4.2 yet? Also i heard that if you update SuperSU to version 0.98 the latest version it could cause issues and you will have to reflash the device.
Thanks,
JBIRD
Thanks,
JBIRD
4.2 OTA already loaded, lost root
Hi, I have learned the hard way not to do the OTA upgrade. I just let the 4.2 OTA download when asked to. Now I lost my root that I had on my Nexus7 with 4.1.2. Still unlocked though. What can I do now to root it again and not lose all my apps and data?
I'm a newbie, so please remember that when responding. Thanks.
Hi hinsdale! I am not a techie- I just learn as I go and read, read, read.
So, my voodoo app has 4 checks in the boxes. I seem to remember only 3 boxes checked when I did the update, but I'm not sure. It would make sense that all are checked.
After I updated, I opened the voodoo app first, and there is a box that says restore root. Then it asked if I wanted to update the su binary. Did that, still not rooted according to Tit. BU. Rebooted, then I was rooted. Good luck with your update.
I'm sorry I can't tell you how to run the initial save root on voodoo. I did it a while ago and don't remember, but it was not hard. Very easy.. Just make sure you Read, re- read, and read again before you do any modifications to your tablet. Know the possible bad outcomes, and be prepared to trouble shoot. This site is very good about helping you out if things go wrong. That's why it's a very good idea to be aware of the possible bad outcomes. The only way to know is to READ-READ=READ!
Did I mention READ??? lol. That's how I figure stuff out. If you read about others mistakes, you can avoid them. I also wait a day or 2 to see how it goes for others before I attempt modifications. That includes new roms. You never know what goes wrong until someone is the guinea pig! I am not techie enough to be the guinea pig!
paulie7880 said:
Hi, I have learned the hard way not to do the OTA upgrade. I just let the 4.2 OTA download when asked to. Now I lost my root that I had on my Nexus7 with 4.1.2. Still unlocked though. What can I do now to root it again and not lose all my apps and data?
I'm a newbie, so please remember that when responding. Thanks.
Click to expand...
Click to collapse
same thing here...I tried to use TWRM to flash SU but it seems that after going into recovery using TWRM I can't see any any file or folder on my SD except 3 folders???? Can someone please help us....
YOu will need to search the best way to root again.
How did you root initially?? You may have to do it that way again. Just make sure the method is compatible with 4.2 JB.
sashusmom said:
YOu will need to search the best way to root again.
How did you root initially?? You may have to do it that way again. Just make sure the method is compatible with 4.2 JB.
Click to expand...
Click to collapse
Nexus Root Toolkit
The OTA update downloaded to my cache folder, I moved it to my sdcard. Wouldn't install since I had to fix a couple of files I had edited. So once those 2 files were fixed it installed just fine. Haven't had any issues yet.
The same on here...
But I guess it is better until they fix all this bugs they are reporting.
I'll wait until then.
Sent from my Nexus 7 using xda app-developers app
Updated to 4.2
Hi have updated the nexus to 4,2 and used Voodoo OTA Rootkeeper to keep my root followed the instructions as I did when updated to 4.1.2,my Nexus appears to be rooted superSu is working also stickmount sees the usb but it will not show any files on the sd card any help here please to get it to see the files on the sd card, thanks for your time
Nick
i dont post often as i am usually here looking for help. this time i get to help
i just downloaded and installed 4.2 OTA.
if your nexus was previously unlocked and rooted, it will download and install just fine. however you will lose root, but KEEP the unlocked state.
to root it again, you must goto "about tablet" and tap your build number 7 times to become a developer, this is not a troll, i got this info from another thread on xda.
then using the nexus root toolkit 1.5.4 with modeltype set to "android *.*.* any build", just do the root procedure.
reboot and ur in business, no need to update supersu, and busybox will still be installed already.
I have rooted my N6 via adb, the supersu .bat file, TWRP, and the Nexus Toolkit. No matter what I do, after restoring my N6 and rebooting, I lose the NFC options under settings. If I do a factory reset I regain the options, but when I re-flash root I lose them again. NFC writing programs can't detect NFC ability on my phone, and ztest says I don't have it.
I am running the stock factory image.
NFC works fine before I root. I have rooted every Android device I've had, and never experienced this. Is this an N6 issue, a lollipop issue, or some special circumstance of my own creating?
Has anyone else experienced this?
TIA.
goodfellaslxa said:
I have rooted my N6 via adb, the supersu .bat file, TWRP, and the Nexus Toolkit. No matter what I do, after restoring my N6 and rebooting, I lose the NFC options under settings. If I do a factory reset I regain the options, but when I re-flash root I lose them again. NFC writing programs can't detect NFC ability on my phone, and ztest says I don't have it.
I am running the stock factory image.
NFC works fine before I root. I have rooted every Android device I've had, and never experienced this. Is this an N6 issue, a lollipop issue, or some special circumstance of my own creating?
Has anyone else experienced this?
TIA.
Click to expand...
Click to collapse
Rooted, and unlocked via NTK here. NFC works fine.
goodfellaslxa said:
I have rooted my N6 via adb, the supersu .bat file, TWRP, and the Nexus Toolkit. No matter what I do, after restoring my N6 and rebooting, I lose the NFC options under settings. If I do a factory reset I regain the options, but when I re-flash root I lose them again. NFC writing programs can't detect NFC ability on my phone, and ztest says I don't have it.
I am running the stock factory image.
NFC works fine before I root. I have rooted every Android device I've had, and never experienced this. Is this an N6 issue, a lollipop issue, or some special circumstance of my own creating?
Has anyone else experienced this?
TIA.
Click to expand...
Click to collapse
what are you using to gain root? the latest supersu should not mess things up. the latest supersu is version 2.37 http://download.chainfire.eu/636/SuperSU/UPDATE-SuperSU-v2.37.zip
I've had no problems at all. I used the wugfresh toolkit over in the development section. Worked flawlessly and was pretty much the easiest root I've ever used. You just click buttons. Lol. Go back to full stock and use that.
I have used Wug's toolkit, and agree it's very easy. I have also tried every other method. I have only flashed the stock rom. Maybe it's something that's loading afterwards? Are any apps known to kill NFC? I literally lose the option to enable NFC (and also Android beam). It's just not there.
My process has been 1. Flash stock rom. 2. Restore from Google. 3. Flash root. Sometime after flashing root (and making sure I still have NFC) it disappears.
Again, I have rooted many phones over the years, and never had this problem. I am going to have to try to diagnose what step exactly causes me to lose NFC. I reflashed yesterday and had NFC, but today it's gone again.
I don't think I'm doing anything out of the ordinary, so I will post IF I find the culprit. I doubt I will be the only one to experience this.
goodfellaslxa said:
I have used Wug's toolkit, and agree it's very easy. I have also tried every other method. I have only flashed the stock rom. Maybe it's something that's loading afterwards? Are any apps known to kill NFC? I literally lose the option to enable NFC (and also Android beam). It's just not there.
My process has been 1. Flash stock rom. 2. Restore from Google. 3. Flash root. Sometime after flashing root (and making sure I still have NFC) it disappears.
Again, I have rooted many phones over the years, and never had this problem. I am going to have to try to diagnose what step exactly causes me to lose NFC. I reflashed yesterday and had NFC, but today it's gone again.
I don't think I'm doing anything out of the ordinary, so I will post IF I find the culprit. I doubt I will be the only one to experience this.
Click to expand...
Click to collapse
again, ill repeat myself, what file are you using to gain root? if you are using older files, they break things.
simms22 said:
again, ill repeat myself, what file are you using to gain root? if you are using older files, they break things.
Click to expand...
Click to collapse
I used 2.36. I'll try 2.37 to see if it makes a difference.
goodfellaslxa said:
I used 2.36. I'll try 2.37 to see if it makes a difference.
Click to expand...
Click to collapse
it doesnt matter, 2.36 is still good. the only thing i can tell you is root your phone the right way. you want to fastboot oem unlock the bootloader first, then fastboot flash a custom recovery, then flash the the supersu file via that recovery, then just reboot.
simms22 said:
it doesnt matter, 2.36 is still good. the only thing i can tell you is root your phone the right way. you want to fastboot oem unlock the bootloader first, then fastboot flash a custom recovery, then flash the the supersu file via that recovery, then just reboot.
Click to expand...
Click to collapse
Is there an issue with the following method?
fastboot oem unlock
chainfire's autoroot in stock recovery
Just trying to understand if there is a reason why I should do it a different way. At this time, I don't need custom recovery (all I want root for at the moment is adaway - and that is working fine). I suspect i will end up flashing TWRP in the near future (when I need it).
jj14 said:
Is there an issue with the following method?
fastboot oem unlock
chainfire's autoroot in stock recovery
Just trying to understand if there is a reason why I should do it a different way. At this time, I don't need custom recovery (all I want root for at the moment is adaway - and that is working fine). I suspect i will end up flashing TWRP in the near future (when I need it).
Click to expand...
Click to collapse
yes, there very well could be. doing it right is just as easy as using any root toolkit, its a nexus and has the options to do it manually, no hacking. if you have the drivers to your computer installed, it takes about 3-4 minutes.
simms22 said:
yes, there very well could be. doing it right is just as easy as using any root toolkit, its a nexus and has the options to do it manually, no hacking. if you have the drivers to your computer installed, it takes about 3-4 minutes.
Click to expand...
Click to collapse
Till Lollipop, I've always done it the manual way. With lollipop on my N5 and then, on my N6, the sticky's here didn't seem to provide any different method - it was autoroot.
Reading other threads showed that it was either custom kernel with relaxed permissions and supersu, or autoroot, or the toolkit.
I know that chainfire was testing a version of supersu that wouldn't need the modified kernel, but it was still in beta.
So, what method would you have recommended? (which did you use?) SuperSU by itself isn't sufficient (unless you went with the beta). Or is there a different guide/sticky thread that I missed?
jj14 said:
Till Lollipop, I've always done it the manual way. With lollipop on my N5 and then, on my N6, the sticky's here didn't seem to provide any different method - it was autoroot.
Reading other threads showed that it was either custom kernel with relaxed permissions and supersu, or autoroot, or the toolkit.
I know that chainfire was testing a version of supersu that wouldn't need the modified kernel, but it was still in beta.
So, what method would you have recommended? (which did you use?) SuperSU by itself isn't sufficient (unless you went with the beta). Or is there a different guide/sticky thread that I missed?
Click to expand...
Click to collapse
i recommend the way i did it, the right way. fastboot oem unlock, fastboot flash a recovery, and flash the latest supersu. what you are reading is now considered old. flashing the new supersu(beta) is all thats needed.
simms22 said:
i recommend the way i did it, the right way. fastboot oem unlock, fastboot flash a recovery, and flash the latest supersu. what you are reading is now considered old. flashing the new supersu(beta) is all thats needed.
Click to expand...
Click to collapse
I guess I'll try it when the next update comes along. Get system partition back to stock by flashing appropriate system images, and then using the new supersu.
jj14 said:
I guess I'll try it when the next update comes along. Get system partition back to stock by flashing appropriate system images, and then using the new supersu.
Click to expand...
Click to collapse
oh, i almost forgot. the n6 has a new option, before unlocking the bootloader, you have to go to developer settings and enable oem unlock.
simms22 said:
oh, i almost forgot. the n6 has a new option, before unlocking the bootloader, you have to go to developer settings and enable oem unlock.
Click to expand...
Click to collapse
Thanks
Yeah, I knew that (I already unlocked bootloader and rooted)
Well, after reflashing and not rooting I still lost NFC (though it took several hours and a few reboots before it stopped), so I decided to try not using google restore, and setup as a new device.
After manually reinstalling 300+ apps, reconfiguring everything, and rooting (using 2.37), NFC appears to be working fine. I *think* that some setting that was being restored from previous google backups eventually killed NFC.
I'm not rooted... stock T-Mobile Nexus 6 running a nano SIM from my Droid Maxx on VZW. There are no NFC settings in the Wireless settings section.
I'm not unlocked or rooted... just took the over the air update that came right after the phone first powered up.
Is the nano SIM a factor? What exactly is the difference between the NFC nano SIM and the non-NFC nano SIM? The Droid Maxx has NFC, so I assume that its nano SIM supports NFC. Not sure what's going on here.
lkevinl said:
I'm not rooted... stock T-Mobile Nexus 6 running a nano SIM from my Droid Maxx on VZW. There are no NFC settings in the Wireless settings section.
I'm not unlocked or rooted... just took the over the air update that came right after the phone first powered up.
Is the nano SIM a factor? What exactly is the difference between the NFC nano SIM and the non-NFC nano SIM? The Droid Maxx has NFC, so I assume that its nano SIM supports NFC. Not sure what's going on here.
Click to expand...
Click to collapse
I think its not a root issue. Did you restore a previous backup, or use the tap-to-import option? I think there is a setting that is being imported that causes this. Try resetting to stock, and when you go through the initial setup don't import a backup. That fixed it for me.
I used the original auto-root, and I still have NFC options available also. (and I never had to enable developer options. I unlocked the bootloader right out of the box).
Hmmm... was hoping to avoid doing the factory reset. I did try to the Tap to Go option but wasn't sure if it did anything. I'm mostly interested in getting my WiFi settings restored. I suspect your right about a restored setting mucking this up. I may have to do the reset anyway because of the other problem I'm having with Facebook that I posted about in an earlier thread.
So I've got a bit of a problem. I think it's a quite unique one, tried searching for it, but no results.
First of all, a little backstory. My USB-cable port broke. I usually clean it with a toothpick or so, just to get dust out of it. I've done this with my older phones as well, but never had any casualties. Maybe this was my first misstep, but I have to say that the port was never really perfect since day 1.
Anyway, my USB-port broke a few days ago, which means no charging. Before I ran out of battery life, I really didn't know what to do, because since I rooted it, it has no warranty. So at 3% of battery life, I got desperate, freaked out and wasn't thinking straight and deleted SuperSU from my phone through the app, hoping that if it needed to be fixed by a "professional", I could just send it back. Smart eh?
I ordered a wireless Qi charger to charge my phone and it was delivered today. Works fine, my phone turned on again, but without SuperSU installed. So I went to chainfire's website and downloaded the SuperSU zip from there and flashed it. Bootloop. I did some googling and read that I need the unofficial updated version, since I've got a 6.0.1 ROM. I totally forgot about that, because it has been a while since I flashed the 6.0.1 ROM.
So I've got this problem: I need to get the new version of the SuperSU zip on my phone, but I can't connect to my PC using a USB cable and I can't download it directly on my phone because of the bootloop. And the Nexus 6 doesn't have a SD card slot, of course. Could there be some other way to delete SuperSU, or very maybe to transfer files wirelessly through TWRP?
I already factory resetted it, with no results. Help? Please?
How about you restore a backup.... You have one on the phone right???
You can also navigate twrp via the provided file manager.
Do you have a ROM zip left on the phone? If so wipe and flash it to start fresh.
Wireless adb push?
Sent from my Pixel using XDA-Developers mobile app
Wireless adb doesn't work in recovery.
Ah hmmm... Then it needs to be physically repaired. Can't think of any other way
Sent from my Pixel using XDA-Developers mobile app
khanam said:
Ah hmmm... Then it needs to be physically repaired. Can't think of any other way
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
Really no other way than repairing it physically? I've heard that can be quite expensive and I'm getting a new phone in a month or two, so I don't really want to spend a lot of money on a phone which I'm not going to use afterwards anyway.
I tried removing SuperSU manually following the steps on this website, but instead of using ES file explorer, I mounted system and used the file explorer in TWRP. But that didn't work either.
If there isn't any other way, could formatting data help to at least stop the bootloop from happening? I wouldn't really mind doing so, because all of my pictures are saved on google photos and I got a TitaniumBackup of all my userapps from a few weeks back on Google Drive.
IYIatthys said:
Really no other way than repairing it physically? I've heard that can be quite expensive and I'm getting a new phone in a month or two, so I don't really want to spend a lot of money on a phone which I'm not going to use afterwards anyway.
I tried removing SuperSU manually following the steps on this website, but instead of using ES file explorer, I mounted system and used the file explorer in TWRP. But that didn't work either.
If there isn't any other way, could formatting data help to at least stop the bootloop from happening? I wouldn't really mind doing so, because all of my pictures are saved on google photos and I got a TitaniumBackup of all my userapps from a few weeks back on Google Drive.
Click to expand...
Click to collapse
as noted above, you can just do a clean flash of any rom zip you have in your phone. After you boot up, there are a ton of apps in the Store that would let you send files wirelessly. Solid Explorer for example as you can set your phone as an FTP server.
ibsk8 said:
Wireless adb doesn't work in recovery.
Click to expand...
Click to collapse
I thought it was a feature of TWRP or CWM to have wireless adb in revcovery?
qnc said:
I thought it was a feature of TWRP or CWM to have wireless adb in revcovery?
Click to expand...
Click to collapse
cwm doesnt have a nexus 6 recovery made. and thats not a feature of twrp.
jibust said:
as noted above, you can just do a clean flash of any rom zip you have in your phone. After you boot up, there are a ton of apps in the Store that would let you send files wirelessly. Solid Explorer for example as you can set your phone as an FTP server.
Click to expand...
Click to collapse
Exactly what I was going to say, just use a file manager to transfer over the zip (I use x-plore file manager by lonely cat games, which supports FTP/SFTP/SMB and also will start a local webserver to you can use the for manager from your PC.