Related
Unofficial Kitkat 4.4.4 update for the Moto G
by GPz1100
Purpose: To explore the recently released 4.4.4 update and retain the ability to revert back to Boost firmware. The full firmware update package changes other areas on the device that prevents downgrading. If/when Verizon implements the foreign ESN ban it will no longer be possible to switch the device between PagePlus accounts. At present there is no Android 4.4.4 update specifically for Boost. Flashing 4.4.2 software on device with the 4.4.4 update results in an unstable, nonworking phone. It also remains to be seen if this flash will even be possible after the Boost 4.4.4 update is released.
This archive contains just the system and kernel portions of the firmware. Based on the official 4.4.4 update from Motorola. By only altering these partitions, full downgrade options remain. In testing, all functions of the phone appear to work normally. Flash is retained, full network connectivity remains (including 3g data), camera works, wifi, etc.
Why: Forward thinking. Retaining options. Samsung devices come to mind. After the first OTA on devices such as the VZW S4 (S3 suffered the same fate after later updates) boot loader was entirely locked. No non-stock roms or even stock roms using non-stock kernels.
Precautions: Generate a backup image of your current system before proceeding. Results have been successful dirty flashing (no factory reset). Highly unlikely to brick your phone, but as with all disclaimers, proceed at your own risk.
Requirements: Moto G w/ Permanent flash, TWRP recovery
Installation:
1) Download and extract the entire contents of the archive into the following location on the internal storage
Computer\XT1028\Internal storage\TWRP\BACKUPS\{SERIAL}
The value for {SERIAL} can be obtained from settings|about|status|serial Number. Case does matter for everything. If the folder structure is not maintained, the package will not be visible in step #4.
2) Reboot into recovery
3) Tap on WIPE, ADVANCED WIPE, put a check mark next to Dalvik cache, and cache (1st and 4th entries). Swipe to begin
WARNING, do not check anything else or you will factory reset or possibly erase the internal storage.
4) Tap Home, then Restore, Select KitKat_4.4.4 as the restore package from the list, Swipe to begin
5) Once done, tap Reboot System. First boot will take a few minutes longer.
Enjoy!
Link
{reserved}
Nice work. I'm not sure if I'm ready to try it but sometimes I get bored and will try just about anything.
Which TWRP version was used for your testing? I'm currently using PHILZ (with backup issues) and will need to switch.
Thanks for your hard work.
Rampart, this was generated using twrp 2.6.3.3. I've never used philz's recovery; not sure if it'll read/write twrp images properly.
I've had this running on my test phone for a few days now. Can't say I've seen any issues or other oddities. I'm still not ready to commit to the full blown ota, so this is the next best thing.
Thanks.
IF I do it, I'll switch to TWRP.
I'm waiting on the 4.4.4 because there seems to be some issues. I learned a long time ago (when I worked for IBM), never be 1st on the block to try new software. 4.4.2 works just fine for what I need it for. Great cheap phone and on PagePlus I save a ton of money.
I've read pretty much every source I can find on getting a custom ROM up on my LG G2, which I haven't even rooted in the past 2 and a half years. My warranty ran out a while back and I'm getting a bit bored with stock now, and I want to start flashing, but the last time I did this was with my old HTC Desire HD.
As you can see I'm on 20d on my LG G2. It's a Hong Kong version for some reason, lol. What I considered doing was the following: update to the latest Lollipop official ROM using the LG Flash Tool (it gives me an available update to 30d); root using the rooting app, install a recovery with AutoRec Lollipop, flash a thermal recovery from the installed recovery (very scared of my phone overheating, I'm even considering putting it on a large, fast-running fan while doing anything, read too much about the phone overheating and making the screen yellow); back up my phone's IMEI data; use the recovery to install a brand new (I'm hoping a Marshmallow) ROM. I also understood that I need to flash a bootstack to change my bootloader to a KitKat, because it can be "fooled" using the BUMP thing. Is that correct? Do I even have to update my phone to Lollipop in this case? Also, how likely is it to overheat while doing all of these procedures?
Thanks in advance!
Sorry for the necroing my old thread, but I have yet to do anything with my phone. I am also still on KK. I saw that I can start rooting and install TWRP from it straight away. After that I need to flash a bootstack, right? How likely is it that I can brick myself? By that I mean what could get mixed up to get a brick while flashing. Also, has anyone had overheating issues while doing root, recovery installation and flashing things (newer TWRP, bootstacks, new ROM)?
Hi, i can understand your situation as i was in same till today, g2 with stock kitkat.
i finally installed cm13 after rooting it and the phone feels fresh.
you have understood most things right and ready now.
you dont need to upgrade to lollipop if youdont want to, you can start from kitkat itself.
few things i can tell you to begin here,
Root your G2,
for kitkat i found few good methods. Either do it via ioRoot using pc. or you can use towelroot or kingoroot apps to do it from phone itself. I used kingoroot since i didnt have a system with me. You can find these apps by searching at google, jst tyoe kingoroot. At first i was skeptical but it worked nice.
after root, you download autorec app, this is to install a custom recovery(twrp) for kitkat. you just have to install the app and run it and press install recovery/twrp and it'll do the rest.
after you have twrp installed, you need to upgrade it to latest version. For that download blastgator's twrp for your model and flash it through your recovery.
oh and dont forget to learn, how to enter into recovery yourself, since each G2 model has different method.
once you have these things you can start flahing roms. Most of the instructions on how to flash certain rom with what bootloader and bootstack etc. is written in its own thread, so you can learn that from that rom's thread that you will flash.
but basically, you need kk bootloader and lp bootstack for cm13 and above. usually both these things come in one zip. (if not you check for hybrid bootstacks)
Just make sure you are downloading things For your Model, if you try to flash different models stuff into yours, itll brick.
The autorec app, blastgator's twrp and ioroot can be found in a sticky thread in G2 general section, along with many other files and guides in that thread, theres complete index in that thread of all thing for all g2 models .
here : http://forum.xda-developers.com/lg-g2/general/05-10-index-guides-fixes-roots-t3218178
also usually the phone doesnt heat up while flashing, just make sure your battery is more than 80% before you start and itll be ok. Even if it does a little, after a custom rom itll be fixed. I suggest you try cm13 for starters as your first custom rom.
hope this helps you :good:
Good Luck ::highfive:
Thank you very much, appreciate the vote of confidence, lol.
I've actually considered installing Resurrection Remix Marshmallow. In the thread they point to the hybrid bootstack I need to install. I am on a D802 phone, so I'll be downloading that boostack. Anything I should really know before flashing that particular stack, except that I need to run the latest recovery from blastagator? Can I boot back into my old stock KK installation before putting the new ROM and Gapps on my phone and wiping + flashing, or will the phone not be able to boot that old firmware with the new bootstack? Theoretically, can the phone still get bricked even if I'm using the latest recovery + the proper bootstack? I've read that the CM13 devs don't recommend flashing bootstacks but instead using the kdz flashing method to flash the latest Lollipop release...
hitmancho said:
Thank you very much, appreciate the vote of confidence, lol.
I've actually considered installing Resurrection Remix Marshmallow. In the thread they point to the hybrid bootstack I need to install. I am on a D802 phone, so I'll be downloading that boostack. Anything I should really know before flashing that particular stack, except that I need to run the latest recovery from blastagator? Can I boot back into my old stock KK installation before putting the new ROM and Gapps on my phone and wiping + flashing, or will the phone not be able to boot that old firmware with the new bootstack? Theoretically, can the phone still get bricked even if I'm using the latest recovery + the proper bootstack? I've read that the CM13 devs don't recommend flashing bootstacks but instead using the kdz flashing method to flash the latest Lollipop release...
Click to expand...
Click to collapse
to upgrade from kitkat you need lp or hybrid bootstacks. they have images (. img files) that are needed for your phone to function properly., like aboot, modem, radios etc. Hybrid bootstack contains aboot from kk and everyhing else from Lp. So when youll flash a bootstack, youll need to wipe everything, except internal storage(or external if you have one) , before you can flash it. that wipe will include, cache, dalvik cache, system, data. so basically all the old system stuff will be gone before you can flash this bootstack. i hope after reading that youll know that you cant access your old kk installation since itll be wiped, therell be nothing to boot to. if youll try, it will give you errors on lg logo.
understand it like this, to install new 21 inches tyres to your car, you need to upgrade the rims to hold a 21 inch tyre right? what will happen if you just put the 21' tyres on old 15' rim or old 15' tyres on new 21' rims?
the cm 13 devs dont recommend you to flash bootstacks because most of the models took the official lollipop update, which put everything in their phone to lolipop level. since there is no official marshmallow(MM) bootstack for our phone (because no official update), everyone developed ways to utilize lollipop bootstack to function on a custom MM Rom. Since most models are already on lollipop, theres no need to flash lollipop bootstack while flashing custom rom. That step is mostly for those who are still on stock or custom kitkat based rom. So they say to get official lollipop through kdz method, instead of flashing Lp bootstack before gettig their rom. But remember if a rom developer asks to install a bootstack for their rom, you should consider it if you dont have much knowledge about it, cause if you dont follow instructions, you can soft brick, in that case youll need hybrid bootstack.
see if you are using everyhing proper for your phone then your phone wont brick. only thing that can go wrong with that condition is your execution, your steps. As long as you dont make a mistake in these steps everything will go fine.
ill explain it what you should do.
1. first root your phone.
2. when done rooting, install "root checker" from google play. itll confirm if you have root or not.
3.Then you come back here and find autorec app from the link i gave you in my previous reply. download that, install the autorec app. and follow on screen instructions and itll install twrp recovery for you.
4. then come back here again, and find blastgator's twrp, from the same link in previous post. itll be the one whih says "twrp with f2fs". download it and remember where you put it.
5. turn off phone, boot into recovery (i hope you've learned by now how to get into recovery of your g2 model). Now youll be in recovery, hit install button there and find where you put that file, flash it, then reboot recovery, youll have new recovery after that. then you reboot into system.
now upto this point, you can play along in your kk, have fun with features, say last goodbyes and all lol. Because everything stock kk related will be gone, past this point, including all the apps you have installed.
[IMPORTANT] : after rooting and installing recovery, get bootstack zip, rom zip and gapps zip files downloaded and placed together in a folder on your phone, before you start with flashing bootstack. Because you wont be able to boot back into system after flashing just bootstack.
now you prepare for MM, boot into recovery, now since you are in kk, you need to install LP bootstack, and for that you need to wipe everything using your recovery's wipe feature.
6. in recovery, hit wipe, hit advanced, select cache, dalvik cache, system, data. [ Dont select internal storage otherwise all flashing files will be gone and youll be left with a brick.] and wipe.
7. Now hit the back button to go back to main recovery screen once wiping is finished. hit install, flash the bootstack zip.
8. now your phone has new bootloader but its still empty, like you got a body but no soul . so hit back button, hit install and flash the rom zip you downloaded.
9. now flash gApps same way.
10. once its done, just hit reboot system. no other steps needed.
11. be patient, first boot takes longer than normal boot.
12.enjoy MM :highfive:
you probably know these steps from all the reading but its for your reference, so you dont screw up at all and be safe from bricking.
you can get google apps from opengapps website. you need to get ARM-> 6.0 -> (your prefered ones) pico/nano/micro/etc.. pico has the least amount of gapps, all important ones are there in pico, then extra will increase as you go up from pico to stock. stock has all the gapps. size will also increase as you go up. so choose as you prefer.
now once you have a cm13 /MM based rom, you wont need to flash bootstacks for other roms from next time unless the developer instructs to do so.
good luck
@MarshisnotMellow
Does the cwm mm come pre rooted? Or unrooted ready from whatever idiocy I'm ready for?
1.stock
2.root
3.autorec twrp
4.upgrade to blastagators 3.0.2-1> or a different version I'm missing? This one says blastas twrp bump
5.put cwm rom, bootloader, gapps <where to get gapps zip?> onto internal memory somewhere familiar to me
5.wipe all but internal memory
6.flash bootloader
7.flash rom
8.flash gapps
9.???
10.profit
Check my steps teacher? I'm gonna start it anyway when my phone hits 80+ percent
andrew2432 said:
@MarshisnotMellow
Does the cwm mm come pre rooted? Or unrooted ready from whatever idiocy I'm ready for?
1.stock
2.root
3.autorec twrp
4.upgrade to blastagators 3.0.2-1> or a different version I'm missing? This one says blastas twrp bump
5.put cwm rom, bootloader, gapps <where to get gapps zip?> onto internal memory somewhere familiar to me
5.wipe all but internal memory
6.flash bootloader
7.flash rom
8.flash gapps
9.???
10.profit
Check my steps teacher? I'm gonna start it anyway when my phone hits 80+ percent
Click to expand...
Click to collapse
cwm is clockworkmod, its a custom recovery. i think you meant CM 13, mm rom.
yes, the Cyanogenmod team have placed root access into the rom, so once youll be finished wih installing cm 13 rom, you can just go to settings, Tap build number repeatedly until a message will show "congrats you are a developer now". that'll open developer options in main setting screen Go into that and youll see root access. turn it on. youll have root.
you can check in root checker app to confirm root access for confirmation. you wont need super su app in any of these roms anymore.
your steps :
stock
1. root
2.autorec (for installing twrp on your phone) for kitkat its on forums, for lollipop its in google play. just get the one for your model, search for autorec in google play.
- blastgator's twrp requires you to have any version of twrp beforehand in order to install his version.
3. download and save blastgator's latest twrp, when youll go to download his twrp, itll be written there which one's is the latest version, just download that one and flash it through recovery.
4. Yes place all files in your phone, you can get gapps from opengapps.org/
select arm- 6.0- whatever size you like(, pico is lightest contains all essential gapps, stock contains every gapps)
5. wipe yes.
6. flash bootstack
7. flash rom
8. flash gapps
9. once gapps done, just hit reboot system.
10. enjoy
yes go for it when you have more than 80% battery, this is to ensure that all flashing steps go through without any issue, you dont want your phone to run out of juice while flashing rom do you that could cause soft bricks. so always keep battery more before flashing.
[IMPORTANT] : remember to read instructions of the rom you're installing and adjust the steps as instructed in there.
Goodluck :highfive:
Awesome, I forgot to.flash gapps prior to something I just did, not sure if it will cause increased global warming or thermonuclear war...update soon
@MarshisnotMellow
Gapps installed!! No Internet connection on the d800 and something sinister has happened to my unlocked WiFi Hotspot so I'll have to check for play store capabilities later!! Thanks for the help!!
I decided to go with the latest 29.10.2016 nightly of CM13 for my first run on this phone. Everything went through, no one died, lol. I'm going to start installing and restoring stuff now, get Xposed on, like I have on my TF701T tablet and trick out my phone's appearance. Just a note - after you install new bootstacks your phone's MAC address will change, so if you have a WiFi network with a MAC filter you might want to add your new address.
Hello all,
Been a LONG while since I've actively played around with rooting and unlocking an android device. I finally "upgraded" from my very aged Galaxy S4 to the Moto E4 XT1768. I have successfully unlocked the bootloader, got TWRP installed, rooted with Magisk, and gotten Xposed installed with my favorite modules.
This morning, I got a prompt that a new security update is available, and like a noob, I tried to take the update. This resulted in me getting stuck in a loop where the phone only wanted to boot into TWRP. I got that fixed thanks to XDA, got the pending and failing update completely cleared and am booted back into the device normally, and have frozen the moto update service.... but now...
Is there a way without completely flashing back to stock rom? I know how to take titanium or nand/twrp backups, but I feel like this would still be hours of work to go back to stock, flash, re-root restore all apps blah blah. what are the chances of there being a dirty-flashable zip put out at this point?
The way I normally do these type of upgrades is to download the firmware (from here), use fastboot commands to wipe (erase) and flash the needed partitions (everything but data and recovery), boot to TWRP - flash the no-verity-opt-encrypt.zip & root, and then reboot to system - done. It's easy enough for me, but I know some prefer to being able to use a flashable zip in TWRP.
Also, I have to ask - did you get your e4 cheap? It's was replaced by the e5, some other phones seem to be getting replaced like the G6 series (it's gone on clearance at some places), so they can be had cheap.
bast525 said:
Hello all,
Been a LONG while since I've actively played around with rooting and unlocking an android device. I finally "upgraded" from my very aged Galaxy S4 to the Moto E4 XT1768. I have successfully unlocked the bootloader, got TWRP installed, rooted with Magisk, and gotten Xposed installed with my favorite modules.
This morning, I got a prompt that a new security update is available, and like a noob, I tried to take the update. This resulted in me getting stuck in a loop where the phone only wanted to boot into TWRP. I got that fixed thanks to XDA, got the pending and failing update completely cleared and am booted back into the device normally, and have frozen the moto update service.... but now...
Is there a way without completely flashing back to stock rom? I know how to take titanium or nand/twrp backups, but I feel like this would still be hours of work to go back to stock, flash, re-root restore all apps blah blah. what are the chances of there being a dirty-flashable zip put out at this point?
Click to expand...
Click to collapse
Flashing back to stock and taking the updates is really the best way. Unless you can find a complete firmware package of the new update which of course takes back to stock as well. Really the only way to do it. @MotoJunkie01 makes some TWRP flashable stock roms. And he also creates the partition updater which updates your oem partition and other important things that can't be done in the Twrp flashable stock ROM.
madbat99 said:
Flashing back to stock and taking me updates is really the best way. Unless you can find a complete firmware package of the new update which of course takes back to stock as well. Really the only way to do it. @MotoJunkie01 makes some TWRP flashable stock roms. And he also creates the partition updater which updates your oem partition and other important things that can't be done in the Twrp flashable stock ROM.
Click to expand...
Click to collapse
Speaking of that, @ALI12 just posted a stock firmware package for the NCQS26.69-64-10 build. He gave me approval to use it to update my firmware thread to the latest build, so I'll be updating that OP shortly.
MotoJunkie01 said:
Speaking of that, @ALI12 just posted a stock firmware package for the NCQS26.69-64-10 build. He gave me approval to use it to update my firmware thread to the latest build, so I'll be updating that OP shortly.
Click to expand...
Click to collapse
This will be for the XT1766, correct? Or will same build work for XT1768 (me thinks not)?
So what would the easiest/quickest way be to get updated with all of my apps and data intact? Twrp backup of data partition? Or would there be any way to do this without wiping data at all?
bast525 said:
So what would the easiest/quickest way be to get updated with all of my apps and data intact? Twrp backup of data partition? Or would there be any way to do this without wiping data at all?
Click to expand...
Click to collapse
If you're going to slash a firmware package you'll want to wipe everything. Especially data. Make a backup of your data first of course. After you flash TWR P you can try restoring your data and see if everything comes back. but everything in your downloads folder and all of that will be gone once you format data to remove encryption again.
Hi,
I've noticed pitch black recovery that i have installed supports miui updates and I've been wondering how to get it to work? The info says i have to flash full miui rom with specific checkboxes ticked and then when the update releases, just update using miui update system.
What i dont understand is - my current miui is 9. and recently miui 10 has been released. From what i understand, I'd need to flash my current ROM again via PBRB and then install update? That leaves me with two questions: Does it mean I'd lose all my data flashing full rom on the first step? Or is there some kind of a workaround, or the full rom flashing actually doesnt delete the data, becasue of the checkboxes ticked?
Wiral said:
Hi,
I've noticed pitch black recovery that i have installed supports miui updates and I've been wondering how to get it to work? The info says i have to flash full miui rom with specific checkboxes ticked and then when the update releases, just update using miui update system.
What i dont understand is - my current miui is 9. and recently miui 10 has been released. From what i understand, I'd need to flash my current ROM again via PBRB and then install update? That leaves me with two questions: Does it mean I'd lose all my data flashing full rom on the first step? Or is there some kind of a workaround, or the full rom flashing actually doesnt delete the data, becasue of the checkboxes ticked?
Click to expand...
Click to collapse
It won't delete any data if you dirty flash, means don't wipe system and data partition.
Dirty flash should do with enabling future ota updates.
Hello,
Currently running Pixel experience with android 9 since October 2019. I've had GPS issues for a long time, with the phone not reaching a fix and I have tried to fix it without sucess by flashing magisk modules.
should I update to PE 10, or the official lineage OS to try and fix the problem? How should I procceed in this case (I have orangefox recovery)?
Also, I've read about firmware updates. How can I update mine, do I need to have a specific ROM?
Thank you
1.-You could try to resolve your GPS issues by flashing any rom you choose, I personaly haven't tried any PE because i don't like this much google apps preinstalled in my system but i have been using many roms like Havoc, POSP, StagOS, Syberia, RR and many more and I didn't have any problems with GPS at all. Right now im using latest StagOS (unofficial) and it works pretty well.
2.-If you already have orangefox recovery the flashing procedure is easy and quite the same for every ROM (usualy descibed in ROM's thread), but keep in mind that you might need to format data partition because of RN7 encryption issues so it's recommended to make backup of internal storage to a PC or SD Card.
3.-As you currently using android 9 it would be good to update your firmware to the latest stable one, there's xda thread about that(https://forum.xda-developers.com/redmi-note-7/development/firmware-xiaomi-redmi-note-7-t3925871)
cieciu89 said:
1.-You could try to resolve your GPS issues by flashing any rom you choose, I personaly haven't tried any PE because i don't like this much google apps preinstalled in my system but i have been using many roms like Havoc, POSP, StagOS, Syberia, RR and many more and I didn't have any problems with GPS at all. Right now im using latest StagOS (unofficial) and it works pretty well.
2.-If you already have orangefox recovery the flashing procedure is easy and quite the same for every ROM (usualy descibed in ROM's thread), but keep in mind that you might need to format data partition because of RN7 encryption issues so it's recommended to make backup of internal storage to a PC or SD Card.
3.-As you currently using android 9 it would be good to update your firmware to the latest stable one, there's xda thread about that(https://forum.xda-developers.com/redmi-note-7/development/firmware-xiaomi-redmi-note-7-t3925871)
Click to expand...
Click to collapse
Thank you a lot for your help! So the procedure should be pretty straightforward right? (I'm always afraid of bricking my phone lol).
Will take a look through the thread. Is the firmware installed before/after the rom? Does it matter if I have Android 9 or 10 before installing it, or can I just do it anytime?
It's recommended to flash firmware package before new ROM (some ROM's cannot even be flashed if the firmware is too old), yes the procedure is straightworward after you update your firmware - wipe: data,system, dalvik, cache and vendor then flash ROM package then gapps if they aren't present in the system you pick (and magisk package if you need root acces) and your done but you might encounter a bootloop and this means you need to format Data partition (not wipe) that is why you should backup all your files from internal memory before you begin with anything.
I'm too experiencing gps problem recently. Switching to Miui EU didn't help either. Have you tried modifying the gps.conf file? It's unstable and not perfect but the result is some what better than not having GPS at all. I've been using the modified gps.conf for 2 days so I can't be sure about anything, but I will post update in this thread.
You can google how you can replace your gps.conf (rooted or unrooted) with a premade file or you can also custom the file by yourself for it to work better within your region.
Sent from my Redmi Note 7 using Tapatalk
go to developer options and enable the option: force full GNNS measurements, restart smarphone and see if there is any improvement in the signal.
in my case it helped a lot.
Rom stock