SamSung Galaxy i7500~need you help !!!! - G1 Q&A, Help & Troubleshooting

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.

Related

help, update, now stuck on android flash screen(fastboot?)

can anyone tell me if they know how to push a update through fastboot? i just did a update and nandroid isnt working, so can anyone provide help on doing a push through fastboot?
errors i get trying to re apply update.zip of jf1.5
the original rc29file? what should i do?
cmd error
Code:
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Kiefer Anderson>cd desktop
C:\Users\Kiefer Anderson\Desktop>cd fastboot
C:\Users\Kiefer Anderson\Desktop\fastboot>fastboot flashall update.zip
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
C:\Users\Kiefer Anderson\Desktop\fastboot>fastboot update update.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.img'
error: update package missing system.img
C:\Users\Kiefer Anderson\Desktop\fastboot>fastboot update {update.zip}
error: failed to load '{update.zip}'
C:\Users\Kiefer Anderson\Desktop\fastboot>fastboot update update.zip
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
C:\Users\Kiefer Anderson\Desktop\fastboot>fastboot update {update.zip}
error: failed to load '{update.zip}'
C:\Users\Kiefer Anderson\Desktop\fastboot>
I tried two different update files, one i added the two .txt files then it asks for the img files, i dont get it.. anyone HELP plzzzzz, if you help ill donate money to your paypal i swear
why dont you just do it through the recovery ?
To mount the sdcard in recovery type the following in adb
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
thanks to JesusFreke for figuring this out.
dpgc213 said:
why dont you just do it through the recovery ?
Click to expand...
Click to collapse
i dont have anything to connect my phone to another usb device..
im not very good at this stuff, but for some reason im stuck at the android loading screen, i think theres something wrong with the 2nd loading screen, idk what to do, i tried doing recovery with nandroid but i get an error, then i tried re apllying the update.zip file and still something wrong, im stuck and need help
so to do recovery, i do home + end button, which brings up everything right? alt stuff..
so what do i do from there, im sorry, but i fyou help me through this, ill do anything.. how do i enter those commands in the recovery?
1. fastboot doesn't work on recovery update zips. It is used on images made from nandroid backup (or img files made from building the source). In other words, fail.
2. Dev forum is not for troubleshooting.
u can mount your phone to your computer in recovery mode but using the code in my above post
dpgc213 said:
u can mount your phone to your computer in recovery mode but using the code in my above post
Click to expand...
Click to collapse
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Kiefer Anderson>echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mas
s_storage/lun0/file
The system cannot find the path specified.
C:\Users\Kiefer Anderson>
still cant figure it out.. im in recovery mode, i did that echo thing, but yeh..
when i had my phone working and connected, it would connect as f:/ sooo what do i do
press alt x and then type that in on the phone
dpgc213 said:
press alt x and then type that in on the phone
Click to expand...
Click to collapse
hmm didnt work, i just get a
"
/ #
"
didnt work i dont think :/
i dont see my sdcard connected, ill try again
not sure then sorry, u sure u copied exactly how it is? or maybe u hav to type su 1st, not sure tho
dpgc213 said:
not sure then sorry, u sure u copied exactly how it is? or maybe u hav to type su 1st, not sure tho
Click to expand...
Click to collapse
uhm in device manager its connected as HTC dream instead of mass usb
gonna try both thanks for helping, if i figure this out, ill be contacting you
gonna cry now
lol sh: su: not found
so su not working idk
ok i got my dads phone, gonna try re installing jf 1.5 i hope it works :/
EDIT update
im sorry to bother you guys, i just want to say thanks for trying to help, withouut you i would be no where, i might of just went in my closet and cryed myself to death..
used my dads nokia to help
thanks guys
Can i Mount Nexus s without enabling USB debugger from Phone(as I cant go past google logo on nexus s)
jashsu said:
1. fastboot doesn't work on recovery update zips. It is used on images made from nandroid backup (or img files made from building the source). In other words, fail.
2. Dev forum is not for troubleshooting.
Click to expand...
Click to collapse
So you can only use the .img files from AndroidSDK to update in fastboot? Im trying to fix an HTC G2 Vision (T-Mobile) for a friend, it doesnt boot and is NOT rooted, it will not seem to accept any official T-Mobile update or any i try to push or flash through fastboot. I have the nandroid backup images from another HTC G2 Vision (both phones stock rom) as well as the official T-Mobile updates yet they wont flash through fastboot or Hboot, ADB wont recognize it,fastboot will, i get failed to verify whole-file signature on most updates, but have gotten Main Version is older! mesage from 1 of the OTA updates i got from T-Mobile, and one that said something like failed to stat sytem/build.prop no such file or directory E:error in /tmp/sideload/package.zip (status7) everytime i boot her phone into recovery i get E:set_bootloader_message_block: emmc_read_data_fail! I thought if i could reflash bootimg or hboot or flashall i could fix it? am i wrong in this aassupmtion? I have reached out over half a dozen sites/forums for help and have not got any real help, if anyone can assist id appreciate it, u can alway pm me instead of dirtying the thread, Thank you!
C:\Users\roger>C:\AndroidSDk\tools\fastboot flash boot C:\AndroidSDK\tools\boot.img
sending 'boot' (2560 KB)...
OKAY [ 0.446s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.770s
IVXX said:
So you can only use the .img files from AndroidSDK to update in fastboot? Im trying to fix an HTC G2 Vision (T-Mobile) for a friend, it doesnt boot and is NOT rooted, it will not seem to accept any official T-Mobile update or any i try to push or flash through fastboot. I have the nandroid backup images from another HTC G2 Vision (both phones stock rom) as well as the official T-Mobile updates yet they wont flash through fastboot or Hboot, ADB wont recognize it,fastboot will, i get failed to verify whole-file signature on most updates, but have gotten Main Version is older! mesage from 1 of the OTA updates i got from T-Mobile, and one that said something like failed to stat sytem/build.prop no such file or directory E:error in /tmp/sideload/package.zip (status7) everytime i boot her phone into recovery i get E:set_bootloader_message_block: emmc_read_data_fail! I thought if i could reflash bootimg or hboot or flashall i could fix it? am i wrong in this aassupmtion? I have reached out over half a dozen sites/forums for help and have not got any real help, if anyone can assist id appreciate it, u can alway pm me instead of dirtying the thread, Thank you!
C:\Users\roger>C:\AndroidSDk\tools\fastboot flash boot C:\AndroidSDK\tools\boot.img
sending 'boot' (2560 KB)...
OKAY [ 0.446s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.770s
Click to expand...
Click to collapse
http://forum.xda-developers.com/forumdisplay.php?f=508
try the G2 forum
Make a new topic there

Flash w/out sdcard?

May have been asked before, but I tried searching and didnt find much luck.
I think my SDCard slot finally gave up, it just will not be read (tried two different 8gb cards that both worked fine on the computer). On Cyan 4.2.9.1.
Anyway, is there a way to flash the phone without the sdcard? I was trying to think how that would be possible, but I think its not right?
Just looking for a quick def. answer so I can know if i need to go phone hunting . Or do something different , which would be much better.
Appreciate it .
Happy holidays btw
You should be able to using ADB, not sure the command lines for that. As well, you might want to try getting a can-o-air and blowing out the SD card slot on your phone.
Lastly, this is the wrong section, should of been posted in Q&A.
pjcforpres said:
You should be able to using ADB, not sure the command lines for that. As well, you might want to try getting a can-o-air and blowing out the SD card slot on your phone.
Lastly, this is the wrong section, should of been posted in Q&A.
Click to expand...
Click to collapse
I didnt really think of adb, yeah that might work. Maybe someone knows them?
Maybe
adb shell recovery flash location/zip ?
Tried the canned air, didnt change. Good thinking though.
And lastly, I did debate which place, but I was thinking I saw a utility here or I am looking for the command lines and thought maybe alittle more technical than a general question? It will fall shortly anyway (hopefully after the commands ) or get moved/deleted.
If someone nandroided, they could just send you their system.img and you could fastboot it onto the phone. Provided you have the engineering/danger SPL.
persiansown said:
If someone nandroided, they could just send you their system.img and you could fastboot it onto the phone. Provided you have the engineering/danger SPL.
Click to expand...
Click to collapse
Thats a pain, and I dont think there are many of those out there...
No adb commands? Ive been searching but it seems scarce
EDIT:
Ok I tried my idea anyway,
adb shell recovery flash update.zip
And it just hangs (no errors though)...probably missing something?
Are you able to warranty your phone for the bad SDCard Reader??
If so, I started this thread and came up with an answer, but it will bring you back to fully stock cupcake
http://forum.xda-developers.com/showthread.php?t=560254
Search for a webpage , how to root/flash/hack g1. It's has everything you need.
You need to go into fastboot
Fastboot update update.zip. somthing like that or do like the website shows 1 at a time.
There might be an adb for it, but I've never used it. Fastboot only option I believe.
bildo said:
Search for a webpage , how to root/flash/hack g1. It's has everything you need.
You need to go into fastboot
Fastboot update update.zip. somthing like that or do like the website shows 1 at a time.
There might be an adb for it, but I've never used it. Fastboot only option I believe.
Click to expand...
Click to collapse
That is the better answer, thanks for continuing. If you just left that first sentence I would have said re-read my problem, I cannot use my sdcard (the normal way rom is flashed).
As for the fastboot, I will look into that. I appreciate it, thanks.
Im getting
No android-info.txt
No android-product.txt
In the package when i try to do this command while in fastboot:
fastboot update update.zip
I found android-info in the update file from htc, but I cannot resign right now. Im also guessing it will still yell about the android-product.txt anyway, so any ideas where to get that file?
If all you're trying to do is flash a .img (system.img, userdata.img, recovery.img) and you have a developer, or hardspl, you can flash using fastboot.
Code:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
flashing an update.zip is only possible through recovery mode, but can still be accomplished using the /cache partition
Code:
adb push update.zip /cache
and you should be able to do the update from cache.
haykuro said:
flashing an update.zip is only possible through recovery mode, but can still be accomplished using the /cache partition
Code:
adb push update.zip /cache
and you should be able to do the update from cache.
Click to expand...
Click to collapse
Using you're SPL, is it still possible to place an update.zip into /cache with the partition table having been re-written??''
I'm assuming yes, since you jumped in and posted that method, I was just curious
jackslim said:
Using you're SPL, is it still possible to place an update.zip into /cache with the partition table having been re-written??''
I'm assuming yes, since you jumped in and posted that method, I was just curious
Click to expand...
Click to collapse
Well you're cache partition should have 30720K (about 30MB)
the last cyanogen rom was 37 MB =[
my other recommendation for you is to push the updates to your sdcard through your phone. (just re-read your post and noticed the SD card is functional in your phone)
Code:
adb push update.zip /sdcard/update.zip
then just proceed as usual.
@theslam08
Your signature say's your using the "Danger SPL" Judging by that you could reflash your spl from fastboot to the hard spl
Code:
fastboot flash hboot spl.bin
Then use the method described above by Haykuro pushing updates to /cache with adb
Thanks for the responses guys .
As for pushing to sdcard while in phone, thats where the problem remains. The sd reader IN the phone is busted it would seem as it just says no sd card found (cannot mount) with 3 different cards I tried (all working on the computer).
Ok so if I flash back the spl will I have more than 40mb free on the cache partition? Because yeh, the most recent update from CM is ~40mb, so it wont fit currently.
ANd once pushed to /cache, how would I go about doing the actual update? You said "you should be able to do the update from the cache part.), not sure how, just give the location?
console: flash update /cache/update.zip ?
Thank you.
theslam08 said:
Thanks for the responses guys .
As for pushing to sdcard while in phone, thats where the problem remains. The sd reader IN the phone is busted it would seem as it just says no sd card found (cannot mount) with 3 different cards I tried (all working on the computer).
Ok so if I flash back the spl will I have more than 40mb free on the cache partition? Because yeh, the most recent update from CM is ~40mb, so it wont fit currently.
ANd once pushed to /cache, how would I go about doing the actual update? You said "you should be able to do the update from the cache part.), not sure how, just give the location?
console: flash update /cache/update.zip ?
Thank you.
Click to expand...
Click to collapse
i forgot the exact command to force a boot-recovery and have it flash through cache (the traditional method)
but if your on cyanogen's recovery you can do
Code:
adb shell mount -t yaffs2 /dev/block/mtdblock4 /sdcard
this should mount cache into /sdcard, allowing you to flash.
haykuro said:
i forgot the exact command to force a boot-recovery and have it flash through cache (the traditional method)
but if your on cyanogen's recovery you can do
Code:
adb shell mount -t yaffs2 /dev/block/mtdblock4 /sdcard
this should mount cache into /sdcard, allowing you to flash.
Click to expand...
Click to collapse
Excellent, that seemed to be the trick (after going back to HSPL because yeah, I didnt have enough room with haykuro's). Though some bugs with that.
I got it to copy once after making that partition mount, and I was able to see the update file. I updated, and everything went well (even though I wondered how in the middle of the update it says formatting cache, yet it still worked).
Now, I went to put on a theme file and it says out of room. I hit 'update from sdcard' in recovery and it says E: No zip files found or something like that, just no files. So if it gets 'wiped' how is there no space? Is there a manual format I should do?
And I dont think this has happened to anyone yet, so thanks for going through this , im sure others down the road will find it helpful.
Not to get off-topic or picky about anything, but having the phone without an SD card being able to be read seems kind of pointless.
After all, you won't be able to run A2SD, or move the cache. The phone's going to run as if it was "stock."
akapoor said:
Not to get off-topic or picky about anything, but having the phone without an SD card being able to be read seems kind of pointless.
After all, you won't be able to run A2SD, or move the cache. The phone's going to run as if it was "stock."
Click to expand...
Click to collapse
Not being blunt but, thats the point. I have 'no' other choice right now, I cannot get a new phone for a while (and warranty is over, its a yr and 3 months since pur)
I obviously know I cannot use A2SD, so I need to get it to run 'stock', and thats proving to be a trick (stock but not). I almost have it, but cache doesnt seem to wipe on its own, which is the new problem. Once that is cleared, then I should be all set .
theslam08 said:
Not being blunt but, thats the point. I have 'no' other choice right now, I cannot get a new phone for a while (and warranty is over, its a yr and 3 months since pur)
I obviously know I cannot use A2SD, so I need to get it to run 'stock', and thats proving to be a trick (stock but not). I almost have it, but cache doesnt seem to wipe on its own, which is the new problem. Once that is cleared, then I should be all set .
Click to expand...
Click to collapse
Ah, okay - now it makes sense. I didn't understand the purpose at first.

[Q] Stuck at Fastboot usb screen

I installed the new zen2.2 rom today and had a working clockwork recovery. Here is where I went stupid, I downloaded the kernel update but rather than running it via update.zip I flashed it using flash_image recovery via adb shell.
Now my phone comes up to fastboot usb and never goes any further, been waiting hours! I have tried booting into fastboot/hboot and it does nothing. I have booted to hboot before successfully but now nothing.
If I run adb devices it shows no devices. If I run fastboot devices it does show my device.
Whats next?
If you cant get into fastboot and you cant get into recovery then you m ight have bricked your phone. Did you try a hard reset?
How do you do a hard reset?
Here is a little more info. I believe it does actually get to fastboot usb as it says so on the top left of the screen and I can run fastboot commands but most commands say error. If I do fastboot devices it shows the device connected.
Little more info - when I try doing a back to basics RUU update it connects, shows the rom version, starts the update and then at about 88% every time, it goes right to a error [171] usb connection error. So its communicating but never finishes. Tried with the sprint RUU stock rom, another that was built by one of the devs in the Hero community and still both do the same.
I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.
ASimmons said:
I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.
Click to expand...
Click to collapse
Right, I also believe that if I could get a recovery back on the phone I would be good as gold! Here is the problem though. I have tried running "fastboot flash recovery [recovery.img]" but it gives me the below error. I have tried multiple key combination's to get into hboot but nothing works. If anyone has any other key combination's I could try please let me know!
Code:
D:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (3720 KB)... FAILED (remote: not allow)
finished. total time: 0.001s
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Yeah I think he knows now not to flash kernels... atleast I hope so. +1 for your post.
unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Click to expand...
Click to collapse
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.
casualonejp said:
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.
Click to expand...
Click to collapse
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
edit: sorry i dont think fastboot will see the sdcard but try anyways.
ASimmons said:
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
Click to expand...
Click to collapse
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.
casualonejp said:
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.
Click to expand...
Click to collapse
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.img
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.
ASimmons said:
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.fimg
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.
Click to expand...
Click to collapse
Negative on the fastboot commands. Also did have a nandroid but on old sdcard which died. I read that I could use anothers nandroid backup but I am currently trying to find one to test.
Tried doing the RUU method with stock/custom roms and it gets as far as seeing the image but when I click on "ok" to start the recovery, it goes to "waiting on bootloader" and then at 88% it errors to a 171 error stating usb connection error.
I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.
ASimmons said:
I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.
Click to expand...
Click to collapse
Ya I have been researching non stop all yesterday evening and today so far all day. I just cant get it to do anything. I will keep researching though. Thanks
Did you fix this yet?
Anyone figure this out yet...I have the same issue and haven't been able to resolve it yet. Still with a brick at this point!
Hey guys,if your stuck at fastboot(As I just was tonight), try in your CMD(if running Windows) fastboot reboot-bootloader or fastboot reboot to reboot as normal,I'll try to keep you updated to get through all this. I am at a loss right now but searching for answers first before i go about asking.
Answer to MY problem(maybe not yours): OK,I have come to the conclusion here tonight that I had a soft brick. What I did was remove the battery,put the battery back in,restarted the phone normally,then I ran the HTC Sprint Hero MR 2.27.651.6 on my computer(essentially restoring back to unrooted factory settings). This worked for me. I am totally refreshed and happy that my phone is ok and all. Yes I may have to go back and re-root but this only take me bout 20 minutes most to root and re-flash a CyanMod7 Nightly Rom. Hope my info can help out somebody!

[Q] Cant flash ClockworkMod Recovery (cannot open for read: No such file or directory

When i type the dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096 to flash over the clockworkmod, into my command promt it says 'cannot open for read: No such file or directory' and i dont know what im doing wrong.
I mean everything else seemed to workout fine. i downloaded the recovery image it said to save it but it was already saved to my computer after i downloaded it so i dont know if this could be the problem.
Then i used the adb push recovery.img/data command to push the recovery image to my phone, i think this might be where i messed up. After i put in the command a long list of text pops up on the command prompt. It starts out showing 'Android Debug Bridge version 1.0.26' then is followed by a long list of adb commands. Idk know if this is what its supposed to show.
Next i did the adb shell, su, dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096 command and that worked fine it said 2560+0 records out, 2560+0 records in 10485760 bites transfered in 0.413 secs and i actually found that file on my sdcard. So i think i did that right.
Next i tried to use the command 'dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096' and like i said earlier it just says 'cannot open for read: No such file or directory'
Lastly i tried the rm /data/recovery.img command and it said rm failed for /data/recovery.img, No such file or directory in the command prompt.
Im sorry i am new at this but i thought i followed the directions perfectly and any help anyone could give me would be greatly appreciated.
First off, before someone else says it, you shouldn't start a new thread for something we already have a topic for. But anyways,
Sounds to me like recovery.img never got pushed to /data. Not sure if its a typo in your post but 'adb push recover.img/data' should be 'adb push recovery.img /data'. The space is important. On your phone use a root file explorer and go to your /data partition and see if recovery.img is there. You may need to either change permissions for /data or just put recovery.img on your sdcard and move it to /data with a root explorer.
Sent from my LG-P925 using Tapatalk
Well im sorry im new to this kind of thing, i didnt want to make anyone mad i just wanted some help and i apologize if ive ticked somone off. How would i change the permissions for the data? And could you tell me how to use the root explorer to put the recovery image in the right place? Again i appreciate any help you can offer.
Is recover.img in the same folder as adb? Because the instructions assume your recovery.img is in the same folder you are working from. So if you have to cd to your adb folder to use adb then recovery.img should be in that folder as well. Look at your cmd window, whatever directory/ folder it says you are in that is where you should put recovery.img.
If you saw a bunch of commands it means the .img did not go through your command did not work. You dont have the recovery.img in /data either put the file on your sdcard and use a root explorer to move it to /data or try the adb push again, you most likely made a typo or something.
You would put recovery.img on your sdcard through your computer. Open root explorer and navigate to your sdcard, long press on the recovery.img select move, go to/ data on the root of the phone, not the one on either sdcard it MUST be /data not /mnt/sdcard/data or anything like that once there paste file to /data and finish up in adb shell.
Alright i copied the recovery image to the /data folder and finished up in command prompt and everything worked out like it was supposed to. what was i supposed to do next to put it into cwm recovery mode? I held power, volume down, 3d button but i just went into normal recovery mode. then i went to rom manager to try and put it into cwm recovery that way but it just rebooted my phone. And when i went back into the /data folder i couldnt find the recovery image there anymore and i did a search on my root explorer and couldnt find it anywhere.
Hold vol down + 3D + power when lg logo appears release power but keep vol down +3D held down until recovery pops up. If you still don't boot into cwm try flashing recovery.img again. Do NOT use rom manager at all to install cwm on this phone.
Well ive tried to take the recovery image from the sd card to the /data folder but when i run 'rm /data/recovery.img' on the command prompt then reboot my phone, i turn it off then try and put it in recovery mode but its just regular recovery mode not cwm recovery mode. And everytime i run the 'rm /data/recovery.img' when my phone boots back up the recovery image is no longer in the /data folder or anywhere. But if i dont run the 'rm /data/recovery.img' after moving the recovery image to the /data folder it stays in the folder. Is it supposed to dissapear from the /data folder?
And i tried putting the recovery image in the same folder as abd which is the platform tools folder then flash it over and i got the same message. (cannot open for read: No such file or directory.)
Im sorry for all the questions and I am thankful for your help. I feel like i cant be the only person having this problem, well i hope im not that would make me feel really stupid. Thanks.
powers.jereme said:
Well ive tried to take the recovery image from the sd card to the /data folder but when i run 'rm /data/recovery.img' on the command prompt then reboot my phone, i turn it off then try and put it in recovery mode but its just regular recovery mode not cwm recovery mode. And everytime i run the 'rm /data/recovery.img' when my phone boots back up the recovery image is no longer in the /data folder or anywhere. But if i dont run the 'rm /data/recovery.img' after moving the recovery image to the /data folder it stays in the folder. Is it supposed to dissapear from the /data folder?
And i tried putting the recovery image in the same folder as abd which is the platform tools folder then flash it over and i got the same message. (cannot open for read: No such file or directory.)
Im sorry for all the questions and I am thankful for your help. I feel like i cant be the only person having this problem, well i hope im not that would make me feel really stupid. Thanks.
Click to expand...
Click to collapse
rm is the command to remove. So yes, recovery.img is supposed to disappear after that command. Put it back on /data and run the whole process from the CWM thread again making sure you do every step. Sounds like you may have accidentally skipped a step.
Sent from my LG-P925 using Tapatalk
Double post.
Ugh...keep selecting quote instead of edit on Tapatalk...Triple post...
Alright ill try that again, so i should put the file back on the /data folder and then still do the step where you try to flash over cwm from the cwm thread, even though its already there? Thanks
powers.jereme said:
Alright ill try that again, so i should put the file back on the /data folder and then still do the step where you try to flash over cwm from the cwm thread, even though its already there? Thanks
Click to expand...
Click to collapse
Yea just do it all again. Worst case is you flash cwm back over cwm
Sent from my LG-P925 using Tapatalk
I got it to work Urabewe was right i just needed to put the recovery image in the correct folder and everything worked perfect. Thanks guys.

1.31.651.2 ruu?

Does anyone know when the new ruu for the HTC One comes out? I went to unroot my phone, locked the bootloader, and went to run the ruu, only to realize I did the system update a few days before. So now I'm stuck in a bootloop and I can't mount my sd card ( I think it's corrupted ) So I'm pretty much out of a phone till then, correct?
Thank you in advance guys.
If you can unlock again, and somehow get adb to work, you can s-off using revone. Then you can flash any RUU. Otherwise, I dunno
Sent from my HTCONE using xda premium
propjockey said:
If you can unlock again, and somehow get adb to work, you can s-off using revone. Then you can flash any RUU. Otherwise, I dunno
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
I re-unlocked the phone again but I have no clue how to do the rest.
If you can get files to your sd, you can run revone or moonshine to get s-off. Look in original development for the corresponding threads and instructions. Once you have that, you can RUU old firmware or unsigned.
Sent from my HTCONE using xda premium
I can't mount my internal storage. Even in TWRP recovery it shows nothing on the sd card. I think some how the internal sd card got corrupted, so I can't mount it.
Chloroform said:
I can't mount my internal storage. Even in TWRP recovery it shows nothing on the sd card. I think some how the internal sd card got corrupted, so I can't mount it.
Click to expand...
Click to collapse
I'm having a similar problem and need some help too!!
tx_jaycee said:
I'm having a similar problem and need some help too!!
Click to expand...
Click to collapse
I think the only thing that will fix our problem is a new version of the ruu. I knowledge on adb is very limited, I'm sure someone that knows what their doing can fix it 1,2,3, but that person isn't me. :crying:
ADB should not be your tool of choice. Fastboot would be your friend here, since it's a lot more direct in its method. If your internal card isn't completely hosed, you should be able to restore using the fastboot flash commands to reflash your /system and /boot and /recovery, at which point you should be fine. There are several threads on how to do this.
Rirere said:
ADB should not be your tool of choice. Fastboot would be your friend here, since it's a lot more direct in its method. If your internal card isn't completely hosed, you should be able to restore using the fastboot flash commands to reflash your /system and /boot and /recovery, at which point you should be fine. There are several threads on how to do this.
Click to expand...
Click to collapse
Can you point me in the right direction?
I tried the all in one kit, tells me device not found. I know it's found by my computer, it's in the device manager, plus I hear the noise that confirms a device is found. I can reboot my phone thru the all in one kit. I think it's best to wait for the newest ruu in my case.
Chloroform said:
Can you point me in the right direction?
Click to expand...
Click to collapse
Download the image of your choosing from this thread: http://forum.xda-developers.com/showthread.php?t=2368907.
Download TWRP 2.5 from this thread: http://forum.xda-developers.com/showthread.php?t=2236620.
Put your phone into fastboot mode (power + volume up + volume down). Plug the phone into your computer.
Install fastboot/ADB. You may need to search the web for the platform tools, or there are some toolkits that can help.
Open a command prompt and run "fastboot flash recovery <path-to-recovery.img>".
Go to Advanced -> ADB sideload, then run "adb install <path-to-downloaded-image.zip>".
If that doesn't work, open the zip and run:
fastboot flash system <path-to-system.img>
fastboot flash recovery <path-to-recovery.img>
Bottom line is if you're not willing to learn a bit about fastboot and ADB, then you shouldn't be using a toolkit because you won't be able to fix your device if something goes wrong.
So I pretty much tried everything with no luck BUT I flashed the boot.img and now I'm getting some where. Now it's showing my internal storage but the rom I had installed I guess erased. I've been searching around people saying flash system.img but how can I flash a system.img? All the files I've been finding are .zip and there any .img roms that I can flash?
Chloroform said:
I can't mount my internal storage. Even in TWRP recovery it shows nothing on the sd card. I think some how the internal sd card got corrupted, so I can't mount it.
Click to expand...
Click to collapse
I've had this problem. To correct it, I put everything I need to flash in /sdcard/0. TWRP sometimes only sees stuff within a 0 folder placed inside root.
If you haven't tried already, make a 0 folder on the sdcard, then copy it and see what TWRP shows.
Thank you to @Indirect for fixing my problem.
Chloroform said:
So I pretty much tried everything with no luck BUT I flashed the boot.img and now I'm getting some where. Now it's showing my internal storage but the rom I had installed I guess erased. I've been searching around people saying flash system.img but how can I flash a system.img? All the files I've been finding are .zip and there any .img roms that I can flash?
Click to expand...
Click to collapse
In the future, try extracting your downloaded .zip files.
OTA packages and recovery-flashable ROMs are provided as .zip files. Each archive contains the necessary .img files and a script that tells the recovery where to put them. You can extract these .img files and flash them with fastboot if you don't have recovery access.
Fastboot factory images generally are .img files compressed as .tar files. You'd better have a tool like 7zip onboard so you can deal with the many archive formats you'll find on the net.
Closed per OP request

Categories

Resources