i was successfully rooting my phone, using fastboot flash, i was thinking to use custom recovery but it need to unlock bootloader, i jog myself around google and found my self exhausted since none of their method work on my device, once i found a way to unlock my bootloader by downgrading the fastboot version, so i install the previous fastboot version with stock recovery on my phone, after that my phone start to reboot and stuck at asus logo, now its stuck at USB logo(clover view plus) now i pray to god to found solution to my problem rather i need dnx, ifwi, dnx osr, and fastboot .bin that worked with my device or any other way that make it through fastboot or droidboot again, i really really appreciate any working brain of yours
Related
Hi all,
I am new to this forum, but have some experience with rooting and custom roms(oneplus one and samsung)
Now with the Mi Max 3, which was unlocked, i have flashed the recovery twrp-3.2.3-0-nitrogen.img, but I did not realize that
i had to reboot into this recovery from the fastboot mode.
so I endet up with a locked bootloader and bottloop and am not able to unlock the bootloader again.
I think my only solution is the test-point method and a EDL authorized account.
Some help would be greatly appreciated.
thanks
Henry
You don't have to boot into the bootloader from fastboot mode, you can press the power button and volume up button like on almost all other Android phones to boot into TWRP recovery. Sometimes it takes a few attempts to get right, but you should learn how to do it eventually.
Unfortunately it sounds like you had one of the dodgy re-sold Chinese models that had been re-flashed with Global firmware and it's locked your bootloader again on reboot.
Your only option is to use the official Miui Flash tool to boot into fastboot mode, flash the latest Global Developer ROM, and then sign in with your account and apply to unlock the bootloader again using the Miui unlock program. It may be instant but, they'll probably make you wait 720 hours, as the entire point of the program was to stop phones like yours being re-sold outside China.
At least you'll have a usable, non-bricked device though.
Thanks for your answer.
now I have opened the backcover (yes was much work ( I succeded without destroying something) and could apply the test point method to get into the lde mode.
Win10 shows it as qualcomxx at com 3
what is the best way now to awake it to life again? even without unlocking.
hi,
with the test point method I could flash the chinese rom, and the mi max 3 is awaken to life again!
The bootloader is still locked.
I have applied for unlocking, but have to wait some 15 days.
One tip: if the case is open, one can apply a little bit of silicon grease to the small pins on the side of the plastic frame
before closing it. Opening it again is much easier then.
One question: if I replace the recovery.img of the chinese rom with a TWRP image (renamed to recovery.img)
and flash that modified rom with the test point method, could this probaly work?
With a working TWRP one could install other roms without unlocking bootloader.
If yes, which TWRP would you apply?
Thanks
freedoc said:
Hi all,
I am new to this forum, but have some experience with rooting and custom roms(oneplus one and samsung)
Now with the Mi Max 3, which was unlocked, i have flashed the recovery twrp-3.2.3-0-nitrogen.img, but I did not realize that
i had to reboot into this recovery from the fastboot mode.
so I endet up with a locked bootloader and bottloop and am not able to unlock the bootloader again.
I think my only solution is the test-point method and a EDL authorized account.
Some help would be greatly appreciated.
thanks
Henry
Click to expand...
Click to collapse
Flashing a recovery should not lock your bootloader, so I don't know how you did it. Note, that if you are using Xiaomi's firmware tool, you should not forget about unticking the box to lock the bootloader. But I would suggest to stay away from that tool and go command line instead with fastboot.
If you can access fastboot, I'd recommend to flash an official fastboot tgz ROM of your choice. Official ROM should boot even with an unlocked bootloader and you may start all over again more carefully.
So I think you might be able to avoid using EDL mode at this stage.
probally I forgot to untick that box. The bootloader is locked and I have to wait 319 hours.
I have got to love the test point EDL method which is simple and effective, and gave me control over the device again.
If I flash again the chinese fastboot rom (in which I have changed the original recovery.img into TWRP.img, named recovery.img) via the EDL
will that give me an installt TWRP (still with locked bootloader, but possible to install custom roms) or will i have a brick again?
thanks
freedoc said:
probally I forgot to untick that box. The bootloader is locked and I have to wait 319 hours.
I have got to love the test point EDL method which is simple and effective, and gave me control over the device again.
If I flash again the chinese fastboot rom (in which I have changed the original recovery.img into TWRP.img, named recovery.img) via the EDL
will that give me an installt TWRP (still with locked bootloader, but possible to install custom roms) or will i have a brick again?
thanks
Click to expand...
Click to collapse
Only you can answer that question by trying it out. Are you sure you have to wait for the unlocking again? Double check that! As I know you also need a priviliged xiaomi account to be able to resurrect a device in EDL mode.
Is there any way to unlock the non european variants of G8s? G810EA, not EAW.
Tried on LG dev page it refuses saying not supported but my fastboot shows option to write a BL unlock key and says it can be unlocked.
Any possibility of getting unlocked BL another way? Im open to unofficial methods.
Many thanks
corpsegrinder62 said:
Is there any way to unlock the non european variants of G8s? G810EA, not EAW.
Tried on LG dev page it refuses saying not supported but my fastboot shows option to write a BL unlock key and says it can be unlocked.
Any possibility of getting unlocked BL another way? Im open to unofficial methods.
Many thanks
Click to expand...
Click to collapse
Well I think the bl unlock method for a while for v40 and g7 was crossflashing to a firmware with fastboot and fastboot booting (not flashing) a magisk patched boot IMG, then using the root to dd flash the engineering abl which allows unlocking. I don't know if that would work for g8s without a brick or if your fastboot even allows fastboot booting
antintin said:
Well I think the bl unlock method for a while for v40 and g7 was crossflashing to a firmware with fastboot and fastboot booting (not flashing) a magisk patched boot IMG, then using the root to dd flash the engineering abl which allows unlocking. I don't know if that would work for g8s without a brick or if your fastboot even allows fastboot booting
Click to expand...
Click to collapse
Thanks alot for the response, that's very hopeful! any place you could point me to the process of flashing the engineering abl? not even sure were to start looking for it on the G8s. P.S im not a noob just a noob to LG
I think my fastboot would allow booting as it does respond to basic commands i've tried so far, only issue is the boot.img's out there are all for the EAW version, anyway to decompile a boot img from a kdz?
Thanks in advance!
corpsegrinder62 said:
Thanks alot for the response, that's very hopeful! any place you could point me to the process of flashing the engineering abl? not even sure were to start looking for it on the G8s. P.S im not a noob just a noob to LG
I think my fastboot would allow booting as it does respond to basic commands i've tried so far, only issue is the boot.img's out there are all for the EAW version, anyway to decompile a boot img from a kdz?
Thanks in advance!
Click to expand...
Click to collapse
Yeah, download the kdz for the exact software version you're on, look up kdztools steadfasterx, go on the GitHub, extract the boot IMG, and patch it in the magisk app. Then try fastboot booting it; flashing it without bl unlock would make it not let you boot, but since fastboot booting worked on g7 and v40, I'd assume it would be ok. You might want to join the telegram group and find someone who knows for certain though
antintin said:
Yeah, download the kdz for the exact software version you're on, look up kdztools steadfasterx, go on the GitHub, extract the boot IMG, and patch it in the magisk app. Then try fastboot booting it; flashing it without bl unlock would make it not let you boot, but since fastboot booting worked on g7 and v40, I'd assume it would be ok. You might want to join the telegram group and find someone who knows for certain though
Click to expand...
Click to collapse
Thanks, im going to try this really appreciate your help here. and the abl any idea how i go about flashing that to unlock? Patching the main boot img from magisk while still locked even if the boot img boots with fastboot obviously still won't work to write boot partition with locked BL would it?
thanks i am in that group and asked several times but got ignored, thats why i thought i would ask here, there are 8 countries on this variant so i figured it would help all if it could be figured out since LG Dev only supports the euro model and this variant can actually be unlocked
corpsegrinder62 said:
Thanks, im going to try this really appreciate your help here. and the abl any idea how i go about flashing that to unlock? Patching the main boot img from magisk while still locked even if the boot img boots with fastboot obviously still won't work to write boot partition with locked BL would it?
thanks i am in that group and asked several times but got ignored, thats why i thought i would ask here, there are 8 countries on this variant so i figured it would help all if it could be figured out since LG Dev only supports the euro model and this variant can actually be unlocked
Click to expand...
Click to collapse
Worry about that later, first figure out if you can fastboot boot a boot IMG. Fastboot flashing it will 100% brick you
antintin said:
Worry about that later, first figure out if you can fastboot boot a boot IMG. Fastboot flashing it will 100% brick you
Click to expand...
Click to collapse
Thanks again, so here is the result.
I am struggling with both kdz tools and kdz firmware extractor, im able to get the DZ and dll files out, but on kdz tools using undz i end up with a bunch of .chunk files, and firmware extractor gives a zlib deflate error and gives a 0 byte file,
Taking this one side, i tried to rename the .chunk to a .img file, fastboot proceeded to download and attempt to boot, but stuck at logo, im guessing because the extraction of the boot img wasn't successful. but fastboot command worked and downloading to the phone worked, and it did attempt to boot, i have no idea now though how to get this kdz extracted. so needless to say without a working boot img i can't confirm 100% all i can confirm is fastboot boot command works.
any ideas?
[EDIT] i changed the unkdz to -c command, it extracted a boot img, i did as you said, patched boot img with magisk, and tried to fastboot boot it, sure enough! booted with dev warning error popups, but went into magisk, root access granted! so the patched boot img works by fastboot booting.
How would i go about the rest though with abl? as far as im aware we still waiting for firehose for G8/s?
corpsegrinder62 said:
Thanks again, so here is the result.
I am struggling with both kdz tools and kdz firmware extractor, im able to get the DZ and dll files out, but on kdz tools using undz i end up with a bunch of .chunk files, and firmware extractor gives a zlib deflate error and gives a 0 byte file,
Taking this one side, i tried to rename the .chunk to a .img file, fastboot proceeded to download and attempt to boot, but stuck at logo, im guessing because the extraction of the boot img wasn't successful. but fastboot command worked and downloading to the phone worked, and it did attempt to boot, i have no idea now though how to get this kdz extracted. so needless to say without a working boot img i can't confirm 100% all i can confirm is fastboot boot command works.
any ideas?
[EDIT] i changed the unkdz to -c command, it extracted a boot img, i did as you said, patched boot img with magisk, and tried to fastboot boot it, sure enough! booted with dev warning error popups, but went into magisk, root access granted! so the patched boot img works by fastboot booting.
How would i go about the rest though with abl? as far as im aware we still waiting for firehose for G8/s?
Click to expand...
Click to collapse
Nice, now you basically have to do the same thing as the other bl unlock guides. You flash the engineering abl to slot b (while on slot a) which needs to have working pie on it. Then you switch to it, go to fastboot, and do fastboot oem unlock.
antintin said:
Nice, now you basically have to do the same thing as the other bl unlock guides. You flash the engineering abl to slot b (while on slot a) which needs to have working pie on it. Then you switch to it, go to fastboot, and do fastboot oem unlock.
Click to expand...
Click to collapse
Thats great! When you say flash though. You mean dd flash with terminal with su to flash boot_b using said root access right? Then using fastboot to switch to boot_b and use that to unlock, correct?
But no abl yet for G8s as far as im aware, so i take it we need to wait on firehose for it or would cross flashing abl from another device work? Also android 10 update is around the corner, im still on pie 10i for now.
Thanks alot for your patience to help
Hello,
i would like to ask if someone on this forum can help with my bricked motorola g6. The bootloader is locked and i cannot access OEM unlock in the system. The only solution i would see is to use an full mmcblk0 image. It would be kind if someone could give another solution or provide an mmcblk0 image.
Greetings,
zOnlyKroks
still no progress as of yet
try booting with boot.img of the same version as installed in your phone. use fastboot getvar all to find out your phones version and then download rom and extract boot omg inside zip file and finally type fastboot boot boot.img
Then try OEM unlock. Is it gray? wait 7 days without shutting phone off ( you can turn screen off, but not entire phone). Didn't help? try updating to lastest version of your phone if not already up to date.
Anyone know how to lock the bootloader successfully? Clarification - I can lock the bootloader successfully but then can't boot normally.
I have a Frankenstein LG G7 emw from Aliexpress.
I have crossflashed it with an open EUR 10 Q kdz (G710EM)
After flashing the V35 onto abl_a and using "fastboot oem lock" the command is successful.
If I then restore my backed up original abl_a I then get a red triangle bootloop. I also sometimes get an unpatched fastboot screen with correct model type (G710EMW instead of the V35 one)
However I am unable to boot normally and then have to restore the V35, unlock the bootloader again, restore original abl, get into download mode and then reflash kdz using LGUP.
What do I need to lock the the bootloader and then boot normally? I want to be able to use Google pay and banking apps
Any help, ideas, tips or clues appreciated
I did relock the bootloader and successfully booted into system, but in between for 10 days my phone was like a dead hardware before coming into original working state.
sourabh7625 said:
I did relock the bootloader and successfully booted into system, but in between for 10 days my phone was like a dead hardware before coming into original working state.
Click to expand...
Click to collapse
When using fastboot to relock bootloader did you use the V35 abl_a or the G7 abl_a?
I'm thinking this may be where I'm going wrong but I haven't had time to test it out yet
gridmuncher said:
When using fastboot to relock bootloader did you use the V35 abl_a or the G7 abl_a?
I'm thinking this may be where I'm going wrong but I haven't had time to test it out yet
Click to expand...
Click to collapse
It was running on competely stock just booted into fastboot from using "adb reboot bootloader" and entered "fastboot oem lock" and everything worked fine.
What's state your phone currently in ? And what is your desired state ?
I have cross flashed the phone with an Android 10 kdz (european 30f). The bootloader is unlocked, but I cannot relock the bootloader. I have erased the laf_a partition to enable fastboot, but then "fastboot oem lock" doens't work. If I flash the v35 to abl_a then th command works but then the phone is in a red triangle bootloop.
I have tried extensively to google it but I have no idea how to make it work. I backed up numerous partitions using QFIL and tried to restore them once bootloader was locked but nothing seemed to help. The only way out of the bootloop was to return to download mode a reflash a kdz using LGUP
Let's see if someone can help me, I locked the bootloader again after putting the last stock rom of my moto g10 and it does not start. I only have access to fastboot with flash locked. i can't unlock it again or flash stock rom. with lmsa it gives me an error and stops at 26%. I have tried to flash the blankflash but it does not take the qualcomm drivers but the android device. I don't know what to do to revive it.
sorry for my bad english, google translate
I managed to put it in edl mode and flash a blankflash, but I get the same result bootloader locked. I can't flash anything or unlock the bootloader, it's definitely dead. It only remains to find a motherboard to replace it...
Ok, what I have is to find a compatible blankflash and stock firmware so that it will let me flash stock rom. someone could help me? I have already tried 3 different ones with no result.
whit themagictoolinstaller.exe i managed to change the flashinglocked mode to oemlocked. After this with rescue & smart assistant I was able to flash his stock rom. Solved