Database Develop

Restore Nexus One for Dummies?

I bought my phone used and I used the universal androot app to root it without locking the bootloader. I want to take it back to just the way it was when it came out of the box. Are there easy to follow step by step directions anywhere? I've searched but everything says it assumes you know how to use adb and fastboot. I don't. Do directions exist for dummies? It sure was a piece of cake to restore my old iPhone.

Yeah, I had the same problem a few weeks ago. My suggestion is look at some tutorials for installing custom ROMs and then reverse engineer those once you've learned how to use adb and fastboot.

You mean something like this -->
http://androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/

cymru said:
You mean something like this -->
http://androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
Click to expand...
Click to collapse
Kind of like that, but this part confused me.
"Once you have this installed, add a folder path for the ADB utility to your System Environment Variables “path” variable."

Ok, when I get to step 7, the command prompt says "FAILED (remote: not allowed)"
What's up with that? HELLLLLLP!

I did a manual erase user data, but now when I go to Type 'fastboot flash userdata userdata.img'
the command prompt tells me FAILED (remote: signature verify fail)
Help?

Okay, sounds like you're panicking.
There's kinda like a fix everything button, and that's a passimg.
Grab it here: (remove the spaces, I'm not allowed to post links)
w w w . megaupload . com/?d=7JQU3MV0
All you gotta do is put that on the root of your SD card. Boot into bootloader mode (hold down trackball when powering) and select recovery. That's all. It'll detect passimg, and fix everything.
The caveat here, is that you'll be on EPE76 - which was super duper annoying to actually upgrade from (but I eventually found a FRF91 rom that worked - I'll see if I can find it and post it for you).
But yeah. Download that. Fix everything. Enjoy

From EPE76 can't you just do an OTA update to upgrade to Froyo? And what exactly does this passimg do and how does it work? I got adb and fastboot working and everything, I just get errors when I try to flash. Do you have to have an unlocked bootloader to do this stuff? I just used the universal androot app to gain root, so the bootloader wasn't actually unlocked.

No. the passimg will just automatically flash radio, recovery, etc. so you don't have to. If you've got it working manually now, no need to use it.

The passimg does pretty much what you were asking about. The Nexus One has the code name "Passion", so "pass/img" is the original factory shipping image for the Nexus One. The OTA should then** come to your phone, maybe in a few hours, but maybe not for a while.

And if I do the passimg it shouldn't screw up the phone since I'm already running froyo and this will kick me back to 2.1?

Read - Nexus One Wiki, "Unroot / Restore your Nexus", PASSIMG.ZIP method.
Written especially to avoid threads like this one.

Well it worked perfectly and now I'm running 2.1 EPE76. Is there a way to force it to update to Froyo?

you should be able to open up your dialer and type
*#*#CHECKIN#*#*
or
*#*#2432546#*#*

scgolfer7 said:
you should be able to open up your dialer and type
*#*#CHECKIN#*#*
or
*#*#2432546#*#*
Click to expand...
Click to collapse
That's a negative. It just says checkin result success, but doesn't download any update. When I go to about phone and system updae it says my system is up to date.
If I was reading correctly I should upgrade from EPE76 to FRF85B and then I should get the FRF91 OTA? Can anyone confirm this?

I got everything working and I'm back to completely stock Froyo FRF91 and I just wanted to thank everyone who contributed to this thread for guiding my annoying newbie ass through the process and teaching me a wealth of knowledge about the Android OS along the way. Thanks again!

For future reference, if you want to restore your phone while having no issues accessing it, just get Rom Manager. Use it to download and install a stock unrooted Froyo rom (just make sure to select wipe data and do not select the rooting options).
Very easy to restore. The passimg method comes in very handy if you cannot even boot into the OS.

[Solution] How to root for latest OTA (AMOLED <non SLCD> SCREENS ONLY)

