How to flash the Kernel correctly? - Xperia Play General

Im having a lot of troubles flashing a new Kernel to my Play. So i wanted to ask if I do something wrong.
Heres what i do to flash a new kernel
1. Unlock bootloader
2. flash new System.img and/or flash new boot.img via fastboot (fastboot flash system system.img / fastboot flash boot boot.img)
For now i succeed in flashing a new system.img which gives me root access, but everytime flash a boot.img (no matter what kind of kernel, even stock) I end up in.. hm not really a bootloop - nothing happens at all, screen doesnt even turn on.
Heres what i do to make my phone work again.
1. flash the relock ftf via flashtool
2. Use sony Ericsson update to renew the whole system
I gotta say that the flashing over flashtool only works with the relock.ftf, every other ftf I have tried gives me Errors, thats why I use the SE Update tool to go back to stock.
I guess flashing a new kernel through fastboot doesnt work for me, maybe i can flash only the kernel through flashtool? Any suggestions?

Nobody has an Idea??? Plz tell me how you flashed your (working) kernel and which kernel to use.

Will, I have a problem like that but i can't flash any thing with fastboot (Kernal or system)
and i'm also looking for help.

Plz say what exactly you did, otherwise nobody can help :-(

Will, Check my thread for details: Here

ddsds said:
Will, Check my thread for details: Here
Click to expand...
Click to collapse
ddsds Just a thought, you could try relocking and unlocking bootloader again, maybe fastboot will work better

AndroHero said:
ddsds Just a thought, you could try relocking and unlocking bootloader again, maybe fastboot will work better
Click to expand...
Click to collapse
I tried many times but no good.

Related

[Q] How to restore DROID RAZR M back to stock JB 4.1.2 from the kitkat 4.4.2

Can any one help me to restore my XT907 back to stock JB 4.1.2 from the stock kitkat 4.4.2 update?
My current System version is: 183.46.10.XT907.Veryzon.en.US
Android Version: 4.4.2
Baseband Version: SM_BP_101031.042.32.86P
Kernal Version: 3.4.42-g5170b6b
[email protected] #1
Fri May 2 00:30:06 PDT 2014
Build Number: KDA20.62-10.1
Build Date: Fri May 2 00:20:25 PDT 2014
Please help me.. Thanks in advance...
Wouldn't recommend you try it on a locked bootloader.
Those that are unlocked shouldn't have any issues.
Technically, with a locked bootloader, if Fastboot will allow you to downgrade, then it should be possible.
You'd have to boot into Fastboot, then run the command:
fastboot flash system system.img
Where system.img is the 4.1.2 image file extracted from the fxz file. If it won't let you do this, then downgrade isn't possible. It will likely say failed flash and you'll have to flash something to kick the phone out of fastboot like logo.img.
You could also try RSDLite and try to flash the 4.1.2 fxz, but I doubt that will work because bootloader and such are not downgradeable and it will likely fail.
GnatGoSplat said:
Technically, with a locked bootloader, if Fastboot will allow you to downgrade, then it should be possible.
You'd have to boot into Fastboot, then run the command:
fastboot flash system system.img
Where system.img is the 4.1.2 image file extracted from the fxz file. If it won't let you do this, then downgrade isn't possible. It will likely say failed flash and you'll have to flash something to kick the phone out of fastboot like logo.img.
You could also try RSDLite and try to flash the 4.1.2 fxz, but I doubt that will work because bootloader and such are not downgradeable and it will likely fail.
Click to expand...
Click to collapse
Thanks for ur reply..
My bootloader is locked. I want to try downgrade to stock 4.1.2. Can u please send me the link to download stock 4.1.2 img and exact steps to downgrade?
Thnaks so much in advance..
kulsforu said:
Thanks for ur reply..
My bootloader is locked. I want to try downgrade to stock 4.1.2. Can u please send me the link to download stock 4.1.2 img and exact steps to downgrade?
Thnaks so much in advance..
Click to expand...
Click to collapse
You can get them here:
http://sbf.droid-developers.org/phone.php?device=8
You can extract the original system.img from the archive as well as logo.img in case the phone doesn't allow you to flash system.img, you can use logo.img to kick the phone out of Fastboot. You will need to install Motorola ADB drivers on your computer in advance, and also need a fastboot.exe file which I think you can find via Google, but if you have ever rooted your phone in the past, usually that also came with fastboot.
Anyway, get into fastboot mode by turning off the phone, then holding down all 3 buttons. Use vol- to select Fastboot and vol+ to choose it. Phone should boot into fastboot.
Connect to PC and issue command:
fastboot flash system system.img
If it works, the phone should be downgraded. If it says flash failed, then downgrade isn't possible. In that case, if the phone is stuck in fastboot mode and can't be rebooted, issue this command to get out of fastboot.
fastboot flash logo logo.img
That should let it reboot as normal.
I actually doubt it's possible to downgrade, but I haven't tried it myself so I can't say for sure.
GnatGoSplat said:
You can get them here:
http://sbf.droid-developers.org/phone.php?device=8
You can extract the original system.img from the archive as well as logo.img in case the phone doesn't allow you to flash system.img, you can use logo.img to kick the phone out of Fastboot. You will need to install Motorola ADB drivers on your computer in advance, and also need a fastboot.exe file which I think you can find via Google, but if you have ever rooted your phone in the past, usually that also came with fastboot.
Anyway, get into fastboot mode by turning off the phone, then holding down all 3 buttons. Use vol- to select Fastboot and vol+ to choose it. Phone should boot into fastboot.
Connect to PC and issue command:
fastboot flash system system.img
If it works, the phone should be downgraded. If it says flash failed, then downgrade isn't possible. In that case, if the phone is stuck in fastboot mode and can't be rebooted, issue this command to get out of fastboot.
fastboot flash logo logo.img
That should let it reboot as normal.
I actually doubt it's possible to downgrade, but I haven't tried it myself so I can't say for sure.
Click to expand...
Click to collapse
Thank u so much my friend, I need to clear that I m using this phone in India with Reliance CDMA network. If downgrade will succeed then will it in verizon locked condition or it will remain unlocked for global use? Also I need to add that I have never unlocked my bootloader or rooted my phone.
kulsforu said:
Thank u so much my friend, I need to clear that I m using this phone in India with Reliance CDMA network. If downgrade will succeed then will it in verizon locked condition or it will remain unlocked for global use? Also I need to add that I have never unlocked my bootloader or rooted my phone.
Click to expand...
Click to collapse
I think it would stay unlocked since you wouldn't be reflashing the radio.
It is easy enough to re-unlock if that should get reversed, however.
Ah, nevermind. Don't bother to try it. Even if you could succeed, you'd end up with black screen after the logo. The newer bootloaders will not allow Jellybean to boot. There is no way to downgrade. KitKat is a one way road with a locked BL. Sorry!
GnatGoSplat said:
Ah, nevermind. Don't bother to try it. Even if you could succeed, you'd end up with black screen after the logo. The newer bootloaders will not allow Jellybean to boot. There is no way to downgrade. KitKat is a one way road with a locked BL. Sorry!
Click to expand...
Click to collapse
:crying::crying::crying::crying::crying:
Sorry for the bad news. I'm in the same boat now too. Thought I would experiment with ways to preserve root, and long story short, now I'm stuck on an unrooted phone on stock KK with locked BL.
Why do you want to downgrade? If it's to be rooted, sorry, no solution for that. If there is some other issue, maybe there is a solution for that specific issue.
GnatGoSplat said:
Sorry for the bad news. I'm in the same boat now too. Thought I would experiment with ways to preserve root, and long story short, now I'm stuck on an unrooted phone on stock KK with locked BL.
Why do you want to downgrade? If it's to be rooted, sorry, no solution for that. If there is some other issue, maybe there is a solution for that specific issue.
Click to expand...
Click to collapse
The issue is my CDMA data is not working after upgrade to kitkat. I m from India and using Reliance CDMA sim. Before update, everything was working perfect. But now only data(EVDO or 1x) is not working. GSM data(3G & 2G) is working.
Please help if u have any solution for this issue.
GnatGoSplat said:
You can get them here:
http://sbf.droid-developers.org/phone.php?device=8
You can extract the original system.img from the archive as well as logo.img in case the phone doesn't allow you to flash system.img, you can use logo.img to kick the phone out of Fastboot. You will need to install Motorola ADB drivers on your computer in advance, and also need a fastboot.exe file which I think you can find via Google, but if you have ever rooted your phone in the past, usually that also came with fastboot.
Anyway, get into fastboot mode by turning off the phone, then holding down all 3 buttons. Use vol- to select Fastboot and vol+ to choose it. Phone should boot into fastboot.
Connect to PC and issue command:
fastboot flash system system.img
If it works, the phone should be downgraded. If it says flash failed, then downgrade isn't possible. In that case, if the phone is stuck in fastboot mode and can't be rebooted, issue this command to get out of fastboot.
fastboot flash logo logo.img
That should let it reboot as normal.
I actually doubt it's possible to downgrade, but I haven't tried it myself so I can't say for sure.
Click to expand...
Click to collapse
I'm also on official KK with locked bootloader, Can i flash kk modified system.img via this method ?
Prohyper said:
I'm also on official KK with locked bootloader, Can i flash kk modified system.img via this method ?
Click to expand...
Click to collapse
Sorry, with locked BL, you can't flash modified system.img or older system.img. I tried it just to make sure, and the phone wouldn't allow it.
GnatGoSplat said:
Sorry for the bad news. I'm in the same boat now too. Thought I would experiment with ways to preserve root, and long story short, now I'm stuck on an unrooted phone on stock KK with locked BL.
Why do you want to downgrade? If it's to be rooted, sorry, no solution for that. If there is some other issue, maybe there is a solution for that specific issue.
Click to expand...
Click to collapse
The issue is my CDMA data is not working after upgrade to kitkat. I m from India and using Reliance CDMA sim. Before update, everything was working perfect. But now only data(EVDO or 1x) is not working. GSM data(3G & 2G) is working.
Please help if u have any solution for this issue.
kulsforu said:
The issue is my CDMA data is not working after upgrade to kitkat. I m from India and using Reliance CDMA sim. Before update, everything was working perfect. But now only data(EVDO or 1x) is not working. GSM data(3G & 2G) is working.
Please help if u have any solution for this issue.
Click to expand...
Click to collapse
Good news is that major developments happened a month ago. :good:
You can now root AND unlock bootloader on KitKat. I think you can find the info you need in this thread:
http://forum.xda-developers.com/showthread.php?t=2783806
Once you have bootloader unlocked, you can downgrade back to JB. I have tried it and can confirm it works.
Good luck!
GnatGoSplat said:
Good news is that major developments happened a month ago. :good:
You can now root AND unlock bootloader on KitKat. I think you can find the info you need in this thread:
http://forum.xda-developers.com/showthread.php?t=2783806
Once you have bootloader unlocked, you can downgrade back to JB. I have tried it and can confirm it works.
Good luck!
Click to expand...
Click to collapse
Thanks much for update..
I can not getting the method. Actually I m new with these things.
Can you please explain how to use tr.apk?
Thanks in Advance..
kulsforu said:
Thanks much for update..
I can not getting the method. Actually I m new with these things.
Can you please explain how to use tr.apk?
Thanks in Advance..
Click to expand...
Click to collapse
You just run it and let it do its thing. Your phone should be rooted once it has rebooted. You can verify with any rootchecker app.
Then install and run Motopocalypse.apk to unlock your bootloader.
You can the use RSDLite to flash back to JellyBean using the JB fxz file. You will need to edit the xml file in the fxz file, removing the lines with gpt.bin and tz.mbn.
GnatGoSplat said:
You just run it and let it do its thing. Your phone should be rooted once it has rebooted. You can verify with any rootchecker app.
Then install and run Motopocalypse.apk to unlock your bootloader.
You can the use RSDLite to flash back to JellyBean using the JB fxz file. You will need to edit the xml file in the fxz file, removing the lines with gpt.bin and tz.mbn.
Click to expand...
Click to collapse
Thanks.. I m getting you.. But I m not using verizon network. My Razr M is unlocked for both CDMA and GSM carrier. I m using my Razr M in India and both CDMA and GSM are working at present. only DATA in CDMA is not working.
My question is will it be remain unlocked for both CDMA and GSM career in India after flashing back stock JELLY BEAN?
Thanks in Advance..
kulsforu said:
My question is will it be remain unlocked for both CDMA and GSM career in India after flashing back stock JELLY BEAN?
Click to expand...
Click to collapse
I believe so, yes.
GnatGoSplat said:
I believe so, yes.
Click to expand...
Click to collapse
Thanks.
Can you please send link to download JB 4.1.2 fxz file. and step by step instruction to flash the file.?

[NO_ROM]Fastboot access but bootloader lock! Help me

Hi guys,
i'm stucking in a not good situation with my OnePlus 2. Maybe someone here can help me..
In this moment i have my phone without access to recovery, but working fastboot.
That problem happened after flashing the Phoenix Rom. I have the bootloader locked, from fastboot i can't do anything. ( flash recovery, flash boot.img etc). No rom working, i can't enabling the possibility to unlock the bootloader..
I already tried with the Hard Brick tricks, but my laptop did not recognize the Qualcomm devices.
somebody can help me?
i will offer you a beer
Thanks!
colol said:
Hi guys,
i'm stucking in a not good situation with my OnePlus 2. Maybe someone here can help me..
In this moment i have my phone without access to recovery, but working fastboot.
That problem happened after flashing the Phoenix Rom. I have the bootloader locked, from fastboot i can't do anything. ( flash recovery, flash boot.img etc). No rom working, i can't enabling the possibility to unlock the bootloader..
I already tried with the Hard Brick tricks, but my laptop did not recognize the Qualcomm devices.
somebody can help me?
i will offer you a beer
Thanks!
Click to expand...
Click to collapse
How did you managed to flash the ROM since your bootloader is locked, which means no custom recovery installed ?
Does
Code:
fastboot boot recovery.img
works ? (BOOT, not FLASH)
casual_kikoo said:
How did you managed to flash the ROM since your bootloader is locked, which means no custom recovery installed ?
Does
Code:
fastboot boot recovery.img
works ? (BOOT, not FLASH)
Click to expand...
Click to collapse
Hi casual_kikoo,
thanks for reply!
I tried to do fastboot boot recovery.img, but not worked. No customer recovery.
I fixed it, following this guide. ( after a lot of windows's driver problems )
http://forum.xda-developers.com/oneplus-2/general/guide-official-stock-reset-to-oos-2-2-0-t3290707
Thanks so much for the help!
Cheers,

Unable to update OTA since repair - alternatives?

Hi all,
To cut a long story short, around the time MM was being released I cracked my display and broke the digitiser. Before sending the phone off for repair I got the update notification -.- but sent it away without updating as I couldn't accept it. Phone returned and working but no OTA notification, factory reset a few times, sim out and try again, all the usual tricks. They flashed my phone in the factory (came back wiped) and for some reason this firmware isn't getting the OTA update.
So after persevering with Lollipop (and cracking the display again, and fixing it myself this time) I'm getting Marshmallow one way or another. I just would like to know the best way.
I'd rather keep everything as stock as possible (in terms of bootloaders and rooting) and my current plan was to flash TWRP and try running a MM OTA file. I'm just looking to verify this would work and if so, any pitfalls (future OTAs) or things that could go horribly wrong by doing something idiotic.
I'm on an EU XT1572 so I'm assuming a general EU OTA file will work?
Thanks in advance for any assistance,
Phil
clarkey586 said:
Hi all,
To cut a long story short, around the time MM was being released I cracked my display and broke the digitiser. Before sending the phone off for repair I got the update notification -.- but sent it away without updating as I couldn't accept it. Phone returned and working but no OTA notification, factory reset a few times, sim out and try again, all the usual tricks. They flashed my phone in the factory (came back wiped) and for some reason this firmware isn't getting the OTA update.
So after persevering with Lollipop (and cracking the display again, and fixing it myself this time) I'm getting Marshmallow one way or another. I just would like to know the best way.
I'd rather keep everything as stock as possible (in terms of bootloaders and rooting) and my current plan was to flash TWRP and try running a MM OTA file. I'm just looking to verify this would work and if so, any pitfalls (future OTAs) or things that could go horribly wrong by doing something idiotic.
I'm on an EU XT1572 so I'm assuming a general EU OTA file will work?
Thanks in advance for any assistance,
Phil
Click to expand...
Click to collapse
Easy-peasy.
*NOTE - Using TWRP to flash the OTA.zip IS NOT an option, it WILL fail. You can however use the stock recovery and ADB sideload it.. but the following is how I would probably do it. It's also easier IMO.
I'm assuming your bootloader is unlocked since you were talking about using TWRP so grab the WHOLE 6.0 firmware for your phone (I'm guessing your're RETEU so -> XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml.zip - It's 1.3GB in size) and then reboot the phone into the bootloader (Fastboot mode) and use the files in it to flash everything (this process will wipe the phone so backup anything important first) with fastboot and you will be on a clean completely stock 6.0 with the february patch.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Standalone Fastboot & adb installer - LINK
WHOLE Firmware - LINK
Good luck! If your bootloader is not already unlocked and you don't want to unlock it there is still hope.. it will just be a bit different process by using the OTA zips and the stock recovery.. let me know if you MUST go down this route.. it's a bit more of a PITA IMO.
EDIT* If terminal commands are not your thing you can also try using RSDLite.(Official Moto tool). but I've not personally tried it with my Moto X Pure... I like the terminal
DaMadOne said:
Easy-peasy.
*NOTE - Using TWRP to flash the OTA.zip IS NOT an option, it WILL fail. You can however use the stock recovery and ADB sideload it.. but the following is how I would probably do it. It's also easier IMO.
I'm assuming your bootloader is unlocked since you were talking about using TWRP so grab the WHOLE 6.0 firmware for your phone (I'm guessing your're RETEU so -> XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml.zip - It's 1.3GB in size) and then reboot the phone into the bootloader (Fastboot mode) and use the files in it to flash everything (this process will wipe the phone so backup anything important first) with fastboot and you will be on a clean completely stock 6.0 with the february patch.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Standalone Fastboot & adb installer - LINK
WHOLE Firmware - LINK
Good luck! If your bootloader is not already unlocked and you don't want to unlock it there is still hope.. it will just be a bit different process by using the OTA zips and the stock recovery.. let me know if you MUST go down this route.. it's a bit more of a PITA IMO.
EDIT* If terminal commands are not your thing you can also try using RSDLite.(Official Moto tool). but I've not personally tried it with my Moto X Pure... I like the terminal
Click to expand...
Click to collapse
Thanks a million.
I've not unlocked my bootloader, but I don't think it should be a problem there's plenty of tutorials etc for that.
Ideally, I'd not like to wipe my phone but alas it looks like that's going to be the case and I'll trust your advice rather than looking for a lazy way out haha. Is there any way to back up everything (even just apps, etc) without root though?
Cheers :good:
clarkey586 said:
Thanks a million.
I've not unlocked my bootloader, but I don't think it should be a problem there's plenty of tutorials etc for that.
Ideally, I'd not like to wipe my phone but alas it looks like that's going to be the case and I'll trust your advice rather than looking for a lazy way out haha. Is there any way to back up everything (even just apps, etc) without root though?
Cheers :good:
Click to expand...
Click to collapse
Yea, your warranty is void at this point anyways so why not just unlock it! I root and use TiBu.. so I've not tested other backup methods but I'm pretty sure there are backup apps on the playstore that don't require root you could try.
BUT, the step "fastboot erase userdata" is what erases your installed apps/setting and personal files, etc. Really you can just SKIP that step and you SHOULD be ok. Then your apps and settings will be there when you boot 6.0. I was just providing instructions for a fully clean flash. I would say you have a 98% chance it will be just fine though if you don't erase userdata.
EDIT* oh and IIRC you will probably get an error or weird msg with the gpt.bin part of the flash.. ignore it..
EDIT 2* Here is one such app that doesn't look like it requires root. If you go this route make sure you copy everything over to your PC after using the backup app if you are going to run the "fastboot erase userdata" command.
GOOD LUCK!
---------- Post added at 06:38 PM ---------- Previous post was at 06:07 PM ----------
Just out of curiosity.. I've just read some posts on here about people getting their phones back from repair and their bootloader says "Device is ENGINEERING" instead of "Device is LOCKED" or "Device is UNLOCKED".
What does yours say? I'm mainly just wondering if it being in ENGINEERING mode is why you are not getting the OTA...
DaMadOne said:
Yea, your warranty is void at this point anyways so why not just unlock it! I root and use TiBu.. so I've not tested other backup methods but I'm pretty sure there are backup apps on the playstore that don't require root you could try.
BUT, the step "fastboot erase userdata" is what erases your installed apps/setting and personal files, etc. Really you can just SKIP that step and you SHOULD be ok. Then your apps and settings will be there when you boot 6.0. I was just providing instructions for a fully clean flash. I would say you have a 98% chance it will be just fine though if you don't erase userdata.
EDIT* oh and IIRC you will probably get an error or weird msg with the gpt.bin part of the flash.. ignore it..
EDIT 2* .... is one such app that doesn't look like it requires root. If you go this route make sure you copy everything over to your PC after using the backup app if you are going to run the "fastboot erase userdata" command.
GOOD LUCK!
---------- Post added at 06:38 PM ---------- Previous post was at 06:07 PM ----------
Just out of curiosity.. I've just read some posts on here about people getting their phones back from repair and their bootloader says "Device is ENGINEERING" instead of "Device is LOCKED" or "Device is UNLOCKED".
What does yours say? I'm mainly just wondering if it being in ENGINEERING mode is why you are not getting the OTA...
Click to expand...
Click to collapse
Haha suppose you're right! Sure I'll probably just wipe my device in the end, be nice to have a clean go at MM haha.
The bootloader status was indeed locked so I don't know what's causing the issue?
Anyway, thanks a million for the help I'll update if/when all goes well :good:
Despite my best efforts, it seems to have been in vain. I'm getting an error when trying to unlock the bootloader (something along the lines of no backup available, please try again) which is common to people who have sent their phone in for repair.
I'm just wondering if I could flash the firmware regardless of bootloader (Odin maybe?) At this point I'm happy to root suit and boot I'm just a bit sick of moto at this stage so want to be able to control my phone haha.
Any help much appreciated
clarkey586 said:
Despite my best efforts, it seems to have been in vain. I'm getting an error when trying to unlock the bootloader (something along the lines of no backup available, please try again) which is common to people who have sent their phone in for repair.
I'm just wondering if I could flash the firmware regardless of bootloader (Odin maybe?) At this point I'm happy to root suit and boot I'm just a bit sick of moto at this stage so want to be able to control my phone haha.
Any help much appreciated
Click to expand...
Click to collapse
Odin is for Samsung. Moto has RSDLite. But if your bootloader is locked the firmware package must be signed by Moto and I don't thing the ones floating around the web are.
So this is the point where it seems you're stuck with the (possibly) more PITA way. What you need to do is find the OTA zip that goes from 5.1.1 -> 6.0 and use the stock recovery to flash that with ADB. Boot to stock recovery, press button sequence to get the menu (I THINK at the fallen android dude you hold vol up for a few seconds then hit the power button while still holding it.. it's something like that to get the actual useful menu) then towards the bottom is an update via ADB, plug phone into pc via usb and select that and then in terminal do "adb sideload <OTA_file>.zip" and it will flash the OTA, assuming your device passes it's check it will feel like it's taking forever. This method won't wipe your phone either.
EDIT* HERE is a post with a link to the EU OTA and much better instructions than mine You can flash it with adb sideload or like that post says by copying it to your phone before booting the recovery and flashing it.
And then.. assuming you get to 6.0 using that OTA hopefully you can trigger the february OTA to auto download. If not... HERE is a link to a post with the february OTA zip for your phone. Flash it the same as last one.
If flashing the OTA with a locked bootloader and stock recovery doesn't work I'm afraid you're either stuck or your phone is on a return path to Moto again.
DaMadOne said:
Odin is for Samsung. Moto has RSDLite. But if your bootloader is locked the firmware package must be signed by Moto and I don't thing the ones floating around the web are.
So this is the point where it seems you're stuck with the (possibly) more PITA way. What you need to do is find the OTA zip that goes from 5.1.1 -> 6.0 and use the stock recovery to flash that with ADB. Boot to stock recovery, press button sequence to get the menu (I THINK at the fallen android dude you hold vol up for a few seconds then hit the power button while still holding it.. it's something like that to get the actual useful menu) then towards the bottom is an update via ADB, plug phone into pc via usb and select that and then in terminal do "adb sideload <OTA_file>.zip" and it will flash the OTA, assuming your device passes it's check it will feel like it's taking forever. This method won't wipe your phone either.
EDIT* HERE is a post with a link to the EU OTA and much better instructions than mine You can flash it with adb sideload or like that post says by copying it to your phone before booting the recovery and flashing it.
And then.. assuming you get to 6.0 using that OTA hopefully you can trigger the february OTA to auto download. If not... HERE is a link to a post with the february OTA zip for your phone. Flash it the same as last one.
If flashing the OTA with a locked bootloader and stock recovery doesn't work I'm afraid you're either stuck or your phone is on a return path to Moto again.
Click to expand...
Click to collapse
Ah sure I'll give that a go! Just checking if there are any precautions I should be taking for this? Don't want to brick the phone without the ability to flash it back to life again!
clarkey586 said:
Ah sure I'll give that a go! Just checking if there are any precautions I should be taking for this? Don't want to brick the phone without the ability to flash it back to life again!
Click to expand...
Click to collapse
You should be fine. The OTA zip is going to check all of the files it is going to patch first and only upgrade if everything passes. If it finds ANYTHING amiss... it will refuse to flash it. If it refuses to flash it your only hope is to send it to Moto unfortunately.
DaMadOne said:
You should be fine. The OTA zip is going to check all of the files it is going to patch first and only upgrade if everything passes. If it finds ANYTHING amiss... it will refuse to flash it. If it refuses to flash it your only hope is to send it to Moto unfortunately.
Click to expand...
Click to collapse
You, my friend, are a hero.
That seems to have done the trick with no issues (going to see if I can potentially unlock the bootloader now) and I'm finally on MM haha. Seems I have to perform the Feb security update separately too for some reason but I'm not too worried about doing things manually.
Sent you a small token of my appreciation, have a pint on me
Thanks once again
clarkey586 said:
You, my friend, are a hero.
That seems to have done the trick with no issues (going to see if I can potentially unlock the bootloader now) and I'm finally on MM haha. Seems I have to perform the Feb security update separately too for some reason but I'm not too worried about doing things manually.
Sent you a small token of my appreciation, have a pint on me
Thanks once again
Click to expand...
Click to collapse
Sweet! Thanks for the pint! Glad you're updated now. Did it end up giving you the OTA for the February patch or did you have to use the 2nd OTA?
DaMadOne said:
Sweet! Thanks for the pint! Glad you're updated now. Did it end up giving you the OTA for the February patch or did you have to use the 2nd OTA?
Click to expand...
Click to collapse
Had to use the 2nd OTA.zip but I didn't really try any of the remove sim card stuff or waiting long. No unlockable bootloader either but I'm satisfied for the moment haha.

