Database Develop

Cant flash anything on a DEV G1!

Hello all.... I am working on a group project where we will be using a dev G1. The phone was shipped to a another group member and before I can get my hands on it, he decided to upgrade the firmware from 1.0 to 1.6, having very little knowledge of android beforehand and therefore he cant really tell me what exactly he did either. He followed the directions on the HTC website. As far as i can tell, I do have the 26I radio, engineering SPL and 1.6 installed currently, not sure about the recovery though (i.e. stock 1.0 or 1.6). When I got the phone, root access was gone but followed some simple steps on this website to regain it. By way of typing in "su" in terminal emulator and in ADB shell, I now also have su. However I still cant flash anything. When trying to flash cm 4.2.5 in the recovery, the system verifies it and then aborts installation. I then tried to install the Amon-RA recovery to no avail. Tried fastboot, ADP, terminal, im not sure how to access the /data/ partition on the phone and there is no option for acessing the console in the recovery menu. Installing through ADB dosnt work, no test-keys in current recovery. In fastboot it says "okay" for both sending and writing the recovery but rebooting into recovery shows that it didnt work. In terminal it says "flash_image: not found". I'm kinda lost and need some help....
All I need is cm4.2.5 on the phone with root.
Thanks in advance.....
Edit: I triple and quadruple checked the name of the recovery image when trying to install through terminal. I'm pretty sure it cant find the command "flash_image" and not the file itself. Just wanted to clarify...

You could try downgrading to RC29: http://wiki.cyanogenmod.com/index.p...ngrading_to_RC29_.28US.29_or_RC7_.28Europe.29

halr9000 said:
You could try downgrading to RC29: http://wiki.cyanogenmod.com/index.p...ngrading_to_RC29_.28US.29_or_RC7_.28Europe.29
Click to expand...
Click to collapse
Tried that, already... That method only works for the stock T-Mobile G1's which have a different SPL. The Dev G1's come with engineering SPL and I have no idea how to flash the .nbh image from that. All it does I think is enable Fastboot, I cant get it to do anything else.

This fails?
fastboot flash recovery recovery.img

Nope... No luck, it says:
sending 'recovery' <4456kb>.... OKAY
writing 'recovery' <4456kb>.... OKAY
and then I reboot using "fastboot reboot", wait till the homescreen loads, and then go back into recovery and it still shoes the the triangle and the !.....

Bump...
Anyone?? Right now we just have a reallly expensive paper-weight in our hands ANY help/thoughts/comments would be very appreciated...

This thread is meaningless since there is NO SUCH THING as a "DEV G1".
alilbitanuthin said:
Hello all.... I am working on a group project where we will be using a dev G1. The phone was shipped to a another group member and before I can get my hands on it, he decided to upgrade the firmware from 1.0 to 1.6, having very little knowledge of android beforehand and therefore he cant really tell me what exactly he did either. He followed the directions on the HTC website. As far as i can tell, I do have the 26I radio, engineering SPL and 1.6 installed currently, not sure about the recovery though (i.e. stock 1.0 or 1.6). When I got the phone, root access was gone but followed some simple steps on this website to regain it. By way of typing in "su" in terminal emulator and in ADB shell, I now also have su. However I still cant flash anything. When trying to flash cm 4.2.5 in the recovery, the system verifies it and then aborts installation. I then tried to install the Amon-RA recovery to no avail. Tried fastboot, ADP, terminal, im not sure how to access the /data/ partition on the phone and there is no option for acessing the console in the recovery menu. Installing through ADB dosnt work, no test-keys in current recovery. In fastboot it says "okay" for both sending and writing the recovery but rebooting into recovery shows that it didnt work. In terminal it says "flash_image: not found". I'm kinda lost and need some help....
All I need is cm4.2.5 on the phone with root.
Thanks in advance.....
Edit: I triple and quadruple checked the name of the recovery image when trying to install through terminal. I'm pretty sure it cant find the command "flash_image" and not the file itself. Just wanted to clarify...
Click to expand...
Click to collapse

Pretty sure there is...
http://developer.htc.com/adp.html

Bump...
anyone?

alilbitanuthin said:
Pretty sure there is...
http://developer.htc.com/adp.html
Click to expand...
Click to collapse
Do you see ANYTHING on there that says "G1"?
Answer: No you definitely do NOT.

