Database Users

Cannot flash system.img, df shows no system partition

Hi everybody!! I have a BIG issue: my nexus 4 is unlocked, with the CWM recovery and CyanogenMod 10.1 installed. Due to some technical problems, I decided to flash the factory rom again (following this guide http://forum.xda-developers.com/showthread.php?t=2010312) but I can't do it!! Indeed when I try to flash the factory rom the prompt says
file:could not allocate 544035848 bytes
error:cannot load system.img :not enough space
And when i checked the system capacity the result is that my system partition doesn't exist (as you can see on the pic attached)!
I wish to send my phone back to google with the RMA (it was delivered 7 days ago) but I'm not sure that the warranty is still valid (what do you think about that?). Indeed there is no OS now, and everything is unlocked.
Anybody could help me?
Thanks a lot!!

StefanoRedi said:
Hi everybody!! I have a BIG issue: my nexus 4 is unlocked, with the CWM recovery and CyanogenMod 10.1 installed. Due to some technical problems, I decided to flash the factory rom again (following this guide http://forum.xda-developers.com/showthread.php?t=2010312) but I can't do it!! Indeed when I try to flash the factory rom the prompt says
file:could not allocate 544035848 bytes
error:cannot load system.img :not enough space
And when i checked the system capacity the result is that my system partition doesn't exist (as you can see on the pic attached)!
I wish to send my phone back to google with the RMA (it was delivered 7 days ago) but I'm not sure that the warranty is still valid (what do you think about that?). Indeed there is no OS now, and everything is unlocked.
Anybody could help me?
Thanks a lot!!
Click to expand...
Click to collapse
use the fastboot commands to erase system, boot, and data. then use flashboot to flash bootloader, then stock recovery, then stock system.

EvoXOhio said:
use the fastboot commands to erase system, boot, and data. then use flashboot to flash bootloader, then stock recovery, then stock system.
Click to expand...
Click to collapse
Thanks!! Just a couple of questions: 1. the prompt commands are "fastboot erase system" "fastboot erase boot" and "fastboot erase data", right? 2. Have I to reboot the system between every erase and every flash?

StefanoRedi said:
Thanks!! Just a couple of questions: 1. the prompt commands are "fastboot erase system" "fastboot erase boot" and "fastboot erase data", right? 2. Have I to reboot the system between every erase and every flash?
Click to expand...
Click to collapse
That sounds right but Fiona search to be safe. No reboots needed.

StefanoRedi said:
Thanks!! Just a couple of questions: 1. the prompt commands are "fastboot erase system" "fastboot erase boot" and "fastboot erase data", right? 2. Have I to reboot the system between every erase and every flash?
Click to expand...
Click to collapse
I tryed to do it without results. I attach the screen.
Have you some other advises? I really don't know what i can do it with my phone. If i send it back to google, do you think that they will check if my phone is locked/unlocked, with/without os, ecc? Because I'm afraid to have wasted my money!

Have you tried booting into recovery and wiping everything before flashing system? Also you're sure you have the right system.img? Maybe re-download the files from google and try again?
---------- Post added at 09:23 AM ---------- Previous post was at 09:22 AM ----------
also, do you have any nandroids or downloaded ROMs on the phone? If so, you could try flashing CWM, and then booting into it and restoring the nandroid or installing a ROM.

R: Cannot flash system.img, df shows no system partition
We tried wiping everything trough fast boot, he does not have any nandroid backup and I think he tried to flash another ROM (cm) with no luck.
We downloaded the right images, we tried both 4.2.1 and JOP40D from the Google site and from the mirror that we found in some thread here on xda.
(I'm his friend and I was helping him via Skype, that's why I know these informations)
I think now we'll try to flash cwm and wipe everything trough it and install a stock ROM or a custom one.
Ty for the help.
Sent from my Nexus 4

squalluca said:
We tried wiping everything trough fast boot, he does not have any nandroid backup and I think he tried to flash another ROM (cm) with no luck.
We downloaded the right images, we tried both 4.2.1 and JOP40D from the Google site and from the mirror that we found in some thread here on xda.
(I'm his friend and I was helping him via Skype, that's why I know these informations)
I think now we'll try to flash cwm and wipe everything trough it and install a stock ROM or a custom one.
Ty for the help.
Sent from my Nexus 4
Click to expand...
Click to collapse
It really sounds like someone made a mistake and ran the wrong command and actually remove the /system partition. Not erased or formatted, but actually removed the mount point. I'm sure there is a way to recreate it, but I have no idea how.

R: Cannot flash system.img, df shows no system partition
That's what I think too... this error appeared before we tried any wipe/erase command trough fastboot... hope someone can help us in recrate the mount point for the system partition...
Sent from my Nexus 4

EvoXOhio said:
It really sounds like someone made a mistake and ran the wrong command and actually remove the /system partition. Not erased or formatted, but actually removed the mount point. I'm sure there is a way to recreate it, but I have no idea how.
Click to expand...
Click to collapse
Thanks guys! I really hope that someone knows how to recreate it and, if it's possibile, very soon, because the RMA expiration day is coming!!

This is generally to be avoided, but I think this may actually be a last resort situation. Download the full factory image extract down a few levels until you have flash-all.bat extracted, at that point you'll also see the radio, bootloader, an image zip, and some linux scripts. Make sure you've actually extracted them and that you aren't just looking in the zip. Run flash-all.bat Don't touch anything until it's done, if you disrupt the write to bootloader or possibly radio, you brick.
By the way, the factory image is here and you may need to use 7zip to extract it. 7zip will have shell integration, so just right click what you want, drop down to 7zip and extract to.
Also, you may be able to accomplish the same thing with:
Code:
fastboot -w update image-occam-jop40c.zip
so maybe try that first.

USSENTERNCC1701E said:
This is generally to be avoided, but I think this may actually be a last resort situation. Download the full factory image extract down a few levels until you have flash-all.bat extracted, at that point you'll also see the radio, bootloader, an image zip, and some linux scripts. Make sure you've actually extracted them and that you aren't just looking in the zip. Run flash-all.bat Don't touch anything until it's done, if you disrupt the write to bootloader or possibly radio, you brick.
By the way, the factory image is here and you may need to use 7zip to extract it. 7zip will have shell integration, so just right click what you want, drop down to 7zip and extract to.
Also, you may be able to accomplish the same thing with:
Code:
fastboot -w update image-occam-jop40c.zip
so maybe try that first.
Click to expand...
Click to collapse
Fine, I will try when I come back home. Just a question: what do you think about the warranty? Do you think that google will check if the phone is unlocked and without os? It is better for me risk with the last suggested process and (maybe) brick the phone or send it back as it is now? It's because I'm just a beginner with mod, scripts, prompts, ecc..sorry!

StefanoRedi said:
Fine, I will try when I come back home. Just a question: what do you think about the warranty? Do you think that google will check if the phone is unlocked and without os? It is better for me risk with the last suggested process and (maybe) brick the phone or send it back as it is now? It's because I'm just a beginner with mod, scripts, prompts, ecc..sorry!
Click to expand...
Click to collapse
The phone was damaged from user error. It is unethical and probably illegal to RMA it. Try to fix it yourself, and if you can't, man up and buy a new phone. RMAs are for faulty products, not products ruined by an inexperienced user doing something wrong.

EvoXOhio said:
The phone was damaged from user error. It is unethical and probably illegal to RMA it. Try to fix it yourself, and if you can't, man up and buy a new phone. RMAs are for faulty products, not products ruined by an inexperienced user doing something wrong.
Click to expand...
Click to collapse
You are completely right. I wrote that just because I messed up the phone (following guides, using toolkit, using cmd in a proper way) trying to fix it (from the first day it was impossible to call due to microphone/speaker software problem). And sometimes, while a was doing the same stuff that everybody do with good results, the phone didn't do what it was supposed to do. Consequently I wanted to RMA it because i think it's my fault (I know it and I admit it) but not completely. I really don't want to cheat anyone.

Well, I fixed it. I don't know the reason but the day after everything was fine (maybe it's because I erased everything from CWM; i wiped everything and then i wen on Mount and I erased everything). Btw, the day after I reflashed everything from prompt with the phone in fastboot and i flashed also system (the partition was "avaible" again); the .img flashed was the factory rom 4.2.0. Then I reboot it but the problem with microphone/speacker wasn't fixed; i updated to 4.2.1 and it still didn't work. Today I will call google to RMA it because now (just now) the phone is not working properly but not due to my errors. Thanks to everybody!!!! :laugh:

StefanoRedi said:
Well, I fixed it. I don't know the reason but the day after everything was fine (maybe it's because I erased everything from CWM; i wiped everything and then i wen on Mount and I erased everything). Btw, the day after I reflashed everything from prompt with the phone in fastboot and i flashed also system (the partition was "avaible" again); the .img flashed was the factory rom 4.2.0. Then I reboot it but the problem with microphone/speacker wasn't fixed; i updated to 4.2.1 and it still didn't work. Today I will call google to RMA it because now (just now) the phone is not working properly but not due to my errors. Thanks to everybody!!!! :laugh:
Click to expand...
Click to collapse
Make sure flash stock recovery and relock the device before sending it in.

