Database Users

Root Status

Well, I've asked a mod to lock the other root status thread. It was getting kind of out of hand. After about page 80, people stopped looking at what we had done so far, and trying to help by putting ideas out that already failed.
This is what we know:
Fastboot is locked down in everything but oem-78 mode. You can get to this mode by typing "reboot oem-78" at an adb shell. Fastboot is essentially unlocked, allowing fastboot boot and fastboot flash, only the .img images we try to boot or flash NEED TO BE SIGNED.
Goldcards no longer allow non signed firmware to be loaded, only signed firmware with a different SID.
All known flashing methods require the .img files to be signed by HTC. We do not have the privatekey, nor do we have any way to decrypt the key as it is RSA. Meaning this is a NO GO.
All previous known exploits (asroot2, g1 telnetd, DROID update.zip method) have been patched. They won't work. And there isn't a way around this.
All the partitions except /data are mounted as read only. Meaning, without root access, there is NO way to modify them. In the init.rc file, they are mounted rw, and directly after that mounted ro. We can read and write to /data as we wish, but NOTHING important is here.
The only folder anything can run as root out of is /system/bin. Every other partition is mounted with the nosuid option, meaning code CANNOT be run as root. Simple enough. We can't run anything as the user root, or the group root.
Lets try to stay a little more on topic this time. Please don't let this become another 40 pages of complete crap. And please keep this thread about root access, any other problems should be posted in the appropriate forum.
Thanks, and lets get this root done!

I'm currently comparing superboot.img in a hex editor to the vanilla boot.img for that phone so I can better understand what he did, and how. I'll see what I can turn up, maybe we can make one for the eris.
EDIT: It seems it's not going to be so easy. There's a lot of things changed. It appears he changed something at the top of the file right after the header, and then there is some sort of (SHA1?) hash right below that, but I don't know what it's calculated from. This is beyond my skills at the moment, I think.

Are any of the fields changed from the original boot.img show up in our boot.img? Chance of searching for each field in our img and replacing with possibly what he did?

is it possible that the guy who made superboot has htc signature, or somehow decrypted it???? 8-O

Yes I guess anything is possable but I think their is a better chance of monkeys flying out of my butt.

well i guess it was time to lock the other thread as some people could not play nice..... so i guess we will use this one now..... next idea anyone, and i am guessing jman will no longer be joing us, so it looks like we are on our own.

im ready to get this done what have we got so far?

About 140 pages of failed attempts.

well i know that much i have been sitting back following from the begining now im ready to get my hands dirty, though i have no clue what im doing

binny1007 said:
well i guess it was time to lock the other thread as some people could not play nice..... so i guess we will use this one now..... next idea anyone, and i am guessing jman will no longer be joing us, so it looks like we are on our own.
Click to expand...
Click to collapse
Ok, I missed something I think. Thats what I get for not refreshing every 10 seconds What happened to jman? Or is it better off that I not ask

punk.kaos said:
Ok, I missed something I think. Thats what I get for not refreshing every 10 seconds What happened to jman? Or is it better off that I not ask
Click to expand...
Click to collapse
I don't think I'll be following these threads anymore. I try to help you guys, but in the end some of you just don't appreciate the help.
I don't claim to be an expert, and I never promised anybody that I could root their phone. I simply have information to share that I think has brought you guys to a greater understanding of your phones and the Android system. Most of you are thankful, but I really don't need to be attacked personally in these threads that don't even have anything to do with my phone.
I'd like to thank the moderator for locking down the other forum, I'd also like to thank whichever moderator deleted the message that was quite insulting to me.... I only happened to see it because it came into my email. Yes, I subscribed to the thread via email to try to keep up with you guys and offer any help I could as quickly as I could.
I'm sorry guys, I wish you luck, but I just don't need to be berated in open forum like that for trying to help the Eris owners out, so I won't be keeping up with your rooting efforts.
There are a couple of you that have been very appreciative, and please feel free to PM me.