If I remember correctly, after you use fastboot to flash the new recovery image, you can't let the phone reboot or it will overwrite the recovery with the stock recovery image
The solution would be to use fastboot to flash either Cyanogen's or Amon_RA's recovery image, and be quick here, but when you send the fastboot reboot command be holding down the home button on the phone so it will boot to the custom recovery image

lbcoder said:
Do you see ANYTHING on there that says "G1"?
Answer: No you definitely do NOT.
Click to expand...
Click to collapse
lol, no need to nitpick, about the name no less. Thats the least of my worries
As long as you get the message across...
jackslim said:
If I remember correctly, after you use fastboot to flash the new recovery image, you can't let the phone reboot or it will overwrite the recovery with the stock recovery image
The solution would be to use fastboot to flash either Cyanogen's or Amon_RA's recovery image, and be quick here, but when you send the fastboot reboot command be holding down the home button on the phone so it will boot to the custom recovery image
Click to expand...
Click to collapse
That maybe it I'll give it a try as soon as I get back home. Thanks a lot for the help!!

Thanks a lot jackslim, finally got it to work!

My rooting woes

So I finally rooted my N1 today using SuperOneClick. I'm on FRG83. Here's what I've done so far...
Rooted.
Installed ROM Manager.
Flashed with ClockworkMod.
Unable to do a NANDBackup -> Re-rooted -> Still unable -> Flashed with RA -> Successfully did a NAND Backup.
Downloaded MoDaCo's ROM -> Tried flashing -> "Signature Verification Error"
Tried flashing again -> Unable to enter recovery.
Flashed with an older version of Clockwork -> Entered recovery -> Tried flashing -> Same error.
Downloaded Cyanogen 6 -> After multiple tries -> Entered recovery -> Same error
Wiped/Factory Reset -> Cannot enter recovery.
There has to be a simple explanation. Please help!
Thanks a lot

Fastboot oem unlock

daveid said:
Fastboot oem unlock
Click to expand...
Click to collapse
Will that unlock the bootloader? Because I rather keep it locked for warranty!
Thanks

Try using RA recovery instead. You can install the last stable version through ROM manager.

fzr-r4 said:
Try using RA recovery instead. You can install the last stable version through ROM manager.
Click to expand...
Click to collapse
Did do it but it doesn't alway boot into recovery. It usually boots with a Android+triangle+! . If it does boot in recovery, it says signature verification error.

i.mac said:
So I finally rooted my N1 today using SuperOneClick. I'm on FRG83. Here's what I've done so far...
Rooted.
Installed ROM Manager.
Flashed with ClockworkMod.
Unable to do a NANDBackup -> Re-rooted -> Still unable -> Flashed with RA -> Successfully did a NAND Backup.
Downloaded MoDaCo's ROM -> Tried flashing -> "Signature Verification Error"
Tried flashing again -> Unable to enter recovery.
Flashed with an older version of Clockwork -> Entered recovery -> Tried flashing -> Same error.
Downloaded Cyanogen 6 -> After multiple tries -> Entered recovery -> Same error
Wiped/Factory Reset -> Cannot enter recovery.
There has to be a simple explanation. Please help!
Thanks a lot
Click to expand...
Click to collapse
hints on rooting without unlocking bootloader:
http://forum.xda-developers.com/showthread.php?t=792016
general Nexus One wiki:
http://forum.xda-developers.com/showthread.php?t=744720
besides I would not worry about unlocking the bootloader (fastboot oem unlock); it has been proven several times that HTC will honor the warranty if the device has a hardware failure, even if the bootloader is unlocked.
it also seems to be the easiest and safest way to get to root
... on another note... you want your thread to be in Q&A, not development. a moderator will probably move your thread soon.

daveid said:
Fastboot oem unlock
Click to expand...
Click to collapse
this. only. this.

I feel the guy (or gal). I like that my initial "X" screen doesn't have the unlocked icon on it. Big deal? I guess not? Personal preference? Yes.

I too like the boot logo with out the padlock, it looks tacky.

The one time I tried clockworkmod, it messed my phone up, I always go with RA's recovery.
Sent from my Nexus One using XDA App

Google's stock ROM overwrites the recovery at boot. That is why your RA or ClockworkMod is not sticking. As a workaround, you should flash your recovery before rebooting into it else you will boot into the stock one.

