Having a problem loading a ROM - myTouch 3G, Magic General

I just tried to load HoFo 307 for 32a. I booted to recovery and wiped the phone and partitioned the sd. I go to apply update.zip and it said error, no such file or directory. I tried to used the nandroid backup and it said run 'nandroid-mobile.sh restore' via adb. Any help is appreciated. Newb post sorry.
[edit] I recently had a problem with my rogers magic 32A device. I was putting on a new ROM and deleted the update.zip by formatting the sdcard at the wrong time. I can get into fastboot mode but have never used the adb that I installed a while ago. I was wondering if you could show me how to access the device and put my update.zip on there. I can still get to my recovery screen as well and load an update.zip but there is nothing on there right now. If you could find the time to help me out it would be appreciated.
[edit] fixed the problem...

Figured out what i did wrong but if anyone knows a way to fix it I would appreciate the info. Have it sitting in recovery right now, not knowing what to do.

Related

Stuck at G1 Splash (Help Please)

As a disclaimer, I have already searched and found some people with the same issue. What I haven't found is someone that arrived at this problem in the same way I did. I am scared ****less of bricking my phone (and hope I haven't already). So at this point, I am looking for some help to figure out my best course of action.
I recently updated to JF1.5 using his updater app, and everything worked. Today when I received my new SDcard, I started the process to get apps on my SD following this tutorial: http://forum.xda-developers.com/showthread.php?t=512743
I got as far as partitioning my card using the Apps2SD application as described, doing everything the tutorial says. I began the partition on my phone, and let it sit.....and sit, and sit. It sat frozen on the partitioning screen (the one with the slider to select the size) for almost an hour before i pulled the battery. I selected 1444mb for the ext2 after reading that it was not a good idea to go higher than 1500mb.
Now, as stated the phone boots to the G1 splash and goes nowhere. I am however still able to boot in recovery mode using Home+Power. Interestingly, it says at the top:
"Android system recovery utility
Build: JFv1.42"
Not sure if this means that 1.5 didn't install correctly or what, but that's what it says.
I have no idea what to do at this point, and am scared to go on without some candid advice. Sorry for the noobishness of my description - if there is anything else needed to give accurate advice please let me know. Also thanks in advance for any help I can get!
Same thing happened to me, you have to reflash. I tried using that method and it never worked for me, although I already had the partition. So reflash jf 1.51 and you are golden. BTW that text you see in recovery is the recovery image version, until you switch to another it will say that.
meoshe said:
Same thing happened to me, you have to reflash. I tried using that method and it never worked for me, although I already had the partition. So reflash jf 1.51 and you are golden. BTW that text you see in recovery is the recovery image version, until you switch to another it will say that.
Click to expand...
Click to collapse
Thanks for the response. I'll have to find a way to get that image onto my SD card. I just bought a 16BG card and that was the card I was using when I ran into this problem.....oh wait a sec....
I'm assuming that the JF1.51 update.zip will still be on my old 1GB card from when I updated to JF1.51 via his updater app last week? If so then my life will be a lot easier, and I'll just swap back to that card, boot up in Recovery, flash from update.zip, and that should be it?
Just want to make sure before I put that old card back in and try to flash....
try wiping before you update? Also to mount your SDcard (if you need to) press alt-x in recovery (or in adb shell) and type
Code:
echo /dev/blockl/mmdblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
x2 that's what i had to do since my computer stopped reading sd cards.
Wipe then update.
I'd also recommend using CMv3.4 because the apps2sd is automated. It runs a2sd by itself
And with Cyanogen Recovery v1.2 you can move apps to sd card
First off, just want to thank everyone for the help. I successfully reflashed with jf1.51, but now I can't seem to sign in. I'm on the welcome screen, skipped the tutorial, entered my Gmail account and it sits for awhile trying to contact the server and then says there's a problem with the service or my sim card.
I know my sim card is provisioned for data, so not sure what's happening here...any ideas?
EDIT: Forgot I had to enter the Rogers APN settings, trying that now (Duhhh)
Abolfazl said:
Wipe then update.
I'd also recommend using CMv3.4 because the apps2sd is automated. It runs a2sd by itself
And with Cyanogen Recovery v1.2 you can move apps to sd card
Click to expand...
Click to collapse
I'm interested in this Cyanogen stuff, but no idea where to start. Any good tutorials? I was following this scene for awhile but kinda lost touch a few months ago - turns out there's been lots of developments.
t3mp3st said:
First off, just want to thank everyone for the help. I successfully reflashed with jf1.51, but now I can't seem to sign in. I'm on the welcome screen, skipped the tutorial, entered my Gmail account and it sits for awhile trying to contact the server and then says there's a problem with the service or my sim card.
I know my sim card is provisioned for data, so not sure what's happening here...any ideas?
EDIT: Forgot I had to enter the Rogers APN settings, trying that now (Duhhh)
I'm interested in this Cyanogen stuff, but no idea where to start. Any good tutorials? I was following this scene for awhile but kinda lost touch a few months ago - turns out there's been lots of developments.
Click to expand...
Click to collapse
It is pretty cut and dry. Cyanogen's Mod unleashes the G1 to its max. Apps2sd is automated and is working before you can even turn your phone on.
CMv3.4
CM Recovery v1.2
Abolfazl said:
It is pretty cut and dry. Cyanogen's Mod unleashes the G1 to its max. Apps2sd is automated and is working before you can even turn your phone on.
CMv3.4
CM Recovery v1.2
Click to expand...
Click to collapse
Cool, I guess I'll try it out now before trying to restore everything. I don't see a tutorial for it though, or am I to just follow the previous "How to root" tutorial and just use his image as the update.zip?
t3mp3st said:
Cool, I guess I'll try it out now before trying to restore everything. I don't see a tutorial for it though, or am I to just follow the previous "How to root" tutorial and just use his image as the update.zip?
Click to expand...
Click to collapse
no no no! just rename CM3.4 to update.zip, enter recovery (Home+power) wipe (alt+w) and flash (alt+s) after it says installation successful, reboot (Home+back)
you might also want to download his recovery image 1.2 like suggested in the posts above me
place the recovery image on your sdcard, do not rename it and do
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
alritewhadeva said:
no no no! just rename CM3.4 to update.zip, enter recovery (Home+power) wipe (alt+w) and flash (alt+s) after it says installation successful, reboot (Home+back)
you might also want to download his recovery image 1.2 like suggested in the posts above me
place the recovery image on your sdcard, do not rename it and do
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
Click to expand...
Click to collapse
Thanks a lot, going to try that now with my 16GB card. And just to be clear (last questions in this thread, I PROMISE!), I should flash with CM3.4 and THEN install the recovery image, or vice versa?
Also, with CM3.4, will I have to go through to steps again to try to partition my card (which is where i ran into the problem from post #1), or is there some automatic process built into his super-de-duper ROM?
Thanks again to all for the speedy responses!!
t3mp3st said:
Thanks a lot, going to try that now with my 16GB card. And just to be clear (last questions in this thread, I PROMISE!), I should flash with CM3.4 and THEN install the recovery image, or vice versa?
Also, with CM3.4, will I have to go through to steps again to try to partition my card (which is where i ran into the problem from post #1), or is there some automatic process built into his super-de-duper ROM?
Thanks again to all for the speedy responses!!
Click to expand...
Click to collapse
Don't worry asking questions is good as long as they are intelligent. You should flash CM3.4 and then the recovery image, as that is what i did. However, i don't think it really matters. To be safe, flash CM3.4 and then the recovery image.
And to your question pertaining to partitioning your SDcard, you can try MarcusMaximus' Apps2SD2 app which formats the card for you here
Unzip it to your sdcard and install it using ASTRO file manager or some other file manager.
If you have adb working,
Code:
adb install AppstoSD2.apk
if you have other questions you can always contact me on AIM- roflzbrianxdd
alritewhadeva said:
Don't worry asking questions is good as long as they are intelligent. You should flash CM3.4 and then the recovery image, as that is what i did. However, i don't think it really matters. To be safe, flash CM3.4 and then the recovery image.
And to your question pertaining to partitioning your SDcard, you can try MarcusMaximus' Apps2SD2 app which formats the card for you here
Unzip it to your sdcard and install it using ASTRO file manager or some other file manager.
If you have adb working,
Code:
adb install AppstoSD2.apk
if you have other questions you can always contact me on AIM- roflzbrianxdd
Click to expand...
Click to collapse
Thanks a ton, I'll get to this right after i finish this delicious sub! I'll also add you so I can IM if i have any more questions..
t3mp3st said:
Thanks a ton, I'll get to this right after i finish this delicious sub! I'll also add you so I can IM if i have any more questions..
Click to expand...
Click to collapse
Cool, Best of Luck with the flashing
alritewhadeva said:
no no no! just rename CM3.4 to update.zip, enter recovery (Home+power) wipe (alt+w) and flash (alt+s) after it says installation successful, reboot (Home+back)
you might also want to download his recovery image 1.2 like suggested in the posts above me
place the recovery image on your sdcard, do not rename it and do
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
Click to expand...
Click to collapse
Alright...I successfully partitioned my card, flashed with CM 3.4, but now when I try this instruction to install the new recovery, i get this error msg in Terminal:
error writing recovery: Permission denied
Any ideas?
You have to enter su before the code..
Code:
su
then
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
meoshe said:
You have to enter su before the code..
Code:
su
then
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
Click to expand...
Click to collapse
I did not enter the su, I will try that now thanks. In the mean time I also performed this step:
13. My /system/sd is read only and/or didn't upgrade to ext3!
Your filesystem is probably corrupt. Boot into recovery and open a console. Run "mount /system" then "/system/bin/e2fsck /dev/block/mmcblk0p2" and fix your filesystem. Reboot.
from: http://forum.xda-developers.com/showthread.php?t=518851
So I hope that didn't hurt anything...ill try with the su now. Thanks!
edit: out of curiosity, what does the "su" stand for? I feel if I know this it may help me to remember to enter it before any commands.
edit #2: does it stand for "Super User" to allow super user permissions? I gathered this after entering SU prompted me to allow superuser access
New recovery.img successfully installed! Thanks again to everyone that helped me with this.
I know I can transfer apps to SD easily from recovery now, but is there also a similar way to do it from the phone (or do they install to the SDcard by default now?)
Hey T3MP3ST... how did it go with upgrade to cm3.4
I had the same problem as you mentioned start of the post....
(stuck at g1, after partition).
this cm3.4 sounds like the solution for me to have apps2sd..
as it is in the ROM automatically, if i understood correctly.
dynamisoz said:
Hey T3MP3ST... how did it go with upgrade to cm3.4
I had the same problem as you mentioned start of the post....
(stuck at g1, after partition).
this cm3.4 sounds like the solution for me to have apps2sd..
as it is in the ROM automatically, if i understood correctly.
Click to expand...
Click to collapse
Hey there, with the help from everyone in this thread, along with the partitioning instructions using Ubuntu (if you still need to partition your card) from tubaking182 found here: http://forum.xda-developers.com/showthread.php?t=523648, It was great.
I just finished flashing with that ROM and then installing CM's recovery image (which is AWESOME...trackball selection, Apps2SD in one click)
I HIGHLY recommend it. If you have any problems, I'm sure you'll find most of the answers in this thread. If not, try PMing one of the helpful respondents, or I may be of SOME help with some minor questions or assurances.

Using flash_image to upgrade recovery partition failed... now what?

Hello folks,
First time poster here, first time I haven't been able to find a fix already posted...
Anyway, I wanted to try out the new Cyanogen mod after not having tried any new ROMs in a long time. Got 5.0.7 installed and running no problem. Then I noticed on the Cyanogen Mod site that there was also a Cyanogen recovery image. "Might as well have everything from the same source," I thought. I got the file, put it on the SD card, and used the terminal on the phone to execute "flash_image recovery /sdcard/cm-recovery-1.4.img," then tried rebooting into recovery mode. No good. Just get hung up at the "myTouch 3g" screen. At this point, I thought I was well and screwed, but fortunately I'm still able to boot normally.
Tried reflashing the same image, then other recovery partition images. No dice. Where do I go from here? I'm used to fixing stuff I've screwed up through the recovery partition, not the other way around!
I appreciate any help or advice!
Sincerely,
Tom
hey tom,
this will fix you up:
install "rom manager" from the market
flash his recovery image (theres in option for that)
then look for the option that lets you flash Amon Ra 1.7.0
let it load, power off & then check.
trust me this is bound to fix your problem.

[Q] bricked

Hi !
today I decided i should upgrade from CM7.0.2 to nb 118. But I first installed latest radio. I did a backup at this point. The radio flash went ok, the phone booted and everything worked fine.
I installed nightly build 118 from ROM manager without google apps, and with a dalvik wipe (no data/cache wipe). The phone booted up ok, but some widgets had disapeared, some shortcuts didn't work and some apps had disapeared too, the autorotation of screen at 0° had been unticked too... I rebooted, and finally decided I should revert to my backup.
That's where the real problem happens : after the backup restoration, the phone is stuck in a boot loop.
I can start with fastboot mode, but I can't access recovery mode, the red exclamation mark is there...
I'm not sure this tutorial : http://forum.xda-developers.com/showthread.php?t=751265 is adapted to my situation, should I follow it ?
Thank you for your help !
PS : I'm S-OFF
This should be @ the Q&A section but anyway, here we go:
I just had that bootloop situation myself and yes, you should follow that usb unbrick tutorial. That'll help you. Also, you should try if you can get to fakeflash by pressing VOLUP + POWER while @ the red exclamation window. If you can and you should be able to, search XDA for "fakeflash clockworkmod" or something similar, you should find a CWM image in a ZIP form. Then put that image into your SDCard, rename it to update.zip, go into the fakeflash menu and apply update.zip, it should fly you to the real recovery menu where you can do a full wipe and flash your ROM again.
Hopefully I'm not forgetting anything =D At least that's how I solved my situation and my phone is working fully again!
Hi.
Do you have the update.zip from recovery clock in the root of your sdcard, if so just press volume up and the power down at the same time, or the other way around ;-) when it change picture choose option, install update.zip and you should be in recovery mode
Im a noob, so dont laugh if i have written it the wrong way
Cheers, and good luck.
Jesus chist, it is written in the second post... Damn.
Hello trying to recover as well from a bricked HTC legend.
I cam unable to get to the update.zip to run.
it fails to verify the file.
and when i do get in to recovery I get E:Can't open /cache/recovery/command
i was trying to root it and it is not going so well I just want to get it back to 2.2
Please help
DroidFreak07 said:
Hello trying to recover as well from a bricked HTC legend.
I cam unable to get to the update.zip to run.
it fails to verify the file.
and when i do get in to recovery I get E:Can't open /cache/recovery/command
i was trying to root it and it is not going so well I just want to get it back to 2.2
Please help
Click to expand...
Click to collapse
That "Can't open /cache etc." error message indicates that you are in the fake-flash menu. Do you have a working recovery image in the root of your SDcard renamed to "update.zip"? If not, try searching the forum for "clockworkmod fakeflash" or something similar and it should show some topics that will help you.
I recently got my Legend working again from bootloop and usb brick so I'm ready to help you with your further problems that may occur =)
EDIT: And please, make sure that your recovery zip is just "update.zip" and not a ZIP file named "update.zip" cause then it will be a file called "update.zip.zip" =D
taksu said:
That "Can't open /cache etc." error message indicates that you are in the fake-flash menu. Do you have a working recovery image in the root of your SDcard renamed to "update.zip"? If not, try searching the forum for "clockworkmod fakeflash" or something similar and it should show some topics that will help you.
I recently got my Legend working again from bootloop and usb brick so I'm ready to help you with your further problems that may occur =)
EDIT: And please, make sure that your recovery zip is just "update.zip" and not a ZIP file named "update.zip" cause then it will be a file called "update.zip.zip" =D
Click to expand...
Click to collapse
Still nothing it try's to verify the file and fails.
any other Ideas? please.
DroidFreak07 said:
Still nothing it try's to verify the file and fails.
any other Ideas? please.
Click to expand...
Click to collapse
I hope you read this and if it isn't fixed yet then take a rom YOU KNOW that works.
go into recovery Go to "mounts and storage" and format SYSTEM. NOTHING ELSE.
Do a wipe and THEN flash your zip.
Remember to NOT go out of recovery when you have formatted the system.
I hope it helps.

HELP! Bought a device that turned out to be rooted. Need to go back to Stock.

First, I knew nothing about rooting any devices up until 2 hours ago. Ever since, I've been trying to set my phone up, but have failed and am extremely miserable at the moment.
So I tried to install the stock rom by using someone else's Nandroid backup, but it says that it "failed to find "cache" partition to mount at "/cache"
I tried to look at different threads and it pointed me to this: http://forum.xda-developers.com/showthread.php?t=988686&highlight=i9023
I read that if I was to "flash_image" that file onto my phone it would allow me to install the stock ROM.
But I can't find anywhere how to do this. At this point, my phone has no ROM on it. If i dont start in recovery, it says stuck at the Google Logo. If it makes any difference I'm on Rogers/ATT device.
Please, help
Is the stock rom zip file installed on SD storage? If so all you need to do is boot into recovery, install from SD card, unzip file (the stock Rom) and then reboot.
Sent from my Nexus S 4G using XDA App
unfortunately, there is no stock ROM on the SD card.
I tried installing everything manually.. I installed the android-sdk, got the usb drivers running, and adb works.
but none of the "flashboot" commands work. they all get stuck on "waiting for device" on the command prompt. I was trying to flash a ROM through the computer.
EDIT: fixed all issues.
used PDANet to reinstall all drivers then installed the new 4.0.0.2 clockwork. made it work. thank god.
I was in the same boat as I just bought mine used yesterday.
dl the stock 2.3.4 rom here. it comes as root or non rooted.
http://forum.xda-developers.com/showthread.php?t=1060192&highlight=stock+rom
then flash through recovery...but keep in mind this won't re-lock your bootloader. if you want to re-lock your bootloader, you have to do it via adb.
BTW, you can access your sd storage via recovery.
Edit: Oops didn't read that you had fixed it. Neeeevermind.

clockwork recovery and nook 1.4.1 update

My problem is at one time or another I must have accidently installed clockwork recovery on the emmc of my nook. I can boot into the nook's software just fine, but when I tried to apply the update it boots into clockwork mod and gives an error and won't install the update.
I normally always use cm7 off the sd card, but I want to have the new update on the nook when I want to boot to it.
My question is how do I get clockwork recovery off the emmc so I can install the update? Any help would be greatly appreciated.
Dude, I'm in the same boat. I didn't think I had CWM on there, but alas, I do...
The problem is that when it tries to execute the install an error comes up saying that the ROM is unsigned. Weird cause it came from the Nook website...
This might help
I had the same problem. This thread solved it for me. I used the file to remove CWM.
http://forum.xda-developers.com/showthread.php?t=914690

Categories

Resources