The only reason I had to do this was because I was rooted with stock kernal(prior to OTA), it downloaded the update and tried to apply. It didnt update properly.
Do a backup of your data using various programs on the market( I use My Backup Pro) and do a Nandroid backup always before trying to update anything(my advice)
****IMPORTANT*** Please make sure you follow steps 1-4 and have S-Off before you continue to next section ****IMPORTANT***
Before Applying OTA or RUU:
1. Root using the Unrevoked tool http://downloads.unrevoked.com/recovery/3.21/reflash_package.exe
2. Make sure you have S-Off using Unrevoked Forever (flash in Clockwork Mod) :if you need the file http://downloads.unrevoked.com/forever/current/unrevoked-forever.zip
3. Check to see if you have S-Off after press Volume Down + Power
4. Once you have S-Off you can continue
Applying RUU:
Apply this after having root prior to OTA------>RUU(stock): http://shipped-roms.com/shipped/Inc...4k_NV_1.50_PRL58006_release_143351_signed.exe
1. Run the RUU and let it reflash your phone to the new OTA
2. Phone will reboot with settings set to factory
3. You should see the new bloatware installed..you cant miss it!
Rooting after having S-Off and applying RUU:
1a. With phone on and make sure you have Debugging enabled (Settings>Applications>Development> check USB debugging)
1b. Use Unrevoked (not Unrevoked Forever) http://downloads.unrevoked.com/recovery/3.21/reflash_package.exe
2. Wait for it to say waiting for root in the Unrevoked flash program(Unrevoked tool will not complete and say:Waiting for root(this is normal at this point) and phone is restarted, then exit Unrevoked.
3. Place clockwork mod on sd card as PB31IMG.zip(it already comes in this filename) and then power down the phone http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
4. Go into recovery(volume down + power button) and let it detect pb31img and let it install(have to manually click yes at the prompts)
5. Then use clockwork mod to install superuser apk manually http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
6. Reboot and you will have root with superuser access
***short term fix until devs can streamline it for the OTA update or if you use the RUU(stock kernal and all the bloatware which can be removed easily)
Then i used Root Explorer(on the Android Market) or you can use ADB shell to delete if you prefer to delete the unwanted bloatware.

Will this work for an slcd incredible?
Also I've tried to root but I can't install the slcd fix file in the bootloader. It shows that it picks up the file but it won't let me install it.

Not Working!
I'm continuing to hack at this myself....I performed the return to stock, updated to the latest OTA, and now using steps 1 to 3 of this method fail, when the phone reboots it checks the zip file and just returns to the menu without install anything. I get the feeling the phone having S-ON right now is an issue.

maxnic said:
I'm continuing to hack at this myself....I performed the return to stock, updated to the latest OTA, and now using steps 1 to 3 of this method fail, when the phone reboots it checks the zip file and just returns to the menu without install anything. I get the feeling the phone having S-ON right now is an issue.
Click to expand...
Click to collapse
I'm guessing you're correct. I'm attempting this on a brand new Incredible and no dice. The PB31IMG.ZIP just gets glossed over.

It fails for me too. If we could just figure out how to get s-off............
Sent from my ADR6300 using XDA App

I should of made it clear that I had S-OFF previous to the procedure above.
Just wondering does the Unrevoked root method do that or no? Maybe someone can chime in with a solution to that.
Just wondering also have you guys done the RUU first to get to stock with the latest OTA?

magneticzero said:
I should of made it clear that I had S-OFF previous to the procedure above.
Just wondering does the Unrevoked root method do that or no? Maybe someone can chime in with a solution to that.
Just wondering also have you guys done the RUU first to get to stock with the latest OTA?
Click to expand...
Click to collapse
You can't use the PB31IMG.ZIP without S-OFF, end of story. Unrevoked can't turn S-OFF unless a custom recovery can be flashed, then flash the unrevoked forever zip and from a stock setting with the new OTA, that cannot be achieved. I activated this new phone and was forced into the new update without question so I'm stuck waiting on Unrevoked to update.

cosine83 said:
You can't use the PB31IMG.ZIP without S-OFF, end of story. Unrevoked can't turn S-OFF unless a custom recovery can be flashed, then flash the unrevoked forever zip and from a stock setting with the new OTA, that cannot be achieved. I activated this new phone and was forced into the new update without question so I'm stuck waiting on Unrevoked to update.
Click to expand...
Click to collapse
im going to try something, give me a sec

So I see that many of you tired it. I have the s-off file that I made into a zip file but since I have an slcd incredible I won't be able to go into recovery and load it.
I guess will have to wait for the unrevoked team to update.

I'm an IT admin at my company and I'm responsible for setting up the phones for every one and we're using Incredibles. I've had several rooted and unrooted users perform the update (against my warning). Thankfully, I got to investigate one of the rooted phones that performed the update. It seems that root was not taken away as SetCPU, ADB root, and other root applications still functioned properly. The phones that are rooted are using Calkulin's ROM and King's #5 BFS. The phones "applied" the update but it seems nothing was actually updated? The software version hasn't changed, the kernel hasn't changed but the baseband and PRI is the same as the new update.

cosine83 said:
I'm an IT admin at my company and I'm responsible for setting up the phones for every one and we're using Incredibles. I've had several rooted and unrooted users perform the update (against my warning). Thankfully, I got to investigate one of the rooted phones that performed the update. It seems that root was not taken away as SetCPU, ADB root, and other root applications still functioned properly. The phones that are rooted are using Calkulin's ROM and King's #5 BFS. The phones "applied" the update but it seems nothing was actually updated? The software version hasn't changed, the kernel hasn't changed but the baseband and PRI is the same as the new update.
Click to expand...
Click to collapse
That great news, but I can't even get my Inc to root.

alphatectz said:
So I see that many of you tired it. I have the s-off file that I made into a zip file but since I have an slcd incredible I won't be able to go into recovery and load it.
I guess will have to wait for the unrevoked team to update.
Click to expand...
Click to collapse
You have to use the Amon Ra port to get into a custom recovery with the SLCD DIncs. All of the new ones I've been getting here are SLCD. I've attached the recovery.img for it. Before plugging in your phone with debugging on and starting unrevoked, you can choose a different recovery than clockwork.

cosine83 said:
You have to use the Amon Ra port to get into a custom recovery with the SLCD DIncs. All of the new ones I've been getting here are SLCD. I've attached the recovery.img for it. Before plugging in your phone with debugging on and starting unrevoked, you can choose a different recovery than clockwork.
Click to expand...
Click to collapse
Thx, can I manually install it on the inc itself and try to push I threw them bootloader?
Or do I have to adb it?
Also if I can upload it manually on the inc. Should I keep the same file name or change it to PB31IMG.zip?

alphatectz said:
Thx, can I manually install it on the inc itself and try to push I threw them bootloader?
Or do I have to adb it?
Click to expand...
Click to collapse
I'd try both and see whichever works. You won't be able to use the PB31IMG.ZIP with S-ON, though. Guess we're stuck waiting on Unrevoked to release for this new update since I cannot root it at all.

cosine83 said:
I'd try both and see whichever works. You won't be able to use the PB31IMG.ZIP with S-ON, though. Guess we're stuck waiting on Unrevoked to release for this new update since I cannot root it at all.
Click to expand...
Click to collapse
I think I might have a fix. Give me a few mins to try if it works the I'll try to upload it on the third thread from my Inc. If I can't upload it I'll have to wait until I get home tonight.
Conclusion :
I've tired to manually downgrade by ruu and it just failed big time.
Hey cosine83 I tired to push that file it also didn't work out for me.

We need a fix for this asap

I see a lot of talk in this thread, by what maybe SLCD users, that there are problems?
So have AMOLED w/S-OFF other users confirmed this works?
I'm curious because I'm apparently running a Deodexed "stock" rom with Root and S-off via the Unrevoked tools, and the OTA pushed to me failed. I'd like to just get back to stock but rooted (I don't mind having to wipe and reload all my apps.)

