Develop Bugs

[TOOL]JellyBean Hboot Firmware Flasher |V0.3|19 Oct| [MAC/LINUX] | hBoot 1.28 |

{
"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"
}
hi all!
i've made a simple tool for mac and linux, for flash the new Hboot ( 1.28 ).
if you have trubles , PLEASE PLEASE PLEASE post here!!
i hope you enjoy it
i would like to thank all the devs for the beautiful work they do for us and Football for the Firmware update! Thanks guys!
As always ,you use this tool at your own risk
CID supported:
cid: HTC__001
cid: HTC__E11
cid: HTC__203
cid: HTC__102
cid: HTC__405
cid: HTC__Y13
cid: HTC__A07
cid: HTC__304
cid: HTC__M27
cid: HTC__032
cid: HTC__016
cid: HTC__J15
Click to expand...
Click to collapse
Features:
check Device CID using "fastboot getvar cid" and if it get's "cid: None" will try with "oem readcid". (if cid not matching the tool will not upgrade the Hboot )
check battery status ( for a secure upgrade. if your battery is too low the tool will not upgrade the hboot until you recharge the battery). If your battery is charged and you get "battery ststus not good", close the tool, reboot your phone in fastboot and try again
lock bootloder
flash firmware
reflash firmware
unlock bootloader
flash recovery ( TWRP)
flash boot.img of the rom you have choose to flash
Click to expand...
Click to collapse
Simple How to:
put YOUR original Unlock_code.bin in the UNLOCK folder
put the boot.img of your choice in the BOOT folder
if you don't want TWRP recovery, download the recovery you want and place it in the RECOV folder ( rename it in " recovery.img " )
reboot your phone in fastboot mode
run in terminal FirmwareFlasher.sh ( ./FirmwareFlasher.sh ). if not running do "chmod 777 FirmwareFlasher.sh " and try again
Follow the onscreen instruction
Click to expand...
Click to collapse
thread on Androidiani.com : http://www.androidiani.com/forum/ht...llybean-hboot-firmware-flasher-mac-linux.html
Click to expand...
Click to collapse
Download :
(for download the archive go to the top left of the page >> file >>download )
Mac:FirmwareFlasher_OneX_MAC_0.3.zip
Linux: FirmwareFlasher_OneX_LINUX_0.3.zip
Click to expand...
Click to collapse
changelog:
Code:
[B]Little Update:[/B] Uploaded Linux version ;)
[B]Update 2:[/B] Reuploaded Linux version, i've forgot the request for sudo password needed for Fastboot commands :silly:
[B]Update 3 ( V0.1):[/B] Cleaned code a bit. Now the script is MOAR colorful for easy reading:D:D
[B]Update 4 (V0.2):[/B] Added Battery-status check ( if battery status isn't good you can't proceed with flash )
[B]Update 5 :[/B] for those who have the "[B]cid: None[/B]" problem, i've attached a version of the script that reads Cid using [B]fastboot oem readcid[/B]. Just unzip the archive and copy the [B].sh[/B] file in the [B]FirmwareFlasher[/B] folder ( thanks [B][COLOR="SeaGreen"]ClydeB1[/COLOR][/B] )
[B]Update 6 (V0.3): Merged 0.2 and 0.2a version. if with "getvar cid" get's "cid: None" the script will try with "oem readcid". As the previous versions, it will check battery status for a more secure upgrade[/B]
Any Feedback is much appreciated! Thanks!
ENJOY!

Good job cesco!
Inviato dal mio Nexus 7

bravo mbare!

You should flash the firmware twice, i had to do that

blubbers said:
You should flash the firmware twice, i had to do that
Click to expand...
Click to collapse
The script flash the firmware two times

Non ho capito bene cosa fare XD devo mettere nella cartella BOOT il boot.img per esempio della rom maximus. Poi devo eseguire solo quel comando e mi trovo con hboot aggiornato alla 1.28 ma rimango sempre con la vecchia rom che ho installato giusto?

Linux
I have CID 102 but it says, my cid is not allowed
And i removed the the CID check from the script but it only says
waiting for device

imesh said:
Non ho capito bene cosa fare XD devo mettere nella cartella BOOT il boot.img per esempio della rom maximus. Poi devo eseguire solo quel comando e mi trovo con hboot aggiornato alla 1.28 ma rimango sempre con la vecchia rom che ho installato giusto?
Click to expand...
Click to collapse
please write in english!
you should put the boot.img of your choice in the BOOT folder and when all is done you must go in recovery mode, plug the device to the PC, go to "mount" and tap "mount USB storage" and copy the ROM.zip you want to flash
And of course, you MUST perform a full wipe before flashing the new rom!
example:
downloaded Rom MaXimus 4.2 with his boot.img, you must put the boot.img in the BOOT folder and then start the script
If you want, you can put the Rom.zip in your virtual SD card before start upgrading hboot

D4rk_nVidia said:
Linux
I have CID 102 but it says, my cid is not allowed
And i removed the the CID check from the script but it only says
waiting for device
Click to expand...
Click to collapse
You need to reboot in fastboot mode and plug device to the pc!
i've forgotten that ADB and Fastboot in linux needs Sudo password, i've attached the script!
Tested now on ubuntu and works
Now i'm going to Reupload Linux Archive

I know that with fastboot mode
I was already on 1.23 but i flashed this in WIndows.
Thank you for your work I flashed it manually. I only take all commands and run it in the terminal with sudo .

D4rk_nVidia said:
I know that with fastboot mode
I was already on 1.23 but i flashed this in WIndows.
Thank you for your work I flashed it manually. I only take all commands and run it in the terminal with sudo .
Click to expand...
Click to collapse
thanks to you for reporting the issue

How did you set up the udev rule for the phone? I'm asking, because I have never needed sudo to flash anything

D4rk_nVidia said:
Linux
I have CID 102 but it says, my cid is not allowed
And i removed the the CID check from the script but it only says
waiting for device
Click to expand...
Click to collapse
The 102 bit is not the only part of the cid, it would need to be HTC__102 to be valid. O2__102 or VODAP102 etc is not a valid cid.

This made it soo easy! thanks!
Sent from my HTC One X using xda premium

Jay_BG said:
How did you set up the udev rule for the phone? I'm asking, because I have never needed sudo to flash anything
Click to expand...
Click to collapse
i've noticed it this morning, with the help of D4rk_nVidia . the latest versions of adb and fastboot for linux needs sudo password
without that, fastboot stucks on " waiting device"
i've not set udev for the phone because i'm for more time on mac ( dualboot mac/ubuntu on MBP 15 )
You can read all the code, i don't want to steal your passwords roftl

