Related
I need a Little help regarding identifying my version of M8
I have looked up the imie number on IMIE Data website and found that its a AT&T US Unlocked Phone.
Now when i try to flash the latest firmware for AT&T through RUU file it gets stuck at sending file stage 1/6 .... ( I have waited about 15 minutes, nothing happened)
Then I have also tried to flash unlocked version firmware and this time i have recieved ERROR 155 - IT says the device is not matching with firmware.
After that i have downloaded some apps from play store related to phone info search.
All these apps are suggesting that its a Sprint_WWE phone.
My phone does not have any logo on it or any bloat ware from the career.
I am confused now, which version of M8 i am using and which firmware RUU should i flash?
Please note: My Bootloader is in locked state and official recovery installed. Never rooted or CWM installed.
I am using this phone in Bangladesh right now so OTA is not coming to my phone.
fastboot getvar all without serial & imei no. will tell your device version.
where should i type it in?
G:\Android\Nexus 7 Wifi\AndroidSDKSlim\android-sdk-windows\platform-tools>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.30.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000499076047
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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: b9f91aef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.027s
Click to expand...
Click to collapse
This is what i got which version is it?
tpteam6 said:
This is what i got which version is it?
Click to expand...
Click to collapse
It might be AT&T branded, but, according to the CID#, your device is completely unlocked and you can basically flash anything. However, you can't flash an AT&T RUU unless you change the CID# back to the default AT&T CID.
(bootloader) product: m8_whl
Click to expand...
Click to collapse
isnt this is for sprint?
and how do i get back to the default CID?
i have tried AT&T, SPRINT & Unlocked Version RUU nothing worked.
AT&T RUU Stucked at sending files,
Sprint RUU Gave ERROR 155
Unlocked RUU Gave ERROR 155 As well.
tpteam6 said:
This is what i got which version is it?
Click to expand...
Click to collapse
First, remove serial & imei no.
m8_whl is a sprint device.
Don't ever install any GSM firmware on your device, it'll brick the radio
but i am using gsm network here. its not a CDMA device..
tpteam6 said:
but i am using gsm network here. its not a CDMA device..
Click to expand...
Click to collapse
Yeah I know you're on GSM network. My advise was never install a GSM firmware like AT&T, Intl GSM & etc. Only Sprint firmware.
then should i set the CID to default Sprint CID? and what is that?
i need help here.. how can i update to lollypop or marshmellow? i have downloaded sprint RUU file but getting error 155. Should i reset the CID to some thing other than "11111111"? please advice.
tpteam6 said:
i need help here.. how can i update to lollypop or marshmellow? i have downloaded sprint RUU file but getting error 155. Should i reset the CID to some thing other than "11111111"? please advice.
Click to expand...
Click to collapse
The Sprint RUU should run fine with SuperCID (11111111).
Error 155 typically means your bootloader is unlocked (which will block RUU). Relock it with the command (run the same way you did fastboot getvar all):
fastboot oem lock
---------- Post added at 10:45 AM ---------- Previous post was at 10:43 AM ----------
tpteam6 said:
but i am using gsm network here. its not a CDMA device..
Click to expand...
Click to collapse
The Sprint version supports CDMA and GSM networks. It doesn't matter whether you are using CDMA or not, its still the "CDMA" (supports CDMA) version of the M8.
But on fasboot im seeing "Botloader status is locked"
Ragarianok said:
It might be AT&T branded, but, according to the CID#, your device is completely unlocked and you can basically flash anything. However, you can't flash an AT&T RUU unless you change the CID# back to the default AT&T CID.
Click to expand...
Click to collapse
1) The product name (m8_whl), model number (0P6B70000), and version number (x.xx.651.xx) all point to this being the Sprint version. The IMEI search coming up with AT&T is odd, and almost certainly incorrect.
2) SuperCID doesn't quite mean you can "flash anything". As ckpv5 pointed out, you can't flash GSM firmware to the Sprint (or Verizon) device, or the result is a radio brick. More commonly, even for the GSM version, you will often need to change the MID to run other version RUUs.
3) The proper version RUU will run fine with SuperCID.
---------- Post added at 10:56 AM ---------- Previous post was at 10:54 AM ----------
tpteam6 said:
But on fasboot im seeing "Botloader status is locked"
Click to expand...
Click to collapse
What is the exact file name of the RUU you are trying to run?
Link the source, if you can.
D:\Android\Nexus 5\AndroidSDKSlim Nexus 5\android-sdk-windows\platform-tools>fastboot oem writecid 11111111
< waiting for device >
...
(bootloader) Start Verify: 0
(bootloader) Input CID is super CID
(bootloader) Start Verify: 0
OKAY [ 0.028s]
finished. total time: 0.028s
D:\Android\Nexus 5\AndroidSDKSlim Nexus 5\android-sdk-windows\platform-tools>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.012s]
finished. total time: 0.012s
D:\Android\Nexus 5\AndroidSDKSlim Nexus 5\android-sdk-windows\platform-tools>
tpteam6 said:
But on fasboot im seeing "Botloader status is locked"
Click to expand...
Click to collapse
On the hboot screen, what does it say near the top LOCKED, RELOCKED or UNLOCKED?
lollypop:
RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_4.25.651.14_Radio_1.09.20.0209_NV_SPCS_1.52_003_release_426232_signed_2
http://www.droidviews.com/restore-sprint-htc-one-m8-to-stock-rom-with-ruu/
I have downloaded it from a third party site.
Marshmellow
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3
http://www.htc.com/us/support/htc-one-m8-sprint/news/
I Have dowloaded it from HTC Site
redpoint73 said:
On the hboot screen, what does it say near the top LOCKED, RELOCKED or UNLOCKED?
Click to expand...
Click to collapse
Its Saying "Locked"
redpoint73 said:
1) The product name (m8_whl), model number (0P6B70000), and version number (x.xx.651.xx) all point to this being the Sprint version. I don't see why you think its AT&T.
2) SuperCID doesn't quite mean you can "flash anything". As ckpv5 pointed out, you can't flash GSM firmware to the Sprint (or Verizon) device, or the result is a radio brick. More commonly, even for the GSM version, you will often need to change the MID to run other version RUUs.
3) The proper version RUU will run fine with SuperCID.
I understand and appreciate you are trying to be helpful. But please try to verify the information, before passing them along. Especially in this case, the advice could have resulted in permanent damage the OP's device.
---------- Post added at 10:56 AM ---------- Previous post was at 10:54 AM ----------
What is the exact file name of the RUU you are trying to run?
Link the source, if you can.
Click to expand...
Click to collapse
When i search my imie on Imie data site i get that its a AT&T device
Do i need to root or custom recovery to update via RUU?
Dear XDA-developers,
I have copy of HTC U11 Eyes Stock ROM and I'd like to get root any one interested to help?
Need U11 Eyes Stock ROM
Hi is there anyone that has a stock ROM for the HTC U11 Eyes? I have an S-OFF device. Thanks!
(bootloader) kernel: lk
(bootloader) product: htc_haydugl
(bootloader) version: 1.0
(bootloader) max-download-size: 1473600000
(bootloader) serialno: HT7AT1D00064
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 353223090027393
(bootloader) version-main: 1.03.999.1
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2Q4R10000
(bootloader) cid: 11111111
ShinGaiven said:
Hi is there anyone that has a stock ROM for the HTC U11 Eyes? I have an S-OFF device. Thanks!
(bootloader) kernel: lk
(bootloader) product: htc_haydugl
(bootloader) version: 1.0
(bootloader) max-download-size: 1473600000
(bootloader) serialno: HT7AT1D00064
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 353223090027393
(bootloader) version-main: 1.03.999.1
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2Q4R10000
(bootloader) cid: 11111111
Click to expand...
Click to collapse
Sorry for being late, kindly find the stock ROM for HTC U11 Eyes in below link
https://drive.google.com/file/d/1l06p8Gc5zJ1csnH6knVOKbFPunlBpD08/view?usp=drivesdk
What is S-OFF mean?
Maybe someone can work with this and try to get it working... https://htcfz.wordpress.com/2018/01/13/htc-u11-eyes-twrp-recovery-untest/
http://theroot.ninja/faq.html
Why should I s-off when I can just unlock?
With an unlocked bootloader, you are able to flash and run custom recoveries, ROMs, and kernels. This is enough for many users. With s-off you have full control of the device. You can do things like flash radios and custom hboots. You can even change properties like CID and MID that can allow you to convert to different editions of your device. If you are a true power user, you need s-off.
Click to expand...
Click to collapse
Alaioby79 said:
Sorry for being late, kindly find the stock ROM for HTC U11 Eyes in below link
https://drive.google.com/file/d/1l06p8Gc5zJ1csnH6knVOKbFPunlBpD08/view?usp=drivesdk
What is S-OFF mean?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
http://theroot.ninja/faq.html
Click to expand...
Click to collapse
Thanks for your reply
Did you download the Stock ROM file? I sent you the link already.
If you have any further questions just ask and I'll try to answer if I can
I did yes... I do not have device,but I can make an insecure boot image for you guy,if bootloaders are able to be unlocked,should at least enable device to get root...
Alaioby79 said:
Thanks for your reply
Did you download the Stock ROM file? I sent you the link already.
If you have any further questions just ask and I'll try to answer if I can
Click to expand...
Click to collapse
Wonders_Never_Cease said:
I did yes... I do not have device,but I can make an insecure boot image for you guy,if bootloaders are able to be unlocked,should at least enable device to get root...
Click to expand...
Click to collapse
Yes the bootloader can be unlocked from developer option.
I think sappbrook made a patched boot.img already... But Ill do one tomorrow morning as well...
Alaioby79 said:
Sorry for being late, kindly find the stock ROM for HTC U11 Eyes in below link
https://drive.google.com/file/d/1l06p8Gc5zJ1csnH6knVOKbFPunlBpD08/view?usp=drivesdk
What is S-OFF mean?
Click to expand...
Click to collapse
Hey, Thanks! is this the ROM that has China Sense version ? If so, I already got the same on my U11 eyes.
BTW regarding S-Off, When your device is set to S-OFF, the security is turned off. This allows you to modify any partition on the device, and changes will not be reset upon a reboot. Also, the signature checking of the firmware zips (ie: PJ75IMG.zip) is disabled, allowing users to flash unsigned firmware zips containing the separate images of the partitions. S-OFF gives the user great power over the device, but also comes with much responsibility to be careful.
@Alaioby79
https://www.androidfilehost.com/?w=files&flid=259861 patched boot.img
@ShinGaiven
ro.aa.maincid=HTC__621
ro.aa.cidlist=HTC__621,HTC__622,HTC__059
ro.aa.mainsku=709
Unsure @ chinese sense support
<item type="boolean" name="support_china_intelligence_feature">false</item>
<item type="boolean" name="support_china_sense_feature">false</item>
<item type="boolean" name="support_china_sense_typeb_feature">false</item>
<item type="boolean" name="support_china_sense_typeb_new_feature">false</item>
ShinGaiven said:
Hey, Thanks! is this the ROM that has China Sense version ? If so, I already got the same on my U11 eyes.
BTW regarding S-Off, When your device is set to S-OFF, the security is turned off. This allows you to modify any partition on the device, and changes will not be reset upon a reboot. Also, the signature checking of the firmware zips (ie: PJ75IMG.zip) is disabled, allowing users to flash unsigned firmware zips containing the separate images of the partitions. S-OFF gives the user great power over the device, but also comes with much responsibility to be careful.
Click to expand...
Click to collapse
Yes it is chinnese Stock ROM
Thanks for your clarification regarding S_OFF
Alaioby79 said:
Yes it is chinnese Stock ROM
Thanks for your clarification regarding S_OFF
Click to expand...
Click to collapse
So unfortunate for us right now..?
I got the same and I have to install the GMS app to have the Google services on the device..?
ShinGaiven said:
So unfortunate for us right now..?
I got the same and I have to install the GMS app to have the Google services on the device..
Click to expand...
Click to collapse
No no need, I bought my HTCU11 Eyes from Hong Kong and once I received and turned it on I had changed the language to English and to remove bloatware Chinese Apps and I have complete Gapps
Alaioby79 said:
No no need, I bought my HTCU11 Eyes from Hong Kong and once I received and turned it on I had changed the language to English and to remove bloatware Chinese Apps and I have complete Gapps
Click to expand...
Click to collapse
btw is it a DUGL version of ROM or DTWL? and what's the method used to flash the ROM and the patch boot? Downloading now and I'll see if this one works better than the one I got. Thanks!
ShinGaiven said:
btw is it a DUGL version of ROM or DTWL? and what's the method used to flash the ROM and the patch boot? Downloading now and I'll see if this one works better than the one I got. Thanks!
Click to expand...
Click to collapse
It's DUGL
Save the Stock RoOM on SD card and switch off the phone press volume down + power and reboot to download mode then choose recovery from SD card
Alaioby79 said:
It's DUGL
Save the Stock RoOM on SD card and switch off the phone press volume down + power and reboot to download mode then choose recovery from SD card
Click to expand...
Click to collapse
What's your device CID and MID? I tried flashing the RUU but doesn't push through. Getting Error 10 which means I have to change the MID and probably CID too.
ShinGaiven said:
What's your device CID and MID? I tried flashing the RUU but doesn't push through. Getting Error 10 which means I have to change the MID and probably CID too.
Click to expand...
Click to collapse
What is CID Nd MID?
Can one of you folks get me the vendor partition dump? Id appreciated it
Alaioby79 said:
What is CID Nd MID?
Click to expand...
Click to collapse
Thanks for sharing the file!! Got it done on my U11 eyes..Now it's working fine..BTW it's kinda hard to explain the definition of both CID and MID but MID stands for Model Identification. It's what I did to flash the RUU you shared, got to change the MID to 2Q410000.?
Hi guys anybody can help me ? My Htc one m8 has been bricked i can't flash stock ruu please help me
this are my fastboot getvar all value :
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.709.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *****
(bootloader) imei: ******
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.008s
so my bootlader is locked with security warning and software status : modified
Which RUU did your try (version number, file name)? And what does that mean you "can't flash stock ruu"? Did you get any error messages, what point did it fail, etc.?
You also need to tell us how it is "bricked"? Were you trying to flash something, or update, etc.? Or just happened on its own (failed to boot to OS)?
Did you do any mods to the phone, or is it (as far as you know) stock? For that matter, did you get the phone used?
redpoint73 said:
Which RUU did your try (version number, file name)? And what does that mean you "can't flash stock ruu"? Did you get any error messages, what point did it fail, etc.?
You also need to tell us how it is "bricked"? Were you trying to flash something, or update, etc.? Or just happened on its own (failed to boot to OS)?
Did you do any mods to the phone, or is it (as far as you know) stock? For that matter, did you get the phone used?
Click to expand...
Click to collapse
When i flash RUU faced with "remote : 12 signautre verify fail" and this is a RUU that i flashed : HTC One M8 6.20.709.2 sense 8
redpoint73 said:
Which RUU did your try (version number, file name)? And what does that mean you "can't flash stock ruu"? Did you get any error messages, what point did it fail, etc.?
You also need to tell us how it is "bricked"? Were you trying to flash something, or update, etc.? Or just happened on its own (failed to boot to OS)?
Did you do any mods to the phone, or is it (as far as you know) stock? For that matter, did you get the phone used?
Click to expand...
Click to collapse
when i unplugged the phone from charger this problem occurred i didn't flash any RUU later and my phone is unrooted .
mamali0067 said:
when i unplugged the phone from charger this problem occurred .
Click to expand...
Click to collapse
I assume when you say "bricked" it means you can't boot to Android OS, but you can get to bootloader (otherwise, you wouldn't have been able to do fastboot getvar).
On the bootloader screen, does it say LOCKED or UNLOCKED near the top?
Also, I recommend you delete IMEI and serial number from your top post. These are personal info, and should not be posted online (and also, not needed to help or advise you).
---------- Post added at 09:09 AM ---------- Previous post was at 09:09 AM ----------
mamali0067 said:
When i flash RUU faced with "remote : 12 signautre verify fail" and this is a RUU that i flashed : HTC One M8 6.20.709.2 sense 8
Click to expand...
Click to collapse
To confirm, the file actually says "RUU" in the file name, and about 1.5 GB in size?
redpoint73 said:
I assume when you say "bricked" it means you can't boot to Android OS, but you can get to bootloader (otherwise, you wouldn't have been able to do fastboot getvar).
On the bootloader screen, does it say LOCKED or UNLOCKED near the top?
Also, I recommend you delete IMEI and serial number from your top post. These are personal info, and should not be posted online (and also, not needed to help or advise you).
---------- Post added at 09:09 AM ---------- Previous post was at 09:09 AM ----------
To confirm, the file actually says "RUU" in the file name, and about 1.5 GB in size?
Click to expand...
Click to collapse
yes of course it's about 1.6 GB and in my bootloader it say LOCKED
mamali0067 said:
yes of course it's about 1.6 GB and in my bootloader it say LOCKED
Click to expand...
Click to collapse
Is this a zip format RUU? If so, cut/paste the exact commands you used.
redpoint73 said:
Is this a zip format RUU? If so, cut/paste the exact commands you used.
Click to expand...
Click to collapse
yes the RUU is a zip file , but i flashed that RUU perefer in finding right RUU thread and faced with remote : 12 signature verify fail
mamali0067 said:
i flashed that RUU perefer in finding right RUU thread
Click to expand...
Click to collapse
I'm not going to jump around threads looking for the info. I already told you that twice. You should be trying to make it easier for folks to help you, not harder!
redpoint73 said:
I'm not going to jump around threads looking for the info. I already told you that twice. You should be trying to make it easier for folks to help you, not harder!
Click to expand...
Click to collapse
Okay dude , so help me here !
mamali0067 said:
Okay dude , so help me here !
Click to expand...
Click to collapse
You didn't provide the info I asked for: cut/paste the exact commands you used
redpoint73 said:
You didn't provide the info I asked for: cut/paste the exact commands you used
Click to expand...
Click to collapse
Yes , I have been cutted and pasted the command
Hi all.
Got a HTC one m8 in and it appears to be stuck on the HTC screen, I can get into bootloader fine, have tried to reflash via SD card but i get a CID error.
Can anyone direct me to what ROM i need to be installing? Its a UK version.
Thanks in advance.
Jabbah said:
Hi all.
Got a HTC one m8 in and it appears to be stuck on the HTC screen, I can get into bootloader fine, have tried to reflash via SD card but i get a CID error.
Can anyone direct me to what ROM i need to be installing? Its a UK version.
Thanks in advance.
Click to expand...
Click to collapse
What does it say next to "OS" in your bootloader menu?
Jabbah said:
have tried to reflash via SD card but i get a CID error.
Can anyone direct me to what ROM i need to be installing? Its a UK version.
Click to expand...
Click to collapse
Tried to flash what? Can't troubleshoot what you did wrong, unless you tell is what you tried to flash. RUU, firmware.zip, or something else? What is the version number and file name?
That is in addition to the info requested in the previous reply.
Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the device.
redpoint73 said:
Tried to flash what? Can't troubleshoot what you did wrong, unless you tell is what you tried to flash. RUU, firmware.zip, or something else? What is the version number and file name?
That is in addition to the info requested in the previous reply.
Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the device.
Click to expand...
Click to collapse
Tried to flash a stock UK rom.
I have no idea how to use that command sorry.
os is 6.12.61.4
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.61.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Jabbah said:
Tried to flash a stock UK rom.
Click to expand...
Click to collapse
Still too vague for us to have any idea what you tried to flash.
I asked some specific questions for a reason; some of which you seem to have missed or ignored. I'm not just typing to exercise my fingers!
redpoint73 said:
RUU, firmware.zip, or something else?
What is the version number and file name?
Click to expand...
Click to collapse
"Stock UK ROM" can mean a number of things. If you are talking about RUU, then calling it a "stock ROM" is not the right term (and confusing) since RUU is a complete image containing something like 41 partitions, with the ROM being only one of those partitions.
In fact, if you are referring to RUU, I don't think your version M8 (or most UK versions, for that matter) has a valid RUU. So you are likely in fact not even trying to flash a stock UK ROM. Which also explains the CID error.
On a positive note, good work figuring out how to do fastboot getvar all. If you can provide more info on what you tried to flash, we can make some progress!
redpoint73 said:
Still too vague for us to have any idea what you tried to flash.
I asked some specific questions for a reason; some of which you seem to have missed or ignored. I'm not just typing to exercise my fingers!
"Stock UK ROM" can mean a number of things. If you are talking about RUU, then calling it a "stock ROM" is not the right term (and confusing) since RUU is a complete image containing something like 41 partitions, with the ROM being only one of those partitions.
In fact, if you are referring to RUU, I don't think your version M8 (or most UK versions, for that matter) has a valid RUU. So you are likely in fact not even trying to flash a stock UK ROM. Which also explains the CID error.
On a positive note, good work figuring out how to do fastboot getvar all. If you can provide more info on what you tried to flash, we can make some progress!
Click to expand...
Click to collapse
Thanks for the replies, ive actually gotten somewhere today, Ive installed twrp, and installed the latest Lineage ROM which booted fine .
But.... Not detecting sim card
Always something haha
Another option (especially now that you have unlocked the bootloader, and installed TWRP), is restore stock TWRP backup 6.12.61.4 from here:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
No need to do Step 3, nor Steps 10 or after (only relevant to get OTA updates - which no longer applies to this device). Just reboot.
Jabbah said:
Thanks for the replies
Click to expand...
Click to collapse
There is a button for that.
Quick update, Restored stock TWRP as you suggested, performed simunlock and am now a happy chappy with a working M8
Now, Whats the best ROM to use for it ? Is it worth installing Lineage ROM?
David.
Jabbah said:
Quick update, Restored stock TWRP as you suggested, performed simunlock and am now a happy chappy with a working M8
Now, Whats the best ROM to use for it ? Is it worth installing Lineage ROM?
Click to expand...
Click to collapse
Glad the TWRP restore worked out for you.
No such thing as a "best ROM". Each individual user has different preferences and tastes. That's the reason there are different ROM choices. If there was a "best ROM", nobody would ever need anything else, right?
I am not personally a Lineage user (so good example right there how one person's opinion may not apply to you). But if you flash it again, I assume you can (or will) have the same problem with SIM not detected. I think I've seen other folks with the problem on Lineage (again, I don't really keep up with that ROM), so you should check the thread to see if there is a fix for that issue.
redpoint73 said:
Glad the TWRP restore worked out for you.
No such thing as a "best ROM". Each individual user has different preferences and tastes. That's the reason there are different ROM choices. If there was a "best ROM", nobody would ever need anything else, right?
I am not personally a Lineage user (so good example right there how one person's opinion may not apply to you). But if you flash it again, I assume you can (or will) have the same problem with SIM not detected. I think I've seen other folks with the problem on Lineage (again, I don't really keep up with that ROM), so you should check the thread to see if there is a fix for that issue.
Click to expand...
Click to collapse
Got around the sim not detected issue, the phone was simlocked to orange, it just didnt pop up with the enter unlock code dialogue.
Ill try a few see what they are like
Thanks again for your help.
Jabbah said:
Got around the sim not detected issue, the phone was simlocked to orange.
Click to expand...
Click to collapse
Understood. I would not have expected the "SIM not detected" error in that case. So thanks for clarifying.
Jabbah said:
it just didnt pop up with the enter unlock code dialogue.
Click to expand...
Click to collapse
Stock (Sense) ROM is needed to unlock SIM. Which you either figured out, or stumbled upon the solution by luck! :good:
Hi everyone.
I know that when reading the title of my thread they can say "pfff just type the USSD code and look for the baseband in the configuration", but if it were that easy we will not be here.
I have this phone (Motorola Z2 Force) which at the time I changed the original ROM (do not ask why, please), at that time I installed a stock ROM that worked but has always generated the message "verity mode set to disable" at startup, that's because the ROM doesn't match the same version of ROM that was on the phone.
So now I want to go back to the original ROM, but I never wrote down what that firmware was, so I have no clue which ROM to look for. I tried installing several ROMs because I know the model of the phone and its variation, but even so there are many ROMs, some worked, some did not, some I did not even try because they are too many, but all that worked for me showed me the same message "verity mode set to disable".
I have tried to find out the exact ROM I had through data that is still true, such as the phone's serial number or IMEI code, but I can't find information on how to interpret those numbers, I can't find a "translator" to find out what Help me find out what my original stock ROM was.
Any ideas?
Loperaco said:
Hi everyone.
I know that when reading the title of my thread they can say "pfff just type the USSD code and look for the baseband in the configuration", but if it were that easy we will not be here.
I have this phone (Motorola Z2 Force) which at the time I changed the original ROM (do not ask why, please), at that time I installed a stock ROM that worked but has always generated the message "verity mode set to disable" at startup, that's because the ROM doesn't match the same version of ROM that was on the phone.
So now I want to go back to the original ROM, but I never wrote down what that firmware was, so I have no clue which ROM to look for. I tried installing several ROMs because I know the model of the phone and its variation, but even so there are many ROMs, some worked, some did not, some I did not even try because they are too many, but all that worked for me showed me the same message "verity mode set to disable".
I have tried to find out the exact ROM I had through data that is still true, such as the phone's serial number or IMEI code, but I can't find information on how to interpret those numbers, I can't find a "translator" to find out what Help me find out what my original stock ROM was.
Any ideas?
Click to expand...
Click to collapse
Go to fastboot and use the command "fastboot getvar all" minus the quotations. Post the report here with your IMEI blacked out and we can help you
There are a few posts here to help you get fastboot setup if you don't have it
Starkiller2 said:
Go to fastboot and use the command "fastboot getvar all" minus the quotations. Post the report here with your IMEI blacked out and we can help you
There are a few posts here to help you get fastboot setup if you don't have it
Click to expand...
Click to collapse
Hi Starkiller.
This what the command returns:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-43c7c77-190920
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: ROW
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SKHYNIX LP4x DIE=12Gb M5=06 M6=04 M7=00 M8=0D
(bootloader) cpu: MSM8998 2.1 (4)
(bootloader) serialno: ZY224WPP9T
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: 3E3684D8
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: XXXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 03-26-2018
(bootloader) sku: XT1789-05
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4346
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:9/PPX29.159-24/
(bootloader) ro.build.fingerprint[1]: e78f1:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.24.nash.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-06500-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g1f14820 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Fri Sep 20 09:23:35 CDT 2019
(bootloader) git:abl: MBM-3.0-nash_retail-43c7c77-190920
(bootloader) git:xbl: MBM-3.0-nash_retail-4fc2afc-190920
(bootloader) gitmic: MBM-3.0-nash_retail-4fc2afc-190920
(bootloader) git:rpm: MBM-3.0-nash_retail-404f7ba-190920
(bootloader) git:tz: MBM-3.0-nash_retail-3537781-190920
(bootloader) git:hyp: MBM-3.0-nash_retail-3537781-190920
(bootloader) git:devcfg: MBM-3.0-nash_retail-3537781-190920
(bootloader) git:cmnlib: MBM-3.0-nash_retail-3537781-190920
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-3537781-190920
(bootloader) git:keymaster: MBM-3.0-nash_retail-3537781-190920
(bootloader) git:storsec: MBM-3.0-nash_retail-3537781-190920
(bootloader) gitrov: MBM-3.0-nash_retail-3537781-190920
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retla
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip - according to your getvar output - this is teh correct model (-05), and corresponds to the currently installed bootloader (159.y).
OR
If you mean you flashed a different firmware, you definitely have a -05 model, so it's:
1. https://mirrors.lolinet.com/firmware/moto/nash/official/RETLA/ - Latin America
https://mirrors.lolinet.com/firmware/moto/nash/official/RETBR/ - Brazil
https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/ - Bought from Moto in US Unlocked
All should work, but only one is right for your region - what's your region/where was this bought?
npjohnson said:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip - according to your getvar output - this is teh correct model (-05), and corresponds to the currently installed bootloader (159.y).
OR
If you mean you flashed a different firmware, you definitely have a -05 model, so it's:
1. https://mirrors.lolinet.com/firmware/moto/nash/official/RETLA/ - Latin America
https://mirrors.lolinet.com/firmware/moto/nash/official/RETBR/ - Brazil
https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/ - Bought from Moto in US Unlocked
All should work, but only one is right for your region - what's your region/where was this bought?
Click to expand...
Click to collapse
Hi npjohnson
I'm afraid you fell into the trap. Although you see that the firmware is correct, it really is not true. As I said before, I have a working ROM installed, and the "getvar" command shows exactly that, that is, what I have installed, so you are immersed in a loop. You see that I have a proper installation, but that is not the original ROM, and apparently it matches because I did indeed look for a firmware that matches my cell phone model, but I know that this is not exactly correct, because I keep getting the message " verity mode set to disable ".
Now, about the variations that you propose to me, I have this:
RETLA: There I found two versions, "XT1789-05_NASH_RETLA_SS" and "XT1789-05_NASH_RETLA_DS". With the first one the cell phone goes blank when it starts, with the second one it shows me the message that I have installed a different firmware.
RETBR: I never tried, because I bought the cell phone in Colombia at the time. Should I try this?
RETAIL: This is actually the one I currently have, but as I said, I have the message "verity mode set to disable".
This is why I need to know, through things that have not had modification such as the serial number or the IMEI, what ROM originally had.
I am very grateful for your help, so I will keep trying my best guys.
Loperaco said:
Hi npjohnson
I'm afraid you fell into the trap. Although you see that the firmware is correct, it really is not true. As I said before, I have a working ROM installed, and the "getvar" command shows exactly that, that is, what I have installed, so you are immersed in a loop. You see that I have a proper installation, but that is not the original ROM, and apparently it matches because I did indeed look for a firmware that matches my cell phone model, but I know that this is not exactly correct, because I keep getting the message " verity mode set to disable ".
Now, about the variations that you propose to me, I have this:
RETLA: There I found two versions, "XT1789-05_NASH_RETLA_SS" and "XT1789-05_NASH_RETLA_DS". With the first one the cell phone goes blank when it starts, with the second one it shows me the message that I have installed a different firmware.
RETBR: I never tried, because I bought the cell phone in Colombia at the time. Should I try this?
RETAIL: This is actually the one I currently have, but as I said, I have the message "verity mode set to disable".
This is why I need to know, through things that have not had modification such as the serial number or the IMEI, what ROM originally had.
I am very grateful for your help, so I will keep trying my best guys.
Click to expand...
Click to collapse
You are confused, the verity mode set to disabled notice is not because you have a firmware for a different device... It's because verity is disabled.
If you relock the bootloader that may go away, but I wouldn't worry about it.
RETLA appears to be correct for your device.
npjohnson said:
You are confused, the verity mode set to disabled notice is not because you have a firmware for a different device... It's because verity is disabled.
If you relock the bootloader that may go away, but I wouldn't worry about it.
RETLA appears to be correct for your device.
Click to expand...
Click to collapse
Ohhhhh I see, so I will not worry about this anymore and I am going to install the RETLA ROM.
I have one more question, what is the difference between RETLA SS and RETLA DS?
Loperaco said:
Ohhhhh I see, so I will not worry about this anymore and I am going to install the RETLA ROM.
I have one more question, what is the difference between RETLA SS and RETLA DS?
Click to expand...
Click to collapse
Never heard of SS, use whichever boots for you.
Loperaco said:
Ohhhhh I see, so I will not worry about this anymore and I am going to install the RETLA ROM.
I have one more question, what is the difference between RETLA SS and RETLA DS?
Click to expand...
Click to collapse
SS is "Single Sim" and DS is "Dual Sim".
Loperaco said:
Hi Starkiller.
This what the command returns:
...
(bootloader) ro.carrier: retla
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
Click to expand...
Click to collapse
It's unusual for a Moto device to be running in slot b
But that shouldn't affect your issue.
If you have a Windows PC LMSA'S Flash rescue option works good for downloading and flashing stock firmware.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ali using XDA Labs
Loperaco said:
Any ideas?
Click to expand...
Click to collapse
You're not alone. I have a RETIN device that I flashed a stock RETIN firmware on. Ever since, it says my phone's loaded a different OS - I have tried Smart Assistant, flashing all known RETIN etc. Only thing I couldn't do is try flashing a stock RETIN firmware using RSDLite, coz I couldn't get the phone to be detected (yet).
I have since then flashed a modified logo.bin that I created to match the blue-yellow Moto logo, to cover all those warnings sorting boot - except for verity disabled
ph03n!x said:
You're not alone. I have a RETIN device that I flashed a stock RETIN firmware on. Ever since, it says my phone's loaded a different OS - I have tried Smart Assistant, flashing all known RETIN etc. Only thing I couldn't do is try flashing a stock RETIN firmware using RSDLite, coz I couldn't get the phone to be detected (yet).
I have since then flashed a modified logo.bin that I created to match the blue-yellow Moto logo, to cover all those warnings sorting boot - except for verity disabled
Click to expand...
Click to collapse
You problem with RSD Lite is likely USB 3 ports, also most PC's that shipped with Windows 10, will not work with RSD Lite.
You need a PC that shipped with Windows 7 or XP, and USB 2 ports.
Sent from my ali using XDA Labs
ph03n!x said:
You're not alone. I have a RETIN device that I flashed a stock RETIN firmware on. Ever since, it says my phone's loaded a different OS - I have tried Smart Assistant, flashing all known RETIN etc. Only thing I couldn't do is try flashing a stock RETIN firmware using RSDLite, coz I couldn't get the phone to be detected (yet).
I have since then flashed a modified logo.bin that I created to match the blue-yellow Moto logo, to cover all those warnings sorting boot - except for verity disabled
Click to expand...
Click to collapse
Hahahaha LOL
ok, clearly that could be an effective solution, unfortunately not the most suitable
sd_shadow said:
You problem with RSD Lite is likely USB 3 ports, also most PC's that shipped with Windows 10, will not work with RSD Lite.
You need a PC that shipped with Windows 7 or XP, and USB 2 ports.
Click to expand...
Click to collapse
After realising that Moto has abandoned this device, I've abandoned Moto firmware too... Experimenting with Lineage now :laugh:
Loperaco said:
ok, clearly that could be an effective solution, unfortunately not the most suitable
Click to expand...
Click to collapse
For me, it was more of an OCD to not see that ugly screen once in a while when I restart. I'm rooted with Magisk, have EdXposed too - while Safety Net passes (for now at least), I do not use banking or Google Pay apps on this device - have a stock, unlocked P30 Pro only for that. So no sweat :highfive:
XT1789-01 engineering bootloader
npjohnson said:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip - according to your getvar output - this is teh correct model (-05), and corresponds to the currently installed bootloader (159.y).
OR
If you mean you flashed a different firmware, you definitely have a -05 model, so it's:
1. https://mirrors.lolinet.com/firmware/moto/nash/official/RETLA/ - Latin America
https://mirrors.lolinet.com/firmware/moto/nash/official/RETBR/ - Brazil
https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/ - Bought from Moto in US Unlocked
All should work, but only one is right for your region - what's your region/where was this bought?
Click to expand...
Click to collapse
Dear I've a Z2 force with XT1789-01 model number which is Verizon but "ENGINEERING BOOTLOADER" so my phone doesn't flash any firmware and says failed to start bootloader mode.
What's compatible firmware for engineering bootloader?
If I flash by commands it shows hardware malfunction
AlahmadPR said:
Dear I've a Z2 force with XT1789-01 model number which is Verizon but "ENGINEERING BOOTLOADER" so my phone doesn't flash any firmware and says failed to start bootloader mode.
What's compatible firmware for engineering bootloader?
If I flash by commands it shows hardware malfunction
Click to expand...
Click to collapse
You have a prototype device, return it to whomever you bought it from and get a new one.
I'm responsible for it
npjohnson said:
You have a prototype device, return it to whomever you bought it from and get a new one.
Click to expand...
Click to collapse
Is there a way to recover? Because I was using it b4