For noobs their is alot of overwhelming info in regards to doing this and seems to be a lil more simple on other models.....have read for hours on the forum and seems to be conflicting info and also a kernel file issue on the rogers dream rooting has me a lil confused....i have had my phone for 6 months and customized as much as you can without a root but i am getting bored and is time to play with it...wanna run roms and all the latest stuff on it and have access to the paid market and save to my sd card and all that other good stuff everyone else is doing.....lol.....i don't want to brick my phone but i would like to root it.....
okay to the point..................
now when i open Flash Rec the "Flash Custom Recovery Image" button does not even appear and i cannot get to the into Recovery mode.
One thing i noticed in Flash Rec says Phone type is EB1/32A...thought would be 32B? could this be a problem from trying to flash earlier?
i need rooting rogers dream 32b for dummies instructions....lol....
p.s someone needs to develop idiot proof rooting software with android ready to explode their will be alot of noobs with bricks.....lol.....
Here's the tutorial I suggest following:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
And yes it does work with 32B. I cannot stress the importance of making sure you know and are 100% comfortable with what you're doing to your phone. If you have to annoy the heck out of xda users to do so then by all means do it .
wow,seems like the rogers dream is more of a pain to root and a little limited cause of kernel issue....sounds like it could make adding future roms a pain cause they could be buggy.....
Its really not that bad if you just want to stick with cyanogen because the EBI1 port is always released promptly. There might be some other EBI1 roms posted in the sapphire development section, check it out. There is another method that makes your the rogers dream compatible with any rom that works on the G1. Some people have reported some connection issues with this method but it works fine for many others. I would only recommend going with that method if the selection of EBI1 roms isn't enough for you.
http://forum.xda-developers.com/showpost.php?p=4280573&postcount=130
The rogers dream is actually EBI1/32B. The reason it says 32A is posted here.
If you have any questions about this be sure to ask away before you decide to root.
i would like to be able to run the latest roms 2.0 and 2.1 once stable and new and up coming roms,sense ui and gadgets..... is it better to go with the other method you mentioned then the cyanogenmod based on that?
thanks for your help
okay am going cyanogenmod way ....lil issue before i move on......
the cm-recovery screen should say "CyanogenMod v1.4 + JF but is saying CyanogenMod v1.2 + JF .. . . .. . . .
lol
what did i miss used the wiki guide and files.......
i downloaded everything according to the wiki page..... am i missing something or doing something wrong that would cause it to load v1.2 instead of v1.4?
soloution found and moved on am at this part now with a new issue
Type the following commands to wipe your Rogers system image (and userdata, and cache) and replace it with the HTC image:
fastboot erase system -w
fastboot flash system system.img
The system will flash and you will see a green progress bar on the fastboot screen while the image is transferring and a red progress bar while it's installing.
Click to expand...
Click to collapse
got past erasing part......
then when type in fastboot flash system system.img i get error: cannot load 'system.img'
chrisyak said:
then when type in fastboot flash system system.img i get error: cannot load 'system.img'
Click to expand...
Click to collapse
Make sure that the system.img file you downloaded is in the same folder as fastboot (the "tools" folder).
I put the system.img file in the same folder as fastboot (the "tools" folder) on my computer and tried it once again only to receive the same error message.
chrisyak said:
I put the system.img file in the same folder as fastboot (the "tools" folder) on my computer and tried it once again only to receive the same error message.
Click to expand...
Click to collapse
It does need to be in that folder but I am not sure why you are still getting that same message. You could try rebooting your phone and starting that section over again. The file could be corrupt. Verify the MD5 sum that is posted on the guide.
Edit: You need to cd to the tools directory before running that command
Related
Since I'm unable to root my dream until I have SPL 1.33.2005 on the phone I've been trying to update it to the correct one. Once in recovery mode upon pressing alt-S with the update.zip on the root of the sdcard I get the following error
E:No signature (5 files)
E:Verification failed
Installation aborted
Exactly what am I missing?
that spl has nothing to do with getting root as far as i know. to get root you have to downgrade to rc-29. that is haykuro's spl that frees up more memory in system
david1171 said:
that spl has nothing to do with getting root as far as i know. to get root you have to downgrade to rc-29. that is haykuro's spl that frees up more memory in system
Click to expand...
Click to collapse
Hes Rogers.
http://forum.xda-developers.com/showthread.php?t=544654
xsnipuhx said:
Hes Rogers.
http://forum.xda-developers.com/showthread.php?t=544654
Click to expand...
Click to collapse
apologies for my ignorance with rogers. never had to deal with a rogers phone lol. but back to the OP's problem, if it says no signature then the spl you have for some reason is not signed. really do not know what the reason for this would be. you could have gotten a bad download of the spl. try to redownload the spl from haykuro's site and see if it will work
Even with haykuro's signed spl I still get the same error as before.
Also following http://forum.xda-developers.com/showpost.php?p=4048946&postcount=404 I get "cannot load "boot-new.img"
I have no clue whats going on anymore.
McTinkerson said:
Even with haykuro's signed spl I still get the same error as before.
Also following http://forum.xda-developers.com/showpost.php?p=4048946&postcount=404 I get "cannot load "boot-new.img"
I have no clue whats going on anymore.
Click to expand...
Click to collapse
do you have the boot-new.img in the same folder as all your other fastboot required stuff. sorry for lack of proper terms. follow the second post in this thread to set up a fastboot folder and place the boot-new.img in it. see if that helps any
The new boot image is in the same folder as the fastboot exectble as well as adb. I added the path of my tools folder to the environmental variables previously as well as copied AdbWinApi.dll to the system32 folder just in case. Again no dice.
Can you use adb or fastboot for anything else?
fastboots useless until I have the new spl installed, which I can't install either.
The only thing i can think of is that since it says the files are not signed, is that you can try to sign the update.zip for the spl and try flashing it. Other than that i can think of nothing else at this time. I'm sorry. Like i said earlier don't really know anything about the rogers rooting process except for what i saw in the thread posted earlier and since i do not have a rogers device to test it on i can't know more than what i read.
PHP:
After further hunting it seems that there are two different update.zips.
One is 184kb and one is 2MB. Using the rogers dream rooting guide I get the 184k one which doesn't work. Should I start hunting for the 2mb one and give the rooting another go?
It can't hurt to look for it. I hope you can finally get it rooted
I may have just bricked the phone.
I used the recovery flasher app from the marketplace to flash the recovery image from the rogers rooting thread. That gave me the cyanogen 1.2 + JF recovery image. I then flashed the .2005 spl or so I thought. After booting into fastboot it still showed .0009 spl. I figured what the hell and made a nandroid backup, the wiped the phone and flashed it with the cyanogen rom 4.0 and now the phone is stuck on the rogers boot screen. I still can get to the modified recovery mode as well as fastboot though.
your phone is not bricked thankfully that is just a soft brick. try to flash haykuro's spl from the rogers root thread again after using the recovery flasher app.
make sure that you do not use the trackball to flash it and that you use the keyboard commands and home and back to reboot.
Dear members, Like always i first of all would like to thank you all for the great effort and hard work all of you have put into this wonderful site.
I am a noob with a rooted nexus one. ( i was begining to think of myself a step above noob recently but trying to update my phone to froyo made me realize i still am a noob.
I so want to update to froyo NOW without waiting for the OTA update but i just cant figure out how to. i downloaded the FR50 ( with and without radio ) but both failed. SO i figured it must be due to stock recovery. So i went to Amon Ra's thread to flash the new recovery image using terminal but after placing the image on the sdcard when i enter the flash image command , it says " image not found " when its most definitely there on the sdcard and i checked the spellings over and over again but it just wont flash and as a result i still cant enjoy froyo
I am sooooo sorry if i posted this thread in the wrong section but i really could use some guidance from the most intelligent Android people i know .
Regards,
Nadeem
It's basically a 4 step process, but make sure you did all of them.
1) Unlock Bootloader
2) Apply Root. I used this method, quick and painless: http://android.modaco.com/content/g...-erd79-frf50-superboot-rooting-the-nexus-one/
3) Flash Recovery using ADB.
3a) Recommended: Do a Nandroid backup image of your Stock 2.1u1, just in case something wierd happens during your flash.
4) Flash FRF50 ROM w/Radio. You want the version with the new Radio, as I believe 2.2 won't work with the 2.1 radio without tinkering.
ATnTdude said:
as I believe 2.2 won't work with the 2.1 radio without tinkering.
Click to expand...
Click to collapse
It works for the most part, but you'll get a crash if you try to record video without updating the radio.
Wait...you put the Recovery image on your SDCard? It should be on your harddrive. You push the the image from the HDD to the phone. Unless there's some other way I don't yet know about.
caliwolv said:
It works for the most part, but you'll get a crash if you try to record video without updating the radio.
Click to expand...
Click to collapse
Well, I'm glad I at least the gist of the material is sticking. I browse this place just about every day trying to keep myself from bricking my phone. If I do, it's back to my Nokia E71, and being forced to use Symbian after Android 2.2...not pleasant at all.
I highly appreciate the super quick response ATnTDUde
The first two steps in your method describe how to get root i presume....
Actually i already rooted my Nexus 1 and i am fairly certain the bootloader is unlocked too ( i see a small padlock unlocked every time i turn my N1 on)
Oh so i am going to have to flash the AMon Ra recovery image using ADB. actually on Amon's thread there was another method of flashing the image using terminal which i tried and failed at. I'll most definitely try ADB method once i get back home.
Just wanted to ask you a quick question Sir.
Once i flash Amon Ra's recovery image i assume i wont be getting any OTA updates from google ???? right ....
Also if i want to go to the stock recovery image ( is there a way to do so ? ) will i start getting OTA updates
Please some one help with the two questions above coz i cant start the process without knowing.
nadeemhasnaat said:
......
Once i flash Amon Ra's recovery image i assume i wont be getting any OTA updates from google ???? right ....
Also if i want to go to the stock recovery image ( is there a way to do so ? ) will i start getting OTA updates
Click to expand...
Click to collapse
1) right
2) yes
ATnTdude said:
Wait...you put the Recovery image on your SDCard? It should be on your harddrive. You push the the image from the HDD to the phone. Unless there's some other way I don't yet know about.
Click to expand...
Click to collapse
Yeah, its very easy.
adb shell flash recovery /sdcard/Amon-Ra.img
or whatever the thing is.
or you can
fastboot flash recovery C:\android\tools\wha\tev\er\Amon-Ra.img
The path just has to be correct wheter o
I'm a relatively new user to root, with my htc hero cdma rooted since Feburary 2010, but I've been having some problems as of late with my custom recovery image.
When I try to load the Image from fastboot, I get the error "Wrong or no image," (Among others of the same nature), as fastboot tries to load the image several times, it fails with the same general error. It happens very quickly, so I can't post many details, but if a picture or two is needed for more information, I can provide a few for refrence. I am running Darchdroid 2.6.2, great rom, and I would love to update to the newest image(And Rom). I've tried booting into recovery several times, but it bootloops at the HTC logo. I've tried booting from fastboot and DS updater, but the same bootloop occurs, probably because the error is ongoing at fastboot. I've tried flashing multiple images and from using flashrec, I get a command line error. I've flashed many through command line, and the same error occurs.
Can Anyone help me out, or knows what's going on?
PS: If it helps, I have all of the fastboot device stock, EX: radio is the stock 1.0.4 and the touch panel is the stock touchpanel, etc.
put a new recovery image on your Sdcard.
Code:
adb remount
adb shell
flash_image recovery /sdcard/recovery.img
See what that does for ya.
Broken Root???????
Kcarpenter said:
put a new recovery image on your Sdcard.
Code:
adb remount
adb shell
flash_image recovery /sdcard/recovery.img
See what that does for ya.
Click to expand...
Click to collapse
I tried it, but unfortunately, it didn't work. Instead, the same error came up again several times, and I tried with many different images, even with my last two working images.
Can you ask or message anyone who you know who might know whats going on, and can help me???
Ryoma Echizen said:
Can you ask or message anyone who you know who might know whats going on, and can help me???
Click to expand...
Click to collapse
What error message is it giving when you try to flash a new image?
I would also try a different SD card.
EDIT:
NVM I assume that you are getting the run via adb error.
Try a different card. Your current ROM should have absolutely no effect on nandroids.
Broken Root???????
Kcarpenter said:
What error message is it giving when you try to flash a new image?
I would also try a different SD card.
EDIT:
NVM I assume that you are getting the run via adb error.
Try a different card. Your current ROM should have absolutely no effect on nandroids.
Click to expand...
Click to collapse
Ok I will try it, thanks. That could be the problem, since I switched sd cards recently. I am not getting the run via adb error, I am getting an error on fastboot that says; wrong or no image. My image started to freeze when I tried to flash when I switched sd cards to an 8gb. I will try this, and thanks a lot. I probably wouldn't have thought of this way of solving the problem!
Broken Root???????
Welllll.......
I still can't get the image to work...
Can you give me any help, like direct message anyone who you know who might know how to solve this problem??? The error is as follows: "finding name of image, some element in the said image,"
"Wrong or no image!"
Can you message zenulator or anyone who you know who might be experienced in this problem.
Kcarpenter said:
put a new recovery image on your Sdcard.
Code:
adb remount
adb shell
flash_image recovery /sdcard/recovery.img
See what that does for ya.
Click to expand...
Click to collapse
Do this:
Code:
adb remount
adb shell
cd \sdcard\
flash_image recovery recovery.img
Thats actually what I always have to do for some reason the other does not work.
Broken Root???????
For some reason, I get the same error.
Here are some more specific details (my approximate translation because it went by so fast, and not even the full 15 or so lines, but the gist of it...) :
Checking sdcard...
Opening HCTDIAG.zip...
No image!
checking HCTDIAG.nhb...
Wrong or no image!
If you think the log would help, I can email or message it to you. I have been trying all kinds of commands for the last three hours, and no luck...
If anyone knows any solution to my problem, it would be a great help...
ADB works fine, anyway, so I don't think that's the problem.
Broken Root???????
Anyways, if it helps, I'm just trying to get back to the damagecontrol 2.1 stock sprint leaked rom. I might be able to get away with a wipe and then leaving the only data on my sdcard as the backup from the stock sprint leaked. I don't mind any method, as long as I can get back to default and sense, I'll even take the official update with the low ram of 40 mb, rather then 80.
Best advice right now is to start over. Run the ruu, then reroot. It only takes fifteen minutes at most. I know you probably don't want to but sometimes you gotta instead of wasting hours
Broken Root???????
There may be one error though...
When I try to install apks (I have a mac), I get the error as follows, ex: can't find Browser.apk to install.
Maybe has to be in the operating system area, not sdcard?
Anyways, forget about this. I just need to get a working recovery image. Any advice on how to access recovery via adb, like maybe, "reboot recovery" though I doubt this will work, considering that it is just another way to boot into my broken recovery mode w/out an image, or the apparent, "wrong image!"
Broken Root???????
How do I do this, since I am running a rom that doesn't have htc sync??? Should I factory data reset and place a backup folder w/stock sprint 2.1 leaked on the sdcard so the boot will retrieve that and boot that data, since the whole operating system is extracted onto that backup? I don't really know how to run ruu's, and I don't want to run the risk of bricking my phone.
(Running darchdroid 2.6.2, and I do not blame darch for my current situation, just trying to avoid any misunderstandings there.) (O.O)
Broken Root???????
Sorry about the situation I'm in. Definitely the worst possible situation, and I really, really appriciate any help that anyone is willing to provide me.I'm clearly in a sticky situation...
go here and download the sprint hero 2.27.651.5 ruu. You need htc sync get that from sprint site in support and downloads. First run the sync then run the ruu exe with your phone plugged in and usb debugging turned on. Actually just follow the root guide from regaw
I found another way, it worked for me:
http://forum.xda-developers.com/showpost.php?p=6879703&postcount=953
Just realized you were on MAC I don't know much bout that but I have heard you can dualboot it with windows. Definitely something you want to do if you can and plan on messing with android
-------------------------------------
Sent via the XDA Tapatalk App
Broken Root???????
Well, I do have a windows vista laptop.
However, the sprint support section of the site is down for repairs, (TT.TT) so I can't download htc sync for the moment...
Broken Root???????
YESSSSSSS
The clockwork recovery option worked!!!
Special thanks to davec1234 for providing a working solution!!!
Thanks to thatguydid for providing another solution, and thanks to everyone who has replied to my problem that I created this thread to solve.
Just in case anyone else has this problem, then try clockwork recovery, and I think that Rom Manager is a great app from the market that helped me fix my problem, as well as improve my device speed and fixed my permissions to slow down force closes.
THANKS TO EVERYONE ON XDA WHO PARTICIPATES AND MAKES THIS FORUM GREAT!!!
I couldn't ever have fixed my problem without everyone's help!!!
STAY AWAY from GOD SPEED
i thought it was cool but it wouldnt let me flash new recoverys and froze phone after nandroideds on cm6... i also think it wouldnt let me flash the newest zen exp but im testing the above posts method
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.
Okay so Im seeing a lot of threads along the lines of sunshine doesnt work for me or w.e. it will youre just missing some points about what they mean by "stock" rom...
theres two ways this is fixed, one involves a RUU (Rom Update Utility) and the other involves a fastboot command.
if youre gonna RUU then this thread isnt intended for you, imho ruuing takes more time than booting into fastboot and flashing a proper boot.img(kernel)
So you downloaded a stock rom from the sprint section and cant get sunshine to work, youre prompted with an error message along the lines of "flash a stock rom"
but you just did? why is this happening?!?! heres the reason. the stock rom most likely has a modified boot.img for r/w permission or a modified ramdisk for another plethora of reasons.
relax though the fix is simple! all you need to do is flash a proper kernel/boot.img. but where can I get this? well there is a firmware zip with the boot.img in there along with other img's for the sprint device's which can be found in omjs thread, and no im not gonna extract those files for you. if you want s-off so badly you can put in a little work.
so this guide is for those on the latest rom version (sense) 4.4.4 as of 12/9/14
:1) youre on the latest rom version and you downloaded a stock rooted rom from this thread http://forum.xda-developers.com/showthread.php?t=2729173 (the stock roms there have modified boot.imgs)
:2) download the appropriate firmware zip you need for your device, e.g. H/K or None H/k (found in this thread http://forum.xda-developers.com/showthread.php?t=2729173 read carefully and find the right firmware.zip)
:3) go into the firmware zip you downloaded and take out the boot.img
:4) place the boot.img in your fastboot path (not covering how to do that here, there's many a guide on how to get that working, use search)
:5) reboot into fastboot
:6) connect your phone to your pc with the data cable, and open a terminal or cmd window. terminal for unix like environments cmd for windows.
:7) type fastboot flash boot boot.img in the terminal window
:8) wait for the after text, saying sent and success.
:9) reboot your device run sunshine, be happy.
Do note this is written under the assumption you have updated everything and are stuck on a snag with sunshine.apk if this is too confusing or you cannot understand do not try it, simply RUU!
reserved for super dumb'd down version which I haven't written yet...
Here's hoping someone finds this useful:thumbup:
Maybe this will cut down on some redundant posts both here & in the Sunshine thread.
Sinistertensai said:
reserved for super dumb'd down version which I haven't written yet...
Click to expand...
Click to collapse
You'll never be able to dumb it down enough. Maybe release a picture book with pop outs..
[GUIDE]Sunshine S-OFF [NOOB PROOF] <---- This is quite a bold claim, sir. Hopefully you're right (but I highly doubt it, lol).
Looking for a noob loophole....
But in other news, Flashify works for those who don't have access to fastboot, or just can't seem to understand how to flash a boot.img.
Granted, they still need working fastboot to use Sunshine...but whatever. Just putting it out there.
____________________________
Please remember to:
Check Q & A forums before asking!
Search forum for similar post before creating!
Hit "thanks" to everyone who may have helped you (it costs nothing)!
Read the OP!!!!
Captain_Throwback said:
[GUIDE]Sunshine S-OFF [NOOB PROOF] <---- This is quite a bold claim, sir. Hopefully you're right (but I highly doubt it, lol).
Click to expand...
Click to collapse
They can ruu or follow the very simple instructions I posted. If my eleven year old cousin can understand the simple steps then I expect people to be able to too. But you're right cap, nothing is noob proof when it comes to xda noobs...