FYI: recovered G5 XT 1676 to stock and updated. :)

Just an FYI type thing that may save people a bit of digging around sometime.
I tried to get the update that just came out, but as i had TWRP as recovery, no good. Anyhow, in my trying i completely bollixed the phone. Would start, but always booted to TWRP and had various conniptions. Could not even get a TWRP backup to load. Strange not encountered before by me stuff............
Anyhow, recovered by the following method to stock and am back in business.
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Not my own work, adapted from this thread by t-bon3
https://forum.xda-developers.com/showthread.php?t=2542219
which I found thanks to eens post18 at this thread
https://forum.xda-developers.com/g5/how-to/npp25-137-33-stock-firmware-moto-g5-t3577084/page2
After this, Motorola system update installed. On Australian XT1676 is build number NPP25.137-15-7
Patch level 1-May-2017
Still get the I cant be trusted page on power up as have unlocked bootloader.
Many thanks to all at XDA, its a resource that can certainly get you into trouble, but then out of it again.
where do you get the stock firmware?
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
We're you able to revert to a locked bootloader after this, I am looking forward to do so
We're you able to revert to a locked bootloader after this, I am looking forward to do so
Click to expand...
Click to collapse
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.
astmacca said:
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.
Click to expand...
Click to collapse
I can confirm what you said, but I am asking because I am sick of the warning before the device starts
ap4ss3rby said:
I can confirm what you said, but I am asking because I am sick of the warning before the device starts
Click to expand...
Click to collapse
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
TheFixItMan said:
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
Click to expand...
Click to collapse
Thanks, but this is why I made a Google pixel themed logo.bin and used a matching boot animation to go with it some time earlier
downgrade
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance
distclean said:
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance
Click to expand...
Click to collapse
No you cannot downgrade (same firmware version or newer required)
Yes - unlocked bootloader not required
As long as your phone still goes into the bootloader
You should flash all sparsechunks in number order
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
You maybe able to - there are different variants of the same phone
As long as the firmware is the same or newer (as in the bootloader and API version) it may flash
It will either flash or error out
There's only one way to find out - if your phone is dead anyway it's not going to make alot of difference
No - generally you can never downgrade firmware - doing so would be dangerous and you may loose the bootloader for good
thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.
distclean said:
thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.
Click to expand...
Click to collapse
You can write in adb
Code:
adb shell
cat /proc
cat /proc/partitions
Hello,
Does anyone know where can I download the latest firmware for Moto G5 XT1676 baseband Version: m8937_ 8000.122.02.40 R
Thanks
astmacca said:
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Click to expand...
Click to collapse
You're partially right. These commands won't work for our files. You have to flash the firmware according to the instructions contained within the "flashfile.xml" file within the archive. For example we have no "motoboot" partition
I've flashed every stock package available now (4 I think) and haven't been offered an update once. I've ran a couple of custom ROMs but they're just not right in one way or another. Might be time to move on.
distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
I upgraded to this and since then can't downgrade the phone to the stock roms available online. From memory trying to flash gpt.bin gave a "Security version downgrade" error. So I wouldn't assume you'll be able to downgrade and until there is a copy of this particular firmware, you won't be able to flash back or relock the bootloader
astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Is this ROM is good to my XT1676 Baseband: M8937_11.16.02.51R ?
astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Hi, i own the same model of moto g5, i do this in fastboot window
fastboot erase userdata
now the phone only boot in twrp and show a message "failed to mount /data". i think that delete my userdata partition, how could i fix it?
once i can avoid this loop in twrp, i follow these steps to flash stock rom
thanks in advance
juan

