Related
This is the method tried on H815T model. But I think this should work with also other H815 models (other devices cannot say). Thanks to @autoprime, @thecubed and @Unjustified Dev for this.
Disclaimer: I am not responsible if your device gets into any more trouble for this.
Steps:
1. Download & clean install LG Drivers in your pc if u don't have it already.
2. Go into download mode by presing down the UP button and connecting the usb cable to the pc.
3. Go into LG ROOT folder. see this link to download: http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
4. Double click on ports.bat to know your COM port. Let's say it's COM4.
5. Open a windows command promt by Shift+Rt Click into the Lg Root folder.
6. Now send these commands:
Code:
Send_Command.exe \\.\COM4
It will reply
Code:
SPECIAL COMMAND : ENTER , LEAVE
#
7. Now command type
Code:
id
It should reply
Code:
uid=(0)root gid=(0)root
#
8. Now type
Code:
dd if=/dev/zero bs=8192 seek=35840 count=5120 of=/dev/block/mmcblk0
It will reply
Code:
#
9. Now pull out your battery, put it back in, go into HARD RESET mode by pressing down DOWN BUTTON+POWER BUTTON together and when the LG logo apprears, release the power button for a second and press it back again.
10. Now in HARD RESET, it will ask you whether you want to reset everything or not. Select "No" and it will take you to fastboot mode.
Special note:
1. @autoprime told me to factory reset everything before starting this whole process. I did as my bootloader was locked. Don't know how it affects in unlocked bootloader.
2. How to get out of fastboot normally: I don't know it quitely. My bootloader was locked, so neither I could flash any system file through fastboot, nor "fastboot reboot" or "fastboot reboot bootloader" worked for me. @autoprime told me to get out of fastboot, manually go into download mode, then pull out your battery and put back in. Actually you can't get out of the fastboot that way until you flash a KDZ.
Thank u. Reply in the comments if fastboot could help you any.
delete
Hi,
Thank you very much for this Guide. Unfortunately, having tried to unbrick my device (H815) previously by hard resetting and not having access to Android to re-activate ADB, the Shell (Send_command.exe) didn't help me (at every command it returns a "FAIL" message, my phone is recognized by Windows by the way).
So I couldn't get into Fastboot by following this Guide.
Hope it works for others, waiting for results!
TheBledard said:
Hi,
Thank you very much for this Guide. Unfortunately, having tried to unbrick my device (H815) previously by hard resetting and not having access to Android to re-activate ADB, the Shell (Send_command.exe) didn't help me (at every command it returns a "FAIL" message, my phone is recognized by Windows by the way).
So I couldn't get into Fastboot by following this Guide.
Hope it works for others, waiting for results!
Click to expand...
Click to collapse
You couldn't get into fastboot or u couldn't flash anything in fastboot? I cannot make my device recognised in adb too, but it is recognised in fastboot. U need to have the adb and fastboot setup in your pc. But I couldn't flash anything in fastboot as it shows my device is locked although someone said, theoritically it was supposed to flash system files through fastboot.
nipun1110 said:
You couldn't get into fastboot or u couldn't flash anything in fastboot? I cannot make my device recognised in adb too, but it is recognised in fastboot. U need to have the adb and fastboot setup in your pc. But I couldn't flash anything in fastboot as it shows my device is locked although someone said, theoritically it was supposed to flash system files through fastboot.
Click to expand...
Click to collapse
I couldn't get into Fastboot at all. Any command typed in send_command.exe gives "Fail" as result... Phone is connected in Download Mode and recognized in Windows, DIAG1 port is COM4.
Screenshot attached
lock bootloader , fastboot unnecessary
29y6145 said:
lock bootloader , fastboot unnecessary
Click to expand...
Click to collapse
True. I didn't realise that before, so gave it a try. But this may help those with unlocked bootloader.
Sent from my LG-H815 using Tapatalk
I always get a "FAIL" reply. Any ideas?
nipun1110 said:
True. I didn't realise that before, so gave it a try. But this may help those with unlocked bootloader.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
With an unlocked bootloader...
Code:
adb reboot bootloader
nobnut said:
With an unlocked bootloader...
Code:
adb reboot bootloader
Click to expand...
Click to collapse
Hahahah tru!
nobnut said:
With an unlocked bootloader...
Code:
adb reboot bootloader
Click to expand...
Click to collapse
maybe u r suggesting to say
fastboot reboot bootloader
right?
Sent from my LG-H815 using Tapatalk
This does not work for me, I have an unlocked bootloader, but just get the response "FAIL".
And... Why don't you just zero the laf partition instead through an adb shell? What does this do that's different?
If we can get into fastboot, can we then do something like
Code:
fastboot boot recovery.img
to get into a custom type recovery and do a backup? I'm on the AT&T H810 version, locked bootloader, I don't know if that means a big fat NO lol or if this method of getting into fastboot mode would even work on my variant.
petermg said:
If we can get into fastboot, can we then do something like
Code:
fastboot boot recovery.img
to get into a custom type recovery and do a backup? I'm on the AT&T H810 version, locked bootloader, I don't know if that means a big fat NO lol or if this method of getting into fastboot mode would even work on my variant.
Click to expand...
Click to collapse
no one should be wiping laf or recovery to get into fastboot. it's a dumbed down fastboot that doesn't let anything flash or boot. the directions I gave OP were in a PM as a last resort because he was stuck in download mode with no booting and wanted to try fastboot. It was never meant to be suggested in public to users who might think they can get anywhere with it.
autoprime said:
no one should be wiping laf or recovery to get into fastboot. it's a dumbed down fastboot that doesn't let anything flash or boot. the directions I gave OP were in a PM as a last resort because he was stuck in download mode with no booting and wanted to try fastboot. It was never meant to be suggested in public to users who might think they can get anywhere with it.
Click to expand...
Click to collapse
Ok then if u suggesting me I should delete the post, I will ask Moderator to do so.
Sent from my LG-H815 using Tapatalk
It's good
Holly molly sir! You are a legend. Long story not so short. My lg got the bootloop bug. Took 2 months to fix, but apparently they changed my locked to three uk H815 "eu open" motherboard with actually unlocked one. So I was finally able to unlock boot-loader, root and **** up (LOL). Apparently I didn't install twrp properly (you'd think "fastboot boot twrp.img" would not install it but run it once) And i was following this to get Android M on. But it requires reboot before boot-loader is flashed. Right when i clicked reboot i figured it wont start in twrp but in stock recovery. So I couldn't even get proper bootloop, it would cut half way into the LG logo. I reckon kdz-ing would havedone the trick, but god it takes ages to DL the kdz file. So in the mean time i found this legendary post. The odd thing was i had to click Yes, on the factory reset screen, but it got me to "Fastboot mode started" and from there i booted into twrp and finished what it had started, currently its Optimising app 35 of 55. Nice one OP, Nice One!
hi i have unlocked bootloader. but i keep getting FAIL as response
nipun1110 said:
8. Now type
Code:
dd if=/dev/zero bs=8192 seek=35840 count=5120 of=/dev/block/mmcblk0
It will reply
Code:
#
Click to expand...
Click to collapse
Hi,
how can I change it back to default Factory reset??
I installed Android O DP2 update via OTA yesterday. The phone updated, rebooted to the new build and restarted abruptly and since then has been stuck in a boot loop. The Google logo shows up, goes to the android animation step and then Google logo appears again.
I don't have bootloader unlocked, don't have TWRP and have done OTA updates. I am able to get into the stock recovery mode.
How do I fix this, i.e. make it work in any way without erasing the user data? I don't mind extreme steps (without erasing user data) because I was planning to reflash 7 with unlocking & rooting today.
Try to wipe cache from recovery - in recovery hold volume-down and select "Wipe cache partition". Should do the trick
I tried, didn't work. Had to factory reset in the end. Also opted out of beta
I just read that some people that took the update from certain builds had boot loops due to the update only replacing part of the OS but leaving the 7.x.x system in place causing it to boot loop. I think it was like on android authority or something like that.
Sent from my Nexus 6P using XDA-Developers Legacy app
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
citifone said:
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
Click to expand...
Click to collapse
You can unlock your bootloader to flash a stock ROM. Do you need the steps?
---------- Post added at 09:54 AM ---------- Previous post was at 09:38 AM ----------
citifone said:
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
Click to expand...
Click to collapse
To flash a system image:
Download the latest system image for your Nexus 6p, then unzip it to a safe directory.
https://dl.google.com/dl/android/aosp/angler-n2g47o-factory-dc258043.zip
or Download any of your choice from here
https://developers.google.com/android/images
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
adb tool
http://developer.android.com/tools/help/adb.html
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device.
POWER BUTTON + VOLUME DOWN BUTTON
Click to expand...
Click to collapse
If necessary, unlock the device's bootloader using one of the following methods:
Code:
fastboot flashing unlock
If you are updating an older device, run this command:
Code:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory or Open a command prompt from within your System image folder (navigate to where you have flash-all.bat located on your PC, shift + right click anywhere within that folder, select open command prompt here
Execute the flash-all script.
Code:
fastboot flash-all.bat
This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
Code:
fastboot flashing lock
or, for older devices, run:
Code:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Mavelos said:
You can unlock your bootloader to flash a stock ROM. Do you need the steps?
---------- Post added at 09:54 AM ---------- Previous post was at 09:38 AM ----------
To flash a system image:
Download the latest system image for your Nexus 6p, then unzip it to a safe directory.
https://dl.google.com/dl/android/aosp/angler-n2g47o-factory-dc258043.zip
or Download any of your choice from here
https://developers.google.com/android/images
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
adb tool
http://developer.android.com/tools/help/adb.html
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device.
If necessary, unlock the device's bootloader using one of the following methods:
Code:
fastboot flashing unlock
If you are updating an older device, run this command:
Code:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory or Open a command prompt from within your System image folder (navigate to where you have flash-all.bat located on your PC, shift + right click anywhere within that folder, select open command prompt here
Execute the flash-all script.
Code:
fastboot flash-all.bat
This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
Code:
fastboot flashing lock
or, for older devices, run:
Code:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
Thanks for your reply..But you can only do this only if you have an unlocked bootloader and debugged mode on. I didn't have either so it won't allow to flash with locked bootloader.
citifone said:
Thanks for your reply..But you can only do this only if you have an unlocked bootloader and debugged mode on. I didn't have either so it won't allow to flash with locked bootloader.
Click to expand...
Click to collapse
Exactly why i posted that. You can unlock your bootloader without turning USB debugging ON. Just Boot up with the POWER + VOLUME down Combination and use the bootloader unlock command in my previous post.
FAILED (remote: OEM unlock is not allowed)
Mavelos said:
Exactly why i posted that. You can unlock your bootloader without turning USB debugging ON. Just Boot up with the POWER + VOLUME down Combination and use the bootloader unlock command in my previous post.
Click to expand...
Click to collapse
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Lord Aguacate said:
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Click to expand...
Click to collapse
Yes, I got the same error. Again, it's because of bootloader locked and debug is off. Any other ways to unlock or flash this phone?
citifone said:
Yes, I got the same error. Again, it's because of bootloader locked and debug is off. Any other ways to unlock or flash this phone?
Click to expand...
Click to collapse
To unlock you first need to have ticked the allow OEM unlock from developer menu within the OS. It won't work otherwise.
Lord Aguacate said:
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Click to expand...
Click to collapse
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Mavelos said:
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here [="https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip"]https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
="https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip"]https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Click to expand...
Click to collapse
Dear Mavelos,
I already tried that and the installation was successful, but my first problem still there, when I installed the Android O Beta, the touch of my screen stop working after the 2nd day of installation.
Now I don't know if this is a problem with Android O or just a coincidence and the hardware its broken.
I went to a lot of forums but nobody its talking about that (Touch Screen not working)
Did You guys hear anything about it?
Mavelos said:
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Click to expand...
Click to collapse
I have the same problem as others, stuck in a bootloop and had not enabled unlock in dev options. I can get to bootloader but not recovery mode (bootloops when I select this). I would love to try this OTA side load, but I can't see my device in adb. I can see it however in fastboot. Not sure how to get it up in adb....
Any help would be much appreciated.
scorneil said:
I have the same problem as others, stuck in a bootloop and had not enabled unlock in dev options. I can get to bootloader but not recovery mode (bootloops when I select this). I would love to try this OTA side load, but I can't see my device in adb. I can see it however in fastboot. Not sure how to get it up in adb....
Any help would be much appreciated.
Click to expand...
Click to collapse
If you get a bootloop when selecting recovery, try rebooting to recovery with fastboot
Code:
fastboot reboot recovery
if that doesn't work, then i think your device is bricked.
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
Lord Aguacate said:
Dear Mavelos,
I already tried that and the installation was successful, but my first problem still there, when I installed the Android O Beta, the touch of my screen stop working after the 2nd day of installation.
Now I don't know if this is a problem with Android O or just a coincidence and the hardware its broken.
I went to a lot of forums but nobody its talking about that (Touch Screen not working)
Did You guys hear anything about it?
Click to expand...
Click to collapse
If your touch screen isn't working, it might be related to the Android O Beta you flashed. Can you boot the phone up? If you have an OTG cable, connect a mouse to your phone. Turn on OEM unlocking in developer options. Do a factory reset.
i have the same problem with this, and i cannot unlock it too, is there anyway to unlock this phone?
OTG works Perfect! But.....
Mavelos said:
If you get a bootloop when selecting recovery, try rebooting to recovery with fastboot
Code:
fastboot reboot recovery
if that doesn't work, then i think your device is bricked.
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
If your touch screen isn't working, it might be related to the Android O Beta you flashed. Can you boot the phone up? If you have an OTG cable, connect a mouse to your phone. Turn on OEM unlocking in developer options. Do a factory reset.
Click to expand...
Click to collapse
So I Follow your suggestion and I bought the OTG adapter, works perfectly I unlocked the bootloader from the developers options, did a factory restore with a previous image, etc.... Touch still not working, I'm starting to believe this a hardware problem with the screen.... Bad Luck maybe, I don't know! ..... I will have to buy that expensive screen ($140).
Anyway thanks for the help...
Regards
Lord Aguacate said:
So I Follow your suggestion and I bought the OTG adapter, works perfectly I unlocked the bootloader from the developers options, did a factory restore with a previous image, etc.... Touch still not working, I'm starting to believe this a hardware problem with the screen.... Bad Luck maybe, I don't know! ..... I will have to buy that expensive screen ($140).
Anyway thanks for the help...
Regards
Click to expand...
Click to collapse
You're welcome. Get your phone fixed and return to the flashing community.
last night i my phone inside my freezer hehehe and this morning i tried to turn it on, and it pass the google logo boot normally but it only lasted for a few minute and then turn off and bootloop again. so i guess my 6p has a hardware faulty
Hey there,
so my problem is, that I just cant unlock my bootloader anymore.
I dont know what to do.
The phone just shows the xiamoi logo for one second and then black screen.
Only fastboot mode does work.
Cmd says remote: oem unlock is not allowed. YES I know that I havent activated developer settings but I cant, because I wiped the system and cant do anything. And how to flash stock rom, when I havent got bootloader permissions.
Qfil and so on doestn work either.
Please respond asap.
heya
only you need to change the partition, ONLY WORK IF YOU DONT ERASE THE 2 SYSTEM PARTITIONS (system_a and system_b), to make that you need to follow instructions:
1.- open CMD in platform tools
2.- in CMD type Fastboot getvar current-slot
3(1).-if the CMD say current-slot:_a you need to type Fastboot set_active b
3(2).-if the CMD say current-slot:_b you need to type Fastboot set_active a
4.- reboot the phone typing fastboot reboot, and Ready!!!
Moratilla3 said:
only you need to change the partition, ONLY WORK IF YOU DONT ERASE THE 2 SYSTEM PARTITIONS (system_a and system_b), to make that you need to follow instructions:
1.- open CMD in platform tools
2.- in CMD type Fastboot getvar current-slot
3(1).-if the CMD say current-slot:_a you need to type Fastboot set_active b
3(2).-if the CMD say current-slot:_b you need to type Fastboot set_active a
4.- reboot the phone typing fastboot reboot, and Ready!!!
Click to expand...
Click to collapse
thanks for your reply, I typed it and it said active slot a, I typed... set_active b ...
I restarted it and I got black screen again... the problem is I cant flash software on it because I cant unlock the bootloader
klapfi said:
Hey there,
so my problem is, that I just cant unlock my bootloader anymore.
I dont know what to do.
The phone just shows the xiamoi logo for one second and then black screen.
Only fastboot mode does work.
Cmd says remote: oem unlock is not allowed. YES I know that I havent activated developer settings but I cant, because I wiped the system and cant do anything. And how to flash stock rom, when I havent got bootloader permissions.
Qfil and so on doestn work either.
Please respond asap.
Click to expand...
Click to collapse
Go to: "Settings" -> "Developer options" oem option activate ?
klapfi said:
Hey there,
so my problem is, that I just cant unlock my bootloader anymore.
I dont know what to do.
The phone just shows the xiamoi logo for one second and then black screen.
Only fastboot mode does work.
Cmd says remote: oem unlock is not allowed. YES I know that I havent activated developer settings but I cant, because I wiped the system and cant do anything. And how to flash stock rom, when I havent got bootloader permissions.
Qfil and so on doestn work either.
Please respond asap.
Click to expand...
Click to collapse
Did you try Mi unlock?
http://en.miui.com/unlock/
You must create a mi account and need to use a chinese proxy to validate registration
I solved it myself. As mentioned I had no OS installed so there was no way to activate developer settings. I couldtn enter edl mode via fastboot so I used testpoint to solve my problem. I then flashed it via Miflash and the phone works now fine :good:
klapfi said:
I solved it myself. As mentioned I had no OS installed so there was no way to activate developer settings. I couldtn enter edl mode via fastboot so I used testpoint to solve my problem. I then flashed it via Miflash and the phone works now fine :good:
Click to expand...
Click to collapse
Before flashing a rom and rom custom is better know how to return to initial configuration
klapfi said:
I solved it myself. As mentioned I had no OS installed so there was no way to activate developer settings. I couldtn enter edl mode via fastboot so I used testpoint to solve my problem. I then flashed it via Miflash and the phone works now fine :good:
Click to expand...
Click to collapse
can you tell how to do testpoint?
Balasubramaniyan said:
can you tell how to do testpoint?
Click to expand...
Click to collapse
Just go on youtube and search for testpoint xiamoi mi a1, I did the same and it worked for me.
Good luck
If you can access Fastboot. THIS WILL ERASE ALL OF YOUR DATA
1. Enter Fastboot Mode > Make sure drivers are installed correctly
2. Enter "fastboot oem edl" > > Ignore Error > Your phone notification led should now blink.
3. Use MiFlash to flash the fastboot ROM.
klapfi said:
I solved it myself. As mentioned I had no OS installed so there was no way to activate developer settings. I couldtn enter edl mode via fastboot so I used testpoint to solve my problem. I then flashed it via Miflash and the phone works now fine :good:
Click to expand...
Click to collapse
Is there a way you could be more specific on what you do please? I don't understand what do you have to do after the testpoint, how do you use miflash to reflash the rom? Please
JFGR11 said:
Is there a way you could be more specific on what you do please? I don't understand what do you have to do after the testpoint, how do you use miflash to reflash the rom? Please
Click to expand...
Click to collapse
When your phone is in testmode you are able to flash stock firmware via Miflash. Download the stock firmware in the internet just google it.
You have to install Miflash. Open it connect phone in fastboot (testpoint). Then select the downloaded firmware in Miflash and flash it.
There are many videos on youtube how to flash with miflash.
Mi A1 show on PC screen failed ( OEM unlock is not allowed)
And not on my device
guys can we unlock bootloader from site : http://en.miui.com/unlock/ ? anybody tried that ?
burimi007 said:
guys can we unlock bootloader from site : http://en.miui.com/unlock/ ? anybody tried that ?
Click to expand...
Click to collapse
no, our device is android one, so bootloader only need a fastboot command and no code/waiting/program needed...
Help
klapfi said:
I solved it myself. As mentioned I had no OS installed so there was no way to activate developer settings. I couldtn enter edl mode via fastboot so I used testpoint to solve my problem. I then flashed it via Miflash and the phone works now fine :good:
Click to expand...
Click to collapse
hi bro your problem and i am the same as me now, and i read from this chat reply that you can finish via testpoint mode, then if you can know what windows you use 7 or 10, because on my windows does not show Qualcom 9008 driver, please help I
Last week i received a notification the 8.1 Oreo update was available for my Moto g4 Plus.
Downloaded the package and hit the install button. My moto restarted in order to perform the installation.
However, since i had TWRP installed and thus bootloader unlocked, the phone restarted in recovery mode.
Downloaded a TWRP 8.1 rom and installed it without a problem.
Unfotunately everytime I restart my Moto it starts up in fastboot mode.
Bootloader log shows: Fastboot Reason: reboot mode set to fastboot
From bootloader I can start the Android OS, but i wan't to get rid of this reboot mode
I tried tools like "Android Multi Tool" and "Free ReiBoot for Android" but this reboot mode can not be cleared.
Anyone encountered this problem and how did you fix it.
Thanks in advance
Try this:
Reboot your device to the bootloader.
Connect your device to your computer and open an ADB terminal on your computer.
In the ADB terminal, type 'fastboot devices' without quotes. Press Enter - your device should respond with its serial number.
If so, then type 'fastboot oem fb_mode_clear' without quotes. Press Enter, then reboot your device.
That fb_mode_clear command seems to clear a flag that keeps your device booting into fastboot (usually for OTA updates).
I have Tried that option as i found it as one of the possible solutions for this issue.
the clear_fb unfortunately does not remove the fastboot mode on my moto.
mbodewes said:
I have Tried that option as i found it as one of the possible solutions for this issue.
the clear_fb unfortunately does not remove the fastboot mode on my moto.
Click to expand...
Click to collapse
Alright, though this is for solving TWRP bootloops, might be useful for you https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
echo92 said:
Alright, though this is for solving TWRP bootloops, might be useful for you https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
Click to expand...
Click to collapse
echo92. Thanks. Works like a charm. Issue fixed.
Just bought a used Pixel 4 to try and flash lineage 17.1 but can't get OEM unlocking to actually work. The enable switch is in the on position and adb recognizes the device but when I try to enter fastboot either by adb reboot bootloader or volume down + power on, the device status comes up in green text "locked." The phone is a G020I and came to me running android 11 with a build number RP1A.20005.004. Is this too new of a phone and wont be able to be flashed? From what I understand, if the bootloader stays locked, I can't even flash a factory image of android 10, correct?
You have to unlock bootloader using fastboot command from pc...
gpvecchi said:
You have to unlock bootloader using fastboot command from pc...
Click to expand...
Click to collapse
Fastboot commands wont work. adb commands will but as soon as I try adb reboot bootloader to get to the point where I can enter fastboot flashing unlock, I get the result in the pics below.
You need to install Google usb driver to use Fastboot
2WildFirE said:
You need to install Google usb driver to use Fastboot
Click to expand...
Click to collapse
Ok, in trying to do that, I get the message from windows that their driver is the most up to date and won't let me install from the file I try to choose. See the pics below.
I had the same issue, updating the USB drivers rc13 did the trick.
GTOJim said:
I had the same issue, updating the USB drivers rc13 did the trick.
Click to expand...
Click to collapse
LInk for that update?
Here you go: https://www.thecustomdroid.com/google-android-usb-drivers/
Finally got it. Windows had to recognize it as a generic device in order to force a driver. If it saw it as Pixel 4 it would stop. Now that I have lineage flashed on it, just need to figure out how to get mms to work. Apparently that is a common problem too.