[Q] Help needed Please to revert to fully stock N1 - Nexus One Q&A, Help & Troubleshooting

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!

Related

I am stuck on epe76

what do i do here .I have a nexus one unlocked from google and i had the froyo 2.2 .in an attempt to root it i had to downgrade it to epe76 and then frf85b.But i am stuck on epe76.what is wrong,what am i doing wrong?i also copied passimg.zip to my sd card .it says no imge!!!!
You said you were unlocked? Then just flash whatever rom you want from the development section.
Long time reader, first time poster ;D
Same problem for me.
screwed up rooting my FRF91, so downgraded to EPE76, which a kind bloke here was good enough to put together as an entire package.
I think OP's problem is that most flashable roms seem to already require a certain radio, or they're just updates to an existing froyo built.
Seems a little difficult to find a stand alone rom you can stick straight onto your device, even with an custom recovery.
I'd love to be proved wrong!
I think another issue is that there's a lot of jargon in most custom rom posts, or just a general assumption that new users will know what they're doing. Of course, given the right research, most people can figure it out. But I feel your pain, OP.
I mean it is unlocked from Google. Does. That mean I can flash any Rom *? Do I need to root it? I got it to frf85 it asked me if I wanted the ota and I did just that.. my reason to do so was just wanting to make sure I get the necessary information before another attempt.
Sent from my Nexus One using XDA App
mamboking said:
I mean it is unlocked from Google. Does. That mean I can flash any Rom *? Do I need to root it? I got it to frf85 it asked me if I wanted the ota and I did just that.. my reason to do so was just wanting to make sure I get the necessary information before another attempt.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
you're confusing things here. see the very nice thread about unlocking/rooting/flashing in the wiki. it's nice.
THE WIKIS BEEN DOWN FOR WEEKS
Sent from my Nexus One using XDA App
mamboking said:
what do i do here .I have a nexus one unlocked from google and i had the froyo 2.2 .in an attempt to root it i had to downgrade it to epe76 and then frf85b.But i am stuck on epe76.what is wrong,what am i doing wrong?i also copied passimg.zip to my sd card .it says no imge!!!!
Click to expand...
Click to collapse
I have exactly the same issue. And cant seem to upgrade either.
Tried with amon_ra but it says the frf85b file is not signed.
And trying with cyn* everything seems to go fine.
I reboot, and it keeps rebooting into amon....
And when i finally set the device to power of, then turn it back on. Im still stuck in epe76.....
Any ideas anyone?