EvoXOhio said:
Make sure flash stock recovery and relock the device before sending it in.
Click to expand...
Click to collapse
Of course! In theory it will not be a problem if there is the CWM recovery and if the phone it's unlucked (at least, I read that for Google and LG is not a problem), but I flashed the stock recovery and then I lucked the phone again. Thanks for your advises.

system.img cannot load, not enough space error
StefanoRedi said:
Well, I fixed it. I don't know the reason but the day after everything was fine (maybe it's because I erased everything from CWM; i wiped everything and then i wen on Mount and I erased everything). Btw, the day after I reflashed everything from prompt with the phone in fastboot and i flashed also system (the partition was "avaible" again); the .img flashed was the factory rom 4.2.0. Then I reboot it but the problem with microphone/speacker wasn't fixed; i updated to 4.2.1 and it still didn't work. Today I will call google to RMA it because now (just now) the phone is not working properly but not due to my errors. Thanks to everybody!!!! :laugh:
Click to expand...
Click to collapse
hey can anyone help me i have this error when i flash Stock 5.0.1 Lollipop, Kitkat flashing is working!

(What if?)how do you recover from a boot loop on nexus4?

Hello everybody! I have a nexus 4 since a couple of months, and I had a Samsung galaxy s before. With that phone if you got stuck on a boot loop and couldn't access recovery, you used Odin to save you..what if it happens on nexus 4? Flash original image with a tool? Or there is some recovery file I can flash? Or what?
Thanks!
Sent from my Nexus 4 using xda app-developers app

