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?
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,
Just got to know that Pantech has released the much awaited Jelly Bean 4.1 for the Flex through OTA AT&T software update.
Like many others, I'm using the flex outside US, therefore, cannot update my flex.
Would request someone to upload the OTA JB zip file.
Can't wait to see Jelly Bean on the Flex.
PS: Check out the Pantech website for this great news
This is good news. I wish I wasn't rooted with CWMR so I could get this. Tried flashing stock recovery.img and boot.img files but get NOT SUPPORT.
Anyone know a way to get this phone back to complete stock so we can get the Jell Bean goodness?
I managed to unroot and restore stock recovery.
Got prompted for the update, it downloaded and installed fine!
This little Flex seems quite a bit better with Jelly Bean. Wish it had been 4.2 but 4.1 is fine.
Tersanyus said:
I managed to unroot and restore stock recovery.
Got prompted for the update, it downloaded and installed fine!
This little Flex seems quite a bit better with Jelly Bean. Wish it had been 4.2 but 4.1 is fine.
Click to expand...
Click to collapse
Can you upload the update file?
How did you unroot?
Sent from my PantechP8010 using xda app-developers app
Not rooted anymore so probably can't get the update file. It was like 264MB or something.
Not planning to root this phone again.
Interesting that the Pantech diag menu shows still rooted and tampered, it's definitely not rooted.
It should be 100% stock.
If you know of a way to get the file off the phone I can look for it.
---------- Post added at 01:09 PM ---------- Previous post was at 12:52 PM ----------
I knew from experience I had to go to stock recovery and unroot to update.
I flashed a stock rooted nandroid backup I had made after rooting initially.
To unroot I think I went into the SuperUser app and choose option to unroot.
Stock recovery file is posted in a thread here somewhere, had recovery.img and boot.img.
Tried flashing those in fastboot but only got NOT SUPPORT mesage.
I took a flashable zip file that had CWM recovery.img file in it and replaced it with the stock recovery.img and flashed it in CWM.
Once stock recovery was on the phone when I tried to use it I only got a little android symbol lying on its back with a red exclamation point.
Phone booted fine and worked ok
Couldn't get it to see the AT&T update until this morning.
Things I have noticed in this new Jelly Bean build for our little Flex:
Of the stock AT&T apps only 3 I could disable (ugh), why no Disable button
good news
Tersanyus said:
Not rooted anymore so probably can't get the update file. It was like 264MB or something.
Not planning to root this phone again.
Interesting that the Pantech diag menu shows still rooted and tampered, it's definitely not rooted.
It should be 100% stock.
If you know of a way to get the file off the phone I can look for it.
Click to expand...
Click to collapse
Basically you will find the update in the /cache folder.
I'm not sure if you you can access this folder without being rooted. You can give it a try using the ES File Explorer.
Let me know if you get the update.
ES File Manager did see the cache folder and all the other system folders. It was empty. I'm sorry, I factory reset the phone last night from stock recovery since it was not updating built in apps properly. Never seen stock recovery on this phone before. It has an option for root. I selected it. Downloaded a few root checker apps, not rooted.
I'm sorry if I hadn't reset it last night I might have found the file. I'm sure it will turn up somewhere. This little Flex doesn't have much in the way of development but someone here at XDA will get it sooner or later.
Tersanyus said:
ES File Manager did see the cache folder and all the other system folders. It was empty. I'm sorry, I factory reset the phone last night from stock recovery since it was not updating built in apps properly. Never seen stock recovery on this phone before. It has an option for root. I selected it. Downloaded a few root checker apps, not rooted.
I'm sorry if I hadn't reset it last night I might have found the file. I'm sure it will turn up somewhere. This little Flex doesn't have much in the way of development but someone here at XDA will get it sooner or later.
Click to expand...
Click to collapse
Oh that's bad!
Actually, there's another way. If you can share your system nandroid backup, maybe that can help.
Try Rooting
Tersanyus said:
ES File Manager did see the cache folder and all the other system folders. It was empty. I'm sorry, I factory reset the phone last night from stock recovery since it was not updating built in apps properly. Never seen stock recovery on this phone before. It has an option for root. I selected it. Downloaded a few root checker apps, not rooted.
I'm sorry if I hadn't reset it last night I might have found the file. I'm sure it will turn up somewhere. This little Flex doesn't have much in the way of development but someone here at XDA will get it sooner or later.
Click to expand...
Click to collapse
Why dont you try to root with this method http://forum.xda-developers.com/showthread.php?t=1886460 ,its the same you used to root 4.0.4 I guess, should work, pull out the update and then unroot the phone as you dont want it rooted.
It happened to me, even rooted I wanst able to see /data content with ES File Blablabla, then tried with root explorer and worked fine.
I'm not going to root this Flex. It's not a primary phone for me (never was). It is used as a spare now and can be used by novice users in my family and friends. Don't want them to have a rooted phone. I'd been wanting to get this phone back to complete stock for a while but hasn't really put much effort into it.
When I saw that Pantech released JB for Flex a few days ago that was my motivation to get it back to stock. Frankly I was surprised I was able to get it back to stock and not brick the phone!
I'm uploading the stock rooted rom I have. Luckily I saved that on my computer. It's uploading to Dropbox now so it will take a while.
Thanks for your help
Tersanyus said:
I'm not going to root this Flex. It's not a primary phone for me (never was). It is used as a spare now and can be used by novice users in my family and friends. Don't want them to have a rooted phone. I'd been wanting to get this phone back to complete stock for a while but hasn't really put much effort into it.
When I saw that Pantech released JB for Flex a few days ago that was my motivation to get it back to stock. Frankly I was surprised I was able to get it back to stock and not brick the phone!
I'm uploading the stock rooted rom I have. Luckily I saved that on my computer. It's uploading to Dropbox now so it will take a while.
Click to expand...
Click to collapse
Well, thanks for the file, I'm outside US and even on stock, update notification doesn't prompt.
I got mine back to Stock, but when I hit check for upgrade it says..."Previous session is running. Please Try Later"
I have wiped it several times. any ideas?
Wait...
kneemeister said:
I got mine back to Stock, but when I hit check for upgrade it says..."Previous session is running. Please Try Later"
I have wiped it several times. any ideas?
Click to expand...
Click to collapse
I can see ATT's software updater sucks, we just can wait for our friend's upload.
Here it is: Link removed, Dropbox suspended it.
That should be a stock but rooted rom. Nothing else done to it at all. At least. I had that on the phone for a while as a backup when I was playing with roms for the flex.
Probably only going to leave this link up for a day. I'd make your own nandroid backup first. You'll probably get an md5 error in CWMR but there are instructions for fixing that around. I think it was ADB commands that had to fix it. I know the instructions for clearing the md5 error are in one of the flex rom threads, not that there were many of those. The standard disclaimer applies, if this nandroid backup bricks your phone, I can't help you.
I got the same previous session message too. Then it said no update after wiping. I think the best thing is just wipe and don't check for updates. Leave phone on, wifi on and wait for the phone to check on it's own. I got the prompt in a few hours.
Hope this helps you.
So, need to flash stock recovery after restoring nandroid correct?
Sent from my PantechP8010 using xda app-developers app
Likely if you do not flash stock recovery in CWMR the update will fail. I tried to take the update before flashing stock recovery, it failed each time. I had already unrooted though. Pretty much what I have learned from flashing various phones over the years is that if you are not stock completely any OTA updates from the carrier will fail or soft brick your device.
I think the Flex was one where I had just that issue. There was some AT&T update a few months back, I said to apply it and I got stuck in recovery. Every time I rebooted the phone it just booted to recovery. Found out if I went into the diag screen on the Flex and choose reboot from there I could boot normally. Eventually I figured out I had the wrong boot.img on the phone. Once that was fixed the phone booted fine. But the update never worked.
You can try to take the update with CWMR but I doubt it will work and could brick or soft brick. I've learned to never take an OTA update from the carrier if you are not completely stock.
Still waiting
Tersanyus said:
Likely if you do not flash stock recovery in CWMR the update will fail. I tried to take the update before flashing stock recovery, it failed each time. I had already unrooted though. Pretty much what I have learned from flashing various phones over the years is that if you are not stock completely any OTA updates from the carrier will fail or soft brick your device.
I think the Flex was one where I had just that issue. There was some AT&T update a few months back, I said to apply it and I got stuck in recovery. Every time I rebooted the phone it just booted to recovery. Found out if I went into the diag screen on the Flex and choose reboot from there I could boot normally. Eventually I figured out I had the wrong boot.img on the phone. Once that was fixed the phone booted fine. But the update never worked.
You can try to take the update with CWMR but I doubt it will work and could brick or soft brick. I've learned to never take an OTA update from the carrier if you are not completely stock.
Click to expand...
Click to collapse
Im on stock and I cant update, no root, stock recovery, Ive been waiting for the update and nothing.
I dont know if is because Im outside US
I got mine back to stock and unrooted, but the upgrade still fails at about 25% and reboots. If I clear cache and wipe, it will download again, then fail again. Even after flashing back to stock, recovery still says rooted and so does the software upload screen. But I have confirmed that I am no longer rooted. I am about to give up.
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.
If anyone is interested, I saw this posted today. A small OTA update released by AT&T today.
http://www.androidcentral.com/att-pushes-out-update-htc-one-m8-brings-android-444-and-hd-voice
scott500 said:
If anyone is interested, I saw this posted today. A small OTA update released by AT&T today.
http://www.androidcentral.com/att-pushes-out-update-htc-one-m8-brings-android-444-and-hd-voice
Click to expand...
Click to collapse
This is merely a rumor. The ATT link is to the old May 2014 update.
Pay no attention.
The link to the att sight yes is for old 1.58 build, does not mean there isnt an update coming...as its being reported with a build number by more and more sights, could just be a rumour but it could also be rolling out.
Well, they finally released the update today. Finally have 4.4.4. On my m8. Now to wait for lollipop
Does anybody know where the OTAPkg file gets downloaded to? I'm trying to preserve the file and not have to download it again and again after a fail update. Thanks.
Edit: n/m found it, it's under the FUMO folder within the internal SD.
Please save a copy. We need it for a custom rom
Sent from my HTC One_M8 using XDA Free mobile app
johnnyutah22 said:
Please save a copy. We need it for a custom rom
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I'm lost. I installed the 4.4.4 OTA, installed the latest CM12 nightly, and now I have no cell service nor options to select/enter an apn. Under apn it states "access point names not available for this user" HElP?!
ALSO, what custom roms can I run using this 4.4.4 OTA?!
bford152 said:
I'm lost. I installed the 4.4.4 OTA, installed the latest CM12 nightly, and now I have no cell service nor options to select/enter an apn. Under apn it states "access point names not available for this user" HElP?!
ALSO, what custom roms can I run using this 4.4.4 OTA?!
Click to expand...
Click to collapse
I can't help you with CM12, but I just installed Viper One and it seems to work fine.
I updated to the 4.4.4 via OTA yesterday, and Viper installed without a hitch.
NB: Make a Nandroid Backup before flashing please.
Whats the best way to update my girlfriend's rooted M8? Currently running 4.4.2 rooted S-ON. Can she just take OTA and then will have to re-root?
I'm S-OFF on my phone so I haven't had to deal with this. Already updated my firmware months ago and have been running 4.4.4 roms.
Thanks!!
Downloading it now.
You'll have to re-flash stock recovery, take the OTA update, then restore twrp (or other custom recovery) and re-root.
Could someone help me with the OTA update. I'm on stock 4.4.2 rooted and s-off. I placed back all the at&t crap in systems and tried my best to restore everything back to stock even recovery. I'm still getting a red triangle approx like 1/4 the way during the update. What sucks is that I have to download the whole update file again and it's 800+megs versus the prior updates which were a lot smaller. It's just very time consuming and would like to find out the root of the issue is.
I've done so many mods on the phone like the HK mod and various other ones. I'm trying to think back now to see if there is anything else and now I'm stuck. I don't want to restore my stock nandroid cause I would have to install everything all over again which would suck big time. I uninstall the drivers for viper4android, xposed, and even reverted the host file back from adaway. I just feel like there might be something within the system files that isn't suppose to be there. I even got rid of the att boot logo and sound but I had restored that back to stock as well. Please help if you could. Thanks.
Also is there anyway to flash twrp without using a pc? I tried flashify but it doesn't seem to be working cause it would revert back to the fastboot no matter what.
Same situation here I think... stock rom (never changed it yet), rooted, unlocked, s-off. Downloaded OTA then realized I needed to flash original recovery back. Did that, now AT&T sw update is of course telling me to wait 24 hours to check again. Any way around that?
jeremyenos said:
Same situation here I think... stock rom (never changed it yet), rooted, unlocked, s-off. Downloaded OTA then realized I needed to flash original recovery back. Did that, now AT&T sw update is of course telling me to wait 24 hours to check again. Any way around that?
Click to expand...
Click to collapse
Yeah just manually change the date one day ahead and try it again. It might take a couple of secs for it to prompt that there is an update.
I just posted a pre-rooted ruu in the dev section.
Backup data in twrp to your ext sd. Flash ruu via sd card method. Flash twrp using the free app flashify. Reboot to twrp and restore data.
No pc required.
Just make sure you backup files on internal.
volcalstone said:
Could someone help me with the OTA update. I'm on stock 4.4.2 rooted and s-off. I placed back all the at&t crap in systems and tried my best to restore everything back to stock even recovery. I'm still getting a red triangle approx like 1/4 the way during the update. What sucks is that I have to download the whole update file again and it's 800+megs versus the prior updates which were a lot smaller. It's just very time consuming and would like to find out the root of the issue is.
I've done so many mods on the phone like the HK mod and various other ones. I'm trying to think back now to see if there is anything else and now I'm stuck. I don't want to restore my stock nandroid cause I would have to install everything all over again which would suck big time. I uninstall the drivers for viper4android, xposed, and even reverted the host file back from adaway. I just feel like there might be something within the system files that isn't suppose to be there. I even got rid of the att boot logo and sound but I had restored that back to stock as well. Please help if you could. Thanks.
Also is there anyway to flash twrp without using a pc? I tried flashify but it doesn't seem to be working cause it would revert back to the fastboot no matter what.
Click to expand...
Click to collapse
There's a boot loader flashable twrp in the dev section posted by jball
dottat said:
I just posted a pre-rooted ruu in the dev section.
Backup data in twrp to your ext sd. Flash ruu via sd card method. Flash twrp using the free app flashify. Reboot to twrp and restore data.
No pc required.
Just make sure you backup files on internal.
Click to expand...
Click to collapse
I noticed that flashify also will install CWM or Philz. Is your method specific to TWRP or can you use the others. The reason I ask is because I currently use Philz and would need that to restore my backup.
johnnyutah22 said:
I noticed that flashify also will install CWM or Philz. Is your method specific to TWRP or can you use the others. The reason I ask is because I currently use Philz and would need that to restore my backup.
Click to expand...
Click to collapse
You can flash whichever you use.
I thought I read where this update would include the EYE Experience. Did I read that wrong or do I just not know how to use my camera anymore?
volcalstone said:
Could someone help me with the OTA update. I'm on stock 4.4.2 rooted and s-off. I placed back all the at&t crap in systems and tried my best to restore everything back to stock even recovery. I'm still getting a red triangle approx like 1/4 the way during the update. What sucks is that I have to download the whole update file again and it's 800+megs versus the prior updates which were a lot smaller. It's just very time consuming and would like to find out the root of the issue is.
I've done so many mods on the phone like the HK mod and various other ones. I'm trying to think back now to see if there is anything else and now I'm stuck. I don't want to restore my stock nandroid cause I would have to install everything all over again which would suck big time. I uninstall the drivers for viper4android, xposed, and even reverted the host file back from adaway. I just feel like there might be something within the system files that isn't suppose to be there. I even got rid of the att boot logo and sound but I had restored that back to stock as well. Please help if you could. Thanks.
Click to expand...
Click to collapse
I don't think root changes are the issue; as typically it will fail before it even goes into recovery with a message that the system has been modified. It might just be a bad download.
Setting up your phone again is really not that bad a proposition; especially if you use Titanium to restore apps. And it will also restore your Xposed installer and modules. Using Titanium, I can easily be up and fully configured again in about a half hour after a factory reset or RUU. Although, of course this will depend on the amount of customization in settings, etc.
You might consider updating with the new RUU (relocking bootloader required if s-on). Not only will this bypass the OTA install issue you are having, but makes for a cleaner install. Yes, you will have to set the phone up again; and you will also need to backup any data on internal storage, as it will be wiped by RUU.