Related
Hi.
I think I should stop and ask for advice before trying anything else.
I have just received a 32gb D802 (International I think) with build KOT49I.D80220b and baseband M8974A-AAAANAZM-1.0.190082
It was pre-rooted. Root worked fine after updating SU binary. I downloaded twrp 2.8.0.1 from within flashify and installed it.
It displayed status 7 during recovery flash. I notice it already had philz touch recovery installed at the time rather than stock recovery.
I then tried D802_AutoRec.apk
On reboot it is stuck in fastboot mode displaying "Fastboot mode started".
I've plugged it in to usb on pc after installing minimal ADB.
What's my next step? I'm worried it may not be charging and I have limited time before it dies?
Edit: To correct sequence of events.
link
bender_007 said:
link
Click to expand...
Click to collapse
Thank you.
I ran pokreni.bat and all operations appeared to complete successfully
However on reboot following 15 seconds pressing power button it just goes back to fastboot mode
Try powering off the device.
Hold volume up - then connect usb to computer.
Is download mode alive ?
anyway - which package(philz) did you flash anyway ?
bender_007 said:
Try powering off the device.
Hold volume up - then connect usb to computer.
Is download mode alive ?
anyway - which package did you flash anyway ?
Click to expand...
Click to collapse
It doesn't power off fully it reboots. If I hold (and continue to hold) volume up immediately following exit from fastboot mode it just goes back to fastboot mode.
All I've flashed since receiving the phone is twrp 2.8.0.1 from within Autorec
Edit, sorry I'm wrong. I downloaded 2.8.0.1 from within flashify
I ask because of this: "I notice it already had philz touch recovery installed at the time rather than stock recovery."
Autorec installs 2.7.0.0
So if you downloaded the right version of 2.8.0.1 / 2.8.0.2 it should work (updating = installing from current TWRP - not philz)
EDIT: long hold the power..long long..until it's off ( cable should be disconnected)..then when you're sure it's off - hold volume up and connect to cable and obviously PC.
bender_007 said:
I ask because of this: "I notice it already had philz touch recovery installed at the time rather than stock recovery."
Autorec installs 2.7.0.0
So if you downloaded the right version of 2.8.0.1 / 2.8.0.2 it should work (updating = installing from current TWRP - not philz)
EDIT: long hold the power..long long..until it's off ( cable should be disconnected)..then when you're sure it's off - hold volume up and connect to cable and obviously PC.
Click to expand...
Click to collapse
Philz was already installed when I received the phone but I didnt realize until I tried to flash twrp with flashify.
OK, I can get it to power off completely then when holding volume up and plugging it into USB/PC it briefly enters download mode then goes to fastboot again
EDIT: Should I try this recovery http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705 then renaming it to recovery.img and re-running the .bat file you linked to previously after replacing the recovery.img there with the new one?
Edit2: Just to be clear (I was confusing myself) I did manage to run D802_AutoRec.apk immediately prior to the fastboot problem.
Edit3: I can get it to the factory data reset screen when attempting to enter recovery but it goes back to fastboot after I select Yes twice
Edit4: I have the 32gb D802. Perhaps something from here would help? http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware and I could fastboot flash the relevant partitions. I dont like the look of 16G Partitions though seeing as I have a 32gb G2.
Is there any more info I can provide? I bought it from http://www.aliexpress.com/item/Orig...uad-core-5-2-inch-Refurbished/2037229256.html where it says it was russian multilanguage although it came setup in English. It does say LG-D802 on the back and packaging just so you know I haven't confused the model.
obvious said:
Is there any more info I can provide? I bought it from http://www.aliexpress.com/item/Orig...uad-core-5-2-inch-Refurbished/2037229256.html where it says it was russian multilanguage although it came setup in English. It does say LG-D802 on the back and packaging just so you know I haven't confused the model.
Click to expand...
Click to collapse
Send me imei so i can find the right kdz for it or use your imei so you can download the propper kdz, extract it etc.
bender_007 said:
Send me imei so i can find the right kdz for it or use your imei so you can download the propper kdz, extract it etc.
Click to expand...
Click to collapse
Serial and IMEI sent. Thank you
Downloading D80220C_00 from http://lg-firmware-rom.com/
Edit: Got it.
Edit2: Extracted DZ - Whole bunch of BIN files
Good. Now take aboot, boot, laf...rename them proper to aboot.img, boot.img, laf.img
bender_007 said:
Good. Now take aboot, boot, laf...rename them proper to aboot.img, boot.img, laf.img
Click to expand...
Click to collapse
Done.
Anticpating the next move I have copied them into fastboot.exe folder on PC where I have the following .bat file from earlier
Code:
fastboot erase laf
fastboot flash laf laf.img
fastboot flash boot boot.img
fastboot flash aboot aboot.img
fastboot erase recovery
fastboot flash recovery recovery.img
Should I remove the recovery.img or use another?
Edit: Nail biting
For now remove the recovery. See if you can get dload mode. Remove also the lines mentioning recovery
bender_007 said:
For now remove the recovery. See if you can get dload mode. Remove also the lines mentioning recovery
Click to expand...
Click to collapse
Powered off, held volume up, plugged in. Cant get into download mode. Goes to fastboot
Tried getting into recovery but that goes to fastboot as well
Try putting the recovery then also
bender_007 said:
Try putting the recovery then also
Click to expand...
Click to collapse
flashed extracted recovery. No errors. Cant get into recovery or download mode though. Just goes back to fastboot.
bender_007 has been a great help via PM. Thanks. I hope he doesn't mind me asking another question here.
I'm at the stage where I downloaded and installed the recommended kdz rom based on imei number but when I flash it it's Korean and the touch screen registers touches in a different place so it's pretty much unusable.
I'd read that other 32GB D802 roms should be safe to flash so I tried the EE 32GB one from http://storagecow.eu/index.php?dir=Xda/LG+G2/Stock/United+Kingdom/ - This one installs but bootloops after a while (kernel panic?) and the touch screen mis-registration issue is still present.
All ideas gratefully received
Oh..btw..I see now it says refurbished. Can you open it up somehow and see if there are other seals ?
Or at least try flashing older firmware and give it on their warranty (if there is any warranty )
bender_007 said:
Oh..btw..I see now it says refurbished. Can you open it up somehow and see if there are other seals ?
Or at least try flashing older firmware and give it on their warranty (if there is any warranty )
Click to expand...
Click to collapse
Can the variant be identified from these pics?
EDIT: Fixed! Big thanks to @S0wL , @bkores , @tamahouse02 and @tron1 for the help. I made a guide to help other people with the same problem:
Guide to get TWRP again HERE
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Try the menu on the boot screen.
Choose an username... said:
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Click to expand...
Click to collapse
Sounds like the issue is with the ROM like it is somehow blocking you from accessing bootloader mode. It's definitely not my toolkit.
Choose an username... said:
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Click to expand...
Click to collapse
Feel the same, 7.1.1 stock recovery is evil, it keep coming back after flash twrp. LOL
Here what I didi to get twrp on 7.1.1:
1. Use axon7tool -w recovery (twrp of couse)
2. Watch closely the cmd, when it said "Successful!","Reboot in 5 second" - unplug your phone
3. Use Volume Up + Power to get to recovery (twrp)
4. Mount > Mount System (dont check read only)
5. Flash something - I don't know - But I get the feeling that it stop stock recovery coming back - I personally flash Chinese Modem (because I have to ))
6. Reboot system
@bkores Yeah I'm pretty sure it's not your toolkit since I can't access it even with key comb, adb, option on the unl bl page...
@lafester Nope, tried many times. It just boots to normal whenever I select fastboot
@tamahouse02 Well I believe that should work, but I can't get axon7tool not to crash... I'll keep trying, maybe it's a driver or sth.
Choose an username... said:
@bkores Yeah I'm pretty sure it's not your toolkit since I can't access it even with key comb, adb, option on the unl bl page...
@lafester Nope, tried many times. It just boots to normal whenever I select fastboot
@tamahouse02 Well I believe that should work, but I can't get axon7tool not to crash... I'll keep trying, maybe it's a driver or sth.
Click to expand...
Click to collapse
Have you restart after install zadig driver?
1. From system: adb reboot edl
2. Install zadig driver
3. Hold "Volume Up + Power"
4. Enter system again: adb reboot edl
5. axon7tool -w recovery
tamahouse02 said:
Have you restart after install zadig driver?
1. From system: adb reboot edl
2. Install zadig driver
3. Hold "Volume Up + Power"
4. Enter system again: adb reboot edl
5. axon7tool -w recovery
Click to expand...
Click to collapse
yes, like 4 times already. I even used the stock Qualcomm COM3 drivers... no dice.
the thing is that I had to do the same when I did the stuff on android 6 and it worked after some time. I even wrote the procedure on another thread xd
Choose an username... said:
yes, like 4 times already. I even used the stock Qualcomm COM3 drivers... no dice.
the thing is that I had to do the same when I did the stuff on android 6 and it worked after some time. I even wrote the procedure on another thread xd
Click to expand...
Click to collapse
Not same my axon7tool. I use this https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Bootloader Mode is Disable/strip in G variant, and if this is how ZTE is headed to future updates it seems like U will have a Disable Bootloader Mode as well.
If you guy can rollback to MM , you can Unlock there using @bkores tool.
DrakenFX said:
Bootloader Mode is Disable/strip in G variant, and if this is how ZTE is headed to future updates it seems like U will have a Disable Bootloader Mode as well.
If you guy can rollback to MM , you can Unlock there using @bkores tool.
Click to expand...
Click to collapse
I was thinking about that, but does mifavor let you roll back from an SD update? I'll try later, but i doubt it.
Besides from that is there any way to flash stuff from the stock recovery? It tells me that ZIPs have to be signed only
tamahouse02 said:
Feel the same, 7.1.1 stock recovery is evil, it keep coming back after flash twrp. LOL
Here what I didi to get twrp on 7.1.1:
1. Use axon7tool -w recovery (twrp of couse)
2. Watch closely the cmd, when it said "Successful!","Reboot in 5 second" - unplug your phone
3. Use Volume Up + Power to get to recovery (twrp)
4. Mount > Mount System (dont check read only)
5. Flash something - I don't know - But I get the feeling that it stop stock recovery coming back - I personally flash Chinese Modem (because I have to ))
6. Reboot system
Click to expand...
Click to collapse
In step 1, which TWRP version did you use? The latest 3.1.0.-0 ?
dnlilas said:
In step 1, which TWRP version did you use? The latest 3.1.0.-0 ?
Click to expand...
Click to collapse
Official 3.0.4.1
@tamahouse02
The latest "official" TWRP is at TWRP site https://twrp.me/devices/zteaxon7.html , version 3.1.0-0.
Is there any problem using it instead of the previous "official" 3.0.4.1 ?
Edit: I also read on TWRP site:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
This is in sync with your information requiring to reboot immediately to TWRP (step 2 and 3).
dnlilas said:
@tamahouse02
The latest "official" TWRP is at TWRP site https://twrp.me/devices/zteaxon7.html , version 3.1.0-0.
Is there any problem using it instead of the previous "official" 3.0.4.1 ?
Edit: I also read on TWRP site:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
This is in sync with your information requiring to reboot immediately to TWRP (step 2 and 3).
Click to expand...
Click to collapse
I use 3.0.4.1 because I flash plenty things before without any issue, so I keep using it.
After write recovery by axon7tool, it's reboot automatically and override the recovery, that why I have to unplug to stop the reboot, and also flash all I can - fortunaeally​ it also stop recovery be overrided
@tamahouse02 sorry to ask, but is the a7tool of the link a fixed version? how does it differ from the one i have?
I've been in the same situation like you @Choose an username... Updated to nougat on G model and I had not bootloader. This is what I did :
1. Downloaded the tool from here https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
2. Installed the driver using the install driver option that you can choose once you connect you phone to your computer
3. Use the tool to perform the unlock bootloader command again even though you have unlocked it before
4. Use the tool to install twrp, it will boot the phone in twrp
5. Flash Supersu before you boot the system first time after flashing twrp
5. Install whatever version of android want after
@S0wL Funny, I had to use Zadig to make it work. I'll try r n, thx
Choose an username... said:
@S0wL Funny, I had to use Zadig to make it work. I'll try r n, thx
Click to expand...
Click to collapse
Use Zadig then and let me know if it worked
@S0wL I can't use bootloader unlock on it, says "This option does not support your device!"
How did you do this??
Choose an username... said:
@tamahouse02 sorry to ask, but is the a7tool of the link a fixed version? how does it differ from the one i have?
Click to expand...
Click to collapse
I try your version once, but it seems not work for me, so I keep using the old one.
---------- Post added at 03:42 AM ---------- Previous post was at 03:39 AM ----------
Choose an username... said:
@S0wL I can't use bootloader unlock on it, says "This option does not support your device!"
How did you do this??
Click to expand...
Click to collapse
I thought you had already unlocked bootloader? Why have you done it twice?
I have a LG K20 plus with t mobile as the carrier. I believe the model should be TP260. I mistakenly restored a twrp backup from a metro pcs phone that I got from this site coincidentally. Now my phone drops calls and data frequently and shows metro pcs on bootup vs tmobile. I have a kdz file but it won't flash because it now also thinks the model is MP260...not TP260 and says it's a mismatch. Any ideas on how I can get a restore for tmobile to try to reset the phone?
Just bumping
i could use a restore too. I installed super SU root and lost access to android pay. I wasnt to try that magisk root
I restored mine with the linked files.
install LG driver (uninstall any other drivers first)
install LGUP
remove battery from phone and replace
hold volume up key
insert USB while holding down volume up key
phone will boot to download mode
drivers will find phone
run UPPERCUT.exe
UPPERCUT.exe will launch LGUP with phone connected. if phone is not connected try again.
in LGUP lower window browse to TP26010k_00_0316.kdz
choose UPGRADE option in LGUP
click START in LGUP
factory ROM and Recovery will be installed, bootloader will still be unlocked
https://drive.google.com/open?id=0BygTApD1iNSSb3pCcU9RRlV1MVE
magisk can be installed using the same method as superSU. Mine is working along with AndroidPay
colemanimal said:
I restored mine with the linked files.
install LG driver (uninstall any other drivers first)
install LGUP
remove battery from phone and replace
hold volume up key
insert USB while holding down volume up key
phone will boot to download mode
drivers will find phone
run UPPERCUT.exe
UPPERCUT.exe will launch LGUP with phone connected. if phone is not connected try again.
in LGUP lower window browse to TP26010k_00_0316.kdz
choose UPGRADE option in LGUP
click START in LGUP
factory ROM and Recovery will be installed, bootloader will still be unlocked
https://drive.google.com/open?id=0BygTApD1iNSSb3pCcU9RRlV1MVE
magisk can be installed using the same method as superSU. Mine is working along with AndroidPay
Click to expand...
Click to collapse
You were able to install TWRP after this process with the TP26010k_00_0316.kdz?
I am on TP26010E and don't want to upgrade to TP26010k if TWRP cannot be flashed as it has been stated here.
Yeah, you have to perform OEM unlock again, but I have been able to flash TWRP after flashing the previously attached .kdz with the LGUP tool
colemanimal said:
I restored mine with the linked files.
install LG driver (uninstall any other drivers first)
install LGUP
remove battery from phone and replace
hold volume up key
insert USB while holding down volume up key
phone will boot to download mode
drivers will find phone
run UPPERCUT.exe
UPPERCUT.exe will launch LGUP with phone connected. if phone is not connected try again.
in LGUP lower window browse to TP26010k_00_0316.kdz
choose UPGRADE option in LGUP
click START in LGUP
factory ROM and Recovery will be installed, bootloader will still be unlocked
https://drive.google.com/open?id=0BygTApD1iNSSb3pCcU9RRlV1MVE
magisk can be installed using the same method as superSU. Mine is working along with AndroidPay
Click to expand...
Click to collapse
Can I install this kdz from twrp and install supersu?
no, you have to use LGUP tool. This is a LG image that will flash everything including your recovery partition, and not a flashable ROM image.
You flash root through TWRP, you use LGUP for kdz as the user above said rom flashing and kdz flashing are two different things
See this post which reflects the new kdz available https://forum.xda-developers.com/showpost.php?p=73690098&postcount=3
Just a Heads up there is a new version out, as of 9/01/17
MP26010r_00_0817.kdz
download link
https://lg-firmwares.com/lg-mp260-firmwares/
Click to expand...
Click to collapse
I flashed the modded ROM for MetroPCS, and couldn't flash kdz file because my phone was identified as MP260, instead of TP260.
I wiped the phone and re-locked the bootloader, and the phone would only boot into download mode, It gave a message about it being corrupted.
I took it back to TMO, and the sales people thought it was a virus, and replaced the device.
I've made a TWRP backup for anyone who runs into the same problem. This will fix your problem, so you can use the flash tools available for this device.
NOTE: I also provided Root tools and instructions for those Rooting for the first time.
1. Power off device, plug into computer, then hold volume up for download mode and let COM drivers install, you may need to change COM port to 41, through device manager.
2. In LGUP, choose upgrade or FOTA upgrade.
2. Once you flash firmware, you'll have to hit reset once or twice to get rid of the encryption failure notification.
3. Enjoy rooting your device again if you so choose.
ROOTING:
NOTE: Must have ADB & Fastboot setup already.
First you must unlock your bootloader.
1. In about phone settings, tap build number 6x to get developer settings, enable adb debugging and OEM unlock. Now plug into your computer.
2. Boot into Fastboot mode.
A. Open command prompt and type: adb reboot-bootloader.
B. Next type: fastboot oem unlock.
WARNING: You'll be prompted to factory reset device to protect your data. Your chance to turn back, if your brave then continue. Your device will factory reset, and you'll have to perform the first step again and you'll be ready to root.
1. To flash TWRP, plug into computer, then in command line navigate to where you have your recovery.img
A. adb reboot-bootloader
B. fastboot flash recovery recovery.img
2. Pull battery and manually boot into recovery,
A. volume+down as soon as you see LG, release then press again quickly and hold, follow the steps provided.
3. Hit cancel for the encryption notice, and swipe to modify system.
4. You must format device to get rid of encryption message, so choose format and it will ask you to type, yes.
5. Stay in recovery and flash the no-encryption.zip, and Magisk, if you choose to use it for your SU manager. Stay in recovery.
6. Reboot into recovery, and then set up your TWRP environment.
7. Enjoy Root:laugh:
NOTE: If you decide to root again, try using Magisk for SU management. Magisk's mods are excellent, and can run along side Xposed. If you choose Magisk, do not flash SuperUser.zip
TWRP STOCK BACKUP
https://mega.nz/#F!a59RBICD!kOisA-eOxviWK07Dn182FA
LG tools w/ Latest kdz
https://mega.nz/#F!b9sWDBwR!LjhrhZgYXB-BNHUWE11tJw
Sent from my K20 Plus using XDA Labs
Question I have a metropcs k20 version.Can I flash the t-mobile Rom with any problems.Thanks
Rican39 said:
Question I have a metropcs k20 version.Can I flash the t-mobile Rom with any problems.Thanks
Click to expand...
Click to collapse
You could probably flash the TWRP back up. After that your device would be Identified as TP260, by the flash tools and you'd end up with the same issue I had, when you decided to go back to stock, so make a TWRP backup on external memory. The KDZ file most likely won't flash because it performs a DLL check, to match device with firmware.
blas4me said:
You could probably flash the TWRP back up. After that your device would be Identified as TP260, by the flash tools and you'd end up with the same issue I had, when you decided to go back to stock, so make a TWRP backup on external memory. The KDZ file most likely won't flash because it performs a DLL check, to match device with firmware.
Click to expand...
Click to collapse
Thanks for reply.And info
does anyone have an mp 260 zip rom for twrp before boot?
5(/!p7 kiddie said:
does anyone have an mp 260 zip rom for twrp before boot?
Click to expand...
Click to collapse
I've got backup after unlock Bootloader and before root. Pretty sure it's got recovery on it. I always make a backup asap. It's the mp26010t (I had the November patch but some reason after root it says Oct).
Is that what you need?
Pm me if this is what you need and I'll send you a link
I have a Metro LG K20 Plus phone and want to change the firmware to T-Mobile. I have not been successful doing this as I always get invalid firmware, because LG UP recognizes the phone as a metro phone. Is there a way to succeed in getting the T-Mobile firmware on the phone?
thanks in advance.
lg k20 plus tmobil
lgup recognizes my model correctly as lg-tp260 on [com41] but it just sits there initializing for eternity. With my model highlighted I select it and I keep getting the error "LGUP cant load the model [C:\Program Files(x86)\LG Electronics\LGUP\model\com. I have installed lg air drive, lg bridge, lgup8994.dll, lgup for store. I desperately need to get this thing back to stock, I have the AICP rom installed but I dont like it. it was a mistake, if anyone can help I would appreciate it.
stovo06 said:
I've got backup after unlock Bootloader and before root. Pretty sure it's got recovery on it. I always make a backup asap. It's the mp26010t (I had the November patch but some reason after root it says Oct).
Is that what you need?
Click to expand...
Click to collapse
Could you PM me this link to the Metro PCS stock backup, if you still have it?
I had stock android 7, used the toolkit, "Unlocked" the bootloader, after that there was a part with erasing all data to factory due to an error, something along the lines there was a pin or password detected, and after I pressed reset the screen went black, and when it tries to boot it shows ZTE for a second and then it vibrates and shuts off instantly. So I can get it in to edl mode and I see the Qualcomm HS-USB QDLoader 9008 in my devices, but I can't find any thread to fix this. Tried flashing stock firmwares via MiFlash, no luck. And the thing is, most roms I download give me a batch of files in a zip, if I put them in a folder and try to flash I get this - Object reference not set to an instance of an object. Help asap, because I am having a horrible time using my partially destroyed S6 Edge Plus. If I spelled smth wrong sorry, Russian here.
This is what I had - My device is stuck on an 'Enter your password to start Android' screen.
Unfortunately this requires a factory reset.
1) Boot your device into recovery mode by pressing and holding the power and volume up buttons for 10-15 seconds.
2) Stock Recovery: Use the volume down key to go down to 'Wipe data/factory reset' and press power to select. Press the volume down key again to go down to 'Yes' and press power to select.
TWRP Recovery: Tap "Wipe" < Tap "Advanced Wipe" < Check the box next to "data" < Tap "Repair or change file system" < Tap "EXT4" < Swipe to confirm.
3) Reboot your device.
Jazkade said:
I had stock android 7, used the toolkit, "Unlocked" the bootloader, after that there was a part with erasing all data to factory due to an error, something along the lines there was a pin or password detected, and after I pressed reset the screen went black, and when it tries to boot it shows ZTE for a second and then it vibrates and shuts off instantly. So I can get it in to edl mode and I see the Qualcomm HS-USB QDLoader 9008 in my devices, but I can't find any thread to fix this. Tried flashing stock firmwares via MiFlash, no luck. And the thing is, most roms I download give me a batch of files in a zip, if I put them in a folder and try to flash I get this - Object reference not set to an instance of an object. Help asap, because I am having a horrible time using my partially destroyed S6 Edge Plus. If I spelled smth wrong sorry, Russian here.
Click to expand...
Click to collapse
I had a similar problem on my 2017U model after flashing a .zip that was supposed to remove the "bootloader is unlocked" screen that shows up after you unlock the bootloader. Long story short, the .zip wasn't meant for U models. Only G. So my phone was in a worse situation than yours and would not power on. You'll need to download an EDL recovery firmware .zip for your phone and place it within the toolkits folders manually and then go through the steps of the toolkit which I'll try to help you do.
First, download the full stock B09 (G) firmware from here. You can OTA update to the latest firmware after a successful flash. It's okay to flash an older firmware in this situation.
Once done, navigate to C:\Axon7Development\Axon7Toolkit\MiFlash\B09\ (copy/move the full .zip of the B09 firmware you downloaded in the first step into this folder) If the B09 folder doesn't exist under \MiFlash, create it manually.
Run the toolkit again from the start and type 11 "RESTORE TO STOCK/RECOVER FROM HARDBRICK (EDL)" and hit enter. On the next screen type in the number that will restore B09. It should tell you how to put the phone in EDL mode and automatically open MiFlash. Make sure to follow the steps and paste the directory path of the firmware in the top bar in MiFlash. After you pasted it his Flash and it should successfully flash the firmware. If it gives you an error or times out, unplug the phone and try a different USB port or USB cable. It's obviously recommended you use the one that came with the phone. My first attempt at MiFlash timed out and didn't flash anything. I tried a different USB port and then it flashed.
After it flashes the firmware, leave the phone plugged in and hold down the power button for about 10 seconds until it restarts out of EDL. From there you should have a working phone again with some exceptions. It'll be on an older firmware so I would recommend booting into stock recovery and factory resetting data and wiping your cache. Then restart the phone and do an OTA update to the latest firmware. After you reach the latest firmware you can then use the toolkit for whatever you need.
Sidenote, your English is very good considering you're Russian. No need to apologize because your post had no spelling errors. :highfive:
brian117 said:
I had a similar problem on my 2017U model after flashing a .zip that was supposed to remove the "bootloader is unlocked" screen that shows up after you unlock the bootloader. Long story short, the .zip wasn't meant for U models. Only G. So my phone was in a worse situation than yours and would not power on. You'll need to download an EDL recovery firmware .zip for your phone and place it within the toolkits folders manually and then go through the steps of the toolkit which I'll try to help you do.
First, download the full stock B09 (G) firmware from here. You can OTA update to the latest firmware after a successful flash. It's okay to flash an older firmware in this situation.
Once done, navigate to C:\Axon7Development\Axon7Toolkit\MiFlash\B09\ (copy/move the full .zip of the B09 firmware you downloaded in the first step into this folder) If the B09 folder doesn't exist under \MiFlash, create it manually.
Run the toolkit again from the start and type 11 "RESTORE TO STOCK/RECOVER FROM HARDBRICK (EDL)" and hit enter. On the next screen type in the number that will restore B09. It should tell you how to put the phone in EDL mode and automatically open MiFlash. Make sure to follow the steps and paste the directory path of the firmware in the top bar in MiFlash. After you pasted it his Flash and it should successfully flash the firmware. If it gives you an error or times out, unplug the phone and try a different USB port or USB cable. It's obviously recommended you use the one that came with the phone. My first attempt at MiFlash timed out and didn't flash anything. I tried a different USB port and then it flashed.
After it flashes the firmware, leave the phone plugged in and hold down the power button for about 10 seconds until it restarts out of EDL. From there you should have a working phone again with some exceptions. It'll be on an older firmware so I would recommend booting into stock recovery and factory resetting data and wiping your cache. Then restart the phone and do an OTA update to the latest firmware. After you reach the latest firmware you can then use the toolkit for whatever you need.
Sidenote, your English is very good considering you're Russian. No need to apologize because your post had no spelling errors. :highfive:
Click to expand...
Click to collapse
When I type in 11 I don't have any options, it forces me to download B10, but when it tries it fails.
Jazkade said:
When I type in 11 I don't have any options, it forces me to download B10, but when it tries it fails.
Click to expand...
Click to collapse
I haven't read what the other guy said, but basically you have to use miflash. just use my DFU unbrick guide but from the point where you short the testpad to enter EDL. But instead of opening the phone just put it in edl via adb reboot edl or holding vol+ - and inserting the cable
Jazkade said:
When I type in 11 I don't have any options, it forces me to download B10, but when it tries it fails.
Click to expand...
Click to collapse
Did you create the B09 folder in the MiFlash directory? I also had errors downloading firmwares through the toolkit, which is why I had to do it manually and move the firmware into the proper directory for the toolkit.
brian117 said:
Did you create the B09 folder in the MiFlash directory? I also had errors downloading firmwares through the toolkit, which is why I had to do it manually and move the firmware into the proper directory for the toolkit.
Click to expand...
Click to collapse
Yes I did
Choose an username... said:
I haven't read what the other guy said, but basically you have to use miflash. just use my DFU unbrick guide but from the point where you short the testpad to enter EDL. But instead of opening the phone just put it in edl via adb reboot edl or holding vol+ - and inserting the cable
Click to expand...
Click to collapse
Can you give me a link pls?
Choose an username... said:
I haven't read what the other guy said, but basically you have to use miflash. just use my DFU unbrick guide but from the point where you short the testpad to enter EDL. But instead of opening the phone just put it in edl via adb reboot edl or holding vol+ - and inserting the cable
Click to expand...
Click to collapse
Flashing in progress.. please may this work..
Oh yeis boiz, the phone is alive! And the main lol is, we have a guy that fixes devices for a living, and he was trashtalking that the Axon 7 is a trash phone and fixing it is a piece of cake, and he failed, and here I am thanks to you with a woring phone! I love you people, and xda in general!
EDIT: Seems you got it working. Congrats.
Jazkade said:
Oh yeis boiz, the phone is alive! And the main lol is, we have a guy that fixes devices for a living, and he was trashtalking that the Axon 7 is a trash phone and fixing it is a piece of cake, and he failed, and here I am thanks to you with a woring phone! I love you people, and xda in general!
Click to expand...
Click to collapse
Choose an username... said:
Click to expand...
Click to collapse
After I unlocked the bootloader via the toolkit by bkores, I get a message "To start android enter your password" even though it was a stock system with no password. Like I got every possible error and solved it and now this, just why?
Jazkade said:
After I unlocked the bootloader via the toolkit by bkores, I get a message "To start android enter your password" even though it was a stock system with no password. Like I got every possible error and solved it and now this, just why?
Click to expand...
Click to collapse
that's totally normal. Your internal storage is encrypted, you have to go into TWRP and format data (not wipe, format). Anyways by unlocking you lose all of your data so it's not like you lose anything
If it doesn't work, then you'll have to change the data partition's filesystem because it may be in F2FS. Change it back to ext4 if that happens
Choose an username... said:
that's totally normal. Your internal storage is encrypted, you have to go into TWRP and format data (not wipe, format). Anyways by unlocking you lose all of your data so it's not like you lose anything
If it doesn't work, then you'll have to change the data partition's filesystem because it may be in F2FS. Change it back to ext4 if that happens
Click to expand...
Click to collapse
I don't have TWRP, firs I Unlocked the bootloader, now I try to flash TWRP and get error due to the force encryption on Nougat, and I can't find a way to disable it, also now when I try to boot to stock recovery the led flashes for a milisecond and powers off.
Jazkade said:
I don't have TWRP, firs I Unlocked the bootloader, now I try to flash TWRP and get error due to the force encryption on Nougat, and I can't find a way to disable it, also now when I try to boot to stock recovery the led flashes for a milisecond and powers off.
Click to expand...
Click to collapse
Enter fastboot and type the command "fastboot erase userdata
Choose an username... said:
Enter fastboot and type the command "fastboot erase userdata
Click to expand...
Click to collapse
adb reboot fastboot and it just reboots normally.
Jazkade said:
adb reboot fastboot and it just reboots normally.
Click to expand...
Click to collapse
Well whatever then just install TWRP. Use controllerboy's guide
Choose an username... said:
Well whatever then just install TWRP. Use controllerboy's guide
Click to expand...
Click to collapse
idk how to downgrade to marshmellow.
Choose an username... said:
Well whatever then just install TWRP. Use controllerboy's guide
Click to expand...
Click to collapse
downgraded, unlocked, twrp is up and running
One of my costumer V20 is now stuck in fastboot.
Whatever I do, it's keep coming back to fastboot mode.
I can enter download mode, and try flash , even using the costum LG up, with upgrade option, partition DL option.
I use Box ( octopus, Z3x ).
I don't know what is wrong with this phone.
it's only going back to fastboot.
Any help is really apreciated.
Thank You.
sing2x said:
One of my costumer V20 is now stuck in fastboot.
Whatever I do, it's keep coming back to fastboot mode.
I can enter download mode, and try flash , even using the costum LG up, with upgrade option, partition DL option.
I use Box ( octopus, Z3x ).
I don't know what is wrong with this phone.
it's only going back to fastboot.
Any help is really apreciated.
Thank You.
Click to expand...
Click to collapse
What does using the "fastboot reboot" cmd do ?
Ak7J4 said:
What does using the "fastboot reboot" cmd do ?
Click to expand...
Click to collapse
It goes back straight to fastboot after LG logo
If you can get into download mode try the 'upgrade' option in lgup
It is stuck in fastboot because your customer tried to root it with lafsploit without unlocking the bootloader.
They have two choices:
1 - Send it to LG to have it repaired.
2 - Wait for me to finish lafsploit 2.0 which will unlock their bootloader, and their phone will just start working.
The partitions that hold the unlock information are not touched when you flash a KDZ, so no amount of flashing is going to fix it.
-- Brian
runningnak3d said:
It is stuck in fastboot because your customer tried to root it with lafsploit without unlocking the bootloader.
They have two choices:
1 - Send it to LG to have it repaired.
2 - Wait for me to finish lafsploit 2.0 which will unlock their bootloader, and their phone will just start working.
The partitions that hold the unlock information are not touched when you flash a KDZ, so no amount of flashing is going to fix it.
-- Brian
Click to expand...
Click to collapse
I think that's what happen, and I don't have any choice except to wait . Returning to LG is not an option.
Thank you very much sir.
did you get to solve this problem also have one stuck in fastboot mode but no download mode
boot loader seem to be lock
thee011 said:
did you get to solve this problem also have one stuck in fastboot mode but no download mode
boot loader seem to be lock
Click to expand...
Click to collapse
If you cant get into download mode by powering off, holding vol up and then plugging into a pc (no power button needed) then you dont have a phone anymore. Unless rooted via dirtysanta which replaces aboot (which provides fastboot), the stock fastboot mode of the h918 can't actually flash anything to the phone which means no unbricking with it; TWRP and download mode are only ways to restore firmware.
I know this is an old thread but my gf has the h918 which is unlocked with twrp Installed, she tried updating magisk from inside magisk and now she's stuck in fastboot mode .The fastboot reboot command does not reboot the phone I even booted into twrp and wiped cache any ideas?
wolf45801 said:
I know this is an old thread but my gf has the h918 which is unlocked with twrp Installed, she tried updating magisk from inside magisk and now she's stuck in fastboot mode .The fastboot reboot command does not reboot the phone I even booted into twrp and wiped cache any ideas?
Click to expand...
Click to collapse
This is a Magisk 20.2 issue there's at two threads in the LGV20 forum on how to recover
Sent from my LG-H910 using XDA Labs