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...
Related
Hi guys,
I need your help.
I rooted and unlocked my device using wug fresh toolkit 1.5.3.
After that I installed TWRP trough adb.
Next, I flashed Paranoid Android and everything was working fine.
By some stupid ideea that i had, because there was no space on my device
due to leftovers from the apps I had before, I tought I should go in TWRP and wipe everything,
than flash the Rom again.
I wiped cache, dalvik, restore factory settings and than I wiped sd card both internal and external.
Right now I cant flash the Rom again or restore a nandroid, because there is nothing on device.
Connecting to computer will not recognize it.
All I can do is, while conected to computer, use buttons and get into bootloader and from there on TWRP recovery.
Please help me with some instructions on how to make my Nexus 7 work again.
Thank you.
You can manually push ROM/Kernel/Gapps files to /sdcard using adb push from Android SDK.
I can't exactly recall if you can push the files from bootloader, or recovery, or both, but a push command would look like:
Code:
adb push FILE.zip /sdcard
adb push being the ADB command to push files from the computer to the device
FILE.zip being the name of the file you want to send to the device (for example, EOS-grouper-20120908-27.zip)
/sdcard being the place on the device you want the file to be placed in
In some cases, /sdcard may not work, but /data/media should work.
Another option is to restock using a factory image from Google and then start over with flashing CWM, and then copying over your ROM/Kernel/Gapps files.
adb push
espionage724 said:
You can manually push ROM/Kernel/Gapps files to /sdcard using adb push from Android SDK.
I can't exactly recall if you can push the files from bootloader, or recovery, or both, but a push command would look like:
Code:
adb push FILE.zip /sdcard
adb push being the ADB command to push files from the computer to the device
FILE.zip being the name of the file you want to send to the device (for example, EOS-grouper-20120908-27.zip)
/sdcard being the place on the device you want the file to be placed in
In some cases, /sdcard may not work, but /data/media should work.
Another option is to restock using a factory image from Google and then start over with flashing CWM, and then copying over your ROM/Kernel/Gapps files.
Click to expand...
Click to collapse
I cannot push as it says "device not found".
Ok, I had to restock and unroot. Now is working fine. I used also wug fresh toolkit.
Will have to root again and so on...
Thanks!
same as above
hey guys my nexus 2012 wifi running 4.3 rooted has TWERP and installed CM 10.1.3 for some dumb reason as the above mentioned i too wiped dalvik cache and sd via TWERP. Now im stuck on google logo with an unlock padlock logo I can still go to fastboot but cant open recovery when I open it I only get the green robot with red warning sign. Im desperate I used wugfresh toolkit 1.7.5 and use the FlashStock+Unroot everything is ok on the script exept for bootloader failed my device got 4.18 while it says the toolkit needs 4.2+ i dont remember anymore. now im still stuck on google logo with an unlock padlock logo. Hope you guys can help me its my daughter's tablet she'll be sad without it..:crying: well be very thankful for any help thank in advance.
heres the code
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.020s]
finished. total time: 0.023s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.039s]
finished. total time: 0.039s
erasing 'recovery'...
OKAY [ 0.020s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.044s]
finished. total time: 0.045s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.977s]
finished. total time: 0.977s
sending 'bootloader' (2100 KB)...
OKAY [ 0.258s]
writing 'bootloader'...
OKAY [ 0.709s]
finished. total time: 0.968s
rebooting into bootloader...
OKAY [ 0.020s]
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.23
Baseband Version.....: N/A
Serial Number........: 015d257818580418
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.022s]
sending 'boot' (4896 KB)...
OKAY [ 0.584s]
writing 'boot'...
OKAY [ 0.179s]
sending 'recovery' (5432 KB)...
OKAY [ 0.653s]
writing 'recovery'...
OKAY [ 0.186s]
erasing 'system'...
OKAY [ 0.057s]
sending 'system' (529061 KB)...
FAILED (remote: (Nv3pBadReceiveLength))
finished. total time: 4.274s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
I have a Redmi Note 1GB ram, 2 sims ( model HM NOTE 1S CT ) running ANDROID 4.4.4 MIUI 8.6.7.28 beta.
I'm trying to install TWRP onto it but keep getting the same error as shown below:
C:\Users\david\Desktop\wt86047-TWRP3.0.2-0_LP\adb>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.078s]
finished. total time: 0.078s
C:\Users\david\Desktop\wt86047-TWRP3.0.2-0_LP\adb>fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (13408 KB)...
OKAY [ 0.426s]
writing 'recovery'...
OKAY [ 0.563s]
finished. total time: 0.989s
C:\Users\david\Desktop\wt86047-TWRP3.0.2-0_LP\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.425s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.534s
I've tried many different twrp versions but always the same error. Anyone help ?
Why you need to flash twrp.img to boot? When I did this part, it was done already.
C:\Users\david\Desktop\wt86047-TWRP3.0.2-0_LP\adb>fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (13408 KB)...
OKAY [ 0.426s]
writing 'recovery'...
OKAY [ 0.563s]
finished. total time: 0.989s
Click to expand...
Click to collapse
That,s just to check it. It should reboot the phone into twrp, but standard recovery is still there.
Even if I try to boot into twrp using the volume down/power button, standard recovery comes up.
Can anyone help ?
blankers said:
Can anyone help ?
Click to expand...
Click to collapse
What ROM are you on? If you are on a Custom ROM already, you can try to use TWRP manager to install.
Another option would be you flash another recovery, like PhilzTouch, and then a Custom ROM, then TWRP manager...
the 2nd command should work "fastboot flash recovery twrp.img"
in my case.its always working.i already try many times
1.flash stock miui rom using MIUI flash tool
2. flash twrp using fastboot "fastboot flash recovery twrp.img"
3. reboot
note : after flashing twp you need to execute "fastboot reboot" and miui/custom rom should boot normally
then reboot to recovery
i used twrp3.0.2
Good afternoon to all, I need a lot of help. I have a p9 lite VNS-L23 C605B120, try to install the rom revolution nougat, unlock the bootloader, install the recovery and from there an update file, when I finish, I reset and the phone left with the black screen, I connect it, the PC and I recognize it: Android bootloader interface, do not enter with the 3 buttons: vol + vol - and button on.
I need help on how I can flash it, with some program or how I can fix it, and what are the necessary files ... Thank you very much already.
Pd: the HiSuit of hawei is opened every time I connect the phone to the PC, but it does not allow me to recover the system, at the beginning it leaves: it is acceded to the system recovery mode, I click to recover system and then leaves, the device Does not support system recovery.
Same here unfortunately
Can you to enter to fastboot? If yes is the bootloader locked or unlocked?
Potato997 said:
Can you to enter to fastboot? If yes is the bootloader locked or unlocked?
Click to expand...
Click to collapse
This is in flashboot mode, and yes unlock bootloader, but black screen, allows to restart with commands, but unfortunately I do not have much knowledge about this, I hope help, what steps can I take to be able to turn it on.
Try to flash again TWRP and boot to recovery.
By fastboot I can reset, install twrp, reboot, but still black screen, there is no vibration, but when connecting the phone, appears in android bootloader interface. What else can I do with commands
As I said, can you boot to TWRP?
Potato997 said:
As I said, can you boot to TWRP?
Click to expand...
Click to collapse
See
hanzox5 said:
See
Click to expand...
Click to collapse
....
But no reboot in recovery
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (13810 KB)...
OKAY [ 0.297s]
writing 'boot'...
OKAY [ 0.491s]
finished. total time: 0.788s
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (32960 KB)...
OKAY [ 0.704s]
writing 'recovery'...
OKAY [ 1.143s]
finished. total time: 1.862s
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (331661 KB)...
OKAY [ 7.077s]
writing 'cust'...
OKAY [ 8.053s]
finished. total time: 15.149s
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (452763 KB)...
OKAY [ 10.992s]
writing 'system'...
OKAY [ 11.640s]
sending sparse 'system' (458056 KB)...
OKAY [ 10.877s]
writing 'system'...
OKAY [ 11.137s]
sending sparse 'system' (459104 KB)...
OKAY [ 11.816s]
writing 'system'...
OKAY [ 12.201s]
sending sparse 'system' (457466 KB)...
OKAY [ 11.096s]
writing 'system'...
OKAY [ 11.214s]
sending sparse 'system' (460756 KB)...
OKAY [ 11.049s]
writing 'system'...
OKAY [ 11.190s]
sending sparse 'system' (135249 KB)...
OKAY [ 3.234s]
writing 'system'...
OKAY [ 3.302s]
finished. total time: 119.793s
C:\Program Files (x86)\HiSuite\hwtools>fastboot reboot
rebooting...
finished. total time: 0.016s
C:\Program Files (x86)\HiSuite\hwtools>
Reboot to recovery in this way: shut down the phone, press volume up + power button
Factory reset
Reboot
Do not enter recovery, still on black screen, can tell me which software I can flash it
I already told you like three times.. try both TWRP and stock recovery..
I installed the twrp as the stock recovery and try to enter using press volume up + power button, and nothing
Is there any way to force the phone to enter twrp via fastboot, would help me with commands.
hanzox5 said:
I installed the twrp as the stock recovery and try to enter using press volume up + power button, and nothing
Is there any way to force the phone to enter twrp via fastboot, would help me with commands.
Click to expand...
Click to collapse
fastboot boot recovery.img
Try that.
Also you should try the three buttons method now.
C:\Program Files (x86)\HiSuite\hwtools>fastboot boot recovery.img
creating boot image...
creating boot image - 33753088 bytes
downloading 'boot.img'...
OKAY [ 0.703s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.719s
hanzox5 said:
C:\Program Files (x86)\HiSuite\hwtools>fastboot boot recovery.img
creating boot image...
creating boot image - 33753088 bytes
downloading 'boot.img'...
OKAY [ 0.703s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.719s
Click to expand...
Click to collapse
ಠ_ಠ
Weird.
479/5000
Several times I installed TWRP and stock recovery, and I can not enter any of the 2 forms and even with the three buttons, I even purchase a micro SD of 32gb class 10, with this saying that the SD was the one that did not work.
Please, let's go again, I recommend doing from 0 to try to solve this blessed problem. That I should be doing, it will be possible to clean the cache and user data from fastboot, and from there to do something more.
Have you tried three button method with update.app in dload folder in SD card?
If yes, did it gave you some error/did the update started/when did it stopped?
If I have the sd, and inside the Dload folder, update.app, but it does nothing.
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?
The phone is the 5G unlocked US version model IN2025
I am running windows 10 with adb and fastboot set in my path variables
I installed the oneplus drivers that came with the phone
I ran the installer and this is the output:
Code:
Do you want to install ROM ( Reccomended )[Y/N]?y
< waiting for any device >
Sending 'recovery' (98304 KB) OKAY [ 2.403s]
Writing 'recovery' OKAY [ 0.285s]
Finished. Total time: 2.913s
Sending 'boot_a' (98304 KB) OKAY [ 2.400s]
Writing 'boot_a' OKAY [ 0.286s]
Finished. Total time: 2.871s
Sending 'dtbo' (24576 KB) OKAY [ 0.612s]
Writing 'dtbo' OKAY [ 0.066s]
Finished. Total time: 0.774s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending sparse 'system' 1/2 (720896 KB) OKAY [ 17.547s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'system_ext' (211392 KB) OKAY [ 5.403s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending sparse 'product' 1/2 (720896 KB) OKAY [ 17.475s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'vbmeta' (8 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.031s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.010s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.035s
CLICK ENTER RECOVERY FACTORY RESET AND REBOOT
UPGRADING FROM SAME ROM, JUST REBOOT
#########################################
# ONEPLUS LOVE! #
#########################################
Press any key to continue . . .
Can anyone help me on what needs to be done in order to have a successful install? Thanks
This should be asked in the relevant thread.
That being said.
1. Install a fresh OOS build, you have to have disabled any magisk modules before this.
2. Follow the instructions in the CRDroid thread.
*Note: you have to be using Windows 10 not 7
Make sure it's the 11 version not the 10 version of the ROM.
Make sure it's in the installer bat format.
You have to factory reset in the PE recovery after the installer has finished.
If you're still having issues then MSM format to 2.2 and then start at point 2
Bare in mind if you're on Verizon AFAIK it will not show your SIM, this is prevalent on all custom ROMs.
dladz said:
This should be asked in the relevant thread.
That being said.
1. Install a fresh OOS build, you have to have disabled any magisk modules before this.
2. Follow the instructions in the CRDroid thread.
*Note: you have to be using Windows 10 not 7
Make sure it's the 11 version not the 10 version of the ROM.
Make sure it's in the installer bat format.
You have to factory reset in the PE recovery after the installer has finished.
If you're still having issues then MSM format to 2.2 and then start at point 2
Bare in mind if you're on Verizon AFAIK it will not show your SIM, this is prevalent on all custom ROMs.
Click to expand...
Click to collapse
Thanks for the reply
I can not flash anything to "critical partitions"
when I issue the command: fastboot flashing unlock_critical
it tells me that the device is already unlocked
when I try to flash the rom using fastboot it tells me it failed because flashing is not allowed to critical partitions
the phone is now soft bricked where it boots to the logo and then shuts off and i need to hold the power buttons
btw holding vol up + down + power brings up fastboot but holding vol down + power never brings up recovery
EDIT: the output of fastboot oem device-info shows
verity mode = true
device unlocked = true
device critical unlock = false
charget screen enabled = true
reppinrengar said:
Thanks for the reply
I can not flash anything to "critical partitions"
when I issue the command: fastboot flashing unlock_critical
it tells me that the device is already unlocked
when I try to flash the rom using fastboot it tells me it failed because flashing is not allowed to critical partitions
the phone is now soft bricked where it boots to the logo and then shuts off and i need to hold the power buttons
btw holding vol up + down + power brings up fastboot but holding vol down + power never brings up recovery
EDIT: the output of fastboot oem device-info shows
verity mode = true
device unlocked = true
device critical unlock = false
charget screen enabled = true
Click to expand...
Click to collapse
You don't flash using fastboot just stick with the installer.bat file, it's in the ROM zip
If that doesn't work then your system is borked, in which case like I said just use the MSM tool.
You're done in several steps.
You should never need to unlock critical
reppinrengar said:
The phone is the 5G unlocked US version model IN2025
I am running windows 10 with adb and fastboot set in my path variables
I installed the oneplus drivers that came with the phone
I ran the installer and this is the output:
Code:
Do you want to install ROM ( Reccomended )[Y/N]?y
< waiting for any device >
Sending 'recovery' (98304 KB) OKAY [ 2.403s]
Writing 'recovery' OKAY [ 0.285s]
Finished. Total time: 2.913s
Sending 'boot_a' (98304 KB) OKAY [ 2.400s]
Writing 'boot_a' OKAY [ 0.286s]
Finished. Total time: 2.871s
Sending 'dtbo' (24576 KB) OKAY [ 0.612s]
Writing 'dtbo' OKAY [ 0.066s]
Finished. Total time: 0.774s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending sparse 'system' 1/2 (720896 KB) OKAY [ 17.547s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'system_ext' (211392 KB) OKAY [ 5.403s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending sparse 'product' 1/2 (720896 KB) OKAY [ 17.475s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'vbmeta' (8 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.031s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.010s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.035s
CLICK ENTER RECOVERY FACTORY RESET AND REBOOT
UPGRADING FROM SAME ROM, JUST REBOOT
#########################################
# ONEPLUS LOVE! #
#########################################
Press any key to continue . . .
Can anyone help me on what needs to be done in order to have a successful install? Thanks
Click to expand...
Click to collapse
Use the original OnePlus cable.