Related
I rooted using PurpleDrake...
That said my questions are:
If I restore the Stock boot.img & Stock recovery.img then perform a *full Unroot in SuperSU can I install the OTA without issue?
How about system files... Does PurpleDrake change them in any way that could cause the OTA to fail even after reverting back to stock boot, stock recovery and Un-rooting?
* not positive this step is necessary or will even work?
TIA to anyone with input!
AndroidUzer said:
I rooted using PurpleDrake...
That said my questions are:
If I restore the Stock boot.img & Stock recovery.img then perform a *full Unroot in SuperSU can I install the OTA without issue?
How about system files... Does PurpleDrake change them in any way that could cause the OTA to fail even after reverting back to stock boot, stock recovery and Un-rooting?
* not positive this step is necessary or will even work?
TIA to anyone with input!
Click to expand...
Click to collapse
Wondering same thing. How to get update, the reroot without having to do a full return to stock first.
Try it and let us know. As long as you don't have twrp installed you won't bootloop. If it does get hung up at all just battery pull and boot normally. At worst it won't take and you'll stay on c.
It worked!
Swizzle82 said:
Try it and let us know. As long as you don't have twrp installed you won't bootloop. If it does get hung up at all just battery pull and boot normally. At worst it won't take and you'll stay on c.
Click to expand...
Click to collapse
Here's the steps that worked for me, your mileage may vary.
Made sure all factory apps were present and or defrosted.
Restored the factory recovery and factory boot image (thanks autoprime) with Flashify.
Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_00-D85110m_00_update.zip" to the Cache folder.
Re-Enabled OTA using dialer code for hidden menu.
Opened Settings > About phone > Update Center > System updates and was met with the Android System Update screen showing the update "Downloaded and verified 154.6MB", hit the "Restart & install" button and it rebooted to factory recovery installed the update without issue.
No data was lost, No reflashing factory "c" image wiping all your data and having to upgrade from there.
I did lose root but it took <2 minutes to get it back.
I know I could have waited for a TWRP update zip but I ran out of patience.
AndroidUzer said:
Here's the steps that worked for me, your mileage may vary.
Made sure all factory apps were present and or defrosted.
Restored the factory recovery and factory boot image (thanks autoprime) with Flashify.
Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_00-D85110m_00_update.zip" to the Cache folder.
Re-Enabled OTA using dialer code for hidden menu.
Opened Settings > About phone > Update Center > System updates and was met with the Android System Update screen showing the update "Downloaded and verified 154.6MB", hit the "Restart & install" button and it rebooted to factory recovery installed the update without issue.
No data was lost, No reflashing factory "c" image wiping all your data and having to upgrade from there.
I did lose root but it took <2 minutes to get it back.
I know I could have waited for a TWRP update zip but I ran out of patience.
Click to expand...
Click to collapse
Hey, I've been searching through the forums trying to find the stock recovery/boot images for the last hour to no avail. Would it be possible for you to post links to where you found them? Thanks!
EDIT: Annnnnnnnnnd of course as soon as I ask, I find it in another thread I was reading http://forum.xda-developers.com/showpost.php?p=55359856&postcount=125
Where can i found the stock boot.image and stock recovery.img
bjg020683 said:
Where can i found the stock boot.image and stock recovery.img
Click to expand...
Click to collapse
Link in post just above yours...
Thanks
Hi, I think I follow all of your steps except confused about this one:
"Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_ 00-D85110m_00_update.zip" to the Cache folder."
Can someone explain what the above means? Thanks!
laoh said:
Hi, I think I follow all of your steps except confused about this one:
"Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_ 00-D85110m_00_update.zip" to the Cache folder."
Can someone explain what the above means? Thanks!
Click to expand...
Click to collapse
That is the actual "m" build OTA update zip file. Why not go straight to "r"?
The only reason I had to restore it was because I had deleted it in the 1st place.
Check your Cache folder for any update zip that may be waiting already.
I did it this way only because I was too impatient to wait for the update zips to be posted here.
But now they exist...
Here is a better way:
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and follow the TWRP instruction for flashing KK builds D85110 C, M, R Untouched_Stock_Restore.zip or even Lollipop D85120B
This will allow you to go straight to "r" skipping "m" all together.
If you are feeling brave and competent you could go straight to Lollipop...
Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
Good luck!
AndroidUzer said:
That is the actual "m" build OTA update zip file. Why not go straight to "r"?
The only reason I had to restore it was because I had deleted it in the 1st place.
Check your Cache folder for any update zip that may be waiting already.
I did it this way only because I was too impatient to wait for the update zips to be posted here.
But now they exist...
Here is a better way:
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and follow the TWRP instruction for flashing KK builds D85110 C, M, R Untouched_Stock_Restore.zip or even Lollipop D85120B
This will allow you to go straight to "r" skipping "m" all together.
If you are feeling brave and competent you could go straight to Lollipop...
Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
Good luck!
Click to expand...
Click to collapse
Thanks for the lengthy explanation. Can I verify if what I'm trying to do is same as what you've done? Here's my situation.
- I have the stock LG 4.4.2 KK rom for D851. Not stock AOSP or CM or any other "custom ROM".
- It is rooted and have TWRP
- The only thing I've really done to the rom is to debloat - used Titanium to freeze lots of apps that came with the LG rom. I have not deleted any since I've read before that if you delete them, it will make it a pain to upgrade to newer Android versions.
So I've learned the hard way trying to update my phone from 4.4.2 to 5.0.1 LG rom.
- I took the OTA and tried to install it. Big mistake. I ended up in a TWRP bootloop. Had me cringing thinking I just lost everything until I found this post http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508 and fixed it with LG_G3_Flash2FixStuckRecovery.zip (flashed it with TWRP). What a godsend it was. Got me out of bootloop and I didn't have to do factory reset or anything. All my apps and data are intact just the way it was before I began OTA.
- So now I'm back to where I started originally before attempting to OTA to Lollipop.
If I'm reading correctly, what I need to do are:
- Unfreeze all apps
- Restore stock recovery (recovery.img) and boot file (boot.img) - this essentially reverses root and custom recovery. Use Flashify to do so.
- Flash the stock LG Lollipop update (btw - the phone says that the new ROM is already downloaded and ready to go but there's nothing in the cache folder... is there somewhere else I should be looking?)
- Before I reboot - I should flash SuperSU and TWRP which restores root and custom recovery
- Reboot phone, cross fingers.
Somewhere in the middle, am I reading that you need to restore LG stock Kitkat rom first (which I already am on), then update to Lollipop? I'm reading that from this part "This will allow you to go straight to "r" skipping "m" all together. If you are feeling brave and competent you could go straight to Lollipop..."
I'm confused here...
One last thing - Once I'm upgradded to Lollipop, is there an easy way to freeze all the apps I had frozen before instead of going one by one? I have the paid Titanium version but I can't figure out if it has a batch/mass freeze feature.
Thanks!!
No, sorry but you are way off base. I think you either did not read my post carefully or you totally misunderstood what I was trying to say.
You don't have to do the steps I did, they are not necessary with the files available at the linked post below.
Yes you can go straight to lollipop but for someone like yourself I would reccomend downloading and flashing KK build "r"
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and READ THE ENTIRE OP CAREFULLY then follow the TWRP Files/flashing guide for flashing KK build D85110R-Untouched_Stock_Restore.zip
*Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
This will at least update you to the last build "r" of Kit Kat
Lollipop for the D851 still has some bugs to be worked out but you can flash it if you want.
You are on your own now...
Good luck!
AndroidUzer said:
No, sorry but you are way off base. I think you either did not read my post carefully or you totally misunderstood what I was trying to say.
You don't have to do the steps I did, they are not necessary with the files available at the linked post below.
Yes you can go straight to lollipop but for someone like yourself I would reccomend downloading and flashing KK build "r"
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and READ THE ENTIRE OP CAREFULLY then follow the TWRP Files/flashing guide for flashing KK build D85110R-Untouched_Stock_Restore.zip
*Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
This will at least update you to the last build "r" of Kit Kat
Lollipop for the D851 still has some bugs to be worked out but you can flash it if you want.
You are on your own now...
Good luck!
Click to expand...
Click to collapse
I appreciate all of your advice. The thing is, I'm trying to upgrade to Lollipop... I'm already on Kitkat and not really interested in upgrading to a latter dot version of Kitkat.... It just seems like a difficult proposition to do OTA upgrade if you rooted and have non-stock recovery. Since I'm on tmobile d851 stock Kitkat (rooted with frozen apps), I should've never put put TWRP. I thought I might put custom ROM on it but never got around to it and since you pretty much lose wifi calling with non-Tmobile ROMs, I just never did... More of a pain now....
Hey Guys,
I just got a new Samsung Galaxy S3 SGH-I747 in the mail and I immediately started to install Cyanogenmod. I have installed it on two S3's in the past, but this time I had no idea about the new bootloader problems after Android 4.3 (I think?). I got CWM touch installed with no problems via Odin, but when I tried to use the Unified Android Toolkit thing to root and stuff I got stuck in a boot loop. The phone would not boot past the Samsung logo, not the animated one with the purple light, but the one that shows the phone model.
I have tried everything I could think of and all that I tried to google for the past couple hours to no avail. I stupidly did not make a backup of my stock ROM, and I couldn't find a stock 4.4.2 ROM except this one that says it is stock but with root. I flashed that ROM and then it booted past the Samsung logo and the animated one, but is now stuck on the AT&T logo. I looked up that problem and couldn't find any real information on that problem except one thread where it said I should install Kies and let it do the Firmware Upgrade and Initialisation option. That failed and then my phone would only turn on straight to download mode.
I reflashed CWM and that worked so I thought that if I tried to install Cyanogenmod 11 it might work because that ROM is 4.4.1 or higher (Again, I think?). Now it's back into the loop where it makes it past the samsung stuff but then gets stuck on the AT&T logo. Is there anything I can do?
Thanks,
Jemimacakes
Did you try wiping cache, data, and Dalvik in CWM?
Did you try installing CM10.2 from CWM?
audit13 said:
Did you try wiping cache, data, and Dalvik in CWM?
Did you try installing CM10.2 from CWM?
Click to expand...
Click to collapse
Yes, I have tried clearing stuff in both CWM and stock recovery. Im not sure about the Dalvik one though, unless that is cleared when you do factory reset and clear cache I didnt do it. I can try flashing CM10.2 ( which I would prefer to have over 11), but my understanding is that my boot loader will not let me install anything that uses any lower versions of android, but I'll give it a shot and let you know.
Ok guys,
I tried to install Cyanogenmod 10.2 and when I put it on my sd card and tried to install it with CWM It threw and ton of errors that look like this.
assert failed: getprop("ro.bootloader") == "I747UCDLK3" || getprop("ro.bootloader") == "I747UCDMG3" || etc etc.
Im not super experienced with programming, but im guessing that CM10.2 can find any bootloader it can use? Im not sure what my bootloader is if that is the case, but I can boot into recovery so I must have something, right?
Anything I can do?
Thanks
Jemimacakes
You should try flashing cm10.2 just to see if you can get your phone to boot. By booting the phone, you can determine your bootloader and modem.
Edit: okay, cm10.2 doesn't work. Are you running the latest version of cwm? Maybe try twrp?
Hey,
I did have the latest version of CWM, but I tried it on TWRP and got the same errors
audit13 said:
You should try flashing cm10.2 just to see if you can get your phone to boot. By booting the phone, you can determine your bootloader and modem.
Edit: okay, cm10.2 doesn't work. Are you running the latest version of cwm? Maybe try twrp?
Click to expand...
Click to collapse
Hey,
I have now tried both custom recoveries and gotten the same errors on both, and I made sure I had the latest version of each. Can I flash the firmware from 4.3 and then install CM10.2? Will that work? I really don't want to hard brick my phone.
EDIT: I installed ADB to find out what my bootloader was, and it returned that I had the NE4 version. Is there a way to get the MJB version safely so I can install 10.2?
At this point I just want it to boot up to anything, so if that is easier to do than get CM to work then im completely open.
You cannot go back to MJB from NE4.
How did you try to install CM the first time? Did you use the install manager or a custom recovery?
The last time I installed CM on a i747 was back when the phone was on 4.1.1. The second phone I installed it on was the international version of the phone, also on 4.1.1. I used a custom recovery both times. I bet if I would have used the new installer on this phone it would have worked, but I was trying some other stuff because I was curious and ended up breaking it.
IT BOOTED!
I reflashed the stock firmware + root, reinstalled stock recovery and wiped everything I got it to boot into its stock ROM. From this point, where do I go? Will the CM installer work or will it just brick it again?
Thanks
Jemimacakes
I would copy a custom rom such as cm11 to the internal and external sd card.
I would then download the latest version of philz touch for the d2lte. Get Odin 3.07. Put the phone in download mode, open Odin, uncheck all options except f reset time. Flash philz, when you see reset in the status window, remove USB cable, remove battery, insert battery, boot into recovery, create a nandroid of your current rom, flash cm11, wipe cache, wipe data, wipe dalvik, reboot.
audit13 said:
I would copy a custom rom such as cm11 to the internal and external sd card.
I would then download the latest version of philz touch for the d2lte. Get Odin 3.07. Put the phone in download mode, open Odin, uncheck all options except f reset time. Flash philz, when you see reset in the status window, remove USB cable, remove battery, insert battery, boot into recovery, create a nandroid of your current rom, flash cm11, wipe cache, wipe data, wipe dalvik, reboot.
Click to expand...
Click to collapse
Which version of CM11 should I get. On the site I see that the last version of CM11 for the I747 (d2att) was released on feburary 16, is this one based on 4.4.2?
EDIT: Also, I should copy CM11 to both the internal and external storage? Why is this?
You should be using roms made for the d2lte.
I suggest both because cwm or twrp may see one but not the other. This doesn't usually happen but I am always paranoid about something going wrong as flashing always involves risk and I like to minimize risks and be prepared for disaster.
audit13 said:
You should be using roms made for the d2lte.
I suggest both because cwm or twrp may see one but not the other. This doesn't usually happen but I am always paranoid about something going wrong as flashing always involves risk and I like to minimize risks and be prepared for disaster.
Click to expand...
Click to collapse
Alright, but I have the at&t version of the phone. Are they both compatible with one another?
EDIT: OK, correct me if im wrong, but my new understanding is that CM now has releases for general versions of phones, so the most recent update of CM for my phone is the d2lte, not d2att?
Before unified builds for the msm8960 were started, the i747 was known as the d2att and the i747m was known as the d2can.
audit13 said:
Before unified builds for the msm8960 were started, the i747 was known as the d2att and the i747m was known as the d2can.
Click to expand...
Click to collapse
Hello again,
Thanks a ton Audit, my phone is up and running with the latest cyanogen nightly! A recap for anyone who might come across with a similar problem.
1. I installed a ROM using an older version of android onto a phone with the new bootloader (NE4), softbricking it.
2. I installed the stock ROM + root from this link using Clockworkmod
https://www.androidfilehost.com/?fid=23501681358550126
3. Installed the stock Recovery from this link and did wiped my data and both caches
https://www.androidfilehost.com/?fid=23681161096070493
4. I rebooted the phone and waited at the AT&T logo for a while, and it booted up normally!
5. I installed the most recent version of Philz Touch Recovery for the d2lte, made a nandroid for safety, and then install the latest nightly of CM11 for the d2lte.
6. It works!
Thanks again to Audit for helping me out!
Jemimacakes
I'm glad it all worked and I was able to help in some way.
It's great that you posted your solution in case it helps other people in a similar situation.
I think i'm in a similar place - a few questions. You used cwm to install the stock ROM? I thought you needed to use odin. Also, why did you need to install the stock recovery (and did you just flash the .zip in cwm)? Also, that stock rom you linked to is 4.4, right? Would that work if I was on 4.3?
Before flashing anything, I suggest you confirm your bootloader and modem. Flashing the wrong combination of modem and bootloader could hard brick your phone.
If your phone does not boot, try flashing Philz Touch for the d2lte and flash the latest cm11. Hoepfully, this will get your phone running so you can confirm the bootloader and modem. CM11 does not flash a modem or bootloader.
Before event thinking about anything, please create a backup of existing ROM.
Why the post?
CM13 is BUMP compatible. ( BUMP explained below)
The Sprint G2 is having very confusing Bootloader and Bootstacks combination needs for every major release of Cyanogenmod.
e.g.
Initially we had to have ZV8 modem for CM11 without it we had bootloops
We were confused with LP-loki and LP-BUMP bootstacks before using CM12.1
I got bootlooped twice doing the upgrade, so I thought to share the experience to save you from such touble and make step-to-step guide for you to help to jump to the amazing Android 6 :angel:
What we need -
Bump TWRP Recovery - http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705 (Thank to blastagator )
Hybrid Bootstack - http://forum.xda-developers.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219 (Thank to daniel.stuart14 )
CM13 based roms (few recommended below)
Resurrection - http://forum.xda-developers.com/lg-...on-remix-m-t3271114/post64315465#post64315465 ( Thank to varund7726 )
crDroid - http://forum.xda-developers.com/lg-g2/development/rom-crdroid-t3120790 (Thank to firebird11 )
waiting for Bliss 6.0 from Team Bliss
Gapps for 6.X.X ( http://download.dirtyunicorns.com/files/gapps/banks_gapps/ )
Why to update TWRP?
CM13 is BUMP. If you are like me and used FreeGee to downgrade aboot, for installing TWRP, then you are on JB bootloader which is Loki based.
Loki is synonyms to JB bootloader & BUMP is synonyms to Kitkat Bootloader.
So if you flash this ROM with current setup, you wont be able to go beyond Bootscreen LG logo (in other words, you would softbrick) because of Modem mismatch.
And if you flash the Hybrid bootloader after flashing ROM, then logically you should be fixing the above problem but your TWRP, which can be booted on Loki (JB), wont be able to boot behind Kitkat Bootloader.
So we will make the TWRP capable to boot on Kitkat bootloader and then start to play with the ROMs.
So first, Install TWRP-thermal from above link. I would recommend to update your current TWRP to 2.8.6.0 with official TWRP files (https://dl.twrp.me/g2spr/) and then flash the above zip to upgrade to 2.8.7.3
Which Bootstack and what about bootloader?
The BUMP recovery can boot against JB bootloader and Kitkat bootloader. So what you have now can boot on current bootloader. So basically you can restart the recovery with JB bootloader without any problem. Reboot and flash the Hybrid bootstack from above link which takes care of everything. Remember to reboot into recovery after you flash the bootstack.
Now for ROM installation the usual procedure is needed,
Wipe Dalvik, system, data and cache
Install ROM
Install Gapps
Reboot
Few common problems and solutions,
Bootstack failing signature validation - (Checksum of the bootstack-ls980-CAF-signed.zip is : e32c3c4d5ece4749903ef7502485f488 ). So if this is matching, uncheck Zip signature verification and flash.
Google Now-On-Tap not working - This will happen if you have opted for Nano Gapps file which would not have all apps for Now-On-Tap (Just Google app is not enough probably ).
So happy flashing and hit the thanks if you see above information useful.
Let me know if you want any clarification regarding above process or any specific points.
Would this method work on the Stock LP? Also, I am from Pakistan so would I need to do network unlock on the CM13 again or would it already be unlocked? If unlock is required, would the general stock LP unlock method work? Would really appreciate your help thanks for the great guide
Followed your directions... worked awesome... Thanks!
junibond said:
Would this method work on the Stock LP? Also, I am from Pakistan so would I need to do network unlock on the CM13 again or would it already be unlocked? If unlock is required, would the general stock LP unlock method work? Would really appreciate your help thanks for the great guide
Followed your directions... worked awesome... Thanks!
Click to expand...
Click to collapse
Hi,
SIM unlock does not go away after ROM installation so it will be unlocked. The SIM unlock procedure is same for AOSP and Stock roms which involves replacing few files with Root access.
If you have a problem with network (e.g. SIM not able to serch network ) after ROM install then it is a probelm with modem file, which is taken care by Hybrid bootstack in above case.
thank you bro
Only until yesterday i heard about bump loki and bootstack, i installed cm12.1 and 13 on my ls980 without knowing all this and they worked great until y tried to install Resurrection Remix and got the soft brick, i solved my problem with another post but i want to thank you anyway
Latest CyanogenMod 13 for LG G2 LS980 is available there: https://www.androidfilehost.com/?a=show&w=files&flid=51135
mrlika said:
Latest CyanogenMod 13 for LG G2 LS980 is available there: https://www.androidfilehost.com/?a=show&w=files&flid=51135
Click to expand...
Click to collapse
thanks for the rom. It runs great with the exception of mobile data(3g or lte). I was wondering if there were some recommended tweaks. I also noticed that when I go into the "cellular network settings", the APN submenu among others are gone, although they were there right after the initial installation. Thanks again!
sparklekid said:
thanks for the rom. It runs great with the exception of mobile data(3g or lte). I was wondering if there were some recommended tweaks. I also noticed that when I go into the "cellular network settings", the APN submenu among others are gone, although they were there right after the initial installation. Thanks again!
Click to expand...
Click to collapse
I've got the exact same issue. Just TOTed back to stock ZVG and restored my 3g/LTE connection. Gonna try flashing again later this evening. I'll let you know if it keeps the data connection or not.
On a side note, I did have 3g at one point but have yet to get LTE in ANY custom rom I've tried.
TheWeirdedOne said:
I've got the exact same issue. Just TOTed back to stock ZVG and restored my 3g/LTE connection. Gonna try flashing again later this evening. I'll let you know if it keeps the data connection or not.
On a side note, I did have 3g at one point but have yet to get LTE in ANY custom rom I've tried.
Click to expand...
Click to collapse
exactly. Same here. I even tried the custom ROMs in the OP. I don't consider having only 3g to be "fully working". I tried AICP, Resurrection, and CM13 above. I'm sticking to stock ZVI for now, because it looks like there won't be any custom Marshmallow development with working LTE.
sparklekid said:
exactly. Same here. I even tried the custom ROMs in the OP. I don't consider having only 3g to be "fully working". I tried AICP, Resurrection, and CM13 above. I'm sticking to stock ZVI for now, because it looks like there won't be any custom Marshmallow development with working LTE.
Click to expand...
Click to collapse
I'm running Blisspop now and i have LTE. that's about the best I've been able to do.
bro i have cm 12 ( lg g2 ls980 ) so how i can to update to cm 13 i need ur help 10x
sparklekid said:
thanks for the rom. It runs great with the exception of mobile data(3g or lte). I was wondering if there were some recommended tweaks. I also noticed that when I go into the "cellular network settings", the APN submenu among others are gone, although they were there right after the initial installation. Thanks again!
Click to expand...
Click to collapse
I don't know why APN submenu disappeared but you can try latest build for LS980 from 06.05.2016: https://androidfilehost.com/?w=files&flid=51135
Mobile data (evdo) is also working! On CDMA - for sure! Thanks to mrlika for great rom!
---------- Post added at 12:25 AM ---------- Previous post was at 12:21 AM ----------
For all who use CDMA network! In all slim roms (AICP, PA, RR, Bliss, Exodus & other) except this rom (cm13-unofficial) you has working phonecalls (even 1x & 3g network) but NO EVDO AT ALL. I've tried all variants for LS980: only in this rom you has working 3G (EVDO). Also I think its the same for LTE. So I've forget about ZVI & use this great CM13 build! All is working!
I am running AICP, have Hybrid bootstack installed, and cannot get LTE or 1x unless I am on modem ZV8.
Is it possible to run a newer modem (at least ZVG) and get LTE?
Help please!
Okay so i did this before but i had to .tot restore my phone but i made a backup after i did this whole process anf i want to restore from it, so would these steps lead to success?
-flash TWRP 2.8.6.0
-Then flash THERMAL twrp from the instructions
-Reboot then reboot back into recovery
-Flash bootstacks
-Reboot back into recovery
-advaced wipe everything except internal storage
-Flash cm13 rom and Gapps
-Reboot
???
-Then restore my backup i created with all restore options enabled (boot, data, system, ect.)
Is everything i listed correct? Please help
Paentherax said:
Okay so i did this before but i had to .tot restore my phone but i made a backup after i did this whole process anf i want to restore from it, so would these steps lead to success?
-flash TWRP 2.8.6.0
-Then flash THERMAL twrp from the instructions
-Reboot then reboot back into recovery
-Flash bootstacks
-Reboot back into recovery
-advaced wipe everything except internal storage
-Flash cm13 rom and Gapps
-Reboot
???
-Then restore my backup i created with all restore options enabled (boot, data, system, ect.)
Is everything i listed correct? Please help
Click to expand...
Click to collapse
No! If you restore your partitions after - you have the same rom as before you install cm13! You must restore your sw using backup software like titanium backup. And NEVER restore xposed software settings - you'll have system crashes after... But another steps seems fine.
---------- Post added at 12:09 AM ---------- Previous post was at 12:06 AM ----------
shdware said:
I am running AICP, have Hybrid bootstack installed, and cannot get LTE or 1x unless I am on modem ZV8.
Is it possible to run a newer modem (at least ZVG) and get LTE?
Click to expand...
Click to collapse
If you flash 5.0.2 bootstack, then you cannot stay on zv8 modem, because bootstack flashes modem also. But anyway you can find zvimodem.zip and flash it through recovery after; I've tried it myself and have no issues with rom after. But LTE & EVDO you can have ONLY on cm13 "clean" rom - this rom by mrlika. If you flash AICP, bliss, exodus etc. - these roms are 'slim', which means you cannot turn on evdo mobile data (or maybe lte also) in it! Be aware about it, because I've tried almost 10 different roms, and EVDO working only in cm13 by mrlika!
astherion said:
No! If you restore your partitions after - you have the same rom as before you install cm13! You must restore your sw using backup software like titanium backup. And NEVER restore xposed software settings - you'll have system crashes after... But another steps seems fine.
---------- Post added at 12:09 AM ---------- Previous post was at 12:06 AM ----------
If you flash 5.0.2 bootstack, then you cannot stay on zv8 modem, because bootstack flashes modem also. But anyway you can find zvimodem.zip and flash it through recovery after; I've tried it myself and have no issues with rom after. But LTE & EVDO you can have ONLY on cm13 "clean" rom - this rom by mrlika. If you flash AICP, bliss, exodus etc. - these roms are 'slim', which means you cannot turn on evdo mobile data (or maybe lte also) in it! Be aware about it, because I've tried almost 10 different roms, and EVDO working only in cm13 by mrlika!
Click to expand...
Click to collapse
I have looked and can't find ZVI for LS980. I did find ZVH and am running it: it fixed my LTE issue.
Works you mind pointing me in the direction of the ZVI modem? I can find only the update itself, and have not been able to extract it successfully.
Here is ZVI modem. I've put it on my google drive https://drive.google.com/open?id=0B_i7PPx6-NrOMHNsdUcyblFhdlU Just flash it through TWRP
astherion said:
No! If you restore your partitions after - you have the same rom as before you install cm13! You must restore your sw using backup software like titanium backup. And NEVER restore xposed software settings - you'll have system crashes after... But another steps seems fine.
---------- Post added at 12:09 AM ---------- Previous post was at 12:06 AM ----------
If you flash 5.0.2 bootstack, then you cannot stay on zv8 modem, because bootstack flashes modem also. But anyway you can find zvimodem.zip and flash it through recovery after; I've tried it myself and have no issues with rom after. But LTE & EVDO you can have ONLY on cm13 "clean" rom - this rom by mrlika. If you flash AICP, bliss, exodus etc. - these roms are 'slim', which means you cannot turn on evdo mobile data (or maybe lte also) in it! Be aware about it, because I've tried almost 10 different roms, and EVDO working only in cm13 by mrlika!
Click to expand...
Click to collapse
Okay just to put this out there... I did exactly the steps I listed in my post and everything worked 100% fine. Also I updated to the latest blastigator 3.0.1-2 after everything, so I can confirm my steps worked! But to add anything important for anyone who might want to know this is what I did before install CM13.
-restored phone with ZVA8.tot (4.2.2)
-rooted using ioroot
-download FreeGee and installed TWRP (while still on stock 4.2.2 btw)
-downloaded cm11 SnapShot
-then I decided to update my TWRP to 2.8.6.0 (the latest available TWRP for lg g2 ls980 from the main TWRP website
-rebooted into recovery and flashed the latest TWRP I installed and rebooted successfully without wiping anything (still on 4.2.2)
-then checked to make sure I have everything I need
-rebooted into recovery again
-went to wipe, advanced wipe, and checked everything except "internal storage"
-then while still in recovery (don't reboot after wiping) flash CM11 and rebooted
-everything worked fine still and cm11 was successful
-went into settings and downloaded the latest CM12 SnapShot and did an auto update after downloading
-rebooted successfully
-then I came here and read on how to install CM13 and did that, and if you follow my exact list from earlier from what I asked, it will lead to success.
~also through the whole process I never installed Gapps except when I upgraded to CM13 (made the process faster) and ONLY update to the latest Thermal/Blastigator TWRP after you install CM13 on the recoveries listed in the main post, and make sure you Backup everything to be safe incase a mistake is made.
/the list I made asking if it would work correctly did work, and aside from restoring from the backup, my list is a simpler version of the instructions from the main post, but I give all credit to the poster and say thanks and I only put their list of steps into my simpler form, thanks!
---------- Post added at 09:28 AM ---------- Previous post was at 09:27 AM ----------
Okay just to put this out there... I did exactly the steps I listed in my post and everything worked 100% fine. Also I updated to the latest blastigator 3.0.1-2 after everything, so I can confirm my steps worked! But to add anything important for anyone who might want to know this is what I did before install CM13.
-restored phone with ZVA8.tot (4.2.2)
-rooted using ioroot
-download FreeGee and installed TWRP (while still on stock 4.2.2 btw)
-downloaded cm11 SnapShot
-then I decided to update my TWRP to 2.8.6.0 (the latest available TWRP for lg g2 ls980 from the main TWRP website
-rebooted into recovery and flashed the latest TWRP I installed and rebooted successfully without wiping anything (still on 4.2.2)
-then checked to make sure I have everything I need
-rebooted into recovery again
-went to wipe, advanced wipe, and checked everything except "internal storage"
-then while still in recovery (don't reboot after wiping) flash CM11 and rebooted
-everything worked fine still and cm11 was successful
-went into settings and downloaded the latest CM12 SnapShot and did an auto update after downloading
-rebooted successfully
-then I came here and read on how to install CM13 and did that, and if you follow my exact list from earlier from what I asked, it will lead to success.
~also through the whole process I never installed Gapps except when I upgraded to CM13 (made the process faster) and ONLY update to the latest Thermal/Blastigator TWRP after you install CM13 on the recoveries listed in the main post, and make sure you Backup everything to be safe incase a mistake is made.
/the list I made asking if it would work correctly did work, and aside from restoring from the backup, my list is a simpler version of the instructions from the main post, but I give all credit to the poster and say thanks and I only put their list of steps into my simpler form, thanks!
Paentherax said:
Okay just to put this out there... I did exactly the steps I listed in my post and everything worked 100% fine. Also I updated to the latest blastigator 3.0.1-2 after everything, so I can confirm my steps worked! But to add anything important for anyone who might want to know this is what I did before install CM13.
-restored phone with ZVA8.tot (4.2.2)
-rooted using ioroot
-download FreeGee and installed TWRP (while still on stock 4.2.2 btw)
-downloaded cm11 SnapShot
-then I decided to update my TWRP to 2.8.6.0 (the latest available TWRP for lg g2 ls980 from the main TWRP website
-rebooted into recovery and flashed the latest TWRP I installed and rebooted successfully without wiping anything (still on 4.2.2)
-then checked to make sure I have everything I need
-rebooted into recovery again
-went to wipe, advanced wipe, and checked everything except "internal storage"
-then while still in recovery (don't reboot after wiping) flash CM11 and rebooted
-everything worked fine still and cm11 was successful
-went into settings and downloaded the latest CM12 SnapShot and did an auto update after downloading
-rebooted successfully
-then I came here and read on how to install CM13 and did that, and if you follow my exact list from earlier from what I asked, it will lead to success.
~also through the whole process I never installed Gapps except when I upgraded to CM13 (made the process faster) and ONLY update to the latest Thermal/Blastigator TWRP after you install CM13 on the recoveries listed in the main post, and make sure you Backup everything to be safe incase a mistake is made.
/the list I made asking if it would work correctly did work, and aside from restoring from the backup, my list is a simpler version of the instructions from the main post, but I give all credit to the poster and say thanks and I only put their list of steps into my simpler form, thanks!
---------- Post added at 09:28 AM ---------- Previous post was at 09:27 AM ----------
Okay just to put this out there... I did exactly the steps I listed in my post and everything worked 100% fine. Also I updated to the latest blastigator 3.0.1-2 after everything, so I can confirm my steps worked! But to add anything important for anyone who might want to know this is what I did before install CM13.
-restored phone with ZVA8.tot (4.2.2)
-rooted using ioroot
-download FreeGee and installed TWRP (while still on stock 4.2.2 btw)
-downloaded cm11 SnapShot
-then I decided to update my TWRP to 2.8.6.0 (the latest available TWRP for lg g2 ls980 from the main TWRP website
-rebooted into recovery and flashed the latest TWRP I installed and rebooted successfully without wiping anything (still on 4.2.2)
-then checked to make sure I have everything I need
-rebooted into recovery again
-went to wipe, advanced wipe, and checked everything except "internal storage"
-then while still in recovery (don't reboot after wiping) flash CM11 and rebooted
-everything worked fine still and cm11 was successful
-went into settings and downloaded the latest CM12 SnapShot and did an auto update after downloading
-rebooted successfully
-then I came here and read on how to install CM13 and did that, and if you follow my exact list from earlier from what I asked, it will lead to success.
~also through the whole process I never installed Gapps except when I upgraded to CM13 (made the process faster) and ONLY update to the latest Thermal/Blastigator TWRP after you install CM13 on the recoveries listed in the main post, and make sure you Backup everything to be safe incase a mistake is made.
/the list I made asking if it would work correctly did work, and aside from restoring from the backup, my list is a simpler version of the instructions from the main post, but I give all credit to the poster and say thanks and I only put their list of steps into my simpler form, thanks!
Click to expand...
Click to collapse
Lots of useless steps. If you has TWRP already, you don't need flash tot or cm11-12! Just flash latest twrp-blasted, then bootstack-caf + cm13 + gapps! Profit! (As I've mentioned before, bootstack updates radio & aboot).
P.S. ZVA (ZV8) tot you need only in 1 case: if you need to make sprint unlock, before you put another phone number (i.e. then you buy it from smb.). For install cm13 if you has twrp & root also - this is unnecessary
Was on 4.4.2 stock NJ2...Odin'ed a custom recovery like TWRP...rebooted.....NO IMEI and BASEBAND. That's about as simple, yet complex it gets. Tried reverting back to stock recovery in Odin, only to find that NO IMEI and BASEBAND still shows up. THE ONLY way I've successfully kept the IMEI/BASEBAND....is by keeping everything stock, from recovery to rom. Why would this be? I've even tried restoring the EFS folder....to no avail!!!! I'M FRUSTRATED!!!! My end goal is to be able to flash a rom, use TWRP/CWM, and KEEP the IMEI/BASEBAND!!!
ANY HELP? ANYONE having the same issue or fix?
THANKS!!!!!!:good:
Possible fix...
Make sure you have not used device encryption on the rom prior to your desired rom...
If you have then a device full wipe script is needed to clean up the phone prior to flashing the new rom...
(don't forget to check your SD card for encryption or data files that may be affected)...
Flash TWRP version 2.8.6.0 and flash your new rom....
Higher TWRP versions have been buggy for me...
Best I've got atm....g
It's because you are using TWRP 3.0.0.1, that one is broken
Hi all, relative newb here.
If there is an RTFM on this, I'm all ears, and won't mind one bit.
I want to take a stock SPH-L710 to CM13, and read the thread. First step is to install CWM. I will try this first step later tonight, but question I have is whether I need to be rooted first.
Reason I ask is prior to taking OH1, I "tried" to get CWM installed on ND8 version, and it wouldn't take. I tried first via Odin 3.07, allowing after the SUCCESS message to let the phone reboot itself, and when I shut down and tried to get into recovery mode, it would just go tot he stock "download mode" screen. i then tried to flash via Odin, and not allow reboot, pulled the battery, and restarted into recovery, and the stock download screen still came up.
In reading the thread about CM13, the thread says to load CWM. The version that is linked to on the clockworkmod page is 6.0.4.5, which is not the version I was trying to install above (it was an older version). Can I assume that installing this version will allow boot into the CWM recovery, so I can get to the next step?
I also searched, and found useful pages on how to convert a .img to at tar.md5, so I think I'm good to use the version on the cwm url.
I've searched hard to find any mention of not being able to boot into CWM, and it has something to do with OTA updates. Asking these questions now, since for some reason, I can only get this site up here at work, not at home using IE on a 32 bit machine.
TIA...and pointers to RTFMs greatly appreciated.
Eric
ejaf said:
Hi all, relative newb here.
If there is an RTFM on this, I'm all ears, and won't mind one bit.
I want to take a stock SPH-L710 to CM13, and read the thread. First step is to install CWM. I will try this first step later tonight, but question I have is whether I need to be rooted first.
Reason I ask is prior to taking OH1, I "tried" to get CWM installed on ND8 version, and it wouldn't take. I tried first via Odin 3.07, allowing after the SUCCESS message to let the phone reboot itself, and when I shut down and tried to get into recovery mode, it would just go tot he stock "download mode" screen. i then tried to flash via Odin, and not allow reboot, pulled the battery, and restarted into recovery, and the stock download screen still came up.
In reading the thread about CM13, the thread says to load CWM. The version that is linked to on the clockworkmod page is 6.0.4.5, which is not the version I was trying to install above (it was an older version). Can I assume that installing this version will allow boot into the CWM recovery, so I can get to the next step?
I also searched, and found useful pages on how to convert a .img to at tar.md5, so I think I'm good to use the version on the cwm url.
I've searched hard to find any mention of not being able to boot into CWM, and it has something to do with OTA updates. Asking these questions now, since for some reason, I can only get this site up here at work, not at home using IE on a 32 bit machine.
TIA...and pointers to RTFMs greatly appreciated.
Eric
Click to expand...
Click to collapse
The thing is CWM is outdated, i believe to install CM13 successfully, you'd have to install twrp.
Here is the link to the latest, grab the first tar flash it via odin & you should be good to boot into recovery to flash roms.
https://dl.twrp.me/d2spr/
Lonelyskatter12 said:
The thing is CWM is outdated, i believe to install CM13 successfully, you'd have to install twrp.
Click to expand...
Click to collapse
Interesting news...thanks. The "Official" thread says that only CWM can be used. Of course, since that thread has a gazillion replies, I couldn't get through it. Of course...I just noticed that the thread I was reading was not specific to CM13, so I have to do more reading.
Main question....haven't got a hit on whether, after installing custom recovery, I need to root or not.
I am also at a disadvantage, since I can't get this site up at home, only at work, so I can't dowload anything while reading.
Thanks for the reply.
ejaf said:
Interesting news...thanks. The "Official" thread says that only CWM can be used. Of course, since that thread has a gazillion replies, I couldn't get through it. Of course...I just noticed that the thread I was reading was not specific to CM13, so I have to do more reading.
Main question....haven't got a hit on whether, after installing custom recovery, I need to root or not.
I am also at a disadvantage, since I can't get this site up at home, only at work, so I can't dowload anything while reading.
Thanks for the reply.
Click to expand...
Click to collapse
Yes, the official thread is CM13, you don't need Cwm, pretty much twrp supports marshmallow now.
And i believe you would need root.
If there's any way for you to be able to download the files, id be happy to give you step by step instructions :good:
THANKS BIG TIME!!!
Cool beans! I got TWRP 3.0.2.0 installed! And when exiting, I installed superSU, followed instructions, updated via play store, and disabled Knox.
I am in the process of downloading CM13 Nightly from cyanogenmod (cm-13.0-20160428-NIGHTLY-d2spr.zip). I don't see an "official" release there, so I guess a nightly is the best I can do if I want CM13 (weird though, since the unofficial thread started in November, and I only see nightlies starting in April.
So this is what's next correct?:
- wipe the device
- flash rom
- flash gapps
- reboot system
TIA...Eric
FYI...I couldn't take it anymore, didn't feel like tracking the IE issue, so I downloaded chrome
ejaf said:
THANKS BIG TIME!!!
Cool beans! I got TWRP 3.0.2.0 installed! And when exiting, I installed superSU, followed instructions, updated via play store, and disabled Knox.
I am in the process of downloading CM13 Nightly from cyanogenmod (cm-13.0-20160428-NIGHTLY-d2spr.zip). I don't see an "official" release there, so I guess a nightly is the best I can do if I want CM13 (weird though, since the unofficial thread started in November, and I only see nightlies starting in April.
So this is what's next correct?:
- wipe the device
- flash rom
- flash gapps
- reboot system
TIA...Eric
FYI...I couldn't take it anymore, didn't feel like tracking the IE issue, so I downloaded chrome
Click to expand...
Click to collapse
Yeah the Unofficial thread was being maintained by a Developer, who stopped as soon as the officials came out.
And yes
1.) Wipe Data, Cache, System, & Internal Storage (So backup anything on there)
2.) Flash Rom, Gapps, SuperSu 2.71 (If you want root)
& should be good to go
Just found this post here on the "Unofficial" CM thread, which causes me some concern:
http://forum.xda-developers.com/showpost.php?p=65865323&postcount=207
This basically states:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
An example of the steps with the assumption someone was coming from the stock android with TWRP installed and everything to be flash stored on the external sdcard. Assuming the user is in TWRP to start.
Issue a full format of the following partitions, /system, /userdata, /internalstorage, /cache, /dalvik
Add the rom to the flash queue (eg. cm-13.0)
Add an android 6 compatible gapps to the queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot into system for the first time
Once booted reboot into TWRP
Add the same rom zip to the flash queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot to system
Everything should be functioning (at least mostly)
Enjoy
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Not sure about the APN stuff, so I guess i have to read more about that as well.
Thanks for getting me through the "baby" steps though...I'm infinitely further than I was before
ejaf said:
Just found this post here on the "Unofficial" CM thread, which causes me some concern:
http://forum.xda-developers.com/showpost.php?p=65865323&postcount=207
This basically states:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
An example of the steps with the assumption someone was coming from the stock android with TWRP installed and everything to be flash stored on the external sdcard. Assuming the user is in TWRP to start.
Issue a full format of the following partitions, /system, /userdata, /internalstorage, /cache, /dalvik
Add the rom to the flash queue (eg. cm-13.0)
Add an android 6 compatible gapps to the queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot into system for the first time
Once booted reboot into TWRP
Add the same rom zip to the flash queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot to system
Everything should be functioning (at least mostly)
Enjoy
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Not sure about the APN stuff, so I guess i have to read more about that as well.
Thanks for getting me through the "baby" steps though...I'm infinitely further than I was before
Click to expand...
Click to collapse
That's the order, now about the apn im not sure, i just use mine for wifi and stuff.
That Cyanogenmod build "04282016" wasn't running so well for me, so I'm on AICP for now.
But i would suggest, OctOs , AICP, or Exodus Roms. Those are the most stable roms for this device.
Same steps just different ROMs.
But i did hear Exodus gives you data right off the bat, so that'd be good to try
Interesting...thanks for the tips. Hopefully I won't have to bother any of you all again, since I really don't have much in the way of knowledge to return
E
FYI...was able to boot up into CM 12.1 over the weekend. Jury's still out on whether to go to a 6.0.1 based ROM, but appreciate all the help.
Eric
I found the APN fix didn't work with the CM13 rom (I've used it previously with 12.1 fine). I also found that the build-in cm update failed on 20160505 nightly. Not sure if this was just that day or a known bug.