For those wondering about XT1644 root - Moto G4 Plus Guides, News, & Discussion

Just got my XT1644 G4 Plus 16GB here in America and brought it home for some testing.
Everything was a piece of cake, I did these things in order with no issues. There are other guides for these things all over XDA so I won't be giving detailed instructions.
Unlocked the bootloader here - https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Installed TWRP from here. - http://forum.xda-developers.com/mot...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
And flashed SuperSU from here - https://download.chainfire.eu/696/supersu/
When TWRP first boots it will ask if you want to run in systemless mode. Make sure you tell it YES!!!
Rebooted on the first try with no issues.

I have Xposed installed with a few modules and it works great.
Sent from my Moto G (4) using Tapatalk

Can anyone get me a stock boot.img i seemed to have messed up my adb protocol on the phone and my computer will no longer allow it to give me an RSA key prompt. The method worked for me though.

mystx2112 said:
Can anyone get me a stock boot.img i seemed to have messed up my adb protocol on the phone and my computer will no longer allow it to give me an RSA key prompt. The method worked for me though.
Click to expand...
Click to collapse
Can extract it from the stock ROM here: https://www.androidfilehost.com/?fid=24572369242687085

not sure if this is full proof i got bootloop

After flashing SuperSu 2.76 the phone is stuck forever at the "moto" logo. Is it because I'm using such a new version of SuperSu? Why do you use 2.46?

How long did it take to get the unlock code? I am waiting for a couple hours now...
LE: 4 hours... and finally I got the code.

Just got XT1644.
Unlocked bootloader with no problem.
Installed TWRP 3.0.2-0 with no problem
Installed SuperSu 2.46 in read only mode.
Stuck at moto screen.
Any help would be appreciated.

craigl14 said:
Just got XT1644.
Unlocked bootloader with no problem.
Installed TWRP 3.0.2-0 with no problem
Installed SuperSu 2.46 in read only mode.
Stuck at moto screen.
Any help would be appreciated.
Click to expand...
Click to collapse
Nevermind. Followed steps 5-8 of this post http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772 and all is well.

I can't get twrp to install. I keep getting told that the image is not signed or corrupt

First unlock Bootloader.
You don't need to install TWRP, just boot into it so you can flash the Systemless SuperSU.

SoNic67 said:
First unlock Bootloader.
You don't need to install TWRP, just boot into it so you can flash the Systemless SuperSU.
Click to expand...
Click to collapse
that's just it... I can't boot to twrp. It's not there.

Where? You can't find it on the SD by browsing in the recovery?

because that's just it, there's nothing in recovery. This has gotten so convoluted that I don't even know what I'm supposed to have where....

@davidkoby
Stock ROM Recovery starts with a "Dead Android" and "no command" written under it, it is you see or something else?

Does supersu need to be in systemless mode?

craigl14 said:
Nevermind. Followed steps 5-8 of this post http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772 and all is well.
Click to expand...
Click to collapse
Hi Bro,
I was also stuck at the moto logo screen and then I followed steps from 5-8, (where I see the superSu file is of different version), and now my phone is not booting at all, normally. I can boot in to bootloader but not normal boot is happening, I cannot even switch on my phone. I am a bit scared. Can you please assist.

sam9s said:
Hi Bro,
I was also stuck at the moto logo screen and then I followed steps from 5-8, (where I see the superSu file is of different version), and now my phone is not booting at all, normally. I can boot in to bootloader but not normal boot is happening, I cannot even switch on my phone. I am a bit scared. Can you please assist.
Click to expand...
Click to collapse
Assuming you have XT1644, stock marshmallow ROM and TWRP recovery installed, maybe boot into recovery and double check that the .supersu file you created is in the data directory (step 6) through file manager. If it's there maybe flash the supersu zip file in OP since that is the version that worked for me. If neither works maybe factory reset in recovery and flash the correct supersu zip and try again. Failing all that, you may have to completely start over and reflash the ROM. My guess is creating the .supersu file wasn't done correctly or the incorrect version of the supersu zip is causing the problem.

