New update messed up my tablet - Nexus 7 (2013) Q&A

So I was rooted, received and installed the latest update (I knew this was a mistake) and now the tablet is frozen. When I unlock the start screen, the Nexus cross comes up and then it goes back to the lock screen. I hooked it up to the Nexus Toolkit and when I try and reroot the tablet, it says that it cannot find ADB.
Any help would be appreciated.
Thanks, Dennis

I don't think re-rooting the tablet will fix it.
Do you have stock Android recovery installed?

RMarkwald said:
I don't think re-rooting the tablet will fix it.
Do you have stock Android recovery installed?
Click to expand...
Click to collapse
yes

You may be able to boot into stock Android recovery, and select "wipe factory data" or "factory data reset" to fix it. That's going to wipe your apps/data too, just an FYI.

fyrmd said:
yes
Click to expand...
Click to collapse
I am by no means an expert, but I would think you could get the original image for your tablet by looking here. If you have the Windows drivers properly installed on your computer (also available at that link), then you should be able to use ODIN to restore your tablet to stock. After that, reapply any updates if you find any, and then re-root your device.
This has worked for me (more often than I would care to mention) on literally every other Android device, so I can't see why it would not work here.
Good luck...

I was afraid you were going to say that. It looks like that did the trick, thanks.

Related

huge problem with galaxy nexus

i recently bought the samsung galaxy nexus.i followed this tutorial http://forum.xda-developers.com/showthread.php?t=1392310
to unlock bootloader install recovery and root i also had latest ota from google(jelly bean JRO03C) and installed no further mods.Yesterday i installed http://forum.xda-developers.com/showthread.php?p=28559395#post28559395 and then my odyssey began.the phone starting bootlooping.i was scared so i wiped cache dalvik cache formatted system and installed bigxie maguro ota.unfortunately bootloops continue.i dont want to full wipe my phone since i have essential sms and contacts which i havent backuped.anyone can help me solve the problem?thnx in advance
but do you used the first or the second one?the first says that's not compatible with ota...you have to used this..http://forum.xda-developers.com/showthread.php?p=28616532#post28616532
you can adb push the right files and flash it over...and if you haven't a nandroid,i don't think there are other possibilities to not loose sms and others..a reflash delete them..
yep i used this but my rom(google official) wasnt deodexed.Update i flashed a google image with option 9 in gnex toolkit and bootloops still remain
msli said:
i recently bought the samsung galaxy nexus.i followed this tutorial http://forum.xda-developers.com/showthread.php?t=1392310
to unlock bootloader install recovery and root i also had latest ota from google(jelly bean JRO03C) and installed no further mods.Yesterday i installed http://forum.xda-developers.com/showthread.php?p=28559395#post28559395 and then my odyssey began.the phone starting bootlooping.i was scared so i wiped cache dalvik cache formatted system and installed bigxie maguro ota.unfortunately bootloops continue.i dont want to full wipe my phone since i have essential sms and contacts which i havent backuped.anyone can help me solve the problem?thnx in advance
Click to expand...
Click to collapse
1) the extended power menu mod you wanted to use said it does not work with the OTA. no matter what you do, you will need to reflash at minimum the system image from stock.
2) if that doesnt work, you need to reflash totally back to stock and you will lose everything.
Zepius said:
1) the extended power menu mod you wanted to use said it does not work with the OTA. no matter what you do, you will need to reflash at minimum the system image from stock.
2) if that doesnt work, you need to reflash totally back to stock and you will lose everything.
Click to expand...
Click to collapse
he sad already flashed google image from toolkit,and he used the right one for ota..only difference he isn't deodexed....OP the only thing you can do is wipe system\factory rest and reflash the rom..there aren't alternatives i think.another times before try this mod,bo a nandroid.i'm sorry for you
sert00 said:
he sad already flashed google image from toolkit,and he used the right one for ota..only difference he isn't deodexed....OP the only thing you can do is wipe system\factory rest and reflash the rom..there aren't alternatives i think.another times before try this mod,bo a nandroid.i'm sorry for you OP
Click to expand...
Click to collapse
if you used fastboot, you can just flash the system image by itself. this would preserve user data.
also, toolkits are just a bad idea.
Zepius said:
also, toolkits are just a bad idea.
Click to expand...
Click to collapse
+1
to be asking how to get out of a simple bootloop, what that says is that op doesnt know what he's doing.
people, don't point new users to toolkits. it only makes troubleshooting harder, what's user error, what isn't.
sent from my i9250
bk201doesntexist said:
+1
to be asking how to get out of a simple bootloop, what that says is that op doesnt know what he's doing.
people, don't point new users to toolkits. it only makes troubleshooting harder, what's user error, what isn't.
sent from my i9250
Click to expand...
Click to collapse
totally agree,i personally always doing all with fastboot with mine 3 fastbootable devices.it's a known fact from some time that toolkit it's best leave them where it is..but new people\user don't listen this reccomendation and always goes into trouble.often the convenience of a UI preserve you to understand better why a thing was happen.begin to read how to use fastboot command,there are plenty of guides out there

