Develop Bugs

Problems with custom roms

Hello,
it looks like that I'm unable to install a custom rom on my GX8 (see details out device at the end of the post).
FRP disabled, bootloader unlocked (this is at least what the fastboot/bootloader screen is saying)
I'm able to flash twrp-3.1.1-0-rio.img to recovery
I can use twrp on recovery and it seems to be fully functional
When I use twrp in 'read-only' mode, I'm able to reboot the system (stock firmware)
But when I use twrp in modifing mode, booting the system (stock firmware) is no longer possible (even if I only wipe cache and/or dalvik). Restarting the device will always end in twrp/recovery.
Backup is possible. Restore backup succeeds, but booting the system (stock firmware) is not possible. Restarting the device will always end in twrp/recovery.
Nevertheless trying to install a custom rom from zip in twrp. This leads to the following error message:
"E3004: This package is for device: RIO-L01, hwRIO-L01, RIO-L02, hwRIO-L02, RIO-L03, hwRIO-L03, RIO-AL00, hwRiO-AL00, RIO-CL00, hwRIO-CL00, RIO-TL00, hwRIO-TL00; this device is rio.
Updater process ended with ERROR: 7"
Well, patch the custom rom in lines of http://www.lineageosdownloads.com/fix-error-7-lineage-os/, i.e. modifing the 'updater-script' in the zip. Now installing the custom rom zip in twrp is possible. Still unable to reboot system.
Installing gapps and/or chainfire supersu does not improve the situation.
Giving up back to stock rom in lines of https://forum.xda-developers.com/gx...tall-stock-rom-g8-t3370013/page2#post73008458 . This has (so far) worked for me to get back a working mobile phone.
Any suggestions, anyone?
Kind regards,
aanno
PS:
device:
Prod
HUAWEI RIO-L01
Serial
MUYDU16122xxxxxx
IMEI
867115027xxxxxx
Prod Id
2983xxxx
Unlock
9725092227xxxxxx
stock firmware used:
EMUI 4.0
Build
RIO-L01C432B340
Android
6.0.1
Kernel
3.10.49-g06216b3
Custom
CUSTC432D001

I've encountered the same exact problem when I flashed using twrp-3.1.1-0-rio.img. Had to force update to stock rom after it got stuck on bootloop.
Solved it when using the older TWRP 3.0.2-0 which you can get here:
https://forum.xda-developers.com/gx8/development/huawei-g8-gx8-t3324538
Hope it might help you too.

change to stock rom failed, phone bricked! HELP!!!

hey guys, I bought this huawei g8 (RIO-AL00) in China about a year ago. recently, i felt huawei stock 5.1.1 rom is suck, so i want to change to stock Android. i unlocked my bootloader, then flush twrp official 3.1.1 and wiped system, cache and data. but when i try to flash official aosp extended, an error occurred: Error 7, your device is not RIO-AL00,RIO-AL01,RIO-AL03 balabala…this device is rio.
i spent more than one day to fix my phone, but it has little effect. somebody said an unofficial twrp 3.0.2 in XDA can fix this error, but there also had an error why i user it to flash rom. the error say my device's…maybe firmware is balabala B22, but flash rom need B35 balabala…
i think that error is because i'm not came from huawei stock 6.0.1 but 5.1.1
anyone can help? thx!

Find the needed firmware (even if it's a different region one ) , use huawei update extractor , flash system. IMG, boot.IMG, cust.IMG via fastboot
Just a quick note regarding cust.IMG , you need to convert it to ext4 format and flash it using the DD command , after doing all of that you are able to flash aosp extended

Can't boot into Recovery with my Z1c

I can't boot in recovery. When I try to do it (in any way you can think of) my phone just continues to boot into the system. My bootloader is unlocked and i have installed the latest available fw with emma. I used fastboot to flash twrp but it still didn't work. Is there a way to fix this, or do I need to flash a whole new os. and if i do need to, can you give me instructions?
There are alot of similar problems but none of the solutions worked for me.. Please help me

Hello,
i have the same prob. Is there any fix?
Firmware 14.6.A.1.236, bootloader unlocked via Sony homepage, newest fw update with emma.
Then flashed twrp (tried sereral versions for z1c tried...3.0.2 for amami, 3.0.2 by derft elot for amami) with adb orders in windows 7 pro. When booting in recovery mode, the display flashes several times in all colors, then display is black, but i have touch response.
I tried also a „multirom“- named twrp version, it displays a vervagen sony logo, then display black, but touch also works.
Have anyone a idea? Have also Kali when linux system is better...
Thx in advance

Same issue here with stock 5.1 (flashed twrp from this thread )

Maybe you need to flash a better TWRP?
Maybe you need to flash a better TWRP?
Here is v3.1.1-0
androidfilehost.com/?fid=961840155545588613

S9 EXYNOS - Lost IMEI Status - Custom ROM

Hi guys
Hope there is anyone that can assist. I rooted my device and installed TWRP recovery etc. I installed various custom ROMs, and was running with Ambassadi latest version (Cross device Section)
I then decided to get my device back to stock, downloaded the latest ODIN version XFA from Sammobile, and flashed it via ODIN. Once the device restarted, i noticed that there was no network. (No IMEI) I then tried to reflash the original PIE ODIN version DBT that i had downloaded. Same thing.
Luckily, i made a TWRP backup of my IMEI when i was on the DBT (PIE Version). I then booted the device, enabled dev mode, but there is no unlock OEM option. Current state is Prenormal. Which means i will need to wait 7 days.
The files i have is:
efs.ext4.win
efs.ext4.win.sha2
efs.info
recovery
How would i go about, to restore my device again? I hope i can flash TWRP, and then restore my IMEI via TWRP? Or is there any other way to try and fix it?

Wooooooop nevermind. Got it sorted. I managed to get TWRP installed again. Format data, reflashed custom. and done )