craigl14 said:
Assuming you have XT1644, stock marshmallow ROM and TWRP recovery installed, maybe boot into recovery and double check that the .supersu file you created is in the data directory (step 6) through file manager. If it's there maybe flash the supersu zip file in OP since that is the version that worked for me. If neither works maybe factory reset in recovery and flash the correct supersu zip and try again. Failing all that, you may have to completely start over and reflash the ROM. My guess is creating the .supersu file wasn't done correctly or the incorrect version of the supersu zip is causing the problem.
Click to expand...
Click to collapse
Ok yes I have XT1644 (any way to confirm BTW), I also have TWRP recovery installed (thats how I took the backup)m BUT, I was not on stock marshmallow, I was on nougat (Stock), The phone did an OTA update, months ago. Could that be the reason.
Also I checked .supersu file was there via file manager. What do you advice ..??? I also have tried now with SR3-SuperSU v2.79, but same result, it get stuck at Moto Boot screen.
Another thing I noticed at the screen where it says "Your phone is unlocked and cant be trusted" and it will boot in 5 seconds, in front of ID it says BAD KEY ... wonder what that means or if it has something to do with what wrong has happened.
Appreciate your assistance here.
Regards
Sammy

sam9s said:
Ok yes I have XT1644 (any way to confirm BTW), I also have TWRP recovery installed (thats how I took the backup)m BUT, I was not on stock marshmallow, I was on nougat (Stock), The phone did an OTA update, months ago. Could that be the reason.
Also I checked .supersu file was there via file manager. What do you advice ..??? I also have tried now with SR3-SuperSU v2.79, but same result, it get stuck at Moto Boot screen.
Another thing I noticed at the screen where it says "Your phone is unlocked and cant be trusted" and it will boot in 5 seconds, in front of ID it says BAD KEY ... wonder what that means or if it has something to do with what wrong has happened.
Appreciate your assistance here.
Regards
Sammy
Click to expand...
Click to collapse
Hmmmm...I don't know if you have XT1644. Most who have that version are still waiting on OTA I think and certainly didn't get it month's ago. It is the G4 Plus North American version. If you still have the box it will be on the UPC label. It will also be in your phone info in settings once your phone works again. Did your phone work fine before you tried to root it? Anyway, Nougat will not root with this method. If you can boot into recovery, try factory reset. If that doesn't work, you're going to have to reflash the Nougat ROM...make sure you get the right one for your phone. You will need to search around on this forum for instructions and which download to get, etc. Once you have Nougat up and running again, you will need to leave it unrooted or use one of the proven methods of root. Again, I don't think systemless supersu works for Nougat. I have no idea what bad key means. The only thing I've ever had is "N/A" come up in the unlock warning. Incidentally, you can get rid of the bootloader warning screen if you want to.

Related

[Q] Problem Rooting 5.01

I did a factory image install of the latest from nVidia then let it update to 5.01. Made sure it was unlocked, put CWM on it, was able to go from bootloader into CWM, installed SuperSU, rebooted. No root. Went into recovery ... and it's the stock recovery ("No command"). Tried this multiple times in multiple ways and no matter what happens, once it boots into the system, CWM is gone.
Is this something I've done wrong or is this something to do with 5.01? I don't understand how it can be the latter given that I'm not seeing anyone else with this problem. Help!
Solved
Okay, I am an idiot. The problem is that I wasn't using the beta SuperSU (BETA-SuperSU-v2.42.zip) which is needed for Lollipop if you're not using a custom boot.img. I was doing neither.
kmellis said:
Okay, I am an idiot. The problem is that I wasn't using the beta SuperSU (BETA-SuperSU-v2.42.zip) which is needed for Lollipop if you're not using a custom boot.img. I was doing neither.
Click to expand...
Click to collapse
can you help me out? Im getting the image of the android on its back with a red triangle and "no command" under it.
not sure if im even doing it correctly
EDIT: Never mind I got it working just had to use the cmd prompt to flash once I did "adb reboot bootloader" from there I followed the steps. thank you everyone who made this possible.

