Develop Bugs

CM13 Bootloop

I bought a new 5X (running 6.0, not 6.0.1) and unlocked bootloader, flashed TWRP as standard - it all worked.
Then I flashed CM13 and got stuck in a bootloop (waited upwards of 10 minutes with the CM logo). I tried the same with the latest stable release and got the same issue. What can I do? Thanks!

Did you do a wipe in twrp before flashing cm? If not do that. Just use twrp's default wipe.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Did you do a wipe in twrp before flashing cm? If not do that. Just use twrp's default wipe.
Yep, both factory reset (default wipe) and full wipe of everything but internal storage.
Click to expand...
Click to collapse

Sounds like you're doing everything correctly. I'd try giving it more time. Sometimes it takes a lot longer than it should to boot up.

jd1639 said:
Sounds like you're doing everything correctly. I'd try giving it more time. Sometimes it takes a lot longer than it should to boot up.
Click to expand...
Click to collapse
Currently tried flashing BlissPop to see if problem persists. How long would you say is "too long"?

Occasionally I've seen 20 minutes or more. That's not usually the case but I have seen that.

Currently on 21 minutes with BlissPop booting. Thank you for your help so far, if this doesn't boot in 10 minutes I'll try and flash the stock images. Is there any way to find what phone model I have just using fastboot?

When you boot into the bootloader that screen will tell you the device you have

I know but none of the options from here https://developers.google.com/android/nexus/images?hl=en#bullhead fit. Or are the "MHC19Q" and such just versions of 6.0.1? Sorry for the (probably) stupid question.

tm.tudor said:
I bought a new 5X (running 6.0, not 6.0.1) and unlocked bootloader, flashed TWRP as standard - it all worked.
Then I flashed CM13 and got stuck in a bootloop (waited upwards of 10 minutes with the CM logo). I tried the same with the latest stable release and got the same issue. What can I do? Thanks!
Click to expand...
Click to collapse
The problem is "running 6.0, not 6.0.1". The CM13 based 6.0.1 android (the newest april security version), so upgrade your stock android to newest 6.0.1.

Shyciii said:
The problem is "running 6.0, not 6.0.1". The CM13 based 6.0.1 android (the newest april security version), so upgrade your stock android to newest 6.0.1.
Click to expand...
Click to collapse
Yep, that was it. Thanks a lot!

[TUTORIAL][ROM][CM14.1] OFFICIAL CyanogenMod 14.1 for Android One 2nd Gen on WF Swift

Due to a number of reports of people bricking their devices, I have removed this tutorial.
For instructions to get your device unbricked, please read here.
I'm terribly sorry for the inconvenience.

Hello,
thanks for sharing, but do you also know a way back to wileyfox stock rom? I don't think a twrp backup holds all nand data. When flashing GM4G rom, you also flash ie. modem partition, and I don't think that this is covered by a twrp backup.
bye...DonQ

Seed has a TWRP patched for cm updater. I'm a seed user but I prefer crackling roms

DonQuichotte said:
Hello,
thanks for sharing, but do you also know a way back to wileyfox stock rom? I don't think a twrp backup holds all nand data. When flashing GM4G rom, you also flash ie. modem partition, and I don't think that this is covered by a twrp backup.
bye...DonQ
Click to expand...
Click to collapse
Flash the factory image.

[email protected] said:
Seed has a TWRP patched for cm updater. I'm a seed user but I prefer crackling roms
Click to expand...
Click to collapse
I can't find a link for the Seed TWRP patched for CM Updater. Can you share it?

seb5049 said:
I can't find a link for the Seed TWRP patched for CM Updater. Can you share it?
Click to expand...
Click to collapse
Yeah I would like to know too

VivaLaVent said:
Flash the factory image.
Click to expand...
Click to collapse
I'm not sure this is enough, cause with the GM4G rom some partitions (.img) get flashed, that are not in the swift factory rom...oem.img, devinfo.bin. I think about switching to seed, cause no more nigthlies and seed has official CM14.1 already. But there has to be a bullet-proof way to return to stock...just in case.
bye DonQ

