Database Info

[q] help flashing freinds g1

I said I would flash cyanogenmod on a friends G1 because he was fed up with 1.6. I've flashed many custom ROM's on several different devices before but I've made a mess of things with this G1 and I can hardly hand back an unusable phone so I would really appreciate your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work because I would need to use DangerSPL as the /system partition is too small on the dream/g1. To be honest at this point I can't be bothered with to do that and this guy will be happy with anything above 1.6 to be honest so I thought I would try and flash CM4 because that's based on Eclair I believe (and so it not require I use DangerSPL or any other method to repartition the NAND). However, I tried it twice and still no luck.
At this point I'm somewhat panicking as I cannot seem to make the phone boot and it isn't even mine! Is anyone able to help?

Anyone? Please?
Look, at this stage I will forget custom roms etc. If anyone can tell me the easiest way to get this phone booting android again i would be very grateful.
Even if you could just tell me exactly how to restore it to stock 1.6 from here?
I have flashed roms on phones before - never had a problem but this is driving me crazy - please help!

wollac11 said:
Hi I said I would flash cyanogenmod on a friends G1 coz he was pissed off with 1.6 but im having trouble and I can hardly hand back an unusable phone so i really need your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work coz i would need to use DangerSPL coz the /system partition is too small on the dream/g1. Tbh i'm tired so I cba to do that and this guy is not that technical so he will be happy with anything above 1.6 so I thought I do CM4 coz thats 2.0 or 2.1 i seem to remember (and it not require I use DangerSPL) - tried it twice and still not luck.
HOW THE HELL CAN A GET THIS STUPID THING TO WORK AGAIN!??
MAJOR PANIC AS THIS IS NOT MY PHONE - PLEASE HELP!!!
Click to expand...
Click to collapse
Try this thread: http://forum.xda-developers.com/showthread.php?t=803482. I hope it helps.

