Develop Bugs

[Q] Note II keeps booting into recovery mode

Hey guys,
I apologize if this has been asked and resolved a thousand times already. I've searched through this sub-forum and the threads on it didn't seem to have a solution that worked for me.
The issue: I just recently flashed CM 12 Nightly and Gapps, along with changing recovery from CWM to TWRP. I flashed TWRP via Odin, then installed CM 12 and Gapps via TWRP. I was able to get into CM 12 ONCE and it worked just fine, but when I restarted my phone after the initial flash, it now just constantly boots into TWRP.
To clarify for those that might wonder: I can get into TWRP and download mode just fine. I just...can't get beyond them.
What I've tried: I found these instructions - http://forum.xda-developers.com/showpost.php?p=21301573&postcount=3
However I can't get ADB to find my device as I can't actually boot it into the OS. If I should be going about this a different way then please let me know.
I've also tried reflashing the recovery, reflashing the ROM and Gapps, reflashing my old ROM and Gapps, wiping Dalvik, cache, and data partition (both via TWRP and Odin), pulling the battery and starting as normal, booting into download mode and then rebooting from there.
All of the above has got me no luck so far.
If any of you have any suggestions then I would be very grateful. Cheers.

I managed to get back into my phone by flashing my carrier's stock ROM via Odin, worked a treat.
Time to start again!

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

[Solved]Can't flash rom+gapps

So i originally had a p2c...blabla
Ota updated to p2a4 or something like that. sf244 ROW
unlocked oem (waited 14days)
flashed twrp.
factory resetted+format system. + data partition is ext4
rom flashed successfully
gapps starts flashing but keeps stuck after just 1% of flashing.. always.
or twrp keeps freezing.
Does anyone have a solution?
Right now i'm back to Stock Rom+Magisk 13.3 .

sm00th4f3 said:
So i originally had a p2c...blabla
Ota updated to p2a4 or something like that. sf244 ROW
unlocked oem (waited 14days)
flashed twrp.
factory resetted+format system. + data partition is ext4
rom flashed successfully
gapps starts flashing but keeps stuck after just 1% of flashing.. always.
or twrp keeps freezing.
Does anyone have a solution?
Right now i'm back to Stock Rom+Magisk 13.3 .
Click to expand...
Click to collapse
If you have backup then Install your stock rom and its every components such as boot, recovery etc....
Or download the fastboot files from the p2 thread and flash it.
Then properly install twrp.

How can i properly install twrp?.. I mean, i think i always installed in correctly...otherwise magisk wouldn't work., right?. Because it does. I need your help. I even got Safetynet Pass and Root Apps like Root Explorer is working Fine.
Only the Flashing of Custom Roms etc fails for me... It's weird.

Okey. I just redid it like 5 Times. And i got a bit farther.. new boot animation shows up. But still blue led after it stops.

I FINALLY found the SolutioN!!! I used this https://androidfilehost.com/?fid=817550096634780916 and did the upgrades per ota. Then adb'd my twrp on my phone. And changed data to ext4. Rebooted. Activated usb debugging again. flashed twrp again(just to be sure), booted into twrp. Formatted system,data,cache,dalvik and then flashed my roms. SUCCESS <3

Help - not booting into os!

Hi.
I dont know where to start.
My redmi 5a had the last original software miui 11 based (android 8.1). Then I successfully unlocked the bootloader some days ago and somehow managed to install nitrogenOS (android 11 based).
Then I tried to flash another custom rom and everything went bad. I cant boot into any os anymore. I get stuck at the boot screen with the android logo and after some time it starts again and again...
I already tried to install a custom oreo recover firmware, which works, so I could start twrp again. But then every os I tried to install does not work. Fastboot works.
I am very confused now and dont know what to do next

