Database Users

KindleFire Partitions error? [Still not fixed]

When I flashed a kernel I did boot boot.img first and it worked so I did flash boot boot.img with fastboot. Well that didn't work. So I just got the other boot.img for cm7 and tryed to do that. Well I got this error:
C:\adb>fastboot flash boot boot.img
sending 'boot' (3196 KB)... OKAY [ 0.875s]
writing 'boot'... FAILED (remote: partition does not exist)
finished. total time: 0.885s
When a wipe is issued:
C:\adb>fastboot -w
erasing 'userdata'... FAILED (remote: : partition doesn't exist)
finished. total time: 0.002s
I am in fastboot but I can not get into twrp2 because when I hold down the power button to enter recovery it just turns amber and just hangs. I do have some mmcblk0pXX .img's if it helps.

I think I'm having the same problem. When I try to boot the bootnew.img for intersectRaven's kernel, it hangs at the FIREFIREFIRE yellow triangle with an amber light. No fastboot commands will take me out of it. If it makes a difference, I installed the custom WiFi driver.

Thats the exact same thing is for me.

TyHi said:
Thats the exact same thing is for me.
Click to expand...
Click to collapse
I guess we're in the same boat then. I think my problem came from booting the kernel up, then installing the custom wifi driver, then trying to boot it up again.

When I flashed a kernel I did boot boot.img first and it worked so I did flash boot boot.img with fastboot. Well that didn't work. So I just got the other boot.img for cm7 and tryed to do that. Well I got this error:
C:\adb>fastboot flash boot boot.img
sending 'boot' (3196 KB)... OKAY [ 0.875s]
writing 'boot'... FAILED (remote: partition does not exist)
finished. total time: 0.885s
I am in fastboot but I can not get into twrp2 because when I hold down the power button to enter recovery it just turns amber and just hangs. I do have some mmcblk0pXX .img's if it helps.
Click to expand...
Click to collapse
Did you follow precisely the commands given here? It sounds like you did, but I just wanted to make sure. I was going to suggest you reset the bootmode to 4000. Have you already tried that?

rwphwp said:
Did you follow precisely the commands given here? It sounds like you did, but I just wanted to make sure. I was going to suggest you reset the bootmode to 4000. Have you already tried that?
Click to expand...
Click to collapse
Since apparently the OP and I have the same problem, yes I tried that. The command "fastboot -i 0x1949 oem idme bootmode 4000" doesn't work for me. It just boots into fastboot again.

I read someplace when I rooted 6.2.1 with perhaps a Burrito Root prog. The recommended order to get CM7 and TWRP . Is to go - in this order. Root, then TWRP AND lastly update.zip to sdcard for install of CM7. I made space avail. for TWRP'S Backup ( STRONGLY RECOMMEND ) BACKUP. ======which saved me a few times already on a couple frozen boots. Cause I experiment with various launchers, I think.

Yes I have. It just hangs on the yellow boot with a green light.

Smmoph said:
I read someplace when I rooted 6.2.1 with perhaps a Burrito Root prog. The recommended order to get CM7 and TWRP . Is to go - in this order. Root, then TWRP AND lastly update.zip to sdcard for install of CM7. I made space avail. for TWRP'S Backup ( STRONGLY RECOMMEND ) BACKUP. ======which saved me a few times already on a couple frozen boots. Cause I experiment with various launchers, I think.
Click to expand...
Click to collapse
The thing is that I cant even root it. It is just stuck it at boot screen for FIREFIREFIRE v1.0.

Smmoph said:
I read someplace when I rooted 6.2.1 with perhaps a Burrito Root prog. The recommended order to get CM7 and TWRP . Is to go - in this order. Root, then TWRP AND lastly update.zip to sdcard for install of CM7. I made space avail. for TWRP'S Backup ( STRONGLY RECOMMEND ) BACKUP. ======which saved me a few times already on a couple frozen boots. Cause I experiment with various launchers, I think.
Click to expand...
Click to collapse
I suck at pushing buttons on forums now (hence the accidental thank), but I'm not really trying to install CM7.

Have you tried the hard reset? Hold power button for app. 18 seconds till screen goes totally dark, then press power bttn on again, once.

Yes I have many times.

I can suggest changing the driver on usb in pc or rebboot pc after uninstall and the change it . But I wanted to show a procedure. win utility 7 gave me the necc. usb driver v. 6 did not have.

TyHi said:
Yes I have. It just hangs on the yellow boot with a green light.
Click to expand...
Click to collapse
Gotcha. Any luck with this method?

There was also A kindlefire utility v.? with an option in red for "factory reset" on the device, perhaps.

rwphwp said:
Gotcha. Any luck with this method?
Click to expand...
Click to collapse
Yes I have. Can't even do adb push. When I get into adb with using boot boot.img from cm7. I get, exec /system/bin/sh' failed no file or directory.

I would not give in, but try to stay calm with all methods to reclaim functionality. I started with rootwiki and Jayce Ooi's And Burrito in order to stay clear of CMD console cause I was not even recognised till Win_usb drivers eventually fell in place. Saw some stuff about editing path's also. Reading alot helped.

I'd join IRC and see what we can accomplish there. You all are all over the place, and some of you aren't even bricked at all.

Vashypooh said:
I'd join IRC and see what we can accomplish there. You all are all over the place, and some of you aren't even bricked at all.
Click to expand...
Click to collapse
I was in there all day, and I never got a working solution.

TheMagicPancake said:
I was in there all day, and I never got a working solution.
Click to expand...
Click to collapse
Join there ~12:45-1am EST, ill be available to help then.

[Q] Custom Rom FAIL, is my Nexus forever lost?

Hi everyone.
I was trying to install Cyanogenmod on my nexus, I was doing so using the Nexus Root Toolkit v1.7.9. I went through the initial setup fine, unlocked my device, rooted it to SuperSU and got up to the stage where I wiped the System, the Cache, the Delvik Cache and the Data. However when trying to install the Rom I forgot to add the gapps zip file which seemed important in the video tutorial I was watching.
From this I panicked and tried to restart my device to see if I could still transfer the zip from my computer to the tablet. However in the midst of panick I forgot I had wiped tthe system and I wouldn't be able to communicate with my PC to transfer the file. So I tried to go back to the Recovery Mode to still try and load up Cyanogemod so I at least have some system files. However now the custom recovery won't load either. I fear the worst that my tablet is irreparable, can anyone help me find out of there is anything I can do.
I have looked all over but nowehere on the internet is there a problem similiar to mine, truly one of a kind idiocy from my part. But if anyone could help it would be great.

DroidDoode said:
Hi everyone.
I was trying to install Cyanogenmod on my nexus, I was doing so using the Nexus Root Toolkit v1.7.9. I went through the initial setup fine, unlocked my device, rooted it to SuperSU and got up to the stage where I wiped the System, the Cache, the Delvik Cache and the Data. However when trying to install the Rom I forgot to add the gapps zip file which seemed important in the video tutorial I was watching.
From this I panicked and tried to restart my device to see if I could still transfer the zip from my computer to the tablet. However in the midst of panick I forgot I had wiped tthe system and I wouldn't be able to communicate with my PC to transfer the file. So I tried to go back to the Recovery Mode to still try and load up Cyanogemod so I at least have some system files. However now the custom recovery won't load either. I fear the worst that my tablet is irreparable, can anyone help me find out of there is anything I can do.
I have looked all over but nowehere on the internet is there a problem similiar to mine, truly one of a kind idiocy from my part. But if anyone could help it would be great.
Click to expand...
Click to collapse
Use the Nexus Root Toolkit.
Reflash stock using "Soft-Bricked/Bootloop"
Just start the device in Fastboot mode (Hold Power and Up/Down Volume Rockers)
I've done the same and it worked just fine.

You would've been fine without the gapps, you just wouldn't have the play store and other Google apps installed. Then you could've rebooted and installed it at any time. Give what the person before me suggested a go.
Sent from my Nexus 7 using xda app-developers app

billiejackfu said:
Use the Nexus Root Toolkit.
Reflash stock using "Soft-Bricked/Bootloop"
Just start the device in Fastboot mode (Hold Power and Up/Down Volume Rockers)
I've done the same and it worked just fine.
Click to expand...
Click to collapse
Thank you for your reply. I tried this in the Nexus Root Toolkit and it says:
sending 'bootloader' <3911KB>...
OKAY [0.468s]
writting 'bootloader'...
FAILED <remote: <InvalidState>>
finished. total time: 0.701s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
Then at "checking product..." it says:
sending 'system' <625382 KB>...
FAILED <remote: <Nv3pBadReceiveLength>>
finished. total time: 4.853s
Those are the only two parts that failed. Any further help? Do you need the full log?

DroidDoode said:
Thank you for your reply. I tried this in the Nexus Root Toolkit and it says:
sending 'bootloader' <3911KB>...
OKAY [0.468s]
writting 'bootloader'...
FAILED <remote: <InvalidState>>
finished. total time: 0.701s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
Then at "checking product..." it says:
sending 'system' <625382 KB>...
FAILED <remote: <Nv3pBadReceiveLength>>
finished. total time: 4.853s
Those are the only two parts that failed. Any further help? Do you need the full log?
Click to expand...
Click to collapse
Try changing USB ports. This happened to me when I was using a faulty usb slot in my computer.

I'd re lock the nexus through the toolkit download a factory image and soft boot recovery as was posted before exact thing happened to me and I was able to save it
Sent from my SPH-L900 using xda app-developers app

Leonhan said:
Try changing USB ports. This happened to me when I was using a faulty usb slot in my computer.
Click to expand...
Click to collapse
I can't believe it was that simple... All I did was change USB ports and I was able to revert to stock Android and now I have installed CM and it is running buttery smooth. THANK YOU SO MUCH!! I thought it was a lost cause!

when I try to flash twrp.img I get this error

why do I keep getting this error when trying to flash twrp? I'm on lineage 14.1
C:\Users\spam1\Desktop\Minimal ADB and Fastboot>fastboot flash boot twrp-mata_6.img
target didn't report max-download-size
sending 'boot' (32124 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.123s
Thanks

I had this same problem. Have you tried "fastboot -w" before attempting to flash twrp?

Try android studio tools, outdated ADB/fastboot was an issue when I was on the pixel xl due to the partitions

Jaysonvstel said:
I had this same problem. Have you tried "fastboot -w" before attempting to flash twrp?
Click to expand...
Click to collapse
I'll try that once I get home. All I did was the update and lost root and recovery

networx2002 said:
I'll that that once I get home. All I did was the update and lost root and recovery
Click to expand...
Click to collapse
It will rested the phone, so backup.

DaveHTC200 said:
Try android studio tools, outdated ADB/fastboot was an issue when I was on the pixel xl due to the partitions
Click to expand...
Click to collapse
Here is the link for OP.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip

I just got home and wanted to tried and flash twrp recovery before I fastboot -w" it and it worked... LOL who knows!

I have the same problem. I tried many times, many methods found online, including swapping USB port, cables, and tried fastboot -w. Neither of them works...

heximing said:
I have the same problem. I tried many times, many methods found online, including swapping USB port, cables, and tried fastboot -w. Neither of them works...
Click to expand...
Click to collapse
Me too, can't figure it out..

networx2002 said:
why do I keep getting this error when trying to flash twrp? I'm on lineage 14.1
C:\Users\spam1\Desktop\Minimal ADB and Fastboot>fastboot flash boot twrp-mata_6.img
target didn't report max-download-size
sending 'boot' (32124 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.123s
Thanks
Click to expand...
Click to collapse
Try changing USB port or use a different USB cable. The is known to solve the issue.
Also once you are in fastbot, reboot again into fastboot using "fastboot reboot bootloader"
And the flash TWRP image
If you still get the error, install Fastboot drivers from Essential website.

networx2002 said:
why do I keep getting this error when trying to flash twrp? I'm on lineage 14.1
C:\Users\spam1\Desktop\Minimal ADB and Fastboot>fastboot flash boot twrp-mata_6.img
target didn't report max-download-size
sending 'boot' (32124 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.123s
Thanks
Click to expand...
Click to collapse
Jaysonvstel said:
I had this same problem. Have you tried "fastboot -w" before attempting to flash twrp?
Click to expand...
Click to collapse
DaveHTC200 said:
Try android studio tools, outdated ADB/fastboot was an issue when I was on the pixel xl due to the partitions
Click to expand...
Click to collapse
heximing said:
I have the same problem. I tried many times, many methods found online, including swapping USB port, cables, and tried fastboot -w. Neither of them works...
Click to expand...
Click to collapse
dsulps said:
Me too, can't figure it out..
Click to expand...
Click to collapse
Use the adb/fastboot from the drivers from essential. It sets environment variable in Windows. Uninstall any other adb/fastboot, and check your environment path to make sure only essential bone is there.
You could easily brick your phone using the wrong adb/fastboot. Beware of dragons and such.

Did that, but somehow it didn't help. Tried a different computer, installed the essential drivers, and used the cable that came with the phone; everything went smoothly. Still don't know what the problem was, the first computer does not have any fastboot/adb in the path variable, after removing the essential drivers, but I suppose the problem's solved, for now. Thanks everyone!

dsulps said:
Did that, but somehow it didn't help. Tried a different computer, installed the essential drivers, and used the cable that came with the phone; everything went smoothly. Still don't know what the problem was, the first computer does not have any fastboot/adb in the path variable, after removing the essential drivers, but I suppose the problem's solved, for now. Thanks everyone!
Click to expand...
Click to collapse
It's Essential voodoo...
@aer0zer0
devnull advocates a PC reboot with the device unplugged, run the command, then plug the device in while "Waiting for device..." And it has worked for me twice when fastboot was drunk

rignfool said:
It's Essential voodoo...
@aer0zer0
devnull advocates a PC reboot with the device unplugged, run the command, then plug the device in while "Waiting for device..." And it has worked for me twice when fastboot was drunk
Click to expand...
Click to collapse
Oh sure, but the bigger question is, why is fastboot drunk to begin with?

aer0zer0 said:
Oh sure, but the bigger question is, why is fastboot drunk to begin with?
Click to expand...
Click to collapse
Because it got into your liquor cabinet?

rignfool said:
Because it got into your liquor cabinet?
Click to expand...
Click to collapse
so fastboot says its hammertime

aer0zer0 said:
so fastboot says its hammertime
Click to expand...
Click to collapse
More like...
"Can't Touch This"

[HELP] Stucked in weird bootloop after flashing

Hi folks, my A1 device is stuck in weird bootloop situation.
This is what I did.
- oem unlock
- boot with a twrp recovery image
- edit build.prop (Added persist.camera.HAL3.enabled=1 on top)
- reboot
- first bootloop (reboot after mi logo)
- flashed with tissot_images_7.12.7_7.1 version
- succeed boot but the device couldn't recognize usim
- factory reset from android setting menu
- second bootloop (reboot after mi logo)
- flashed with tissot_images_7.12.7_7.1 version
- still bootloop (reboot after mi logo). Since this, it always reproduces bootloop even I had flashing again.
- reboot with twrp and checked /sdcard directory. It was empty. There was only 'TWRP' directory
- after searching, I assumed that it was partition broken issue. (http://en.miui.com/thread-970194-1-1.html)
- Followed this article to fix partition problem. https://forum.xda-developers.com/xiaomi-mi-3/general/guide-instruction-to-restore-mi4-mi3-t3279927
- After flashing, went to hardbrick(edl_mode). After several trying, could flash again.
- Different type of bootloop. Could pass mi logo and android one logo. But after few second after, it reboots.
Last bootloop(current status) does not depend on special action. Even when I skipped few task(setup network, account, etc), it still reboots.
Maybe it could depend on time. I think something was broken in the background.
Does anyone know about this kind of problem?
I searched for two days, but A1 is newer device so there is not much information for troubleshooting.
Please help me :crying:

Try flashing the persist.img through fastboot by typing fastboot flash persist persist.img .
I guess you're fimiliar about how fastboot flashing works. I did got my phone with the similar issue fixed doing that, but later the persist image couldn't be flashed and I ended up hard bricking the device as my PC restarted while I was flashing using MiFlash and service guys had to replace the entire motherboard.
You can try doing that but do note that flashing the persist.img many times is strictly prohibited.

Use MiFlash to flash the rom completely. Did you try to preserve user data when flashing?
Seems that unless you are rooted, playing with the build.prop from TWRP or some other method is a bad idea.

FAILED (remote: Error: This image isn't allow download)
Edwin Hamal said:
Try flashing the persist.img through fastboot by typing fastboot flash persist persist.img .
I guess you're fimiliar about how fastboot flashing works. I did got my phone with the similar issue fixed doing that, but later the persist image couldn't be flashed and I ended up hard bricking the device as my PC restarted while I was flashing using MiFlash and service guys had to replace they mother.
You can try doing that but do note that flashing the persist.img many times is strictly prohibited.
Click to expand...
Click to collapse
Thanks very much for you helping Edwin!
I tried the command that you let me know, but it returns following error.
./fastboot flash persist images/persist.img
target reported max download size of 536870912 bytes
sending 'persist' (4720 KB)...
OKAY [ 0.160s]
writing 'persist'...
FAILED (remote: Error: This image isn't allow download)
finished. total time: 0.180s
I searched cases for this error, but couldn't find working answer.
Do you have any idea about this?
Thanks! Have a great day!

Try emptying the userdata partition using fastboot.

I heard that the low version of the driver also causes errors. Update the driver's fastboot, and try to flash again.

Try manually flashing the firmware by following this guide
http://en.miui.com/thread-942449-1-1.html
after completing the last step given in the guide,type "fastboot reboot".
Also this only works with unlocked bootloader

pitzcarraldo said:
Thanks very much for you helping Edwin!
I tried the command that you let me know, but it returns following error.
./fastboot flash persist images/persist.img
target reported max download size of 536870912 bytes
sending 'persist' (4720 KB)...
OKAY [ 0.160s]
writing 'persist'...
FAILED (remote: Error: This image isn't allow download)
finished. total time: 0.180s
I searched cases for this error, but couldn't find working answer.
Do you have any idea about this?
Thanks! Have a great day!
Click to expand...
Click to collapse
Try restoring the persist.img from the August build. I think that error occurs because the size of persist is different in those two builds.

Oh My Savior!!!!!!!!!!!!!!
Edwin Hamal said:
Try restoring the persist.img from the August build. I think that error occurs because the size of persist is different in those two builds.
Click to expand...
Click to collapse
Finally, it is fixed!!!!!!!!!
Thank you sooooooo much my savior!
God bless you!
I really really owe you!
Happy holiday!
You're my Santa Clause!

pitzcarraldo said:
Finally, it is fixed!!!!!!!!!
Thank you sooooooo much my savior!
God bless you!
I really really owe you!
Happy holiday!
You're my Santa Clause!
Click to expand...
Click to collapse
I'm really glad that I could help. I had this issue too and I can recall how painful it was. I think more people need to know about this fix, can you post the august persist.img file here so more people can access that easily?

persist.img
Edwin Hamal said:
I'm really glad that I could help. I had this issue too and I can recall how painful it was. I think more people need to know about this fix, can you post the august persist.img file here so more people can access that easily?
Click to expand...
Click to collapse
Sure. Here is persist.img file that I used to fix my case.
Thanks.
Happy Holidays!

pitzcarraldo said:
Sure. Here is persist.img file that I used to fix my case.
Thanks.
Happy Holidays!
Click to expand...
Click to collapse
I was in a very similar scenario, however, I could not find any persist.img I could flash through fastboot. Can't erase it also.
I also tried to get it working though using twrp and downloading the latest stable build from Xiaomi.
Booting temporally into the TWRP, sending the persist.img found into the build files and using the following cmd:
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27
No luck. Device boots, goes to setup wizard, then reboots a few seconds later. =(
Not sure what to try anymore. Xiaomi doesn't officially sell phones in my country so I can't contact warranty.

rlsin said:
I was in a very similar scenario, however, I could not find any persist.img I could flash through fastboot. Can't erase it also.
I also tried to get it working though using twrp and downloading the latest stable build from Xiaomi.
Booting temporally into the TWRP, sending the persist.img found into the build files and using the following cmd:
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27
No luck. Device boots, goes to setup wizard, then reboots a few seconds later. =(
Not sure what to try anymore. Xiaomi doesn't officially sell phones in my country so I can't contact warranty.
Click to expand...
Click to collapse
Brother persist.img file size 32mb no 4 MB size Google searching mi a1 persist partition repair my telegram +90594461388 add me bro

Byramklc said:
Brother persist.img file size 32mb no 4 MB size Google searching mi a1 persist partition repair my telegram +90594461388 add me bro
Click to expand...
Click to collapse
Thanks for helping mate! Though this specific google search I found some additional information on this matter (not kidding).
I was able to flash persist by downgrading back to the august nougat build. Then flashed the original persist file.
The instructions don't work if you are in any newer build, I guess I first misunderstood that part (or it just worked after a couple of tries).
Though now it doesn't recognize my sim card, so I'll keep working on it.
Best regards.

rlsin said:
Thanks for helping mate! Though this specific google search I found some additional information on this matter (not kidding).
I was able to flash persist by downgrading back to the august nougat build. Then flashed the original persist file.
The instructions don't work if you are in any newer build, I guess I first misunderstood that part (or it just worked after a couple of tries).
Though now it doesn't recognize my sim card, so I'll keep working on it.
Best regards.
Click to expand...
Click to collapse
Bro IMEI number 0 or normal

Byramklc said:
Bro IMEI number 0 or normal
Click to expand...
Click to collapse
Spot on! IMEI number 0. Trying to rewrite it somehow...

rlsin said:
Spot on! IMEI number 0. Trying to rewrite it somehow...
Click to expand...
Click to collapse
Bro agus security using 7.8.23 rom
Dualwrite IMEI. Used

Hi Guys, got the same problem here. Out of the blue my phone doesn't boot anymore (no root, no flash, nothing).
I tried flashing, with MiFlash and Fastboot, 7.1 December and Oreo January, but it didn't work unfortunately.
Now after reading your last posts I'm looking for august update. Could you please tell me where you got it.
It's weird because if i flash correctly (fastboot 7.1) i get the Android One Logo, a glitch and then it reboots, but when i try 8.0 or MiFlash i only get the Xiaomi logo and then it reboots :/
Trying to flash persist (both with 4.6MB and 32MB images through DD and TWRP) might have slightly changed the behavior ...
No clue about IMEI numbers being wiped out or not :/ (but i have the phone box with them in need)
Thanks for you help anyways

gridaz said:
Hi Guys, got the same problem here. Out of the blue my phone doesn't boot anymore (no root, no flash, nothing).
I tried flashing, with MiFlash and Fastboot, 7.1 December and Oreo January, but it didn't work unfortunately.
Now after reading your last posts I'm looking for august update. Could you please tell me where you got it.
It's weird because if i flash correctly (fastboot 7.1) i get the Android One Logo, a glitch and then it reboots, but when i try 8.0 or MiFlash i only get the Xiaomi logo and then it reboots :/
Trying to flash persist (both with 4.6MB and 32MB images through DD and TWRP) might have slightly changed the behavior ...
No clue about IMEI numbers being wiped out or not :/ (but i have the phone box with them in need)
Thanks for you help anyways
Click to expand...
Click to collapse
I am stuck at bootloop again while tinkering with imei codes. Probably killed my phone...
You can find august build and others here:
https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/

Thanks for the links, unfortunately it doesn't boot either.
It looks like it's going too, android one logo, color animation and then it reboots :/ I don't really know what i can try more.

[H918] Back to Stock Everything

Saw a post in the roms section (for different variant) of a flashable to turn back to stock.
I flashed/rooted a while ago, I did a factory reset and now it boots into TWRP.
Looking to get it back to stock.
Thanks!

Reboot into twrp that's installed on recovery. Flash
this to get download mode back. Use it and LG UP in upgrade mode to flash a kdz to restore literally everything to stock.

Phoenix591 said:
Reboot into twrp that's installed on recovery. Flash
this to get download mode back. Use it and LG UP in upgrade mode to flash a kdz to restore literally everything to stock.
Click to expand...
Click to collapse
Does aboot check laf version?

Alibaba0101 said:
Does aboot check laf version?
Click to expand...
Click to collapse
Yes, but that is laf for the H918 -- so you are good.
-- Brian

Every TWRP I try to flash says:
target reported max download size of 536870912 bytes
sending 'recovery' (22616 KB)...
OKAY [ 1.505s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 1.528s
It already has TWRP previously flashed in some way, but I cannot get into it. I see the logo flash up from time to time.
Tried Uppercut's LG UP and it will actually connect and give me the chance to flash a KDZ, but the phone will just do a quick restart and f*k everything.
OTA updates fail and say the software isn't verified. Also get the warning screen at bootup that the device has loaded a different operating system.
Any ideas? I just want it back to stock.

runningnak3d said:
Yes, but that is laf for the H918 -- so you are good.
-- Brian
Click to expand...
Click to collapse
How do I boot into TWRP? Feels like a silly question...
"adb reboot recovery" just boots to what looks like regular recovery. However, when I try to update or flash a .KDZ through LG UP, it will restart and flash up the twrp logo and say twrp 3.2.1-3. So I know the fcker is in there somewhere. I want it gone... all of it.
HALP!! Please.

Cookster128 said:
Every TWRP I try to flash says:
target reported max download size of 536870912 bytes
sending 'recovery' (22616 KB)...
OKAY [ 1.505s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 1.528s
It already has TWRP previously flashed in some way, but I cannot get into it. I see the logo flash up from time to time.
Tried Uppercut's LG UP and it will actually connect and give me the chance to flash a KDZ, but the phone will just do a quick restart and f*k everything.
OTA updates fail and say the software isn't verified. Also get the warning screen at bootup that the device has loaded a different operating system.
Any ideas? I just want it back to stock.
Click to expand...
Click to collapse
OTA updates and unmodified official stock files won't flash via TWRP.
Try flashing a copy of your stock recovery, then try installing the OTA update via stock recovery.
By the way, is that Charlotte NC? I ask because I live in Rockingham.
Sent from my LGL84VL using Tapatalk

Droidriven said:
OTA updates and unmodified official stock files won't flash via TWRP.
Try flashing a copy of your stock recovery, then try installing the OTA update via stock recovery.
By the way, is that Charlotte NC? I ask because I live in Rockingham.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Eh... Charlotte is about two hours from me. I'm at the bottom of the mountain, but I've been to Rockingham a few times. Dad graduated as a RCHS Cougar in '78.
Also, if you didn't already know, I'm the same fool from the noob thread. Glad you found me here. So, when I say it has download mode, I mean when I hit volume up and plug in, it flashes up and says it, then shows the twrp logo, then boots as normal. Calling 'adb reboot download mode' just reboots. You think the bootloader needs to be re-locked?

Cookster128 said:
Eh... Charlotte is about two hours from me. I'm at the bottom of the mountain, but I've been to Rockingham a few times. Dad graduated as a RCHS Cougar in '78.
Also, if you didn't already know, I'm the same fool from the noob thread. Glad you found me here. So, when I say it has download mode, I mean when I hit volume up and plug in, it flashes up and says it, then shows the twrp logo, then boots as normal. Calling 'adb reboot download mode' just reboots. You think the bootloader needs to be re-locked?
Click to expand...
Click to collapse
Yeah, I saw you in the noob thread, I came here looking for the issue you were having.
I'm not certain about the bootloader, I own LG devices, but none of them have fastboot or download mode so I don't have experience troubleshooting flashing issues on LG devices.
Have you tried removing root and any changes you've made to system via the file manager or terminal emulator that is built into TWRP then flashing a copy of stock recovery via TWRP then reboot recovery to allow stock recovery to boot then boot to fastboot and try locking the bootloader then try flashing firmware.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Yeah, I saw you in the noob thread, I came here looking for the issue you were having.
I'm not certain about the bootloader, I own LG devices, but none of them have fastboot or download mode so I don't have experience troubleshooting flashing issues on LG devices.
Have you tried removing root and any changes you've made to system via the file manager or terminal emulator that is built into TWRP then flashing a copy of stock recovery via TWRP then reboot recovery to allow stock recovery to boot then boot to fastboot and try locking the bootloader then try flashing firmware.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I may have got it! Maybe... don't pop the champagne yet. I couldn't get into TWRP at all. It would flash up then just boot regularly. Finally I tried to enter DL mode again but this time I kept holding down the volume up button and pressed every other button like I was entering a secret code on Mortal Kombat. It actually entered TWRP!
Luckily I had already put a laf.zip and H91820f.zip on the SD card. Flashed the ROM first... did nothing except put Magisk on it... don't want. Reboot, flashed laf.zip with my secret MK code, then I had access to the real DL mode! LG UP found it and flash the real ROM. Still working on it to make sure it's all good.
---------- Post added at 07:20 PM ---------- Previous post was at 06:38 PM ----------
Yep, it's good now. Even updated itself to H91820h with no verification snags.
I shall now sell it on eBay for one billion dollars! Muahahaha!