CID?
Hi, first of all thanks for your work. But unfortunately CID-check is not working for me. Using following the command: "fastboot getvar cid" the answer is "None", but using "fastboot oem readcid", I got "HTC__102" which should work!?! Any workaround? Thanks
Edit: I am OSX

krustovsky said:
Hi, first of all thanks for your work. But unfortunately CID-check is not working for me. Using following the command: "fastboot getvar cid" the answer is "None", but using "fastboot oem readcid", I got "HTC__102" which should work!?! Any workaround? Thanks
Click to expand...
Click to collapse
Why do you need a workaround. The reason you got None when running fastboot getvar cid is probably because your bootloader is still locked. Your cid is HTC__102 and so you can proceed.
Edit: If the tool is failing when checking cid, then try to lock bootloader first before running tool.

Thanks for your quick reply. But relocking the bootloader first gives me the same result Still the CID check via "fastboot getvar cid" fails...

ClydeB1 said:
Why do you need a workaround. The reason you got None when running fastboot getvar cid is probably because your bootloader is still locked. Your cid is HTC__102 and so you can proceed.
Edit: If the tool is failing when checking cid, then try to lock bootloader first before running tool.
Click to expand...
Click to collapse
or, if you are ABSOLUTELY SURE your CID is HTC__102, just create a "cid.txt" file in the same folder of the script, at first line write cid: HTC__102 and save the file.
Open in a text editor FirmwareFlasher.sh and comment the line with "./fastboot getvar cid ". ( the final result should be # ./fastboot getvar cid
save the file and run it in the terminal

good to see you here
Great job Cesco: Good:

Desire Unlock BootLoader Problem

i Cant unlock Bootloader
Also I need To Downgrade hoot
S-onn
Hboot 1.02
radio 5.17
Room 2.3.3
Build Number 3.14.405.1
I use Revolutionary Always Get Wrong ( I Sure With I Write Code And Read Serial Correctly )
When I Use htcdev I get This Error :
Code:
C:\Adb>fastboot oem get_identifier_token
... FAILED (status malformed (1 bytes))
finished. total time: 0.000s
Also I Didnt Find my ROM version In List
HTC Desire
Carrier ROM Model #
US Cellular 2.11.573.5 PB9940000 Download
Cellular South 2.12.563.1 PB9940000 Download
CS 2.12.563.3 PB9940000 Download
COX 2.12.590.10 PB9940000 Download
Alltel 2.12.671.2 PB9940000 Download
SKT KR 2.12.911.2 PB9920000 Download
UTStarcom 2.13.557.0 PB9940000 Download
Appalachian Wireless 2.13.557.0 PB9940000 Download
Cellcom 2.13.557.0 PB9940000 Download
Northwest Missouri Cellular 2.13.557.0 PB9940000 Download
Bluegrass 2.13.557.0 PB9940000 Download
Carolina West Wireless 2.13.557.0 PB9940000 Download
GCI 2.13.557.0 PB9940000 Download
Silver Star Wireless 2.13.557.0 PB9940000 Download
Thumb Cellular 2.13.557.0 PB9940000 Download
Illinois Valley Cellular 2.13.557.0 PB9940000 Download
Nex-Tech Wireless 2.13.557.0 PB9940000 Download
Inland Cellular 2.13.557.0 PB9940000 Download
ETEX WIreless 2.13.557.0 PB9940000 Download
Cox Communications Inc. 2.13.557.0 PB9940000 Download
Mobi PCS 2.13.557.0 PB9940000 Download
Cellular One of NEPA 2.13.557.0 PB9940000 Download
NTELOS 2.13.557.0 PB9940000 Download
James Valley Wireless 2.13.557.0 PB9940000 Download
SRT Communications 2.13.557.0 PB9940000 Download
Panhandle Telephone - (PTCI) 2.13.557.0 PB9940000 Download
Nemont Telephone 2.13.557.0 PB9940000 Download
MTA 2.13.557.0 PB9940000 Download
Copper Valley Wireless 2.13.557.0 PB9940000 Download
United Wireless 2.13.557.0 PB9940000 Download
Syringa Wireless 2.13.557.0 PB9940000 Download
Golden State Cellular 2.13.557.0 PB9940000 Download
Mid-Rivers 2.13.557.0 PB9940000 Download
Chat Mobility 1 / 2 2.13.557.0 PB9940000 Download
LEACO 2.13.557.0 PB9940000 Download
ACS 2.13.557.0 PB9940000 Download
South Central Communications 2.13.557.0 PB9940000 Download
Pioneer Cellular 2.13.557.0 PB9940000 Download
Open Mobile 2.13.557.0 PB9940000 Download
Revol 2.13.557.0 PB9940000 Download
RCC/Rural Cellular Corperation/Unicel 2.13.557.0 PB9940000 Download
Commnet/Choice Wireless 2.13.557.0 PB9940000 Download
Strata Networks 2.13.557.0 PB9940000 Download
Mohave Wireless 2.13.557.0 PB9940000 Download
hTC Asia India 2.13.720.2 PB9920000 Download
TMO PL 2.15.118.2 PB9920000 Download
Orange UK 2.17.61.3 PB9920000 Download
Virgin Mobile 2.22.351.2 PB9920000 Download
Orange PL 2.22.69.3 PB9920000 Download
Orange CH FRA 2.22.71.4 PB9920000 Download
Orange FR 2.22.73.6 PB9920000 Download
Orange ES 2.22.75.3 PB9920000 Download
Fastweb IT 2.25.1600.2 PB9920000 Download
TELUS 2.25.661.2 PB9922000 Download
HTCCN CHS 2.26.1400.3 PB9920000 Download
Telstra WWE 2.26.841.2 PB9921000 Download
SoftBank JP 2.28.762.3 PB9920000 Download
TMO UK 2.29.110.6 PB9920000 Download
TMO AT 2.29.112.6 PB9920000 Download
O2 DE 2.29.207.4 PB9920000 Download
HTC EU 2.29.405.14 PB9920000 Download
hTC Asia WWE 2.29.707.3 PB9920000 Download
H3G UK 2.29.771.3 PB9920000 Download
hTC Asia HK 2.29.832.3 PB9920000 Download
Brightstar Personal Argentina SPA 2.30.545.7 PB9922000 Download
Vodafone TR 2.31.184.4 PB9920000 Download
Vodafone UK 2.33.161.6 PB9920000 Download
Vodafone FRA 2.33.163.5 PB9920000 Download
Brightstar SPA 2.34.515.1 PB9922000 Download
Brightstar Movistar Peru 2.34.546.2 PB9922000 Download
Brightstar Tigo Guatemala 2.34.547.3 PB9922000 Download
HTCCN CHS CU 2.35.1402.5 PB9920000 Download
Yoigo ES 2.35.1510.6 PB9920000 Download
Proceed to Step 1
Click to expand...
Click to collapse
Any Help !

Revolutionary should work. What goes wrong?

abaaaabbbb63 said:
Revolutionary should work. What goes wrong?
Click to expand...
Click to collapse
Serial : SH0AZR802791
{
"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"
}

try copy/paste in the beta key

jmcclue said:
try copy/paste in the beta key
Click to expand...
Click to collapse
I Already Do That Cope And Past It

cas77per said:
I Already Do That Cope And Past It
Click to expand...
Click to collapse
the only other reason why the beta key dont work is maybe u filled in the wrong details on the revolutionary page. i would start again, fill in the drop down boxes and try again
---------- Post added at 10:08 PM ---------- Previous post was at 10:07 PM ----------
this ur beta key --
PivF1lm3F3y1Frbh

jmcclue said:
the only other reason why the beta key dont work is maybe u filled in the wrong details on the revolutionary page. i would start again, fill in the drop down boxes and try again
---------- Post added at 10:08 PM ---------- Previous post was at 10:07 PM ----------
this ur beta key --
PivF1lm3F3y1Frbh
Click to expand...
Click to collapse
Bro Now Its Working , but i need to Know What's Wrong i do !
I Change To Laptop's
Thanks For Your Help Bro

cas77per said:
Bro Now Its Working , but i need to Know What's Wrong i do !
I Change To Laptop's
Thanks For Your Help Bro
Click to expand...
Click to collapse
lol i only filled in the details on revolutionary site that was in ur post.
Your operating system: windows
Your device: HTC Desire
HBOOT version: 1.02.0001
Serial number: SH0AZR802791
Beta Key = PivF1lm3F3y1Frbh
My guess is u filled in one of the boxes wrong.

Which ruu to flash on an HTC M8

Here is the thing.
I have bought an refurbished HTC one M8 online and after using it for a while i did the android updates. It had android 4.4 then it installed 5.0.1 and then it updated to 6.0, after a couple of days the back camera started to crush when opened. I did a little research and as a presumed problem was the android update i did. So i tryed to install the European Ruu from the htc site but without success. Can anyone help me further.
The mob cid: 11111111
Please let me know what details to provide if needed.
Thanks

So i flashed the ruu of unlock/developer also that of AT&T but all the same, no success with the camera. I don't know what to do anymore, please someone help.

ALBI SHTYLLA said:
Here is the thing.
I have bought an refurbished HTC one M8 online and after using it for a while i did the android updates. It had android 4.4 then it installed 5.0.1 and then it updated to 6.0, after a couple of days the back camera started to crush when opened. I did a little research and as a presumed problem was the android update i did. So i tryed to install the European Ruu from the htc site but without success. Can anyone help me further.
The mob cid: 11111111
Please let me know what details to provide if needed.
Thanks
Click to expand...
Click to collapse
Post the results of fastboot getvar all minus your IMEI and serial#, and I or someone else here will be able to direct you to the right RUU/firmware

xunholyx said:
Post the results of fastboot getvar all minus your IMEI and serial#, and I or someone else here will be able to direct you to the right RUU/firmware
Click to expand...
Click to collapse
I flashed the ruu of unlock/developer also that of AT&T but all the same, no success with the camera. I don't know what to do anymore, please someone help.

ALBI SHTYLLA said:
I flashed the ruu of unlock/developer also that of AT&T but all the same, no success with the camera. I don't know what to do anymore, please someone help.
Click to expand...
Click to collapse
If you aren't going to do what I asked of you, then I can't help you.

xunholyx said:
Post the results of fastboot getvar all minus your IMEI and serial#, and I or someone else here will be able to direct you to the right RUU/firmware
Click to expand...
Click to collapse
{
"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"
}
can you help me wih this picture ?
i'll wait for my friend to give me the phone then i'll do "fastboot getvar all"
thanks advancely

idir543 said:
can you help me wih this picture ?
i'll wait for my friend to give me the phone then i'll do "fastboot getvar all"
thanks advancely
Click to expand...
Click to collapse
You have a Verizon device, and can only use Verizon firmware. US Unlocked and AT&T firmware won't work.
You can get the RUU.zip that you need from here.

That's LRA device .. flashing Verizon firmware is not recommended.

xunholyx said:
You have a Verizon device, and can only use Verizon firmware. US Unlocked and AT&T firmware won't work.
[/URL].
Click to expand...
Click to collapse
Thanks , is there a tutorial? Do i have to unlock bootloader or no? Do i need s-off or s-on ? Thanks
---------- Post added at 01:40 PM ---------- Previous post was at 01:38 PM ----------
ckpv5 said:
That's LRA device .. flashing Verizon firmware is not recommended.
Click to expand...
Click to collapse
Hum , i didn't understand, why?

idir543 said:
Hum , i didn't understand, why?
Click to expand...
Click to collapse
Because the radio config data (rcdata) on Verizon meant for Verizon network but
LRA rcdata is for non-Verizon network
When you install Verizon firmware which has Verizon rcdata, your data most probably won't work.
Read this : http://forum.xda-developers.com/htc-one-m8/help/help-friends-t3402398

Does this help?
xunholyx said:
If you aren't going to do what I asked of you, then I can't help you.
Click to expand...
Click to collapse
This is the at&t ru installed provided from the htc support website

My results
xunholyx said:
If you aren't going to do what I asked of you, then I can't help you.
Click to expand...
Click to collapse
Does this help?

ALBI SHTYLLA said:
Does this help?
Click to expand...
Click to collapse
Like I said before, post the results of fastboot getvar all
The app you are using is just reading from the build.prop and doesn't tell the information needed to find a proper RUU for you.

ALBI SHTYLLA said:
So i tryed to install the European Ruu from the htc site but without success.
Click to expand...
Click to collapse
They don't post the Euro RUUs on the HTC website. You flashed something else. Try providing the exact file name, instead of vague, incorrect statements like "European RUU" (which even if true - which its not - wouldn't tell us what version number Euro RUU).
---------- Post added at 12:46 PM ---------- Previous post was at 12:43 PM ----------
ALBI SHTYLLA said:
Does this help?
Click to expand...
Click to collapse
It really does not.
It only provides a portion of the info, and those apps often report incorrect info.
Do fastboot getvar all, as asked previously. If you can't manage doing that, you shouldn't be messing with the phone.

