I had my phone rooted with the first official Android 11... I uninstalled root and completely reset the phone. Now I am on the second release of Android 11 and when I try to flash modified boot image in fastboot mode it says "Waiting for device" any suggestions or fixes? My device is available in adb mode doing the adb devices command... Please advise.
akinkoff85 said:
I had my phone rooted with the first official Android 11... I uninstalled root and completely reset the phone. Now I am on the second release of Android 11 and when I try to flash modified boot image in fastboot mode it says "Waiting for device" any suggestions or fixes? My device is available in adb mode doing the adb devices command... Please advise.
Click to expand...
Click to collapse
Did you unlock the bootloader again? Or was it just a wipe
Is usb debugging turned on?
Perhaps revoke it and cycle it then test ADB again.
If so run ADB kill-server
Then run ADB reboot bootloader should work then.
Also did you get the prompt when you did ADB devices on your phone to allow connections to that device?
Seems like driver issue.
Search for
ualcomm-hs-usb-qdloader-9008-driver-64-bit
akinkoff85 said:
I had my phone rooted with the first official Android 11... I uninstalled root and completely reset the phone. Now I am on the second release of Android 11 and when I try to flash modified boot image in fastboot mode it says "Waiting for device" any suggestions or fixes? My device is available in adb mode doing the adb devices command... Please advise.
Click to expand...
Click to collapse
Hey I'm having the same issue. Did you get this resolved?
It’s 100% a driver issue
If you're using Windows 7 there's a known issue with drivers, use Windows 10
I tried for hours to unlock on windows 10. I could access the device in adb while the phone was on and as soon booted into fastboot, Windows 10 says there was no driver.
Disabled verified drivers in Win 10 and was able to install the drivers, but fastboot still couldn't recognize the oneplus.
ymDroid said:
I tried for hours to unlock on windows 10. I could access the device in adb while the phone was on and as soon booted into fastboot, Windows 10 says there was no driver.
Disabled verified drivers in Win 10 and was able to install the drivers, but fastboot still couldn't recognize the oneplus.
Click to expand...
Click to collapse
Quite strange that.
From a completely fresh win 10 installation I just plugged in my phone, install the OnePlus drivers, then activated USB debugging, allowed all drivers to be installed.
Added necessary ADB and fastboot files in a folder to C: and then typed ADB devices via powershell in that folder, got prompted to accept the device.
From that point fastboot worked and always has.
try this solution https://forum.xda-developers.com/t/...owing-up-in-fastboot-mode-windows-10.4194491/
-
This did the job for me.
Hi everybody.
I have same problem.
(The story):
Unfortunately default Lenovo TAB M8 8505x OS have multiuser and many unwanted def app. So I was not success to limit my girl's tablet. Then I tried on custom rom and used fastboot mode ( by keep DOWN+POWER keys ). after this command (fastboot reboot fastboot)my fastboot mode was disabled and I can not connect to my tablet . now this show the logo for a few seconds and then restart again. I searched on the web to how to enable fastboot mode again and not found anything. One person prefer to wait for recharge battery completely and then charge but it does not work. to So I need help immediately.
This is my list of commands I used :
D:\LENOVO TAB M8\platform-tools>fastboot devices
HGT6FPQP fastboot
D:\LENOVO TAB M8\platform-tools>fastboot getvar version-bootloader
version-bootloader: akita_row_call-622276bd-20220223142906-20220706021818
Finished. Total time: 0.003s
D:\LENOVO TAB M8\platform-tools>fastboot flashing unlock
(bootloader) Start unlock flow
D:\LENOVO TAB M8\platform-tools>fastboot flash boot boot.img
Sending 'boot' (32768 KB) OKAY [ 1.219s]
Writing 'boot' OKAY [ 0.470s]
Finished. Total time: 1.867s
D:\LENOVO TAB M8\platform-tools>fastboot flash system system.img
Sending sparse 'system' 1/24 (130096 KB) OKAY [ 5.518s]
Writing 'system' OKAY [ 1.905s]
Sending sparse 'system' 2/24 (128056 KB) OKAY [ 5.592s]
Writing 'system' OKAY [ 1.865s]
......
Sending sparse 'system' 24/24 (31296 KB) OKAY [ 1.241s]
Writing 'system' OKAY [ 0.482s]
Finished. Total time: 198.984s
D:\LENOVO TAB M8\platform-tools>fastboot flash recovery recovery.img
Sending 'recovery' (32768 KB) OKAY [ 1.271s]
Writing 'recovery' OKAY [ 0.472s]
Finished. Total time: 1.907s
D:\LENOVO TAB M8\platform-tools>fastboot flash cache cache.img
Sending 'cache' (128 KB) OKAY [ 0.016s]
Writing 'cache' OKAY [ 0.016s]
Finished. Total time: 0.062s
D:\LENOVO TAB M8\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
D:\LENOVO TAB M8\platform-tools>fastboot flash recovery twrp34.img
Sending 'recovery' (4562 KB) OKAY [ 0.163s]
Writing 'recovery' OKAY [ 0.069s]
Finished. Total time: 0.254s
D:\LENOVO TAB M8\platform-tools>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
^C
D:\LENOVO TAB M8\platform-tools>
D:\LENOVO TAB M8\platform-tools>fastboot reboot fastboot
< waiting for any device >
^C
D:\LENOVO TAB M8\platform-tools>
D:\LENOVO TAB M8\platform-tools>fastboot reboot fastboot
< waiting for any device >
^C
D:\LENOVO TAB M8\platform-tools>fastboot reboot
< waiting for any device >
^C
As you can see , fastboot reboot fastboot was the last command I used and then my tablet restarted and fastboot mode disabled for ever. So turning off and then keeping Down+Power keys for going to fastboot not working
How can I enable fastboot mode again ?
M323 said:
Hi everybody.
I have same problem.
(The story):
Unfortunately default Lenovo TAB M8 8505x OS have multiuser and many unwanted def app. So I was not success to limit my girl's tablet. Then I tried on custom rom and used fastboot mode ( by keep DOWN+POWER keys ). after this command (fastboot reboot fastboot)my fastboot mode was disabled and I can not connect to my tablet . now this show the logo for a few seconds and then restart again. I searched on the web to how to enable fastboot mode again and not found anything. One person prefer to wait for recharge battery completely and then charge but it does not work. to So I need help immediately.
...
Click to expand...
Click to collapse
I am fairly certain you'd be better off asking in your Lenovo Tab forum, not here in the Oneplus 8 one.
Thank you Nimueh for your reply. I think the issue is not just for a model of cell phone.
Did you ever test this command in fastboot mode? : fastboot reboot fastboot
Why this command disabled fastboot mode ?
M323 said:
Thank you Nimueh for your reply. I think the issue is not just for a model of cell phone.
Did you ever test this command in fastboot mode? : fastboot reboot fastboot
Why this command disabled fastboot mode ?
Click to expand...
Click to collapse
No, that's not a command I've ever used, only JUST fastboot reboot
NO idea, sorry.
Romyo717 said:
This did the job for me.
Click to expand...
Click to collapse
Had this issue on my LG V30 unlocking the bootloader and this worked for me. Looks like a scam, and I'd uninstall it thoroughly after using it, but it did work! I also had to swap to a usb-2.0 hub to get the process I was doing to work so that might be useful.
Did you ever get it fixed?
Related
Hi,
I just wanted to install a new ROM but I ended without any Bootloader and System.
What I did:
- Wiped everything
- Forgot to copy the .zip files - so thats the point where everything went wrong
- Tried to upload it via adb push - failed when I wanted to install the zip
- Startet the flash-all.sh to install the factory image - went wrong -> no system.ing etc found
So what can I do now?
Its a Nexus Wifi (2012).
Thanks!
hd21337 said:
Hi,
I just wanted to install a new ROM but I ended without any Bootloader and System.
What I did:
Wiped everything
forgot to copy the .zip files - so thats the point where everything went wrong
tried to upload it via adb push - failed when I wanted to install the zip
startet the flash-all.sh to install the factory image - went wrong -> no system.ing etc found
So what can I do now?
Its a Nexus Wifi (2012).
Thanks!
Click to expand...
Click to collapse
Hi, hd21337...
What happens when you (from a fully shut down state) press VOL-DOWN, hold.. whilst holding, press POWER-ON?
What do you see when you plug the Nexus 7 into the wall charger? Do you see the WHITE-ON-BLACK battery charging animation?
Have you tried pressing, and holding for 30 seconds, the POWER ON button? (Your tablet could just be stuck in APX mode).
Rgrds,
Ged.
hd21337 said:
Hi,
I just wanted to install a new ROM but I ended without any Bootloader and System.
What I did:
Wiped everything
forgot to copy the .zip files - so thats the point where everything went wrong
tried to upload it via adb push - failed when I wanted to install the zip
startet the flash-all.sh to install the factory image - went wrong -> no system.ing etc found
So what can I do now?
Its a Nexus Wifi (2012).
Thanks!
Click to expand...
Click to collapse
Blessed are the backup makers, for they hath made Nandroids.
Exasperations, 3:16
I didn't know you could wipe out the bootloader. You should still be able to push recovery from PC via adb - fastboot. Then if pc recognizes the device transfer the zips from the pc.
Other than that, just don't know atp.
Someone more knowledgeable than I will need to chime in.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
GedBlake said:
Hi, hd21337...
What happens when you (from a fully shut down state) press VOL-DOWN, hold.. whilst holding, press POWER-ON?
What do you see when you plug the Nexus 7 into the wall charger? Do you see the WHITE-ON-BLACK battery charging animation?
Have you tried pressing, and holding for 30 seconds, the POWER ON button? (Your tablet could just be stuck in APX mode).
Rgrds,
Ged.
Click to expand...
Click to collapse
VOL-DOWN + Power On = Bootload appears but when I click on "Recovery mode" I see the Google logo with a notification in the top (Booting failed) in red. The same notification appears when I click on "Start".
I see the charging animation and holding the power button for 30 second didnt help.
wtherrell said:
Blessed are the backup makers, for they hath made Nandroids.
Exasperations, 3:16
I didn't know you could wipe out the bootloader. You should still be able to push recovery from PC via adb - fastboot. Then if pc recognizes the device transfer the zips from the pc.
Other than that, just don't know atp.
Someone more knowledgeable than I will need to chime in.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
Click to expand...
Click to collapse
Nah I think that i corrupted/deleted it with the factory image script from google!
And when I enter the bootloader, I dont see my device via "adb devices" :>
Downloads/nakasi-jwr66y » sudo ./flash-all.sh
Password:
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.577s]
finished. total time: 0.577s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.026s]
finished. total time: 1.026s
erasing 'recovery'...
OKAY [ 0.852s]
finished. total time: 0.852s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.488s]
finished. total time: 0.488s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 6.493s]
finished. total time: 6.493s
sending 'bootloader' (2100 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.412s
rebooting into bootloader...
OKAY [ 0.019s]
finished. total time: 0.020s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.18
Baseband Version.....: N/A
Serial Number........: XXXXXXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
FAILED
Device version-bootloader is '4.18'.
Update requires '4.23'.
finished. total time: 0.139s
Click to expand...
Click to collapse
hd21337 said:
Nah I think that i corrupted/deleted it with the factory image script from google!
And when I enter the bootloader, I dont see my device via "adb devices" :>
Click to expand...
Click to collapse
Maybe not... the v4.23 bootloader from Jellybean 4.3 build JWR66Y is known to cause issues when fastboot flashing back to factory stock. For this reason, it is recommended you replace that version of the bootloader with the one from build JWR66V. It's still, ostensibly, the same bootloader, but seems to fastboot flash OK.
As build JWR66V is now no longer available on the Google Developers website, somebody has extracted and uploaded the old bootloader from build JWR66V here. (You might have to scroll down a little for the link).
Oh.... and ADB devices doesn't work when you're in the bootloader... it requires a fully booted Android OS to work.
The command I think you're looking for is fastboot devices
Rgrds,
Ged.
hd21337 said:
VOL-DOWN + Power On = Bootload appears but when I click on "Recovery mode" I see the Google logo with a notification in the top (Booting failed) in red. The same notification appears when I click on "Start".
Click to expand...
Click to collapse
You are in bootloader (fastboot ) mode so when you wiped everything except bootloader it is normal state. Now check if computer know your nexus (if not install driver ) and run from factory image flash-all.bat and wait for restart. That's all. Adb and fastboot are two different things...
jkkk88 said:
You are in bootloader (fastboot ) mode so when you wiped everything except bootloader it is normal state. Now check if computer know your nexus (if not install driver ) and run from factory image flash-all.bat and wait for restart. That's all. Adb and fastboot are two different things...
Click to expand...
Click to collapse
Erm... yeah... I think the OP has probably done this already.
It was his fastboot output...
writing bootloader...
FAILED (remote: (InvalidState))
finished. total time: 0.412s
rebooting into bootloader...
...that suggested to me, the known issue with the bootloader from build JWR66Y as detailed here (in red letters, at the very top of the first post in the thread), and discussed here... as being the likely cause of the problem.
So, to reiterate @hd21337... fastboot flash the bootloader from build JWR66V, instead of the one from build JWR66Y... and it just might get your Nexus 7 back up and running again.
Good luck.
Rgrds,
Ged.
GedBlake said:
Erm... yeah... I think the OP has probably done this already.
It was his fastboot output...
writing bootloader...
FAILED (remote: (InvalidState))
finished. total time: 0.412s
rebooting into bootloader...
...
So, to reiterate @hd21337... fastboot flash the bootloader from build JWR66V, instead of the one from build JWR66Y... and it just might get your Nexus 7 back up and running again.
Click to expand...
Click to collapse
My concern was that OP could not start (deleted ) recovery from bootloader menu. He should look into stickies. Nexus is still alive and should get new bootloader as you recommended from another build.
Hi guys (@GedBlake and @jkkk88),
sorry for the late answer.
I just tried to run the flash-all.sh with the other bootloader image... but its worse than before.
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.580s]
finished. total time: 0.580s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.769s]
finished. total time: 0.769s
erasing 'recovery'...
OKAY [ 0.854s]
finished. total time: 0.854s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.489s]
finished. total time: 0.489s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 6.494s]
finished. total time: 6.495s
sending 'bootloader' (2100 KB)...
OKAY [ 0.267s]
writing 'bootloader'...
OKAY [ 9.376s]
finished. total time: 9.643s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for device >
Click to expand...
Click to collapse
So and at this point, he stuck for about 20 minutes - I aborted it because he didnt move on. And now the N7 is dead. No power charging icon and animation and I cant turn it on (30 seconds holding power button etc.).
So I think I just killed it
Any ideas if there is an another reset trick etc.?
Thanks!
Hello people,
I think, I've killed my nexus7 nakasi - 16GB model for ever today. Could you please help me try to resurrect it, or did I really kill him ?
Before, I was using unlocked, SuperSU rooted, KK 4.4.4 with TWRP bootloader and disabled some services (to stop stupid ota notifications coming up).
Today I wanted to try 5.1.1 (LMY47V), so I downloaded the ota, unzipped it, loaded adb, reboot into bootloader and ran flash-all.bat, as usually (I have already done it coulpe times before and never had any problems), until now.
Everything was running fine, until rebooting into bootloader ... ok.. waiting for device. The command line has stuck, so I removed table, terminated job, and tried booting bootloader by volume- & power. Nothing.
Please find my log output below.
Code:
D:\temp\adb>adb reboot bootloader
D:\temp\adb>flash-all.bat
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.022s]
finished. total time: 0.022s
erasing 'boot'...
OKAY [ 0.033s]
finished. total time: 0.036s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.266s]
finished. total time: 0.270s
erasing 'recovery'...
OKAY [ 0.036s]
finished. total time: 0.039s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.319s]
finished. total time: 0.322s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 8.775s]
finished. total time: 8.778s
sending 'bootloader' (2100 KB)...
OKAY [ 0.268s]
writing 'bootloader'...
OKAY [ 1.249s]
finished. total time: 1.524s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for device >
^CTerminate batch job (Y/N)? y
Is there anything I can do to revive him ? Or is he dead now ?
I have tried:
VOL+ VOL- POWER
VOL- POWER
Disconnecting battery + combination of previous before & after battery removal
Connecting power + combination of previous before & after battery removal
When i connect it to my pc now, I can hear sound of new device connected - in APX mode.
Holding POWR VOL+ VOL- for 15 sec, causes tablet to disconnect and connect again in APX, but bootloader won't start.
Plugging it on charger does nothing, battery indicator doesn't show up.
Please help !
remusator said:
Hello people,
I think, I've killed my nexus7 nakasi - 16GB model for ever today. Could you please help me try to resurrect it, or did I really kill him ?
Before, I was using unlocked, SuperSU rooted, KK 4.4.4 with TWRP bootloader and disabled some services (to stop stupid ota notifications coming up).
Today I wanted to try 5.1.1 (LMY47V), so I downloaded the ota, unzipped it, loaded adb, reboot into bootloader and ran flash-all.bat, as usually (I have already done it coulpe times before and never had any problems), until now.
Everything was running fine, until rebooting into bootloader ... ok.. waiting for device. The command line has stuck, so I removed table, terminated job, and tried booting bootloader by volume- & power. Nothing.
Please find my log output below.
Code:
D:\temp\adb>adb reboot bootloader
D:\temp\adb>flash-all.bat
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.022s]
finished. total time: 0.022s
erasing 'boot'...
OKAY [ 0.033s]
finished. total time: 0.036s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.266s]
finished. total time: 0.270s
erasing 'recovery'...
OKAY [ 0.036s]
finished. total time: 0.039s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.319s]
finished. total time: 0.322s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 8.775s]
finished. total time: 8.778s
sending 'bootloader' (2100 KB)...
OKAY [ 0.268s]
writing 'bootloader'...
OKAY [ 1.249s]
finished. total time: 1.524s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for device >
^CTerminate batch job (Y/N)? y
Is there anything I can do to revive him ? Or is he dead now ?
I have tried:
VOL+ VOL- POWER
VOL- POWER
Disconnecting battery + combination of previous before & after battery removal
Connecting power + combination of previous before & after battery removal
When i connect it to my pc now, I can hear sound of new device connected - in APX mode.
Holding POWR VOL+ VOL- for 15 sec, causes tablet to disconnect and connect again in APX, but bootloader won't start.
Plugging it on charger does nothing, battery indicator doesn't show up.
Please help !
Click to expand...
Click to collapse
Hi, remusator...
Sorry to be the bearer of bad news, but it sounds like your Nexus 7 is hardbricked. Both APX mode and the lack of the battery charging animation are classic hallmarks of a bootloader that may have have become corrupted, erased or accidentally overwritten.
APX mode is the state the N7 defaults to in the absence of a working bootloader, and with the expectation that somebody with the necessary software tools and knowledge will be able to nvFlash a replacement bootloader.
Unfortunately, there is no universal nvFlash tool available for the Nexus 7. The only way of accessing nvFlash on the Nexus 7 is, if you had, at some previous point, created your own unique Nexus 7 device dependant 'wheelie' blobs via the Flatline procedure.
So, without a working bootloader, the Nexus 7 cannot boot, nor can it be reflashed via fastboot commands (since it's the bootloader that 'accepts' those commands).
The only option (other than via nvFlash with previously generated Flatline 'wheelie' blobs, and which I suspect you don't have) is to have the motherboard replaced.
I have read accounts here on XDA of people sourcing Nexus 7 replacement motherboards from various online sources, and performing the replacement themselves. I don't know how easy or difficult it is, or how much it might cost (probably not much), but with a dead bootloader, it's likely the only way of resurrecting your Nexus 7.
Good luck...
Rgrds,
Ged.
Addendum: I assume you've tried all of these (that might be applicable)...
[REF] Nexus 7 Button Combinations
http://forum.xda-developers.com/showthread.php?t=2133986
----
Hey guys,
I can't install TWRP anymore on my unlocked "P8 lite" after the last Stock ROM Update. I've done the installation many times before without problems using Minimal ADB and fastboot and even the Universal Fastboot and ADB tool. When I try to flash I get no failed command, but nothing happens on my phone. I've tried with the newest grace .img (for "P8") and with an older .img that I've used in the past successfully. Commands "adb devices" and "adb reboot bootloader" work fine.
Any solution?
thx
CMD commands:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (26226 KB)...
OKAY [ 1.437s]
writing 'recovery'...
OKAY [ 1.172s]
finished. total time: 2.625s
Hi guys,
I had 7.0/5.1 with TWRP installed and root etc. I tried to flash an Oreo ROM but now the phone just remains on a black screen. Holding down either up or down with power button just does nothing. I do have fastboot access though and able to flash but not boot at all!
fastboot devices
2XJDU17719015729 fastboot
sending 'boot' (16612 KB)...
OKAY [ 0.416s]
writing 'boot'...
OKAY [ 0.124s]
finished. total time: 0.540s
sending 'recovery' (35992 KB)...
OKAY [ 0.892s]
writing 'recovery'...
OKAY [ 0.648s]
finished. total time: 1.540s
fastboot boot RECOVERY.img
creating boot image...
creating boot image - 36857856 bytes
downloading 'boot.img'...
OKAY [ 0.902s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.902s
korval said:
Hi guys,
I had 7.0/5.1 with TWRP installed and root etc. I tried to flash an Oreo ROM but now the phone just remains on a black screen. Holding down either up or down with power button just does nothing. I do have fastboot access though and able to flash but not boot at all!
fastboot devices
2XJDU17719015729 fastboot
sending 'boot' (16612 KB)...
OKAY [ 0.416s]
writing 'boot'...
OKAY [ 0.124s]
finished. total time: 0.540s
sending 'recovery' (35992 KB)...
OKAY [ 0.892s]
writing 'recovery'...
OKAY [ 0.648s]
finished. total time: 1.540s
fastboot boot RECOVERY.img
creating boot image...
creating boot image - 36857856 bytes
downloading 'boot.img'...
OKAY [ 0.902s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.902s
Click to expand...
Click to collapse
The easiest method to install oreo but be careful after this method you will get bootloader locked. If you want method which will not lock your bootloader try HwOta.
eldorado999 said:
The easiest method to install oreo but be careful after this method you will get bootloader locked. If you want method which will not lock your bootloader try HwOta.
Click to expand...
Click to collapse
Thanks for your reply but the phone is permanently stuck on a totally black screen with fastboot. Pressing power+vol keys do nothing. I can't get to erecovery or the normal white screen/bootloader/fastboot screen. I am still able to send fastboot commands.
:crying:
C:\Windows\system32>fastboot oem get-product-model
...
(bootloader) WAS-LX1A
OKAY [ 0.003s]
C:\Windows\system32>fastboot oem get-build-number
...
(bootloader) :WAS-LX1AC432B198
OKAY [ 0.003s]
finished. total time: 0.003s
C:\Windows\system32>fastboot oem unlock
...
FAILED (remote: already fastboot unlocked)
finished. total time: 0.001s
If anyone has any suggestions please share them, I cant believe how easy it was to brick this phone! I've flashed and rooted at least 5x samsung phones prior to this but never bricked one!
korval said:
If anyone has any suggestions please share them, I cant believe how easy it was to brick this phone! I've flashed and rooted at least 5x samsung phones prior to this but never bricked one!
Click to expand...
Click to collapse
I don't know if you installed a custom Rom or not, but install the stock Huawei recovery. Than in a microSD card put the stock ROM. Than press vol up+voldown+lockscreenbutton.
Tiagohsoares said:
I don't know if you installed a custom Rom or not, but install the stock Huawei recovery. Than in a microSD card put the stock ROM. Than press vol up+voldown+lockscreenbutton.
Click to expand...
Click to collapse
I tried to install Elite ROM v7.7 for P10 Lite via TWRP using the zip file. It installed with some errors but after rebooting the phone does not come on at all. Screen is black. but I do have fastboot access. I've tried using the factory ROM in the dload folder but when I hold in the buttons it just makes the USB connect/disconnect sound in windows as if you plug or unplug a usb device, screen stays black. I'm starting to lose all hope now. I just payed a lot of money for this phone only to brick it...
korval said:
I tried to install Elite ROM v7.7 for P10 Lite via TWRP using the zip file. It installed with some errors but after rebooting the phone does not come on at all. Screen is black. but I do have fastboot access. I've tried using the factory ROM in the dload folder but when I hold in the buttons it just makes the USB connect/disconnect sound in windows as if you plug or unplug a usb device, screen stays black. I'm starting to lose all hope now. I just payed a lot of money for this phone only to brick it...
Click to expand...
Click to collapse
If you can flash and boot recovery try with hwota7 to install to install stock rom...
This guide is for flashing GSI on Umidigi A7 Pro device, which was released in 2020 with Android 10. This device supports Project Treble and comes with a super partition that contains system, product and vendor partitions. I tried flashing the GSI by the unofficial TWRP and it was not possible. TWRP couldn't break the encryption and I couldn't see the system partition to finally flash the GSI image.
So the only way I was able to flash the GSI was through adb/fastboot. There are several guides on the internet but all with some erroneous command suggestion. The best guide was found in a Telegram channel and it worked for me and which I successfully adapted in the flash of the GSI AOSP of the PHH, version 411 (system-squeak-arm64-ab-vndklite-gapps-secure.img).
You who have this model and want to venture into custom Android, follow below the instructions I used successfully.
Warning
=======
VERY IMPORTANT: Before trying to make any changes to your device, keep in mind the high risk this entails. It takes knowledge and experience to succeed. I am not responsible for bricking your device and do so at your own risk if you wish. I'm narrating what I did to successfully install Android 12 on my device. Before succeeding, I failed miserably in 5 attempts, resulting in a brick, but with the right tools, I was able to get my Stock ROM back to life. Have the tools you need to recover your device at hand.
Also, be aware that a GSI (any of them) is made by Goggle for development testing by application developers and is not 100% usable on a daily basis. They are adapted by the developers themselves and all have some problem or failure to use the device.
For example: fingerprint to unlock does not work.
Even a Custom ROM that is different from GSI has its limitations, as they are not developed by the device manufacturer, but by Android enthusiasts.
My advice, research and study about Android, about your Android device, about your device's ROM and about ROM customization. Watch videos on Youtube and learn about Android on XDA Forums.
That said, whether you feel free to move on or not, read and reread this guide carefully. If in doubt or with fears: DO NOT GO AHEAD!!!
Tools Needed to flash only on Umidigi A7 pro
=====================================
1. Stock ROM official:
https://community.umidigi.com/forum.php?mod=viewthread&tid=20976&extra=page%3D1
2. Adb and fastboot tool, choose for your Windows or Linux platform, it must already be installed before GSI flash:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
3. Umidigi USB Drivers for Windows users, must already be installed before flashing GSI:
https://community.umidigi.com/forum.php?mod=viewthread&tid=4916&extra=page%3D1
4. Notice: TWRP recovery has on Android 12 version, it should not be flashed. And for this GSI flash we are not going to use TWRP recovery. Also because it is not possible to flash .img file in TWRP for Umidigi A7 pro.
5. Download any GSI PHH and choose the version that suits you best. I tested Vanilla (without Google apps), Gogapps (slim version of Google apps) and Gapps-secure (normal version of Google apps and to install Magisk), extract the file before installing:
Release AOSP 12.1 v411 · phhusson/treble_experimentations
Fixes boot on some devices (notably Mediatek but probably others as well) Fixes gapps variant' launcher Fixes floss' variant webview Fix setup wizard on gapps variant Fix fingerprint on some oplus ...
github.com
6. Download the product.img which will replace the product.img from the Stock ROM. This partition must not be deleted.
[Tutorial] Magisk on GSI on devices with dynamic partition
I hope you already know how to flash GSI on devices with dyamic partition already. If not then you can follow this guide: https://forum.xda-developers.com/t/how-to-flash-gsis-on-devices-with-dynamic-super-partition.4256667/#post-85271987 If...
forum.xda-developers.com
7. To flash the GSI, the device must have the bootloader unlocked. The bootloader unlock process has the same result as factory reset, erases all user data and restores the ROM as if you turned on the device for the first time. So backup your data before starting. Another thing, your device must have the updated Stock ROM (UMIDIGI A7 PRO V1.4_20211115 ROM - SPFT + OTA release, the link is in item 1 above) and cannot be rooted.
8. This guide is for flashing GSI on Umidigi A7 pro, bootloader must already be unlocked. For unlocking bootloader or flashing root Magisk is another guide. Save this guide to your PC and use it to help you install the GSI.
9- Create a folder on your computer's Desktop to save the downloaded files. Install the drivers if it's Windows and install the ADB/FASTBOOT Platform. Test to connect your device to the PC and test ADB/FASTBOOT with the following command:
[email protected]:/home/edupaz/Documentos/A7pro/custom rom# adb devices
List of devices attached
A7PRO205020712 device
Click to expand...
Click to collapse
Let's start flashing on Umidigi A7 pro:
=======================================
10- Connect the connected device to the PC, open a CMD (Windows) or Terminal (Linux) with Administrator privileges.
11- Run the command to verify the connection with ADB:
adb devices
12- Run the command to enter Bootloader mode:
adb reboot bootloader
13- Run the command to unlock the system boot:
fastboot --disable-verification flash vbmeta vbmeta.img
14- Run the command to enter FASTBOOTD mode:
fastboot reboot fastboot
15- Run the command to confirm that you are in FASTBOOTD mode, if yes it is in FASTBOOTD mode:
fastboot getvar is-userspace
16- Run the command to flash the new product partition:
fastboot flash product product.img
17- Run the command to wipe the Data partition:
fastboot -w
18- Run the command to delete the system partition:
fastboot erase system
19- Run the command for flash system:
fastboot flash system <arquivo da GSI que você baixou no item 5>.img
20- Run the command to resize the system partition:
fastboot resize-logical-partition system 2952790016
21- Now you can start your smartphone with the new GSI. There are two ways to start:
21-1 Holding the VOLUME DOWN button + POWER button and wait for the device to restart
or
21-2 Run the command to start Recovery and press the POWER button with the option "Reboot system now":
fastboot reboot recovery
Credits:
======
@kusti420 and @Allexwin50 - [Tutorial] Magisk on GSI on devices with dynamic partition
[Tutorial] Magisk on GSI on devices with dynamic partition
I hope you already know how to flash GSI on devices with dyamic partition already. If not then you can follow this guide: https://forum.xda-developers.com/t/how-to-flash-gsis-on-devices-with-dynamic-super-partition.4256667/#post-85271987 If...
forum.xda-developers.com
@D34thstroke and @Kenzomusik - channel Telegram Umidigi A7 Pro Chat - https://web.telegram.org/z/#-1311986347
See below a mirror of my flash successfully:
[email protected]:/home/edupaz/Documentos/A7pro/custom rom# adb devices
List of devices attached
A7PRO205020712 device
[email protected]:/home/edupaz/Documentos/A7pro/custom rom# adb reboot bootloader
[email protected]:/home/edupaz/Documentos/A7pro/custom rom# fastboot --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.015s]
Writing 'vbmeta' OKAY [ 0.005s]
Finished. Total time: 0.023s
[email protected]:/home/edupaz/Documentos/A7pro/custom rom# fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.005s]
< waiting for any device >
Finished. Total time: 22.492s
[email protected]:/home/edupaz/Documentos/A7pro/custom rom# fastboot getvar is-userspace
is-userspace: yes
Finished. Total time: 0.001s
[email protected]:/home/edupaz/Documentos/A7pro/custom rom# fastboot flash product product.img
Resizing 'product' OKAY [ 0.010s]
Sending 'product' (328 KB) OKAY [ 0.023s]
Writing 'product' OKAY [ 0.297s]
Finished. Total time: 0.345s
[email protected]:/home/edupaz/Documentos/A7pro/custom rom# fastboot -w
Erasing 'userdata' OKAY [ 2.865s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.011s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 2.899s
[email protected]:/home/edupaz/Documentos/A7pro/custom rom# fastboot erase system
Erasing 'system' OKAY [ 0.314s]
Finished. Total time: 0.327s
[email protected]:/home/edupaz/Documentos/A7pro/custom rom# fastboot flash system system-squeak-arm64-ab-vndklite-gapps-secure.img
Invalid sparse file format at header magic
Resizing 'system' OKAY [ 0.009s]
Sending sparse 'system' 1/11 (260993 KB) OKAY [ 19.500s]
Writing 'system' OKAY [ 3.699s]
Sending sparse 'system' 2/11 (262116 KB) OKAY [ 20.437s]
Writing 'system' OKAY [ 3.739s]
Sending sparse 'system' 3/11 (262116 KB) OKAY [ 20.493s]
Writing 'system' OKAY [ 2.558s]
Sending sparse 'system' 4/11 (262124 KB) OKAY [ 20.680s]
Writing 'system' OKAY [ 2.737s]
Sending sparse 'system' 5/11 (262128 KB) OKAY [ 19.856s]
Writing 'system' OKAY [ 2.716s]
Sending sparse 'system' 6/11 (262116 KB) OKAY [ 20.530s]
Writing 'system' OKAY [ 2.670s]
Sending sparse 'system' 7/11 (262124 KB) OKAY [ 21.190s]
Writing 'system' OKAY [ 2.678s]
Sending sparse 'system' 8/11 (254283 KB) OKAY [ 19.683s]
Writing 'system' OKAY [ 2.678s]
Sending sparse 'system' 9/11 (262036 KB) OKAY [ 20.256s]
Writing 'system' OKAY [ 2.643s]
Sending sparse 'system' 10/11 (262096 KB) OKAY [ 19.545s]
Writing 'system' OKAY [ 2.600s]
Sending sparse 'system' 11/11 (19134 KB) OKAY [ 1.474s]
Writing 'system' OKAY [ 0.577s]
Finished. Total time: 239.843s
[email protected]:/home/edupaz/Documentos/A7pro/custom rom# fastboot resize-logical-partition system 2952790016
Resizing 'system' OKAY [ 0.016s]
Finished. Total time: 0.016s
[email protected]:/home/edupaz/Documentos/A7pro/magisk# fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.252s
Click to expand...
Click to collapse
Ayoo just wanted to say thank you for the guide. I just went through this for my A7 Pro and it worked beautifully. Cleaner than stock rom, and being on A12 is nice.
Granted, none of the stock rom downloads worked, I was able to find an older version "Umidigi_A7_Pro_MT6763_128G_EEA_V1.0_20200528".
I also had some issues getting the flash tool to work but finally figured that out as well. For me, I had to have my phone connected to my pc, then turn it off, then press the volume down button to start the flash.
I also have a Umidigi A7 Pro I have stock Android 10 bit sad they don't support it long enough to update it but anyways... I'm interested in flashing a GSI to my device I used to flash custom roms on my older devices... Can u recommend any decent GSIs for the device and give me heads up on any problems on the way like fingerprint or gapps not working properly etc before I go ahead with flashing...
BayramRav3r said:
I also have a Umidigi A7 Pro I have stock Android 10 bit sad they don't support it long enough to update it but anyways... I'm interested in flashing a GSI to my device I used to flash custom roms on my older devices... Can u recommend any decent GSIs for the device and give me heads up on any problems on the way like fingerprint or gapps not working properly etc before I go ahead with flashing...
Click to expand...
Click to collapse
Honestly, it was really cool to do, but the os is super laggy. Like opening and closing apps or Windows has a very apparent lag to it.
I tried messing around with some of the developer settings to see if I could enable or disable some things that would improve performance, but nothing worked.
On the bright side, it is running Android 12 and a stock clean version of it. So that's really cool.
Oogwaysmash said:
Honestly, it was really cool to do, but the os is super laggy. Like opening and closing apps or Windows has a very apparent lag to it.
I tried messing around with some of the developer settings to see if I could enable or disable some things that would improve performance, but nothing worked.
On the bright side, it is running Android 12 and a stock clean version of it. So that's really cool.
Click to expand...
Click to collapse
Oh really that's bound to happen on a few years old tech think most things with less than a few GB of ram now uses a Android GO version which is lite.
So did you get everything like dual SIM, camera, and fingerprint working or not?
Another thing is can you dual boot a GSI I know you can temp boot a GSI instead of flash it sooo was thinking...