I tried to flash android 10 based gsi for my coolpad but after wiping system,the new gsi didnot managed to get flashed.
Since I was using aosp android 9 pie beforehand,so i tried to flash that,which was working before the wipe, but it was also showing errors after errors so i downloaded the stock firmware and tried to flash the rom through twrp but the terminal stuck at patching system image unconditionally.
I tried to flash rom with fastboot and qfil with no success.
Related
EDIT: Hey guys, so since the previous post I have tried numerous things - most notably manually flashing the system, boot and recovery images directly with fastboot. While I was able to do this (using B361 and currently B320) the phone got stuck in a bootloop even though the official recovery successfully did a factory reset and cache wipe. I am fairly certain that if I can get the rollback image to flash I will be able to revert back to stock - but currently this is proving to be difficult. Flashing the rollback image directly with dload fails and I'm currently considering flashing the image through fastboot. Checking the image on firmware extractor tool shows the following:
CRC
CURVER
EFI
RECOVERY
RECOVERY2
VERLIST
VERSION
What extracted image will I be able to flash through fastboot? Thanks for any help in advance
Hey guys,
Firstly I have read through and tried all the usual methods of trying to get back to stock (MM or Nougat) after upgrading to B361. I am currently unable to flash any images through the dload method (not rollback, not nougat, anything). What I've tried flashing (all failed):
L19C185B361 (full)
L19C185B220 (full)
L19C185B210 (full)
L19C185B320 (OTA)
Official rollback image
This is the path I followed:
L19C185B210
MM LOS
L19C185B220
L19C185B320
L19C185B361
(Tried to reflash L19C185B361, failed)
Rollback, failed
TWRP L19C185B220, messed up system partition
Rollback still failed
L19C185B220 still failed
L19C185B361 still failed
Currently running a TWRP flash of L19C185B321, a beta leak image that doesn't work properly
The TWRP running is the Nougat TWRP (MM TWRP not working) leading me to be believe that there is still an official Nougat presence somewhere on the system. I hace an unlocked bootloader, fastboot and adb access but no root. Any help will be greatly appreciated as I've been struggling for over 10 hours now.
Bump - changed the thread question in the hope of getting help
Hello, I have a problem with my Xiaomi Redmi 4X phone, as I said, I can not flash any Custom ROM for Android 8.1 All this happened after I put my phone in service to replace the display on which I've broken it. Now any version of Android 8.1 I try to flash results in a bootloop. I have to mention 3 things
1. In TWRP when flashing I noticed that all Custom ROMs are stuck in "Flashing system files ..." for a few seconds after saying that it ended flash-but did not abssolut anything.
2. Now a few hours I accidentally flashed Pixel Experince, but now I have the same problem.
3. I can not flash any versions of TWRP.Not much but...
THIS IS HAPPENING ONLY ON THE ANDROID OREO ROMs, Nougat ROMs works perfectlly
Try to flash first latest version of twrp or you can flash redwolf recovery then flash firmware v40 then try clean flash for oreo roms
As mentioned by above user...(latest TWRP recovery and firmware is must)
Flash latest TWRP recovery, 3.2.1-0 should be fine but there's update available 3.2.2.-0 so any will do.
Next, flash latest firmware.
Clean flash is must when changing OS.
It's most likely you don't have latest TWRP recovery and firmware.
Do backup first.
Hi guys.
The problem is gsi is Bootlooping every time in custome vendor stock vendor no matter how much i try to install with different methods by different vendors rom.
Tried formatting many times, changing file system, flashing vbmeta, even flashed on both slots nothing happened same Bootloop.
Even tried flashing no verify decryption zip, magisk.
Don't get it what's the problem its booting but Bootlooping.
If gsi is not supported or corrupt img so it'll not boot right? But booting means it gets installed.
But every time the gsi get stuck at bootanimation
Need help what to do now because it installing successfully everytime but at the end Bootlooping.
Tried ported gsi roms
And official gsi roms
Those are not booting..
Urgent help will be appreciated and I'll be very thankful.
:good:
arya_tech said:
Hi guys.
The problem is gsi is Bootlooping every time in custome vendor stock vendor no matter how much i try to install with different methods by different vendors rom.
Tried formatting many times, changing file system, flashing vbmeta, even flashed on both slots nothing happened same Bootloop.
Even tried flashing no verify decryption zip, magisk.
Don't get it what's the problem its booting but Bootlooping.
If gsi is not supported or corrupt img so it'll not boot right? But booting means it gets installed.
But every time the gsi get stuck at bootanimation
Need help what to do now because it installing successfully everytime but at the end Bootlooping.
Tried ported gsi roms
And official gsi roms
Those are not booting..
Urgent help will be appreciated and I'll be very thankful.
:good:
Click to expand...
Click to collapse
You should try generic gsi from this site https://mirrors.lolinet.com/firmware/gsi/
Choose generic AB.. currently latest one is from 11th July @ Developer Preview 5.
Download Havoc os, flash it on slot A.
Reboot to slot B, wipe everything and reboot to recovery again.
Then flash gsi file, permissiver v4, darkness kernel, magisk canary, and disable force encryption.
Wait for it to boot up. ?
How to reboot to slot B and flash to slot A? Zip files are flashing like custom roms, GSI images are for slot A, slot B and AB. Sorry but I'm noob in flashing GSI roms. I never succeeded with that... ((
Hi there,
I've been rooting phones since Android 2, but lately it has been quite a challenge.
What I did so far:
Unpack new Xiaomi MI A2 (jasmine) device
Enabled Developer, USB debugging, OEM unlock in Android settings
Code:
fastboot oem unlock
Code:
fastboot flash boot_b TWRP-3.2.3-jasmine-20180804.img
TWRP ran fine. However, started with boot_a again.
OTA updated (about 6 times) to the newest version (Android 10, QKQ1.190910.002 V11.0.12.0.QDIMIXM)
Code:
fastboot flash boot_b twrp-3.4.0-0-jasmine_sprout.img
TWRP started only to the splash screen (showing "teamwin" and "Recovery Project 3.4.0-0"). Why is TWRP not starting properly?
Downloaded the stock fastboot image V11.0.12.0.QDIMIXM from https ://xiaomifirmwareupdater.com/archive/miui/jasmine/ and flash the stock boot.img via
Code:
fastboot flash boot_b jasmine_global_images_V11.0.12.0.QDIMIXM_10.0/images/boot.img
(my goal is to later patch it with Magisk and then install the patched version). However, the stock boot.img just hangs forever on the androidone screen. Why is the stock boot.img not starting properly?
I haven't used the Mi Unlock app and I didn't do an "fastboot flashing unlock_critical" yet. Is this necessary? What do I have to do to make the boot images work?
floydsen said:
Hi there,
I've been rooting phones since Android 2, but lately it has been quite a challenge.
What I did so far:
Unpack new Xiaomi MI A2 (jasmine) device
Enabled Developer, USB debugging, OEM unlock in Android settings
TWRP ran fine. However, started with boot_a again.
OTA updated (about 6 times) to the newest version (Android 10, QKQ1.190910.002 V11.0.12.0.QDIMIXM)
TWRP started only to the splash screen (showing "teamwin" and "Recovery Project 3.4.0-0"). Why is TWRP not starting properly?
Downloaded the stock fastboot image V11.0.12.0.QDIMIXM from https ://xiaomifirmwareupdater.com/archive/miui/jasmine/ and flash the stock boot.img via (my goal is to later patch it with Magisk and then install the patched version). However, the stock boot.img just hangs forever on the androidone screen. Why is the stock boot.img not starting properly?
I haven't used the Mi Unlock app and I didn't do an "fastboot flashing unlock_critical" yet. Is this necessary? What do I have to do to make the boot images work?
Click to expand...
Click to collapse
why do you feel you must use boot images ...the tried and working method for "jasmine" is to boot custom recovery and then flash magisk zip ( root only ) ..or...flash custom recovery installer zip which will flash recovery to both a/b slots.. then flash magisk
to properly boot you need to overcome stuff like secure boot and force encryption
if you aren't planning on custom roms just boot twrp to flash magisk
or
flash installer zip for recovery and wipe everything including formatting data to remove encryption and boot directly to recovery to install custom rom
twrp custom recovery had problems with decryption on stock rom ...secure boot won't allow booting modified images ..
lastly remember on jasmine there is no recovery partition..so everything is in the boot image ..magisk and recovery ..so everytime you flash stock , stock boot overwrites these changes and should flash everything again
tbh that's why i converted to wayne to get old partition layout as the A/B story pissed me off
KevMetal said:
why do you feel you must use boot images ...the tried and working method for "jasmine" is to boot custom recovery and then flash magisk zip ( root only ) ..or...flash custom recovery installer zip which will flash recovery to both a/b slots.. then flash magisk
to properly boot you need to overcome stuff like secure boot and force encryption
if you aren't planning on custom roms just boot twrp to flash magisk
or
flash installer zip for recovery and wipe everything including formatting data to remove encryption and boot directly to recovery to install custom rom
twrp custom recovery had problems with decryption on stock rom ...secure boot won't allow booting modified images ..
lastly remember on jasmine there is no recovery partition..so everything is in the boot image ..magisk and recovery ..so everytime you flash stock , stock boot overwrites these changes and should flash everything again
tbh that's why i converted to wayne to get old partition layout as the A/B story pissed me off
Click to expand...
Click to collapse
Ok. So I'm back to Stock image jasmine_global_images_V11.0.12.0.QDIMIXM_10.0 by executing "flash_all.sh". You are saying I should "simply boot". You mean:
Code:
fastboot boot TWRP-3.4.0-0-jasmine_sprout-for_V11.0.12.0.img
right? That doesn't work, it won't boot. How do I overcome secure boot and force encryption?
floydsen said:
Ok. So I'm back to Stock image jasmine_global_images_V11.0.12.0.QDIMIXM_10.0 by executing "flash_all.sh". You are saying I should "simply boot". You mean:
right? That doesn't work, it won't boot. How do I overcome secure boot and force encryption?
Click to expand...
Click to collapse
yes im saying that but post a pic of the error ...why or how doesn't it boot ..
if it is the official twrp just dump it and look for the unofficial Russian one or one modified by Nebrassy or use Orange fox and or Pitch black ..official is broken last time i checked
also the name of that looks like one hell of a job ..shorten it to
recovery.img or twrp.img
fastboot boot recovery.img
but first run
fastboot getvar all
& also run fastboot flashing unlock_critical
but most importantly get another recovery
& i don't want to insult your intelligence but after flashing stock did you check to make sure bootloader was still unlocked and that dev settings was activated and that adb was toggled to on and that you authorised adb again
basicall after stock boot device and do the above ..plug in usb ..toggle adb ..authorise ..run adb devices ..if you see your device ..adb reboot bootloader ..fastboot devices ..see your device ..fastboot getvar all ..see bootloader is unlocked ..fastboot flashing unlock_critical if not done yet ...make sure to do ALL the above again after data gets wiped.....put twrp in adb folder ( MUST BE UNOFFICIAL RUSSIAN OR MODUFIED BY NEBRASSY ..rename to revovery.img ...fastboot boot recovery.img .. use file manager to put magisk.zip on internal then flash ..then reboot to rooted phone with stock recovery ...
Sent from my wayne using XDA Labs
KevMetal said:
why do you feel you must use boot images ...the tried and working method for "jasmine" is to boot custom recovery and then flash magisk zip ( root only ) ..or...flash custom recovery installer zip which will flash recovery to both a/b slots.. then flash magisk
to properly boot you need to overcome stuff like secure boot and force encryption
if you aren't planning on custom roms just boot twrp to flash magisk
or
flash installer zip for recovery and wipe everything including formatting data to remove encryption and boot directly to recovery to install custom rom
twrp custom recovery had problems with decryption on stock rom ...secure boot won't allow booting modified images ..
lastly remember on jasmine there is no recovery partition..so everything is in the boot image ..magisk and recovery ..so everytime you flash stock , stock boot overwrites these changes and should flash everything again
tbh that's why i converted to wayne to get old partition layout as the A/B story pissed me off
Click to expand...
Click to collapse
KevMetal said:
yes im saying that but post a pic of the error ...why or how doesn't it boot ..
if it is the official twrp just dump it and look for the unofficial Russian one or one modified by Nebrassy or use Orange fox and or Pitch black ..official is broken last time i checked
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Of course it is the official one. OMFG twrp-3.4.0-0-jasmine_sprout.img is broken (freezes on the TWRP splash screen), but version 3.3.1 seems to work. That's a relief, so I will try to flash magisk now. Although, I think I will need to do the decryption thing for jasmine first, but I guess I'll follow https://www.the***********.com/install-twrp-recovery-root-xiaomi-mi-a2-a2-lite/ mostly
floydsen said:
Of course it is the official one. OMFG twrp-3.4.0-0-jasmine_sprout.img is broken (freezes on the TWRP splash screen), but version 3.3.1 seems to work. That's a relief, so I will try to flash magisk now. Although, I think I will need to do the decryption thing for jasmine first, but I guess I'll follow https://www.the***********.com/install-twrp-recovery-root-xiaomi-mi-a2-a2-lite/ mostly
Click to expand...
Click to collapse
jajaja well now you know ...be careful ...some "official" roms are also more buggy than unofficial ones for Jasmine/Wayne..
LOS is an example ..so be forewarned .. if you like android 1 i guess stock rooted is a smart option to keep updates and keep device certified for google stuffs . .
alternativeky go FULL custom rom because stock and custom recovery is just a pain and not worth the hassle on an A/B treble device flashable by fastboot ..just boot the recovery when if ever needed
fyi ..you can flash magisk and it will boot ...if you don't try changing the recovery ..so you can have stock rooted with magisk without rcustom recovery...* recommended by me if you only wamt stock with root
Sent from my wayne using XDA Labs
All good now, thanks for your help! I just flashed Magisk (and also TWRP) and everything works nicely! I will need to get some experience, but I'll keep in mind that I maybe want to get rid of the TWRP recovery. Finally security testing is fun again. Thx!
1> The Shamshung recent firmware upgrade CWD1 might have some patches that makes rooting problemtic. I flashed TukiROM1.2 with Magisk 26.1 (boot.img patch method) the first time and it worked but as soon as I connected to wifi somehow it upgraded to Magisk Delta (thats how I came to know about the existence of Magisk Delta). Both Magisk 24.3 & 26.1 are not surviving reboots even after flashing (Magisk.OTA.persistence-v1.zip). So staying rooted on a stock factory rom is still an issue. I will try TukiRom1.3 though I request OP to compress the ROM file from 2.7GB to lesser if possible.
2> GSI RAW image files don't go past the bootlogo screen. I tried system image files Elixir, LPOS, Crdroid, EvolutionX, Derpfest etc., none of them booted no matter what dmverity or multidisaabler etc. I flashed before or after. The same raw images used to boot on the same device when it was Andoid 11 but now on Andoid 13 Stock Factory ROM CWD1 GSI images dont boot.
3> Since Magisk is either bootlooping the device after reboot/ After flashing Magisk/or Magisk patched images not surviving reboots, so when I flash the Stock boot image it goes straight to download mode with Vbmeta signed using public key etc errors, or if I flash Magisk patched boot image from TWRP it stuck on Shamshung logo.
4> I have tried some of Dev Roynas ROMs [https://sourceforge.net/projects/a51-builds-by-royna/files/] but they all end up with [TWRP error : 1 Assert failed : update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")] also same error through Sideload.
5> I tried (systemrw_1.32_flashable) by Dev Lebigmac but since the altercation between XDA & Lebigmac on March 2023 he got banned from XDA, I cant get hold of (systemrw_1.4_flashable) to try to check if CWD1 Update is RO-Rom and anything other than 1UI5.1 based wont flash etc.
If anyone has any solutions for CWD1 Factory Stock Rom pls assist. TIA