Hello there!
I’m currently the newest Nougat image (7.0.0 NBD90Z). Before flashing to this version I was on the latest marshmallow image (6.0.1 MOB31H). Initially I dirty-flashed the image, keeping the data partition intact.
However, after I tried to root the phone with SuperSU 3.78 SR1 via TWRP recovery I got into a bootloop. After restoring stock again, I backed up my data partition (nandroid backup) and did a clean flash. On the clean ROM rooting works just fine - when I tried restoring my data partition after root was up the phone got into a bootloop again.
I repeated my experiments with SuperSU 3.78 (non-SR) and 3.76 - same results.
It seems the phone gets stuck quite late into the booting process since it is detected by my PC and listed under adb (as offline, mind you).
I don't even know how to begin to analyze or debug this problem since rooting and even dirty-flashing between major versions has been working for me since Nexus 4 / KiteKat times.
Letting go of all my userdata (at least entirely) is not an option.
Any ideas or directions how I could proceed into tracking down the problem?
Hello to all
im used to modding of google nexus (all models), since I took this op3t I have only problems....basic problems, need some help!
this is my way:
unlocked bootloader
flashed latest twrp, and make a full backup
all wipe cache, dalvik, data and system
flash resurrection remix, opengapps x64 micro, supersu
reboot
whenever I try to reboot it always comes back on the screen TWRP, where i am wrong?
I tried to flash the rom via adb sideload, but on reboot tells me: os absent or not installed, but the flash result was ok.
then I noticed that putting the TWRP recovery, internal memory I went from 64 gb to 20 gb, its normal?
I kindly ask a little help or if there is a guide for this phone, it is impossible that I can not flash a custom rom on my op3t?
thanks for help or suggestions
About the storage I do not know, about the booting into TWRP I had the same problem.
How I fixed it was turn it off completely (like 10-15 seconds pushing the power button) and then start the phone. It should then boot from the ROM.
iaio72 said:
Hello to all
im used to modding of google nexus (all models), since I took this op3t I have only problems....basic problems, need some help!
this is my way:
unlocked bootloader
flashed latest twrp, and make a full backup
all wipe cache, dalvik, data and system
flash resurrection remix, opengapps x64 micro, supersu
reboot
whenever I try to reboot it always comes back on the screen TWRP, where i am wrong?
then I noticed that putting the TWRP recovery, internal memory I went from 64 gb to 20 gb, its normal?
I kindly ask a little help or if there is a guide for this phone, it is impossible that I can not flash a custom rom on my op3t?
thanks for help or suggestions
Click to expand...
Click to collapse
Follow this thread, you should be good.
https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/
Also there is a toolkit by Ahmed, could try that too.
Hey Boys and girls,
I dont know why lineage os 14. 1 dont run on my s4active. Its a I9295.
First i installed twrp 3.1.1.0 recovery with heimdall 1.4.1 on ubuntu 16.04.
Then i flashed lineage-14.1-20171017-UNOFFICIAL-jactivelte from Sd Card in recovery mode
(with the same setup and method i flashed lineage os 14.1 on I9300 and I9500 without problems)
Next i can see lineage startscreen for hours
I tested it too with twrp 3.1.0.0 and two older builds of lineage 14.1. with and without gapps, everytimes I wiped Dalvik, System, Data, Internal Storage and Cache bevore flashing,
and wipe cache&Dalvik after flashing. Always whithout errors.
Thank you everybody and sorry for my scool english
Unfortunately I can't offer help, because I suffer from the exact same problem. Tried to flash tsvetkov_vlad's CM14.1 once some time back in spring already and the behavior has not changed since.
It remains stuck showing the boot animation and does not even arrive at the screen to input the encryption password.
There are no errors in the TWRP log.
Ok, I found the solution (for me). I stumbled accross some blog post claiming that most of the time when the boot animation shows infinitely long, there is a problem with mounting some partition. For me, that was /cache, which I had previously formatted as f2fs. After changing it back to ext4 again, booting works as expected. This has never been a problem with any of the older versions of CM I used before, though.
Maybe this helps?!
Oh yes this was the solution for me too.:fingers-crossed:
I had to formate /cache in f2fs then back in ext4 for four times.
Then booting was completely normal.
Longpu you have changed my live My gratitude will haunt you forever and ever
The newest TWRP 3.2.3.-1 does not let me boot into ROM, just brings me back to TWRP again. I have to restore a backed up boot image (with 3.2.3-0) to boot normally. Even flashing TWRP 3.2.3-0 in TWRP does not bring me back.
Anyone else having experiencing this? I have attached my recovery logs.
I was on stock ...and just install los16 without problem... So i dont have problems with TWRP.
Resolved.
After dirty flashing the ROM zip/GAPPs and flashing TWRP, I was able to boot successfully. I Then just saved a new backup including the newest TWRP.
It is strange that just flashing TWRP would make the OS unbootable.
jhedfors said:
Resolved.
After dirty flashing the ROM zip/GAPPs and flashing TWRP, I was able to boot successfully. I Then just saved a new backup including the newest TWRP.
It is strange that just flashing TWRP would make the OS unbootable.
Click to expand...
Click to collapse
There is always a risk when flashing your device. One of the reasons why I prefer to flash using Linux was that Windows would have so much going on in the background that I risked the data transfer being corrupt. That said, if you're using Windows, I'd close all programs and especially disable any anti-virus running in the background. Sure, Linux may have a few things running, but I have always found it did a better job multitasking resources than Microsoft Windows with a fewer chance of data loss.
It is probably because after installing Google Apps, your /data partition gets corrupted.
So after installing Google Apps, go to TWRP > Wipe > "Format Data" & reboot.
I've the same problem & this resolves the issue for me.
For me, this did not help. I had to reflash everything from bootloader.
Funny thing is: it just has downloaded and installed an OTA update. With open bootloader.
I ran into this issue yesterday when a bad flash caused the infamous "no bootable A/B" error. After I resolved it and install TWRP I kept being rebooted back into TWRP. The 3.2.3-0 version resolved everything. I really do believe 3.2.3-1 is a bit buggy. I mean it works, but once you really start to use it more than the average user, you start to notice little things.
I too had this same issue. Eventually realized that updating TWRP by flashing zip from TWRP caused it. I had to flash stock boot partition, then follow the process for flashing TWRP as if you are flashing it for the first time (first boot into TWRP and then flash the corresponding zip). This resolved the issue.
Okay. Am currently on MIUI 11.0.3 (the latest one available for RaphaelIN)
So, the problem am facing is that, when i flash a custom rom, my phone gets rebooted to recovery and sometimes to fastboot(this happens occasionally) and i just simply cant get the rom to load.
Sometimes my phone gets into a state which resembles hardbrick (none of the buttons work, even holding the power button for 10secs doesn't) and after sometimes, usually 15 to 20 mins it restarts itself. This has happened thrice till date and all while booting to system.
The Roms i have tried-
-Pixel experience (unofficial) (android Q)
- Lineage OS 17 (unofficial)
- Havoc OS (both official and unofficial) (both pie and Q versions)
-MIUI (European rom)
I have also tried flashing the chinese, indian and global vendor (all done separately) thinking it was a vendor issue, but it also doesn't work.
Recovery is TWRP latest version, have also used orange fox recovery
Bootloader unlocking was done through the official method and the official app.
Any solutions for this problem and has anyone faced these problems or is it only me?
Astrek said:
Okay. Am currently on MIUI 11.0.3 (the latest one available for RaphaelIN)
So, the problem am facing is that, when i flash a custom rom, my phone gets rebooted to recovery and sometimes to fastboot(this happens occasionally) and i just simply cant get the rom to load.
Sometimes my phone gets into a state which resembles hardbrick (none of the buttons work, even holding the power button for 10secs doesn't) and after sometimes, usually 15 to 20 mins it restarts itself. This has happened thrice till date and all while booting to system.
The Roms i have tried-
-Pixel experience (unofficial) (android Q)
- Lineage OS 17 (unofficial)
- Havoc OS (both official and unofficial) (both pie and Q versions)
-MIUI (European rom)
I have also tried flashing the chinese, indian and global vendor (all done separately) thinking it was a vendor issue, but it also doesn't work.
Recovery is TWRP latest version, have also used orange fox recovery
Bootloader unlocking was done through the official method and the official app.
Any solutions for this problem and has anyone faced these problems or is it only me?
Click to expand...
Click to collapse
Consider this an overkill solution that always works for me if I run into issues with other methods. It will wipe everything so backup your data and apps.
Download the latest fastboot Indian MIUI ROM (for anyone else reading this download the ROM that is the same region as your phone)
Fully extract the ROM and flash it - make sure, if you use the Mi Flash Tool, that you change the flash option to 'clean all'
Boot into MIUI once, you don't need to actually go through the set-up, just let it fully load.
Boot the phone into fastboot and install TWRP - I recommend the latest mauronofrio TWRP.
After installing TWRP boot immediately into TWRP.
Format the data partition - don't skip this step.
Wipe cache and dakvik - don't wipe anything else.
In TWRP goto the mount menu and unmount the data partition then mount it again - others would suggested rebooting back into TWRP, either way works, you just need to make sure the data partition is properly mounted after formatting it.
Install the ROM of your choice - either have the ROM on a USB OTG stick, or copy it onto the phone from a PC whilst still in TWRP.
If your ROM doesn't include Google apps and services and you want Google, then install GApps - at the time of writing this Android 10 GApps is still in beta and packages bigger than nano may cause issues, so stick with pico or nano, assuming your installing an Android 10 ROM.
Boot into the ROM.
If you want Magisk, once the ROM has loaded, boot back into TWRP and flash the latest Magisk installer - it is possible to flash Magisk without booting into the ROM first and you'll probably be OK, but occasionally it can cause problems, I can't remember the details, but for the sake of 30 seconds I now boot into the ROM before flashing, just to be on the safe side.
At the time of writing this people have recently reported issues flashing GApps immediately after flashing Havoc 3.0 and recommend booting Havoc before flashing GApps. Although others say they've not had any problems. So if you choose to install Havoc you 'might' have problems if you install GApps without booting into Havoc at least once first.
I've never had problems when following this method.
You didn't format data that's why your rom doesn't boot. Follow Robbos nice guide and you are good to go.:good:
Robbo.5000 said:
Consider this an overkill solution that always works for me if I run into issues with other methods. It will wipe everything so backup your data and apps.
Download the latest fastboot Indian MIUI ROM (for anyone else reading this download the ROM that is the same region as your phone)
Fully extract the ROM and flash it - make sure, if you use the Mi Flash Tool, that you change the flash option to 'clean all'
Boot into MIUI once, you don't need to actually go through the set-up, just let it fully load.
Boot the phone into fastboot and install TWRP - I recommend the latest mauronofrio TWRP.
After installing TWRP boot immediately into TWRP.
Format the data partition - don't skip this step.
Wipe cache and dakvik - don't wipe anything else.
In TWRP goto the mount menu and unmount the data partition then mount it again - others would suggested rebooting back into TWRP, either way works, you just need to make sure the data partition is properly mounted after formatting it.
Install the ROM of your choice - either have the ROM on a USB OTG stick, or copy it onto the phone from a PC whilst still in TWRP.
If your ROM doesn't include Google apps and services and you want Google, then install GApps - at the time of writing this Android 10 GApps is still in beta and packages bigger than nano may cause issues, so stick with pico or nano, assuming your installing an Android 10 ROM.
Boot into the ROM.
If you want Magisk, once the ROM has loaded, boot back into TWRP and flash the latest Magisk installer - it is possible to flash Magisk without booting into the ROM first and you'll probably be OK, but occasionally it can cause problems, I can't remember the details, but for the sake of 30 seconds I now boot into the ROM before flashing, just to be on the safe side.
At the time of writing this people have recently reported issues flashing GApps immediately after flashing Havoc 3.0 and recommend booting Havoc before flashing GApps. Although others say they've not had any problems. So if you choose to install Havoc you 'might' have problems if you install GApps without booting into Havoc at least once first.
I've never had problems when following this method.
Click to expand...
Click to collapse
Thnx for the guide. i will do this within a day or two and update you if it worked or not.
Kollachi said:
You didn't format data that's why your rom doesn't boot. Follow Robbos nice guide and you are good to go.:good:
Click to expand...
Click to collapse
I did format the data partition coz that's one thing I and my friends always do when flashing new rom. I don't exactly remember but i think, the pseudo hardbrick thingy started after i formatted the system, data, cache & internal storage.
I will follow Robbos guide adn keep you guys updated on what happened.
Astrek said:
I did format the data partition coz that's one thing I and my friends always do when flashing new rom. I don't exactly remember but i think, the pseudo hardbrick thingy started after i formatted the system, data, cache & internal storage.
I will follow Robbos guide adn keep you guys updated on what happened.
Click to expand...
Click to collapse
Format data = (you will need to type in "yes")
Note: Format data or wipe data isn't the same thing.
Robbo.5000 said:
Consider this an overkill solution that always works for me if I run into issues with other methods. It will wipe everything so backup your data and apps.
Download the latest fastboot Indian MIUI ROM (for anyone else reading this download the ROM that is the same region as your phone)
Fully extract the ROM and flash it - make sure, if you use the Mi Flash Tool, that you change the flash option to 'clean all'
Boot into MIUI once, you don't need to actually go through the set-up, just let it fully load.
Boot the phone into fastboot and install TWRP - I recommend the latest mauronofrio TWRP.
After installing TWRP boot immediately into TWRP.
Format the data partition - don't skip this step.
Wipe cache and dakvik - don't wipe anything else.
In TWRP goto the mount menu and unmount the data partition then mount it again - others would suggested rebooting back into TWRP, either way works, you just need to make sure the data partition is properly mounted after formatting it.
Install the ROM of your choice - either have the ROM on a USB OTG stick, or copy it onto the phone from a PC whilst still in TWRP.
If your ROM doesn't include Google apps and services and you want Google, then install GApps - at the time of writing this Android 10 GApps is still in beta and packages bigger than nano may cause issues, so stick with pico or nano, assuming your installing an Android 10 ROM.
Boot into the ROM.
If you want Magisk, once the ROM has loaded, boot back into TWRP and flash the latest Magisk installer - it is possible to flash Magisk without booting into the ROM first and you'll probably be OK, but occasionally it can cause problems, I can't remember the details, but for the sake of 30 seconds I now boot into the ROM before flashing, just to be on the safe side.
At the time of writing this people have recently reported issues flashing GApps immediately after flashing Havoc 3.0 and recommend booting Havoc before flashing GApps. Although others say they've not had any problems. So if you choose to install Havoc you 'might' have problems if you install GApps without booting into Havoc at least once first.
I've never had problems when following this method.
Click to expand...
Click to collapse
Ohhh *****...!!!! It ****ing worked!!!! Though i made some mistakes like clean all and lock in first step, but was able to unlock bootloader almost instantly, no idea why but i can almost instantly unlock certain mi phone's bootloader instantly. But a lot of thanx for taking your time and writing this up... You really saved me from being stuck in MIUI forever!
A lot of thnx.... and also happy new year... 1st day of 2020 went quite well for me all thnx to you and i hope yours goes well too.!
Robbo.5000 said:
Consider this an overkill solution that always works for me if I run into issues with other methods. It will wipe everything so backup your data and apps.
Download the latest fastboot Indian MIUI ROM (for anyone else reading this download the ROM that is the same region as your phone)
Fully extract the ROM and flash it - make sure, if you use the Mi Flash Tool, that you change the flash option to 'clean all'
Boot into MIUI once, you don't need to actually go through the set-up, just let it fully load.
Boot the phone into fastboot and install TWRP - I recommend the latest mauronofrio TWRP.
After installing TWRP boot immediately into TWRP.
Format the data partition - don't skip this step.
Wipe cache and dakvik - don't wipe anything else.
In TWRP goto the mount menu and unmount the data partition then mount it again - others would suggested rebooting back into TWRP, either way works, you just need to make sure the data partition is properly mounted after formatting it.
Install the ROM of your choice - either have the ROM on a USB OTG stick, or copy it onto the phone from a PC whilst still in TWRP.
If your ROM doesn't include Google apps and services and you want Google, then install GApps - at the time of writing this Android 10 GApps is still in beta and packages bigger than nano may cause issues, so stick with pico or nano, assuming your installing an Android 10 ROM.
Boot into the ROM.
If you want Magisk, once the ROM has loaded, boot back into TWRP and flash the latest Magisk installer - it is possible to flash Magisk without booting into the ROM first and you'll probably be OK, but occasionally it can cause problems, I can't remember the details, but for the sake of 30 seconds I now boot into the ROM before flashing, just to be on the safe side.
At the time of writing this people have recently reported issues flashing GApps immediately after flashing Havoc 3.0 and recommend booting Havoc before flashing GApps. Although others say they've not had any problems. So if you choose to install Havoc you 'might' have problems if you install GApps without booting into Havoc at least once first.
I've never had problems when following this method.
Click to expand...
Click to collapse
thanks for help
but no work for me
after flash rom and reboot booting to twrp auto..
Kollachi said:
Format data = (you will need to type in "yes")
Note: Format data or wipe data isn't the same thing.
Click to expand...
Click to collapse
many times the tiniest msg has the greatest significance. thanks mate!!!
Guys i need your help,, i flashed my phones custom Rom tecno 7cs using sp flashing tool.
That worked and it showed the tick icon on my pc.
The problem is that it does nothing to my phone because the software issues are still there
my phone keeps restarting itself almost all the time and sometimes won't even boot it takes longer to boot,,, apps keep on crushing and many more.AM tired am going to break it and throw it if i don't get solutions asap!
So the flashing process only wiped data on the phone nothing else whatsoever.
tecno 7cs p121 Bi safaricom ke 20151111