hi @ all,
im semi-familiar with rooting and flashing on several phones and tablets , learning by doing for one year or so ...
... but in this case i think my phone is at the end of trial and error so i hope to find some one who realy knows what to do
look
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3654mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.034s
this HTC one 801n (m7ul) was htcdev unlocked s-off by rumrunner,tempered removed , latest darkboot firmware from htc1guru , normaly runing renovate with elementalx but even every other rom-kernel combination i used worked quite well so as backup and restore
in TWRP i made a fullwhipe and flashed CM11 M3 and boot to system , made some settings it seemed to be ok , i boot to recovery ,whipe and flash elementalx kernel , while flashing the screen went black and i find my phone in this condition :
no light at all , no reaction at all , -i am on win 7- in system there is a "myHTC" device and fastboot seemed to work but every try to flash :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip 4.19.401.8_firmware_darkboot.zip
target reported max download size of 452980736 bytes
sending 'zip' (24782 KB)...
OKAY [ 1.105s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 1.109s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: -1
OKAY [ 0.044s]
finished. total time: 0.045s
after this the phone does not answer any more :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip 4.19.401.8_firmware_darkboot.zip
< waiting for device >
is there some one to take my hand and lead me out off this darkness, please
muezae said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 35xxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
Click to expand...
Click to collapse
not again :crying:
Is that really the output of your getvar? in particular the ones in bold-red?
nkk71 said:
not again :crying:
Is that really the output of your getvar? in particular the ones in bold-red?
Click to expand...
Click to collapse
Well if that really is the output of the getvar.. it don't look good
Wish the noobs would read and then re-read all the guides, befor messing with their phones
nkk71 said:
not again :crying:
Is that really the output of your getvar? in particular the ones in bold-red?
Click to expand...
Click to collapse
yes it is ,
i can fastboot oem writecid and imei but at next reconect settings are gone agin , also serialnumber is not correct
muezae said:
yes it is ,
i can fastboot oem writecid and imei but at next reconect settings are gone agin , also serialnumber is not correct
Click to expand...
Click to collapse
So do you want to explain how the phone got in this condition or should we just guess ?
flashed CM11 M3 and boot to system , made some settings it seemed to be ok , i boot to recovery ,wipe and flash elementalx kernel , while flashing the screen went black and i find my phone in this condition :
Click to expand...
Click to collapse
Seems you were intentionally trying to brick the phone
Does everyone mix and match OS and Kernels like this ?
From the ElementalX thread
Kernel for Google Play Edition and Sense-based ROMs
Click to expand...
Click to collapse
where does it say CM 11 ?
muezae said:
yes it is ,
i can fastboot oem writecid and imei but at next reconect settings are gone agin , also serialnumber is not correct
Click to expand...
Click to collapse
Sorry mate, I think it's best to send it to repair, your mfg partition is corrupt, and there's no redundancy for that, and it contains a lot more info than just your serial number and modelid.
Just out of curiosity, do you also have Active Commandline overflow, in the bootloader screen? and can you share the links and version numbers of:
"in TWRP i made a fullwhipe and flashed CM11 M3 and boot to system , made some settings it seemed to be ok , i boot to recovery ,whipe and flash elementalx kernel , while flashing the screen went black and i find my phone in this condition"
bored_stupid said:
Well if that really is the output of the getvar.. it don't look good
Wish the noobs would read and then re-read all the guides, befor messing with their phones
Click to expand...
Click to collapse
thanks for relay but what do you think did i noob not read and reread ? this was happen to me during normal flash with correct kernel , i like to know my mistake but i dont see , do you ?
muezae said:
thanks for relay but what do you think did i noob not read and reread ? this was happen to me during normal flash with correct kernel , i like to know my mistake but i dont see , do you ?
Click to expand...
Click to collapse
This "im semi-familiar with rooting and flashing on several phones and tablets , learning by doing for one year or so ..." means you're not a noob.
And you're not the first in this situation, but I'd appreciate it if you could answer my previous question, about links and versions.
Thanks
nkk71 said:
Sorry mate, I think it's best to send it to repair, your mfg partition is corrupt, and there's no redundancy for that, and it contains a lot more info than just your serial number and modelid.
Just out of curiosity, do you also have Active Commandline overflow, in the bootloader screen? and can you share the links and version numbers of:
"in TWRP i made a fullwhipe and flashed CM11 M3 and boot to system , made some settings it seemed to be ok , i boot to recovery ,whipe and flash elementalx kernel , while flashing the screen went black and i find my phone in this condition"
Click to expand...
Click to collapse
thak you
CM11 M3 : http://download.cyanogenmod.org/?type=snapshot&device=m7
TWPR is 2.6.2.4 at the moment i dont know from where i got it
elementalx : http://forum.xda-developers.com/showthread.php?t=2249774 ; now i see this is not what i whant to flash ,
Just out of curiosity, do you also have Active Commandline overflow, in the bootloader screen? SORRY ???
muezae said:
thak you
CM11 M3 : http://download.cyanogenmod.org/?type=snapshot&device=m7
TWPR is 2.6.2.4 at the moment i dont know from where i got it
elementalx : http://forum.xda-developers.com/showthread.php?t=2249774 ; now i see this is not what i whant to flash ,
Just out of curiosity, do you also have Active Commandline overflow, in the bootloader screen? SORRY ???
Click to expand...
Click to collapse
1- you mean TWRP 2.6.3.4 right?
2- which version of elementalX, do you remember?
3- look at first screenshot here: http://forum.xda-developers.com/showpost.php?p=50678849&postcount=23 do you have "Active cmdline overflow" too?
This is not helping you, I'm sorry for that.
I'm just trying to trace how/why/what could have corrupted your mmcblk0p6 [mfg] partition (the one in the screenshot is s-on, so it didn't get corrupted, but no solution yet either even with S-On)
On the other hand, the guy in this thread is in exactly the same situation as you, and here you can see what the mfg partition is about: http://forum.xda-developers.com/showpost.php?p=50712531&postcount=37
clsA said:
So do you want to explain how the phone got in this condition or should we just guess ?
Seems you were intentionally trying to brick the phone
Does everyone mix and match OS and Kernels like this ?
From the ElementalX thread
where does it say CM 11 ?
Click to expand...
Click to collapse
yes thank you , i dont know why i guess it is for CM11 ...
muezae said:
yes thank you , i dont know why i guess it is for CM11 ...
Click to expand...
Click to collapse
Sorry but you made many mistakes in a row and now it's not recoverable(that I can tell)
nkk71 said:
1- you mean TWRP 2.6.3.4 right?
2- which version of elementalX, do you remember?
3- look at first screenshot here: http://forum.xda-developers.com/showpost.php?p=50678849&postcount=23 do you have "Active cmdline overflow" too?
This is not helping you, I'm sorry for that.
I'm just trying to trace how/why/what could have corrupted your mmcblk0p6 [mfg] partition (the one in the screenshot is s-on, so it didn't get corrupted, but no solution yet either even with S-On)
On the other hand, the guy in this thread is in exactly the same situation as you, and here you can see what the mfg partition is about: http://forum.xda-developers.com/showpost.php?p=50712531&postcount=37
Click to expand...
Click to collapse
yes TWRP 2.6.3.4 , ElementalX-m7-13.0 , i got a black screen so dont know cmdline overflow
clsA said:
Sorry but you made many mistakes in a row and now it's not recoverable(that I can tell)
Click to expand...
Click to collapse
yes
but all my backup and copy will not help ?
muezae said:
yes
but all my backup and copy will not help ?
Click to expand...
Click to collapse
no .. the wrong kernel totally scrambled the partition ...no idea why
that's all i can make of it
muezae said:
yes
but all my backup and copy will not help ?
Click to expand...
Click to collapse
No they will not help you at all.
As nnk71 said " you have corrupted your mmcblk0p6 [mfg] partition. Has of yet, there is no way of restoring your phone to a usable condition.
clsA said:
no .. the wrong kernel totally scrambled the partition ...no idea why
that's all i can make of it
Click to expand...
Click to collapse
ok so just delete and reststore partition from backup?
muezae said:
ok so just delete and reststore partition from backup?
Click to expand...
Click to collapse
you don't seem to be getting it ...your phone is Dead
take it to a service center and tell them you got up this morning and it was like that ...play dumb and don't admit to doing anything
bored_stupid said:
No they will not help you at all.
As nnk71 said " you have corrupted your mmcblk0p6 [mfg] partition. Has of yet, there is no way of restoring your phone to a usable condition.
Click to expand...
Click to collapse
even when i got the original file named mmcblk0p6 ?
muezae said:
even when i got the original file named mmcblk0p6 ?
Click to expand...
Click to collapse
try restoring it and see .. you have nothing to loose
Related
Hi all,
First, i would like to apologize for my poor english.
Then, i have some problems with my HTC M7.
Yesterday, when i woke up, my phone was shut down. I thought that i had no battery anymore. (i had less than 10% when i went to bed so, it's possible).
Well, plug my phone in the charger, and wait... and, when he booted, i could not use my phone as usually: no PIN code, no ability to make phone call... After a few minutes, i saw that the IMEI zone was empty.
I was not worrying, and though that a simple cache cleearing could help me... Well, it was not...
Now, i'm not able to use my phone AT ALL.
He's rooted, S-OFF, and i tried to install 3 or 4 different roms but same problem.
The ROM install has some difficulties to be finished: in fact, on each rom i tried to install, i have now the same problem;
-> No IMEI
-> When i want to compose a phone number, the dialer does not appear
-> A message "com.htc.htcdialer isn't responding" appears every minute...
I tried to install another dialer, same problem...
I'm really lost.
hope that somebody could help me?
Regards,
Cyril
PS: For information, after the incident, my phone was not rooted anymore and was S-ON, i don't know if it was already the case before the incident...
UPDATE: Finally, i succeed to install a rom.
Everything works fine now, but still no imei present...
This is a firmware problem. It seems your firmware has corrupted.Best way is download a RUU for ur phone and just flash it.K ur s-on>can u get me a getvar all.
access ur bootloader select fastboot and then type " fastboot getvar all " without quotes.
Slim Shady said:
This is a firmware problem. It seems your firmware has corrupted.Best way is download a RUU for ur phone and just flash it.K ur s-on>can u get me a getvar all.
access ur bootloader select fastboot and then type " fastboot getvar all " without quotes.
Click to expand...
Click to collapse
Hi,
I've just started to work, but i will send you these informations as soon as possible.
Thanks a lot.
Slim Shady said:
This is a firmware problem. It seems your firmware has corrupted.Best way is download a RUU for ur phone and just flash it.K ur s-on>can u get me a getvar all.
access ur bootloader select fastboot and then type " fastboot getvar all " without quotes.
Click to expand...
Click to collapse
Re Slim Shady,
Here are the results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXX
(bootloader) imei: XXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 3828mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
I'm not sure about what to do.
May i have to switch on s-on? Or relock the bootloader?
I don't really know how to install a new firmware...
an idea?
Leodagan said:
Re Slim Shady,
Here are the results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 3828mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
I'm not sure about what to do.
May i have to switch on s-on? Or relock the bootloader?
I don't really know how to install a new firmware...
Click to expand...
Click to collapse
first please edit ur post and remove the imei and serial no from the post.Regarding ur problem download and flash this RUU http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Start the ruu and follow instructions like any windows application.If u have any questions feel free to ask .
Slim Shady said:
first please edit ur post and remove the imei and serial no from the post.Regarding ur problem download and flash this RUU http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Start the ruu and follow instructions like any windows application.If u have any questions feel free to ask .
Click to expand...
Click to collapse
just a quick note, he's s-off, personally I would go with a 1.xx ruu (except 1.20.xxx.x)
Slim Shady said:
first please edit ur post and remove the imei and serial no from the post.Regarding ur problem download and flash this RUU http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Start the ruu and follow instructions like any windows application.If u have any questions feel free to ask .
Click to expand...
Click to collapse
Done for IMEI and Serial NO, thx.
I've started to download it.
nkk71 said:
just a quick note, he's s-off, personally I would go with a 1.xx ruu (except 1.20.xxx.x)
Click to expand...
Click to collapse
Ok, so have i to switch on s-on?
Also, have i stay on unlocked mode?
Thanks guys, really.
Guys,
I tried to install the RUU but it failed:
Update from 3.62.1700.1 to 4.19.401.9, i click on next, then next, then a message (in french so i translate to you):
The update tool cannot update the android phone,
Please obtain the right update tool and try again.
Then, i can only click on ReadMe or Recovery, but nothing relevant after that.
Leodagan said:
Ok, so have i to switch on s-on?
Click to expand...
Click to collapse
Nooooo, do not go s-on!!
nkk71 said:
Nooooo, do not go s-on!!
Click to expand...
Click to collapse
Ok, i haven't done that, thanks ^^
So, now i'm stucked, i don't know what to do. Try another ruu?
I'm actually downloading RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe, is it ok?
Well, it's not ok, with this rom too i can't update my phone...
Maybe should i have to find a 3.62 RUU in order to update?
Leodagan said:
Well, it's not ok, with this rom too i can't update my phone...
Maybe should i have to find a 3.62 RUU in order to update?
Click to expand...
Click to collapse
What do you mean, can't update... you mean the ruu isn't working?
if so, then get this one: ruu_m7ul_1.28.401.7.zip
AFH mirror: http://www.androidfilehost.com/?fid=23329332407584993
then (after making sure MD5 is correct), rename the file to ruu.zip, and:
In bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
fastboot reboot-bootloader
there is no need to relock bootloader or anything else with S-OFF (and stay S-OFF, don't even think about S-On!!)
if you want to see what kind of output to expect, check my guide http://forum.xda-developers.com/showthread.php?p=47794257&postcount=8 (post 8) which has a some visual feedback of what to expect. (disregard the guide, i'm just linking it for you to get an idea of what kind of output to expect)
Oh and you cannot do this on Win 8.1!!! http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2 FAQ#1
nkk71 said:
What do you mean, can't update... you mean the ruu isn't working?
Click to expand...
Click to collapse
Yep, same message than the other ruu:
Update from 3.62.1700.1 to 1.2*******, i click on next, then next, then a message :
The update tool cannot update the android phone,
Please obtain the right update tool and try again.
I'll try your last post, i let you know when finished.
Leodagan said:
Yep, same message than the other ruu:
Update from 3.62.1700.1 to 1.2*******, i click on next, then next, then a message :
The update tool cannot update the android phone,
Please obtain the right update tool and try again.
I'll try your last post, i let you know when finished.
Click to expand...
Click to collapse
HELL YES IT WORKS!!!
Thank you thank you !!
(well for the moment i'm in 4.1.2, i will wait a moment before flashing a new recovery, a new rom and all the stuff :laugh::laugh::laugh
Leodagan said:
HELL YES IT WORKS!!!
Thank you thank you !!
(well for the moment i'm in 4.1.2, i will wait a moment before flashing a new recovery, a new rom and all the stuff :laugh::laugh::laugh
Click to expand...
Click to collapse
and IMEI, baseband etc are all working again?
Yep, all is functional again... thanks again !
Leodagan said:
Yep, all is functional again... thanks again !
Click to expand...
Click to collapse
:good: :good: my pleasure.
BTW, if you going for 4.4 ROMs, use TWRP: get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
2.7.0.4b: http://forum.xda-developers.com/showthread.php?t=2708134
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
PS: for future reference about s-off vs s-on, check here http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2 (under Not so FAQ #2)
if all is good now, can you also edit main thread title to include [SOLVED], thanks
edit the first post -> at the bottom of the edit window, click Go Advanced, and then you can edit main title
Done.
Thank you again, guys.
Hi all
My htc one (m7) doing restart all the time after i open the device
i change to viper rom and to revolution hd and the problem not solved
i tried to install rom without sense and the restart problem and errors solved but i didn't get Mobile ME.(maybe because my phone is S-on?)
could you help me please to solve this issue?
thanks
eliorbbb said:
Hi all
My htc one (m7) doing restart all the time after i open the device
i change to viper rom and to revolution hd and the problem not solved
i tried to install rom without sense and the restart problem and errors solved but i didn't get Mobile ME.(maybe because my phone is S-on?)
could you help me please to solve this issue?
thanks
Click to expand...
Click to collapse
with what recovery version did you flashed these roms?
alray said:
with what recovery version did you flashed these roms?
Click to expand...
Click to collapse
openrecovery-twrp-2.6.3.3-m7
eliorbbb said:
openrecovery-twrp-2.6.3.3-m7
Click to expand...
Click to collapse
can you still see your IMEI # in settings --> about --> phone identity ?
alray said:
can you still see your IMEI # in settings --> about --> phone identity ?
Click to expand...
Click to collapse
I cant open the phone...after that i try to open the device white screen with HTC logs appear
BTW
why you need the IMEI?
eliorbbb said:
I cant open the phone...after that i try to open the device white screen with HTC logs appear
BTW
why you need the IMEI?
Click to expand...
Click to collapse
I dont need to know your imei (dont post it) Just tell me if the IMEI is still there or it does it say <UNKNOW> ? And does your imei is present in your "fastboot getvar all" output? you might want to return back to stock and see if it works.
alray said:
I dont need to know your imei (dont post it) Just tell me if the IMEI is still there or it does it say <UNKNOW> ? And does your imei is present in your "fastboot getvar all" output? you might want to return back to stock and see if it works.
Click to expand...
Click to collapse
In fastboot getvar all i can see the imei but i in the OS i cant since the phone restarting before that i Manages to do anything.
if i will do S-off and install the same rom again that might help?
eliorbbb said:
In fastboot getvar all i can see the imei but i in the OS i cant since the phone restarting before that i Manages to do anything.
if i will do S-off and install the same rom again that might help?
Click to expand...
Click to collapse
i installed rom without sense and in the phone information the imei is unknown
what this is mean?
eliorbbb said:
i installed rom without sense and in the phone information the imei is unknown
what this is mean?
Click to expand...
Click to collapse
it's usually not a good sign, if it's not a hardware problem, possibly a ruu could fix it, and also check this: http://forum.xda-developers.com/showthread.php?t=2728428
nkk71 said:
it's usually not a good sign, if it's not a hardware problem, possibly a ruu could fix it, and also check this: http://forum.xda-developers.com/showthread.php?t=2728428
Click to expand...
Click to collapse
In this guide he is Saying:
"check your OS version which is written in your bootloader"
in my bootloader the OS is empty whice ruu should i take?!
eliorbbb said:
In this guide he is Saying:
"check your OS version which is written in your bootloader"
in my bootloader the OS is empty whice ruu should i take?!
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (excluding IMEI and s/n)
nkk71 said:
can you post a "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
c:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx-xxxx02
(bootloader) imei: XXX-XXX 34345
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4327mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
eliorbbb said:
c:\fastboot>fastboot getvar all
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
Click to expand...
Click to collapse
hmm, S-ON+hboot 1.57+MID+CID would indicate you are already on a 5.xx.1540.x version
to be honest, i never understood what the other guy did for it to work out for him
the latest ruu for you is (which will not work since it's a lower version): http://androidruu.com/getdownload.p...8_10.38r.1157.04L_release_353887_signed_3.exe
or if you have a functioning ROM right now, you may want to try and S-Off, then you can downgrade.
.
nkk71 said:
hmm, S-ON+hboot 1.57+MID+CID would indicate you are already on a 5.xx.1540.x version
to be honest, i never understood what the other guy did for it to work out for him
the latest ruu for you is (which will not work since it's a lower version): http://androidruu.com/getdownload.p...8_10.38r.1157.04L_release_353887_signed_3.exe
or if you have a functioning ROM right now, you may want to try and S-Off, then you can downgrade.
.
Click to expand...
Click to collapse
i didnt understand you recomend to do S-off and then downgrade to the latest ruu for me?
eliorbbb said:
i didnt understand you recomend to do S-off and then downgrade to the latest ruu for me?
Click to expand...
Click to collapse
you can't downgrade without S-OFF. so even if you try running that RUU it will fail
i'm saying that if you can get S-Off, then you should try, because that would allow you to use a downgrade ruu... i don't know what "triggered" the other guy's phone to come back to life (whether locking/unlocking bootloader did the trick, or something else... his solution is somewhat vague to me)
nkk71 said:
you can't downgrade without S-OFF. so even if you try running that RUU it will fail
i'm saying that if you can get S-Off, then you should try, because that would allow you to use a downgrade ruu... i don't know what "triggered" the other guy's phone to come back to life (whether locking/unlocking bootloader did the trick, or something else... his solution is somewhat vague to me)
Click to expand...
Click to collapse
format data inside TWRP fixed his problem mate, then I had him flash boot.img and then install the rom, if you mean the guy we were both helping out the other day, I figured everything was a bit of a mess after all the things he had tried flashing.
Seanie280672 said:
format data inside TWRP fixed his problem mate, then I had him flash boot.img and then install the rom, if you mean the guy we were both helping out the other day, I figured everything was a bit of a mess after all the things he had tried flashing.
Click to expand...
Click to collapse
can you please explain(guide or something) how can i do that from my current situation please?
eliorbbb said:
can you please explain(guide or something) how can i do that from my current situation please?
Click to expand...
Click to collapse
you already tried it in your other thread, its was done inside TWRP recovery, select wipe then format data, it will leave your phone completely empty, you then have to push a rom to the sdcard to flash.
Seanie280672 said:
you already tried it in your other thread, its was done inside TWRP recovery, select wipe then format data, it will leave your phone completely empty, you then have to push a rom to the sdcard to flash.
Click to expand...
Click to collapse
and since this didn't help i guess that i now have to send him to repair?
Hey guys, i never really need anyones help but this is annoying me now. My problem is that i have converted my HTC One to the google edition firmware and all was going great. Earlier today i wanted to try the latest MIUI Rom so i downloaded it and flashed it. Everything went smoothly until it came to reboot (i totally wiped phone before i installed MIUI) and now it wont turn on or charge and show only signs of life in the form of fastboot which i can use getvar all to pull my system info. Some fields are blank which arent meant to be. I cannot flash anything as screen wont turn on or even vibrate. Kind of at a loss now and any help will be appreciated.
Noel
noel8211 said:
Hey guys, i never really need anyones help but this is annoying me now. My problem is that i have converted my HTC One to the google edition firmware and all was going great. Earlier today i wanted to try the latest MIUI Rom so i downloaded it and flashed it. Everything went smoothly until it came to reboot (i totally wiped phone before i installed MIUI) and now it wont turn on or charge and show only signs of life in the form of fastboot which i can use getvar all to pull my system info. Some fields are blank which arent meant to be. I cannot flash anything as screen wont turn on or even vibrate. Kind of at a loss now and any help will be appreciated.
Noel
Click to expand...
Click to collapse
not positive but the MIUI rom may require a special version custom recovery. did you check that you have the correct recovery before flashing ?
clsA said:
not positive but the MIUI rom may require a special version custom recovery. did you check that you have the correct recovery before flashing ?
Click to expand...
Click to collapse
hey thanks for replying. i used the latest 2.8.0.0 twrp recovery. my getvar all is:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3662mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
C:\Program Files (x86)\Minimal ADB and Fastboot>
im not sure if thats all ok or not
noel8211 said:
hey thanks for replying. i used the latest 2.8.0.0 twrp recovery. my getvar all is:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3662mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
C:\Program Files (x86)\Minimal ADB and Fastboot>
im not sure if thats all ok or not
Click to expand...
Click to collapse
Is that your real MID and CID?
You should correct those and RUU back to stock and start over. Your phone is having an identity crisis [emoji2]
clsA said:
Is that your real MID and CID?
You should correct those and RUU back to stock and start over. Your phone is having an identity crisis [emoji2]
Click to expand...
Click to collapse
lol yeah thats what it said after i flashed MIUI. what would be the best way to sort them out?
Theirs a MID change tool you use in Twrp
And changing the CID is a simple fastboot command
clsA said:
Theirs a MID change tool you use in Twrp
And changing the CID is a simple fastboot command
Click to expand...
Click to collapse
ah CID will be easy but MID wont as i cant even get to recovery or anything. not even bootloader. I didnt realise MIUI would screw up this bad, or could it be something to do with the 'latest' twrp being too new?
noel8211 said:
ah CID will be easy but MID wont as i cant even get to recovery or anything. not even bootloader. I didnt realise MIUI would screw up this bad, or could it be something to do with the 'latest' twrp being too new?
Click to expand...
Click to collapse
Flash TWRP 2.6.3.3 it's the most reliable version
clsA said:
Flash TWRP 2.6.3.3 it's the most reliable version
Click to expand...
Click to collapse
i have been trying that for a while now but keep getting remote: not allowed errors
Is your bootloader relocked?
clsA said:
Is your bootloader relocked?
Click to expand...
Click to collapse
i didnt relock it after i flashed. can it relock itself?
noel8211 said:
i didnt relock it after i flashed. can it relock itself?
Click to expand...
Click to collapse
No and don't relock it. Their are people stuck and can't unlock coming from GPE
clsA said:
No and don't relock it. Their are people stuck and can't unlock coming from GPE
Click to expand...
Click to collapse
ah thats good then. i never bothered to re-lock it when i flashed the firmware as didnt see the point. all the guides i can find are to change things through adb which doesnt work as comupet dont pick it up. when however i do a fastboot devices, my device instaed of numbers , is ???????????????. im sure thats not normal.
by the way, thanks for helping me
noel8211 said:
ah thats good then. i never bothered to re-lock it when i flashed the firmware as didnt see the point. all the guides i can find are to change things through adb which doesnt work as comupet dont pick it up. when however i do a fastboot devices, my device instaed of numbers , is ???????????????. im sure thats not normal.
by the way, thanks for helping me
Click to expand...
Click to collapse
Well adb is only going to work in recovery so ignore that
So you flashed firmware ? Which one?
Did you try and get in stock recovery and do a factory reset
clsA said:
Well adb is only going to work in recovery so ignore that
So you flashed firmware ? Which one?
Did you try and get in stock recovery and do a factory reset
Click to expand...
Click to collapse
I flashed the latest MIUI from MIUIandroid and then just rebooted afterwards. the phone seems dead but i can get fastboot to partially work as my computer recognises it
noel8211 said:
I flashed the latest MIUI from MIUIandroid and then just rebooted afterwards. the phone seems dead but i can get fastboot to partially work as my computer recognises it
Click to expand...
Click to collapse
I'm going to need my PC to get you the links you need to try and get back up and running. I'll be back home in an hour or so
clsA said:
I'm going to need my PC to get you the links you need to try and get back up and running. I'll be back home in an hour or so
Click to expand...
Click to collapse
Thank you very much, i really appreciate it
noel8211 said:
Thank you very much, i really appreciate it
Click to expand...
Click to collapse
Ok I'm back
First lets try and get a working recovery on your phone
download and flash this >> twrp-recovery-2.7-m7-nobcb.img
fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img
fastboot erase cache
fastboot reboot-bootloader
Now enter recovery
We are following nkk71 guide here if you want to jump ahead
http://forum.xda-developers.com/showthread.php?t=2739126
also could you give me the name of the MIUI you downloaded
clsA said:
Ok I'm back
First lets try and get a working recovery on your phone
also could you give me the name of the MIUI you downloaded
Click to expand...
Click to collapse
i think he has a lot more to fix than just the misc partition, not sure if this is fixable, i believe the updater-script wrote to hboot partition, and he's unlikely to even be able to "fastboot oem rebootRUU" to fix that,
if by some chance he's able to get to recovery, then he'd have to manually dd all the messed up partitions.
OP, can you upload the updater-script (it's in <nameofrom>zip /META-INF/com/google/android) to pastebin (or zip it and attach it here).
nkk71 said:
i think he has a lot more to fix than just the misc partition, not sure if this is fixable, i believe the updater-script wrote to hboot partition, and he's unlikely to even be able to "fastboot oem rebootRUU" to fix that,
if by some chance he's able to get to recovery, then he'd have to manually dd all the messed up partitions.
OP, can you upload the updater-script (it's in <nameofrom>zip /META-INF/com/google/android) to pastebin (or zip it and attach it here).
Click to expand...
Click to collapse
yeah this could get complicated, I don't know the actual MIUI he used and he mentioned flashing a firmware, I hope he just meant flash a rom.
I need really bad help with my phone, it's s-on i cant install any roms and i cant restore from a backup anymore, i have twrp installed as of now, I have tried every method for getting s - off in the past but that was with a custom crappy rom so it didnt work.
Att htc one m7 32gb please add me on skype, i need direct help and i cannot just waiting on somebody to reply to this thread, please i seek desperate help my skype name is rtorr724, please i need someone that knows a lot about android and could help me fix this problem.
i can give you any other info you may need on skype to help me fix my problem. thanks.
rtorr724 said:
I need really bad help with my phone, it's s-on i cant install any roms and i cant restore from a backup anymore, i have twrp installed as of now, I have tried every method for getting s - off in the past but that was with a custom crappy rom so it didnt work.
Att htc one m7 32gb please add me on skype, i need direct help and i cannot just waiting on somebody to reply to this thread, please i seek desperate help my skype name is rtorr724, please i need someone that knows a lot about android and could help me fix this problem.
i can give you any other info you may need on skype to help me fix my problem. thanks.
Click to expand...
Click to collapse
Reboot into fastboot mode.
Hold Power + Volume Down until, select Fastboot.
Run this command:
Code:
fastboot getvar all
We can then get the CID/Model and Fastboot version so you can use an RUU to recover the device.
DennisBold said:
Reboot into fastboot mode.
Hold Power + Volume Down until, select Fastboot.
Run this command:
Code:
fastboot getvar all
We can then get the CID/Model and Fastboot version so you can use an RUU to recover the device.
Click to expand...
Click to collapse
I did not know what to look for so i just copy nd pasted all of it
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 000000000
(bootloader) imei: 0000000000
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3959mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
rtorr724 said:
I did not know what to look for so i just copy nd pasted all of it
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3959mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
you can use that RUU to restore your phone: http://www.htc1guru.com/2014/03/att-ruu/
with s-on you must have a locked or re-locked bootloader use it.
and btw, remove imei and serialno from your above post.
alray said:
you can use that RUU to restore your phone:
with s-on you must have a locked or re-locked bootloader use it.
and btw, remove imei and serialno from your above post.
Click to expand...
Click to collapse
I install it through sideload correct?
also what could someone do with my imei and serialno?
rtorr724 said:
I install it through sideload correct?
Click to expand...
Click to collapse
No its an .exe file. You must launch that executable using a windows pc with the phone connected to it and booted in bootloader mode.
also what could someone do with my imei and serialno?
Click to expand...
Click to collapse
Someone could use it to clone your phone.
alray said:
No its an .exe file. You must launch that executable using a windows pc with the phone connected to it and booted in bootloader mode.
Someone could use it to clone your phone.
Click to expand...
Click to collapse
Well thank you for telling me about it I wouldn't have wanted that to happen.
The download is pretty slow so when its done ill post back here with my results
rtorr724 said:
Well thank you for telling me about it I wouldn't have wanted that to happen.
The download is pretty slow so when its done ill post back here with my results
Click to expand...
Click to collapse
ok, also make sure to check that the MD5 value of your downloaded file will match the value given on the website.
should be: 5f121d72b8fa3f6f1704588467752605
you can use winMd5 program to check the value.
alray said:
ok, also make sure to check that the MD5 value of your downloaded file will match the value given on the website.
Click to expand...
Click to collapse
The program failed to work and got error 155, the md5 value matched and my phone just went to a black htc screen.
Like i said before if someone could add me on skype so it would be easier to help that would be great
rtorr724 <- skype
rtorr724 said:
The program failed to work and got error 155, the md5 value matched and my phone just went to a black htc screen.
Like i said before if someone could add me on skype so it would be easier to help that would be great
rtorr724 <- skype
Click to expand...
Click to collapse
is your bootloader locked or unlocked?
alray said:
is your bootloader locked or unlocked?
Click to expand...
Click to collapse
unlocked
rtorr724 said:
unlocked
Click to expand...
Click to collapse
so go back and read post #4 again...
alray said:
so go back and read post #4 again...
Click to expand...
Click to collapse
._. im really stupid xD
so what do i do now?
rtorr724 said:
._. im really stupid xD
so what do i do now?
Click to expand...
Click to collapse
relock the bootloader and run the ruu....
to lock the bootloader:
Code:
fastboot oem lock
alray said:
relock the bootloader and run the ruu....
to lock the bootloader:
Code:
fastboot oem lock
Click to expand...
Click to collapse
Thanks so much! but how do i get unlocked again?
rtorr724 said:
Thanks so much! but how do i get unlocked again?
Click to expand...
Click to collapse
you can unlock again the same way you did the first time, using the unlock_code.bin you have received from htcdev.com. if the unlock code you already have doesnt work anymore, request a new unlock code by submitting you identifier token again.
alray said:
you can unlock again the same way you did the first time, using the unlock_code.bin you have received from htcdev.com. if the unlock code you already have doesnt work anymore, request a new unlock code by submitting you identifier token again.
Click to expand...
Click to collapse
I have one last problem, i got s-off and everything and now im trying to get cm12 5.0 and everytime i try to install it, it returns with the error
E:Error in /data/media/0/cm.zip
(Status 0)
Installation aborted.
And above that it says a bunch of stuff of failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system:no such file or directory
and then it says the same thing for the unmount
rtorr724 said:
I have one last problem, i got s-off and everything and now im trying to get cm12 5.0 and everytime i try to install it, it returns with the error
E:Error in /data/media/0/cm.zip
(Status 0)
Installation aborted.
And above that it says a bunch of stuff of failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system:no such file or directory
and then it says the same thing for the unmount
Click to expand...
Click to collapse
Which recovery are you using?
DennisBold said:
Which recovery are you using?
Click to expand...
Click to collapse
TWRP and CWM i get an error for both, i think its because when I wipe data/factory reset it gets rid of systtem
rtorr724 said:
TWRP and CWM i get an error for both, i think its because when I wipe data/factory reset it gets rid of systtem
Click to expand...
Click to collapse
I was more or less asking for your preference.
Your phone has partitions of memory which hold data, and when you update or install a custom ROM, the recovery utility mounts the partitions so they can be accessed to write and read data. Android does this every-time you turn on your phone. Formatting a partition doesn't delete it, it simply removes everything. CyanogenMod incorporated "block by name" mounting. Which basically makes it easier to mount partitions without being device specific.
Try this version of TWRP: http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.7.1.1-m7.img
Anything above 2.7.1.1 should work, anything below will not.
For ClockWorkMod anything above 6.0.4.8 will work.
Hi I'm going crazy right now, I really need some help, here's the history:
Today I bought a htc one m7 from a girl and when she was restoring it I saw that it was with a custom recovery, I didnt care about it becouse anyway I was going to install it some day. After that I went home and started searching some lollipop rom.
Well I downloaded it and copied it to the internal storage, I was ready to flash so I did it.
After flashing the rom it begins to bootloop, so I thougt "ok, it maybe need just a wipe" so I wiped it, as it didnt solved the problem I wiped again but this time with all boxes checked, after that y realized that I was wiping EVERYTHING (It happened before in a nexus 5 and 4).
Ok, I thought f**k it, I'll push the files with adb and problem solved, but when I conected the phone to the pc it has now driver problems, I cant get adb to work, neither fasboot, I installed and uninstalled al drivers I found on the internet, I really dont know what else to do.
If I conect the phone with the pc in fastboot mode in devices manager it says that the usb device ist recognized and something like that there is an error with the number.
And when I conect it in recovery mode it says "one" with the exclamation symbol, I red a lot of posts about how to solve it, but when I force install the drivers nothing happens.
Help me please, I dont know what more to do. And sorry about my english
If you need some information/pictures, just ask for it
Im new with this phone and I have no idea what to do
nachoy9 said:
Hi I'm going crazy right now, I really need some help, here's the history:
Today I bought a htc one m7 from a girl and when she was restoring it I saw that it was with a custom recovery, I didnt care about it becouse anyway I was going to install it some day. After that I went home and started searching some lollipop rom.
Well I downloaded it and copied it to the internal storage, I was ready to flash so I did it.
After flashing the rom it begins to bootloop, so I thougt "ok, it maybe need just a wipe" so I wiped it, as it didnt solved the problem I wiped again but this time with all boxes checked, after that y realized that I was wiping EVERYTHING (It happened before in a nexus 5 and 4).
Ok, I thought f**k it, I'll push the files with adb and problem solved, but when I conected the phone to the pc it has now driver problems, I cant get adb to work, neither fasboot, I installed and uninstalled al drivers I found on the internet, I really dont know what else to do.
If I conect the phone with the pc in fastboot mode in devices manager it says that the usb device ist recognized and something like that there is an error with the number.
And when I conect it in recovery mode it says "one" with the exclamation symbol, I red a lot of posts about how to solve it, but when I force install the drivers nothing happens.
Help me please, I dont know what more to do. And sorry about my english
If you need some information/pictures, just ask for it
Im new with this phone and I have no idea what to do
Click to expand...
Click to collapse
go here and read post 2 FAQ 2
http://forum.xda-developers.com/showthread.php?t=2541082
That should get your drivers working
post your fastboot getvar all (minus your serial no and IMEI) and I can try and help you find the correct files for your phone
clsA said:
go here and read post 2 FAQ 2
http://forum.xda-developers.com/showthread.php?t=2541082
That should get your drivers working
post your fastboot getvar all (minus your serial no and IMEI) and I can try and help you find the correct files for your phone
Click to expand...
Click to collapse
Wow THANKS A LOT, I was doing something like that when installing drivers but not that, now I have adb working.
I dont want to do anything more wrong, can you tell me wich file to flash over TWR to get it working? my fastboot shows:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-OFF RH
CID-CWS_001
HBOOT-1.44.0000
RADIO-A1.14.3250.13
OpenDPS-v26.120.274.0202
eMMC-boot
May 3 2013,19:16:59:-1
I cant post the getvar becouse I have windows 8.1 and as I saw, fastboot comands doesnt works with windows 8.1 if I have HBOOT-1.44
clsA said:
go here and read post 2 FAQ 2
http://forum.xda-developers.com/showthread.php?t=2541082
That should get your drivers working
post your fastboot getvar all (minus your serial no and IMEI) and I can try and help you find the correct files for your phone
Click to expand...
Click to collapse
I used my grandmas PC
C:\Users\Miriam\Desktop\androidññ\platform-tools>fastboot devices
HT36KW908410 fastboot
C:\Users\Miriam\Desktop\androidññ\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ------
(bootloader) imei: ------
(bootloader) meid: ------
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3868mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.068s
nachoy9 said:
I used my grandmas PC
C:\Users\Miriam\Desktop\androidññ\platform-tools>fastboot devices
HT36KW908410 fastboot
C:\Users\Miriam\Desktop\androidññ\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ------
(bootloader) imei: ------
(bootloader) meid: ------
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3868mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.068s
Click to expand...
Click to collapse
I would use this first
http://dl3.htc.com/application/RUU_...4_10.33E.1718.01L_release_404528_signed_2.exe
clsA said:
I would use this first
http://dl3.htc.com/application/RUU_...4_10.33E.1718.01L_release_404528_signed_2.exe
Click to expand...
Click to collapse
how does it work? I have to put the phone on fastboot mode or in a custom recovery for adb comands?
nachoy9 said:
how does it work? I have to put the phone on fastboot mode or in a custom recovery for adb comands?
Click to expand...
Click to collapse
just leave the phone plugged into the PC and in Fastboot USB mode on the bootloader screen
then run the RUU
clsA said:
just leave the phone plugged into the PC and in Fastboot USB mode on the bootloader screen
then run the RUU
Click to expand...
Click to collapse
Just made it, thanks a lot, do you know how to install updates now? becouse it doesnt find any OTA
nachoy9 said:
Just made it, thanks a lot, do you know how to install updates now? becouse it doesnt find any OTA
Click to expand...
Click to collapse
are you on the AT&T network ?
clsA said:
are you on the AT&T network ?
Click to expand...
Click to collapse
No, Im from Uruguay (South America)
nachoy9 said:
No, Im from Uruguay (South America)
Click to expand...
Click to collapse
I recommend you convert your phone to Developer edition
I posted instructions here for another guy >> http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11
clsA said:
I recommend you convert your phone to Developer edition
I posted instructions here for another guy >> http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11
Click to expand...
Click to collapse
Ill do it, THANKS A LOT
clsA said:
I recommend you convert your phone to Developer edition
I posted instructions here for another guy >> http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11
Click to expand...
Click to collapse
Sorry Im bothering you again, but I tryed to install that RUU and it says that there is an error with the image version or something like that
nachoy9 said:
Sorry Im bothering you again, but I tryed to install that RUU and it says that there is an error with the image version or something like that
Click to expand...
Click to collapse
Did you change your CID?
clsA said:
Did you change your CID?
Click to expand...
Click to collapse
Yes
nachoy9 said:
Yes
Click to expand...
Click to collapse
your on 3.x 502 AT&T
try the 4.X.1540 DE RUU here >> http://www.androidruu.com/getdownlo...8_10.38r.1157.04L_release_353887_signed_3.exe
If it gives you an error flash this firmware then the RUU
https://www.androidfilehost.com/?fid=95887005526790121
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
clsA said:
your on 3.x 502 AT&T
try the 4.X.1540 DE RUU here >> http://www.androidruu.com/getdownlo...8_10.38r.1157.04L_release_353887_signed_3.exe
If it gives you an error flash this firmware then the RUU
https://www.androidfilehost.com/?fid=95887005526790121
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
Click to expand...
Click to collapse
Ok, ill try and tomorrow I tell you if it worked, thanks