Hi everyone,i am asking for your help i am noob at this. So i wanted to install a custom rom on my s9+ (Pixle Expirience),after using the rom i installed a random android pie kernel,then the rom woudnt boot.So i installed a normal custom rom that i knew it worked.I flash that but i didint have mobile data and i coudnt see my IMEI and my flight mode was plain blue instead of gray(but my wifi worked like everything elese).Then i installed stock firmware via odin,still nothing.
Then i panic and found some software which with u can insert your IMEI,but i have accidentally wiped my efs.So now when i install firmware it is stuck at samsung logo,and in TWRP it says failed to mount /efs Invalid argument.So i ask u if u can guide me on what to do and how to get efs file.Your help is appreciated.Thank you.

Reset efs then repair imei by chimera ...

Weird behavior with flashing custom rom

I have a strange and weird behavior with flashing custom rom by twrp
I have two RN8 Global phones
- batch 07-2020 64GB A9 Miui 11.09
- batch 11-2020 128GB A9 Miui 11.011 board ID 3.29
The first one I have flashed without problems with RR official in august and updated till the last from DqrKn3Zz.
The second flashed without any error in twrp, but refuses to boot in twrp or system,
Screen went black, pushing powerbutton does lcd backlight only short flashing. usb isn't recognized.
Only solution is testpoint, edl flash with qfil.
What are the differences with flashing:
- Miui version
- Board ID, I think
- Storage 128Gb vs 64GB
- Twrp 3.5 vs 3.4
- Twrp flashing rom from external SD card vs internal storage
- FW and RR version are for both devices the same, the FW 12.01 Global and last RR 8.6.4 from DqrKn3Zz
- The first one I started with RR8.5.8 and FW 20.8.27 CN, but don't dare to flash CN FW anymore
I followed the instructions for unlocking, twrp and FW and RR flashing, but get always a flashing screen and fastboot isn't possible anymore.
In the past I haved flashed about 12 different Xiaomi phones, but this is the first time I am out of ideas how to solve this.
My suspicion is that something is or isn't changed in the booting process with flashing FW.
Tried different scenarios like, partly flashing and starting to twrp again.
I can flash and start twrp, flash magisk, decrypt etc. but if I flash FW and Rom that ended it.
I have formatted data, wipe system, caches and vendor etc. but no succes
Testpoint/EDL I have used 5 times to recover Miui 11 again, without problems or sahara error
With starting Miui, my account is still there, I only have to activate it and bootloader is still unlocked.
The last thing I can try is flash only RR and no FW, but I don't know if it is possible to flash A10 custom on A9 FW
Or official update to Miui 12 - A10 and try to flash custom rom only.
But I am afraid that if there is again a brick, the EDL solution won't work.
Has anybody some other ideas what I can do?

Answer my own question:
The headache is over
At last I found the reason of this brick.
It is impossible to flash Miui 12.0.1 with recovery on Miui 11.0.11
Only with Miui 11.0.11 you must flash Miui 12.0.1 with fastboot
The first version which you can flash with recovery is Miui 12.0.2
I didn't know this because I never intended to use Miui.
After a search I found a source for this information
Installed RR8.6.7 with FW 12.03 without problems

