I just upgraded from a Droid X2- everything was relatively easy on there; root, recovery, flash, reboot, done. I'm kinda lost on the G2, though. I've spent the past few hours, looking over the TWRP guide thread, the TWRP 2.6.3.4 thread, ROM threads, etc. I'm just wondering if I have the steps correct before I do anything (I have a VS980, rooted, on 4.2.2):
1. Use Flashify to flash TWRP 2.6.3.2
2. Go into TWRP (power and volume down on boot up?) to flash 2.6.3.3.
3. Use TWRP to wipe, flash ROM, reboot, done.
From what I've read, people are having issues with 2.6.3.4- is it really necessary? And as far as what ROM: from what I've read the 4.4+ ROMs aren't completely stable. Is this still true? If so, then I don't mind waiting and just flashing Malladus on 4.2.2, for now.
Any info is greatly appreciated.
TWRP 2.6.3.2 will work for flashing Malladus just fine. But it won't flash 4.4 ROMs.
But it sounds like you've got a good grasp of how to do things. Happy flashing.
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM 4.3.
Ended up just doing 2.6.3.2 with Malladus for now. Went smoother than I thought. If I decide to flash a 4.4 ROM later, will I need to just flash 2.6.3.3 over 3.2 in TWRP? Thanks!
Related
I got an OTA update notification a few days back, and without thinking I decided to install it. Stupid decision. I was on a custom rom AND a custom recovery (TWRP). Now, whenever I turn on my phone it will just take me to TWRP recovery. Even if I flash a rom like AOKP or CM, the install will say "successful", but it will still go to recovery instead of the actual operating system when I power on the phone.
My guess is it has something to do with the bootloader, but I'm not too familiar with the way Android devices bootup and whatnot. This is on a D801 (T-Mobile version), and I was running a stock rooted rom with TWRP recovery installed. I'm posting here instead of the T-Mobile subforum because I don't think it's an issue unique to my model.
Since I can load up TWRP just fine, I don't think it should be too catastrophic of an issue.
Any help would be greatly appreciated
AlexRamallo said:
I got an OTA update notification a few days back, and without thinking I decided to install it. Stupid decision. I was on a custom rom AND a custom recovery (TWRP). Now, whenever I turn on my phone it will just take me to TWRP recovery. Even if I flash a rom like AOKP or CM, the install will say "successful", but it will still go to recovery instead of the actual operating system when I power on the phone.
My guess is it has something to do with the bootloader, but I'm not too familiar with the way Android devices bootup and whatnot. This is on a D801 (T-Mobile version), and I was running a stock rooted rom with TWRP recovery installed. I'm posting here instead of the T-Mobile subforum because I don't think it's an issue unique to my model.
Since I can load up TWRP just fine, I don't think it should be too catastrophic of an issue.
Any help would be greatly appreciated
Click to expand...
Click to collapse
This might help;
http://forum.xda-developers.com/showthread.php?t=2451696
Hello everyone,
I'm trying to flash a rom for the first time and I've been fighting with TWRP for the last week or so. Here's what I've done. LG G2 D803 Rogers Canada
1. Rooted Device.
2. Installed TWRP Manager and Installed TWRP Recovery Image (2.6.3.2) and I can restore with no issues.
3. Downloaded latest PA 4.4 roms for my phone version (LG G2 D803), including the most recent GAPPS (mini modular). And transferred to phone.
4. Reboot into recovery.
5. Wipe Cache, Dalvik, Data, ... etc)
6. Select install ROM.
7. Get error right away (E:Error executing updater binary in zip)
8. Flashing rom FAILED.
What can I do to fix this?
My device is not supported on CWMR, so I'm not sure if that would work. Also, I've tried downloading older roms, so I'm pretty sure it's not a bad download issue.
Thanks for any help!
TWRP 2.6.3.2 isn't the latest release, so that might be your problem. Go here: http://forum.xda-developers.com/showthread.php?t=2469995 flash the new zip from your current TWRP, and you should be able to flash KitKat ROMs now. Or, if you prefer CWM, there's PhilZ Touch CWM here http://forum.xda-developers.com/showthread.php?t=2554053
gusly said:
TWRP 2.6.3.2 isn't the latest release, so that might be your problem. Go here: http://forum.xda-developers.com/showthread.php?t=2469995 flash the new zip from your current TWRP, and you should be able to flash KitKat ROMs now. Or, if you prefer CWM, there's PhilZ Touch CWM here http://forum.xda-developers.com/showthread.php?t=2554053
Click to expand...
Click to collapse
Gave you a thanks, it worked perfectly! Wohoo!
oakster15 said:
Gave you a thanks, it worked perfectly! Wohoo!
Click to expand...
Click to collapse
No problem man. Had the same problem myself, so I knew how to fix it
Sent from my G2 using Tapatalk
gusly said:
No problem man. Had the same problem myself, so I knew how to fix it
Sent from my G2 using Tapatalk
Click to expand...
Click to collapse
oakster15 said:
Gave you a thanks, it worked perfectly! Wohoo!
Click to expand...
Click to collapse
Hey guys. I'm having the hardest time flashing anything right now. I'm on the 2.6.3.2 and I get the binary updater problem so then I tried flashing other twrp then I get the fast boot error then I tried philz touch then I get boot certification verify error.
All I want to do is flash a 4.4.2 rom.
Canadian rom D803 here.
Thanks
wootever's TWRP 2.6.3.4 oakster15 had posted above worked on my D803, however there are a couple of 2.6.3.4 download versions that didn't work when I flashed it while running TWRP 2.6.3.2. I'm not familar with loki but I'm guessing the one that worked had been "loki-fied".
---------- Post added at 09:49 AM ---------- Previous post was at 09:40 AM ----------
Brava27 said:
Hey guys. I'm having the hardest time flashing anything right now. I'm on the 2.6.3.2 and I get the binary updater problem so then I tried flashing other twrp then I get the fast boot error then I tried philz touch then I get boot certification verify error.
All I want to do is flash a 4.4.2 rom.
Canadian rom D803 here.
Thanks
Click to expand...
Click to collapse
If you haven't' found this already, here is a great list for the D803 with several options that may work for you. http://forum.xda-developers.com/showthread.php?t=2611749
Hope this helps.
Hey Guys,
As someone with a D803 variant of the G2, I had been pulling my hair out the last few days on this. Anyway, thanks to the Mahdi team, I was able to get TWRP 2.7.1.0 via this link:
https://www.mediafire.com/folder/hid9ny9jl91yx/TWRPS
The 4.4.4 rom I flashed was made by the Mahdi team and can be found here:
http://forum.xda-developers.com/showthread.php?t=2590700
Cheers!
Q&A for [CM12] [Lollerpop] JFLTEATT Nightly Kangs
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [CM12] [Lollerpop] JFLTEATT Nightly Kangs. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
noremac258 said:
No love for the jfltecan?
Click to expand...
Click to collapse
Yea I tried even using the jflteatt philz to trick it but the data part failed and system was success. So I didn't bother trying to boot. You can still use Antares however, it is unified.
I am wondering if I can flash Antares and then dirty flash this over to get the system part, I just don't wanna have to go through Odin to stock rigamarole.
cm-12-20141124.1217-jflteatt
Can't get it to boot on my AT&T S4. It tries, black screens, then reboots into AD recovery automatically.
I'm unlocked using T-mobile, but I don't think that should matter.
TWRP v2.7.1.0-- Using stock slot with safestrap disabled (no success on making new slots with safestrap enabled, either).
Lollerpop CM12 - AT&T Samsung Galaxy S4 (SGH-i337) - Unauthorized
Hi,
I tried replying to the CM12 Lollerpop thread but even though I have been utilizing XDA for YEARS, I am still considered a noob due to lack of posts.
Anyway, I just wanted to let the awesome developers know that I tried installing CM12 Lollerpop through TWRP, on my AT&T Samsung Galaxy S4 (SGH-i337) that I have installed ROMs on hundreds of times. For some strange reason that I cannot explain, with the Beta version of CM12 right after I power on the device after installing I see an ! and "AT&T UNAUTHORIZED SOFTWARE HAS BEEN DETECTED" and device went to a black screen after 5 -> 10 seconds. Fortunately I was still able to get back into TWRP after a reboot and home + volume up and successfully completed a restore from a 4.4.4 Beanstalk complete backup I took prior to testing CM12 installation / boot, etc.
I would greatly appreciate it if someone could A) explain why this is happening with CM12 and more importantly B) how to get around this annonying blocking message.
Kind Regards,
Jason Vincent
Sr Integration & Validation Engineer
VoIP SME
jkvincent said:
I would greatly appreciate it if someone could A) explain why this is happening with CM12 and more importantly B) how to get around this annonying blocking message.
Click to expand...
Click to collapse
It sounds like you did not flash a Loki-Doki package. Search the AT&T Galaxy S4 forum and you can find it. You need to flash this after you flash your ROM (or anything else) to trick your phone into thinking you have stock software. Some ROMS have this included, which is probably why you have never had to flash this package before, but I would say that most don't. And no, even if the ROM has a Loki package included inside of it, it doesn't hurt to flash it twice so I end up flashing Loki-Doki a lot.
Sent from my GT-I9505G using XDA Free mobile app. Press "Thanks" if I helped!
Unauthorized - Loki & Safestrap
Hi,
I downloaded loki-doki.zip, wiped, installed CM12*.zip, gapps-lp*.zip and applied loki-doki.zip to find the annoying "Unauthorized..." message again. I tried installing loki by itself after a clean reboot. I tried with wiping dalvik + cache and without. Same thing.
After reading up on Loki, I ran into a bit that stated Loki is designed for 4.4.2 and for 4.4.4+ I should be using Safestrap. I downloaded the Safestrap*.apk file, installed it, granted root access and installed Recovery (says Safestrap is built off TWRP).
The first thing I noticed was the TWRP version was still 2.8.1 (I also updated TWRP prior). I went through the same process without Loki. Same "Unauthorized..." message. Tried Loki after. Same message.
I am not sure at this point but I have never had much luck installing Recoveries while being booted into Android. I have always had to install from a .zip in Recovery or use Odin. I'm not convinced Safestrap updated or even if it is the right way to go. What would be really sweet is if the Devs could wrap whatever is needed to get around the "Unauthorized...", into the CM12 installation. Maybe that is asking for too much. I need to still research Safestrap and it is getting late. I do appreciate you pointing out Loki because it got me pointed in the right direction. I kind of forgot about it with the ROMs being Lok'd.
Kind Regards,
Jason Vincent
Sr Integration & Validation Engineer
VoIP SME
For those who are on AT&T, this is how I got 11-30 to work. Worked perfectly, except the battery drain.
Install cm12 using TWRP (shouldn't matter, but I used 2.8.0.1), flash gapps if you want, flash ktoonsez aosp 5.0 kernel just updated few days ago. No loki patch needed. Good luck.
Didn't get a chance to test bluetooth, but camera seemed to work.
I am using a AT&T s4 (no safestrap)
Hi, Try installing a kernel. it work for me. Alicard or ktoonz.
Question here
I have the sgh-i337 rooted on stock firmware 4.2.2 and have installed shabbyPenguin recovery (I know it's an old recovery but it seems to work fine). I am able to flash this ROM like my bootloader is unlocked or do I need to do something else like flash the loki-doki.zip file?
Thanks in advance!
StoneyJSG said:
I have the sgh-i337 rooted on stock firmware 4.2.2 and have installed shabbyPenguin recovery (I know it's an old recovery but it seems to work fine). I am able to flash this ROM like my bootloader is unlocked or do I need to do something else like flash the loki-doki.zip file?
Thanks in advance!
Click to expand...
Click to collapse
I'm not sure what you said in that last line. But I'm guessing you mean to ask if you can flash this or not. Simple answer, no.
Long answer: I'm not sure what your device exactly is, or what you have done with it. I'm guessing it's not an MDL or earlier device to which the loki-doki patch applies. So using that on your device could be bad idea. I'm assuming the recovery you listed is a modified version for safestrap users. In which case, you can only run touch wiz based roms or Google play edition (safestrap), which this is neither of.
thesummoner101 said:
I'm not sure what you said in that last line. But I'm guessing you mean to ask if you can flash this or not. Simple answer, no.
Long answer: I'm not sure what your device exactly is, or what you have done with it. I'm guessing it's not an MDL or earlier device to which the loki-doki patch applies. So using that on your device could be bad idea. I'm assuming the recovery you listed is a modified version for safestrap users. In which case, you can only run touch wiz based roms or Google play edition (safestrap), which this is neither of.
Click to expand...
Click to collapse
Sorry for my typos. I was asking if I can flash this rom like I have an unlocked bootloader since I am on the MDL firmware Android 4.2.2 and can use LOKi. I have ShabbyPenguin's version of Clockwork mod recovery installed.
StoneyJSG said:
Sorry for my typos. I was asking if I can flash this rom like I have an unlocked bootloader since I am on the MDL firmware Android 4.2.2 and can use LOKi. I have ShabbyPenguin's version of Clockwork mod recovery installed.
Click to expand...
Click to collapse
Okay, if you're on MDL, then you have a couple of options. Here's the process that has worked for me without issue. I'm also on MDL. I'm using twrp but prices should be similar. This could also be a good time to update the recovery, it's really easy.
1) download rom to external sd
2) download PA micro 5 gapps
3) download ktoonsez 5.0 att aosp 12-9 kernel
4) factory reset, wipe dalvik/cache
5) install rom
6) install kernel
7) boot then let it settle and reboot into recovery
8) install gapps
9) boot and let it settle
BTW, our bootloader isn't exactly unlocked, it's just hacked/patched/fooled to think it is. It doesn't seem any different than an unlocked one, except that it needs loki patch, patched recovery, or AT&T kernel.
Good luck.
thesummoner101 said:
Okay, if you're on MDL, then you have a couple of options. Here's the process that has worked for me without issue. I'm also on MDL. I'm using twrp but prices should be similar. This could also be a good time to update the recovery, it's really easy.
1) download rom to external sd
2) download PA micro 5 gapps
3) download ktoonsez 5.0 att aosp 12-9 kernel
4) factory reset, wipe dalvik/cache
5) install rom
6) install kernel
7) boot then let it settle and reboot into recovery
8) install gapps
9) boot and let it settle
BTW, our bootloader isn't exactly unlocked, it's just hacked/patched/fooled to think it is. It doesn't seem any different than an unlocked one, except that it needs loki patch, patched recovery, or AT&T kernel.
Good luck.
Click to expand...
Click to collapse
Awesome! Thanks dude. Since I am partial to CWM, I was going to flash PhilZ touch recovery, but from what I have read the ShabbyPenguin recovery is supposed auto loki upon flashing. I also have the loki-doki.zip file for flashing as well just in case.
How do I even flash CM12 on my device?
My SGH-I337 has Lollipop 5.0.1 and it is rooted no custom recovery.
Please help
ahmedbatty said:
How do I even flash CM12 on my device?
My SGH-I337 has Lollipop 5.0.1 and it is rooted no custom recovery.
Please help
Click to expand...
Click to collapse
How you installed custom recovery in S4 i337 at & t?
Jordan Gonzalez said:
How you installed custom recovery in S4 i337 at & t?
Click to expand...
Click to collapse
I found out that I can't flash any custom ROM or recovery if I have the latest bootloader, so it's locked
Hello all,
I have a stock 4.4.2 20h d802 that I plan to reinstall with cm12 as soon as m1 is released.
I've read a kazillion threads here and thought I had everything covered but the more I read more variations I can see.
I would prefer a PC free solution.
20h blocks towelroot so I guess I have to use stump root instead.
I have the following plan. Any advice or anything missing in here? I do not want to brick my g2
1) root with stumproot 1.2 apk
2) install autorec apk to automatically downgrade boot loader and install old twrp
3) upgrade twrp to 2.8.3 with zip file from recovery
4) erase cache from recovery
5) flash cm12 from recovery
But now I am reading stuff about baseband flashes and that lollipop needs jellybean stuff. So am I missing something our am I good to go?
When I flash lg official rom I have to choose the specific 32gb version. Will this be okay with generic cm12?
Thanks for any help!
Stefan
stefan1975 said:
I have a stock 4.4.2 20h d802 that I plan to reinstall with cm12 as soon as m1 is released.
Click to expand...
Click to collapse
Sorry, but what somebody tells you now, might not apply at the m1 time. Or might have better ways. Might be a long wait as well.
Just saying that you will need to ask this again when the M1 comes. Right now you can only ask how to flash it now.
Thanks for the the reply.
I thought m1 is just a few weeks away so figured I'd start with the rest of the process already so that rooting, autorec and twrp are in place.
But for arguments sake, let's say I want to flash the current official d802 nightly. Would these steps suffice? Do I need to worry about Loki.sh a well?
stefan1975 said:
Thanks for the the reply.
I thought m1 is just a few weeks away so figured I'd start with the rest of the process already so that rooting, autorec and twrp are in place.
But for arguments sake, let's say I want to flash the current official d802 nightly. Would these steps suffice? Do I need to worry about Loki.sh a well?
Click to expand...
Click to collapse
Well to tell you the truth I do not remember how I rooted my device. Was really long ago... and what applies to the 20h.
I know at some point I used autorec.
And now I have the 2831 twrp.
What i can tell you though, that wiping cache won't be enough when flashing cm.
IIRC you have to make a clean install when coming from stock rom. So 4th step has to be about that, not just cache.
Thanks. I will make sure to wipe system as well then.
So autorec will leave me with an old twrp I am reading. I need to update this for cm12 I understand.
What exactly is the difference between Loki twrp 2.8.x and bump 2.8.x? The one I got from the twrp site doesn't have either in the file name. A xda guide said Loki trwp is needed and rootjunky on YouTube said not to use Loki twrp but bump twrp.
Now I am confused
Stefan.
Howdy folks -- I'm having issues with my G2 that I hope people here can help me with. I've already had some advice in the Noobs thread, so thanks for that.
My phone is a LG G2 D800 (AT&T) and is unlocked, being used on the Rogers network. The previous owner of the phone had installed CloudyFlex, which is what I was using until recently.
Here's the story in a nutshell:
On my first attempt to upgrade my ROM from CloudyFlex, I booted into recovery (TWRP installed by the previous owner) and then flashed the newest TWRP for my phone. I then realized I didn't have all the files needed to do the upgrade, so after the TWRP image was successfully flashed, I went to "Reboot System". Doing so gave me a non-responsive phone (LG logo then nothing but a slowly flashing LED).
I managed to get the phone into Download Mode and followed the instructions for LG Flash Tool in the first post here exactly: http://forum.xda-developers.com/showthread.php?t=2432476 which gave me a "stock" functional phone again, but one now running Jellybean (4.2.2, software version D80010o). I'd like to be on Kitkat or (preferably) Lollipop.
I am able to root the phone easily using the LG One Click Root tool. No problem there.
So that's the story. I now have a AT&T D800, unlocked and running on Rogers with Jellybean 4.2.2 (D80010o). I would like to bring my phone into 2016 by updating it to at least KitKat, preferably Lollipop (if I can). The problem is that I can't get a working recovery. Here's what I've tried:
Flashify: following its instructions exactly seems at first like it's working (I get some kind of "success" message) but when it then goes to reboot the phone, it reboots to a black screen (phone is non-responsive -- have to hold down the power button to shut it off, then turn it back on, at which point it boots normally into Android)
TWRP Manager: I've tried it as well, and get the same outcome as Flashify (apparent success followed by a black screen etc.). Once the phone is on and back into Android, TWRP Manager seems to think that TWRP is not installed.
AutoRec: I installed the version from the thread here: http://forum.xda-developers.com/showthread.php?t=2715496 ran it, and again it appeared to be successful. When it rebooted, it did go into recovery, TWRP 2.7.0.0 or something like that. Then I went to "reboot system" but got the same problem as before -- phone non-responsive, slow flashing LED, had to go back into Download Mode and flash the Jellybean TOT file, etc.
Can anyone help me figure out what is going on? I just want to get my phone to a nice stable Lollipop state with decent performance and battery life. Failing that, KitKat. Not sure what to do next.
Crisis averted: I managed to get CloudyG2 2.2 running on my phone and all seems well. Here's what I did:
I installed stock KitKat on my phone using the procedure outlined at http://forum.xda-developers.com/showthread.php?t=2663369
I then rooted the phone with ioroot (following its instructions)
I then used AutoRec to install recovery. For some reason I'm only ever able to boot to recovery directly from AutoRec -- when I try to get into recovery using the usual techniques, the phone locks up. I literally have to reinstall recovery every time and then say "yes" when AutoRec asks me if I want to reboot into recovery. Not sure why this is. The TWRP version I see is 2.7.0.0
I then flashed the KK bootloader and then CloudyG2. So far so good.
I'm a bit too shellshocked to try to install a Lollipop ROM on this phone right now. Maybe some day. In the meantime, many thanks to those who helped me out on other threads.
Why didn't you just tot to the latest rom?
stan54 said:
Why didn't you just tot to the latest rom?
Click to expand...
Click to collapse
Based on comments at http://forum.xda-developers.com/showthread.php?t=2432476 I was under the impression that the farthest I could get would be Jellybean. Then found the other thread with the KitKat TOT. That enabled me to use Autorec (though recovery still works wonky on my phone) so I now have CloudyG2.