Database Users

Fastboot error

I have tried to install twrp recovery via fastboot and I get this error
1.C:\fastboot>fastboot flash recovery recovery.img
2.target reported max download size of 1526722560 bytes
3.error: cannot load 'recovery.img': No error
All other commands work to erase, reboot etc, but cannot flash recovery twrp on to my LGG2 D803 , any help will be appreciated.

Got it to work but flashed 3 different twrp and cm mod img and will not boot into recovery

Well if you ever Brick your phone to the point that the only thing that works is Fastboot, I was able to recover my phone using this procedure, It was a lifesaver. The phone works perfectly now, follow the Youtube instructions, I also typed the procedure out too. Always type fastboot flash then the command
https://www.youtube.com/watch?v=hQVTc2m6U-I
Use above link to completely redoo your LGG2 from fastboot, re loading all the partitions.
fastboot flash boot boot.img
aboot aboot.img
recovery recovery.img
laf laf.img
dbi dbi.img
modem modem.img
persist persist.img
PrimaryGPT PrimaryGPT.img
rpm rpm.img
stli stli.img
tz tz.img
fastboot flash reboot
after flashing all the partitions it should load so you can flash the tot/kdz file via flash utility 2014 in the command mode, by holding the volume up mode and plugging in the usb into the phone. then reload the original firmware and install twrp and if you want wipe it and reload one of the custom roms.

Well if you ever Brick your phone to the point that the only thing that works is Fastboot, I was able to recover my phone using this procedure, It was a lifesaver. The phone works perfectly now, follow the Youtube instructions, I also typed the procedure out too. Always type fastboot flash then the command
https://www.youtube.com/watch?v=hQVTc2m6U-I
Use above link to completely redoo your LGG2 from fastboot, re loading all the partitions.
fastboot flash boot boot.img
aboot aboot.img
recovery recovery.img
laf laf.img
dbi dbi.img
modem modem.img
persist persist.img
PrimaryGPT PrimaryGPT.img
rpm rpm.img
stli stli.img
tz tz.img
fastboot flash reboot
after flashing all the partitions it should load so you can flash the tot/kdz file via flash utility 2014, in the command mode, by holding the volume up button and plugging in the usb into the phone. then reload the original firmware and install twrp and if you want wipe it and reload one of the custom roms.

after updating to nougat space dissapeer

hello
i update to nougat by using these commands
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
Fastboot flash vendor vendor.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
and now instead of 64GB i see only 24..where is the rest?
i have root and twrp
thanks

Only those with the 32gb model need to flash user data
So just format your device and start over and you should have 64gb again.

ok so i just to skip the
fastboot flash userdata userdata.img
but it stays as before 24.1GB
and what is - Fastboot flash vendor vendor.img
thank you

Note: You should never flash the userdata image. It doesn't take into consideration the storage capacity of the device and always allocates 32gb of storage. This is ok for the 32gb model, but for the 64gb and 128gb models you'll end up with much less storage capacity than you should have. If you wish to wipe your internal storage you'd use the following command instead:
Code:
fastboot format userdata
and i did fastboot flash userdata userdata.img
so to fix these i did the flash all.bat
just left to know what is the Fastboot flash vendor vendor.img
thanks

Format data
See guide here : http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

vendor formats data???

flashing the vendor will not cause a wipe of data.
firstly fastboot format userdata
then follow the guide by Heisenberg that is stickied.
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img

what does the vendor command?

I7210I said:
what does the vendor command?
Click to expand...
Click to collapse
It will flash the vendor.img

so if the device doesn't know that he is from huawei so these will remind him?
Sent from my Nexus 6P using Tapatalk

Help, a/b parition screwing up my OS

Hey so I was previously on the oreo beta and reverted back to stock. I reflashed stock using a few tutorials around and it worked for a bit but magisk was screwing it up and the log file kept filling up all the storage (a known bug) and every time it rebooted it would factory reset the phone. For some reason I changed the active partition to b instead of a and magisk isnt installed but apps like snapchat don't work.
What's the best course of action to fix this? Twrp doesnt show up in recovery, its only the stock recovery. Do I need to reflash twrp on partition b and swap back to a?

Flash back to stock
Then do not lock bootloaders
Sent from my PH-1 using XDA Labs

I never locked bootloader, and do you have a good tutorial on going back to stock since the one I used didn't work that well?

zNiiC said:
I never locked bootloader, and do you have a good tutorial on going back to stock since the one I used didn't work that well?
Click to expand...
Click to collapse
This thread : https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Download one of the stock OTA firmwares and "flash_all.bat/sh"
This will flash both A/B partitions and take you back to stock.

