Hi everybody, I've encountered a strange problem and i come to see if anybody can help me.
Symptom: can't boot into primary ROM. Fine booting into secondary.
I'm using OnePlus 3 with H2OS 3.0 stable v2 as my primary ROM, and official Resurrection Remix as my secondary (installed to data partition).
Today I wanted to update my RR to the newest version so I downloaded the zip and by the way updated Dual Boot Patcher to 9.2.0_r106.
When I turned to ROM tab, it asked me to set kernel (which i did not know why), I didn't care much and pressed 'Yes' (in my Resurrection Remix), then i rebooted to recovery in order to install the patched zip file.
Somehow it failed to install, so I decided to boot into primary and flash with Dual Boot Patcher in primary ROM. But here it happened...It turned black out after I've chosen to boot into primary in the boot screen.
I tried flashing the boot-before-updating-ramdisk.img but it only led to boot loop in boot animation of primary ROM.
ps. Today I found my magisk root in RR is lost. Are these things related?
Can anybody help me with this......
is it because I set kernel while not in primary rom? How do i solve it?
And I'd also like to know what exactly does 'set kernel' do? What files does it modify?
Related
No matter what kernel I flash, the phone crashes on the recovery splash screen (besides new cyanogen recovery). Unlocked bootloader, had cyanogenmod 11 previously but it started having problems...
Previously it was working fine, until today. I'm not sure what happened. Tried installing Kitkat rom because Lollipop is dependent on SDcard and all my SDcards are corrupt (fat32 fine but ext4 broken). Lollipop ROM Cyanogen recovery boots fine, but when I try installing kitkat rom it says footer is wrong. Both CWM and TWRP from KK recoveries crashes on the splash screen.
Suggestions? Very serious issue and I can't boot to ROM without recovery...
Hi,
My galaxy note 2 (N7105) had a lot of crash since a couple of months so I decided to flash a custom rom.
So, first step I rooted my phone with odin & CF-Auto-Root. Then, I installed CWM & download some ROM to try.
First, with MIUI V5 : http://forum.xda-developers.com/showthread.php?t=2597096
On boot, ask me for my pin then load again & again, non stop. Can't change language & it was Japanese...
Second, CM : http://forum.xda-developers.com/galaxy-note-2/development-n7105/rom-unofficial-build-t3067695
Boot correctly but don't know why, after one or two reboot, I got a bootloop...
Third, to fix bootloop, I flashed Stock rom deodexed : http://forum.xda-developers.com/showthread.php?t=2761937
Using Odin (can't access to recovery). Boot correctly but my sim card is not recognized, so for a phone... not perfect
Finally, I tried to install again CM 12.1 but got infinity boot & then tried to flash Resurection rom : http://forum.xda-developers.com/gal...om-resurrectionremix-lp-v5-5-2-t0lte-t3170529
But got a infinity boot again so I flashed again Stock rom deodexed & my sim card is not recognized like before.
So, what's the problem ? Why can't i flash cm or other rom without infinity boot ? & Why stock rom can't recognize my SIM card ?
Please, help me cause I don't have other phone currently...
Thanks in advance !
alain21218 said:
Hi,
My galaxy note 2 (N7105) had a lot of crash since a couple of months so I decided to flash a custom rom.
So, first step I rooted my phone with odin & CF-Auto-Root. Then, I installed CWM & download some ROM to try.
First, with MIUI V5 : http://forum.xda-developers.com/showthread.php?t=2597096
On boot, ask me for my pin then load again & again, non stop. Can't change language & it was Japanese...
Second, CM : http://forum.xda-developers.com/galaxy-note-2/development-n7105/rom-unofficial-build-t3067695
Boot correctly but don't know why, after one or two reboot, I got a bootloop...
Third, to fix bootloop, I flashed Stock rom deodexed : http://forum.xda-developers.com/showthread.php?t=2761937
Using Odin (can't access to recovery). Boot correctly but my sim card is not recognized, so for a phone... not perfect
Finally, I tried to install again CM 12.1 but got infinity boot & then tried to flash Resurection rom : http://forum.xda-developers.com/gal...om-resurrectionremix-lp-v5-5-2-t0lte-t3170529
But got a infinity boot again so I flashed again Stock rom deodexed & my sim card is not recognized like before.
So, what's the problem ? Why can't i flash cm or other rom without infinity boot ? & Why stock rom can't recognize my SIM card ?
Please, help me cause I don't have other phone currently...
Thanks in advance !
Click to expand...
Click to collapse
probably old bootloader or modem
did you do a factory reset in recovery?
you can try twrp
Mmh I tried with twrp but it's the same (with factory reset)
Hello to everyone. I have the problem that when I flash something, for example a custom kernel or other flashable zip and I reboot the phone, it boot but the boot never stop, endless boot. Only when I dirty flash the ROM and the flashable zip (mods or something else) it will boot up normally and I can use my phone ... I installed Al's hosts from adaway and the same.... Endless boot. I think at first that it cause the custom kernel the problem and I tried also with the stock one that canes with the ROM. The same issue remaining. It goes tiring to dirty flash again and again... Someone have the same issue in this ROM?
Edit: Device is N5X running 13/1/17 RR 5.8.0 with latest security patch.
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
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.