Related
I don't know if someone already posted this, but searched and couldn't find the answer. I get stuck at boot screen all on AOSP 4.2.2 roms that I tried, but with any TW roms are fine (no problem at all). Can anyone help? I want to run AOSP rom. Thanks.
I think you may be using a touch wiz kernel
You can find some aosp kernels in the original development thread
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
jinxzn said:
I don't know if someone already posted this, but searched and couldn't find the answer. I get stuck at boot screen all on AOSP 4.2.2 roms that I tried, but with any TW roms are fine (no problem at all). Can anyone help? I want to run AOSP rom. Thanks.
Click to expand...
Click to collapse
which rom did you flash, and what did you flash?
the rom only?
the rom and GAAPS?
The rom and kernel?
you need to provide more details if you want to be helped..
Zachinater said:
I think you may be using a touch wiz kernel
You can find some aosp kernels in the original development thread
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I did flashed SOAPKernel along with aosp roms.
wase4711 said:
which rom did you flash, and what did you flash?
the rom only?
the rom and GAAPS?
The rom and kernel?
you need to provide more details if you want to be helped..
Click to expand...
Click to collapse
I flashed BeanStalk, SlimBean, CyanogenMod 10.1 official nightlies, FSC rom, and IllusionRom.
I have CWM Philz_Touch 5.07.1. Every time install a new rom, I wiped Caches + Data / Factory Reset 2x.
I flashed rom only, then flashed rom and GAPPS, those 2 didn't work, I even tried rom w/ SOAPKernel and still didn't work.
ok, you should try switching to TWRP, since most of the time people have zero issues flashing AOSP roms with TWRP.
Also, after all your wipes, flash the rom and GAAPS in the same session, and reboot..
I've done this exact procedure for years, and it works for me 99.98% of the time..
wase4711 said:
ok, you should try switching to TWRP, since most of the time people have zero issues flashing AOSP roms with TWRP.
Also, after all your wipes, flash the rom and GAAPS in the same session, and reboot..
I've done this exact procedure for years, and it works for me 99.98% of the time..
Click to expand...
Click to collapse
Switched to TWRP, and did all the wipes, install rom and GAAPS. Same thing.
Planning to flash stock rom, and redo all the root/recovery procedures all over again. Do you think I should do that?
it couldnt hurt...
some phones are just tempremental; do you have an SD card in your phone?
are you installing from the sd card or internal memory?
try installing from one or the other to see if that helps; sometimes it does...
wase4711 said:
it couldnt hurt...
some phones are just tempremental; do you have an SD card in your phone?
are you installing from the sd card or internal memory?
try installing from one or the other to see if that helps; sometimes it does...
Click to expand...
Click to collapse
I did try both, none work for me.
Thank you so much for your help thou. I'll now just install stock rom and re-root it, see how it goes.
jinxzn said:
I did try both, none work for me.
Thank you so much for your help thou. I'll now just install stock rom and re-root it, see how it goes.
Click to expand...
Click to collapse
good luck, and post back if you get it working properly
flashed stock rom and rooted and installed boot recovery, after all that, it's still not let me install any AOSP roms. Really don't why I can only flash TW roms but not AOSP roms.
hello,
(with "this rom" i mean >sultan cm13<. I edited the title, before that it "was can't but sultan cm13", but now i know it doesnt boots any aosp roms)
a few days ago i used this rom as secondary with multirom (primary was freedom 1.10). now today, i wanted to use this rom as my dailydriver rom. i made the normal procedure, making a backup, then wiping the partitions (system, data, cache, dalvik) and after it flashing the rom. on the first try, i did it like i usually do, first the rom, then the gapps and then xposed. then i rebooted, and it was stuck on the 1+ logo screen about 10 mins. then i reflashed it, but just the cm.zip. then i still got stuck.
i tried it with the unofficial and the official twrp recovery. now i did a nandroid restore to the freedomos rom, and it boots normal.
please help me, i really want to use sultans cm13, i really like it!
i don't know why it doesn't work, i mean as a secondary it booted flawless..
btw i'm on the 3.2.7 firmware
(problem exists on all 6.0 aosp roms i tried. Please read further posts)
Did you follow the flashing instructions to the letter? If you did, you would have seen that the CM13 requires a one time flash of the OOS 3.2.6 firmware (linked in the thread).
Yeah sure but it did work with the 3.2.7 firmware on multirom, so i thought i dont have to do this. Well i will try this, and give you feedback then
Thanks
ReNeH99 said:
Yeah sure but it did work with the 3.2.7 firmware on multirom, so i thought i dont have to do this. Well i will try this, and give you feedback then
Thanks
Click to expand...
Click to collapse
BTW, which xposed version did you flash? If it was v86.x then that's the most likely culprit (since the latest patch, v87 works, v86.x causes bootloop).
i just flashed the 3.2.6 firmware, still does not work.
yes i used the v87 xposed, also the second try i only installed the cm.zip, without xposed and gapps, etc.
ReNeH99 said:
i just flashed the 3.2.6 firmware, still does not work.
yes i used the v87 xposed, also the second try i only installed the cm.zip, without xposed and gapps, etc.
Click to expand...
Click to collapse
Hmm... strange... TWRP doesn't give any errors either?
Hw4ng3r said:
Hmm... strange... TWRP doesn't give any errors either?
Click to expand...
Click to collapse
nope no errors, all the folders and build.prop, etc is in the /system folder too..
i also redownloaded the rom, md5 hash is right and it doesn't help either
May be a silly question but did you uninstall multirom?
Hw4ng3r said:
May be a silly question but did you uninstall multirom?
Click to expand...
Click to collapse
yep
i gonna try to flash RR 5.7.4, to see what happens then
edit: what i forgot to say, i also reinstalled multirom and the multirom recovery for another try. in the multirom menu the touch doesn't work then, and when the primary rom (cm13 sultan) boots after 5 secs, i just get a black screen, the phone isnt of, just a black screen, i have to press all 3 buttons for a reboot then.
edit2: RR also does not boot
edit3: lol i just reinstalled multirom and it boots as secondary rom. then i copied it to the primary slot, and *bling* it doesn't boot again... i dont get this...
Ok i tried it with multiple AOSP roms and it simply doesn't work. Strange thing is, they work as a secondary rom when i have multirom installed.
Does anybody have a solution for this maybe? I hope someone who knows about this problem can help me i don't want oos anymore i need aosp
I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Does anyone know what the problem could be?
I would suggest you clean flash OOS first before going to Freedom.
I think RR is based on Lineage OS while Freedom is based on stock OOS.
Envoyé de mon iPhone en utilisant Tapatalk
Wrong forum.
danecr7 said:
I would suggest you clean flash OOS first before going to Freedom.
I think RR is based on Lineage OS while Freedom is based on stock OOS.
Envoyé de mon iPhone en utilisant Tapatalk
Click to expand...
Click to collapse
RR is based on CM. I'm just scared to flash OOS in case it goes wrong because stock OOS will overwrite TWRP with its stock recovery and then I'll be screwed because I'll have no way to restore from a backup if it goes wrong
RazorBlade123 said:
Wrong forum.
Click to expand...
Click to collapse
Yeah I thought it seemed a little out of place but I don't know where to post it? Is there a general questions forum?
evilkitty69 said:
RR is based on CM. I'm just scared to flash OOS in case it goes wrong because stock OOS will overwrite TWRP with its stock recovery and then I'll be screwed because I'll have no way to restore from a backup if it goes wrong
Click to expand...
Click to collapse
I don't think that there is a risk in flashing stock OOS. But if the custom recovery is overwritten then flash it back, your backup files are stored in your internal memory and unless you wipe it you are safe.
danecr7 said:
I don't think that there is a risk in flashing stock OOS. But if the custom recovery is overwritten then flash it back, your backup files are stored in your internal memory and unless you wipe it you are safe.
Click to expand...
Click to collapse
Even when I tried flashing other CM based ROMs, including ones I'd flashed before, it failed, only flashing RR actually worked. I don't know why this is the case but I'm not sure flashing OOS without knowing what the issue is, is the solution because if I lose TWRP there's no telling whether I'll be able to flash it back in fastboot if the phone isn't working properly
evilkitty69 said:
Even when I tried flashing other CM based ROMs, including ones I'd flashed before, it failed, only flashing RR actually worked. I don't know why this is the case but I'm not sure flashing OOS without knowing what the issue is, is the solution because if I lose TWRP there's no telling whether I'll be able to flash it back in fastboot if the phone isn't working properly
Click to expand...
Click to collapse
I once flashed RR based on android 7.1.1 and because I did not like it very much I wanted to go back to Freedom but at that time it was based on android 7.0.1 thus I was unable to boot. Maybe you are facing the same issue. But in my case I hardbricked my device and used the unbricking tool from OP3 forum.
If you download the latest OOS zip file you can flash it through TWRP and you won't lose you custom recovery.
danecr7 said:
I once flashed RR based on android 7.1.1 and because I did not like it very much I wanted to go back to Freedom but at that time it was based on android 7.0.1 thus I was unable to boot. Maybe you are facing the same issue. But in my case I hardbricked my device and used the unbricking tool from OP3 forum.
If you download the latest OOS zip file you can flash it through TWRP and you won't lose you custom recovery.
Click to expand...
Click to collapse
All of the ROMs I tried with were android 6.0.1, I'm avoiding touching android 7 because I'm not a fan
The strange thing is that in TWRP under "mount", system is unchecked and it won't stay checked when I reboot or try to flash something and then the flash fails. Strangely however, I can flash RR afresh and it will work but nothing else works
Therefore I don't think OOS would work either
i've been struggling lately to install miui on my device and i remember that i used to be able to. but now, every time i flash any build of Miui, it looks like it's messing up the graphic card. steps i did:
having ob 18 installed, i flashed 3.2.8(and 3.2.7) firmware and modem (everything ok)
next, i flashed miui(all of them, with and without gapps)
and after the instalations succeds,, i reboot, and the screen looks blueish and pixelated, like it's burned.
the only way yo fix this was to flash 3.2.8 firmware and modem again, just to be able to boot to the rom
BUT.... that's not it
i boot succesfully into the rom, and if i lock, then unlock the phone, that overlay gets back
the problem is present even on the bootloader and recovery menu.
i'm back to oos now, but i will flash it again tonight and post some pictures
cheers
Here is a video I made
XDRdaniel said:
i've been struggling lately to install miui on my device and i remember that i used to be able to. but now, every time i flash any build of Miui, it looks like it's messing up the graphic card. steps i did:
having ob 18 installed, i flashed 3.2.8(and 3.2.7) firmware and modem (everything ok)
next, i flashed miui(all of them, with and without gapps)
and after the instalations succeds,, i reboot, and the screen looks blueish and pixelated, like it's burned.
the only way yo fix this was to flash 3.2.8 firmware and modem again, just to be able to boot to the rom
BUT.... that's not it
i boot succesfully into the rom, and if i lock, then unlock the phone, that overlay gets back
the problem is present even on the bootloader and recovery menu.
i'm back to oos now, but i will flash it again tonight and post some pictures
cheers
Click to expand...
Click to collapse
thanks
MarJava said:
thanks
Click to expand...
Click to collapse
for what? :|
XDRdaniel said:
for what? :|
Click to expand...
Click to collapse
不错啊
MarJava said:
不错啊
Click to expand...
Click to collapse
what's nice?
XDRdaniel said:
i've been struggling lately to install miui on my device and i remember that i used to be able to. but now, every time i flash any build of Miui, it looks like it's messing up the graphic card. steps i did:
having ob 18 installed, i flashed 3.2.8(and 3.2.7) firmware and modem (everything ok)
next, i flashed miui(all of them, with and without gapps)
and after the instalations succeds,, i reboot, and the screen looks blueish and pixelated, like it's burned.
the only way yo fix this was to flash 3.2.8 firmware and modem again, just to be able to boot to the rom
BUT.... that's not it
i boot succesfully into the rom, and if i lock, then unlock the phone, that overlay gets back
the problem is present even on the bootloader and recovery menu.
i'm back to oos now, but i will flash it again tonight and post some pictures
cheers
Click to expand...
Click to collapse
是不是底包问题
MarJava said:
是不是底包问题
Click to expand...
Click to collapse
it isn't? do you know what's causing the problem? did it ever happend to you?
XDRdaniel said:
it isn't? do you know what's causing the problem? did it ever happend to you?
Click to expand...
Click to collapse
我没用MIUI啊
change your file system for ext4 ... miui rom just suport ext file system and that fixed the issue for me
pedrosantosobral said:
change your file system for ext4 ... miui rom just suport ext file system and that fixed the issue for me
Click to expand...
Click to collapse
Thats riiiight. Now i remember that a moyh ago i switched from ext4 to f2fs.
Yet, i can't tell if this is the reason, because now i am running the latest miui from x_s, and this one runs just fine.
Thank you anyway.
Did you actually get the same screen issue?
XDRdaniel said:
Thats riiiight. Now i remember that a moyh ago i switched from ext4 to f2fs.
Yet, i can't tell if this is the reason, because now i am running the latest miui from x_s, and this one runs just fine.
Thank you anyway.
Did you actually get the same screen issue?
Click to expand...
Click to collapse
No I had a different issue but I'm 100 sure that problem comes due to your file system...the versions u using is adapted to f2fs so it works but unmodified versions have a lot of issues and some of them doesn't even boot on f2fs
Sent from my OnePlus 3 using XDA Labs
Latest miui is based on nougat or marshmallow ? Can you give me a link for the miui you installed ? I want to test it
Diaze said:
Latest miui is based on nougat or marshmallow ? Can you give me a link for the miui you installed ? I want to test it
Click to expand...
Click to collapse
Still mm based. It has the firmware included, so you can flash it over any rom.
https://www.androidfilehost.com/?fid=961840155545570150
I am currently using aosp 8.0 ROM as my daily driver. When I found out that the new aosp 8.1 ROM is available,I flashed(did a clean wipe thou)it got encryption issue(and asked me to reset my phone..when I clicked on the reset button it just used to boot me into my Twrp recovery)so thought something was faulty in the ROM
Then I saw pixel experience ROM based on 8.1 flashed got the same issue again.....I tried to install stock 7.0 recovery from Lenovo it say resetting system but the problem is still there....I also tried changing my my data partition to ext4 but the problem still exist.....SOMEONE PLZ HELLLPPPP
..btw every 8.0 and lower version of ANDRIOD ROM works perfectly.
Hi flash this on twrp https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip and let me know if it works for you, had the same problem.
rksayush said:
I am currently using aosp 8.0 ROM as my daily driver. When I found out that the new aosp 8.1 ROM is available,I flashed(did a clean wipe thou)it got encryption issue(and asked me to reset my phone..when I clicked on the reset button it just used to boot me into my Twrp recovery)so thought something was faulty in the ROM
Then I saw pixel experience ROM based on 8.1 flashed got the same issue again.....I tried to install stock 7.0 recovery from Lenovo it say resetting system but the problem is still there....I also tried changing my my data partition to ext4 but the problem still exist.....SOMEONE PLZ HELLLPPPP
..btw every 8.0 and lower version of ANDRIOD ROM works perfectly.
Click to expand...
Click to collapse
Change data partition to ext4 and den reflash
Use Boardsearch
https://forum.xda-developers.com/lenovo-p2/help/encryption-unsuccessful-aufter-flashing-t3732484
I don't understand
roli0201 said:
Use Boardsearch
https://forum.xda-developers.com/lenovo-p2/help/encryption-unsuccessful-aufter-flashing-t3732484
Click to expand...
Click to collapse
What do u want to say mate?
Problem was solved
ASP02 said:
Change data partition to ext4 and den reflash
Click to expand...
Click to collapse
Just wiped all the data and changed it to ext4 and flashed the ROM again it worked for me.thanks
It didn't but
Cuvillier said:
Hi flash this on twrp https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip and let me know if it works for you, had the same problem.
Click to expand...
Click to collapse
Well I was unable to solve my problem with this but I ahve a question when do I have to flash this before flashing the ROM or after flashing this rom I am making a YouTube video on this issue so your opinion will help a lot thanks.
i have the problem on all oreo roms, i press encrypt, then i see the custom logo loading, and at the reboot i am STILL UNENCRYPTED. the problem is that being unencrypted i do not see any option to use the FINGERPRINT scanner!