Thanks jman and I understand, if I was in your shoes I would do the same and I reported that post almost right after it was posted hoping you would not see it. But I know for me I have a greater understanding of my phone and like I have said before Thank you very much for your help. It's a shame to see you go but we understand.
Binny

doubt this will help, its all that htc tech support would throw up at me.
http://developer.htc.com/
contains hero and adp but nothing about eris.

jmanley69 said:
I don't think I'll be following these threads anymore. I try to help you guys, but in the end some of you just don't appreciate the help.
I don't claim to be an expert, and I never promised anybody that I could root their phone. I simply have information to share that I think has brought you guys to a greater understanding of your phones and the Android system. Most of you are thankful, but I really don't need to be attacked personally in these threads that don't even have anything to do with my phone.
I'd like to thank the moderator for locking down the other forum, I'd also like to thank whichever moderator deleted the message that was quite insulting to me.... I only happened to see it because it came into my email. Yes, I subscribed to the thread via email to try to keep up with you guys and offer any help I could as quickly as I could.
I'm sorry guys, I wish you luck, but I just don't need to be berated in open forum like that for trying to help the Eris owners out, so I won't be keeping up with your rooting efforts.
There are a couple of you that have been very appreciative, and please feel free to PM me.
Click to expand...
Click to collapse
Thanks for sticking through with us. You've been extremely helpful since day one, and I would like to say thanks and basically say what Binny said above.
I haven't had a lot of time to follow the thread, but, I too, am happy that it was locked. Hopefully the Eris owners can regroup in a day or so after we all chill out. Sigh. Fingers are still crossed for root.

Has anyone been able to actually BOOT any of the images extracted from the rom.zip via fastboot in oem-78 mode? If so, and you could post how, I might have access to an image with root access. I've tried repeated times to perform "fastboot boot recovery.img" but it sends it and then sticks on "booting..." I have moved forward with the RUU at this point, but the device never actually boots into the img.
Unfortunately, I cannot not upload the image due to my job.

Also, if anyone can help with goldcard downgrading, I might be able to downgrade to an old version with root access. My downgrade continues to fail due to the bootloader version being too high. I created the goldcard per the appropriate thread and it appeared to work as the Cell South thread indicated, but still no dice on the downgrade.

If your gold card is made right it should work.... are you putting the .zip on you gold card and renameing it PB00IMG.zip?

binny1007 said:
If your gold card is made right it should work.... are you putting the .zip on you gold card and renameing it PB00IMG.zip?
Click to expand...
Click to collapse
Yes, but it still fails with error 43, I believe. "Main version check"

Did you run the simlock option in the bootloader, and it passed

binny1007 said:
Did you run the simlock option in the bootloader, and it passed
Click to expand...
Click to collapse
Yes. Perhaps goldcard doesn't work on this device like it's supposed to.

<HOW TO> Easy Guide to Using Odin/Unbricking Your Phone

I have noticed that while there are many guides to do this, people still ask the question in threads, so I'll simplify it here. It is meant as an Odin helper.
Make sure you have downloaded the files you need (firmware and odin) from the bottom of this post. I have only included Odin v3.1 and the needed file for UCJF6 restore, cause the jh3 and other stuff is too big to upload directly. This Odin works with all firmwares. Just d/l the desired firmware and use this odin to flash. Just unzip both my files and there you go.
1 - PHONE MUST BE POWERED OFF (not plugged in and pull the battery for 5 seconds if you have to).
2 - Open Odin and choose the files you need. Do everything EXCEPT press start.
3 - HOLD BOTH volume buttons and, while holding them, count to 2 then plug in usb and wait 2-4 more seconds. Phone will enter download mode and Odin will recognize it on a COM.
4 - Press start in Odin. When it completes and your phone reboots, close Odin.
5 - BE PATIENT!!! Your phone may now appear to stick on one of the boot screens or a blackscreen, but it is really doing stuff. Wait 5-10 minutes before you impatient people decide it didnt work.
I can only say this: THIS METHOD HAS NEVER FAILED FOR ME
I hope this helps someone, as someone was kind enough to do for me.....
Enjoy, and happy modding! =)