KidJoe said:
I see a lot of talk in this thread, by what maybe SLCD users, that there are problems?
So have AMOLED w/S-OFF other users confirmed this works?
I'm curious because I'm apparently running a Deodexed "stock" rom with Root and S-off via the Unrevoked tools, and the OTA pushed to me failed. I'd like to just get back to stock but rooted (I don't mind having to wipe and reload all my apps.)
Click to expand...
Click to collapse
Naw..I am not slcd just got an amoled refurb that came fully
Updated

KidJoe said:
I see a lot of talk in this thread, by what maybe SLCD users, that there are problems?
So have AMOLED w/S-OFF other users confirmed this works?
I'm curious because I'm apparently running a Deodexed "stock" rom with Root and S-off via the Unrevoked tools, and the OTA pushed to me failed. I'd like to just get back to stock but rooted (I don't mind having to wipe and reload all my apps.)
Click to expand...
Click to collapse
Well the major problem is that we all updated to the lastest ota that Verizon has pushed out.
This means that us using. SLCD incredible's are stuck without a root method. The unrevoked team needs to push out an update.
As for amoled users they're fine since the recovery.img is working. SLCD recovery.img is messed up. In order to fix the recovery.img we need to have s-off in order to push the fix on the bootloader.
Since you want to update an return to rooted stock items advise you to find a rooted version of the lastest ota. It should be somewhere in the xda forms.

csseale said:
Naw..I am not slcd just got an ambled refurb that's came fully updated
Click to expand...
Click to collapse
Are you 100% positive that you have AMOLED?

[Q] Help needed Please to revert to fully stock N1

Hi Guys,
I am a newbie to all things root etc.,but wanting to start I have purchased a 2nd hand Nexus One. However it seems to have a different Build number than most of you. Here are the specs: Android version
2.2.1
Baseband version
32.50.00.32U_5.12.00.08
Kernel version
2.6.32.9-Connect-UTB-20101020-27240-gbca5320
Build number
UTB-ROM 1.1
Could some one please guide me to revert my phone to a complete up to date Stock phone?
Any help much appreciated!

Anyone?
I Haven't just posted without spending hours on reposts and wiki, even asked original member who devised UTB-1.1 but no replies yet.I have tried instructions on wiki to revert to FRG33,but I get an error! Have tried other members advice posts, Rusty being one,still get an error. On the Recovery mode I notice I have Clockwork there,is this the problem?
Stuck on UTB-1.1 just want original stock phone to receive OTA updates etc.,

Which hboot version do you have?
Sent from my Nexus One using XDA App

Hi it is 0.35.0017

Ahhhh, well that's why the passimg method won't work.
I don't know of anyway, other than rooting, or unlocking the bootloader. You may already be rooted, though...
Sent from my Nexus One using XDA App

Hi, Thanks for taking the time to reply, so, I don't know either if it is rooted, if I root will I be able to use passimg? don't really want to unlock the bootloader unless there is no other way.

To see if you're rooted, download a flashlight app that requires root, and see if it works...
You cannot use the passimg method, sorry.
Unlocking bootloader is the easiest, but I can respect you not wanting to do that.
Let me know if you're rooted...
Sent from my Nexus One using XDA App

