Ok - so I acquired a "bricked" One X.
When I got it, it supposedly had a boot loop - occasionally booted into the Sense ROM that was installed - but whenever it got there, it hung.
So I couldn't tell properly, if it had USB debugging activated.
But - I do appear to have been able to unlock the device - because when you go into the Boot Loader, it does say UNLOCKED.
However - all of my attempts so far to chuck a new ROM on it have failed.
I did try at one point to put the proper nandroid backup on the device (it comes back saying it's CID is VODAP001).
But my attempts to do that failed. (I seem to recall something about wrong MD5 sum or something like that).
I have been able to put clockworkmod 5.8.4.0 on it
HBOOT 1.72.0000 is on it.
So - I tried installing CM10 - flashes the boot.img ok - but installing the ROM fails.
Initially with a Status 7 error (and then after I tried the "trick" to remove the "assert" line from the updater-script, it just failed, with no error number displayed).
I tried also with CM11 - and it fails too. (Status 7)
I've tried a few things to find out about the device - I can get the CID as above - but can't pull the MID (using Automated Fastboot Commands V2.3 by Team Hex)
When I try "adb devices" no devices are listed.
But it can mount as USB storage - I can copy files to the devices.
But I'm stuck.
So - I'm wondering - what can I do here?
Anything?
PS - though it might sound from the above that I know a wee bit about this stuff - that's it - I know a wee bit.
I managed to fix my own phone recently (another One X) which is now running CM11 - but that was a painful experience too.
So - any guidance please be patient with me!!!
Any help is really appreciated though.
subharmonic said:
Ok - so I acquired a "bricked" One X.
When I got it, it supposedly had a boot loop - occasionally booted into the Sense ROM that was installed - but whenever it got there, it hung.
So I couldn't tell properly, if it had USB debugging activated.
But - I do appear to have been able to unlock the device - because when you go into the Boot Loader, it does say UNLOCKED.
However - all of my attempts so far to chuck a new ROM on it have failed.
I did try at one point to put the proper nandroid backup on the device (it comes back saying it's CID is VODAP001).
But my attempts to do that failed. (I seem to recall something about wrong MD5 sum or something like that).
I have been able to put clockworkmod 5.8.4.0 on it
HBOOT 1.72.0000 is on it.
So - I tried installing CM10 - flashes the boot.img ok - but installing the ROM fails.
Initially with a Status 7 error (and then after I tried the "trick" to remove the "assert" line from the updater-script, it just failed, with no error number displayed).
I tried also with CM11 - and it fails too. (Status 7)
I've tried a few things to find out about the device - I can get the CID as above - but can't pull the MID (using Automated Fastboot Commands V2.3 by Team Hex)
When I try "adb devices" no devices are listed.
But it can mount as USB storage - I can copy files to the devices.
But I'm stuck.
So - I'm wondering - what can I do here?
Anything?
PS - though it might sound from the above that I know a wee bit about this stuff - that's it - I know a wee bit.
I managed to fix my own phone recently (another One X) which is now running CM11 - but that was a painful experience too.
So - any guidance please be patient with me!!!
Any help is really appreciated though.
Click to expand...
Click to collapse
If you have CM11 on your sd card flash TWRP 2.8.1 and then install it and flash the boot.img. If you don't have any rom on the sd card flash Philz 5.15.9 then mount sd card copy what you need on your sd card then flash TWRP2.8.1 then install the rom and flash the boot.img
Does TWRP 2.8.1.0 work on the One X?
The unit is an Endevour... ie Tegra 3 based International version...
Ok - so I tried installing several versions of TWRP - only TWRP 2.4.0.0 would let me do anything (ie Touch was activated).
None of them would let me install the ROMs due to the MD5 thing again.
I reverted to the clockworkmod 5.8.4.0 - and this let me install CM10 - but it doesn't get out of boot - I just see the white HTC screen and it hangs.
I did the flash at 66% battery though - could that be the problem?
PS - given that I couldn't actually check at any stage to see if USB debugging was enabled - is it likely to be the case that it is - given that I've been able to unlock the device and flash various recoveries?
Still no further forward...
So to recap...
I've can flash recoveries.
Everytime I try to put on CM10 or 11, I get a Status 7 error - or, it says I have an MD5 mismatch - or it just says installation aborted.
It seems that I can flash boot.img ok.
Whenever I try to flash - I clear the cache, and Dalvik cache - and before reboot just to make sure, I flash the boot.img again.
Each time I just get the white HTC screen.
My device has CID VODAP001.
Any suggestions? (apologies for the bump).
Still stuck with this thing.
Fastboot works ok - here's the getvar all
version: 0.5a
version-bootloader: 1.72.0000
version-baseband: 5.1204.164D3.31
version-cpld: None
version-microp: None
version-main: 4.17.161.3
serialno:
imei:
product: endeavoru
platform: HBOOT-T30S
modelid: PJ4610000
cidnum: VODAP001
battery-status: good
battery-voltage: 4157mV
devpower: 100
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
adb devices doesn't show any devices attached though?
Any ideas what I could try?
I keep getting a Status 7 error on installing CM10, or CM11 or even GAPPS for 4.4.3 - eg
set metadata_recursive: some changes failed
Error in /sdcard/ROMS/... etc (Status 7)
Flashing some recoveries don't work - ie recoveries which are supposedly meant to work (ie clockworkmod recovery 6.0.4.8 - the one recommended by CM to install before trying to flash CM11 - doesn't even run properly).
Not sure if this is relevant, but when in recovery, the phone is listed when adb devices is run.
ie
SH25.......... recovery
Just tried to ADB sideload CM11.
*failed to write data 'protocol fault (no status)'*
So that didn't work either...
subharmonic said:
Just tried to ADB sideload CM11.
*failed to write data 'protocol fault (no status)'*
So that didn't work either...
Click to expand...
Click to collapse
PS - tried the ADB sideload - this time it did work - but on installation of the package, it failed again.
Same error but different location this time?
set_metadata_recursive: some changes failed
E: Error in /tmp/update.zip
Status 7
Installation aborted
Did I mention that I'm a noob?
Didn't realise that ADB only works when in recovery - and not when in bootloader.
Oh well.
Does that mean I might be able to flash an RUU then?
I'd rather not to be honest - I don't want stock - esp given that it was originally a Vodafone One X.
I'd rather go with CM11 if possible.
It just doesn't want to install it though.
I do have Philz 5.11.2 - HTC One X installed, and it seems to do most things I'm finding handy right now - ie charging when in recovery - mounting drives etc.
Related
Hi,
I have a HTC One X international version been in use for last 2 years. Just yesterday, I have unlocked the boot loader following instruction on HTCDev.com. Successfully rooted the phone following the instructions on onexroot.com. I have installed the ClockworkMod ROM on it. Until here things were fine. I have installed the ROM Manager from Android Market. Got the Super Admin. I have downloaded the Carbon ROM and Google Apps zip files to my phone. I have attempted install the Carbon Custom Rom on my phone, got the error status 7. this is where the problem started, by mistaken without taking the backup I have done the wipe data / factory reset. My phone is gone. It doesn't get identified in my Computer. Battery doesn't get charge. I have a clockworkmod recovery v5.8.2.7 on it.
Please please please help.. I did a sin..
bannyk.76 said:
Hi,
I have a HTC One X international version been in use for last 2 years. Just yesterday, I have unlocked the boot loader following instruction on HTCDev.com. Successfully rooted the phone following the instructions on onexroot.com. I have installed the ClockworkMod ROM on it. Until here things were fine. I have installed the ROM Manager from Android Market. Got the Super Admin. I have downloaded the Carbon ROM and Google Apps zip files to my phone. I have attempted install the Carbon Custom Rom on my phone, got the error status 7. this is where the problem started, by mistaken without taking the backup I have done the wipe data / factory reset. My phone is gone. It doesn't get identified in my Computer. Battery doesn't get charge. I have a clockworkmod recovery v5.8.2.7 on it.
Please please please help.. I did a sin..
Click to expand...
Click to collapse
First download the latest CWM 6.0.4.8 from CM11 thread or latest TWRP 2.7.1 or latest Philz recovery from original android section then install carbon rom. Carbon is based on 4.4.2 and you need latest recovery where support kitkat
EDIT: and something else you need to flash boot.img from rom.zip manually with the command fastboot flash boot boot.img , Rom Manager don't work on S-ON devices like ONE X
My phone shows battery level is too low to flash
bannyk.76 said:
Hi,
I have a HTC One X international version been in use for last 2 years. Just yesterday, I have unlocked the boot loader following instruction on HTCDev.com. Successfully rooted the phone following the instructions on onexroot.com. I have installed the ClockworkMod ROM on it. Until here things were fine. I have installed the ROM Manager from Android Market. Got the Super Admin. I have downloaded the Carbon ROM and Google Apps zip files to my phone. I have attempted install the Carbon Custom Rom on my phone, got the error status 7. this is where the problem started, by mistaken without taking the backup I have done the wipe data / factory reset. My phone is gone. It doesn't get identified in my Computer. Battery doesn't get charge. I have a clockworkmod recovery v5.8.2.7 on it.
Please please please help.. I did a sin..
Click to expand...
Click to collapse
Hi,
I am in Fastboot USB mode and the phone shows Battery level is too low to flash
I am unable to copy the files using fastboot commands. Also if I believe the charging levels are fluctuating and not consistent increasing.
Please advise.
Thanks a ton!!
bannyk.76 said:
Hi,
I am in Fastboot USB mode and the phone shows Battery level is too low to flash
I am unable to copy the files using fastboot commands. Also if I believe the charging levels are fluctuating and not consistent increasing.
Please advise.
Thanks a ton!!
Click to expand...
Click to collapse
first try to go in custom recovery and see if you can charge the phone from recovery if not Download THIS and connect the phone in fastboot and run the file chargeonex.bat
EDIT: no such rom like ClockworkMod ROM CWM is a recovery and you must to use command fastboot flash recovery nameofrecovery.img
Thanks a Ton
Your file chargeONEX really did a magic. my phone is charging now, slowly .. slowly ...
May I please request for detailed step by steps for what to be done next? I am getting a hope that my phone will be back to work.. Please advise.
bannyk.76 said:
Your file chargeONEX really did a magic. my phone is charging now, slowly .. slowly ...
May I please request for detailed step by steps for what to be done next? I am getting a hope that my phone will be back to work.. Please advise.
Click to expand...
Click to collapse
after you reach 3800mV flash custom recovery like Philz 5.15.9 and mount sd card copy what you need to the sd card after this if you whant to install 4.4.x you need to flash some of the latest recoverys on CWM,TWRP or Philz because Philz.5.15.9 will not work with the kitkat you can use it only to mount sd card and copy things to sd card. When you are done with the copy things flash the boot.img from rom.zip via fastboot and then flash the rom.zip from recovery and that is
Unable to boot in recovery with CWM 6.x
I have charged the battery for whole night and did a flash a CWM 5.8.4.0 and restarted the phone in recovery. After that I have flashed CWM 6.0 for KitKat and after that I am unable to restart the phone in Recovery mode. It stuck at the HTC Quietly brilliant screen.
Not sure where to start, I am totally confused with too many discussion forums with different suggestions. I am lost and my phone is in screwed up status.
What would you suggest as I am a novice person.
After flashing CWM 5.8.4.0 I am able to start phone in recovery, took back up, what is next? should I do a RUU... what is the funda of S-Off.
This is how my screen looks like now ..
**************Unlocked***********
ENDEAVORU PVT SHIP S-On RL
HBOOT - 1.73.0000
CPLD-NONE
MICROP-None
RADIO-5.1204.167.31
eMMC-boot mode : disabled
CPU-boot mode: disabled
HW Secure boot : enabled
C:\Development\All New>fastboot getvar all
INFOversion: 0.5a
INFOversion-bootloader: 1.73.0000
INFOversion-baseband: 5.1204.167.31
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.19.707.3
INFOserialno: SH23KW105277
INFOimei: 359188045391604
INFOproduct: endeavoru
INFOplatform: HBOOT-T30S
INFOmodelid: PJ4610000
INFOcidnum: HTC__044
INFObattery-status: good
INFObattery-voltage: 3610mV
INFOdevpower: 1
INFOpartition-layout: None
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: None
INFOhbootpreupdate: 2
INFOgencheckpt: 0
all: Done!
I think i am closer
Hot from the POT!!!
Able to mount the SD card in CWM v5.8.4.0 and copied the cm-11-20140613-NIGHTLY-endeavoru and gapps-kk-20140606-signed file and tried to "install zip from SDcard". both have failed with Status 7.
Any advise from here .. it seems I am close to getting back my phone....
bannyk.76 said:
Hot from the POT!!!
Able to mount the SD card in CWM v5.8.4.0 and copied the cm-11-20140613-NIGHTLY-endeavoru and gapps-kk-20140606-signed file and tried to "install zip from SDcard". both have failed with Status 7.
Any advise from here .. it seems I am close to getting back my phone....
Click to expand...
Click to collapse
Yes you must to be with the latest CWM 6.0.4.8 or TWRP2.7.x or Philz latest
Hello friends, I am new to android as i am switching from iphone.I just bought used M8 with viper rom installed.I am hesitating to use the phone as it is because i am afraid if previous owner had installed any bug to scoop out any my personal info.I have already done reset from the settings and now looks like viper rom is gone.Previous owner said that it was locked to rogers(canadian)
It shows :
android version 4.4.3
htc sense version 6.0
insertcoin version 4.0.4
htc sdk api level 6.25
Recovery mode info:
***unlocked***
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.18.0.0000
OpenDSP-v45.2.2-00542-M8974_HM.0422
OS-
Jul 11 2014
My questions are:
1.Should i go to total stock as its never touched and do modding by myself to assure that its free of any bug?
2.What is intercoin?Its already installed.
3.What are the other options i can try? Thanks.
1.Should i go to total stock as its never touched and do modding by myself to assure that its free of any bug?
If you know how, why not ... I make my own custom ROM too
2.What is intercoin?Its already installed.
It's one of a custom ROM that you can find here : http://forum.xda-developers.com/htc-one-m8/development
Your current version is quite old.
3.What are the other options i can try?
You have a S-Off device with the latest firmware, so you're good to flash any Sense based custom ROM in the link I give above
It's good also to take note your modelid (MID), boot to bootloader/fastboot mode
then run command fastboot getvar MID and take note the result.
This is needed to determine your device stock ROM version no. as your bootloader now showing blank OS.
But since it is S-Off, you can change the device to any version that you like, for e.g to an Intl GSM like EU_WWE
Thanks ckpv5 for the reply. You call OS a ROM.right?Does it shows blank OS because i did reset and it wiped viper rom? and can we install multiple roms at the same time?because viperrom and intercoin were installed at the same time.Why after reset,intsertcoin did not go away but viper got cleaned? sorry for the newbie questions,still trying to get into the android..thanks
looks like i am messing it up by saying both roms at same time.I think when i did a reset,it switched from viper to insertcoin.
Another question.If i go to stock,will i be able to root,unlock ,S-off and can install custom rom and TWRP again? and for reverting back to stock,do i have to find stock firmware for the carrier which is rogers?
ninja_zx11 said:
Thanks ckpv5 for the reply. You call OS a ROM.right?Does it shows blank OS because i did reset and it wiped viper rom? and can we install multiple roms at the same time?because viperrom and intercoin were installed at the same time.Why after reset,intsertcoin did not go away but viper got cleaned? sorry for the newbie questions,still trying to get into the android..thanks
looks like i am messing it up by saying both roms at same time.I think when i did a reset,it switched from viper to insertcoin.
Click to expand...
Click to collapse
Most people call OS as ROM but for me, the OS written on the bootloader is meant for the firmware version.
It shows blank because of TWRP bug, nothing to do with reset
I have no idea .. but AFAIK there is no possibility yet to install multiple ROM on a device. When you reset it and it now becomes insertcoin, I believe the ROM installed is insertcoin not viper. Maybe some theming make it look like viper.
---------- Post added at 10:26 AM ---------- Previous post was at 10:19 AM ----------
ninja_zx11 said:
Another question.If i go to stock,will i be able to root,unlock ,S-off and can install custom rom and TWRP again? and for reverting back to stock,do i have to find stock firmware for the carrier which is rogers?
Click to expand...
Click to collapse
Always remember that you don't need to relock bootloader and change to S-On if you decide to go back to stock, so re-unlock and re-S-Off are out of questions for now (you need them only for warranty claim purpose)
With an unlocked bootloader, you can re-root, install TWRP and install custom ROM.
For reverting back to stock .. you still do not answer the question that I posted before ... get the info of command fastboot getvar mid or better if you run fastboot getvar all and post the details of :
(bootloader) version-bootloader: ??
(bootloader) modelid: ??
(bootloader) cidnum: 11111111 (as this device is SuperCID)
then we can talk about firmware and stock ROM
i ran the command and here is the output:
Code:
C:\adb>fastboot 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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA43FWM0xxxx
(bootloader) imei: 35169006007xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(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
all: Done!
finished. total time: 0.054s
also my duo camera is not working.it says not to block the second camera.i think its software problem as there other problems like missing google play store.thats why i want to flash stock and go from there.but you will guide me better.thanks for taking ur time..
1. Grab the TWRP stock nandroid backup that I uploaded : http://forum.xda-developers.com/showpost.php?p=55404564&postcount=1925
2. Use a proper TWRP with OS bug fixed, search in this thread http://forum.xda-developers.com/showthread.php?t=2717932
or follow the link in my signature for the one that I'm using
3. Then follow the following steps :
a. extract the 2.23.631.2.zip to your PC. If you use "extract here" it will be one folder. If you use "extract to 2.23.631.2", you'll have double 2.23.631.2 folder. So use the one inside.
b. to make thing easier, in TWRP select backup and make a backup of your boot, so when you reboot you will see a backup of it either in internal sdcard or external sdcard where the location is TWRP/BACKUPS/YourDeviceSerialNo./BACKUP folder here
c. transfer the extracted 2.23.631.2 to the same folder for backup
so you'll see TWRP/BACKUPS/YourDeviceSerialNo./2.23.631.2
d. boot to recovery - select restore - select 2.23.631.2 then tick all boot, data and system
e. do the restore and wait till it complete
f. done, reboot and you'll be at the setup wizard screen
4. To fix the missing OS on bootloader and to fix any irregularity with current firmware.
a. Download the firmware here : http://sourceforge.net/projects/htconem8/files/2.23.631.2_firmware.zip/download
b. put the 2.23.631.2_firmware.zip in the same folder as your adb/fastboot files on PC
c. boot your device to bootloader/fastboot mode and run the following commands:
fastboot oem rebootRUU
fastboot flash zip 2.23.631.2_firmware.zip
if failed : FAILED (remote: 90 hboot pre-update! please flush image again immediately)
repeat fastboot flash zip 2.23.631.2_firmware.zip
fastboot reboot-bootloader
d. reboot ...done
e. or optional - reflash TWRP recovery and reboot ...done.
ckpv5 said:
1. Grab the TWRP stock nandroid backup that I uploaded : http://forum.xda-developers.com/showpost.php?p=55404564&postcount=1925
2. Use a proper TWRP with OS bug fixed, search in this thread http://forum.xda-developers.com/showthread.php?t=2717932
or follow the link in my signature for the one that I'm using
3. Then follow the following steps :
a. extract the 2.23.631.2.zip to your PC. If you use "extract here" it will be one folder. If you use "extract to 2.23.631.2", you'll have double 2.23.631.2 folder. So use the one inside.
b. to make thing easier, in TWRP select backup and make a backup of your boot, so when you reboot you will see a backup of it either in internal sdcard or external sdcard where the location is TWRP/BACKUPS/YourDeviceSerialNo./BACKUP folder here
c. transfer the extracted 2.23.631.2 to the same folder for backup
so you'll see TWRP/BACKUPS/YourDeviceSerialNo./2.23.631.2
d. boot to recovery - select restore - select 2.23.631.2 then tick all boot, data and system
e. do the restore and wait till it complete
f. done, reboot and you'll be at the setup wizard screen
4. To fix the missing OS on bootloader and to fix any irregularity with current firmware.
a. Download the firmware here : http://sourceforge.net/projects/htconem8/files/2.23.631.2_firmware.zip/download
b. put the 2.23.631.2_firmware.zip in the same folder as your adb/fastboot files on PC
c. boot your device to bootloader/fastboot mode and run the following commands:
fastboot oem rebootRUU
fastboot flash zip 2.23.631.2_firmware.zip
if failed : FAILED (remote: 90 hboot pre-update! please flush image again immediately)
repeat fastboot flash zip 2.23.631.2_firmware.zip
fastboot reboot-bootloader
d. reboot ...done
e. or optional - reflash TWRP recovery and reboot ...done.
Click to expand...
Click to collapse
Thanks a lot ckpv5...i am at work and will try soon and will report back....
I did it and now my phone has all the missing apps.you are greatThanks a lot...
i got few more questions:
1. can i receive OTA updates?
2.My camera still says not to block the second camera. what do you think it could be?
3.So did you have to make special nandroid back up specific to my phone or it was generic?
4.what rom you suggest? viper or android HD? thanks again my friend...
ninja_zx11 said:
I did it and now my phone has all the missing apps.you are greatThanks a lot...
i got few more questions:
1. can i receive OTA updates?
2.My camera still says not to block the second camera. what do you think it could be?
3.So did you have to make special nandroid back up specific to my phone or it was generic?
4.what rom you suggest? viper or android HD? thanks again my friend...
Click to expand...
Click to collapse
1. If you're stock then yes you can receive OTA updates. Need stock recovery as well!!!
2. Is the second camera lens broken? Perhaps it's faulty hence why the original owner sold it off in the first place
3. I think maybe he just converted his phone to your version, did the OTA updates to get latest version, made a backup and uploaded it to share. It'll then be "generic" as anyone could use it. Still doesn't take away the effort he put into it though.
4. We can NOT suggest ROMs. As it'll lead to someone having an opinion that's different for another ROM and it'll boil down to a flame war. All developers work hard on their ROMs and the only one that knows what he wants/needs is YOU! So try them both and use which one you like most. All I can say is that I think ARHD is stock as well, just debloated like crazy. Viper is more customized with themes and stuff. Again, you try them both and stick to the one you like best. :good:
ninja_zx11 said:
I did it and now my phone has all the missing apps.you are greatThanks a lot...
i got few more questions:
1. can i receive OTA updates?
2.My camera still says not to block the second camera. what do you think it could be?
3.So did you have to make special nandroid back up specific to my phone or it was generic?
4.what rom you suggest? viper or android HD? thanks again my friend...
Click to expand...
Click to collapse
1. Yes...when there is one available
2. Maybe a hardware issue, not sure ...or dirty lense, try clean the lense
3. No.. it's specific for your device version ..so it is stock for Rogers and a custom for non-Rogers
4. I can't suggest any ROM as I don't use all of them... you should try all of them and decide what is best for your needs.
I wanted to get rid of old data and pictures from the phone but they are still there.I even tried to do factory reset from the settings--backup &reset-----reset phone---selected erase all data and erase sd card but all the old pictures are still in there.Now i got some questions again.
1.How to get rid of them and how to wipe everything and make it as a new phone like out of the box.Latest TWRP is installed.
2.Also sometimes i get a red warning while booting saying that something do not distribute this build....How to get rid of that red warning.
3.Previous owner had installed custom boot bios screen like bios similar to what we have in PC's.and that screen still shows android version 4.4.2 but if i go to software information from the settings menu,it shows 4.4.3.Thanks
ninja_zx11 said:
I wanted to get rid of old data and pictures from the phone but they are still there.I even tried to do factory reset from the settings--backup &reset-----reset phone---selected erase all data and erase sd card but all the old pictures are still in there.Now i got some questions again.
1.How to get rid of them and how to wipe everything and make it as a new phone like out of the box.Latest TWRP is installed.
Click to expand...
Click to collapse
Try this and see whether it will work for you :
boot to recovery - select wipe - select advance wipe - select internal storage - swipe to wipe
This will remove everything on your internal sdcard/memory so make a backup to PC before you attempt this
ninja_zx11 said:
2.Also sometimes i get a red warning while booting saying that something do not distribute this build....How to get rid of that red warning.
Click to expand...
Click to collapse
That's because of custom recovery and/or custom kernel is installed. To remove that, you need a modified hboot. Make a request in this thread and provide him your device firmware (I linked that before, right ?) (also note that you need to complete 10 posts before you can write in this thread)
http://forum.xda-developers.com/showthread.php?t=2710503
ninja_zx11 said:
3.Previous owner had installed custom boot bios screen like bios similar to what we have in PC's.and that screen still shows android version 4.4.2 but if i go to software information from the settings menu,it shows 4.4.3
Click to expand...
Click to collapse
That's customized splash screen. There are many more here : http://forum.xda-developers.com/htc...-customize-boot-splash-online-splash-t2817059
and you can make one on your own with your own image with his online service
If you need a stock one, attached is mine ... flash/install it in recovery
So i put sim in it and tried.For some reason i am not able to get LTE.Just 4G even i am in LTE zone.Even i got a new rogers LTE sim card but still just 4G only.Any ideas? Thanks
Did some other test.I put my friends iphone 5's (which i know has working LTE) sim into my M8 and instantly LTE is working on my M8.So the problem is from ROGERS's side.I am going to call them.
Problem solved.They refreshed my data account at their end and LTE is working now.
As everything is working now with the help of ckpv5 and now its the time to understand the android system and also i would like to remove some confusions about android system.
1.Does restoring via someone's nandroid backup (over 1 GB in size) means like cloning two phones? Restoring using someone's nandroid backup does not alter imie and serial number?.So where are serial,imie and mac addresses gets stored? and whats that area called where all this data gets stored?
2.What is firmware.zip?. Like ckpv5 told me in previous post to put 2.23.631.2_firmware.zip (just 45.5Mb in size) in adb folder and use these"fastboot oem rebootRUU
fastboot flash zip 2.23.631.2_firmware.zip" commands.So if i had already done full nandroid restore,then why it was necessary to use 2.23.631.2_firmware.zip. What did that step do?
3.There was another file named 2.23.631.2_recovery.img (just 15.2 Mb) in this post .http://forum.xda-developers.com/showpost.php?p=55404564&postcount=1925. What is this file for?
Sorry i got so confused with all these different files.Thanks
ninja_zx11 said:
1.Does restoring via someone's nandroid backup (over 1 GB in size) means like cloning two phones? Restoring using someone's nandroid backup does not alter imie and serial number?.So where are serial,imie and mac addresses gets stored? and whats that area called where all this data gets stored?
Click to expand...
Click to collapse
No, not cloning as you can't write the imei and serial no. I have no idea where are those stored as I never bothered to know them (you can try to search for info if you want to). The nandroid will restore/put the files on your system partition and data partition too (for my backup, the data partition is filled with preload folder and preload files only, no other user data)
ninja_zx11 said:
2.What is firmware.zip?. Like ckpv5 told me in previous post to put 2.23.631.2_firmware.zip (just 45.5Mb in size) in adb folder and use these"fastboot oem rebootRUU
fastboot flash zip 2.23.631.2_firmware.zip" commands.So if i had already done full nandroid restore,then why it was necessary to use 2.23.631.2_firmware.zip. What did that step do?
Click to expand...
Click to collapse
Firmware and ROM are two different things. The nandroid backup is the ROM which is software. The firmware is like a bios. I asked you to reflash firmware because the condition of your phone, so flashing a firmware will bring it back the way it should. Some people will flash all kind of firmware when they S-Off and some are mixed firmware. As you bought this from someone ..so it's best to restore the firmware to stock one, same as you restore the ROM to stock one when restoring my uploaded nandroid.
ninja_zx11 said:
3.There was another file named 2.23.631.2_recovery.img (just 15.2 Mb) in this post .http://forum.xda-developers.com/showpost.php?p=55404564&postcount=1925. What is this file for?
Click to expand...
Click to collapse
That is for people require the stock recovery only when they want to do next OTA update or return everything to stock for warranty purpose or maybe sell the device.
Today I received the android m update I download it and install stock recovery so I can install the update But every Time I do it gets to the half of the bar and then says install aborted I have tried factory reset and wipe cache nothing worked
I had twrp recovery before And every time I get any update I replace the twrp with stock recovery and it always worked for me until today
Any solution please?????
What did you use TWRP for, or better asked what did you change on your system? Has your system been rooted or the system.img been manipulated in any kind?
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
HTCNerdYoda said:
What did you use TWRP for, or better asked what did you change on your system? Has your system been rooted or the system.img been manipulated in any kind?
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
Click to expand...
Click to collapse
I used TWRP for root access and yes my system Is rooted but and boot loader unlocked for reinstalling stock recovery was working before and the updates were installed successfully
OTA failure
My device is not rooted and today I tried to upgrade to marshmallow (ota) but it failed to do so after 80% it aborted the installation and now I'm stuck with a dump phone please help I'm not familiar with this kind of situation. I tried to wipe cache partition and wipe data/factory reset but nothing works. IT says on the screen:
Android Recovery
HTC/htc_m8/htc_m8
6.0/MRA58K/buildteam12171409
user/release-keys
Use volume up/down and power.
-----------------------------------------
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Power off
-----------------------------------------
Supported API: 3
handle_cota_install: install cwpkg to/c
ache/data/cwtemp/cwpkg.zip
handle_cota_install: install cwprop to /
cache/data/cwtemp/cw.prop
Write host_mode success
handle_cota_install: No CW files. Skip c
w installation.
ecmelg said:
My device is not rooted and today I tried to upgrade to marshmallow (ota) but it failed to do so after 80% it aborted the installation and now I'm stuck with a dump phone please help I'm not familiar with this kind of situation. I tried to wipe cache partition and wipe data/factory reset but nothing works. IT says on the screen:
Android Recovery
HTC/htc_m8/htc_m8
6.0/MRA58K/buildteam12171409
user/release-keys
Use volume up/down and power.
-----------------------------------------
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Power off
-----------------------------------------
Supported API: 3
handle_cota_install: install cwpkg to/c
ache/data/cwtemp/cwpkg.zip
handle_cota_install: install cwprop to /
cache/data/cwtemp/cw.prop
Write host_mode success
handle_cota_install: No CW files. Skip c
w installation.
Click to expand...
Click to collapse
Try flashing RUU for ur model id.
Alxens said:
I used TWRP for root access and yes my system Is rooted but and boot loader unlocked for reinstalling stock recovery was working before and the updates were installed successfully
Click to expand...
Click to collapse
If it is rooted the OTA won't be installed as the system partition and thus it's md5 has been changed by mounting it r/w and flashing SuperSU. This is as google and HTC following this guidelines changed the OTA delivery to a block based system where the routine checks if the system has been untouched prior to installing it. You got to restore the untouched image of the system partition for your device. After this you could flash the stock recovery and install the OTA.
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
HTCNerdYoda said:
If it is rooted the OTA won't be installed as the system partition and thus it's md5 has been changed by mounting it r/w and flashing SuperSU. This is as google and HTC following this guidelines changed the OTA delivery to a block based system where the routine checks if the system has been untouched prior to installing it. You got to restore the untouched image of the system partition for your device. After this you could flash the stock recovery and install the OTA.
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
Click to expand...
Click to collapse
I have twrp backup system
would this work??
Alxens said:
Today I received the android m update I download it and install stock recovery so I can install the update But every Time I do it gets to the half of the bar and then says install aborted I have tried factory reset and wipe cache nothing worked
I had twrp recovery before And every time I get any update I replace the twrp with stock recovery and it always worked for me until today
Any solution please?????
Click to expand...
Click to collapse
Esta solución me sirvió a mi. www . htc.com/us/support/rom- downloads . html (saca los espacios) en tú caso descarga la versión desbloqueada
Yes would work
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
I'm having the same problem. I don't have a ROOT and already talked to the HTC help desk and didn't find any solution. With this TWRP can I fix this problem?
sonoman87 said:
I'm having the same problem. I don't have a ROOT and already talked to the HTC help desk and didn't find any solution. With this TWRP can I fix this problem?
Click to expand...
Click to collapse
Most likely NO.
The above user(s) used TWRP backups to remove changes that were done by root.
Since you never rooted (from the sounds of it) you don't have the same problem.
redpoint73 said:
Most likely NO.
The above user(s) used TWRP backups to remove changes that were done by root.
Since you never rooted (from the sounds of it) you don't have the same problem.
Click to expand...
Click to collapse
Thanks redpoint73. So, what do you recommend me to do now? Because, the problem started with the android notification of the update and then the system crashed. Search for a ROM and try to install it?
Thanks again!
sonoman87 said:
Thanks redpoint73. So, what do you recommend me to do now? Because, the problem started with the android notification of the update and then the system crashed. Search for a ROM and try to install it?
Click to expand...
Click to collapse
If there is a MM RUU for your version, download and run it.
redpoint73 said:
If there is a MM RUU for your version, download and run it.
Click to expand...
Click to collapse
I've fixed it! Thanks so much again!
sonoman87 said:
I've fixed it! Thanks so much again!
Click to expand...
Click to collapse
Which country are you from? And which ROM did you use? I'm from Spain and I'm afraid if I install the ROM it wouldn't work again in my country
oscar1355 said:
Which country are you from? And which ROM did you use? I'm from Spain and I'm afraid if I install the ROM it wouldn't work again in my country
Click to expand...
Click to collapse
First of all, you need to understand that ROM and RUU are two very different things.
Also, nobody can advise you the proper RUU is, without knowing some basic information. Namely, do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
Hey everyone,
I am trying to get my M8 to stock (been stuck at this for about 10 days now, tried everything). I am from India. There was some problem and I accidentally have a phone now with no OS and TWRP. I have installed stock recovery and plan to flash the ROM/RUU. Some details of my device:
Software status: Modified
Unlocked S-ON
C:\Android>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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: <serial number>
(bootloader) imei: <imei number>
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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
I would really appreciate it if you could guide me how to get my phone to stock OS. The ROM that I should prefer etc. I have been going through a lot of forums and ended up being utterly confused.
Thanks in advance for the help!
skull_143 said:
been stuck at this for about 10 days now, tried everything
There was some problem and I accidentally have a phone now with no OS and TWRP.
Click to expand...
Click to collapse
Sorry, this is a pet peeve of mine, but I really wish folks would stop posting they "tried everything". This literally tells us nothing, and you should list specifically one-by-one (and in detail) what things you tried, and the results (again in detail) of each.
"Accidentally" appears to mean you unlocked the bootloader, then flashed an very old, obsolete version TWRP (which causes the main version to be blank) then decided it was a good idea to wipe the OS (system)? Again, you need to tell us exactly what steps you took to get to this point.
My next advice to you, is to only do things that are specifically instructed for you to do in your situation. Don't guess or do things without fully understanding them. As your present situation seems to indicate you don't have a very good understanding of what you are doing, and only making matter worse by proceeding with insufficient knowledge.
skull_143 said:
I have installed stock recovery and plan to flash the ROM/RUU. Some details of my device
Click to expand...
Click to collapse
RUU will only work if its version 6.15.720.2
Your version (CID and MID) is rather obscure, so I'm not sure whether such RUU exists or not. If not, your best bet is to get TWRP back on the phone, and restore the stock nandroid 6.15.720.2 using the files and instructions on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Also, flashing stock recovery is not needed to RUU; and not helpful in your current situation (you'll probably need to go back to custom recovery TWRP).
redpoint73 said:
Sorry, this is a pet peeve of mine, but I really wish folks would stop posting they "tried everything". This literally tells us nothing, and you should list specifically one-by-one (and in detail) what things you tried, and the results (again in detail) of each.
"Accidentally" appears to mean you unlocked the bootloader, then flashed an very old, obsolete version TWRP (which causes the main version to be blank) then decided it was a good idea to wipe the OS (system)? Again, you need to tell us exactly what steps you took to get to this point.
My next advice to you, is to only do things that are specifically instructed for you to do in your situation. Don't guess or do things without fully understanding them. As your present situation seems to indicate you don't have a very good understanding of what you are doing, and only making matter worse by proceeding with insufficient knowledge.
RUU will only work if its version 6.15.720.2
Your version (CID and MID) is rather obscure, so I'm not sure whether such RUU exists or not. If not, your best bet is to get TWRP back on the phone, and restore the stock nandroid 6.15.720.2 using the files and instructions on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Also, flashing stock recovery is not needed to RUU; and not helpful in your current situation (you'll probably need to go back to custom recovery TWRP).
Click to expand...
Click to collapse
Sorry about the shortened version, just though it might be too big and unnecessary. Okay here goes what happened. I moved the whatsapp media to my laptop (at this time the device was unrooted and running stock android M updated over OTA). After the move, the device was stuck at the splash screen with HTC logo. After this I gave the phone to a service centre (not official HTC) and asked them to NOT root and put stock OS and get the phone working. What they did was, rooted it and installed a custom ROM with TWRM recovery (which was very screwed up, as in the camera kept crashing and I couldn't even use that). So, I decided to get it back to stock ROM and sense UI.
So what I did was looked up some thread (not sure which one) and went ahead to do a wipe through recovery. Here I did the mistake of wiping everything and so the device doesn't have any OS at the moment. The phone is still getting stuck in HTC logo now (obviously as it doesn't have an OS). I have tried to do the following:
1. To flash the boot only using fastboot flash boot and fastboot flash zip commands. The version I tried was stock 3.35.720.1_recovery.img. This didnt seem to work.
2. Next tried to go to usb fastboot mode and tried to run the RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe official one from the laptop. But it showed some mismatch of versions and aborted.
3. Then I read that stock could only be flashed on S-ON devices if we relock the bootloader. So used the fastboot oem relock command to relock bootloader and then tried both the above but didn't work.
4. Next saw somewhere that it is pretty impossible to flash on a locked S-ON device. So went to htcdev and got the bootloader unlocked again.
5. Downloaded a stock image 3.35.720.1 Stock Unrooted. Read that we need lower or same stock recovery to flash the same and so flashed the stock recovery of the same version. Next extracted the .win001 and .win002 files using the tar command and finally put them along with META_INF folder and boot.img files into a zip file. The image had the contents of the system folder and tried to flash this using fastboot and also through the stock option "Update from SD card". Got error "E: footer is wrong. E: update signature verification failed".
This is the status so far. I am not sure what I should be doing anymore. Hope this helps in understanding the situation. Sorry it's so long.
Please advice what I should do now. Currently, I have stock recovery installed and no OS. I just want to have the stock sense OS on the device.
Thanks for all your time.
skull_143 said:
Please advice what I should do now. Currently, I have stock recovery installed and no OS. I just want to have the stock sense OS on the device.
Thanks for all your time.
Click to expand...
Click to collapse
1. Download the 6.15.720.2 RUU.zip : http://forum.xda-developers.com/showpost.php?p=66309774&postcount=20
2. relock the bootloader with command - fastboot oem lock
option 1 - if you have a microsd
1. rename the downloaded RUU.zip as to 0P6BIMG.zip
2. put it on root of your microsd not in any folder
3. on bootloader select hboot - it will scan the zip and ask you to update.
4. select volume up to update
5. once completed, delete the zip from microsd
option 2
1. Download htc_fastboot.exe : https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/view
2. put both htc_fastboot.exe and the 0P6BIMG.zip in your fastboot folder
3. run below commands :
fastboot reboot-bootloader (reboot to bootloader to ensure the connection is good)
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip 0P6BIMG.zip (to install RUU - read it is htc_fastboot not fastboot)
Once complete - fastboot reboot
run setup .. done
Sorry about any terminology...
Recently my htc one m8 stopped booting. I had rooted it a long time ago and had a ROM that was working fine for a long time. No recent changes.
On normal boot it sits on the white and green text 'htc' forever.
If I boot with power+down buttons I get to a hboot screen, but choosing 'recovery' takes me to a white screen small pink 'Entering Recovery' text. Nothing happens. To even get power+down screen to be available I had to move two zip files from root of sdcard which I guess were related to the custom rom, being 0P6BIMG.zip and M8-GPE-03-16-2015.zip
I tried reinstalling twrp after downloading the latest .img file
fastboot command
c:\twrp>fastboot flash recovery twrp-3.0.2-0-m8.img
just says <waiting for device> whether on pink text screen or white 'htc'
I can see the sdcard through a pc card reader and manipulate files. Is there any way to copy files manually so it will boot?
This is on Win 10, UK unlocked version of phone.
bt999 said:
To even get power+down screen to be available I had to move two zip files from root of sdcard which I guess were related to the custom rom, being 0P6BIMG.zip and M8-GPE-03-16-2015.zip
Click to expand...
Click to collapse
When you have a file named 0P6BIMG.zip, it will automatically try to install it every time you enter bootloader. Its an update or RUU of some sort, placed there by you, but exactly what is impossible to tell.
The other file is a ROM zip for a GPE ROM, which I would guess is the custom ROM you installed. It doesn't make a difference for this file not be on the SD card or not (bootloader will not try to install it automatically, and bootloader will function normally).
bt999 said:
I tried reinstalling twrp after downloading the latest .img file
fastboot command
c:\twrp>fastboot flash recovery twrp-3.0.2-0-m8.img
just says <waiting for device> whether on pink text screen or white 'htc'
Click to expand...
Click to collapse
Are you in bootloader-fastboot mode when you run the command (which is required)? Meaning, FASTBOOT should be highlighted in red just under the green text on the bootloader screen. If not, just select using the vol buttons, and confirm using power button.
Fastboot clarification
redpoint73 said:
When you have a file named 0P6BIMG.zip, it will automatically try to install it every time you enter bootloader. Its an update or RUU of some sort, placed there by you, but exactly what is impossible to tell.
The other file is a ROM zip for a GPE ROM, which I would guess is the custom ROM you installed. It doesn't make a difference for this file not be on the SD card or not (bootloader will not try to install it automatically, and bootloader will function normally).
Are you in bootloader-fastboot mode when you run the command (which is required)? Meaning, FASTBOOT should be highlighted in red just under the green text on the bootloader screen. If not, just select using the vol buttons, and confirm using power button.
Click to expand...
Click to collapse
Thanks for your reply.
I guess the 0P6BIMG.zip file would explain why it was always slow to boot when things were working ok, if it was being reinstalled each time. I don't recall its purpose.
I wasn't in bootloader-fastboot mode when trying the fastboot command, but have tried it again.
When connected to an Ubuntu 16.04 machine the white on red text says 'fastboot usb', but ubuntu commandline fastboot flash ... gives same 'waiting for device'. When connected to Win 10 white/red text just says 'fastboot', if that is relevant. When I installed fastboot on Win 10 from instructions at http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 there is a note to remove Google drivers before installing new ones - I did not do this, not sure if relevant, but new driver install gave no errors.
Is there a way to copy a new ROM image to the sdcard so that on 'normal' booting it gets detected and applied? Or to copy twrp somewhere manually?
Is there a log file that would show how far through the normal boot things get? I guess it is inaccessible until things work better.
bt999 said:
I wasn't in bootloader-fastboot mode when trying the fastboot command, but have tried it again.
When connected to an Ubuntu 16.04 machine the white on red text says 'fastboot usb', but ubuntu commandline fastboot flash ... gives same 'waiting for device'. When connected to Win 10 white/red text just says 'fastboot', if that is relevant. When I installed fastboot on Win 10 from instructions at http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 there is a note to remove Google drivers before installing new ones - I did not do this, not sure if relevant, but new driver install gave no errors.
Click to expand...
Click to collapse
Try going into Windows Device Manager, finding the device, and picking the option to manually select drivers, and select the generic Android MTP drivers. See if that helps fastboot connect.
Make sure you have HTC drivers (HTC Sync) installed as well. Try to re-install HTC Sync.
bt999 said:
Is there a way to copy a new ROM image to the sdcard so that on 'normal' booting it gets detected and applied? Or to copy twrp somewhere manually?
Click to expand...
Click to collapse
You can't flash a ROM, if TWRP isn't working properly. And there isn't a way to make one automatically flash upon normal boot, that I am aware.
I've seen some folks make 0P6BIMG.zip files for TWRP, which will install automatically when you boot to bootloader. But honestly, USB fastboot connectivity is a pretty vital thing to have working, and usually just a matter of right drivers and a good cable (and being in fastboot mode is a must), so shouldn't be that hard to troubleshoot.
Old twrp
redpoint73 said:
Try going into Windows Device Manager, finding the device, and picking the option to manually select drivers, and select the generic Android MTP drivers. See if that helps fastboot connect.
Make sure you have HTC drivers (HTC Sync) installed as well. Try to re-install HTC Sync.
You can't flash a ROM, if TWRP isn't working properly. And there isn't a way to make one automatically flash upon normal boot, that I am aware.
I've seen some folks make 0P6BIMG.zip files for TWRP, which will install automatically when you boot to bootloader. But honestly, USB fastboot connectivity is a pretty vital thing to have working, and usually just a matter of right drivers and a good cable (and being in fastboot mode is a must), so shouldn't be that hard to troubleshoot.
Click to expand...
Click to collapse
I have got a twrp running, unfortunately it says it is only compatible with bootloader 3.19 and above when I try to install the rom. I have 3.16.
Do you know where I can get an old twrp?
Thanks.
bt999 said:
I have got a twrp running, unfortunately it says it is only compatible with bootloader 3.19 and above when I try to install the rom. I have 3.16.
Do you know where I can get an old twrp?
Thanks.
Click to expand...
Click to collapse
https://dl.twrp.me/m8/
twrp versions
xunholyx said:
https://dl.twrp.me/m8/
Click to expand...
Click to collapse
Thanks. I have now tried
twrp-2.7.0.1-m8.img twrp-2.7.1.0-m8.img twrp-2.8.7.0-m8.img
twrp-2.7.0.2-m8.img twrp-2.8.0.0-m8.img twrp-3.0.2-0-m8.img
The oldest ones don't run the newer ones work but I still get an error on attempting to install the custom ROM. I think I may be misinterpreting the error message. I now think it is telling me the custom ROM needs bootloader 3.19, rather than twrp not being able to run, i.e. twrp knows not to install the rom.
Message 'This package supports bootloader(s): 3.19.0.0000; this device has bootloader 3.16.0.0000'
Do you know how I can update my bootloader?
bt999 said:
Do you know how I can update my bootloader?
Click to expand...
Click to collapse
Post fastboot getvar all result without serial & imei no.
Without proper info, everyone is guessing what you actually need.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: HTC__001
(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: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I found this thread http://forum.xda-developers.com/showthread.php?t=2696282 and went through the process with a zip linked from there , but I guess it was old and turned out to still be 3.16
Shouldn't HTC be distributing these files? Or my carrier?
You need to relock bootloader if not yet done.
Command :
fasboot oem lock
fastboot reboot-bootloader
Then follow this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Put both files in your adb/fastboot folder.
(The guide was written for system-wide adb/fastboot)
Once completed, you can re unlock boorloader and install latest TWRP and install any ROM that you like, if you want to.
I have a working phone now, htc setup screens ended up with no google account prompts or apps, so I installed cwm nightlies and open-gapps hoping I would have full functionality, however gapps was rejected for not having enough internal storage.
I don't care whether htc or cwm but need gapps/play store. Is there anything you can suggest?
/Last reply lost..]I now have a working phone with cwm nightlies. Unfortunately open-gapps wont install saying not enough space on internal drive.
Any suggestions on how to clear space or to make HTC install Google accounts/store (it did not ask)?
I have a working phone now.
RUU didn't install google app store, so I installed cwm nightlies. I got an error that there was not enough space on internal for open-gappps.
Is there a way to free up space?
bt999 said:
I have a working phone now.
RUU didn't install google app store, so I installed cwm nightlies. I got an error that there was not enough space on internal for open-gappps.
Is there a way to free up space?
Click to expand...
Click to collapse
I have no idea what cwm nightlies is ... but if you have this kind of error not enough internal space ... you need to format data (not wipe) in TWRP.
Install latest TWRP, select wipe - format data - yes ... reboot to recovery again, now you can install ROM.
Solved
ckpv5 said:
I have no idea what cwm nightlies is ... but if you have this kind of error not enough internal space ... you need to format data (not wipe) in TWRP.
Install latest TWRP, select wipe - format data - yes ... reboot to recovery again, now you can install ROM.
Click to expand...
Click to collapse
I installed a mini gapps that had just Play Store then installed other apps manually through that.
Thank you all for your help, this is a well-informed forum.
For anyone reading one thing I learned was to run fastboot from Ubuntu/Linux with 'sudo' or else it will not connect, just says 'waiting for device'
ckpv5 said:
I have no idea what cwm nightlies is
Click to expand...
Click to collapse
He means CM, not CWM. Easy mistake to make (adding one letter) but the two are completely different things (Cyanogen Mod custom ROM versus Clockwork Mod custom recovery).
Hi,
after normally being a consumer on XDA for many years (actually started with the HTC Touch) and always been able to solve my problems by reading, this is the first time I am genuinly stuck and see no way out...
Following details:
- Phone: HTC One M9 International unlocked
- S-off
- Latest Nougat firmware with ICE ROM
All worked fine until today. I was copying Titanium Backup data from internal storage to external SD card and out of nowhere the phone tried to reboot. As of that point it just keeps in a bootloop and will not stop. So...I have tried following:
- Boot to Bootloader: successfull
- Boot to Download: does not work, results in a bootloop
- Boot to Recovery (latest TWRP installed): does not work, results in a bootloop
- From Bootloader tried to fastboot flash recovery. It tells "OKAY" but does not do anything
- Tried all the fastboot erase options: no change
- Fastboot boot twrp recovery: this works allowing me to use TWRP with following symptoms:
- Clean ROM install, stuck at 61.82% and does not continue
- Mount or Wipe fails on any of the partitions: "Unable to mount...." system, cache, data...whatever.....it cannot mount anything
- ADB sideload does not work
- Clean RUU Install does not work, tells me the battery is below 30% where it is charged fully
- Putting RUU zip straight on SD does not trigger install
- Fastboot oem relock does not work
Now I am actually lost for any further ideas. I am afraid there is some hardware corruption or so, but am not sure if there would be any other option to try, or if someone has any further ideas for me.
As I said....reading normally solves all my issues, but I have been reading everything i could find on this topic and tried everything, but all without success....
Thanks for any suggestions...
Cheers
Remko
remko said:
Hi,
after normally being a consumer on XDA for many years (actually started with the HTC Touch) and always been able to solve my problems by reading, this is the first time I am genuinly stuck and see no way out...
Following details:
- Phone: HTC One M9 International unlocked
- S-off
- Latest Nougat firmware with ICE ROM
All worked fine until today. I was copying Titanium Backup data from internal storage to external SD card and out of nowhere the phone tried to reboot. As of that point it just keeps in a bootloop and will not stop. So...I have tried following:
- Boot to Bootloader: successfull
- Boot to Download: does not work, results in a bootloop
- Boot to Recovery (latest TWRP installed): does not work, results in a bootloop
- From Bootloader tried to fastboot flash recovery. It tells "OKAY" but does not do anything
- Tried all the fastboot erase options: no change
- Fastboot boot twrp recovery: this works allowing me to use TWRP with following symptoms:
- Clean ROM install, stuck at 61.82% and does not continue
- Mount or Wipe fails on any of the partitions: "Unable to mount...." system, cache, data...whatever.....it cannot mount anything
- ADB sideload does not work
- Clean RUU Install does not work, tells me the battery is below 30% where it is charged fully
- Putting RUU zip straight on SD does not trigger install
- Fastboot oem relock does not work
Now I am actually lost for any further ideas. I am afraid there is some hardware corruption or so, but am not sure if there would be any other option to try, or if someone has any further ideas for me.
As I said....reading normally solves all my issues, but I have been reading everything i could find on this topic and tried everything, but all without success....
Thanks for any suggestions...
Cheers
Remko
Click to expand...
Click to collapse
Sounds like a chip on your motherboard went bad. Try pulling the system information (fastboot getvar all) and seeing what comes up. I'd bet you get some missing information, which is a sign of the same.
C:\HTC10\platform-tools>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT577YJ00072
all:
finished. total time: 0.156s
That is what getvar gives me. I also have the feeling that fastboot isn't working as it should. Flashing recovery also gives me OK but does not seem to work...