Related
So ive alpharev'd my DS. Just wondering if anyone can help me with what to do next. Ive never normally had a problem before (rooted/goldcarded/custom ROM/stock ROM the HTC Hero/Desire and Desire HD before with no problems) but i cant seem to figure out where to go next with the DS. Im after installing a stock ROM woth no bloatware from any carriers.
Do i goldcard and then go for it or is there something else? I dont really want to just go for it and brick my phone.
Cheers all,
Si
Rather than instal a stock rom, why not instal a custom rom that's based on a the stock rom like LBC MOD?
this thread discusses the benefits of a custom over stock http://forum.xda-developers.com/showthread.php?t=1164418
All you'll need is clock work mod recovery which you may have already installed as post of the akpharevx process
Sent from my HTC Desire S using XDA Premium App
Its not that i dont see the benefits of a custom ROM, its just this one is going to be my mrs' phone and im pretty sure there's no way she'll ever need/use anything that a custom ROM has to offer. Which one would you recommend for someone in her shoes? Would need one that didnt overwhelm her with random stuff, in other words one thats more of a user experience than one thats good for dev's / tinkerers? Also, in the thread you posted above, it says you cant install OTA updates - not a bad thing but if i update a custom ROM will the phone have to be reset every time?
Cheers
Si
Ah, I see, although would still recommend LBC rom, it's stable & solid, fast, pretty, bug free and basically just improved stock.
In fact when my wife's contact is up at the end off this month, she's getting a DS and I'll be putting it on that.
Sent from my HTC Desire S using XDA Premium App
Awesome thanks for that Is there anything else id need to do? Or is it literally just download LBC and go for it? o i need to get a radio or is it complete with one? (ive already done the cwm btw).
Si
chockyT said:
Awesome thanks for that Is there anything else id need to do? Or is it literally just download LBC and go for it? o i need to get a radio or is it complete with one? (ive already done the cwm btw).
Si
Click to expand...
Click to collapse
I'm not sure if you're root yet? if you're not, then run ginger break v1.2.
I'd ensure that at this point after getting root that you take a full Nadndroid backup of your device using CWM recovery.
Then I'd replace your CWM recovery with the better EXT4 recovery, which is built on the same code base, but easier to use and has many more options. To do this simply download the ZIP file onto your SD card boot into recovery and select flash ZIP from SD.
Now for flashing the ROM.
I'd then look at the LBC ROM thread (although there is a lot of it, I'd suggest reading the entire thing). most of the information is in #1 and detailed guides are on LBC MOD site.
You;ll need to download from LBC MOD website both the ROM Itself v0.5.2 and the pre-WIPE ALL script, putting them both onto your SD card.
Then boot into recovery and first run the WIPE script from LBC which will create all ext4 partitions for you and WIPE ALL OF YOUR DATA in preparation for the clean install.
Lastly run the ROM ZIP which will eventaully boot a clean device.
You shouldn't need to flash a radio just yet (you can see from my signature which one I run)....everything should just work. Although there are RADIO install instructions and the actual downloads available on the LBC website.
ROM Manager has an option to "Backup Current ROM" and "Manage and Restore Backups". Can all that be used on stock (odexed), rooted ROM?
The End.
I noticed this feature as well. I personally never tried but i am not sure how it would work. It might create a file in the the clockwork mod folder. But i doubt it works. You could always try it out. the worst it could do it bootloop your phone and you can just fxz? haha.
I don't have a method yet for flashing a fxz file. I'm on linux. Ive never been forced to learn how to do it. You try. ;-)
The End.
Haha. That is a great challenge. My phone is charging right now. We need to find another "victim" to do it. I don't think ROM toolbox is very reliable though. Or at least not as reliable as CWM
I use this app to backup and restore apps.
Don't know for sure to backup and restore rom.
Need someone who has warranty to try this though LOL
Sent from my MB865 using Tapatalk 2
kindacrazyazn said:
Haha. That is a great challenge. My phone is charging right now. We need to find another "victim" to do it. I don't think ROM toolbox is very reliable though. Or at least not as reliable as CWM
Click to expand...
Click to collapse
We're talking about ROM Manager by Koushik Dutta. Not "ROM Toolbox". Right?
The End.
As far as backing up and restoring a stock rom, I fairly certain that it will. However, it depends on a CWM mod recovery and at the moment all we have is a frankinmod recovery and Rom Manager doesn't even acknowledge it.
So, if we had CWM in better shape, or a way for Rom Manager to see it, then everything else would fall into place.
On a random note, Rom Manager will boot into recovery with our frankinmod, but that's about it.
@41rw4lk
These are exactly the concerns i have.
The End.
I was referring to ROM Toolbox but i personally never trusted ROM Toolbox or ROM manager. But that is just me personally.
ROM Manager makes things a whole lot easier for flashing ROMs and backing up/restoring. It's developed by koushikdutta, the same person that develops CWM, so everything should be seamlessly integrated. But as 41rw4lk stated, ROM Manager only partially detects our modified, bootstrapped recovery (it can boot into it but no automation). However, you can get it to work on the A2 . Apply the A2 bootstrap, then flash the Bionic recovery from ROM Manager, then re-apply the A2 bootstrap.
---------- Post added at 12:26 AM ---------- Previous post was at 12:24 AM ----------
kindacrazyazn said:
I was referring to ROM Toolbox but i personally never trusted ROM Toolbox or ROM manager. But that is just me personally.
Click to expand...
Click to collapse
Using ROM Toolbox for flashing/restoring/backing up/etc only works if you have the premium ROM Manager. It uses methods from the premium ROM Manager to do just what ROM Manager does. So ROM Toolbox works although there isn't really a reason to use it.
I did away with the bootstrapper and use the cwm on every boot method, which is built into the Sonya rom now I believe. Can I flash the Bionic recovery still without messing everything up?
41rw4lk said:
I did away with the bootstrapper and use the cwm on every boot method, which is built into the Sonya rom now I believe. Can I flash the Bionic recovery still without messing everything up?
Click to expand...
Click to collapse
yes it will work finr as i have done so. Also, the options in rom manager that alow you to backup or restore a rom do work as i have used both mutiple times with out a problem. I just flashed the new lithium rom today right after i backed up my atrix sonya rom using the backup option.
@cogeary
Is there a method to remove the Bionic Recovery? When the Atrix 2 Recovery becomes available would we install that over the Bionic?
The End.
rob219 said:
yes it will work finr as i have done so. Also, the options in rom manager that alow you to backup or restore a rom do work as i have used both mutiple times with out a problem. I just flashed the new lithium rom today right after i backed up my atrix sonya rom using the backup option.
Click to expand...
Click to collapse
I just flashed the Bionic recovery and it works perfectly with Rom Manager. One click backup. Thanks for the tip.
KEB64 said:
@cogeary
Is there a method to remove the Bionic Recovery? When the Atrix 2 Recovery becomes available would we install that over the Bionic?
The End.
Click to expand...
Click to collapse
im not sure about removing it from out phone, but i do know if we ever get an officail or unofficial recovery made just for the atrix 2 you would just either flash it using rom manager (if its in the list of devices) or flash the zip in recovery and reboot into your rom or reboot recovery to check it out.
Technically, the recoveries we're flashing now aren't replacing the system recovery, they're just put in the system and loaded like any other script. If you try to get to recovery manually with buttons, you hit the default system recovery. If we ever get an unlocked bootloader and an official CWM then we're golden and can overwrite the system recovery. So uninstalling everything else should be a matter of deleting scripts, or just not build them into roms anymore since we won't need to.
It's late, so if I'm talking out my ass I apologize. I will say, I appreciate all the work and help from everyone here.
I have been using RM and CWMR since mid 2010, and never considered it was anything but the default app for flashing and the CWM was the "goto" recovery. But I am considering flashing zydroid because it looks like something that would work well for me... But I keep running into TWRP...
Since I may be old school, can someone tell me (I) if this TWRP recovery is advisable, (II) if this is only a One-S thing, or is there a "changing of the guard" taking place, and (III) I already installed goo manager...But I don't see how to change/flash the TWRP recovery, and if it is as simple as just flashing it like we do using RM.
Thanks a lot!
Sent from my HTC One-S (rooted), stock ROM
syntropic said:
I have been using RM and CWMR since mid 2010, and never considered it was anything but the default app for flashing and the CWM was the "goto" recovery. But I am considering flashing zydroid because it looks like something that would work well for me... But I keep running into TWRP...
Since I may be old school, can someone tell me (I) if this TWRP recovery is advisable, (II) if this is only a One-S thing, or is there a "changing of the guard" taking place, and (III) I already installed goo manager...But I don't see how to change/flash the TWRP recovery, and if it is as simple as just flashing it like we do using RM.
Thanks a lot!
Sent from my HTC One-S (rooted), stock ROM
Click to expand...
Click to collapse
In goo manager press flash roms then press try to find me one. It will give you a few prompts and will flash twrp for you simple as that. The next time you boot into recovery it will be TWRP. I'm pretty sure you'll like it.
On a side note TWRP CWM back up and recoveries aren't compatible with each other so once you flash TWRP make sure you make a back up.
Also as long as you have a S4 processor you shouldn't have problems with anything as far as flashing roms or recoveries.
Sent from my HTC VLE_U using xda premium
Just do it, you won't regret it. TWRP is awesome and has so many features. Like states above me, make a backup once you install TWRP since your cwm backup won't work in TWRP
HTC One S running Zydroid!
You also just need to open goo manager then hit menu and one of the options is " install open recovery script", click that and follow the prompts. Boom done.
HTC One S running Zydroid!
Ok.... Do I run the open reccovery script, or do I follow your instructions in your first post? Are they separate (in other words)?
Oh.. and as long s you are here.. what is your experience with Wi-Fi after flashing Zydroid compared to "stock" stock? Any problems?
How is the bootani, etc. Things you think are pretty cool?
Really like the parts of Sense that mod AOSP a little, but I would love a ROM that is a touch of Sense 4 without all the underlying garbage that is either TMO or HTC 's doing.
Alright, I am going to flash (or try to figure it out) and make a backup.
Oh wait, one more question. Besides booting into recovery to Fix Permissions, does goo manager have an option to Fix Permissions while the OS is up? Because I couldn't seem to find it.
Thanks a lot!
Sent from my HTC One-S (rooted), stock ROM
Just open goo manager and press menu, you'll see install open recovery script. That's it, it won't even reboot and you'll have TWRP.
Zydroid works perfectly for me. In fact it's the only rom I installed that wifi even works. I like it and won't leave it unless something incredible comes out that just kills zydroid. There are add ons all available thru goo manager along with kernel choices.
So for me, TWRP is is definitely the way to go. With TWRP you don't need to fastboot boot.img separately. So not having to hook my phone up to a pc and just be able to flash roms when I'm at work and such is a huge part of my decision to go with TWRP.
It's basically stock one S rom with the nice features built in and all of tmobiles crap taken out.
Fix Permissions I know is in TWRP, not sure If you're given the option thru goo manager
HTC One S running Zydroid!
Hi All,
I am looking for a complete guide (or links to various parts) to install the new CM10.1 nightlies that started on 5/19/2013.
I've been looking through XDA and I see a lot of information that's dated for the 4.2.1 and earlier, but nothing that confirms these steps work for these new nightlies.
1. Unlock BL using ASUS v8? (I am on 4.2.1)
2. Root it (how, what procedure should I follow and which files)?
3. Which BL should I install? I've been using CWM on my GS3, but a lot of these guides use TWRP. which versions
4. This guide looks dated, please confirm
http://forum.xda-developers.com/showthread.php?t=2055430
5. Any recommendations for a better ROM? Or is the CM10.1 the best for this tablet?
6. Since I have the WIFI version of this, I am assuming I dont need to worries about the baseband updates that were recently required for the CM10.1 updates? If I am wrong, please advise.
Thanks for you help in advance!
snoopspecial said:
Hi All,
I am looking for a complete guide (on links to various parts) to install the new CM10.1 nightlies that started on 5/19/2013.
I've been looking through XDA and I see a lot of information thats dated for the 4.2.1 and earlier, but nothing that confirms these steps work for these new nightlies.
1. Unlock BL using ASUS v8? (I am on 4.2.1)
2. Root it (how, what procedure should I follow and which files)?
3. Which BL should I install? I've been using CWM on my GS3, but a lot of these guides use TWRP. which versions
4. This guide looks dated, please confirm
http://forum.xda-developers.com/showthread.php?t=2055430
5. Any recommendations for a better ROM? Or is the CM10.1 the best for this tablet?
6. Since I have the WIFI version of this, I am assuming I dont need to worries about the baseband updates that were recently required for the CM10.1 updates? If I am wrong, please advise.
Thanks for you help in advance!
Click to expand...
Click to collapse
Most of your questions have already been answered multiple times. Ill do my best to summarize the answers ......
1) V8 unlocks most although there are some who arent able to unlock after having things come back from Asus from repair.
2) Unless you are stuck on a locked bootloader, skip rooting if you are planning on installing a custom rom..... why waste your time rooting something you wont be using? If you fall into this category, your option are limited but there is a way to root without TWRP or CWM.
3) Personally I have found that the 4.1 bootloader version 10.4.2.20 seems to play nicest with my tf300t. This of course means im stuck using Roms made specifically for 4.1 bootloaders. Im using twrp 2.4.4.0. Instructions on downgrading firmware are all over, but im pretty sure you must have an unlocked bootloader for this as well. Its a simple fastboot command to push the older system blob file to the device. Relatively easy.
4) Cant comment as I dont use CM
5) Im using CleanRom Inheritance and found that it not only benches higher, but runs much much faster than anything else I have tried on my tablet. I started with the latest 4.2.1 ROM and Bootloader. After trying everything out and everything lagging on my tablet, I decided to downgrade firmware. ROMS are nothing but personal preference, but, I find personally that Cromi ( for 4.1 ) along with Unter's kernel,makes my device smooth as butter. YMMV
6) Again, I cant comment as I dont use CM. Maybe someone else can chime in on this ? There are PLENTY of rom options available. Just try things out and see what you like best. Just remember to read the roms OP very carefully to make sure you have the proper bootloader installed for it. You can brick your device if you mismatch the rom and bootloaders.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
pyraxiate said:
Most of your questions have already been answered multiple times. Ill do my best to summarize the answers ......
1) V8 unlocks most although there are some who arent able to unlock after having things come back from Asus from repair.
2) Unless you are stuck on a locked bootloader, skip rooting if you are planning on installing a custom rom..... why waste your time rooting something you wont be using? If you fall into this category, your option are limited but there is a way to root without TWRP or CWM.
3) Personally I have found that the 4.1 bootloader version 10.4.2.20 seems to play nicest with my tf300t. This of course means im stuck using Roms made specifically for 4.1 bootloaders. Im using twrp 2.4.4.0. Instructions on downgrading firmware are all over, but im pretty sure you must have an unlocked bootloader for this as well. Its a simple fastboot command to push the older system blob file to the device. Relatively easy.
4) Cant comment as I dont use CM
5) Im using CleanRom Inheritance and found that it not only benches higher, but runs much much faster than anything else I have tried on my tablet. I started with the latest 4.2.1 ROM and Bootloader. After trying everything out and everything lagging on my tablet, I decided to downgrade firmware. ROMS are nothing but personal preference, but, I find personally that Cromi ( for 4.1 ) along with Unter's kernel,makes my device smooth as butter. YMMV
6) Again, I cant comment as I dont use CM. Maybe someone else can chime in on this ? There are PLENTY of rom options available. Just try things out and see what you like best. Just remember to read the roms OP very carefully to make sure you have the proper bootloader installed for it. You can brick your device if you mismatch the rom and bootloaders.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
First of all, thanks for the quick reply and detail!
1. I have a new one - so hopefully I should be ok. But I'll use v8
2. Great point, duh! The ROMs are already rooted!
3. I'd like to stick with the 4.2.2 bootloaders since my other devices are all running the same stuff. I haven't used TWRP before - any preference to that versus CWM?
4. no worries
5. I'll definitely keep in mind along with your bootloader suggestion should I downgrade. I've felt the lag with the ASUS Stock 4.2.1 ROM and all it's bloatware - I'm expect an immediate change right there with a clean rom.
6. yeah that is the primary reason I am asking about which bootloader to use with CM10.1's new nightlies.
snoopspecial said:
First of all, thanks for the quick reply and detail!
1. I have a new one - so hopefully I should be ok. But I'll use v8
2. Great point, duh! The ROMs are already rooted!
3. I'd like to stick with the 4.2.2 bootloaders since my other devices are all running the same stuff. I haven't used TWRP before - any preference to that versus CWM?
4. no worries
5. I'll definitely keep in mind along with your bootloader suggestion should I downgrade. I've felt the lag with the ASUS Stock 4.2.1 ROM and all it's bloatware - I'm expect an immediate change right there with a clean rom.
6. yeah that is the primary reason I am asking about which bootloader to use with CM10.1's new nightlies.
Click to expand...
Click to collapse
To be honest, the lag is still there accross all the 4.2 roms I tried, even debloated. Its not as bad but its still there. My alternate device has a beastly exynos in it so im used to a perfect smooth experience. I notice even a little bit of jitter and it drives me crazy ( hence why I downgraded to 4.1 ) .
As far as what bootloader to use for which CM rom, each will tell you which to use specifically. I saw there is a cm10.1 for 4.2 and for 4.1. Just make sure to match things.
I used to be a CWM user all the way, but twrp does trump it in features and usability, especially for the transformer series. I beleive there is only one single twrp that works properly on the new bootloader for stock based roms ( no cwm will work on it at all). It ends in .42 so make sure you flash the correct one. If not, your partitions wont be writable.
One MAJOR warning.........
Do NOT use the wipe / factory reset on ANY bootloader. You will brick your tablet!!! Permanently!!!!
You can ONLY use the wipes inside of twrp / CWM.
Sent from my SGH-T889 using xda app-developers app
dude, you are so awesome!
definitely smart to have installed TWRP - CWM through ROM Manager tried to suggest installing a TF201 recovery. From the web site it's vague but suggest a TF101 image as well.
I followed your suggestion and downloaded the 42 TWRP recovery from after having done all the SDK Tools installation and testing connectivity with FASTBOOT (from the installed SDK package, not random ones from the internet).
http://www.teamw.in/project/twrp2/97
I'm up in TWRP and running a backup of the ASUS original installation, will copy to External SD card.
previously i've formatted the internal card and then installed the ROM and GAPPS. Should I not do this?
thanks again! I'm keeping notes and will update when done.
pyraxiate said:
Most of your questions have already been answered multiple times. Ill do my best to summarize the answers ......
1) V8 unlocks most although there are some who arent able to unlock after having things come back from Asus from repair.
2) Unless you are stuck on a locked bootloader, skip rooting if you are planning on installing a custom rom..... why waste your time rooting something you wont be using? If you fall into this category, your option are limited but there is a way to root without TWRP or CWM.
3) Personally I have found that the 4.1 bootloader version 10.4.2.20 seems to play nicest with my tf300t. This of course means im stuck using Roms made specifically for 4.1 bootloaders. Im using twrp 2.4.4.0. Instructions on downgrading firmware are all over, but im pretty sure you must have an unlocked bootloader for this as well. Its a simple fastboot command to push the older system blob file to the device. Relatively easy.
4) Cant comment as I dont use CM
5) Im using CleanRom Inheritance and found that it not only benches higher, but runs much much faster than anything else I have tried on my tablet. I started with the latest 4.2.1 ROM and Bootloader. After trying everything out and everything lagging on my tablet, I decided to downgrade firmware. ROMS are nothing but personal preference, but, I find personally that Cromi ( for 4.1 ) along with Unter's kernel,makes my device smooth as butter. YMMV
6) Again, I cant comment as I dont use CM. Maybe someone else can chime in on this ? There are PLENTY of rom options available. Just try things out and see what you like best. Just remember to read the roms OP very carefully to make sure you have the proper bootloader installed for it. You can brick your device if you mismatch the rom and bootloaders.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
snoopspecial said:
dude, you are so awesome!
definitely smart to have installed TWRP - CWM through ROM Manager tried to suggest installing a TF201 recovery. From the web site it's vague but suggest a TF101 image as well.
I followed your suggestion and downloaded the 42 TWRP recovery from after having done all the SDK Tools installation and testing connectivity with FASTBOOT (from the installed SDK package, not random ones from the internet).
http://www.teamw.in/project/twrp2/97
I'm up in TWRP and running a backup of the ASUS original installation, will copy to External SD card.
previously i've formatted the internal card and then installed the ROM and GAPPS. Should I not do this?
thanks again! I'm keeping notes and will update when done.
Click to expand...
Click to collapse
okay - lots of options in TWRP - going the simple safe route and just following the norm:
http://teamw.in/whattowipe
snoopspecial said:
dude, you are so awesome!
definitely smart to have installed TWRP - CWM through ROM Manager tried to suggest installing a TF201 recovery. From the web site it's vague but suggest a TF101 image as well.
I followed your suggestion and downloaded the 42 TWRP recovery from after having done all the SDK Tools installation and testing connectivity with FASTBOOT (from the installed SDK package, not random ones from the internet).
http://www.teamw.in/project/twrp2/97
I'm up in TWRP and running a backup of the ASUS original installation, will copy to External SD card.
previously i've formatted the internal card and then installed the ROM and GAPPS. Should I not do this?
thanks again! I'm keeping notes and will update when done.
Click to expand...
Click to collapse
Im assuming you are flashing CM10 then? The only important thing is fully read the OP and match your bootloader to whatever one they tell you. Its generally not a suggestion, but an actual requirement.
Mines a 32gb so I keep all of my backups and rom flashes right on the internal storage. I feel its safer in case of SD corruption or an accidental wipe. It doesnt hurt to have it in 2 places though ( backup your original rom to SD card but keep everything on the internal as well ). I always flash from internal ( roms and nandroids alike ). Ive never had an issue.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
so this is what i've done so far and am stuck now it seems. probably a mismatch between the CM ROM and the BOOTLOADER.
1. Installed TWRP 2.5.0.0 - version ending with 42.
2. From the Wipe -> Advanced in TWRP, I selected SYSTEM, CACHE, DALVIK CACHE, and DATA (skipped the last two options).
3. I have the ROMs/GAPPS on my external SD card (and backup now too)
4. I installed today's nightly CM 10.1 for TF300T and the 20130301-signed (per 4.2.2 CM builds).
5. Reboot (via TWRP, Power Off)
I hit the power button to turn on and it gets stuck at the ASUS screen. Cannot boot into ROM either via the Android icon in the Bootloader menu.
snoopspecial said:
so this is what i've done so far and am stuck now it seems. probably a mismatch between the CM ROM and the BOOTLOADER.
1. Installed TWRP 2.5.0.0 - version ending with 42.
2. From the Wipe -> Advanced in TWRP, I selected SYSTEM, CACHE, DALVIK CACHE, and DATA (skipped the last two options).
3. I have the ROMs/GAPPS on my external SD card (and backup now too)
4. I installed today's nightly CM 10.1 for TF300T and the 20130301-signed (per 4.2.2 CM builds).
5. Reboot (via TWRP, Power Off)
I hit the power button to turn on and it gets stuck at the ASUS screen. Cannot boot into ROM either via the Android icon in the Bootloader menu.
Click to expand...
Click to collapse
going to give Cromi 4.2.1 a try too while I am in this bootloader:
http://forum.xda-developers.com/showthread.php?t=2204166
I have the matching ASUS bootloader and TWRP combination this the ROM needs.
As for the CM10.1 - looks like for TF300T they are still using the older JB requirements... but still researching.
snoopspecial said:
going to give Cromi 4.2.1 a try too while I am in this bootloader:
http://forum.xda-developers.com/showthread.php?t=2204166
I have the matching ASUS bootloader and TWRP combination this the ROM needs.
As for the CM10.1 - looks like for TF300T they are still using the older JB requirements... but still researching.
Click to expand...
Click to collapse
interesting - this ROM is packed with configuration options - you can really tailor your install.. very interesting - should work since it is a stock-based rom. we'll see. installing now.
snoopspecial said:
interesting - this ROM is packed with configuration options - you can really tailor your install.. very interesting - should work since it is a stock-based rom. we'll see. installing now.
Click to expand...
Click to collapse
yeah so that worked fine. the CM10.1 version must require some different combination.
taking your suggestions now and downgrading to the 4.1 bootloader. will also install the CleanInheritance rom.
by the way, thanks again for your help and suggestions!
So just for other people out there... if you want to run the TF300T downloads from get.cm (the nightlies as of now).
I've confirmed the following requirements:
1. 10.4.2.20 - TWRP 2.5.0.0 - JB
2. CM 10.1 5/25/2013 Nighty (This is a 4.2.2 ROM - requiring the JB, not 4.2 bootloader - i imagine at some point this will be updated)
3. GAPPS 20130301-signed
ah so nice!
First off huge thanks to every dev in this thread. At the time my G2 was being repaired so I didn't get to help out
By following the steps below, you can run the new 4.4.2 kitkat rom from LG (and 4.4.2 stock modified roms to come) with our old partitions which are fully loki-able
DO THIS ENTIRE PROCESS AT YOUR OWN RISK - IF YOU DO NOT UNDERSTAND THESE DIRECTIONS, THEY ARE NOT FOR YOU. I TRIED TO MAKE THEM AS SIMPLE AS POSSIBLE. THIS WILL WIPE YOUR WHOLE PHONE. THIS IS FOR D801 ONLY.
Also please no stupid questions, I will not answer. I will try to help with legitimate problems.
If you upgraded to 4.4.2 through the KDZ or flashed the 4.4.2 stock rom from smiley on this forum (since he included the new partitions) you must follow every step here. If you are still on 4.2.2 partitions (You have these if you currently are using an aosp / cm rom with a custom recovery) - Then you may go straight to step 5.
1. You must revert to stock 4.2.2 using this guide. You must restore to the C version. DO NOT USE G. You can find the link to 801C here.
2. Once you successfully flash this, your phone should boot loop on the T-Mobile screen. Boot into recovery (which is now LG's stock recovery) once you are in press power twice to data reset. Remove the USB cable from the phone when trying to boot to recovery, it makes it much easier for some reason. After data reset your phone should now boot into stock LG 4.2.2
3. Root your phone with this.
4. Install a custom recovery with this guide. The TWRP listed in this guide is old and you must this one instead. Method 1 works fine for this if anyone is wondering.
5. At this point you should have 4.2.2 partitions with root and custom recovery. Bet you wish you didn't update to 4.4.2 Stock at this point :good:
6. Boot into recovery. FULL WIPE EVERYTHING (Except for internal storage. This mean you wipe System Data Cache and Dalvik. Very Important.) Flash this Rom in recovery that I put together (And here is a Mirror). It contains the 4.4.2 KDZ system image with the 4.4.2 modem. Make sure you backup your EFS. The kernel inside this rom is stock LG 4.4.2 with a minor change to allow it to boot on the 4.2.2 bootloader. Thanks to the dev's in that thread who worked on it.
7. Flash SuperSU for root.
8. You are now on 4.4.2 Stock rom with recovery, root, loki and the ability to flash custom 4.4.2 stock kernels when they are released (soon)
At this point you will be able to flash any rom you want, including aosp stuff. Do not flash any other kernel on the included LG 4.4.2 stock rom. I will be making a custom kernel / 4.4 stock roms for this soon anyway - WHEN FLASHING 4.4.2 STOCK ROMS PLEASE MAKE SURE THEY DONT HAVE PARTITIONS BESIDES SYSTEM/MODEM/RPM/TZ INSIDE!!!! JUST OPEN THE ZIP AND CHECK INSIDE. ANYTHING EXTRA YOU WILL HAVE TO REDO THIS ENTIRE PROCESS !!!!!!!! I really hope devs stop putting up roms with the new partitions included.
Excellent. Thank you
Awesome great job Doc.
Sent from my LG-D801 using XDA Premium 4 mobile app
Excellent! Thank you!
One question, will this work for the D800? J/K :laugh:
Just what I've been looking for. Thanks.
Niceeeeee !!!!!!
Finally, Thanks to everyone involved in making this possible. :good:
Can't get the download to finish, mirror?
Sent from my LG-D801 using xda app-developers app
Smokeey said:
Can't get the download to finish, mirror?
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
I'll put up a mirror for the stock rom zip, its going to take a little bit to upload. Guessing 25 mins from now expect the link.
Edit: Mirror up under Step 6
Thanks man.
I love you full homo lol
Sent from my LG-D801 using XDA Premium 4 mobile app
Super happy about this. I've been crack-refreshing this forum waiting to see this happen. Now, any way to do this on a Mac since the LG tool doesn't work?
adampdx said:
Super happy about this. I've been crack-refreshing this forum waiting to see this happen. Now, any way to do this on a Mac since the LG tool doesn't work?
Click to expand...
Click to collapse
no clue, you need to search around. Never had a mac Maybe you can get access to a laptop or something
dr87 said:
no clue, you need to search around. Never had a mac Maybe you can get access to a laptop or something
Click to expand...
Click to collapse
I have searched into the depths of Google. To my knowledge, besides the LG tool there is no way to flash a .kdz file on a Mac. I have a Windows desktop and even a VM on the Mac, but my desktop keeps blowing power supplies and I haven't set up Windows on the VM. Oh, well! Looks like I know what I'm doing this weekend.
OK. I am currently on Mahdi 2.5 with TWRP 2.6.3.5. I have a backup of stock 801c from just after I rooted. Can I revert to that backup and then just flash this?
Project X-Ray said:
OK. I am currently on Mahdi 2.5 with TWRP 2.6.3.5. I have a backup of stock 801c from just after I rooted. Can I revert to that backup and then just flash this?
Click to expand...
Click to collapse
"If you are still on 4.2.2 partitions with a custom recovery / aosp you may go straight to step 5."
I just made it more clear in the OP what 4.2.2 partitions are
Is someone going to be a beast and make a video tutorial for this?? Need me a video tutorial to really grasp it for me to feel completely safe. Lol. Really want custom recovery. Anyways THANK YOU to those who whipped this up!
Sent from my LG-D801 using xda app-developers app
Flashing supersu fails for me. Cant figure out how to get around it. Also seems i lost root. any ideas?
davidgq said:
Flashing supersu fails for me. Cant figure out how to get around it. Also seems i lost root. any ideas?
Click to expand...
Click to collapse
Well with no SU you won't have root of course. What does the error say. I completed this whole process twice and never ran into this issue.
dr87 said:
Well with no SU you won't have root of course. What does the error say. I completed this whole process twice and never ran into this issue.
Click to expand...
Click to collapse
During the flash it says it is unable to open the zip file
Everything running Smooth
Did the whole proccess with no problem, Been running on KK for a couple of hours with no issues except for Gmail bookmarks not syncing on LG's stock browser. Battery looks pretty decent, should get better after a few cycles.