Well, since the FRG33 PASSIMG has HBOOT 0.35.0017 in it, how come you cannot reflash it? I also have that HBOOT (at least I think so, I used the FRG33 PASSIMG then OTA'd to FRG83D) and I can reflash that anytime I want.
I tried yesterday night... I didn't actually reflash but I forgot I had the file there, launched HBOOT and it checked and offered me to flash it. So by using a FRG33 PASSIMG I guess it should work.

You can try it, but like the OP said, you get an error...
Sent from my Nexus One using XDA App

G0belet you were right! danger-rat I did get error x 3 , but whilst searching to see if my n1 is rooted, I saw G0belet's post and went back to my passimg file. I am an idiot! I copied the instructions for FRG33 from wiki exactly. Where I went wrong was renaming the passimg file passimg.zip, it is already a zip file,so my phone sd card read passimg.zip.zip! Argggh! after all those hours and your help I am now on Build FRG33.
Thank you G0belet and danger-rat for spending time to help.Guess you can tell I am new to this. Now all I need to do is update to FRG83 somehow?
Many Thanks again guys...
Update: After I finished typing all this, my nexus updated ota to FRG83D!
so all fixed I think..

Instructions in the wiki to upgrade from FRG33 to FRG83...
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Sent from my Nexus One using XDA App

You're welcome
Just connect your N1 to your Wi-Fi or cellular network. You will get a prompt to update very soon. Check Settings > About this phone > Updates (or something like this) to see if it's loading. If it's not, you can attempt tapping Phone, and typing *#*#2432546#*#* to manually trigger the update verification. That's the easy and official way to update. It will directly load stock FRG83D on your phone.

Thanks it's on FRG83D now after OTA update, Brilliant!

[FIX] for Status 7 Error in Nexus S 2.3.1 Upgrade

Those of us who flashed rootboot.img to install a rooted/insecure boot image were unable to update via the 2.3.1 OTA (Status 7 Error). A few different solutions have been posted. Here's one which worked for me, courtesy of momohammed20 and Luxferro:
Step 1: Restore the "2010-12-22.21.06.07" Nandroid backup which momohammed20 shared in this thread. That wipes your phone completely and gives you stock 2.3.1 without root.
Step 2: Follow the steps provided by Luxferro in this post. That gets you back root along with ClockworkMod Recovery.
Worked perfectly for me. Again, the solution is already out there in a few other threads, but I thought this deserved its own thread since a lot of folks have been stuck with the Status 7 error when trying to update.
Thanks again to momohammed20 and Luxferro!

Umm if we have 2.3 we can't nandroid a 2.3.1 backup. Ull get an error every time.
Sent from my Nexus S using XDA App

I followed these steps, and they worked nicely with no errors whatsoever. Others have done the same.

U were runninr2.3 rooted and then nandroid the 2.3.1 and u didn't get a MD5 error? Hard to beloved BC I've tried 5 times. Can anyone else try this out n let us know? ?
Sent from my Nexus S using XDA App

EDIT: just got it to work.. I re-downloaded it and it loaded. Seems the nandroid I dl from that thread the first time got renamed n it had a "(" in it, and recovery couldn't read the file...
Thanks alot tho, u were right!!
Sent from my Nexus One using XDA App

So will this allow the future flashing of OTAs without issue?

i also want to know if this will allow for future updates. i dont want to be reflashing my phone for every minor update.

Yes it will. The bootloader remains unlocked. But it restores everything to stock 2.3.1, and will have stock recovery, so next time there's a OTA it won't get an error when Its flashing BC u will be using the stock recovery n not CWR
Oh btw there's no root, in case u didn't understand what Stock 2.3.1 meant.
Sent from my Nexus S using XDA App

petep86 said:
Yes it will. The bootloader remains unlocked. But it restores everything to stock 2.3.1, and will have stock recovery, so next time there's a OTA it won't get an error when Its flashing BC u will be using the stock recovery n not CWR
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
From what I understand, the problem lies in the boot.img and not ClockworkMod.

TheBiles said:
From what I understand, the problem lies in the boot.img and not ClockworkMod.
Click to expand...
Click to collapse
What problem are u referring to?
That u can't ota the update??
Sent from my Nexus S using XDA App

petep86 said:
What problem are u referring to?
That u can't ota the update??
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
"Status 7" is the result of a rooted boot.img. It has nothing to do with ClockworkMod Recovery.

TheBiles said:
So will this allow the future flashing of OTAs without issue?
Click to expand...
Click to collapse
I don't know about that. For this particular OTA, it seems that the problem was the root boot. The method in the OP addresses that. However, I wouldn't assume that the next OTA will be compatible with a rooted device. My understanding (and I am no authority) is that the only way to know you're going to be getting OTAs is to revert to full stock. My intent was to have root and recovery in 2.3.1, not to get back to stock and stay there.

Wish this was posted this morning before i gave up
between some people getting it to work and other not working. People posting methods with stock boot.img but come to find out it wont work with rootboot....ect
Then realizing some people are on one root method while other used another...too confusing and i gave up after countless tries and gave and flashed modaco GRH78 r2 and glad i did because its pretty good..
IMO guys if this is going to require to you wipe your data save your self from headaches and just flash modaco GRH78 r2 with supercurio's EXT4 tweak it also rooted has new market and other fun stuff

demo, that's a good point. I'm using the r2 MoDaCo ROM now - it seems very good!

Amin Sabet said:
I don't know about that. For this particular OTA, it seems that the problem was the root boot. The method in the OP addresses that. However, I wouldn't assume that the next OTA will be compatible with a rooted device. My understanding (and I am no authority) is that the only way to know you're going to be getting OTAs is to revert to full stock. My intent was to have root and recovery in 2.3.1, not to get back to stock and stay there.
Click to expand...
Click to collapse
Nope, that is false. I had initially used superboot to root my phone when I first got it (w/ the pre-rooted modified boot.img). And I still got the prompt for the update. It will just give you a MD5 mismatch error when you accept the prompt and try to update.

deleted (accidental double post)

Luxferro, I think you misunderstood what I wrote. I too was rooted and got the prompt for this particular OTA, and some folks who were rooted (without root boot) were able to apply the OTA without an error. What I was trying to say was that the only way to be sure that they can receive and apply all future OTA updates would be to revert to stock (or have a means to revert to stock).

the status 7 error is a result of the patch process not finding a proper checksum for the things its patching if you have deleted system/framework apk's/odex's de-odexd the system/framework themed the system/framework changed the kernel this will cause status 7 error and will give you a hint on where the issue lies i.e. it will say somthing about calculator not match if you deleted it and error code 7

Help! no reovery

Hi,
I tried to upgrade my Dream to a version of And 2.2, after flashing my phone was boot looping, so re reflashed to rc29 using xda's return to stock guide. It boots fine now in normal mode, but now I can't get into recovery and I cant get anything to flash, not even rc29 again. If I try flashing using the phone I get Model ID incorrect, with fastboot I get remote: not allow. Very few threads mention HBOOT 1.33.0014, maybe its the problem? Any help would be appreciated
DREAM PVT 32B
HBOOT 1.33.0014
CPLD-4
RADIO-3.22.26.17
Forgot to mention, its Rogers but I don't have a sim card

Use the telnet method to flash a new recovery, in the future if you ever get stuck and have to flash the orange.nbh not the dreaimg.nbh
Sent from my HTC Vision using xda premium

re
demkantor said:
Use the telnet method to flash a new recovery, in the future if you ever get stuck and have to flash the orange.nbh not the dreaimg.nbh
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I tried reflashing with orange also, same message, though I didn't try with telnet because I couldn't get it connected to localhost.
typed telnetd at home screen
started telnet when I click connect
I get either server refused
or null

Did you hit enter twice
Sent from my HTC Vision using xda premium

demkantor said:
Did you hit enter twice
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
yeah 2 times, then type telnetd (ignored the contact search), press enter.
open telnet, click connect. Does the port make a difference? I left it as it was, its set to 23

you should make a gold card (just goole it)
or well can you update via ota, under settings look for updates, if you can get to 1.5 then you can use androot or maybe see if THIS GUIDE helps.
ive only rooted one rogers branded g1, and you dont do the dreaimg.nbh method rather
LIKE SO but at this point you need to move on, try some of the above stuff

re
demkantor said:
you should make a gold card (just goole it)
or well can you update via ota, under settings look for updates, if you can get to 1.5 then you can use androot or maybe see if THIS GUIDE helps.
ive only rooted one rogers branded g1, and you dont do the dreaimg.nbh method rather
LIKE SO but at this point you need to move on, try some of the above stuff
Click to expand...
Click to collapse
ok went searching for update in settings and noticed firmware is at 1.5 , I didn't think it could update automatically without a sim? so I'm guessing DREAIMG.nbh didn't take? Just messed my recovery? I installed Androot and it says I'm "already rooted, root again?" The first guide you pointed to THIS GUIDE says for "Tmobile G1 only", should I go ahead anyway? The last one LIKE SO , I would like to try the rogers_1.89.631.1.nbh but it seems to have disappeared from the net. I'll look into the gold card idea this weekend. Thx for your input :good:

re
demkantor said:
you should make a gold card (just goole it)
or well can you update via ota, under settings look for updates, if you can get to 1.5 then you can use androot or maybe see if THIS GUIDE helps.
ive only rooted one rogers branded g1, and you dont do the dreaimg.nbh method rather
LIKE SO but at this point you need to move on, try some of the above stuff
Click to expand...
Click to collapse
Well made a gold card, but got a message "main version is older" when I tried to update the image, I think the problem is finding the right image file. I thought Gold cards got around that? I guess I'll just use 1.5, doesn't have everything I want, but its working at least. thx for the help just the same

The gold card didn't take, may need to use a different sd.
But did you say you have root? Do you have a custom recovery? Maybe you can go about this in a different way, can you post everything on your bootloader screen?
Sent from my HTC Vision using xda premium

re:
demkantor said:
The gold card didn't take, may need to use a different sd.
But did you say you have root? Do you have a custom recovery? Maybe you can go about this in a different way, can you post everything on your bootloader screen?
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
ok heres what I have: see attachment
no recovery btw
cant seem to get telnet to work
fastboot works but wont successfully flash
adb works but wont succesfully flash
bootloader gives update fail
Androot says I'm rooted
Adb gives me # when I enter superuser which means I should be rooted
I also get superuser request popup on my phone

demkantor said:
The gold card didn't take, may need to use a different sd.
But did you say you have root? Do you have a custom recovery? Maybe you can go about this in a different way, can you post everything on your bootloader screen?
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I read your post to m3talmouth:
Find amonra recovery in xda, latest is 1.7 something
Put on root of sd card and name it recovery.img
Open a terminal and type
su
If you see a # procees
flash_image recovery /sdcard/recovery.img
If you have an error it could be you need to add the flash image bianary or you have a bad download or named it wrong,
I figured It might work for me, now I have AmonRA recovery 1.7 :good:
So now following the guide you posted earlier http://forum.xda-developers.com/wiki/HTC_Dream/Rooting_Branded_EBI1s, I should install the engineering SPL, then the EB1 port file, then flash cm 6.1.zip?

Hey good! Well if you have a custom recovery you are most of the way there, now remember you have a rogers dream and need tgo flash the proper radio and spl, make sure they are listed for your phone, check md5sums, flash radio first then spl then id recomend cm5 (faster) flash rom and gapps
Do this right, just the other day someone flashed either spl first or a curropt image and got a brick. Only warning so you don't but as long as you do what I said above you'll be safe
Sent from my HTC Vision using xda premium

demkantor said:
Hey good! Well if you have a custom recovery you are most of the way there, now remember you have a rogers dream and need tgo flash the proper radio and spl, make sure they are listed for your phone, check md5sums, flash radio first then spl then id recomend cm5 (faster) flash rom and gapps
Do this right, just the other day someone flashed either spl first or a curropt image and got a brick. Only warning so you don't but as long as you do what I said above you'll be safe
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Well...I i did a nandroid backup, tried i now have the eng SPL installed, tried the CM 6.1 as it was easier to find for my phone + the port file, but it stuck at rogers boot screen. I've seen some posts for 2708 kernel but it never mentions this in any of the install guides. I have found CM 5 roms but only with the 2708 kernel and no mention of rogers, so I'm staying clear of those for the moment. Will search some more for CM 5, its not Android 2.2 though is it?

Cm5 is 2.1 but smoother than cm6 on these phones. You can flash the one in cm wiki just flash the right kernel on top of it. If you want to do the 2708+ update (I say a good idea) then just follow ezterrys instruction in his thread. Download radio and SPL, check md5sums, and then flash via fastboot. Now they can also be flashed in recovery but I don't recommend it. After that you can flash any of the newer ROMs and it won't mater that your phone was once rogers. But older ROMs (mostly eclair and older) will need a different kernel flashed on top of them
Sent from my Nexus 7 using xda premium

re:
demkantor said:
Cm5 is 2.1 but smoother than cm6 on these phones. You can flash the one in cm wiki just flash the right kernel on top of it. If you want to do the 2708+ update (I say a good idea) then just follow ezterrys instruction in his thread. Download radio and SPL, check md5sums, and then flash via fastboot. Now they can also be flashed in recovery but I don't recommend it. After that you can flash any of the newer ROMs and it won't mater that your phone was once rogers. But older ROMs (mostly eclair and older) will need a different kernel flashed on top of them
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Success!!!!! I have CM 5.08 + 2708 installed and working, thx for everything, will try this mod for a while to see if it covers all I need, if so I'm good to go. :laugh: :good:

Awesome! You may need to move to froyo if apps you need aren't avalible on 2.1, there are many good aosp and cm variants just straight cm6 is kinda poor on these phones, try a few out, make nandroids so you can change back easy, there are about a dozen 2.3 and 2.2 roms that I feel run great on the dream and I personally keep a back up of each for a quick change
Sent from my HTC Vision using xda premium

Do not forget that your phone is no longer EBI1.
You will no longer need to flash EBI1 ports.
On a side note, looks like you somehow got the 1.33.0014 update.
1.33.0014 is a bootloader released by HTC somewhere last year for HTC Dream. They claimed it was unlockable, and you could flash with it. I did the unlock process, and I can promise you that HTC duped us. It's not unlockable. The unlock does absolutely nothing other than change the text at the top. I even had someone reverse some of the code, and they claimed the code for doing fastboot flash doesn't seem to be there.

yeah the .0014 official unlocked bootloader is a crock, when it first came out i was about to test it and someone else here tried first, turned into a nightmare for him so i tell all to stay away! some phones it actually isnt too bad if better ways like hacked bootloaders or radio s-off has been found for it, but its a pain and you usually need to flash a rom in recovery, extract the kernel from the .zip and then flash the kernel through fastboot.
so yeah any phone that you dont need this option, stay far away from it!