It's been way too long since I rooted mine to be of any real help but I shall try nonetheless.
Firstly, there is a guide in the G1 forum to unroot and get back to stock firmware: Here (but note that I've never done this).
I must stress though (admittedly from memory) that if you have flashed an SPL or radio image at all, be VERY careful about the order in which you revert back to stock (or go to get a custom ROM depending on which way you decide to go). The G1 is very picky, and flashing things (mostly SPL and radio IIRC) in the wrong order will brick the device. That said, if you follow the instructions you find to the letter you should be OK. But yeah, read twice, flash once.
There is a lot of information in the stickies in the G1 forum. It could take a while to wade through but it should all be there. Failing that, post in the Q&A or General G1 subforums and I'm sure a current user will help you out.
I apologise if I've just posted a bunch of stuff you already know/have read - like I said, I've not used the phone in a while - just trying to offer what I can.

Thanks
No worries now guys i've done it! It was quite complicated but its all sorted now. If anyone is trying this and has the same (or similar) issue then pm me and I will tell you how I sorted it.
Otherwise thanks guys and you can conciser this thread:
---------------------closed--------------------------

Clockwork Mod Not Flashing ROMS

Hello, please let me know what I'm doing wrong, I've looked exhaustively for a solution to my problem on my own but I can't seem to find one:
1.) Rooted my G2x
2.) Installed Clockwork ROM Manager
3.) Copied two separate Gingerbread ROMs, Cyanogen 7, and Modaco into Root Folder (no sd card, just phone storage)
4.) Tried flashing both Roms multiple times with Rom Manager by both rebooting into recovery and installing from .zip (this option won't display either of the ROMs, just the log file folder.) I have tried installing .zip from SD in ROM Manager, and the phone just reboots as if nothing has happened.
*I believe ROM Manager does have difficulty mounting the phone storage, as it takes a full twenty count before attempting to flash the ROM.
**I don't know if this helps, but I have not received the OTA Gingerbread update from T-Mobile (even when my phone was unrooted), and when I prompt for the OTA update, I receive a "connection error" message. The LG Updater Tool indicates that my phone is "up to date" when it clearly, is Froyo 2.2.2.
Any help would be greatly appreciated with this issue guys, I usually scour forums for answers to my questions or fumble my way through it myself, but this has really sucked out lots of hours from my life.

No external sd card
You have to have a external to flash roms if im not mistaken

when you install recovery there are 2 choices external storage and internal storage if you dont have an sdcard reinstall clockwork using the internal option. that should do the trick for you.

eagle1967 said:
when you install recovery there are 2 choices external storage and internal storage if you dont have an sdcard reinstall clockwork using the internal option. that should do the trick for you.
Click to expand...
Click to collapse
I am going to try with an external SD card. Also, I am unsure of how to flash it to use internal storage, I checked the settings through ROM manager and couldn't find out how to do it. Is this something I access during Recovery mode? Thanks for the suggestions so far guys, I'll definitely post with results.

pathmarkpolice said:
Hello, please let me know what I'm doing wrong, I've looked exhaustively for a solution to my problem on my own but I can't seem to find one:
1.) Rooted my G2x
2.) Installed Clockwork ROM Manager
3.) Copied two separate Gingerbread ROMs, Cyanogen 7, and Modaco into Root Folder (no sd card, just phone storage)
4.) Tried flashing both Roms multiple times with Rom Manager by both rebooting into recovery and installing from .zip (this option won't display either of the ROMs, just the log file folder.) I have tried installing .zip from SD in ROM Manager, and the phone just reboots as if nothing has happened.
*I believe ROM Manager does have difficulty mounting the phone storage, as it takes a full twenty count before attempting to flash the ROM.
**I don't know if this helps, but I have not received the OTA Gingerbread update from T-Mobile (even when my phone was unrooted), and when I prompt for the OTA update, I receive a "connection error" message. The LG Updater Tool indicates that my phone is "up to date" when it clearly, is Froyo 2.2.2.
Any help would be greatly appreciated with this issue guys, I usually scour forums for answers to my questions or fumble my way through it myself, but this has really sucked out lots of hours from my life.
Click to expand...
Click to collapse
I can't quite tell if you used rom manager to flash CWM, but if you did then make sure to use nvflash. I don't know if it could cause things not to work, but it's the only way to guarantee you can always get into recovery. As people have said above, try to use external, although I hadn't read anything about problems with using internal to flash roms, at least if nvflash has been used.
I'll assume you've already heard of wiping/factory reset and all that since you joined a few years back, but make sure to do it when going to a new rom. As for the update issues, I would say just restore stock froyo, maybe from the nandroid tgagunman created if something is wrong with yours, factory reset it just to be careful, unroot using superoneclick, flash stock recovery using tgagunman's one click recovery flasher, and make sure usb drivers are up to date.
If you really can't get the new baseband and roms working after all that... tell t-mobile you can't get the update and ask for a new one haha.

Thanks Guys...
Danish, Eagle, Water, thanks a lot to all of you guys. I was able to flash a new ROM using an External SD card, I'm still having problems finding a ROM that is stable and is compatible with all of the apps I want to use (I'm currently having difficulty installing Tooyoou on the Bionix ROM I downloaded, which is otherwise AWESOME). I mean, it's not that big of a deal, but I'd like to get my extra $2.50 a month from the program.

Oh and NV Flash...
NV Flash helped me when I messed up my G2x's ability to boot into recovery with a Cyanogenmod 7 ROM build. Here's a link to a guide that helped immensely for anyone who finds themselves in this thread with a similar issue:
http://forum.xda-developers.com/showthread.php?t=1056847

Htc one S. Time of the month.

Hi need a bit of help with this one if possible.
start the top..
went to flash leedroids rom..flashed boot image but forgot to pull rom over.
so had various issues getting over in the end had to mess around with recoverys and totally wipe my sd for it to be recognized.
so i solved all this then..now the issue is..of everything i push over..only one rom boots up and installs fine..and that is a cm9 test without sd mounting..so it solves nothing.
any ideas of how to get a rom on there where i can mount the sd..download a rom and put it on..
ill be honest..htc+internal sd card=not happy
ive pushed leedroids..virtuous..utbs rom but nothing.
i tried aokp but it didnt even push.
with these also some get corrupted by a protocol failure..
many questions. currently has cm9 on..but no mounting..so great

Did you already try a factory reset after flashing the stock recovery (e.g. from MoDaCo)?

