Related
Hello,
Trying to install latest PA 'pa_i9300-5.1-20150528.zip' on Galaxy S3 i9300 using TWRP 2.8.6.1.
Zip installs faster, shows no error.
I select the reboot option, it reboots and sits on PA loading logo
I have been using CM12.1 by JustArchi for some time, thought of giving PA a try.
same here, Im also flashing with TWRP2.8.6.1
The pa_i9300-5.1-20150520 version runs well. But the pa_i9300-5.1-20150528 doesnt. It goes directly to TWRP.
wipe, format, factory reset, redownload rom, reflash,.... dont solve.
The same happens when upgrading from Paranoid_OTA app =/
Same here.
But i'm surprised, you say the pa_i9300-5.1-20150520 run well on your I9300 ?
Can you tell me how you managed to make it work ?
I tried a full swipe then install, didn't had any luck, tried differents gapps with no success.
Can you tell me wich Gapps you use please ?
I had tried 'pa_i9300-5.1-20150520.zip' also, it showed the same behavior.
I don't flash gapps on the first go, I boot with just the rom and later reboot into recovery and load all the zips.
mackhdo said:
But i'm surprised, you say the pa_i9300-5.1-20150520 run well on your I9300 ?
Can you tell me how you managed to make it work ?
I tried a full swipe then install, didn't had any luck, tried differents gapps with no success.
Can you tell me wich Gapps you use please ?
Click to expand...
Click to collapse
I ve just followed a tutorial on the internet.
Boot into TWRP, Format, Wipe Cache/Dalvik/System, Install PA, Install GApps, Wipe Cache/Dalvik, and reboot.
And mine is the 5.1.x mini package from there: http://forum.xda-developers.com/paranoid-android/general/5-1-x-5-0-x-4-4-x-pa-gapps-mirror-t3069879
Unable to BOOT
I did a clean installation of PA 5.1 dated 12/6/15. Gapps did well too. Phone reboots and enters CWM again.. did multiple times but it always jumps to CWM. Any guidance Senior Members.
Pretty sure you have to flash a kernel
naveed8695 said:
I did a clean installation of PA 5.1 dated 12/6/15. Gapps did well too. Phone reboots and enters CWM again.. did multiple times but it always jumps to CWM. Any guidance Senior Members.
Click to expand...
Click to collapse
Having exactly the same problem. I can only get the original 5.1 ROM from may to work, but none of the updates. Tried formatting system, cache, dalvik and even tried flashing the boot.img inside the zip file. No luck ?.
YanN509 said:
Having exactly the same problem. I can only get the original 5.1 ROM from may to work, but none of the updates. Tried formatting system, cache, dalvik and even tried flashing the boot.img inside the zip file. No luck ?.
Click to expand...
Click to collapse
You need to flash a different kernel. The boot.img that ships with the rom keeps getting bored during the build it would appear.
This is covered extensively in the g+ community
Pirateghost said:
You need to flash a different kernel. The boot.img that ships with the rom keeps getting bored during the build it would appear.
This is covered extensively in the g+ community
Click to expand...
Click to collapse
Thank you for the advice. :good:
It worked with Boeffla Kernel 12.1 alpha 3 (but the latest ones did not)
pa_i9300-5.1-20150520.zip works!
texmty said:
same here, Im also flashing with TWRP2.8.6.1
The pa_i9300-5.1-20150520 version runs well. But the pa_i9300-5.1-20150528 doesnt. It goes directly to TWRP.
wipe, format, factory reset, redownload rom, reflash,.... dont solve.
The same happens when upgrading from Paranoid_OTA app =/
Click to expand...
Click to collapse
pa_i9300-5.1-20150520.zip works indeed after wipe: dalvik, cache, data, system. then format.
when it successfully boots, restart into recovery and make backup of only "boot" to external_sd.
then format again and factory reset, then install latest zip (pa_i9300-5.1-20150704.zip).
before reboot first restore "boot" from backup.
Tequila4alvin said:
pa_i9300-5.1-20150520.zip works indeed after wipe: dalvik, cache, data, system. then format.
when it successfully boots, restart into recovery and make backup of only "boot" to external_sd.
then format again and factory reset, then install latest zip (pa_i9300-5.1-20150704.zip).
before reboot first restore "boot" from backup.
Click to expand...
Click to collapse
That worked for me too
Heyy,
as i had some problems with my g2 i had to flash stock rom kitkat 4.4.2.
I rooted with ioroot, downloaded lineage and gapps files, flashed custom recovery with autorec but if i then go to twrp and install lineage os and gapps, i always get "your device does not appear to have root. do u want to install supersu?", althoug ive checked root with "root checker" before... i cant find the mistake
I WANT LINEAGE OS
Quicka said:
Heyy,
as i had some problems with my g2 i had to flash stock rom kitkat 4.4.2.
I rooted with ioroot, downloaded lineage and gapps files, flashed custom recovery with autorec but if i then go to twrp and install lineage os and gapps, i always get "your device does not appear to have root. do u want to install supersu?", althoug ive checked root with "root checker" before... i cant find the mistake
I WANT LINEAGE OS
Click to expand...
Click to collapse
Autorec is just the first step to twrp. Go to https://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705 and get the bumped version 3.1.0-1.
Then put it in your phones memory, boot into twrp you got from autorec and flash the new version.
Jan Philipp said:
Autorec is just the first step to twrp. Go to https://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705 and get the bumped version 3.1.0-1.
Then put it in your phones memory, boot into twrp you got from autorec and flash the new version.
Click to expand...
Click to collapse
i have done it... but after i wiped data,... etc. flashed lineage os and gapps and reboot system, phone screen gets black... and i can only go to download mode to flash again stock rom ive tried it about 5 times
Problem fixed
problem fixed: flashed lollipop firmware, then rooted with LGoneClickRoot and installed TWRP with autorec
Quicka said:
problem fixed: flashed lollipop firmware, then rooted with LGoneClickRoot and installed TWRP with autorec
Click to expand...
Click to collapse
How did you flashed your phone? Your display have been black and you haven't seen anything. How did you entered into download mode?
djsasha78 said:
How did you flashed your phone? Your display have been black and you haven't seen anything. How did you entered into download mode?
Click to expand...
Click to collapse
just held the volume up button and then connected with pc. then using lg flash tool to flash lollipop stock rom
1. Root + TWRP : https://www.dropbox.com/s/2shvozzbu29xjfu/LGG2-D802-OneClickRootRecoveryV1.1.zip?dl=0
2. Update TWRP to 3.1 by flashing zip file and then rebooting recovery: http://www.gregtwallace.com/lgg2-projects/twrp/?version=3.1.0-1
3. LineageOS by flashing rom zip file and gapps: https://download.lineageos.org/d802 + http://opengapps.org/ (ARM + Android 7.1)
easiest method to flash lineageOS on LG G2 https://www.youtube.com/watch?v=BoPjGM0nrak (Video tutorial)
Hi,
It seems I have the same issue :
I tried to install LineAge, using TWRP 3.2.1 (from CM12.1), but nothing is working (I tried 20180425 and 20180404 nightly versions). After reboot I can see the backlight on the lcd screen but nothing else. Then I tested the installation of a CM12 version, all is right, normal boot. No error message written in the console. i tried also a CM13 install, same as Lineage.
Do you think I have to flask back to LG "OS" ?
JackSparreau said:
Hi,
It seems I have the same issue :
I tried to install LineAge, using TWRP 3.2.1 (from CM12.1), but nothing is working (I tried 20180425 and 20180404 nightly versions). After reboot I can see the backlight on the lcd screen but nothing else. Then I tested the installation of a CM12 version, all is right, normal boot. No error message written in the console. i tried also a CM13 install, same as Lineage.
Do you think I have to flask back to LG "OS" ?
Click to expand...
Click to collapse
Are you clean flashing? Make sure to factory reset, wipe system, data and cache before flash. Never wipe internal storage. Swipe factory reset again after flash. Try flashing gapps later after confirming that Rom boots fine.
cropsroth said:
Are you clean flashing? Make sure to factory reset, wipe system, data and cache before flash. Never wipe internal storage. Swipe factory reset again after flash. Try flashing gapps later after confirming that Rom boots fine.
Click to expand...
Click to collapse
Hi,
yes I wiped Dalvik, system, data & cache through TWRP, before flash. But I don't wipe after, I rebooted without GApps...
Maybe, because I read that somewhere, I need to flash a bootstack. I don't know when I have to di it, if I have to do.
Thanks
JackSparreau said:
Hi,
yes I wiped Dalvik, system, data & cache through TWRP, before flash. But I don't wipe after, I rebooted without GApps...
Maybe, because I read that somewhere, I need to flash a bootstack. I don't know when I have to di it, if I have to do.
Thanks
Click to expand...
Click to collapse
Yes, you don't wipe after flash, but you swipe the factory reset, it does not wipe but resets the flashed Rom. Give it a clean shot again. Check MD5 of the all files you downloaded with original MD5 to confirm the file didn't get corrupt.
Boot stack flash not needed. Please read the first post thoroughly in lineage thread
"""
Requirements:
Custom recovery (TWRP or any other)
KitKat (KK) bootloader (included in the lg-devs LP bootstack)
KitKat (KK) bootstack minimum; Please read the entire FAQ for important bootstack information. Installation of bootstacks is NOT recommended.
Clean flash if coming from another ROM or CM 13 (no dirty flash, wipe system too check you bootstack(needen bump support)
"""
crophs said:
... but you swipe the factory reset, it does not wipe but resets the flashed Rom. Give it a clean shot again. ...
Click to expand...
Click to collapse
Hi,
what do you mean by "you swipe the factory reset", I'm not sure what it is, either "give it a clean shot again".
Sorry I'm not very aware of all those processes ^_^, and I'm french so not very aware of some vocabulary words
Thank you
My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
I had an older version of twrp so I just updated it to the latest one before attempting this ofc...
I tried flashing the latest RR and AICP and both give me boot loops and I always get this one problem where it says
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
I'm not sure if this has anything to do with the bootloop though...
Going to recovery after seeing the bootloop I always get the "keep system read only?" prompt where i swipe to allow modification but i usually just restore back to my backup from there... i dont think allowing it and trying to boot again will get rid of the bootloop...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
OppaiHeroStar said:
My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
Click to expand...
Click to collapse
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
dzidexx said:
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
Click to expand...
Click to collapse
The first 3 steps I've already done that since the beginning
Where can i get the nougat modem/is it possible to update to it? I guess that's the reason every single 7.1 custom rom I tried in the android development section gave me boot loops...
And could you link the 21.11.2017 version of RR? I'm looking at the download links for RR and I dont see one with that exact date
edit-just saw your edit
Custom roms for MM modem works better.
I fully wiped using TWRP, checked everything I possibly could except my micro SD card and I flashed RR-N-v5.8.5-20171121-clark-Final.zip then gapps arm64, 7.1 nano and it's still giving me boot loops. I'm using TWRP 3.2.1-0
im gonna try using gapps arm64 7.1 mini really quick since you said I should use that one and see if it boot loops... - Edit guess I was too optimistic thinking this would fix it
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
dzidexx said:
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
Click to expand...
Click to collapse
changed to 3.1.1-0 and did everything you said, still have boot loop...
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
OppaiHeroStar said:
changed to 3.1.1-0 and did everything you said, still have boot loop...
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
dzidexx said:
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
Click to expand...
Click to collapse
I tried crDroidAndroid-7.1.2-20171119-clark-v3.8.3.zip and it still boot loops :\ I also already tried LineageOS and AICP before we started talking
I went back to my backup and it put me in a bootloop which never happened before but changing cache back to ext4 instead of f2fs fixed it..
OppaiHeroStar said:
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
A little late to chime in and this does not help with your current situation, but here's a little advice. I flash a lot of ROMs (how else am I going to test builds right?). This error happens all the time, BUT if you flash a ROM twice it should not show on the 2nd flash.
So flash order goes:
Wipe/Factory reset
Format data x3 (yes I format my data 3 times for every ROM)
Reboot
Wipe/Factory reset
ROM
ROM again
GAPPS
Wipe caches
Reboot
Do the Initial setup
Reboot before use
OPTIONAL Kernel (if its not already build in)
OPTIONAL Magisk (I never flash Magisk on a clean build but heck I'm expecting a NON boot most of the time anyways)
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
acejavelin said:
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
Click to expand...
Click to collapse
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
OppaiHeroStar said:
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
Click to expand...
Click to collapse
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
acejavelin said:
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
Click to expand...
Click to collapse
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
OppaiHeroStar said:
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
Click to expand...
Click to collapse
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
acejavelin said:
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
Click to expand...
Click to collapse
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
OppaiHeroStar said:
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
Click to expand...
Click to collapse
What custom did you flashed?
dzidexx said:
What custom did you flashed?
Click to expand...
Click to collapse
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
OppaiHeroStar said:
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
Click to expand...
Click to collapse
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
dzidexx said:
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
Click to expand...
Click to collapse
I'm using t-mobile and I've checked the access points, clicking on the one im using and hitting save doesn't fix it. Always getting a notification telling me to sign in to network. Not sure what else I can do. I'll give it a day since I had this kind of problem before when I switched sim cards and data didn't work until the next day
Edit - just went back to stock and my data doesn't work now either... just going to stay at RR now and hope my data fixes itself because my access point settings for tmobile should be correct since I looked it up on the official website..
I have bricked my phone the issue I am facing is I don't own and can't afford an SD card to sideload the rom onto my phone is there a 7.0 stock based rom that is flashable via TWRP or? Really need some ideas need to fix this device.
If you have access to TWRP, then plug your phone into your computer and it'll mount your internal sdcard. Copy any Rom you want onto it and flash as normal (remember to wipe cache and dalvik!). If you get the "error 7" output, edit your updater script and do it again. If you get a bootloop after successfully flashing, flash the latest magisk zip (I assume you use root?) or noverity file if not.
wang1chung said:
If you have access to TWRP, then plug your phone into your computer and it'll mount your internal sdcard. Copy any Rom you want onto it and flash as normal (remember to wipe cache and dalvik!). If you get the "error 7" output, edit your updater script and do it again. If you get a bootloop after successfully flashing, flash the latest magisk zip (I assume you use root?) or noverity file if not.
Click to expand...
Click to collapse
I use root and both but when I decided to remove root and was looking at installing another rom it failed now I don't see any twrp flashable roms for my device would you know of any? I tried stock but it can't be flashed from TWRP sadly I have no bootable rom at the moment.
@mastermarkofroms
EVERY Rom that can be flashed through stock recovery can be flashed through TWRP.
....all you need to do is edit the updater script as I said above. Give it a shot
Edit: you softbricked your phone removing root? Just perform a factory reset, you'll lose your personal data but it'll boot. Remember to wipe cache and dalvik.
wang1chung said:
@mastermarkofroms
EVERY Rom that can be flashed through stock recovery can be flashed through TWRP.
....all you need to do is edit the updater script as I said above. Give it a shot
Edit: you softbricked your phone removing root? Just perform a factory reset, you'll lose your personal data but it'll boot. Remember to wipe cache and dalvik.
Click to expand...
Click to collapse
I have never modified that before what would I need to modify to get it working?
@mastermarkofroms
Open the Rom archive and edit the updater script (/META-INF/com/google/android/updater-script) to remove the first 7 lines (sometimes more or less) of code, so the script starts at "ui_print....." now. Save it, and load it onto your sdcard and flash.
wang1chung said:
@mastermarkofroms
Open the Rom archive and edit the updater script (/META-INF/com/google/android/updater-script) to remove the first 7 lines (sometimes more or less) of code, so the script starts at "ui_print....." now. Save it, and load it onto your sdcard and flash.
Click to expand...
Click to collapse
I will give that a shot turns out a factory reset did not start up device so this is my last choice as I can still access recovery
edit: so after modifying the script it did flash without an issue but it still has failed to boot reloading the bootloader.
Flash magisk or the no verify file
wang1chung said:
Flash magisk or the no verify file
Click to expand...
Click to collapse
the no verify file was flashed when I rooted this device
Which Rom did you flash?
You performed a factory reset and wiped dalvik and cache after flashing? How long did you wait after rebooting? Usually takes 5-10min on the first boot.
Edit: you flashed the no verity file after flashing the rom today, right?
wang1chung said:
Which Rom did you flash?
You performed a factory reset and wiped dalvik and cache after flashing? How long did you wait after rebooting? Usually takes 5-10min on the first boot.
Edit: you flashed the no verity file after flashing the rom today, right?
Click to expand...
Click to collapse
I tried flashing Unofficial LineageOS 14.1 for ZE552KL by basenode with opengapps it just failed to flash not an error 7 it actually gave me a wrong device error although I know I have the ze552kL model. and since then it don' boot it tries to you see the asus logo and it just restarts again in a boot loop
Flash magisk right now, then wipe cache and dalvik
Go back asus nougat 7.0 -> factory reset -> flash LOS 14.1 -> flash gapps -> done. Flash magisk if you want.
Edit: when you go back asus rom and face bootloop then just flash no-verity file, everything will work like normal .
[email protected]@ said:
Go back asus nougat 7.0 -> factory reset -> flash LOS 14.1 -> flash gapps -> done. Flash magisk if you want.
Edit: when you go back asus rom and face bootloop then just flash no-verity file, everything will work like normal .
Click to expand...
Click to collapse
Thanks for the info will give that a shot as soon as I do get home from work. Just ablittle annoyed that first phone I have ever bricked
[email protected]@ said:
Go back asus nougat 7.0 -> factory reset -> flash LOS 14.1 -> flash gapps -> done. Flash magisk if you want.
Edit: when you go back asus rom and face bootloop then just flash no-verity file, everything will work like normal .
Click to expand...
Click to collapse
Any ideas where I can find the no verity file? I dont see it on the forum unless I am blind
mastermarkofroms said:
Any ideas where I can find the no verity file? I dont see it on the forum unless I am blind
Click to expand...
Click to collapse
Here https://forum.xda-developers.com/ze...20kl-ota-upgrade-doesnt-t3706856/post74571792
[email protected]@ said:
Here https://forum.xda-developers.com/ze...20kl-ota-upgrade-doesnt-t3706856/post74571792
Click to expand...
Click to collapse
Problem solved back on stock thanks for all the help @everyone
mastermarkofroms said:
Problem solved back on stock thanks for all the help @everyone
Click to expand...
Click to collapse
I thought you ask for the LOS rom.
I did the thing is had it installed and everything but my phone kept freezing and lagging with it not sure why as I had nothing on there that would of caused it. But the lag once I got it working was just unbearable for me
mastermarkofroms said:
I did the thing is had it installed and everything but my phone kept freezing and lagging with it not sure why as I had nothing on there that would of caused it. But the lag once I got it working was just unbearable for me
Click to expand...
Click to collapse
Which rom?
Hello together,
after 3 Days of reading and searching and testing solutions, I have to ask you if you can solve my problem.
I can't find the reason by myself, because I'm new with this topic. I want to install a Custom ROM on my Huawei P 8 Lite Alice from 2015, but everytime I flash any Custom ROM which should match, it ends in a bootloop (huawei logo, then logo custom rom, then huawei logo etc....).
My device:
Huawei P8 Lite ALE L21 from 2015 - Alice
Built number before start this "project": ALE-L21C432B634
Android 6
Emui 4.0.3
Bootloader unlocked with code generated by dc-unlocker
No Root
My prefered Custom ROM is Lineage OS 14.1 and I tried to flash it following the steps in this thread:
[url]https://forum.xda-developers.com/p8lite/development/rom-lineageos-14-1-p8-lite-t3824247[/URL]
1. step - Flash TWRP
First Problem was to install the TWRP 3.1.1 linked in this thread:
[url]https://forum.xda-developers.com/p8lite/orig-development/twrp-t3583180[/url][/URL]
To flash the TWRP image with adb caused no problem. When I boot into recovery, TWRP starts, but when I touch anything on the screen (like swipe to unlock) the System boots (With OS installed it boots the OS and without it stucks at huawei logo). Booting again into TWRP is no Problem.
I solved this problem with a TWRP image 3.1.0-1 from this forum:
[url]https://www.android-hilfe.de/forum/root-custom-roms-modding-fuer-huawei-p8-lite.2476/huawei-p8lite-neues-inoffizielles-twrp-3-1-0-1-von-surdu_petru-xda.826139.html[/URL]
The thread references on the same XDA thread mentioned above, but it is linked to another version of TWRP image. This Version 3.1.0-1 is working good.
2. step - flash EMUI 4.1
I flashed the EMUI Update B896 with TWRP. In the thread to the Lineage OS 14.1 mentioned above, it is described that you need this update. I used the linked .zip.
Steps:
1. Wipe Data, internal storage, system, Dalvik Cache, Cache (all except micro sd card).
2. Format Data
3. Reboot into TWRP
4. flash .zip from SD card
5. Wipe Davlik Cache and Cache
5. Reboot System
After that :
Android 6
Build number: ALE B896
EMUI: 4.1
The updated ROM works good.
3. Step - Flash Lineage OS 14.1
Steps:
1. Wipe Data, internal storage, system, Dalvik Cache, Cache (all except micro sd card).
2. Format Data
3. Reboot into TWRP
4. flash .zip from SD card
5. Wipe Davlik Cache and Cache
5. Reboot System
Result Boot Loop :victory:
Trouble shooting:
I tried to install different TWRP versions, but only the TWRP 3.1.0-1 works.
I useb adb sideload to flash the Lineage
I flashed the EMUI 4.03. I had before and than Lineage 14.1 (EMUI works, but Lineage doesn't)
I wiped dalvik cache and data, cache after flashing Lineage, to fix the bootloop
I flashed versions of Lineage OS 14.1 from different dates and different download websites
I flashed different Custom ROMS - all the same Problem except Lineage 13.0. Lineage 13.0 boots till it is ready to "preparing" apps and than boots again.
Now I don't know what do do and would be very thankful to get some new ideas to try or perhaps a solution
Thank you! :highfive:
The ROM needs Emui 4.1 B895/B896 update to be installed first
Then unlock bootloader, flash twrp then flash ROM
Thank you for your help. I'll try this. So I have to lock bootloader again first?
No. You flash the update with twrp
Go to step 6 in the first post on this thread
https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
Keran_3066 said:
No. You flash the update with twrp
Go to step 6 in the first post on this thread
https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
Click to expand...
Click to collapse
Maybe I described it not so good in my first post but I think I did it already exactly like that.
1. Unlock bootloader
2. Flash TWRP
3. Flash Emui 4.1 update B896 ( its working on my phone now)
4. Flash TWRP again
5. Flash Custom Rom ( evertime the result is a bootloop)
Or did I overlook anything?
Sorry I didn't read that part where you flashed emui 4.1
Lineage os 14.1 works for me.
Did you try Resurrection Remix OS
https://forum.xda-developers.com/p8lite/development/rom-t3606568
Keran_3066 said:
Sorry I didn't read that part where you flashed emui 4.1
Lineage os 14.1 works for me.
Did you try Resurrection Remix OS
https://forum.xda-developers.com/p8lite/development/rom-t3606568
Click to expand...
Click to collapse
Thank you very much, that you tried to help me Im happy about all suggestions.
Yes I tried RR and Paranoid, but its the same Problem. I'm wondering that the EMUI Roms which are not officially from Huawei work and any custom rom does not. Maybe there is a Problem with the structure of my system but I dont know anything about this stuff and how to find out the reason for my Problem:laugh:
Maybe you know a command for adb or android terminal app to check if everything is ok?
Jaba Wup said:
Maybe you know a command for adb or android terminal app to check if everything is ok?
Click to expand...
Click to collapse
I'm kinda out of ideas
Keran_3066 said:
I'm kinda out of ideas
Click to expand...
Click to collapse
I feel like you:laugh: thanks and have a nice evening:good: