Just wanted to get a few pointers on the update process once 4.2.2. factory images are released.
I'm currently running CM 10.1 latest nightly complete with Faux's custom kernel. When the factory images are released, i want to take advantage of the new radio and bootloader, that hopefully will be shipping, along with anything else without having to fully wipe and start from fresh.
Please correct me if i'm wrong on any of my thoughts about how to update below, or if i've missed anything
Bootloader - extract from factory image and flash in fastboot with
fastboot flash bootloader bootloaderxxxx.img
Radio - extract from factory image and flash in fastboot with
fastboot flash radio radioxxxx.img
Kernel - hopefully faux will update once source drops and can be flashed via recovery
ROM - hopefully CM will update with 4.2.2 is AOSP and can be flashed in recovery, along with updated GAAPS
Am i missing anything else??
Thanks
That will do it.
You just have to hope they work with CM10.1 though...
peedub said:
That will do it.
You just have to hope they work with CM10.1 though...
Click to expand...
Click to collapse
Yeah I'll check that out before I do anything, fingers crossed it will be good!
I haven't missed anything out then, bootloader, radio, kernel, ROM is all there is to update?
Sent from my Nexus 10 using Tapatalk HD
Just not to start a new thread. Can anyone conform for me this: currently stock everything - except running CWM recovery.
I'll have to flash the stock recovery before trying to get the OTA update?
chrisastrous said:
Just not to start a new thread. Can anyone conform for me this: currently stock everything - except running CWM recovery.
I'll have to flash the stock recovery before trying to get the OTA update?
Click to expand...
Click to collapse
Yes...u wont be able to apply the OTA update with a custom recovery...but u can flash the update through CWM...
Stock everything, never been rooted.. will the OTA update erase any data whatsoever? When can we expect it?
dralways said:
Stock everything, never been rooted.. will the OTA update erase any data whatsoever? When can we expect it?
Click to expand...
Click to collapse
No the OTA will not erase anything. As for when you will get it? It should be soon. If you're impatient you can flash it manually buuuut i'd hold off on that becuase of all of the" help trouble after updating to 4.2.2" threads popping up recently.
I just received the update downloaded notification on my Nexus 7 but still nothing on the N4.
uploder said:
No the OTA will not erase anything. As for when you will get it? It should be soon. If you're impatient you can flash it manually buuuut i'd hold off on that becuase of all of the" help trouble after updating to 4.2.2" threads popping up recently.
Click to expand...
Click to collapse
Will the stock 4.2.2 wipe my apps? I know it will damaged the internal SD.
What about my apps adn corporate data? Pls advise
Ramu
darkkid85 said:
Will the stock 4.2.2 wipe my apps? I know it will damaged the internal SD.
What about my apps adn corporate data? Pls advise
Ramu
Click to expand...
Click to collapse
Just ran the update my phone is in exactly the same state as before. Nothing got deleted
chrisastrous said:
Just ran the update my phone is in exactly the same state as before. Nothing got deleted
Click to expand...
Click to collapse
Thanks dude,
i just did too, all info reimained intact
ramu
darkkid85 said:
Thanks dude,
i just did too, all info reimained intact
ramu
Click to expand...
Click to collapse
Well how about giving me a thanks lol
Apparently superuser remains but you still lose root! Will get back to you when I find out more info.
Related
So, I'm new to the world of tablets - the only interaction with them being some light use on my mom's tablet (including rooting it via Iconia Root and installing Acer Recovery Installer v2.54) I was curious about updating via ARI (since she's rooted and being plagued by OTA popups). Back when she first got the tablet, she tried to update and it would stop mid-download, giving no error, and just sit there until she cancelled it (this was before the root). So, basically, my question is: Is it possible to run a stock update (Ie "Stock 3.1 4.010.42_EMEA_GEN3") without having to wipe during install? I have a backup via ARI and also Titanium backup installed but I'd really like to not have to re-install all the apps/set up the homescreen (she's on stock) and stuff. I know on my OG droid that when I installed CM7 I had to do a wipe for it to even get past the boot screen but I figure with this being a stock update maybe it's different...
If not is there some way that I can install an update while keeping the root/system data?
AliceInUnderland said:
So, I'm new to the world of tablets - the only interaction with them being some light use on my mom's tablet (including rooting it via Iconia Root and installing Acer Recovery Installer v2.54) I was curious about updating via ARI (since she's rooted and being plagued by OTA popups). Back when she first got the tablet, she tried to update and it would stop mid-download, giving no error, and just sit there until she cancelled it (this was before the root). So, basically, my question is: Is it possible to run a stock update (Ie "Stock 3.1 4.010.42_EMEA_GEN3") without having to wipe during install? I have a backup via ARI and also Titanium backup installed but I'd really like to not have to re-install all the apps/set up the homescreen (she's on stock) and stuff. I know on my OG droid that when I installed CM7 I had to do a wipe for it to even get past the boot screen but I figure with this being a stock update maybe it's different...
If not is there some way that I can install an update while keeping the root/system data?
Click to expand...
Click to collapse
No. If you run the OTA, you WILL lose root. Not to mention I don't have a lot of faith in any device OTA updates. Prior experience, and hanging around various forums, well, you can read the horror stories.
I would advise, if you want to upgrade her OS and get rid of the "pesky" update notifications, is to flash one of the Stock rooted roms available. Or maybe a stripped down version of a Stock rom.
Search the developer section for a rooted version of the stock OTA, there are several in there. Install it via recovery, you only need to wipe dalvik and cache before the install. All of her data and programs will still be there. It will upgrade just fine. Remember wipe Dalvik and cache but do not wipe data and everything will be fine.
get and flash one of the honeylicious rom from the dev area .. good rom very basic apps.. but has a update to get the acer apps back.. and bunch of other cool mods.. the dev is also . kinda trustworthy..
Giggles.. ok he is kewl for a guy yukeeee guys smell..
good luck .. read read read read before you flash anything and of course back up and back up your backups .. then back them up again
cruise350 said:
Search the developer section for a rooted version of the stock OTA, there are several in there. Install it via recovery, you only need to wipe dalvik and cache before the install. All of her data and programs will still be there. It will upgrade just fine. Remember wipe Dalvik and cache but do not wipe data and everything will be fine.
Click to expand...
Click to collapse
Well... if the person was going to do an update to the exact same rom (different version) I would say ok.
But... if you are going to go to a totally different Rom, you NEED to wipe User Data.
Or, does anybody want to tell me you never have to?
3 Wipes. Mandatory when switching between roms, unless you are a dev and know exactly what you are doing.
Or.... you can forget about the safe side of things, and just flash away, and hope luck is with you.
The Market, SHOULD, allow you to re-download apps based on the market version you previously used. If not, it's a good time to clean house of the useless apps.
Moscow Desire said:
No. If you run the OTA, you WILL lose root. Not to mention I don't have a lot of faith in any device OTA updates. Prior experience, and hanging around various forums, well, you can read the horror stories.
I would advise, if you want to upgrade her OS and get rid of the "pesky" update notifications, is to flash one of the Stock rooted roms available. Or maybe a stripped down version of a Stock rom.
Click to expand...
Click to collapse
I wasn't talking about an OTA, I was talking about the stock 'rom' updates via recovery. I've had experiences with phones that have been rooted and accidentally updated via OTA, it's not fun. My phone was actually put into something I like to refer to as the Root limbo lol, bricked it for a small period of time - that was fun fixing it. I didn't have a nandroid at the time so I had to start from scratch...
cruise350 said:
Search the developer section for a rooted version of the stock OTA, there are several in there. Install it via recovery, you only need to wipe dalvik and cache before the install. All of her data and programs will still be there. It will upgrade just fine. Remember wipe Dalvik and cache but do not wipe data and everything will be fine.
Click to expand...
Click to collapse
So if I find a rooted version of stock OTA I can install it and only wipe Dalvik? I won't get stuck in a bootloop if I don't wipe data?
AliceInUnderland said:
So if I find a rooted version of stock OTA I can install it and only wipe Dalvik? I won't get stuck in a bootloop if I don't wipe data?
Click to expand...
Click to collapse
If you stick with a stock pre-rooted ROM, you won't get stuck in a bootloop like you do some phones. You're just doing an upgrade.
But like doing an upgrade to any other OS without formatting first, you're writing good data over bad, so your mileage may vary.
---------- Post added at 06:38 PM ---------- Previous post was at 06:34 PM ----------
erica_renee said:
get and flash one of the honeylicious rom from the dev area .. good rom very basic apps.. but has a update to get the acer apps back.. and bunch of other cool mods.. the dev is also . kinda trustworthy..
Giggles.. ok he is kewl for a guy yukeeee guys smell..
good luck .. read read read read before you flash anything and of course back up and back up your backups .. then back them up again
Click to expand...
Click to collapse
Hey I resemble....or is it resent that remark! lol
kjy2010 said:
If you stick with a stock pre-rooted ROM, you won't get stuck in a bootloop like you do some phones. You're just doing an upgrade.
But like doing an upgrade to any other OS without formatting first, you're writing good data over bad, so your mileage may vary.
I can't seem to find any pre-rooted stock Roms on the Developers forum. Links? I know I'm probably being a pain in the ass but I really don't want to get something by mistake and start with scratch on my mom's tablet - if it were mine I wouldn't care. lol
Click to expand...
Click to collapse
The link in the post above yours in this thread. Is a link to the rom scroll up one post
Giggles
AliceInUnderland said:
kjy2010 said:
If you stick with a stock pre-rooted ROM, you won't get stuck in a bootloop like you do some phones. You're just doing an upgrade.
But like doing an upgrade to any other OS without formatting first, you're writing good data over bad, so your mileage may vary.
I can't seem to find any pre-rooted stock Roms on the Developers forum. Links? I know I'm probably being a pain in the ass but I really don't want to get something by mistake and start with scratch on my mom's tablet - if it were mine I wouldn't care. lol
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1290318
Click to expand...
Click to collapse
kjy2010 said:
AliceInUnderland said:
http://forum.xda-developers.com/showthread.php?t=1290318
Click to expand...
Click to collapse
Oh my god you rock, thanks so much!
Click to expand...
Click to collapse
AliceInUnderland said:
kjy2010 said:
Oh my god you rock, thanks so much!
Click to expand...
Click to collapse
Yw
Click to expand...
Click to collapse
kjy2010 said:
AliceInUnderland said:
http://forum.xda-developers.com/showthread.php?t=1290318
Click to expand...
Click to collapse
Okay, this sent her into a bootloop so I had to nandroid. I wiped dalvik cache before installing this. Put it in the root of my SD card and installed via CWM in recovery. what am I doing wrong?
Click to expand...
Click to collapse
AliceInUnderland said:
kjy2010 said:
Okay, this sent her into a bootloop so I had to nandroid. I wiped dalvik cache before installing this. Put it in the root of my SD card and installed via CWM in recovery. what am I doing wrong?
Click to expand...
Click to collapse
I've never heard of the A500 going into a bootloop simply from flashing one rooted stock ROM to another, but then again most people do all the necessary wipes when they do. Did you wipe dalvik and battery stats? That's about as minimal as you're going to get. If that doesn't work, you'll just have to flash the proper way. Instructions here complete with a video tutorial on how to flash by yours truly:
http://forum.xda-developers.com/showthread.php?t=1390860
Click to expand...
Click to collapse
kjy2010 said:
AliceInUnderland said:
I've never heard of the A500 going into a bootloop simply from flashing one rooted stock ROM to another, but then again most people do all the necessary wipes when they do. Did you wipe dalvik and battery stats? That's about as minimal as you're going to get. If that doesn't work, you'll just have to flash the proper way. Instructions here complete with a video tutorial on how to flash by yours truly:
http://forum.xda-developers.com/showthread.php?t=1390860
Click to expand...
Click to collapse
Nevermind, I fixed it XD I wiped dalvik and battery/partition and it worked fine lol.
Click to expand...
Click to collapse
AliceInUnderland said:
kjy2010 said:
Nevermind, I fixed it XD I wiped dalvik and battery/partition and it worked fine lol.
Click to expand...
Click to collapse
Uh huh....you're welcome!
Click to expand...
Click to collapse
As the title says, I'm getting notifications to upgrade my Nexus 7 to 4.2 even though I have 4.2 already. If it were the 4.2.1 update that it wanted me to update to, wound't it say 4.2.1 instead of 4.2?
Info on the device:
Rooted
Bootloader Unlocked
Stock ROM
I went ahead and tried installing the update many times and while it shutdown to do its dirty work, it eventually error-ed out (while the little Android guy is on his back). I have even done a factory reset and I still get the prompts to update to 4.2... from 4.2. Errors are there as well. Thank you for your help.
John J
P.S There are pics
jjimenezjj said:
As the title says, I'm getting notifications to upgrade my Nexus 7 to 4.2 even though I have 4.2 already. If it were the 4.2.1 update that it wanted me to update to, wound't it say 4.2.1 instead of 4.2?
Info on the device:
Rooted
Bootloader Unlocked
Stock ROM
I went ahead and tried installing the update many times and while it shutdown to do its dirty work, it eventually error-ed out (while the little Android guy is on his back). I have even done a factory reset and I still get the prompts to update to 4.2... from 4.2. Errors are there as well. Thank you for your help.
John J
P.S There are pics
Click to expand...
Click to collapse
This has been posted about before.
Yes, the 4.2.1 upgrade says "4.2" in the update screen. Your device is trying to go from 4.2->4.2.1.
The upgrade however seems to be failing. Since you are using a stock recovery, there is no indication on what part is stopping it. It could just be a glitch or, more likely, you modified something. Did you install any mods or root and modify any system apps? Freezing them in TiBu/etc. will break it too.
phonic said:
This has been posted about before.
Yes, the 4.2.1 upgrade says "4.2" in the update screen. Your device is trying to go from 4.2->4.2.1.
The upgrade however seems to be failing. Since you are using a stock recovery, there is no indication on what part is stopping it. It could just be a glitch or, more likely, you modified something. Did you install any mods or root and modify any system apps? Freezing them in TiBu/etc. will break it too.
Click to expand...
Click to collapse
I did read other posts but they didn't seem to help.
After I rooted the device, I went ahead and pasted the original browser.apk in the System/App folder and installed it from there. From what I read, that was most likely my problem. I deleted it but still got the error. After that I said "screw this" and applied a data factory reset thinking that would solve my problems
Thank you for your reply.
John J
jjimenezjj said:
I did read other posts but they didn't seem to help.
After I rooted the device, I went ahead and pasted the original browser.apk in the System/App folder and installed it from there. From what I read, that was most likely my problem. I deleted it but still got the error. After that I said "screw this" and applied a data factory reset thinking that would solve my problems
Thank you for your reply.
John J
Click to expand...
Click to collapse
Yes, that modification would certainly break the OTA update.
Doing a factory wipe won't help. That won't revert the old system apk back to stock. Nor will deleting it.
Your best bet is to download the full 4.2.1 image and flash that. Or, you could find and restore the original browser.apk.
This should serve as another reminder to people who make tweaks - always backup the original file!
phonic said:
Yes, that modification would certainly break the OTA update.
Doing a factory wipe won't help. That won't revert the old system apk back to stock. Nor will deleting it.
Your best bet is to download the full 4.2.1 image and flash that. Or, you could find and restore the original browser.apk.
This should serve as another reminder to people who make tweaks - always backup the original file!
Click to expand...
Click to collapse
It's not that bad. Everything works fine except for updating the thing. As for the restoring the original browser.apk, if you mean Chrome, I never touched it so it is there.
My guess is that I didn't install the CWM Recovery correctly because I can't boot into Recovery Mode. It just hangs and stays in a loop. I will re-install CWM and see if that helps.
John J
Re-installed CWM Recovery and flashed 4.2.1 from there. Lost everything but I had anything important backup already. All is good
So first off im gonna start off and say that I dont really care about being rooted in the first place. I thought id be flashing a lot more stuff but It turns out that I never flashed anything. So on my phone as of now I just have root and I have twrp installed onto it. I did that process to take off the custom recovery status from using motochopper as well. Now my problem is that every time i try to take the ota I get booted right into twrp and then i am unable to take the update. I even downloaded the zip file and tried flashing it and I just get a failed message. Can anyone tell me whats going on? Or point me into the right direction so i can uninstall twrp so I can take the update?
Odin back to stock, then do a factory reset in settings.
Sledutah said:
Odin back to stock, then do a factory reset in settings.
Click to expand...
Click to collapse
Will this make everything on my phone get deleted?
blackguy101 said:
Will this make everything on my phone get deleted?
Click to expand...
Click to collapse
It did not wipe either internal or extral sdcards when I used odin, been awhile though.
TheAxman said:
It did not wipe either internal or extral sdcards when I used odin, been awhile though.
Click to expand...
Click to collapse
Well actually I have one more question. Arent I already stock? I havent even flashed another rom. I literally just got root status and put twrp recovery on it. Do I still need to use odin?
blackguy101 said:
Well actually I have one more question. Arent I already stock? I havent even flashed another rom. I literally just got root status and put twrp recovery on it. Do I still need to use odin?
Click to expand...
Click to collapse
You say you are rooted, then do a factory reset, and un-root, then you will be able to get the update.
blackguy101 said:
Will this make everything on my phone get deleted?
Click to expand...
Click to collapse
Like axman said, flashing with Odin to stock nothing gets deleted. If you do a factory wipe, everything gets deleted.
You could also try to update with kies instead of ota. Maybe that will work.
The problem is not that you removed root you still are using a custom recovery you need to get back to full stock use odin to get the phone back to full stockso you'll have a stock recovery
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
Where can I find a good copy of the full stock recovery for odin
Roadk1ng said:
Where can I find a good copy of the full stock recovery for odin
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=40976805
Last night my phone wanted to update to 4.4.4 because it's been wanting to for a while, but I know it wouldn't work because my phone is rooted. It had tried this at least 3 times before and everything was fine; download update, tries to install, fails, boots right back up. I wanted to get rid of the Update notification in the top bar, so I just ran it again thinking it'd be okay. Well, this time it bricked my phone, leaving me at a neverending loop at the boot animation. I first tried to wipe the cache and dalvik cache, which did nothing. Then I tried a factory restore, which also did nothing. Then I reinstalled the stock 4.4.3 rom I had been using, which did nothing. Then I wiped the SD card completely and reinstalled a stock 4.4.4 rom through sideload, which has done nothing. My phone just sits at the boot animation and taunts me. Worse yet, I have a 16-hour drive tomorrow and my phone was going to be the majority of my sanity during that time.
What should I do?? Is there anything I can do? Normally I would just contact Google to get a replacement (I've done this before when the 4.2 update was causing a lot of bricks,I think it was 4.2 anyway, I forgot) but I'd like to have a working phone for my 16 hour trip..... if possible. Any help would be greatly appreciated! Thank you.
Well, I never had heard of any devices that still stuck in the bootanimation after flashing the factory image. There is something really wrong.
Did you already tried flashing a custom rom? Can you boot into recovery?
CCody said:
Well, I never had heard of any devices that still stuck in the bootanimation after flashing the factory image. There is something really wrong.
Did you already tried flashing a custom rom? Can you boot into recovery?
Click to expand...
Click to collapse
I had a Vanir 4.4.3 rom on my phone that I tried to flash as well, but for some reason it went right into "Optimizing Apps" after the first boot, something I hadn't seen before. Then it got stuck at "Starting Apps...", then after a restart, it too was stuck at the boot animation.
I can boot into recovery luckily, but that's all I can do. I have CWMR v6.0.3.5. I've tried just about everything I can think of. [edit] I was able to contact Google for some live chat support and am now #2 in the queue. Hopefully they can either help me or get a replacement going. Either way, I'd still love any help you guys can give me, I'd really like to get it fixed rather than waiting for a replacement.
Okay, try this: Wipe everything via recovery and with everything i mean really everything! Cache, dalvik, storage, your whole system. There must be nothing left on your phone. Then flash a rom of your choice. Wipe cache and dalvik afterwards and see if it works
CCody said:
Okay, try this: Wipe everything via recovery and with everything i mean really everything! Cache, dalvik, storage, your whole system. There must be nothing left on your phone. Then flash a rom of your choice. Wipe cache and dalvik afterwards and see if it works
Click to expand...
Click to collapse
I've done that already, Factory Reset + wipe cache + wipe dalvik cache + format system/data/cache/sdcard/data/media. The phone was completely bare and that's when I sideloaded the stock 4.4.4 rom (otherwise it's stuck at the Google boot screen). I'll try it again, though.
Okay right now I'm using the Nexus Toolkit to flash the stock 4.4.4 .tgz image directly from google and unroot my phone (checking the option that the phone is Soft-bricked/Bootloop.
....Okay that finished and I'm still stuck at the boot animation and now I don't have CWMR. ****. [EDIT] But I can still boot into a custom recovery through the toolkit, which is good.
RawrNate said:
Okay right now I'm using the Nexus Toolkit to flash the stock 4.4.4 .tgz image directly from google and unroot my phone (checking the option that the phone is Soft-bricked/Bootloop.
....Okay that finished and I'm still stuck at the boot animation and now I don't have CWMR. ****. [EDIT] But I can still boot into a custom recovery through the toolkit, which is good.
Click to expand...
Click to collapse
Damn, I really am stumped right now. That's really strange. Normally everything should be fine after a factory reset...
I've search several threads with bootloop problems, but none of them have this persistent bootloop. I believe you have damage your storage somehow, so that the system can't read the files and boot up properly. Maybe because of this 4.4.4 OTA update. Man, that's kinda sucks right now...
CCody said:
Damn, I really am stumped right now. That's really strange. Normally everything should be fine after a factory reset...
I've search several threads with bootloop problems, but none of them have this persistent bootloop. I believe you have damage your storage somehow, so that the system can't read the files and boot up properly. Maybe because of this 4.4.4 OTA update. Man, that's kinda sucks right now...
Click to expand...
Click to collapse
Yeah haha, it's really really strange. I appreciate you trying to help me, though! Lucky for me I'm getting a "One-time exception replacement" since my warranty is expired but they must be super stumped with the issue as well xD
I forgot something! Did you also flashed the 4.4.4 binaries?
https://developers.google.com/android/nexus/drivers#makoktu84p
I also read somewhere, that the LG Fashtool may help.
Try this out!
CCody said:
I forgot something! Did you also flashed the 4.4.4 binaries?
https://developers.google.com/android/nexus/drivers#makoktu84p
I also read somewhere, that the LG Fashtool may help.
Try this out!
Click to expand...
Click to collapse
Hm, I didn't think I'd need to with the factory image, but I'll try that. I tried the 4.4.3 factory image as well but that didn't work either. I also can't find anything about the LG Flashtool that's Nexus 4 specific, but I'll try to look more into it.
Wait, how do I flash the binaries since they're .tgz files?
RawrNate said:
Hm, I didn't think I'd need to with the factory image, but I'll try that. I tried the 4.4.3 factory image as well but that didn't work either. I also can't find anything about the LG Flashtool that's Nexus 4 specific, but I'll try to look more into it.
Click to expand...
Click to collapse
This is really strange man. Flashing stock ROM is the last resort but even that seems to be failing for you.
Have you tried downloading the stockRom again (just to make sure it isn't corrupted). Also, maybe you can try using TWRP instead of CWM this time.
Good luck.
RawrNate said:
Wait, how do I flash the binaries since they're .tgz files?
Click to expand...
Click to collapse
No need to flash them, since you are on a factory image, sry.
Woah now, I've made progress! Maybe.... Anyway, in TWRP, I "fixed permissions" and mounted "system" but now I'm at the "Android is Upgrading, Optimizing Apps - Starting Apps" screen again (it only had to optimize 23 apps?). I was at this issue before when I was flashing roms last night trying to fix it, but going back to here is better than not getting it to boot at all. What else should I try next?
Note: I'm on the 4.4.4 factory image now and TWRP is just temporary through the Nexus Root Toolkit.
RawrNate said:
Woah now, I've made progress! Maybe.... Anyway, in TWRP, I "fixed permissions" and mounted "system" but now I'm at the "Android is Upgrading, Optimizing Apps - Starting Apps" screen again (it only had to optimize 23 apps?). I was at this issue before when I was flashing roms last night trying to fix it, but going back to here is better than not getting it to boot at all. What else should I try next?
Note: I'm on the 4.4.4 factory image now and TWRP is just temporary through the Nexus Root Toolkit.
Click to expand...
Click to collapse
And? Did it boot up or just stuck in 'optimizing apps'? I would suggest to try another android version, like 4.3 or 4.4.2 at least.
CCody said:
And? Did it boot up or just stuck in 'optimizing apps'? I would suggest to try another android version, like 4.3 or 4.4.2 at least.
Click to expand...
Click to collapse
30 minutes later and it's still at "Starting apps..."
I tried factory images of 4.4.3 and 4.3, still nothing.
RawrNate said:
30 minutes later and it's still at "Starting apps..."
I tried factory images of 4.4.3 and 4.3, still nothing.
Click to expand...
Click to collapse
Jesus!
What about custom ROM? Cyanogenmod maybe? Make sure to downlaod the M7-Release.
Hm, alright, I'll give that a shot.
On a side note, is there a way to lock the bootloader again while in either recovery or bootloader? I fear that if it's unlocked, I won't get the $250 refund for the replacement.
RawrNate said:
Hm, alright, I'll give that a shot.
On a side note, is there a way to lock the bootloader again while in either recovery or bootloader? I fear that if it's unlocked, I won't get the $250 refund for the replacement.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=tZbvuikfnks
CCody said:
https://www.youtube.com/watch?v=tZbvuikfnks
Click to expand...
Click to collapse
Oh good that was easier than I thought xD
Hi guys,
I rooted my s3 successfully, but now cannot install the 19s update. I've tried undoing the root and updating afterwards unsuccessfully. Do you guys have any other things I can try? Do I need to re flash the stock ROM?
Thanks !
Rooting typically breaks OTA updates in my experience. You can try flashing stock + stock recovery and then take the OTA. I'm not 100% sure that'll work, but it should.
Come to think of it, I think it's more twrp that breaks OTAs and not root.
benjmiester said:
Rooting typically breaks OTA updates in my experience. You can try flashing stock + stock recovery and then take the OTA. I'm not 100% sure that'll work, but it should.
Come to think of it, I think it's more twrp that breaks OTAs and not root.
Click to expand...
Click to collapse
Darn, I was a moron and didn't back up the stock recovery, so I guess I'm stuck waiting for someone else with an S3 to upload theirs. Oh well, lesson learned!
Thanks!
try flashing the stock recovery from here:
http://forum.xda-developers.com/le-2/development/leeco-le-2-x526-stock-recovery-t3449208
it's from 16S, but it should work. after that you should be able to install the OTA. no gaurantees though
randomsmash said:
Darn, I was a moron and didn't back up the stock recovery, so I guess I'm stuck waiting for someone else with an S3 to upload theirs. Oh well, lesson learned!
Thanks!
Click to expand...
Click to collapse
No prob, it happens. I keep seeing .20 builds on YouTube, that add theme store/more theme support and fingerprint sensor gestures. So I might want to do an OTA soon myself. Let us know if 99's solution works.
Sent from my LEX727 using XDA-Developers mobile app
benjmiester said:
No prob, it happens. I keep seeing .20 builds on YouTube, that add theme store/more theme support and fingerprint sensor gestures. So I might want to do an OTA soon myself. Let us know if 99's solution works.
Sent from my LEX727 using XDA-Developers mobile app
Click to expand...
Click to collapse
it wont. i fiddled with my S3 last night and accidently booted TWRP as "read/write", which the OTA can detect as it runs a checksum on the /system partition. if the system partition has EVER been mounted as read/write it changes, and therefore the OTA file will never flash/install. the only way around it is to have someone do a full system image backup from TWRP via a "fastboot boot twrp.img" then selecting to keep TWRP mounted as read only. this also affects all of us on the Pro3 (i have both). it would be wise if we could pull full system images for all US models as there are no full ROM's available
instructions on how to do that are here:
http://forum.xda-developers.com/showpost.php?p=69758375&postcount=89
http://forum.xda-developers.com/le-2/help/x522-stock-019s-rom-lost-imei-baseband-t3505356
fixed it.
ExTREmE99 said:
http://forum.xda-developers.com/le-2/help/x522-stock-019s-rom-lost-imei-baseband-t3505356
fixed it.
Click to expand...
Click to collapse
Hey man,
I followed your instructions in your post in that thread, but the modified ota update fails to flash as well, and upon reboot I'm back at my old home screen. Perhaps it was an error on my part throughout the bootloader unlock process; I'm also dumb and didn't know how to boot TWRP into read-only mode (what I did was check the "mount system as read-only" option in the "Mount" menu, don't know if that was right!).
Either way, congrats on getting your phone back to receiving OTAs!
Somebody still have a TWRP untouched system partition might try a dd backup. So we can compare where the different are
rainlake said:
Somebody still have a TWRP untouched system partition might try a dd backup. So we can compare where the different are
Click to expand...
Click to collapse
I just got a new phone..let me know what needs to be done to get backup of stock ROM/recovery which can be later flashed to take OTA updates