Here's where I'm at right now...
I can boot into recovery every time now.
On ClockworkMod... once I select the .zip file (tried 3 now), it starts. Opening, verifying. As soon as it gets to the installing command it exits and goes back into recovery.
On RA, it always says signature verification failed.
Any ideas?
Thanks for all your help guys!

i.mac said:
Here's where I'm at right now...
I can boot into recovery every time now.
On ClockworkMod... once I select the .zip file (tried 3 now), it starts. Opening, verifying. As soon as it gets to the installing command it exits and goes back into recovery.
On RA, it always says signature verification failed.
Any ideas?
Thanks for all your help guys!
Click to expand...
Click to collapse
1) did you unlock the bootloader (fastboot oem unlock)? -- i recommend it
2) which version of amon_ra are you using?... all above 1.8 (i am using 1.9 alpha) allow flashing unsigned *.zip files
3) make sure you have downloaded the CORRECT amon_ra recovery *.img file (for NEXUS, any other will not work)
4) rename the AR recovery file to recovery.img (for easier typing and error minimization when flashing in fastboot) then put it in a folder where fastboot can find it
5) fastboot flash recovery recovery.img
6) flash a ROM of your choosing (i like CM6) - make sure it's fully downloaded and the zip file is not corrupt (= check the md5 sum)
7) flash in amon_ra recovery
8) if you use CM6, have gapps ready (http://wiki.cyanogenmod.com/index.php?title=Gapps) and flash immediately after CM6
9) reboot

i.mac said:
Here's where I'm at right now...
I can boot into recovery every time now.
On ClockworkMod... once I select the .zip file (tried 3 now), it starts. Opening, verifying. As soon as it gets to the installing command it exits and goes back into recovery.
On RA, it always says signature verification failed.
Any ideas?
Thanks for all your help guys!
Click to expand...
Click to collapse
Get Amon RA 1.9a like so (has instructions for locked bootloader):
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Recovery_Images

I use RA 1.8.0.1 to skip around signatures. I'm not unlocked and haven't had issues flashing or the phone unrooting.
Sent from my Nexus One using XDA App

Ignore everyone saying you have to unlock the bootloader, there's zero reason to do so..
You just didn't follow instructions. As someone posted, follow the link for the XDA Wiki recovery images. You missed the part where you have to remove two files, or it restores the recovery image. /!\ symbol = stock recovery; the system restores it automatically if you don't remove the two files.
So right now, read the guide, re-flash RA, remove the two files, then your recovery will stick.
As for one this-or-that ROM doesn't install; ask in their thread.

khaytsus said:
Ignore everyone saying you have to unlock the bootloader, there's zero reason to do so..
Click to expand...
Click to collapse
HTC has proven that they will fix hardware (dust, power button) with or without an unlocked bootloader so circumventing 'fastboot oem unlock' for warranty purposes is not only a bit more trouble for those who can't read/are new.. its also counter productive in light of the whole G2 debacle.. kinda like they give us nice things and we abuse them anyways..

crachel said:
HTC has proven that they will fix hardware (dust, power button) with or without an unlocked bootloader so circumventing 'fastboot oem unlock' for warranty purposes is not only a bit more trouble for those who can't read/are new.. its also counter productive in light of the whole G2 debacle.. kinda like they give us nice things and we abuse them anyways..
Click to expand...
Click to collapse
They denied my warranty (trackball does not scroll downwards anymore) stating they would have to charge $200 for the repair. But, I found a local shop that will do it for $40 and have it done in an hour. I have no regrets unlocking my bootloader, that is why I bought this phone.
I do believe it is the best method, and I would not abuse it just for warranty claims - in hopes that there will be another device with this ability.

Honestly, what's the point of owning a Google Developer phone if you're going to *****-foot around unlocking the full potential of your device?
Honestly, the first thing I did when I got this phone in the mail was unlock it. Best decision ever.

wdfowty said:
Honestly, what's the point of owning a Google Developer phone if you're going to *****-foot around unlocking the full potential of your device?
Honestly, the first thing I did when I got this phone in the mail was unlock it. Best decision ever.
Click to expand...
Click to collapse
To each his or her own, but I have the potential of my phone fully available. If I'd gotten the N1 in January, I may have unlocked the bootloader.
Since there were good root options when I got the phone without unlocking the bootloader, though, I was happy to go that route.
Sent from my Nexus One using XDA App

