Hello, how are you? My Name Is Cristian and I'm from Argentina.
I've had a Moto G5 for a while and a lot of custom roms were installed on it. However, there were many problems in the process. The roms had bugs, performance issues, and some didn't even boot.
So i made the decision to go back to the factory rom and close the bootloader forever. But it couldn't. Something prevented it. Something was causing the phone to not start properly.
Therefore, after doing so many laps, i was able to do the whole process.
And today i publish this topic so that you can do it too. I hope you can come out triumphant in the process just like me. Have lucky!
1) The first thing you should do is download Rescue & Smart assistant. Install on your pc and create account (if you not) or login in.
Code:
https://support.lenovo.com/es/es/downloads/DS101291
2) You will need to find the official firmware of your device. Search for the exact device SKU (model of your phone) and exact region. For example the SKU of my device is XT1670 the region is RETAR (from Argentina). If you are from United States (and try to install RETAR) Rescue & Smart assistant will not recognize the SKU of your device, and will not be able to continue.
Find the exact firmware corresponding to your mobile phone.
Code:
https://mirrors.lolinet.com/firmware/moto/cedric/official/
Unzip the rom in the place that you prefer.
3) Now put your device in bootloader mode and execute the following commands (ignoring any errors in the process)
Code:
fastboot oem fb_mode_set
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 dsp adspso.bin
fastboot flash oem oem.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 erase cache
fastboot erase userdata
fastboot reboot
4) Once the above process is finished, start your phone normally. Go to the developer options and activate usb debugging. Plug the phone into PC.
Open "Rescue & Smart assistant" and accept usb debugging on your phone. The app installs some control app, dont worry.
Go to Rescue & Smart assistant and select "Rescue". The program will recognize your phone's SKU if you downloaded the correct firmware. Otherwise, if a wrong sign appears, you will have to repeat step 2 and 3 with the correct firmware.
Click on "Rescue now" and the program will download the firmware corresponding to your phone. After this, the firmware installation will begin.
Why do all this process?
The Rescue & Smart app is official from Motorola. When the official firmware is installed, the signed firmware files are also installed with it. The firmware is official because is delivered directly by Motorola, specifically for your mobile phone, and not by unofficial sites.
5) Hey, wait! the bootloader needs to be blocked. True.
Go to C:\ProgramData\LMSA\Download\RomFiles and you will find there the official rom downloaded by "Rescue & Smart". This rom is unique, signed and official. Only for your phone, only for its hardware. Do not lose it. It will save your ass from many inconveniences, if one day you want to continue experimenting with your phone.
Copy the whole directory in other site and open cmd in it. Now shutdown your phone and start it in bootloader mode.
Now put these commands (ignoring bla bla bla errors):
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 boot boot.img
fastboot oem lock
And that's it. Your mobile phone is now official and with its bootloader locked. almost factory-made.
So thank you for reading all this and I hope the information has served you a lot. Any questions about it (about this) do not hesitate to consult.
Great post and thanks for taking the time to post it :good:
For people who might struggle with this I've used Moto Auto Flash Tool v8.2 By Jamesjerss.rar with great success,
https://www.ytechb.com/moto-auto-flash-tool/
Takes a lot of the hard work out of it :good:
R1ffR4ff said:
Great post and thanks for taking the time to post it :good:
For people who might struggle with this I've used Moto Auto Flash Tool v8.2 By Jamesjerss.rar with great success,
https://www.ytechb.com/moto-auto-flash-tool/
Takes a lot of the hard work out of it :good:
Click to expand...
Click to collapse
The reason i made this post was mainly because a lot of people have problems with unsigned firmware and cannot follow normal recovery processes. However, I will consider this application for future experiments. It seems to be an application that already has the commands prepared, so there are no errors. The problem is that it does not offer the official firmware (from Motorola) directly for the specific device. Anyway it is good not to make mistakes in the commands.
Ty.
He.Art said:
The reason i made this post was mainly because a lot of people have problems with unsigned firmware and cannot follow normal recovery processes. However, I will consider this application for future experiments. It seems to be an application that already has the commands prepared, so there are no errors. The problem is that it does not offer the official firmware (from Motorola) directly for the specific device. Anyway it is good not to make mistakes in the commands.
Ty.
Click to expand...
Click to collapse
It's a great little program that I had to use Yesterday on a Moto G3 as the normal ADB way as per your post wouldn't work for whatever reason and I've used ADB loads
I was my own fault on that phone as I,"Soft Bricked" it using the latest version Magisk uninstall option so NEVER use this option in Magisk. I returned the phone to Stock and then upgraded it to my favourite Custom roms
Related
Hello all,
I'm a bit confused about the process of taking my current '3' ROM and changing it to the official Lenovo Rom.
I have downloaded the lenovo drivers (installed and ok) phone is in debug mode.
I have downloaded the stock rom from here: https://forum.xda-developers.com/lenovo-p2/development/7-0-lenovo-p2a42-stock-nougat-update-t3581517 and have adb / fastboot.
I know I have to use the volume rocker and powerbutton to get into the boot mode but I don't know the commands for adb or fastboot. I have changed the name of the rom to 'update'
Can someone please advise me on the commands I am meant to enter to get this onto my phone please?
Thanks in advance,
Cue
Copy all the code below, paste it to a new text file on your PC and save it as All Files instead of .txt and name it a fastboot.bat. Place the fastboot.bat in the adb/fastboot directory, also place the unpacked rom in the same path. Run it as admin. Profit.
Code:
fastboot flash partition gpt_both0.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash system systemchunk0.img
fastboot flash system systemchunk1.img
fastboot flash system systemchunk2.img
fastboot flash system systemchunk3.img
fastboot flash system systemchunk4.img
fastboot flash system systemchunk5.img
fastboot flash system systemchunk6.img
fastboot flash system systemchunk7.img
fastboot flash system systemchunk8.img
fastboot flash system systemchunk9.img
fastboot flash system systemchunk10.img
fastboot flash system systemchunk11.img
fastboot flash system systemchunk12.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo pause
Hi, op here.
Firstly, thank you for responding! Your instructions seem very clear. When i had a look at the contents of the ROM (in zip) i couldn't see any of the systemchunk files you mention, are they hidden deep somewhere?
Regards,
Cue.
If your phone is stock the Rom can be updated without fastboot or a PC.
All the instructions are in that thread.
Huh. Surely just boot into recovery and install the update.zip? No need to have it connected to pc.
Hello all,
Yep. I un-encrypted the sd card copied the zip onto it and booted up that way. Very easy. Now running stock directly from Lenovo which I am very happy about! It also pushed the new 78mb update as well.
Thank you for all your input.
same way i did it too theirs no need to do it through fastboot method just like the other people i did it through the built in recovery by renaming the Nougat rom to update.zip works fine and you will get another update ota straight after t obring it right up to date.
Sounds like you guys have this sorted :highfive:
Just for completeness, can somebody upload the original 3 rom? It just helps out the person who thinks they have a hardware issue and may need to return the phone to 3.
If you try and return your phone and it doesn't have the original 3 rom, your chances of a good outcome are obviously less as you have tampered with the phone etc.
The warranty is with Lenovo Not three.
Doubt there'd be an issue as the bootloader will still be locked and it's an official Lenovo Firmware.
Since flashing nougat and a factory wipe my VOLTE is now working.
I did the same flashed nougat and volte is working but only shows up some times not as much as I'd like is their any way to get volte to work more often. In my bedroom where the signal is weak I don't get the volte symbol at all.
philje123 said:
The warranty is with Lenovo Not three.
Doubt there'd be an issue as the bootloader will still be locked and it's an official Lenovo Firmware.
Since flashing nougat and a factory wipe my VOLTE is now working.
Click to expand...
Click to collapse
How you enabled VoLte on nougat? You are on stock rom or branded?
I'm on stock unbranded.
VOLTE settings now show up in phone menu and it just works. I had to factory reset though as initially it didn't work after flashing nougat.
How to go from Lineage OS 14.1 to stock? (Updated with the process & latest links)
I am currently on lineage OS 14.1 (7.1.2) dated 18.09.2017.
I want to go back to stock firmware as I am facing some issues with lineage.
How to find the latest firmware. Found this website which has all the images https://firmware.center/firmware/Motorola/Moto Z Play/Stock/XT1635-02/
But I am unable to select the correct one for my device. (do not want to brick it). Also found another thread stating latest firmware
https://forum.xda-developers.com/moto-z-play/help/addisonnpns26-118-22-1cid50subsidy-t3675521
I am an Indian MOTO Z Play
Is there a way to go full stock and also start to receive OTA updates. Can someone provide me with full guide with links?
First you need exactly your software channel and the build of your baseband and bootloader. You know how to get this information?
After a lot of tries, finally was able to go back to stock. Will be compiling a guide for other to follow with links.
On latest 7.1.1 with August patches.
Is there a problem with audio fx,
Even viper4android not working.
kkube said:
After a lot of tries, finally was able to go back to stock. Will be compiling a guide for other to follow with links.
On latest 7.1.1 with August patches.
Is there a problem with audio fx,
Even viper4android not working.
Click to expand...
Click to collapse
I'll be waiting for it.
Process to go from custom rom back to stock (August update)
There are several guides on going back from custom rom to full stock, but still I made this guide with latest links. I just went from LOS 14.1 back to full stock. Below is the step I took:
1) Download and install minimal ADB AND FASTBOOT
I used version 1.4.2 which is the latest version https://www.androidfilehost.com/?fid=745425885120698566
2) Download and install motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
3) Download the latest firmware
I used ADDISON_NPNS26.118-22-1 which has august security updates https://www.androidfilehost.com/?fid=673368273298986785
4) Extract the zip file (firmware) and move all its contents to the folder where you have installed minimal adb and fastboot
5) Create a text file, add the following text to it and save it as "launch.bat" in the same folder.
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
Click to expand...
Click to collapse
6) Switch off your phone and open it in fastboot mode (press power and volume down button for few seconds after phone as switched off)
7) Connect your mobile to your computer
8) Click on the launch.bat file that you saved and it will install stock firmware on to your mobile. It will take a couple of minutes. (It will wipe everything on your mobile so take a backup of your important data)
9) Once the process is complete, it will ask you to enter any key, after which it will reboot itself.
Once rebooted, you will have full stock, non rooted, and latest firmware with august patches.
Is this works with European version of Moto Z Play? Like I bought it from France. Thanks.
And can we do OTA updates after doing this?
Thank you so much for this guide, my phone was rebooting to recovery every single time and nothing worked. I flashed this rom as you said and my phone just booted and it's working. I can't believe it.
Is this works with European version of Moto Z Play? Like I bought it from France. Thanks.
Click to expand...
Click to collapse
My phone is reteu and after flashing is still on reteu, so it should be fine, dont worry. Also you should get any future updates via OTA.
kkube said:
There are several guides on going back from custom rom to full stock, but still I made this guide with latest links. I just went from LOS 14.1 back to full stock. Below is the step I took:
1) Download and install minimal ADB AND FASTBOOT
I used version 1.4.2 which is the latest version https://www.androidfilehost.com/?fid=745425885120698566
2) Download and install motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
3) Download the latest firmware
I used ADDISON_NPNS26.118-22-1 which has august security updates https://www.androidfilehost.com/?fid=673368273298986785
4) Extract the zip file (firmware) and move all its contents to the folder where you have installed minimal adb and fastboot
5) Create a text file, add the following text to it and save it as "launch.bat" in the same folder.
6) Switch off your phone and open it in fastboot mode (press power and volume down button for few seconds after phone as switched off)
7) Connect your mobile to your computer
8) Click on the launch.bat file that you saved and it will install stock firmware on to your mobile. It will take a couple of minutes. (It will wipe everything on your mobile so take a backup of your important data)
9) Once the process is complete, it will ask you to enter any key, after which it will reboot itself.
Once rebooted, you will have full stock, non rooted, and latest firmware with august patches.
Click to expand...
Click to collapse
Thanks a lot for this guide! Just wanted to ask if it's safe and stable to root this and pass safetynet check.
Thanks for you time
Only way to root and still pass safetynet is via magisk
But unfortunately it needs a custom kernel with f2fs fix. However with 7.1 update motorola fixed it but broke some other things.
There is not a custom kernel for 7.1, so till then no way to root and have safety net.
But you can easily root via magisk
akshaypatil869 said:
Thanks a lot for this guide! Just wanted to ask if it's safe and stable to root this and pass safetynet check.
Thanks for you time
Click to expand...
Click to collapse
Only way to root and still pass safetynet is via magisk
But unfortunately it needs a custom kernel with f2fs fix. However with 7.1 update motorola fixed it but broke some other things.
There is not a custom kernel for 7.1, so till then no way to root and have safety net.
But you can easily root via magisk
Does anyone receive the update with September patch via OTA after back to stock following post #5 instructions?
This a fantastic guide - THANKS!!! - I have linked to it giving credit. Thanks!
I have also a thread, if you follow that one. Bootloader is locked/ u will be able to get ota'$
My friend let me have his Gold Z2 Force for around $50 since my phone broke. He never used it, like new condition. Sweet.
Anyway, I am on verizon, he's on sprint so it's the Sprint Variant. I was searching around before I bought it, and I heard that I could unlock the bootloader for this specific model of the phone as opposed to the Verizon one which has a locked down bootloader. This is great, since I would want to root it.
Here is my question, after looking around it doesn't seem that I can get a clear answer. Would I be able to unlock the bootloader and install TWRP, and flash the verizon firmware onto the phone? I've already checked, the LTE bands are supported (Bands 2,4 and 13 along with the now legacy af CDMA fallback that is probably dead.).
I know you can use the Sprint version, on Verizon as it is, so even if I can't do all of this I can still use it with no issues, which is a plus.
Edit, steps further down below
I've got a Razr HD (XT925). After unlocking the bootloader, I could flash the Verizon fw to it. Flash a variant fw to an another unlocked-bootloader one (cross-flash) is capable. I cannot unlock my ATT one so I dont know exactly. I can only guess. Dont try to kill your phone :"(
mr_5kool said:
I've got a Razr HD (XT925). After unlocking the bootloader, I could flash the Verizon fw to it. Flash a variant fw to an another unlocked-bootloader one (cross-flash) is capable. I cannot unlock my ATT one so I dont know exactly. I can only guess. Dont try to kill your phone :"(
Click to expand...
Click to collapse
I'll try not to, lol.
That said, I either suck at finding it or just can't find it, but would you be able to point me towards where I could find the Verizon FW for the Z2 Force? I've tried searching but can't find it.
KOAO said:
I'll try not to, lol.
That said, I either suck at finding it or just can't find it, but would you be able to point me towards where I could find the Verizon FW for the Z2 Force? I've tried searching but can't find it.
Click to expand...
Click to collapse
Here you are
https://mirrors.lolinet.com/firmware/moto/nash/official/VZW/
mr_5kool said:
Here you are
https://mirrors.lolinet.com/firmware/moto/nash/official/VZW/
Click to expand...
Click to collapse
Alright, thanks!
OP - were you able to flash verizon fw on sprint z2 force?
dementor123 said:
OP - were you able to flash verizon fw on sprint z2 force?
Click to expand...
Click to collapse
Actually, shockingly, yes. I was. And it works. I did **** up the first few tries through trial and error, but currently I am using the Sprint Z2 Force on Verizon, running Verizon firmware with everything running. Glitches and all the same from a Z2 Force that would come with Verizon. Hell, you even get their bloat! Truly the Verizon Experience with the addition of Root and an Unlocked bootloader.
Doing this, I'd assume you have sim unlocked it and unlocked the Bootloader of your Z2 Force . Also note that this wipes EVERYTHING, SO BACK UP.
Also note that considering I was stunned when it worked, it's possible I missed a step while writing this up so again, have a window of time to be free. And a backup phone of possible.
The way I did it, is first prepping to have a few hours of your time because it could take a while. Set up like 2 or so hours where no one is going to call you on your phone since you'll need your Sim in the Z2 in case anything goes wrong.
Then, you need to download the latest Verizon Z2 Force Firmware. You don't have to technically do this, but updating is going to be a pain since you aren't going to be allowed to take OTA's (more on that later.) So just get the one with the January Security Patch as that is the most recent one
Here is the Verizon Firmware. Just sort by date to the most recent one for this year, there is only one lol.
https://mirrors.lolinet.com/firmware/moto/nash/official/VZW/
Next is download the flashall utility. You aren't going to use the flashall.bat, but adb is in there. Extract the Verizon firmware into that flash all folder. From there, assuming you have adb debugging and all, boot into the bootloader.
Once you have everything prepped, follow this guide here. The first one, with wipe
https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-flash-update-stock-rom-t3838213
But, if you don't want to open another tab, here are the instructions. There is an important thing to note. The Verizon Firmware has it's OEM in 2 chunks, as opposed to the single .img file the others do. In this case you would run the fastboot oem, drag oem chunk 0 into cmd and run it, then run fastboot oem again and do the same for oem chunk 1 from the folder you are performing everything from. I also think we are missing sparsechunks 6-10, so just follow the steps for what files you have and ignore the ones you don't. We also have system sparse chunk b's, two files, to flash as well. We seem to have a few files others don't.
Run these commands one by one.
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
fastboot erase cache
fastboot erase carrier
fastboot erase ddr
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Do not forget to run fastboot oem fb_mode_clear, otherwise you will boot into fastboot at every reboot.
After that, everything should be working. It worked for me I'll try to help if anything goes wrong but I hope that doesn't happen.
That said, an important note about updates and OTA's. Our Z2 Force is not a real Verizon Z2 Force. Something internally, most likely the fact it's not certified and is the same reason it doesn't show up in Verizon's site as an offical Z2 Force, is the reason we cannot take OTA's. If an Update were to come out for our phone, we would need to download the latest firmware. Once someone can get the latest OTA from Verizon for us, we then have to use the same ADB method to update our devices.
The steps for updating without deleting data are in the link to the thread above, but here are the commands for doing so without wiping data. Again, reminder that our flash oem is in two chunks, And we don't have sparsechunks 6-10.
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
fastboot erase cache
fastboot erase carrier
fastboot oem fb_mode_clear
fastboot reboot
Again, do not forget to run fastboot oem fb_mode_clear. I cannot stress this enough because I nearly said "**** this ****" because of this simple command that I forgot to copy in. This is what puts our phone into it's state to flash firmware. So disable it once you are done.
I would assume that this would also work for flashing the Sprint to a true unlocked version. I was tempted to test it, since the unlocked retail versions get updates first and are already on the latest March Security patch. But, I was stopped because I could not find the retail firmware anywhere. The link for the retail in this thread 404'd, so this is the next best thing.
I did encounter an anomaly once everything was said and done. The phone app wasn't showing up once I had all my apps set up. I had to find it, clear the cache, and for good measure disabled and re-enabled it and it never disappeared/stopped responding again. I did end up using Magisk to install the Google Dialer framework and am using that with no issues. Aside the issue that I can't download it from the playstore, so I had to download it from a reputable site.
Note that I never had sprint service on it, so anything related to that or battery life on the sprint rom is something I have no clue about. But, I seem to get very good battery life on it.
I posted some screen shots below.
Just trying to understand something. Does verizon block sprint phones via a whitelist or via firmware?
benphillipstn said:
Just trying to understand something. Does verizon block sprint phones via a whitelist or via firmware?
Click to expand...
Click to collapse
I'm not sure, it might be the Whitelist. Since if you check your MyVerizon account it still doesn't believe its a Z2 Force. The phone's guts are the same but not all the IMEI numbers are registered.
Here are the VZW firmware. Android 9.0 1/31/2020 appears to be the most recent:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Hi everyone,
I bought a Motorola G6 play model XT1922-3 type 374B and wanted root acces on this device.
So I started by succesfully unlocking my bootloader using the following tutorial.
After this a started tried to root the device using this tutorial.
This tutorial doesn't link to boot images anymore so I was able to find the moto-g6-play-jeter-patched-twrp.img somewhere else.
I did the following things:
- reboot to bootloader [Succesfull]
- fastboot boot moto-g6-play-jeter-patched-twrp.img [Unsuccesfull]
The device did boot the twrp image but I was unable to interact with it in any way. I couldn't swipe or press buttons.
I made a short video to show this.
I wanted to retry the whole thing so I did reboot to bootloader but then I accidently entered the following command:
fastboot flash boot moto-g6-play-jeter-patched-twrp.img picture of command prompt
After this I wasn't able to normally boot my device. When I try to do so the screen goes black and says n/a in the left corner.
Please does anyone know how I could either be able to boot my normal stock rom again or to have a rooted rom?
Kind regards Sven Onderbeke
Hi Sven,
This isn't going to be the most advanced reply, as I'm not very experienced with this stuff either, but it seems you have accidentally flashed your twrp image to 'boot', wherever that is, which is why the phone isn't able to boot to system.
Can you still boot into bootloader and recovery (twrp)?
If so, then I'd suggest using fastboot to flash a sock or custom ROM. I'm not sure exactly which one though, you have basically the same model as me and that seems to use the JETER ROMS a list of which are over here (can't post links yet, so you will just have to search on mirrors . lolnet . com /firmware/moto/jeter/official/ or remove the spaces
I seem to have somehow lost the partitions on mine, but will start a new thread question about that.
Sven Onderbeke said:
Hi everyone,
I bought a Motorola G6 play model XT1922-3 type 374B and wanted root acces on this device.
So I started by succesfully unlocking my bootloader using the following tutorial.
After this a started tried to root the device using this tutorial.
This tutorial doesn't link to boot images anymore so I was able to find the moto-g6-play-jeter-patched-twrp.img somewhere else.
I did the following things:
- reboot to bootloader [Succesfull]
- fastboot boot moto-g6-play-jeter-patched-twrp.img [Unsuccesfull]
The device did boot the twrp image but I was unable to interact with it in any way. I couldn't swipe or press buttons.
I made a short video to show this.
I wanted to retry the whole thing so I did reboot to bootloader but then I accidently entered the following command:
fastboot flash boot moto-g6-play-jeter-patched-twrp.imgpicture of command prompt
After this I wasn't able to normally boot my device. When I try to do so the screen goes black and says n/a in the left corner.
Please does anyone know how I could either be able to boot my normal stock rom again or to have a rooted rom?
Kind regards Sven Onderbeke
Click to expand...
Click to collapse
Just flash a stock boot.img to boot. Then just flash TWRP to recovery. In TWRP, format data. Type yes. Then reboot recovery. Then Use TWRP to flash magisk. Done.
Hi again Sven,
I just wanted to let you know that I just downloaded the following RETAIL ROM
ALJETER_RETAIL_9.0_PPPS29.55-35-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
and used the following fastboot commands, one at a time.
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.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 oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Which rebooted into bootloader so pressed "start" and all booted fine now. It looks like we have the same device, so hopefully that will work for you too.
Hello people! I hope you are well
First of all, sorry if the English I write with is not good, I am using Google translator (I am from Argentina)
I want to ask for your help (and I apologize in advance if this is not the correct section, it is my first post)
I have a motorola moto G5 xt1670 which restarts without stopping. I tell you; Friday it started with constant reboots and it did not allow me to use the device correctly. On Saturday morning I reinstalled the operating system (android 8.1 stock) using ADB and fastboot commands, so far so great. I walked for a couple of hours correctly, however, after a few hours the phone restarts and stays in a kind of Bootloop which I can NOT remove. It restarts 5 or 6 times in a row, once it is turned on, I can use it for no more than 5 minutes and it restarts again and so on.
I tried installing the operating system through fastboot, through recovery, I did a thousand wipes, from the same recovery I tried to repair the files, I deleted the original rom and I tried installing an alternative rom (lineage OS and pixel experience), and I can swear that the phone does not rips me off.
In fact, after installing pixel experience, the cell phone sends me a message that says the following: "Android system, there is an internal problem with your device, contact the manufacturer for instructions"
The truth is that I don't know what to try now, reinstall the stock firmware more than 5 times, try to downgrade, and the same thing happens. The phone passes the initial configuration, I move it for two minutes on the desktop and it restarts without end.
If anyone has an idea what it might be, I would greatly appreciate your help!
Thank you!
The message you get on pixel experience about an internal problem contact the manufacturer is normal - this is because the system and vendor fingerprint do not match in a hack to pass safetynet
Anyway going back to your problem
If you have downloaded firmware from
https://mirrors.lolinet.com/firmware/moto/cedric/official/
I recommend using the latest retail version
And installed it using these commands in order
Code:
fastboot oem fb_mode_set
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 dsp adspso.bin
fastboot flash oem oem.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 oem fb_mode_clear
fastboot reboot
Without any errors (eg validation error security downgrade error etc)
Then you may have a hardware fault - anything from the battery to the main board or other components
Take it to a repair shop for testing
You can also run an adb logcat but this has to be running at the exact moment the reboot happens & it may show why the phone the restarted
And remove the sdcard if you have one inserted or format it to make sure it's not causing any issues