Hi guys.
Trying not to panic right now. Flashed TWRP on my phone, 3.0, all good. Then proceed to flash ROOT, and it got stuck on the bootloader warning.
Tried flashing another version of ROOT on top, and it didn't solve the problem, but was able to reach boot animation.
After searching, i saw it's possible to unbrick device by reflashing stock rom. Can also solve the problem by flashing CM 13 lux instead?
Update: going to try it now. Whish me luck!!!
success with installing the CM13! working perfect. Now just choosing which gapps to install.
su 2.62-63 works with stock
It's all solved now, with GAPPS and Root from chainfire, finally working. Awesome!
Related
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:
Heya guys, I've been rocking my OnePlus 2 for a while. I was wanting to install a newer ROM on it but I seem to run into some problems and I just can't figure it out.
I tried to install several roms (which are all based on 7.1 android) and I seem to be getting the same error on all of them: E:Error executing updater binary in zip '/sdcard/crDroidAndroid-7.1-20161128-oneplus2.zip' This was when I tried the crDroid mod, of course. The only ones that seem to work are CM13 and OxygenOS 2.2.
Couldn't really find a good solution for this when I google'd. I tried carefully wiping what I had to but that didn't seem to help.
I also tried updating my recovery, but when I try to update my recovery it just freezes when I boot. I tried this using fastboot and or via TWRP. I'm currently using version 2.8.7.0 of TWRP because the lastest version of TWRP bricks my recovery. I've also tried the blue spark TWRP and TWRP-hybrid, they don't seem to work either, my phone just stays on the 1+ logo. I have to flash the old version of TWRP back onto it using fastboot to get a working recovery.
Anyone have a solution for me?
EDIT: I have a Chinese OnePlus2, the A2001.
EDIT2: Forgot to mention something that might be critical to the problem: I did update from OxygenOS 2.2.1 to the latest as of now, 3.1. This removed my TWRP recovery and I couldn't get the new one to work, which made me install 2.2.1 again. I've seen people mention some problems with 3.1 so this might be the cause of it?
Hello,
I've installed twrp on my lg g2 802. Using twrp i tried to install lineageos, but on reboot the screen remains black. I see the monitor on but nothing happens. I have to force the reboot. I can still go into recovery but i don't understand where is the problem.
I already tried to wipe everything, and i installed latest nightly of lineageos (no gapps).
Da you have an idea?
I have this same exact problem. I hope a solution is out there!
i installed from a kitkat. Maybe this can be a problem? Should i install lineage from a lollipop?
Flash this
https://forum.xda-developers.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219
I got LineageOS to work!
It was a long grind of reading various posts on here and looking up other info on google, but I finally got my phone to run LineageOS.
The three things that I think are key are:
Making sure your phone is starting off with kitkat. I wasn't able to root my phone with lollipop. Stumproot, towelroot, and ioroot all didn't work. Once I downgraded to kitkat, I rooted successfully with ioroot.
After getting TWRP, updating it to 3.1.0. I had to first get an older version and then flash 3.1.0
Change the bootloader to kitkat if it isn't on it already. I used Bootloader Changer.
emilio84music said:
i installed from a kitkat. Maybe this can be a problem? Should i install lineage from a lollipop?
Click to expand...
Click to collapse
Yes u need lp bootstacks. Or you can simply get to the stock lollipop using flashtool and then flash lineage os
Thank you for support. Now it works
Feel free to scold me, I'm not too upset but would like to fix the phone if it is possible.
Background - Phone is a Moto G4 16gb, XT1625, running android 7.0 nougat. Phone resets a lot so before replacing it I thought I would try rooting and loading a different ROM to see if it helped. I followed THIS guide:
https://theunlockr.com/root-motorola-moto-g4-moto-g4-plus/
I successfully unlocked and flashed TWRP recovery. I then tried to flash supersu v2.82 as a zip through TWRP, and upon completion the phone no longer boots up.
I can access the bootloader and and access TWRP recovery, but otherwise wiping data/factory reset or re-flashing supersu does nothing. I also tried flashing supersu as a systemless root install. I just get a black screen and a flashing white led at the bottom when charging/trying to power on. I only after the fact happened to read something about an elementalx kernel for nougat so I'm thinking maybe this was the problem.
I this a hard brick or a soft brick or just in an unbootable state? Is there a way to recover? Thanks.
Update, after playing around with it all morning I was able to get it back to booting by first flashing the el;ementalx kernel, then downloading and flashing the latest beta release of SuperSU, and then wiping dalvik cache. Not sure exactly which step cured it but in case anyone searches and finds this thread.
dskater411 said:
Update, after playing around with it all morning I was able to get it back to booting by first flashing the el;ementalx kernel, then downloading and flashing the latest beta release of SuperSU, and then wiping dalvik cache. Not sure exactly which step cured it but in case anyone searches and finds this thread.
Click to expand...
Click to collapse
Glad to hear you got your device fixed. For future reference, it's likely the ElementalX kernel that got you out - with stock Nougat on our devices, you can't root the stock Motorola kernel. You'll soft brick your device otherwise.
The problem with those guides is that they often don't mention that step - whilst the procedure may work for our devices with Marshmallow and Oreo, it just won't work for Nougat. Also, that article is over 2 years old, before we got Nougat onto our devices. If you wanted to flash a custom ROM, root is not needed, you just need an unlocked bootloader and TWRP.
As an aside, SuperSU is obselete, and likely abandoned by its developer. You may wish to flash magisk as your root solution, which would necessitate uninstalling SuperSU, reflashing the stock Motorola kernel and then ElementalX, then magisk.
Hey,
I flashed twrp and then flashed Magisk and SuperSu in MIUI 10.2.4.0, 10.2.5.0 and 11.0.7.0... After flashing and rebooting my phone was not rooted, I tried many versions of Magisk and many times. But didn't work, anyone have any working files?? And does custom rom/kenrel helps rooting the device.
Thank you..
you need to patch the boot img. you can find patched boot img for older roms like that
nvm i had 2 tabs looked the same