[Q] Nexus One Gingerbread 2.3.3 HOW TO ROOT?

I've just updated my Nexus to 2.3.3 and lost my root. I tried rageagainstthecage again, but it seems that particular exploit is now closed. In fact, when I ran it and adb reset, I could no longer USB debug on my phone until I restarted it.
So... How do we root the Nexus One with 2.3.3 ??
Thanks, Steve.

looking for similar thing too, i had rooted stock N1 2.2.1 then updated to 2.3.3 (CMW with custom ROM+rooted) works pretty cool, what i am wonder, what about if i flash not rooted version , what happen after that, do i lose? ability to root again? or i can just flash su?
thx

The inventor of rageagainsthecage has stated it no longer works on gingerbread. He has another exploit called gingerbreak which he will release when more devices get gingerbread or something. For now, downgrade and flash a pre-rooted gingerbread build. Good luck with that, I still can't seem to downgrade...

Are both you guys running an unlocked bootloader with custom recovery?
If so, then head over to this thread: http://forum.xda-developers.com/showthread.php?t=968396 and download the su.zip that's attached at the bottom of the first post.
Once downloaded, put it on your SD card, boot into recovery (hold volume down after you hit the power button, then select recovery form the menu with the volume down key and press the power button to confirm). Then, simply flash the su.zip from within recover.
**This all assumes you have a custom recovery image such as Amon RA.
I haven't come across a clear cut way to root GRI40 without the use of custom recovery.

dnlsmy said:
Good luck with that, I still can't seem to downgrade...
Click to expand...
Click to collapse
You can find stock (FRG83G) rooted and unrooted images from dsixda here: http://forum.xda-developers.com/showthread.php?t=927935
This of course assumes you have custom recovery/unlocked bootloader.
If not, you can follow the instructions here: http://forum.xda-developers.com/showpost.php?p=11618802&postcount=972

Not using a custom recovery so can't do the idea listed here. As for downgrading and then upgrading, it's probably the only solution but I think I'll wait for GINGERBREAK

thx, seems i will wait until GINGERBREAK
do i need to unlock to use custom recovery? i have stock version, dont wonna unlock it