The results.
xunholyx said:
Post the results of fastboot getvar all minus your IMEI and serial#, and I or someone else here will be able to direct you to the right RUU/firmware
Click to expand...
Click to collapse
As you asked. Thanks.

What firmware should I flash? i am getting different software version information in bootloader and in settings> software info, page. What to do
here is the data from bootloader and screenshot from the cell.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:[COLOR="Red"] 4.28.502.1[/COLOR]
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: <removed>
(bootloader) imei: <removed>
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6768a7b1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

chshahid2k said:
What firmware should I flash? i am getting different software version information in bootloader and in settings> software info, page. What to do
here is the data from bootloader and screenshot from the cell.
(bootloader) version-main: 4.28.502.1
(bootloader) product: m8_ul
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: 11111111
Click to expand...
Click to collapse
What RUU to flash, indeed. You have a mess going on there.
Don't go by the screenshot, which shows Software version in Settings. It just corresponds to the currently installed ROM, which may be a Euro based (4.16.401.10)custom ROM; and really has no bearing on what RUU to run.
The getvar data is what you need to go by, but you have some conflicting info:
Model ID (MID) 0P6B13000 is for T-Mobile US. Product m8_ul would also correspond to T-Mob US (although other versions also are m8_ul, including Euro version). However, the main version 4.28.502.1 seems to indicate that someone flashed AT&T firmware to the device. CID 1111111 is SuperCID, which would also indicate the device was modified (as does the s-off indicator).
Since the phone is s-off, you have some options. Your best bet in your case is probably to change the MID, then flash the corresponding RUU. An unbranded variant's MID and RUU (such as Euro or Asia) is probably preferred, given your location. But what version exactly would somewhat depend on what band support you need for 3G and LTE for your carrier.

