Related
Following the CyanogenMod Full Update Guide, to flash a T-Mobile G1 with the latest CyanogenMod, 4.2.15.1 at the time of this writing, I run into a problem while trying to flash the cm-recovery-1.4.mg.
Basically, when I tried to do: flash_image recovery /sdcard/cm-recovery-1.4.img (or recovery-RA-dream-v1.5.2.img or recovery-RA-dream-v1.6.2.img), I got this error:
mtd: erase failure at 0x003e0000 (Input/output error)
mtd: erase failure at 0x003e0000 (Input/output error)
mtd: skipping write block at 0x003e0000
I even tried (without any luck either):
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
If I then turned off the phone, and tried to get into recovery mode, by pressing the Home and Power/End buttons, I got into the rainbow screen, and can not do anything.
By trial and error, I was able to flash a recovery image called recovery_RC30_xda-dev_v1.2.img, with an MD5 of 8d055734022496906244b71f849a6b6d, without errors, so that, when I boot in recovery mode, I get:
Android system recovery utility Build: JFv1.42
ALT+S Apply update.zip
ALT+W Wipe/factory reset.
ALT+B Backup.
ALT+X Console mode.
I was then able to flash the HardSPL, by copying a "Hard SPL zip" file into the SD Card as "update.zip", turning off the phone, starting recovery mode, ALT+S to apply, and then rebooting.
After that, I flashed an Android ROM called JFv1.42_RC33, by copying a "JFv1.42_RC33 zip" file into the SD Card, again as "update.zip", turning off the phone, starting recovery mode, ALT+S to apply, and then rebooting.
While all was functioning fine, I still wanted to install CyanogenMod 4.2.15.1.
The problem is that the Full Update Guide states, after downgrading, rooting, and wiping, there are 3 more steps:
1) flash DRC83_base_defanged.zip
2) flash update-cm-4.2.x-signed.zip
3) flash ota-radio-2_22_19_26I.zip
and between 1, 2, 3, it says "STOP - DO NOT REBOOT YOUR PHONE".
So I took the chance, and did 1, 2, and 3. And after each flash, the recovery tool (JFv1.42) would tell me to reboot, which I did.
Basically, I had to mount the phone, copy the corresponding zip file to SD Card, rename to update.zip, turn off phone, turn on phone in recovery mode, ALT+S to flash the update.zip, reboot, and repeat, with each 3 of the zip files.
At the end, I also did the same with the the SPL_Hard_Update_Signed.zip, as it is a G1.
(Basically i did the wiki article, but substituting the recovery.img with the small one, and by having to copy one "update.zip" at a time, and rebooting)
So, while I now have a fully flashed CyanogenMod 4.2.15.1, there are still a couple of doubts:
1) Why can't i flash bigger Recovery Images? Could it be a bad memory?
2) Is there any other "small" Recovery Image i should try that allows me to select the zip and not reboot?
3) Is there a way to do the flashes using the terminal in recovery mode (ALT+X)?
4) If i want to try again to flash CM or RA, and it fails, can i just go ahead and re-flash the recovery image that i have working, or should i need to re-do all again?
5) If, lets say i want to flash SuperD, and i boot in recovery, and flash it, would it be ok, or i would need to do anything else?
Any other ideas/comments?
yaffs2 needs to be -yaffs2
yes, you just replace it, or rename recovery-RA-dream-v1.5.2.img to recovery.img. Also, v1.6.2 is out.
I've never seen the cat recovery.img > /system/recovery.img
I've never had to do it, but if it says do it - do it.
Are you sure you are holding home power? Seems like you're holding back and power or camera and power. Home and power shouldn't do that. By any means. The most it should do is refuse to boot into recovery and just hang on the G1 screen because you either soft-bricked or flashed the wrong recovery.
I have been doing some tests, so i rewrote the first post.
re-wrote it once more.
Anybody has an idea?
have you tried fastboot ?
fastboot erase recovery
fastboot flash recovery recovery-RA-dream-v1.6.2.img
?
kwanbis said:
1) Why can't i flash bigger Recovery Images? Could it be a bad memory?
2) Is there any other "small" Recovery Image i should try that allows me to select the zip and not reboot?
3) Is there a way to do the flashes using the terminal in recovery mode (ALT+X)?
4) If i want to try again to flash CM or RA, and it fails, can i just go ahead and re-flash the recovery image that i have working, or should i need to re-do all again?
5) If, lets say i want to flash SuperD, and i boot in recovery, and flash it, would it be ok, or i would need to do anything else?
Any other ideas/comments?
Click to expand...
Click to collapse
1/
Dunno, it seems weird, but I would try and erase it in fastboot and then go from their.
2/
I dont know of any, they all float around the same size
3/
If you build a system.img and what not, you could do.
flash_image system system.img | flash_image boot boot.img etc etc from the console.
4/
Its a risk, but flashing the recovery wont effect the install of cyanogen (or whatever custom build of android you have installed), worse case though is losing recovery if you cant put one back on.
5/
It should be ok.
Dont know how good you are with coding etc... but most recovery images have the source code avalable.
You could rip out all the crap you didnt want and shrink its size like that.
vixsandlee said:
1/ Dunno, it seems weird, but I would try and erase it in fastboot and then go from their.
Click to expand...
Click to collapse
You mean to flash a recovery image with fastboot?
vixsandlee said:
2/ I dont know of any, they all float around the same size.
Click to expand...
Click to collapse
The one i have flashed, is about 2M, the ones from CM/AR are about 4MB.
vixsandlee said:
3/ If you build a system.img and what not, you could do.
flash_image system system.img | flash_image boot boot.img etc etc from the console.
Click to expand...
Click to collapse
I have no idea of what you are talking about. (I just got this G1 a week ago.)
vixsandlee said:
4/ Its a risk, but flashing the recovery wont effect the install of cyanogen (or whatever custom build of android you have installed), worse case though is losing recovery if you cant put one back on.
Click to expand...
Click to collapse
So, if i can not flash CM/AR, i can re-flash the one that worked you mean?
vixsandlee said:
Dont know how good you are with coding etc... but most recovery images have the source code available.
Click to expand...
Click to collapse
While I have been programing for more than 20 years, I do not code much in C/C++ which i assume is what this is done in.
kwanbis said:
You mean to flash a recovery image with fastboot?
Click to expand...
Click to collapse
Yes, you can
Code:
fastboot erase recovery
fastboot flash recovery recovery-RA-dream-v1.6.2.img
A few guides saw to follow this step if you have problems flashing a recovery image, but it can be risky of course because it will wipe your now working recovery, so if it then wont let you flash the recovery image you now have you wont have one.
The one i have flashed, is about 2M, the ones from CM/AR are about 4MB.
Click to expand...
Click to collapse
yes I should have said most newer ones
I have no idea of what you are talking about. (I just got this G1 a week ago.)
Click to expand...
Click to collapse
I know that when you compile from source you get boot.img (the boot image) and system.img (the system.img)
you can flash them from the recovery console using the commands
flash_image boot boot.img
flash_image system system.img
etc... if you can find a build that has those images in the update.zip you could flash them manually.
So, if i can not flash CM/AR, i can re-flash the one that worked you mean?
Click to expand...
Click to collapse
I cant see why you wouldnt be able too, if it has flashed once it should flash again, but given that it may be a hardware fault (I am not saying that it is, but IF it is) then it could be risky.
While I have been programing for more than 20 years, I do not code much in C/C++ which i assume is what this is done in.
Click to expand...
Click to collapse
I have never looked, but yes I agree. If i knew more about it I would attempt it for you, but I am inexperienced at that kind of programming.
Hello!
Yesterday I found myself in a very terrible situation. I spend about 6-7 hours...
It just happened that I deleted the recovery (through fastboot), and before that deleted firmware of the phone. That is, there remained only mode HBOOT (fastboot). Around the internet and google there are no guides on how to return
recovery by the alternative methods or how to flash a new ROM through
fastboot.
Thats why i want to present to you my little guide... Coz i think it will be very useful for some ppls like me with the same trouble.
So, if you're in a situation where you do not have Recovery, and the phone is not started in boot ROM then first try a standard way to flash a new Recovery through fastboot mode
Standart way of flashing new recovery via fastboot
1.Connect your phone with PC via USB and power off your phone (if it up).
2.Than start up in fastboot mode - (in my situation, fastboot mode is CAMERA+POWER, then button "send") in all other (as i know) this is starting the phone while pressing button BACK.
3.Open -> Start->Run->cmd (open command prompt in windows*) and write:
Code:
fastboot devices
Than you must see your device serial number like this:
Code:
H94XTGAMSHDY
and should say "fastboot".
If all right - go next. If not - check fastboot mode (is on?) and USB cable.
4.Than change directory via cmd to where you have saved your recovery image (NEW recovery.img !!! ALWAYS CHECK MD5 SUM)
5. Than type this :
Code:
fastboot flash recovery recovery.img [enter]
(while you are stay in the same dir where you saved recovery.img)
(if you got some error about previously version or smth like this you can try to use this: fastboot erase recovery and only than try to flash new recovery from step №5)
6.Check your phone's display, as recovery is being sent and flashed to your device. And check your command prompt/shell to make sure the process is over.
7.Reboot into recovery by holding Home and Power (before it power off device).
Thats all! You can use any recovery, all what you like. I use Amon_RA's recovery.
IF WHILE FLASHING YOU GOT :
Code:
sending 'recovery' <4594kb>... OKAY [ 1.734s]
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
finished. total time: 3.125
Use next steps (my Alternative method)
And IF you can't flash recovery by this method it is not big trouble as you think now
Alternative way of BOOTING new recovery via fastboot checked and founded by me
Everything here is much easier and faster!
Do not be scared as I did it yesterday
Only what you need it :
Change directory via cmd to where you have saved your recovery image (NEW recovery.img !!! ALWAYS CHECK MD5 SUM)
And than TYPE:
Code:
fastboot boot recovery recovery.img
And your phone will be rebooted about 2 seconds in RECOVERY MODE. Yes!
After this you can use your old Nand Back up (restore it) and start up your old ROM. Or you can wipe all and try to flash new ROM and many operations what you can use via recovery. When you will get working ROM and flash it - you can flash recovery via adb. Or Use Rom Manager (Not recommended!)
Why we use this method? Because if you got error while flashing - FAILED <remote: signature verigy fail> you CAN'T FLASH ANY .img. Why? I Don't know, i hope some android guru's help us with it theory
(ALL AFTER THIS LINE ALL TEXT COPYED FROM WIKI.CYANOGEN.COM CREDITS GOES TO Cyanogen. Thx you, god)
If you want to flash recovery via adb (using power on phone with working firmware) (This method working 100% but strongly need working phone with working ROM)
Working only with HTC DREAM (G1) - Attention.
adb method by cyanogen version
Restoring the custom recovery image
Download the flash_image tool (HERE LINK
Next, place the file on your desktop
Change the directory to where "flash_image" is located, e.g. in Windows: cd C:\<path-to-flash_image-location>, in Linux: cd /home/USERNAME/path/to/flash_image on a Mac: cd /Users/USERNAME/path/to/flash_image)
IMPORTANT: Turn on USB debugging. Settings -> Applications -> Development -> check the box "USB Debugging"
Open up and adb shell
With your phone booted, type the following command
s:
Code:
adb root
This will start ADB as root, or notify if it is already running as root.
Code:
adb remount
This will mount the system partition (/system) as writable, allowing the following
Code:
adb push flash_image /system/bin
This will send the flash_image script into the /system/bin, so we can use it from within the shell
Code:
adb shell chmod 0755 /system/bin/flash_image
Finally, change the permissions of the script to allow it to perform the desired action.
Now that the script is installed, we are ready to proceed with flashing the custom recovery, saved on the root of the SD card earlier:
Code:
adb shell flash_image recovery /sdcard/recovery.img
P.S. If you want i can post here method by flashing original 1.6 ADP Rom via fastboot (but as i think it is on htc dev web... But i can post here cut version of this - coz original version have many not needed things.)
Credits:
Cyanogen
all xda cool ppls
ANtiHazarD
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Nice steps! man hope this gets a good stick or added to the rom bible, you do know though fastboot method is a common way to flash recovery
ilostchild said:
Nice steps! man hope this gets a good stick or added to the rom bible, you do know though fastboot method is a common way to flash recovery
Click to expand...
Click to collapse
That's what I was thinking... Seems almost pointless for a guide since there's instructions how to fastboot on every recovery thread.
Either way, nicely written guide. Someone will probably find this useful.
pablo34 said:
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Click to expand...
Click to collapse
With a desire this is quite different, as it has an activated nand flash protection (s-on), so no fastboot flash recovery here. Although this should prevent you from not having a recovery at all...
* note: I don't have a desire (yet) so this is speculation *
Best is probably something similar to this http://forum.xda-developers.com/showthread.php?t=750852
I guess if you get the correct PB99IMG.zip for exactly your device/brand you will not need a goldcard, so don't follow the howto blindly (it is for the newer SLCD versions, but the basics will still be applicable to AMOLED devices). Best would be a PB99IMG.zip that still has a hboot version < 0.92, otherwise you will need to downgrade to root. If you already have 0.92, then just take the newest image, as older ones are normally not flashable.
After step 7 of the howto, you are either done, or you will need to find instructions to downgrade if you want to root.
As soon as you have a working system, with a 0.8* hboot you can just use unrevoked to root and flash a custom recovery.
Enough OT... @ANtiHazarD: Very useful overview. Thanks.
WAY WAY WAY more complicated than it should be...
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
lbcoder said:
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
Click to expand...
Click to collapse
Its not quite that simple,
1) if eng spl use fastboot instructions from RA recovery post (fastboot flash recovery recovery.img)
2) if older stock spl with fastboot ruu modes (1.33.000*) where the * is
lbcoder said:
WAY WAY WAY more complicated than it should be...
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
Click to expand...
Click to collapse
maybe so
but i want to post here ALL known methods thats why so much text is here
why? coz it was a trouble and the method with
fastboot flash recovery recovery.img
not working! thats why - all ways is here.
(all pre-info into 1st post in the top)
pablo34 said:
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Click to expand...
Click to collapse
oh... i want to give to you some advice, but don't know what exact. because i don't have desire at my hands... and can't test.
so... thats why only - sorry
maybe there is some guide in the same way in desire section?
p.s. and thanks one more time to ezterry for old support
Can you please help me,
I have stuck here with the G1 phone,
it starts up and stucks on the G! logo.
I can get into fastboot bet have the same problem :
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
I get into fastboot with thre android logos on skates,
even tried to restore nandroid using fastboot but I get the same error? could you help me out?
I have HTC DREAM with 1.33.0013d and radio 2.22.27.08
I am really frustrated,
I tried all you gave up here but none worked for me.
Also when I try to get into recovery I see a G1 logo with a fastboot usb written on top left in red.
behzadbayat said:
Can you please help me,
I have stuck here with the G1 phone,
it starts up and stucks on the G! logo.
I can get into fastboot bet have the same problem :
writing 'recovery'... INFOsignature checking...
FAILED
I get into fastboot with thre android logos on skates,
even tried to restore nandroid using fastboot but I get the same error? could you help me out?
I have HTC DREAM with 1.33.0013d and radio 2.22.27.08
I am really frustrated,
I tried all you gave up here but none worked for me.
Click to expand...
Click to collapse
Did you read everything before you flashed the 1.33.0013d SPL?
If yes, you would have noticed, that this SPL is not able to flash a recovery or radio using fastboot. You have to flash the orange-...nbh file to get back a full engineering SPL, but you will loose everything you have installed on the phone ...
Send from my G1 with HTCClay's UNOFFICIAL Superfly 1.6 D/S ADS using XDA App
i don't know about this spl, but all what you can do (what i know) you can use this method which named in prev. post. with RC29 or RC7 stock firmware *.nbh
after flashing all data, radio, recovery will be reflashed by a stock data. All must be fine after this... i hope
ezterry can give for your advanced advice, may be
ANtiHazarD said:
i don't know about this spl, but all what you can do (what i know) you can use this method which named in prev. post. with RC29 or RC7 stock firmware *.nbh
after flashing all data, radio, recovery will be reflashed by a stock data. All must be fine after this... i hope
ezterry can give for your advanced advice, may be
Click to expand...
Click to collapse
Don't use RC29.. its once of the most annoying NBH files to need to re-root for the dream.
If you have 1.33.0013d note the orange.nbh posted on the new radio OP post: here
ezterry said:
If you find yourself stuck without recovery!!
Dream
1) Download: orange-1.58.73.2.nbh (MD5: aca4dee0c1ece7e9773f2ecbdfbba7c0) (mirror)
2) enter fastboot and run 'fastboot flash nbh orange-1.58.73.2.nbh'
3) wait for the entire nbh to flash
4) boot into the bootloader again (it will be an engineering SPL 1.42.2000)
5) You can now re-flash the radio/hboot/recovery via fastboot that you wish to have installed.
Click to expand...
Click to collapse
basically if you intend to still use the new radio; after installing 1.58.73.2 you can reboot-bootloader; and use my fastboot installation steps at the top of that post
You can do this without a goldcard because I bypass various checks in 1.33.0013d
(It will let you install any other signed NBH but that will still wipe the phone completely; and if it fails to flash cleanly it will leave you without an engineering SPL thus make it harder to make android go again)
hey i tried to flash the MTD too and now i keep getting "E:cant open CACHE:recovery/log" when i go into recovery . I can flash roms but when i reboot my phone my phone stays in the G1 Logo . and when it does make it to the rom i can not get my market or gapps no matter what i do . please help me guys .
EDIT: theres times when i get past the g1 logo but itll just stay on the roms boot screen forever until the phone dies . does anyone have any ideas ?
try to 'fastboot wipe system -w'
after
wipe all (data/cache, cache, dalvik, ext, stats)
and move log to sd
ANtiHazarD said:
try to 'fastboot wipe system -w'
after
wipe all (data/cache, cache, dalvik, ext, stats)
and move log to sd
Click to expand...
Click to collapse
ive never really done fastboot tho . is there any other way ?
breezy169 said:
ive never really done fastboot tho . is there any other way ?
Click to expand...
Click to collapse
It's worth learning to use it ...
Really, especially when using the 14MB-hack or CustomMTD and it's not so difficult. There should be a tutorial on adb and fastboot here in the forum.
AndDiSa said:
It's worth learning to use it ...
Really, especially when using the 14MB-hack or CustomMTD and it's not so difficult. There should be a tutorial on adb and fastboot here in the forum.
Click to expand...
Click to collapse
i agree but i just finished reading the forum that shows how to do it but it sounds so complicated .
EDIT: i ended up flashing another recovery and that solved the problem . that was the weirdest thinq ive ever seen . and honestly i thought i bricked my phone but it was a simpleee fix lol . thanks for the advice tho
I am hanging at booting while trying to do this any ideas?
Magic 32b
I have fastboot working, and can enter recovery mode (with clockwork 2.5 and/or Amon-Ra v1.2 - oddly Amon-Ra's 1.7 doesn't work for me)
The recovery modes that boot tell me they are successfully installing cm-6.00 RC3 OR 5.08, but when I go to reboot, I don't make it past the red vodafone screen.
My SPL is Engineering's 2005.
Any Suggestions on how to proceed/troubleshoot/get AR-1.7 recovery working?
(Always working with phone plugged in - does it charge if it isn't actually booted into a normal OS?)
Juneappal said:
Magic 32b
I have fastboot working, and can enter recovery mode (with clockwork 2.5 and/or Amon-Ra v1.2 - oddly Amon-Ra's 1.7 doesn't work for me)
The recovery modes that boot tell me they are successfully installing cm-6.00 RC3 OR 5.08, but when I go to reboot, I don't make it past the red vodafone screen.
My SPL is Engineering's 2005.
Any Suggestions on how to proceed/troubleshoot/get AR-1.7 recovery working?
(Always working with phone plugged in - does it charge if it isn't actually booted into a normal OS?)
Click to expand...
Click to collapse
Sometimes flashing a rom takes a few seconds to show anything but the Vodofone screen. Do you have adb installed on your pc?
If so then use it and enter "logcat" to get details as to what's going on exactly.
Also... did you do a complete wipe before installing? Some members don't want to do that... but it might help.
Binary100100 said:
Sometimes flashing a rom takes a few seconds to show anything but the Vodofone screen. Do you have adb installed on your pc?
If so then use it and enter "logcat" to get details as to what's going on exactly.
Click to expand...
Click to collapse
Am I trying to do the correct thing here? Using a mac:
[ ami tools/]$ ./adb devices
List of devices attached
HT96WLV08283 recovery
[ ami tools/]$ ./adb logcat
/sbin/sh: exec: line 1: logcat: not found
Also... did you do a complete wipe before installing? Some members don't want to do that... but it might help.
Click to expand...
Click to collapse
Total wipe - cache, data, devlik. No dice.
So I took a look at the recovery log after trying to install 6.0.0RC3. It seems to all have gone well except for two lines near the end:
/ # more tmp/recovery.log
minzip: Extracted file "/system/xbin/xbin.sqf"
set_perm: chown of /system/etc/install-recovery.sh to 0 0 failed: No such file or directory
set_perm: chmod of /system/etc/install-recovery.sh to 544 failed: No such file or directory
I:read: progress 0.200000 0
about to run program [/tmp/backuptool.sh] with 2 args
I:read: progress 0.200000 10
I:read: progress 0.200000 10
wrote boot partition from /tmp/boot.img
I:read: progress 0.100000 0
script result was [/system]
Install from sdcard complete.
I:Set boot command "
Is this related to my inability to boot up?
Have you had any luck yet?
Try reinstalling everything, SPL & radio & Recovery. Try recovery first, because the same has happened to me also sometime. And then the rest, if it doesn't help.
hey juneappal, i just wonder why do you need engineering spl? i got the stock spl and still able to upgrade custom rom.
my stock spl is h2004 security on
btw, if i want to get back to original firmware, however after restored with nandroid, it just does not let me do ota update. i flashed the custom amon recovery rom, so thats what i suspect,
or do i need engineering spl as well?
thanks
razor813 said:
or do i need engineering spl as well?
Click to expand...
Click to collapse
I am going to refrain from answering your question, because I don't know wtf I am talking about. Sorry
I actually got it to work with the setup described above, but I had to install a 32a kernel. Wacky.
I was getting lots of crashes, though, so I reinstalled the radio (went to a 32b radio) then installed clockwork, and a 32b kernel. All seems to be working (fairly) well. I get about 1 unexplained crash per day, but I can live with that, because it works so much better when it is running than it under 1.6. (Faster, better feature set, better UI) Thanks for your ideas, all.
So Clockwork installation & flashing works? Nice!
I've been running CM7 nightlies on my MT4G for a while now and have been quite happy with it. Unfortunately now I'm not able to boot it up. It's not a fully-fledged brick yet - I can still bot into recovery.
When I boot into CWR I get the following errors:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
I followed the directions in this thread: forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/ , but running parted gives me the following error:
Error: /dev/block/mmcblk0: unrecognised disk label
Click to expand...
Click to collapse
Trying it again with /dev/block/mmcblk0p27 gives the same:
Error: /dev/block/mmcblk0p27: unrecognised disk label
Click to expand...
Click to collapse
I've posted recovery.log here: pastebin.com/N6EbBzJM
Note the following error:
/sbin/tune2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0p27
Click to expand...
Click to collapse
Running e2fsck from adb shell gives me a similar error:
e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0
Could this be a zero-length partition?
Click to expand...
Click to collapse
It sounds to me like I have some bad memory blocks, but I can't figure out how to fix them. I was hoping e2fsck would do the trick.
Any help would be appreciated.
might be fried SD?
Are you referring to the internal SD? The external SD is working just fine, and at least the recovery partition is working (although I am unable flash a recovery image to it using fastboot, for some reason).
It seems like I have some bad blocks on the internal memory, but I don't know how to confirm this. Any ideas, anyone?
mine always says that when I make first selection, cannot find, etc...
But then I have to confirm it on second screen and works fine.
I have never seen it make any menton of internal however, I always install or flash from external sd.
So you cannot restore to a previous restore that did work?
No, I can not restore any of my backups - any attempt to flash fails due to the failure to mount the cache partition.
The errors "Can't mount /cache..." occur in CW recovery, not the bootloader.
samhiatt said:
No, I can not restore any of my backups - any attempt to flash fails due to the failure to mount the cache partition.
The errors "Can't mount /cache..." occur in CW recovery, not the bootloader.
Click to expand...
Click to collapse
Have you tried to pd15img it back to stock yet? Link in my sig.
Yes, I have tried flashing the pd15img. The bootloader finds the image, asks if I want to install it, and then says "Fail_PU" after trying to install both the boot and recovery partitions, then freezes and eventually reboots while installing the radio image.
I've done a lot of searching around and wasn't able to find what the "Fail_PU" messages mean.
samhiatt said:
Yes, I have tried flashing the pd15img. The bootloader finds the image, asks if I want to install it, and then says "Fail_PU" after trying to install both the boot and recovery partitions, then freezes and eventually reboots while installing the radio image.
I've done a lot of searching around and wasn't able to find what the "Fail_PU" messages mean.
Click to expand...
Click to collapse
That doesn't bode well. I'd say it's time for warranty.
Sent from my HTC Glacier
I was afraid of that. ... It seems like there's gotta be a way to repair the disk and get it running again. But maybe it's not worth the time that would take.
... Has anyone had any experience making a warranty claim on a "rooted" phone with Tmobile?
samhiatt said:
I was afraid of that. ... It seems like there's gotta be a way to repair the disk and get it running again. But maybe it's not worth the time that would take.
... Has anyone had any experience making a warranty claim on a "rooted" phone with Tmobile?
Click to expand...
Click to collapse
I agree with you. It seems like a simple reformat should be all it would take.
How did this happen anyway?
Not sure what made it crash, but it seemed spontaneous. One morning I tried to open Messaging but it would immediately close (with no FC message). I think I tried a couple other apps, they wouldn't open so I tried a reboot. Froze during reboot, so I booted into recovery and tried wiping the cache. Since then I haven't been able to start android.
I had just flashed CM7 RC1 and then reverted back to a previous nightly the day before it crashed. I don't know if this could have anything to do with it, but it doesn't seem too likely.
Using CWR to try to reformat the cache throws this error: "Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0p27"
What can I do to confirm if this is a hardware failure?
try holding the up volume button and power, for stock boot,and reformat, use image you used for the first backup ever. See if that works
samhiatt said:
Not sure what made it crash, but it seemed spontaneous. One morning I tried to open Messaging but it would immediately close (with no FC message). I think I tried a couple other apps, they wouldn't open so I tried a reboot. Froze during reboot, so I booted into recovery and tried wiping the cache. Since then I haven't been able to start android.
I had just flashed CM7 RC1 and then reverted back to a previous nightly the day before it crashed. I don't know if this could have anything to do with it, but it doesn't seem too likely.
Using CWR to try to reformat the cache throws this error: "Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0p27"
What can I do to confirm if this is a hardware failure?
Click to expand...
Click to collapse
You said earlier that fastboot flash of recovery failed, correct? Which recovery are you using now and do you still have access to it? I assume you tried reflashing other roms as well?
That doesn't work. After holding vol up + power the phone vibrates 3 times, then the LED keeps flashing red with a blank screen.
I would try another SD card, if that doesn't work, Brick
Phateless said:
You said earlier that fastboot flash of recovery failed, correct? Which recovery are you using now and do you still have access to it? I assume you tried reflashing other roms as well?
Click to expand...
Click to collapse
Correct. Fastboot flash fails with the following:
writing 'recovery'... FAILED (remote: image update error)
Click to expand...
Click to collapse
Yes I am able to boot into the CW Recovery 3.0.0.5 on the phone. I am also able to do a fastboot boot into 3.0.0.6 over USB.
Attempting to flash any rom fails with:
Error while erasing boot image!
Click to expand...
Click to collapse
I just posted the output of dmesg at http://pastebin.com/4Ffj6sUx. Note all the errors with mmcblk0.
lion766 said:
I would try another SD card, if that doesn't work, Brick
Click to expand...
Click to collapse
The SD card is fine. Internal memory (mmcblk0) is the one with the errors. That's not replaceable, right?
It it is not retrieving good information from the SD card, you will get that error
That error looks more like a recovery image error, as opposed to a phone issue. Try and redownload and fastboot flash recovery again.
also, from fastboot try
Code:
fastboot erase system -w
option94 said:
That error looks more like a recovery image error, as opposed to a phone issue. Try and redownload and fastboot flash recovery again.
also, from fastboot try
Code:
fastboot erase system -w
Click to expand...
Click to collapse
Thanks option94. I've tried several recovery images and though I'm not able to flash them to my phone I can boot them from fastboot. I just tried booting up CWR 2.5.1.2 which worked, but I still got the "can't mount /cache..." errors. Dmesg after trying to format cache from CWR 2 shows a bunch of error messages like:
[ 67.592468] mmcblk0: error -110 requesting status
[ 67.592712] mmc_blk_issue_rq failed!!
[ 67.604736] mmcblk0: error -110 sending status comand
[ 67.604858] mmcblk0: error -110 sending read/write command, response 0x40ff8080, card status 0x40ff8080
Click to expand...
Click to collapse
I just tried
Code:
fastboot erase system -w
It's been stuck on "erasing 'system' ..." for at least the past ten minutes...
Before I start. I would like to address the reason why. The first thing I hated about Motorola is that when you have updated to Jellybean OTA. It won't be unlocked. Unlike my past phones (ex: Samsung)
1) So it started when I installed SAFESTRAP, which did installed successfully.
2) Placed the Eclipse ROM in the root of my sd card.
3) Made a new ROM SLOT.
4) Saving some space, I deleted the whole /stock files. (Factory reset, wipe data and so on.)
5) When I was about to launch it. Everything was smooth until when I tried to delete files. Nothing can't be deleted or transferred. Which is weird.
6) Out of clumsiness, since I loved the JB look and thinking that would fix my file problem, I downloaded the Eclipse ROM ( the one I think isn't safe-strap compatible)
7) When I was about to boot to the system. It got stucked on ap fastboot, recovery can be accessed but even the button combos can't boot it normally.
The error shown :
Device is LOCKED, Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
Anyone can help me? Thank you so very much if you did.
Cyb3rw0lfest1 said:
Before I start. I would like to address the reason why. The first thing I hated about Motorola is that when you have updated to Jellybean OTA. It won't be unlocked. Unlike my past phones (ex: Samsung)
1) So it started when I installed SAFESTRAP, which did installed successfully.
2) Placed the Eclipse ROM in the root of my sd card.
3) Made a new ROM SLOT.
4) Saving some space, I deleted the whole /stock files. (Factory reset, wipe data and so on.)
5) When I was about to launch it. Everything was smooth until when I tried to delete files. Nothing can't be deleted or transferred. Which is weird.
6) Out of clumsiness, since I loved the JB look and thinking that would fix my file problem, I downloaded the Eclipse ROM ( the one I think isn't safe-strap compatible)
7) When I was about to boot to the system. It got stucked on ap fastboot, recovery can be accessed but even the button combos can't boot it normally.
The error shown :
Device is LOCKED, Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
Anyone can help me? Thank you so very much if you did.
Click to expand...
Click to collapse
Run this from windows
It's Russian . Just say yes. http://forum.xda-developers.com/showthread.php?t=2656659
Flash Failure
aviwdoowks said:
Run this from windows
It's Russian . Just say yes. http://forum.xda-developers.com/showthread.php?t=2656659
Click to expand...
Click to collapse
It now says Fastboot Reason : Flash Failure
I have tried fastboot option like from House of Moto and even the Droid Razr M Utility, but everytime it reaches
sending boot or system. it is stuck at that point.
Using RSD Lite, it shows failed flashing process gptmain0.bin (Something like that.)
I took the gptmain0.bin from the GPT Fix version of Droid Razr M Utility, placed it in there, and it reaches to failed flashing process tz.mbn
What to do? I'm all out of options really. Thanks.
UPDATE: Tried the logo.bat you sent me, it just says waiting for device. It won't even budge a little. Back to the usual hab boot error. Successfully flashed it using it 1.10. Just that I'm back to the first part. (Boot failure)
So you are locked on ...94 (1) right?
Boot Failure
aviwdoowks said:
So you are locked on ...94 (1) right?
Click to expand...
Click to collapse
Tried the logo.bat you sent me, it just says waiting for device. It won't even budge a little. Back to the usual hab boot error. Successfully flashed it using Razr M Utility1.10 (I don't know what version it flashed.). Just that I'm back to the first part. (Boot failure)
aviwdoowks said:
So you are locked on ...94 (1) right?
Click to expand...
Click to collapse
^^^^^^^^^^ what he said.
Build you are on? Locked boot?
aviwdoowks said:
^^^^^^^^^^ what he said.
Build you are on? Locked boot?
Click to expand...
Click to collapse
Now I can access safestrap recovery.
Shows
Unable to mount '/data' (tw_mount)
Unable to mount '/cache' (tw_mount)
Unable to mount '/ss' (tw_mount)
Unable to mount 'datamedia' (tw_mount)
Failed to mount /datamedia (Invalid argument)
Everytime I do something in the safestrap..
Cyb3rw0lfest1 said:
Now I can access safestrap recovery.
Shows FAILED TO MOUNT /DATAMEDIA (INVALID ARGUMENT}
Click to expand...
Click to collapse
Why do think you are on matt's version? If you were you could unlock!
You are on the one you last took the ota for or was on the phone. That is what locked means.
All you can do is rsd restore the above version or upgrade.
aviwdoowks said:
Why do think you are on matt's version? You are on the one you last took the ota for or was on the phone. That is what locked means.
All you can do is rsd restore the above version or upgrade.
Click to expand...
Click to collapse
I can access Safestrap recovery, flashed the boot.img separately. If I used RSD, it will only show failed flashing process gptmain0.bin or the tz.mbn
Cyb3rw0lfest1 said:
I can access Safestrap recovery, flashed the boot.img separately. If I used RSD, it will only show failed flashing process gptmain0.bin or the tz.mbn
Click to expand...
Click to collapse
Your boot is locked!
Read more.
I have a signature link...
Learn how to rsd ..94 & get on my SS dst rom.
Xposed works on locked boots.
aviwdoowks said:
Your boot is locked!
Read more.
I have a signature link...
Learn how to rsd ..94 & get on my SS dst rom.
Xposed works on locked boots.
Click to expand...
Click to collapse
Well now the only thing I can access is Safestrap recovery. Is there anyway I can fastboot in the safestrap recovery. The only thing I can see clearly in my Safestrap is that it can't mount CACHE or /CACHE/RECOVERY
Successfully fixed it myself. All it takes is trial and error all the way and the correct boot.img.