i hard bricked my device(potter) but got it working using albus blankflash and flashed pixel experience 8.1.0 , and was wondering if it is safe to go back to stock , because i know nothing about blankflash and what it does to the device.
Try one of the TWRP flashable stock builds.
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...
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
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"
I flashed Mokee 8.1 coming from [EUI-6.0.030s]-[Official-Cleaned-Modded]-LEX722[Discontinued]. On booting into Mokee, it appeared that my wifi no longer worked (no networks found). I flashed back to [EUI-6.0.030s]-[Official-Cleaned-Modded]-LEX722[Discontinued] thinking this might fix it but it's still broken. I have also tried flashing the firmware again but this has not fixed it.
Would I be best going back to stock EUI to fix it? If so can anyone help me in doing this on the X722. I know that you you have to flash it through the stock LeEco recovery, not TWRP. Can this be done via the All In One Tool? If so, can anyone give me a step by step guide on exactly how to do it? I have the stock rom and recovery files.
I was using Bootleggers (8.1 Oreo ) ROM on my XT1686 and tried flashing Pixel experience (9.0 pie ).
Steps i went through:
1. Clean Wipe
2. Flashing Pixel Experience
3. Losing my network signals and IMEI
4. TWRP flashable 8.1 stock rom
5. Flashing the bootleggers 9.0pie update
6. Trying the erasemodemst 1/2 commands. NO result.
6. Restoring EFS and persist from the previous backup.
7. Ended up having IMEI back but still no network signals after multiple reboots.
I do know that flashing a STOCK ROM using fastboot and performing a clean reset will get my network back but will i have to stay back in the STOCK ROM ? Can nothing be done that allows me to keep using this amazing rom with a functioning network ?
TL;DR: NO NETWORK, IMEI AVAILABLE. EFS AND PERSIST BACKUPS ARE FLASHED ALREADY.
sjjatin9568 said:
I was using Bootleggers (8.1 Oreo ) ROM on my XT1686 and tried flashing Pixel experience (9.0 pie ).
Steps i went through:
1. Clean Wipe
2. Flashing Pixel Experience
3. Losing my network signals and IMEI
4. TWRP flashable 8.1 stock rom
5. Flashing the bootleggers 9.0pie update
6. Trying the erasemodemst 1/2 commands. NO result.
6. Restoring EFS and persist from the previous backup.
7. Ended up having IMEI back but still no network signals after multiple reboots.
I do know that flashing a STOCK ROM using fastboot and performing a clean reset will get my network back but will i have to stay back in the STOCK ROM ? Can nothing be done that allows me to keep using this amazing rom with a functioning network ?
TL;DR: NO NETWORK, IMEI AVAILABLE. EFS AND PERSIST BACKUPS ARE FLASHED ALREADY.
Click to expand...
Click to collapse
You didn't say from what ROM/firmware the persist.img backup was taken. If it wasn't from your original stock firmware that may be a problem. If it was from stock which version, 7.0 or 8.1?
If you flash a 8.1 signed fastboot firmware you should be able to change to every ROM you want to afterwards.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
You didn't say from what ROM/firmware the persist.img backup was taken. If it wasn't from your original stock firmware that may be a problem. If it was from stock which version, 7.0 or 8.1?
If you flash a 8.1 signed fastboot firmware you should be able to change to every ROM you want to afterwards.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
I lost the IMEI and VoLTE when i switched from 7.0 (stock) to 8.1 (experience ) rom and then had to use the VoLTE fix to set it straight.
After i got everything working in my 8.1 pixel experience ROM , i made a backup of all the partitions. I used that backup here.
sjjatin9568 said:
I lost the IMEI and VoLTE when i switched from 7.0 (stock) to 8.1 (experience ) rom and then had to use the VoLTE fix to set it straight.
After i got everything working in my 8.1 pixel experience ROM , i made a backup of all the partitions. I used that backup here.
Click to expand...
Click to collapse
Most probably the problem was to switch from 7.0 stock to a custom ROM, you should have updated to stock 8.1 and make a backup of persist before doing that. The persist.img will be modified when flashing a custom ROM.
If you haven't flashed someone else's persist file the best way to go would be flashing a signed Motorola 8.1 firmware by fastboot, take a full nandroid incl. persist and go from there to a custom ROM.
Here's how to do it and links to all available firmwares:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
Most probably the problem was to switch from 7.0 stock to a custom ROM, you should have updated to stock 8.1 and make a backup of persist before doing that. The persist.img will be modified when flashing a custom ROM.
If you haven't flashed someone else's persist file the best way to go would be flashing a signed Motorola 8.1 firmware by fastboot, take a full nandroid incl. persist and go from there to a custom ROM.
Here's how to do it and links to all available firmwares:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Thanks alot @Wolfcity. Sorry i couldnt reply sooner. I flashed a twpr flashable 8.0 stock by @NZpred from the page here:
https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
It brought back the signals. After that i backed up all the files and EFS and reflashed the custom rom and the EFS and persist.
Thanks alot for your help and timely response.