I have read and appears that I have to downgrade but I am not sure. Please advise
Thanks
docmarioce said:
I have read and appears that I have to downgrade but I am not sure. Please advise
Thanks
Click to expand...
Click to collapse
What you read is correct. You have to downgrade to 10b to root. After that, if you want to go back to 12b rooted, do NOT bump with TWRP. Instead, tell SuperSU to maintain root across OTAs and then take each OTA as it comes. When you are finally on 12b, you can either leave it as is (not bumped) or install TWRP to bump it. Reason you cannot bump is because you need the stock recovery (not TWRP) to install the OTAs.
How do we go about doing that process? Can someone point me in that direction plz
mrlee19 said:
How do we go about doing that process? Can someone point me in that direction plz
Click to expand...
Click to collapse
general forum, return to stock thread.
Ok just asking because ive saw a few post.. And ppl were saying that method wasnt working but ill check again.. Thanks
mrlee19 said:
Ok just asking because ive saw a few post.. And ppl were saying that method wasnt working but ill check again.. Thanks
Click to expand...
Click to collapse
if the "tot" method doesnt work, the "kdz" should. but afterwards, you still need to use the tot method to get back on the update path.
iBolski said:
What you read is correct. You have to downgrade to 10b to root. After that, if you want to go back to 12b rooted, do NOT bump with TWRP. Instead, tell SuperSU to maintain root across OTAs and then take each OTA as it comes. When you are finally on 12b, you can either leave it as is (not bumped) or install TWRP to bump it. Reason you cannot bump is because you need the stock recovery (not TWRP) to install the OTAs.
Click to expand...
Click to collapse
Thanks I have downgraded and rooted my phone. I want to be able to install kit Kat ROMs. I don't care about taking OTA to 12B if I can install ROMs based in 12B anyway. Should I bump with TWRP? Are there any bumped ROMs that are worth it? I am not planning in installing android L in my device in the future anyways since my Samsung Gear 2 watch won't work with it. I just want to start flashing this phone away.
Thanks
docmarioce said:
Thanks I have downgraded and rooted my phone. I want to be able to install kit Kat ROMs. I don't care about taking OTA to 12B if I can install ROMs based in 12B anyway. Should I bump with TWRP? Are there any bumped ROMs that are worth it? I am not planning in installing android L in my device in the future anyways since my Samsung Gear 2 watch won't work with it. I just want to start flashing this phone away.
Thanks
Click to expand...
Click to collapse
Before you can even begin to flash ROMs, you have to install TWRP.
As for which ROMs are worth it, I have no idea. Most are LP ROMs and currently LP is not completely stable and there still are issues to be worked out.
I myself am happy running full stock 12B rooted. I am bumped in case I want to flash a ROM, but at this time, I don't have any desire to flash a ROM at the current moment.
Best thing is to go and read about the ROMs in the developer section. Note what issues people are having and which ROM is best for you is up to you. Everyone has their preferences. Asking "which ROM is the best" is not a question that can be answered since it's all down to personal preferences and what issues you can live with.
If you have twrp installed. First thing you have to do is backup your stock rom
You don't "bump with twrp".
Normally code in the bootloader prevents the loading of unsigned stuff like kernels and custom recoveries. That includes TWRP, but Team Codefire figured out a way to fake the signature onto things like twrp and aosp ROMs, by changing slightly their images. This allows them to load.
iBolski said:
Before you can even begin to flash ROMs, you have to install TWRP.
As for which ROMs are worth it, I have no idea. Most are LP ROMs and currently LP is not completely stable and there still are issues to be worked out.
I myself am happy running full stock 12B rooted. I am bumped in case I want to flash a ROM, but at this time, I don't have any desire to flash a ROM at the current moment.
Best thing is to go and read about the ROMs in the developer section. Note what issues people are having and which ROM is best for you is up to you. Everyone has their preferences. Asking "which ROM is the best" is not a question that can be answered since it's all down to personal preferences and what issues you can live with.
Click to expand...
Click to collapse
A quick question: If you had to flash back to 10b to be Rooted and Bumped how did you wind up on a fully stock 12b rooted and bumped if you did not flash a rom. You should not have been able to upgrade if you downgraded your phone to 10b to root and bump which if I recall takes away the ability to upgrade to 12b while rooted and bumped without flashing a rom. Or do you have another method? Thanks.
Jimi Mack said:
A quick question: If you had to flash back to 10b to be Rooted and Bumped how did you wind up on a fully stock 12b rooted and bumped if you did not flash a rom. You should not have been able to upgrade if you downgraded your phone to 10b to root and bump which if I recall takes away the ability to upgrade to 12b while rooted and bumped without flashing a rom. Or do you have another method? Thanks.
Click to expand...
Click to collapse
So far from all I have read, users have been able to progress from 10B to 11C and on to 12B all while maintaining root. You can only gain root, however, while on 10B. Once you have root you can install TWRP whenever. However, you cannot take an OTA while you have TWRP installed....I mean you can, but you'll get stuck in a boot loop By far the easiest and best thing to do if you're looking for stability and compatibility of stock would be to install an awesome, stock-based rom like Jasmine rom - that way you get all the benefits of the latest VZW updates, while keeping all the stability of full stock, and not "risking" anything by accidentally accepting some OTA down the road. Just my 2 cents!
Jimi Mack said:
A quick question: If you had to flash back to 10b to be Rooted and Bumped how did you wind up on a fully stock 12b rooted and bumped if you did not flash a rom. You should not have been able to upgrade if you downgraded your phone to 10b to root and bump which if I recall takes away the ability to upgrade to 12b while rooted and bumped without flashing a rom. Or do you have another method? Thanks.
Click to expand...
Click to collapse
I didn't bump until after I otad to 12b. First, I stumped rooted on 10b. Then I told SuperSU to maintain root across otas. Once I updated to 12b, that's when I bumped in case I wanted to flash a rom or do a nandroid backup.
Of course, if a new ota comes out, I'll have to downgrade back to 10b and root again before I can take it.
Sent from my Nexus 7 using Tapatalk
iBolski said:
I didn't bump until after I otad to 12b. First, I stumped rooted on 10b. Then intokd SuperSU to maintain root across otas. Once I updated to 12b, that's when I bumped in case I wanted to flash a rom or do a nandroid backup.
Of course, if a new ota comes out, I'll have to downgrade back to 10b and root again before I can take it.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
That is what I had thought but was not sure if I missed a method other than that, thank you.
Related
Hey guys,
So as the thread title states, I have a rooted DNA with an unlocked bootloader and now S-OFF. I'm wholly new to this whole "forcing" of an OTA upon me (by Verizon?)...so I don't know what the best course of action is. I've already flashed the radio from the OTA and I'm just waiting for an attractive custom ROM to come out before flashing one. In the meantime, what should I do? I saw this thread:
(Mod)[2.15.13] Stop/Remove Verizon OTA V2 2.04.605.2 710RD (http://forum.xda-developers.com/showthread.php?t=2149417)
Idk...I'll do it if I have to...it just seems a bit drastic in what it removes. Is there a safe way to update my firmware/kernel to that of the OTA while keeping my unlocked bootloader/root/s-off? I'm used to Nexus devices so this is all very strange to me...any help would be greatly appreciated, thanks!
mtmjr90 said:
Hey guys,
So as the thread title states, I have a rooted DNA with an unlocked bootloader and now S-OFF. I'm wholly new to this whole "forcing" of an OTA upon me (by Verizon?)...so I don't know what the best course of action is. I've already flashed the radio from the OTA and I'm just waiting for an attractive custom ROM to come out before flashing one. In the meantime, what should I do? I saw this thread:
(Mod)[2.15.13] Stop/Remove Verizon OTA V2 2.04.605.2 710RD (http://forum.xda-developers.com/showthread.php?t=2149417)
Idk...I'll do it if I have to...it just seems a bit drastic in what it removes. Is there a safe way to update my firmware/kernel to that of the OTA while keeping my unlocked bootloader/root/s-off? I'm used to Nexus devices so this is all very strange to me...any help would be greatly appreciated, thanks!
Click to expand...
Click to collapse
Would like to know what to do - I postponed my update to tomorrow, so if no one replies to this thread I am going to follow the other thread.
http://forum.xda-developers.com/showthread.php?t=2152993
According to jcase beaups and Dr_drache and zifnab its OK to take the ota with s-off
And then I'm telling you to do it at your own risk
The OTA from what I've seen (and experienced) does not lock the bootloader and also shouldn't affect the s-off according to those guys
Sent from my Nexus 7 using XDA Premium HD app
.torrented said:
According to jcase beaups and Dr_drache and zifnab its OK to take the ota with s-off
And then I'm telling you to do it at your own risk
The OTA from what I've seen (and experienced) does not lock the bootloader and also shouldn't affect the s-off according to those guys
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Yes, but I think you must be on stock rom and stock recovery. I'm on stock rom but not stock recovery. Can anyone confirm if the steps would be (for someone on stock rom, TWRP, rooted, unlocked, S-OFF):
1. Flash stock recovery
2. Update OTA
3. Flash back TWRP
Or do we need to unlock again between steps 2 and 3 or take any other steps? Or is there a flashable OTA zipped up that will update everything? I don't mind waiting by the way. Not in a huge hurry... Thanks in advance, you guys are awesome.
n8mack33 said:
Yes, but I think you must be on stock rom and stock recovery. I'm on stock rom but not stock recovery. Can anyone confirm if the steps would be (for someone on stock rom, TWRP, rooted, unlocked, S-OFF):
1. Flash stock recovery
2. Update OTA
3. Flash back TWRP
Or do we need to unlock again between steps 2 and 3 or take any other steps? Or is there a flashable OTA zipped up that will update everything? I don't mind waiting by the way. Not in a huge hurry... Thanks in advance, you guys are awesome.
Click to expand...
Click to collapse
should work with stock recovery (you might need the stock kernel too not sure)
If you flash the whole OTA package you'll also need /system to be mostly stock, along with stock recovery and kernel.
Or, you could try what I did and download the OTA from the dev section, remove /system, /boot (kernel), and /recovery updates from it and flash the new zip from RUU mode (fastboot oem rebootRUU). However, this is somewhat involved and not user friendly. Also, if you do this, when you flash it it usually says to "flush the update again", in which case you simply run the fastboot flash zip [file] again (it *might* result in a brick if not done correctly).
Better yet, chances are a dev will put together a firmware package which can be easily flashed with a guide on how to do it. If you aren't confident about flashing the firmware, its best to wait for something like this.
Hm...okay...if I just wait until the day I "deferred" the OTA until, will I be able to defer again (and again, and again, etc)? If so, I can just keep doing that until there's a safe way to flash either the update itself or a custom ROM that interests me.
I just want to add that this whole situation is absurd.
mtmjr90 said:
Hm...okay...if I just wait until the day I "deferred" the OTA until, will I be able to defer again (and again, and again, etc)? If so, I can just keep doing that until there's a safe way to flash either the update itself or a custom ROM that interests me.
I just want to add that this whole situation is absurd.
Click to expand...
Click to collapse
Go to the droid original dev thread and get the notification remover that justin (nitsuj) posted. Dl and flash it via recovery and you won't have to worry about deferring anymore.
So I used saferoot to root back at the 4.3 update; however, overnight one night my phone decided to install the tiny update Verizon pushed that kept 4.3 but took away root. Now I am trying to update to 4.4.2 via OTA update but it continuously fails...Since I've lost root already, I'm looking for a way to manually install the 4.4.2 update (knowing I won't have root access..but I don't know so...) or revert back to an 4.3 so I can root again with safestrap...
Can anyone offer any insight on either of these options? I'd probably prefer to revert to 4.3 and have root over 4.4.2 without....
Phone Details
FYI
Android Version - 4.3
Baseband Version - I605VRUAND3
kbrown.1407 said:
So I used safestrap to root back at the 4.3 update; however, overnight one night my phone decided to install the tiny update Verizon pushed that kept 4.3 but took away root. Now I am trying to update to 4.4.2 via OTA update but it continuously fails...Since I've lost root already, I'm looking for a way to manually install the 4.4.2 update (knowing I won't have root access..but I don't know so...) or revert back to an 4.3 so I can root again with safestrap...
Can anyone offer any insight on either of these options? I'd probably prefer to revert to 4.3 and have root over 4.4.2 without....
Click to expand...
Click to collapse
If you're on 4.3 w/o root, you can follow this thread and regain root. - http://forum.xda-developers.com/showthread.php?t=2752360
I haven't see anyone post 4.4.2 yet to manually flash if the download fails. I'm the same boat there. Give it a few days and I'm sure someone will post it.
Thanks
xnatex21 said:
If you're on 4.3 w/o root, you can follow this thread and regain root. - http://forum.xda-developers.com/showthread.php?t=2752360
I haven't see anyone post 4.4.2 yet to manually flash if the download fails. I'm the same boat there. Give it a few days and I'm sure someone will post it.
Click to expand...
Click to collapse
Thanks, I actually came across that post just a bit ago (apparently gave up on finding an answer a bit early, sorry). One other question though, if and/or when someone posts 4.4.2, is there a way to update manually and maintain root access? Or is root lost once it's updated in any way?
kbrown.1407 said:
Thanks, I actually came across that post just a bit ago (apparently gave up on finding an answer a bit early, sorry). One other question though, if and/or when someone posts 4.4.2, is there a way to update manually and maintain root access? Or is root lost once it's updated in any way?
Click to expand...
Click to collapse
The only way you'd be able to get root is if someone finds a root exploit for this specific device and 4.4.2 (assuming you're on 4.3 with a locked bootloader already).
If you don't have a locked bootloader, then you can flash custom 4.4.x roms with root.
But if you are on a custom rom with an unlocked bootloader and you ODIN to the stock Verizon 4.4.2 that rolled out yesterday, you'd get a locked (possibly permanently) bootloader and a potentially un-rootable 4.4.2 rom.
xnatex21 said:
The only way you'd be able to get root is if someone finds a root exploit for this specific device and 4.4.2 (assuming you're on 4.3 with a locked bootloader already).
If you don't have a locked bootloader, then you can flash custom 4.4.x roms with root.
But if you are on a custom rom with an unlocked bootloader and you ODIN to the stock Verizon 4.4.2 that rolled out yesterday, you'd get a locked (possibly permanently) bootloader and a potentially un-rootable 4.4.2 rom.
Click to expand...
Click to collapse
I am on 4.3 with the locked bootloader. Thanks again for the help.
xnatex21 said:
If you're on 4.3 w/o root, you can follow this thread and regain root. - http://forum.xda-developers.com/showthread.php?t=2752360
I haven't see anyone post 4.4.2 yet to manually flash if the download fails. I'm the same boat there. Give it a few days and I'm sure someone will post it.
Click to expand...
Click to collapse
My update failed too, so I am interested as well if someone has the 4.4.2 official
mgarcia86 said:
My update failed too, so I am interested as well if someone has the 4.4.2 official
Click to expand...
Click to collapse
Mine did the first couple times. What I did was odin to stock 4.3 again and take the small update on 4.3 and then the 4.4.2 worked after that.
Hey guys, I recently downgrade from the latest OTA to 10b via the TOT method and worked great. I rooted the device and then went ahead and "unlocked" the bootloader via the Bump method. I've recently read the threads and 'ish went down. I want to flash a rom on my VZW LG G3, but I don't see any "Bumped" roms. I'm assuming I can't flash anything then? Any assistance on this? Is there an alternate method to flash roms than the Bump unlock method? I appreciate the responses!
If you already bumped your G3, you should be able to boot into TWRP recovery. From there you can flash roms . Just read the OP of each rom developers prereq for further details on their rom. FYI, you should have post this into Q&A section. good luck.
Practically all ROMS available are "bumped" and ready to flash. Just boot into recovery and start flashing. I personally use flashify to boot into recovery. It's easy than the other method.
Just stick to Roms in the vzw g3 android development areas and you should be fine.
jcyoun33 said:
Hey guys, I recently downgrade from the latest OTA to 10b via the TOT method and worked great. I rooted the device and then went ahead and "unlocked" the bootloader via the Bump method. I've recently read the threads and 'ish went down. I want to flash a rom on my VZW LG G3, but I don't see any "Bumped" roms. I'm assuming I can't flash anything then? Any assistance on this? Is there an alternate method to flash roms than the Bump unlock method? I appreciate the responses!
Click to expand...
Click to collapse
Jasmin is a nice stock Rom, very stable.
jcyoun33 said:
Hey guys, I recently downgrade from the latest OTA to 10b via the TOT method and worked great. I rooted the device and then went ahead and "unlocked" the bootloader via the Bump method. I've recently read the threads and 'ish went down. I want to flash a rom on my VZW LG G3, but I don't see any "Bumped" roms. I'm assuming I can't flash anything then? Any assistance on this? Is there an alternate method to flash roms than the Bump unlock method? I appreciate the responses!
Click to expand...
Click to collapse
You down graded from 12b?
mopartonyg said:
You down graded from 12b?
Click to expand...
Click to collapse
Yeah I did. I used the TOT method. Pretty straight forward.
Thanks for the responses. I just wanted to make sure that using the Bump method didn't affect my ability to flash any VZW rom.
Bump does not unlock the Verizon G3. It does nothing at all to the phone. It is applied to things like TWRP so they will appear to be signed with LG keys and be allowed to load. Non stock firmwares and kernels and recoveries must be changed by the bump method to look like they are officially signed. They all are, if you find them discussed here.
The bump method could be broken in any future update, so avoid OTA's at all costs.
Currently installed is SkyDragon. How can I update the phone to a GPE Lollipop ROM? I have S-ON.
catzilla said:
Currently installed is SkyDragon. How can I update the phone to a GPE Lollipop ROM? I have S-ON.
Click to expand...
Click to collapse
There is no official lollipop for AT&T yet, but wonders_never_cease has a dev edition ROM modified for at&t, all the directions to flash it are in the thread, I recommend trying it, very fast with no bugs ?
catzilla said:
Currently installed is SkyDragon. How can I update the phone to a GPE Lollipop ROM? I have S-ON.
Click to expand...
Click to collapse
just flash skydragons lollipop gpe
rbouza1 said:
just flash skydragons lollipop gpe
Click to expand...
Click to collapse
If the OP hasn't updated to 4.4.4 firmware by OTA (and can't do it manually with s-on) broken WiFi may be the result after flashing SD LP.
4.4.4 is reportedly started to roll out today for AT&T (which will update the firmware).
redpoint73 said:
If the OP hasn't updated to 4.4.4 firmware by OTA (and can't do it manually with s-on) broken WiFi may be the result after flashing SD LP.
4.4.4 is reportedly started to roll out today for AT&T (which will update the firmware).
Click to expand...
Click to collapse
How can I update to AT&T's 4.4.4 without unlocking S-On? Is that possible?
I think I read something around here that says that going back from a GPE rom to a carrier rom is impossible unless s-off.
Can you please confirm?
Really, I have absolutely zero need in AT&T's 4.4.4 if there is any way I could jump straight to SkyDragon 5.0 GPE, without screwing up connectivity.
Another thing is, I have an update notification waiting for me (see pic). What will happen if I flash that? Will that completely screw up my phone, or will that get me to Google's stock Lollipop GPE?
catzilla said:
How can I update to AT&T's 4.4.4 without unlocking S-On? Is that possible?
Click to expand...
Click to collapse
Its certainly possible. Either return to stock ROM and stock recovery, and OTA to 4.4.4.
Or alternately, relock the bootloader and flash the 4.4.4 RUU (back any personal data before RUU, all internal storage will be wiped).
catzilla said:
I think I read something around here that says that going back from a GPE rom to a carrier rom is impossible unless s-off.
Can you please confirm?
Click to expand...
Click to collapse
That is incorrect. If you just flash a GPE based ROM, you can freely go back to Sense.
S-off is needed to fully convert to GPE (including GPE CID, bootloader, partitioning, etc.); or alternately, to fully convert a GPE version to Sense.
catzilla said:
Really, I have absolutely zero need in AT&T's 4.4.4 if there is any way I could jump straight to SkyDragon 5.0 GPE.
Click to expand...
Click to collapse
You don't need the ROM, but you absolutely do need the 4.4.4 firmware. If you don't have it, WiFi will be broken. You might also have extremely long boot times (10+ minutes).
And that is the only reason I'm suggesting the OTA, so you can update the firmware without having to s-off.
---------- Post added at 11:22 AM ---------- Previous post was at 11:18 AM ----------
catzilla said:
Another thing is, I have an update notification waiting for me (see pic). What will happen if I flash that? Will that completely screw up my phone, or will that get me to Google's stock Lollipop GPE?
Click to expand...
Click to collapse
With you current setup the OTA won't work:
1) You have to be on a stock ROM or the OTA will fail.
2) You have to be on corresponding stock recovery, or the OTA will not install (phone will loop booting TWRP looking for stock recovery and not finding it).
3) You need the GPE Carrier ID (CID) or OTA will fail. You can't change CID with s-on.
So what you are saying is, my best course of action would be to:
1) Flash stock 4.4.2 (is rooted version okay?)
2) Update to stock 4.4.4 via OTA (is there root available? how do I not lose it?)
3) Flash SkyDragon Lollipop
catzilla said:
So what you are saying is, my best course of action would be to:
1) Flash stock 4.4.2 (is rooted version okay?)
2) Update to stock 4.4.4 via OTA (is there root available? how do I not lose it?)
3) Flash SkyDragon Lollipop
Click to expand...
Click to collapse
1) Rooted is okay, as long as no system files have been altered (which should be the case if its called "stock"). You also need stock recovery.
2) You will lose root. Simply root again. Flash TWRP, and flash SU or SuperSU. Or just boot TWRP, and it will probably ask you if you want to root.
3) Yes.
Alternately, since the 4.4.4 RUU is now available:
- backup any personal data
- Relock bootloader
- RUU
- Re-unlock bootloader and install TWRP
- Flash Skydragon
I can't say RUU methos is necessarily any better or easier. Just another option, really. But it might take the footwork out of finding the right stock ROM and stock recovery combo, and restore the phone to "stock" in one fell swoop.
One last question, and I feel sad for asking this because I really should be able to find it myself: where can I find this mythical 4.4.4 AT&T RUU? I've looked all over the forum but I just don't see it.
Edit: I think I got it. Is this it? http://dl3.htc.com/application/RUU_...40.34.C35006.02_F_release_407726_signed_2.exe
Relocked, ran RUU, unlocked, flashed recovery, flashed rom, currently patiently waiting for it to boot.
I think this is going to work, thanks for all your help! =)
Hey guys. Just got a lg g3 off swappa. Just wanted some information regarding the current state of root/custom roms. Also...should/can I update to the latest OTA or is it only rootable up to a certain version? Thanks!!
dont take no ota's. if u r on 10b u can root and add a recovery by bump. if u r on a later software like 11c or 12b u can go back.
hi. thanks for getting black. can you still root the latest ota?
corz123 said:
hi. thanks for getting black. can you still root the latest ota?
Click to expand...
Click to collapse
Thanks for asking that question! I also picked up a red one off swappa this week to play with., and wanted to know the same. Off to find the downgrade instructions, I'm on 12B.
Curious that you guys would buy a phone that's been out for a while, then look into root and roms.
Would have sucked if there was no way past a certain build.
Just a thought for the future.
All versions can be rooted ATM, iirc. Stump root only works on 10b. There is a different method using adb for other versions. You can downgrade backwards to 10b from all.
Latest ota is 12b. The 23a and 23b ROMs u may see are leaked builds and not official OTA.
Sent from my LG-VS985 using XDA Free mobile app