tech_head said:
This thread : https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Download one of the stock OTA firmwares and "flash_all.bat/sh"
This will flash both A/B partitions and take you back to stock.
Click to expand...
Click to collapse
Hmm thats the guide I used. I'll try it again.

zNiiC said:
Hmm thats the guide I used. I'll try it again.
Click to expand...
Click to collapse
He's what I see for a "flash_all.bat/sh" for Oreo Beta2:
fastboot flash abl_a abl
fastboot flash abl_b abl
fastboot flash bluetooth_a bluetooth
fastboot flash bluetooth_b bluetooth
fastboot flash boot_a boot
fastboot flash boot_b boot
fastboot flash cmnlib_a cmnlib
fastboot flash cmnlib_b cmnlib
fastboot flash cmnlib64_a cmnlib64
fastboot flash cmnlib64_b cmnlib64
fastboot flash devcfg_a devcfg
fastboot flash devcfg_b devcfg
fastboot flash dsp_a dsp
fastboot flash dsp_b dsp
fastboot flash hyp_a hyp
fastboot flash hyp_b hyp
fastboot flash keymaster_a keymaster
fastboot flash keymaster_b keymaster
fastboot flash mdtp_a mdtp
fastboot flash mdtp_b mdtp
fastboot flash mdtpsecapp_a mdtpsecapp
fastboot flash mdtpsecapp_b mdtpsecapp
fastboot flash modem_a modem
fastboot flash modem_b modem
fastboot flash nvdef_a nvdef
fastboot flash nvdef_b nvdef
fastboot flash pmic_a pmic
fastboot flash pmic_b pmic
fastboot flash rpm_a rpm
fastboot flash rpm_b rpm
fastboot flash system_a system
fastboot flash system_b system
fastboot flash tz_a tz
fastboot flash tz_b tz
fastboot flash vendor_a vendor
fastboot flash vendor_b vendor
fastboot flash xbl_a xbl
fastboot flash xbl_b xbl
Note that both partitions are flashed.
Look at the flash commands in the version you want to go to and make sure BOTH slots are being flashed.

I'll double check that too. Also, do I need the /sh at the end of the .bat file? I don't remember reading that I need to use that on windows.

zNiiC said:
I'll double check that too. Also, do I need the /sh at the end of the .bat file? I don't remember reading that I need to use that on windows.
Click to expand...
Click to collapse
I'm sure you have solved this, but for the record, it's either. .bat or .sh depending on whether you are using windows or Linux.

Can't get hard bricked OP8P to EDL mode

Hello Everyone
My Oneplus 8 Pro won't turn on at all , not to recovery mode , not to fastboot mode , not to EDL mode , not even to charge... nothing
And I'm pretty sure everything is set up correctly , the msm tool , the qualcomm drivers , the cable and the port because i have an old oneplus 3t which i'm using for now and it got recognized in the msm tool as soon as i connected it
Here is some context of what happened before my Oneplus 8 Pro died :
I never flashed any custom roms on it , i've been using the stock firmware with root the whole time
I had a custom kernel installed on Android 11 before updating to Android 12 , when i updated to Android 12 (OTA update) the kernel went back to the stock one
after updating to Android 12 there was another OTA update that always fails to install (I believe it was 11.c.16), i got tired of it so i decided to manually updating to the latest firmware including that 11.c.16 incremental update and be done with it
I couldn't sideload it using TWRP becuase i couldn't install TWRP , everytime i tried to flash it using fastboot it seems like it succeeded but when i boot to recovery it boots to fastboot mode
so i googled how to install a firmware using fastboot commands , i found a method to flash the files one by one after extracting them using payload dumper and i tried it , when i was done flashing the files , as soon as i hit enter on the last command to reboot the phone it went to a black screen and has been dead ever since
Here are the fastboot commands i used to flash the firmware :
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot -w
fastboot reboot
Sorry for taking so long , I'm desperate
Any kind of help , suggestions or ideas are much appreciated

I haven't been keeping up on that thread since since it doesn't affect me, but I think you fell into the known "OOS Deathtrap" that's been explained here.
Like I said - no idea if it has a solution, or even if there is one now, but it couldn't hurt to read it.

Well... at least now i know what caused the issue , unfortunately i don't think there is a solution other than replacing the motherboard (which was the the solution i wanted to avoid)
I think it's time to say goodbye to oneplus
I wish i had read that article before flashing , Oneplus should put a disclaimer or a warning or something

Question Downgraded. Phone works. But no customization