You should also add how to do it if someone flashes a I9000 rom
Sent from my phone so excuse the spelling errors

You guys should really read the stickies...
http://forum.xda-developers.com/showthread.php?t=731989

tytdfn said:
You should also add how to do it if someone flashes a I9000 rom
Sent from my phone so excuse the spelling errors
Click to expand...
Click to collapse
Same procedure.
designgears said:
You guys should really read the stickies...
http://forum.xda-developers.com/showthread.php?t=731989
Click to expand...
Click to collapse
I have read almost every sticky here, and I swear of the 15-20 threads I am subscribed to I see AT LEAST 3 a day saying ".... I think my phone is bricked.....", so I figured I'd just put it right there on the 1st easy post in kind of a monkeys-could-do-it-like-this mode. I'm just trying to help those that DON'T read the really long threads. We know they should, but they don't.

techmik67 said:
I have read almost every sticky here, and I swear of the 15-20 threads I am subscribed to I see AT LEAST 3 a day saying ".... I think my phone is bricked.....", so I figured I'd just put it right there on the 1st easy post in kind of a monkeys-could-do-it-like-this mode. I'm just trying to help those that DON'T read the really long threads. We know they should, but they don't.
Click to expand...
Click to collapse
It's in the OP... if they cant find it in the thread with the tools how are they going to find it in some random thread?

