With unlocked bootloader we should be able to flash GSI. There are only two photos yet, but no instruction how to do it.
I tried yesterday flashing the image with fastboot, but ended in boot loops.
Any hint what I did wrong is welcome.
Regards,
Mart
@Mart Son
If you have fastboot commands (which you mention you do), just follow the Google Installation guide for GSI images and you'll be good to go,
Just remember to do a Factory Reset or fastboot command to wipe Userdata after the GSI flashing , or you'll end up with bootloops, plus keep in mind there is no Security options using Android 10 Google GSI image.
Yeah, I haven't wiped userdata... and ended in bootloops. In the meanwhile I read some guides and installed Android 10. When gaming it got slow and I went back to official.
Thanks @DrakenFX. I followed you since Axon7.
You did a lot for that device and I hope your knowledge will meet the Axon 10 the same
Related
Hi folks,
I'm in an odd situation, as my device is the EU 5G variant that before this mess, I believe was on the 10.0.3 OTA. From what I gather, this means fastboot images and MSM tools are scarce, and generally not available for my device. Like an idiot, I pressed on with trying to install the LineageOS 16 build from:
https://wiki.lineageos.org/devices/guacamole/install
For some reason, the LineageOS rom wouldn't flash through their recovery, so I tried some other ROMS I thought might be compatible to no avail.
After a series of mishaps, I managed to get TWRP to boot and formatted everything, including system. From then, I'm stuck in a bootloader loop without any kind of recovery or OS on either partition.
I can't fastboot boot any boot or recovery images, or fastboot flash boot. Everything just throws up the fastboot screen again, though I feel like this may just be a case of me not understanding the partitions.
I'm at a complete loss. I don't know how MSM tools work or if they exist for my variant.
How can I save my phone?
Thanks in advance
PM sent
Probably need to flash an entire fast boot rom and then wipe data.
Okay so yesterday I decided to finally try to install TWRP to flash a custom rom on the system, but never thought it would give so much headache. My drivers were bad, the system locked and android 11 updating making the phone all sorts of bugs, I was anxious to get rid of it, and I did somehow. I was unable to flash TWRP into the recovery as the system partition type is different than usual for it seems, but the recovery partition was all weird, "no command" was stuck in the screen even after a hard reset through there. So I got Magisk and got Root and used Smart Flash to install TWRP through the running system and it landed successful. But when going to the recovery the TWRP screen was flickering, but I could send ADB commands yet and boot normally, I just couldn't access the recovery functions yet. So I flashed a different version of the TWRP with the IMG and the zip folder and nothing worked then I realized that maybe I should erase the partition before flashing it and then the murder. I found a tutorial on erasing stuff, but the whole process cost me more than twelve hours as I messed with so many things and was kinda learning the hows and dos.
But then I saw the command "fastboot erase system -w" that was a shortcut for all cleanup processes and I was wanting to wipe it again even to recover my google backup and be able to use my messenger apps. But it did erase, of course, the whole system and everything, simply destroying everything, but yet stuck in the fastboot screen. What I did? Well, I downloaded the TGRZ of an older version of xiaomi mi a3 firmware, the android 10, as I was tired and thought that maybe if I downgraded it I would get my phone to get rid of android 11 bugs and sleep for good till tomorrow, that is today. I ran the script to wipe anything and install the system over it and it did successfully, then the message "successfully installed, press any key to finish" but then the prompt closed and the phone tried to reboot but fell into a hard brick. The computer recognizes the device as the name "QUSB_BULK_CID:0411_SN:EFCF04FD" and the hardware ID "USB\VID_05C6&PID_9008" matches the original.
So is there anything I could do yet? Phone warranty ended in january and that's why I tried that process, it is any worth?
BillyWroth said:
Okay so yesterday I decided to finally try to install TWRP to flash a custom rom on the system, but never thought it would give so much headache. My drivers were bad, the system locked and android 11 updating making the phone all sorts of bugs, I was anxious to get rid of it, and I did somehow. I was unable to flash TWRP into the recovery as the system partition type is different than usual for it seems, but the recovery partition was all weird, "no command" was stuck in the screen even after a hard reset through there. So I got Magisk and got Root and used Smart Flash to install TWRP through the running system and it landed successful. But when going to the recovery the TWRP screen was flickering, but I could send ADB commands yet and boot normally, I just couldn't access the recovery functions yet. So I flashed a different version of the TWRP with the IMG and the zip folder and nothing worked then I realized that maybe I should erase the partition before flashing it and then the murder. I found a tutorial on erasing stuff, but the whole process cost me more than twelve hours as I messed with so many things and was kinda learning the hows and dos.
But then I saw the command "fastboot erase system -w" that was a shortcut for all cleanup processes and I was wanting to wipe it again even to recover my google backup and be able to use my messenger apps. But it did erase, of course, the whole system and everything, simply destroying everything, but yet stuck in the fastboot screen. What I did? Well, I downloaded the TGRZ of an older version of xiaomi mi a3 firmware, the android 10, as I was tired and thought that maybe if I downgraded it I would get my phone to get rid of android 11 bugs and sleep for good till tomorrow, that is today. I ran the script to wipe anything and install the system over it and it did successfully, then the message "successfully installed, press any key to finish" but then the prompt closed and the phone tried to reboot but fell into a hard brick. The computer recognizes the device as the name "QUSB_BULK_CID:0411_SN:EFCF04FD" and the hardware ID "USB\VID_05C6&PID_9008" matches the original.
So is there anything I could do yet? Phone warranty ended in january and that's why I tried that process, it is any worth?
Click to expand...
Click to collapse
You should never try to install software for another board (mi mix 3 global is codenamed "perseus")...
If you are unable to reach fastboot and recovery, you may refer to this, since it sounds like your phone is in EDL mode:
Reboot to EDL mode from FASTBOOT!
Reboot to EDL mode from FASTBOOT! No more Test Point Method needed Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the...
forum.xda-developers.com
I never encountered this issue so only do this if you're absolutely sure you have no other means of flashing anything on it (i.e. through fastboot), and use the appropriate firmware at all times for your specific model
CriGiu said:
You should never try to install software for another board (mi mix 3 global is codenamed "perseus")...
If you are unable to reach fastboot and recovery, you may refer to this, since it sounds like your phone is in EDL mode:
Reboot to EDL mode from FASTBOOT!
Reboot to EDL mode from FASTBOOT! No more Test Point Method needed Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the...
forum.xda-developers.com
I never encountered this issue so only do this if you're absolutely sure you have no other means of flashing anything on it (i.e. through fastboot), and use the appropriate firmware at all times for your specific model
Click to expand...
Click to collapse
well it seems I recovered it back, I bricked it and somehow it just got into EDL mode without cable or opening it up. So I found a tutorial back on reddit showing how use GFIL to install the stock rom back. I used android 10 stock rom before bricking it, but as I just flashed everything on empty partitions it didn't work, it seems that the Qualcomm setup needs some kind of previous work to set everything up. Anyways I managed to boot it, but now I'm aware that I should use Lineage recovery instead of TWRP as Mi A3 support is lacking, that's why after installing it I got it flickering (no compatible version with the latest Android 11 firmware).
BillyWroth said:
well it seems I recovered it back, I bricked it and somehow it just got into EDL mode without cable or opening it up. So I found a tutorial back on reddit showing how use GFIL to install the stock rom back. I used android 10 stock rom before bricking it, but as I just flashed everything on empty partitions it didn't work, it seems that the Qualcomm setup needs some kind of previous work to set everything up. Anyways I managed to boot it, but now I'm aware that I should use Lineage recovery instead of TWRP as Mi A3 support is lacking, that's why after installing it I got it flickering (no compatible version with the latest Android 11 firmware).
Click to expand...
Click to collapse
hello, im having maybe a similiar case with my phone (in this case its a MI A3) i installed "succefully" evolution x 6.3 on my phone and everthing was ok with a few bugs, the only problem was that mi cannot connect to internet, so i decided to restart the phone and now my phone just don't turn on, the power button don't respond and i cannot start up my phone and its just a black screen, if u remeber ¿can u pass the tutorial that u saw on reddit? maybe it can help me
Hi Guys,
I think I f...ed up big time...
My device was rooted and I tried to unroot/factory reset to give it to my wife. Since I'm now sitting here for about 5 hrs I try to summarize what I've been doing:
1. I started with trying to Flash a Factory Image with the ALL-IN-ONE Tool
- My Device was on the Latest Oxygen OS 11 and I just stupidly followed the instructions of the Tool and downloaded a OOS 10 based Stock Rom and flashed it (thats where my nightmare began)
- After I flashed the OOS 10 Stock Rom I was Stuck in at the Open Bootloader warning screen ("the boot loader is unlocked and software integrity cannot be guaranteed ...")
2. Since there is no (at least I couldn't find one for the life of me) OOS 11 fastboot stock ROM I tried to downgrade via an OOS Beta ROM I found in a downgrade guide
- That didn't work either and I ended up stuck at the same Screen
3. After some googling I came across this guide and tried to manually flash a none fastboot OOS 11 ROM by manually extracting all the images of the payload.bin
- After I extracted all the images I flashed them one by one as mentioned in the guide via fastboot and this ended up with
Qualcomm Crash Dump mode dm-verity device corrupted force dump Kernel restart
Click to expand...
Click to collapse
4. After that I panicked a little since I've never seen this error before and tried to Flash the OOS 10 based Stock rom via the ALL-IN-ONE Tool again
- This worked with no errors but now I'm still stuck in the "Open Bootloader warning Screen"
Since then I tried Step 4 with another OOS 11 none fastboot ROM but now I keep getting following error everytime I try to flash one of the extracted images via fastboot (which worked before):
FAILED (remote: Flashing is not allowed for Critical Partitions
Click to expand...
Click to collapse
I did some research, seems like this error indicates a locked bootloader which is wrong, bootloader is still unlocked.
Even if I try to unlock the bootloader again I get the reply that bootloader cannot be unlocked since it already is unlocked.
So now I'm stuck with a completely f...ed up device with absolutely no clue if and how I can fix this.
I really hope anyone of you guys can help ...
Apologies for the bad writing but it's 5 am and I'm tired and frustrated af ...
greetings from Germany.
Timo
EDIT: Oh and yes, I know about the MSM-Tool and tried it but I can't get it to work since my device is not showing. I followed this guide several time but nothing is happening and my device is not even showing in the device manager. Only time it shows in the device manager is when in fastboot mode.
Guys I finally did it.
I deinstalled all stale/inactive drivers and reinstalled the Qualcomm drivers and finally managed to get the MSM Tool up and running and revived the phone.
I have a new Pixel 4a, Android 12. I want to use lineage 19.1. I try already several days to flash TWRP, sunfish_twrp3.6.1-11 or sunfish_twrp11-test3. No success. Finally I write fastboot flash boot_a_twrp.img instead of fastboot boot twrp.img. It ended up with the screen of teamwin, hanging there. Now the pixel is not booting to android any more but each time to the incomplete teamwin screen. So I tried to flash the newest factory image. No success : "writing 'boot' failed (remote: Failed to write to partition Not Found)
I need help urgently. Thanks!
Henneranek said:
I have a new Pixel 4a, Android 12. I want to use lineage 19.1. I try already several days to flash TWRP, sunfish_twrp3.6.1-11 or sunfish_twrp11-test3. No success. Finally I write fastboot flash boot_a_twrp.img instead of fastboot boot twrp.img. It ended up with the screen of teamwin, hanging there. Now the pixel is not booting to android any more but each time to the incomplete teamwin screen. So I tried to flash the newest factory image. No success : "writing 'boot' failed (remote: Failed to write to partition Not Found)
I need help urgently. Thanks!
Click to expand...
Click to collapse
I don't think you're providing enough info. "I tried to flash the newest factory image" doesn't tell useful people what you did. I'm not useful, anyway.
I wouldn't use TWRP on the 4a. I'm using LOS recovery. You can follow the instructions (read the whole thing first) here: https://wiki.lineageos.org/devices/sunfish/install
That should allow you to do a clean install of LOS19.
Thank you for giving advice. I followed exactly your recommended web-site (Install LineageOS on sunfish, Temporarily booting a custom recovery using fastboot). From what I understand the first step is to install a recovery which in my case was sunfish_twrp3.6.1-11.img . I did not work. I also tried an older twrp.img. "fastboot flash boot twrp.img" did not work. I read and read, learned about 2 slots, without a deep understanding. Then I tried " fastboot flash boot_a_twrp.img". It seemed to work. But when I reboot into recovery it is stuck at the screen of teamwin (see attachment).
I thought to give up and do a factory reset. But there I got this: Failed to write to partition Not Found. What can I do now? Is there a way to do a factory reset to slot_b ?
If you try to help me please remember that I don't have enough knowledge to understand abbreviations.
Henneranek said:
Thank you for giving advice. I followed exactly your recommended web-site (Install LineageOS on sunfish, Temporarily booting a custom recovery using fastboot). From what I understand the first step is to install a recovery which in my case was sunfish_twrp3.6.1-11.img . I did not work. I also tried an older twrp.img. "fastboot flash boot twrp.img" did not work. I read and read, learned about 2 slots, without a deep understanding. Then I tried " fastboot flash boot_a_twrp.img". It seemed to work. But when I reboot into recovery it is stuck at the screen of teamwin (see attachment).
I thought to give up and do a factory reset. But there I got this: Failed to write to partition Not Found. What can I do now? Is there a way to do a factory reset to slot_b ?
If you try to help me please remember that I don't have enough knowledge to understand abbreviations.
Click to expand...
Click to collapse
if it goes into bootloader head over to the android flash tool and give that a try,,https://source.android.com/setup/contribute/flash
To hammered58 Thank you for this suggestion reg. android flash tool. This seems very complicated and I don' t understand some terms. I am a NOOB.
In my Pixel 4a the slot a is somehow obstructed. Can't I use slot b to do a factory reset?
Henneranek said:
To hammered58 Thank you for this suggestion reg. android flash tool. This seems very complicated and I don' t understand some terms. I am a NOOB.
In my Pixel 4a the slot a is somehow obstructed. Can't I use slot b to do a factory reset?
Click to expand...
Click to collapse
Its not complicated at all,, just put you phone in fastboot, which I know you have done before , go here (https://flash.android.com) and follow the on screen prompts, select any factory image and start.
Dear hammered58, I am so thankful to you! Thank you for encouraging me to use the Android Flash Tool. I was skeptical. To undo the pop-up blocker in Chrome was complicated for me. After some failures because I was not patient enough I finally succeeded.
Henneranek said:
Dear hammered58, I am so thankful to you! Thank you for encouraging me to use the Android Flash Tool. I was skeptical. To undo the pop-up blocker in Chrome was complicated for me. After some failures because I was not patient enough I finally succeeded.
Click to expand...
Click to collapse
Good to know it worked for you
Hi guys
I have an edge s with a stock g100 firmware
can someone refer me to a guide that will help me install custom recovery?
right now I don't seem to have any recovery menu
In fact you can find all information here:
https://wiki.lineageos.org/devices/nio/
and here:
https://lineageosroms.com/nio/
Though:
You have to unlock your bootloader first with the unlock key from the Motorola website: https://accounts.motorola.com/ssoauth/login?TARGET=https://motorola-global-portal.custhelp.com/cc/cas/sso/redirect/standalone/bootloader/unlock-your-device-b
To unlock:
adb reboot bootloader
fastboot devices
fastboot oem unlock UNLOCK_KEY
Important:
Start point should be latest G100 firmware
Afterwards You have to flash additional partitions (see information in first two links)
Afterwards You have to copy a to be (see information in first two links)
To flash recovery:
adb reboot bootloader
fastboot devices
fastboot flash boot_a <recovery.img>
fastboot flash boot_b <recovery.img>
Where <recovery.img> is the name of the recovery you want to flash.
I would suggest the LOS recovery:
https://download.lineageos.org/nio
Then you can reboot into LOS recovery, format data and install LOS.
This is as I remember it when I did the first install.
Hope it helps... ;-)
thanks for answering, I really appreciate it
I've tried that guid on the LOS website but it threw my phone into a boot look after which I had no choice but to factory reset my device
I want to avoid factory resetting my device if I can
I've found another guide and would really appreciate if you could give me your opinion on it
Will the "fastboot format userdata" command factory reset my device?
nate8819 said:
thanks for answering, I really appreciate it
I've tried that guid on the LOS website but it threw my phone into a boot look after which I had no choice but to factory reset my device
I want to avoid factory resetting my device if I can
I've found another guide and would really appreciate if you could give me your opinion on it
Will the "fastboot format userdata" command factory reset my device?
Click to expand...
Click to collapse
Yes, it will reset your device.
And...why do you need custom recovery?
If you don't have custom ROM to install, custom recovery is useless.
If you want to install LOS then you need custom recovery for LOS, not TWRP.
May be my first post about installation experience will help also.
In fact I had the same experience; after installing custom recovery and LOS I had a bootloop.
Though, as you can boot in fastboot, it is not neccessary to factory reset; you can still do whatever you want... ;-)
Some new installation experiences
Hi there, I don't know how first installation of Lineage (and probably other Android tastes) went, though I had some issues I would like to share for people trying to install another OS then factory setup in the future. I bought a new fresh...
forum.xda-developers.com