Hello everybody!
Im trying to ditch the spywareOS that came with my phone, but i seem to be unable to find a replacement.
The only thing that actually boots after install is a lineageOS 17.zip installation, but thats incredibly unstable and has deal-breaking bugs.
So im trying desperately to get treble roms to work and i belive ive tried "them all" already, none of them actually boots up or shows the custom boot animation, its in a loop, the redmi logo shows up, then screen goes black (reboot?) and then the redmi logo shows up again.
Ive been trying both 32bit and 64bit roms, both Aonly and A/B varations, with no difference what so ever, so i figure i must be doing something wrong, missing a step somewhere..
Ive been following THIS TUTORIAL mostly, but the Permissiver_v4.zip install always failed with a error (cant remember exactly) but i found a version 5 witch does install.
I did downgrade MIUI to 10.2.5 before starting the procedure and i did find the corresponding boot-image witch im using, along with the vbmeta.img file listed in the tutorial, so i do belive i have done everything by the book, but still no cigar...
Ive tried (gsi treble roms): Descendant X, Quack Phh-Treble, Havoc-OS-3.5, LineageOS 17.x aswell as googles own GSI.
I also made sure to vacuum the forum topic for each of the ROM´s, in case there´s a hint or suggestion that i might find useful, but theyre all pretty much the same:
Wipe dalvik, System, Data and cache, install rom, reboot.
Some have suggested to clear dalvik and cache after install (sometimes with a reboot in between) and some have hinted that the magisk is mandatory in order to fix boot issues, but still no go..
So, does anybody have any suggestions?
Related
So I did everythign I normally do with a new device!
1)I unlocked it through Fastboot
2) I downloaded the latest TWRP recovery image for that device and flashed it with Fastboot
3) I rebooted the device into recovery to check if everything is ok.
4) Proceeded to download Cyanogenmod for Nexus 6p (Angler) and OpenGapps ARM64 for 6.0 stock package and put them on the phone
5) Opened the Zips from the phone to check that none are corrupted
6) Wiped Everything on the phone via Advanced Wipe incl System, Data, Cache etc,
7) Flashed Cyanogenmod Zip first after that the Gapps package
8) Rebooted to System and waited for the phone to finish its first boot
This is where my problems begin. No matter what I do and how much I toubleshoot the first boot never seems to finish. I have played with devices long before I got the 6p and know that the first boot taked a long time but not this long!
I checked if it was the recovery, or the CM zip or Gapps but no matter how many scenarios I try and rule out Im stuck at the CM boot logo (Which seems pretty laggy). I even tried without gapps.
I searched online and cant find ppl with a similar problem. There are people who cant get past the Google logo but I get past that with no problem. Its just that I cant boot the OS.
I even checked a few guides to see if I missed a step when I was doing it on my own but no! I have done everything absolutely correctly and cant seem to find an issue this time (usually finding issues with Android and repairing them is my specialty ).
I can not think of ANYTHING that ive missed here. I just cant seem to find the problem. The hardware boots Stock/Factory imaged perfectly so its working fine. Where am doing wrong?
bogomil4e said:
So I did everythign I normally do with a new device!
1)I unlocked it through Fastboot
2) I downloaded the latest TWRP recovery image for that device and flashed it with Fastboot
3) I rebooted the device into recovery to check if everything is ok.
4) Proceeded to download Cyanogenmod for Nexus 6p (Angler) and OpenGapps ARM64 for 6.0 stock package and put them on the phone
5) Opened the Zips from the phone to check that none are corrupted
6) Wiped Everything on the phone via Advanced Wipe incl System, Data, Cache etc,
7) Flashed Cyanogenmod Zip first after that the Gapps package
8) Rebooted to System and waited for the phone to finish its first boot
This is where my problems begin. No matter what I do and how much I toubleshoot the first boot never seems to finish. I have played with devices long before I got the 6p and know that the first boot taked a long time but not this long!
I checked if it was the recovery, or the CM zip or Gapps but no matter how many scenarios I try and rule out Im stuck at the CM boot logo (Which seems pretty laggy). I even tried without gapps.
I searched online and cant find ppl with a similar problem. There are people who cant get past the Google logo but I get past that with no problem. Its just that I cant boot the OS.
I even checked a few guides to see if I missed a step when I was doing it on my own but no! I have done everything absolutely correctly and cant seem to find an issue this time (usually finding issues with Android and repairing them is my specialty ).
I can not think of ANYTHING that ive missed here. I just cant seem to find the problem. The hardware boots Stock/Factory imaged perfectly so its working fine. Where am doing wrong?
Click to expand...
Click to collapse
I'm not sure but on an old HTC phone I had the same issue which was caused by a mismatch between the rom version and phones firmware. I'm not sure how it works on the nexus hope someone here can help
Try different GAPPS ?
Sent from my Nexus 6P using Tapatalk
Have you tried flashing a vendor zip yet? Sounds like not booting cause missing binaries.
https://www.androidfilehost.com/?w=files&flid=43551
If you're able to get to twrp, wipe everything, flash cyanogen reboot, and then flash a different gappd
Sent from my Nexus 6P using Tapatalk
You must format data in TWRP or it won't boot.
Hi you there,
I start this thread because I´m having some issues installing 8.0 and 8.1 Oreo Roms, every of them have the same problems when I try to install them in my device (REDMI 3X). Actually, I have install and running Resurrection Remix Nougat + Gapps Micro, and it works fine.
When I try to install some Oreo Rom, I have these 2 possible options:
1 - I install rom + gapps (no matter which one, cause I tried each one): phone restarts and stucks at logo and after maybe 30 minutes I must restart it manually and reinstall a nougat rom. It never starts, and it is f...ng annoying.
2 - I install rom, afterwards, I restart and it works fine, but I have no gapps. The I boot into recovery and after gapps are installed I restart the phone, then gapps never work.
Please, I just get 2 times an oreo rom working, but now they never work, I don´t know whta to do. I also tried different recoveries, flashing them from PC, installing them from .img with TWRP, nothing seems to work. As I said: F...NG ANNOYING. I need heeeeeeeeeeeeeeeeelp
I think I am not the only one with this problem, if anyone can help I will appreciate that.
Thansk in advance.
First of all, this should be in the Q&A section. Secondly, I can help you. I'm sure that you downloaded the gapps from the cloudkenzo something, right? Yeah those gapps do not have any issues, instead they make an issue. After flashing your rom and then these gapps file, the system partition normally unmounts. But usually when you boot into the ROM, the partition should re-mount. These unofficial gapps causes some issues with that. A simple solution- Just mount system in twrp, now reboot to system and you should be fine. I faced the same issue and this is my solution.
alopez_666 said:
Hi you there,
I start this thread because I´m having some issues installing 8.0 and 8.1 Oreo Roms, every of them have the same problems when I try to install them in my device (REDMI 3X). Actually, I have install and running Resurrection Remix Nougat + Gapps Micro, and it works fine.
When I try to install some Oreo Rom, I have these 2 possible options:
1 - I install rom + gapps (no matter which one, cause I tried each one): phone restarts and stucks at logo and after maybe 30 minutes I must restart it manually and reinstall a nougat rom. It never starts, and it is f...ng annoying.
2 - I install rom, afterwards, I restart and it works fine, but I have no gapps. The I boot into recovery and after gapps are installed I restart the phone, then gapps never work.
Please, I just get 2 times an oreo rom working, but now they never work, I don´t know whta to do. I also tried different recoveries, flashing them from PC, installing them from .img with TWRP, nothing seems to work. As I said: F...NG ANNOYING. I need heeeeeeeeeeeeeeeeelp
I think I am not the only one with this problem, if anyone can help I will appreciate that.
Thansk in advance.
Click to expand...
Click to collapse
Make sure using the latest twrp.
If u already have the latest twrp then the problem is in gapps, use gapps for oreo 8.1, maybe there is posted in ur rom thread
F4nno said:
Make sure using the latest twrp.
If u already have the latest twrp then the problem is in gapps, use gapps for oreo 8.1, maybe there is posted in ur rom thread
Click to expand...
Click to collapse
I already tried, it did not work, I have installed last gapps 8.1, last twrp, last everything and it never works, it keeps stucking again and again.
same ****ty problem with my 3s 2gb .. doesnt matter which oreo 8.1 rom i flash.. tried almost 4 oreo 8.1 roms.. all couldnt boot.. and if by chance it boots then cant add google account..
yet to try that 'Mount' thing solution suggested by Williams
You ask in wrong place stupid!
Ask in Q&A section stupid!
This section jus for downloading rom and kernel stupid!
I face the same issue with a Redmi 3 S (global version) with 3 GB RAM. Nougat ROM's are fine but all Oreo ROM's which I tried (most recent builds of PixelExperience, crDroid, Atomic-OS) show these boot loops. This is all with the latest TWRP installed (also tried custom builds), cleaned properly my device and was using the linked Oreo GAPPS. I usually flash in one instance 1) ROM, 2) GAPPS and 3) Magisk.
The only time I had a working Oreo ROM was after several tries with PixelExperience where on my last try I booted into safe mode and it somehow worked after that.
AidANiem said:
You ask in wrong place stupid!
Ask in Q&A section stupid!
This section jus for downloading rom and kernel stupid!
Click to expand...
Click to collapse
go **** your mother, she likes it
william.johhn7! said:
First of all, this should be in the Q&A section. Secondly, I can help you. I'm sure that you downloaded the gapps from the cloudkenzo something, right? Yeah those gapps do not have any issues, instead they make an issue. After flashing your rom and then these gapps file, the system partition normally unmounts. But usually when you boot into the ROM, the partition should re-mount. These unofficial gapps causes some issues with that. A simple solution- Just mount system in twrp, now reboot to system and you should be fine. I faced the same issue and this is my solution.
Click to expand...
Click to collapse
Thanks, it worked for me:
1 - full wipe and format
2 - install rom
3 - install gapps
4 - mount system
5 - reboot system
Hi guys,
so I am running into a strange issue: I can't flash any ROMs in recovery anymore.
I switched to Pixel Experience Q from xiaomi.eu's MIUI ROM ~1 week ago without wiping internal storage, so I ended up not being able to use TWRP as I was faced with a password prompt that accepted none of my passwords (current, previous or default_password, etc.). So when an update for PE came I thought "okay let's get this over with now" and did a complete wipe including /data/media from OrangeFox recovery - so far so good.
Now I transferred back the new ROM zip and wanted to proceed flashing it.
Result: Error 7 Failed to update system image (E1001)
Confused by this I went back to the previous version's zip, but the same error comes up.
Even more confused I downloaded all kinds of ROMs and every single one comes up with this error.
I tried
another full wipe
mounting/unmounting system before flashing
MIUI, Android 10, Android 9 ROMs
Different versions of TWRP and OFR
Even different firmware packages
Removed assert and abort lines in the updater-script (which results in skipping the flashing of the system image and then failing at vendor)
Flashing by adb sideload
So the only thing getting me back to a working phone is flashing a fastboot ROM. That works.
Even after doing that, flashing back TWRP/OrangeFox, wiping and flashing a ROM the same error comes up again. I also checked the MD5 hash for my files. They are fine.
I am at a loss of ideas at this point and no solution I found helped. I hope you guys can help me. Thanks in advance. :-/
Well, scratch that, I guess.
After hours of troubleshooting somehow it's working again now.
So for anyone who gets this issue:
Flash a fastboot ROM and...go to sleep and try in the morning.
I'm facing the same problem now.. I think after trying many times its a flash problem, because when I flash over fastboot sometimes stick on 5/7 and others 3/7 etc.. well its a xiaomi is something to expect.
Format Data partition, not just wipe, this should fix those kind of issues.
This.
After more xiaomi devices and more flashing I can definitely say this is the fix.
This.
After more xiaomi devices and more flashing I can definitely say this is the fix.
Try transferring the ROM using a USB 3.0 port. Worked for me...
I am facing the same problem. Can you help me?
Hi,
I used Lineage OS 17.1 Lavender on my Xiaomi Redmi Note 7. I used their recovery to install the ROM and open gapps. Recently I downloaded the Brave Browser and I wanted to enable rewards. I than googled, that Brave doesn't allow rewards on rooted phones. I decided to wipe the entire phone, since I don't use the root functionality and to re-flash Lineage OS 17.1. I factory reseted the phone and wiped everything, just like I did, when I installed Lineage for the first time. I clicked on "Yes" when prompted that the ISO couldn't be verified, and waited for the flash. After a while I was "greeted" with Updater process ended with Error 7. I did some research and found out that it is something to do with the updater file verification and that I should try and delete some lines. I did that, but the error persisted. I than decided to try another ROM. I used Pixel Experience since it was working on my device before. Unfortunatly I had no luck. Same error message. I than tried to flash TWRP with fastboot, which worked. Wiped my device, just like they say it in all the guides (Dalvik, Data, Cache) and tried to flash Lineage (still no luck), than PixelExperience (still no luck) and Magisk worked. After I flashed Magisk I tried Lineage and Pixel once again, but still the same error.
If you know, how to fix that error I will be so glad. Is it possible that my device is bricked and beyond recovery? Thank you in advance.
update your tvvrp
Which firmware do you have installed? Use stable to maximum compatibility, on some ROMs if you have latest you gonna get that error. Also, use the latest TWRP or Orange Fox.
As Tatoh said, this error occurs when you have old firmware flashed on your RN7, some roms require specific version but usually flashing latest stable will give you best compatibility, here you have xda links to latest xiaomi firmware files: https://forum.xda-developers.com/redmi-note-7/development/firmware-xiaomi-redmi-note-7-t3925871
Hello everybody.
Twice I tried to install LineageOS 18 on my 6T, equipped with latest OxygenOS/Android 11 version, without any success despite having followed several tutorials on Youtube and on websites.
Two days ago I unlocked the bootloader, I restarted the phone from the PC in Fastboot mode and I tried to install the TWRP recovery, always getting an error and when it seemed that I had succeeded the phone restarted showing the message "Qualcomm Crashdump" and the phone was dead.
Fortunately, a Wipe Data from the Recovery allowed me to get the 6T working again.
Last night I tried again by installing the LineageOS recovery first, I restarted the phone and I realized that it was in bootloop.
At this point I could only restart it in Recovery or Fastboot mode, without being able to start the 6T correctly; not even a wipe data helped me.
At that point I used the MSM download Tool, with which I was able to reinstall OxygenOS v9.xx and restart the 6T, then updating it to OxygenOS 11.
The drawback now is that when I turn on the phone it takes over a minute to boot (the two dots around the OnePlus symbol make a good 37 laps, after which the phone starts up and works perfectly).
How can I fix this slow boot problem?
And why has it become so difficult to install a custom ROM on the 6T? It occurs to me that OnePlus has deliberately complicated things to hinder modding.
dequadim said:
Hello everybody.
Twice I tried to install LineageOS 18 on my 6T, equipped with latest OxygenOS/Android 11 version, without any success despite having followed several tutorials on Youtube and on websites.
Two days ago I unlocked the bootloader, I restarted the phone from the PC in Fastboot mode and I tried to install the TWRP recovery, always getting an error and when it seemed that I had succeeded the phone restarted showing the message "Qualcomm Crashdump" and the phone was dead.
Fortunately, a Wipe Data from the Recovery allowed me to get the 6T working again.
Last night I tried again by installing the LineageOS recovery first, I restarted the phone and I realized that it was in bootloop.
At this point I could only restart it in Recovery or Fastboot mode, without being able to start the 6T correctly; not even a wipe data helped me.
At that point I used the MSM download Tool, with which I was able to reinstall OxygenOS v9.xx and restart the 6T, then updating it to OxygenOS 11.
The drawback now is that when I turn on the phone it takes over a minute to boot (the two dots around the OnePlus symbol make a good 37 laps, after which the phone starts up and works perfectly).
How can I fix this slow boot problem?
And why has it become so difficult to install a custom ROM on the 6T? It occurs to me that OnePlus has deliberately complicated things to hinder modding.
Click to expand...
Click to collapse
Did you get twrp installed? Wipe data by typing yes after flashing?
dequadim said:
Hello everybody.
Twice I tried to install LineageOS 18 on my 6T, equipped with latest OxygenOS/Android 11 version, without any success despite having followed several tutorials on Youtube and on websites.
Two days ago I unlocked the bootloader, I restarted the phone from the PC in Fastboot mode and I tried to install the TWRP recovery, always getting an error and when it seemed that I had succeeded the phone restarted showing the message "Qualcomm Crashdump" and the phone was dead.
Fortunately, a Wipe Data from the Recovery allowed me to get the 6T working again.
Last night I tried again by installing the LineageOS recovery first, I restarted the phone and I realized that it was in bootloop.
At this point I could only restart it in Recovery or Fastboot mode, without being able to start the 6T correctly; not even a wipe data helped me.
At that point I used the MSM download Tool, with which I was able to reinstall OxygenOS v9.xx and restart the 6T, then updating it to OxygenOS 11.
The drawback now is that when I turn on the phone it takes over a minute to boot (the two dots around the OnePlus symbol make a good 37 laps, after which the phone starts up and works perfectly).
How can I fix this slow boot problem?
And why has it become so difficult to install a custom ROM on the 6T? It occurs to me that OnePlus has deliberately complicated things to hinder modding.
Click to expand...
Click to collapse
You can follow this. If you want to install lineage os and want Google service make sure follow the "non gapp version" under installation method.
Havoc Flashing Notes for OnePlus 6 /6T from OOS 11 [Using TWRP Recovery]
1. Clean Flash : 2. Dirty Flash 3. Update oos base 1. Clean Flash : 🔊 Make sure you've backed up whatever data you want to keep to somewhere that's not on your phone; we're going to format the data partition and you're going to lose everything from internal storage. Basic requirements ○...
telegra.ph
Thanks for replies.
I must add this point: my 6T has OxygenOS v11.1.1.1; maybe this the reason of the problem? Maybe OnePlus did something that screws any modding attempt?
I simply followed the instructions found on YouTube, in the LineageOS' Fajita page and installed TWRP, but my 6T went in "Qualcomm Crashdump" and TWRP was not working → phone bricked.
Then I've tried installing, in the same way via ADB and Fastoot commands the Lineage Recovery, that has worked but when I tried to boot system, keeping OxygenOS, the phone went in bootloop.
So where is the error/fault?
Please, help me with a step-by-step tutorial that lead me to successfully install TWRP and LineageOS on my 6T.
dequadim said:
Thanks for replies.
I must add this point: my 6T has OxygenOS v11.1.1.1; maybe this the reason of the problem? Maybe OnePlus did something that screws any modding attempt?
I simply followed the instructions found on YouTube, in the LineageOS' Fajita page and installed TWRP, but my 6T went in "Qualcomm Crashdump" and TWRP was not working → phone bricked.
Then I've tried installing, in the same way via ADB and Fastoot commands the Lineage Recovery, that has worked but when I tried to boot system, keeping OxygenOS, the phone went in bootloop.
So where is the error/fault?
Please, help me with a step-by-step tutorial that lead me to successfully install TWRP and LineageOS on my
Click to expand...
Click to collapse
OnePlus definitely didn't do anything to make it harder. You need to fastboot boot twrp.img then flash the twrp installer zip. I'll attach both In next post. Reboot to recovery. Then install OOS, twrp installer, reboot to recovery. Install oos again, twrp installer again, reboot to recovery. Now install lineage, twrp installer, reboot to recovery. Install lineage again, twrp installer again, reboot to recovery. Factory reset and wipe data by typing yes. Boot to system
The img is for fastboot boot
The zip is for installing in twrp
Thanks for your reply.
I'm still wondering how to speed up the boot.
dequadim said:
Thanks for your reply.
I'm still wondering how to speed up the boot.
Click to expand...
Click to collapse
If everything is installed correctly it won't take long to boot
Brettroth said:
If everything is installed correctly it won't take long to boot
Click to expand...
Click to collapse
There is clearly something wrong, as my 6T's boot is slow.
Furthermore, the Recovery of the previous message is the one I downloaded three days ago and that made me go to the 6T in Qualcomm Crashdump.
I repeat my request: where can I find a safe and updated guide that explains how to install LineageOS without risk?
If you can't fastboot boot into that twrp on a11 without crash dumping there is something really wrong
If you can't fastboot boot into that twrp on a11 without crash dumping there is something really
dequadim said:
There is clearly something wrong, as my 6T's boot is slow.
Furthermore, the Recovery of the previous message is the one I downloaded three days ago and that made me go to the 6T in Qualcomm Crashdump.
I repeat my request: where can I find a safe and updated guide that explains how to install LineageOS without risk?
Click to expand...
Click to collapse
You sure you didn't try 3.6.0_9?
Clearing your cache might help with current boot. But once you install a new os everything will run smooth like it should
Thank you for the advice.
1) I've downloaded "twrp-3.6.0_9-0-fajita.img" and tried to install it several times, getting errors and then bricking my phone.
2) I have already cleared the cache several times from Recovery, without anything having changed; the two white dots on the boot screen continue to rotate 37 times around the red dot before the phone starts up and then works perfectly.
It occurred to me that the MSM Download Tool program uses a decrypted image of the original firmware; could this possibly be the cause of the long boot?
dequadim said:
Thank you for the advice.
1) I've downloaded "twrp-3.6.0_9-0-fajita.img" and tried to install it several times, getting errors and then bricking my phone.
2) I have already cleared the cache several times from Recovery, without anything having changed; the two white dots on the boot screen continue to rotate 37 times around the red dot before the phone starts up and then works perfectly.
It occurred to me that the MSM Download Tool program uses a decrypted image of the original firmware; could this possibly be the cause of the long boot?
Click to expand...
Click to collapse
That twrp version always will crash dump on a11. Use the one I sent
I followed these steps:
after having managed to make MSM Download Tool detect the phone in EDL mode, I proceeded by reinstalling OOS v9.0.13, after which I reconfigured the phone and restored the apps backup stored in my Google account.
Later, I don't remember the details well, I received the update notification for OOS v10 and later for OOs v11.1.2.2.
I don't remember exactly where the boot started to stretch, however this is more or less the process I followed to bring my 6T back to life.
Brettroth said:
That twrp version always will crash dump on a11. Use the one I sent
Click to expand...
Click to collapse
Are you sure that this TWRP will work without problems?
I've tried also with Lineage Recovery for Fajita, resulting with the 6T in bootloop :-(
dequadim said:
Are you sure that this TWRP will work without problems?
I've tried also with Lineage Recovery for Fajita, resulting with the 6T in bootloop :-(
Click to expand...
Click to collapse
I promise it works. I do t know what happened with your previous updating and msm tool but something sounds messed up. Just get twrp running and ease all your problems. Clean flashing and getting everything fresh
Brettroth said:
I promise it works. I do t know what happened with your previous updating and msm tool but something sounds messed up. Just get twrp running and ease all your problems. Clean flashing and getting everything fresh
Click to expand...
Click to collapse
Keep your finger crossed...
Another question: assuming I can install TWRP and make it working, LineageOS image must be copied in the 6T's internal SD and proceeding to install from TWRP?
dequadim said:
Another question: assuming I can install TWRP and make it working, LineageOS image must be copied in the 6T's internal SD and proceeding to install from TWRP?
Click to expand...
Click to collapse
Or you could use USB OTG. Or a PC and use adb sideload