The results
redpoint73 said:
They don't post the Euro RUUs on the HTC website. You flashed something else. Try providing the exact file name, instead of vague, incorrect statements like "European RUU" (which even if true - which its not - wouldn't tell us what version number Euro RUU).
---------- Post added at 12:46 PM ---------- Previous post was at 12:43 PM ----------
It really does not.
It only provides a portion of the info, and those apps often report incorrect info.
Do fastboot getvar all, as asked previously. If you can't manage doing that, you shouldn't be messing with the phone.
Click to expand...
Click to collapse
Please help me....

ALBI SHTYLLA said:
Please help me....
Click to expand...
Click to collapse
Your getvar seems to indicate the phone was originally AT&T version based on product name m8_ul_ca and firmware version 6.20.502.5; but at some point someone tried to convert it to another version (s-off, superCID and Euro model ID). Either that conversion was not completed properly (otherwise it would not have ATT firmware number 6.20.502.5) or it was converted, but had ATT firmware flashed again later.
I assume you would prefer to use Euro RUU, as AT&T RUU is not preferred by most folks, unless you are in the US and an actual AT&T customer (even then, I'm on ATT, and I can't stand the ATT stock ROM).
If that is the case, you can try the Euro RUU here: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
This is a zip format RUU (not an exe) so follow the instructions in the post.
One thing I'm not sure of, is if the ATT firmware will interfere with the installation of this Euro RUU. If it doesn't install, we may need to do some additional steps, such as flash Euro RUU firmware.zip, then Euro RUU.

redpoint73 said:
What RUU to flash, indeed. You have a mess going on there.
Don't go by the screenshot, which shows Software version in Settings. It just corresponds to the currently installed ROM, which may be a Euro based (4.16.401.10)custom ROM; and really has no bearing on what RUU to run.
The getvar data is what you need to go by, but you have some conflicting info:
Model ID (MID) 0P6B13000 is for T-Mobile US. Product m8_ul would also correspond to T-Mob US (although other versions also are m8_ul, including Euro version). However, the main version 4.28.502.1 seems to indicate that someone flashed AT&T firmware to the device. CID 1111111 is SuperCID, which would also indicate the device was modified (as does the s-off indicator).
Since the phone is s-off, you have some options. Your best bet in your case is probably to change the MID, then flash the corresponding RUU. An unbranded variant's MID and RUU (such as Euro or Asia) is probably preferred, given your location. But what version exactly would somewhat depend on what band support you need for 3G and LTE for your carrier.
Click to expand...
Click to collapse
Thanks for the reply. Well I am from Pakistan, Middle East Region.
My OTA update thingy countinuously giving me notification about Update 4.16.401.13 is available (57.xx MB) but when its fully downloaded it gives me an error of "Variant Software Detected" and it doesnt install. I have once changed its MID to 0P6B10000 but it didnt work. Well I am getting more info in "Simple CID Getter" App. Some of the Info is attached.
Code:
[DEVICE_PROVISIONED]: [1]
[gsm.version.baseband]: [[email protected]_40.45.C33065.00_F]
[ro.aa.customizationid]: [980227]
[ro.aa.maincid]: [HTC__001]
[ro.aa.mainsku]: [401]
[ro.aa.modelid]:[COLOR="Red"] [0P6B10000][/COLOR]
[ro.aa.project]: [[COLOR="red"]M8_UL_L50_SENSE60_MR][/COLOR]
[ro.aa.romver]: [4.16.401.10]
[ro.aa.skulist]: [401]
[ro.aa.taskid]: [417003]
[ro.baseband]: [[email protected]]
[ro.bc_tmo]: [300]
[ro.board.platform]: [msm8974]
[ro.boot.baseband]: [[email protected]]
[ro.boot.batt_poweron]: [good_battery]
[ro.boot.bootloader]: [3.19.0.0000]
[ro.boot.carrier]: [ALL]
[ro.boot.ddrmid]: [(0x3)]
[ro.bootloader]: [3.19.0.0000]
[ro.build.buildline]:[COLOR="red"] [M8UL_HTC_WWE_L50_CRC_Sense60_Stable_MR][/COLOR]
[ro.build.changelist]: [448934]
[ro.build.characteristics]: [default]
[ro.build.date.utc]: [1421333072]
[ro.build.date]: [四 1月 15 22:44:32 CST 2015]
[ro.build.description]: [4.16.401.10 CL448934 release-keys]
[ro.build.display.id]: [LRX22C release-keys]
[ro.build.fingerprint]: [htc/htc_europe/htc_m8:5.0.1/LRX22C/448934.10:user/release-keys]
[ro.build.host]: [ABM101]
[ro.build.id]: [LRX22C]
[ro.build.languageremove]: []
[ro.build.product]: [htc_m8]
[ro.build.project]: [M8_UL_L50_SENSE60_MR:417003]
[ro.build.sense.version]: [6.0]
[ro.build.sku]: [HTC Europe]
[ro.build.tags]: [release-keys]
[ro.build.type]: [user]
[ro.build.user]: [buildteam]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.htcsdk]: [HTCExt:HTCExtension_Sense60_L_2;SDK:6.55;hdkbase:19.2]
[ro.build.version.incremental]: [448934.10]
[ro.build.version.release]: [5.0.1]
[ro.build.version.sdk]: [21]
[ro.carrier]: [unknown]
[ro.chipset.model]: [MSM8974]
[ro.chipset.vendor]: [QCT]
[ro.chipset.version]: [1.x]
[ro.chk_prd]: [1]
[ro.cid]: [T-MOB010]
[ro.com.android.dataroaming]: [false]
[ro.com.android.dateformat]: [MM-dd-yyyy]
[ro.com.google.clientidbase]: [android-htc-rev]
[ro.com.google.gmsversion]: [5.0_r1]
[ro.config.alarm_alert]: [Alarm_Classic.ogg]
[ro.config.htc.enableCOTA]: [1]
[ro.customer.HTC__J15]: [PROJECT_G0005_flag, 0x0034]
[ro.customer.HTC__K18]: [PROJECT_G0005_flag, 0x0034]
[ro.customer.default]: [PROJECT_G0005_flag, 0x0034]
[ro.cwkey]: [CWS__001]
[ro.language.HTC__J15]: [LANGUAGE_ARA_flag, 0x0019]
[ro.language.HTC__K18]: [LANGUAGE_ISR_flag, 0x0038]
[ro.language.default]: [LANGUAGE_WWE_flag, 0x0000]
[ro.lb]: [1]
[ro.mid]: [COLOR="red"][0P6B13000][/COLOR]
[ro.product.manufacturer]: [HTC]
[ro.product.model]: [HTC One_M8]
[ro.product.name]: [htc_europe]
[ro.product.ram]: [2GB]
[ro.product.version]: [4.16.401.10]
[ro.ril.vmail.22201]: [41901,I TIM]
[ro.ril.vmail.22210]: [42020,Vodafone IT]
[ro.ril.vmail.22288]: [4200,I WIND]
[ro.ril.vmail.22299]: [4133,3ITA]
[ro.ril.vmail.23410]: [901,O2 UK,905,TESCO,443,giffgaff]
[ro.ril.vmail.23415]: [1571,BT,121,VDF UK]
As i highlighed i can see different MID in it.
Tell me what to do? Can i have MarshMallow Official ROM (if any) directly flashed over the current version using stock recovery or adb.
Can i flash this OTA Update on it? All In One - [OTA] Firmware 4.16.401.13 + NoRedText HBOOT + TWRP 2.8.7.0 Recovery
Thanks and Regards
Shahid

