Ok, I know there are a lot of posts already on updating to 2.3.6 and root, but there appears to be a lot of different situations and limited information that is causing me some confusion.
So, what I want to do is get some clear details about probably the second most common situation: A Motorola Atrix 4G running the stock ROM with root access and an unlocked bootloader.
With regards to updating, aside from the obvious actions (i.e. TiBu, maybe a Nandroid), is there anything else that needs to be done to perform the update?
Additionally, I would like to keep root/unlocked even with the update, but I am willing to re-do root after the update. I can't find clear information on what methods work to keep root or to restore root after updating.
That is pretty much all that I am trying to do. I can not afford to brick my phone, so I want to make sure that I understand everything before I update.
P.S. Curse Motorola and it's stupid locked bootloaders!
I'm in the same shoes and looking to do the same thing...I want to keep root, not brick my phone...Apply the 141 update. I don't mind a little work (re-root, re-modify some files)
I'm running an unlocked bootloader, AT&T Atrix with 4.5.91 which is rooted with some custom changes (tethering, 2g/3g toggle, unlock APNs, agps)
Seems it could be possible to rebuild Blur_Version_91.4.5.141.MB860ATT.en.US available from Motorola and exclude the bootloader portions to keep the phone from bricking?
psychephylax said:
I'm in the same shoes and looking to do the same thing...I want to keep root, not brick my phone...Apply the 141 update. I don't mind a little work (re-root, re-modify some files)
I'm running an unlocked bootloader, AT&T Atrix with 4.5.91 which is rooted with some custom changes (tethering, 2g/3g toggle, unlock APNs, agps)
Click to expand...
Click to collapse
Yeah, I used the script that applied the tethering/hotspot tweak. That's about it. I haven't had to use any agps or anything, it's got amazing gps as it is.
Glad I'm not the only one though
If you have a stock rom unlocked bootloader with root don't do the ota update.I just soft bricked my phone.
Sadly, I did just that. I just wasn't paying attention.
Update: resorted to a factory reset. Now I have 2.3.6 running. Just going to take some time to restore my apps and settings.
Looks like I'm in the same boat. What's the best way to recover from a soft-brick in this situation?
thatguy193 said:
If you have a stock rom unlocked bootloader with root don't do the ota update.I just soft bricked my phone.
Click to expand...
Click to collapse
Yeah, this is exactly why I have asked. I read at least one post somewhere where someone tried both the SD Card and the OTA update and the SD didn't work, but the 2nd OTA try did. I don't know if they said they had unlocked or not.
Johnston212 said:
Yeah, this is exactly why I have asked. I read at least one post somewhere where someone tried both the SD Card and the OTA update and the SD didn't work, but the 2nd OTA try did. I don't know if they said they had unlocked or not.
Click to expand...
Click to collapse
Well I found this threadhttp://forum.xda-developers.com/showthread.php?t=1498856 was trying the auto updater as suggested but my phone wont stay on long enough for it to work.It does the auto shutdown and tries re-installing the OTA update which gives me the android triangle guy.
I recently made an update of my Atrix 4G's System from 2.3.4 to 2.3.6.
My 2.3.4 version was unlocked and rooted. It is on ATT.
Initially I received a notification in my phone about the new System update available. I tried three times OTA, but each time the process failed. When it was booting up always gave me the Android Icon with an Exclamation mark inside of a triangle. But nothing else happens. My phone continued working but with the 2.3.4 version.
Then I went to this page:
Because I haven't less than 8 post in this site I can't post any URL.
But, go for the "Motorola software update" in the Motorola's web page or Google it and get it.
And installed the "Motorola Software update" application. I had to restart my PC in order to make the software to recognize and connect to my Atrix 4G. When the Atrix was connected, by USB port, I had to select the "Windows media Sync" in the USB connection options list to make the connection to work.
Then, all that I had to do was wait until the process got completed.
I hadn't see nothing different with the new update.
I conserved my "unlocked" condition but I lost my "Rooted" condition. But that is not a big issue, there are several thread in the web that help you to get rooted again.
Hope this can help, It works for me.
cjfermin said:
I conserved my "unlocked" condition but I lost my "Rooted" condition. But that is not a big issue, there are several thread in the web that help you to get rooted again.
Hope this can help, It works for me.
Click to expand...
Click to collapse
You have an unlocked bootloader? Or sim-unlocked phone?
I'm in the same situation of @cjfermin and the 2.3.6 was flashed without any problem.
Of course I've lost ROOT, but I've followed simple instructions on the web (using Fasboot) and I've re-rooted the Atrix in 3 minutes.
PS: my Atrix was/is sim-unlocked and with unlocked bootloader.
emandt said:
I'm in the same situation of @cjfermin and the 2.3.6 was flashed without any problem.
Of course I've lost ROOT, but I've followed simple instructions on the web (using Fasboot) and I've re-rooted the Atrix in 3 minutes.
PS: my Atrix was/is sim-unlocked and with unlocked bootloader.
Click to expand...
Click to collapse
Thanks, that is exactly what I was needing to find out. I've heard yes and no's on different re-rooting methods. Could you link the one that you used? I was thinking about using Gingerbreak or OneClickRoot
I was trying to apply the OTA 4.5.141, on my rooted AT&T Motorola Atrix stock rom 2.3.4 and after the first reboot, following the instructions from the update, I am getting the message “failed to boot 2 starting rds mode” and just sit there. After removing the battery and booting up again, the phone seems to booting up normally and then when the phone finishes loading most of the widgets, I get a message saying “turning off” and the same cycle keeps repeating.
This is my primary phone and I am really desperate right now and I do not know what to do.
Please I need some help,
Johnston212 said:
Could you link the one that you used?
Click to expand...
Click to collapse
Here: http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
Hope that helps you!
Alverik said:
I was trying to apply the OTA 4.5.141, on my rooted AT&T Motorola Atrix stock rom 2.3.4 and after the first reboot, following the instructions from the update, I am getting the message “failed to boot 2 starting rds mode” and just sit there. After removing the battery and booting up again, the phone seems to booting up normally and then when the phone finishes loading most of the widgets, I get a message saying “turning off” and the same cycle keeps repeating.
This is my primary phone and I am really desperate right now and I do not know what to do.
Please I need some help,
Click to expand...
Click to collapse
Ok, is your bootloader unlocked as well? I googled the "failed to boot 2 starting RSD mode" that you mentioned and there are a number of posts on it from over the years. It seems that you may need to flash a SBF file, but I don't know enough about your situation to competently tell you more than that.
Johnston212 said:
Ok, is your bootloader unlocked as well? I googled the "failed to boot 2 starting RSD mode" that you mentioned and there are a number of posts on it from over the years. It seems that you may need to flash a SBF file, but I don't know enough about your situation to competently tell you more than that.
Click to expand...
Click to collapse
I am on stock rom 2.3.4 and have only rooted my phone nothing else. It seems that because it was a rooted phone the update could not finish the process.
Now I don’t know what to do.
Should I try to flash to 2.3.4 using RDS lite and then update using OTA 4.5.141 or flash using 4.5.141 (I don’t know where to find it)?
Help please, this is my only phone.
Alverik said:
I am on stock rom 2.3.4 and have only rooted my phone nothing else. It seems that because it was a rooted phone the update could not finish the process.
Now I don’t know what to do.
Should I try to flash to 2.3.4 using RDS lite and then update using OTA 4.5.141 or flash using 4.5.141 (I don’t know where to find it)?
Help please, this is my only phone.
Click to expand...
Click to collapse
If the only thing you've ever done to the phone is root then flashing the official 2.3.4 (not fruitcake) with RSDlite and then applying the 141 OTA update should be ok. Things to note:
1) Make sure the phone is fully charged
2) Apply the 141 OTA update from sd card. Go to motorola's website . I've had mixed results when applying previous updates when downloading over wifi.
3) Be VERY sure you've done nothing else to your phone other than root, i.e. unlock, mess with the bootloader and/or recovery (unlock, ROMs).
gnahc79 said:
If the only thing you've ever done to the phone is root then flashing the official 2.3.4 (not fruitcake) with RSDlite and then applying the 141 OTA update should be ok. Things to note:
1) Make sure the phone is fully charged
2) Apply the 141 OTA update from sd card. Go to motorola's website . I've had mixed results when applying previous updates when downloading over wifi.
3) Be VERY sure you've done nothing else to your phone other than root, i.e. unlock, mess with the bootloader and/or recovery (unlock, ROMs).
Click to expand...
Click to collapse
The only thing that I have done other than rooting my phone it’s unlocking the sim card.
I don't have a SIM unlocked phone, so I can't with 100% certainty say you will be ok. You should be fine though. Maybe others with SIM unlocked phones will chime in.
gnahc79 said:
I don't have a SIM unlocked phone, so I can't with 100% certainty say you will be ok. You should be fine though. Maybe others with SIM unlocked phones will chime in.
Click to expand...
Click to collapse
I am not able to copy the update file to the SD card because I get a message saying “turning off” a little bit after the phone loads the sd card and then I get the "failed to boot 2 starting RSD mode" and after that the only way to take it out of that mode, it’s by removing the battery.
What options do I have now?
Thank you,
Related
After some fighting I managed to convince my phone to redownload the ota(had to delete old zip and clear data on the htcdm service, then the "check new" option started working again). I accepted the update, it downloaded. There was a loud ding and then nothing, phone still on, no prompts, no reboot, no nothing. Ideas? Could it be something that was frozen by the cleantool?
I'm sure the reason why nobody has replied is because you didnt use the search at all..go to the front page and look for OTA and you will be on the right track....
Are you stock or rooted? If your rooted then this problem is normal..even if you did get a prompt and somehow managed to get into recovery then you would get an error..if your stock then I'm not sure what's wrong..either way there is a stock rooted Rom with the update out already and I'm sure other rims will incorporate the update also.
I've used the search and so far have yet to see anyone with the exact same problem. Have you seen something I haven't?
I'm stock (no rom at all), rooted, default recovery
esheesle said:
I've used the search and so far have yet to see anyone with the exact same problem. Have you seen something I haven't?
I'm stock (no rom at all), rooted, default recovery
Click to expand...
Click to collapse
lock your bootloader my friend.
fastboot oem relock
then you can unlock it again after..
So if the bootloader is unlocked it won't even reboot to try the update?
It's weird cause read postings here saying people are rooted and unlocked and still install just fine. So what's the actual truth?
In fact right in this thread someone says they didn't lose lock(as in never relocked seemingly):
http://forum.xda-developers.com/showthread.php?t=1466474&page=10
My theory is that some service disabled by Cleantool may be required for this update to get started, but just a theory. Has anyone who completely debloated run this successfully yet?
Love to hear other theories though.
Question
I know the original unlock was a hard reset to the phone.
Do subsequent RELOCK and UNLOCK do the same thing?
andybones said:
lock your bootloader my friend.
fastboot oem relock
then you can unlock it again after..
Click to expand...
Click to collapse
That would be a great fix IF it worked for all Rezounds....
Unfortunately, it doesn't. My buddies phone was also unlocked thru HTCDEV and rooted and the update sailed right thru for him.....not for me though
xbxjunkie said:
That would be a great fix IF it worked for all Rezounds....
Unfortunately, it doesn't. My buddies phone was also unlocked thru HTCDEV and rooted and the update sailed right thru for him.....not for me though
Click to expand...
Click to collapse
What happened with yours? I just tried unfreezing some stuff and going to try installing after work. What was the difference between you and your friends phones? Bloat removal, etc?
esheesle said:
What happened with yours? I just tried unfreezing some stuff and going to try installing after work.
Click to expand...
Click to collapse
I can download the update, but during the attempted install I get the red triangle and I gotta pull the battery. I unfroze all my bloatware from rom toolbox and tried again....nope. I did a backup, and tried a factory reset....nope again.
xbxjunkie said:
I can download the update, but during the attempted install I get the red triangle and I gotta pull the battery. I unfroze all my bloatware from rom toolbox and tried again....nope. I did a backup, and tried a factory reset....nope again.
Click to expand...
Click to collapse
At least you are getting to the reboot. Mine doesn't even reboot, just downloads and then beeps at me, then nothing.
jdmba said:
I know the original unlock was a hard reset to the phone.
Do subsequent RELOCK and UNLOCK do the same thing?
Click to expand...
Click to collapse
I was messing with this earlier today. I reengaged the lock and then my phone would only load hboot. I eventually gave up and reran the unlock process, which unfortunately did wipe out all of my data. Thank goodness for AM and my nandroid from last night!
I have the same problem as well. I am stock, no root but I have used CleanTool to get rid of bloat. I have downloaded the update atleast 10 times and it has never done anything. Just dings at me, I click OK and no reboot, nothing. Not sure what is up.
EDIT: I used the CleanTool again and temp rooted and restored all the bloat, option 5 I believe and now it is taking the update.
Radiman said:
I have downloaded the update at least 10 times and it has never done anything. I click OK and no reboot, nothing. Not sure what is up.
Click to expand...
Click to collapse
X2 no luck
RustyNailz said:
I was messing with this earlier today. I reengaged the lock and then my phone would only load hboot. I eventually gave up and reran the unlock process, which unfortunately did wipe out all of my data. Thank goodness for AM and my nandroid from last night!
Click to expand...
Click to collapse
I had the same issue , drove me batty, i thought maybe i left a ph98zip on my card. Took the card out and still wouldn't reboot. I just said screw it and tried the RUU through fastboot and it worked ! Then I just downloaded the update and unlocked again and rerooted. I did lose data on internal SD also lol.. I am a noob to Titanium backup and when I redownloaded it couldn't figure out why all my apps were gone..
Or you guys could just download cons rom with the updates in it...
Someone will extract it soon and make a flashable zip
Did any one figure out how to get the OTA to Re-download?
Did any one figure out how to get the OTA to Re-download? Mine downloaded, gave the option to install, said battery to low and try with charged battery. Didn't realize that it was downloading or I would have made sure the battery was fully charged. It has not given me another prompt to install. How do you get to download again? Just deleting the OTApkg.zip will not do it. What other file needs deleting or?
Hi all,
My AT&T Atrix is running 4.5.91. I unrooted it to update to 4.5.141 OTA (I understood it was risky to do an OTA update while rooted).
After I finished downloading the update, I started installing but during installation, the package icon changed to a warning icon (with no error message) and the phone rebooted on 4.5.91 with a message saying the update failed
I think the package may have been corrupted in the download as it was interrupted. Although, I did try this 3 times (redownloading each time)
Any tips?
Thanks
You must have frozen and/or deleted some Blur apps as well as being rooted. Unless you have all the stock files from the firmware you are updating from, the install will fail.
I have unrooted the phone
However, I did use the "integrate system apps updates into ROM" option on TB.
I did not freeze anything
Will this work:
http://www.motorola.com/Support/US-EN/Atrix+Upgrade/Atrix-Gingerbread-Update
If not, what must I do?
Edit: Oh, and I also have AdFree installed and enabled. Should I revert?
mickeycohen said:
I have unrooted the phone
However, I did use the "integrate system apps updates into ROM" option on TB.
I did not freeze anything
Will this work:
http://www.motorola.com/Support/US-EN/Atrix+Upgrade/Atrix-Gingerbread-Update
If not, what must I do?
Edit: Oh, and I also have AdFree installed and enabled. Should I revert?
Click to expand...
Click to collapse
The sd card method will fail for you as well. Undo everything that required root access, including adfree...not sure if it will restore the modified files back to stock though, never used that app.
Exactly what happened to me. Successfully updated using Motorola Software Update
Hi
You have succeeded?
I am stuck for months trying to do this update...
It's absolutely frustrating...
I actually stopped trying. I got a RAZR a few weeks after I started this thread...
I might unlock the BL and install some ROMs to play with the Atrix but basically I don't use it anymore...
Anyway, I think the problem I was having was because I integrated updates into the ROM and I don't think it can be undone
Bootloader Unlocked?
If your bootloader is unlocked the update will most likely not work. Regardless, the link below has some useful information.
http://forum.xda-developers.com/showthread.php?t=1501532
I am currently using Motorola Atrix 4G, OS 2.3.4, system version 4.5.91. I have done two modifications on my handset
(i) rooted using moto-fastboot flash preinstall preinstall.img
(http://www.digitaltweaker.com/andro...t-motorola-atrix-4-5-91-on-gingerbread-2-3-4/)
(ii) Updated radio baseband version from 1.77.30 to 1.87 (flashing with RSDLite)
(http://forum.xda-developers.com/showthread.php?t=1052914)
Now I tried to update my phone to 4.5.141. I used both the method provided by Motorola. Using OTA and from sdcard. Updates ended with one triangle during the process, and when I rebooted it says Update failed. Then I tried through Motorola Software update, but it says "There is no update for this device. Try it later on."
I went through the different posts here and came to know the possibilities of bricking the phone in updating a rooted phone.
I spent lots of time for unrooting the device, updating to 4.5.91 but I didn't get any convenient and helpful topic.
Can someone let me know,
(i) How can I unroot first (I went through aroot script method, but I didn't feel comfortable with that method)
(ii) how can I update it safely without bricking my phone. I want to avoid flashing with ROM.
Waiting for someones response.
I am pretty sure you can use petes one click root to undo your root or maybe even super oneclick
http://forum.xda-developers.com/showthread.php?t=1154600&highlight=how+to+root+internation+atrix
that thread has a how to root with petes one click and i am positive that it has a un root option to it as well
Pbwizkid said:
I am pretty sure you can use petes one click root to undo your root or maybe even super oneclick
http://forum.xda-developers.com/showthread.php?t=1154600&highlight=how+to+root+internation+atrix
that thread has a how to root with petes one click and i am positive that it has a un root option to it as well
Click to expand...
Click to collapse
Thanks for your response. I have not used super oneclick method for rooting my device. So will it be safe. Any way will have a try and let you know.
Try this:
Put update file on SD card, named update.zip
Put phone in recovery mode
select update from sd card
Choose the udpate.zip file
Watch the process to determine what error stops the process. In my case, I had removed a file the update process was looking for.
CAREFUL
I was rooted. I hid the root using a tool on the market. After the update all seemed fine. But it BROKE my wifi. Now wifi disconnects every 20 minutes or so. I dont think this is related to the fact I was rooted since the same thing happened to many people and the update did nothing noteable that I can see. If I had it to do over again, I would skip the update since the phone worked perfectly before the update. There are several threads here and on the motorola forum about the wifi breaking. I have tried all of the suggested fixes but nothing has worked. I have been a member here a long time with many phones. There are more stories about people breaking their Atrix than any other phone. Anyway, its a fact the update broke a lot of phones, even phones that had no mods whatsoever. Be cautious. Supposedly the engineers at Motorola are looking at this for a possible fix but nothing is guaranteed.
dratsablive said:
Try this:
Put update file on SD card, named update.zip
Put phone in recovery mode
select update from sd card
Choose the udpate.zip file
Watch the process to determine what error stops the process. In my case, I had removed a file the update process was looking for.
Click to expand...
Click to collapse
Thanks for the guide. Is this safe to do.
panflute said:
I was rooted. I hid the root using a tool on the market. After the update all seemed fine. But it BROKE my wifi. Now wifi disconnects every 20 minutes or so. I dont think this is related to the fact I was rooted since the same thing happened to many people and the update did nothing noteable that I can see. If I had it to do over again, I would skip the update since the phone worked perfectly before the update. There are several threads here and on the motorola forum about the wifi breaking. I have tried all of the suggested fixes but nothing has worked. I have been a member here a long time with many phones. There are more stories about people breaking their Atrix than any other phone. Anyway, its a fact the update broke a lot of phones, even phones that had no mods whatsoever. Be cautious. Supposedly the engineers at Motorola are looking at this for a possible fix but nothing is guaranteed.
Click to expand...
Click to collapse
Thanks for your valuable suggestion. You are right that now it's working like a charm and I don't want to do experiment on my phone unless I get some safest alternative. I will consider your points before doing anything to my Phone. Thanks again.
I'm new to developing and not too experienced. I attempted to root my phone, but was only successful with unlocking the Boot loader. When I attempted to download the new Kit-Kat update, my phone encountered a Firmware upgrade issue. Now in recovery mode, Kies 3 fails to connect nor recognize my phone.
cfales25 said:
I'm new to developing and not too experienced. I attempted to root my phone, but was only successful with unlocking the Boot loader. When I attempted to download the new Kit-Kat update, my phone encountered a Firmware upgrade issue. Now in recovery mode, Kies 3 fails to connect nor recognize my phone.
Click to expand...
Click to collapse
Bah. Kies sucks. Odin is a much better tool for updating / fixing things. What update were you on, as it is important to know the actual build version as well because there are often mini updates that keep the same android version but update other things that can cause a headache if not rooted or modified properly. Also, are you sure it was the bootloader that you unlocked? There is the Loki option and SafeStrap recovery, but not a way to unlock the bootloader unless you have a Dev Edition. I think you had to go to 4.3 before 4.4.2 too. What part did it get to before it failed and you got the error message? If you're lucky, it didn't actually do anything important before it failed, because then you can use Odin to install the original system update you did have then restart from there. If not, then you will need to go to 4.3, then 4.4.2. Once you update to 4.3 and above, your only options for custom roms are via the SafeStrap recovery which has some serious limitations.
es0tericcha0s said:
Bah. Kies sucks. Odin is a much better tool for updating / fixing things. What update were you on, as it is important to know the actual build version as well because there are often mini updates that keep the same android version but update other things that can cause a headache if not rooted or modified properly. Also, are you sure it was the bootloader that you unlocked? There is the Loki option and SafeStrap recovery, but not a way to unlock the bootloader unless you have a Dev Edition. I think you had to go to 4.3 before 4.4.2 too. What part did it get to before it failed and you got the error message? If you're lucky, it didn't actually do anything important before it failed, because then you can use Odin to install the original system update you did have then restart from there. If not, then you will need to go to 4.3, then 4.4.2. Once you update to 4.3 and above, your only options for custom roms are via the SafeStrap recovery which has some serious limitations.
Click to expand...
Click to collapse
I tried to gain root access awhile ago, it showed that my bootloader was unlocked, but I don't recall ever gaining root access, so I left it alone and figured I was just gonna wait for Kitkat. It's weird what is happening to my phone now. It just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." After trying Kies Lite and normal both versions 1 & Kies 3, my phone won't even be read nor connect to Kies anymore. It won't show up in Odin. I have tried fully uninstalling all the Samsung programs on my computer then redownloading and installing them and still no luck. I really don't know what else to do. Should I just take my phone into Verizon and try my luck?
cfales25 said:
I tried to gain root access awhile ago, it showed that my bootloader was unlocked, but I don't recall ever gaining root access, so I left it alone and figured I was just gonna wait for Kitkat. It's weird what is happening to my phone now. It just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." After trying Kies Lite and normal both versions 1 & Kies 3, my phone won't even be read nor connect to Kies anymore. It won't show up in Odin. I have tried fully uninstalling all the Samsung programs on my computer then redownloading and installing them and still no luck. I really don't know what else to do. Should I just take my phone into Verizon and try my luck?
Click to expand...
Click to collapse
The chance of finding someone at VZW who could fix this is pretty slim. But the open lock graphic that shows up when you first boot the phone does not imply the bootloader is unlocked on Galaxy phones, unlike say, a Nexus. It just means that something has been done to trip the custom binary check. If you tell me what update you were on, I can tell you how to fix your phone, or if you don't know, then you just need to follow this :
http://forum.xda-developers.com/showthread.php?t=2578209
It should show up in Odin. Not when it has the warning like that, but when you boot to Download Mode. I've bricked plenty of Galaxies like that and have been able to recover every one.
es0tericcha0s said:
The chance of finding someone at VZW who could fix this is pretty slim. But the open lock graphic that shows up when you first boot the phone does not imply the bootloader is unlocked on Galaxy phones, unlike say, a Nexus. It just means that something has been done to trip the custom binary check. If you tell me what update you were on, I can tell you how to fix your phone, or if you don't know, then you just need to follow this :
http://forum.xda-developers.com/showthread.php?t=2578209
It should show up in Odin. Not when it has the warning like that, but when you boot to Download Mode. I've bricked plenty of Galaxies like that and have been able to recover every one.
Click to expand...
Click to collapse
Ok. Thanks, man. I was running on 4.3. My laptop runs Ubuntu, is Odin compatible with this software?
cfales25 said:
Ok. Thanks, man. I was running on 4.3. My laptop runs Ubuntu, is Odin compatible with this software?
Click to expand...
Click to collapse
You'll either need to use Heimdall or the http://casual-dev.com/2014/01/04/jodin3-web-browser-or-offline-flashing-tool/
Alright, I don't really know what happened or what I did, but something bad happened. To begin with, I rooted my phone with Stump and that went fine. After a month or so my phone started to lock itself out and sometimes not unlock. This bug, I don't know what it was, was probably from one of the roms. I uninstalled and removed all the roms and "unrooted" my phone. When I try to root my phone again, it sees the phone as unsupported. I did a hard reset/ I even used towelroot and that was bad. My phone also can't be used on my computer because it won't read it as an LG device with a driver. I've hard reset several times and tried many things. What I know for sure is that one rom or something didn't get removed. For example, I had an emoji switcher rom and I still have Google's emoji's instead of the default LG after reset. I can also lock my phone by double tapping the top left corner, which was another rom. This is all when "unrooted"
Can someone help me fix this? I don't have a warranty on the phone and SuperSU doesn't let me do anything on it.
Andorew said:
Alright, I don't really know what happened or what I did, but something bad happened. To begin with, I rooted my phone with Stump and that went fine. After a month or so my phone started to lock itself out and sometimes not unlock. This bug, I don't know what it was, was probably from one of the roms. I uninstalled and removed all the roms and "unrooted" my phone. When I try to root my phone again, it sees the phone as unsupported. I did a hard reset/ I even used towelroot and that was bad. My phone also can't be used on my computer because it won't read it as an LG device with a driver. I've hard reset several times and tried many things. What I know for sure is that one rom or something didn't get removed. For example, I had an emoji switcher rom and I still have Google's emoji's instead of the default LG after reset. I can also lock my phone by double tapping the top left corner, which was another rom. This is all when "unrooted"
Can someone help me fix this? I don't have a warranty on the phone and SuperSU doesn't let me do anything on it.
Click to expand...
Click to collapse
after removing root, you need to flash back to stock to get it working again with the exploit.
Andorew said:
Alright, I don't really know what happened or what I did, but something bad happened. To begin with, I rooted my phone with Stump and that went fine. After a month or so my phone started to lock itself out and sometimes not unlock. This bug, I don't know what it was, was probably from one of the roms. I uninstalled and removed all the roms and "unrooted" my phone. When I try to root my phone again, it sees the phone as unsupported. I did a hard reset/ I even used towelroot and that was bad. My phone also can't be used on my computer because it won't read it as an LG device with a driver. I've hard reset several times and tried many things. What I know for sure is that one rom or something didn't get removed. For example, I had an emoji switcher rom and I still have Google's emoji's instead of the default LG after reset. I can also lock my phone by double tapping the top left corner, which was another rom. This is all when "unrooted"
Can someone help me fix this? I don't have a warranty on the phone and SuperSU doesn't let me do anything on it.
Click to expand...
Click to collapse
You have to flash back to stock via the link below. Once you Unroot it is the only way of getting root back. Plus it is always nice to know how to return to stock before someone starts rooting, flashing roms etc... so when you get into this positions you already know the solution.
Edit: Make sure you do not take the System update after you flash back to 10b otherwise you will not be able to root any way.
http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
Jimi Mack said:
You have to flash back to stock via the link below. Once you Unroot it is the only way of getting root back. Plus it is always nice to know how to return to stock before someone starts rooting, flashing roms etc... so when you get into this positions you already know the solution.
Edit: Make sure you do not take the System update after you flash back to 10b otherwise you will not be able to root any way.
http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
Click to expand...
Click to collapse
Thanks for the Help. I got my phone back to stock. I don't actually plan on rerooting it for a while. But, do you know why my phone won't take the system update? I tried to and an error appeared.
Andorew said:
Thanks for the Help. I got my phone back to stock. I don't actually plan on rerooting it for a while. But, do you know why my phone won't take the system update? I tried to and an error appeared.
Click to expand...
Click to collapse
Did you get back to stock via the method I supplied? It has to be done that way and then check in your "about phone" and verify you are on "10b". From here the phone should take the 11c update.
Jimi Mack said:
Did you get back to stock via the method I supplied? It has to be done that way and then check in your "about phone" and verify you are on "10b". From here the phone should take the 11c update.
Click to expand...
Click to collapse
Yes, I have 10b, but it fails to update to 11c
Andorew said:
Yes, I have 10b, but it fails to update to 11c
Click to expand...
Click to collapse
Did you disable anything ?
If you returned to stock v10b via the .kdz file, you will not get the OTA because your are on an earlier version of v10b than the phone released with.
You are in a perfect situation to flash bumped TWRP recovery and then the v11c modem, system, and boot images, effectively updating you just like the OTA would have.
If you require the OTA to self-apply, then you need to restore using the .TOT method.
Sent from my VS985 4G using Tapatalk
trent999 said:
If you returned to stock v10b via the .kdz file, you will not get the OTA because your are on an earlier version of v10b than the phone released with.
You are in a perfect situation to flash bumped TWRP recovery and then the v11c modem, system, and boot images, effectively updating you just like the OTA would have.
If you require the OTA to self-apply, then you need to restore using the .TOT method.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
How can I flash a newer version such as 11c(Or upcoming Android L)? Without .tot
You can't. You kdz back to keep from getting the update so you can root and bump and flash roms. You tot to get to the right version to take the update
Once L is released OTA, our noble developers will make it possible for us who have root and recovery to flash the OTA components safely, retaining root and custom recovery.
We hope.
Why would you want to take the current locked OTA?
If you TOT you can still root. Before you take the update.