So I flashed my phone using the fastboot ROM from this page.
reindex-ot.github.io
Re*Index. GitHub Pages
reindex-ot.github.io
I downgraded, even upgraded using this method to get root and call recording. All went fine, downgrading, upgrading, root, etc. Except no matter what I do all I get is a brown background with no customization options in any of the ROMS. They all produce the same.
What am I missing here ?
Thanks !

That's it . That's all !

rogerrulez said:
So I flashed my phone using the fastboot ROM from this page.
reindex-ot.github.io
Re*Index. GitHub Pages
reindex-ot.github.io
I downgraded, even upgraded using this method to get root and call recording. All went fine, downgrading, upgrading, root, etc. Except no matter what I do all I get is a brown background with no customization options in any of the ROMS. They all produce the same.
What am I missing here ?
Thanks !
Click to expand...
Click to collapse
What more you think of that ROM has?

solomon.rajan said:
What more you think of that ROM has
Click to expand...
Click to collapse
solomon.rajan said:
What more you think of that ROM has?
Click to expand...
Click to collapse
Seriously ?

Can't help you unless you mention what you're looking for

What i do if i like to go "stock" to do clean updates or to simply set everything to default.
I restore/downgrade to 1.1.3 (all partitions + super partition) and update via ADB sideload or system update.
Never had "missing wallpapers" if i get your problem correctly.

xtcislove said:
What i do if i like to go "stock" to do clean updates or to simply set everything to default.
I restore/downgrade to 1.1.3 (all partitions + super partition) and update via ADB sideload or system update.
Never had "missing wallpapers" if i get your problem correctly.
Click to expand...
Click to collapse
Yeah that’s what I would like to do. There is an msmtool out there but there are no links to download the necessary files.