It's highly unlikely that you won't be able to boot into the recovery anymore on a nexus device as the recovery is pretty much "flash once, forget forever".
Meaning, you normally don't mess with the recovery partition.
If you, for whatever reason, really can't access the recovery anymore, you can flash a new one through the bootloader using fastboot.
fastboot flash recovery recovery.img
Should be the command to do so. Just check the tutorials around here.

Nuu~ said:
It's highly unlikely that you won't be able to boot into the recovery anymore on a nexus device as the recovery is pretty much "flash once, forget forever".
Meaning, you normally don't mess with the recovery partition.
If you, for whatever reason, really can't access the recovery anymore, you can flash a new one through the bootloader using fastboot.
fastboot flash recovery recovery.img
Should be the command to do so. Just check the tutorials around here.
Click to expand...
Click to collapse
What he said, and also should be noted that if you do backups of your roms, if you ever upgraded the recovery (say TWRP) you may wish to re-do a backup after you upgrade with the recovery option checked (or don't use it at all) since I've run into a situation once where I backed up my original stock on 2.4.4.0, and when I restored it, it downgraded my 2.5.0.0 to that, didn't cause problems just some options went bye-bye until I reflashed the recovery from fastboot (and just made sure to make a flashable-zip of just that recovery just in case).
As long as you can get to the bootloader on an N4 you can do just about anything to bring your device back to life, even if it's something like erasing the userdata, then formating /data in the new recovery because *cough*me*cough* stupidly flashed a galaxy nexus recovery from goomanager.
PS: Holding down the power for 10 seconds or more is pretty much the universal kill switch, from there should be able to bring up bootloader just fine.

kbeezie said:
What he said, and also should be noted that if you do backups of your roms, if you ever upgraded the recovery (say TWRP) you may wish to re-do a backup after you upgrade with the recovery option checked (or don't use it at all) since I've run into a situation once where I backed up my original stock on 2.4.4.0, and when I restored it, it downgraded my 2.5.0.0 to that, didn't cause problems just some options went bye-bye until I reflashed the recovery from fastboot (and just made sure to make a flashable-zip of just that recovery just in case).
As long as you can get to the bootloader on an N4 you can do just about anything to bring your device back to life, even if it's something like erasing the userdata, then formating /data in the new recovery because *cough*me*cough* stupidly flashed a galaxy nexus recovery from goomanager.
PS: Holding down the power for 10 seconds or more is pretty much the universal kill switch, from there should be able to bring up bootloader just fine.
Click to expand...
Click to collapse
Try booting in safe mode https://support.google.com/nexus/4/answer/2852139?hl=nl. 3rd party apps will not boot in that mode.

gee2012 said:
Try booting in safe mode https://support.google.com/nexus/4/answer/2852139?hl=nl. 3rd party apps will not boot in that mode.
Click to expand...
Click to collapse
Not sure why you linked that or how it even pertained to me (especially since it's been long since resolved and was using as an example). Also those tips do nothing if you couldn't get past the boot splash animation to begin with.

kbeezie said:
Not sure why you linked that or how it even pertained to me (especially since it's been long since resolved and was using as an example). Also those tips do nothing if you couldn't get past the boot splash animation to begin with.
Click to expand...
Click to collapse
It got me out of a bootloop mate, so if you speak for yourself that`s oke but that doesn`t mean it couldn`t work for others

gee2012 said:
It got me out of a bootloop mate, so if you speak for yourself that`s oke but that doesn`t mean it couldn`t work for others
Click to expand...
Click to collapse
How exactly do you get out of a boot-loop, when you can't even get into the rom to bring up the Power dialog in the first place like that instruction says? (The instructions you posted only works if you're already in the rom, holding down the ok button before it reboots, and I suspect all that's doing is clearing the Dalvik-cache which you can do from recovery anyways).
Also my problem wouldn't have anything to do with that, because if you flash a galaxy nexus recovery onto an N4, and reboot, it won't let you in because it'll ask for a password to decrypt storage, an the recovery will do the same thing, and my post which you quoted didn't have anything to do with a bootloop, just simply that you can get out of just bout any situations with a Nexus 4.

These are the most common bootloop solutions http://droidviews.com/2012/how-to-recover-when-your-android-device-is-caught-in-bootloop/.

LG G2 ADB unauthorized device (unable to get into system)

Hey guys, I was running 4.3.x for a while with the loki twrp solution and all was well, after many attempts to flash 4.4 I finally decided to ditch twrp and go to CWM, that went without a hitch and brought me into the latest nightly of CM, yet I wanted a fresh install (No accounts, no pictures media etc etc) so I tried to do factory reset from within the OS and it wouldn't let me. so I then went into recovery and tried to format things from there...
Since then I have been unable to get past the spinning CyanogenMod boot screen and though adb sees there is a device, it is telling me it is "unauthorized". Of course since I can't get into the OS the RSA confirmation thing can't come up and I can't select any system preferences. Before I went messing around in recovery formatting things ADB was working flawlessly.
Any ideas on where to go from here?
Thanks guys,
Lokin

HellaBester said:
Hey guys, I was running 4.3.x for a while with the loki twrp solution and all was well, after many attempts to flash 4.4 I finally decided to ditch twrp and go to CWM, that went without a hitch and brought me into the latest nightly of CM, yet I wanted a fresh install (No accounts, no pictures media etc etc) so I tried to do factory reset from within the OS and it wouldn't let me. so I then went into recovery and tried to format things from there...
Since then I have been unable to get past the spinning CyanogenMod boot screen and though adb sees there is a device, it is telling me it is "unauthorized". Of course since I can't get into the OS the RSA confirmation thing can't come up and I can't select any system preferences. Before I went messing around in recovery formatting things ADB was working flawlessly.
Any ideas on where to go from here?
Thanks guys,
Lokin
Click to expand...
Click to collapse
I had an issue with my adb, it was out dated. I updated the sdk system, and it detected the lg g2, this could possibly help you.

osugsxr said:
I had an issue with my adb, it was out dated. I updated the sdk system, and it detected the lg g2, this could possibly help you.
Click to expand...
Click to collapse
Yeah I considered that but no everything is up to date. It seems more like the RSA auth fingerprint is not being recognized. Plus it does recognize the phone, it just tells me it is unauthorized.

Get back into Recovery mode and use ADB from there

votinh said:
Get back into Recovery mode and use ADB from there
Click to expand...
Click to collapse
How do I get into recovery without being able to "adb reboot recovery"?

unomicu how
Bump. Anything guys? Really struggling here....

Can you get in recovery using button combination?

votinh said:
Can you get in recovery using button combination?
Click to expand...
Click to collapse
Nope, doesn't seem like it. Though I can get into download mode no problem.

Alright guys, since it seems like not many people out there know whats going on with me I'll dow what i can to keep an update.
Finally got back into Recovery using this super convenient little trick I did not know existed.
Though now I am unable to mount anything at all from recovery "E:Can't mount /cache.. etc"

HellaBester said:
Alright guys, since it seems like not many people out there know whats going on with me I'll dow what i can to keep an update.
Finally got back into Recovery using this super convenient little trick I did not know existed.
Though now I am unable to mount anything at all from recovery "E:Can't mount /cache.. etc"
Click to expand...
Click to collapse
I've never been able to mount anything using the recovery. Not sure if it because of the LG phone or of my recovery. But I've tried different ones (CWM, TWRP, Philz Touch), none was able to mount my phone from recovery. Your best bet right now is to flash the files from a OTG cable and flash drive. Also when you said you formatted the phone from the recovery, did you format the system partition as well? TWRP has that option so I assume CWM has it as well

super114 said:
I've never been able to mount anything using the recovery. Not sure if it because of the LG phone or of my recovery. But I've tried different ones (CWM, TWRP, Philz Touch), none was able to mount my phone from recovery. Your best bet right now is to flash the files from a OTG cable and flash drive. Also when you said you formatted the phone from the recovery, did you format the system partition as well? TWRP has that option so I assume CWM has it as well
Click to expand...
Click to collapse
Heyoo, just in the last hour or so I've got it all fixed!
I did a full system, data and cache format om CWM after that there was no OS or amnything of the sort, then I was able to mount the SD and adb push cm11 + gapps-kk to the sdcard, I flashed those two zips restarted, failed, then i did a system reset (resets everything but the OS) and I popped out in CM11 with a perfectly fresh install. got all that setup and am golden now ::

Congratz

Check the .android folder
My problem started when I tried to connect another phone which happened to be the same type of phone as the previous one. Not sure if that's actually related, but my working hypothesis is that ADB gets confused in this scenario. I tried everything listed here and in many other places, and nothing seemed to work. Finally, I did this:
1. Rename .android folder in your user directory (~/username/.android on Mac OSX) to .android_bak (for safe keeping).
2. Restart the adb daemon: "adb kill-server" followed by "adb start-server"
After that, I got the authentication confirmation on the phone (don't forget that part, of course) and all was well.
These steps merely recreate the .android folder and get rid of any authentication credentials you already have. Note of course that this will impact all other phones you may be connecting.

Freezes on Google screen after attempted SU Install from TWRP

Ok I am sure I did this before without any problem, but this time, through TWRP on the NRTK, I installed Magisk, no problems, and then went back to install the SU with the zip file in TWRP again and then on the reboot it freezes on the Google startup screen.
I didnt even want to install the SU zip, but when I ran SU after Magisk installed after reboot, SU gave an error, so I decided to install SU from TWRP.
Did I do something wrong there, so I dont repeat the same error next time?
And how do I get out of this locked state?
I've tried wiping all cache to factory reset without deleting internal storage data... I am hoping I dont have to delete and wipe everything and start all over. I did not have a chance to eve install TiB yet.

Dathaeus said:
Ok I am sure I did this before without any problem, but this time, through TWRP on the NRTK, I installed Magisk, no problems, and then went back to install the SU with the zip file in TWRP again and then on the reboot it freezes on the Google startup screen.
I didnt even want to install the SU zip, but when I ran SU after Magisk installed after reboot, SU gave an error, so I decided to install SU from TWRP.
Did I do something wrong there, so I dont repeat the same error next time?
And how do I get out of this locked state?
I've tried wiping all cache to factory reset without deleting internal storage data... I am hoping I dont have to delete and wipe everything and start all over. I did not have a chance to eve install TiB yet.
Click to expand...
Click to collapse
Flash the stock boot.img from the image/rom you were using before this and reboot. You will have to re-root (properly) afterwards, but your phone should boot up. If you use Magisk, you don't need SU, and vice versa. Use only one method to root.

v12xke said:
Flash the stock boot.img from the image/rom you were using before this and reboot. You will have to re-root (properly) afterwards, but your phone should boot up. If you use Magisk, you don't need SU, and vice versa. Use only one method to root.
Click to expand...
Click to collapse
Hmmm ya I prob should have posted that SU error message instead of what I did, douche move.
But how do I flash the boot.img... I have an original copy of it on my PC... can I somehow while in TWRP on the phone connect to my PC via cable and run commands from my PC in CMD and execute that old boot.img flash? Or is there a location in the stock Nexus already I can use? Because there is no file in the root drive after I did the soft wipe.
P.S. Everything I have done so far has not deleted my whole storage, yet.... not sure if that is necessary at this point bec it seems reflashing the boot.img wipes absolutely everything again? If I have to it is what it is... just painful when this happens before I could get TiB running... unless my Nandroid backup file I have will restore and work after I do this?

Dathaeus said:
Hmmm ya I prob should have posted that SU error message instead of what I did, douche move.
But how do I flash the boot.img... I have an original copy of it on my PC... can I somehow while in TWRP on the phone connect to my PC via cable and run commands from my PC in CMD and execute that old boot.img flash? Or is there a location in the stock Nexus already I can use? Because there is no file in the root drive after I did the soft wipe.
Click to expand...
Click to collapse
While in TWRP you have MTP (file transfer) so you can add files to your device. Transfer the boot.img over to your device via MTP and then use TWRP to flash. Just be sure to select flash IMAGE rather than ZIP. Lesson here is when you get back up and running, install fastboot/adb and make sure it is working well and communicating with your PC. Then you can learn how to use it. This would take literally 5 seconds to flash via fastboot (device in bootloader mode).
---------- Post added at 01:29 PM ---------- Previous post was at 01:26 PM ----------
Dathaeus said:
P.S. Everything I have done so far has not deleted my whole storage, yet.... not sure if that is necessary at this point bec it seems reflashing the boot.img wipes absolutely everything again? If I have to it is what it is... just painful when this happens before I could get TiB running... unless my Nandroid backup file I have will restore and work after I do this?
Click to expand...
Click to collapse
NO, flashing boot.img will not delete any of your files. It will only write to the boot partition. If using fastboot the command is fastboot flash boot boot.img

v12xke said:
While in TWRP you have MTP (file transfer) so you can add files to your device. Transfer the boot.img over to your device via MTP and then use TWRP to flash. Just be sure to select flash IMAGE rather than ZIP. Lesson here is when you get back up and running, install fastboot/adb and make sure it is working well and communicating with your PC. Then you can learn how to use it. This would take literally 5 seconds to flash via fastboot (device in bootloader mode).
NO, flashing boot.img will not delete any of your files. It will only write to the boot partition. If using fastboot the command is fastboot flash boot boot.img
Click to expand...
Click to collapse
Yep I actually had those platform files already, and yes the MTP was active there, I just never tried that before so didnt know it was even a possibility or the right way.
So I tried via flashing my very old boot.img and also the one from
https://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
via TWRP "Install" via image install (not zip) and to the "boot partition"
and no change, same stuck on Google logo screen.
I tried the fastboot command from CMD and it says
< waiting for any device >
and doesnt do anything. I had it on the default TWRP menu screen.... I waited over 20 min although I know it shouldnt take near that long, just in case.
My bootloader is unlocked BTW, I dont want to assume anything here.

You need help getting the latest fastboot/adb binaries working on your PC. So many tutorials on how to do this. Ugh.

Dathaeus said:
Yep I actually had those platform files already, and yes the MTP was active there, I just never tried that before so didnt know it was even a possibility or the right way.
So I tried via flashing my very old boot.img and also the one from
https://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
via TWRP "Install" via image install (not zip) and to the "boot partition"
and no change, same stuck on Google logo screen.
I tried the fastboot command from CMD and it says
< waiting for any device >
and doesnt do anything. I had it on the default TWRP menu screen.... I waited over 20 min although I know it shouldnt take near that long, just in case.
My bootloader is unlocked BTW, I dont want to assume anything here.
Click to expand...
Click to collapse
Which OS security patch were you running? Flash the system (to the system partition in TWRP) and boot images (again) from the 6P factory image of the same name:
https://developers.google.com/android/images?hl=en
See if this helps.
Sent from my Nexus 5X using Tapatalk

v12xke said:
You need help getting the latest fastboot/adb binaries working on your PC. So many tutorials on how to do this. Ugh.
Click to expand...
Click to collapse
Not sure what you mean... I JUST did all that when I redid my phone completely back to factory etc etc.... just few weeks ago and then again on my new replacement. But just to be sure, I downloaded all those files again today and it didnt make any difference.
Still stuck on the
< waiting for any device >
I have to be missing some other step or something else is wrong here.
FYI not sure if this matters but when phone boots to recovery there's a red error message
"Unable to mount storage"
but it loads to TWRP fine anyways.

SlimSnoopOS said:
Which OS security patch were you running? Flash the system (to the system partition in TWRP) and boot images (again) from the 6P factory image of the same name:
https://developers.google.com/android/images?hl=en
Click to expand...
Click to collapse
Yep thats what I been doing.....
So the CMD command still doesnt work, which I think is weird in itself... and when I try to install from recovery, it goes through the whole process, both boot.img and system.img, but then it freezes on the Google logo again, so no change.
Sorry I am not sure what security patch, I just got this used from eBay, and one thing, not sure if this means anything, it says its a beta version or something and that message came up all the time when I rebooted when the phone was working.

Do I need to suck it up and redo the whole phone again........ :/

Us996 TWRP not sticking

I'm using the tutorial on the LineageOS wiki for the Us996. I've unlocked the bootloader via official means from LG, but when it comes time to send the recovery via fastboot, it successfully sends and writes it, it even let's me boot into it, after pulling the battery, and using the correct button commands. But if I restart and try to enter again I'm greeted by the official erase everything recovery.
Does anyone know what I'm doing wrong? Do I need to flash root to get the recovery to stick?

Take a look at this video. If you have TWRP installed right, and are going to it through a battery pull and the power button volume down combination, then the screen that comes up looks scary and looks like you'll "format" your phone, but as you see in this video, you don't.

baldybill said:
Take a look at this video. If you have TWRP installed right, and are going to it through a battery pull and the power button volume down combination, then the screen that comes up looks scary and looks like you'll "format" your phone, but as you see in this video, you don't.
https://www.youtube.com/watch?v=https://www.youtube.com/watch?v=tDq0qMbgjL4
Click to expand...
Click to collapse
See I've gotten into TWRP, then I reboot system(actual Android not just restarting recovery).the problem is When I power off my phone and tried to get back into TWRP, I clicked yes and yes and it proceeded to wipe my phone. TWRP wasn't there just factory reset lol

lowsnamebrand said:
See I've gotten into TWRP, then I reboot system(actual Android not just restarting recovery).the problem is When I power off my phone and tried to get back into TWRP, I clicked yes and yes and it proceeded to wipe my phone. TWRP wasn't there just factory reset lol
Click to expand...
Click to collapse
Not sure why it isnt happening automatically (it usually does when flashing things like magisk to root) but when you get into twrp or with root rename /system/recovery-from-boot.p to /system/recovery-from-boot.bak. If in twrp first go into the mount page and uncheck the box at the bottom that says something about system read only first, then you can use the file manager.
Or since it sounds like you want to flash lineage, just flash the lineageos zip (and then optionally opengapps and root). Be sure to format data too (wipe->format data->yes). Then if you dont have lineage on an sdcard ready to go you could reboot recovery so that the formatted data is ready then connect to pc and send the zips over by using adb push C:\path\to\lineage.zip /sdcard/

Phoenix591 said:
Not sure why it isnt happening automatically (it usually does when flashing things like magisk to root) but when you get into twrp or with root rename /system/recovery-from-boot.p to /system/recovery-from-boot.bak. If in twrp first go into the mount page and uncheck the box at the bottom that says something about system read only first, then you can use the file manager.
Or since it sounds like you want to flash lineage, just flash the lineageos zip (and then optionally opengapps and root). Be sure to format data too (wipe->format data->yes). Then if you dont have lineage on an sdcard ready to go you could reboot recovery so that the formatted data is ready then connect to pc and send the zips over by using adb push C:\path\to\lineage.zip /sdcard/
Click to expand...
Click to collapse
What I'm thinking about doing is flashing TWRP again, on first boot(of TWRP) backing up my current rom(stock) and trying to boot into recovery again, because if it doesn't stick again, it'll wipe but at least I'll have a backup.
I've noticed a lot of different root files which would you recommend?

lowsnamebrand said:
What I'm thinking about doing is flashing TWRP again, on first boot(of TWRP) backing up my current rom(stock) and trying to boot into recovery again, because if it doesn't stick again, it'll wipe but at least I'll have a backup.
I've noticed a lot of different root files which would you recommend?
Click to expand...
Click to collapse
Sorry for the double post but does the "LG factory reset" stay even after having TWRP installed? Like will I always have to answer yes twice to enter TWRP?

lowsnamebrand said:
Sorry for the double post but does the "LG factory reset" stay even after having TWRP installed? Like will I always have to answer yes twice to enter TWRP?
Click to expand...
Click to collapse
Yes thats always the same.
If you don't flash lineage or something to root stock (I reccommend magisk since the alternative, Supersu, is owned by some Chinese company, and magisk has various modules that do many things) and don't rename /system/recovery-from-boot.p manually (theres a file manager under advanced in twrp) the stock rom will use that file to reflash stock recovery any time it boots.

Phoenix591 said:
Yes thats always the same.
If you don't flash lineage or something to root stock (I reccommend magisk since the alternative, Supersu, is owned by some Chinese company, and magisk has various modules that do many things) and don't rename /system/recovery-from-boot.p manually (theres a file manager under advanced in twrp) the stock rom will use that file to reflash stock recovery any time it boots.
Click to expand...
Click to collapse
Awesome I think my issue is not renaming that file and the stock rom reinstalling stock recovery. I've used SuperSU, never used magisk, is there a stickied release thread for it?

lowsnamebrand said:
Awesome I think my issue is not renaming that file and the stock rom reinstalling stock recovery. I've used SuperSU, never used magisk, is there a stickied release thread for it?
Click to expand...
Click to collapse
Its got more than a thread, has a whole section. Anyway heres the main release thread

Phoenix591 said:
Its got more than a thread, has a whole section. Anyway heres the main release thread
Click to expand...
Click to collapse
You've been a huge help, thank you! I'll report back later tonight, when I can actually work on my phone

So i was able to obtain root aswell as installed twrp, the only issue I had was every rom I tried refused to boot. They just hung at the loading screen, that includes the back up I'd made of stock, is there something I missed?

lowsnamebrand said:
So i was able to obtain root aswell as installed twrp, the only issue I had was every rom I tried refused to boot. They just hung at the loading screen, that includes the back up I'd made of stock, is there something I missed?
Click to expand...
Click to collapse
If you mean the boot animation, the very first time can take a good while, like 20 minutes. Also make sure you've formatted /data if you havnt yet especially going to lineage.

Phoenix591 said:
If you mean the boot animation, the very first time can take a good while, like 20 minutes. Also make sure you've formatted /data if you havnt yet especially going to lineage.
Click to expand...
Click to collapse
Sorry for the late reply, yeah I think I just let the boot animation go for around 5, I'm gonna have to try reflashing it and hoping for the best, I'll be sure to answer back when I get a chance

OK, I know this is an old thread - but I just got a replacement US996 phone; my old standby has a charger plug problem so I decided to get another one and put a rooted stock Oreo ROM on it. However, I'm having the same issue as the OP. Get into fastboot, flash TWRP (I have the 3.3.1-0 version, as the newer 3.3.1-1 version does not have any download mirrors). The flash appears to go just fine, it says the write was completed. However, when I reboot into adb mode and do "adb reboot recovery" I get "no command" and the little droid with his belly hatch open. So obviously TWRP wasn't flashed. The OP says he eventually was able to get it to work and install root. How did you fix the issue?
Do I still need to do the old recowvery shenanigans that we had to do back when the phone first came out?
Thanks!

I believe you MUST use the button combo to reboot into twrp.
See here:
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239/post78513963

pistacios said:
I believe you MUST use the button combo to reboot into twrp.
See here:
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239/post78513963
Click to expand...
Click to collapse
I've done that. The problem is that TWRP hasn't actually been installed via fastboot flash recovery - it goes through the motions, SAYS it's been installed, but when I do the button combo, it actually does reset my phone rather than booting into TWRP.
---------- Post added at 09:36 AM ---------- Previous post was at 08:55 AM ----------
Disregard the above. Flashed it again (4th time), and it finally took.

The same happened with my wife's US996 now that you mention it. Took a few tries and was a bit frustrating.
When I flashed TWRP on mine it was a "one and done".
Glad you got it sorted.

Thanks - all good. Rooted stock Oreo ROM installed, working great.