twrp patched by Arvin Quilao
VivaLaVent said:
Yeah I would like to know too
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=457095661767122264 i use this and updated via cm updater twice with no problem....

[email protected] said:
https://www.androidfilehost.com/?fid=457095661767122264 i use this and updated via cm updater twice with no problem....
Click to expand...
Click to collapse
Okay so I'm guessing updating with CM updater does work, but the recovery you linked is not the latest version of TWRP.

Hello, I've tried to flash this rom General Mobile 4G (seed) and it finishes OK, but device does not restart ( brick but USB COM port detected), I've reinserted the battery and device does not turn on, googled a bit, and used qualcomm flash tool to unbrick my wileyfox.
What am I doing wrong here ?
I've also tried with GM_4G_7.0_NRD90R_FASTBOOT_STOCK_ROM_BY_TURKDEVS same problem device is bricked
Also I've tried from stock Cynogen OS (12.1-YOG4PAS33J) but same result device bricked
PS. downloaded files are ok, not corrupted....

Twrp version status...
VivaLaVent said:
Okay so I'm guessing updating with CM updater does work, but the recovery you linked is not the latest version of TWRP.
Click to expand...
Click to collapse
Yeahhh it isnt the latest i know. The latest is 3.0.2-1 but isnt patched for cm ota updates like that shared by me later. The dev stated the official version patched from twrp website will come later. Using it dnt create any prblm.

piromanneo said:
Hello, I've tried to flash this rom General Mobile 4G (seed) and it finishes OK, but device does not restart ( brick but USB COM port detected), I've reinserted the battery and device does not turn on, googled a bit, and used qualcomm flash tool to unbrick my wileyfox.
What am I doing wrong here ?
I've also tried with GM_4G_7.0_NRD90R_FASTBOOT_STOCK_ROM_BY_TURKDEVS same problem device is bricked
Also I've tried from stock Cynogen OS (12.1-YOG4PAS33J) but same result device bricked
PS. downloaded files are ok, not corrupted....
Click to expand...
Click to collapse
I'm having the same problem.

seb5049 said:
I'm having the same problem.
Click to expand...
Click to collapse
I'm starting to think I made an error, can anyone confirm they successfully used this method?

VivaLaVent said:
I'm starting to think I made an error, can anyone confirm they successfully used this method?
Click to expand...
Click to collapse
I was unsuccessful with your method. I even tried two times then I gave up and restored my backup with cm-13

How is it running on CM 14? Is there noticeable lag and such?

If you want CM14, try crDroid, it works great. I'm using it for two weeks now, no FC errors, good battery performance, no serious lags.
When I read the bricks of some users trying to flash a ROM that is meant for a clone with ALMOST the same hardware - I won't try this.

I am considering doing this update. But I have an issue. Since Android 6 has integrated sdcards, I had to reformat the sdcard on every update which is a pain in the ass. I using mixed mode. Is there any way to do an update which allows to reintegrate the sdcard without reformatting the sdcard?

piromanneo said:
Hello, I've tried to flash this rom General Mobile 4G (seed) and it finishes OK, but device does not restart ( brick but USB COM port detected), I've reinserted the battery and device does not turn on, googled a bit, and used qualcomm flash tool to unbrick my wileyfox.
What am I doing wrong here ?
I've also tried with GM_4G_7.0_NRD90R_FASTBOOT_STOCK_ROM_BY_TURKDEVS same problem device is bricked
Also I've tried from stock Cynogen OS (12.1-YOG4PAS33J) but same result device bricked
PS. downloaded files are ok, not corrupted....
Click to expand...
Click to collapse
I seem to have the same problem as you, device doesn't respond, no boot or whatever.
Could you link me to the solution you used to unbrick the device?

Due to a number of reports of people bricking their devices, I have removed this tutorial.
For instructions to get your device unbricked, please read here.
I'm terribly sorry for the inconvenience.

custom roms do not boot up