Stuck in Never-NeverLand

Long story short, I have two phones, an iPhone 4S (no camera because of work), and an SGS III (camera and LTE, for weekends). I am traveling this weekend, and I want the SGS III, but I need MHS, and I have an old plan that doesn't include it, so I figured I'd go ahead and root. I had good luck upgrading to 6.2 on the iPhone and running evasi0n last night, so I figured I'd give rooting a try tonight. I sort of know what I'm doing as I installed a ton of ROMs on the Captivate, which I had before the iPhone.
So I followed the steps on the Redmond Pie tutorial, but I got stuck. I managed to get up to the part where you boot into CWM, but the CMW_SuperUser_v3.07.zip file isn't showing up on the device, even though I put it there, and the device won't boot into Android normally to put it in USB mode, load it on there again, try again, etc. My first thought was to use a MicroSD card to get the file into CWM, except that I don't have one handy, and I can't get access to one before my trip.
So what should I do now?
try a different superuser?
and if you have your phone rooted
you can go playstore and download the app instead
pcshano said:
try a different superuser?
and if you have your phone rooted
you can go playstore and download the app instead
Click to expand...
Click to collapse
Different superuser? And I have to get the phone to boot in order to get to the Play Store...
I threw the phone on it's charger so that it wouldn't drain out, and now it's toasty warm... what now?
GSMinCT said:
Different superuser? And I have to get the phone to boot in order to get to the Play Store...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2042775
have to try this one?
pcshano said:
http://forum.xda-developers.com/showthread.php?t=2042775
have to try this one?
Click to expand...
Click to collapse
Are you suggesting I reflash the whole phone? That would be a MAJOR PITA, as I'd have to re-install all my apps and re-log-in to everything. I do have all the data in various cloud services though in case I have to take the nuclear option.
GSMinCT said:
Are you suggesting I reflash the whole phone? That would be a MAJOR PITA, as I'd have to re-install all my apps and re-log-in to everything. I do have all the data in various cloud services though in case I have to take the nuclear option.
Click to expand...
Click to collapse
err no?
you aren't flashing at firmware...
the only thing you're flashing thru odin is the recovery img
and the other thing that you are flashing is the root files in cwm
pcshano said:
err no?
you aren't flashing at firmware...
the only thing you're flashing thru odin is the recovery img
and the other thing that you are flashing is the root files in cwm
Click to expand...
Click to collapse
So I'd be able to boot again???
GSMinCT said:
So I'd be able to boot again???
Click to expand...
Click to collapse
should be, unless you mess up something along the way which could result in soft brick but chances are unlikely because the steps are really easy to follow
the whole process should only take ~5-10 mins so good luck
I tried that guide, and it doesn't work, I just get a newer version of CWM Recovery, which works with the touch screen and is awesome, but it doesn't help me get into Android. I'm sensing I have to re-flash the OS? God I hate AT&T.
I would recommend either flashing a pre-rooted stock firmware (root 66), or the stock firmware, via Odin. if using stock, then root with the chain fire auto root method.
either way, you're going to lose everything that's not on SD or extSD. but at least then it'll boot.

[Q] Cyanogen 10.1 mod gone wrong.

