Related
This does work to upgrade from 4.4.2 to 4.4.4 and there was no data/setting loss. I am running Verizon, developer phone, rooted, with xposed. Here are the directions I used:
1. disable Xposed - I just went to the app and uninstalled it
2. boot into bootloader/fastboot - connect your computer to the phone via USB. Then push the down volume and power at the same time. This will take you to the bootloader/fastboot
3. flash stock recovery (fastboot flash recovery yourfilename.img) - to do this (and to flash stock system) you need the motorola fastboot files and you will need to use the command prompt on the PC. for directions and download for the fastboot files check out this link - http://www.addictivetips.com/android/root-moto-x-install-cwm-recovery-complete-guide/ To actually download the stock recovery and stock system files you can download them here (look for 4.4.2 verizon - http://sbf.droid-developers.org/phone.php?device=0. I actually pasted the recovery.img/stock.img files into the windows fastboot folder and accessed CMD prompt from there to flash them. I flashed recovery then moved onto stock. I did not reboot until both were done.
4. flash stock system (fastboot flash system yourfilename.img)
5. reboot (stay in the CMD prompt and type - fastboot reboot)
6. update via OTA
7. reboot
You are now stock unrooted 4.4.4, so just re-apply root the same way you did the first time:
1. boot into bootloader/fastboot - you should be able to follow the directions from above to do this now
2. flash custom recovery - you should be able to follow the directions from above to do this now. Note that I tried CWM and it didnt work until I used TWRP. - download the latest version here and stick in the same fastboot folder you were using above - http://teamw.in/project/twrp2
3. boot to recovery - make sure you do this from the bootloader/fastboot screen. To do it, press down until you get to recovery then up to actually select it. I kept pressing power to select which doesnt actually select it.
4. flash SuperSU - this should be on your phone from the first time you rooted. If doing a new root you will need to get it first.
5. reboot
6. re-enable Xposed - i just reinstalled it and all of my settings were back
7. reboot
- BAM you are done!
I'm curious to see if this works the same for unlocked non developer edition Moto X's on VZW too
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
Multiple reports all over the forum say YES. (must flash stock recovery back, FIRST -- OR just use the FXZ and don't worry about having to flash stock recovery...)
Also, to the OP: questions belong in Q&A, not General. See the 2nd Sticky post at the top of the General forum....please post in the correct forums in the future...
I have a vzw DE
I took the 4.4.4 FXZ file from the other thread and just flashed it, no prep, didn't disable xposed.I was flashing in fastboot, not recovery, so its not checking for intact files. Then had to twrp/root and re-enable xposed.
But if you want to take the OTA then your procedure would be good.
Ryphez said:
I'm curious to see if this works the same for unlocked non developer edition Moto X's on VZW too
Click to expand...
Click to collapse
There is no difference whatsoever between an unlocked dev edition and any other unlocked X. The ONLY difference is the dev edition keeps its warranty when you unlock.
Whats the best twrp for root on 4.4.4
Mickoou said:
Whats the best twrp for root on 4.4.4
Click to expand...
Click to collapse
How about the latest version from the official source? Here: http://techerrata.com/browse/twrp2/ghost
It will root for you. Just flash w/fastboot, then "fastboot reboot-bootloader", then VOL DOWN to RECOVERY, and VOL UP to select it. When you go to exit, it will offer to install SuperSU Installer. Once booted, launch SuperSU Installer, and select Play Store method.
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
No, you should be the guinea pig for all of us.
I can confirm that this works. I did it. I did not lose any data. It took about 20 minutes total. I already had everything installed otherwise you are looking at about 45 minutes.
The only reason to flash stock system.img before taking an OTA is if you made so many changes to system files you can't remember them to undo them. i.e. you modified your system so much that flashing system.img is the fastest way back to stock so it passes the validation checks of the OTA.
I thought there is an Xposed disabler (in the xposed thread) that you can run rather than uninstalling?
That being said.. this information has been the same for EVERY OTA Update. You have to flash stock recovery for the OTA to install, and your system can't be modified too much or it will fail the validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
IF you are close enough to stock... you can also use the following... WITHOUT a PC... i.e. you haven't modified system too much, etc.
Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Install Rashr.
Use Rashr to to flash stock recovery (select other from storage, and select your stock recovery). When it completes, pick the option to reboot to stock recovery.
From stock recovery, install the update zip and reboot the phone.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
KidJoe said:
The only reason to flash stock system.img before taking an OTA is if you made so many changes to system files you can't remember them to undo them. i.e. you modified your system so much that flashing system.img is the fastest way back to stock so it passes the validation checks of the OTA.
I thought there is an Xposed disabler (in the xposed thread) that you can run rather than uninstalling?
That being said.. this information has been the same for EVERY OTA Update. You have to flash stock recovery for the OTA to install, and your system can't be modified too much or it will fail the validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
IF you are close enough to stock... you can also use the following... WITHOUT a PC... i.e. you haven't modified system too much, etc.
Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Install Rashr.
Use Rashr to to flash stock recovery (select other from storage, and select your stock recovery). When it completes, pick the option to reboot to stock recovery.
From stock recovery, install the update zip and reboot the phone.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
Click to expand...
Click to collapse
Thanks for the tip. I believe I did it the way I mentioned because last time gravity box didnt have a wifi tether available so I had to modify the system files. this time I didnt touch them.
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Schaweet said:
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
+1 :good:
Schaweet said:
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I'm getting an error while attempting to flash the system.img. I don't remember the exact wording but it was something like "data exceeds download buffer". I flashed the recovery.img without issue. I tried to take the OTA and it gets halfway through and craps out with the red exclamation triangle... Any ideas?
zoid_99 said:
I'm getting an error while attempting to flash the system.img. I don't remember the exact wording but it was something like "data exceeds download buffer". I flashed the recovery.img without issue. I tried to take the OTA and it gets halfway through and craps out with the red exclamation triangle... Any ideas?
Click to expand...
Click to collapse
Are you using mfastboot to flash system.img? You can't use regular fastboot. Just search for mfastboot.
Sent from my Dev Edition Moto X
Schaweet said:
Are you using mfastboot to flash system.img? You can't use regular fastboot. Just search for mfastboot.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Thank you Thank you.... That was it.
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
1.6 SU was the only issue I had, I got the latest and had no issue
http://download.chainfire.eu/supersu
KidJoe said:
[*]Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Click to expand...
Click to collapse
Where do I get the stock recovery.img file?
Thank you!
fede_arg said:
Where do I get the stock recovery.img file?
Thank you!
Click to expand...
Click to collapse
The OP tells you in the very first post...
I tried to flash many roms on my cell without any succes, so i wonder if anyone can tell me wich rom should i install via original recovery sideload, I got an xt1063 type MOFB9 ON TITAN_UMTS:4.4.4/kxb21.85-23/21
Please i know i can flash and downgrade many roms via fasboot,or custome recovery twrp or pholz, but i want to know, if in original, i got the latest , or what would be the next rom to flash acording to the system i have. thanks for the help.
abispac said:
I tried to flash many roms on my cell without any succes, so i wonder if anyone can tell me wich rom should i install via original recovery sideload, I got an xt1063 type MOFB9 ON TITAN_UMTS:4.4.4/kxb21.85-23/21
Please i know i can flash and downgrade many roms via fasboot,or custome recovery twrp or pholz, but i want to know, if in original, i got the latest , or what would be the next rom to flash acording to the system i have. thanks for the help.
Click to expand...
Click to collapse
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1ALL MOTO G firmware available (1st, 2nd and 3rd Gen) pick correct XT1063 in your case
reefuge said:
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1ALL MOTO G firmware available (1st, 2nd and 3rd Gen) pick correct XT1063 in your case
Click to expand...
Click to collapse
Thank you sir, but i see this roms end in xml, wich i think are for flashing via fasboot? if im wrong please correct me, im looking for the ota original to flash via original recovery.
abispac said:
Thank you sir, but i see this roms end in xml, wich i think are for flashing via fasboot? if im wrong please correct me, im looking for the ota original to flash via original recovery.
Click to expand...
Click to collapse
thats correct these are via ADB mfastboot (which ignores OTA fingerprint check) as flashes full firmware, not the ota.zip which is only a smaller (not full firmware) update
ota.zip is NOT full firmware, so will not fix a corrupted / altered or non stock firmware
but you say you've flashed many roms.... you need to be on correct rom and matching recovery and also un-rooted to flash a OTA.zip as it checks Recovery version and the build fingerprint inside /system folder of original stock rom. if any of these mismatch it will fail.
also (apologies if wrong) but dont you believe your phone to be corrupted or read only hence why you cant flash images?
reefuge said:
thats correct these are via ADB mfastboot (which ignores OTA fingerprint check) as flashes full firmware, not the ota.zip which is only a smaller (not full firmware) update
ota.zip is NOT full firmware, so will not fix a corrupted / altered or non stock firmware
but you say you've flashed many roms.... you need to be on correct rom and matching recovery and also un-rooted to flash a OTA.zip as it checks Recovery version and the build fingerprint inside /system folder of original stock rom. if any of these mismatch it will fail.
also (apologies if wrong) but dont you believe your phone to be corrupted or read only hence why you cant flash images?
Click to expand...
Click to collapse
Chanses are my phone its corrupted, i had the hope that a mayor ota, such a 5.0 (not5.0.2) would rewrite the phone and fix it, as the olny option i have not be able to tried was install an original ota or rom via recover sideload. I got recovery KXB21.85-23. Are there any fixes for read only out there? because i have found non....
Thanks for the help thought.
abispac said:
Chanses are my phone its corrupted, i had the hope that a mayor ota, such a 5.0 (not5.0.2) would rewrite the phone and fix it, as the olny option i have not be able to tried was install an original ota or rom via recover sideload. I got recovery KXB21.85-23. Are there any fixes for read only out there? because i have found non....
Thanks for the help thought.
Click to expand...
Click to collapse
what error do you get via ADB when you flash?
can you remember what was the original firmware on phone as several for xt1063
or if boots the system version in about phone
reefuge said:
what error do you get via ADB when you flash?
can you remember what was the original firmware on phone as several for xt1063
or if boots the system version in about phone
Click to expand...
Click to collapse
Phone wont boot, its gets to the point where a blue m apears the goes to a blank screen, when flahing a rom via fasboot, all seems to get right but after restart is like nothing happened, i go back to the same state, same thing happens with twrp or philz, if you want to help, we can continue here but your more then wellcome to read this (nevermind i see you allready did)
So let me make a backup of twrp and see if i can post results, thanks allot, iveen waiting to fix this for so many days now.
A bit of background, i consider myself an advance user, someone that can google problems and fix stuff with it, ivee flashed alot of cellphones in the past ,many xt1064 and other models, just like everybody ealse, easy and no problems, but this one i just cant figure out. Seems like its on read only mode or freezed as a deepfreezed computer, dont mater how many roms i flash and the way i do, everything comes back to the same state, even if i reforma partitions, eeven if i delete pictures or folders, they come back once i reboot.
Its going to take 5hrs to upload my backup
abispac said:
Phone wont boot, its gets to the point where a blue m apears the goes to a blank screen, when flahing a rom via fasboot, all seems to get right but after restart is like nothing happened, i go back to the same state, same thing happens with twrp or philz, if you want to help, we can continue here but your more then wellcome to read this (nevermind i see you allready did)
So let me make a backup of twrp and see if i can post results, thanks allot, iveen waiting to fix this for so many days now.
A bit of background, i consider myself an advance user, someone that can google problems and fix stuff with it, ivee flashed alot of cellphones in the past ,many xt1064 and other models, just like everybody ealse, easy and no problems, but this one i just cant figure out. Seems like its on read only mode or freezed as a deepfreezed computer, dont mater how many roms i flash and the way i do, everything comes back to the same state, even if i reforma partitions, eeven if i delete pictures or folders, they come back once i reboot.
Click to expand...
Click to collapse
ok ii'm thinking corrupted partitions too.... but if you are willing to try i've made a xt1063 easy installer script for you to try now normally i work on xt1068 and would test on my xt1068 - so have NO xt1063 its UNTESTED - use at own risk.....
just stock firmware / drivers / adb and mfastboot ( same as my xt1068 script) I see no reason it should not be compatible.
download to pc / unzip to folder / read instruction inside
https://mega.co.nz/#!Tok2DJ6T!ggMoQDfAzuA7cmQQjbGCbXolWZTnx_567vG02CiURVsxt1063 4.4.4 easy installer
I repeat it YOUR choice - if it works- great - if runs ok but rom remains same would suggest somethings corrupt - if it doesnt work at all back to square 1....
now im presuming your boot loader is unlocked, as will fail if locked or relocked - if you use and get error please report what they are, i would have done 5.0.2 but its only 50% downloaded with a 1 hr+ to still go, estimate 2 hrs from time of this post until I can post a link
im uploading the backup, in the mean time i dont know if this is of any use ,its the recovery log zipped...
abispac said:
im uploading the backup, in the mean time i dont know if this is of any use ,its the recovery log zipped...
Click to expand...
Click to collapse
just to let you know TWRP is now 2.5.8.0 fixes some bugs cause older versions know to break permissions in Lollipop!!
https://mega.co.nz/#!Dx03wTbD!3sDFubGomhegQqdoGzNb1RWnQwApzyaTlVq69uX1TqkFlash-able version (unzip to pc and flash from there) 2.5.8.0
https://mega.co.nz/#!n5cUQCAY!uf66vEcQlmtu6VZMLPxksEFMEioZUFpystzTP6kwU4I Temporary boot version (no flash) 2.5.8.0.
will look but cant promise
I tried your easy install tool, brand new drivers, diferent usb port, all went smooth but after restart, im at the same situation. Funny thing, and ivee done this multiple times, after reflashing a new rom, most of them never give errors, then after nothing happens , i flash twrp and boot it, and all the files (the original ones , not the just flashed ones) are there intact, even pictures and music.
abispac said:
I tried your easy install tool, brand new drivers, diferent usb port, all went smooth but after restart, im at the same situation. Funny thing, and ivee done this multiple times, after reflashing a new rom, most of them never give errors, then after nothing happens , i flash twrp and boot it, and all the files (the original ones , not the just flashed ones) are there intact, even pictures and music.
Click to expand...
Click to collapse
ok have you tried mfastboot erase userdata and mfastboot erase cache? from a command window?
i.m interested in the I flash twrp and boot..... does this mean you are able to replace recovery with a custom recovery ON phone
rather than temporary booting into it?
reefuge said:
ok have you tried mfastboot erase userdata and mfastboot erase cache? from a command window?
i.m interested in the I flash twrp and boot..... does this mean you are able to replace recovery with a custom recovery ON phone
rather than temporary booting into it?
Click to expand...
Click to collapse
Yeah i tried those erase commands many many times and same result, i cant replace recovery at all, only boot of it, so when i do " mfastbooot flash recovery twrprecovery.img " then try to boot of recovery, i boot into factory recovery not, twrp, but if i do, "mfasboot boot twrprecovery.img" i can see the recovery img gets flashed and the phone boots of twrp. Weird behavior. So when i notice that i tried to flash a rom with mfastboot, and at the end i gave the command mfasboot boot recovery.img (the original rom recovery) then it gets flashed, and phone reboots, but i gets stuck at the motorola logo. This phone its playing hard to get....
heres, my backup https://mega.co.nz/#!md0AwbLR!uWe9PLklIugOziPLV6O_plbU-Zz9EXbqRvUVpYxECk0 hope you can find something.
Im going to take this phone to a shop to see if they can fix it as i have lost all hope, thanks refuuge for your help.
Hi, everyone this is my first post.
Though I am not new to rooting, but earlier i used to do one click root..so unrooting was also that damn easy.
Recently i rooted my moto x 2nd gen xt1092 by unlocking bootloader and after flashing TWRP and later using SuperSu.
But here is the catch I didn't take nandroid backup before rooting.
So my question is
1 If I take backup now , will this backup be a rooted backup , means that if in future I flash this backup my phone will be directly boot in rooted mode..?
2 If I unroot using supersu are there chances I may stuck in bootloop?
3 now as I alreday have Twrp flashed how can I get to my original OS I once had? 9(system recovery image)
Plz let my doubts get cleared.
thanks in advance
saumyadip said:
Hi, everyone this is my first post.
Though I am not new to rooting, but earlier i used to do one click root..so unrooting was also that damn easy.
Recently i rooted my moto x 2nd gen xt1092 by unlocking bootloader and after flashing TWRP and later using SuperSu.
But here is the catch I didn't take nandroid backup before rooting.
So my question is
1 If I take backup now , will this backup be a rooted backup , means that if in future I flash this backup my phone will be directly boot in rooted mode..?
2 If I unroot using supersu are there chances I may stuck in bootloop?
3 now as I alreday have Twrp flashed how can I get to my original OS I once had? 9(system recovery image)
Plz let my doubts get cleared.
thanks in advance
Click to expand...
Click to collapse
1. yes, you can do a full backup of system, data, recovery, boot, etc (default configuration of backup) and when you do a restore you have the same root system.
2, sometimes, you have a 50% of possible failure, the best option is flash the stock system files and after do a ota update or similar (never do a downgrade, can kill your phone(hardbrick))
3. Via bootloader (down volume button when you turn on the phone)
Write or copy this lines on bootloader mode (in the same folder where you have execute the command for your unlock code for the unlock of boot loader)
fastboot flash recovery recovery.img
fastboot reboot
The recovery is on image of StockRom.
Sorry my English, I`m Chilean.
cyker31 said:
1. yes, you can do a full backup of system, data, recovery, boot, etc (default configuration of backup) and when you do a restore you have the same root system.
2, sometimes, you have a 50% of possible failure, the best option is flash the stock system files and after do a ota update or similar (never do a downgrade, can kill your phone(hardbrick))
3. Via bootloader (down volume button when you turn on the phone)
Write or copy this lines on bootloader mode (in the same folder where you have execute the command for your unlock code for the unlock of boot loader)
fastboot flash recovery recovery.img
fastboot reboot
The recovery is on image of StockRom.
Sorry my English, I`m Chilean.
Click to expand...
Click to collapse
Thanks cyke31.
My two doubts are absolutely clear.
I have a doubt regarding the 3 point.
where I will find that recovey.img file?
And after flashing that recovery.img file will I get back to my stock rom, that I had before TWRP was installed ?
Can I take OTA updates?
Will TWRP get uninstalled ?
your english is pretty good..
I am Indian ....so don't worry . I'm not grammar NAZI..
saumyadip said:
Thanks cyke31.
My two doubts are absolutely clear.
I have a doubt regarding the 3 point.
where I will find that recovey.img file?
And after flashing that recovery.img file will I get back to my stock rom, that I had before TWRP was installed ?
Can I take OTA updates?
Will TWRP get uninstalled ?
your english is pretty good..
I am Indian ....so don't worry . I'm not grammar NAZI..
Click to expand...
Click to collapse
I recommend downloading the stock rom and do a clean install , because any change you've made in system, will generate bootloop...
Here the links to the Rom (you must download The xt1092 version)
Firmwares 4.4.4 hasta 5.0.X: https://mega.co.nz/#F!TkIwRTjR!m7W1V35qfLBiiUargAx1vg
Firmwares 5.1 y 6.0: https://mega.co.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
And them install via guides on xda.
cyker31 said:
I recommend downloading the stock rom and do a clean install , because any change you've made in system, will generate bootloop...
Here the links to the Rom (you must download The xt1092 version)
Firmwares 4.4.4 hasta 5.0.X: https://mega.co.nz/#F!TkIwRTjR!m7W1V35qfLBiiUargAx1vg
Firmwares 5.1 y 6.0: https://mega.co.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
And them install via guides on xda.
Click to expand...
Click to collapse
so its better to flash system files than flashing recovery.img
though I'm in no mood to unroot my device. just wanted to know the consequences. I'll do normal backup of my current rooted rom. If in case anything happens I'll flash stock system files from motorola website.
Thanks for the info.
Xposed is the reason I rooted my device. Heard that is better to take nandroid backup before installing Xposed.
saumyadip said:
so its better to flash system files than flashing recovery.img
though I'm in no mood to unroot my device. just wanted to know the consequences. I'll do normal backup of my current rooted rom. If in case anything happens I'll flash stock system files from motorola website.
Thanks for the info.
Xposed is the reason I rooted my device. Heard that is better to take nandroid backup before installing Xposed.
Click to expand...
Click to collapse
Yes, but xposed is a thing, and the modules are totally different thing,Xposed by itself does not cause any problems...
yeah know that but...wanted to be sure..... as there is no service center in my state
Hello,
Thanks for taking the time to look at this. I ran into a bootloop issue after updating my nexus 6 to a higher version of android. After I flashed the new version everything worked just fine but I kept getting the error message "Google play services has stopped" so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Thanks.
Wipe the phone, connect the N6 to your PC, and using ADB flash a stock ROM. Where the components are mismatched, flashing a stock ROM will resolve that issue and probably all your others. You will however need to flash your recovery and then your custom ROM - if you use one - as well as your root solution. Finally, whatever you do from now on, don't use Flashfire for the baseband.
irontaco1 said:
... so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Click to expand...
Click to collapse
Since I "routinely" flash modem zips through FF, I'm wondering if what you did was try to extract the modem img from the full software update? That is not a direction I would go in [emoji4]
There are modem flashable zips for the N6 that can be flashed through FF.
I also think the issue with accessing your back up is due to the user data partition being encrypted. What version of TWRP are you using? If not the newest (as of this writing 3.1.1-0), then that can also give you trouble.
irontaco1 said:
Hello,
Thanks for taking the time to look at this. I ran into a bootloop issue after updating my nexus 6 to a higher version of android. After I flashed the new version everything worked just fine but I kept getting the error message "Google play services has stopped" so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Thanks.
Click to expand...
Click to collapse
Read this for information on how to bypass the password that your backup is asking for https://www.google.com/amp/s/www.ho...fter-restoring-from-twrp-android-backups/amp/
Strephon Alkhalikoi said:
Wipe the phone, connect the N6 to your PC, and using ADB flash a stock ROM. Where the components are mismatched, flashing a stock ROM will resolve that issue and probably all your others. You will however need to flash your recovery and then your custom ROM - if you use one - as well as your root solution. Finally, whatever you do from now on, don't use Flashfire for the baseband.
Click to expand...
Click to collapse
Hey thanks for the help phone is running just fine now. I grabbed the factory image from the Google dev page and flashed it the hard way. For some reason ADB wouldn't mount /system after it was finished so I used fastboot to flash system, boot, radio, etc. Guess I won't use Flashfire for baseband anymore :laugh:
ktmom said:
Since I "routinely" flash modem zips through FF, I'm wondering if what you did was try to extract the modem img from the full software update? That is not a direction I would go in [emoji4]
There are modem flashable zips for the N6 that can be flashed through FF.
I also think the issue with accessing your back up is due to the user data partition being encrypted. What version of TWRP are you using? If not the newest (as of this writing 3.1.1-0), then that can also give you trouble.
Click to expand...
Click to collapse
Phone is working fine now. The files were encrypted because the stock kernel I was using was obviously non-permissive so it automatically encrypted my files upon reboot before it bootlooped. Really appreciate the help though.
H87220a Flashable ROM for the T-Mobile LG G6
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP v3.2.1-0, 11g ROM
Based On: LG Stock ROM
Click to expand...
Click to collapse
This ROM based on H87220xxxx.kdz then extracted and repacked with autoprime's zip based on this thread.
Also, thanks for runningnak3d for TWRP install method. This ROM is ARB01 which is safe if you want revert to 11g.
Installation :
Modullar Installation
You should install at least bootloader, modem, and system in order to boot properly.
Install xxxOreo.zip using TWRP don't reboot
Press back button and Install Magisk (It's mandatory if you want root and twrp retained)
DONE and Reboot
[*]In most case, you'll lost your /data due to data encryption. so backup first
[*]This build's ONLY for T-Mobile US LG G6
[*]If you decided to downgrade, make it sure that firmware is ARB01 (11g or later)
Download :
As requested by many people I've uploaded new update within 4 modules (Bootloader, Laf, Modem, and System).
You can download here: H87220g (latest)
LGH87220F
LGH87220D
LGH87220A
Recommended TWRP/Orangefox Recovery
my G6 seems broken, it has no display but it still ringing when I call it. probably LCD issue. Basically, I can't test any future update with this phone. I've planned to buy v30 soon and try to repair my g6 by myself. Any info or some suggestions will be appreciated
Have a nice day,
OK -- So I am going to install that later today...but just to be clear (and hopefully this helps others)...if you have been flashing other ROM, you should have...
1) H870 TWRP in laf, accessible for emergencies via holding up button and plugging phone into computer.
2) H872 Unofficial TWRP in recovery...
So, to flash this, using H872 recovery/TWRP:
1) TWRP backup whatever you want to keep.
2) Wipe all normal stuff
3) Flash this and magisk, assuming you want to root anyway.
4) Using TWRP File manager, delete /system/recovery_rom_boot.p so that if something goes wrong, you don't have to reflash H872 TWRP into recovery using laf.
Boot, and you should have the stock 8.x rooted?
In my case, I also a going to try and install stock GApps to replace LG/TMobile stuff...I'll post about my success on that later...
MW
MetroWestMA said:
OK -- So I am going to install that later today...but just to be clear (and hopefully this helps others)...if you have been flashing other ROM, you should have...
1) H870 TWRP in laf, accessible for emergencies via holding up button and plugging phone into computer.
2) H872 Unofficial TWRP in recovery...
Click to expand...
Click to collapse
You'll get download mode back after flashing this zip anyway (stock laf). in case something bad happens, you should not worry much. though, i've never use custom rom in this phone before. so, extra precaution will be good for you.:good:
immns said:
You'll get download mode back after flashing this zip anyway (stock laf). in case something bad happens, you should not worry much. though, i've never use custom rom in this phone before. so, extra precaution will be good for you.:good:
Click to expand...
Click to collapse
Which is the correct way to do it in my opinion. Once you TWRP installed in Recovery, having it stay on LAF is dangerous as far I'm concerned. In theory TWRP should be able to keep you from needing to ever restore back to stock, but it has been known to fail sometimes. Leaving with no way of using LG UP or any other flasher outside of sending it into LG (unless firehose files get leaked).
NighthawkXL said:
Which is the correct way to do it in my opinion. Once you TWRP installed in Recovery, having it stay on LAF is dangerous as far I'm concerned. In theory TWRP should be able to keep you from needing to ever restore back to stock, but it has been known to fail sometimes. Leaving with no way of using LG UP or any other flasher outside of sending it into LG (unless firehose files get leaked).
Click to expand...
Click to collapse
yep, flashing back original laf will save you in the future mistakes.
By "Stock" do you mean LG's bloatware stuffed "stock" or do you mean "Vanilla Android" stock?
MetroWestMA said:
OK -- So I am going to install that later today...but just to be clear (and hopefully this helps others)...if you have been flashing other ROM, you should have...
1) H870 TWRP in laf, accessible for emergencies via holding up button and plugging phone into computer.
2) H872 Unofficial TWRP in recovery...
So, to flash this, using H872 recovery/TWRP:
1) TWRP backup whatever you want to keep.
2) Wipe all normal stuff
3) Flash this and magisk, assuming you want to root anyway.
4) Using TWRP File manager, delete /system/recovery_rom_boot.p so that if something goes wrong, you don't have to reflash H872 TWRP into recovery using laf.
Boot, and you should have the stock 8.x rooted?
In my case, I also a going to try and install stock GApps to replace LG/TMobile stuff...I'll post about my success on that later...
MW
Click to expand...
Click to collapse
BTW -- I did this method, got laf back to what it should be, rooted the H872 Oreo, installed GApps, and have a pretty good setup with Volte/WiFI calling, Goodle Dialer and Messages (with web message support), stock camera, etc -- kinda best of all worlds.
The only issue, as noted in another thread, is that TWRP can no longer mount data -- meaning you gotta jump through some hoops to back it up...so hopefully this get fixed.
For those that are not aware, with TWRP still in recovery, you can boot to this following the factory reset options for the phone, but after answer to confirm "Yes" twice, you will boot into recover TWRP, so you can always get back there without a laptop and / or fastboot. If I recall, the key sequence is hold down button, hold power until logo appears, then turn power on and off until factory reset appears...
But TWRP needs to be fixed to access that data partition -- no idea what that is all about.
So twrp rebooted even though I clicked cancel on reboot, magisk not installed. Is there anyway back? I'm totally fine on stock btw if that's the case.
GoofyPanda said:
So twrp rebooted even though I clicked cancel on reboot, magisk not installed. Is there anyway back? I'm totally fine on stock btw if that's the case.
Click to expand...
Click to collapse
Try to combination buttons for reset, it'll brings you to TWRP again, and install magisk after that. Hope twrp still remains in recovery partition as sometimes they'll be replaced by bootloader. If it doesn't work, you should be able to use LGUP to flash 11g kdz, and try flashing twrp again.
MetroWestMA said:
The only issue, as noted in another thread, is that TWRP can no longer mount data -- meaning you gotta jump through some hoops to back it up...so hopefully this get fixed.
Click to expand...
Click to collapse
I believe that's possible, all you need's the right dm-verity disabler that works with this phone. In theory, just format (not wipe) your data partition, flash rom, flash dm-verity disabler, and then reboot. Data partition is encrypted by bootloader, I've checked twrp's fstab and all point to the right direction. But still, we've to try this before knowing what's actually possible or not. For now, I utilize LG Mobile Switch to backup my data and it's totally fine.
UPDATE: It doesn't work, dm-verity patches actually only patch boot.img while this phone has aboot, tz, and a lot elf programer
immns said:
Try to combination buttons for reset, it'll brings you to TWRP again, and install magisk after that. Hope twrp still remains in recovery partition as sometimes they'll be replaced by bootloader. If it doesn't work, you should be able to use LGUP to flash 11g kdz, and try flashing twrp again.
Click to expand...
Click to collapse
Seems that it is back to stock recovery also, I am going to try flashing the 11g kids later
GoofyPanda said:
Seems that it is back to stock recovery also, I am going to try flashing the 11g kids later
Click to expand...
Click to collapse
I doubt it is...because mine didn't and there was no /system/recovery_rom_boot.p to delete.
you can try installing a program like Titanium Backup that has the option to reboot into recovery.
Did you get it to the menu asking to factory reset -- if you got that and answered yes both times and did not get into recovery, then it is gone...
Kdz h827bk is same as h872?
AdrianNeo said:
Kdz h827bk is same as h872?
Click to expand...
Click to collapse
do you mean h872bk? The answer is yes, this is from H872BK kdz
immns said:
do you mean h872bk? The answer is yes, this is from H872BK kdz
Click to expand...
Click to collapse
mine is h872, but lg firmware only has the h872bk and h872tn, i do not know which down.
AdrianNeo said:
mine is h872, but lg firmware only has the h872bk and h872tn, i do not know which down.
Click to expand...
Click to collapse
if your phone is from T-Mobile, it's b872bk. please check ota update. if you got oreo update then you're in the right path. but if not, then it's more likely that your phone is the 872tn one.
I'm assuming the 2 letters at the end signify the color of the devices (BK = Black and TN = Titanium/Silver). Even though the devices are the same, perhaps there are minute differences in each build? I flashed the 20a zip that was provided by OP, but it changed my splash screen to say G6 ThinQ? The G6 I have is T-Mobile branded Titanium color, but I definitely had the devices before the ThinQ moniker became a thing. I'm going to download the KDZ branded for my 872TN and see what happens when I flash with LGUP.
The G6 ThinQ splash screen came with the oreo update. I think too that bk=black and tn=titanium no diff at the builds.
Your zip save my phone
Keep it up bro ..
Thanks
So I should be able to flash this through twrp like any other zip?
Y'all were talking about deleting deleting things so I wanted to make sure before I did anything.
I'm in agreement with fixing the laf after getting root, and this way looks like it would simplify matters if you got stuck with an issue and didn't want to or didn't have access to a pc.
Thanks