8T on OOS A12 - C.16 Recovery with ADB Enabled

Tested on my own KB2003, work flawlessly. Useful for many cases.
I followed the GUIDE of @s3axel here : https://forum.xda-developers.com/t/...n-os-stock-recovery-with-adb-enabled.4084487/
All credits to him.
Basically, this modded Recovery just saved my a** )))) Just unzip using 7z then flash it to Recovery as normal.
LinhBT said:
Tested on my own KB2003, work flawlessly. Useful for many cases.
I followed the GUIDE of @s3axel here : https://forum.xda-developers.com/t/...n-os-stock-recovery-with-adb-enabled.4084487/
All credits to him.
Basically, this modded Recovery just saved my a** )))) Just unzip using 7z then flash it to Recovery as normal.
Click to expand...
Click to collapse
Can you share your file?
Rootk1t said:
Can you share your file?
Click to expand...
Click to collapse
Sure man, find attachment
Hi, I am facing a strange issue on OOS12 not able to factory reset or enter stock recovery it says boot/recovery.img damaged flash the correct one or contact support can any one help me out with this issue.
houstontaxi said:
Hi, I am facing a strange issue on OOS12 not able to factory reset or enter stock recovery it says boot/recovery.img damaged flash the correct one or contact support can any one help me out with this issue.
Click to expand...
Click to collapse
unpack your firmware, extract stock recovery.img and flash it.
But for flashing do I need to unlock bootloader or it can be done without unlocking?
houstontaxi said:
But for flashing do I need to unlock bootloader or it can be done without unlocking?
Click to expand...
Click to collapse
As far as i remember to flash partitions with stock firmware you don't need unlocked bootloader.
Rootk1t said:
As far as i remember to flash partitions with stock firmware you don't need unlocked bootloader.
Click to expand...
Click to collapse
If it needs to flash recovery the same way as we do for custom roms like fastboot flash recovery in platform tools then i tried that doesn't work to make it work bootloader needs to be unlocked I did that(unlocked the boot loader) then flashed stock recovery and it worked but after locking the boot loader with fastboot oem lock same issue happened again couldn't boot into recovery.
houstontaxi said:
But for flashing do I need to unlock bootloader or it can be done without unlocking?
Click to expand...
Click to collapse
To flash ANY partitions, u must unlock bootloader even if the partition is critical or not. And to prevent the boot/recovery image damaged error, u must flash stock boot/recovery images along with vbmeta.img ( also extracted from stock, same build ).
LinhBT said:
To flash ANY partitions, u must unlock bootloader even if the partition is critical or not. And to prevent the boot/recovery image damaged error, u must flash stock boot/recovery images along with vbmeta.img ( also extracted from stock, same build ).
Click to expand...
Click to collapse
I'm gonna try this also need to know if I have to flash boot.img and recovery.img as there are two files when extracted from the stock rom
houstontaxi said:
I'm gonna try this also need to know if I have to flash boot.img and recovery.img as there are two files when extracted from the stock rom
Click to expand...
Click to collapse
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
LinhBT said:
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
Click to expand...
Click to collapse
I'm gonna try that thanks for the help and I hope it resolves my issue with OOS A12 recovery as I don't face this kind of issue on OOS11
1
LinhBT said:
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
Click to expand...
Click to collapse
Hello, tell me that your recovery cannot decrypt the date section? I need to extract data from the phone, the phone won't boot into the system, I tried to boot into your recovery but I can't access the folders.
lenox30 said:
Hello, tell me that your recovery cannot decrypt the date section? I need to extract data from the phone, the phone won't boot into the system, I tried to boot into your recovery but I can't access the folders.
Click to expand...
Click to collapse
This is simply Stock Recovery with ADB enabled bro. It only can help u in some tasks which need to access adb via Recovery, it won't help to decrypt ur device and/or have any functions as other custom recovery

Categories

Resources