AT&T Galaxy S3
Mac OSX 10.8
I know I can get my device back, I'm just not sure how. I successfully rooted using CASUAL, no problems there. Got the normal root applications installed, did the Clockwork backup, everything was great.
I then decided to try a custom ROM - the Cyanogen 10.1. It downloaded fine, and I selected to also install Google Apps, then it rebooted and the Cyanogen boot screen with the spinning circle came up. However, this lasted way longer than I thought it should, so I looked it up, and what I got from the research is that I had the wrong gapps on there.
So, I followed the instructions in this thread (same problem as me), and wiped the system. However, I believe I used the wrong list item, and now everything I had is gone. I can't boot from recovery because it doesn't exist, and when booting into CM I just get the same error message that setup has stopped working. I thought maybe I could put a new ROM on the sd card or phone harddrive and boot from that, but both are inaccessible through USB on my Mac.
I can get it into ODIN mode (where it says "Downloading... Do not turn off target!"), which I'm thinking is what I want, and I have Heimdall installed and it runs and recognizes my device, but I cannot for the life of me find a tar.gz file to use.
If anyone can offer any sort of help, I would super appreciate it.
chazbot7 said:
AT&T Galaxy S3
Mac OSX 10.8
I know I can get my device back, I'm just not sure how. I successfully rooted using CASUAL, no problems there. Got the normal root applications installed, did the Clockwork backup, everything was great.
I then decided to try a custom ROM - the Cyanogen 10.1. It downloaded fine, and I selected to also install Google Apps, then it rebooted and the Cyanogen boot screen with the spinning circle came up. However, this lasted way longer than I thought it should, so I looked it up, and what I got from the research is that I had the wrong gapps on there.
So, I followed the instructions in this thread (same problem as me), and wiped the system. However, I believe I used the wrong list item, and now everything I had is gone. I can't boot from recovery because it doesn't exist, and when booting into CM I just get the same error message that setup has stopped working. I thought maybe I could put a new ROM on the sd card or phone harddrive and boot from that, but both are inaccessible through USB on my Mac.
I can get it into ODIN mode (where it says "Downloading... Do not turn off target!"), which I'm thinking is what I want, and I have Heimdall installed and it runs and recognizes my device, but I cannot for the life of me find a tar.gz file to use.
If anyone can offer any sort of help, I would super appreciate it.
Click to expand...
Click to collapse
Your recovery shouldn't be affected by a wipe (unless you flashed something over it) as ROMs don't flash recovery, therefor vol up + home + power should get you in it. If you success to, You should be able to mount through recovery.
As for Heimdall, it just got S3 support (last week I believe), therefor it might not be easy to find a stock file for it. That being said, if you have access to any Windows pc, that'd be the easiest solution here (using Odin).
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
BWolf56 said:
Your recovery shouldn't be affected by a wipe (unless you flashed something over it) as ROMs don't flash recovery, therefor vol up + home + power should get you in it. If you success to, You should be able to mount through recovery.
As for Heimdall, it just got S3 support (last week I believe), therefor it might not be easy to find a stock file for it. That being said, if you have access to any Windows pc, that'd be the easiest solution here (using Odin).
Click to expand...
Click to collapse
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
chazbot7 said:
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
Click to expand...
Click to collapse
Windows pc is definitely the easiest option here but you try mounting your SD from recovery, redownload the ROM and Gapps you wanna use, put them on your device and flash them after a factory reset.
If you wiped your SD card, it's normal that you don't have a backup anymore.
BWolf56 said:
Windows pc is definitely the easiest option here but you try mounting your SD from recovery, redownload the ROM and Gapps you wanna use, put them on your device and flash them after a factory reset.
If you wiped your SD card, it's normal that you don't have a backup anymore.
Click to expand...
Click to collapse
It's aaaliiiiiiive! Grabbed an extra micro SD I had, threw Cyanogen 10.1.0 RC4 on it, and installed it just fine. Now updating to RC5. My only question now is how to get Google Apps on there. Does this need to be done beforehand, or can it be done after?
chazbot7 said:
It's aaaliiiiiiive! Grabbed an extra micro SD I had, threw Cyanogen 10.1.0 RC4 on it, and installed it just fine. Now updating to RC5. My only question now is how to get Google Apps on there. Does this need to be done beforehand, or can it be done after?
Click to expand...
Click to collapse
You usually flash the Gapps right after flashing the ROM, before rebooting.
P.S.: fully reading the instructions helps before flashing
Sent from my SGH-I747 using xda app-developers app
BWolf56 said:
You usually flash the Gapps right after flashing the ROM, before rebooting.
P.S.: fully reading the instructions helps before flashing
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Gotcha, sorry about that. Thanks for all the help good sir. This is actually way faster than my stock ROM, I'm pretty stoked on it, Google Apps or not.
chazbot7 said:
Gotcha, sorry about that. Thanks for all the help good sir. This is actually way faster than my stock ROM, I'm pretty stoked on it, Google Apps or not.
Click to expand...
Click to collapse
No need to apologize. Glad you got it back up! And it was mostly to keep you from making similar mistakes in the future
Sent from my SGH-I747 using xda app-developers app
also one thing you need to know
First boot after you flash will always take longer than normal. After that, it's fine

