Related
hello all,
my friend wanted me a favour for making his ONE working but i couldn't do it so any advice will be appreciated...here is the situation...
while he's charging, phone suddenly stopped and now it is not working...i open command line, but couldn't find the device anymore. he said he's sure that he checked "usb debugging" and "unknown sources". also it's not charging anymore.
i tried downgrade hboot then flash RUU.exe but no comment was working...
what should i do? PLEASE HELP ME
ayk33 said:
hello all,
my friend wanted me a favour for making his ONE working but i couldn't do it so any advice will be appreciated...here is the situation...
while he's charging, phone suddenly stopped and now it is not working...i open command line, but couldn't find the device anymore. he said he's sure that he checked "usb debugging" and "unknown sources". also it's not charging anymore.
i tried downgrade hboot then flash RUU.exe but no comment was working...
what should i do? PLEASE HELP ME
Click to expand...
Click to collapse
let me get this right. the phone does NOT power on and does not charge ?
baadnewz said:
let me get this right. the phone does NOT power on and does not charge ?
Click to expand...
Click to collapse
it does stuck on bootloader only and does not charge...whatever i do, it turns again to bootloader. I tried many things but since device could not be found, the commands aren't accepted. all i can do is RUU.exe but it gives me error 155 (which means the RUU is not the right RUU) and i couldn't find the right RUU.exe...
This is my friend's ONE and as he said, he last flashed your rom;
on bootloader screen, it says;
*** TAMPERED ***
*** RELOCKED ***
M7_U UNKNOWN SHIP S-OFF RH
CID-11111111
HBOOT-1.56.0000
RADIO-4A.22.3263.14
OpenDSP-v32.120.274.0909
OS-4.06.1540.2
eMMC-boot 2048MB
etc
etc
ayk33 said:
it does stuck on bootloader only and does not charge...whatever i do, it turns again to bootloader. I tried many things but since device could not be found, the commands aren't accepted. all i can do is RUU.exe but it gives me error 155 (which means the RUU is not the right RUU) and i couldn't find the right RUU.exe...
This is my friend's ONE and as he said, he last flashed your rom;
on bootloader screen, it says;
*** TAMPERED ***
*** RELOCKED ***
M7_U UNKNOWN SHIP S-OFF RH
CID-11111111
HBOOT-1.56.0000
RADIO-4A.22.3263.14
OpenDSP-v32.120.274.0909
OS-4.06.1540.2
eMMC-boot 2048MB
etc
etc
Click to expand...
Click to collapse
It's giving you error 155 because hboot is 1.56; RUU.EXE downgrade will fail with hboot 1.55+
post a "fastboot getvar all" (except IMEI and s/n)
and WTH is "M7_U UNKNOWN SHIP S-OFF RH", were you messing around with an ENG hboot?
nkk71 said:
It's giving you error 155 because hboot is 1.56; RUU.EXE downgrade will fail with hboot 1.55+
post a "fastboot getvar all" (except IMEI and s/n)
and WTH is "M7_U UNKNOWN SHIP S-OFF RH", were you messing around with an ENG hboot?
Click to expand...
Click to collapse
all getvar is this;
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.22.3263.14
version-cpld: None
version-microp: None
version-main: 4.06.1540.2
version-misc: UNKNOWN SHIP S-OFF
serialno: ü;üåÏ*úëR_Ó´%Zè
imei: xxxx
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: 0←♦ê►ê4ç8çõ*☼♀‼áDç
cidnum: 11111111
battery-status: good
battery-voltage: 4279mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bee46337
hbootpreupdate: 11
gencheckpt: 0
beside these, believe me i have no idea what he has flashed so far but i've always told him to use IC roms, probably he did what was written there
and since i can't enter any command, i cannot change hboot to 1.44 because of unknown device problem
ayk33 said:
all getvar is this;
imei: XXX
Click to expand...
Click to collapse
Hide this
ayk33 said:
all getvar is this;
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.22.3263.14
version-cpld: None
version-microp: None
version-main: 4.06.1540.2
version-misc: UNKNOWN SHIP S-OFF
serialno: ü;üåÏ*úëR_Ó´%Zè
imei: 35xxxxxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: 0←♦ê►ê4ç8çõ*☼♀‼áDç
cidnum: 11111111
battery-status: good
battery-voltage: 4279mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bee46337
hbootpreupdate: 11
gencheckpt: 0
beside these, believe me i have no idea what he has flashed so far but i've always told him to use IC roms, probably he did what was written there
and since i can't enter any command, i cannot change hboot to 1.44 because of unknown device problem
Click to expand...
Click to collapse
^^^^ WOW, never seen a system that messed up before!!
can you post a screenshot of bootloader,
but you definitely have one or more low-level partitions really messed up, I don't know if this is fixable.
I've already told my friend to say goodbye but i wanna surprise him i will post screenshot as soon as i can...
Thanks one more time
Sent from my HTC One using xda app-developers app
This is the photo of the trouble
Sent from my HTC One using xda app-developers app
ayk33 said:
This is the photo of the trouble
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
well i'm off for tonight, but i do have to say WOW.... sorry if that comes across in a bad way, not trying to be an ass or anything.
I'll give it some thought, but so far, looks like some really low level partitions are f**ed, including:
mmcblk0p3, mmcblk0p6, maybe mmcblk0p7, and mmcblk0p19
(not to mention hboot)
eventually, you're going to have to end up using an ruu.zip in "fastboot oem rebootRUU" mode, but not sure how much this is going to fix your low-level partitions..... it's amazing you still have an IMEI.
nkk71 said:
well i'm off for tonight, but i do have to say WOW.... sorry if that comes across in a bad way, not trying to be an ass or anything.
I'll give it some thought, but so far, looks like some really low level partitions are f**ed, including:
mmcblk0p3, mmcblk0p6, maybe mmcblk0p7, and mmcblk0p19
(not to mention hboot)
eventually, you're going to have to end up using an ruu.zip in "fastboot oem rebootRUU" mode, but not sure how much this is going to fix your low-level partitions..... it's amazing you still have an IMEI.
Click to expand...
Click to collapse
Thanks anyway...waiting for an answer
Sent from my HTC One using xda app-developers app
cmdline overflow usually happens when your kernel cmdline is longer that it must be. can you try to flash another boot.img. preferably a stock one. or downgrade hboot to 1.44
baadnewz said:
cmdline overflow usually happens when your kernel cmdline is longer that it must be. can you try to flash another boot.img. preferably a stock one. or downgrade hboot to 1.44
Click to expand...
Click to collapse
Since i have "unknown device" issue, i can't flash anything i guess he has dead ONE
Sent from my HTC One using xda app-developers app
ayk33 said:
Since i have "unknown device" issue, i can't flash anything i guess he has dead ONE
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Well it's probably going to be a futile exercise, but WTH, download this:
http://www.htc1guru.com/dld/ruu-zip...0-01_release_311663_signed_2_4_decrypted-zip/
rename it to ruu.zip and put it in your adb/fastboot folder, go to bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
again
fastboot flash zip ruu.zip
fastboot reboot-bootloader
copy/paste output here.
nkk71 said:
Well it's probably going to be a futile exercise, but WTH, download this:
http://www.htc1guru.com/dld/ruu-zip...0-01_release_311663_signed_2_4_decrypted-zip/
rename it to ruu.zip and put it in your adb/fastboot folder, go to bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
again
fastboot flash zip ruu.zip
fastboot reboot-bootloader
copy/paste output here.
Click to expand...
Click to collapse
aaaaand what i got is here;
C:\Users\Aykal\Desktop\fastboot>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1009472 KB)...
OKAY [ 42.950s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 43.375s
can it be sth related with cid? should i change it since model id fail
ayk33 said:
aaaaand what i got is here;
C:\Users\Aykal\Desktop\fastboot>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1009472 KB)...
OKAY [ 42.950s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 43.375s
can it be sth related with cid? should i change it since model id fail
Click to expand...
Click to collapse
It is not related to CID because your CID is 1111111 (SuperCID)
So you have to add your MID to the android-info.txt file...
And since your MID is:
Code:
0←♦ê►ê4ç8çõ*☼♀‼áDç
Just add exactly that to your android-info.txt and if you now have something new on your getvar all output.. just add the result you get related to "modeliid"
P.S.
android-info.txt is inside the RUU.zip file.... just extract it... add your MID with the same syntaxis like the other MIDs and repack everything..
LibertyMarine said:
It is not related to CID because your CID is 1111111 (SuperCID)
So you have to add your MID to the android-info.txt file...
And since your MID is:
Code:
0←♦ê►ê4ç8çõ*☼♀‼áDç
Just add exactly that to your android-info.txt and if you now have something new on your getvar all output.. just add the result you get related to "modeliid"
P.S.
android-info.txt is inside the RUU.zip file.... just extract it... add your MID with the same syntaxis like the other MIDs and repack everything..
Click to expand...
Click to collapse
BIG BIG THANK YOU well we eliminate step one, let's do the rest :fingers-crossed: new output;
C:\Users\Aykal\Desktop\fastboot>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1006864 KB)...
OKAY [ 43.471s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 43.752s
ayk33 said:
BIG BIG THANK YOU well we eliminate step one, let's do the rest :fingers-crossed: new output;
C:\Users\Aykal\Desktop\fastboot>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1006864 KB)...
OKAY [ 43.471s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 43.752s
Click to expand...
Click to collapse
Not really the way I would have done it, but can you check your inbox please.
nkk71 said:
Not really the way I would have done it, but can you check your inbox please.
Click to expand...
Click to collapse
I'm interested, how would you do it?
LibertyMarine said:
I'm interested, how would you do it?
Click to expand...
Click to collapse
Hi LibertyMarine
actually my bad,
* he has a locked bootloader
* and no custom recovery
we tried a bit earlier, but didnt get very far, maybe he'll come back later and we'll give it another shot.
I need a custom recovery on it, to be able to see a few things :cyclops::cyclops:
After the struggle of finding a way to revert my Vodafone Australia branded HTC One back to it's former, virgin glory..
I have finally locked the bootloader, set my CID back and got a stock ROM and recovery - thanks to Guru Stock Reset ROMs, which is the closest thing I could get to being stock as there are no available RUU's.
But the last and final hurdle is S-ON. My Googling tells me all it takes is this fastboot command: "fastboot oem writesecureflag 3"
But when I throw that in a command prompt, all I get is an error:
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 1.624s]
finished. total time: 1.625s
Could anyone please help? I have to return my diseased pink/purple-tinted, crappy camera issue!
Jikstah said:
After the struggle of finding a way to revert my Vodafone Australia branded HTC One back to it's former, virgin glory..
I have finally locked the bootloader, set my CID back and got a stock ROM and recovery - thanks to Guru Stock Reset ROMs, which is the closest thing I could get to being stock as there are no available RUU's.
But the last and final hurdle is S-ON. My Googling tells me all it takes is this fastboot command: "fastboot oem writesecureflag 3"
But when I throw that in a command prompt, all I get is an error:
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 1.624s]
finished. total time: 1.625s
Could anyone please help? I have to return my diseased pink/purple-tinted, crappy camera issue!
Click to expand...
Click to collapse
wow, brick alert!
you have a modded hboot in there, so you're obviously not as stock as you'd like to think. better you rethink your strategy, and/or check my guide http://forum.xda-developers.com/showthread.php?t=2541082
nkk71 said:
wow, brick alert!
you have a modded hboot in there, so you're obviously not as stock as you'd like to think. better you rethink your strategy, and/or check my guide http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Damn dude, how far am I from a brick? :S
and you are absolutely correct, I completely forgot about my hboot being modified at 1.55.
It's been awhile since I tampered around with my phone.
Is it then possible to downgrade my hboot to 1.44, with my current set-up? and continue to s-on?
I thank you immensely.
Jikstah said:
Damn dude, how far am I from a brick? :S
and you are absolutely correct, I completely forgot about my hboot being modified at 1.55.
It's been awhile since I tampered around with my phone.
Click to expand...
Click to collapse
Luckily the signature check kept you away from a brick, had you been able to S-On with a modded hboot, then you would have had a brick.
Jikstah said:
Is it then possible to downgrade my hboot to 1.44, with my current set-up? and continue to s-on?
Click to expand...
Click to collapse
I'm not sure what method you used to return to stock, but obviously hboot is not stock, and so could other things as well; I would recommend following my guide, especially if you intend on going S-On.
If you do want to follow my guide, post a "fastboot getvar all" (excluding IMEI and s/n), and I'll let you know which files you need.
nkk71 said:
I'm not sure what method you used to return to stock, but obviously hboot is not stock, and so could other things as well; I would recommend following my guide, especially if you intend on going S-On.
If you do want to follow my guide, post a "fastboot getvar all" (excluding IMEI and s/n), and I'll let you know which files you need.
Click to expand...
Click to collapse
I mean no offence in not wanting to follow your guide, it's great - especially for those less knowledgeable, and in need.
So here's my getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 3782mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.067s
Surely I'm close?! Thanks again.
Jikstah said:
I mean no offence in not wanting to follow your guide, it's great - especially for those less knowledgeable, and in need.
So here's my getvar:
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
Surely I'm close?! Thanks again.
Click to expand...
Click to collapse
no offense taken
but you have PN0714000 + VODAP021 and firmware 3.62.401.1 (.401. = WWE unbranded), so you need to get your firmware correct too; inline with the ROM you are now on.
and personally, I don't recommend going S-Off to S-On on hboot 1.55, sometimes it works fine, but sometimes it triggers "tamper detected" and the tampered is back (can't say when/if it will happen to you)
nkk71 said:
no offense taken
but you have PN0714000 + VODAP021 and firmware 3.62.401.1 (.401. = WWE unbranded), so you need to get your firmware correct too; inline with the ROM you are now on.
and personally, I don't recommend going S-Off to S-On on hboot 1.55, sometimes it works fine, but sometimes it triggers "tamper detected" and the tampered is back (can't say when/if it will happen to you)
Click to expand...
Click to collapse
Ugh, more complications.. back to the drawing board it is!
So looks like all I need is firmware and hboot?
But do you reckon, the repair center will pay any attention to these attributes? I've heard all they check is S-ON, tamper flags and unlocked bootloaders?
Jikstah said:
Ugh, more complications.. back to the drawing board it is!
So looks like all I need is firmware and hboot?
But do you reckon, the repair center will pay any attention to these attributes? I've heard all they check is S-ON, tamper flags and unlocked bootloaders?
Click to expand...
Click to collapse
hboot will be part of the firmware.zip,
and I don't know what they will check, but you may have a problem when it comes back -> if you're S-On, LOCKED bootloader with firmware not matching your MID and CID, then chances are high that HTCDev won't unlock your phone.
nkk71 said:
hboot will be part of the firmware.zip,
and I don't know what they will check, but you may have a problem when it comes back -> if you're S-On, LOCKED bootloader with firmware not matching your MID and CID, then chances are high that HTCDev won't unlock your phone.
Click to expand...
Click to collapse
Okay, well that simplifies things..
Now I just have to find a firmware.zip
You're pretty well-versed, I must thank you again for your foresight.
Jikstah said:
Okay, well that simplifies things..
Now I just have to find a firmware.zip
You're pretty well-versed, I must thank you again for your foresight.
Click to expand...
Click to collapse
I'm assuming you used Guru ROM 2.24.980.2 ? i made a quick search but came up empty on the firmware for that. you could pull it from the OTA file if you find it; within the OTA.ZIP is another firmware.zip <- that's signed original firmware
nkk71 said:
I'm assuming you used Guru ROM 2.24.980.2 ? i made a quick search but came up empty on the firmware for that. you could pull it from the OTA file if you find it; within the OTA.ZIP is another firmware.zip <- that's signed original firmware
Click to expand...
Click to collapse
Rejoice! For I have found the exact firmware for the ROM - http://forum.xda-developers.com/showpost.php?p=44452049&postcount=438
Google is truly a wonderful thing, and you Mr. nkk71.
Jikstah said:
Rejoice! For I have found the exact firmware for the ROM - http://forum.xda-developers.com/showpost.php?p=44452049&postcount=438
Google is truly a wonderful thing, and you Mr. nkk71.
Click to expand...
Click to collapse
Nice find :good: :good:
don't forget to flash it twice:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
and since firmware & ROM are 2.xx (hboot 1.54), going from S-Off to S-On should be safe
nkk71 said:
Nice find :good: :good:
don't forget to flash it twice:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
and since firmware & ROM are 2.xx (hboot 1.54), going from S-Off to S-On should be safe
Click to expand...
Click to collapse
Oh jeez, here we go. I put the firmware.zip into my sd card, pulled up a cmd, entered rebootRUU mode, and tried to flash firmware zip.
And...
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (28294 KB)...
OKAY [ 2.210s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 2.701s
What's wrong with my CID? I even changed it from VODAP021 to HTC__039 to see if it would run, still the same error.. :|
EDIT: Okay so I SuperCID'ed, it worked however my bootloader is still 1.55? wut.
Don't tell me I need an unlocked bootloader, I need an unlocked bootloader right? -_-
I believe you said HTCdev won't unlock it if I had a non-matching firmware to my CID/MID? ugh.
EDIT: NOPE, no luck either with an unlocked bootloader - same result.
Jikstah said:
Oh jeez, here we go. I put the firmware.zip into my sd card, pulled up a cmd, entered rebootRUU mode, and tried to flash firmware zip.
And...
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (28294 KB)...
OKAY [ 2.210s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 2.701s
What's wrong with my CID? I even changed it from VODAP021 to HTC__039 to see if it would run, still the same error.. :|
EDIT: Okay so I SuperCID'ed, it worked however my bootloader is still 1.55? wut.
Don't tell me I need an unlocked bootloader, I need an unlocked bootloader right? -_-
I believe you said HTCdev won't unlock it if I had a non-matching firmware to my CID/MID? ugh.
EDIT: NOPE, no luck either with an unlocked bootloader - same result.
Click to expand...
Click to collapse
You do realize those errors/safe-guards are actually saving you!!
There's nothing wrong with your CID, so set it back to what it's supposed to be.
And the reason it's not working (actually it is), you are flashing the wrong firmware.zip, the one you are flashing is 28294 KB (probably a modded one), whereas the one you should be flashing (from the link you posted earlier) is 41197KB.
now put the correct firmware.zip in your adb/fastboot folder and flash it, fastboot doesn't use anything from your sdcard, it uses the files on your PC.
nkk71 said:
You do realize those errors/safe-guards are actually saving you!!
There's nothing wrong with your CID, so set it back to what it's supposed to be.
And the reason it's not working (actually it is), you are flashing the wrong firmware.zip, the one you are flashing is 28294 KB (probably a modded one), whereas the one you should be flashing (from the link you posted earlier) is 41197KB.
now put the correct firmware.zip in your adb/fastboot folder and flash it, fastboot doesn't use anything from your sdcard, it uses the files on your PC.
Click to expand...
Click to collapse
Gosh, you are too good. This is definitely the big break.
But nope, freakin' adb decides to bail on me and my device can no longer be detected. WTF?! What have I done to deserve such trouble.. -_-
Hi!
So I have a problem with my M7 and I need to return it to stock so that I can send it back to HTC for repair. I have downloaded the "RUU M7 UL K44 SENSE55 MR O2 UK 4.20.206.16 Radio 4A.23.3263.28 10.38r.1157.04L Release 353143 Signed 2" from here (multiple times to check if I had a corrupted download or something like that).
Every time I run the RUU it reboots it to the black HTC screen then gives me the error message
Code:
ERROR [158]: IMAGE ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
My bootloader is Unlocked (though I have tried it with Relocked). I first tried with SuperCId then I did
Code:
fastboot oem writecid O2___001
(that's 3 underscores - I think that is right!) to put it back to the O2 UK cid and I get the same error. Below is what
Code:
fastboot getvar all
returns.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4222mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.063s
I'm almost certain that this is the correct RUU I should be using.
Can anybody help or tell me why it's going wrong? Thanks in advance!
One thing I forgot to mention - I have previously flashed an RUU zip file from here when I had super cid to unbrick my device. Might that have something to do with it?
HapticThreek said:
One thing I forgot to mention - I have previously flashed an RUU zip file from here when I had super cid to unbrick my device. Might that have something to do with it?
Click to expand...
Click to collapse
Your version main says your on a 401 ruu, your trying to run a 206 ruu, I would change the cid back to HTC__001 and run the 401.ruu personally.
158 error specifies wrong ruu
Seanie280672 said:
Your version main says your on a 401 ruu, your trying to run a 206 ruu, I would change the cid back to HTC__001 and run the 401.ruu personally.
158 error specifies wrong ruu
Click to expand...
Click to collapse
That sounds like it's because I flashed the wrong RUU before then. I thought with super cid I should be able to flash any RUU?
Do you know if there's any way to get my version main back to 206 (which I'm fairly sure it was before I flashed the first ruu), or to get the O2 UK ruu to reflash the version main?
The reason I ask is because the phone has already been sent to HTC for repair once so they would probably know what software was on it when it was returned to me.
Thanks
EDIT: the cid was always O2___001 before I got supercid to unbrick phone. I have used this RUU previously on this phone successfully.
HapticThreek said:
That sounds like it's because I flashed the wrong RUU before then. I thought with super cid I should be able to flash any RUU?
Do you know if there's any way to get my version main back to 206 (which I'm fairly sure it was before I flashed the first ruu), or to get the O2 UK ruu to reflash the version main?
The reason I ask is because the phone has already been sent to HTC for repair once so they would probably know what software was on it when it was returned to me.
Thanks
EDIT: the cid was always O2___001 before I got supercid to unbrick phone. I have used this RUU previously on this phone successfully.
Click to expand...
Click to collapse
You could try setting super cid first, run the O2 ruu and after its finished then set the phone to the O2 cid, or, you could pull the firmware zip from the ruu, force flash that and then run the ruu.
Seanie280672 said:
You could try setting super cid first, run the O2 ruu and after its finished then set the phone to the O2 cid, or, you could pull the firmware zip from the ruu, force flash that and then run the ruu.
Click to expand...
Click to collapse
Thanks, I'll give the second one a shot first. Will the firmware.zip be in the temp folder/rom.zip?
HapticThreek said:
Thanks, I'll give the second one a shot first. Will the firmware.zip be in the temp folder/rom.zip?
Click to expand...
Click to collapse
Yes, when you run the ruu it unpacks itself to a temp folder on your pc, right before you accept the license agreement, find the temp.folder and pull the firmware.zip from the Rom
Seanie280672 said:
Yes, when you run the ruu it unpacks itself to a temp folder on your pc, right before you accept the license agreement, find the temp.folder and pull the firmware.zip from the Rom
Click to expand...
Click to collapse
When I go to extract the rom.zip file I get the message that the archive is corrupt and that CRC data failed in dzdata_32g.img and dzdata_64g.img.
I have tried this on multiple downloads which I have verified the md5 hashes. Using winrar to extract - should I be using something else?
EDIT - quick search tells me its because its encrypted - will look for decrypting solutions
HapticThreek said:
When I go to extract the rom.zip file I get the message that the archive is corrupt and that CRC data failed in dzdata_32g.img and dzdata_64g.img.
I have tried this on multiple downloads which I have verified the md5 hashes. Using winrar to extract - should I be using something else?
EDIT - quick search tells me its because its encrypted - will look for decrypting solutions
Click to expand...
Click to collapse
Yeah, sorry for the slow reply, its because its encrypted, try this
http://forum.xda-developers.com/showthread.php?t=2084470
Seanie280672 said:
Yeah, sorry for the slow reply, its because its encrypted, try this
http://forum.xda-developers.com/showthread.php?t=2084470
Click to expand...
Click to collapse
Hi, thanks very much. So I have extracted the rom.zip, for some reason it split it into 5 zip files. Unfortunately for me none of these zips contained the firmware.zip file you spoke about (or any other zip file).
I think what happened is it extracted what was in the zips too. One of the extracted zips contained the following files:
adsp.img
android-info.txt
cir.img
hboot_signedbyaa.img
pg2fs_spcustom.img
radio.img
ramdisk.img
rcdata.img
recovery_signed.img
rpm.img
sbl1-1.img
sbl1-2.img
sbl1-3.img
sbl2.img
sbl3.img
splash1.nb0
tp_SYN3202.img
tz.img
Am I right in thinking this is the firmware zip file? ( I hope! lol )
HapticThreek said:
Hi, thanks very much. So I have extracted the rom.zip, for some reason it split it into 5 zip files. Unfortunately for me none of these zips contained the firmware.zip file you spoke about (or any other zip file).
I think what happened is it extracted what was in the zips too. One of the extracted zips contained the following files:
adsp.img
android-info.txt
cir.img
hboot_signedbyaa.img
pg2fs_spcustom.img
radio.img
ramdisk.img
rcdata.img
recovery_signed.img
rpm.img
sbl1-1.img
sbl1-2.img
sbl1-3.img
sbl2.img
sbl3.img
splash1.nb0
tp_SYN3202.img
tz.img
Am I right in thinking this is the firmware zip file? ( I hope! lol )
Click to expand...
Click to collapse
Yup that's firmware.zip, all the system files etc, just zip those files back up into one zip, name it firmware.zip and flash it, don't forget to flash it twice, make sure on the 2nd time it says successful at the end, if it says anything else do not restart your phone, it will brick, you will need to find another firmware to flash whilst the phone is still in RUU mode.
see here: http://trjlive.com/guide-install-firmware-htc-one-m7/
Seanie280672 said:
Yup that's firmware.zip, all the system files etc, just zip those files back up into one zip, name it firmware.zip and flash it, don't forget to flash it twice, make sure on the 2nd time it says successful at the end, if it says anything else do not restart your phone, it will brick, you will need to find another firmware to flash whilst the phone is still in RUU mode.
see here: http://trjlive.com/guide-install-firmware-htc-one-m7/
Click to expand...
Click to collapse
Hi, so I did that and followed the guide, unfortunately hasn't worked. get the following when I run fastboot flash zip firmware.zip:
Code:
sending 'zip' (41218 KB)...
OKAY [ 3.118s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 3.396s
Does it need to be re-encrypted or something?
EDIT - actually think the firmware.zip is already encrypted still. trying to see if I can decrypt it.
trying to unzip it gives me "invalid compressed data to inflate" error
EDIT 2 - seems like I'm getting the same issue as this dude http://forum.xda-developers.com/showpost.php?p=49519579&postcount=155. Will look for a different way to decrypt rom.zip
Seanie280672 said:
Yup that's firmware.zip, all the system files etc, just zip those files back up into one zip, name it firmware.zip and flash it, don't forget to flash it twice, make sure on the 2nd time it says successful at the end, if it says anything else do not restart your phone, it will brick, you will need to find another firmware to flash whilst the phone is still in RUU mode.
see here: http://trjlive.com/guide-install-firmware-htc-one-m7/
Click to expand...
Click to collapse
So managed to decrypt properly and flash. Woohoo!
Here is the new output for fastboot getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.206.16
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3830mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-44d68d6b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.064s
Version main now has the 206 in it so hopefully when I get to try the RUU again tomorrow it works, fingers crossed and thanks for all your input so far, you've been really helpful!
EDIT - should have waited til tomorrow to flash this firmware - touch screen is non functional now! bah. Hopefully ruu works tomorrow!
SOLVED
Well, the RUU worked this time and I now have a fully stock phone to return.
Thanks for all your help and pointing me in the right directions. Will hit the thanks button on your posts!
Hi,
I`ve had my fun tuning my htc one, but i`ve no clue how to get it to normal m7 phone with sense 6 lol.
I`ve got TWRP and running the OTA rom does not do anything. Am I trying with the incorrect rom or what?
Thanks for any feedback!
sycorax1337 said:
Hi,
I`ve had my fun tuning my htc one, but i`ve no clue how to get it to normal m7 phone with sense 6 lol.
I`ve got TWRP and running the OTA rom does not do anything. Am I trying with the incorrect rom or what?
Thanks for any feedback!
Click to expand...
Click to collapse
First, we will need to see a fastboot getvar all with the imei and serialno removed. This is needed to know which variant/version of the HTC One M7 you have, so we can point you in the right direction.
Second, OTA's are update files for stock roms with stock recovery for specific versions. If you don't have the correct combination then it will not run properly.
Third, here is a guide for going back to stock. You probably don't want to go to 100% stock but it shows you the proper steps.
majmoz said:
First, we will need to see a fastboot getvar all with the imei and serialno removed. This is needed to know which variant/version of the HTC One M7 you have, so we can point you in the right direction.
Second, OTA's are update files for stock roms with stock recovery for specific versions. If you don't have the correct combination then it will not run properly.
Third, here is a guide for going back to stock. You probably don't want to go to 100% stock but it shows you the proper steps.
Click to expand...
Click to collapse
Sorry, my bad
Code:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: H3G__001
battery-status: good
battery-voltage: 4273mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
sycorax1337 said:
Sorry, my bad
Code:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: H3G__001
battery-status: good
battery-voltage: 4273mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
I can not find a RUU for your phone but I did find a GURU Stock Reset: http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/
Guru Reset file are simply Stock ROM’s packaged with the nice graphical interface of the aroma installer. They include the stock radio and stock recovery, so if you are still S-on then this is best way to reset to stock. It can’t change your firmware but it can get the stock ROM installed with the stock recovery so that you can get OTA updates and it should also remove the Tampered text from your bootloader.
Click to expand...
Click to collapse
There is an OTA at this site for your phone.
I would try to get S-OFF before doing the Stock Reset it would give you more flexibility. If firewater doesn't work to get S-OFF then view this post about a service in the UK.
majmoz said:
I can not find a RUU for your phone but I did find a GURU Stock Reset: http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/
There is an OTA at this site for your phone.
I would try to get S-OFF before doing the Stock Reset it would give you more flexibility. If firewater doesn't work to get S-OFF then view this post about a service in the UK.
Click to expand...
Click to collapse
After installing that GURU stock reset, and updating to sense 5.5, the phone stuck in a reboot loop.
I can get to TWRP within recovery, but I cant push any ROM to the phone so I can use it. Tried the push command, in fastboot mode and command prompt prints message device not found. What am I missing?
sycorax1337 said:
After installing that GURU stock reset, and updating to sense 5.5, the phone stuck in a reboot loop.
I can get to TWRP within recovery, but I cant push any ROM to the phone so I can use it. Tried the push command, in fastboot mode and command prompt prints message device not found. What am I missing?
Click to expand...
Click to collapse
Try the sideload method. Make sure HTC Drivers are installed and ADB is already working. If not, then check out this FAQ Post.
1. Reboot into TWRP
2. In TWRP, hit ADVANCED and find SIDELOAD
3. Swipe to start the SIDELOAD
4. Open a CMD Prompt window and Change Directories to where your adb.exe is
5. Type adb devices and it should show your device connected and say SIDELOAD
6. Your ZIP file should already be in your adb folder
7. You are now ready to push the zip.....
8. Type adb sideload nameofzip.zip
9. Wait until it says 100% and reboot back into recovery to flash the ROM
10. If hitting power does not make the screen come one, type adb reboot recovery
11. If adb reboot recovery does not work, hold power and volume down until it reboots to fastboot then go to recovery
sycorax1337 said:
After installing that GURU stock reset, and updating to sense 5.5, the phone stuck in a reboot loop.
I can get to TWRP within recovery, but I cant push any ROM to the phone so I can use it. Tried the push command, in fastboot mode and command prompt prints message device not found. What am I missing?
Click to expand...
Click to collapse
You can't use that guru reset file, it's too low for your hboot version, the only way you can use it is to downgrade your hboot and the only way you can do that is to get s-off, the otas are putting you into a bootloop because they are trying to upgrade your hboot and as you already have the latest hboot they can't complete that task.
Your stuck with custom roms unless you can get your phone s-off, or find a nandroid backup of your latest rom.
---------- Post added at 06:38 PM ---------- Previous post was at 06:35 PM ----------
as for your driver problem, see FAQ 2 here by nkk71 http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Mate I have same problem like you. No way to bring a phone to life. I try a custom and lot of ruu, but nothing with some ruu i got error 155, and 130. With CyanogenMod, using sideload i got error on the phone, and nothing instal.
Hire is my getvar all.
Code:
C:\ADB>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.57.00
INFOversion-baseband: 4T.27.321
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-OF
INFOserialno:
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4331mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-e47fb74b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.069s
C:\ADB>
People help us to get alive our phones...
Errornt said:
Mate I have same problem like you. No way to bring a phone to life. I try a custom and lot of ruu, but nothing with some ruu i got error 155, and 130. With CyanogenMod, using sideload i got error on the phone, and nothing instal.
Hire is my getvar all.
Code:
C:\ADB>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.57.00
INFOversion-baseband: 4T.27.321
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-OF
INFOserialno:
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4331mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-e47fb74b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.069s
C:\ADB>
People help us to get alive our phones...
Click to expand...
Click to collapse
First, remove the imei and serialno from your original post!
Second, I have had problems running RUU because the hboot was too high. Since, you are S-OFF you can downgrade your hboot then install the RUU. This post will explain the procedure. When the RUU executes it will change your hboot to that of the RUU.
Ok thx mate, I downgrade my Hboot to 1.44.000. Here is log.
Code:
C:\ADB>fastboot flash zip 1.29.401.12_hboot_1.44.zip
sending 'zip' (501 KB)... OKAY [ 0.261s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[hboot] unzipping & flushing...
INFO[RUU]UZ,hboot,0
INFO[RUU]UZ,hboot,50
INFO[RUU]UZ,hboot,100
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,99
INFO[RUU]WP,hboot,100
INFO...... Successful
OKAY [ 2.339s]
finished. total time: 2.602s
C:\ADB>
Then I try flash firmware above in this theard, and got faill in CMD, hire is log.
Code:
C:\ADB>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (733251 KB)... OKAY [ 48.690s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 55.696s
C:\ADB>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (733251 KB)... OKAY [ 48.494s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 55.753s
C:\ADB>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (733251 KB)... OKAY [ 66.921s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 74.199s
Is it possible to my eMMC-boot is death. There is no size text. Look @ picture.
After i flash a new HBOOT text has gone 2048MB
Did you put your phone into ruu mode before trying to flash the firmware ?
Code:
fastboot oem rebootRUU
Seanie280672 said:
Did you put your phone into ruu mode before trying to flash the firmware ?
Code:
fastboot oem rebootRUU
Click to expand...
Click to collapse
Yes mate, the black screen with HTC text.
Can somebody tell me what region is my phone, i buy it from internet and I dont know what RUU to download, to try flash it.
Errornt said:
Yes mate, the black screen with HTC text.
Can somebody tell me what region is my phone, i buy it from internet and I dont know what RUU to download, to try flash it.
Click to expand...
Click to collapse
Well your on 401 which is WWE Europe, same as the hboot you flashed, so you need to flash an ruu or a firmware which is 4.xx.401.xx however I see what your problem is, you have super cid, 401 android-info.txt doesn't have super cid in it, change your cid to HTC__001 then reboot bootloader and try flash the firmware zip again.
Seanie280672 said:
Well your on 401 which is WWE Europe, same as the hboot you flashed, so you need to flash an ruu or a firmware which is 4.xx.401.xx however I see what your problem is, you have super cid, 401 android-info.txt doesn't have super cid in it, change your cid to HTC__001 then reboot bootloader and try flash the firmware zip again.
Click to expand...
Click to collapse
Ok so i need to change my cid to HTC__001 and then flash Some WWE Europe RUU, can you give me a link of some ruu that you thing its good for me. (thx).
Sorry for my bad English.
Edit: I edited my CID to HTC__001 so now I need good RUU to flash it. I woud like to have a orginal rom, but i will be happy if I get my phone on with any custom rom if not with oem.
Errornt said:
Ok so i need to change my cid to HTC__001 and then flash Some WWE Europe RUU, can you give me a link of some ruu that you thing its good for me. (thx).
Sorry for my bad English.
Click to expand...
Click to collapse
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
You may need to find the 4.19.401.9 firmware and flash that first.
I got ERROR 158 IMAGE ERROR, when i try to flash this RUU.
My radio is 4T, and this RUU is 4A is that problem?
Errornt said:
I got ERROR 158 IMAGE ERROR, when i try to flash this RUU.
My radio is 4T, and this RUU is 4A is that problem?
Click to expand...
Click to collapse
Nope, you need to find the corrisponding firmware and flash that first like I said before , you need 4.19.401.9 firmware.zip, flash that first then run the ruu
Seanie280672 said:
Nope, you need to find the corrisponding firmware and flash that first like I said before , you need 4.19.401.9 firmware.zip, flash that first then run the ruu
Click to expand...
Click to collapse
Can you give me more details how to make that to flash 4.19.401.9 firmware.zip, and how to flash it, with cmd? fastboot? Should be unlocked or relocked? when flashing that firmware, and can you help me to find that firmware on the net, because i dont know what i need to search. :angel:
Errornt said:
Can you give me more details how to make that to flash 4.19.401.9 firmware.zip, and how to flash it, with cmd? fastboot? Should be unlocked or relocked? when flashing that firmware, and can you help me to find that firmware on the net, because i dont know what i need to search. :angel:
Click to expand...
Click to collapse
You will have to wait till I get home from work in a few hours for all of that or do a bit of reading and searching
what firmware are you after?
I have been having trouble with data connectivity and I wanted trying returning to stock but have had issues.
First off I was on a 6.* firmware and S-ON so I decided to S-OFF, update the firstware to 6.09.401.5 and got super CID
So then I tried the RUU update (or backdate in my case) to 1.26.502.12 via htc1guru.com (EXE) method and the process failed. Keep in my I change the CID back CWS__001 before
Is this because the firmware is so different or something else?
Is there a RUU available for the 6.09.401.5 firmware / android 4.4.3 I was not able to find one.
I am stuck now, the data is worse that it was before and I just want to get back to stock at this point.
maxpower2078 said:
I have been having trouble with data connectivity and I wanted trying returning to stock but have had issues.
First off I was on a 6.* firmware and S-ON so I decided to S-OFF, update the firstware to 6.09.401.5 and got super CID
So then I tried the RUU update (or backdate in my case) to 1.26.502.12 via htc1guru.com (EXE) method and the process failed. Keep in my I change the CID back CWS__001 before
Is this because the firmware is so different or something else?
Is there a RUU available for the 6.09.401.5 firmware / android 4.4.3 I was not able to find one.
I am stuck now, the data is worse that it was before and I just want to get back to stock at this point.
Click to expand...
Click to collapse
Is your phone AT&T = CWS__001 ? or is it international = 6.9.401.5 ?
If you on 6.x why in the world would you go all the back to 1.x ? that's 2 years old ?
clsA said:
Is your phone AT&T = CWS__001 ? or is it international = 6.9.401.5 ?
If you on 6.x why in the world would you go all the back to 1.x ? that's 2 years old ?
Click to expand...
Click to collapse
I'm just trying to find the combo that works at this point.
I flashed 4.18.502.7 in hopes to flash that RUU as I am getting the following right now
D:\android\dev\platform-tools>fastboot flash zip ROM.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 38723880 is not a multiple of the block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 38723880 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 38723880 is not a multiple of the block size 4096
OKAY [ 65.799s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 66.006s
this came from trying to install RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_decrypted.ROM.zip linked to from your post actually
I would like the latest 4.4.3 RUU but can't find it.
I have set the CID to 11111111 for now but it was CWS__001 so yes, US AT&T
Is there a better way?
for good measure
Code:
D:\android\dev\platform-tools>fastboot getvar al
(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: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3937mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.166s
maxpower2078 said:
I'm just trying to find the combo that works at this point.
I flashed 4.18.502.7 in hopes to flash that RUU as I am getting the following right now
D:\android\dev\platform-tools>fastboot flash zip ROM.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 38723880 is not a multiple of the block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 38723880 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 38723880 is not a multiple of the block size 4096
OKAY [ 65.799s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 66.006s
this came from trying to install RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_decrypted.ROM.zip linked to from your post actually
I would like the latest 4.4.3 RUU but can't find it.
I have set the CID to 11111111 for now but it was CWS__001 so yes, US AT&T
Is there a better way?
Click to expand...
Click to collapse
Your s-off so use the firmware and RUU combination and leave your CID at CWS__001
flash this first then the 4.x.502 RUU
https://www.androidfilehost.com/?fid=23329332407580581
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
after this you can take the OTA to 5.x.502
after it's done you can flash back to custom recovery if you want.
clsA said:
Your s-off so use the firmware and RUU combination and leave your CID at CWS__001
flash this first then the 4.x.502 RUU
https://www.androidfilehost.com/?fid=23329332407580581
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
after this you can take the OTA to 5.x.502
after it's done you can flash back to custom recovery if you want.
Click to expand...
Click to collapse
I do have firmware 4.18.502.7 on right now but am getting the message above. i found a thread that attributed it to the fastboot version and to use mfastboot but that appears to be for motorolas.
I am using the ruu linked here http://forum.xda-developers.com/showthread.php?t=2695749
do i need to have the same firmware one as the ruu has when flashing it?
maxpower2078 said:
do i need to have the same firmware one as the ruu has when flashing it?
Click to expand...
Click to collapse
yes flash the firmware then the RUU , regardless if your on it now or not
update your fastboot here > http://forum.xda-developers.com/showthread.php?t=2588979
clsA said:
yes flash the firmware then the RUU , regardless if your on it now or not
update your fastboot here > http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
thanks, got the EXE version of 4.18.502.7 to work. Now I'll see if there is an OTA from here, but I'm on Straightalk so I am not sure if I can receive AT&T OTAs
maxpower2078 said:
thanks, got the EXE version of 4.18.502.7 to work. Now I'll see if there is an OTA from here, but I'm on Straightalk so I am not sure if I can receive AT&T OTAs
Click to expand...
Click to collapse
Well if your back to stock with a working phone i guess your ok
If you want to continue on go here >> http://forum.xda-developers.com/showthread.php?t=2775650
clsA said:
Well if your back to stock with a working phone i guess your ok
If you want to continue on go here >> http://forum.xda-developers.com/showthread.php?t=2775650
Click to expand...
Click to collapse
Thanks, this has been a huge struggle and all brought on by sporadic non functioning data. Tested on this and it works great. I am doing the OTA update right now. I will put another recovery on it to backup the current image at minimum.
maxpower2078 said:
Thanks, this has been a huge struggle and all brought on by sporadic non functioning data. Tested on this and it works great. I am doing the OTA update right now. I will put another recovery on it to backup the current image at minimum.
Click to expand...
Click to collapse
and this is all my wifes phone, mine has the same problem and have to do it all over again, haha
maxpower2078 said:
Thanks, this has been a huge struggle and all brought on by sporadic non functioning data. Tested on this and it works great. I am doing the OTA update right now. I will put another recovery on it to backup the current image at minimum.
Click to expand...
Click to collapse
Good deal, TWRP 2.8.4.0 has been working well for me