Used MZP factory baseband ver

I bought used Moto Z Play (after my first MZP got stolen) XT1635-02 and don't receive updates.
M8953_10229.50.0465R
ADDISON_ROW_cust
Is this official ROM? I tried root app from Google play and it says no root.
Sent from my XT1635-02 using Tapatalk

Hmm, can you show us a screenshot of About Phone (Settings app>About Phone), to show us what build you have please and other details?
If you have ADB on a computer, then you could also try getting the getvar info from the device (assuming you have minimal ADB and preferably the Motorola USB drivers too):
Boot the device to the bootloader. Connect the device to your computer via USB.
Open the ADB terminal on your computer and type 'fastboot getvar all' without quotes into the terminal. Press Enter.
Please copy and paste the command output into a post here - you may wish to omit IMEI from the output (but please state if it's present if you remove it). This output should be a list of your device variables including what stock firmware it has.

echo92 said:
Hmm, can you show us a screenshot of About Phone (Settings app>About Phone), to show us what build you have please and other details?
If you have ADB on a computer, then you could also try getting the getvar info from the device (assuming you have minimal ADB and preferably the Motorola USB drivers too):
Boot the device to the bootloader. Connect the device to your computer via USB.
Open the ADB terminal on your computer and type 'fastboot getvar all' without quotes into the terminal. Press Enter.
Please copy and paste the command output into a post here - you may wish to omit IMEI from the output (but please state if it's present if you remove it). This output should be a list of your device variables including what stock firmware it has.
Click to expand...
Click to collapse
could not insert image., will try later. Have to use image hosting site?
Build number: NPNS26.118-22-2-12

vokmed said:
could not insert image., will try later. Have to use image hosting site?
Build number: NPNS26.118-22-2-12
Click to expand...
Click to collapse
Apparently I don't have permission to post an attachment in this forum.
Sent from my XT1635-02 using Tapatalk

vokmed said:
I bought used Moto Z Play (after my first MZP got stolen) XT1635-02 and don't receive updates.
M8953_10229.50.0465R
ADDISON_ROW_cust
Is this official ROM? I tried root app from Google play and it says no root.
Sent from my XT1635-02 using Tapatalk
Click to expand...
Click to collapse
First off do we even know if the bootloader is unlocked if not then there is no way it is rooted. If the BL is unlocked is there any sign of a root app such as SU or Magisk? Being you had this same model before it was stolen, does any of the software seem different or missing any sign that the phone is rooted?

Jimi Mack said:
First off do we even know if the bootloader is unlocked if not then there is no way it is rooted. If the BL is unlocked is there any sign of a root app such as SU or Magisk? Being you had this same model before it was stolen, does any of the software seem different or missing any sign that the phone is rooted?
Click to expand...
Click to collapse
There is no sign of Magisk or SU. Comparing boxes seems the same model and the other phone had already security update on about january 12 installed. On current used phone , December 1st 2017 security patch. Could it be unlocked, flashed with different ROM? IMEI matches Packaging box label. And when I check about phone it has: ADDISON_ROW_cust, is that mean custom ROM?
In regards to fastboot, I'll have to buy usb cable, got stolen from my carry on in airport.

Jimi Mack said:
First off do we even know if the bootloader is unlocked if not then there is no way it is rooted. If the BL is unlocked is there any sign of a root app such as SU or Magisk? Being you had this same model before it was stolen, does any of the software seem different or missing any sign that the phone is rooted?
Click to expand...
Click to collapse
vokmed said:
There is no sign of Magisk or SU. Comparing boxes seems the same model and the other phone had already security update on about january 12 installed. On current used phone , December 1st 2017 security patch. Could it be unlocked, flashed with different ROM? IMEI matches Packaging box label. And when I check about phone it has: ADDISON_ROW_cust, is that mean custom ROM?
In regards to fastboot, I'll have to buy usb cable, got stolen from my carry on in airport.
Click to expand...
Click to collapse
{
"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"
}

I don't know if you can flash stock with locked bootloader, but if you want to make sure you can flash this one , it's the latest ROM.
Btw: if you are on December 2017 patch level then it's no surprise you don't receive Updates, there are none

Artim_96 said:
I don't know if you can flash stock with locked bootloader, but if you want to make sure you can flash this one , it's the latest ROM.
Btw: if you are on December 2017 patch level then it's no surprise you don't receive Updates, there are none
Click to expand...
Click to collapse
I had a January update on my stolen phone...
Sent from my XT1635-02 using Tapatalk

vokmed said:
I had a January update on my stolen phone...
Click to expand...
Click to collapse
Well, that can't be January 2018 since that one isn't released yet

echo92 said:
Hmm, can you show us a screenshot of About Phone (Settings app>About Phone), to show us what build you have please and other details?
If you have ADB on a computer, then you could also try getting the getvar info from the device (assuming you have minimal ADB and preferably the Motorola USB drivers too):
Boot the device to the bootloader. Connect the device to your computer via USB.
Open the ADB terminal on your computer and type 'fastboot getvar all' without quotes into the terminal. Press Enter.
Please copy and paste the command output into a post here - you may wish to omit IMEI from the output (but please state if it's present if you remove it). This output should be a list of your device variables including what stock firmware it has.
Click to expand...
Click to collapse
Ok, here we go:
icrosoft Windows [Version 6.1.7601]
opyright (c) 2009 Microsoft Corporation. All rights reserved.
:\Users\Xxxxxx>fastboot getvar all
bootloader) version: 0.5
bootloader) version-bootloader: moto-msm8953-C1.13
bootloader) product: addison
bootloader) board: addison
bootloader) secure: yes
bootloader) hwrev: P7
bootloader) radio: 2
bootloader) storage-type: emmc
bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
bootloader) cpu: MSM8953
bootloader) serialno: ZY223NK9ZF
bootloader) cid: 0x0032
bootloader) channelid: 0x80
bootloader) uid: 0965095100000000000000000000
bootloader) securestate: oem_locked
bootloader) iswarrantyvoid: no
bootloader) max-download-size: 536870912
bootloader) reason: Volume down key pressed
bootloader) imei: XXXXXXXXXXXXXXX
bootloader) meid:
bootloader) date: 11-06-2016
bootloader) sku: XT1635-02
bootloader) battid: SNN5974A
bootloader) iccid:
bootloader) cust_md5:
bootloader) max-sparse-size: 268435456
bootloader) current-time:
bootloader) ro.build.fingerprint[0]: motorola/addison/addison:7.1.1/NPN
bootloader) ro.build.fingerprint[1]: S26.118-22-2-12/15:user/release-ke
bootloader) ro.build.fingerprint[2]: ys
bootloader) poweroffalarm: 0
bootloader) ro.build.version.full[0]: Blur_Version.26.241.15.addison.re
bootloader) ro.build.version.full[1]: tail.en.US
bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
bootloader) version-baseband: M8953_10229.50.04.65R ADDISON_ROW_CUST
bootloader) kernel.version[0]: Linux version 3.18.31-perf-gdc74c68 (hud
bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT T
bootloader) kernel.version[3]: ue Dec 5 06:42:56 CST 2017
bootloader) sbl1.git: git=MBM-NG-VC1.13-0-g12bcf78
bootloader) rpm.git: git=5578f74
bootloader) tz.git: git=82f94af-dirty
bootloader) devcfg.git: git=82f94af-dirty
bootloader) keymaster.git: git=82f94af-dirty
bootloader) cmnlib.git: git=82f94af-dirty
bootloader) cmnlib64.git: git=82f94af-dirty
bootloader) prov.git: git=82f94af-dirty
bootloader) aboot.git: git=MBM-NG-VC1.13-0-gd027fe9
bootloader) qe: qe 0/0
bootloader) frp-state: protected (77)
bootloader) ro.carrier: retca
ll: listed above
inished. total time: 0.102s

vokmed said:
Ok, here we go:
icrosoft Windows [Version 6.1.7601]
opyright (c) 2009 Microsoft Corporation. All rights reserved.
:\Users\Xxxxxx>fastboot getvar all
bootloader) version: 0.5
bootloader) version-bootloader: moto-msm8953-C1.13
<snip>
bootloader) securestate: oem_locked
bootloader) iswarrantyvoid: no
bootloader) max-download-size: 536870912
bootloader) reason: Volume down key pressed
<snip>
bootloader) ro.build.fingerprint[0]: motorola/addison/addison:7.1.1/NPN
bootloader) ro.build.fingerprint[1]: S26.118-22-2-12/15:user/release-ke
bootloader) ro.build.fingerprint[2]: ys
bootloader) poweroffalarm: 0
bootloader) ro.build.version.full[0]: Blur_Version.26.241.15.addison.re
bootloader) ro.build.version.full[1]: tail.en.US
bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
bootloader) version-baseband: M8953_10229.50.04.65R ADDISON_ROW_CUST
bootloader) kernel.version[0]: Linux version 3.18.31-perf-gdc74c68 (hud
bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT T
bootloader) kernel.version[3]: ue Dec 5 06:42:56 CST 2017
bootloader) sbl1.git: git=MBM-NG-VC1.13-0-g12bcf78
bootloader) rpm.git: git=5578f74
bootloader) tz.git: git=82f94af-dirty
bootloader) devcfg.git: git=82f94af-dirty
bootloader) keymaster.git: git=82f94af-dirty
bootloader) cmnlib.git: git=82f94af-dirty
bootloader) cmnlib64.git: git=82f94af-dirty
bootloader) prov.git: git=82f94af-dirty
bootloader) aboot.git: git=MBM-NG-VC1.13-0-gd027fe9
bootloader) qe: qe 0/0
bootloader) frp-state: protected (77)
bootloader) ro.carrier: retca
ll: listed above
inished. total time: 0.102s
Click to expand...
Click to collapse
Thanks for that. A few things:
1)Your iswarrantyvoid flag is still no, so suggests the previous owner did not unlock the bootloader. The warranty is still with the previous owner however, I'm not sure if Motorola will honour the warranty if you have any issues.
2)You have the December 2017 7.1.1 firmware on your device. As Artim_96 has pointed out, that seems to be the latest stock firmware for Moto Z Play devices. You'd likely only have a January 2018 patch with a custom ROM or perhaps if you were with the Motorola Feedback Network? Either way, you aren't expecting OTA updates yet (seems Oreo is in the works).
3)The baseband matches up with the baseband in that December 2017 stock ROM too:
Code:
BUILD REQUEST INFO:
SW Version: addison-user 7.1.1 NPNS26.118-22-2-12 15 release-keysM8953_10229.50.04.65R
MBM Version: C1.13
Modem Version: M8953_10229.50.04.65R
FSG Version: FSG-8953-04.90
Build Fingerprint: motorola/addison/addison:7.1.1/NPNS26.118-22-2-12/15:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 26.241.15.addison.retail.en.US
Model Number: XT1635-02
Android Version: 7.1.1
Baseband Version: M8953_10229.50.04.65R
Build Id: NPNS26.118-22-2-12
SW Display Build ID: NPNS26.118-22-2-12
Build Date: Tue Dec 5 06:32:05 CST 2017
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.26.241.15.addison.retail.en.US
Version when read from CPV: addison-user 7.1.1 NPNS26.118-22-2-12 15 release-keys
AB Update Enabled: False
Full Treble Enabled: False
In summary, looks like you have the latest firmware on your device and the previous owner did not attempt to unlock the bootloader, so you should have Android Pay and Moto Mods active.