designgears said:
It's in the OP... if they cant find it in the thread with the tools how are they going to find it in some random thread?
Click to expand...
Click to collapse
It seems like most people are messing up AFTER they have the necessary firmware files, which is why I didn't add any links. At least that's what I'm getting from the posts they make.
Honestly, and really I mean no offense here because I love your work AND advice, I see 1 flaw in your post, at least on my captivate which is all i can practice on. Copied from your post:
1. Download and install the correct drivers below (mac and linux don't need drivers)
2. Plug in your usb cable to your phone and computer
3. Open Odin
4. Enter Download Mode (see below)
5. Click Start
If I plug in BEFORE opening Odin, Odin does not pick up my phone. Doing it my way, holding both volume and then inserting usb while holding them with the phone powered off, has NEVER not worked for me. That's all I was trying to clarify for people. Sorry if I stepped on your toes.

Uploaded Odin and stock jf6 to the OP

Then what you can do is ask DG to include this as a method. There is no reason for you posting the same info which is already a sticky thread. This will eventually get lost while the sticky will stay at the top.

Alright i just wanted to say thank you to everyone. With your help i was finally able recover my phone using odin 1click. I have to say thay i was convinced that it was an unrecoverable brick and i had that sick feeling in my stomach but i read, read again, and re read the entrire odin 1click thread, and i discovered that i was booting into stock recov and not download. I think out of the 10 plus times i tried it i actually got it to go into download, by luck im afraid. Anyway the point of my long post is to thank you guys for being so smart lol u saved my phone. And me from getting an ulcer. Note Do Not download circle batt mod with black evo notification bar with the vibrant hybrid rom. from eugene. It Will brick your phone. At least it did mine. Now to figure out if i want to root again after dodging that bullet lol
Sent from my SAMSUNG-SGH-I897 using XDA App

Also i dont care where it gets posted to be honest. I am one of those monkies that probably should not root, but cant help myself trying ti learn all i can from you all lol
Sent from my SAMSUNG-SGH-I897 using XDA App

flashman2002 said:
Then what you can do is ask DG to include this as a method. There is no reason for you posting the same info which is already a sticky thread. This will eventually get lost while the sticky will stay at the top.
Click to expand...
Click to collapse
I didn't even think of that. You are right. Although I personally prefer my 3.1 odin to the 1 click, it should've been added to his, since my main point was/is the ease of getting into d/l mode if needed. I'll think before I start a new thread next time =)

flashman2002 said:
Then what you can do is ask DG to include this as a method. There is no reason for you posting the same info which is already a sticky thread. This will eventually get lost while the sticky will stay at the top.
Click to expand...
Click to collapse
It has been in there for about a month now... people don't read which is why that thread is 2093482094823 pages long
did you see how many time I had to post not to flash to an I9000, bolded at the top of the OP like 10 times

techmik67 said:
I didn't even think of that. You are right. Although I personally prefer my 3.1 odin to the 1 click, it should've been added to his, since my main point was/is the ease of getting into d/l mode if needed. I'll think before I start a new thread next time =)
Click to expand...
Click to collapse
No worries, it was just a suggestion and I feel that if this method works it would be best up there. Im glad this method worked for you as compared to the other methods.

[Q] Brand new to rooting - questions....

Hey guys... I am brand new to all of this... just got my samsung vibrant a couple of months ago and love it. I have since always wanted to root my phone, but am scared of doing so because I don't want to void my manufacturer's warranty on it (and i'm paying for an extended warranty). I was reading through the "guide - tips - tricks" post and found a LOT of good information. But it did not really answer my questions due to me being so new, so anyway, here they are:
1. Do I need to create a back-up of my system the way it is before I root? if so, how do i do it (in beginner's language w/ step by step instructions pls). I saw where I can down load the "ROM Manager App." But I don't even understand what "Flashing" the Rom means?
2. I didn't understand the post about returning your system back to a "factory OS" the way it was when you received your phone... (http://forum.xda-developers.com/showthread.php?t=728471 )In this post he explains supposedly how to do it, but I don't understand entering that stuff in a "terminal" on your computer... could someone explain in noob terms w/ step by step instructions?
Just to make sure... in theory, I can make a back up of my system before I root. Then I can root my phone. But if I ever want to "unroot" it, then I would have to follow the instructions in the link above, and then afterwards do a recovery of my nandroid backup to put me back to where I originally was? thanks guys

Rooting your phone will change nothing (meaning you lose nothing).
So, after you root, simply download Rom Manager, open it, click on flash recovery, then reboot into recovery (at this point you can make a backup of your phone).
Once you have root, you can also use titanium backup (in the market also) to backup all of your apps.
flash = install a rom *you do this in recovery, see above*

If you know nothing about this the best advice is to read the very first thread in this section. It walks you step by step from "hey I want to root" to "I'm rooted, Now what?" to "Hey I F'd up, can I fix this" and so on. And on the "Hey I f'd up" note apparently the Vibrant likes to brick, meaning it won't turn on and you'll think you broke it, so you need to be familiar with ODIN which you'll find out more about in the three threads I refer to. Also the first two threads in the Development section are also must reads. All of the answers are here. A lot of people here will be very helpful in giving guidance or pointing you to the answer your looking for but there are quite a few that will flame you for not searching.
You'll be much happier and more comfortable after reading these three threads. Good Luck.
Answer to question 1 can be found here. http://forum.xda-developers.com/showpost.php?p=7324731&postcount=1
Answer to question 2 can be found here. The terminal you speak of is ODIN. Kind of a fail safe if you will. http://forum.xda-developers.com/showthread.php?t=734475

A "I need to send this back for warranty repairs" backup isn't critical since you can just load up Odin and flash it back to stock with that. No need for you to be hyper critical on that.
With this phone, pretty much anything you can mess up can be fixed with Odin (short of flashing things that aren't meant for this phone).
While I wouldn't volunteer to be the first to flash an image, I wouldn't be too scared of it either.
Rooting your phone will add a few files (superuser, busybox) and otherwise leave your system intact. If something breaks later & you need to sent it back to TMO/Samsung, you'd just Odin it back to stock and give them a "blank slate" which is actually something you'd want to do anyways (you don't want them having access to your gmail for example...when I send a laptop back for repairs, I always image it back to stock as well).
I would suggest you read through the Vibrant Bible and just poke around. When you see something that shows/tells you how to do things like flash, follow along (load up the software and do as much as you can without actually doing anything [if that makes any sense]).
Never EVER flash anything that wasn't meant for your phone (a few people bricked their vibrants by accidentally flashing the SPLs from their G1s...how they make that mistake I don't know, but it's happened). Be careful, follow directions & you'll be good to go.
There are youtube videos showing how to use Odin and get back to stock (I believe the bible has links) and there are probably also youtube videos showing how to do other things as well.
For root, all you have to do is download "RyanZA's OCLF 2.0" from the market and click the root button. Follow its directions & you are good to go.
For many of us, that's not good enough. You'll want to then install ROM Manager and have it download the new Recovery.
From there, the world is open, find a ROM and flash away! I'm partial to Bionix, but have recently started to like the Axura froyo ROM as well.

Froyo Update Won't Install

I have the Samsung Fascinate and I recently rooted it to get all the wonderful benefits that come with rooting.
I downloaded the leaked Froyo update, renamed it "update.zip" and put it in my sd card folder in order to update.
I then turned off my phone and pushed the power button plus the volume up and down until I got to the boot screen. I kept getting an error saying it couldn't verify the package (or something along those lines) and then it sent me to a screen with the triangle, exclamation point and the little droid guy.
I also tried using Rom Manager but the same thing happened.
I hear you are supposed to use Odin, but I am running on a mac and Odin is a windows application.
Please help me, I'm desperate to get the Froyo update on my device.
Thanks in advance.

Yikes u didn't do any research at all did you?? U can't use Odin on Mac....and u need it. Do u even have cwm? Probably not since u didn't Odin. U need to Odin cwm...Make a backup...Odin eb01 modem...flash rom. Update.zip is not correct...u don't rename .zip roms...you flash them via cwm. Not trying to bash u....but you are way off...and getting help via forums will b tough.
You need to go to irc and be polite and find some help there. Someone should hopefully be able to help you...I will b on eventually.
sent from my vanilla voodoo fascinate

I did my research but if I'm not literate with how or what a CWM is or how to use it, that doesn't mean I didn't do my research.
But are you telling me I can't install the update without a windows computer?
I have access to one where I am but I would rather know all the steps before I get on someone else's computer and start trying to figure it out there.
I looked through all 50 or so pages of the Froyo leaked thread and I saw a few people who understood all these things, but if I don't understand and there isn't a tutorial it makes it harder for me to accomplish my goal.

Can your phone boot up?
Someone varify my directions.
This might work if u can get into download mode. U need to find all the links urself since I'm on tapatalk.
First off...find a pc. Without one you can't do anything. Put ur eb01 rom on sdcard for later. Instal the 32 bit or 64 bit Samsung drivers depending on ur pc. For many..its the 32 bit. Then get Odin. U will need to find a link to cwm...if I'm not mistaking there is one on like the 2nd or 3rd page in android development section...will say updated cwmq for dj05 or dl09 or something like that. Find directions of how to use Odin...but simply place the cwm.tar file in the pda section on Odin...then click start. When that's done...u should make a backup...however...u may not b able to boot up because of what u have already done. U may try odining the eb01 modem. Once u have that done...hold up down and power to get I to your new updated cwm. From there click instal zip from sdcard...and flash ur eb01 rom of choice....wipe wipe wipe...reboot system.
Again...this may not work since I'm not possitive what u already did to ur phone by not doing your research. Like I already said...be polite and head over to irc. .someone will have more time than I do to fix ur phone.
sent from my vanilla voodoo fascinate

You obviously didn't research. There is an eb01 walkthrough on fascinate development section...impossible to miss. If ur incompetent at following step by step directions u should not be Modding your phone. Seek help and knowledge before doing anything...u don't want a 600 dollar paper clip do you?
sent from my vanilla voodoo fascinate

kyfredrickson said:
You obviously didn't research. There is an eb01 walkthrough on fascinate development section...impossible to miss. If ur incompetent at following step by step directions u should not be Modding your phone. Seek help and knowledge before doing anything...u don't want a 600 dollar paper clip do you?
sent from my vanilla voodoo fascinate
Click to expand...
Click to collapse
How would you use it as a paper clip? A paper weight I see, but not a paper clip?!?!

TheFake said:
I did my research but if I'm not literate with how or what a CWM is or how to use it, that doesn't mean I didn't do my research.
But are you telling me I can't install the update without a windows computer?
I have access to one where I am but I would rather know all the steps before I get on someone else's computer and start trying to figure it out there.
I looked through all 50 or so pages of the Froyo leaked thread and I saw a few people who understood all these things, but if I don't understand and there isn't a tutorial it makes it harder for me to accomplish my goal.
Click to expand...
Click to collapse
Not to be a ****...but the first thing you learn when reading is how to flash the modem using ODIN...so, yeah....
Since you've f'd up the phone already. Download the restore to stock files and odin. Go to someone with a PC and follow the restore directions to the T. DO NOT FALTER.

kyfredrickson said:
You obviously didn't research. There is an eb01 walkthrough on fascinate development section...impossible to miss. If ur incompetent at following step by step directions u should not be Modding your phone. Seek help and knowledge before doing anything...u don't want a 600 dollar paper clip do you?
sent from my vanilla voodoo fascinate
Click to expand...
Click to collapse
No, but I also don't see the need for the disrespectful way you are treating someone looking for help.
Not everyone out there is as "smart" as you may be with modding but that's what this forum is for. Questions and answers, not smartass replies that don't help at all.
I appreciate the other posters response because at least he gave me information with no attitude. If you want to help someone, help them, don't demean them and offer a little advice.

jenisiz said:
Not to be a ****...but the first thing you learn when reading is how to flash the modem using ODIN...so, yeah....
Since you've f'd up the phone already. Download the restore to stock files and odin. Go to someone with a PC and follow the restore directions to the T. DO NOT FALTER.
Click to expand...
Click to collapse
The phone is working fine, if not better than before.

TheFake said:
The phone is working fine, if not better than before.
Click to expand...
Click to collapse
Honestly, you haven't done anything to your phone yet, so it shouldn't be running any differently than it was before.
There is a way to push CWM using ADB and Terminal on a Mac, but you would still need Odin to flash the modem, so might as well do everything that way. Download this Odin package from Android Central, and flash that using the PDA box in Odin. After that, you can flash a different 2.2 ROM or theme if you like

The only thing I am having trouble with is how to "flash" something.

TheFake said:
The only thing I am having trouble with is how to "flash" something.
Click to expand...
Click to collapse
Go to the Eb01 modem thread and read it. They will tell you how to "flash". You download the modem, plug in your phone, select PDA in ODIN and hit write or whatever...
It's as easy as reading and searching,
http://forum.xda-developers.com/showthread.php?t=948679
Not searching for things will get you flamed, ignored and banned (If not reading the rules). The reason I suggested you flash back to complete stock is because until you know what flashing is, difference between a ROM and a Radio...you are in dangerous territory of bricking your phone.

Guys, I'm also new to this flashing thing, but I've used Odin before and have read all the steps in the EB01 thread. My question is: can I install EB01 on top of stock, unmodded EA28 (which is the latest Eclair from Verizon) without wiping my data? All sets of instructions I've read include wiping, wiping, wiping... But since the new ROM is supposedly signed with the same Samsung/Verizon key as my current ROM, why shouldn't I be able to just install it on top, without wiping my data?
Or is it that because the guy who posted the ROM actually modified it, it's no longer signed with the Samsung or Verizon key?
I searched, but didn't find. I think the answer to this may be relevant to the original poster of this thread too, that's why I'm posting here.

thetodor said:
Guys, I'm also new to this flashing thing, but I've used Odin before and have read all the steps in the EB01 thread. My question is: can I install EB01 on top of stock, unmodded EA28 (which is the latest Eclair from Verizon) without wiping my data? All sets of instructions I've read include wiping, wiping, wiping... But since the new ROM is supposedly signed with the same Samsung/Verizon key as my current ROM, why shouldn't I be able to just install it on top, without wiping my data?
Or is it that because the guy who posted the ROM actually modified it, it's no longer signed with the Samsung or Verizon key?
I searched, but didn't find. I think the answer to this may be relevant to the original poster of this thread too, that's why I'm posting here.
Click to expand...
Click to collapse
It's always recommended to wipe. Those that don't are typically those who end up complaining about bad battery life, force close loops and utter suckageness...now flashing let's say super clean 2.0 to 2.2...that's fine bypassing the wipe, but imho that's the only exception.

thetodor said:
Guys, I'm also new to this flashing thing, but I've used Odin before and have read all the steps in the EB01 thread. My question is: can I install EB01 on top of stock, unmodded EA28 (which is the latest Eclair from Verizon) without wiping my data? All sets of instructions I've read include wiping, wiping, wiping... But since the new ROM is supposedly signed with the same Samsung/Verizon key as my current ROM, why shouldn't I be able to just install it on top, without wiping my data?
Or is it that because the guy who posted the ROM actually modified it, it's no longer signed with the Samsung or Verizon key?
I searched, but didn't find. I think the answer to this may be relevant to the original poster of this thread too, that's why I'm posting here.
Click to expand...
Click to collapse
You can install without wiping (saying from experience) as long as you dont mind problems later. I had plenty of force close problems and widget problems when I didnt wipe data.
Most ROM here are modified, to help protect the person who leaked it.

Interesting. Do we know the cause of those problems? How come no such problems exist when you update OTA with a similar official build?
I'm a developer and it seems weird to me that if you're starting with a stock ROM and upgrading to another stock ROM, apps will have issues. Or are the issues due to the fact that the newer ROM is still buggy (and that's probably why they haven't officially released it yet)?
Also, it doesn't hurt to try, right? And if I do get problems, THEN I can just do a simple wipe and start off clean. But if I don't have huge problems, I don't have to go through the trouble of restoring all my apps and settings, logging into everything again, etc.

it's not hard to restore apps/data, use titanium backup.
go ahead and try it without wiping, just do a full nandroid backup first. then if it sucks or you get funny errors you can revert really easily. I'd wipe with a major change like this, but if you're determined to try it there's really no big downside. just back up!
I ran EB01 over the weekend, didn't like a couple of things and was back up and running on DL09 in no time when I decided to switch back.

Its recommended to wipe but I've seen it a lot where u OK not wiping... u can try without and it u get bootloop just do a wipe. Like posted...titanium backup is ur bff when I mod.
Also about the post about me being rude.. I gave u the info u need...just telling you to research. U said u did, and I pointed out u didn't. If your not going to take the time to learn what ur doing...then expect help ASAP...expect ppl to b a bit rude. Ppl are welcome to help...but if u do something dumb without research...expect people to tell you.
Glad u got it working ok
sent from my vanilla voodoo fascinate

Just FYI everyone, I was able to to install Froyo without wiping and everything works fine. (except that my home screen shortcuts and maybe even some of my settings got reset... which was one of the things I was trying to avoid... but whatever.). The only issue I've run into so far is that Google Maps hangs for many seconds every once in a while. But I reset its internal cache and it's better now. All other apps are working fine.

umm "TheFake" is obviously a troll
nobody is that stupid, and his screen name gives it away

[Q] problem: n7 3g 32 jwr66y wont boot recovery

so i had jwr66v rooted with superSU twrp cmw 6.035 or whast ever.
now i have updated to ******y and i tried to flash a ROM in in CWM but it did nothing. at all. i rebooted into recovery only to get a droid on his back with a red ! coming out his belly. um problem here. i opened super Su and it said i need to reroot because i have installed 4.3
how can i reroot if i can't access recovery.
tried using toolkit to reroot (un root to stock first) but it froze now having this problem: post #455
http://forum.xda-developers.com/showthread.php?p=45162727&posted=1#post45162727

anyone?

Just flash recovery from cmd/terminal using fastboot.
Sent from my Nexus 7 using xda app-developers app

never used it. details would be nice.

Want details? There are stickies and tutorials for a reason. Lemme guess, you used a toolkit to root it the first time?
Sent from my Galaxy Nexus

sure I'll follow one of your tutorials. most of the time written as if we know every detail about android development jargon. oh and most tuts have missing details that usually means moderate technical knowledge people have to make assumptions when following those instructions. another issue I'm funding with following "stickies" is because there are so many different ways to update and so many different versions of root tools made by many different clever developers. sometimes they don't all work together. most of the time i will follow some developers half thrown together set of instructions only to have to redo the instructions 3 of 4 times because of the reasons all mentioned above.
short response to your reply. i followed a simple tutorial put up by a developer and most likely used a tool kit. now i have issues. rather then spend countless hours hunting for else who has had the same problem and actually posted it, i decided to ask the question so someone like yourself that enjoys spending hours each night balls deep in code can give me a simple link or basic set of instructions so i can have some relief.

Adb and fastboot. Those are the only tools you need to use.
If I had been in your shoes, I would have done a bit of googling on the term 'fastboot recovery'
I don't know why some people make this so hard. This is a developer site, if you don't want to learn, you shouldn't be here. Considering all this **** is literally spelled out for you with step by step documentation, it doesn't make any sense to click that 'new thread' button when this issue is so common.
Sent from my Galaxy Nexus

yeah googling more is what got me following half arse instructions and wading hours of my day. so which part of your detailed instructions would have led you ( if in my shoes) to Google fast boot recovery?
well I have now downloaded the latest tool kit so i can un root. then I'm going to hunt through countless posts and try find which is the best way to root and install cm10.x hopefully next time their is an update i won't have to reroot just to get all my little root access apps back.
ps this is the trouble shoot q&a section not the developers only section. hence why i posted here.

Welcome to xda-DEVELOPERS.com.
Maybe you missed that part. The domain name isn't xda-hold-lazy-asses-hand-and-make-their-device-cool.com
You are expected to read, comprehend, and take initiative to learn. Asking for a hand holding session is not the way.
If you would bother reading the stickies, you would see how easy it is to flash recovery. There is a tutorial in the damn stickies that literally walks you through the process.
Hint: every goddamn nexus gets rooted and recovery flash the same way regardless of what version of android you are on
I don't know how much more plain and simple we could be here.
Fastboot flash recovery name of recovery.IMG
I mean wtf how could you NOT find that?
Sent from my Galaxy Nexus
since you are being so lazy, and i have obviously had enough to drink tonight:
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?t=2150661
http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro
http://forum.xda-developers.com/showthread.php?t=2072732
http://forum.xda-developers.com/showthread.php?t=2175086
READ!
heres another hint. you need a recovery made SPECIFICALLY for your device 'tilapia'

so..... thanks for the pointless rant, after re read many guides and how tos, also wasting a saturday. still cant get the bootloader to update from version 4.13 (read post 1 again) not even using fastboot. Also read post #455 http://forum.xda-developers.com/showthread.php?p=45162727&posted=1#post45162727

aza510 said:
so..... thanks for the pointless rant, after re read many guides and how tos, also wasting a saturday. still cant get the bootloader to update from version 4.13 (read post 1 again) not even using fastboot. Also read post #455 http://forum.xda-developers.com/showthread.php?p=45162727&posted=1#post45162727
Click to expand...
Click to collapse
Use stock images for Android 4.2 and not 4.3 to avoid that error.
But i'm not sure why you want to flash anything else than recovery? Do you want to get it back to pure stock?