hey been out of the android modding scene for quite a few years now, been playing around with some GSI's, all bootloop at bootanimation... (Stock/Kirisakura patched via magisk) boot to animation, non patched kernels bootloops at google screen, cant flash permissiver, any other tricks i can try? adb aint active neither in any kernel
Cheers
stevendeb25 said:
hey been out of the android modding scene for quite a few years now, been playing around with some GSI's, all bootloop at bootanimation... (Stock/Kirisakura patched via magisk) boot to animation, non patched kernels bootloops at google screen, cant flash permissiver, any other tricks i can try? adb aint active neither in any kernel
Cheers
Click to expand...
Click to collapse
I really don't know much about GSI's, but don't you have to disable AVB before flashing one? Basically disabling vbmeta verification and verity (which would require a factory reset afterwards)? Not sure if you've done or tried this, so just throwing it out there.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Generic System Images (GSIs) | Platform | Android Developers
developer.android.com
Some more information would be helpful. What did you do exactly? Best tell us every step, every file you used and when.
You say that ADB isn't active. Does that mean that you can neither boot into recovery/your PC does not recognize the phone/ you can't use fastboot? You say that your device bootloops, that means it boots up at least, so your bootloader is still intact/working?
These two websites here are your first go to in that case:
Google Pixel - Update and Software Repair
&
Android Flash Tool
flash.android.com
Morgrain said:
Some more information would be helpful. What did you do exactly? Best tell us every step, every file you used and when.
You say that ADB isn't active. Does that mean that you can neither boot into recovery/your PC does not recognize the phone/ you can't use fastboot? You say that your device bootloops, that means it boots up at least, so your bootloader is still intact/working?
These two websites here are your first go to in that case:
Google Pixel - Update and Software Repair
&
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
The bootloader has nothing to do with the bootanimation. If you see the bootanimation, the bootloader has done it's work ages before.
From stock
Fastboot reboot bootloader
Fastboot reboot fastboot
Fastboot erase system
Fastboot flash system gsi.img
Fastboot reboot
Nothing data corrupted
Rebooted back to bootloader
Fastboot reboot recovery
Data reset
=Google logo
Fastboot reboot bootloader
Fastboot flash boot magisk_patched.img
Fastboot reboot
=Bootanimation
ADB ain't enabled in boot.imgs so can't pull logcats to try to see why no boot.
Tried lineage, octativeos, LeOS, phusson, same with all GSI's
P.s phone is intact and easily put back to stock
stevendeb25 said:
From stock
Fastboot reboot bootloader
Fastboot reboot fastboot
Fastboot erase system
Fastboot flash system gsi.img
Fastboot reboot
Click to expand...
Click to collapse
As @Lughnasadh said, it looks like you're missing the disabling of AVB by flashing Google's custom vbmeta.img before installing the GSI image.
Note: If your device has adopted Android Verified Boot (AVB), download and flash the following image to disable AVB before flashing a GSI: vbmeta.img
Click to expand...
Click to collapse
As above, see here: https://developer.android.com/topic/generic-system-image#flash-gsi (blue box).
hi thanks for that, flash vbmeta
still stuck on bootanimation.
i have tried a number of gsi's does this error matter when flashing gsi? "Invalid sparse file format at header magic" still installs fine
Related
My phone is arc and I installed like this.
1. Xperia Arc S
2. Super Jelly Bean 2.0
But I tried to install fxp209 for easy updating, but I could not flash boot.img.
ths adb driver installed as this picture.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And I tried to install kernel as this.
but the message is only "flashing...", and not end it.
Please let me know what's problem.
Thanks in advance.
Default fastboot flash problem
First question is your bootloader unlocked!!
If yes try flashing like below
How to fastboot a kernel
(1) Download kernel .boot img place in folder Windows/Flashtool/Firmware
View attachment 1787067
(2) Press lightening bolt
(3) Select Fastboot mode
(4) Connect phone in Fastboot mode (Hold Menu Button ) then connect your phone to pc
(5) Choose select kernel to flash in Fastboot on pc
(6) Wait -until finished 10 seconds tops
(7) Done! switch phone on boot to cwm wait for vibrate/blue light press down/up/or back button depending on kernel or age of phone
Also try booting into fasboot manually as above (step 4)
Also if the fxp kernel not working try another compatible kernel there is plenty in the forum
First question is your bootloader unlocked!!
Click to expand...
Click to collapse
He is using CM10 based ROM so I think his bootloader must be unlocked.
To OP: You can try to flash a kernel with a fastboot and CMD like a real man ; D. Google how to use fastboot.
pypcier said:
He is using CM10 based ROM so I think his bootloader must be unlocked.
To OP: You can try to flash a kernel with a fastboot and CMD like a real man ; D. Google how to use fastboot.
Click to expand...
Click to collapse
Lol I knew that But believe me I have seen people try to flash cm based rom's/kernels with locked bootloaders that's why I never presume it is unlocked unless they have stated it in the post that it is unlocked :good:
My phone is "bootloader unlocked".
And I tried to flash at command line, but it didn't finished.
The correct command is fastboot flash boot kernelname.img See the link in my sig for more help.
XperienceD said:
The correct command is fastboot flash boot kernelname.img See the link in my sig for more help.
Click to expand...
Click to collapse
Yes, I did "fastboot.exe flash boot boot.img".
Try again without an .exe extension. Just type fastboot flash boot kernel.img
After command "fastboot flash boot kernelname.img", command line shows;
sending 'boot' <6430 KB>....
Click to expand...
Click to collapse
That's how it's supposed to be. Show us the rest of CMD content after typing that command.
Hi,
PLEASE VISIT THE CORRECT AND OFFICIAL THREAD HERE. THIS THREAD WILL NO LONGER BE UPDATED.
As some of you may know, @beroid has a TWRP 3.0.0-0 which he released on his Unofficial CM13 thread. I was unaware of this but lukily (thanks to @yasteellutch) I was told about this new TWRP. So, if you are looking for it, or are unaware of it because you dont look through the original thread, well here it is and now you know!
Installing
Go the download link here and you will be presented with two files.
FOR CURRENT TWRP USERS:
Download the zip file and flash it within TWRP. Your device should reboot automaticly into the new TWRP.
FOR NEW USERS:
Download the img file and place it in your platform-tools folder on your pc. Then reboot your device in fastboot. Then, open a command window in that folder and run commands:
Code:
fastboot -i 0x2970 erase recovery
- IF YOU GET WAITING FOR (ANY) DEVICE SKIP TO NEXT PART
Then enter
Code:
fastboot -i 0x2970 flash recovery recovery.img
Disconnect the device from your computer. Then remove the battery. Then replace the battery and press VOLUME DOWN and POWER to rebbot in to recovery mode to verify the installation. IF YOU DONT, IT WONT WORK!
IF YOU GET WAITING FOR DEVICE:
Do the same commands but without the vendor id eg.
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Credits to:
@beroid for making this. IT IS ALL @beroid's WORK!
So, now you know about TWRP 3.0.0-0!
SCREENSHOTS:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-Jev
Hello,
Thank you, I have used it since few weeks without problem. But your TWRP build doesn't seem to include encryption support. TWRP asks for the password but it can't decrypt data partition. Is there some kind of missing module or this is not officially support by TWRP 3 ?
jevtheboss said:
Hi,
As some of you may know, @beroid has a TWRP 3.0.0-0 which he released on his Unofficial CM13 thread. I was unaware of this but lukily (thanks to @yasteellutch) I was told about this new TWRP. So, if you are looking for it, or are unaware of it because you dont look through the original thread, well here it is and now you know!
Installing
Go the download link here and you will be presented with two files.
FOR CURRENT TWRP USERS:
Download the zip file and flash it within TWRP. Your device should reboot automaticly into the new TWRP.
FOR NEW USERS:
Download the img file and place it in your platform-tools folder on your pc. Then reboot your device in fastboot. Then, open a command window in that folder and run commands:
Code:
fastboot -i 0x2970 erase recovery
- IF YOU GET WAITING FOR (ANY) DEVICE SKIP TO NEXT PART
Then enter
Code:
fastboot -i 0x2970 flash recovery recovery.img
Disconnect the device from your computer. Then remove the battery. Then replace the battery and press VOLUME DOWN and POWER to rebbot in to recovery mode to verify the installation. IF YOU DONT, IT WONT WORK!
IF YOU GET WAITING FOR DEVICE:
Do the same commands but without the vendor id eg.
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Credits to:
@beroid for making this. IT IS ALL @beroid's WORK!
So, now you know about TWRP 3.0.0-0!
SCREENSHOTS:
-Jev
Click to expand...
Click to collapse
Not sure if -i 0x2970 is needed for fastboot think its only for fastboot oem
No need for battery removal there is a fastboot command ........fastboot reboot......... that does the same thing
dnahc said:
Hello,
Thank you, I have used it since few weeks without problem. But your TWRP build doesn't seem to include encryption support. TWRP asks for the password but it can't decrypt data partition. Is there some kind of missing module or this is not officially support by TWRP 3 ?
Click to expand...
Click to collapse
Hi,
Please could you visit the thread here and ask the question there. I think TWRP 3.0.1 will fix the issue. :good: If not, on the TWRP website, 3.0.2 has been released which is supposed to fix some decryption issues so please wait for the thread (the one I linked to earlier) to be updated
i just need to flash twrp recovery on my redmi note 5 last miui 11.0.3 android version is 9
i just follow the steps but i didnt flash to twrp recovery when i write the command in adb//
some peoples telling me that the last twrp img recovery contain password or something like this any one can help me
Unlock bootloader first
Re: @wickednight
TWRP is a custom recovery. Flash it need an unlocked bootloader.
If your bootloader is locked, go to https://en.miui.com/unlock/ to apply for unlocking permissions. Download Mi Unlock Tool and proceed to unlock. A waiting period and instruction will then be displayed in Mi Unlock Tool. Use your phone actively during the waiting period.
More information about unlocking: https://c.mi.com/thread-2262302-1-0.html
Once you successfully unlocked the bootloader, in theory, you can flash any file as you want. However, Xiaomi has enabled ANTI_ROLLBACK feature on the Redmi Note 5 (whyred). Check the anti level first so you can choose the right flashing method.
Install all drivers needed on your computer and connect your phone to PC. Hold POWER and VOLUME DOWN for about 11s to enter fastboot mode. Open a command prompt window in the adb tool folder, type this command to check the anti level of your phone:
fastboot getvar anti
Look for the number after "anti:" in output imformation in order to know about the anti level of your phone. The flashing steps is a little different for anti3 devices and anti4 devices.
If the anti level is 3 or lower, you can flash the twrp recovery img file using fastboot command directly. Make sure the twrp img file has been placed in the adb tool folder, and has been renamed to "twrp.img".Type this following command to flash twrp recovery easily:
fastboot flash recovery twrp.img
Check the output, make sure "sending recovery" and "writing recovery" are all OK. Now the recovery on your phone is TWRP recovery. Hold POWER and VOLUME UP to force the phone reboot into twrp recovery.
If the anti level is 4 or higher, the steps is more complicated. You must bypass the ARB first. Download the whyred-arbpass.img and flash it to antirbpass partition or the ARB will block all your flashing commands. All needed files I will put their links at the end of the post. Type this command to bypass the ARB for one time. You need to use the whyred-arbpass.img to bypass the ARB everytime you want to flash. Make sure the whyred-arbpass.img is placed in the adb tool folder.
Command to bypass ARB and allow you to flash the recovery:
fastboot flash antirbpass whyred-arbpass.img
Check the output, make sure "sending antirbpass" and "writing antirbpass" are all OK. Now you can flash the recovery like anti3's devices:
fastboot flash recovery twrp.img
Check the output, make sure "sending recovery" and "writing recovery" are all OK. Now the recovery on your phone is TWRP recovery. Hold POWER and VOLUME UP to force the phone reboot into twrp recovery.
All needed files:
1. TWRP recovery img files for whyred:
https://dl.twrp.me/whyred/
2. ANTI_ROLLBACK bypasser file (need to flash it to antirbpass partition):
https://drive.google.com/open?id=1cbHeULrh62R0COSD-RU9OwsWFR2zyfmc
MD5:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you find it useful, please click thanks.
The situation
in 2020 Jan my phone display broken, so i keep my phone aside and switched to iPhone. now i fixed the screen and phone booted and there was an update i installed it and rebooted phone, but phone never boot to OS after that.
what i can access now
1. fastboot
2. recovery
3. i can install twrp
the Problem
fastboot rom flash end with saying system, vendor, product partition not found. i tiring to enter edl mode and not happening., tried with 3 PC with usb 3 and usb 2 ports.
Any suggestion will be helpful.
Have you tried the MSM tool? Find the right firmware for your model and when phone is off hold volume up and down and make sure the cable is in the laptop or PC you are using and stick in the plug and it should say connected on MSM tool but the phone screen will still be black and make sure to untick the shasum box but leave auto reboot ticked and run it and it will reboot when done.
yes, i have the Indian variant.
when is press vol- and vol + then plug it in nothing happens PC not detecting any thing. not even unknown device. when i leave the vol up and down device start and goes to fastboot.
anything i am missing? i triggered edl from twrp also phone reboots and stuck at bootloader unlocked message screen.
is hd1910 is 7T pro? but I have 7T.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
edl not triggering
fastboot rom gives this error
any suggestions are welcome.
Needs fastbootD to flash critical partitions
HueyT said:
Needs fastbootD to flash critical partitions
Click to expand...
Click to collapse
yes, "fastboot reboot fastboot" from fastboot right. i am flashing from there only.
system , vendor , product partitions are zero size and unable to mount.
sathara said:
system , vendor , product partitions are zero size and unable to mount.
Click to expand...
Click to collapse
Bootloader unlocked?
HD1910 is OP7T PRO and not compatible with OP7T roms
HueyT said:
Bootloader unlocked?
Click to expand...
Click to collapse
yes
HueyT said:
HD1910 is OP7T PRO and not compatible with OP7T roms
Click to expand...
Click to collapse
but why it showing in my device manager. i have 7T only.
Try latest Qualcomm USB 9008 driver to get EDL or MSM tool to work
in the past week i download over 21 gb.
you have any URL?
but why the PC don't even see anything?
Unzip and run in 64bit win10
HueyT said:
Unzip and run in 64bit win10
Click to expand...
Click to collapse
bro, i tried everything. i have 6 cables , 3 laptops , USB 3, USB 2.
with type c to c cable when try to boot to edl in the PC i can here a sound, but nothing showing in device manager.
any other way other than edl?
fastboot working good but some partitions is not found, is there any way to recreate the partitions?
Why don't u fastboot install custom roms like yaap: https://t.me/yaapop7
It is so much better than OOS11
HueyT said:
It is so much better than OOS11
Click to expand...
Click to collapse
i need to restore partition table before doing that
Have u tried adb sideload OOS11.zip from twrp?
After 168 hours bought. I've unlocked my Xiaomi 11 lite 5G NE.
I follow the offical guide to install the latest Lineageos. https://wiki.lineageos.org/devices/lisa/install
here is my operations:
Enable devleoper mode and USB debugging on my device.
adb devices shows OK, it can list my device.
enter the fastboot mode, type `fastboot devices` shows ok, it can list my device.
I've download all files from this page: https://download.lineageos.org/devices/lisa/builds
lineage-19.1-20230325-nightly-lisa-signed.zip
boot.img
dtbo.img
super_empty.img
vbmeta.img
vendor_boot.img
then I enter the fastboot mode in my phone and connected to my computer(adb, fastboot, usb drivers was installed).
I follow the Lineageos instructions and type the following command.
fastboot flash dtbo <dtbo>.img //dtbo.img listed above
fastboot flash vendor_boot <vendor_boot>.img //vendor_boot.img listed above
fastboot flash boot <recovery_filename>.img //boot.img listed above
then the guide let me enter the recovery mode(hold power + volumn up), my phone shows this image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It can not enter the recovery mode like the guide says.
Hello,
don't know if it could be a reason, but was official miui 13 or 14 (Android 12 or 13) ?
newbie_or_not_newbie said:
Hello,
don't know if it could be a reason, but was official miui 13 or 14 (Android 12 or 13) ?
Click to expand...
Click to collapse
I don't know which version of miui installed in my phone. I didn't check my phone's default miui version. I've just brought this phone a week.
In lineage OS flash instructions, it says this :
WARNING: Before following these instructions please ensure that the device is currently using Android 12 firmware.
Don't know if it can softbrick your phone if it's android 13.
newbie_or_not_newbie said:
In lineage OS flash instructions, it says this :
WARNING: Before following these instructions please ensure that the device is currently using Android 12 firmware.
Don't know if it can softbrick your phone if it's android 13.
Click to expand...
Click to collapse
I think that's the really problem. I will recovery the offical miui and try again.
it cold possibile a problem with usb driver or cable problems
i think you only flash dtbo.img , boot and vendor_boot did not get on the device
start you lisa device with fastboot (power + Vol down)
fastboot flash boot_ab .\path to boot.img all files in the same folder
Code:
PS C:\lisa\lineageos19\> .\fastboot.exe flash boot boot.img
press enter,
than connect the cable after its finish unplug the cable
an do it with dtbo and vender_boot the same way
Trismo said:
it cold possibile a problem with usb driver or cable problems
i think you only flash dtbo.img , boot and vendor_boot did not get on the device
start you lisa device with fastboot (power + Vol down)
fastboot flash boot_ab .\path to boot.img all files in the same folder
Code:
PS C:\lisa\lineageos19\> .\fastboot.exe flash boot boot.img
press enter,
than connect the cable after its finish unplug the cable
an do it with dtbo and vender_boot the same way
Click to expand...
Click to collapse
It doesn't work. I've tried.
newbie_or_not_newbie said:
In lineage OS flash instructions, it says this :
WARNING: Before following these instructions please ensure that the device is currently using Android 12 firmware.
Don't know if it can softbrick your phone if it's android 13.
Click to expand...
Click to collapse
No, I've tried to recovery Miui. And ensuring my Miui to equal android 12. It is still not work.
treelu said:
It doesn't work. I've tried.
No, I've tried to recovery Miui. And ensuring my Miui to equal android 12. It is still not work.
Click to expand...
Click to collapse
And Miui Start ?
Hi
Bro no worry
Flash the the latest xiaomi.eu rom for lisa
Via fastboot and it will boot normaly
Ps all data will be erased
Nillesse said:
Hi
Bro no worry
Flash the the latest xiaomi.eu rom for lisa
Via fastboot and it will boot normaly
Ps all data will be erased
Click to expand...
Click to collapse
Thanks. I am not worry. My phone can still work with Miui.