[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

[Q] How to return to stock?

Rooted and running CM 6.1.0, have backed up 1.21 firmware, what is the easiest way to unroot and return to stock? (remove CWM also). Need to send the phone in for button repair. If I apply OTA update on the 1.21 firmware (updating to 2.2) will it wipe everything clean?
Thanks in advance
DrBarrell said:
Rooted and running CM 6.1.0, have backed up 1.21 firmware, what is the easiest way to unroot and return to stock? (remove CWM also). Need to send the phone in for button repair. If I apply OTA update on the 1.21 firmware (updating to 2.2) will it wipe everything clean?
Thanks in advance
Click to expand...
Click to collapse
uhh im not too sure anymore but i think the best way to do it would be to apply an older stock rooted rom and then plug your phone into a comp with htc sync, and then do the update thing thats it got on there.. thats the way i was told a while back but im not sure if theres an easier/better way to do it. probably should wait till someone else comments before you go do anything but yeah youre meant to do something like that ^ i believe..
From my own experience, the technicians doesn't know if its stock, cm or what. They fix the problem and that's it.
I've sent my device twice with cm on it and there was no problem
Sent from my Legend
Thanks for the replies although I would be happy to send it in with CM and whatnot, as it is not mine I do not even want to take the risk. Can anyone confirm that installing the latest vodafone firmware will restore phone to stock?
basically run a htc update on it (if you haven't S-OFFed then 2.1 is fine)
Search isn't working now so I can't link you, but either way find an offical RUU and it will do everything for you. Remember if you do update it to froyo (official) it is a difference process to root again (but still possible)
Or else.. search the forum.. I made a thread called "easiest way to unroot".. or something like that.. Always use the SEARCH feature before asking questions..
Sent from my Legend using XDA App
Or ask anyway, and feel the loving response from the XDA forums
Ol' whitetigerdk's thread on unrooting is a good one though, check it out buddy!
TheGrammarFreak said:
Or ask anyway, and feel the loving response from the XDA forums
Ol' whitetigerdk's thread on unrooting is a good one though, check it out buddy!
Click to expand...
Click to collapse
Old???? Okay I admit.. did turn 34 on the 17th this month.. but Old¿?? ;-P
Sent from my Legend using XDA App
whitetigerdk said:
Old???? Okay I admit.. did turn 34 on the 17th this month.. but Old¿?? ;-P
Sent from my Legend using XDA App
Click to expand...
Click to collapse
It's time for the younglings my friend
method 1 (preferred)
you can leave the LEGEIMG.zip to the root of your goldcard and go to boot loader and let it load and you confirm the update. i suggest using the same one that you use for the downgrade.
if, you don't have it download Legend rooting tools, extract the zip. locate testimage.zip... copy it to your goldcard and rename it to LEGEIMG.zip. (make sure you dont ended up renaming it to LEGEIMG.zip.zip if you know what i mean lol)
method 2 (goldcard not needed)
For the past few days i've been playing around with official RUU. and heres what i've done so far on testing the official RUUs from HTC (link from stickies)... it'll turn your Legend to stock.... even if your on CM7 or any other roms....
But... if you have an HBOOT of less than 1.00... be warn. RUU with Froyo will update it and there's no known method to downgrade. unless you dont care about it and thinks its about time you update it and you have intention on doing the S-OFF...

[Q] Incredible 2.3.4 cannot get S-off/root/temp root/anything

I have an Incredible 2.3.4 with this taken from HBOOT
Incrediblec XC Ship S-On
HBOOT-0.92.0000
Microp-0417
Touch Panel-ATMEL224_16ab
Radio-2.15.10.07.07
Ok, so here is my problem, I want to be rooted and I want S-off, but I cannot get anything done. The phone wouldn't recognize the SD Card, I got that taken care of. The phone does the 5 Vibrates when turning it on unless I have the USB plugged in and I do a battery pull. (This really screws up updates/RUU fixes where updates are necessary). And along those lines I tried an RUU back to 2.1 which didn't work because of the restart issue, but then I was able to run the update after booting into HBOOT USB but the RUU failed ultimately.
I've tried to gain root access through unrevoked 3.22, it simply says failed to push recovery, terminated. I've tried rooting using zergRush, it tells me that it has found a path and that its sending zergs, then it just stops without telling me what happened and kicks me back out of adb shell. This is a recurring problem, I will be in adb shell and then randomly and for no reason it was kick me out to the root of my computer.
I'm working on a Windows 7 64 bit machine, I have been using an ADB mini download, but have also tried working through the installed ADB with equal results.
If anyone has any idea of what I could be doing wrong or different please let me know. I really need some kind of help because I am at a major loss.
2.3.4 on the Incredible has not yet been rooted, therefore the rooting software (Unrevoked) has not been updated with a root method. That would be why it's not working for you. I've never tried to downgrade to an old version using an RUU, so I can't really speak to that.
Also, this was posted in the incorrect forum. You should have posted in the Q&A section, as this has nothing to do with development.
What about the radio?
I was wondering this same thing because my wife's Incredible isn't rooted, but she's on 2.3.4. If she ever asks me to root her phone to put something on it or give her some feature not otherwise available, I'd rather be prepared if possible.
While looking over the UnRevoked site, I noticed it didn't really mention the Android versions it worked with, just the radios. I wonder if it's possible to just flash the radio to 2.15.00.07.28, which is rootable, according to the UnRevoked site, and try the UnRevoked Forever tool?
The radios are pretty easy to get here after all.
I'm not recommending this without some confirmation from someone with a lot more experience rooting than I have though, so Caveat Emptor!
Just a thought.
Cheers!
keyslapper said:
I was wondering this same thing because my wife's Incredible isn't rooted, but she's on 2.3.4. If she ever asks me to root her phone to put something on it or give her some feature not otherwise available, I'd rather be prepared if possible.
While looking over the UnRevoked site, I noticed it didn't really mention the Android versions it worked with, just the radios. I wonder if it's possible to just flash the radio to 2.15.00.07.28, which is rootable, according to the UnRevoked site, and try the UnRevoked Forever tool?
The radios are pretty easy to get here after all.
I'm not recommending this without some confirmation from someone with a lot more experience rooting than I have though, so Caveat Emptor!
Just a thought.
Cheers!
Click to expand...
Click to collapse
You can flash radios in the bootloader, but, having S-ON, the zip file may need to be signed, so i'd say NO it's not possible to flash a radio w/o root.
Yeah, flashing radios with s-on is a brick magnet.
There is thread on downgrading to 2.2 and rooting in dev. It works.
Sent from my ADR6300 using XDA App
Sorry not dev but Q & A. Also it is on android forums.
Sent from my ADR6300 using XDA App
Long night....its in general search for root 2.3.4, downgrade, and s off.
Sent from my ADR6300 using XDA App
jpjj225 said:
Yeah, flashing radios with s-on is a brick magnet.
Click to expand...
Click to collapse
Actually it just wouldn't flash, because the file wouldn't be signed by HTC, so it wouldn't (shouldn't) brick the phone.
http://androidforums.com/incredible-all-things-root/427344-2-3-4-root-downgrade-s-off.html
There is the guide my friend used to do his recently acquired inc
Sent from my ADR6300 using XDA App
jpjj225 said:
Yeah, flashing radios with s-on is a brick magnet.
Click to expand...
Click to collapse
The phone won't brick. It just won't flash.
Oh sorry, thought I read that somewhere a long time ago. Something about flashing new radios is dangerous if you do it wrong. MY BAD!!!

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!

Categories

Resources