So Phone model : a500F
Previous version 5.0.2
Rooted
TWRP 3.0.0.1
I tried flashing many roms like Aryamod, Ressurection remix ( both N & M ) and Lineage OS
The only on that flashed successfully is Lineage but when I try to reboot it restarts back to TWRP
The other roms doesn't flash as it gives Error 7
Any ideas ?
Try v 3.0.2.1. Also go to specific thread and read this has a solution and I think there is no need to create a separate thread for that. There is even a zip that you can flash to get out of the twrp loop as I would call it.
Related
Hello,
hopefully someone could help me solve my issue.
i've installed the latest nightly of cm 12.1 today overwriting my previous installation of cm11 with a build from january.
the recovery i used so far was twrp.
after upgrading cm to 12.1 i can no longer access the recovery. the phone shows a black screen and reboots when i press the power button.
i've tried reflashing current and older (2.7) versions of twrp with odin but with no success.
NiteFlame1003 said:
Hello,
hopefully someone could help me solve my issue.
i've installed the latest nightly of cm 12.1 today overwriting my previous installation of cm11 with a build from january.
the recovery i used so far was twrp.
after upgrading cm to 12.1 i can no longer access the recovery. the phone shows a black screen and reboots when i press the power button.
i've tried reflashing current and older (2.7) versions of twrp with odin but with no success.
Click to expand...
Click to collapse
You should have flashed official lollipop first, to get the latest bootloader. And you should begin there. And then flash twrp for your rom and cm12.1 using twrp.
Use a cm12.1 rom from development forums instead. E.g temaseks.
so just to make it clear for the dummy kind of user which i seem to be the necessary steps are:
1. getting a stock lp rom and flash this
2. flashing a custom recovery
3. flashing custom rom (e.g. temaseks or standard cm12.1)
Does the Phone have to be rooted for these steps? It looks like it has lost its root status with the update to 12.1 or when i tried to re-flash the broken recovery partition.
thanks for your patience.
Hi guys, I faced some trouble while installing xposed with my galaxy A500F.
Here are the problem, my phone keep on boot into recovery (twrp) when i flashed any zip files except the root file recommended by this thread. http://forum.xda-developers.com/samsung-a-series/development/recovery-samsung-galaxy-a52015-sm-a500f-t3360802 .
I have tried other TWRP and Cynogen Recovery which is still the same. This one from the link which at least let me boot into normal.
The only method for me to boot into normal is to flash to the stock firmware via odin which then I need to reroot, reinstall twrp and try to figure out is there any other method with.
Restoring backup are not working as well for twrp which still boot back to the recovery. Some flash files, which event better ( this refer to the deodex http://forum.xda-developers.com/sam...nt/deodex-deodexed-samsung-galaxy-a5-t3232134 ) which stuck in that samsung loding screen while booting.
Any help would be thankful
Jacker31 said:
Hi guys, I faced some trouble while installing xposed with my galaxy A500F.
Here are the problem, my phone keep on boot into recovery (twrp) when i flashed any zip files except the root file recommended by this thread. http://forum.xda-developers.com/samsung-a-series/development/recovery-samsung-galaxy-a52015-sm-a500f-t3360802 .
I have tried other TWRP and Cynogen Recovery which is still the same. This one from the link which at least let me boot into normal.
The only method for me to boot into normal is to flash to the stock firmware via odin which then I need to reroot, reinstall twrp and try to figure out is there any other method with.
Restoring backup are not working as well for twrp which still boot back to the recovery. Some flash files, which event better ( this refer to the deodex http://forum.xda-developers.com/sam...nt/deodex-deodexed-samsung-galaxy-a5-t3232134 ) which stuck in that samsung loding screen while booting.
Any help would be thankful
Click to expand...
Click to collapse
Hello:
- First, TWRP to use and it is the only one that does not give me trouble installing ROMs Marshmallow (as Resurrection Remix, AICP or CM13) is the v3.0.0.1 of mygalaxya (download here). Steps for install: here
- Second, if you are in ROM Stock 5.0.2 and just want TWRP to install Xposed, I recommend using the v2.8.7 (here) does not give problems at all, although no use to install ROMs Marshmallow.
- Third, it is not necessary deodex the ROM to install Xposed, since there is a modified version of Xposed that works perfectly both as Deodex and Odex ROMs, you can download it from here.
If after using TWRP 3.0.0.1 (or higher) and enters Recovery restart always, I recommend the v2.8.7 flash on it for a normal boot.
I hope the information is usefull. :good:
Hi all! I'm new here (at least at account level) and with my first thread I want to help people which can't flash 6.0+ roms in official 2.8.x TWRP for our Moto X 2013 (like @dziarski in TWRP 2.8.7.0 thread).
I have Moto X 2013 (XT1052 model for reference) and I unlock bootloader, root and put costum roms not so long ago but here out to resolve this.
You need to upgrade your TWRP because TWRP <3.x don't support 6.0+ rom flashing well (edit: mochi579 below report twrp 2.8.7.0 can work for flashing too even I recommend latest 3.0.x version for avoid all problem especially with 7.x roms). I advice you to check out unofficial TWRP 3.0.2-0 by fantastic TeamMEX here.
This updated version grant you to flash both 6.0+ and 7.0 roms (tested myself) without any error.
There are my ROMs test to try this TWRP:
Legenda: (Android version)
TWRP 2.8.6.0 official:
Resurrection Remix 5.7.4 (6.0.1) -> failed immediately with this error
Code:
E: Error executing updater binary in zip "/..."
Error flashing zip "/..."
After some research I understood I need to updated my TWRP and here's the result
TWRP unofficial 3.0.2-0 by @TeamMex:
RR 5.7.4 (6.0.1) again -> succes without problem (I use right now)
CM13 (6.0.1) -> succes
CM14 (7.0) -> succes
OctOS Oct-M (6.0.1) -> succes
Xperience 11.0.0_rxx (7.0) -> succes
All succes without any error during flashing.
Just in case I want to add my step even its very common:
1) Make a NANDroid backup if I don't have it already
2) Wipe Cache, Data, System, ART/Dalvick cache
3) Optional factory reset (cache,art/dalvik and data)
4) Flashing ROM + Gapps from OpenGapps (remember to select ARM)
5) Reboot and finish
If there's a problem in the post or its wrong place (its here or Q&A) please let me know
Thank you WOrld1. But I'm flashing cm13, cm 14 & xpe 11 using TWRP 2.8.7.0 and it's working perfect except some known bugs.
mochi579 said:
Thank you WOrld1. But I'm flashing cm13, cm 14 & xpe 11 using TWRP 2.8.7.0 and it's working perfect except some known bugs.
Click to expand...
Click to collapse
Hi,
I was using 2.8.6.0 because in the root thread by Kidjoe here in General he write about a possible read error about SD card in the phone (clearly a bug because we don't have it xD), so my experience with 2.8.7.0 is zero unfortunately but I think it's very similar.
I have zero problem flashing the rom I listed, for various reason some mod I flashing more than one time (never because flashing problem, usually rom itself problem or just jumping back and forth).
I flash xperience 2 times, cm13/14 and OctOS one time and Resurrection Remix many times if we include backup when coming back from these ROMs.
The only know bug I experienced in 3.0.2-0 is slow flashing in "normal" condition. Just follow the note in the op of recovery thread:
Code:
NOTE: If you have slow format on ext4 go to Settings->Use rm -rf instead of formatting
Copy pasted from TeamMEX thread.
SOLVED: TWRP 3.0.3 uploaded by sub77 on androidfilehost doesn't properly recognize devices. I flashed the older 3.0.2-8 and it works fine and let me able to flash matisselte rom. Anyway, I flashed crdroid but It's stuck on boot animation.
Hello everybody,
I recently bought a secondhand Galaxy Tab 4 SM-T535. It has the android stock rom 5.2 and I wanted to flash a CM or any custom rom to speed it up a bit and remove all pre-installed apps. I did flash TWRP through Odin and it works fine, then I copied Gapps for 7.1 pico versión and crDroid custom rom based on LineageOS 14.1 and nougat 7.1 for matisselte aka Tab 4 SM-T535. I followed instructions (that are pretty the same for every custom rom) so I wiped dalvik, cache, system and data, then I flashed (tried to) crDroid 14.1 zip and... TWRP says something like: unable to flash zip, it is for device matisselte but this is matissewifi. Wtf?! So, ok. I thought I'm blind and I got the wrong version, I downloaded the matissewifi version, tried to flash again and it did flash. Then I flashed Gapps and rebooted, now it goes directly in download mode and says Could not boot normally... What is happening? I also tried CM 14.1 for matissewifi, it flashes but can't boot and I'm unable to flash the matisselte version. Why?
it is for sure the LTE tablet, I read it in settings and info in the android stock rom and it has a sim slot, so it can't be the wifi one.
Thank you in advance for any reply. Let me know if you need more informations. Thanks.
P. S. I already searched in the forum and didn't find any similar case.
Hi,
has anybody found a solution...?
seen too late.....
"SOLVED: TWRP 3.0.3 uploaded by sub77 on androidfilehost doesn't properly recognize devices. I flashed the older 3.0.2-8 and it works fine and let me able to flash matisselte rom. Anyway, I flashed crdroid but It's stuck on boot animation. "
So glad you posted this because I had failed in all my attempts and had tried a few TWRP versions but not that one, which worked perfectly with Lineage 14.1.
I'm using the xxxNolimits rom 5.1.3. When I try to do the procedure to update the version of the oxygen I can not. I downloaded the rom from the site of oneplus, 5.1.4, I make the flash in the TWRP blu spark latest version and when I reboot the message "no OS installed"
I do not know what to do, my oneplus only recognizes the custom rom if I try to go back to the stock it does not recognize. It's like I'm not flashing anything. MA does not appear any error during the flashing of the stock rom by twrp
Could someone help me?
if u flashed stock rom only,the recovery would be stock recovery after reboot,check it
then u could adb sideload in recovery mode ag
last option is flashing unbrick rom