I've installed TWRP 3.1.1-0 using fastboot but every time I try to flash a rom using it, I enter a bootloop ([1+] logo, the phone vibrate and reboot).
I've tried with AOSiP 6.3, AOSPlusOne 250817 and AOSPExtended 4.5. (With and without OpenGapps).
With the following procedure:
-Wipe Dalvik, Data, cache, system.
-Flash ROM
-Flash OpenGapps
-Wipe caches
-Reboot.
Am I doing something wrong ? Skipped a step ? Should I use another Rom/Recovery ?
EDIT: Solved ! Before flashing rom, you need to flash the latest official CM13 and then wipe /system before flashing anything else.
Wanted to say thanks. Your post helped me install a good rom again after unbricking my phone. Surprisingly I couldn't find this simple info elsewhere and also Cyanogenmod 13 is also hard to find cause the whole ROM landscape has changed! For instance Using a latest Lineage OS ROM didn't help either. I had to use TWRP from TugaPower and an outdated CM13 from a shady link to get it to work. Not sure which one did the trick but between one of them
Hatomike said:
I've installed TWRP 3.1.1-0 using fastboot but every time I try to flash a rom using it, I enter a bootloop ([1+] logo, the phone vibrate and reboot).
I've tried with AOSiP 6.3, AOSPlusOne 250817 and AOSPExtended 4.5. (With and without OpenGapps).
With the following procedure:
-Wipe Dalvik, Data, cache, system.
-Flash ROM
-Flash OpenGapps
-Wipe caches
-Reboot.
Am I doing something wrong ? Skipped a step ? Should I use another Rom/Recovery ?
EDIT: Solved ! Before flashing rom, you need to flash the latest official CM13 and then wipe /system before flashing anything else.
Click to expand...
Click to collapse
Glad I could help you, I didn't find anything else for this too.
From what I heard, it have something to do with some kind of drivers that are installed with OTA update. Since I disabled them I needed to install the latest official rom from Oneplus
Hatomike said:
I've installed TWRP 3.1.1-0 using fastboot but every time I try to flash a rom using it, I enter a bootloop ([1+] logo, the phone vibrate and reboot).
I've tried with AOSiP 6.3, AOSPlusOne 250817 and AOSPExtended 4.5. (With and without OpenGapps).
With the following procedure:
-Wipe Dalvik, Data, cache, system.
-Flash ROM
-Flash OpenGapps
-Wipe caches
-Reboot.
Am I doing something wrong ? Skipped a step ? Should I use another Rom/Recovery ?
EDIT: Solved ! Before flashing rom, you need to flash the latest official CM13 and then wipe /system before flashing anything else.
Click to expand...
Click to collapse
have to register just say THANK YOU!
saba.ahang said:
Wanted to say thanks. Your post helped me install a good rom again after unbricking my phone. Surprisingly I couldn't find this simple info elsewhere and also Cyanogenmod 13 is also hard to find cause the whole ROM landscape has changed! For instance Using a latest Lineage OS ROM didn't help either. I had to use TWRP from TugaPower and an outdated CM13 from a shady link to get it to work. Not sure which one did the trick but between one of them
Click to expand...
Click to collapse
gottdamm this may be my issue, I've tried a new battery without success, see my thread in this forum.
I'm using the latest TWRP and latest Lineage.
Could you, or anybody, post the links to the Tugapower TWRP and CM13 you used?
edit: I flashed CM13 but still boot looping, as per my other thread. Wondering what the hardware issue is.
Related
Hey,
I'm quite new here, maybe there's an easy solution to that, but I don't know what to do.
I've flashed the CyanogenMod 10 on my HTC Sensation and everything works fine, but as soon as I flash Gapps from the CWM the device enters a boot loop bringing me back to the CWM after rebooting.
J've just tried the newest CM10 (http://forum.xda-developers.com/showthread.php?t=1782009) and the problem is still the same.
Thank you!
Stan.
stanix.de said:
Hey,
I'm quite new here, maybe there's an easy solution to that, but I don't know what to do.
I've flashed the CyanogenMod 10 on my HTC Sensation and everything works fine, but as soon as I flash Gapps from the CWM the device enters a boot loop bringing me back to the CWM after rebooting.
J've just tried the newest CM10 (http://forum.xda-developers.com/showthread.php?t=1782009) and the problem is still the same.
Thank you!
Stan.
Click to expand...
Click to collapse
Hi,
Are you s-on/off?
Did you flash the ROM and Gapps at the same time?
malybru said:
Hi,
Are you s-on/off?
Did you flash the ROM and Gapps at the same time?
Click to expand...
Click to collapse
I'm S-OFF. Yes, I flashed at the same time, first the ROM, then the Gapps
stanix.de said:
I'm S-OFF. Yes, I flashed at the same time, first the ROM, then the Gapps
Click to expand...
Click to collapse
Hi,
Then,there is no reason why it should not work.
I would download ROM and Gapps again,place on the sd card,check md5 checksum.
Format all partitions (except sd card),then,install both again.
malybru said:
Hi,
Then,there is no reason why it should not work.
I would download ROM and Gapps again,place on the sd card,check md5 checksum.
Format all partitions (except sd card),then,install both again.
Click to expand...
Click to collapse
Just a question before I start deleting everything - is it possible that this has something to do with the CID number? I have no idea what it is, but I remember that I had to change it once (now it's set to 11111111)
stanix.de said:
Just a question before I start deleting everything - is it possible that this has something to do with the CID number? I have no idea what it is, but I remember that I had to change it once (now it's set to 11111111)
Click to expand...
Click to collapse
no it has not
Problem solved by flashing a new recovery image (CWM Touch 5.8.0.9)
Thanks!
FIX for bootloop after installing GApps
stanix.de said:
Hey,
I'm quite new here, maybe there's an easy solution to that, but I don't know what to do.
I've flashed the CyanogenMod 10 on my HTC Sensation and everything works fine, but as soon as I flash Gapps from the CWM the device enters a boot loop bringing me back to the CWM after rebooting.
J've just tried the newest CM10 (http://forum.xda-developers.com/showthread.php?t=1782009) and the problem is still the same.
Thank you!
Stan.
Click to expand...
Click to collapse
So, here is a fix, follow my steps:
1. DO NOT USE CWM Recovery OR PhilzTouch Recovery, because you will have bootloop with them OR flashing GApps will fail, so u need to use TWRP
2. Copy CM13 ROM to your sdcard1 (extSDCard) and GApps (nano package from opengapps.com, ARM, 6.0)
3. I think it doesn't matter if you have already CM13 ROM or firmware (correct me if it matters), so just do factory reset, clear cache and dalvik cache
4. After that, flash CM13 and GApps at same time (you have option to choose more ZIPs, 1st ROM, 2nd GApps)
5. After that, you will have button "clear cache", click on it
6. Then Reboot your phone
That's it, I've done this on my i9300, I had already installed CM13 and GApps with CWM Recovery (with bootloop) after that I've done these steps..
Sorry for bad English..
Hope this helps...
PLEASE SHARE THIS IF IT WORKS, I REALLY WANT TO HELP PEOPLE
Nadarevicc said:
So, here is a fix, follow my steps:
1. DO NOT USE CWM Recovery OR PhilzTouch Recovery, because you will have bootloop with them OR flashing GApps will fail, so u need to use TWRP
2. Copy CM13 ROM to your sdcard1 (extSDCard) and GApps (nano package from opengapps.com, ARM, 6.0)
3. I think it doesn't matter if you have already CM13 ROM or firmware (correct me if it matters), so just do factory reset, clear cache and dalvik cache
4. After that, flash CM13 and GApps at same time (you have option to choose more ZIPs, 1st ROM, 2nd GApps)
5. After that, you will have button "clear cache", click on it
6. Then Reboot your phone
That's it, I've done this on my i9300, I had already installed CM13 and GApps with CWM Recovery (with bootloop) after that I've done these steps..
Sorry for bad English..
Hope this helps...
PLEASE SHARE THIS IF IT WORKS, I REALLY WANT TO HELP PEOPLE
Click to expand...
Click to collapse
I have done that, and it works, but I think the gapps install somehow corrupted my data, because after my phone didn't boot I backed up data just in case, and doing this it boots, but when I restore data it doesn't. do you have any ideas?
Nadarevicc said:
So, here is a fix, follow my steps:
1. DO NOT USE CWM Recovery OR PhilzTouch Recovery, because you will have bootloop with them OR flashing GApps will fail, so u need to use TWRP
2. Copy CM13 ROM to your sdcard1 (extSDCard) and GApps (nano package from opengapps.com, ARM, 6.0)
3. I think it doesn't matter if you have already CM13 ROM or firmware (correct me if it matters), so just do factory reset, clear cache and dalvik cache
4. After that, flash CM13 and GApps at same time (you have option to choose more ZIPs, 1st ROM, 2nd GApps)
5. After that, you will have button "clear cache", click on it
6. Then Reboot your phone
That's it, I've done this on my i9300, I had already installed CM13 and GApps with CWM Recovery (with bootloop) after that I've done these steps..
Sorry for bad English..
Hope this helps...
PLEASE SHARE THIS IF IT WORKS, I REALLY WANT TO HELP PEOPLE
Click to expand...
Click to collapse
Thank you so much, this worked for me. I was using CWM.
I was on CM12 stock 5.0.2 (version 12.0-YNG1TAS2I3) and i wanted to root my phone , so I unlocked bootloader and rooted the phone but now I want to flash a new Rom but I ve read in a couple of rom threads that we have to flash another 5.1nightly before flashing a ROM and I am not sure I understand this part.
I would be grateful if someone could help me with the process of flashing a 5.1 rom and gaaps for the first time on a freshly rooted phone
P.S : ( I also want to use calaukin's gaaps modified by mohit (http://forum.xda-developers.com/oneplus-one/themes-apps/gapps-modified-slim-gapps-calkulin-t3082242).
Flashing the CM12.1 nightly first ensures that your firmware is up to date. The process goes like this:
1. Download the latest CM12.1 nightly and install it with your custom recovery (no need to flash gapps, but make sure you perform a full wipe (system, data, cache, dalvik cache) first).
2. Boot the phone up once.
3. Boot back into your custom recovery and perform a full wipe.
4. Install your chosen ROM + gapps.
5. Boot phone.
6. Enjoy.
Heisenberg said:
Flashing the CM12.1 nightly first ensures that your firmware is up to date. The process goes like this:
1. Download the latest CM12.1 nightly and install it with your custom recovery (no need to flash gapps, but make sure you perform a full wipe (system, data, cache, dalvik cache) first).
2. Boot the phone up once.
3. Boot back into your custom recovery and perform a full wipe.
4. Install your chosen ROM + gapps.
5. Boot phone.
6. Enjoy.
Click to expand...
Click to collapse
Thank you so much . I followed your guide too so thank you for the support .
It is not necessary to flash nightly first, most ROM threads provide a separate firmware flashable .zip (just make sure it is flashed correctly, cause people reported issues with newer TWRP than 2.8.6.0)
davebugyi said:
It is not necessary to flash nightly first, most ROM threads provide a separate firmware flashable .zip (just make sure it is flashed correctly, cause people reported issues with newer TWRP than 2.8.6.0)
Click to expand...
Click to collapse
I used to share your opinion. But, while a lot of ROM threads do provide a firmware zip, they aren't maintained, it's usually uploaded and forgotten about. Flashing the nightly ensures that you're on the very latest firmware available.
Hi people,
I've been struggling with this for the past 2 days and I'm trying really hard not to give up
I downloaded the stable rom from the MIUI website (for Mi Note 3 aka jason), installed it successfully via MiFlash, and tried flashing Lineage after I did a factory + data + system + cache wipe. It ended with me getting the dreaded error 7.
A bit later, I realized I had to get the dev build from the MIUI website and flash it before flashing Lineage OS. So I did - I updated to MIUI 10 using the dev build, made sure it was working and tried flashing Lineage OS on top of it (after wiping the partitions I mentioned earlier, following the Lineage OS instructions).
So eventually I got it to work - sort of.
Lineage OS is booting properly, but the device freezes before it can find any wifi networks to connect to (and then reboots), and that's why I think the culprit is the modem.
So, a few questions -
1. did it happen to anyone else? I searched endlessly but came up with nothing
2. If it is a modem issue - where can I find a working one? I looked it up and found nothing
3. If it isn't a modem issue - what should I do?
If I'm doing anything wrong - please tell me. I'm flashing custom roms since 2011 and this is the first time something like this has happened to me.
Thanks for all your help!
Hi, first of all you need an unencrypted phone - Format data in TWRP (3.2.3.1), then wipe system, data, cache, dalvik. Flash the Miui 10 china stable firmware 10.0.2 or 10.0.4, then rom, gapps and reboot.
Good luck, zaqm
zaqm said:
Hi, first of all you need an unencrypted phone - Format data in TWRP (3.2.3.1), then wipe system, data, cache, dalvik. Flash the Miui 10 china stable firmware 10.0.2 or 10.0.4, then rom, gapps and reboot.
Good luck, zaqm
Click to expand...
Click to collapse
You're a true lifesaver. Worked on the first try.
Thank you!
No problems ?
Hi,
I have a little problem with the official TWRP on my HonorView10 (eu) (C432), I cannot wipe the cache (dalvik is ok).
I've flashed the stock firmware just in case but still, TWRP is saying the same thing :
Unable to wipe Cache.
Unable to wipe /cache.
Any solution ?
Use stock recovery - there is no TWRP version that works 100% on the BKL-09
Thanks for your answer, but then, how do I install a custom rom then ?
I'm getting into a bootloop every time I try to install a rom (no matter the rom).
Yedrimas said:
Thanks for your answer, but then, how do I install a custom rom then ?
I'm getting into a bootloop every time I try to install a rom (no matter the rom).
Click to expand...
Click to collapse
Via adb of course.
Check openkirin.net for guides and a few great roms that work on our EU View 10
EDIT: This is specifically for the Umidigi F1.
This is not my work, but I discovered this post in one of the hacking forums. I don't know how accurate it is yet (and given the publish date, I may be a fool), but I figured it was worth sharing.
https://forum.xda-developers.com/android/development/psa-project-treble-t3917284?nocache=1
LOL! Sorry man thats my thread I honestly didn't even realize yesterday was april fools! It's for real 100% legit .
That looks SO cool! Unfortunately I'm still struggling with TWRP as it simply cannot read anything (to be able to do step #9 on the OP). When I solve this, I'll post here as maybe it'll be good to update the steps
Well, in the end I was able to boot some SOs, but only after patching a different force encryption disable zip file (from here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389) but anyway, no custom ROM worked properly - I faced a huge amount of lag, crashes and sudden loss of input recognition. So, in the end I went back to stock Pie + Magisk to try solving the RAM issue this way. Thanks all!
Leo_Freitas said:
Well, in the end I was able to boot some SOs, but only after patching a different force encryption disable zip file (from here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389) but anyway, no custom ROM worked properly - I faced a huge amount of lag, crashes and sudden loss of input recognition. So, in the end I went back to stock Pie + Magisk to try solving the RAM issue this way. Thanks all!
Click to expand...
Click to collapse
Please tell me which ROMs did you try and what problems did you face ?
I tried the 3 mentioned in the OP:
Resurrection Remix
Descendant
Bliss ROM
But had no luck with them. Bliss seemed to be the best among them (at least I was able to boot from that haha) but after a reboot I got stuck on bootloop again (looks like the system could not see the OS anymore).
Leo_Freitas said:
I tried the 3 mentioned in the OP:
Resurrection Remix
Descendant
Bliss ROM
But had no luck with them. Bliss seemed to be the best among them (at least I was able to boot from that haha) but after a reboot I got stuck on bootloop again (looks like the system could not see the OS anymore).
Click to expand...
Click to collapse
That's a shame about the bootloop thank you for your post this helps me a lot.
Leo_Freitas said:
I tried the 3 mentioned in the OP:
Resurrection Remix
Descendant
Bliss ROM
But had no luck with them. Bliss seemed to be the best among them (at least I was able to boot from that haha) but after a reboot I got stuck on bootloop again (looks like the system could not see the OS anymore).
Click to expand...
Click to collapse
Maybe a A/B partition problem? Could maybe flash rom on both partition slots.
Leo_Freitas said:
I tried the 3 mentioned in the OP:
Resurrection Remix
Descendant
Bliss ROM
But had no luck with them. Bliss seemed to be the best among them (at least I was able to boot from that haha) but after a reboot I got stuck on bootloop again (looks like the system could not see the OS anymore).
Click to expand...
Click to collapse
A few questions:
1. How did you flash them? Did you use the SP Flash Tool?
2. After installing them, did you run the DM-Verity tool to disable encryption?
riceboyler said:
A few questions:
1. How did you flash them? Did you use the SP Flash Tool?
2. After installing them, did you run the DM-Verity tool to disable encryption?
Click to expand...
Click to collapse
hello
i bought Umidigi F1 Play for more than 1 months
and i test a lot of treble project (Havoc OS,Ressurection Remix,Blissrom,Lineage OS,Omnirom) all android 9 and it did boot up
so this my method to boot up
first :
-Unlock your Bootloader
-Download TWRP Recovery- Download Any Rom You Want to try And copy it to internal memory as .img file
-Download Magisk
-Flash TWRP Using SP Flash Tool and go to Recovery
-Make a Backup For your System if something go Wrong
-Wipe Data, Cache, System, Dalvik Cache
-go to install, press Install Image , Select your Rom File , select System Image As the partition to Flash Image
-Swipe and Wait
-Back to install and Flash Magisk
- Reboot and Enjoy
for People using gapps there is a problem with twrp is doesnt support a/b so opengapps doesnt detect if the phone is a normal or a/b device but i manage to fix a temporary opengapps to work on our device waiting for the twrp developer to fix this bug
this is the working gapps https://drive.google.com/open?id=1-Dguq8rs4k4W7eZKA2KnJxB5fKXCw2Y-
Shadow Of Leaf said:
hello
i bought Umidigi F1 Play for more than 1 months
and i test a lot of treble project (Havoc OS,Ressurection Remix,Blissrom,Lineage OS,Omnirom) all android 9 and it did boot up
so this my method to boot up
first :
-Unlock your Bootloader
-Download TWRP Recovery- Download Any Rom You Want to try And copy it to internal memory as .img file
-Download Magisk
-Flash TWRP Using SP Flash Tool and go to Recovery
-Make a Backup For your System if something go Wrong
-Wipe Data, Cache, System, Dalvik Cache
-go to install, press Install Image , Select your Rom File , select System Image As the partition to Flash Image
-Swipe and Wait
-Back to install and Flash Magisk
- Reboot and Enjoy
for People using gapps there is a problem with twrp is doesnt support a/b so opengapps doesnt detect if the phone is a normal or a/b device but i manage to fix a temporary opengapps to work on our device waiting for the twrp developer to fix this bug
this is the working gapps https://drive.google.com/open?id=1-Dguq8rs4k4W7eZKA2KnJxB5fKXCw2Y-
Click to expand...
Click to collapse
Boot and recovery only options i get in twrp