Thank you for prompt reply, appreciated!!!
1 - Even if I request a proof of of purchase from original owner? (when unlocked and re locked that flag will show "yes"?
2 - My other MotoZplay were getting security patches like a clock work once a month,...
3 - Reason all started that I cannot read NFC with it, it's enabled from menu
echo92 said:
Thanks for that. A few things:
1)Your iswarrantyvoid flag is still no, so suggests the previous owner did not unlock the bootloader. The warranty is still with the previous owner however, I'm not sure if Motorola will honour the warranty if you have any issues.
2)You have the December 2017 7.1.1 firmware on your device. As Artim_96 has pointed out, that seems to be the latest stock firmware for Moto Z Play devices. You'd likely only have a January 2018 patch with a custom ROM or perhaps if you were with the Motorola Feedback Network? Either way, you aren't expecting OTA updates yet (seems Oreo is in the works).
3)The baseband matches up with the baseband in that December 2017 stock ROM too:
Code:
BUILD REQUEST INFO:
SW Version: addison-user 7.1.1 NPNS26.118-22-2-12 15 release-keysM8953_10229.50.04.65R
MBM Version: C1.13
Modem Version: M8953_10229.50.04.65R
FSG Version: FSG-8953-04.90
Build Fingerprint: motorola/addison/addison:7.1.1/NPNS26.118-22-2-12/15:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 26.241.15.addison.retail.en.US
Model Number: XT1635-02
Android Version: 7.1.1
Baseband Version: M8953_10229.50.04.65R
Build Id: NPNS26.118-22-2-12
SW Display Build ID: NPNS26.118-22-2-12
Build Date: Tue Dec 5 06:32:05 CST 2017
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.26.241.15.addison.retail.en.US
Version when read from CPV: addison-user 7.1.1 NPNS26.118-22-2-12 15 release-keys
AB Update Enabled: False
Full Treble Enabled: False
In summary, looks like you have the latest firmware on your device and the previous owner did not attempt to unlock the bootloader, so you should have Android Pay and Moto Mods active.
Click to expand...
Click to collapse

vokmed said:
Thank you for prompt reply, appreciated!!!
1 - Even if I request a proof of of purchase from original owner? (when unlocked and re locked that flag will show "yes"?
2 - My other MotoZplay were getting security patches like a clock work once a month,...
3 - Reason all started that I cannot read NFC with it, it's enabled from menu
Click to expand...
Click to collapse
1) You could get a proof of purchase from the original owner, if they're willing to give it to you. However, the warranty legal info does suggest the warranty is only awarded to the original purchaser and not transferable (this is for the UK: https://motorola-global-en-uk.custh...233517/redirect/1/filename/Warranty_EN_24.pdf ) However, depending on your local consumer protection laws, you may be able to get a repair. That being said, if the device is still in its warranty period (which is usually between 1-2 years), you could always try for a warranty repair, as the service centre may check the IMEI. Your experience may vary.
2)Yeah, seems that the Z Play updates are on hold whilst the Oreo update is being tested (since I've not seen any OTA updates, and the test build for Oreo seems to come with the February 2018 patch), so it's possible normal service and updates will resume once the new OS is deployed.
3)Hmm, that's odd - how are you testing NFC (I'm guessing with debit/credit cards?), is Android Pay working okay?

echo92 said:
1) You could get a proof of purchase from the original owner, if they're willing to give it to you. However, the warranty legal info does suggest the warranty is only awarded to the original purchaser and not transferable (this is for the UK: https://motorola-global-en-uk.custh...233517/redirect/1/filename/Warranty_EN_24.pdf ) However, depending on your local consumer protection laws, you may be able to get a repair. That being said, if the device is still in its warranty period (which is usually between 1-2 years), you could always try for a warranty repair, as the service centre may check the IMEI. Your experience may vary.
2)Yeah, seems that the Z Play updates are on hold whilst the Oreo update is being tested (since I've not seen any OTA updates, and the test build for Oreo seems to come with the February 2018 patch), so it's possible normal service and updates will resume once the new OS is deployed.
3)Hmm, that's odd - how are you testing NFC (I'm guessing with debit/credit cards?), is Android Pay working okay?
Click to expand...
Click to collapse
NFC I tested with tags that created with other MZP phone. With Android Pay I got only Amex card that I can add to AP and I haven't tested yet.
Thank for explaining my questions.
Sent from my XT1635-02 using Tapatalk

vokmed said:
NFC I tested with tags that created with other MZP phone. With Android Pay I got only Amex card that I can add to AP and I haven't tested yet.
Thank for explaining my questions.
Sent from my XT1635-02 using Tapatalk
Click to expand...
Click to collapse
Just a thought, is it possible the NFC tags are linked to your other device? I wonder if a new NFC tag would register okay on your replacement device.
Could be worth seeing if the Amex card works.

echo92 said:
Just a thought, is it possible the NFC tags are linked to your other device? I wonder if a new NFC tag would register okay on your replacement device.
Could be worth seeing if the Amex card works.
Click to expand...
Click to collapse
Just tried with new tags from tagger.com with the case on and off in just a possibility of case blocking signal and ii does not work.
Sent from my XT1635-02 using Tapatalk

vokmed said:
Just tried with new tags from tagger.com with the case on and off in just a possibility of case blocking signal and ii does not work.
Sent from my XT1635-02 using Tapatalk
Click to expand...
Click to collapse
[SOLVED] Just tried again and it worked, I guess I forgot about this weird antenna placement in top right corner that I did not move tags high enough...

Jiofi 3 jmr540 Unlocking.

