Dear All,
I was on Validus rom 8.10 r4, then i decided to sell the phone and go back to stock and relock bootloader.
I use the toolkit of Motorola Moto G5+ Toolkit.
I flashed and everything went good. Restarted and I can't access to my network.
I have the Amazon version Italian.
Xt1685 Retail...
please help me
tufoz said:
Dear All,
I was on Validus rom 8.10 r4, then i decided to sell the phone and go back to stock and relock bootloader.
I use the toolkit of Motorola Moto G5+ Toolkit.
I flashed and everything went good. Restarted and I can't access to my network.
I have the Amazon version Italian.
Xt1685 Retail...
please help me
Click to expand...
Click to collapse
You have an XT1685 Retail Italian version... Or a Amazon ad supported version? It can't be both, the fact you may have purchased it from Amazon it not relevant.
That aside... 99% chance the radio firmware did not flash correctly. Reflash the ROM manually and watch each step for a failure, if any piece fails, repeat it up to 3 times before continuing (radio firmware often requires 2 or sometimes 3 attempts to flash properly).
acejavelin said:
You have an XT1685 Retail Italian version... Or a Amazon ad supported version? It can't be both, the fact you may have purchased it from Amazon it not relevant.
That aside... 99% chance the radio firmware did not flash correctly. Reflash the ROM manually and watch each step for a failure, if any piece fails, repeat it up to 3 times before continuing (radio firmware often requires 2 or sometimes 3 attempts to flash properly).
Click to expand...
Click to collapse
https://s17.postimg.org/l8pargixr/P1040621.jpg
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so what firmware do you suggest?
I used this procedure and one step fails.. i will do it again...
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 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
fastboot oem fb_mode_clear
fastboot reboot
tufoz said:
so what firmware do you suggest?
Click to expand...
Click to collapse
Retail Italian, whatever is current... Your missing the point though, you need to flash it manually because the most likely case is the radio firmware (NON-HLOS and fsg.mbn) didn't take correctly.
acejavelin said:
Retail Italian, whatever is current... Your missing the point though, you need to flash it manually because the most likely case is the radio firmware (NON-HLOS and fsg.mbn) didn't take correctly.
Click to expand...
Click to collapse
Thanks sir...
I will do it...
So I will pick this one: "POTTER_RETAIL_7.0_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" Agreed ?
tufoz said:
Thanks sir...
I will do it...
So I will pick this one: "POTTER_RETAIL_7.0_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" Agreed ?
Click to expand...
Click to collapse
That firmware appears to be for US devices, which firmware did you lock your device with?
As far as I know, retail EU (software channel retEU) device firmware is up to NPNS25.137-33-11 . I do not know if the npn25.137-92 firmware is suitable for EU devices.
echo92 said:
That firmware appears to be for US devices, which firmware did you lock your device with?
As far as I know, retail EU (software channel retEU) device firmware is up to NPNS25.137-33-11 . I do not know if the npn25.137-92 firmware is suitable for EU devices.
Click to expand...
Click to collapse
edit..
everything went good but still no netw access..
i can see the list of the network but if i try to log in .. it fails..
tufoz said:
edit..
everything went good but still no netw access..
i can see the list of the network but if i try to log in .. it fails..
Click to expand...
Click to collapse
Hmm, is the the Wi-Fi network or the SIM/telephone network you're trying to access?
If the SIM/telephone network, check your mobile APNs are set correctly, and check if the SIM is working in another device (to verify it's not the SIM at fault).
echo92 said:
Hmm, is the the Wi-Fi network or the SIM/telephone network you're trying to access?
If the SIM/telephone network, check your mobile APNs are set correctly, and check if the SIM is working in another device (to verify it's not the SIM at fault).
Click to expand...
Click to collapse
mobile career network...
I done this: returned to stock and the carrier doens't work
Flashed Validus and it doesn't work
But If i Flash omnirom it starts to work.. and then i can flash validus over omnirom to let it work.... very strange!
so what does Ominrom has in order to let it work? Omni rom is the turning point..
tufoz said:
mobile career network...
I done this: returned to stock and the carrier doens't work
Flashed Validus and it doesn't work
But If i Flash omnirom it starts to work.. and then i can flash validus over omnirom to let it work.... very strange!
so what does Ominrom has in order to let it work? Omni rom is the turning point..
Click to expand...
Click to collapse
is 4g working ?
tufoz said:
mobile career network...
I done this: returned to stock and the carrier doens't work
Flashed Validus and it doesn't work
But If i Flash omnirom it starts to work.. and then i can flash validus over omnirom to let it work.... very strange!
so what does Ominrom has in order to let it work? Omni rom is the turning point..
Click to expand...
Click to collapse
The fact that some ROMs work and others don't means your radio firmware did not flash correctly, it is incorrect (US firmware on EU model). I know you said it flashed it correctly, but the symptoms dictate otherwise.
Some ROMs support Marshmallow firmware and others Nougat... But stock requires kernel and firmware match.
I have the same problem, now my imei is on "0" the two imei the same, and i have "without service", so i cant call anyone, i cant use mobile network.
acejavelin said:
The fact that some ROMs work and others don't means your radio firmware did not flash correctly, it is incorrect (US firmware on EU model). I know you said it flashed it correctly, but the symptoms dictate otherwise.
Some ROMs support Marshmallow firmware and others Nougat... But stock requires kernel and firmware match.
Click to expand...
Click to collapse
Can be that i chose the wrong stock file image? now on "pixelEperience" i have GSM signal but only in 3g
rakesh95 said:
is 4g working ?
Click to expand...
Click to collapse
It seems no..
tufoz said:
Can be that i chose the wrong stock file image? now on "pixelEperience" i have GSM signal but only in 3g
It seems no..
Click to expand...
Click to collapse
I have the same problem, the same the same, i want my 4G+ again :crying:
I have the same problem. I manually flashed the stock firmware (NPN25.137-92) many times but I still get no service. Both NON-HLOS and fsg.mbn seem to have flashed without any errors. The only parts that fail are the following:
fastboot erase customize (permission denied)
fastboot erase clogo (permission denied)
When I flash PixelExperience or crDroid only 3g works. I tried changing APN settings but no luck.
Yoga K. said:
I have the same problem. I manually flashed the stock firmware (NPN25.137-92) many times but I still get no service. Both NON-HLOS and fsg.mbn seem to have flashed without any errors. The only parts that fail are the following:
fastboot erase customize (permission denied)
fastboot erase clogo (permission denied)
When I flash PixelExperience or crDroid only 3g works. I tried changing APN settings but no luck.
Click to expand...
Click to collapse
so it's a common situation.... where are you from?
tufoz said:
so it's a common situation.... where are you from?
Click to expand...
Click to collapse
XT1687 retail US
tufoz said:
so it's a common situation.... where are you from?
Click to expand...
Click to collapse
I have one also XT-1681 NPN25.137-92 no imei's showing.
Yoga K. said:
XT1687 retail US
Click to expand...
Click to collapse
Hmm, to the best of my knowledge, NPN25.137-92 is not a firmware designed for retus devices - I think the latest for US devices is NPN25.137-83.
I don't know if you can safely downgrade to NPN25.137-83 now you've flashed NPN25.137-92 onto your device. You may have to wait for a newer retus firmware or if you do downgrade, avoid using OTA updates.
Related
This OTA has been copied straight from the /cache folder by @KennyWuLee.
Download Here!
Steps For Applying the Update:
Copy the ZIP to your Moto G.
Go into Recovery.
Select "apply update from sdcard"
Choose the File which you copied.
Wait till it finishes and select reboot.
This update is specifically for the XT1063 model and isn't meant for other variants.
Update Details:
Code:
v22.11.6
Android Version: 5.0
Build Number: LXB22.39-6
Are you sure? cause the file name is "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US.zip"
Any chance of this working on XT1068?
emmanuelreyes said:
Are you sure? cause the file name is "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US.zip"
Click to expand...
Click to collapse
Yes, he is sure because the filename naming scheme used by Motorola automatically renames any update to the name of the firmware currently installed.
KennyWuLee, had 21.11.17 installed while he downloaded the update and that is why the filename is "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US.zip"
pleomaxell said:
Yes, he is sure because the filename naming scheme used by Motorola automatically renames any update to the name of the firmware currently installed.
KennyWuLee, had 21.11.17 installed while he downloaded the update and that is why the filename is "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US.zip"
Click to expand...
Click to collapse
What if i have a different version? Will it work? or i have to rename it?
emmanuelreyes said:
Are you sure? cause the file name is "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US.zip"
Click to expand...
Click to collapse
pleomaxell said:
Yes, he is sure because the filename naming scheme used by Motorola automatically renames any update to the name of the firmware currently installed.
KennyWuLee, had 21.11.17 installed while he downloaded the update and that is why the filename is "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US.zip"
Click to expand...
Click to collapse
@emmanuelreyes, Exactly what @pleomaxell said. Plus here's the screenshot running on my XT1063.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there a chance to make this file a flashable zip through TWRP? For some reason it doesn't want to install, it says "/system/lib/hw/sensort.MSM8226.so" has unexpected contents :S
Fine to XT1068
Thanks and this works fine with my XT1068, check this post http://forum.xda-developers.com/showpost.php?p=56765946&postcount=138
@Taimur Akmal why does the screenshot show an Exclamation(!) sign with the network icon?
pleomaxell said:
@Taimur Akmal why does the screenshot show an Exclamation(!) sign with the network icon?
Click to expand...
Click to collapse
It shows that I am without an Internet connection. I have Mobile Internet turned off.
Cannot lock bootloader
tbunlmtd said:
Working just fine, thanks!
Click to expand...
Click to collapse
I am stuck here too. Cannot relock bootloader ...
build version KXB21.85-17; System version: Blur_Version.21.11.17.titan_retuglb.retuglb.en.US
I have downloaded the same firmware from http://sbf.droid-developers.org/phone.php?device=36
Applied flash according to :
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
Click to expand...
Click to collapse
getting downgrade error, PIV signed image error, sst lock fail error !
[NB: I have changed to US version (retuaws) before and flashed back to global ]
Sounds like your on a XT1063. This is what I did when I was in the same position as you. I restored my Nandroid of KK. If you have a all stock copy then you should be better then I was & about to skip a few of these steps. I found a system dump on here of the stock system & started pushing the files I knew I removed. Actually I used ES File Explorer & done a select all, copy, paste. You get prompted to ask what to do about files that are already there. Check apply to all & choose skip. This left me with a audio file that was replaced & had to be change back. You should make a new Nandroid to save your work to this point. Flash the stock recovery & run the update.zip. mine installed fine with the unlocked bootloader & root.
L is really buggy tho so be warned.
Sorry for the noob question.
I have the XT1063 and my system version is 21.11.14 titan_retla.retla.en.01 . Will this ota work on my phone?
rasbin said:
Sorry for the noob question.
I have the XT1063 and my system version is 21.11.14 titan_retla.retla.en.01 . Will this ota work on my phone?
Click to expand...
Click to collapse
I doubt it will without flashing the other firmware.
rasbin said:
Sorry for the noob question.
I have the XT1063 and my system version is 21.11.14 titan_retla.retla.en.01 . Will this ota work on my phone?
Click to expand...
Click to collapse
You will have to flash via fastboot the XT1063 retugbl firmware in order to use this OTA file.
Check this thread, but consider making a full backup.
My md5 checksum:
2e632d07edc3c1ceb38a0ee486f12a5b
you need the bootloader unlocked?
I successfully flashed this while being fully stock/locked bootloader. Everything works except the flashlight won't turn back off after I activate it... anyone else have this issue?
patrickjaden said:
I successfully flashed this while being fully stock/locked bootloader. Everything works except the flashlight won't turn back off after I activate it... anyone else have this issue?
Click to expand...
Click to collapse
Working totally fine on my end. You are talking about the Flashlight from the Notif menu right?
Taimur Akmal said:
Working totally fine on my end. You are talking about the Flashlight from the Notif menu right?
Click to expand...
Click to collapse
Yes the bootloader needs unlocked to flash the stock firmware.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[YOUR WARRANTY IS NOW VOID]
****I TESTED ONLY ON MY XT1058 MODEL I DON'T KNOW IF WORKS ON OTHER MODELS***
-First you need to unlock your bootloader [MORE INFO CLICK HERE]
-Install the motorola drivers [DOWNLOAD HERE]
1.- Activate developer settings and copy the "UPDATE-SuperSU-v2.46.zip" to the Internal Storage of the Moto X
2.- Reboot your Moto X on Fastboot Mode (Power + Volume Down Key) (at least 5 seconds)
3.- On Fastboot Mode, connect your device to the USB port of your PC
4.- Go to the downloaded folder and run the "Installer.bat" file
5.- Continue with the instructions of the program, the program will send the recovery to the Phone, now in your phone select "Recovery" option and press the Power Up Key.
6.- When you are in the TWRP recovery select "Reboot", then "System", the swype to install SuperSu.
7.- When your phone has booted normally, select "Install SuperSu" and follow the instructions that appears on phone screen
SCREENSHOTS
[DOWNLOADS]
Google Drive: https://drive.google.com/file/d/0B0yyE-L_FGXrLXpPMlZpSk05dnM/view?usp=sharing
ZippyShare: http://www30.zippyshare.com/v/ua3qv2bK/file.html
MEGA:https://mega.co.nz/#!gQpQTCAa!krYHdwWDCZSlm14PkgNombjSOB1sdfjy4SVnbqr3NnI
VIA: Moto X Brasil
Works on my xt1060 thanks
sorullo_xgrx said:
Works on my xt1060 thanks
Click to expand...
Click to collapse
Wait you Flashed the Soak Test to your XT1060? I thought 1060 was only VZW?
gchase23 said:
Wait you Flashed the Soak Test to your XT1060? I thought 1060 was only VZW?
Click to expand...
Click to collapse
It is but I switch the T-Mobile and its working great
Worked great for me. Unlocked Bootloader XT1058 AT&T US on 5.0.2
Will I be able to go back to stock after doing this? I mean there's no sbf for 5.0.2 yet, so is there anyway to revert this process?
I haven't done it yet, won't do if theres no way to go back.
Thanks
changes the stock recovery?or is only temporary
lukaop said:
Will I be able to go back to stock after doing this? I mean there's no sbf for 5.0.2 yet, so is there anyway to revert this process?
I haven't done it yet, won't do if theres no way to go back.
Thanks
Click to expand...
Click to collapse
Yeah you can always go back to stock by flashing 4.4.4 sbf file. I just flashed on my XT1053 and it works just fine.
ken1645 said:
Yeah you can always go back to stock by flashing 4.4.4 sbf file. I just flashed on my XT1053 and it works just fine.
Click to expand...
Click to collapse
Really? Thought you couldn't downgrade from 5.0 to 4.4, but I will wait for an 5.0 sbf just in case.
Anyway, thanks!
TWRP and SU included in the 5.0.2 ROM
Found out can't downgrade from 5.0 to 4.4.4 and am screwed after trying to take an OTA soak update.
edit: found a way how... it's sneaky though. Use the stock 4.4.4 recovery files, but for the gpt.bin file, replace it using a gpt.bin file from one of the leaked 5.0.2 recovery files and flash as normal to get back to 4.4.4. I had a 1% battery stuck bug though after doing this and discovered by killing the phone all the way to 0% shut down and then recharge the battery meter fixed itself again. Got all the way back to stock 5.0.2 soak test once again after doing this.
The stock recovery of lollipop is the same as KitKat?
ken1645 said:
Found out can't downgrade from 5.0 to 4.4.4 and an screwed after trying to take an OTA soak update.
Click to expand...
Click to collapse
I'm in a similar situation. sucks...
vikramkhalsa said:
I'm in a similar situation. sucks...
Click to expand...
Click to collapse
I found a way how... it's sneaky though. Use the stock 4.4.4 recovery files, but for the gpt.bin file, replace it using a gpt.bin file from one of the leaked 5.0.2 recovery files and flash as normal to get back to 4.4.4. I had a 1% battery stuck bug though after doing this and discovered by killing the phone all the way to 0% shut down and then recharge the battery meter fixed itself again. Got all the way back to stock 5.0.2 soak test once again after doing this.
ken1645 said:
I found a way how... it's sneaky though. Use the stock 4.4.4 recovery files, but for the gpt.bin file, replace it using a gpt.bin file from one of the leaked 5.0.2 recovery files and flash as normal to get back to 4.4.4. I had a 1% battery stuck bug though after doing this and discovered by killing the phone all the way to 0% shut down and then recharge the battery meter fixed itself again. Got all the way back to stock 5.0.2 soak test once again after doing this.
Click to expand...
Click to collapse
I saw that, but I don't want to brick my phone.. Isn't that likely using this way?
Vivjen said:
TWRP and SU included in the 5.0.2 ROM
Click to expand...
Click to collapse
What's in this? because after i flashed this the phone lost signal and even though i flash european modem won't fix it.
alexhdkn said:
What's in this? because after i flashed this the phone lost signal and even though i flash european modem won't fix it.
Click to expand...
Click to collapse
I looked at that zip. With regards to the modem, it flashes an unknown version (soak version?) of both NON-HLOS.bin AND fsg.mbn
I am running LP 5.02 (soak2) with the stock att xt1058 4.4.4 modem without issue, so it *might* work if you extract NON-HLOS.bin and fsg.mbn from your stock version of 4.4.4 and run the following from fastboot:
Code:
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
Good luck.
Ctrl-Freak said:
I looked at that zip. With regards to the modem, it flashes an unknown version (soak version?) of both NON-HLOS.bin AND fsg.mbn
I am running LP 5.02 (soak2) with the stock att xt1058 4.4.4 modem without issue, so it *might* work if you extract NON-HLOS.bin and fsg.mbn from your stock version of 4.4.4 and run the following from fastboot:
Code:
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
Good luck.
Click to expand...
Click to collapse
Somehow i managed to downgrade everything, even the bootloader. After the flash of your zip i tried to flash fsg and modem but it seems that i forgot to erase the two st1/2. Thanks for the interest though
ken1645 said:
Found out can't downgrade from 5.0 to 4.4.4 and am screwed after trying to take an OTA soak update.
edit: found a way how... it's sneaky though. Use the stock 4.4.4 recovery files, but for the gpt.bin file, replace it using a gpt.bin file from one of the leaked 5.0.2 recovery files and flash as normal to get back to 4.4.4. I had a 1% battery stuck bug though after doing this and discovered by killing the phone all the way to 0% shut down and then recharge the battery meter fixed itself again. Got all the way back to stock 5.0.2 soak test once again after doing this.
Click to expand...
Click to collapse
I did the same but just deleted the gpt.bin reference line in the xml to skip over flashing it. I'm not now .38 soak test
So it is safe to downgrade? I would like come back to stock 4.4.4 and then install CM12, my question is because of the bootloader version I read a downgrade may cause brick
Sent from my XT1058 using XDA Free mobile app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The HotROM Box - Early Build
Hey people, I'm spamtheboss, former known on Titan forum on Miui V6 development and also a few tricks I've posted there. But, I have a project called The HotROM Box, which consists in a tool that provides almost everything you need to restore your device in no time, basically an automator. All you need is your adb and fastboot and (for now) your Stock FW.
Main Features
Stock ROM Flashing method
TWRP Recovery Flashing method
Phone Reboot option
Reboot to Bootloader option
Reboot to Recovery option
Dealing with The HotROM Box
1.1: Install
-Copy all files to the folder where your Stock ROM files are located.
1.2: Usabillity
Windows: .bat interactive menu
Linux: .sh interactive menu using Zenity
1.3: F.A.Q (Frequently Asked Questions)
- Q: ROM flashing doesn't work!
- A: You're probably using mFastboot, an alternative version of fastboot. Install the original version and this issue will be solved (until I release a alternative version)
- Q: TWRP flashing doesn't work!
- A: If you haven't downloaded this file via xda official thread some stuff may be corrupted. TWRP image is uploaded with the script and you must copy those to your ROM folder.
- Q: ETA?
- A: Please, do not ask this kind of question. I'm not a dev, I just like (very much) to program some cool stuff, and if something on the code goes wrong, warn me and i'll fix it and release a new version as soon as I can.
- Q: Will you add more features?
- A: Always, this tool will grow with features as the way I improve my programming skills.
Changelog
Initial Release (Stock ROM flashing, TWRP flashing and other minor options)
Added alternative mFastboot flashing method
Tool ported to THEA and OSPREY
Tool ported to Linux
Downloads
Mediafire Last update!
Github Repo (LINUX)
Github Repo (WINDOWS) Not available (yet).
Vote Poll
What you think about The HotROM Box? Vote your opinion about it!
Link: http://www.strawpoll.me/10664791
Updates
To update HRB, just paste the new files on the older files directory. Simple as that!
OSPREY-2.1
Source Code: http://github.com/lelufg
XDA:DevDB Information
The HotROM Box, Tool/Utility for the Moto G 2015
Contributors
spamtheboss
Version Information
Status: Nightly
Current Stable Version: 2.0
Stable Release Date: 2015-12-30
Current Beta Version: 2.0
Beta Release Date: 2015-12-18
Created 2015-12-31
Last Updated 2015-12-31
Reserved.
Was waiting for this to come to ospery
Never heard this one but impressive.. Will try it..
sounds cool, will try it as soon as factory image 6.0 is available ....
Bangbang_cannon said:
Was waiting for this to come to ospery
Click to expand...
Click to collapse
Well, thank you!
Glad I extended to Osprey then. I'll try to update it weekly but can't promise. Also I will create a repo for it on Github very soon.
FPThatea said:
Never heard this one but impressive.. Will try it..
Click to expand...
Click to collapse
Yes, I'm not that known lol. But I did created this tool formely for Moto G 2014 some months ago, and now I'm porting to other devices. I hope you have a good experience with it, and if anything weird happens during tool usage, tell me here. I will be glad to help and update it.
kiekeboeboe said:
sounds cool, will try it as soon as factory image 6.0 is available ....
Click to expand...
Click to collapse
I am waiting for it too. I think it will add or remove some file, and if my suspects are correct, I will have to update this tool in order to flash Stock MM firmwares too.
I used it yesterday. Flawless! Thanks!
Sent from my MotoG3 using Tapatalk
nelsonw said:
I used it yesterday. Flawless! Thanks!
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
You're welcome, bro.
nelsonw said:
I used it yesterday. Flawless! Thanks!
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
This tool looks to be amazing. I do however have the dumbest question ever. I'm use to using fastboot mode all the time. What's the exact steps after downloading THB? I have adb and fastbbot already and the stock rom in the same folder. Just wondering if I place THB in the same folder and run it from there? Thanks for any help.
professorfoxx said:
This tool looks to be amazing. I do however have the dumbest question ever. I'm use to using fastboot mode all the time. What's the exact steps after downloading THB? I have adb and fastbbot already and the stock rom in the same folder. Just wondering if I place THB in the same folder and run it from there? Thanks for any help.
Click to expand...
Click to collapse
Yes, it's a .bat file. You need the extracted ROM files and the Fastboot files on the same folder. It's pretty important to avoid brick the phone due to typos.
Sent from my MotoG3 using Tapatalk
nelsonw said:
Yes, it's a .bat file. You need the extracted ROM files and the Fastboot files on the same folder. It's pretty important to avoid brick the phone due to typos.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Thank you very much. This tool is absolutely fantastic. It made getting back to stock the easiest! Definitely great work?????
professorfoxx said:
This tool looks to be amazing. I do however have the dumbest question ever. I'm use to using fastboot mode all the time. What's the exact steps after downloading THB? I have adb and fastbbot already and the stock rom in the same folder. Just wondering if I place THB in the same folder and run it from there? Thanks for any help.
Click to expand...
Click to collapse
nelsonw said:
Yes, it's a .bat file. You need the extracted ROM files and the Fastboot files on the same folder. It's pretty important to avoid brick the phone due to typos.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Yes, as Nelson said, you need to put the .bat file and the .img into the same folder of the adb, fastboot and the Stock ROM. I'll push an update today just to bring it all together instead of pasting it to some weird directory (like the people who installed adb within android studio); Stock ROM direct download can be mentioned too, but just on a future version.
professorfoxx said:
Thank you very much. This tool is absolutely fantastic. It made getting back to stock the easiest! Definitely great work????
Click to expand...
Click to collapse
You're welcome, mate! Glad I'm helping.
2.1 update for Osprey!
2.1 update is out! It's also released for Moto G 2014 and Moto G 2014 LTE.
Changelog
Updated TWRP
Bugfixes
Added ADB and Fastboot directly
Download link on OP.
Commands Missing
Add: Missing commands in Bold
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
will it wipe internal storage
would flashing stock rom clean the internal storage.?
spamtheboss said:
Well, thank you!
Glad I extended to Osprey then. I'll try to update it weekly but can't promise. Also I will create a repo for it on Github very soon.
Yes, I'm not that known lol. But I did created this tool formely for Moto G 2014 some months ago, and now I'm porting to other devices. I hope you have a good experience with it, and if anything weird happens during tool usage, tell me here. I will be glad to help and update it.
I am waiting for it too. I think it will add or remove some file, and if my suspects are correct, I will have to update this tool in order to flash Stock MM firmwares too.
Click to expand...
Click to collapse
please update to flash mm firmwares. im waiting for it to be updated . gotta say its ur tool that saved me.
prasi.ram10 said:
please update to flash mm firmwares. im waiting for it to be updated . gotta say its ur tool that saved me.
Click to expand...
Click to collapse
I will, as soon as the whole firmware gets released! I am waiting too... xD
unkushad said:
would flashing stock rom clean the internal storage.?
Click to expand...
Click to collapse
Hello unkushad, sorry for the late answer. Yes, it will wipe the whole internal storage, because Android needs to clean all the remaining data from the other versions.
amansingh63 said:
Commands Missing
Add: Missing commands in Bold
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
Click to expand...
Click to collapse
They're missing because I removed them. This tool *for now* doesn't lock the bootloader. I will update it later to add this feature.
spamtheboss said:
They're missing because I removed them. This tool *for now* doesn't lock the bootloader. I will update it later to add this feature.
Click to expand...
Click to collapse
mm compatibility??
Hi,
my situation is this:
1.) I had installed TWRP + Root + Xposed + Stock Android 6.0.1 and everything worked fine.
2.) Then came the last OTA update notification.
3.) I picked an old backup when i had only TWRP installed and the rest was untouched.
4.) When the backup was done i picked the recovery.img file from this .rar XT1602_HARPIA_MPI24.241-15.3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml (4) and flashed it with mfastboot. (USB Debugging Enabled, Fastboot Mode Enabled)
5.) I started the Recovery Mode and ended with the "Dead Android Guy". Even though i was able to reach the stock recovery menu using a key combination (POWER+VOL UP+VOL DN at the same time)
6.) Restart the phone
7.) Download the OTA Update
8.) Tried to install it but ended always with an error
9.) Phone restart -> "An error occured during the OTA update"...
Everytime when i try to reach the stock recovery i always see the dead android guy first. Ive also tried to wipe the cache+wipe data + factory mode. But nothing helps. How the hell can i fix that and install the last OTA update (and why did that happen to me -.-?)
EDIT
I managed to solve the problem by flashing every single file of the firmware. Heres a list:
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
Click to expand...
Click to collapse
EDIT
But still. When i try to enter the stock recovery i see the dead android guy first. Can you help me out?
Well, the "dead droid" before stock recovery it's the expected behavior, isn't it?
Idk. Im not used to the dead droid.
removed
sevenRA1 said:
Idk. Im not used to the dead droid.
Click to expand...
Click to collapse
In the stock the dead droid always cames before the stock Recovery, don't worry about it.
Same problem here. I've got an XT1602 with 6.0.1. stock and Oct 2016 security patches and an OTA update is available, but fails to install. TWRP says error 7, stock displays the dead droid.
I have my phone rooted, but installed a system backup before installing the OTA.
Flashing stock from here leads to 6.0.1. with July patches, but no OTA update available.
Any Ideas? Can anyone provide a a newer stock rom?
@sevenRA1 are you sure you're on the latest version? can you please check your security patch level?
Yes im very sure. Security Level is now Feb. 2017 and when i search for new updates it doesnt find some. Do what i did. Flash every single file by hand. Heres a How To.
ValdarX said:
Same problem here. I've got an XT1602 with 6.0.1. stock and Oct 2016 security patches and an OTA update is available, but fails to install. TWRP says error 7, stock displays the dead droid.
I have my phone rooted, but installed a system backup before installing the OTA.
Flashing stock from here leads to 6.0.1. with July patches, but no OTA update available.
Any Ideas? Can anyone provide a a newer stock rom?
@sevenRA1 are you sure you're on the latest version? can you please check your security patch level?
Click to expand...
Click to collapse
ValdarX did you manage to solve this problem? I've got the same thing: restored to stock (saving the user data) and no more OTA available, so stuck on an old version. I guess maybe only full recovery to stock will work.
Excuse me, I would like to do the same thing, in order to prepare for nougat. My phone is bought from vodafone romania, vodafone branded. It is harpia xt1604. Its specs are shown in picture. Could I flash the Harpia XT1602 firmware RETAIL from here to have it unbranded and to get the latest updates?
Thank you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TheEvilVirus said:
ValdarX did you manage to solve this problem? I've got the same thing: restored to stock (saving the user data) and no more OTA available, so stuck on an old version. I guess maybe only full recovery to stock will work.
Click to expand...
Click to collapse
unfortunately not
I have the same issue. I've tried several times to install the update on my stock xt1607 and it fails every time. I've restored my stock backup from immediately after I unlocked my bootloader...totally unmodified. I get an error in stock recovery saying there was an unexpected change to /system. I even flashed the stock boot logo again, just in case. My only remaining option is a full factory flash, to be completely sure the /system is unmodified.
me too
Before rooting, I did backups of untouched /system /boot, recovery and logo partition.
I've carefully followed this howto and it doesn't work definitively.
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-sucsessfull-ota-update-rooting-t3472658
On second attempt, I've tried this without success :
https://forum.xda-developers.com/showpost.php?p=71461568&postcount=64
After rebooting, "Parameters>>About Phone>>System Update" says my phone is up to date and I'm unable to get the OTA. I tried to apply the OTA (Blur_Version.24.201.8.harpia.retail.en.US.zip) downloaded with my current version (MPIS24.241-15.3-7) , I got another error :
Package expects build thumbprint of 6.0.1/MPIS24.241-15.3-16/17 .... or 6.0.1/MPIS24.241-15.3-7/8 ... ; this device has 6.0.1/MPIS24.241-15.3-3/3
So at now, I'm blocked at security level Oct 2016.
Anybody to help us ?
hamelg said:
me too
Before rooting, I did backups of untouched /system /boot, recovery and logo partition.
I've carefully followed this howto and it doesn't work definitively.
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-sucsessfull-ota-update-rooting-t3472658
On second attempt, I've tried this without success :
https://forum.xda-developers.com/showpost.php?p=71461568&postcount=64
After rebooting, "Parameters>>About Phone>>System Update" says my phone is up to date and I'm unable to get the OTA. I tried to apply the OTA (Blur_Version.24.201.8.harpia.retail.en.US.zip) downloaded with my current version (MPIS24.241-15.3-7) , I got another error :
Package expects build thumbprint of 6.0.1/MPIS24.241-15.3-16/17 .... or 6.0.1/MPIS24.241-15.3-7/8 ... ; this device has 6.0.1/MPIS24.241-15.3-3/3
So at now, I'm blocked at security level Oct 2016.
Anybody to help us ?
Click to expand...
Click to collapse
Did you try to flash the stock rom through fastboot? Including recovery?
Yes, but I flashed only boot.img, logo.bin, recovery.img, system.img_sparsechunk.0 till 7.
I'm a little bit nervous to do a full flash and to be stick with July Patch like ValdarX at comment #6. After a full flash, if something goes wrong, I won't be able to restore my backup.
Edit :
What about to keep my data, can I safely skip erase userdata ?
What is the purpose of the customize partition ?
issue solved, here :
https://forum.xda-developers.com/showpost.php?p=71999579&postcount=11
No need to worry, the only thing you are missing is. It may be possible that you installed fiware not contain Moto upgrade sevice. You should download this from play store. Or download the correct fiware from firmwarecentre
sevenRA1 said:
Yes im very sure. Security Level is now Feb. 2017 and when i search for new updates it doesnt find some. Do what i did. Flash every single file by hand..
Click to expand...
Click to collapse
I stand corrected, that works. I'm on Feb 2017 security patches now. Didn't even have to erase userdata.
I have the same issues again with the next security update -.-
@hamelg Your advice fixed nothing for me. This night ill flash the whole stock image again.
Does anybody have any experience how/whether this works if the only image available for your phone model now involves a downgrade?
My phone (XT1602 reteu) was delivered with a July 2016 patch level, which corresponds to the only stock image (the XT1602 RETAIL one) I see available for it.
Flashing that to unroot, apply the OTA updates (up to February 2017) and then re-root worked fine, but what about a repeat performance? I originally assumed I could simply start with that stock image again and then apply all OTAs (including any new ones) once more, but I've since learned that the bootloader (and partition table) isn't necessarily downgradable and might cause problems with reapplying the OTAs after downgrading the rest of the phone.
Although at least for the time being never mind - it seems like there are now RETAIL images for both February and May patch levels floating around, which avoids any need to downgrade.
Hi, yesterday i have unlock bootloader of my moto g4, xt 1622 , i have flashed twrp and this is perfect, but after i have flashed zip of magisk.zip for root permission, when i reboot i obtain only black screen and led white ( intermittence led) .
The device is recognize by windows 10 (in test mode and no signature driver verify ) but not in tray bar..
Mode recognized by pc are:
in fast boot like " fastboot athene_13mp S " in "other device"
In adb mode " sideload" ( from stock recovery) like "Moto g4 plus " in device manager/usb devices"
I have stock recovery and can't start blank flash because the device isn t recognized by pc like qualcomm device..
What can i do??? Thanks a lot my friends!!
The problem is that magisk is not compatible with the Stock kernel, so if you want magisk you need to flash a custom kernel, i recomend this: https://elementalx.org/devices/moto-g4/ you need to flash the kernel and after this flash magisk.
Regards
Wow! So the phone is save? ?
And what can i flash pther kernel, can i have a guide plz? Can i flash with sideload? Thanks!
Yes, you need to enter un recovery, conect your phone to pc and with adb put in the cmd adb sideload nameofyourzip.zip and then flash magisk with sideload if hoy wanr
Unfortunately i recive this error.. what can i do? Thanks!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok, first you need to install twrp: https://forum.xda-developers.com/mo...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
Then you need to go in twrp to avanced and adb sideload and flash it.
Hmm, can you confirm if you have stock Marshmallow (6.0.1) or Nougat (7.0) on your device? I see from the stock recovery version that it's 6.0.1/MPJ24.139-23-4 (a really old build of Marshmallow).
Thanks ismael! I m going to try it
@ECHO first of this mods, the smartphone have nougat full stock. When i have installed twrp the sistem started normally, but when i flashed magisk the sistem started with black screen, before this i ve factory reset and flash a zip of stock rom.. and start a very problem!!
Thaks a lot to all for help me and sorry for my bad english.
David
scossa1994 said:
Thanks ismael! I m going to try it
@ECHO first of this mods, the smartphone have nougat full stock. When i have installed twrp the sistem started normally, but when i flashed magisk the sistem started with black screen, before this i ve factory reset and flash a zip of stock rom.. and start a very problem!!
Thaks a lot to all for help me and sorry for my bad english.
David
Click to expand...
Click to collapse
Thanks, as Ismael034202 pointed out above, if you were on stock Nougat, then you will need to flash a custom kernel, as rooting on the stock Motorola Nougat kernel will cause a boot failure. If you were still on Nougat, then you could have followed this guide https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 with flashing magisk instead of SuperSU.
As you've re-flashed the old Marshmallow stock ROM, then you do not need a custom kernel (Marshmallow stock ROM kernels are less strict about rooting), flashing TWRP and then flashing magisk should work on Marshmallow.
However, you need to be very careful if you revert back to full stock - as you've appeared to have downgraded from Nougat, taking OTA updates may hard brick your device. If you can remember what Nougat stock ROM you had before unlocking your device, I would recommend downloading a copy of that stock ROM and using the stock ROM to update. Try not to use stock OTA updates.
Very well explained echo92. +1 ?
what can i flash somethings?? because usb debug is off after wipe dataa, and i can t enter in android to activate it!! plz help
i think that android is stock nougat, with old stock recovery and magisk(the real problem) and stock kernel.
what can i solve?
thanks
scossa1994 said:
what can i flash somethings?? because usb debug is off after wipe dataa, and i can t enter in android to activate it!! plz help
i think that android is stock nougat, with old stock recovery and magisk(the real problem) and stock kernel.
what can i solve?
thanks
Click to expand...
Click to collapse
Hmm, in that case, the easiest way may be to flash the latest stock ROM to your device and start over again. As an alternative, do you have a TWRP backup of your device?
For XT1622, you'll likely want NPJS25.93-14-13 (Nougat, 7.0 stock, December 2017 security patch) firmware from here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Download and extract as directed in the post, and to flash to repair your device, use the following flashing commands:
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
This should not re-lock your bootloader. Next, download TWRP, ElementalX and magisk and flash as I suggested in the guide above. The basic guide for rooting on Nougat is:
a)Flash/boot TWRP. Backup your device.
b)Flash ElementalX.
c)Flash magisk or SuperSU.
d)Wipe cache/Dalvik in TWRP.
e)Reboot and wait for boot.
f)Any issues, revert to your backup made in a)
Can i use fastboot within debug usb off? Because i recive an error, i m tryng and post a pic.
Thanks
This is my situation after try to use fastboot
Hace you installed Motorola drivers for pc, you can use fastboot without USB debugging
https://mobilesupport.lenovo.com/rola/es/solution/MS89882 This os the link for the fastboot drivers
Thanks guys!! I had write the stock 7.0!! Now the phone is perfect!! Thanks!!
I had wrong driver and pc not recognized the phone!! Now yes ??
Now install twrp, elementalX Kernel, magisk and enjoy
Hi i need urgent help. My Moto g4 plus is not starting anymore. I was using it and but suddenly switched off and nithing works now. Only the led light comes two times when charging cable is connected. Please help help
It was rooted.
Moto Singh said:
Hi i need urgent help. My Moto g4 plus is not starting anymore. I was using it and but suddenly switched off and nithing works now. Only the led light comes two times when charging cable is connected. Please help help
It was rooted.
Click to expand...
Click to collapse
Can you enter in bootloader pressing vol - and power?? If is possible is not problem because you can flash stock rom in fastboot.
scossa1994 said:
Can you enter in bootloader pressing vol - and power?? If is possible is not problem because you can flash stock rom in fastboot.
Click to expand...
Click to collapse
No nothing is working.
Moto Singh said:
No nothing is working.
Click to expand...
Click to collapse
I don t know.. the problem is the corrupted bootloader ( i think..)