Is there a way to install the d003 ota update from TWRP on a rooted 5x KIW-L24 running B331? The updater pops up every time I boot up, but that method fails. Could it be because I used that script to remove stuff preinstalled on my phone?
bigman1 said:
Is there a way to install the d003 ota update from TWRP on a rooted 5x KIW-L24 running B331? The updater pops up every time I boot up, but that method fails. Could it be because I used that script to remove stuff preinstalled on my phone?
Click to expand...
Click to collapse
It would not update on mine with stock rom and twrp recovery. I think you need to go stock recovery and then update. You can reflash custom recovery and root once it's done. The D003 update definitely took care of my horrible GPS accuracy and fix.
cheers
I flashed the stock b331 recovery. Restored a b331 nandroid. Tried to ota, failed. Dowloaded the full image and did the dload folder reboot to stock recovery method. Fails out at 5%. Tried flashing the update.zip through twrp, fails. tried the newest b331 recovery from the repo, tried to dload folder again. fails... HELP!!!!! please?
bircky311 said:
I flashed the stock b331 recovery. Restored a b331 nandroid. Tried to ota, failed. Dowloaded the full image and did the dload folder reboot to stock recovery method. Fails out at 5%. Tried flashing the update.zip through twrp, fails. tried the newest b331 recovery from the repo, tried to dload folder again. fails... HELP!!!!! please?
Click to expand...
Click to collapse
I used the stock b331 plus stock recovery zip (July 31?) provided in the how to return to stock thread and did a factory reset before boot. It sounds like you still had a custom recovery. That will not work.
You need to be complete stock to be able to install an OTA. It's because it's a file patcher, if files are missing, or modified, it will fail.
That worked !!! Thanks a bunch. Nandroiding a fresh reset for future flubs.
Good !
bircky311 said:
That worked mooms! Thanks a bunch. Nandroiding a fresh reset for future flubs.
Click to expand...
Click to collapse
You are welcome
Related
I have received the OTA update for my stock rooted 4.3 device. When I tell the system to update, it reboots into recovery, which for me is TWRP. If I go to "install" it defaults to the sdcard/downloads folder and there is a file there called: ota_M7_UL_SENSE55-MR_TMOUS_4.19.531.10-3.24.531.3_release_351678 If I choose to "install" this, there's a bunch of error messages, first with "unable to locate zip" (references a specific file), followed by an "assert failed" and the "error executing update binary..."
I will assume that this is because of the fact that I'm rooted and have TWRP.
It's important for me to be stock (I need the TM WiFi calling) and I want to retain root. Given that, how can I update to Kit Kat?
You'll have to flash back to stock recovery and redo the OTA (or, if you know where the OTA file is on your device, boot into stock recovery and select that file for the update).
You will most likely loose root, but it's easy enough to reflash TWRP and superuser to get root back, I would imagine.
knytphal said:
You'll have to flash back to stock recovery and redo the OTA (or, if you know where the OTA file is on your device, boot into stock recovery and select that file for the update).
You will most likely loose root, but it's easy enough to reflash TWRP and superuser to get root back, I would imagine.
Click to expand...
Click to collapse
I found and flashed a stock recovery and then reran the OTA update. It appeared to have gone all the way through the process. When I reboot the device I get a pink screen that blinks with white dashes, and it does get to an HTC One splash screen with a blue beats audio icon (different than in 4.3). It never gets passed there.
I am able to adb and fastboot at that screen, so I was able to reflash TWRP, and tried rebooting, but get stuck at the same spot. I had done a TWRP backup a couple weeks ago, so I restored that so that at least I'm functional again.
Any advice on how to get 4.4 on this device?
When I was unlocked and rooted on 4.3 I relocked the bootloader, ran the 4.3 RUU and was able to get the OTA update then re-unlock and re-root
Basically, I did the same thing gwingzero said he did in this post
I rooted my LG G3 with StumpRoot. Everything went fine and I had successful root. Checked it and all. Then I flashed the new Barren ROM (v1) and I lost root. I tried re-running StumpRoot and StumpRoot is claiming I already have my device is already rooted. However, any application that requires root or Superuser, it says that root is not detected. I have Superuser on my phone.
Did you flash through TWRP?
Can you still boot into recovery, and does TWRP come up as your recovery?
This ^^^^^
I have no idea how you can lose root when it's built into it.
Now if you took the OTA update then you will lose root.
Then you have to revert back to zv4 via Flashtool if you want root again.
The FAQ, and the ZV6 threads have all to info you need.
engine95 said:
This ^^^^^
I have no idea how you can lose root when it's built into it.
Now if you took the OTA update then you will lose root.
Then you have to revert back to zv4 via Flashtool if you want root again.
The FAQ, and the ZV6 threads have all to info you need.
Click to expand...
Click to collapse
I don't know how I lost root either. I did not do any OTA updates. All I did was "Update Profile" to get my data working again. I've rooted and flashed roms on many phones, never had this issue until the G3.
CodeCompile said:
I don't know how I lost root either. I did not do any OTA updates. All I did was "Update Profile" to get my data working again. I've rooted and flashed roms on many phones, never had this issue until the G3.
Click to expand...
Click to collapse
Did you unlock the bootloader with "Bump", so you have TWRP?
Then just flash the Rom again. Or any Rom for that matter
engine95 said:
Did you unlock the bootloader with "Bump", so you have TWRP?
Then just flash the Rom again. Or any Rom for that matter
Click to expand...
Click to collapse
I downloaded the TWRP listed on some thread on Sprint LG G3 then used flashify on my rooted G3 to flash it, after that I flashed the custom ROM using TWRP.
Since then, I tried to boot into recovery (power+volume down) and it just booted into safe mode.
Also, if/when I do boot it into recovery, should I also try flashing a SuperSU rom too?
CodeCompile said:
I downloaded the TWRP listed on some thread on Sprint LG G3 then used flashify on my rooted G3 to flash it, after that I flashed the custom ROM using TWRP.
Since then, I tried to boot into recovery (power+volume down) and it just booted into safe mode.
Also, if/when I do boot it into recovery, should I also try flashing a SuperSU rom too?
Click to expand...
Click to collapse
The only thing I can think of is that the download was corrupt. I would try flashing TWRP with Flashify again. If that works, then reinstall SuperSU. That should get you root back. Then download a ROM again, verify the MD5, and flash in TWRP.
If Flashify won't run, then try reinstalling SuperSU, and see if that helps. If not, I think you'll have to revert to the stock ZV4 ROM with LG's Flashtool.
I suggest the Barrin V2 ROM. It's the latest version of Barren, built on the ZV6 ROM instead of ZV4: http://forum.xda-developers.com/sprint-lg-g3/development/rom-barrin-odexed-deodexed-t2950747
I tried using flashify and it gave me an error saying I needed root. I tried booting intorecovery husing the instructions and it either just boots up regularly or goes into safe mmode. Have I bricked my phone to this Rom?
Revert to stock as explained here:http://forum.xda-developers.com/spr...de-how-to-restore-sprint-lg-g3-ls990-t2852042
Then reroot, and start over.
As the heading says, I need help installing lollipop using TWRP, sideloading the .zip fails every time. Any suggestions, it would be nice to install this update as it doesn't seem to be coming as an OTA any time soon for me. Thanks.
Well, the OTA came in this morning and saved the day. I reflashed stock recovery just in case, so it wouldn't brick like my G3 did when I tried to install an OTA. I then rebooted after flahing stock and installed the update. All is well.
rjzmanz said:
Well, the OTA came in this morning and saved the day. I reflashed stock recovery just in case, so it wouldn't brick like my G3 did when I tried to install an OTA. I then rebooted after flahing stock and installed the update. All is well.
Click to expand...
Click to collapse
Glad you got it working, it would seem that you need stock recovery to flash the OTA as the TWRP recovery causes the ZIP's version check asserts to fail. So you wouldn't have bricked, it just wouldn't have installed for you.
I have an HTC One M8 with ROM 4.16.1540.8 (5.0.1)
I'm trying to remove my SuperSU app so that i can downgrade it to a lower version(2.20) due to incompatibility with some of my apps (puzzle and dragons).
Bootloader is unlocked and it is s-on.
I have tried removing SuperSU through the app itself by using the reinstall, switch superuser app, and full unroot functions, but everytime I restarted the phone superSU would be back and in version 2.46. I also tried manually deleting the apk and su files in the bin and xbin folders in system using es file explorer but a restart just brought those back too.
Any help would be greatly appreciated. Thanks!
Find the flashable zip for the "older" version and flash in recovery. I would think that should do it.
Hi thanks for the reply.
I flashed superSU 2.23 from recovery, but i got stuck in bootloop. What should i do to fix it? Thanks!
Edit: flashed the updated su back in and got out of it. How do i do the downgrade without a bootloop?
ah46657 said:
Hi thanks for the reply.
I flashed superSU 2.23 from recovery, but i got stuck in bootloop. What should i do to fix it? Thanks!
Edit: flashed the updated su back in and got out of it. How do i do the downgrade without a bootloop?
Click to expand...
Click to collapse
Hmm, wouldn't expect that to happen. Obviously, since I would never intentionally bootloop someone!
Flash the stock ROM or restore stock nandroid. Then flash the desire SuperSU zip. That's the best I can think of.
Make a nandroid backup of your current setup (if you haven't already) to revert to "just in case".
how to unflash supersu zip
redpoint73 said:
Hmm, wouldn't expect that to happen. Obviously, since I would never intentionally bootloop someone!
Flash the stock ROM or restore stock nandroid. Then flash the desire SuperSU zip. That's the best I can think of.
Make a nandroid backup of your current setup (if you haven't already) to revert to "just in case".
Click to expand...
Click to collapse
recently i installed lineage os 14.1 in my device (rooted) and flashed supersu2.79 , but after updating it it 2.82, its showing SU BINARY OCCUPIED , so can i try downgrade supersu by flshing lower version,, if so how should i unflash previous supersu zip help
rajkumar1221 said:
recently i installed lineage os 14.1 in my device (rooted) and flashed supersu2.79 , but after updating it it 2.82, its showing SU BINARY OCCUPIED , so can i try downgrade supersu by flshing lower version,, if so how should i unflash previous supersu zip help
Click to expand...
Click to collapse
So you tried to flash 2.82? I don't think that is the proper way to update. Since you already have SuperSU installed, you should just be able to go into the SuperSU app, and update the binary from there. Or is that what led to the "binary occupied" error?
But back to the basic question, you can't "unflash" SuperSU. You can "dirty flash" Lineage (just wipe cache and dalvik, can keep user data), and that will put you back on the "unrooted" Lineage ROM. Then you should be able to flash SuperSU 2.82 via zip.
redpoint73 said:
So you tried to flash 2.82? I don't think that is the proper way to update. Since you already have SuperSU installed, you should just be able to go into the SuperSU app, and update the binary from there. Or is that what led to the "binary occupied" error?
But back to the basic question, you can't "unflash" SuperSU. You can "dirty flash" Lineage (just wipe cache and dalvik, can keep user data), and that will put you back on the "unrooted" Lineage ROM. Then you should be able to flash SuperSU 2.82 via zip.
Click to expand...
Click to collapse
i unrooted my device now,, should i have to "first root" it with official lineage os extra file addonsu arm and then should i have to flash supersu zip ?
rajkumar1221 said:
i unrooted my device now,, should i have to "first root" it with official lineage os extra file addonsu arm and then should i have to flash supersu zip ?
Click to expand...
Click to collapse
I don't personally use Lineage. I believe you will need to flash both of those, yes.
@redpoint73 , found this script made by osm0sis to "unSU". not sure if is relevant to earlier posts but thought maybe if you havent seen it yet would be worth looking at. maybe could help someone.?
http://forum.xda-developers.com/showthread.php?p=63615067
I rooted and installed TWRP recovery. I want to update my stock rom with the OTA update. The update is downloaded to my phone, but won't update, re-boots and goes into TWRP. I think I need to first install a stock recovery, but I can't find one. If I find the stock recovery will that allow me to update OTA.
cma371 said:
I rooted and installed TWRP recovery. I want to update my stock rom with the OTA update. The update is downloaded to my phone, but won't update, re-boots and goes into TWRP. I think I need to first install a stock recovery, but I can't find one. If I find the stock recovery will that allow me to update OTA.
Click to expand...
Click to collapse
As long as you haven't modified your rom you should be able to take the OTA with a STOCK recovery. You can find them here.
Also you might want to unroot before taking the OTA then reroot afterwards.
Got the ota and clicked install by mistake with stock recovery and root. It failed and had to do a battery pull to get it to boot. So yeah I'd unroot just in case.
I unrooted and installed stock recovery, but update failed?