-
Hi rootrider, yeah i followed a post i found..
basically i used the one click toolkit to flash the stock recovery..then cleared storage and all data etc.then installed clockwork back..it doesnt like the working roms though
cm9 is the only one i can boot up..at least it sees the sd card again in clockwork though

Had your problem as well... I don't remember exactly what I did to get out among many other things (sh..).
Had some trouble as well flashing stock recovery with the one click tool kit. It didn't work as expected. So I did it with adb. Just keep on trying, there is a way out.

-
My next course of action is, to flash the stock recovery, clear everything,reinstall clockwork then install aokp..if its something with the type of rom.maybe that will work..i can mount..get a rom on the sd and resume business as usual..
debatebale whether itll work lol

If this doesn't help get Thor's hammer and flash your appropriate RUU (again).

Easiest method would be to run an RUU and start over again. I see your vodafone UK so try this one
http://dl.dropbox.com/u/69014495/RU..._2_10.23.31501S.10L_release_258386_signed.exe
It also includes the new radio too !
Just relock bootloader before running it, After its finished unlock and fastboot flash cwm..
easy peasy !!

--
thanks people, im running leedroids rom now, seemed my issue was is after pushing the file over i just tried to install immediatley..after a couple of reboots just for the hell of it,untouchables rom started installing...phew..
sadly all my sd contents have gone..very dissapointed with the sd card business!
still least its working again!
thankfully azzle didnt need to go back to ruu

Aye, captain. Glad to read this.

[Q] Help... Galaxy s3 i9300 cm9 suddenly huge 6gb Nandroid!!

Yesterday i updated to the at the time latest CM9 nightly, and im not sure if that is the cause but before then my backups were aroud the 1gb mark, then, when i tried to do another backup after updating it kept failing. when i restarted my phone the entire memory was full of the aborted backup.
I deleted stuff until the free space outweighed the used space so i could definitely fit whatever size the backup was and it worked but the result was 6gb!!
Is this a problem anyone else has had with or without cm9? as i said im not 100! sure that was the cause but it does seem likely.
If theres a better place to ask this question please let me know.
... Ive tried re flashing clockwork mod recovery and re installing rom manager. I also flashed the touch version with rom manager. None of that has made any difference so far. Any help would be greatly appreciated as im no expert.

Updating/Installing/Uninstalling ROM manager doesn't affect ClockworkMod recovery at ALL. ROM manager's sole purpose is to install Clockworkmod and help beginners with flashing ROMs. And if you have the money HELP you find ROMs as far as I can see.
As for your problem, it looks very weird, Reflashing a ROM would probably solve it, but you would love to make a backup first.
Try using Titanium backup to backup your apps and some information. Sync your contacts and calendar most importantly and make sure you backup everything. Then try flashing a different ROM. Remember the ROM is nightly for a reason; this could be the reason.
Cheers

well i think i've found what it was... its a known problem with recovery version 5.8.4.5... its backing up everything resulting in huge backups... the weird thing is its the same version ive been using for a few weeks and ive never had that problem before. Now i just have to work out how to replace this version with the older version.

[Q] Stuck on Bootloader. No ROM on disk. Repartioned Flash ROM incorrectly

HTC One-S US version. Wow. I will try to keep this short and would really appreciate any input I can get. I should probably resolve myself to it being bricked but who knows.
I updated my device last night to the latest Cyanogen mod (was already running the last release). I factory reset before. While reloading the new version the device froze on the white HTC screen.
I was able to get back to the bootloader and at times the Clockwork Recovery screen. Somehow in the process the SD card became unmounted. I followed the *numerous* threads here on how to resolve it but to no avail. At one point I reformatted the SD card and, for some reason, repartioned the flash ROM allocation to a size much to small to run Cyanogen (I tried to reinstall the stock software from .exe file after relocking the device and this is how I determined the allocated size was to small.
So I am now stuck on the bootloader screen. Is it possible from either ADB commands or ? to correctly partition the drive again? I have Googled and Googled and probably spent more time flying solo on this than I should of (at least past my expertise). I have tried the usuals, factory reset, clear storage, etc. When I tried to use the HTC software to reload the original build, it showed no existing OS on the device. So I am stumped and will provide any information as needed to clarify this confounding problem. Thank you.
michaelsean

It seems like you might have to go back to a stock RUU, What version of HBoot are you on?