Since you have bootloader already unlocked you can use Mi Flash (Xiaomi's own flash tool) to flash a stock ROM back to you device. This usually help, but of course, it will make you lose the custom ROM installed and the recovery.
Also, pay attention while flashing with this tool. There is an option at the bottom of the program that locks the bootloader again. If you don't want that you have to change this options every time you close the program.

OK, I started XiaomiTool V2 (on linux) and choose the option, that my device is bricked. I then have to choose my model (Redmi 5a riva) and start in fastboot. Now the tool starts to download and install the following rom to recover the smartphone:
riva_global_images_V11.0.2.0.OCKMIXM_20191106.0000.00_8.1_global_605da3d46d.tgz
But it does not work. The smartphone starts and I can see the start screen (powered by android). After some seconds there is a white screen with the words: just a sec. Then the smartphone starts again and it repeats again and again...

Nobody an idea?

sylvio2000 said:
OK, I started XiaomiTool V2 (on linux) and choose the option, that my device is bricked. I then have to choose my model (Redmi 5a riva) and start in fastboot. Now the tool starts to download and install the following rom to recover the smartphone:
riva_global_images_V11.0.2.0.OCKMIXM_20191106.0000.00_8.1_global_605da3d46d.tgz
But it does not work. The smartphone starts and I can see the start screen (powered by android). After some seconds there is a white screen with the words: just a sec. Then the smartphone starts again and it repeats again and again...
Click to expand...
Click to collapse
This has happened to me before. From the name of the image that XiaomiTool download and installed I can assume it is an more recent ROM. (since it has 2019 and 8.1 Global in it)
Do not let XiaomiTool download and install a ROM. Download a older Stock ROM yourself and make XiaomiTool install the ROM that you have download.
As I said previously. Try to download the original Stock ROM that came with your phone when you bought. BEFORE ANY official updates from Xiaomi. This have worked for me.

Hi.
Thanks It works now. I have installed the stock rom.
Is there a guide to get from stock rom (nougat) to custom rom?

sylvio2000 said:
Hi.
Thanks It works now. I have installed the stock rom.
Is there a guide to get from stock rom (nougat) to custom rom?
Click to expand...
Click to collapse
So firstly you need a recovery image (TWRP, PBRP, OF, Batik Recovery) to replace MIUI Recovery. flash it via fastboot with adb (you can do it right?).
After that reboot and push the button to recovery and remember make backup firstly or you can ignore it and yeah do it own your risk.
wipe or advanced wipe Cache, Data, System, Dalvik, Vendor.
and then install the CUSROM, and GApps.
and yeah only that to install CUSROM i know

Can't install any rom

Hello,
Just after unlocked the bootloader, I flashed Orange Fox recovery and tried to install the last Pixel Experience, but I was stuck on boot animation.
Same for previous Pixel Experience rom.
Then, I tried LineageOS 19.1, and successfully booter on it. But, I got screen that said "Your data may be corrupter" and can't do anything but reboot into recovery.
I'm out of option, now... Did I forgot something ?
PS: I also tried to flash Chikori Kernel but I got error "New image is larger than targeted partition"

shim80 said:
Hello,
Just after unlocked the bootloader, I flashed Orange Fox recovery and tried to install the last Pixel Experience, but I was stuck on boot animation.
Same for previous Pixel Experience rom.
Then, I tried LineageOS 19.1, and successfully booter on it. But, I got screen that said "Your data may be corrupter" and can't do anything but reboot into recovery.
I'm out of option, now... Did I forgot something ?
PS: I also tried to flash Chikori Kernel but I got error "New image is larger than targeted partition"
Click to expand...
Click to collapse
Try to flash V12.5.3.0.QFLCNXM with Twrp/O.f (TWRP is newer than this OF.)
then
reboot Twrp/O.F
Wipe/format data type yes
reboot Twrp/O.F
Flash rom
Sometimes the flashing of the recovery ROM does not work with the Twrp/O.F in this case use Miflash with a fastboot rom.

If you're still trying to figure this one out, I think I know how to solve your issue installing LOS.
You most likely used TWRP v3.70, am I right?
You should use TWRP v3.61 coz that was the last stable version that worked, the only thing is that you might need to find another custom recovery other than the official TWRP after installing an Android 12 custom ROM like LOS 19.1.
Lineage OS has their own recovery so you'd probably need to use that if you want to update it.

Same issue with me. yesterday. Though mine is fixed.
My workaround was: I installed the official 12.5.3 MIUI using OrangeFox. After boot, I tried installing PixelExperience using Pixel recovery. There I got successfully installed a custom ROM. Alhough I am not sure if the mounting/encryption of Internal SD is the cause.