Gentlemen, I bricked my x pure a few days ago and it took 2 days for me to get back. Thanks Shawn1562!! After learning how to get back to stock recovery, I've gotten all of the OTAs and now I am maxed out at 7.0 Nougat which is fine by me. Now I want to reinstall TWRP and root so I can get rid of that horrible "Lenovo" logo.bin, it sucks. Plus, get rid of the "warning bootloader unlocked" crap. I want to be able to get back to stock recovery, but is probably not that big a deal, but I cannot find a proper 7.0 Nougat recovery image to replace TWRP with when the time comes and I don't know how to suck it out of the Blur 7.0 file I downloaded from the Motorola Firmware guys. Does anyone have that file? Or is my thinking all wrong and I'm going about this the wrong way? Thanks for your help!!!
the stock firmware here https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
has the recovery.img . just flash using "fastboot flash recovery recovery.img"
Related
I've just been planing out how i'm gonna root, twrp, exposed etc. Of particular concern to me is being able to return to stock when the marshmallow ota arrives. I came across this, regarding the moto x 2014
"Thanks. I'm pretty sure I can just fastboot flash [stock] recovery and then do a factory reset and be back to 100% stock. That's what I'm going to try anyway. Update, it worked. Just fastboot flash recovery recovery.img then factory reset and my phone is back to stock. Now to send it back to Motorola and get my new one!"
So do you think i'll be able to do this? (using the recovery.img for the moto x style, of course)
Thanks
I thought the same, but it didn't work for me, I flashed the stock recovery but it freezes when I tap in recovery mode. I don't know why...
Ok, hello everyone, I have a quick question. Would the steps for updating to nougat be?: 1) Download and install B29 modded in twrp to reset everything back to stock 2) If fastboot doesn't work flash bl_unlock file from twrp after using axon7tool to flash twrp to get fastboot back? 3) flash back stock recovery and download the update? 4) Install b15 and then go back to edl and install twrp and then flash the unlock again 5) flash modem fix2 to get partitions to work? 6)profit?
so would that work? i am half way through this. i just got back fastboot and was wondering if this would work to help get to B15. I want to see how botched the b15 update is. Feedback would be great for US peeps who did this already to get to b15 and if a better method is there that you used. by all means talk to me like a 5 year old, I am stupid when it comes to brickable chances with modding. And after i do it and get it from you guys help i will write a tutorial and publish on XDA
I flashed TWRP on my Moto G4 after booting the TWRP img using fastboot, and now I can't seem to get Android to start. I can boot into TWRP just fine, but when I try to start Android the phone screen just goes black and the LED USB indicator blinks.
Does anyone know what happened and how / if I can fix it without flashing the stock rom?
try flashing everything from recovery again? Maybe you messed up something, like rooting your rom without knowing it
I managed to get it to boot again by flashing the stock system image, but now there are a few odd bugs and I can't get the Android 7 OTA. Fastboot is giving me issues when I try to follow Motorola's instructions (gyazo.com/38675380995061a98714678c796ba92b, motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images) saying that the images aren't signed or are corrupt. I'll try just flashing the image files from TWRP like you said.
The forum won't let me link to websites.
I had the same boot problem after trying to systemless root after 7.0 updateon twrp 3.1. Had to reflash to stock recovery and stock boot image before it would boot to anything other than fastboot or a blank screen.
So it seems like the best solution for now is to not flash twrp as recovery when running Android 7 and just booting into twrp temporarily with
Code:
fastboot boot <twrp.img file>
I didn't have any problems systemless rooting my Android 7 phone with supersu doing it this way, the problem only started after I attempted to flash twrp as my recovery.
After flashing the stock firmware, my only issue now is not getting the OTA, which is very frustrating as I had it working earlier today.
EDIT; Found a possible solution for getting the OTA for XT1625 in another thread, flash XT1625-XT1644_ATHENE-RETUS_MPJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml.zip to the phone from here firmware.center/firmware/Motorola/Moto%20G4%20%28Plus%29/Stock/
* Currently testing this now, not sure if it'll work
EDIT; Worked for me, a few seconds after booting I got the OTA update. I'm on Moto G4 (XT1625 Athene) retusa
If you want to know how to flash the .49 rom, refer to this thread (forum.xda-developers.com/moto-g4/development/unbrick-hard-bricked-moto-g4-amazon-t3486578) and follow the instructions as closely as you can. There are some differences between the Amazon version and the non Amazon.
IMPORTANT: do not attempt to systemless root (at least with SuperSu 2.79 SR3), it just caused Android to not boot. For now, wait for a fix. (But if you simply must attempt a root, make a backup in twrp)
Good luck!
unprofessional hacker said:
So it seems like the best solution for now is to not flash twrp as recovery when running Android 7 and just booting into twrp temporarily with
Code:
fastboot boot <twrp.img file>
Click to expand...
Click to collapse
Thanks for this! I didn't know how to do it until now
I once Hard Bricked my phone. Then when I somehow recovered it and tried to install stock firmware, it went into bootloop, then I used g5 plus software to flash boot.img and it worked but after that I lost my original recovery and I have TWRP recovery instead and I can't update my software because it will hard brick again. I have tried reflashing stock Android (problem remained the same) and I am not sure but I guess I somehow modified my system and that's why I am not able to get my stock recovery back(I tried to flash that but that failed). Please help as I need to update my system because Within months Android O updates will roll out. Thanks.
Fastboot to stock. It's the only true way to get what you want.
Karlinski said:
Fastboot to stock. It's the only true way to get what you want.
Click to expand...
Click to collapse
I'm not able to. In My Fastboot it says "System status: Modified" instead of system status Official, so any idea how to get Official System status?
fastboot doesn't care about firmware status. if you want to get official, you need to relock your bootloader. There are instructions on how to do so on the forums here.
Karlinski said:
fastboot doesn't care about firmware status. if you want to get official, you need to relock your bootloader. There are instructions on how to do so on the forums here.
Click to expand...
Click to collapse
Then I'd be able to download system updates?
harshtomar1308 said:
Then I'd be able to download system updates?
Click to expand...
Click to collapse
Depends on what happened to your device when you hard bricked it in the first place and how you recovered from it.
If you recovered using the albus (Moto Z2 Play) blankflash, then I don't think you'll be able to re-flash the stock firmware completely, as you have a different bootloader to what's expected (i.e. Moto Z2 Play bootloader on a G5 Plus). You'd still be able to flash the system and modem side of the firmware, just likely not the GPT or bootloader. Thus, you're likely better off waiting for TWRP flashables of the stock Oreo ROM, which would mean you don't have to worry about your bootloader. Of course, that means you won't be able to take OTA updates again.
What device do you have and what stock firmware were you/are you running on your device? Maybe you're flashing either the wrong firmware or too old firmware for your device.
echo92 said:
Depends on what happened to your device when you hard bricked it in the first place and how you recovered from it.
If you recovered using the albus (Moto Z2 Play) blankflash, then I don't think you'll be able to re-flash the stock firmware completely, as you have a different bootloader to what's expected (i.e. Moto Z2 Play bootloader on a G5 Plus). You'd still be able to flash the system and modem side of the firmware, just likely not the GPT or bootloader. Thus, you're likely better off waiting for TWRP flashables of the stock Oreo ROM, which would mean you don't have to worry about your bootloader. Of course, that means you won't be able to take OTA updates again.
What device do you have and what stock firmware were you/are you running on your device? Maybe you're flashing either the wrong firmware or too old firmware for your device.
Click to expand...
Click to collapse
Yes, I used this method to regain my phone. I'm on XT1686 and build number is NPN25.137-15
My device is hard bricked
harshtomar1308 said:
I once Hard Bricked my phone. Then when I somehow recovered it and tried to install stock firmware, it went into bootloop, then I used g5 plus software to flash boot.img and it worked but after that I lost my original recovery and I have TWRP recovery instead and I can't update my software because it will hard brick again. I have tried reflashing stock Android (problem remained the same) and I am not sure but I guess I somehow modified my system and that's why I am not able to get my stock recovery back(I tried to flash that but that failed). Please help as I need to update my system because Within months Android O updates will roll out. Thanks.
Click to expand...
Click to collapse
I have installed the stock firmware on my Moto g5 plus and when I updated it to .67
The phone started to be updating but when the bar fills up then my phone just stucked. Please help me I cannot even go to bootloader or the fast boot. No logo nor any kind of signals are showing but no results please help me
Would anyone here have it? I overlooked the "7.1.1" message and used TWRP anyways, THEN used the 7.1.1 boot img which threw me into a bootloop, I can boot into EDL just fine, sideload doesn't work with me, so I see obtaining my original B2017G US boot.img and reflashing it with tulip as the best option to get back on track! Hope someone is able to help
Though, would there be any other methods of flashing the boot.img and removing the bootloop, like updating my firmware to 7.1.1 or something?
https://forum.xda-developers.com/showpost.php?p=73257562&postcount=13
I see something here, downloaded "Axon7mini_Android7(SD card software).zip" but unfortunately I don't know what to do with that update.zip file.