ok first off this is a little more technical then the other root methods. all u really need from the root update is actually the spl (hboot.img) from that point u can fast boot and are pretty much in God Mode. so yeah i wanted to root my wifes Eris. but alo wanted to make a nandroid of her stock build with all her apps and stuff. just encase she didnt like the 2.1 build. anyhow heres how i did it.
before i start fastboot will be needed for this method. u can find it attached to this post. now fastboot is a very handy thing for a dev or anyone who may wanna flash boot.img, kernels, recoveries and really anything flashable. even update.zips. anyhow put it in ur working dirrectory rename it fastboot and excute as directed. this is a linux compiled fastboot so it will ost likely only be useful to those who are running linux.
i had to rename it "fastboot.zip" to upload to xda. download and rename "fastboot" and it will work fine
also look at the attached pictures on this post. they show what stock and GOD MODE hboot menus look like. that way u can confirm u have GOD MODE before pulling the battery. u will but just to remove all doubt i posted pics so one can confirm they are in fact in GOD MODE before they pull the battery. the top line in hboot menu is all that really says ur in GOD MODE. acutually it says... "PB00100 XC ENG S-OFF"
SO LETS ROCK AND ROLL
step one: get the PBOOIMG.zip from here (md5: 63eacc5ede3b179f95dc22d8ef585f94)
step two: put it on the root of ur sdcard and turn off the phone
step three: hold volume down while powering on. let it fine the PBOOIMG.zip and read it. at this point it will ask u to push the the jogball in to continue. BUT WAIT STOP RIGHT THERE. with that screen up pull the cover off the back of ur phone.
step four: ok now that were set with the cover off the back of our phone. get ready because this will go pretty quick. push in on the jog ball to continue with the install. the phone will reboot and when it comes back it will start looking for and reading the PBOOIMG.zip (we need to stop this or else itll flash the whole build) at this point pull the battery out. the hboot.img(spl) installed in that split second before it rebooted. which means u have GOD MODE.
step five: power the phone back on normaly. once ur booted in u need to remove the PBOOIMG.zip from the sdcard. i did it like this.
adb shell rm /sdcard/PBOOIMG.zip
step six: power the phone back of then hold volume down and power back on into hboot menu
step seven: get the recovery.img from here put in a directory u can remember on ur computer.
step eight: at this point with ur phone plugged into ur computer and in hboot menu. u will notice at the top it says..."PB00100 XC ENG S-OFF" <~~this is GOD MODE. anyhow look further down and u will see the fastboot option in orange. press send key to enable. wait a second or two and u will see "fastboot usb" in red. this means ur all setup to fastboot.
step nine: now were gonna fastboot flash the recovery.img to the recovery partition. u can do this buy this command: (btw i use linux and this is where it was on my computer)
fastboot flash recovery ~/Downloads/recovery-RA-eris-v1.6.2.img
if all goes well it should print this:
sending 'recovery' (3834 KB)... OKAY
writing 'recovery'... OKAY
step ten: press volume down to return to hboot mode. then volume up to reboot to recovery.
step eleven: then navigate through recovery to backup/restore>Nand backup or BART backup (ur choice) then select and wait for the backup to finish. once its finished u can just press volume down till u get back to the main screen and then just reboot.
were finished. now ur stock rom is not a root rom. so once u reboot back into it ur not gonna have su and #. u will still need to flash a custom update.zip via recovery to have a root build. but at this point u have a nandroid backup of all the stuff had. so if for some reason u ever wanna flash back stock ur set.
the spl (hboot.img) is all u actually need from the PBOOIMG.zip to be able to have root and flash custom roms. the radio.img from the PBOOIMG.zip can also be extracted from the zip and flashed via recovery or fastboot.
reserved::
toastcfh,
Awesome, makes perfect sense! I think this might be exactly what I was waiting for in order to loosen my grip on 1.5 and do the root dance.
I have a couple of questions though, I hope you don't mind:
My impression is that Amon_RA's recovery + Nandoid, BART, et cetera - (or fastboot+ S-OFF) allows you to backup/restore anything on a partition-by-partition basis, e.g. on the Eris we have
$ cat /proc/mtd :
Code:
dev: size erasesize name
mtd0: 000a0000 00020000 "misc" (normally skipped)
mtd1: 00500000 00020000 "recovery" (normally skipped so it won't get nuked accidentally)
mtd2: 00280000 00020000 "boot"
mtd3: 0aa00000 00020000 "system"
mtd4: 08200000 00020000 "cache" (normally skipped)
mtd5: 09f80000 00020000 "userdata"
...but I'll have to admit - my understanding about the flashing of hboot, radio, and nv images is little bit fuzzy about what is possible - specifically if it can be done without a signed zip (the way it normally happens is with the RUU update process).
They are neither backed up nor restored by by the recovery tools, correct? (Amon_RA doesn't mention them in his announcement thread)
I was under the impression that fastboot can't flash any of those images, well... one by one anyway. Is that what the "fastboot update update.zip" method is for, or is there some other way to avoid the zip-signature issue that the RUU/PB00IMG.ZIP+hboot methods use?
I'm probably missing something completely obvious - and of, course, I'm aware that we have the 1.5 image files (hboot, radio, & nv) from the RUUs - but how do you burn them to the phone, assuming the S-OFF bootloader and/or (Amon_RA) recovery are in place on the phone?
bftb0
Also...
- can steps 5 & 6 be skipped by ejecting the SD card after the battery pull (step 4), and re-inserting it just before step 10? (Delete the PB00IMG.ZIP file later - after everything else is done.)
bftb0
bftb0 said:
Also...
- can steps 5 & 6 be skipped by ejecting the SD card after the battery pull (step 4), and re-inserting it just before step 10? (Delete the PB00IMG.ZIP file later - after everything else is done.)
bftb0
Click to expand...
Click to collapse
well im sure it might work. but... if u eject the sdcard it will stil sit and search for the it and u will have to sit and wait for a bit. i say pull the battery because its prolly the quickest way to pull this off and its how i did it. if u wanna try to eject the sdcard instead of pulling the battery ur welcome to try. if u do it and it works well post and give feed back on what happened. i tried to make this as detailed as possible to clear up most questions. so a good post on what u did and how it went down would be great for me to update the my post. thanx
bftb0 said:
toastcfh,
Awesome, makes perfect sense! I think this might be exactly what I was waiting for in order to loosen my grip on 1.5 and do the root dance.
I have a couple of questions though, I hope you don't mind:
My impression is that Amon_RA's recovery + Nandoid, BART, et cetera - (or fastboot+ S-OFF) allows you to backup/restore anything on a partition-by-partition basis, e.g. on the Eris we have
$ cat /proc/mtd :
Code:
dev: size erasesize name
mtd0: 000a0000 00020000 "misc" (normally skipped)
mtd1: 00500000 00020000 "recovery" (normally skipped so it won't get nuked accidentally)
mtd2: 00280000 00020000 "boot"
mtd3: 0aa00000 00020000 "system"
mtd4: 08200000 00020000 "cache" (normally skipped)
mtd5: 09f80000 00020000 "userdata"
...but I'll have to admit - my understanding about the flashing of hboot, radio, and nv images is little bit fuzzy about what is possible - specifically if it can be done without a signed zip (the way it normally happens is with the RUU update process).
They are neither backed up nor restored by by the recovery tools, correct? (Amon_RA doesn't mention them in his announcement thread)
I was under the impression that fastboot can't flash any of those images, well... one by one anyway. Is that what the "fastboot update update.zip" method is for, or is there some other way to avoid the zip-signature issue that the RUU/PB00IMG.ZIP+hboot methods use?
I'm probably missing something completely obvious - and of, course, I'm aware that we have the 1.5 image files (hboot, radio, & nv) from the RUUs - but how do you burn them to the phone, assuming the S-OFF bootloader and/or (Amon_RA) recovery are in place on the phone?
bftb0
Click to expand...
Click to collapse
ok im gonna give this a shot for u. ok u got the partions listed here correctly which is good. ok when u flash amon_RA's recovery it flashes to the recovery partition. at that point u got the ability to use flash_image which is in the recovery. flash_image enables recovery to flash update.zips and some .img files. image ".img" files are whats inside the RUU ur talking about. a RUU is just a utility that whenn u run it, it will extract the includes image files to a file on ur computer. then flash those files via hboot. but it does it all automagic for u to avoid the user error part of life. just one thing about the image files though. u can flash via amon's recovery the radio, hboot, and boot.img using the flash_image comand while in amons recovery. the hboot u will never need to change most likely. it doesnt hurt to have full root (GOD MODE).
now as for fastboot. fast boot gives u the ability to flash all image files to all partitions. but it doesnt give u the big backup restore option like amon_RA recovery does. fastboot is more for dev purposes. giving a dev the ability to flash images without pushing them to the phone first and also the option to just boot the image instead of flashing it. so if it a image file doesnt do what was expected by the dev then he can just boot back into hboot menu and try the next, without having to take the extra steps of booting into recovery, pushing the next image file, flashing it and rbooting. hence the name fastboot. its fast but again this is really a dev tool. flashing or booting update.zips from fastboot i have never tried. as amon_RA recovery does this fine and lets me do a backup first.
for the use of this method of gaining root is the only time u should flash the recovery partition from fastboot. it can be done in root roms with ease if they are built correct.
there i hope i answered ur questions. sorry such a large post once u go root this way u will always have the reverse option. well as long as u have ur backup on ur sdcard. i did root this way for my wife and myself to have that security of knowing if she isnt happy with 2.1 or any other custom rom. she always has the build she knows she likes. 1.5 stock.
What exactly are Radios
toastcfh
[size=+2]AWESOME.[/size]
I'm running 1.5... with a S-OFF bootloader and Amon_RA's v1.2.6 recovery.
I need to figure out if there's any money in my Paypal account (haven't used it in 6 years), and buy both you and Amon_RA a coffee.
Gonna run out and get another SD card. Any suggestions about partitioning strategies, or whether you prefer Nandroid to BART for backup/restore, etc?
One thing you might edit in to the original instructions (step 9) is a mention to run fastboot from a root (Linux) or privileged account (Windoze), and check first that you are talking to the phone with a "fastboot devices" command. ( I got a small scare when I got to that step and forgot about needing root to write to the USB device under Ubuntu - I thought that the new bootloader was deaf for a minute there.)
bftb0
bftb0 said:
toastcfh
[size=+2]AWESOME.[/size]
I'm running 1.5... with a S-OFF bootloader and Amon_RA's v1.2.6 recovery.
I need to figure out if there's any money in my Paypal account (haven't used it in 6 years), and buy both you and Amon_RA a coffee.
Gonna run out and get another SD card. Any suggestions about partitioning strategies, or whether you prefer Nandroid to BART for backup/restore, etc?
One thing you might edit in to the original instructions (step 9) is a mention to run fastboot from a root (Linux) or privileged account (Windoze), and check first that you are talking to the phone with a "fastboot devices" command. ( I got a small scare when I got to that step and forgot about needing root to write to the USB device under Ubuntu - I thought that the new bootloader was deaf for a minute there.)
bftb0
Click to expand...
Click to collapse
Great man and I'm glad all went well. It was easy easy huh. Lol sorry bout not adding the whole root user deal. But thanx for the heads up. I will add it in as soon as I'm finished with this stupid windows install.( my hdd took a crap last week) anyhow about partitioning... I use nandroid for backups. But that doesn't make bart suck. It has some advantages over nandroid that I don't remember. Also for partitions I use ext 3 for a2sd on my heroc. But haven't hooked up the Eris yet. I will build a Rom soon that'll include a lot of goodies so keep an eye out
toastcfh said:
Great man and I'm glad all went well. It was easy easy huh.
Click to expand...
Click to collapse
When I saw your original post, I actually laughed out loud as soon as I got to the part about doing the battery pull.
I had noticed that little "flashing hboot" blip that occurs right before the 2nd reboot during the many times I had re-run PB00IMG.ZIP flashes - but I never put 2+2 together the way you did.
Very nice - anyone that wants the option of rolling completely back to "factory 1.5" has that option now.
bftb0
[Edit] PS - One more minor thing - I think that use of the trackball (step #3) for confirming operations in the bootloader menu wasn't present in the OTA 1.5 (HTC) bootloader - you use the End Key in step #3 if you have the factory/OTA 1.5 bootloader on the phone (7501a_1.47.0000_091023). Not a big deal, but thought I'd mention it cuz it might confuse folks - it never mentions the trackball in the menu with the factory 1.5 bootloader.
So just to make sure I understand this fully before I attempt, step 9 requires using the PC to type commands to the phone, correct?
I'm not sure I completely understand how to do that, but would like to learn.....
Sub-Standard said:
So just to make sure I understand this fully before I attempt, step 9 requires using the PC to type commands to the phone, correct?
I'm not sure I completely understand how to do that, but would like to learn.....
Click to expand...
Click to collapse
Yes.. ur gonna need to download the android sdk also to make fastboot. I gave all the resources u need for gettin the sdk making and using fastboot in my first post. I myself would suggest ubuntu as a os. As u can easily use wubi to dual boot it and its a noob friendly Linux distro. Most of the things u can do to ur phone are much easier to do in Linux
So download the SDK for windows starter pack, & download ubuntu, spend a little time reading up on how to use fastboot, then attempt the tutorial.....
So just to make sure I'm very clear, this is incase you want to have a backup to get your phone back to bone stock 1.5 for warranty issues etc.... are is this just if you want to store a backup of all of your apps, settings, files?
I posted links to both the full sdk and the fastboot wiki and cheat sheet. If ur gonna do it through windows u need to follow the windows constructions for the sdk. If ur gonna use Linux u need to follow Linux instructions to get the sdk from the link o provided.
As for what this will backup... it will backup ur entire system and boot partitions. Including all apps settings preferences and everything else u had while stock. Leaving u with the option to restore ur device to stock specs. This will not however back up ur stock recovery and hboot partutions. U would however be able to return to stock specs. But that's a whole new tutorial. This will just leave u with the option to return to ur stock setup if u ever desire too. Like a snapshot of ur setup before u went root. Instead of just aimlessly flashing an entire build and losing everything u had before root. It just was more practical for me to still have that stock option. So if my wife wanted to go back stock she could easily. In the end to just get root. U don't have to flash the entire root build u just need to flash the GOD MODE spl (hboot.img). After that's installed u can flash anything u desire through fastboot.
I'm assuming something stops this process from working on Leak 2.1? And it has been tried?
Having a recovery partition installed would be clutch.
Great tutorial, fwiw. You make this community better, sir.
pkopalek said:
I'm assuming something stops this process from working on Leak 2.1? And it has been tried?
Having a recovery partition installed would be clutch.
Great tutorial, fwiw. You make this community better, sir.
Click to expand...
Click to collapse
what stops the process from working on the leak is the fact u dont have the ability to flash anything. ur not root but in the event of having root a downgrade is very possible. unrooting and using an ruu i very possible also. but yeah once u can flash amons recovery to recovery u are all set as root. the reason the we can flash this is because of the spl not an actual exploit. the spl or hboot.img give the ability to flash any partition on the phone. thats why i say flashing the entire update.zip is kinda pointless. the only part of the entire build u need is the hboot.img the build is root i believe. but from the tests ive done on the build ive found its nothing to write home about. i would suggest to anyone to go and do their homework on how to use fastboot and the rest of the sdk and root this way. the installing and using of the sdk will help to get comfortable with the device and root. all the tools u need to contribute to this and any forum are in that sdk.
and as for making this community better. i dont think i do anything different then any good dev should or would. i share all my work for free, educate those who wanna learn, help all i can that are in need, and am very open about all my workings. i hope to see more dev theads on this forum and see everyone work together as a community. this forum can and will be a place to find lots of information.
very nice work toastcfh! I think this is exactly what I've been hunting for. Sorry to be obtuse, but just so I'm clear: with this method, I should be able to backup, go for the 2.1 root, and if I do not love the 2.1 root experience get back to "stock?" If I reverted to stock, is there any reason I wouldnt be able to get the long awaited 2.1 OTA? thanks for your patience with those still trying to understand all this.
los04 said:
very nice work toastcfh! I think this is exactly what I've been hunting for. Sorry to be obtuse, but just so I'm clear: with this method, I should be able to backup, go for the 2.1 root, and if I do not love the 2.1 root experience get back to "stock?" If I reverted to stock, is there any reason I wouldnt be able to get the long awaited 2.1 OTA? thanks for your patience with those still trying to understand all this.
Click to expand...
Click to collapse
well when u do this u will flash amon to recovery. once u do that u can backup ur stock 1.5 system and apps to nandroid or BART backup in the recovery. that will save a "snapshot" of exactly what u had stock. at that point u can flash any of the custom roms the guys around here are making. if u dont happen to like the builds they are making and wanna go back to 1.5(stock) u can and all the apps,setting,everything will be there just like u left it.
but... DO NOT try to flash the rest of the root leak as it will over right ur amon_RA recovery, but ... if u decide u want to anyhow. as soon as u flash amon_RA recovery and go in to backup/restore>restore u will still have ur 1.5(stock) snapshot on ur sdcard. well as long as u didnt wipe ur sdcard
anyhow yeah this wont give u the option to go back and flash the stock ruu that i know of but it will at least keep that stock snapshot for u to fall back on anytime u may want or need. ie for the hell of it or when u go into the verizon store .
as far as when verizon releases have no fear... ur root now. im sure either i or anothr dev will cook up a rom to be flash from recovery within the first hours of its release. i promise u that when ur root u dont worry about when the next release is. u just look foreward to the next leak. well the flashoholics do at least.
Followed these directions, worked flawless. Thanks for giving us the option to go back to 1.5.
I'm now running rooted 0.3 and happy with it so far...but of course the OTA came out hours after.....
droost said:
Followed these directions, worked flawless. Thanks for giving us the option to go back to 1.5.
I'm now running rooted 0.3 and happy with it so far...but of course the OTA came out hours after.....
Click to expand...
Click to collapse
thats why i say flashing the whole root build is a waist. all u really want and need is the spl.
Related
Basically I unlocked bootloader and tried to load ROM. I tried the Desire and Cynagen. I was not successful at either. I manage to do a factory reset and the phone is working, except my wi-fi is shot, and when i recieve the initial OTA update it starts to download and then stops and I get the triangle of death as I call it with the lil android guy. I realy dont know what the hell Im doing and I need inch by inch restoring ROM for dummies instruction. I would like to go back to stock.I have been in threads but i get lost on certain things. I dont know what a adb is or how to acess it. I did read the noobies guide.. Please help as I am ready to chuck this thing out the window, i love my N1
I have searched the ORIGINAL SHIPPING TUTORIAL
and one other thread but i guess i cant post links.
please help!!!
do a search for adb for dummies on this site. it should help
Buck Shot said:
Basically I unlocked bootloader and tried to load ROM. I tried the Desire and Cynagen. I was not successful at either. I manage to do a factory reset and the phone is working, except my wi-fi is shot, and when i recieve the initial OTA update it starts to download and then stops and I get the triangle of death as I call it with the lil android guy. I realy dont know what the hell Im doing and I need inch by inch restoring ROM for dummies instruction. I would like to go back to stock.I have been in threads but i get lost on certain things. I dont know what a adb is or how to acess it. I did read the noobies guide.. Please help as I am ready to chuck this thing out the window, i love my N1
I have searched the ORIGINAL SHIPPING TUTORIAL
and one other thread but i guess i cant post links.
please help!!!
Click to expand...
Click to collapse
did you try to load rom in the recovery img? This also happened to me (triangle with the android guy) and I thought I couldnt flash custom roms. For some reason the regular reboot to recovery mode gives me the triangle of death as you call it.
I got around this by loading in into bootloader mode then going to my command console, getting to my skd tools folder, and then typing
fastboot boot (whatever recovery img you used)
Then everything worked perfectly.
They are going to move this to General....
You did not follow the steps correctly it sounds.
Did you Load Amon Ras Recovery?
IF YES,
GO into Recovery
WIPE data
Flash Cyanogen's Latest ROM
Flash Google Apps available on Cyanogen's front page Post
In future ALWAYS nandroid Backup...
If you did not load Amon Ra's Recovery, you should go do this from fastboot.
I'll try to explain it to you:
1. The Bootloader is unlocked (you see the open lock at the first screen)? If you don't see the lock this is the first you should do or send it directly in for repair!
2. Then you have to flash the Recovery ROM (http://forum.xda-developers.com/showthread.php?t=611829) This you need to flash an update.zip Exact instalation guide is in the Link.
3. The ROM. If you want Stock then here you'll find it as an update.zip: http://android.modaco.com/content/g...-online-kitchen-optional-root-insecure-himem/
Choose one without includet Radio ROM!!! (See below why!)
4. Copy the ROM to your SD Card Root
5. Go into Recovery ROM (Vol Down with Power and then select recovery with the Volume button). There you select wipe and choose the first entry there (wipe data and cache)
6. Stay in Recovery ROM and selct Flash from update.zip and select the update.zip. Wait until everything is done and you are promted to reset your N1.
(DON'T MESS AROUND WITH THE RADIO ROM IF YOU DON'T KNOW EXACTLY WHAT YOU ARE DOING. DON'T UNDERSTAND ME WRONG, I THINK YOU HAVE NO GLIMPS WHAT YOU ARE DOING SO BETTER LEAVE THE RADIO ROM ALONE!!! YOU MAY BRICK (DESTROY) YOUR PHONE WITH IT!!! If you dont believe: http://android.modaco.com/content/g...odaco-com/303716/nexus-cannot-on-after-flash/)
7. There should be no 7. Everything should be fine by now.
Hope I could help.
** 100 Posts **
Stheoft u are my hero!!! Now hold do I get the multitouch update? lol sorry
DID YOU EVERY KNOW THAT UR MY HERRRRRRROOOOO
edit: i got it, im back to square one... thanks alot for all ur help
@ Buck Shot, this is a development forum... threads with question shud go in the general forum... these are making the development forum a mess....
Download removed, go ahead and thank user nimdae for pointing out the wrongness of my work. I am done with Eris dev work because of people like him.
nimdae <-- that user right there.
THIS IS NOT FOR LEAK USERS SO DON'T ASK
*start rant* THIS MEANS DON'T MESSAGE ME ASKING HOW TO USE IT ON 2.1LEAK, ITS NOT CURRENTLY POSSIBLE TO DOWNGRADE FROM LEAK. PLEASE STOP SENDING ME MESSAGES ASKING HOW.*end rant*
If it bricks your phone, not my fault (it shouldn't and I hope it doesn't).
Please read and follow the directions included in this thread.
unzipme.zip md5sum: 0ed3c91d7574367d65428b3bc230f217
This is fully working, I just did a full reflash to 1.5, including the kernel, the system software, the radio firmware, recovery image and the bootloader.
This must be done from a PC with Fastboot, which comes with windows. Linux/Mac users will have to find it and compile it. You will need to have Amon's recovery image installed to use this downgrade, at the end we will overwrite his image with the stock one.
Inside unzipme.zip are three files
downgrade.zip md5sum: c440c87f1e67f4b62e05da0d255e80e9
-Do not unzip/open/alter this file
--Contains your kernel, radio firmware, and system.
recovery.img md5sum: 71a4b633bdb32de9dcdd8953fef43cdc
--stock recovery image
hboot.nb0 md5sum: 38899da4e5e002e3be22900f5f4eb6f7
--Original bootloader
Step one:
Put hboot.nb0 and recovery.img in the tools dir of your sdk.
Put downgrade.zip on the sdcard of your phone
Step two:
Turn your phone off, then turn it back on holding the power button (red) and send button (green). Once in the boot loader press volume down, then volume up to get to Amon's recovery image. Go to wipe, wipe dalvik cache, and do a factory reset (aka wipe data). Then choose flash zip from sdcard, and flash downgrade.zip. The phone will flash the kernel, and system softare, then ask you to reboot. Let it reboot so it can flash the radio, it will restart back in the recovery image. You can power down your phone now.
Once the phone says "Formatting CACHE:" wait 30seconds and your done. This is an minor error in the update-config on my part, but it is not harmful and I won't be fixing it.
At this point if your just wanted 1.5 back, you are done.
If you want the original bootloader and recovery image, (ie 100% stock) continue on.
Step three:
Plug your phone into your PC. Power your phone on using the power button (red) and send button (green). Your phone should now be sitting back at the bootloader screen and say FASTBOOT USB. Now on your PC, go to the sdk tools dir in command line. Issue this command.
Code:
fastboot flash recovery recovery.img
Let it flash, when done wait a minute (just to make sure).
Then issue this command
Code:
fastboot flash hboot hboot.nb0
Once this is done, wait a minute then pull your battery and restart your phone.
You are now back at factory stock.
Thank you ivanmmj for showing me how to do this crud, and zifnab06 for telling me the right way to flash hboot.
...
..
.
jcase
Risk of losing root permanently? I could be up to test, but I won't be home til after 5 pst. I'll hit you up on irc later to check if you're still looking for someone.
This is not the droid your looking for......
move along move along.
What are the risks / requirements?
Darn, if this was a 2.1leak to 1.5 test, I would so be your guinea pig, since I'm getting a new phone tomorrow anyway. lol
Ruh17 said:
Risk of losing root permanently? I could be up to test, but I won't be home til after 5 pst. I'll hit you up on irc later to check if you're still looking for someone.
Click to expand...
Click to collapse
no you could just root again by loading the rooted 2.1 rom
Thanks jamezelle. Good job devs. Don't know how you find the time to work your magic every day.
I have 2 eris's here. Ones an extra. Let me know..
This kind of gets me excited being on 2.1 leak atm but I guess I should not bother to get hopes up doing things while rooted is a lot easier than when not so Im guessing I am going to be stuck.
OH DANG!!!!!
i am so excited!!! if you're like 90% seure it will work i volunteer!!!
i love 2.1 but i WANT to root SO BAD
Too bad its not for 2.1 leakers huh?
Has anyone tried this? I have an extra eris sitting around running the 2.1 root. If it has not been tried i will test it on the extra one (warranty have to send it back in a few days)
morbidpete said:
Has anyone tried this? I have an extra eris sitting around running the 2.1 root. If it has not been tried i will test it on the extra one (warranty have to send it back in a few days)
Click to expand...
Click to collapse
Please try it! I want to have a sure downgrade after root.
no links :-/
Apparently I need to fix it, and i dont have time right now.
jcase said:
Apparently I need to fix it, and i dont have time right now.
Click to expand...
Click to collapse
ohh ok. NP
where is the link to download
?
bah never mind shouldhave read the last post.... =X
Now, if I root and go stock, the engineering bootloader stays correct? Would they notice that the engineering bootloader was there if I turned it in for warranty? What's the difference in appearance on the engineering bootloader?
I have successfully flashed my Sprint THC hero with no problems.
My issue though is flashing the phone to 2.1d. i can't for the life of me follow these directions and I am really stumped on the process of doing a nandroid and flashing the ROM.
I downloaded the nandroid from this site but not sure where I put the directory with the files at. Can anyone break this process down into "ejpyle terminology"?
My problems are:
- where to copy the nandroid directory
- where to put the 2.1d ROM
- do i need this busybox that everyone is talking about?
Successfully flashed what? And what method.
If you mean you successfully ROOTED your Phone then huzzah, that's step one complete.
Part of the rooting process should include putting a recovery image on the phone. If you did that correctly then do this, power off the phone.hold down the home button and power it back up. In a few seconds you should boot into a recovery menu with options to do a nandroid backup/restore turn on the usb connection to move files to the phone from your pc, and flashing a zip. If you don't have this recovery menu then you need to install it.
I don't think you have downloaded a Nandroid, I think you have downloaded an "update.zip" as we so affectionitly call them around here. This is a term used from the first set of recovery tools we had, where we had to rename update files update.zip to be loaded. Thankfully the recovery software has been updated to let us store and use multiple files.
So you probable have fresh-cdma-hero-2.0d.zip downloaded.
Plug your phone into USB and set it to Mount SD Card or what ever it says in 1.5
Copy this file to the root of the sdcard. don't put it in to any folders just F:\ or whatever the drive letter is.
THEN
Unmount the sdcard or turn off the disk drive mode (Cant remember what 1.5 calls it)
THEN
Power off the phone.
Power the phone back on whilst holding the home key. When you feel the vibration (let your girl hold it if she wants ROFL) let go and it will boot into recovery.
THEN
Go to Wipe...do Factory Reset
THEN
Wipe dalvik
THEN
Go back to Flash Update from SDcard
Select the update file above and hit the home key to flash it.
The phone SHOULD install and go back to the main screen of recovery.
THEN select
Reboot
THEN
Wait a hell of a long time 10+ minutes is NOT uncommon (it has to rebuild dalvik and other stuff)
THEN
When the phone boots hit Always Allow for the memory settings app.
THEN
Setup all your google info again.....
THEN
You should be good to go
AND DEN????????
HAHAHAHAHAHAHA
EDIT:
I am SURE that I left a step out above, just go with the flow and wipe everything under the wipe menu. It's laid out so a monkey can do this stuff...hence the reason I am able to.
gunnyman said:
Successfully flashed what? And what method.
If you mean you successfully ROOTED your Phone then huzzah, that's step one complete.
Part of the rooting process should include putting a recovery image on the phone. If you did that correctly then do this, power off the phone.hold down the home button and power it back up. In a few seconds you should boot into a recovery menu with options to do a nandroid backup/restore turn on the usb connection to move files to the phone from your pc, and flashing a zip. If you don't have this recovery menu then you need to install it.
Click to expand...
Click to collapse
thank you thank thank you... you have me going in the right directions.
Quesion..what is the best (most reliable without as many bugs) ROM to load that is 2.0-1?
ejpyle said:
thank you thank thank you... you have me going in the right directions.
Quesion..what is the best (most reliable without as many bugs) ROM to load that is 2.0-1?
Click to expand...
Click to collapse
Not to be rude, because you seem like a decent enough person, but please read http://forum.xda-developers.com/showthread.php?t=668905 before asking anything else. Most of your answers are there, and 'search' will find the rest.
Kcarpenter said:
I don't think you have downloaded a Nandroid, I think you have downloaded an "update.zip" as we so affectionitly call them around here. This is a term used from the first set of recovery tools we had, where we had to rename update files update.zip to be loaded. Thankfully the recovery software has been updated to let us store and use multiple files.
So you probable have fresh-cdma-hero-2.0d.zip downloaded.
Plug your phone into USB and set it to Mount SD Card or what ever it says in 1.5
Copy this file to the root of the sdcard. don't put it in to any folders just F:\ or whatever the drive letter is.
THEN
Unmount the sdcard or turn off the disk drive mode (Cant remember what 1.5 calls it)
THEN
Power off the phone.
Power the phone back on whilst holding the home key. When you feel the vibration (let your girl hold it if she wants ROFL) let go and it will boot into recovery.
THEN
Go to Wipe...do Factory Reset
THEN
Wipe dalvik
THEN
Go back to Flash Update from SDcard
Select the update file above and hit the home key to flash it.
The phone SHOULD install and go back to the main screen of recovery.
THEN select
Reboot
THEN
Wait a hell of a long time 10+ minutes is NOT uncommon (it has to rebuild dalvik and other stuff)
THEN
When the phone boots hit Always Allow for the memory settings app.
THEN
Setup all your google info again.....
THEN
You should be good to go
AND DEN????????
HAHAHAHAHAHAHA
EDIT:
I am SURE that I left a step out above, just go with the flow and wipe everything under the wipe menu. It's laid out so a monkey can do this stuff...hence the reason I am able to.
Click to expand...
Click to collapse
You rock....You just taught a death and blind monkey how to do it. Thanks man!!!!! I will be sure to have my wife hold the phone for the vibrate thing. LMFAO
ejpyle said:
thank you thank thank you... you have me going in the right directions.
Quesion..what is the best (most reliable without as many bugs) ROM to load that is 2.0-1?
Click to expand...
Click to collapse
There is no best one. The 2.1 ROMS are all very stable. Just avoid the ones that say {DEV} in the thread title because they are under development and likely have lots of stuff broken in them.
Decide what you want for yourself, beauty, speed, both? A good hint is to look for the ROM threads that have the most pages attached to them these are the ROMS that have the most discussion and help within them.
ejpyle said:
You rock....You just taught a death and blind monkey how to do it. Thanks man!!!!! I will be sure to have my wife hold the phone for the vibrate thing. LMFAO
Click to expand...
Click to collapse
DO NOT FLASH THE 2.1 Signed RUU Test ROM
OR I WILL FIND AND KILL YOU!
gunnyman said:
There is no best one. The 2.1 ROMS are all very stable. Just avoid the ones that say {DEV} in the thread title because they are under development and likely have lots of stuff broken in them.
Decide what you want for yourself, beauty, speed, both? A good hint is to look for the ROM threads that have the most pages attached to them these are the ROMS that have the most discussion and help within them.
Click to expand...
Click to collapse
thanks man, if I win the power ball lottery I will be sending you all a private message.
one more quickie though, If Sprint releases the 2.1 before I become eligible for AARP will I have to flash back to the 1.5 version before updating my device with it?
Kcarpenter said:
I don't think you have downloaded a Nandroid, I think you have downloaded an "update.zip" as we so affectionitly call them around here. This is a term used from the first set of recovery tools we had, where we had to rename update files update.zip to be loaded. Thankfully the recovery software has been updated to let us store and use multiple files.
So you probable have fresh-cdma-hero-2.0d.zip downloaded.
Plug your phone into USB and set it to Mount SD Card or what ever it says in 1.5
Copy this file to the root of the sdcard. don't put it in to any folders just F:\ or whatever the drive letter is.
THEN
Unmount the sdcard or turn off the disk drive mode (Cant remember what 1.5 calls it)
THEN
Power off the phone.
Power the phone back on whilst holding the home key. When you feel the vibration (let your girl hold it if she wants ROFL) let go and it will boot into recovery.
THEN
Go to Wipe...do Factory Reset
THEN
Wipe dalvik
THEN
Go back to Flash Update from SDcard
Select the update file above and hit the home key to flash it.
The phone SHOULD install and go back to the main screen of recovery.
THEN select
Reboot
THEN
Wait a hell of a long time 10+ minutes is NOT uncommon (it has to rebuild dalvik and other stuff)
THEN
When the phone boots hit Always Allow for the memory settings app.
THEN
Setup all your google info again.....
THEN
You should be good to go
AND DEN????????
HAHAHAHAHAHAHA
EDIT:
I am SURE that I left a step out above, just go with the flow and wipe everything under the wipe menu. It's laid out so a monkey can do this stuff...hence the reason I am able to.
Click to expand...
Click to collapse
I hope the possible step left out above does not give me "another" bricked phone.
ejpyle said:
I hope the possible step left out above does not give me "another" bricked phone.
Click to expand...
Click to collapse
I think I may have left out a step if you have apps on your sd card...
NOT WAIT I LEFT OUT THE DO A NANDROID BACK UP FIRST!!!!!!!!!!! DO THAT FIRST!!!! HOLY CRAP I HOPE YOU HAVEN'T DONE ANYTHING YET!!! DO A NANDROID!!!!!!!
Nope no chance at all of that as far as I can tell.
The only bricks we have seen are from people downloading GSM software or dropping a brick on their phone...that sounded funnier in my head.
smw6180 said:
Not to be rude, because you seem like a decent enough person, but please read http://forum.xda-developers.com/showthread.php?t=668905 before asking anything else. Most of your answers are there, and 'search' will find the rest.
Click to expand...
Click to collapse
Because you too seem like a decent person I will share this with you....
I followed a thread on here at the beginning of march to install a ROM and the directions (which I followed exact) bricked my phone. I spent hours reading up on this website to find out after the fact that the RUU might have a bug and some users will have issues. With that said, I decided to ask questions. This site has a lot of cleanup going on (no disrespect to anyone here as you are all VERY intelligent) and I do not think that someone as myself would be comfortable just "searching" for the answer without asking questions first with respect to the experience we have had in the past.
Kcarpenter said:
I think I may have left out a step if you have apps on your sd card...
NOT WAIT I LEFT OUT THE DO A NANDROID BACK UP FIRST!!!!!!!!!!! DO THAT FIRST!!!! HOLY CRAP I HOPE YOU HAVEN'T DONE ANYTHING YET!!! DO A NANDROID!!!!!!!
Nope no chance at all of that as far as I can tell.
The only bricks we have seen are from people downloading GSM software or dropping a brick on their phone...that sounded funnier in my head.
Click to expand...
Click to collapse
LOL I have not done it yet. I am about to copy this nandroid - file name "nandroid-2.0.zip" to my SDCARD. then i will do it.
ejpyle said:
LOL I have not done it yet. I am about to copy this nandroid - file name "nandroid-2.0.zip" to my SDCARD. then i will do it.
Click to expand...
Click to collapse
So you have gotten me curious now, where did you pick up that file at?
My only guess is that someone has posted a nandroid of their device and zipped it. Most of the Rom downloads are ROMNAME.zip....
You can always try to load it, it won't load if its not setup properly inside for a rom.
And about your going back to 1.5 to update to sprints 2.1:
IF YOU UPDATE TO SPRINTS OTA 2.1 UPDATE YOU WILL NOT BE ABLE TO ROOT AGAIN UNTIL SOMEONE FINDS ANOTHER EXPLOIT!!! WHICH COULD BE NEVER!!
Kcarpenter said:
So you have gotten me curious now, where did you pick up that file at?
My only guess is that someone has posted a nandroid of their device and zipped it. Most of the Rom downloads are ROMNAME.zip....
You can always try to load it, it won't load if its not setup properly inside for a rom.
And about your going back to 1.5 to update to sprints 2.1:
IF YOU UPDATE TO SPRINTS OTA 2.1 UPDATE YOU WILL NOT BE ABLE TO ROOT AGAIN UNTIL SOMEONE FINDS ANOTHER EXPLOIT!!! WHICH COULD BE NEVER!!
Click to expand...
Click to collapse
I got it from here....
http://dx.infernix.net/nandroid-2.0.zip
when you boot into recovery, what do you see?
If you rooted correctly and put a recovery image on there there isn't anything else you have to do to enable Nandroid.
ejpyle said:
I got it from here....
http://dx.infernix.net/nandroid-2.0.zip
Click to expand...
Click to collapse
Ok, so this leads me to another question. Where is the thread that links to this download?
The reason I am worried about this file now that I see it:
It's only 942kb - WAY to small for a rom or nandroid.
gunnyman said:
when you boot into recovery, what do you see?
If you rooted correctly and put a recovery image on there there isn't anything else you have to do to enable Nandroid.
Click to expand...
Click to collapse
I had a triangle with an exclamation point.
I am copying the recovery to my SDCARD now... recovery-RA-heroc-v1.5.2
ejpyle said:
I had a triangle with an exclamation point.
I am copying the recovery to my SDCARD now... recovery-RA-heroc-v1.5.2
Click to expand...
Click to collapse
1.6.2 is the latest. Not a whole lot different from 1.5.2 but some bugs where fixed and you can get the nifty Green Nexus Carebear back ground.
Kcarpenter said:
1.6.2 is the latest. Not a whole lot different from 1.5.2 but some bugs where fixed and you can get the nifty Green Nexus Carebear back ground.
Click to expand...
Click to collapse
I copied everything you indicated to my card. When I press HOME and PWR together I get a triangle with an exclamation point. Did this monkey not do something right?
You know the guy I'm talking about: while he's sitting in the VD clinic with an itchy crotch, he's praying to God: "Oh God, please don't let it be herpes. If it's not herpes I swear I won't visit another whorehouse as long as I live."
Then, as soon as the doctor announces that he's just got a case of jock itch and he should put some anti-fungal on it, the guy runs to the whorehouse to celebrate....
Because, see, just a few days ago I semi-bricked my Evo running after a failed Unrevoked. Not sure why it failed, but the phone would lock up every 15 seconds. So I flashed a stock image to repair the damage, and then a newer one, and wound up with a phone that worked except it wouldn't read the SD card or USB port (charging would only occur if the phone was turned off).
So as I was working my way through the fix I kept promising myself that if I got it fixed I'd just keep it stock unrooted and be happy with it.
Then, thanks to the good fold here, I managed to get the device running again the way it should. Wheeew, I thought, I'm happy now.
But... of course... it only took a few hours before the "root" itch hit me again. Fixing the semi-brick issue required installing z4root, and that app gave me a taste of da root acces... and ooooh did it taste goooood! Problem with z4root, though is that you're still s-on, and it's my understanding that if you're s-on and take the new GB update, you're SOL (at least for the time being). And I wanted to be s-off for the peace of mind it offered.
So my desire for real permanent root got the better of me. I decided that the reason unrevoked had failed for me the first time probably had something to do with all the cr*p I had installed on my phone. So I used Titanium backup along with z4root to back up the stuff I'd installed since getting my phone back and re-flashed the stock 2.2 image that had worked for me, and started with afresh phone.
Tried unrevoked one more time and... viola! It worked!!!
I'm happy now... a happy, unrepentant sinner!
Anyway, if you've read through all this: bless you.
I do have a couple of questions:
1) Am I correct that being s-off means I can now install unsigned ROMs the same way I installed the stock image I am on? (basically, rename it PC36IMG.zip, put it on the root of the SD card and boot into the bootloader and let it install)?
2) do I need to run "unrevoked forever"? I'm not clear on this. Getting some conflicting information from searching. My best guess, from what I've read, is that the latest unrevoked includes all the stuff that unrevoked forever does.
-Is blessed-
1. You don't need to make a PC36IMG to flash a rom; just download the file, then backup your current rom, do a full wipe, then flash the rom zip
2. You don't need to flash the forever zip; it was used to give you nand unlock -s-off- in the older versions of unrevoked, and was incorporated into the new one.
And keep applying that jock itch.
And once you flash a couple roms, you will get the itch to start using the kitchen and playing with your own custom rom, its only a matter of time, lol
I probably try two a week now. Its amazing how much work these guys do.
Unrevoked forever is incorporated in Unrevoked now. So need for that.
Also, you dont flash them in the bootloader. Boot into the bootloader, then use volume down to go down to the option that says "recovery" then use the power button to select. It will boot into recovery menu which should have a list of options, go down to flash zip from sdcard, then select zip from sdcard. It will show you a list of everything on your sdcard. Navigate to wherever your rom .zip file is that you downloaded and select it. It will ask you if you want to flash, select yes.
PS dont forget to wipe before you flash. ("Wipe all user data/factory reset" option when your in recovery.)
RileyGrant said:
Unrevoked forever is incorporated in Unrevoked now. So need for that.
Also, you dont flash them in the bootloader. Boot into the bootloader, then use volume down to go down to the option that says "recovery" then use the power button to select. It will boot into recovery menu which should have a list of options, go down to flash zip from sdcard, then select zip from sdcard. It will show you a list of everything on your sdcard. Navigate to wherever your rom .zip file is that you downloaded and select it. It will ask you if you want to flash, select yes.
PS dont forget to wipe before you flash. ("Wipe all user data/factory reset" option when your in recovery.)
Click to expand...
Click to collapse
OK, so that's pretty much the same as with the Nook flashing Phiremod (a Cyanogenmod variant).
i have read LOTS of forums on this, but have found no diffinative, working methods. has anyone actually ever done this, and if so what method did you use? links/guides would be much appreciated! thanks
I also have searched everywhere and apart from "get a pc" or "get parallels and windows 7 for your mac" I've heard nothing concrete.
Any advice on this would be hugely appreciated!
ishamm said:
i have read LOTS of forums on this, but have found no diffinative, working methods. has anyone actually ever done this, and if so what method did you use? links/guides would be much appreciated! thanks
Click to expand...
Click to collapse
No guys, all the methods posted are just theoretical blabber posted for the LULZ!...
.... NOT!!!
... all the methods mentioned on this forum work, unless stated otherwise...
only a handful require a Windows PC
yes, preinstall method works, CWM root package works, gingerbreak works,
1-click easy root also works
follow the link, go to post 3... and you have directions for Mac OS
sorry, i didnt mention, im not on gingerbread (thanks to tmobiles slow updating), and most of these rooting methods seem to require it. would going straight to unlocking the bootloader be easier on mac? (i realise the methods arent written for fun, but many require a lot of presumed knowledge of terminal commands, which unfortunately i lack XD )
thanks
Bootcamp or parallels with windows 7. That's how I did it.
xploited said:
No guys, all the methods posted are just theoretical blabber posted for the LULZ!...
.... NOT!!!
... all the methods mentioned on this forum work, unless stated otherwise...
only a handful require a Windows PC
yes, preinstall method works, CWM root package works, gingerbreak works,
1-click easy root also works
follow the link, go to post 3... and you have directions for Mac OS
Click to expand...
Click to collapse
Many thanks, I'll try one of the ones you mentioned.
I'd love to try the one click method for mac but I clocked on the link, went to third post and it's not as you suggested it might be.
If there is a simple oneclick method for mac dullards like me it would be great to tell me where to go for it. Thanks again!
i have tried using dorootv3.sh and doroot2, on terminal, but both always fail, is there any other .sh that has been shown to work?
---------- Post added at 06:19 PM ---------- Previous post was at 05:32 PM ----------
basically, after a load of different attempts, my main problem seems to be this: to root on mac, i need 2.3.4 (i have 2.2.2); to get 2.3.4 i need to unlock the bootloader; and to unlock the bootloader it must be rooted.
it seems im stuck in this cycle, and dont really know what i should do. any help would be great.
can i flash with the at&t 2.3.4 from this thread http://forum.xda-developers.com/showthread.php?t=1125944 ?
you dont need root to unlock bootloader....you unlock bootloader through an sbf flash
we seriously need a popup box on every freaking forum that will explain what ROOT actually is.
root is SYSTEM access within the OS. outside of the OS, root doesnt mean squat
you will wipe all your system when you unlock your bootloader which means:
contacts stored on phone (unless you export them to vcf on sdcard)
settings
text messages
user installed apps
it does NOT wipe internal or external sdcard (i always keep a backup of this stuff on my computer anyway when i start messing with my phone)
oh sorry, in that case i totally got the wrong end of the stick reading the noob intro howtos so to unlock the bootloader what sbf do i need to flash? that i can do now through terminal, which is very handy, but i havnt come across any howto on bootloader unlocking that just says flash an sbf
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
i typed in google.com
'unlock motorola atrix bootloader'
a link lead me directly to that.....its the exact same tut listed here on xda....
sorry, im having a serious slow day, just gone on holiday so brain is totally out of gear XD thanks so much for clearing up the root/bootloader confusion, i have now unlocked successfuly, and will be installing my first rom!
ishamm said:
sorry, im having a serious slow day, just gone on holiday so brain is totally out of gear XD thanks so much for clearing up the root/bootloader confusion, i have now unlocked successfuly, and will be installing my first rom!
Click to expand...
Click to collapse
its not just you confused with root. its xda-wide.
for some reason sooooo many people have this notion that root=unlocking bl/s-off/rom-flashing
its frustrating to see people suggesting to others on some forums around here that they need to 're-root' their device when they are already on a rooted rom....its baffling that so much misinformation can be spread like wildfire.
my last confusion, for now XD, is this: the alien rom contains an image, which i can flash ok, but also a Meta Inf folder and System folder. if i follow this method
"
1. Extract all the files to the same directory and CD there in the terminal.
2. Put your phone in fastboot mode (turn it on holding volume down button then press volume up)
3. Type these commands in the terminal:
chmod +x moto-fastboot-osx64
./moto-fastboot-osx64 flash boot XXXXXX.boot.img (work out what Tegra part you need to flash and change the XXXXXX to that!)
./moto-fastboot-osx64 flash system ORFR234-system.img
./moto-fastboot-osx64 flash webtop webtop.img
./moto-fastboot-osx64 reboot
"
what should i do with the 2 folders, since as far as i know, i cant just flash folders right?
thanks
ishamm said:
my last confusion, for now XD, is this: the alien rom contains an image, which i can flash ok, but also a Meta Inf folder and System folder. if i follow this method
"
1. Extract all the files to the same directory and CD there in the terminal.
2. Put your phone in fastboot mode (turn it on holding volume down button then press volume up)
3. Type these commands in the terminal:
chmod +x moto-fastboot-osx64
./moto-fastboot-osx64 flash boot XXXXXX.boot.img (work out what Tegra part you need to flash and change the XXXXXX to that!)
./moto-fastboot-osx64 flash system ORFR234-system.img
./moto-fastboot-osx64 flash webtop webtop.img
./moto-fastboot-osx64 reboot
"
what should i do with the 2 folders, since as far as i know, i cant just flash folders right?
thanks
Click to expand...
Click to collapse
alien rom, as with any other custom rom, comes packaged for CLOCKWORK MOD RECOVERY
you dont extract rom zips
you need CWM installed on your unlocked atrix, then you boot to recovery, and flash the rom zip
oh man, just when i thought i'd started to understand everything! XD
if its not too much trouble, can you explain the method to go about installing alien on a mac, or if it exists, link a relevent thread? i can only find ones which confuse me even more
many thanks
ishamm said:
oh man, just when i thought i'd started to understand everything! XD
if its not too much trouble, can you explain the method to go about installing alien on a mac, or if it exists, link a relevent thread? i can only find ones which confuse me even more
many thanks
Click to expand...
Click to collapse
you dont install roms from your computer
you need to make sure you have CWM installed. you can do this with fastboot
fastboot this recovery on
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-olympus.img
instructions can be found
http://forum.xda-developers.com/showthread.php?t=1204500
you download a rom to your phone and flash it through recovery. no computer needed at all after you have unlocked and flashed recovery on.
and is this do-able without an SD card installed? before i get halfway down the road and find im screwed XD also it seems i need to be rooted for CWM, though i still cant find a way to do it...
ishamm said:
and is this do-able without an SD card installed? before i get halfway down the road and find im screwed XD also it seems i need to be rooted for CWM, though i still cant find a way to do it...
Click to expand...
Click to collapse
did you actually read the post above????
you can fastboot the recovery image.
you DO NOT need root in order to do so.....
yes i did read it... while it might be obvious to you, some of us have no idea what were doing. loads of howtos include having to install the rom from a SD card. also CWM says "The SD Card needs to be mounted to use ROM Manager" so i dont think its too much of a stretch to think i need one
ishamm said:
yes i did read it... while it might be obvious to you, some of us have no idea what were doing. loads of howtos include having to install the rom from a SD card. also CWM says "The SD Card needs to be mounted to use ROM Manager" so i dont think its too much of a stretch to think i need one
Click to expand...
Click to collapse
you dont need rom manager....
you boot into recovery and install from there.......
A. download rom
B. transfer to phone's storage (if you download directly from phone, obviously skip this step)
C. boot into recovery
D. wipe data/factory reset (option in CWM recovery)
E. select option: install from sdcard
F. confirm
G. after flash is complete reboot your phone, you are now on a new rom.