Recently I've been googling on how to unlock my jiofi jmr540 device and found nothing.
But I discovered something else. I don't think we need a custom rom to unlock the device. I'm not a expert in these stuff.
Every jiofi device has web UI.
I discovered that every jiofi device have a hidden web UI that is engineer mode.
I didn't find any rom for my device but I found for jmr520 which was in bin format. I opened it using notepad in my pc and discovered that engineer mode does exist in its coding. There is lots of options present in engineer mode like manually selecting network band, choosing between 2g, 3g, and 4g, manual network search, and I also saw some network unlock coding which I couldn't understand by entering unlock code.
Can anyone help to access engineer mode in my device. I think it is also a html just like jiofi.local.html.
It would be really great if someone helped as many jiofi users are still wanting to unlock the device.
My device details are,
Firmware Version: FXN_JMR540_R6.11
Hardware Version: FXN_JMR540_V055
Device manufacturer : Foxconn

Interesting. Did you have any success?

mGforCe said:
Interesting. Did you have any success?
Click to expand...
Click to collapse
Nope. I gave up. Jiofi is not like other devices. Other devices can be configured using data cables from any computers with the device configuration software. But jiofi can be configured only using Web UI. That is the MAJOR problem.

How to enter in engineer mode in jiofi jrm520
How to enter in engineer mode in jiofi jrm520

None of the blue whales in this ocean can fix it?

Found Some interesting Facts on JIOFI3 ( JMR540 )
I managed to make the device into FASTBOOT.
using ANDROID BOOTLOADER INTERFACE.
Able to ping the hardware and get the following:
(bootloader) version:0.5
(bootloader) version-baseband:
(bootloader) version-bootloader:V055
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x8000000
(bootloader) serialno:8*32***4
(bootloader) kernel:lk
(bootloader) product:JioFi3
Click to expand...
Click to collapse
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel: OKAY

Any firmware available till now , mdm9607 firmware can be flashed via adb.... if anyone has firmware kindly share :
unlocked devices are sold at alibaba JMR541, both are same chipset
https://www.alibaba.com/product-det...?spm=a2700.details.deiletai6.2.2ea36c5acxqHqD

tr

Jio-fi-3 JMR_541
how did you did that @ Electroboy_Prakash

Electroboy_Prakash said:
Found Some interesting Facts on JIOFI3 ( JMR540 )
I managed to make the device into FASTBOOT.
using ANDROID BOOTLOADER INTERFACE.
Able to ping the hardware and get the following:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel: OKAY
Click to expand...
Click to collapse
How did you get fastboot menu? Can you extract firmware and send it.

Here is another jio fi 2. You can log in to Jio fi. Use 192.168. Username Administrator Password is written on Jio Fi box.
ODMPegasusProduct IDM2
IMEI 911522-----------
Firmware VersionPEG_M2_B38.2Firmware Creation Date2019-11-29
Frequency Bands Supported B3,B5,B 40

I've managed it to unlock this device. Enabled diagnostic mode and adb. Custom firmwares are possible in this devices. Once modified firmware can be flashed via fastboot mode which is easily accessible without any modification.
Check my Twitter thread here https://twitter.com/ab_hi_j/status/1395394412545515521
{
"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"
}

Can you help me with the procedure i also want to unlock my jiofi3

sksinha said:
Can you help me with the procedure i also want to unlock my jiofi3
Click to expand...
Click to collapse
Here is the unlocking guide
[GUIDE][UPDATED] Unlocking JioFi 3 JMR540 & JMR541 for all networks
Unlocked Firmware for JioFi 3 JMR540 & JMR541 Disclaimer I am not responsible for any kind of damage to your device. Use this firmware at your own risk Post is for educational purpose only. ONLY FOR JMR 540 & JMR 541 I was able to dump and...
forum.xda-developers.com

Vismay G S said:
Recently I've been googling on how to unlock my jiofi jmr540 device and found nothing.
But I discovered something else. I don't think we need a custom rom to unlock the device. I'm not a expert in these stuff.
Every jiofi device has web UI.
I discovered that every jiofi device have a hidden web UI that is engineer mode.
I didn't find any rom for my device but I found for jmr520 which was in bin format. I opened it using notepad in my pc and discovered that engineer mode does exist in its coding. There is lots of options present in engineer mode like manually selecting network band, choosing between 2g, 3g, and 4g, manual network search, and I also saw some network unlock coding which I couldn't understand by entering unlock code.
Can anyone help to access engineer mode in my device. I think it is also a html just like jiofi.local.html.
It would be really great if someone helped as many jiofi users are still wanting to unlock the device.
My device details are,
Firmware Version: FXN_JMR540_R6.11
Hardware Version: FXN_JMR540_V055
Device manufacturer : Foxconn
Click to expand...
Click to collapse
need this. please take look

abhimortal6 said:
Here is the unlocking guide
[GUIDE][UPDATED] Unlocking JioFi 3 JMR540 & JMR541 for all networks
Unlocked Firmware for JioFi 3 JMR540 & JMR541 Disclaimer I am not responsible for any kind of damage to your device. Use this firmware at your own risk Post is for educational purpose only. ONLY FOR JMR 540 & JMR 541 I was able to dump and...
forum.xda-developers.com
Click to expand...
Click to collapse
I have accidentally erased the recovery partition of JMR540 and my jiofi not starting always go in fastboot mode. Can you please provide boot.img file of JMR540 jiofi.

message removed

Jio pushed new firmware JMR540 and following changes are made.
-> locked boot loader
-> TTL RX disabled so we are not able to access root shell via UART.
only option to unlock modem is
-> boot modem to EDL( Emergency Download Mode) mode.
-> take backup and flash old recovery via QPST (qualcomm firehose prog file required for MDM9207)
@abhimortal6
sorry for chasing you again. Hope you know the exact procedure.
Can you share
1) EDL points for JMR 540 to short and boot to EDL mode.
2) Qualcomm firehose prog file for MDM9207

It's fine @jithinvp4, okay so there's no exact test points you can short. Trick is to stop power to EMMC for fraction of a second while booting. There's a single resistor 2nd one from bottom in left of EMMC. You can use RPi pico to build brute switch.
If done correctly while booting it'll fail and fall to un-secure download mode. Yes you read that right un-secure it's an old Qualcomm thing.
I had chat with one of Manager/People from JioFi device team after first exploit. I'm not sure they'll fix this too. It's doable I think. Not sure if they'll do this because not everyone can do this. So yeah private exploit is still there

@abhimortal6 Thanks for your response.
I was spending too much time for last few weeks to find a method to unlock JMR 540 . I thought there is a test-point . Don't have much knowledge to use RPi pico.
please let me know any other simple method available to boot EDL .
Otherwise i will be monitoring your tread for your next unlock solution.