Related
Hi all,
I have installed the rom GPE with this cid and mid, S-off but i lost my carrier, sim is no unlocked. Then i try to back to stock rom. The big mistake i have do is to do no backup of my original CID and MID. So during 3 mouths i had try all solutions that i see on the web ex :
Fashing splash firmware : 1.54.401.5 with stock rom but the phone always stuck on bootloader
Then i try 1.54.401.10 , 4.16.401.5 , 4.16.401.10 and last 2.22.401.4 with there rom stock and sotck recovery but nothing change, always stuck on bootloader.
NB : i'm in super CID
I have try :
1) wirecid : supercid or HTC__001 or HTC__J15 etc...
2) Flashing firmware 1.54.401.5, 1.54.401.10, 4.16.401.5, 4.16.401.10, 2.22.401.4
3) flashing custom recovery twrp
4) format data and changing partition cache because it's always corruped after flashing new firmware
5) install rom stock with there firmware :
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed.zip
m8_4.16.401.10_AROMA.zip
One_M8_4.16.401.10_stock_system_dump.zip
insertcoin-7.1.9-REPACK-M8_UL_L50_SENSE70_MR_HTC_Europe_4.16.401.10.zip
rom_one_m8_2.22.401.4_odexed.zip revolution HD
Android_Revolution_HD-One_M8_45.0_758ff1.zip
m8_1.54.401.5_AROMA
6) reboot phone, but stuck on bootloader
7) try to flash boot.img and stock recovery on the firmware but nothing change,
8) try to enter to stock recovery but redirected in bootloader
9) try to lock bootloader
I have do this with all firmware and rom
I have try to install with ruu.exe but the application have error 155, i have change the cid and mid to match with in the androidinfo.txt.
!!! But boot with custom like CM12, Carbon rom etc... the only problem is that the simcard is not detected.
If anyone have other solution ?
My last getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -------
(bootloader) imei: --------
(bootloader) imei2: Not Support
(bootloader) meid: --------
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please help, i will become the master of reflashing rom and firmware on HTC ONE M8 but corrupted.
Someone can help me ?
Someone can help me ?
kimpak said:
Hi all,
I have installed the rom GPE with this cid and mid, S-off but i lost my carrier, sim is no unlocked. Then i try to back to stock rom. The big mistake i have do is to do no backup of my original CID and MID. So during 3 mouths i had try all solutions that i see on the web ex :
Fashing splash firmware : 1.54.401.5 with stock rom but the phone always stuck on bootloader
Then i try 1.54.401.10 , 4.16.401.5 , 4.16.401.10 and last 2.22.401.4 with there rom stock and sotck recovery but nothing change, always stuck on bootloader.
NB : i'm in super CID
I have try :
1) wirecid : supercid or HTC__001 or HTC__J15 etc...
2) Flashing firmware 1.54.401.5, 1.54.401.10, 4.16.401.5, 4.16.401.10, 2.22.401.4
3) flashing custom recovery twrp
4) format data and changing partition cache because it's always corruped after flashing new firmware
5) install rom stock with there firmware :
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed.zip
m8_4.16.401.10_AROMA.zip
One_M8_4.16.401.10_stock_system_dump.zip
insertcoin-7.1.9-REPACK-M8_UL_L50_SENSE70_MR_HTC_Europe_4.16.401.10.zip
rom_one_m8_2.22.401.4_odexed.zip revolution HD
Android_Revolution_HD-One_M8_45.0_758ff1.zip
m8_1.54.401.5_AROMA
6) reboot phone, but stuck on bootloader
7) try to flash boot.img and stock recovery on the firmware but nothing change,
8) try to enter to stock recovery but redirected in bootloader
9) try to lock bootloader
I have do this with all firmware and rom
I have try to install with ruu.exe but the application have error 155, i have change the cid and mid to match with in the androidinfo.txt.
!!! But boot with custom like CM12, Carbon rom etc... the only problem is that the simcard is not detected.
If anyone have other solution ?
My last getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -------
(bootloader) imei: --------
(bootloader) imei2: Not Support
(bootloader) meid: --------
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please help, i will become the master of reflashing rom and firmware on HTC ONE M8 but corrupted.
Click to expand...
Click to collapse
Your device is a Sprint .. you shouldn't convert it to any Intl GSM/GPE. You shouldn't change its MID.
Not sure whether this is still fixable because on Verizon I know, this conversion will kill the radio.
Change back your MID to 0P6B70000
and get the correct firmware and RUU here : http://forum.xda-developers.com/showthread.php?t=2729173
Anything you're not sure, ask in that thread or in Sprint Q&A
Hold Power + Volume Up for at-least 20secs and when screen turns black, release the buttons and hold Volume Down until you enter bootloader... which is mainly couple of seconds.
Mr_Jack_Frost said:
Hold Power + Volume Up for at-least 20secs and when screen turns black, release the buttons and hold Volume Down until you enter bootloader... which is mainly couple of seconds.
Click to expand...
Click to collapse
The OP is already in bootloader, and stuck there.
CID Numbers (Sprint only):
SPCS_001: standard Sprint M8
SPCS_004: Harman/Kardon version M8
I would try to rewrite the correct cid--> Update Hboot to 3.19-->Relock Bootloader-->Flash latest Ruu
---------- Post added at 04:07 PM ---------- Previous post was at 04:06 PM ----------
bombo_b said:
CID Numbers (Sprint only):
SPCS_001: standard Sprint M8
SPCS_004: Harman/Kardon version M8
I would try to rewrite the correct cid--> Update Hboot to 3.19-->Relock Bootloader-->Flash latest Ruu
Click to expand...
Click to collapse
Tho latest Ruu should already contain the 3.19 Hboot
bombo_b said:
I would try to rewrite the correct cid--> Update Hboot to 3.19-->Relock Bootloader-->Flash latest Ruu
Click to expand...
Click to collapse
In addition to your comment, that hboot does not need to be updated before RUU (RUU will do it):
1) Need to change MID back to Sprint MID to RUU
2) Shouldn't need to change CID, but it doesn't hurt to do so.
3) No need to relock bootloader to RUU, since OP is s-off.
But I agree, the OP should try to RUU back to Sprint stock image. (and obviously take the actions to meet the requirements to do so). After that, if is still doesn't work its probably a radio brick.
redpoint73 said:
In addition to your comment, that hboot does not need to be updated before RUU (RUU will do it):
1) Need to change MID back to Sprint MID to RUU
2) Shouldn't need to change CID, but it doesn't hurt to do so.
3) No need to relock bootloader to RUU, since OP is s-off.
But I agree, the OP should try to RUU back to Sprint stock image. (and obviously take the actions to meet the requirements to do so). After that, if is still doesn't work its probably a radio brick.
Click to expand...
Click to collapse
Error 155 is usually fixed by relocking Bootloader. Since the phone is in a funny state I would advise putting all chances on your side. Dont worry if the logic says S-off doesnt need BL relocked , you just need every chance to flash Stock ruu back to the phone
Thanks, i will try it...
So, if it's work i can unlock the phone to use another operator ?
ckpv5 said:
Your device is a Sprint .. you shouldn't convert it to any Intl GSM/GPE. You shouldn't change its MID.
Not sure whether this is still fixable because on Verizon I know, this conversion will kill the radio.
Change back your MID to 0P6B70000
and get the correct firmware and RUU here : http://forum.xda-developers.com/showthread.php?t=2729173
Anything you're not sure, ask in that thread or in Sprint Q&A
Click to expand...
Click to collapse
Amazing, it's work :highfive:
Actualy, i'm working to unlock the SIM now....
ckpv5 said:
Your device is a Sprint .. you shouldn't convert it to any Intl GSM/GPE. You shouldn't change its MID.
Not sure whether this is still fixable because on Verizon I know, this conversion will kill the radio.
Change back your MID to 0P6B70000
and get the correct firmware and RUU here : http://forum.xda-developers.com/showthread.php?t=2729173
Anything you're not sure, ask in that thread or in Sprint Q&A
Click to expand...
Click to collapse
kimpak said:
Thanks, i will try it...
So, if it's work i can unlock the phone to use another operator ?
Click to expand...
Click to collapse
All right tout marche bien
kimpak said:
Amazing, it's work :highfive:
Actualy, i'm working to unlock the SIM now....
Click to expand...
Click to collapse
kimpak said:
All right tout marche bien
Click to expand...
Click to collapse
Good to hear that it worked for you.
How do you saw that my phone is for sprint version ?
ckpv5 said:
Your device is a Sprint .. you shouldn't convert it to any Intl GSM/GPE. You shouldn't change its MID.
Not sure whether this is still fixable because on Verizon I know, this conversion will kill the radio.
Change back your MID to 0P6B70000
and get the correct firmware and RUU here : http://forum.xda-developers.com/showthread.php?t=2729173
Anything you're not sure, ask in that thread or in Sprint Q&A
Click to expand...
Click to collapse
kimpak said:
How do you saw that my phone is for sprint version ?
Click to expand...
Click to collapse
(bootloader) product: m8_whl
m8_whl is Sprint device
m8_ul is GSM device
Boot Loader Loop, Unlocked, S-Off, Rooted HTC M8 Tmobile
A year ago I believe I used HBoot and or Firewater to root my M8. I recently removed some applications that seemed to make my phone act funny, and now the phone is stuck in a boot loop, or rather just a boot and stop at the second HTC "One" screen. Not exactly a loop.
I've download ADB tool and tried the fastboot method to install TWRP but have no success because the computer does not recognize the phone while running ADB or Fastboot, therefore I cant install TWRP and am stuck in the bootloader menu. I have tried various different cables and restarted the pc several times, and installed htc sync and other drivers necessary for that process. Also uninstalled and installed different drivers later as well. Now im not sure what i have installed but I have access to the phones internal drive via explorer.
Using Hboot.
Stats:
***UNLOCKED***
M8_UL PVT SHIP S-OFF
CID-HTC__32
RADIO- 1.15.2133156
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.54.401.5
eMMc-boot 2048MB
Mar 22 2014, 00:53:32.0
Options:
HBOOT (when scanning says that all images are not found)
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMART SD
IMAGE CRC
SHOW BARCODE
Recovery leads to nothing and eventually returns to the HTC One menu stop.
Reset does nothing, acts like fast boot actually.
Ramdump under fastboot seems to works, and does produce log files.
While the phone was still active, I managed to create a full "manual" backup of the device by plugging it in and backing up/copying the entire internal memory. After screwing with the phone and every option for several hours I managed to access the files of the internal memory by switching to recovery mode via the boot menu and then plugging in the phone via usb to comp while deleting the drivers at the same time. I tried a full restoration of the internal backup i made, by copy and replace if the same method, but still nothing.
Ive attached an image of the Hboot menu with the details and options of that Hboot for those of you familiar with hboot.
The ideal situation, or what i'd like to do is restore the phone without flashing the rom and loosing the information, then id like to upgrade to lollipop or a new custom rom I found here actually, but the first step is getting back into the phone which i would be very grateful for in general.
also, not great with cmd and all that stuff, I do have sdk tools downloaded and installed but not great with that either. If there was a more simple way to replace existing files in the phone via the file manager (because im able to access the internal drive via the file manager, that would be the most ideal and easiest situation. But knowing the path and the boot files and which files are necessary for boot is what im looking for as well.
Also i know how to flash a sd and htc has a sdcard slot as well. Also i should mention that prior to the phone being screwed up I did want to delete some internal certificates because i believe someone installed a spy application on the phone, hence the reason for all of this checkup and removal anyway. In the process of trying to do that, i followed a tutorial on this forum which suggested I create a security lock pin, which I did. This could also be the cause of the problem not being recognized by the adb or fastboot script.
Who ever helps me do that gets a tip.
Please help.
---------- Post added at 05:02 PM ---------- Previous post was at 04:49 PM ----------
JamesM8 said:
A year ago I believe I used HBoot and or Firewater to root my M8. I recently removed some applications that seemed to make my phone act funny, and now the phone is stuck in a boot loop, or rather just a boot and stop at the second HTC "One" screen. Not exactly a loop.
I've download ADB tool and tried the fastboot method to install TWRP but have no success because the computer does not recognize the phone while running ADB or Fastboot, therefore I cant install TWRP and am stuck in the bootloader menu. I have tried various different cables and restarted the pc several times, and installed htc sync and other drivers necessary for that process. Also uninstalled and installed different drivers later as well. Now im not sure what i have installed but I have access to the phones internal drive via explorer.
Using Hboot.
Stats:
***UNLOCKED***
M8_UL PVT SHIP S-OFF
CID-HTC__32
RADIO- 1.15.2133156
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.54.401.5
eMMc-boot 2048MB
Mar 22 2014, 00:53:32.0
Options:
HBOOT (when scanning says that all images are not found)
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMART SD
IMAGE CRC
SHOW BARCODE
Recovery leads to nothing and eventually returns to the HTC One menu stop.
Reset does nothing, acts like fast boot actually.
Ramdump under fastboot seems to works, and does produce log files.
While the phone was still active, I managed to create a full "manual" backup of the device by plugging it in and backing up/copying the entire internal memory. After screwing with the phone and every option for several hours I managed to access the files of the internal memory by switching to recovery mode via the boot menu and then plugging in the phone via usb to comp while deleting the drivers at the same time. I tried a full restoration of the internal backup i made, by copy and replace if the same method, but still nothing.
Ive attached an image of the Hboot menu with the details and options of that Hboot for those of you familiar with hboot.
The ideal situation, or what i'd like to do is restore the phone without flashing the rom and loosing the information, then id like to upgrade to lollipop or a new custom rom I found here actually, but the first step is getting back into the phone which i would be very grateful for in general.
also, not great with cmd and all that stuff, I do have sdk tools downloaded and installed but not great with that either. If there was a more simple way to replace existing files in the phone via the file manager (because im able to access the internal drive via the file manager, that would be the most ideal and easiest situation. But knowing the path and the boot files and which files are necessary for boot is what im looking for as well.
Also i know how to flash a sd and htc has a sdcard slot as well. Also i should mention that prior to the phone being screwed up I did want to delete some internal certificates because i believe someone installed a spy application on the phone, hence the reason for all of this checkup and removal anyway. In the process of trying to do that, i followed a tutorial on this forum which suggested I create a security lock pin, which I did. This could also be the cause of the problem not being recognized by the adb or fastboot script.
Who ever helps me do that gets a tip.
Please help.
Click to expand...
Click to collapse
**** I just realized it would be more appropriate to create a new thread for my problem rather than intruding on this mans problem, please see the One (M8) Q&A, Help & Troubleshooting. And respond there*****
Hi everyone,
I have an m8 which is s-off, when I bought it was unlocked. To get the marshmallow update I relocked it using guides here.
Now my phone is locked, like original. (Still s-off) I used ruu.
I live in Turkey and 4g lte is active now, but my phone cant see it. I made a quick search and saw that I can unlock any lte band I want.
But for this I need root, for root I need recovery, I cant install recovery because my phone is locked.
I dont want to loose everything in my phone by unlocking htcdev. I locked my phone using a simple cmd command, but I cant unlock it.
How can I unlock it without htc dev?
Please help me,
mehmetolgungun said:
I dont want to loose everything in my phone by unlocking htcdev. I locked my phone using a simple cmd command, but I cant unlock it.
How can I unlock it without htc dev?
Click to expand...
Click to collapse
1. find firmware.zip that match your current firmware no.
2. rename TWRP 3.0.0.1 to recovery.img
3. drag the recovery.img to firmware.zip
4. download SuperSU.zip (version 2.65) and put it on root of your storage (internal or external doesn't matter)
5. fastboot flash zip firmware.zip
6. reboot to recovery and install SuperSU.zip
7. reboot then unlock it with this guide : http://forum.xda-developers.com/showthread.php?t=2708571
mehmetolgungun said:
I have an m8 which is s-off, when I bought it was unlocked. To get the marshmallow update I relocked it using guides here.
Now my phone is locked, like original. (Still s-off) I used ruu.
Click to expand...
Click to collapse
You don't need to relock the bootloader to RUU (or for any other reason, for that matter) when you have s-off.
mehmetolgungun said:
I live in Turkey and 4g lte is active now, but my phone cant see it. I made a quick search and saw that I can unlock any lte band I want.
But for this I need root, for root I need recovery, I cant install recovery because my phone is locked.
Click to expand...
Click to collapse
If you are talking about this mod (and you probably are) it only works on Sprint and VZN "CDMA" versions of the M8.
For other versions of the M8, the only way I know to change band support is to flash another version's radio baseband (which you can do since you have s-off).
What version M8 do you have? Do fastboot getvar all, and post the results (delete IMEI and serial number before posting) if you want further advice on version, baseband, etc.
What band (or bands) does your carrier use for LTE?
mehmetolgungun said:
I dont want to loose everything in my phone by unlocking htcdev. I locked my phone using a simple cmd command, but I cant unlock it.
Click to expand...
Click to collapse
The command to relock is simple (fastboot oem lock); however unlocking doesn't have a similar command (such as "fastboot oem unlock"). Fastboot command needs to include the unlock token from HTCDev.com.
Otherwise, to unlock bootloader without HTCDev.com, you need to use the guide linked by ckpv5 above.
Thank you for you support.
My phone is AT&T. "m8_ul_ca"
But I changed mid and cid to 401. After this I applied 401 ruu.
Vodafone Turkey uses band 20, but I cannot get signal.
As you said I have radio and firmware for it. (401=Europe).
fastboot oem lock gave an error, so I used firmware method to put twrp, it was succeded. I installed twrp, and after it I installed ARHD latest.
I still get no 4g signal
mehmetolgungun said:
My phone is AT&T. "m8_ul_ca"
But I changed mid and cid to 401. After this I applied 401 ruu.
Vodafone Turkey uses band 20, but I cannot get signal.
As you said I have radio and firmware for it. (401=Europe).
Click to expand...
Click to collapse
Euro (401) version already supports LTE Band 20, so you shouldn't need to unlock any bands or change band support (by flashing a different radio). Some other problem (besides band support) is preventing you from getting LTE.
What version number RUU (whole version number, not just "401") did you use?
redpoint73 said:
Euro (401) version already supports LTE Band 20, so you shouldn't need to unlock any bands or change band support (by flashing a different radio). Some other problem (besides band support) is preventing you from getting LTE.
What version number RUU (whole version number, not just "401") did you use?
Click to expand...
Click to collapse
Baseband version
1.29.214500021.12G_20.72.4196t.01_F
Build number
6.12.401.4 CL662736 release_keys
Android security patch level
2015-12-01
Here are some more info
C:\fastboot>fastboot getvar all
(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.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ***************
(bootloader) imei: *********************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Everything looks to be in order, as far as firmware. Its properly updated to MM (to be compatible with MM ROMs) and as you mentioned on the Euro 401 radio, so it should support LTE Band 20.
You're sure the SIM works on other devices (receiving LTE Band 20)?
If so, I've tried helping a few folks that have had issues getting LTE to work, after flashing the appropriate radio that supports their carrier's LTE band. In those cases as well, I couldn't find anything that should be keeping them from getting LTE. Might be some carrier specific issues on how they handle LTE. But I'm really not sure, and can't personally help anymore than that.
Hi,
Using *#4636#* I selected lte only and phone connected to vodafone band 3.
Band 3 is not listed in at&t models. So you are right, installing europe radio changes available bands.
But there is still a problem when i select 2g/3g/4g auto, phone selects 3g. There is no option like lte preffered. Lte only uses lte but auto uses 3g.
hi,
i bought a htc one m9 "0PJA100 ve FCC ID: NM80PJA100 M9u". it can bootloop only in bootloader and not any more. when select the download mode screen was blue and restarted again. i flashed the some *.img files in adb folder just like this this message
http://forum.xda-developers.com/one-m9/help/htc-m9-corruted-bootloader-blue-screen-t3164927/page2
it went good and i could boot in download mode. when i wrote "fastboot getvar all"
mid: 0PJA10000 and cid:11111111 so this one is international version.
i flashed many kind of rom (*.**.401.*--*.**.617.*--*.**.605.* with change with suitable mid number also and many custom rom) but all of them had not recognised "empty imei ,emty baseband and no sim card" but no problem with the imei number it was original. last one i flashed stock rom (3.35.401.12) with zip file. with 0PJAIMG.zip in download mode all went good but same thing happened. "empty imei ,emty baseband and no sim card"
"fastboot getvar all" screen is
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 3***************
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: 11111111
what can be done ? is it a solution to flash firmware file one by one ( so i flashed some of them firts)
Cid is supercid. Compatible?. Yes updates are incremental.
Beamed in by telepathy.
no baseband no imei
shivadow said:
Cid is supercid. Compatible?. Yes updates are incremental.
Beamed in by telepathy.
Click to expand...
Click to collapse
hi,
i also tried with international cid number (htc__m27) but no luck. I tried almost every stock rom (international, developer, asian and europe version) but same result no baseband no imei. i dont think its a hardware problem. what else can be done?
no IMEI no Baseband, no sim, no solution
It is same with me, I just flashed Multirom and then uninstalled it -> now no IMEI no Baseband and cannot do anything with the phone, it works normally just does not accept sim card so no signal. I do not think it is hardware as so many people have the same problem. Could someone please look into this?
Same problem for me!!m9 verizon himawl gsm, unknown baseband!help us??
It could be problem of fabric
Maybe is inside of hardware
Mine Htc One M9 has problem of Radio Fm
Doesen't work even when was on lollipop and now on Nougat
I gone on alot of phone services and told me that is not a big deal that ,dont screw your phone only that has no radio
I was thinking that is better this way
I told my friend who bought my phone from Ebay to complain to the seller but is a long way of getting my money back
So for every thing you done check it with the seller you bought it your phone
Cause was from the alterations to the boot firmware when SuperSU was installed. I flashed the original boot.img back to the phone and baseband were restored. I re-installed SuperSU 2.78 and Baseband and imei were gone. SuperSU is the cause. When you restore the boot image, you loose root.
Solution: flash original unaltered boot.img back to phone using fastboot. Then install SuperSU-v2.82.
Hi, I made this post in the Sprint section a few days ago, but figured I'd post here as well to see if maybe this section has more traffic. If that's not allowed, I apologize in advance.
https://forum.xda-developers.com/sprint-htc-one-m8/help/stock-roms-t3669676
Basically, I'm looking for a stock rom for Sprint that would work with 1.54.651.8 firmware. All the links I can find on the forums seem to be dead.
Alternatively, a nandroid backup or way to extract the rom from the 1.54.651.8 RUU I do have (but won't successfully flash for whatever reason)
Any help would be appreciated. Thanks!
A custom ROM would need to support the Sprint M8, and be based on 4.4.2. Most any newer (newer than KitKat) ROMs will suffer major incompatibility with your ancient firmware, including extreme long boot time or no boot, and broken WiFi.
Suggest stocking with updating the firmware. Is the device s-on or s-off?
Problems with the RUU while "sending" are usually on the PC side. Try to re-install HTC drivers, try another USB port (USB 2.0 works best), and try another cable. Or even try another PC if possible.
Yeah I was able to find one custom 4.4.4 ROM (It was labelled 4.4.2, but it works so I guess it's close enough). There are just a few issues with it and I've always been more of a stock person anyway so I'd rather use a stock rom if I have the option.
As far as updating firmware, I am S-ON - I only originally rooted for a wifi hotspot app, so I didn't have a need to go S-OFF.
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site? I was willing to try it back when I had no rom at all, but now that I have a custom rom that mostly works, I'd rather not totally crap the bed.
Fuhcue said:
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site?
Click to expand...
Click to collapse
You can "skip" RUUs, and go the latest. However, you may (probably) need to update to the Marshmallow firmware anyway, before you can RUU. There is a strange limitation on most US version M8, where the RUU will fail with Error 155, if you try to go to Marshmallow from any former version (be it Kitkat or Lollipop) without first updating the firmware.
So the steps would be:
1) Relock bootloader
2) Flash to Marshmallow signed firmware (Sprint), in fastbootRUU mode
3) RUU to Marshmallow
4) Unlock bootloader again
5) Flash TWRP, root, and do whatever mods you want
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.
redpoint73 said:
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.
Click to expand...
Click to collapse
I don't so much mind the wipe, but I am a bit nervous about updating the firmware since that sounds like it could leave me in limbo if the RUU still didn't want to work for whatever reason. I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).
Fuhcue said:
I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
Click to expand...
Click to collapse
The firmware is posted in the same thread as the RUUs. And instructions on how to flash, as well.
https://forum.xda-developers.com/showthread.php?t=2729173
Fuhcue said:
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).
Click to expand...
Click to collapse
You can also opt for the Lollipop RUU (does not require flashing the firmware first). While not the latest, it's obviously more updated than what you presently have. And most of the current MM ROMs should work with LP firmware. There isn't much difference in the firmware it seems, for LP versus MM. Much different from KK to LP, which causes the problems I mentioned earlier (if you try to run KK firmware with LP or MM ROMs).
For maximum compatibility, matching the firmware is usually best. But I was running LP firmware with MM ROMs for a while (was simply to lazy to flash the MM firmware or RUU).
Ok so it sounds like the easiest option for me at this point is to grab a Lollipop RUU and try to flash it from a new computer with a fresh install of all the drivers. That way, at least if it fails to recognize my phone like the newest one did, I'll still be where I currently am with the stock (though outdated) firmware and custom rom.
Otherwise, I'll keep my fingers crossed that someone stumbles across this thread that has a meticulous archive of all old stock Sprint roms
Thanks so much for all your help and answering my questions so quickly. Much appreciated.
Hi
This is Sudheer from INDIA
i got Sprint HTC one M8 Harman Kardon from my friend.
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting. yesterday i am trying to install os from following reference.
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.
Krishna Sudheer said:
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
Click to expand...
Click to collapse
"Jail break" is a term specific to only iPhones. There is not such thing as "jail break" on an Android device. I assume you mean s-off, or some other mod? I can only guess, if you don't use the specific and proper terminology.
Krishna Sudheer said:
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting.
Click to expand...
Click to collapse
All in one Toolkit is obsolete, you shouldn't be using it. It contains a very old version of TWRP which will cause problems for many folks.
System partition is the OS/ROM. Should be obvious, that wiping the system partition results in no OS. Can't boot to an OS that isn't there any more. If you didn't know what the result would be from wiping a partition, you should be touching it in the first place!!!! Those options are listed under "Advanced" for a reason. If you aren't an advanced user, don't mess with them, unless you are following directions form an experienced user, or know what the result is going to be.
Krishna Sudheer said:
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.
Click to expand...
Click to collapse
Not enough info to know why the RUU failed. You linked a post with multiple RUUs, so we don't know which one you tried. We also don't know your current phone configuration.
Which version number RUU did you try? For HK version, you typically will need to flash the one that contains the digits "654". The RUU with digits "651" is for non-HK Sprint version. Assuming CID/MID has not been modified (which we don't know, if you don't provide more info).
Post specific info about your phone. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
If the phone is s-on, you need to lock it in order to RUU. I don't know if you are s-on of s--off.
You can't run a lower number (downgrade) RUU unless you have s-off. Again, I don't know what version number RUU you tried, your current version number on the phone, or whether you are s-on or s-off.
Hi Sir,
Thank you for replying. Sim Unlocked from mobile store. actually I also don't know witch method they are using to unlock. After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
I tried to change CID and s-off but it's not working.
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot?
My mobile model is HTC one M8 HK (831C) Sprint Internal storage is 32GB.
I download and used to flash following files.
1. signed_6.20.654.3_firmware.zip
2.RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe
3.0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(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.031s
Kindly check and do the needful. Let me know how to install OS and where witch rom I use to install.
My responses below in red font:
Krishna Sudheer said:
After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
LTE is difficult (maybe impossible) to get working in cases where the device is not intended for your region/carrier (which I assume is the case, that you are not located in US, on the Sprint carrier). GSM should work (as you indicated) as well as 3G (HSPA) provided that your carrier uses a band(s) supported by the Sprint version M8
I tried to change CID and s-off but it's not working. I don't know what that means "it's not working". Most folks who say they have trouble with getting s-off, are trying the hopeless waste of time, which is trying to usethe long obsolete "free" s-off method of firewater. It's never going to work.
Also, you should also be careful here, when changing CID. Only use a Sprint CID, or SuperCID with a Sprint firmware/RUU. Trying to use any other firmware or RUU will result in a radio brick (possibly permanent).
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot? That version is too old (over 4 years) and you should have used current TWRP. This was probably caused by using the toolkit (which I mentioned is not advised anymore). Old versions of TWRP was not compatible with Sprint M8 (it had it's own "CDMA" version TWRP) and it probably caused the wrong partition to be overwritten.
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3 Try flashing firmware again, the number should show up in getvar all (below) under "version-main". Flashing firmware twice is usually a good idea.
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Error 155 is common, if flashing a US Marshmallow RUU, without being on the matching firmware. Flashing firmware again, as indicated above, may solve it.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: firmware number should appear here
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(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.031s
Click to expand...
Click to collapse
So, I had a marshmallow update on my phone, and later i converted into GPE, but didn't like it. Went back to Sense, but it just doesn't feel as good as before. One day, the battery died, and when i tried turning it on, it would give me all sorts of errors. This never happened while i was on marshmallow before conversion to GPE. Had to reset it from the recovery. I think it hasn't returned to Sense properly.
As i am S-Off, i was thinking of flashing it with a RUU which is compatible with my device. Please suggest me which is compatible.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.21450002
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.708.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -------------------
(bootloader) imei: --------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B63000
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.090s
Based on your MID, looks like you're on a GSM M8? I'd go to HTC Dev and download their stock ROM, or go the appropriate carrier sub section for the M8 and use an RUU there.
I have read here that flashing carrier RUU can brick the device radio for good. So, this is why I wanted to confirm.
cytherian said:
I'd go to HTC Dev and download their stock ROM, or go the appropriate carrier sub section for the M8 and use an RUU there.
Click to expand...
Click to collapse
HTC does not post the RUU for his version on HTC Dev.com (many versions are not posted there)
OP's version doesn't have a carrier forum sub-section.
---------- Post added at 09:38 AM ---------- Previous post was at 09:36 AM ----------
xexux said:
(bootloader) version-main: 6.16.708.1
Click to expand...
Click to collapse
I don't know if there is an RUU for this version number.
One alternative, is to restore the TWRP backup 6.16.708.1 from here: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
---------- Post added at 09:42 AM ---------- Previous post was at 09:38 AM ----------
xexux said:
Went back to Sense, but it just doesn't feel as good as before.
I think it hasn't returned to Sense properly.
Click to expand...
Click to collapse
How exactly did you go back to Sense?
I tried the guide here, but I just couldn't complete it, as i received some modelid error. Tried multiple times to no avail. So, i tried the TWRP nandroid method, and restored to Sense that way.
xexux said:
I tried the guide here, but I just couldn't complete it, as i received some modelid error. Tried multiple times to no avail. So, i tried the TWRP nandroid method, and restored to Sense that way.
Click to expand...
Click to collapse
Good to hear that it worked out and thanks for posting. :good:
cytherian said:
Good to hear that it worked out and thanks for posting. :good:
Click to expand...
Click to collapse
This is how I got Sense back, and after that, I started experiencing bugs with M8 as explained in my first post.
xexux said:
So, i tried the TWRP nandroid method, and restored to Sense that way.
Click to expand...
Click to collapse
Which TWRP backup did you restore? Did you flash firmware, or only restore the TWRP backup?
redpoint73 said:
Which TWRP backup did you restore? Did you flash firmware, or only restore the TWRP backup?
Click to expand...
Click to collapse
I restored it with the latest TWRP backup for my model. About firmware, I am not sure, but i do see that firmware version in 'fastboot var all' data.
Since I am S-off, is there any Marshmallow RUU which i can try without bricking anything? May be a developer version or RUU for european/asian variant? Or the ones linked at gsmhosting M8 page? I have read people experiencing LTE radio problem with that. I hope that's not the case anymore, and there is a work around.
xexux said:
I restored it with the latest TWRP backup for my model.
Click to expand...
Click to collapse
What version number exactly? Perhaps you still have the files on your computer, and can look?
I've seen a number of times, folks say and think they restored the right version for their model, and once we ask for version numbers, we see they actually got it wrong.
xexux said:
About firmware, I am not sure, but i do see that firmware version in 'fastboot var all' data.
Click to expand...
Click to collapse
I can see it too. But doyou actually remember manually download and flash the firmware in RUU mode?
Did you convert to GPE using the RUU?
xexux said:
Since I am S-off, is there any Marshmallow RUU which i can try without bricking anything? May be a developer version or RUU for european/asian variant? Or the ones linked at gsmhosting M8 page? I have read people experiencing LTE radio problem with that. I hope that's not the case anymore, and there is a work around.
Click to expand...
Click to collapse
It's possible. But flashing another region's RUU will also change the radio baseband, and therefore changes the specific bands supported. It may have undesirable results (not support the 3G or LTE band or bands used by your local carrier).
My htc one m8 has no os due to an unsuccessful update, I have s-on, boot loader unlocked and not fully rooted. I have twrp as recovery. What are my options to get the official ruu to flash
Bukss said:
My htc one m8 has no os due to an unsuccessful update, I have s-on, boot loader unlocked and not fully rooted. I have twrp as recovery. What are my options to get the official ruu to flash
Click to expand...
Click to collapse
First of all, the phone won't update with TWRP installed (need stock recovery) so that is one reason for the update to fail.
Also, if the ROM is not stock (such as custom ROM, root) in any way, it needs to be returned to stock in order to update. I don't know what "not fully rooted" means. But if it was rooted, you need to re-install the stock ROM (such as stock TWRP backup) as most other "unroot" methods do not work (update will still fail).
RUU will update the phone, and bypasses the above requirements. But we would need to know more about the phone to know if your version M8 has an RUU. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
redpoint73 said:
First of all, the phone won't update with TWRP installed (need stock recovery) so that is one reason for the update to fail.
Also, if the ROM is not stock (such as custom ROM, root) in any way, it needs to be returned to stock in order to update. I don't know what "not fully rooted" means. But if it was rooted, you need to re-install the stock ROM (such as stock TWRP backup) as most other "unroot" methods do not work (update will still fail).
RUU will update the phone, and bypasses the above requirements. But we would need to know more about the phone to know if your version M8 has an RUU. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
Hello guys. I took my M8 to someone to repair and they completely messed up the phone. Now no matter how you try to boot up the phone, a black screen with a silver HTC logo in the middle and 4 silver triangles in the corner shows up. I cannot reboot into bootloader, it brings me back to the same screen. Here is a getvar of my htc one m8, i was wondering if you could point me to the right RUU to use.
c:\miniadb_m7>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.A13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.07.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 99000499834418
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(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: RUU
(bootloader) commitno-bootloader: 11459804
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.036s
Abnova said:
Hello guys. I took my M8 to someone to repair and they completely messed up the phone. Now no matter how you try to boot up the phone, a black screen with a silver HTC logo in the middle and 4 silver triangles in the corner shows up. I cannot reboot into bootloader, it brings me back to the same screen. Here is a getvar of my htc one m8, i was wondering if you could point me to the right RUU to use.
(bootloader) version-main: 5.07.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m8_wlv
(bootloader) modelid: 0P6B12000
Click to expand...
Click to collapse
Wow, this is quite a mess!
Was this a repair shop, or just some person you knew that tried to "fix" the phone. Either way, it is probably apparent that they shouldn't be trusted, and don't seem too knowledgeable (at least with this specific device).
Although there are a few details I'm not clear on, and you should clarify:
1) If you can't get to bootloader, how did you do fastboot getvar all?
2) What exactly was wrong with the phone that the shop/person tried to "fix" for you (and the specific condition before you gave it to them)? Was it able to boot to OS? Something else wrong (no SIM, etc.)?
What is clear, is that your device is the US Verizon version M8 (as shown by the product ID m8_wlv). But at some point (not completely clear if it was the repair person, or before that) it had its MID changed to that of the US Developer's Edition (0P6B12000). And had the Google Play Edition (GPE) firmware and/or RUU installed.
Those last two things (changing to Dev Ed MID, and running GPE RUU/firmware) are a very bad idea on the Verizon version M8. Reason being, the Verizon M8 is peculiar, and can only run firmware/RUU intended for the Verizon variant M8 (so Verizon RUU or firmware). Installing any other RUU/firmware will result in a radio brick, possibly permanent. And is probably also the reason the phone won't boot to OS now. It may be fixable. But first, I'd like more information (items above) on the history of the phone, and exactly what was done to it before the repair person worked their "magic" (as much as you know).
redpoint73 said:
Wow, this is quite a mess!
Was this a repair shop, or just some person you knew that tried to "fix" the phone. Either way, it is probably apparent that they shouldn't be trusted, and don't seem too knowledgeable (at least with this specific device).
Although there are a few details I'm not clear on, and you should clarify:
1) If you can't get to bootloader, how did you do fastboot getvar all?
2) What exactly was wrong with the phone that the shop/person tried to "fix" for you (and the specific condition before you gave it to them)? Was it able to boot to OS? Something else wrong (no SIM, etc.)?
What is clear, is that your device is the US Verizon version M8 (as shown by the product ID m8_wlv). But at some point (not completely clear if it was the repair person, or before that) it had its MID changed to that of the US Developer's Edition (0P6B12000). And had the Google Play Edition (GPE) firmware and/or RUU installed.
Those last two things (changing to Dev Ed MID, and running GPE RUU/firmware) are a very bad idea on the Verizon version M8. Reason being, the Verizon M8 is peculiar, and can only run firmware/RUU intended for the Verizon variant M8 (so Verizon RUU or firmware). Installing any other RUU/firmware will result in a radio brick, possibly permanent. And is probably also the reason the phone won't boot to OS now. It may be fixable. But first, I'd like more information (items above) on the history of the phone, and exactly what was done to it before the repair person worked their "magic" (as much as you know).
Click to expand...
Click to collapse
Yeah I realised how big of a mess I was in when I got it back. Anyway
1.)On further investigation it seems like the the phone is in a wierd RUU mode. So it still can interface with the laptop through fastboot. Like I said earlier, trying to reboot to bootloader brings you to the same black screen with the silver Logo (see attached). When the phone is plugged in to the laptop or switches to the HTC silver Logo screen however when it's unplugged, it goes to a wierd bootloader like screen but black and only has the option for RUU. ( See attached)
2.) I took it to them to replace the battery because . The phone would switch off even at 100% battery. It only worked when it stayed plugged in , like a PC. I'm guessing the repair guys saw I had modified the software (I was running Dirty Unicorns, Android 7.1.2, Latest TWRP with a relocked Bootloader, S-Off) and had thought the problem actually had to do with the software. I live in Kenya and the HTC model available here is the international Gsm model so im guessing it seemed reasonable for them to RUU the Google play edition to try to bring it to a stable, stock, state. It most likely previously worked on the other M8's brought to them. I doubt they realized that I had imported the phone from the US, so they were probably shocked when it failed.
Anyway I hope this information helps. Thanks for your help.
Abnova said:
I live in Kenya and the HTC model available here is the international Gsm model so im guessing it seemed reasonable for them to RUU the Google play edition to try to bring it to a stable, stock, state. It most likely previously worked on the other M8's brought to them. I doubt they realized that I had imported the phone from the US, so they were probably shocked when it failed.
Click to expand...
Click to collapse
"Because it worked before" is not a good philosophy when working with these devices. Different models have their own nuances, for any smartphone. Any repair shop should be smart enough to know that different models/versions of the same phone can have major differences. And assuming otherwise can have catastrophic results!
Abnova said:
1.)On further investigation it seems like the the phone is in a wierd RUU mode.
Click to expand...
Click to collapse
Not a bad thing, if it is in fact RUU mode. You can try the Verizon RUUs. As mentioned, these are the only RUUs you should try on your device!
https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
You will likely need to change back to the Verizon MID to run those RUUs. Otherwise the RUU will fail with wrong MID.
https://forum.xda-developers.com/showthread.php?t=2708581
If the phone boots to OS, but with no SIM or no signal, the repair shop flashing the wrong RUU may have bricked the radio. You can try to flash an older (Kitkat) Verizon RUU, which sometimes will fix the problem. If it does fix the radio, then you can update up to something more recent (Marshmallow).
Of course, I don't know if any of this will help your original problem of the phone shutting off when not on charger. If it is a software problem, then the original factory image (Verizon RUU) has the best chance of fixing it!
Thanks for your contribution, will definitely try tomorrow
redpoint73 said:
"Because it worked before" is not a good philosophy when working with these devices. Different models have their own nuances, for any smartphone. Any repair shop should be smart enough to know that different models/versions of the same phone can have major differences. And assuming otherwise can have catastrophic results!
Not a bad thing, if it is in fact RUU mode. You can try the Verizon RUUs. As mentioned, these are the only RUUs you should try on your device!
https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
You will likely need to change back to the Verizon MID to run those RUUs. Otherwise the RUU will fail with wrong MID.
https://forum.xda-developers.com/showthread.php?t=2708581
If the phone boots to OS, but with no SIM or no signal, the repair shop flashing the wrong RUU may have bricked the radio. You can try to flash an older (Kitkat) Verizon RUU, which sometimes will fix the problem. If it does fix the radio, then you can update up to something more recent (Marshmallow).
Of course, I don't know if any of this will help your original problem of the phone shutting off when not on charger. If it is a software problem, then the original factory image (Verizon RUU) has the best chance of fixing it!
Click to expand...
Click to collapse
I'm having trouble changing the MID Because adb is not working. However, fastboot is. So I've been stuck and I don't know what to do
Abnova said:
I'm having trouble changing the MID Because adb is not working. However, fastboot is. So I've been stuck and I don't know what to do
Click to expand...
Click to collapse
Ah, yes. Good point. You need adb to change the MID.
Try booting TWRP custom recovery, which should give you adb access.
Download TWRP (I suggest the latest, version 3.2.1-0). Put it in the same folder as fastboot.exe
Then do command: fastboot boot twrp.img
Where "twrp.img" has to match the exact file name of what you downloaded (you can change the name of the file to twrp.img or else type the whole/exact file name as downloaded).
Hopefully, you will see TWRP boot on the phone. Once it does, you should have adb access.
I also believe you should be able to run root (su) commands in TWRP (which is necessary to change MID). But I don't remember if there is an extra step of not to that.
Basically, the repair shop really screwed you by changing the MID and flashing the wrong RUU. Extra steps/tricks to do now, but hopefully we can get some progress anyway.
redpoint73 said:
Ah, yes. Good point. You need adb to change the MID.
Try booting TWRP custom recovery, which should give you adb access.
Download TWRP (I suggest the latest, version 3.2.1-0). Put it in the same folder as fastboot.exe
Then do command: fastboot boot twrp.img
Where "twrp.img" has to match the exact file name of what you downloaded (you can change the name of the file to twrp.img or else type the whole/exact file name as downloaded).
Hopefully, you will see TWRP boot on the phone. Once it does, you should have adb access.
I also believe you should be able to run root (su) commands in TWRP (which is necessary to change MID). But I don't remember if there is an extra step of not to that.
Basically, the repair shop really screwed you by changing the MID and flashing the wrong RUU. Extra steps/tricks to do now, but hopefully we can get some progress anyway.
Click to expand...
Click to collapse
I tried that, it would flash then refuse to reboot to the recovery. I've tried so many things but none of them worked. My only hope is if someone edited the Android.txt file inside the Rom Zip so that the model ID is the same as that of my corrupt phone. That way it'll flash and hopefully fix it. I've tried myself but everytime I tried to edit it says the zip/archive is corrupt on WinRAR. I don't know whether it's a problem with my laptop or if it's a complication related to the rom.zip. I've downloaded it again but it still does the same thing. So basically I'm stuck because there is no way I can change the MID. This probably means the phone is bricked.