hi there,
i used crDroidAndroid-8.1-20180606-riva-v4.3 but there were color problems i didnt know 2 fix so i decided 2 flash a new rom resp. a newer version but no custom rom boots up.
when it tries 2 boot is freezes at the boot screen, then screen switches off and nothing happens. i can go 2 fastboot and recovery.
sometimes it boots up but after a few seconds it freezes 2.
i tried different roms and recoveries but nothing works.
i foolishly wiped internal storage once but then i flashed the stock rom again which boots up. then i unlocked the bootloader and flashed a custom recovery and a rom again but the same error is there (no booting up)
anyone got a solution for this problem? no unbricking suggestions plz
edit: im in the wrong thread i think. i wanted 2 post it in "Guides, News, & Discussion". cant delete it. sry for that

logs
so i managed 2 create logs while booting up.
1) https://pastebin.com/cgrX2DA1
2) https://pastebin.com/r7DmcN46
3) https://pastebin.com/0pwXyuys
4) https://pastebin.com/S41FG2SQ
1) is 1st part of the log while booting with no success to boot into the os.
2) is 2nd part of the log while booting with no success to boot into the os.
3) is 1st part of the log while booting with successful boot into the os.
4) is 2nd part of the log while booting with successful boot into the os.
i also tried 2 log "cat /proc/last_kmsg > /sdcard/last_kernel_message_log.txt"
and "dmesg > /sdcard/kernel_boot_log.txt" via terminal in linux but it only sais file or directory not found.
i hope sum1 can give me sum help now.

so i did this https://en.miui.com/thread-3921604-1-1.html but it doesnt help. as i expected.
any1? i can post more information if necessary. just say which and perhaps how ;D

cmon guys. i can impossibly b the only 1 who faces this problem.
i dont think its a hardware thing cause stock rom and android 7.1.2 (viper os) work. maybe a vendor problem? could flash another vendor img solve this problem? can sum1 send me his?
i got sum more logs after flashing rr 7.0:
logcat 1st part: https://pastebin.com/EBZAgbhF
logcat 2nd part: https://pastebin.com/qaMFrvxi
dmesg: https://pastebin.com/Gg8bYkJy
cheers

Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.

NaAnBcEhEuL9A8K7 said:
Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.
Click to expand...
Click to collapse
thx for ur answer but i tried this already. does not work on android 8 and 9 roms

daemonicvs said:
thx for ur answer but i tried this already. does not work on android 8 and 9 roms
Click to expand...
Click to collapse
Well it worked for me.
Which custom rom you want to use?

well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..

daemonicvs said:
well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..
Click to expand...
Click to collapse
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.

NaAnBcEhEuL9A8K7 said:
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.
Click to expand...
Click to collapse
i did it several times before but 2 b safe i did it again like that:
i flashed riva_global_images_V10.1.1.0.NCKMIFI_20181029.0000.00_7.1_global_f444c158ed.tgz using XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan-master. im on linux mint 18.3. i have 4 options:
flash_all_lock.sh
flash_all_lock_crc.sh
flash_all_except_data_storage.sh
flash_all.sh
i chose flash_all.sh
i booted into the stock rom and set it up, enabled dev options and adb.
then i switched it off, went into bootloader, flashed twrp-3.2.3-0-riva.img via fastboot.
after that i entered twrp, flashed OrangeFox-R8.3-riva.zip and rebooted into recovery
i wiped everything except external sd and usb otg (i dont have these)
after a reboot intorecovery i formatted data then rebooted in recovery
i flahed crDroidAndroid-9.0-20181002-riva-v5.0.zip
then reboot into system
no success as i expected! wtf is wrong wtf. this cant b true!
but thank u very much for ur efforts! perhaps i would try 2 restore a vendor img from sum1 which rom does work. i know its a great demand but could u send me urs? ;D i dont know if there r sum personal info..
best regards

Don't give up there might be a solution.
Pray to God for some help.
:good:
---------- Post added at 01:23 PM ---------- Previous post was at 12:59 PM ----------
Currently I am using Xiaomi.eu beta rom. You can check their website for all the features. Its smooth, stable and can update without needing to got the recovery:victory:
This should work for you because unlike other roms this is based on miui for riva. That means you will get updates till Xiaomi ditches support for riva.
I recommend you use this rom over the global rom until you fix the problem with your phone.
Some things missing:
Choice of region is limited( India is not available)
There is no custom kernel available for miui oreo as of now.
Magisk safetynet not passed
If you're going flash this rom you need to be on latest global beta fastboot rom and need a recovery that supports oreo base.
I use batik recovery base oreo.

yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway

daemonicvs said:
yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway
Click to expand...
Click to collapse
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.

NaAnBcEhEuL9A8K7 said:
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.
Click to expand...
Click to collapse
theres no difference between my device and yours... everybody must have this problem ;/

daemonicvs said:
theres no difference between my device and yours... everybody must have this problem ;/
Click to expand...
Click to collapse
Did you try edl method?

NaAnBcEhEuL9A8K7 said:
Did you try edl method?
Click to expand...
Click to collapse
yes. i could flash the stock rom this way but the problem is not solved this way

daemonicvs said:
yes. i could flash the stock rom this way but the problem is not solved this way
Click to expand...
Click to collapse
At least you have to try.

I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.

Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
Did you flash lazy flasher?

Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
dont u have 2 wait 2 weeks or so till bootloader is unlocked?
what exactly do u mean with won't boot up? bootloop? or stuck at boot logo?
after flashing a custom recovery, did u boot directly into the system or did u try 2 boot into recovery? sometimes the stock recovery overwrites the custom 1 when stock rom boots up
my problem is solved. i remembered that i made a full nandroid backup with twrp before i flashed a new rom and the problem appeared. so i restored everything i backed up with twrp (incl cust) and voila, rom booted up. and i can wipe system and data and flash every rom i wanna and it still boots up \o/
i really could have tried it earlier but i didnt think of this untill yesterday ;D
well, thx for ur efforts anyway buddy @NaAnBcEhEuL9A8K7
cheers

Bootloop flashing miui 12 closed beta

hi, i am having aproblem right now trying to flash miui 12. first time i just formatted the phone in twrp. used adb push to push the zip on the phone. and flashed it. it was successful but after booting into the system it had a password for some reason and there was no setup screen. so i tried to reflash by formatting again and repeating the process. now i boot into system and it just goes into bootloop at the MI boot screen.
Its super weird that it worked the first time. then it doesnt work anymore no matter what (adb sideload, multiple recoveries) and it seems the rom isnt installing correctly because afterwards i cannot flash magisk (cannot mount system partition)

Use fox twrp to flash.

haovh_85 said:
Use fox twrp to flash.
Click to expand...
Click to collapse
I used TWRP. Also tried orangefox

haovh_85 said:
Use fox twrp to flash.
Click to expand...
Click to collapse
I also tried flashing the firmware first

-iwl- said:
hi, i am having aproblem right now trying to flash miui 12. first time i just formatted the phone in twrp. used adb push to push the zip on the phone. and flashed it. it was successful but after booting into the system it had a password for some reason and there was no setup screen. so i tried to reflash by formatting again and repeating the process. now i boot into system and it just goes into bootloop at the MI boot screen.
Its super weird that it worked the first time. then it doesnt work anymore no matter what (adb sideload, multiple recoveries) and it seems the rom isnt installing correctly because afterwards i cannot flash magisk (cannot mount system partition)
Click to expand...
Click to collapse
Wait for some days,when some one success.
I have also flashed the rom first day.
I struggle for 1 hour with my laptop than i booted into LOS 17.1 after destroying my whole 100 gb internal data of my phone.

paradise220 said:
Wait for some days,when some one success.
I have also flashed the rom first day.
I struggle for 1 hour with my laptop than i booted into LOS 17.1 after destroying my whole 100 gb internal data of my phone.
Click to expand...
Click to collapse
did you encounter the same issue? this person has it correctly installed:
https://www.youtube.com/watch?v=x5HJgH8QrMs
also. sometimes it says no os instlaled after i flashed

paradise220 said:
Wait for some days,when some one success.
I have also flashed the rom first day.
I struggle for 1 hour with my laptop than i booted into LOS 17.1 after destroying my whole 100 gb internal data of my phone.
Click to expand...
Click to collapse
i have no idea what to do now