Stuck on "Warning Bootloader unlocked" screen

Flashed “BETA-SuperSU-v2.66-20160103015024.zip”. System now stuck on "Warning Bootloader unlocked" screen. I can get to Android recovery. I did wipe cache but same condition exists. Is it safe to do a factory reset at this point?
Although I recovered by restoring a Nandroid backup, I am still curious if selecting factory reset from stock recovery would have worked, or is this not an advisable method for soft brick recovery?
MrTooPhone said:
Although I recovered by restoring a Nandroid backup, I am still curious if selecting factory reset from stock recovery would have worked, or is this not an advisable method for soft brick recovery?
Click to expand...
Click to collapse
Flash BETA-SuperSU-v2.62-3-20151211162651.zip in xt1550 moto g3. Done and working fine
MrTooPhone said:
Flashed “BETA-SuperSU-v2.66-20160103015024.zip”. System now stuck on "Warning Bootloader unlocked" screen. I can get to Android recovery. I did wipe cache but same condition exists. Is it safe to do a factory reset at this point?
Click to expand...
Click to collapse
First flash system firmware.. then flash TWRP recovery.. then Flash BETA-SuperSU-v2.62-3-20151211162651.zip SuperSU Package.. Done..
sieze.s said:
Flash BETA-SuperSU-v2.62-3-20151211162651.zip in xt1550 moto g3. Done and working fine
Click to expand...
Click to collapse
Maybe I did not use the best words to ask my question. Can you recover from a system stuck on "Warning Bootloader unlocked" screen by simply doing a factory reset?
Did the same thing
MrTooPhone said:
Flashed “BETA-SuperSU-v2.66-20160103015024.zip”. System now stuck on "Warning Bootloader unlocked" screen. I can get to Android recovery. I did wipe cache but same condition exists. Is it safe to do a factory reset at this point?
Click to expand...
Click to collapse
I did the same thing could someone help me? I updated to 6.0 a couple days ago (I just got the phone) and decided to unlock the bootloader. Everything worked fine. I have minimal ADB and fastboot set up and all the drivers are set up properly too.
I then decided to flash TWRP. I didn't check "Read Only". Everything seemed fine. I swiped to reboot and was told to install supersu so I did and then rebooted.
Now I can't get past the white "Warning Bootloader Unlocked" screen. I can access the bootloader and TWRP, I'm just not sure what exactly to do next.
I have a Moto G 2015 2GB on T-Mobile USA
dcalf94 said:
I then decided to flash TWRP. I didn't check "Read Only". Everything seemed fine. I swiped to reboot and was told to install supersu so I did and then rebooted.
Now I can't get past the white "Warning Bootloader Unlocked" screen. I can access the bootloader and TWRP, I'm just not sure what exactly to do next.
I have a Moto G 2015 2GB on T-Mobile USA
Click to expand...
Click to collapse
You should not have installed supersu. Not sure why that option exists.
MrTooPhone said:
You should not have installed supersu. Not sure why that option exists.
Click to expand...
Click to collapse
What can I do to fix it?
dcalf94 said:
What can I do to fix it?
Click to expand...
Click to collapse
Did you make a Nandroid backup before flashing SuperSU? If so, restore your backup and start again.
MrTooPhone said:
Did you make a Nandroid backup before flashing SuperSU? If so, restore your backup and start again.
Click to expand...
Click to collapse
I do not have a back-up :/ Is it still safe to flash the 5.1.1 stock firmware if I was already on 6.0 via OTA? I tried a factory reset in TWRP, but that did't work.
dcalf94 said:
I do not have a back-up :/ Is it still safe to flash the 5.1.1 stock firmware if I was already on 6.0 via OTA? I tried a factory reset in TWRP, but that did't work.
Click to expand...
Click to collapse
If you are going to reflash, why not 6.0 firmware?
Is flashing my only option since I have no back-up?
MrTooPhone said:
If you are going to reflash, why not 6.0 firmware?
Click to expand...
Click to collapse
I haven't been able to find the 6.0 stock firmware for it. only 5.1.1
If all I have to do is flash 6.0 stock firmware and my phone is fixed could I do it in TWRP? Like, just drag the firmware into my phone's download folder and just install in TWRP?
MrTooPhone said:
If you are going to reflash, why not 6.0 firmware?
Click to expand...
Click to collapse
Did you look at http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 or http://firmware.center/firmware/Motorola/Moto G (3rd gen-2015)/Stock/
dcalf94 said:
I haven't been able to find the 6.0 stock firmware for it. only 5.1.1
If all I have to do is flash 6.0 stock firmware and my phone is fixed could I do it in TWRP? Like, just drag the firmware into my phone's download folder and just install in TWRP?
Click to expand...
Click to collapse
You also may want to look at http://forum.xda-developers.com/2015-moto-g/development/rom-stock-motorola-rom-collection-t3296964
MrTooPhone said:
Maybe I did not use the best words to ask my question. Can you recover from a system stuck on "Warning Bootloader unlocked" screen by simply doing a factory reset?
Click to expand...
Click to collapse
Yes you can.
Edit - My phone was also stuck at this screen only - "Warning Bootloader unlocked"
I also soft bricked my phone 3-4 days ago but got it back.
Follow below steps and you are good to go -
1. Download and install Motorola Moto Drivers
2. download stock firmware from http://forum.xda-developers.com/2015...mages-t3169639 for your Moto G3 model (in my case it was XT1550)
3. download TWRP from http://forum.xda-developers.com/devd...1051#downloads [ i used twrp-osprey-2.8.7-r5.img version ]
4. download SuperSU from http://forum.xda-developers.com/show...25&postcount=3 [make sure you download BETA-SuperSU-v2.62-3-20151211162651.zip version only else you'll again brick your phone]
Now as you have all required things to get your phone back, now follow below steps -
Now flash stock ROM, Instruction here -> http://forum.xda-developers.com/2015...ctory-t3187750
Now flash TWRP - fastboot flash recovery your_recovery_name_here.img
now start your phone (takes 15 minutes around)
now go to recovery and flash BETA-SuperSU-v2.62-3-20151211162651.zip and start your phone [ do not allow TWRP to root your phone when it asks you to root your phone just tap not now (or whatever i don't remember right now)]
Starting up phone now takes 25-30 minutes approx.
Rooted
[Don't brick and blame me , do it at your own risk ]
The point where things went wrong was that last screen where TWRP asks you if you want to root the phone - NEVER let it do that, ever, even after you properly root it the right way (which is manually flashing that specific version of SuperSU or a later version).
I've had instances where on a random reboot into TWRP - on a properly rooted Moto G3 - where that question screen comes up. It should not come up when the phone is actually rooted but I've seen it once or twice. Again, the point is: NEVER EVER let TWRP do it's own internal rooting process because that's what breaks things on the Moto G3.
- flash stock firmware complete
- go back and flash TWRP
- use TWRP to manually flash the SuperSU version (at least 2.62 beta which is what the Moto G3 running Marshmallow requires)
- make sure after that flash of SuperSU you do NOT use the TWRP option to root the device when you close out TWRP, ever
- flash a replacement logo so you don't see the bootloader is locked splash screen
That's about it.
I just unlocked BL. How long does it take to restart the phone from ADB recovery screen? Seems like forever.
guest_2011 said:
I just unlocked BL. How long does it take to restart the phone from ADB recovery screen? Seems like forever.
Click to expand...
Click to collapse
It is basically a factory reset. Not sure you need adb at this point.
MrTooPhone said:
It is basically a factory reset. Not sure you need adb at this point.
Click to expand...
Click to collapse
I kept holding pow button, it kept restarting back to the same BL unlocked message, then finally booted back to MM. Took a while i thought i bricked it.
guest_2011 said:
I kept holding pow button, it kept restarting back to the same BL unlocked message, then finally booted back to MM. Took a while i thought i bricked it.
Click to expand...
Click to collapse
same problem with me. almost an hour and the same page "BL Unlocked". how long did it take for your phone to spring back to life?

Installed Nougat but cannot get TWRP to work. Need help rolling back to marshmallow!

Ive tried to install TWRP via adb about 3 times now and it just will not work. The install goes perfectly but when i try to enter recovery mode from the phone being turned off, it just infinitely says my phone is booting. Does not go into twrp at all. My Nougat installation is extremely buggy. I have no model number, i went through complete hell to even enter my google account info. Everything seems to work fine on nougat though but i just cannot stand the bugged installation. Could really use some help.....
EDIT: Flashed TWRP through adb sideload and the phone just sits there still even when i enabled usb debugging and all. Bluetooth doesnt work and NFC doesnt work. But everything else works perfectly fine. It would just be nice to get the full functionality of my phone back. Phone isnt rooted. Just need some quick assistance.... Thanks for whomever answers.
United States user
Huawei NXT-L29
Android 7.0
have you tried to flash through fastboot the twrp in this thread? http://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617 (do not worry if is for mate 9. it works anyway)
also please check if your bootloader is unlocked before doing it.
download srk huawei tool, is pretty easy to use: http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
First you need to roll back to ur previous firmware.
You can try dload method using ur previous firmware or use rollback package.http://forum.xda-developers.com/mate-8/general/best-easiest-to-rollback-to-emui-4-0-t3507399/page1
When ur back with a working firmware,you have to unlock bootloader if its locked again,and flash twrp.
Once done u have to download nougat firmware with the data zip ment for ur region.
Go to twrp install the 2 zips( firmware and data) than reboot.
If the phone didn't boot after 10 minutes ,reboot into recovery( twrp will be replaced with stock recovery after installing the zips) and do factory reset.
Omg i forgot that the bootloader might be locked.. Ill try to find the comand to put my unlock code in and get back to this thread.. Thanks so much for suggestions.. Though ive had tkbdeal with it nougat is FANTASTIC
UPDATE: So far nothing is working. Tried the rollback packages and im still on nougat. I have an actual firmware version now. But its Russian firmware? Trying the dload method with L29185 firmwares like 200 and 320 and nothing works. Tried many things and now i cannot even install twrp. The install process would work it just wouldnt do anything when i tried to boot to twrp but now when i try to flash twrp over the recovery it just completely fails. no error code it just says it cannot find a file by that name or it cannot read it. adb says the bootloader is unlocked. Am i just completely stuck here on a buggy nougat installation? Is there any way to force a twrp backup to load outside of twrp?
gm007 said:
First you need to roll back to ur previous firmware.
You can try dload method using ur previous firmware or use rollback package.http://forum.xda-developers.com/mate-8/general/best-easiest-to-rollback-to-emui-4-0-t3507399/page1
When ur back with a working firmware,you have to unlock bootloader if its locked again,and flash twrp.
Once done u have to download nougat firmware with the data zip ment for ur region.
Go to twrp install the 2 zips( firmware and data) than reboot.
If the phone didn't boot after 10 minutes ,reboot into recovery( twrp will be replaced with stock recovery after installing the zips) and do factory reset.
Click to expand...
Click to collapse
ok so now most of this is done. Excuse me for pulling you aside I do hope you reply. Im having an issue getting twrp to work. Im on an official stock firmware. Bootloader unlocked, flashed twrp and im stuck at the screen that says my device cannot be trusted. Its on its way to booting to twrp but it completely wont. Its just stuck at that screen for about 5 minutes now. Ive let it ride and i think its just frozen there. Any ideas? im using the twrp posted by the commenter above you. The 3.0.2-1 and this is where im at.
Well now i cannot get my phone to stop wanting to factory reset itself. It keeps trying to boot into recovery and twrp is flashed over stock recovery and twrp still wont boot even though bootloader is unlocked. it freezes at the unsafe device booting screen every time it starts. I think this phone is bricked beyond repair now. Nougat update completely ruined my phone.
OcazPrime said:
ok so now most of this is done. Excuse me for pulling you aside I do hope you reply. Im having an issue getting twrp to work. Im on an official stock firmware. Bootloader unlocked, flashed twrp and im stuck at the screen that says my device cannot be trusted. Its on its way to booting to twrp but it completely wont. Its just stuck at that screen for about 5 minutes now. Ive let it ride and i think its just frozen there. Any ideas? im using the twrp posted by the commenter above you. The 3.0.2-1 and this is where im at.
Click to expand...
Click to collapse
That twrp is for mate 9 and will not work for mate 8 you need to fastboot another twrp. You need to flash another twrp you can try the twrp for the honor 8 which will work on mate 8
http://forum.xda-developers.com/honor-8/how-to/twrp-nougat-edition-t3504140
You will be to get into this twrp but not all functions are working.
---------- Post added at 02:03 AM ---------- Previous post was at 01:59 AM ----------
OcazPrime said:
Well now i cannot get my phone to stop wanting to factory reset itself. It keeps trying to boot into recovery and twrp is flashed over stock recovery and twrp still wont boot even though bootloader is unlocked. it freezes at the unsafe device booting screen every time it starts. I think this phone is bricked beyond repair now. Nougat update completely ruined my phone.
Click to expand...
Click to collapse
As long as you can get into fastboot mode, you can recover. Try to flash the nougat stock recovery then use the rollback package (try all three to see which one work) then you can dload back to your previous rom.
---------- Post added at 02:06 AM ---------- Previous post was at 02:03 AM ----------
Icchan said:
have you tried to flash through fastboot the twrp in this thread? http://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617 (do not worry if is for mate 9. it works anyway)
also please check if your bootloader is unlocked before doing it.
download srk huawei tool, is pretty easy to use: http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
Click to expand...
Click to collapse
Did you try it and it works for you? I flashed this twrp and my phone just get stuck at the screen "your phone is booting" and I have to flash another twrp.
In total what ive done up to my current state:
Flashed nougat in. Installed wrong tried reverting and noticed twrp wouldnt boot. Downloaded rollback packages. Only the russian one worked and ended up on C636B180 firmware. Checked my other recovery thread for twrp and got twrp working finally. TWRP wont flash any roms for some reason. When it flashes roms it doesnt actually install anything. When i boot it just sits there on the screen you get with an unlocked bootloader i havent let it sit there for long because when i get back into twrp and check the file manager, there are no files in sdcard. So my rom straight up didnt install. When i check it on my pc the storage size hasnt decreased at all. Its just completely screwed right now and im so frustrated im probably getting a new phone.
OcazPrime said:
In total what ive done up to my current state:
Flashed nougat in. Installed wrong tried reverting and noticed twrp wouldnt boot. Downloaded rollback packages. Only the russian one worked and ended up on C636B180 firmware. Checked my other recovery thread for twrp and got twrp working finally. TWRP wont flash any roms for some reason. When it flashes roms it doesnt actually install anything. When i boot it just sits there on the screen you get with an unlocked bootloader i havent let it sit there for long because when i get back into twrp and check the file manager, there are no files in sdcard. So my rom straight up didnt install. When i check it on my pc the storage size hasnt decreased at all. Its just completely screwed right now and im so frustrated im probably getting a new phone.
Click to expand...
Click to collapse
If you are back to C636B180 firmware, you need to unlock the phone, flash twrp, which is fully working in emui 4, root the phone then use SRK to change to the software region you want:
http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
Can i just download a superuser zip and flash it with twrp to root? Havemt rooted this phone in forever cuz i never did much with it since my first and only rooting
The reason why recovery doesn't work is due to kernel isn't supported on new bootloader
LastStandingDroid said:
The reason why recovery doesn't work is due to kernel isn't supported on new bootloader
Click to expand...
Click to collapse
What?
The previous twrp version doesn't work on nougat due to kernel.
I guess it's selected by bootloader or the new teecd
You can download twrp as mentioned here
http://forum.xda-developers.com/showthread.php?p=70126187
Also @tknguyencsu what works in that version for your mate 8?
Does MTP work and adb?
Data won't work unless you use encrypted version.
Sent from my FRD-L09 using Tapatalk
OcazPrime said:
Ive tried to install TWRP via adb about 3 times now and it just will not work. The install goes perfectly but when i try to enter recovery mode from the phone being turned off, it just infinitely says my phone is booting. Does not go into twrp at all. My Nougat installation is extremely buggy. I have no model number, i went through complete hell to even enter my google account info. Everything seems to work fine on nougat though but i just cannot stand the bugged installation. Could really use some help.....
EDIT: Flashed TWRP through adb sideload and the phone just sits there still even when i enabled usb debugging and all. Bluetooth doesnt work and NFC doesnt work. But everything else works perfectly fine. It would just be nice to get the full functionality of my phone back. Phone isnt rooted. Just need some quick assistance.... Thanks for whomever answers.
United States user
Huawei NXT-L29
Android 7.0
Click to expand...
Click to collapse
Budy I have same problem Pls note me when u find somethıng :=)) ıf I then ı will let u know.
TWRP Recovery 3.0.3
Download TWRP Recovery 3.0.3
http://sillanwali.com/downloads/twp-3.0.3.img

Stuck on Boot screen after flashing TWRP

Hello,
I just flashed the latest ROM for the S8+ (AQL5) and that went well.
Afterwards I tried to flash TWRP, but now the phone is stuck on the Samsung screen.
I then followed the guide I found here to use the BL file of AQF7 in Odin and spam the Start button so I managed to get into TWRP.
Question is, what do I do next? I restart the system it's the same problem all over again.
No one explains anywhere what to do in TWRP to save the phone.
Can I remove TWRP or somehow save the phone (without wiping my data)
Please help
Can you get to download mode? Then go to ODIN and redo your flashing of the OS and then TWRP. After the flash of TWRP, immediately boot into TWRP, and do Verity if you want that, and your root, if not already done. Clear Dalvik/cache and reboot to system.
It is not uncommon for folks, following TWRP flash, to get stuck in boot loop, unfortunately. Can take a little time, but you will get through it and finally to System.
But I thought all new firmware versions are incompatible with TWRP and cause this error.
I might try to install TWRP again if I flash the latest compatible version (I think it's the F7 one).
Does "Verify" in TWRP make that annoying "Your phone is not verified" message go away? The only option is to Reset phone when that thing comes up and I don't want to do that.
I managed to get out of that by reflashing the AQL5 version and just not installing TWPR.
Kind of scared to retry because everything goes wrong when I try to follow the guides on here or youtube
nkomp18 said:
But I thought all new firmware versions are incompatible with TWRP and cause this error.
I might try to install TWRP again if I flash the latest compatible version (I think it's the F7 one).
Does "Verify" in TWRP make that annoying "Your phone is not verified" message go away? The only option is to Reset phone when that thing comes up and I don't want to do that.
I managed to get out of that by reflashing the AQL5 version and just not installing TWPR.
Kind of scared to retry because everything goes wrong when I try to follow the guides on here or youtube
Click to expand...
Click to collapse
Would you please provide the info from my first post? and Exynos of Snapdragon?
JeffDC said:
Would you please provide the info from my first post? and Exynos of Snapdragon?
Click to expand...
Click to collapse
I have Exynos - model SM-G955F
Yes I can go to download mode but I won't do the things you ask because they're guaranteed to soft-brick the phone again and I have it working now
i have the same problem, followed this guide https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-root-galaxy-s8-crgh-rom-t3846009 managed to get to TWRP no problems, once i reset the device though im stuck at the samung galaxy s8+ boot screen and can't get it off
any suggestions ? i did try to search but this old thread was the only relevant one i could find
stuck on boot screen after flashing twrp for magisk manager
i flashed magisk manager in twrp youtube.com/watch?v=r3R9kiBIx34 by this and now not booting to android . before i had this i reflashed miui 11 using official software and coulnt be sucess this time also please help me any one . my mobile is redmi 6 pro.:crying::crying::crying::crying:

[Bricked] One of the harder ones =|

I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Whole story:
This whole episode began when I wanted to install Magisk to use MagiskManager's HideMe feature. This required me to install TWRP recovery which inturn lead me to unlock my bootloader in the process, straightforward and went off nicely. Now it was time to gain superuser which I already had done before on another device, installing SuperSU through TWRP recovery was painless but after booting found out MagiskManager needs Magisk Root to work. I then followed Android Exlpained's article to do so. Running unSU through recovery went smoothly but running Magisk didn't, on the initial run I was prompted to use Adrian DC's BootBridge which after removing a few Assert lines ran nicely. However there was no root install, SuperSU was removed though.
At the time I wasn't sure what exactly I was doing and ended up soft-bricking by flash boot through TWRP, at this time FRP was unlocked. After many many hours I restored to stock firmware by using YMNDLZ's guide. I used BLN-L24C567B370(OTA-MF-FULL) for the img files then proceed to flash the vendor.img using TWRP and the rest (boot.img, recovery.img, system.img) using fastboot in that order as instructed. The only part which didn't work was the forced update, it always failed at 5% however after more hours going recovery mode (now stock) wiping the cache and data/factory reset did the trick (Note: my model showed BLN-L24C567B369). I proceeded to reinstall TWRP, installed MagiskManager, tried to install Magisk 16.0 which ran but didn't root me but was fine because MagiskManager's download worked. I then thought since I went through all this trouble might as well install a custom rom, EliteRom was my ROM of choice. At this point I had logged in with my gmail credentials FRP was now locked.
*Before further action was taken I took the precaution to backup my current stable stock ROM after installing EliteROM but before booting*
The steps to install EliteROM went by flawlessly, installed EliteTWRP reboot into it, ran EliteROM
went through the setup without any hiccups. However up system restart I the ROM wouldn't boot leading me to boot into my recovery only to be prompted for an encryption password (???). Since I didn't recall setting one, couldn't boot into the OS, and FRP was locked I couldn't read my own internal storage. So I reformatted the internal storage and tried what had worked before, flashing the img files using TWRP then booting into stock recovery wiping cache and data/hard reset. . . this did not work. And here I am FRP locked so fastboot isn't useful (I think?), stock recovery doesn't work, eRecovery fails connection, and force update still fails at 5% with "Software install failed!".
Click to expand...
Click to collapse
Lemme know if there is any insight anyone can provide and thanks in advance.
This problem has been solved?
MisterRee said:
I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Lemme know if there is any insight anyone can provide and thanks in advance.
Click to expand...
Click to collapse
you have to follow only xda methods to root or change to custom rom. i have never heard about flashing stock images from twrp. i think u didn't followed elite rom instructions clearly. you need to formate data then reboot to recovery then wipe everything then flash the os in this way you won't get encription error. anyway now your frp is locked so there is no way to flash twrp so download all the available firmwares for your phone oeminfo then do flashing via dload you will get it worked.
even i was also once stuck with elite rom. i didn't liked it because missing apps icon and forgetting permission. i tried to go back to stock but stuck at 5% error. then went to google searched stock rom for honor 6x india and downloaded nearly 3 roms last one worked helped me to get back to stock.
never flash system images boot,vendor etc from fastboot and twrp unless you are on emui8 and going to try gsi roms.
hey i cant revert back to stock rom. it fails to get package from server. does jio voice calling works on this device?? if no then plz guide me how to go back to stock rom..
MisterRee said:
I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Lemme know if there is any insight anyone can provide and thanks in advance.
Click to expand...
Click to collapse
Register for update using firmware finder and Puts dns address in the router settings and then use erecovery

Categories

Resources