Database Develop

SamSung Galaxy i7500~need you help !!!!

I used SamSung Galaxy i7500
because my friend gave me the wrong update.zip(for G1 >_<), the recovery model has been changed resulted the Phone can't be turn on.
Now it only can be entered the recovery model instead of entering the normal system.
I have used sdk 1.5 system.img of emulator change system which could connect to adb, and the root gets the right as well.
I have found the whole Rom system.img and update.zip
because it can not enter the system, I can not put the update.zip into the 8G memory storage . The recovery system is work in the 8Gmemory storage( /sdcard). Even, I put the update.zip into sd memery card, it still doesnt work.
I have tried 3 different methods-
using adb to put the update.zip into 8G,
"adb push update.zip /sdcard/update.zip"
but the Phone shows
Read-only file system...............
try again
"mount -o remount,rw /sdcard"
could not....
second method
"fastboot flash system system.img"
show.....
sending 'system' (86424 KB)... FAILED (remote: data too large)
img file too large.........！！
third method
use adb update.........
"fastboot update update.zip"
show.....
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
OH~~~help Me！！！
last I post wrong place , sorry！

http://forum.xda-developers.com/showthread.php?t=548759
or
http://forum.xda-developers.com/showthread.php?t=512453

Use an SD card reader to put the update on your memory card

stefan.buddle said:
Use an SD card reader to put the update on your memory card
Click to expand...
Click to collapse
I have tried
because SamSung i7500 in recovery mode
Only read 8G memory storage !!!!

I don't know how to help you, but seriously. Next time download the update yourself and make sure it's the right one. I wouldn't trust my 300€ worth phone to anyone.

SlashSpeed said:
I don't know how to help you, but seriously. Next time download the update yourself and make sure it's the right one. I wouldn't trust my 300€ worth phone to anyone.
Click to expand...
Click to collapse
johnny obvious.

stogchris81 said:
johnny obvious.
Click to expand...
Click to collapse
HEY!
That's Captain Obvious to you soldier.
Anyways, see if you can see it from ADB at any point, if so, you can probably install a ROM from there or at least do something to recover it.

monerlin said:
I used SamSung Galaxy i7500
because my friend gave me the wrong update.zip(for G1 >_<), the recovery model has been changed resulted the Phone can't be turn on.
Now it only can be entered the recovery model instead of entering the normal system.
I have used sdk 1.5 system.img of emulator change system which could connect to adb, and the root gets the right as well.
I have found the whole Rom system.img and update.zip
because it can not enter the system, I can not put the update.zip into the 8G memory storage . The recovery system is work in the 8Gmemory storage( /sdcard). Even, I put the update.zip into sd memery card, it still doesnt work.
I have tried 3 different methods-
using adb to put the update.zip into 8G,
"adb push update.zip /sdcard/update.zip"
but the Phone shows
Read-only file system...............
try again
"mount -o remount,rw /sdcard"
could not....
second method
"fastboot flash system system.img"
show.....
sending 'system' (86424 KB)... FAILED (remote: data too large)
img file too large.........！！
third method
use adb update.........
"fastboot update update.zip"
show.....
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
OH~~~help Me！！！
last I post wrong place , sorry！
Click to expand...
Click to collapse
Try the I7500 section at Android Community someone might be able to help.

wow ur screwed man. i would just send it in.

Moved to Q&A
Post in the right forums
Last warning

hi,
not sure if you solved the problem, but maybe it will help...
I thought I just bricked my phone as I updated it using wrong update.zip file that wasn't meant to be for Galaxy. After that the phone didn't turn on at all.
http://darkforestgroup.com/forum/index.php?topic=764.msg5747
there you can find how to flash your phone using odin. What's what I've done. the only difference is that I
*put tick in one package
*didn't specify the path to Boot, Phone, PDA, CSC
*specify path to ONE PACKAGE and link that to I7500XXIH8-PDA-CL53973-REV5(VIA).tar
click start
and my phone is working now.
It's not root, but it can be done again.
Hope that helps
good luck.
PS. you can download firmwre from samsung-firmware.webs.com if you havent got one.

[How-To] Unbrick HTC Tattoo(CLICK) after bad recovery

