Related
[Q] "Mobile network not available" on Sprint with fresh install of Cyanogenmod 11
I have an HTC One M7 on Sprint, and I just installed the latest snapshot build of CM 11 from four days ago... And now I have no mobile network connectivity. :crying: I'm very new to the custom ROM scene, so I'm thinking (and hoping) there's just some very obvious step that I've missed somewhere, but I don't know enough to know what I should be looking for, so my search for similar problems didn't yield much useful information.
When I look at the mobile network settings, it's pretty much Greek to me. Do I need to change the preferred network type? It's set to "Global" by default. Is there anything else I should try?
Or should I just try a different, more stable build?
Thanks in advance.
I hope you didn't flash the m7_ul cm11 if so you need to ruu back to stock and flash the Sprint version
Sent from my HTC One using XDA Premium 4 mobile app
Whoareyou said:
I hope you didn't flash the m7_ul cm11 if so you need to ruu back to stock and flash the Sprint version
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, I only flashed the Sprint version. I used the file cm-11-20140708-SNAPSHOT-M8-m7spr.zip
But on that note, could you give me a push in the right direction for how to go back to the stock ROM in case it comes to that? I'm guessing that going back to stock will not quite be as simple as just installing one of these zip files from recovery mode.
EDIT: And in case it helps, here is the the fastboot getvar all output:
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxx
(bootloader) imei: xxx
(bootloader) meid: xxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4196mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.034s
EDIT 2: One other thing is that I did not install the firewater S-OFF and HBOOT tools that seemed to be recommended on the cyanogenmod wiki. They weren't necessary from what I could tell. Could that be part of the problem?
i dont think that could be an issue, but i would recommend using firewater to s-off, it'll make all processes alot easier.
if it comes to you needing to RUU back to stock, heres a link to the M7_SPR RUU: http://www.androidfilehost.com/?fid=23329332407573774
to flash it you will likely need to be s-off
run "fastboot oem lock"
unzip it and run the exe
also, make sure you install all ota's (BE S-OFF SO YOU ARENT STUCK WITHOUT ROOT) so you get the latest radio.
Whoareyou said:
i dont think that could be an issue, but i would recommend using firewater to s-off, it'll make all processes alot easier.
if it comes to you needing to RUU back to stock, heres a link to the M7_SPR RUU:
to flash it you will likely need to be s-off
run "fastboot oem lock"
unzip it and run the exe
also, make sure you install all ota's (BE S-OFF SO YOU ARENT STUCK WITHOUT ROOT) so you get the latest radio.
Click to expand...
Click to collapse
So does this mean you'd recommend going back to stock to fix the problem? There aren't any obvious solutions for fixing my problem while keeping CM 11 installed?
Also, when you say "be s-off", does that mean that I should have some kind of setting configured before flashing the stock ROM? Or that I should just make the device s-off (i.e. run firewater s-off successfully) before flashing? I don't know my terminology here very well yet.
RocketGuy3 said:
So does this mean you'd recommend going back to stock to fix the problem? There aren't any obvious solutions for fixing my problem while keeping CM 11 installed?
Also, when you say "be s-off", does that mean that I should have some kind of setting configured before flashing the stock ROM? Or that I should just make the device s-off (i.e. run firewater s-off successfully) before flashing? I don't know my terminology here very well yet.
Click to expand...
Click to collapse
It might, yes, run firewater to s-off, and then fastboot oem lock then flash. then install all OTA updates, then try again with unlocking and flashing.
So you mean following the above steps you gave me for flashing the stock ROM will re-lock the bootloader?
Also, when you say "OTA" updates, you mean the OEM updates for my OS? That would take me from Android 4.3 to 4.4.x?
Exactly, they also bring new firmware, like radio and hboot versions. go up to the latest version then try the unlock procedure and flash CM11 again, its that doesnt work then im not sure
Whoareyou said:
Exactly, they also bring new firmware, like radio and hboot versions. go up to the latest version then try the unlock procedure and flash CM11 again, its that doesnt work then im not sure
Click to expand...
Click to collapse
Hmmm, ok, cool. I'll give that a try. I'm pretty sure I was running the latest OEM software before I began the update process since I always did any system updates as soon as I was notified about them. Only thing is that when I unlocked the bootloader, factory reset, and rooted, somewhere along the way, it took me back from 4.4.x to 4.3... so maybe that's where the problem was.
Whoareyou said:
i dont think that could be an issue, but i would recommend using firewater to s-off, it'll make all processes alot easier.
if it comes to you needing to RUU back to stock, heres a link to the M7_SPR RUU: http://www.androidfilehost.com/?fid=23329332407573774
to flash it you will likely need to be s-off
run "fastboot oem lock"
unzip it and run the exe
also, make sure you install all ota's (BE S-OFF SO YOU ARENT STUCK WITHOUT ROOT) so you get the latest radio.
Click to expand...
Click to collapse
Two other [hopefully] quick questions about this. I just realized you mentioned running an exe, but when I look in that zip, there are several. Which exe are you referring to? The fastboot-htc.exe? Also, does one of these utilities exist for macos? I could run it on a Windows machine, but I'm guessing I'll need to install the Android SDK platform tools and whatnot for it to work properly.
Should be aruwizard
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
And no, but you may be able to use fastboot on your Mac and boot into fastboot then run "fastboot oem rebootRUU" then run "fastboot flash zip ROM.zip"
Sent from my HTC One using XDA Premium 4 mobile app
Whoareyou said:
Should be aruwizard
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
And no, but you may be able to use fastboot on your Mac and boot into fastboot then run "fastboot oem rebootRUU" then run "fastboot flash zip ROM.zip"
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That exe was getting my hopes up. It started running fine on my windows PC, and then I got an "htc_fastboot.exe has stopped working" dialog of death. Happened on consecutive tries. :/ So I tried the method you described for my Mac, and I got another failure:
$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.042s]
finished. total time: 0.042s
$
$ 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 122174151 is not a multiple of the block size 4096
sending sparse 'zip' (1478258 KB)...
error: write_sparse_skip_chunk: don't care size 122174151 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 122174151 is not a multiple of the block size 4096
OKAY [ 66.233s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 66.446s
Any ideas what the problem could be here?
BAH. I hope I don't have to buy a new phone.
EDIT: And just to be sure I had the steps right, I was supposed to re-lock the bootloader via fastboot BEFORE attempting to image the phone back to stock, right? And I shouldn't try to use the TWRP recovery to install the rom.zip file the same way I installed CM11?
If you haven't s-offed yes, but I've not seen that error, maybe your zip is corrupt did you make sure to extract all the files from the archive with the exes in it?
And no you can't flash that kind of zip in recovery, try to open the rom.zip and make sure you see like, system.img sp1.img radio.img, things like thay
Sent from my HTC One using XDA Premium 4 mobile app
Whoareyou said:
If you haven't s-offed yes, but I've not seen that error, maybe your zip is corrupt did you make sure to extract all the files from the archive with the exes in it?
And no you can't flash that kind of zip in recovery, try to open the rom.zip and make sure you see like, system.img sp1.img radio.img, things like thay
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, I extracted all the files. But wait, I wasn't supposed to s-off before locking the bootloader and imaging? Because I did s-off the phone. Do I need to s-on again? Or should I just be following a different procedure with s-off?
EDIT: Good call on checking the rom.zip file. Apparently it's corrupt:
$ unzip rom.zip
Archive: rom.zip
warning [rom.zip]: 1131492323 extra bytes at beginning or within zipfile
(attempting to process anyway)
file #1: bad zipfile offset (local header sig): 1131492323
(attempting to re-compensate)
file #1: bad zipfile offset (local header sig): 1131492323
file #2: bad zipfile offset (local header sig): 171
(attempting to re-compensate)
file #2: bad zipfile offset (local header sig): 171
file #3: bad zipfile offset (local header sig): 1299614395
file #4: bad zipfile offset (local header sig): 1467750400
file #5: bad zipfile offset (local header sig): 1467752388
file #6: bad zipfile offset (local header sig): 1467755030
inflating: dzdata_64g.hdr
inflating: tp_HMX852XD.img
inflating: boot_signed.img
The md5 hash checks out, and I tried re-downloading the RUU zip with no luck.
RocketGuy3 said:
Yeah, I extracted all the files. But wait, I wasn't supposed to s-off before locking the bootloader and imaging? Because I did s-off the phone. Do I need to s-on again? Or should I just be following a different procedure with s-off?
EDIT: Good call on checking the rom.zip file. Apparently it's corrupt:
$ unzip rom.zip
Archive: rom.zip
warning [rom.zip]: 1131492323 extra bytes at beginning or within zipfile
(attempting to process anyway)
file #1: bad zipfile offset (local header sig): 1131492323
(attempting to re-compensate)
file #1: bad zipfile offset (local header sig): 1131492323
file #2: bad zipfile offset (local header sig): 171
(attempting to re-compensate)
file #2: bad zipfile offset (local header sig): 171
file #3: bad zipfile offset (local header sig): 1299614395
file #4: bad zipfile offset (local header sig): 1467750400
file #5: bad zipfile offset (local header sig): 1467752388
file #6: bad zipfile offset (local header sig): 1467755030
inflating: dzdata_64g.hdr
inflating: tp_HMX852XD.img
inflating: boot_signed.img
The md5 hash checks out, and I tried re-downloading the RUU zip with no luck.
Click to expand...
Click to collapse
No, If you s-off it just means you don't have to relock your boot loader to flash an RUU, youbcant unzip it because its encrypted by HTC, here's a decrypted version, try flashing this instead, http://www.androidfilehost.com/?fid=23329332407573741
You must be s-off to flash the decrypted ruu I believe
Sent from my HTC One using XDA Premium 4 mobile app
Whoareyou said:
No, If you s-off it just means you don't have to relock your boot loader to flash an RUU, youbcant unzip it because its encrypted by HTC, here's a decrypted version, try flashing this instead, http://www.androidfilehost.com/?fid=23329332407573741
You must be s-off to flash the decrypted ruu I believe
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So I see the file structure in here is very different from the encrypted version. From what I found on this link:
http://forum.xda-developers.com/showthread.php?t=2658910
I should cat three image files together into one new system image file. I did that, but can you tell me what the next step is? Do I need to zip that new img file up and then run flashboot flash zip with it? In which case, I have to wonder what all those other files are for.
RocketGuy3 said:
So I see the file structure in here is very different from the encrypted version. From what I found on this link:
http://forum.xda-developers.com/showthread.php?t=2658910
I should cat three image files together into one new system image file. I did that, but can you tell me what the next step is? Do I need to zip that new img file up and then run flashboot flash zip with it? In which case, I have to wonder what all those other files are for.
Click to expand...
Click to collapse
not sure, i dont have the sprint model so ive nevefr done this with this file, id follow the directions in the link you posted if i were you
Whoareyou said:
not sure, i dont have the sprint model so ive nevefr done this with this file, id follow the directions in the link you posted if i were you
Click to expand...
Click to collapse
I would, but it doesn't seem that they have much more detail about the process other than that cat command from what I can tell. But I'll ask in that thread. Thanks for your help.
No prob, sorry i couldnt be of more assistance
One last question, and maybe my stupidest one yet -- Do you think there is any possibility that Sprint will be able to recover my phone for me if I take it into a Sprint store? I know it's a longshot, but I figure they MIGHT have some canned way of doing this that they teach their employees.
If not, I think I'm about to just buy a Nexus 5 and call it a day.
Fastboot flash system ...
(bootloader) Data size exceeds download buffer
FAILED (Remote Failure)
What is going on?
Need the new fastboot
papi92 said:
Need the new fastboot
Click to expand...
Click to collapse
I have tried that with no success
Unlocked bootloader? Stock USB cable.
papi92 said:
Unlocked bootloader? Stock USB cable.
Click to expand...
Click to collapse
Yeah stock cable, bootloader is unlocked and everything besides the system image flashes without a hitch
Weird.
Maybe a corrupt download? Try downloading it again and/or check the MD5. (af4520213c1a3e2b3dd811aef030b87b)
same here
i'm stuck...
jamesadalpiaz said:
Maybe a corrupt download? Try downloading it again and/or check the MD5. (af4520213c1a3e2b3dd811aef030b87b)
Click to expand...
Click to collapse
Thanks man didn't even think to check, 'twas a bad download!
still doesnt work for me.
my download is okay.
when trying to flash system img -- still getting the same message as above.
when trying to use flash all bat file --getting these quoets:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain recovery.sig'
failed to allocate 1679592636 bytes
error: update package missing system.img
Click to expand...
Click to collapse
Please help me
itamarbh said:
still doesnt work for me.
my download is okay.
when trying to flash system img -- still getting the same message as above.
when trying to use flash all bat file --getting these quoets:
Please help me
Click to expand...
Click to collapse
what error do you get when you try to unzip and flash the individual img files?
jj14 said:
what error do you get when you try to unzip and flash the individual img files?
Click to expand...
Click to collapse
this...
(bootloader) Data size exceeds download buffer
FAILED (Remote Failure)
Thanks !
itamarbh said:
still doesnt work for me.
my download is okay.
when trying to flash system img -- still getting the same message as above.
when trying to use flash all bat file --getting these quoets:
Please help me
Click to expand...
Click to collapse
When you downloaded the .tgz file and extracted it, it contained a .tar file. When you extract the .tar file you get the shamu-lrx21o folder. Within that folder you have the flash-all.bat, but you also have the image-shamu-lrx21o.zip file. Extract the contents of that zip file and try again. The system.img file is in that zip file.
Astraeus85 said:
When you downloaded the .tgz file and extracted it, it contained a .tar file. When you extract the .tar file you get the shamu-lrx21o folder. Within that folder you have the flash-all.bat, but you also have the image-shamu-lrx21o.zip file. Extract the contents of that zip file and try again. The system.img file is in that zip file.
Click to expand...
Click to collapse
I know, tried that as well, didn't work...
i'm stuck.
itamarbh said:
still doesnt work for me.
my download is okay.
when trying to flash system img -- still getting the same message as above.
when trying to use flash all bat file --getting these quoets:
Please help me
Click to expand...
Click to collapse
Here's your help. I had the same exact problem. Follow the instructions to this link and you'll be back on track.
http://www.ibtimes.co.uk/how-fix-er...roid-5-0-factory-images-nexus-devices-1474865
glensta said:
Here's your help. I had the same exact problem. Follow the instructions to this link and you'll be back on track.
http://www.ibtimes.co.uk/how-fix-er...roid-5-0-factory-images-nexus-devices-1474865
Click to expand...
Click to collapse
Thanks for reponding,
But this didn't help, like I said before -- I'm getting an error while flashing the system img alone as well...
Thanks anyway...
Anyone else?
itamarbh said:
Thanks for reponding,
But this didn't help, like I said before -- I'm getting an error while flashing the system img alone as well...
Thanks anyway...
Anyone else?
Click to expand...
Click to collapse
Did u even try this method above I posted? How could it not help. It works perfectly. Seems u didn't try it is my guess. If your stuck don't try just flashing the system.img only, start over with a complete factory image reflash. It'll wipe ur data but so what, u'll be back in business
itamarbh said:
this...
(bootloader) Data size exceeds download buffer
FAILED (Remote Failure)
Thanks !
Click to expand...
Click to collapse
I ran into this yesterday, do this:
Download the Android SDK: https://developer.android.com/sdk
Grab fastboot from the platforms-tools folder.
Flash System again
This will fix it, you just need the newest Fastboot.
Sent from my Nexus 6 using XDA Free mobile app
I'm also stuck.
I keep getting the error 'cannot load system.img'. Everything else flashes fine. The bootloader and the radio. I received the OTA and that didn't install either. I was left with the android guy on his back and it said error. I'm not sure if it has to do with the encryption on the phone or not but it's frustrating. I did root with CFauto root method but my recovery is still stock. I'll try the new fastboot and see what happens.
This might not apply in this situation, but coming from several years of previous Motorola phones, sometimes I had to download and use mfastboot (Motorola's version of fastboot) for large images to flash. It's worth a shot and won't hurt to try it
Edit: here is the link. If you decide to try it, make sure to read the first section on renaming the file http://mark.cdmaforums.com/ADB.htm
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M_PUT SHIP S-ON RH
HBOOT-1.57.0000
OpenDSP-v32.120.274.0909
OS-5.502.2
eMMC-bot 2048MB
Apr 22 2014, 01:10:58.0
HTC One (M7) AT&T
^^^^^^^^^^^^^^^^^^^^^^^^^^
Above is my information on my phone when booting up into the fastboot, recovery, factory reset, etc menu
I don't have an OS as well
Now the problem I have here is that I can't load my stock ROM when rebooting. I already loaded up a ZIP file of the specific stock ROM that I'm suppose to be on but nothing happens when on command prompt!
This is what happens:
>fastboot flash zip Guru_Reset_M7_5.12.502.2_clsA.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1245080 KB)...
OKAY [ 57.277s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 180.581s
Very frustrating especially with the fact that there isn't a EXE file version so I can't go and try that way either. Running out of options. Hoping somebody here to diagnosis this situation
AndroidHTC2013 said:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M_PUT SHIP S-ON RH
HBOOT-1.57.0000
OpenDSP-v32.120.274.0909
OS-5.502.2
eMMC-bot 2048MB
Apr 22 2014, 01:10:58.0
HTC One (M7) AT&T
^^^^^^^^^^^^^^^^^^^^^^^^^^
Above is my information on my phone when booting up into the fastboot, recovery, factory reset, etc menu
I don't have an OS as well
Now the problem I have here is that I can't load my stock ROM when rebooting. I already loaded up a ZIP file of the specific stock ROM that I'm suppose to be on but nothing happens when on command prompt!
This is what happens:
>fastboot flash zip Guru_Reset_M7_5.12.502.2_clsA.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1245080 KB)...
OKAY [ 57.277s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 180.581s
Very frustrating especially with the fact that there isn't a EXE file version so I can't go and try that way either. Running out of options. Hoping somebody here to diagnosis this situation
Click to expand...
Click to collapse
The Guru Reset your trying to flash is flashed in custom recovery
Unlock the bootloader first then
Flash TWRP 2.6.3.3 >> http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
now boot to recovery and push the Guru reset to the phone
adb push rom.zip /sdcard/
just put the rom in the same folder as adb and fastboot and rename it rom.zip
the last step is to install the rom in TWRP / Install
During the install you can choose to keep the custom recovery you have now or return to stock recovery so you can recieve OTA updates again .. that's up to you
clsA said:
now boot to recovery and push the Guru reset to the phone
adb push rom.zip /sdcard/
just put the rom in the same folder as adb and fastboot and rename it rom.zip
the last step is to install the rom in TWRP / Install
Click to expand...
Click to collapse
Okay up until this point everything was going great except when I typed "adb push rom.zip /sdcard/" (I copied and pasted what you wrote) into the command prompt and this message appeared:
>adb push rom.zip /sdcard/
cannot stat 'rom.zip': No such file or directory
Now what did I do wrong? I renamed the file as rom.zip just like you said and I placed it in the same folder as adb and fastboot. Was I suppose to go to a specific part of TWRP recovery? ADB sideload? I already tried ADB sideload but nothing happened....
AndroidHTC2013 said:
Okay up until this point everything was going great except when I typed "adb push rom.zip /sdcard/" (I copied and pasted what you wrote) into the command prompt and this message appeared:
>adb push rom.zip /sdcard/
cannot stat 'rom.zip': No such file or directory
Now what did I do wrong? I renamed the file as rom.zip just like you said and I placed it in the same folder as adb and fastboot.
Click to expand...
Click to collapse
if your using windows you probably renamed it rom.zip.zip
in the command window type adb push then leave a space and drag the rom.zip to the window now finish the command with a space then /sdcard/
clsA said:
if your using windows you probably renamed it rom.zip.zip
in the command window type adb push then leave a space and drag the rom.zip to the window now finish the command with a space then /sdcard/
Click to expand...
Click to collapse
I don't understand this part; do you mean to actually drag and drop the rom.zip to command prompt? It didn't work
Sorry if I'm making this more harder than it should be, and yes I'm using Windows as my operating system
AndroidHTC2013 said:
I don't understand this part; do you mean to actually drag and drop the rom.zip to command prompt? It didn't work
Sorry if I'm making this more harder than it should be, and yes I'm using Windows as my operating system
Click to expand...
Click to collapse
in the command window type dir and hit enter ... now whats the name of your rom.zip
clsA said:
in the command window type dir and hit enter ... now whats the name of your rom.zip
Click to expand...
Click to collapse
Okay so I left the ZIP file as "rom" and then I re-did the whole process again. After that I finally got that GURU Reset file in the SD card. But when trying to install it it just gave me an error message! I'm assuming that it wasn't compatible with my software even though it match specifically with mines. Do you think I may have gotten the wrong software even though it's HTC One (M7) Sense 6 5.502.2(which was the last stock rom I got before rooting) ? Is there even a version released in the US specifically?
AndroidHTC2013 said:
Okay so I left the ZIP file as "rom" and then I re-did the whole process again. After that I finally got that GURU Reset file in the SD card. But when trying to install it it just gave me an error message! I'm assuming that it wasn't compatible with my software even though it match specifically with mines. Do you think I may have gotten the wrong software even though it's HTC One (M7) Sense 6 5.502.2(which was the last stock rom I got before rooting) ? Is there even a version released in the US specifically?
Click to expand...
Click to collapse
what error message ? did aroma start or did TWRP give the error ?
did you md5 check your download ?
Guru_Reset_M7_5.12.502.2_clsA.zip
http://www.androidfilehost.com/?fid=23501681358545274
MD5: 3b4013265e9134bc6916cf3c5fd14406
clsA said:
what error message ? did aroma start or did TWRP give the error ?
did you md5 check your download ?
Guru_Reset_M7_5.12.502.2_clsA.zip
http://www.androidfilehost.com/?fid=23501681358545274
MD5: 3b4013265e9134bc6916cf3c5fd14406
Click to expand...
Click to collapse
TWRP gave me the message. No I didn't let MD5 check my download... am I suppose to?
AndroidHTC2013 said:
TWRP gave me the message. No I didn't let MD5 check my download... am I suppose to?
Click to expand...
Click to collapse
Please check your downloads
clsA said:
Please check your downloads
Click to expand...
Click to collapse
I just tried intalling MD5 on TWRP and it said:
Updating partition details...
Error flashing zip '/sdcard/md5.zip'
Failed
WHAT?
AndroidHTC2013 said:
I just tried intalling MD5 on TWRP and it said:
Updating partition details...
Error flashing zip '/sdcard/md5.zip'
Failed
WHAT?
Click to expand...
Click to collapse
Wow ... it a pc app just unzip it to your desktop
clsA said:
Wow ... it a pc app just unzip it to your desktop
Click to expand...
Click to collapse
It said that they don't match... Now what?
AndroidHTC2013 said:
It said that they don't match... Now what?
Click to expand...
Click to collapse
re-download it, you can't flash it if it's corrupt
clsA said:
re-download it, you can't flash it if it's corrupt
Click to expand...
Click to collapse
That link for the GURU Reset you gave me didn't work. I re-downloaded it again but still the same result
Is there any other places where I can redownload HTC One M7 Sense 6 AT&T version
AndroidHTC2013 said:
That link for the GURU Reset you gave me didn't work. I re-downloaded it again but still the same result
Is there any other places where I can redownload HTC One M7 Sense 6 AT&T version
Click to expand...
Click to collapse
What ??
Their are 9 mirrors on that link
Guru_Reset_M7_5.12.502.2_clsA.zip
http://www.androidfilehost.com/?fid=23501681358545274
clsA said:
What ??
Their are 9 mirrors on that link
Guru_Reset_M7_5.12.502.2_clsA.zip
http://www.androidfilehost.com/?fid=23501681358545274
Click to expand...
Click to collapse
I tried all of them. Not one matched! I think something occurred between the day that they were put out and now that caused this to happen...
Want proof? I 've attached a screenshot of what I've been getting. This occurred over the nine different places that the ROM was from
Is there any chance of a EXE file version of this? Or any other places for a complete ZIP file? Oh and just to let you know the website said 1.2 GB, but the actual downloaded file had only 1.18 GB, not sure if this helps or not, just to let you know
AndroidHTC2013 said:
I tried all of them. Not one matched! I think something occurred between the day that they were put out and now that caused this to happen...
Want proof? I 've attached a screenshot of what I've been getting. This occurred over the nine different places that the ROM was from
Is there any chance of a EXE file version of this? Or any other places for a complete ZIP file? Oh and just to let you know the website said 1.2 GB, but the actual downloaded file had only 1.18 GB, not sure if this helps or not, just to let you know
Click to expand...
Click to collapse
man your are something else
try using the actual MD5 in the box that says Paste next to it
3b4013265e9134bc6916cf3c5fd14406
did you actually think the MD5 was 5.502.2 ?????
@Danny201281 ...please help before i shoot myself
clsA said:
man your are something else
try using the actual MD5 in the box that says Paste next to it
3b4013265e9134bc6916cf3c5fd14406
did you actually think the MD5 was 5.502.2 ?????
@Danny201281 ...please help before i shoot myself
Click to expand...
Click to collapse
No actually that was my computer that automatically set it. And, I'm still stuck at the TWRP installation again but this time it says:
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
Sorry I'm losing your patience here, if it helps I'll donate, because I'm getting help at least! I WILL DONATE
AndroidHTC2013 said:
No actually that was my computer that automatically set it. And, I'm still stuck at the TWRP installation again but this time it says:
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
Sorry I'm losing your patience here, if it helps I'll donate, because I'm getting help at least! I WILL DONATE
Click to expand...
Click to collapse
LOL sorry man it's fine, I just expect a lot from those i'm helping.
the cache error is meaningless you erased the cache so you get the error ...it has nothing to do with flashing the guru reset
what happens when you go to install the rom (post a picture if possible)
My HTC One M7 (UK O2) was prompting me to update to the latest operating system.
Eventually I succumbed and installed the update. The phone is stock although I had unlocked the bootloader in preparation for experimenting with new operating systems (I'm a noob but curious about experimenting).
After installing, the phone rebooted and wound up on a screen with a red exclamation mark in a picture of a phone.
Sometimes it boots into the white Android startup screen, then shuts down and goes throught the whole startup cycle in a loop
I can get it into bootloader mode but none of the options presented there such as factory reset seem to do anything.
I don't think it's a hardwear problem as it seems to be a direct result of trying to install the update.
I would send it in for a warranty repair but I think that as I have unlocked then relocked the bootloader and it shows a 'relocked' flag then that voids the warranty, is that right?
Any help to sort this mess out would be appreciated.
Thanks
jimbobly
During unlocking bootloader some files deleted and during update ota checks file integrity so file found missing and update stops
So basically you have to restore that files
Or RUU update can be found here
But it will delete your all data photo songs contact apps so backup them
http://forum.xda-developers.com/showthread.php?t=3053944
Thanks Yatindroid,
I don't think I can restore the files so I need to use the RUU. Can you tell me how to identify the correct file?
Thanks
jimbobly said:
Thanks Yatindroid,
I don't think I can restore the files so I need to use the RUU. Can you tell me how to identify the correct file?
Thanks
Click to expand...
Click to collapse
this file: https://www.androidfilehost.com/?fid=95916177934541097
instructions on how to flash it are at the top of the page in Yatindroid's link.
RUU
Seanie280672 said:
this file androidfilehost.com/?fid=95916177934541097
instructions on how to flash it are at the top of the page in Yatindroid's link.
Click to expand...
Click to collapse
This file seems to be corrupt/ can't be opened, downloaded it 3 times, can you link an alternative or explain the things that I need to consider in order to be able to choose an RUU myself.
Thanks
jimbobly said:
This file seems to be corrupt/ can't be opened, downloaded it 3 times, can you link an alternative or explain the things that I need to consider in order to be able to choose an RUU myself.
Thanks
Click to expand...
Click to collapse
This file is not corrupted, its encrypted, you can't open it. Want to know if its corrupted? MD5 value is what you want to check.
If the MD5 is ok then flash the zip.
md5: 399fa4bc8e841cc993a358e7c09fc4ca
alray said:
This file is not corrupted, its encrypted, you can't open it. Want to know if its corrupted? MD5 value is what you want to check.
If the MD5 is ok then flash the zip.
md5: 399fa4bc8e841cc993a358e7c09fc4ca
Click to expand...
Click to collapse
Can you explain what is happening when I try to flash it over to the phone.
I go through all the steps and when I execute the flash command for this zip file it says 'Preprocess_file : Cannot open file RUU.zip' This lead me to believe it was defective in some way. What am I missing?
jimbobly said:
Can you explain what is happening when I try to flash it over to the phone.
I go through all the steps and when I execute the flash command for this zip file it says 'Preprocess_file : Cannot open file RUU.zip' This lead me to believe it was defective in some way. What am I missing?
Click to expand...
Click to collapse
First is the Md5 good?
RUU
jimbobly said:
Can you explain what is happening when I try to flash it over to the phone.
I go through all the steps and when I execute the flash command for this zip file it says 'Preprocess_file : Cannot open file RUU.zip' This lead me to believe it was defective in some way. What am I missing?
Click to expand...
Click to collapse
Also, when I try to unpack the zip file I get the message that the compressed file is empty!
jimbobly said:
Also, when I try to unpack the zip file I get the message that the compressed file is empty!
Click to expand...
Click to collapse
To eliminate any doubt about corrupted file, the only thing you have to do is to check the md5 value. ANd like we already said, the file is encrypted you can't open an encrypted zip. Just check the md5 to confirm the file is good.
alray said:
To eliminate any doubt about corrupted file, the only thing you have to do is to check the md5 value. ANd like we already said, the file is encrypted you can't open an encrypted zip. Just check the md5 to confirm the file is good.
Click to expand...
Click to collapse
Unfortunately, this is a bit advanced for me. How can I do this?
jimbobly said:
Unfortunately, this is a bit advanced for me. How can I do this?
Click to expand...
Click to collapse
http://www.winmd5.com/
alray said:
http://www.winmd5.com/
Click to expand...
Click to collapse
OK, I checked the md5 with the tool and they match. But I still get the message 'preprocess file cannot open zip'.
How should I be handling the file, with the fastboot commands?
jimbobly said:
OK, I checked the md5 with the tool and they match. But I still get the message 'preprocess file cannot open zip'.
How should I be handling the file, with the fastboot commands?
Click to expand...
Click to collapse
you need learn flashing RUU zip
reboot your phone to fastboot mode (same as you posted pic )
setup adb folder find miniSDK HERE and Here
Download htc fastboot HERE copy it adb folder rename it fastboot.exe (rename old fastboot to other name)
open adb folder put your RUU zip there rename it RUU.zip
connect your phone with PC
your phone should be locked/relocked
at adb folder open CMD (shift + right click)
type command below
Code:
fastboot devices
(will show attached phone to PC match serial no)
Code:
fastboot oem rebootRUU
(reboot phone to flashing ruu mode)
Code:
fastboot flash zip RUU.zip
(wait it will take time 8-10 minutes it will show successfully at last if not repeat same command immediately)
Code:
fastboot reboot-bootloader
( it is last and important step of flashing)
now see new version showing at phone details
reboot to system
RUU
Thanks for taking the time to look at this Yatindroid.
I followed your instructions but there seems to be a problem with the RUU file.
When I execute the 'flash zip' command I get an 'unable to read zip message!
The file I have has been recommended by several people.
Am I handling this file incorrectly?
This is the file I am using. https://www.androidfilehost.com/?fid=95916177934541097
All I did was rename the file RUU.zip and move it to the ADB folder.
Thanks for the help.
jimbobly said:
Thanks for taking the time to look at this Yatindroid.
I followed your instructions but there seems to be a problem with the RUU file.
When I execute the 'flash zip' command I get an 'unable to read zip message!
The file I have has been recommended by several people.
Am I handling this file incorrectly?
This is the file I am using. https://www.androidfilehost.com/?fid=95916177934541097
All I did was rename the file RUU.zip and move it to the ADB folder.
Thanks for the help.
Click to expand...
Click to collapse
put RUU.zip in fastboot/adb folder
name should be RUU.zip not RUU.zip.zip
use htc fastboot rename that to fastboot
RUU
I changed the name to just RUU, I thought the filename had to include the .zip term.
Now it tells me that it cannot open RUU.zip.
yatindroid said:
put RUU.zip in fastboot/adb folder
name should be RUU.zip not RUU.zip.zip
use htc fastboot rename that to fastboot
Click to expand...
Click to collapse
RUU
I changed the name to just RUU, I thought the filename had to include the .zip term.
Now it tells me that it cannot open RUU.zip.
jimbobly said:
RUU
I changed the name to just RUU, I thought the filename had to include the .zip term.
Now it tells me that it cannot open RUU.zip.
Click to expand...
Click to collapse
check md5
fastboot flash zip ( pressing tab will show files in fastboot folder press tab until you got ruu.zip )
Already checked the md5 and it's ok.
What is the best thing to do? Just try a new RUU?
Hello !
Can someone help me with stock rom for htc m7 asian version
OTA_M7_UL_K443_SENSE60_MR_hTC_Asia_HK_6.13.708.1-5.12.708.3_release_386271.zip
None of the zip archives which I dodnloaded works.
zip archives are damaged so bad
ratio : 4t.35.3218.29
Thanks
sony855 said:
Hello !
Can someone help me with stock rom for htc m7 asian version
OTA_M7_UL_K443_SENSE60_MR_hTC_Asia_HK_6.13.708.1-5.12.708.3_release_386271.zip
None of the zip archives which I dodnloaded works.
zip archives are damaged so bad
ratio : 4t.35.3218.29
Thanks
Click to expand...
Click to collapse
What files are you downloading and from where? The file listed above is an OTA update file not a rom. What is your "fastboot getvar all" output?
reply
alray said:
What files are you downloading and from where? The file listed above is an OTA update file not a rom. What is your "fastboot getvar all" output?
Click to expand...
Click to collapse
this is the fastboot getvar all
I found the right rom, but all archives are damaged
sony855 said:
I found the right rom, but all archives are damaged
Click to expand...
Click to collapse
Damaged? Checked md5?
hi
alray said:
Damaged? Checked md5?
Click to expand...
Click to collapse
yes when i download the archive and its damaged.. i can't extract it.
this is asian hong kong version.
4t.35.3218.29 stock rom !
and redirect me to the baidu.com for download
https://yun.baidu.com/share/link?uk=1275354262&shareid=1428103921&third=0&adapt=pc&fr=ftw
sony855 said:
yes when i download the archive and its damaged.. i can't extract it.
this is asian hong kong version.
4t.35.3218.29 stock rom !
and redirect me to the baidu.com for download
https://yun.baidu.com/share/link?uk=1275354262&shareid=1428103921&third=0&adapt=pc&fr=ftw
Click to expand...
Click to collapse
RUU are encrypted files hence why you can extract them using winzip, winrar or anything similar. And you don't need to extract the file to use it, flash with fastboot in ruu mode. To check integrity of your RUU use the Winmd5 and compare the md5 value obtained with the md5 of your download source.
alray said:
RUU are encrypted files hence why you can extract them using winzip, winrar or anything similar. And you don't need to extract the file to use it, flash with fastboot in ruu mode. To check integrity of your RUU use the Winmd5 and compare the md5 value obtained with the md5 of your download source.
Click to expand...
Click to collapse
it gives me a error
invalid sparse file format at header magi
i tried also TWRP recovery install from zip the same result. archive corrupt !
OTG cable and sd card
whats wrong with this
sony855 said:
it gives me a error
invalid sparse file format at header magi
i tried also TWRP recovery install from zip the same result. archive corrupt !
OTG cable and sd card
whats wrong with this
Click to expand...
Click to collapse
Again you CANT flash ruu using TWRP. It must be flashed using fastboot.
The error you are getting "invalid sparse file format" is because you are not using the right fastboot version. Latest RUU versions must be flashed using htc_fastboot.exe instead of the regular fastboot.exe. You can download it here. Just save it in the same folder where you already have your adb.exe, fastboot.exe and your ruu.zip
Code:
fastboot oem rebootRUU
htc_fastboot flash zip <file_name.zip>
fastboot reboot
Thanks
alray said:
Again you CANT flash ruu using TWRP. It must be flashed using fastboot.
The error you are getting "invalid sparse file format" is because you are not using the right fastboot version. Latest RUU versions must be flashed using htc_fastboot.exe instead of the regular fastboot.exe. You can download it here. Just save it in the same folder where you already have your adb.exe, fastboot.exe and your ruu.zip
Code:
fastboot oem rebootRUU
htc_fastboot flash zip <file_name.zip>
fastboot reboot
Click to expand...
Click to collapse
all done Thanks
Appreciate your help