rogerrulez said:
Yeah that’s what I would like to do. There is an msmtool out there but there are no links to download the necessary files.
Click to expand...
Click to collapse
Tool found here:
unbrick tool- EDL Flash-Read-Repair Region Change tool
unbrick tool Now available for Nothing Phone1.. Features: Read Firmware (EDL) (locked bootloader) Flash Firmware (EDL) (locked bootloader) backup EFS (EDL) (locked bootloader) Wipe FRP & userdata (EDL) (locked bootloader) Size: 2.7GB Version...
forum.xda-developers.com
That hard part is getting your phone to boot to EDL (if you're bricked) otherwise that'll shoot you straight back to stock with bootloader still unlocked.

rogerrulez said:
Yeah that’s what I would like to do. There is an msmtool out there but there are no links to download the necessary files.
Click to expand...
Click to collapse
How to unbrick Nothing Phone 1 fastboot bootloop
Welcome to this unbrick tutorial NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours. I do not suggest following this tutorial if...
forum.xda-developers.com
You need EEA fastboot rom of 1.1.3 and the super.img from post 2.
This tutorial works fine.
I simply have a batch script with this content:
Code:
cd /d F:\Android\NothingPhone1\Other\platform-tools_r33.0.2-windows
fastboot -w
fastboot --set-active=a
fastboot reboot fastboot
fastboot flash super F:\Android\NothingPhone1\Firmware\1.1.3_EEA_super_backup\super.img
fastboot flash abl_a F:\Android\NothingPhone1\Firmware\1.1.3\abl.img
fastboot flash aop_a F:\Android\NothingPhone1\Firmware\1.1.3\aop.img
fastboot flash bluetooth_a F:\Android\NothingPhone1\Firmware\1.1.3\bluetooth.img
fastboot flash boot_a F:\Android\NothingPhone1\Firmware\1.1.3\boot.img
fastboot flash cpucp_a F:\Android\NothingPhone1\Firmware\1.1.3\cpucp.img
fastboot flash devcfg_a F:\Android\NothingPhone1\Firmware\1.1.3\devcfg.img
fastboot flash dsp_a F:\Android\NothingPhone1\Firmware\1.1.3\dsp.img
fastboot flash dtbo_a F:\Android\NothingPhone1\Firmware\1.1.3\dtbo.img
fastboot flash featenabler_a F:\Android\NothingPhone1\Firmware\1.1.3\featenabler.img
fastboot flash hyp_a F:\Android\NothingPhone1\Firmware\1.1.3\hyp.img
fastboot flash imagefv_a F:\Android\NothingPhone1\Firmware\1.1.3\imagefv.img
fastboot flash keymaster_a F:\Android\NothingPhone1\Firmware\1.1.3\keymaster.img
fastboot flash modem_a F:\Android\NothingPhone1\Firmware\1.1.3\modem.img
fastboot flash multiimgoem_a F:\Android\NothingPhone1\Firmware\1.1.3\multiimgoem.img
fastboot flash odm_a F:\Android\NothingPhone1\Firmware\1.1.3\odm.img
fastboot flash product_a F:\Android\NothingPhone1\Firmware\1.1.3\product.img
fastboot flash qupfw_a F:\Android\NothingPhone1\Firmware\1.1.3\qupfw.img
fastboot flash shrm_a F:\Android\NothingPhone1\Firmware\1.1.3\shrm.img
fastboot flash system_a F:\Android\NothingPhone1\Firmware\1.1.3\system.img
fastboot flash system_ext_a F:\Android\NothingPhone1\Firmware\1.1.3\system_ext.img
fastboot flash tz_a F:\Android\NothingPhone1\Firmware\1.1.3\tz.img
fastboot flash uefisecapp_a F:\Android\NothingPhone1\Firmware\1.1.3\uefisecapp.img
fastboot flash vbmeta_a F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta.img
fastboot flash vbmeta_system_a F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta_system.img
fastboot flash vendor_a F:\Android\NothingPhone1\Firmware\1.1.3\vendor.img
fastboot flash vendor_boot_a F:\Android\NothingPhone1\Firmware\1.1.3\vendor_boot.img
fastboot flash xbl_a F:\Android\NothingPhone1\Firmware\1.1.3\xbl.img
fastboot flash xbl_config_a F:\Android\NothingPhone1\Firmware\1.1.3\xbl_config.img
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot fastboot
fastboot flash abl_b F:\Android\NothingPhone1\Firmware\1.1.3\abl.img
fastboot flash aop_b F:\Android\NothingPhone1\Firmware\1.1.3\aop.img
fastboot flash bluetooth_b F:\Android\NothingPhone1\Firmware\1.1.3\bluetooth.img
fastboot flash boot_b F:\Android\NothingPhone1\Firmware\1.1.3\boot.img
fastboot flash cpucp_b F:\Android\NothingPhone1\Firmware\1.1.3\cpucp.img
fastboot flash devcfg_b F:\Android\NothingPhone1\Firmware\1.1.3\devcfg.img
fastboot flash dsp_b F:\Android\NothingPhone1\Firmware\1.1.3\dsp.img
fastboot flash dtbo_b F:\Android\NothingPhone1\Firmware\1.1.3\dtbo.img
fastboot flash featenabler_b F:\Android\NothingPhone1\Firmware\1.1.3\featenabler.img
fastboot flash hyp_b F:\Android\NothingPhone1\Firmware\1.1.3\hyp.img
fastboot flash imagefv_b F:\Android\NothingPhone1\Firmware\1.1.3\imagefv.img
fastboot flash keymaster_b F:\Android\NothingPhone1\Firmware\1.1.3\keymaster.img
fastboot flash modem_b F:\Android\NothingPhone1\Firmware\1.1.3\modem.img
fastboot flash multiimgoem_b F:\Android\NothingPhone1\Firmware\1.1.3\multiimgoem.img
fastboot flash odm_b F:\Android\NothingPhone1\Firmware\1.1.3\odm.img
fastboot flash product_b F:\Android\NothingPhone1\Firmware\1.1.3\product.img
fastboot flash qupfw_b F:\Android\NothingPhone1\Firmware\1.1.3\qupfw.img
fastboot flash shrm_b F:\Android\NothingPhone1\Firmware\1.1.3\shrm.img
fastboot flash system_b F:\Android\NothingPhone1\Firmware\1.1.3\system.img
fastboot flash system_ext_b F:\Android\NothingPhone1\Firmware\1.1.3\system_ext.img
fastboot flash tz_b F:\Android\NothingPhone1\Firmware\1.1.3\tz.img
fastboot flash uefisecapp_b F:\Android\NothingPhone1\Firmware\1.1.3\uefisecapp.img
fastboot flash vbmeta_b F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta.img
fastboot flash vbmeta_system_b F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta_system.img
fastboot flash vendor_b F:\Android\NothingPhone1\Firmware\1.1.3\vendor.img
fastboot flash vendor_boot_b F:\Android\NothingPhone1\Firmware\1.1.3\vendor_boot.img
fastboot flash xbl_b F:\Android\NothingPhone1\Firmware\1.1.3\xbl.img
fastboot flash xbl_config_b F:\Android\NothingPhone1\Firmware\1.1.3\xbl_config.img
fastboot reboot bootloader
fastboot --set-active=a
fastboot reboot
pause