I know it was not a twrp error, but i used it to gain your attention. Sorry but i am in trouble.
Recently, I had the stock version of k3 with kingroot and twrp. I tried to change the rom to Resurrection Remix v5.8.0v2. I took the nandroid backup.
I had wiped the caches and data.
And after i tried to install the zip, it showed me, partitioning system or something like that.
And after some time it showed me unable to mount system.
Flash was failed and by mistake i wiped my system, and then i tried to restore my android and every time it said unable to mount system.
During the reboot it said no os detected.
My phone was taken to the mobile repairing shop, and they installled the official​ marshmallow rom in my device.
Now, i have marshmallow and now I don't have root access, and now when i try to flash super su with the help of twrp into my device. Twrp show me unpartitioned memory. Do you want to modify.
My questions are :—
1.What caused my phone into that problem of no os detected.
2. What to do if it happen again.
3. Now what should I do, as the twrp says to modify the system.
Please help, first time tried to flash custom rom and
already told you the pain.
Related
So I recently tried to upgrade to S433 rom. I had taken a Nanadroid backup but my recovery was old cwm so I flashed TWRP 2.8 and now TWRP doesn't show my backup but even although old CWM was able to restore the backup it never booted it just went into boot loop.
So I tried flashing a new ROM through TWRP but it's always getting zip verification failed although I think that those are proper signed Roms. Ive tried two Roms and both are giving the same error.
Nothing happens when I use SP flash so I am assuming that there's some problem with drivers on Win 7.
So what should or could I do now?
I can boot into the TWRP recovery.
If I turn off zip verification, it just goes into TWRP instantly.
Flash SP is your best bet..Did SP tools see your phone? If not then try searching for drivers
Try Androium rom flashed with 3.0.2 twrp. Format data, cache, dalvik, system before flashing. Never gave me a 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.
So, I recently installed TWRP on my SM-T813. I then flashed LineageOS 14.1 successfully, but didn't like it, so I reflashed stock ROM. Everything was working fine, until I tried to install SuperSU on my stock ROM.
Now, my tablet is stuck into booting recovery mode, and cannot boot into the ROM (although Download Mode is still usable, more on that later). Upon trying to reflash the backup again, and attempting to reboot, TWRP states "No OS installed!" SO I tried reflashing the LineageOS ROM, same thing. Upon trying to restore a firmware with Odin, I get an error saying "SW REV CHECK FAIL aboot Fused 2 Binary 1." After finding no answers, I delved into my SD card and found that I had flashed the WRONG version of SuperSU, although it had been cleared when reformatting with TWRP. I then tried using the CORRECT SuperSU, and I am still stuck in recovery bootloop.
Can someone analyze what's going on and see what the problem is?
(SM-T813 - USA)
Lucarje said:
So, I recently installed TWRP on my SM-T813. I then flashed LineageOS 14.1 successfully, but didn't like it, so I reflashed stock ROM. Everything was working fine, until I tried to install SuperSU on my stock ROM.
Now, my tablet is stuck into booting recovery mode, and cannot boot into the ROM (although Download Mode is still usable, more on that later). Upon trying to reflash the backup again, and attempting to reboot, TWRP states "No OS installed!" SO I tried reflashing the LineageOS ROM, same thing. Upon trying to restore a firmware with Odin, I get an error saying "SW REV CHECK FAIL aboot Fused 2 Binary 1." After finding no answers, I delved into my SD card and found that I had flashed the WRONG version of SuperSU, although it had been cleared when reformatting with TWRP. I then tried using the CORRECT SuperSU, and I am still stuck in recovery bootloop.
Can someone analyze what's going on and see what the problem is?
(SM-T813 - USA)
Click to expand...
Click to collapse
This has been posted a million times all over the forum. A quick search here or Google would have revealed the answer
You need to flash a revision 2 firmware. So that would be something like t813xxu2 in the firmware build number.
Sorry for being late with reply. Your advice helped me fix my tablet! Thanks so much!
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.
Hi.
I have a Zenfone 5 (ZE620KL, X00QD). It is a brand phone (Vivo Brand, which is a mobile operator in Brazil).
I'm trying to flash custom roms but it seems they simply don't work.
I already bootloaded and rooted the phone. It has TWRP 3.3.1-0 installed now. When I rooted, I used Magisk with the original stock rom boot.img from Vivo Brand firmware to generate the rooted boot.img. It worked as intended and the phone was rooted.
I tried to install many roms. All of them, I wiped the folders (Dalvik, cache, Data, vendor, system) and even formated data (and rebooted the phone after each procedure) before trying to install the roms.
I also downloaded the roms from XDA respective topics. The list of each rom I tried and the errors are:
CRDroid and dotOS: do install, but enter in bootloop. I tried to wait for a few boots. I entered twrp again and wiped cache, data, dalvik and vendor). But still bootloop.
HavocOS and Pixel Experience: installed and no bootloop, but it doesn't quit from the initial screen loading (I waited for 2 hours). I also tried to reboot and nothing. Then, I wiped the folders again and nothing.
NezukoOS: close one. It installs and even gets to a screen where it asks for a password. When I enter the password it says the password is correct, but decryption uncessful. It asks to erase data. I did it (tried just wipe cache, data, Dalvik, but not the system folder this time! I also tried to format data). But no good ending. It says again about the decryption problem.
LineageOS 16.1 and Viper OS: they give me an "error installing zip file" message in TWRP. This is odd, because the zip file is not corrupted. I can open and extract it on my PC. But, I also downloaded again and tried a second time and nothing.
Is it because the phone is brand vivo? Or any sugestions?
I also tried the above procedures with adb sideload. The problems were the same.
Sorry if the term "brand vivo" is incorrect or about my English.