Elinx said:
I have a strange and weird behavior with flashing custom rom by twrp
I have two RN8 Global phones
- batch 07-2020 64GB A9 Miui 11.09
- batch 11-2020 128GB A9 Miui 11.011 board ID 3.29
The first one I have flashed without problems with RR official in august and updated till the last from DqrKn3Zz.
The second flashed without any error in twrp, but refuses to boot in twrp or system,
Screen went black, pushing powerbutton does lcd backlight only short flashing. usb isn't recognized.
Only solution is testpoint, edl flash with qfil.
What are the differences with flashing:
- Miui version
- Board ID, I think
- Storage 128Gb vs 64GB
- Twrp 3.5 vs 3.4
- Twrp flashing rom from external SD card vs internal storage
- FW and RR version are for both devices the same, the FW 12.01 Global and last RR 8.6.4 from DqrKn3Zz
- The first one I started with RR8.5.8 and FW 20.8.27 CN, but don't dare to flash CN FW anymore
I followed the instructions for unlocking, twrp and FW and RR flashing, but get always a flashing screen and fastboot isn't possible anymore.
In the past I haved flashed about 12 different Xiaomi phones, but this is the first time I am out of ideas how to solve this.
My suspicion is that something is or isn't changed in the booting process with flashing FW.
Tried different scenarios like, partly flashing and starting to twrp again.
I can flash and start twrp, flash magisk, decrypt etc. but if I flash FW and Rom that ended it.
I have formatted data, wipe system, caches and vendor etc. but no succes
Testpoint/EDL I have used 5 times to recover Miui 11 again, without problems or sahara error
With starting Miui, my account is still there, I only have to activate it and bootloader is still unlocked.
The last thing I can try is flash only RR and no FW, but I don't know if it is possible to flash A10 custom on A9 FW
Or official update to Miui 12 - A10 and try to flash custom rom only.
But I am afraid that if there is again a brick, the EDL solution won't work.
Has anybody some other ideas what I can do?
Click to expand...
Click to collapse
i flashed over 250 rom on my 128gb variant without a single problem
i always flash rom + dfe + format sometimes if required
about 100 rom with twrp
and the rest with orangefox
i was on OFox when i flashed miui12 but the phone booted normally
maybe because i have "Aggressive stock recovery deactivation" option enabled ...
i don't like to flash FW a lot
they seem to be N1 problem source for ginkgo ...

I too have a lot of experience with flashing (not 250+), but becasue I stay far away of Miui I didn't know of this incombabilty with Miui 11.0.11 and recovery-flash of 12.0.1 Firmware. Older versions of Miui 11 hadn't this problem.
For me this was the first time I had such a problem.
If I had flashed the latest RR ZhanTech version immediately, I wouldn't even have noticed this problem.
But the first RN8 is in use by my wife and isn't completely flawness.
With the second one I had planned to experiment first with some solutions for that,, because I could always back to base.
Luckely I choose always a Xiaomi which has a lot of development for it, so mostly is this an older type and never the newest.
In this case it was very easy to flash back with EDL and patched firehose file.

Elinx said:
I didn't know of this incombabilty with Miui 11.0.11 and recovery-flash of 12.0.1 Firmware.
Click to expand...
Click to collapse
maybe because it "patch" the custom recovery ???
anyway, i will never back to miui unless i want to sell it
and i think the best way is flash a custom rom based on miui

loopypalm said:
maybe because it "patch" the custom recovery ???
..
Click to expand...
Click to collapse
No, with Miui OTA you flash with Xiaomi recovery, but before you get a warning 12.01 is incompateble and recovery doesn't start.
Directly with twrp, you don't get this warning and also you don't get any flashing error.
That is why I didn't expect that it was of incompatiblity of the FW.
One of the last things I did was flashing rom, magisk etc and started between to system.
As last I flashed 12.01 FW and got a brick.
After this I was searching for this problem and there where complains about a brick with flashing the new Miui 12 with twrp.
I was afraid that I couldn't flash new FW, but then I found that it is only with FW 12.01....... flashing 12.02 and 12.03 give no problems.

Elinx said:
flashing 12.02 and 12.03 give no problems.
Click to expand...
Click to collapse
with twrp you mean ?

loopypalm said:
with twrp you mean ?
Click to expand...
Click to collapse
Yes, only 12.01 FW or Miui12.01 with twrp gives a brick.
12.02 and higher is possible with twrp.
it is only possible to flash Miui 12.01 entirety with Miflash/fastboot

Elinx said:
Yes, only 12.01 FW or Miui12.01 with twrp gives a brick.
12.02 and higher is possible with twrp.
it is only possible to flash Miui 12.01 entirety with Miflash/fastboot
Click to expand...
Click to collapse
ow, i see
thx for the informations