Hello all,
PROBLEM
I while ago I had flashed my tattoo with a ROM that came with ROMmanager (wich is able to flash a custom recovery within Android) and the result was that my recovery was corupted and I couldn't flash another rom anymore, since I have a locked SPL.
POSSIBLE SOLUTION
What you can try is to download the latest RUU for your device and try to update the tattoo. However, I know that alot of people will get the error code 170 or 171: USB not connected. Don't panic, I have found after so many days of searching the solution to this problem.
WHAT WILL YOU NEED ?
The correct RUU for your device forum.xda-developers.com/showthread.php?t=591746"]
Procmon, this is a Process Monitor. You will need this to extract the rom.zip file from the RUU. technet.microsoft.com/en-us/sysinternals/bb896645.aspx"]
The android SDK and ADB set up correctly ( just search it on Google, and you'll find it).
LETS GET STARTED
The first thing you'll need to do is to open your prefered RUU you just downloaded from the link above, and wait till it says "welcome to the htc update..."
Just click next once, and leave the RUU open.
NOTE: The RUU can't be minimalized, so I sugest to slide it down to the taskbar.
Next, open the Procmon application, it will show you all open tasks (don't start searching like a fool, there are too many processes running to find the file we're searching for!).
Still in the Procmon, search in the for a filter button (the sixth button, white with a bleu thing above it), and click on it, now there will popup a screen.
Change the first tab (Architecture) to Path, and the seccond one (is) to contains, then in the box type rom.zip, and leave the Include tab how it is.
Now press add, and then press apply and ok. And search to one of the path's that ends with rom.zip in the list.
Right-click on it, and select Jump To, now you will see the rom.zip file in a temporary windows folder. Copy the rom to whereever you want (e.g. on your desktop) and close the RUU and Process Monitor.
Now, we have found and extracted the original rom that comes with the tattoo, so we're ready to flash this rom manually to our tattoo:
Open up command prompt, and cd to adb (where you have installed the SDK).
Now connect the tattoo to your pc and make sure its recognized under ADB Devices in device manager in windows.
Go back to the command prompt, and type
Code:
adb devices
If ADB is setup how it should, then you'll see the tattoo there (a long number)
Now type:
Code:
adb shell
adb reboot oem-78
The tattoo is now going to reboot in RUU mode, so we can do fastboot commands. (You will see only HTC logo on the tattoo)
Copy the rom.zip you extracted from the RUU to the tools folder of your SDK.
Now type:
Code:
fastboot flash zip rom.zip
(rom.zip is the name of your extracted rom, if you renamed it, then use the name of your rom).
Wait for the flashing procedure to finish, you'll see some message of completed or done or something, and unplug your tattoo, it should be in the bootloader screen (with 3 skateboards) and in the middle you should see RUU in orange.
Reboot your device, and hold the HOME + END button till the tattoo screen comes up, and wait till you see a screen with an exlimation mark, now shortly press on the HOME+END butten and you should be able to see the recovery menu now!
OPTIONAL
Redoo the 'root the tattoo in one click', and you'll get a custom recovery and root acces. IF YOU DO SO, I STRONGLY RECOMMEND YOU TO FLASH ANOTHER CUSTOM RECOVERY TO THE TATTOO, JUST SEARCH ONE ON THE FORUM HERE AND YOU'LL ALSO FIND HOW TO DO SO TROUGH ADB COMMANDS.
Once you have a custom recovery, you can flash rom's again from the recovery.
Hope this tread was helpfull !

Very usefull tnx
Sent from my Tattoo using XDA App

Now I'm even less afraid of flashing my a.. of. :-D
Thanx man!
Sent from my Tattoo using Tapatalk

MOdel ID checl Failed
Hi ,
I am getting this error
C:\androidtools\tools>fastboot flash zip "C:\My Folder\Datas\Mobile\Tattoo\rom.z
ip"
sending 'zip' (88968 KB)... OKAY [ 12.422s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 40.079s
C:\androidtools\tools>

soulaiman said:
Hello all,
PROBLEM
I while ago I had flashed my tattoo with a ROM that came with ROMmanager (wich is able to flash a custom recovery within Android) and the result was that my recovery was corupted and I couldn't flash another rom anymore, since I have a locked SPL.
POSSIBLE SOLUTION
What you can try is to download the latest RUU for your device and try to update the tattoo. However, I know that alot of people will get the error code 170 or 171: USB not connected. Don't panic, I have found after so many days of searching the solution to this problem.
WHAT WILL YOU NEED ?
The correct RUU for your device forum.xda-developers.com/showthread.php?t=591746"]
Procmon, this is a Process Monitor. You will need this to extract the rom.zip file from the RUU. technet.microsoft.com/en-us/sysinternals/bb896645.aspx"]
The android SDK and ADB set up correctly ( just search it on Google, and you'll find it).
LETS GET STARTED
The first thing you'll need to do is to open your prefered RUU you just downloaded from the link above, and wait till it says "welcome to the htc update..."
Just click next once, and leave the RUU open.
NOTE: The RUU can't be minimalized, so I sugest to slide it down to the taskbar.
Next, open the Procmon application, it will show you all open tasks (don't start searching like a fool, there are too many processes running to find the file we're searching for!).
Still in the Procmon, search in the for a filter button (the sixth button, white with a bleu thing above it), and click on it, now there will popup a screen.
Change the first tab (Architecture) to Path, and the seccond one (is) to contains, then in the box type rom.zip, and leave the Include tab how it is.
Now press add, and then press apply and ok. And search to one of the path's that ends with rom.zip in the list.
Right-click on it, and select Jump To, now you will see the rom.zip file in a temporary windows folder. Copy the rom to whereever you want (e.g. on your desktop) and close the RUU and Process Monitor.
Now, we have found and extracted the original rom that comes with the tattoo, so we're ready to flash this rom manually to our tattoo:
Open up command prompt, and cd to adb (where you have installed the SDK).
Now connect the tattoo to your pc and make sure its recognized under ADB Devices in device manager in windows.
Go back to the command prompt, and type
Code:
adb devices
If ADB is setup how it should, then you'll see the tattoo there (a long number)
Now type:
Code:
adb shell
adb reboot oem-78
The tattoo is now going to reboot in RUU mode, so we can do fastboot commands. (You will see only HTC logo on the tattoo)
Copy the rom.zip you extracted from the RUU to the tools folder of your SDK.
Now type:
Code:
fastboot flash zip rom.zip
(rom.zip is the name of your extracted rom, if you renamed it, then use the name of your rom).
Wait for the flashing procedure to finish, you'll see some message of completed or done or something, and unplug your tattoo, it should be in the bootloader screen (with 3 skateboards) and in the middle you should see RUU in orange.
Reboot your device, and hold the HOME + END button till the tattoo screen comes up, and wait till you see a screen with an exlimation mark, now shortly press on the HOME+END butten and you should be able to see the recovery menu now!
OPTIONAL
Redoo the 'root the tattoo in one click', and you'll get a custom recovery and root acces. IF YOU DO SO, I STRONGLY RECOMMEND YOU TO FLASH ANOTHER CUSTOM RECOVERY TO THE TATTOO, JUST SEARCH ONE ON THE FORUM HERE AND YOU'LL ALSO FIND HOW TO DO SO TROUGH ADB COMMANDS.
Once you have a custom recovery, you can flash rom's again from the recovery.
Hope this tread was helpfull !
Click to expand...
Click to collapse
If this post does what it says it does, it should maybe be made a sticky so that everyone who bricks their device knows EXACTLY what to do to fix it.........

This metod work,excelent

nkaderfe said:
Hi ,
I am getting this error
C:\androidtools\tools>fastboot flash zip "C:\My Folder\Datas\Mobile\Tattoo\rom.z
ip"
sending 'zip' (88968 KB)... OKAY [ 12.422s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 40.079s
C:\androidtools\tools>
Click to expand...
Click to collapse
Hmm, seems like adb can't verify the model of your phone. Try a different ROM or Reinstall the sdk tools. If that doesn't make sense, then try to recreate your goldcard, but I don't think that that would make some difference at all.

soulaiman said:
WHAT WILL YOU NEED ?
The correct RUU for your device forum.xda-developers.com/showthread.php?t=591746"]
Procmon, this is a Process Monitor. You will need this to extract the rom.zip file from the RUU. technet.microsoft.com/en-us/sysinternals/bb896645.aspx"]
The android SDK and ADB set up correctly ( just search it on Google, and you'll find it).
Click to expand...
Click to collapse
Well, the rom.zip is always located in %tmp% (Start->run->%tmp% and then enter). Search the folders and somewhere you will find the rom.zip then...procmon is a little over-engineered
nkaderfe said:
Hi ,
I am getting this error
C:\androidtools\tools>fastboot flash zip "C:\My Folder\Datas\Mobile\Tattoo\rom.z
ip"
sending 'zip' (88968 KB)... OKAY [ 12.422s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 40.079s
C:\androidtools\tools>
Click to expand...
Click to collapse
Then you have a vendor specific build - Vodafone? Orange? You have to flash this in order to get the flashing started...
/EDIT: Did u create a goldcard?

Getting stuck.
When I type adb shell it responds with: -exec '/system/bin/sh' failed: No such file or directory <2> -
adb reboot oem-78
fastboot flash zip rom.zip
<waiting for device>
My phone is plugged in but doesn't want to boot past tattoo screen.
Plz help if you know the problem.

timlambo said:
Getting stuck.
When I type adb shell it responds with: -exec '/system/bin/sh' failed: No such file or directory <2> -
adb reboot oem-78
fastboot flash zip rom.zip
<waiting for device>
My phone is plugged in but doesn't want to boot past tattoo screen.
Plz help if you know the problem.
Click to expand...
Click to collapse
Hi,
You have to boot your phone first in bootloader mode, to do so you have to pull out battery, put it back in, hold in the down volume button while pressing power, it wil bring you in a white screen with at the bottom three androids on skeatboards.
Hope this helps you.

soulaiman said:
Hi,
You have to boot your phone first in bootloader mode, to do so you have to pull out battery, put it back in, hold in the down volume button while pressing power, it wil bring you in a white screen with at the bottom three androids on skeatboards.
Hope this helps you.
Click to expand...
Click to collapse
I know. That is where I were. I think the problem were with my rom, found old backup om pc and restored to that, but now it is working again.
Thanks for the help.

[REQ] 10.1 System Dump (.img)

Hi,
Could someone please dump a system image for the 10.1? It's reeeealy easy
There are a few soft-bricks already due to people flashing the wrong image or to the wrong partition ( you know who you are, people! ) and you would be doing them a massive favour if you did.
If you already have busybox, all you have to do is run this:
Code:
dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Then you can pick it up the system.img from /sdcard
Code:
adb pull /sdcard/system.img
ZIP it and upload it somewhere ( Dropbox ) and you're done!
TIA
BC

Http://droidbasement.com/galaxy/sys-backup
The system_extra backup contains extra stuff (from the 'tools' compilation).

Thanks. There are a couple of people who will really appreciate that
OT: I just repacked your su/busybox update with the boot.img from the Voda 10.1 and it works fine. Link to the Voda boot.img is here

Would it be possible to get the original system image without the extra tools? I am trying to flash this image however I keep getting a remote error when I do so. Could it have something to do with the fact that this image is 600MB compared to other system images that are around 200 MB like for the gt 10.1v? Thanks again for posting it.

the extra stuff is not making it 600mb (maybe 10-20). It is quite big on the IO.
In order to fastboot flash it you must have an unlocked bootloader to do so (which in unlocked by default on the IO).

Ok so my bootloader is unlock however every time I try flashing this image i get the following:
sending 'system' (591872 KB)...
FAILED (remote: (00000006))
finished. total time: 0.002s
I am able to flash other system images no problem however, this one seems to be giving me some issues. Any other ideas to flash this image successfully? Thanks.

nadewad said:
Ok so my bootloader is unlock however every time I try flashing this image i get the following:
sending 'system' (591872 KB)...
FAILED (remote: (00000006))
finished. total time: 0.002s
I am able to flash other system images no problem however, this one seems to be giving me some issues. Any other ideas to flash this image successfully? Thanks.
Click to expand...
Click to collapse
ill retake the dump and upload it. ill do it tonight. maybe some corruption ocurred, etc.

It might be the same trick where you have to create a sparse ext4 image instead of ripping the image straight, because fastboot transfers the entire image in RAM before flashing it...
Try
Code:
make_ext4fs -l 512m -s /sdcard/system.img /system

If anyone has created a system image but isn't quite sure if it is the correct one, I'll be glad to try it out as I am one of those people who soft bricked their device. Just PM me and I'll be more than happy to flash my device and verify the stability of the system image. Thanks.
Nader

bump? Did anyone end up getting a system image? Thanks.
Nader

Ok so I was able to get a hold of another system image however, it still failed with the same error.
ydaraishy mentioned something about using make_ext4fs to make a sparse image? How is this done exactly? Is this through the adb shell or is this a separate tool that can be used on a linux machine. Any help on bringing my device back to life would be greatly appreciated. Thanks.

nadewad said:
Ok so I was able to get a hold of another system image however, it still failed with the same error.
ydaraishy mentioned something about using make_ext4fs to make a sparse image? How is this done exactly? Is this through the adb shell or is this a separate tool that can be used on a linux machine. Any help on bringing my device back to life would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Run it on the device instead of using dd on the device.

ydaraishy said:
Run it on the device instead of using dd on the device.
Click to expand...
Click to collapse
He has a soft-bricked device so that's not an option unfortunately.
You can do a MD5 checksum of the file and get pershoot to check it against the original.
Otherwise, in the mean time, you can try this tool:
http://www.diskinternals.com/download/
You want the tool called "Linux Reader 2.0". It says it can only read ext2 and ext3, but I just tried it on my 10.1v system image which I created using the same method as pershoot, and it works fine.
...and see if you can mount it in Windows. If you can, the image is (probably) OK.

bcmobile said:
He has a soft-bricked device so that's not an option unfortunately.
Click to expand...
Click to collapse
Well, obviously, someone _else_ has to provide that image from a working device.

Same error here, while trying to flash the system.img. Any alternatives?
Thanks,
Eduardo.

I just received another system image from a friend of mine who created it using make_ext4fs. It does flash successfully however, it still leaves my device in a boot loop. Whats the button combination to get the device into recovery mode?
I find it funny that the boot, recovery and system images for the galaxy tab 10.1v actually work and the device runs. Although the accelerometer, camera and usb don't work though.
Eduardo if you would like, you can PM me and I can share with you the dropbox folder of the system image that actually flashed to see if it would work on your device.
I think at this point I may just throw in the towel and send my device back to Samsung to get repaired :/
Thanks to everyone on the xda forums who tried helping me out. You guys are truly awesome

nadewad said:
I just received another system image from a friend of mine who created it using make_ext4fs. It does flash successfully however, it still leaves my device in a boot loop. Whats the button combination to get the device into recovery mode?
I find it funny that the boot, recovery and system images for the galaxy tab 10.1v actually work and the device runs. Although the accelerometer, camera and usb don't work though.
Eduardo if you would like, you can PM me and I can share with you the dropbox folder of the system image that actually flashed to see if it would work on your device.
I think at this point I may just throw in the towel and send my device back to Samsung to get repaired :/
Thanks to everyone on the xda forums who tried helping me out. You guys are truly awesome
Click to expand...
Click to collapse
Samsung may charge you for the repair
Before you send it back, just have one more go at flashing the boot.img which smaskell provided from here. Just do a:
Code:
fastboot flash boot boot.img
The boot loop may be due to a different (incompatible) kernel if you still have the boot partition from the 10.1v
Failing that, if you're still up for it, do a:
Code:
adb logcat > %userprofile%\desktop\logcat-out.txt
...then open the locgat-out.txt file on your desktop and post the contents here or just zip and attach the file. That might give us something to work with

I am also not able to flash this system.img file. I get the same error.

I did remember to flash the boot image of the 10.1 over the 10.1v. However, even when the device is booting up I still can't get access to the adb shell. Any ideas as to why I cannot access the adb shell?
I did notice though that when I had typed in:
fastboot getvar product
It had returned GT-P7100 which is the product number for the Galaxy Tab 10.1v, however the Galaxy Tab 10.1 has the product number GT-P7510.
Could this be because I had accidentally flashed the 10.1v rom or that these devices both use the same version of fastboot etc?

nadewad said:
I did remember to flash the boot image of the 10.1 over the 10.1v. However, even when the device is booting up I still can't get access to the adb shell. Any ideas as to why I cannot access the adb shell?
I did notice though that when I had typed in:
fastboot getvar product
It had returned GT-P7100 which is the product number for the Galaxy Tab 10.1v, however the Galaxy Tab 10.1 has the product number GT-P7510.
Could this be because I had accidentally flashed the 10.1v rom or that these devices both use the same version of fastboot etc?
Click to expand...
Click to collapse
My tablet is showing P7100 as well. I tested with my employee's GT LE, and it shows the same. So, this is not the problem...
adb is not accessible to me as well.

[Q] TWRP flash via Fastboot failing

I just took my good ol' Streak 7 to update it as I see some nice JB action here. But as I understand any manipulation to be made needs TWRP to be present on device. As GooManager wasn't instaling recovery the simple way, I decided to download image and flash it via Fastboot. Yet every single time it failed to do so.
Code:
fastboot flash recovery twrps.img
sending 'recovery' (4822 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
I was flashing the latest (2.6.x) version. Also my device is empty atm (had 3.2, now has nothing). Custom Recovery is CWR 5.
Need help to flash the TWRP and begin using JB roms.

YOu need to use the NVflash pack, which write the recovery.img to the correct partition at a lower level than fastboot.
The error you are seeing is due to Dell screwing things up and resulting in fastboot being able to read the partitions name value.

giveen said:
YOu need to use the NVflash pack, which write the recovery.img to the correct partition at a lower level than fastboot.
The error you are seeing is due to Dell screwing things up and resulting in fastboot being able to read the partitions name value.
Click to expand...
Click to collapse
Seems that all download links for nvflash pack for DS7 are now dead both on xda and google.

[Q] Can't Boot Up Stock ROM. Stuck

*** 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)