Develop Bugs

[Q] Why can't I install any custom rom

HELLO
I'm trying to install many MM custom roms (on my LG G3 D855) like blisspop, xosp, pacman, resurection remix... but i cant. twrp says at the end that "unmount of /system failed no such volume" "script succeeded: result was (0.20000)"
When i install pacman there is no error but when i boot it keeps rebooting
Fulmics rom works perfectly (i think it's thanks to aroma installer) but i still have wifi and bluetooth issues
Help me PLEEEEEEASE
(sorry for my english i'm french )

what TWRP version are you using? make sure you have version 3.

tunichi01 said:
what TWRP version are you using? make sure you have version 3.
Click to expand...
Click to collapse
Thank you for replying
Yep I have twrp v3.0.2

Nobody can help me ?

after wipe, reboot to recovery then flash it whithout mount/unmount anything..
if still failed.. update your modem to 21c

Bayoe04 said:
after wipe, reboot to recovery then flash it whithout mount/unmount anything..
if still failed.. update your modem to 21c
Click to expand...
Click to collapse
I installed Resurrection Remix by downgrade to 5.0, root and install twrp then install RR! Everything worked but it restarted and just after the Lg logo it keep showing a black screen and i can't restart, i pulled the battery out and restarted, it did the same!
I managed to install Turbo Rom, but 5 seconds after showing the logo it restarts. IDK what to do

Now when i install a CM13 based rom it reboot until the rom's logo then it restart.. What is the problem?
thank you

LineageOS-based roms won't boot - Firmware 4.1.0

I'm having issues with LineageOS based roms. Basically, ever since 4.1.0 was released, I haven't been able to boot anything other than OxygenOS.
The first time I flashed the 4.1.0 firmware, my OnePlus 3 bricked. I then used the unbrick tool to fix it. I then tried again, by flashing the 4.1.0 firmware, then flashing the latest LineageOS "lineage-14.1-20170316-nightly-oneplus3-signed.zip". Upon reboot, the phone stays stuck at the lineageos boot animation. I can't get any logcats (adb logcat doesn't seem to work).
Things I've tried so far:
- Using TWRP 3.0.4-1
- Using TWRP 3.1.0-0
- Dirty flash
- Clean flash
- Data as both f2fs and ext4, neither works
- Tried using TWRP's "Fix Contents"
- Tried using TWRP's filesystem repair, no problems with the filesystem
I'm at a loss, no idea what to do. I really want to get back to LineageOS, but ever since that original brick, the phone hasn't been able to boot anything other than the stock ROM.

do you try download again that rom?
i had some problems with AICP, flashing last firmware+modem was solved
you can try using other base, like 4.02, or freedomOS OB12
just ideas, I don't know what's the problem :/

bro i flashed the 316 build on oos 4.1 firmware and modem no issue here all works fine still using it with blue spark kernal you must have done something wrong

vasu1312 said:
bro i flashed the 316 build on oos 4.1 firmware and modem no issue here all works fine still using it with blue spark kernal you must have done something wrong
Click to expand...
Click to collapse
I don't think I screwed up anything. I had flashed multiple roms before. (LineageOS, ResurrectionRemix, AICP, FreedomOS...)
All of them worked, up until recently. When the 4.1.0 update came out, LineageOS Roms stopped booting. OxygenOS ROMS still work fine though. Flashing the OB12 firmware doesn't help.
This is the first time this has happened, I have no idea why its happening.

Do you flash SuperSU, without SuperSU mine boots fine. Without i m stuck in boot

Tried flashing SuperSU, but nothing has changed. Android still won't boot up if it is a LineageOS based ROM

go to stock recovery (oxygen os stock one)
then flash 4.1.0 with that recovery
then boot
now replace the recovery with twrp 3.1.0
once done dont boot the rom n go to recovery and flash su
now boot rom
now again go to twrp n wipe system, data, cache, dalvik
and then flash lineage lastest build.. it will work
if not lemme know i will help you further

indroider said:
go to stock recovery (oxygen os stock one)
then flash 4.1.0 with that recovery
then boot
now replace the recovery with twrp 3.1.0
once done dont boot the rom n go to recovery and flash su
now boot rom
now again go to twrp n wipe system, data, cache, dalvik
and then flash lineage lastest build.. it will work
if not lemme know i will help you further
Click to expand...
Click to collapse
Just did it. It didn't work, the phone gets stuck in the LineageOS Boot screen

Now, not even Android 6.0 ROMS will boot. I think some partitions are corrupted, but I'm unable to wipe them in fastboot mode.
Edit: So, finally, after 3 days, I was able to get in contact with OnePlus. OnePlus fixed the problem with the Qualcomm Tools, not entirely sure what they did, but it fixed the problem. I'm finally able to boot LineageOS!!!!

AquaBytez said:
Just did it. It didn't work, the phone gets stuck in the LineageOS Boot screen
Click to expand...
Click to collapse
how much time do you wait because first boot does take 5 or more minutes

indroider said:
how much time do you wait because first boot does take 5 or more minutes
Click to expand...
Click to collapse
OnePlus said that the persist partition had been corrupted. So they re-flashed it and the phone started booting custom ROMS again. I guess the ROMS weren't booting because they got stuck waiting on the sensors. (To be completely honest, I never noticed that the sensors were broken. Since the only one I frequently use is the Gyroscope and that one was working fine)

AquaBytez said:
OnePlus said that the persist partition had been corrupted. So they re-flashed it and the phone started booting custom ROMS again. I guess the ROMS weren't booting because they got stuck waiting on the sensors. (To be completely honest, I never noticed that the sensors were broken. Since the only one I frequently use is the Gyroscope and that one was working fine)
Click to expand...
Click to collapse
perfect... that is what i was trying ro instruct you reflasing the stock but somehow ,,, it was not able to be done throught stock oxygen recovery... from ur end
nevertheless happy ur device is working fine now

Bricked my Mi6

So I just got Mi6 in my hands today, and tried to install Xiaomi EU v8.5.2.0 ROM.
Now, it won't boot. Stuck in Mi logo.
I have flashed TWRP
I have wiped Dalvik Cache, Cache, System, Data, Internal Storage (and probably that messed it up)
Then, installed the ROM via sideload. Rebooted phone, and it's stuck in boot logo
Some friends said something about "boot.img" and SuperSU. What should I do now?
Thank you!

I think your best bet now to use miflash tool and flash fastboot rom.
Though if you can flash twrp, you should be able to flash custom rom using that. Follow the steps 1 by 1. Sometimes certain rom needs u to flash firmware first.

cagriari said:
So I just got Mi6 in my hands today, and tried to install Xiaomi EU v8.5.2.0 ROM.
Now, it won't boot. Stuck in Mi logo.
I have flashed TWRP
I have wiped Dalvik Cache, Cache, System, Data, Internal Storage (and probably that messed it up)
Then, installed the ROM via sideload. Rebooted phone, and it's stuck in boot logo
Some friends said something about "boot.img" and SuperSU. What should I do now?
Thank you!
Click to expand...
Click to collapse
Hi if access to twrp put this ROM on : http://bigota.d.miui.com/7.8.24/miui_MI6Global_7.8.24_52ee82c864_7.1.zip
Then flash via twrp then reboot

jejemc said:
Hi if access to twrp put this ROM on :
Then flash via twrp then reboot
Click to expand...
Click to collapse
Well, I have fixed it by repairing system partition. But now, no EU ROM will boot. MIUI Global Stable v8.2 boots, but Wi-Fi and fingerprint is broken.

cagriari said:
Well, I have fixed it by repairing system partition. But now, no EU ROM will boot. MIUI Global Stable v8.2 boots, but Wi-Fi and fingerprint is broken.
Click to expand...
Click to collapse
So he restarted? Test can be ROM dev to see
But bizarre that on stable ROM this does not work

Yeah, I would suggest flash stable fastboot rom via miflash and start again. If fingerprint/wifi still broken after flash fastboot rom via miflash, there is high chance the hardware is broken.
If it does back to stock and everything works, follow flash procedure for custom rom step by step. There is no real reason it will not work. Good luck

yumm91 said:
Yeah, I would suggest flash stable fastboot rom via miflash and start again. If fingerprint/wifi still broken after flash fastboot rom via miflash, there is high chance the hardware is broken.
If it does back to stock and everything works, follow flash procedure for custom rom step by step. There is no real reason it will not work. Good luck
Click to expand...
Click to collapse
MiFlash gives me "cast id invalid" error, I've been using TWRP and fastboot to flash. I flashed it few times, but it didn't work. So I wiped all the data, flashed again and it works now.
Any ideas why won't EU ROMs boot?
Thanks!

I am using xiaomi.eu ROM myself flashed via twrp 3.1.1.0 Seems working fine. I just boot the twrp via fastboot boot, using twrp mtp to transfer EU rom inside, and flashed.
Done. Everything works. I am currently under miui 8.2 atm. Seems good so far.

[Help needed] Lost TWRP after flashing Xtended ROM.

I wiped the phone clean and tried to flash the new version of AEX But, it showed Error 7.
Tried looking for fix for Error 7 on internet, it didn't work for AEX5.6, 5.5, 5.4.
5.3 installs normally.
But felt like needed something new.
Went on the forums to find Xtended ROM. Flashed it.
After flashing it tried flashing Nano GAPPS.. Didn't work.
Tried to system reboot and thought I can later work it out.
ROM is all fine... But, later when I got to recovery mode.
(Problem begins)
I realised I lost TWRP.
And the recovery that's there wouldn't allow me to flash anything.
It looks more like CWM recovery but with less options.
It doesn't even have a advanced wipe!
Now I'm stuck with a non rooted phone, without Google bare minimum functionalities.
Am I alone? Help me out!

UKWZ7 said:
I wiped the phone clean and tried to flash the new version of AEX But, it showed Error 7.
Tried looking for fix for Error 7 on internet, it didn't work for AEX5.6, 5.5, 5.4.
5.3 installs normally.
But felt like needed something new.
Went on the forums to find Xtended ROM. Flashed it.
After flashing it tried flashing Nano GAPPS.. Didn't work.
Tried to system reboot and thought I can later work it out.
ROM is all fine... But, later when I got to recovery mode.
(Problem begins)
I realised I lost TWRP.
And the recovery that's there wouldn't allow me to flash anything.
It looks more like CWM recovery but with less options.
It doesn't even have a advanced wipe!
Now I'm stuck with a non rooted phone, without Google bare minimum functionalities.
Am I alone? Help me out!
Click to expand...
Click to collapse
For aex issue did you flash factory2vendor zip before flashing rom?
You will have to install twrp image using PC. Like the first time you did when you were unlocking bootloader

Flash zui using qfil or miflash.
If bootloader is unlocked still. You can directly flash twrp.
If not first unlock your bootloader and then flash twrp.
For treble rom like aex5.5 you need to flash factory2vendor.zip and then flash twrp with treble support.
For info on flashing and link visit aex5.5 rom page.

Error 7 in TWRP when flashing custom roms

I used to be on resurrection remix 7.1.2, but I flashed stock ROM so I could do a clean flash with another ROM. I used Xiaomi unlock tool to unlock bootloader again, then flashed TWRP thru ADB in fastboot. After that I went into recovery, wipe data,cache etc and tried to flash dotos 3.0, but it gave me error 7. I repeated same process with zirconium android 9.0, same thing I'm using latest TWRP, y do I get error 7?? I definitely have the right model etc

Hey mate, have you tried using a vendor based custom recovery? . Is your Twrp vendor based? ( you'll be able to see cust/vendor partition in the advanced wipe menu).
I was messing around today with Dot0s 3.0 and regular Twrp too and found out that i couldn't install any pie roms on regular Twrp. I was previously using batik recovery. So you might be able to flash on it. Let me know if you try it.
Edit : I got the same error 7 on pretty much all oreo and pie roms.

jeevan bk said:
Hey mate, have you tried using a vendor based custom recovery? . Is your Twrp vendor based? ( you'll be able to see cust/vendor partition in the advanced wipe menu).
I was messing around today with Dot0s 3.0 and regular Twrp too and found out that i couldn't install any pie roms on regular Twrp. I was previously using batik recovery. So you might be able to flash on it. Let me know if you try it.
Edit : I got the same error 7 on pretty much all oreo and pie roms.
Click to expand...
Click to collapse
Ah, thanks man. I've been only using regular TWRP, I'll use batik in a bit

Flash old firmware and then upgrade
Arathergreendroid said:
Ah, thanks man. I've been only using regular TWRP, I'll use batik in a bit
Click to expand...
Click to collapse
Flashing Nougat firmware first and then custom recovery worked.
See https://forum.xda-developers.com/xiaomi-redmi-5a/how-to/rollback-downgrade-to-miui-nougat-t3938904

This is work for me.. just extract your cusrom and then go to Meta-Inf > google , edit the updater script. and delete line "get prop ......." all of that line.
so the first line must " ui_print ("Target: ........"); "
save
and select all files from your cusrom, create zip, copy to sd card, install via Recovery