While trying to update my phone to the latest Cyanogen mod, I made the mistake of also applied the 32A/EBI1 kernel. My phone is a 32B and this of course did not boot.
I am now without a phone that boots, I can't upgrade the RA since I do not have an Engineering SPL and adb refuses to see the device. Fastboot does see it though.
Any thoughts on getting the phone back to working order? And how can I upgrade to the latest RA-Sapphire from RA-sapphire-v1.5.2G?
Thanks!
I guess a reflash of the CM just did the trick. now to upgrade RA...
from the terminal app emulator, I get:
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
......
error writing recovery: No space left on device
Any help would be great!
You can't simply wipe and reflash like you did except with the right kernel?
Mod. edit: not dev related, moved to general
gl though
3rdcoast that's pretty much what I ended up doing - had to do it twice though for it to really overwrite the incorrect kernel.
Thanks to the admin for moving this to the right location though!
Related
I searched the forums and couldn't find anything. I had the cyanogen recovery console 1.4 on my fiances G1 and I was trying to update it through the terminal to the amon ra recovery.
Su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
flash_image recovery /sdcard/recovery-RA-dream-v1.6.2-green.img
I used tht command in the terminal and it gave me a bunch of errors and failed. Now whenever I try to boot into recovery with home+power it boot into the spl screen (whichis the fctory spl) as if I used camera+power. It gives me these errors everytime I try to flashthe recovery. I know I'm stupid not posting the errors but I don't have my finces phone on me at the moment. Ill edit my post lter with the errors it gives.
I do remeber it saying something about not having enough room though.
In that case, I think you'll have to remove the old recovery image first, then flash the new one into the space it occupied. Think I read something about that somewhere with the solution being to adb pull the old recovery and adb push the new recovery.
Found it. Hope this helps.
cyanogen said:
If you have problems with a "no space on device" error, try using fastboot and erasing first:
Code:
fastboot erase recovery
fastboot flash recovery cm-recovery-1.4.img
Click to expand...
Click to collapse
I found that solution myself, but the problem is, tht requires the danger spl to do the fastboot nd her phone still has the factory spl... the only solution I have come up with is to go r29 and use the bluetooth hole in telnt to flash a new recovery, but I don't know if this will work as I could give me this same error of not having enough spce.
ram100987 said:
I found that solution myself, but the problem is, tht requires the danger spl to do the fastboot nd her phone still has the factory spl... the only solution I have come up with is to go r29 and use the bluetooth hole in telnt to flash a new recovery, but I don't know if this will work as I could give me this same error of not having enough spce.
Click to expand...
Click to collapse
You don't need the Danger spl just one of the engineering Spls.
http://forum.xda-developers.com/showthread.php?t=455860
Hard Spl is what you want. You still need to be able to flash that.
Ah, right. What a unique situation...
Borrowed this from Cyanogen's wiki:
Restoring the custom recovery 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 commands:
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
If you receive an error, join us in the IRC channel (irc.freenode.net #cyanogenmod
Click to expand...
Click to collapse
billquinn1 said:
You don't need the Danger spl just one of the engineering Spls.
http://forum.xda-developers.com/showthread.php?t=455860
Hard Spl is what you want. You still need to be able to flash that.
Click to expand...
Click to collapse
But typically you need to get to recovery to flash an SPL, right?
r4d14n7 said:
But typically you need to get to recovery to flash an SPL, right?
Click to expand...
Click to collapse
Yes, your answer is the one you want, mine is to try to prevent something terrible. If by some quirk that I can't remember, you managed to flash the Doom bringer without the right radio... That would suck since to use fastboot you only need one of the engineering Spls.
http://forum.xda-developers.com/showthread.php?t=566669
If you check out AmonRA, it gives you all the instructions for various ways to install his recovery image. I ususlly use the terminal method but adb is good as well.
if i use:
Code:
flash_image recovery /sdcard/[recovery].img
for terminal or:
Code:
adb shell flash_image recovery /sdcard/[recovery].img
it gives me this error:
Code:
mtd: erase failure at 0x001e0000 (I/O error)
mtd: erase failure at 0x001e0000 (I/O error)
mtd: skipping write block at 0x001e0000
mtd: erase failure at 0x00220000 (I/O error)
mtd: erase failure at 0x00220000 (I/O error)
mtd: skipping write block at 0x00220000
mtd: erase failure at 0x00260000 (I/O error)
mtd: erase failure at 0x00260000 (I/O error)
mtd: skipping write block at 0x00260000
mtd: erase failure at 0x002a0000 (I/O error)
mtd: erase failure at 0x002a0000 (I/O error)
mtd: skipping write block at 0x002a0000
error closing recovery: No space left on device
since i have the factory spl i cannot erase the recovery through fastboot and I cannot flash a hardspl because i cannot access recovery..... so im stuck.
I wonder if you can run something like:
Code:
adb shell format recovery
Not sure if this would work, but it sounds like it should... I know you can format CACHE, DATA, and SYSTEM in a similar way.
Just an idea, so.....
*Do research, I don't want the blame for bricking anything*
I really hope you can resolve this, I can imagine the frustration. Once you do resolve this, billquinn1 was correct, you only need the engineering SPL or HardSPL, but of which are completely safe for the G1.
r4d14n7 said:
I wonder if you can run something like:
Code:
adb shell format recovery
Not sure if this would work, but it sounds like it should... I know you can format CACHE, DATA, and SYSTEM in a similar way.
Just an idea, so.....
*Do research, I don't want the blame for bricking anything*
I really hope you can resolve this, I can imagine the frustration. Once you do resolve this, billquinn1 was correct, you only need the engineering SPL or HardSPL, but of which are completely safe for the G1.
Click to expand...
Click to collapse
Before you try anything else, I would go to the AmonRA thread and ask this question there.
Last night I went through the process of rooting my G1, installing DangerSPL, and finally loading up CM6-RC1. Today I started to update my wife's phone using the same process, and even the same files (which were still on my PC). Before going to the Danger/CM5 instructions, I started by following the Wiki instructions for downgrading. Reverting to RC29 (DREAIMG.nbh) went fine.
The instructions say the next step is to install Cupcake. So I format the card and copy update.zip over, power down, and restart with Home + End. I get the /!\ screen, I type ALT+S, and it starts the loading process.
But instead of finishing, it gets about halfway through the progress bar then goes back to the /!\ screen.
If I reboot the phone, the phone works properly so it isn't bricked or anything. I tried reformatting, I've re-downloaded update.zip... does the same thing every time. What's wrong?
Also... do I actually need Cupcake to load DangerSPL and CM6?
Ah, it appears Cupcake gives me the newer 2.x radio, is that right?
I see the newer radio linked from the DangerSPL page in the Wiki, I guess I'll try loading that...
Edit: Didn't work. Recovery mode seems OK with the 2.x radio ZIP but afterwards fastboot still shows radio 1.22.x.
Oh well.
It appears I have bigger issues. The Recovery screens (the regular /!\ version and Amon_Ra if I bother to go that far) always show the "E:Can't read MISC:" error, and so far I haven't found a clear explanation of how/why that happens -- or more importantly, how to fix it.
Thanks to this post:
forum.xda-developers.com/showpost.php?p=5401531&postcount=506
I determined I should try a nandroid backup from my other working G1 and grab the misc.img... but unfortunately nandroid backup from RA errors out, and the nandroid folder on the card contains .img files for everything but misc... Arrgh.
Finally used adb shell to run nandroid backup and force a misc backup on my working phone, then copied it to the sdcard root and attempted to flash_image misc /sdcard/misc.img
Results are not encouraging:
flash_image misc /sdcard/misc.img
mtd: ECC errors (0 soft, 1 hard) at 0x00000000
mtd: ECC errors (0 soft, 1 hard) at 0x00020000
mtd: erase failure at 0x00000000 (I/O error)
mtd: erase failure at 0x00000000 (I/O error)
mtd: skipping write block at 0x00000000
error writing misc: No space left on device
No idea what all of that means.
Hi all, when I'm trying to flash RA's recovery image through cmd prompt I receive this...picture is also attached
mtd: erase failure at 0x004e0000 (I/O error)
mtd: skipping write block at 0x004e0000
error writing recovery: No space left on device
How do I go about fixing this issue? I've done a full wipe,cache, davik wipe.
Are you already rooted? If it's giving you an error via cmd line, i'd suggest using ROM Manager to "Flash Alternate Recovery" to get RA setup.
I'm new at installing custom ROMs, so I would like to know what do I need to install a custom ROM on my phone before jumping in to it, if there is already a thread please let me know, but I hate having to go through to figure out what I need.
My Phone:
OS: Android Froyo 2.2.1 from this post: http://forum.xda-developers.com/showthread.php?t=807899
Rooted via SuperOneClick: http://forum.xda-developers.com/showthread.php?p=13651805
FastBoot Info:
Sapphire PVT 32B S-ON G
HBoot-1.33.0013 (SAPP30000)
CPLID-10
Radio-2.22.28.25
Oct 21 2009,22:33:27
I would like to try out Gingerbread like COS-DS or Ginger Yoshi, but if those are not recomended for my phone, then the best recomended ROM.
Please let me know what preparations I need to get me started with this.
Thank You in advanced for all your help.
http://forum.xda-developers.com/showthread.php?t=794445
read that and then
you could try these:
http://forum.xda-developers.com/showthread.php?t=1025330
http://forum.xda-developers.com/showthread.php?t=932118
happy flashing buddy
What NBH should I use?
I read this post http://forum.xda-developers.com/showthread.php?t=529019 and I do have a fastboot remote: not allow (Perfected SPL), soi I went to the post linked (http://forum.xda-developers.com/showthread.php?t=548218) With my HBoot Info above, what NBH Should I Use?
A) ROM v2.53.707.2 (Engineerings SPL v1.33.2010)
B) ROM v2.16.707.3 (NON-Perfected stock SPL v1.33.0009)
C) ROM v2.16.151.1 (NON-Perfected stock SPL v1.33.0009)
D) Other? (Please specify and provide link)
Please consider I will be trying to flash Ginger Yoshi (http://forum.xda-developers.com/showthread.php?t=932118)
Thank You.
you'll need to update your spl buddy so follow this (this is the exact guide you need if you want ginger yoshi)
http://forum.xda-developers.com/showthread.php?t=909900
then go ahead and flash ginger yoshi
http://forum.xda-developers.com/showthread.php?t=932118
happy flashing
I Flashed Recovery!
I try to flash recovery and it doesn't work! ROM Manager say's it flashed the recovery but neither clockworkmod nor Amon_Ra works When I try to boot in to recovery it stays at the green MyTouch Spash Screen and nothing happens, and if I connect it to the USB port "FLASHBOOT USB" appears in the upper left corner, but I can't do anything... Here is my OS info, maybe it´s blocking the flahsinf of the custom recovery:
Android Version: 2.2.1
Baseband Version: 62.50SJ.20.17U_2.22.28.25
Kernel Version: 2.6.32.9-27237-gbe746fb [email protected] #1
Build Number: FRG83D
I googled and I tried flahsing the recovery via FastBoot and I get the Remote Not Allow eror and if I try Flas_Image I get the Stop (Signal) error and/or Invalid Instrucion error.
Edit: I took the flash_image file from the Ginger Yoshi ROM (opened the "Ginger+yoshi+1.1.zip" and took flash_image from system\bin\) pushed it to the sdcard, pushed the reovery.img and followed these steps:
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
now flash_image doesn't give me an "Illegal instruction" but gives me these:
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
mtd: read error at 0x00080000 (Out of memory)
mtd: read error at 0x000a0000 (Out of memory)
.
.
.
mtd: read error at 0x004e0000 (Out of memory)
error reading recovery: No space left on device
flashing recovery from /sdcard/recovery.img
mtd: write error at 0x00000000 (Out of memory)
mtd: re-read error at 0x00000000 (Out of memory)
.
.
.
mtd: re-read error at 0x004e0000 (Out of memory)
mtd: write error at 0x004e0000 (Out of memory)
mtd: re-read error at 0x004e0000 (Out of memory)
mtd: skipping write block at 0x004e0000
failed with error: -1
error writing recovery#
Also, I tried flashing RA Recovery from CM Mod and it read that it flashed OK, but when I try to boot to recovery (after waiting more than 1 minute) I plugged it in to the USB and noticed the green over red "FastBoot USB" on the upper left corner of the MyTouch 3G screen, so I tried fastboot devices and I got "HT98TP302788 fastboot"
After some serious googleing I found out that I need to flash_image as soon as the phone boots up so it can run seems that the the MT3G (32B) uses too much memory on 2.2.1 to fhasl_iamge to run I'm creating a nandroid backup and will proceed with the rest... wish me luck!
What options do I have?
I'm Running on Ginger Yoshi!
Woot! Thanks CH3NO2 for pointing me in the right direction!
I just got 32B vodafone from my friend and now it's 1.5 cupcake.. and i want to update to 2.1 or above .. i tried to open in recovery mode by press Home + Power but it still freeze at HTC magic screen.
i flashed Recovery recovery-RA-sapphire-v1.7.0G.img by fastboot / flashrec it's said finished! but when i back to recovery mode it's stuck at the same.
i tried to flash by Terminal too but... >
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
mtd: read error at 0x00080000 (Out of memory)
mtd: read error at 0x000a0000 (Out of memory)
mtd: read error at 0x000c0000 (Out of memory)
mtd: read error at 0x000e0000 (Out of memory)
mtd: read error at 0x00100000 (Out of memory)
mtd: read error at 0x00120000 (Out of memory)
mtd: read error at 0x00140000 (Out of memory)
mtd: read error at 0x00160000 (Out of memory)
. . . . . .
my Device is
SAPPHIRE PVT 32B ENG S-OFF H
HBOOT-1.33.2010 (SAPP10000)
CPLD-10
RADIO-3.22.20.17
Jun 2 2009, 17:27:03
some one help me please... i need Market and 2.1 up
Thank you (and sorry for my English it's very poor)
Danger combination
Mmm. You have danger combination.
Your Magic is 32B (cause it has 32B motherboard with 192 MB RAM onboard)
But your SPL (hboot + radio) has 32A combination: 1.33.2010 + 3.22.20.17
It is very dangerous. Because the most hboot+radio for 32A are deadly for 32B phones. If you will install something other from 32A - you will brick the phone.
You have two ways:
1. Restore to right combination for 32B (example: hboot 1.33.2005 + radio 2.22.19.26I)
Code:
fastboot flash radio 2.22.19.26I.img
fastboot flash hboot 1.33.2005.img
fastboot flash recovery recovery_with_G.img
(don't reboot between commands, use these commands in sequence as above)
Then use 32B roms
2. Stay on current SPL and use 32A roms
It is safe, but you will have some problems: most of 32A roms are bigger and consume more memory than 32B has. You have to use light roms (CyanogenMod and other ROMs builded from AOSP (without extended UI).
To use these roms you need install recovery for 32A radio - AmonRa 1.7.0 H
(H - cause you have radio 3.22.XX.XX)
Don't forget install 32A kernel (It links to radio 3.22.XX.XX too) if it exists...
p.s. It you have other questions please write here or PM me, cause you have dangerous combination
Am facing this problem also.
I need a radio.img file to downgrade via fastboot to desired 2.22 radio
any idea where I can find such file?