Related
Hi Guys,
So I unlocked my phone's bootloader, flashed ClockworkMod Touch Recovery and then tried to flash CM10.... something went wrong and now my phone is stuck on the HTC Logo with the red text that says "This build is for development purposes only......".
I have tried just about everything I have read about, and I am still just as screwed. Have I permanently bricked my phone?
Thanks for your help.
First for the One XL it is suggested you use TWRP and not CWM
You can get it here from their website .
It tells you how to fastboot flash it.
If you did an OTA to 2.20 or your device came with 2.20 you probably need to flash the boot.img /kernel
So in your CM10 zip, extract the boot image.
and use fastboot to flash the boot img with the command
fastboot flash boot boot.img
and that should help you out.
I also suggest reflashing the rom with TWRP just in case. Hope this helps.
Can adb see the phone?
FrustratedAndConfused said:
Hi Guys,
So I unlocked my phone's bootloader, flashed ClockworkMod Touch Recovery and then tried to flash CM10.... something went wrong and now my phone is stuck on the HTC Logo with the red text that says "This build is for development purposes only......".
I have tried just about everything I have read about, and I am still just as screwed. Have I permanently bricked my phone?
Thanks for your help.
Click to expand...
Click to collapse
This is the one xl correct, not the international on x?
If you can get anything on your screen, your phone isn't hard-bricked.
First, which phone do you have? ClockworkMod Touch Recovery does not work on the AT&T One X (One XL). If you tried flashing a ROM through it, it's not going to work and it's probably not booting up because the ROM is corrupted.
I would start with flashing a new recovery in adb. Use TWRP, because even the basic CWM is not supported for this phone and can cause issues.
Can you get into recovery? If so is the SD card mountable?
First time I flashed i had a similar issue where the SD couldn't mount. I ended up having to run the factory RUU after relocking the bootloader & then start again. I waited for a later nightly to come out. Also seems to go better if you flash a different rom first like viper.
NismoR31 said:
Can you get into recovery? If so is the SD card mountable?
Click to expand...
Click to collapse
Doesn't matter. He flashed the wrong recovery (not for our phone). There is not Touch CWM for our version.
i should really refresh pages before replying
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.
Hello, yesterday I had the most annoying issue with my A9, after unlocking the bootloader and doing everything to be able to flash the recovery I had no luck until I flashed "twrp-3.0.3-5_CPTB-TEST2-hiae.img" and the recovery actually booted normally. However, I noticed that my device actually boot up and show the HTC logo for 5 seconds and then reboot again and again, so I download MoKee rom and did a wipe and installed it now it when I try to boot system it boot into the bootloader I actually have no idea what to do now I have no system on my device and can't open it at all.
My device is GSM international (hiaeuhl)
Last software on my device with the stock nougat 7.0
If anyone can help me with flashing an actual working software so I be able to boot up my device I would be most grateful.
Got my new XZP yesterday, unlocked it fine. But Im a dumbass and WIPED THE WHOLE THING so there's No OS. No matter how many times I try to Wipe it and Flash TWRP it Won't boot into TWRP. It won't even give me a Sony Logo. It only gives me the "Your device is unlocked - Boot in 5 seconds " message and then Endlessly will do that. I can't boot into recovery. I need to know if there's a way to remedy this I'm desperate as hell cause I rooted my Xperia X just fine. I even used Newflasher to flash a new updated Stock ROM to it. Seemed to work fine, still wouldn't give me a Sony Logo or Boot into recovery.
PLEASE HELP!!! Edit: I re flashed just a system .sin and that allowed me to get back into TWRP. I still have no clue why flashing a ROM didn't work. But I have TWRP and an SD Card.
CRIMNALSNEAK said:
Got my new XZP yesterday, unlocked it fine. But Im a dumbass and WIPED THE WHOLE THING so there's No OS. No matter how many times I try to Wipe it and Flash TWRP it Won't boot into TWRP. It won't even give me a Sony Logo. It only gives me the "Your device is unlocked - Boot in 5 seconds " message and then Endlessly will do that. I can't boot into recovery. I need to know if there's a way to remedy this I'm desperate as hell cause I rooted my Xperia X just fine. I even used Newflasher to flash a new updated Stock ROM to it. Seemed to work fine, still wouldn't give me a Sony Logo or Boot into recovery.
PLEASE HELP!!! Edit: I re flashed just a system .sin and that allowed me to get back into TWRP. I still have no clue why flashing a ROM didn't work. But I have TWRP and an SD Card.
Click to expand...
Click to collapse
that is very very interesting... did you try flashtool and flash older android version?
Can you boot into Fastboot and flash a valid rom via newflasher?
It could be possible, that in fastboot the screen is still dark
Hello,
I'm stuck on TWRP, no way to load Android.
TWRP wasn't reading the partition so I tried to repair, pass to EXT2 and back to EXT4.
All got stuck on TWRP, I could only go to fastboot, at boot it goes back to TWRP automatically. The message on TWRP console is :
"Android Rescue Party trigger! Possible solutions?
Either :
1) Wipe caches, and/or
2) Format data, and/or
3) Clean - Flash your ROM
The reported problem is:
"init_user0_failed"
Unable to decrypt FBE device."
TWRP version 3.6.2_12-MI10Ultra_v3.7_A12
First ROM present on device: xiaomi.eu_multi_MI10Ultra_22.6.15_v13-12-fastboot.zip
Second time I tried to flash with fastboot and XiaomiFlash the same ROM, successfully installed, but I was still stuck in the loop.
Third time I flashed xiaomi.eu_multi_MI10Ultra_22.6.29_v13-12.zip with TWRP, successfully, but I'm still stuck on the same loop, Android won't load.
Please I need help, I use the phone for work and actually I've been without for a whole day.
How can i fix TWRP possibly without lose all my apps and data?
sergio-bodyweb said:
Hello,
I'm stuck on TWRP, no way to load Android.
TWRP wasn't reading the partition so I tried to repair, pass to EXT2 and back to EXT4.
All got stuck on TWRP, I could only go to fastboot, at boot it goes back to TWRP automatically. The message on TWRP console is :
"Android Rescue Party trigger! Possible solutions?
Either :
1) Wipe caches, and/or
2) Format data, and/or
3) Clean - Flash your ROM
The reported problem is:
"init_user0_failed"
Unable to decrypt FBE device."
TWRP version 3.6.2_12-MI10Ultra_v3.7_A12
First ROM present on device: xiaomi.eu_multi_MI10Ultra_22.6.15_v13-12-fastboot.zip
Second time I tried to flash with fastboot and XiaomiFlash the same ROM, successfully installed, but I was still stuck in the loop.
Third time I flashed xiaomi.eu_multi_MI10Ultra_22.6.29_v13-12.zip with TWRP, successfully, but I'm still stuck on the same loop, Android won't load.
Please I need help, I use the phone for work and actually I've been without for a whole day.
How can i fix TWRP possibly without lose all my apps and data?
Click to expand...
Click to collapse
Afternoon matey, not to sure if this is helpful or not, may not be even specific to your device, but the error is the same error, so may shine a little light on the error.
Unable to decrypt FBE device
Plz anybody help this out... I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery. Initially console shows decrypted FBE device with default password. But Encryption status : Encryped So I went into wipe...
forum.xda-developers.com
plegdroid said:
Afternoon matey, not to sure if this is helpful or not, may not be even specific to your device, but the error is the same error, so may shine a little light on the error.
Unable to decrypt FBE device
Plz anybody help this out... I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery. Initially console shows decrypted FBE device with default password. But Encryption status : Encryped So I went into wipe...
forum.xda-developers.com
Click to expand...
Click to collapse
Forgot to add, would recommend reading the whole thread, you can then judge what actually works or not before trying
plegdroid said:
Forgot to add, would recommend reading the whole thread, you can then judge what actually works or not before trying
Click to expand...
Click to collapse
Of course, thx.