So I did the root keeper wrong and updated, losing root. Anyone else in this club with me? It's only been a few hours and I already miss it.
Atleast I have better pictures though....
Sent from my XT1058 using xda app-developers app
You could reflash the software back to before the update with the KXZ firmware and try the process over again. Depends if the hassle is worth it to you.
http://forum.xda-developers.com/showthread.php?t=2411618
Abyssul said:
You could reflash the software back to before the update with the KXZ firmware and try the process over again. Depends if the hassle is worth it to you.
http://forum.xda-developers.com/showthread.php?t=2411618
Click to expand...
Click to collapse
This process is just flashing the firmware through rsdlite which won't happen because it's a downgrade. I tried.
Sent from my XT1058 using xda app-developers app
Maybe this will work? http://forum.xda-developers.com/showthread.php?p=45955669#post45955669
You can't flash with fastboot? I'm new to the Android ecosystem, but there must be some way to downgrade.
freak4dell said:
Maybe this will work? http://forum.xda-developers.com/showthread.php?p=45955669#post45955669
Click to expand...
Click to collapse
just tried, did not work. fails at the boot.img
Abyssul said:
You can't flash with fastboot? I'm new to the Android ecosystem, but there must be some way to downgrade.
Click to expand...
Click to collapse
first things I tried and doesn't work
I did the update and protected root but my wifi was messed up and wouldn't turn on. I did RSDLite to downgrade and redo it all and it worked fine.
BTW I used this http://forum.xda-developers.com/showthread.php?t=2446515
Some of us didn't want root in the first place! #TeamStockMotoX :silly:
I'm confused as to why someone wouldn't just unlock their bootloader if they are going to be making changes to their system. I understand the warranty issue but who uses that? Most people go through asurion and they won't even notice. Haha
Sent from my Moto X using XDA Premium
eyeisdasteve said:
I'm confused as to why someone wouldn't just unlock their bootloader if they are going to be making changes to their system. I understand the warranty issue but who uses that? Most people go through asurion and they won't even notice. Haha
Sent from my Moto X using XDA Premium
Click to expand...
Click to collapse
Because some of us can't unlock our bootloader.
eyeisdasteve said:
I'm confused as to why someone wouldn't just unlock their bootloader if they are going to be making changes to their system. I understand the warranty issue but who uses that? Most people go through asurion and they won't even notice. Haha
Sent from my Moto X using XDA Premium
Click to expand...
Click to collapse
Just remember that Retail AT&T and Verizon and MotoMaker AT&T variants aren't able to have their boot loaders unlocked
Sent from my XT1058 using Tapatalk 4
Lost root don't care. Motorola got this phone right. I'm good with stock.
rivlez said:
I did the update and protected root but my wifi was messed up and wouldn't turn on. I did RSDLite to downgrade and redo it all and it worked fine.
BTW I used this http://forum.xda-developers.com/showthread.php?t=2446515
Click to expand...
Click to collapse
Your wifi was only screwed up within Recovery mode (write off) correct?
I have a similiar issue. Whether its affecting other things or not, i dont know.
But what do you mean you restored via RSD lite and did it all over again and it was fine?
How did you ujse RSD lite to reflash the firmware since you got the updated OTA, it wont let you downgrade
emerica243 said:
Your wifi was only screwed up within Recovery mode (write off) correct?
I have a similiar issue. Whether its affecting other things or not, i dont know.
But what do you mean you restored via RSD lite and did it all over again and it was fine?
How did you ujse RSD lite to reflash the firmware since you got the updated OTA, it wont let you downgrade
Click to expand...
Click to collapse
My wifi was messed up in any mode. It wouldn't turn on for some reason. I restored the 17.51 firmware after the botched update messed up my wifi and it worked fine and I actually ended up doing it 2 times since a titanium backup messed up my phone. I was definitely on the 17.54 update. It definitely let me downgrade. How would you like me to prove it to you?
my wifi messed up in recovery mode but lte works. Normal mode everything is fine. I am rooted now with latest update.
sravanz said:
my wifi messed up in recovery mode but lte works. Normal mode everything is fine. I am rooted now with latest update.
Click to expand...
Click to collapse
Add me in as another one with no wifi in recovery. Normal mode works just fine as well. Would be nice if there was a fix for this but just glad to still have root with the update.
Rask40 said:
Add me in as another one with no wifi in recovery. Normal mode works just fine as well. Would be nice if there was a fix for this but just glad to still have root with the update.
Click to expand...
Click to collapse
Me too. My wifi is FUBARED in recovery. It's because we don't have the new kernel and to be technical were using the old system/recovery in our "recovery mode" I think that's why it's working in the regular mode and not recovery mode..... Or that's what I understand. Though I'm probably wrong.
When I upgraded I got a failed upgrade after final boot. Although it still says the newest version. I'm tempted to RSD back like some others have just to try but I don't want a paper weight.
Sent from non rooted motoX :'(
gunnyman said:
Lost root don't care. Motorola got this phone right. I'm good with stock.
Click to expand...
Click to collapse
While I'm kind of excited to see SafeStrap out, and updated (fixes phone/data, etc...), I'm still hoping some attempt is in the works for unlock on at&t.
Regardless, there aren't any custom roms to really flash anyways.
Had I an unlocked bootloader, I'd have a custom kernel in the works, and maybe some custom roms with some TeamAcid love.
Come see, come saw... Patience wins all.
Related
Hello,
I have a NEVER ROOTED Motorola Droid Razr M XT709
In the end all I want to do is use my SD card to store app stuff, just the data would be acceptable ( entire thing would be best ). I am figuring I need to root my device to be able to do this but before I did I wanted to make sure I was capable of rooting it and UNrooting it as well. Here is a link to a screen shot from my phone with it's basic specs displayed under Settings > About Phone : https://dl.dropboxusercontent.com/u/16564468/Screenshot_2013-11-23-09-44-00.png
So...
Can I move apps or app data to SD without rooting? If so, how? If not...
Can I root? If so, what would be the safest method?
Can I unroot? If so, what is the safest method?
Thanks!
-Reiz
I hit a button accidentally while playing a game and got an ota. Posted link to new stats after ota
https://www.dropbox.com/s/eo11d9gqkbbltss/2013-11-23 16.20.04.png
Sent from my XT907 using XDA Premium 4 mobile app
Unfortunately, I can't open your links at work, but I did see your first pic last night and on that version, you would have been able to root. If you took the latest update, then you can't root it.
RikRong said:
Unfortunately, I can't open your links at work, but I did see your first pic last night and on that version, you would have been able to root. If you took the latest update, then you can't root it.
Click to expand...
Click to collapse
Is there any way to roll back on the OTA?
Reizvoller said:
Is there any way to roll back on the OTA?
Click to expand...
Click to collapse
Not if your bootloader is locked.
RikRong said:
Not if your bootloader is locked.
Click to expand...
Click to collapse
So essentially, even if I did a 'hard reset' , I am still boned?
Reizvoller said:
So essentially, even if I did a 'hard reset' , I am still boned?
Click to expand...
Click to collapse
I would assume that you're talking about a factory reset? Yes, you are boned, it will only revert back to the latest OTA, which you just did.
Just wondering...
I was about to go through the process when it ocurred to me that the update would be coming AT SOME POINT.
Is there any reason to wait?
I would, and did. To each his own. What do you have?
rdenova said:
I would, and did. To each his own. What do you have?
Click to expand...
Click to collapse
You would and did what? Wait or root?
I have an old school, unrooted 32g Maxx with the last OTA installed (4.4).
Thanks.
Root, for sure. If you're on 19.6.3, you will have to RSD the 19.5.3 image so you can achieve the permanent root with write protect off, then take the OTA up to 19.6.3.
rdenova said:
Root, for sure. If you're on 19.6.3, you will have to RSD the 19.5.3 image so you can achieve the permanent root with write protect off, then take the OTA up to 19.6.3.
Click to expand...
Click to collapse
He is right. Root it because soon you wont have the chance too and will regret it.
I will add, that I started with 19.5.3 and achieved root with WP off. I have not tested the OTA using RSD to go from 19.6.3 back to 19.5.3. I only assume perhaps wrongfully, it will work. I have had no trouble restoring my now debloated stock image from SS. Had the Eclispe ROM in the stock slot, didn't care for it and went back to my image. Root access only tools are cool.:good:
rdenova said:
I will add, that I started with 19.5.3 and achieved root with WP off. I have not tested the OTA using RSD to go from 19.6.3 back to 19.5.3. I only assume perhaps wrongfully, it will work. I have had no trouble restoring my now debloated stock image from SS. Had the Eclispe ROM in the stock slot, didn't care for it and went back to my image. Root access only tools are cool.:good:
Click to expand...
Click to collapse
So did you flash a rom? Sorry if I misread but I thought you had to have unlocked bootloader
Sent from my XT1080 using XDA Free mobile app
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
rdenova said:
I will add, that I started with 19.5.3 and achieved root with WP off. I have not tested the OTA using RSD to go from 19.6.3 back to 19.5.3. I only assume perhaps wrongfully, it will work. I have had no trouble restoring my now debloated stock image from SS. Had the Eclispe ROM in the stock slot, didn't care for it and went back to my image. Root access only tools are cool.:good:
Click to expand...
Click to collapse
RSD lite will work that's what I had to do. It will take about 5-10 minutes and all of your data will be gone but its worth it. Just back everything up
Sent from my XT1080 using XDA Free mobile app
Cgordon17 said:
So did you flash a rom? Sorry if I misread but I thought you had to have unlocked bootloader
Click to expand...
Click to collapse
The unlocked bootloader will allow you to use AOSP ROMs like CyanogenMod however -
Once you have permanent root with WP off - with SafeStrap installed you can backup your stock slot. I was looking around for ROMs for the Maxx and happened to find one for the stock slot, seems you can not install a ROM into any other slot as it just comes up with the belly up android bot. But an Eclipse ROM did install to the stock slot. It wasn't anything like CM and more resembled the stock ROM only somewhat modded. I just didn't care for it and restored my back up. I used ROMToolBox to uninstall the unwanted Verizon and Google stuff and made a new backup.
Bootloader remains locked. Everything works including wifi hotspot, cameras, etc...
"RSD lite will work that's what I had to do. It will take about 5-10 minutes and all of your data will be gone but its worth it. Just back everything up"
Just so you know, there is now a method out that allows you to go back to 19.5.3, root and return to 19.6.3 with full root and write protection off without losing data. I did it last night and everything worked, without losing any data.
rdenova said:
The unlocked bootloader will allow you to use AOSP ROMs like CyanogenMod however -
Once you have permanent root with WP off - with SafeStrap installed you can backup your stock slot. I was looking around for ROMs for the Maxx and happened to find one for the stock slot, seems you can not install a ROM into any other slot as it just comes up with the belly up android bot. But an Eclipse ROM did install to the stock slot. It wasn't anything like CM and more resembled the stock ROM only somewhat modded. I just didn't care for it and restored my back up. I used ROMToolBox to uninstall the unwanted Verizon and Google stuff and made a new backup.
Bootloader remains locked. Everything works including wifi hotspot, cameras, etc...
Click to expand...
Click to collapse
How did you get the WiFi hotspot to work? I think k I already have it after download that Verizon entitlement.apk file and changes some names around but what did you do?
Sent from my XT1080 using XDA Free mobile app
Using the Verizon one from stock 19.6.3. It just works as expected.
rdenova said:
Using the Verizon one from stock 19.6.3. It just works as expected.
Click to expand...
Click to collapse
I have the 19.6.3 update, I'm new to this forum. I believe I have to downgrade to the previous version in order to root and have bootloader unlocked is that correct?
cal4877 said:
I have the 19.6.3 update, I'm new to this forum. I believe I have to downgrade to the previous version in order to root and have bootloader unlocked is that correct?
Click to expand...
Click to collapse
Yes correct
Sent from my XT1080 using XDA Free mobile app
Cgordon17 said:
Yes correct
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Is there a way to unlock our bootloader not buying the unlock code via ebay?
Enviado desde mi MB520 usando Tapatalk 2
josuearisty said:
Is there a way to unlock our bootloader not buying the unlock code via ebay?
Enviado desde mi MB520 usando Tapatalk 2
Click to expand...
Click to collapse
No
Sent From My Droid Ultra
cal4877 said:
I have the 19.6.3 update, I'm new to this forum. I believe I have to downgrade to the previous version in order to root and have bootloader unlocked is that correct?
Click to expand...
Click to collapse
If you have the 19.6.3 version, you can revert back to the 19.5.3 and ONLY 19.5.3 update. This can be done using House of Moto if you wish to keep your data. Once on 19.5.3, root is possible. Correct me if I'm wrong, but you are able to go back to previous system versions (i.e. 19.6.3 -> 19.5.3) as long as it is the same version of android (i.e. 4.4 -> 4.4).
For bootloader unlock, the only way to go about that is through the Chinese vendor. This can be done for any system version.
rds217 said:
@Cgordon17 that is not correct. If you have the 19.6.3 version, you can revert back to the 19.5.3 and ONLY 19.5.3 update. This can be done using House of Moto if you wish to keep your data. Correct me if I'm wrong, but you are able to go back to previous system versions (i.e. 19.6.3 -> 19.5.3) as long as it is the same version of android (i.e. 4.4 -> 4.4).
Click to expand...
Click to collapse
I never said anything about downgrading further. He asked if he had to downgrade to root and I said yes. That's all I don't the furthest you can go is 19.5.3
Sent from my XT1080 using XDA Free mobile app
Cgordon17 said:
I never said anything about downgrading further. He asked if he had to downgrade to root and I said yes. That's all I don't the furthest you can go is 19.5.3
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
I know it's out there but not sure where to look.
Can anyone link the steps to take to root without losing data?
Thanks so much.
Cgordon17 said:
I never said anything about downgrading further. He asked if he had to downgrade to root and I said yes. That's all I don't the furthest you can go is 19.5.3
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, sorry about that. I misread the original quote and thought you were saying a downgrade is required for bootloader unlock.
redddog said:
I know it's out there but not sure where to look.
Can anyone link the steps to take to root without losing data?
Thanks so much.
Click to expand...
Click to collapse
Sure: http://forum.xda-developers.com/showpost.php?p=53189750&postcount=26
I just got an invite from moto to test software. I didn't because I'm unlocked and rooted.
Sent from my unlocked consumer edition Motorola Droid Maxx xt1080m.
So, I was going to use Cf-Auroroot like I have for every other Samsung device I've got but apparently there's an issue with it for the N915G.
What I did was put the latest super su file (i used v2.40) on my external SD card and then in Odin flash the latest TWRP recovery from here - http://forum.xda-developers.com/note-edge/general/easy-steps-stock-odin-n915tuvu1anjl-sm-t2943993 (you can also use the sd card fix from here too, flash in TWRP, just install supersu, then add another flash file and install the sd card fix).
Go to recovery mode and flash super su.
I found it had an error flashing cache but a factory reset fixed this so best done BEFORE setting everything up.
Let phone reset, set it up and you now have root access with a clean install of stock rom.
Happy days.
This worked fine for me and left out the step of flashing CF-Autoroot which wasn't needed.
You will still trip Knox.
I don't know if this will work flawlessly for you or for all models, especially if the bootloader is locked, but theoretically it should.
Good luck guys, happy flashing.
And HAPPY NEW YEAR...:laugh:
Root for Lollipop
Thanks I have the 915g also and I used your method for Kitkat it worked flawlessly thank you I want to install lollipop now and I want to root again what method do I use and could you point me in the right direction please
jdoogzie said:
Thanks I have the 915g also and I used your method for Kitkat it worked flawlessly thank you I want to install lollipop now and I want to root again what method do I use and could you point me in the right direction please
Click to expand...
Click to collapse
Exactly the same method... I believe Twrp 2.8.5.0 and Supersu 2.4.6 were what I used to root Lollipop...
jdoogzie said:
Thanks I have the 915g also and I used your method for Kitkat it worked flawlessly thank you I want to install lollipop now and I want to root again what method do I use and could you point me in the right direction please
Click to expand...
Click to collapse
Is this for G version? Didnt work for me
pride_kr said:
Is this for G version? Didnt work for me
Click to expand...
Click to collapse
It seems to work on most variants, except those with locked bootloaders..
If it didn't I don't know why.
A lot of people have rooted their device this way....
ultramag69 said:
It seems to work on most variants, except those with locked bootloaders..
If it didn't I don't know why.
A lot of people have rooted their device this way....
Click to expand...
Click to collapse
I tried all methods described in these fóruns... Always giving fail message in Odin.... And authentication error on download mode
Try to see if you have untick the reactivation lock. Its under setting and security.
Sent from my SM-N915G using XDA Free mobile app
kuailan said:
Try to see if you have untick the reactivation lock. Its under setting and security.
Sent from my SM-N915G using XDA Free mobile app
Click to expand...
Click to collapse
Yes, it really was reactivation lock issue! Thanks!
But already went back to 4.4.4.... too many freezes, fc, on 5.0.1
pride_kr said:
Yes, it really was reactivation lock issue! Thanks!
But already went back to 4.4.4.... too many freezes, fc, on 5.0.1
Click to expand...
Click to collapse
You should not have many issues with 5.0.1. What you need to do after flashing the 5.0.1...you need to reset to factory setting. Im sure by now you know when upgrading..you still keep data from the kitkat. This may cause conflict and issues. At the moment the only issue i had is sometime i get that contact closed notifications. I have google this issue...seem like it happen to other phones to with early 5.0.1. For me im ok...cause it only happen very rarely...i hope a much later lollipop will fix this issues.
Sent from my SM-N915G using XDA Free mobile app
kuailan said:
You should not have many issues with 5.0.1. What you need to do after flashing the 5.0.1...you need to reset to factory setting. Im sure by now you know when upgrading..you still keep data from the kitkat. This may cause conflict and issues. At the moment the only issue i had is sometime i get that contact closed notifications. I have google this issue...seem like it happen to other phones to with early 5.0.1. For me im ok...cause it only happen very rarely...i hope a much later lollipop will fix this issues.
Sent from my SM-N915G using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, that really makes sense... upgrading, and old data coming along... didnt think about that.... without xposed though..... not sure if Ill try it again!
I am interested in buying SM-N915G. does it have unlocked bootloader? if not, can it be unlocked? Appreciate advice.
Agent5150 said:
I am interested in buying SM-N915G. does it have unlocked bootloader? if not, can it be unlocked? Appreciate advice.
Click to expand...
Click to collapse
Aussie 915G is unlocked. As far as I know so are all others...
Mentioned locked bootloaders as this will work on other models too...
Got my SM-915G, and got it rooted and TWRP installed following you method. It is working with AT&T and I am getting LTE data speeds, but it is struggling on voice network. hardly any bars are visible on the signal strength icon.
Is there any solution?
Agent5150 said:
Got my SM-915G, and got it rooted and TWRP installed following you method. It is working with AT&T and I am getting LTE data speeds, but it is struggling on voice network. hardly any bars are visible on the signal strength icon.
Is there any solution?
Click to expand...
Click to collapse
Possibly flashing the modem and non-HLOS.bin for AT&T.
I can't really say as I live in Oz and have no problems with voice calls...
I do find that my bars don't tend to go over 3 or more than halfway but that could be due to where I live and the crappy coverage we get here... No problem with voice calls though...
I am not sure if I can install SM-N915A modem on 915G.
Can someone confirm if that is possible, if so, what version?
tell me one thing is xposed framework and freedom app now working on note edge 915G lollipop
Nope. Better stick with Kitkat if you intend to use Freedom and Xposed.
This method trips knox?
Greenarcher707 said:
This method trips knox?
Click to expand...
Click to collapse
Yes
Oh well, no way around it then. Warranty is for the timid anyway lol. Gotta pay to play.
So i recently updated to the new mhc19l version on my nexus 6p (this is not android N, just the latest android update for the 6p). I did it via the flashfire method following this youtube video: https://www.youtube.com/watch?v=cvs0JQswTWw&feature=youtu.be
I dont have multirom so i didnt do the stuff it mentioned about that. At first I thought I was successful and everything was working great. I reflashed xposed to the latest version, and updated my elemental X kernal too.
But now when I do anything with the camera the phone gets really weird. Post reboot the camera preview will work only once. If I take a photo it crashes. And every time I try to do anything with the camera involved the thing will crash and not even load preview anymore. That includes 3rd party apps like snap chat. Also I can't edit quick setting tiles in system ui as it tells me system ui tuner has crashed, but that i can live with. The camera issues I can not live with.
None of that happens with my rooted 6p on the same build. I think you need to look at xposed, the kernel changes and all the other jiggerypokery you've done. I'd do begin by reflashing the factory image and do this manually either using Heisenberg's extremely clear guide, or by the flash-all.bat command that google supplies in the factory build. Then you can check camera, flash recovery (again, using Heisenberg's guide, it takes but a couple of commands), then root, add xposed, kernels and all that special sauce. Do it step by step, then you'll know when something goes wrong and only have to fix that.
Thank you for your help. I'll check that out. Do you think it may be because I updated from a pretty old build? (808L) I skipped a few updates and went right to the latest one, could that cause any problems?
Not really. I think it's because you've done too much using a tool and without checking things after each step. Stop using tools like flashfire when you don't understand what they do and get yourself up to speed with using the commands. After that, you'll spot where things have gone wrong and be able to fix or troubleshoot it within the community. No one can help you when it's an issue that could caused by one or more of a hundred things you've tinkered with.
It's not hard and worth the little bit of busy work and brain thought. You'll enjoy it!
Yea I like to tinker and stuff. It's just the customizations with dashclock and stuff that I don't want to lose. But I did app backups so hopefully I won't.
Something probably went wrong during the flash process. I highly doubt xposed or kernel modifications are to blame. I keep 12 xposed modules running at all times with kylo kernel which I have heavily modified with EX kernel app. Read Heisenberg's guide and learn to flash images properly and you should be good to go.
Before I do any reflashing today can anyone do me a favour and upload their camera APK?
Im just hoping it has something to do with that. Last ditch effort.
And thanks for the help guys
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
and313 said:
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You can't flash anything with a locked bl. Locking the BL is nothing but trouble if you like to tinker.
Sent from my Nexus 6P using Tapatalk
and313 said:
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
dirtyuzbek said:
Before I do any reflashing today can anyone do me a favour and upload their camera APK?
Im just hoping it has something to do with that. Last ditch effort.
And thanks for the help guys
Click to expand...
Click to collapse
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Any Advice ?
Heisenberg said:
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Click to expand...
Click to collapse
Hello you seem very knowledgeable on the subject. I just picked up a 6P and was wondering how does encryption affect things such as TWRP and root. Do you advise to disable encryption on the device for ease-of-use in TWRP and root.
naruto.ninjakid said:
Hello you seem very knowledgeable on the subject. I just picked up a 6P and was wondering how does encryption affect things such as TWRP and root. Do you advise to disable encryption on the device for ease-of-use in TWRP and root.
Click to expand...
Click to collapse
Look at my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Deception isn't necessary anymore, as long as you use the latest TWRP you should have no problems.
did it flash the vendor?
Heisenberg said:
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Click to expand...
Click to collapse
Wait.. If the bootloader is locked and a ota fails you cant oem unlock it?
Sent from my Nexus 6P using Tapatalk
and313 said:
Wait.. If the bootloader is locked and a ota fails you cant oem unlock it?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, because if the OTA fails you won't have access to the option in Developer Options to enable OEM unlocking. Trust me, you want to have that bootloader unlocked. You don't wanna end up like the other guys who had to send their phone back for repair because they locked it.
Heisenberg said:
No, because if the OTA fails you won't have access to the option in Developer Options to enable OEM unlocking. Trust me, you want to have that bootloader unlocked. You don't wanna end up like the other guys who had to send their phone back for repair because they locked it.
Click to expand...
Click to collapse
Right... I did not think that the first step (enable bootloader unlock from dev options) is actually necessary.
Sent from my Nexus 6P using Tapatalk
Does anyone know to unroot it and go back to stock?
My speaker got broken. I need to send phone for replacement. Im not lucky one
thank you so much for help
Find the stock tot for your model and flash it-that should return you to stock unrooted.
wyvernwaddell said:
Find the stock tot for your model and flash it-that should return you to stock unrooted.
Click to expand...
Click to collapse
As far as I know tot file flashing doesnt work because dll's files are missing.
netgar said:
As far as I know tot file flashing doesnt work because dll's files are missing.
Click to expand...
Click to collapse
My bad- you're right! Sorry about the bad info..won't happen again.
wyvernwaddell said:
Find the stock tot for your model and flash it-that should return you to stock unrooted.
Click to expand...
Click to collapse
netgar said:
As far as I know tot file flashing doesnt work because dll's files are missing.
Click to expand...
Click to collapse
wyvernwaddell said:
My bad- you're right! Sorry about the bad info..won't happen again.
Click to expand...
Click to collapse
No harm,no foul,we've all done similar on at least one occasion.
You're a good man for offering to help ! :good:
Any help with that?
I am also awaiting an answer.
My last 2 Samsung phones had issues and I needed to Odin back to stock for warranty exchange at T-Mobile.
So I'm holding off on rooting till we have something of the sort for the v20.
Using Odin to flash my s7e back to stock while having severe screen issues saved my butt.
I'm on JoD for reference, and needed to switch phones at a brick and mortar.
Side note : loving the blooming development for this device.
Thanks for that, all parties concerned.
Sent from my LG-H918 using Tapatalk
I believe in jcadduono root thread he says you can relock bootloader and flash his stock imgs in Twrp to be back on stock
kelvin216 said:
I believe in jcadduono root thread he says you can relock bootloader and flash his stock imgs in Twrp to be back on stock
Click to expand...
Click to collapse
Thank you
I will try to find it.
Nice people gave me an answer: http://forum.xda-developers.com/showpost.php?p=69824782&postcount=1007
Sound very complicated for newbie. Anyone can try it?
I made an easy to understand guide to do just this.
http://forum.xda-developers.com/v20/how-to/restore-h918-to-100-stock-requires-twrp-t3504798
Vuciz said:
I made an easy to understand guide to do just this.
http://forum.xda-developers.com/v20/how-to/restore-h918-to-100-stock-requires-twrp-t3504798
Click to expand...
Click to collapse
Does this unroot method work for the sprint variant? I am stock unrooted on the build the phone came out of the box with, and waiting until rooting isn't a one-way street to take the plunge. If it does, are you 100% certain that it had been used in sprint v20s successfully?
That thread specifically says H918. So no.
tooandrew said:
Does this unroot method work for the sprint variant? I am stock unrooted on the build the phone came out of the box with, and waiting until rooting isn't a one-way street to take the plunge. If it does, are you 100% certain that it had been used in sprint v20s successfully?
Click to expand...
Click to collapse
You are in the exact same position as me. I'm excited that we have an unlocked bootloader and root for the Sprint variant, but I have no desire to do anything until there's an established procedure to unroot and revert back to stock.
MidwestDrummer said:
You are in the exact same position as me. I'm excited that we have an unlocked bootloader and root for the Sprint variant, but I have no desire to do anything until there's an established procedure to unroot and revert back to stock.
Click to expand...
Click to collapse
Here's hoping it's taken care of. Sprint didn't used to be such a **** when it came to bootloaders. Anyways, I appreciate all the hard work the devs have been doing. Can't wait until I get the chance to experience it. With a stable 200mhz overclock, there's no functional difference between the snapdragon 820 and the snapdragon 821.
Do any of the posted methods work to restore the VS995 variant to stock?
I really want to go ahead and root it (and yes, have disabled updates so still run 12A since I knew VZW was going to be evil and patch it) but I'm very hesitant to do so without a way to restore to stock. Is it one of those things that's just a matter of time, or is there a substantial likelihood it may never be possible?