-iwl- said:
did you encounter the same issue? this person has it correctly installed:
https://www.youtube.com/watch?v=x5HJgH8QrMs
also. sometimes it says no os instlaled after i flashed
Click to expand...
Click to collapse
when i flashed miui 12 beta it showed on operating software installed before reboot.

paradise220 said:
when i flashed miui 12 beta it showed on operating software installed before reboot.
Click to expand...
Click to collapse
it seems they released a broken rom. i tested again with lineage os and it worked perfectly. so its xiaomi at fault here

Ive installed It yesterday (dont know where but i Saw someone saying that It need Magisk, i flashed It and It worked).
But i turned back to oficial miui 11, my sim card was not working with this beta

Use chinese twrp

JrAdams said:
Ive installed It yesterday (dont know where but i Saw someone saying that It need Magisk, i flashed It and It worked).
But i turned back to oficial miui 11, my sim card was not working with this beta
Click to expand...
Click to collapse
Gapps or any google related services doesnt seem to be working with this beta. lots of bugs encountered too, i might just go back to havoc os

Yunus Ceyhan said:
Use chinese twrp
Click to expand...
Click to collapse
Got it working already. just had to flash magisk along with the rom

Question Installing GSI rom with U3 bootloader

After installing U3 bootloader I am unable to install any GSI roms with Android 11 or 12, always bootloops . Only Android 13 roms work now. Anyway to install Android 11/12 GSI with U3 bootloader? Thanks

Isn't possible

Well, it does boot but gets stuck in the rom boot phase. Like I see lineageos on the screen it just doesn't fully enter the operating system, it feels like it's almost there. Maybe the boot.img can be altered to fully boot

gnomiik said:
Well, it does boot but gets stuck in the rom boot phase. Like I see lineageos on the screen it just doesn't fully enter the operating system, it feels like it's almost there. Maybe the boot.img can be altered to fully boot
Click to expand...
Click to collapse
What exactly did you do?
Sounds like you didnt wipe/format your data partition.

Simon1511 said:
What exactly did you do?
Sounds like you didnt wipe/format your data partition.
Click to expand...
Click to collapse
I did wipe and format as well. I tried it several times. Should it work with the u3 bootloader?

gnomiik said:
I did wipe and format as well. I tried it several times. Should it work with the u3 bootloader?
Click to expand...
Click to collapse
It's supposed to work with all three bootloader revisions (U1, U2, U3) and I had others confirm that it works just fine with those.

Simon1511 said:
It's supposed to work with all three bootloader revisions (U1, U2, U3) and I had others confirm that it works just fine with those.
Click to expand...
Click to collapse
So you are saying I can install Android 11 GSI and it will work with U3 Bootloader? I tried it with LiR 18.1 GSI and could not get it to get past the LineageOS boot screen.
My Steps:
1. In Odin I flashed AP, BL, CP, and CSC (with U3 Bootloader)
2. Next flashed VBMETA U3 and TWRP in Odin
3. In TWRP, wiped Cache, Dalvick Cache, and Data
4. Flashed LiR 18.1 (based on Android 11) to system partition
5. Did Format Data
6. Reboot
At this point Boot occurred, but got stuck on the LineageOS logo and never completed booting.
These steps should have worked correct? Unless I am missing something, but I did these exact steps when I had the U1 bootloader and Lineage fully booted, but with U3 bootloader, Lineage did not fully boot.

gnomiik said:
So you are saying I can install Android 11 GSI and it will work with U3 Bootloader? I tried it with LiR 18.1 GSI and could not get it to get past the LineageOS boot screen.
Click to expand...
Click to collapse
gnomiik said:
These steps should have worked correct? Unless I am missing something, but I did these exact steps when I had the U1 bootloader and Lineage fully booted, but with U3 bootloader, Lineage did not fully boot.
Click to expand...
Click to collapse
I said that U3 works with my LineageOS ROM.
I dont know if any Android 11 GSI still works or not.

Simon1511 said:
I said that U3 works with my LineageOS ROM.
I dont know if any Android 11 GSI still works or not.
Click to expand...
Click to collapse
Understood. Initially I wrote asking about Android 11 / 12 GSI, not your rom. Your rom works just fine on my phone, but I hate Android 13