You could follow the instructions in this (http://forum.xda-developers.com/showpost.php?p=11626567&postcount=70 ) thread if you want root, but don't want to unlock bootloader.
More detailed info avaliable here: http://forum.xda-developers.com/showthread.php?t=931865

This has fastboot commands which means the bootloader has to be unlocked...
Sent from my Nexus One using XDA App

Code:
fastboot oem unlock

Having an unlocked bootloader since minute 5, I am guessing here.
But couldn't you downgrade with passimg and then reroot the same way you did previously, install CW recovery, and then upgrade to one of the rooted GRI40 builds?

Brownbay said:
You could follow the instructions in this (http://forum.xda-developers.com/showpost.php?p=11626567&postcount=70 ) thread if you want root, but don't want to unlock bootloader.
More detailed info avaliable here: http://forum.xda-developers.com/showthread.php?t=931865
Click to expand...
Click to collapse
thx helped a lot , are there any (market) apps that i can check if iam unlocked? i am still not sure

You will see an unlocked padlock on the static x boot screen when you boot the phone...
Sent from my Nexus One using XDA App

higi22 said:
thx helped a lot , are there any (market) apps that i can check if iam unlocked? i am still not sure
Click to expand...
Click to collapse
You will have a padlock icon on your 'X' screen if you have unlocked the bootloader successfully. To check whether or not you have root access, open up a terminal from the phone and type su. If it asks for root access and you click allow, you should see a # sign. If it doesn't give you a # sign, you aren't rooted.

Brownbay said:
Are both you guys running an unlocked bootloader with custom recovery?
If so, then head over to this thread: http://forum.xda-developers.com/showthread.php?t=968396 and download the su.zip that's attached at the bottom of the first post.
Once downloaded, put it on your SD card, boot into recovery (hold volume down after you hit the power button, then select recovery form the menu with the volume down key and press the power button to confirm). Then, simply flash the su.zip from within recover.
**This all assumes you have a custom recovery image such as Amon RA.
I haven't come across a clear cut way to root GRI40 without the use of custom recovery.
Click to expand...
Click to collapse
Thanks Brownbay this su.zip worked for me..
1. Had a rooted 2.2.2 before
2. Update to 2.3.3 and my root is gone
3. Tried manual rooting steps for Froyo didn't work out
4. Downloaded this su.zip file
5. In my 2.3.3 used Superboot to flash Amon RA recovery while I was in Fastboot(shutdown and then Trackball+power). For some reason wasnt able to flash when the phone is powered on and in normal working mode.
6. Select su.zip for update
7. Reboot after finish, Installed Titanium backup again and tested working fine...
Great now I will have all the fun again

ihtkassakthi said:
5. In my 2.3.3 used Superboot to flash Amon RA recovery while I was in Fastboot(shutdown and then Trackball+power). For some reason wasnt able to flash when the phone is powered on and in normal working mode.
6. Select su.zip for update
Click to expand...
Click to collapse
Hi, this is interesting, could you please elaborate more on the above steps?

It's called "Install custom recovery, guide for unlocked bootloader", and then "flash a SU file through custom recovery".
Guides in Wiki.
People, have a look before asking!!

1. Download Superboot and extract to your system(mine c:\superboot)
2. Download Amon RA-Passion recovery image and place it in the superboot folder
3. Shutdown you phone, reboot pby pressing Trackball+Power button
4. In you computer open command prompt and gotto c:\superboot
5. Type "fastboot-youros flash recovery your-ra.img-filename"
6. It will upload and once said done disconnect you phone from computer
7. Select Bootloader and Recovery
8. Now select update zip and select the SU.zip and update

Have you guys tried this: http://forum.xda-developers.com/showthread.php?t=736271
It worked on Eclair but probably not in GB.
I flashed an old Eclair rom, rooted, installed Rom Manager, Clockwork, and back to CM7.

call me a little crazy but I rooted last night using modaco's superboot. Yes, I know there is no version for GRI40 yet, but i just used the one for FRG83D. It hung on first boot and had to issue an adb reboot command to get it to boot, but everything seems fine after that. And it rooted successfully

[ROM] [NANDROID] Nexus S 2.3.2 Build GRH78C + Bootloader + Radio

THIS HAS ONLY BEEN TESTED ON THE USA NEXUS S, I9020T. THIS WILL WIPE ALL DATA ON YOUR PHONE. NOT RESPONSIBLE FOR ANY DAMAGE CAUSED BY THIS. IF YOU ARE NEW TO THIS KIND OF THING, I HIGHLY RECOMMEND BEING IN THE COMPANY OF SOMEONE MORE EXPERIENCED BEFORE TRYING THIS
Link to file: http://www.mediafire.com/?lvt874fhzzzjqy1
I have created a Nandroid backup of the stock Android 2.3.2 ROM just in case there's anyone out there who hates the 2.3.3 update and wants an easy way to get back without installing 2.3.1 and upgrading. This ROM is 100% stock GRH78C with no root, no custom kernel, and no additional apps.
I have also included the 2.3.2 bootloader (I9020XXJK1) and radio (I9020XXJK8), plus a copy of ClockworkMod 3.0.0.5.
What you'll need:
Unlocked bootloader (see this thread)
ADB and Fastboot installed and working (see this thread)
Instructions:
Extract the contents of the ZIP file.
Move the clockworkmod folder to the root of your phone's USB storage.
Put the "images" folder somewhere on your computer.
Connect your phone to your PC via USB.
Power your phone off.
Hold down the volume up key while pressing power to boot into the bootloader.
Open a command prompt on your PC.
------ OPTIONAL. DO THIS IF YOU WANT TO USE THE ORIGINAL RADIO AND BOOTLOADER FOR THIS ROM --------
Change directory to the images folder from the zip.
Type (without quotes) "fastboot flash bootloader bootloader.img"
Type (without quotes) "fastboot flash radio radio.img"
------ END OF OPTIONAL STEPS --------
If you don't yet have clockworkmod recovery installed, type (without quotes) "fastboot flash recovery clockworkmod_3.0.0.5_crespo.img"
Select "Recovery" from the bootloader menu which will boot you into clockworkmod.
Select "backup and restore", then "backup" to make a backup of your current ROM.
Select "restore" and choose 2011-04-04.20.44.33.
Wait for it to finish.
You will now be running Android 2.3.2 stock/unrooted and (optionally) the proper bootloader and radio versions. Keep in mind that the first time you boot into this ROM, Clockworkmod recovery will be erased and replaced with the stock 3e recovery.

Followed every step and it worked perfectly. My phone is now running 2.3.2 again. Have my excellent colors again. Thanx
oldblue910 said:
this has only been tested on the usa nexus s, i9020. This will wipe all data on your phone. Not responsible for any damage caused by this. If you are new to this kind of thing, i highly recommend being in the company of someone more experienced before trying this
link to file: http://www.mediafire.com/?lvt874fhzzzjqy1
i have created a nandroid backup of the stock android 2.3.2 rom just in case there's anyone out there who hates the 2.3.3 update and wants an easy way to get back without installing 2.3.1 and upgrading. This rom is 100% stock grh78c with no root, no custom kernel, and no additional apps.
I have also included the 2.3.2 bootloader (i9020xxjk1) and radio (i9020xxjk8), plus a copy of clockworkmod 3.0.0.5.
What you'll need:
Unlocked bootloader (see this thread)
adb and fastboot installed and working (see this thread)
instructions:
Extract the contents of the zip file.
Move the clockworkmod folder to the root of your phone's usb storage.
Put the "images" folder somewhere on your computer.
Connect your phone to your pc via usb.
Power your phone off.
Hold down the volume up key while pressing power to boot into the bootloader.
Open a command prompt on your pc.
------ optional. Do this if you want to use the original radio and bootloader for this rom --------
change directory to the images folder from the zip.
Type (without quotes) "fastboot flash bootloader bootloader.img"
type (without quotes) "fastboot flash radio radio.img"
------ end of optional steps --------
if you don't yet have clockworkmod recovery installed, type (without quotes) "fastboot flash recovery clockworkmod_3.0.0.5_crespo.img"
select "recovery" from the bootloader menu which will boot you into clockworkmod.
Select "backup and restore", then "backup" to make a backup of your current rom.
Select "restore" and choose 2011-04-04.20.44.33.
Wait for it to finish.
You will now be running android 2.3.2 stock/unrooted and (optionally) the proper bootloader and radio versions. Keep in mind that the first time you boot into this rom, clockworkmod recovery will be erased and replaced with the stock 3e recovery.
Click to expand...
Click to collapse

Thanks. Since Google stopped updating and my NS is only 3 weeks old I never had a chance to make my own 2.3.2 backup. I did manually update to 2.3.3 but I am having sporadic data connection issues since I updated. So hopefully my NS will like 2.3.2 better than 2.3.3.

Just wanted to say thanks for this. It was nice to have the bootloader and radio for the 2.3.2 ROM in a nice package.
I had received the OTA update notification (2.3.2 -> 2.3.4) this morning, and after flashing the default bootloader I had a failed update (thankfully I had a fresh nandroid). So flashed the radio/bootloader again from your package and was able to restore my backup and successfully flash an OTA for the first time ever on this phone.

hrm does anyone have a 9023 equivalent? I'd really really really need the original bootloader

gotjazz said:
hrm does anyone have a 9023 equivalent? I'd really really really need the original bootloader
Click to expand...
Click to collapse
The original bootloader for I9023 is XXKA3, which you can find in this file: http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip
Extract the bootloader.img file from the ZIP. DO NOT flash this entire ZIP as this contains GRI40 with the KB1 radio. Just extract the bootloader.img.
Reboot into your bootloader.
Plug your phone into USB on your computer.
Make sure ADB and Fastboot are set up.
In your command prompt, change to the directory where you extracted the bootloader.img file.
Type "fastboot flash bootloader bootloader.img"
That should be it.
Not responsible for any damage, yadda yadda.

Ah thanks a lot - I'll give this some consideration. I just "needed" it because I flashed the full rom update to 2.3.4 for 9023 lately (and later returned to my nandroid CM7 backup) and I noticed the bootloader being flashed and now it claims to be I9020XXXKA3, which is the version you quoted anyway though. So now I'm not sure anything has really changed. Or should it be I9023XXXKA3? (it also lists my radio as I9220whatever but from the running system that is shown as 9023 and I can't for the life of me remember what the bootloader said before)
Anyway thanks a lot man - I was beginning to think I'd have to familiarize myself with Odin. Thing is I'm thinking about sending my phone in and should I do it of course I'd have to make it as close to being a virgin as possible first
oldblue910 said:
The original bootloader for I9023 is XXKA3, which you can find in this file: http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip
Extract the bootloader.img file from the ZIP. DO NOT flash this entire ZIP as this contains GRI40 with the KB1 radio. Just extract the bootloader.img.
Reboot into your bootloader.
Plug your phone into USB on your computer.
Make sure ADB and Fastboot are set up.
In your command prompt, change to the directory where you extracted the bootloader.img file.
Type "fastboot flash bootloader bootloader.img"
That should be it.
Not responsible for any damage, yadda yadda.
Click to expand...
Click to collapse

gotjazz said:
Ah thanks a lot - I'll give this some consideration. I just "needed" it because I flashed the full rom update to 2.3.4 for 9023 lately (and later returned to my nandroid CM7 backup) and I noticed the bootloader being flashed and now it claims to be I9020XXXKA3, which is the version you quoted anyway though. So now I'm not sure anything has really changed. Or should it be I9023XXXKA3? (it also lists my radio as I9220whatever but from the running system that is shown as 9023 and I can't for the life of me remember what the bootloader said before)
Anyway thanks a lot man - I was beginning to think I'd have to familiarize myself with Odin. Thing is I'm thinking about sending my phone in and should I do it of course I'd have to make it as close to being a virgin as possible first
Click to expand...
Click to collapse
Yeah no problem. 2.3.3 and 2.3.4 use the same bootloader so you're good.

yeah - I was just worried about the 9020 in the name and wondering if it shouldn't be 9023

gotjazz said:
yeah - I was just worried about the 9020 in the name and wondering if it shouldn't be 9023
Click to expand...
Click to collapse
That shouldn't matter a bit.

well i know it works - my point was i was wondering if someone could tell by that that the phone had been unlocked at some point. But oh well - I have a thread open in the Q&A Forum asking 9023 owners what their bootloaders say. Someone is bound to answer eventually
Thanks for your help again

I could be wrong, but I'm pretty sure it's a known issue that the 2.3.4 update changes i9023 to i9020 on the bootloader and radio so I'd say you have nothing to worry about.

hrm sure hope you're right

[Q] Milestone flashing recovery issue

Ok, so bit of background here.
I installed MIUI Rom using GOT OpenRecovery.
Its very cool and I really enjoy using it. Much better (IMO) than CM7.
It got to Saturday and it said there was an OTA update to install which I couldn't work out how to install. On researching it a bit around the internet it turns out that you need to have ClockworkMod Recovery flashed in order to install OTA updates.
So I tried to install ClockworkMod Recovery. I did a few different things. Firstly I downloaded the ClockworkMod Rom Manager and chose the option in there to flash. It said "Downloaded successfully" but it didn't flash. I rebooted into recovery and tried to "Apply update.zip" but it said something about it not being signed properly and wouldn't open.
So onto the next bit. I tried to flash it using one of the many manual instructions on the internet. eg:
Code:
adb shell
# flash_image recovery /sdcard/recovery.img
and
Code:
fastboot-mac flash recovery /path/to/recovery.img
The first one seems to be quite quick and just goes to the next # line. There's no error or confirmation or anything. This one broke the stock recovery. Now when I boot into recovery there's just a bootloader screen with an error on it (Err:A5,69,35,00,2F).
The second one doesn't do anything. Well it goes onto a new line and it says "sending 'recovery' (2798 KB)..." and just stays like that indefinitely until I do Ctrl+C and cancel it. Similarly doing:
Code:
fastboot-mac erase recovery
shows: "erasing 'recovery'..." and stays at that indefinitely.
So now I'm stuck. My system works - I can boot into MIUI and use the phone normally, but I don't know how to get the recovery partition working properly.
The best thing that could happen is that I get ClockworkMod Recovery installed so that I can flash MIUI updates, but failing that I would at least like to get the stock recovery back so I can continue to use GOT OpenRecovery.
What can I do to sort this?
Thanks for any help you can give me.

tclayson said:
Ok, so bit of background here.
I installed MIUI Rom using GOT OpenRecovery.
Its very cool and I really enjoy using it. Much better (IMO) than CM7.
It got to Saturday and it said there was an OTA update to install which I couldn't work out how to install. On researching it a bit around the internet it turns out that you need to have ClockworkMod Recovery flashed in order to install OTA updates.
So I tried to install ClockworkMod Recovery. I did a few different things. Firstly I downloaded the ClockworkMod Rom Manager and chose the option in there to flash. It said "Downloaded successfully" but it didn't flash. I rebooted into recovery and tried to "Apply update.zip" but it said something about it not being signed properly and wouldn't open.
So onto the next bit. I tried to flash it using one of the many manual instructions on the internet. eg:
Code:
adb shell
# flash_image recovery /sdcard/recovery.img
and
Code:
fastboot-mac flash recovery /path/to/recovery.img
The first one seems to be quite quick and just goes to the next # line. There's no error or confirmation or anything. This one broke the stock recovery. Now when I boot into recovery there's just a bootloader screen with an error on it (Err:A5,69,35,00,2F).
The second one doesn't do anything. Well it goes onto a new line and it says "sending 'recovery' (2798 KB)..." and just stays like that indefinitely until I do Ctrl+C and cancel it. Similarly doing:
Code:
fastboot-mac erase recovery
shows: "erasing 'recovery'..." and stays at that indefinitely.
So now I'm stuck. My system works - I can boot into MIUI and use the phone normally, but I don't know how to get the recovery partition working properly.
The best thing that could happen is that I get ClockworkMod Recovery installed so that I can flash MIUI updates, but failing that I would at least like to get the stock recovery back so I can continue to use GOT OpenRecovery.
What can I do to sort this?
Thanks for any help you can give me.
Click to expand...
Click to collapse
GOT recovery? You have a Milestone then? You are on the wrong path then. Clockwork Recovery Mod doesn't work on the Milestone, nor does ROM Manager.
You need to reflash the stock sbf for your country, then flash the rootable sbf, place OpenRecovery on your SD Card, and root the phone, flash a custom ROM and reboot. Look at the tutorials in the Milestone development forum and ask here if you have any other questions.

I do have a milestone - sorry, I forgot it was the Droid AND Milestone forum.
Motorola milestone is included in the list of recovery images on the clockworkmod website (clockworkmod[dot]com/recovery_images.html). Plus when installing the ROM Manager and clicking "flash recovery" it says "Confirm phone" with "Motorola Milestone" in the options.
I'm pretty sure as well from reading around on the internet and looking at different forums and such that Clockworkmod does work on the Milestone... maybe I'm completely wrong.
Thanks

tclayson said:
I do have a milestone - sorry, I forgot it was the Droid AND Milestone forum.
Motorola milestone is included in the list of recovery images on the clockworkmod website (clockworkmod[dot]com/recovery_images.html). Plus when installing the ROM Manager and clicking "flash recovery" it says "Confirm phone" with "Motorola Milestone" in the options.
I'm pretty sure as well from reading around on the internet and looking at different forums and such that Clockworkmod does work on the Milestone... maybe I'm completely wrong.
Thanks
Click to expand...
Click to collapse
It doesn't work, even though it shows it as supported. Because the bootloader is not unlocked on the Milestone, it will cause a soft brick. You will need to follow my instructions to get your Milestone running on MIUI again. The OTA update for MIUI works for devices with CWM installed, so it doesn't really work with Milestone. You'll need to manually update MIUI when DannyDroid posts the updates.

Ah gutted, ok thank you for that. I will follow your instructions. Thanks for clearing it up for me.

Just out of interest - a quick search on google shows that it IS possible to update MIUI OTA for the Milestone... Any ideas how that works? Is there a different recovery or something?

tclayson said:
Just out of interest - a quick search on google shows that it IS possible to update MIUI OTA for the Milestone... Any ideas how that works? Is there a different recovery or something?
Click to expand...
Click to collapse
People say that ROM Manager MIGHT work on Milestone. I don't think so and I wouldn't risk it just for OTA updates, seeing as the miuiAndroid build is very basic compared to the one Danny releases. Better to just wait for his releases, a lot more worthwhile!

Ok, well thank you very much! Restored to stock and gonna keep on top of danny's releases. Thanks skadude.