[Q] Boot Loop

I just entered the world of a rooted phone, all exciting and new. I used triangle away, and everything is well. I even turned off the debugging mode as i thought i was all done with things rooting and didn't need it.
The next day I realize there is update for supersu, so i accept, if gives me two choices in the update, i choose one, and now my phone is the in GTN7100 loop non stop. Seems of the two options, I choose wrongly. I can put it into download mode. I think I can put it into recovery mode too.
I used this method to boot.
galaxy-note2.wonderhowto.com/how-to/root-your-samsung-galaxy-note-2-using-odin-for-windows-so-easy-your-grandma-can-do-it-0146884
I did perform some basic backups with kies and i believe an app called my backup, so in the worst case, I believe i can recover everything if had to do some kind of reset that would erase all the data. (I am hoping to avoid that, as the recovery may be a learning process if any challenges with it)
its with 4.1.2 and I am not sure if any other details I should provide. so i feel proud i got this far, sad the supersu update made some kind of corruption. i know you guys may be extremely busy and i thank you so much in advance.
Try getting into recovery (CMW or Philz touch) and re-flash a ROM?
thank you bunglebp
bunglebp said:
Try getting into recovery (CMW or Philz touch) and re-flash a ROM?
Click to expand...
Click to collapse
Thank you so much for your reply bunglebp.
I believe I had the CMW when i rooted. Reflashing the ROM won't lose the data, or will? This is new territory for me, so I am going step be step.
Volume up - home - power, i think i understand this far. I just don't want to make any mistakes and follow to a T to bring the phone back up with least work at it if possible.
Macguyer2000 said:
Thank you so much for your reply bunglebp.
I believe I had the CMW when i rooted. Reflashing the ROM won't lose the data, or will? This is new territory for me, so I am going step be step.
Volume up - home - power, i think i understand this far. I just don't want to make any mistakes and follow to a T to bring the phone back up with least work at it if possible.
Click to expand...
Click to collapse
Yes your description of how to get into recovery is correct. But your description of your situation is light on details, hard to get a clear picture, but I feel your pain!
If you have a ROM sitting on your phone that you can reflash in recovery, do it. You won't lose any media on your internal memory e.g. pictured, movies. All your app settings will remain if you don't wipe anything in recovery prior to flashing - but in your situation I suggest a full wipe & reset to (hopefully) clear out any problems.
As for upgrading SU, I'm wondering what you mean by two options? Let us know how you get on. Also feel free to PM me if you're truly stuck, I've been there myself and received help that saved me untold stress.
tweeny80 said:
Yes your description of how to get into recovery is correct. But your description of your situation is light on details, hard to get a clear picture, but I feel your pain!
If you have a ROM sitting on your phone that you can reflash in recovery, do it. You won't lose any media on your internal memory e.g. pictured, movies. All your app settings will remain if you don't wipe anything in recovery prior to flashing - but in your situation I suggest a full wipe & reset to (hopefully) clear out any problems.
As for upgrading SU, I'm wondering what you mean by two options? Let us know how you get on. Also feel free to PM me if you're truly stuck, I've been there myself and received help that saved me untold stress.
Click to expand...
Click to collapse
When I was welcomed to update supersu, it had a left choice (normal) and a right side choice cwm/twrp (not sure the spelling) I choose the right.
I really want to first thank you so so much.
Which options within the recovery should i choose?
When I did try to repeat the original root process, I got a PIT message that just stayed and did not change. I was on slow machine, but I think it was because the debug usb was off or as i was starting to hear, the partition might be changed in the rooting process? Not sure how that would relate. likely because the debug was off
The pain and fear that broke the phone is really intense. Plus, I use it all the time, before this happened. what information do you need?
Macguyer2000 said:
When I was welcomed to update supersu, it had a left choice (normal) and a right side choice cwm/twrp (not sure the spelling) I choose the right.
I really want to first thank you so so much.
Which options within the recovery should i choose?
When I did try to repeat the original root process, I got a PIT message that just stayed and did not change. I was on slow machine, but I think it was because the debug usb was off or as i was starting to hear, the partition might be changed in the rooting process? Not sure how that would relate. likely because the debug was off
The pain and fear that broke the phone is really intense. Plus, I use it all the time, before this happened. what information do you need?
Click to expand...
Click to collapse
My assumptions are you were successfully rooted, I'm unsure if you are on stock ROM or custom ROM, you updated SU and ended up in bootloop. You are able to get into recovery - do you have a ROM already sitting on your phone, that you can flash/install? If yes, do that. But first, in recovery look for options named factory reset, do that. You suggested you have CWM recovery - there is option to wipe cache, then under advanced option, is wipe dalvik cache, do those. I hope I adequately described the menu structure, my phone is not with me right now to check.
Really, we just want to get you back into a functioning ROM, and stop the bootloops. As for updating SU, I assume you tried updating from recovery? If so, stick to the Play Store updates only.
Again lemme know how you get on, and confirm my assumptions so I can help further if needed.
tweeny80 said:
My assumptions are you were successfully rooted, I'm unsure if you are on stock ROM or custom ROM, you updated SU and ended up in bootloop. You are able to get into recovery - do you have a ROM already sitting on your phone, that you can flash/install? If yes, do that. But first, in recovery look for options named factory reset, do that. You suggested you have CWM recovery - there is option to wipe cache, then under advanced option, is wipe dalvik cache, do those. I hope I adequately described the menu structure, my phone is not with me right now to check.
Really, we just want to get you back into a functioning ROM, and stop the bootloops. As for updating SU, I assume you tried updating from recovery? If so, stick to the Play Store updates only.
Again lemme know how you get on, and confirm my assumptions so I can help further if needed.
Click to expand...
Click to collapse
[If you don't already have it, download and install the Samsung USB Drivers. Now, download and unzip the GalaxyNote2Root.zip file. Open the ODIN program by double-clicking the odin3 v1.85.exe application file.] from the website i followed. with this catchy title:
How to Root Your Samsung Galaxy Note 2 Using ODIN for Windows (So Easy Your Grandma Can Do It)
and it rooted with no problem...just that boot loop the next day when updating supersu...and using the google only site is a good idea.
I am having trouble to get the recovery mode on. I can go into download mode easily, but to go into recovery appears to be a trickier issue. I just can't get it. Can you guide me on this....
Simply reflash rom and reroot again.
Flashing stock rom won't erase data. So if after flashing rom device boot up normally, tour data will be there intact, incase it doesn't boot normally after flashing rom then you may need to wipe it.
Sent from my GT-N7100 using xda premium
Macguyer2000 said:
I just entered the world of a rooted phone, all exciting and new. I used triangle away, and everything is well. I even turned off the debugging mode as i thought i was all done with things rooting and didn't need it.
The next day I realize there is update for supersu, so i accept, if gives me two choices in the update, i choose one, and now my phone is the in GTN7100 loop non stop. Seems of the two options, I choose wrongly. I can put it into download mode. I think I can put it into recovery mode too.
I used this method to boot.
galaxy-note2.wonderhowto.com/how-to/root-your-samsung-galaxy-note-2-using-odin-for-windows-so-easy-your-grandma-can-do-it-0146884
I did perform some basic backups with kies and i believe an app called my backup, so in the worst case, I believe i can recover everything if had to do some kind of reset that would erase all the data. (I am hoping to avoid that, as the recovery may be a learning process if any challenges with it)
its with 4.1.2 and I am not sure if any other details I should provide. so i feel proud i got this far, sad the supersu update made some kind of corruption. i know you guys may be extremely busy and i thank you so much in advance.
Click to expand...
Click to collapse
Just to let you know I have used both sources of available update for super su.
And have never had any problems, I highly doubt your boot loop is anything todo with the su update. The guus on here at xda are superb and will have you back up and running no problem.
GT N7105 with XDA Premium......that is all......
bearusa said:
Just to let you know I have used both sources of available update for super su.
And have never had any problems, I highly doubt your boot loop is anything todo with the su update. The guus on here at xda are superb and will have you back up and running no problem.
GT N7105 with XDA Premium......that is all......
Click to expand...
Click to collapse
thank you for the positive thinking. but I think I have a serious problem here.
I can not get into recovery, as much as i try.
Before all this happened, i unticked usb debug.
I can however get into download mode.
I really feel that i have critically wounded my phone.
Macguyer2000 said:
thank you for the positive thinking. but I think I have a serious problem here.
I can not get into recovery, as much as i try.
Before all this happened, i unticked usb debug.
I can however get into download mode.
I really feel that i have critically wounded my phone.
Click to expand...
Click to collapse
Enter download mode and reflash the recovery using odin. Unticking debug should not put your phone into bootloop neither. . You have to make sure your flashing the correct recovery or rom for your phone model. Depending if you have n7100 or n7105..
GT N7105 with XDA Premium......that is all......
bearusa said:
Enter download mode and reflash the recovery using odin. Unticking debug should not put your phone into bootloop neither. . You have to make sure your flashing the correct recovery or rom for your phone model. Depending if you have n7100 or n7105..
GT N7105 with XDA Premium......that is all......
Click to expand...
Click to collapse
OK, let me make sure I understand correctly..I can put some of my fears/worries to rest.
Let me restate
My situation is a bootloop.
My usb debugging is off. (the day after the rooting, I didn't think I needed it on anymore, as I completed the root)
Later that day, just moment before the loop happened, I was updating SuperSu. (something the phone didn't like)
I found: I can go into download mode. I can not go into recovery mode.
(a phone with a bootloop, usb debugging is off, and download mode is accessible)
So:
(When rooting, I opened Odin, I selected the PDA option, choose the proper file, and pressed start. Yellow changed to Green and we were done)
So Now, I open Odin, select the PDA option, choose the correct file for my phone (GT N7100) from likely the samsung website, I see the Yellow, hit start, yellow turns to green, and we're ok?
That simple thing I said 24 hr ago, still you are here.
It has nothing to do with usb debugging.
If you keep it enable /disable, it won't make any difference in flashing.
Sent from my GT-N7100 using xda premium
Phone is OK now!
dr.ketan said:
That simple thing I said 24 hr ago, still you are here.
It has nothing to do with usb debugging.
If you keep it enable /disable, it won't make any difference in flashing.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I want to say thank you to everyone. I flashed recovery and it told of bad install. I rebooted and everything is FINE!
Thank you so much!

Encrypted on boot with 5.1.1 ROMs

Hey all,
I searched and couldn't find anyone else with this issue, so I thought I'd ask. My phone was stock and unrooted, and I had encrypted it. When the conversion to Developer Edition came out, I converted and wiped the phone. I installed CM 13 and it works well. Whenever I install a 5.1.1 ROM, though, it asks for a password on boot and says it's encrypted. I tried my previous password and it says it is incorrect. I tried doing all options on Advanced Wipe in TWRP, as well as Factory Reset and Format. Reinstalled 5.1.1 ROM and still encrypted. Not sure what else to try.
Any advice would be helpful. Thanks!
Nobody? I'm tearing my hair out here.
What I'm going to suggest is fraught with peril, but...
Try returning to an unrooted, 5.1.1 condition. Use this and flash in Odin. http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224 Wipe everything first including the system.
The peril? This will return your phone to its unrooted condition. Your recovery options will be fewer. But this should return your phone to its out of the box condition.
douger1957 said:
What I'm going to suggest is fraught with peril, but...
Try returning to an unrooted, 5.1.1 condition. Use this and flash in Odin. http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224 Wipe everything first including the system.
The peril? This will return your phone to its unrooted condition. Your recovery options will be fewer. But this should return your phone to its out of the box condition.
Click to expand...
Click to collapse
I really did not want to try this and lose root, so I been holding out. Today I took the plunge - full restore, bootloader locked, root lost, everything wipes. Still encrypted! How is this possible?
Vagabondage80 said:
I really did not want to try this and lose root, so I been holding out. Today I took the plunge - full restore, bootloader locked, root lost, everything wipes. Still encrypted! How is this possible?
Click to expand...
Click to collapse
Dude, I'm sorry.
douger1957 said:
Dude, I'm sorry.
Click to expand...
Click to collapse
Thanks. I may have it now. I just hammered wrong passwords until it did a factory reset. This time it appears to have actually reset it. Won't be sure until I get root again, but it booted.
Vagabondage80 said:
Thanks. I may have it now. I just hammered wrong passwords until it did a factory reset. This time it appears to have actually reset it. Won't be sure until I get root again, but it booted.
Click to expand...
Click to collapse
That was an unique solution. I would have bet anything that doing an ODIN flash would have put the phone in an out of the box condition. Live and learn, I guess. I'm glad it worked out for you.
douger1957 said:
That was an unique solution. I would have bet anything that doing an ODIN flash would have put the phone in an out of the box condition. Live and learn, I guess. I'm glad it worked out for you.
Click to expand...
Click to collapse
Yeah, no idea what could have still been encrypted after that many wipes. Oh well, it seems to be working now.

Categories

Resources