Related
Alright.
Seriously, whats the deal with the Rogers Dream and the normal Dream? I dont get the difference. Please explain some in detail.
The only thing I've been reading for a while is the DRE2100 or something compared to the normal thing.
seriously. What is rooting?
I have a Rogers Dream and I really want to know where to start playing around with it.
Its sad however that I have to look for threads with "Rogers" tagged on it.
previously, I had an HTC Kaiser, and I played around/flashed it a LOT. and I moved on to a Rogers Dream, I've had it for quite a while, just didn't know where to start.
Thanks
Theres a few minor differences between the 2. The main one is the frequency it runs on. But to get you started understanding everything this is what you need to look at.
http://forum.xda-developers.com/showthread.php?t=519523
Alright. I am so. tired of looking up stuff. I'm not going to do anything yet.
I barely get anything.
What is root for?
what is it used for?
I have used Ubuntu and Fedora a couple of times but, seriously, root was just a command really.
After I root. then what?
Also. I was wondering. can Rogers ever be converted into the DREAM100/DREAM110?. i dont know, just wondering. If that was possible, It would make things very simple for people like me.
I believe that dream100/110 are boards so they could never be converted.
Root is basicly in windows terms- the admin, getting root allows you su like the sudo command in linux. Having root allows you to flash custom roms, nandroid backup, themes, allow deeper hardware access, full privs to the kernel processes of the system, allowing apps to sd, allow you to wipe or activate gps from sms, dentonate nuclear warheads, so on and so on
Have I answer the ? Sufficently enough yet
Oh and root on linux is the same thing and not just a command
da pavinator said:
Alright. I am so. tired of looking up stuff. I'm not going to do anything yet.
I barely get anything.
What is root for?
what is it used for?
I have used Ubuntu and Fedora a couple of times but, seriously, root was just a command really.
After I root. then what?
Also. I was wondering. can Rogers ever be converted into the DREAM100/DREAM110?. i dont know, just wondering. If that was possible, It would make things very simple for people like me.
Click to expand...
Click to collapse
Since you're a lazy noob (at least to the G1), check the link in my sig that will answer most of your preliminary questions. Also look in the development forum's stickies, as there is A LOT of information for noobs about rooting (how to do it, and what it's good for, etc.) and flashing SPL, Recovery, and ROMs.
^That noob thread should be stickied. lol
So now, I am following instructions.
and I am a bit confused.
I am right now setting up my pc for rooting
http://developer.android.com/guide/developing/device.html
It says
Setting up a Device for Development said:
Step 1.) Declare your application as "debuggable" in your Android Manifest.
In Eclipse, you can do this from the Application tab when viewing the Manifest (on the right side, set Debuggable to true). Otherwise, in the AndroidManifest.xml file, add android:debuggable="true" to the <application> element.
Click to expand...
Click to collapse
What exactly does this mean?
Which application.
I have learned that AndroidManifest.xml is used for every application
I have the AndroidSDK on my computer, and I have also installed the usb driver
And when I searched in there, boy I got lots of results for "AndroidManifest.xml"
A little help?
Thanks a lot.
EDIT-
See, while here, I just had a simple question
http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
HyeProfile said:
Rooting the Rogers Dream
3.Install the proper drivers for your device, and make sure you can mount the microSD card and access it from your computer
Click to expand...
Click to collapse
Does this mean, being able to access the MicroSD card straight from you computer with an adapter/card reader? or though the phone?
I can access it from the phone btw
Follow the simple root link in my signature. Takes you to a thread specific to root on a Roger's dream along with a crowd of other canucks executing the same procedure.
A 1gig swap, way way overkill and completely useless to have anywhere near that much
Hey Y'all,
Anyone know what would cause my internal memory to get about 1mb fuller in what seems like each day. I turn my phone off completely at nite, I am non rooted with OS 2.1
I have even removed some apps to see if this stops. It hasn't Seems like something is writting to my memory with each new startup.
Is there an app, other than Astro or File Manager that will allow me to trim some fat off the internal memory. Also, where (what file) would that be stored in.
Sorry if I haven't explain'd this well but its got me baffled too.
When I updated the OS to 2.1, I was only using about 60mb of internal memory, then I restored all my apps and it came up to about 75mb used, now doing normal daily backups and just normal loads, I have used up 91mb. My backups are saved on the SD, not the internal.
If anyone has any ideas, I would be greatful. At this rate, I will run out of internal memory in about 2 months, lol
any reason why u dont wanna root??? it makes life with android so much easier..
anyway, ur probably buildin up a lot of cache.. if you was rooted you could just use cachemate found in the market and one click would get rid of your cache.. but sense your not, your gonna have to delete cache manually one app at a time..
menu>settings>applications>manage applications
let that load (it will take a min or two depending on how many apps u've got)
after it loads, click menu then sort by size..
start with the first app on the list and click on it.. once that opens you will see "Cache" and the amount (if theres any).. click on Clear Cache.. do that for each app (you will see that a lot of apps are at 0 already so just go onto the next one)
hope that helps..
Not really other than fear of screwing my phone up and not being able to put it back to 2.1 stock. I have been looking over the 2.1 root:
http://forum.xda-developers.com/showthread.php?t=694572
however and I never say never.
Thanks alot for the info about the cache(s). I will give it a try.
I really do appreicate your help.
UPDATE: I just did as you recommended, PERFECT!!
Went from 86mb used to 70mb used. 16mbs more free, I'll take it. Thanks again....
rdisanza said:
Not really other than fear of screwing my phone up and not being able to put it back to 2.1 stock. I have been looking over the 2.1 root:
http://forum.xda-developers.com/showthread.php?t=694572
however and I never say never.
Thanks alot for the info about the cache(s). I will give it a try.
I really do appreicate your help.
UPDATE: I just did as you recommended, PERFECT!!
Went from 86mb used to 70mb used. 16mbs more free, I'll take it. Thanks again....
Click to expand...
Click to collapse
glad it worked for u.. now just think about it, you could do that whole process with one click if you were rooted..
bk718 said:
glad it worked for u.. now just think about it, you could do that whole process with one click if you were rooted..
Click to expand...
Click to collapse
I know u r right, still thinking it over. My problem is really all the people who are rooted and all the problems they are having. This forum has 1000's of the" Help, I rooted and now this or that doesn't work" OR "Help, I just rooted and now my phone is Locked and I can't access anything" that scares me. My phone works perfectly, it tethers perfectly and its the old adage, If its not broken, lalalala....
Anyway, I haven't said NO.
BTW, Ic you're in Spartanburg, lol, used to date a gal in Easley and I am a grad of USC, GO *****!!
thanks man....
rdisanza said:
I know u r right, still thinking it over. My problem is really all the people who are rooted and all the problems they are having. This forum has 1000's of the" Help, I rooted and now this or that doesn't work" OR "Help, I just rooted and now my phone is Locked and I can't access anything" that scares me. My phone works perfectly, it tethers perfectly and its the old adage, If its not broken, lalalala....
Anyway, I haven't said NO.
BTW, Ic you're in Spartanburg, lol, used to date a gal in Easley and I am a grad of USC, GO *****!!
thanks man....
Click to expand...
Click to collapse
Well, just cause you root dosent mean you need a custom ROM. You can stay stock rooted and just get the rooted abilities. IE Wifi tethering, Cashe cleaning, a bunch of other stuff.
Most people had the fear of messing up there phone, however as in the previous post you can root and stay with the stock ROM. I have rooted several android phones, not just hero's, and have not once had a problem. I know that some have problems if they are not on Sprint and try flashing a ROM which might changed their profile info. And the great thing is that there have not been any issues with the 2.1 RUU. So if you rooted and had problems, which I doubt, you can always RUU back to 2.1
They're not having issues due to root...it's the custom roms they are loading. I've had mine rooted since last November, and I haven't had a problem with the phone because of root. Now, I have had problems with custom roms before...but the nice thing about root is that you can always reflash to a new custom rom...or you can go back to stock (or stick with stock if that's your preference).
All root does is gives you more control of your phone. What you do with that control is up to you.
rdisanza said:
I know u r right, still thinking it over. My problem is really all the people who are rooted and all the problems they are having. This forum has 1000's of the" Help, I rooted and now this or that doesn't work" OR "Help, I just rooted and now my phone is Locked and I can't access anything" that scares me. My phone works perfectly, it tethers perfectly and its the old adage, If its not broken, lalalala....
Anyway, I haven't said NO.
BTW, Ic you're in Spartanburg, lol, used to date a gal in Easley and I am a grad of USC, GO *****!!
thanks man....
Click to expand...
Click to collapse
tkirton said:
They're not having issues due to root...it's the custom roms they are loading. I've had mine rooted since last November, and I haven't had a problem with the phone because of root. Now, I have had problems with custom roms before...but the nice thing about root is that you can always reflash to a new custom rom...or you can go back to stock (or stick with stock if that's your preference).
All root does is gives you more control of your phone. What you do with that control is up to you.
Click to expand...
Click to collapse
Basically, this.
Well thx folks, so if I do this root proceedure:
http://forum.xda-developers.com/showthread.php?t=694572
, I will have SuperUser perms and tipically NO problems as long as I stick with the stock ROM? Another question, Tethering is very important to me. I currently use PdaNet, will it still work after ROOT plus give me WiFi Tethering too?
Thanks again, this just got more interesting.
Pretty much wifi teather does have its limits but its still pretty wicked
Thx again folks, Ima gonna do it. Seems fool proof and the positives outweigh the negatives. I can also revert to pure stock if all else fails, so, WHY NOT?
Regards,
Soon to be ROOTED!!
OK, trying to ROOT, getting this while following instructions exactly:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Rich>cd C:\android-sdk-windows\toolsadb devices
The system cannot find the path specified.
C:\Users\Rich>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9B3HF00237 device
C:\android-sdk-windows\tools>adb push unrevoded /sdcard
cannot stat 'unrevoded': No such file or directory
C:\android-sdk-windows\tools>
Revoked. Spelling mistake. Check again.
Sent from my HERO200 using XDA App
sekarpdkt said:
Revoked. Spelling mistake. Check again.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Retry with spelling corrected, and btw, this is copy & paste:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Rich>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9B3HF00237 device
C:\android-sdk-windows\tools>adb push unrevoked /sdcard
cannot stat 'unrevoked': No such file or directory
C:\android-sdk-windows\tools>
humm!
Following the instructons exactly..
what the heck is unrevoked? looks like its missing an extension too. eg; .img
Sent from my Hero CDMA using the XDA mobile application powered by Tapatalk
go here:
http://forum.xda-developers.com/showthread.php?t=694572
SEE Step 9:3
I am following these instructions but I agree, something is missing but then again, it then again, if something really is missing, I can't be the 1st to find it.
I tried this proceedure 4 times and gave up, then installed the normal 2.1.
PITS
Did you get the hero-root.zip? If so, did you uncompress it in the tools folder?
rdisanza said:
go here:
http://forum.xda-developers.com/showthread.php?t=694572
SEE Step 9:3
I am following these instructions but I agree, something is missing but then again, it then again, if something really is missing, I can't be the 1st to find it.
I tried this proceedure 4 times and gave up, then installed the normal 2.1.
PITS
Click to expand...
Click to collapse
Yes I did, I decompressed the 3 files within hero-root.zip to the C:\android-sdk-windows\tools folder.
The funny thing however is in the
C:\android-sdk-windows
folder, there is nothing, no files, only the TOOLS subfolder and in the TOOLS folder are the three following files:
adb.exe
AdbWinApi.dll
AdbWinsbApi.dll
It this correct?
So for the past year I've had a grand ol' time playing with assorted ROMs and now I've run into a problem I can't fix. First, I'm 95% certain the microUSB on the bottom of my N1 is shot. It will still charge the phone, but cannot connect via Windows/ADB/Superboot or anything. I've tried different cables, different computers, different USB ports and different OSs... still cannot get any computer to recognize device. I'm not paying $200 for HTC to fix this (broken USB ports are not covered)... so here's where I stand:
I installed the Clockwork RomManager to try to DL and install ROMs more easily. It didn't work, it was unable to install anything, and it screwed up my original Amon_RA recovery. So then both means of flashing new ROMs were totally dead. Reluctantly, with no other choice (that I knew of) I reverted back to stock recovery and stock FRG83.
With the Stock ROM I lost Root privileges. And with the stock recovery program (the one with blue writing) I am entirely unable to flash ANY of the common rooted ROMs. I renamed a whole bunch (Cyanogen, Enomther, Rodriguez etc.) to the correct update.zip, but the stock recovery image refuses to flash any of them. It always fails on the Verification stage.
So I can't flash a rooted ROM via the stock recovery program, and I can't use ADB/Superboot/Fastboot to root the device via USB. How can I regain root? Are there any rooted ROMs that are certain to work with the stock recovery image program? Any other ways?
Since all my data is backed up with Titanium, I really need Root to get my life back! Thanks for any ideas!
If you're still on FRG83 (and not FRG83D), you may still be able to root on-device using Visionary, but I'm not sure which version of Visionary to counsel you to try.
If your USB port is broken, how are you charging it?
Which HBOOT version do you have? If none of the on-device methods are working, could you try the PASSIMG for FRF91 and roll back? Universal AndRoot and z4root should work on that build. From there if you want to re-upgrade and keep root, you'll need to take the pre-rooted update.zip format for custom recovery rather than the OTA.
Doesn't sound like it's broken... Weird. And you're 100% sure you have the drivers and everything installed on the computer?
Hi cmstlistand thanks for your advice.
I am now on FRG83D. I looked for Visionary in the market but didn't see it there.
The strange thing about the broken USB is that I'm still able to charge through it without any problems. This is why I'm only 95% sure it's broken... seems very odd that the wires for charging would still be making contact while the others wouldn't. (Please see in my OP all the things I've tried to get it to connect to a computer... certainly open to new ideas if I've missed any.)
I just checked and my HBOOT is version 0.35.0017. I'd be willing to "try the PASSIMG for FRF91" as you suggest. Would I just find the stock FRF91 and rename it PASSIMG and hold down volume down while powering on? Does that sound like my best option?
Thanks again!
KAwAtA said:
Doesn't sound like it's broken... Weird. And you're 100% sure you have the drivers and everything installed on the computer?
Click to expand...
Click to collapse
Sadly, no. I'd say I'm 95% certain...
The thing is I've tried to connect on my desktop PC with W7 64-bit, my XP laptop and another PC with Linux (Ubuntu and Kubuntu) all to no avail.
Here's what I've done on my main PC (Win7 64bit) to try and connect the N1 (which, btw, connected just fine a few months ago, albeit to a different W7 install). The problem might still be in here, and not in the hardware, so I'm open to any ideas.
1. Whenever I connect I get the "USB Device not Recognized" alert in the taskbar.Clicking on that alert yields no actionable information.
2. The Device Manager shows the exclamation mark by unidentified USB device. Uninstalling, Disabling and attempting to manually update the driver from within the Device Manager all have no effect. Windows says I already have the most current drivers.
3. Tried the USBDeview program. It's supposed to "show all hidden and previously installed usb drivers on your computer." It shows nothing related to HTC or Nexus or Google.
4. I tried manually installing the USB drivers from here.
5. I installed & uninstalled & reinstalled the Android SDK thinking that might fix the USB issue. It didn't.
6. Tried running W7 in Safe Mode and without firewall/anti-virus.
7. Tried three different cables on all of the USB ports on my PC.
All throughout... it's always "USB Device not Recognized"
There should be some PASSIMG files you can try at Shipped ROMs. Usually it's a ZIP inside of another ZIP, so you have to extract the inner file first and rename it PASSIMG.zip.
Visionary is not on the Market anymore, nor are most other rooting apps. You'll have to search for them on the web. So far I don't know of any apps that root FRG83D on-device.
Install pdanet on your pc, and try again. It's an easy way to update the drivers.
The sdk has changed with the gingerbread release, and you have to reload the drivers, etc...
Sent from my Nexus One using XDA App
danger-rat said:
Install pdanet on your pc, and try again. It's an easy way to update the drivers.
The sdk has changed with the gingerbread release, and you have to reload the drivers, etc...
Click to expand...
Click to collapse
I'd actually tried that before and forgot to mention it. So I just tried it again and no dice. At the point where you plug in your phone, I get the Device Not Recognized immediately in the taskbar. In Device Manager, there is no "Android Devices" category.
cmstlist said:
There should be some PASSIMG files you can try at Shipped ROMs. Usually it's a ZIP inside of another ZIP, so you have to extract the inner file first and rename it PASSIMG.zip.
Visionary is not on the Market anymore, nor are most other rooting apps. You'll have to search for them on the web. So far I don't know of any apps that root FRG83D on-device.
Click to expand...
Click to collapse
I tried the FRF81 from that site and yes it was a zip inside a zip. Renamed it to PASSIMG... but the installation failed at the verification stage.
Thanks for everyone's help so far. I'm totally at a loss with this thing. I don't even know if this is a software or hardware issue. All I know is that I'm dangerously close to driving a railroad spike through the screen.
Any other suggestions greatly appreciated!
JohnHenrySDM said:
I'd actually tried that before and forgot to mention it. So I just tried it again and no dice. At the point where you plug in your phone, I get the Device Not Recognized immediately in the taskbar. In Device Manager, there is no "Android Devices" category.
I tried the FRF81 from that site and yes it was a zip inside a zip. Renamed it to PASSIMG... but the installation failed at the verification stage.
Thanks for everyone's help so far. I'm totally at a loss with this thing. I don't even know if this is a software or hardware issue. All I know is that I'm dangerously close to driving a railroad spike through the screen.
Any other suggestions greatly appreciated!
Click to expand...
Click to collapse
If a passimg isn't working it's possible your on FRG33 or something else that doesn't like them. Just use visionary to root like suggested it's been taken down from the market so you'll have to find it here
Ozymandias88 said:
If a passimg isn't working it's possible your on FRG33 or something else that doesn't like them. Just use visionary to root like suggested it's been taken down from the market so you'll have to find it here
Click to expand...
Click to collapse
Visionary does not work on FRG83D, which is what the OP has. Thus my suggestion to try downgrading.
If you're on the newer HBOOT, try the KT_KR release of FRF91 (rootable with Universal Androot or z4root), or try FRG33 (rootable with Visionary). Both are available as PASSIMG files.
That's correct I have FRG83D so Visionary will not work.
Thanks for the suggestions Cmstlist.
Any advice on where to find the KT_KR release of FRF91? I'm searching as we speak, but not finding much...
EDIT: Never mind, just found it here Link. Downloading it now, I'll report back soon.
Thanks Again.
Ok I just DLd KT_KR release of FRF91, renamed it to PASSIMG, copied to root of SD card, rebooted holding volume down. Phone finds and starts to load PASSIMG but then I get the "Main Version is Older! Update fail!" error.
I'll look for and try the FRG33 PASSIMG next, but I'm pretty certain I'll get the same error.
Ok just tried FRG33 I found HERE.
It didn't work, but it didn't work in a different way.
HBOOT finds PASSIMG.zip and loads it (blue bar at top right). After loading it says (Checking... PASSIMG.zip) Then it stays there for a few seconds, and then just jumps back to the original HBOOT screen. There's no error message.
I guess where I'm confused now is that I currently have the newest version (FRG83D) installed. So won't all other PASSIMG files be older and therefore result in one of the above errors?
EDIT: Just thought of something else. For both of the above files I needed to rename them myself to PASSIMG. They were originally named Passion_Google_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip and PASSIMG_Passion_KT_KR_2.15.1010.2_FRF91_release_signed.zip. I was correct in needing to rename them, right? Just want to make sure...
Yes you'd be correct to extract and rename them.
Usually the main version error relates to HBOOT and not the OS version itself, which is why I was hoping FRG33 would work for you.
Sent from my Nexus One using XDA App
I see. Thanks for the info.
Still looking for any new ideas to try if anyone has them.
Is there any way I could just revert the phone back to a much earlier build, like ERExx ? Or any way to erase everything, but retain the unlocked state, and then load up a differrent build, one that's software rootable?
Or is it likely that I'm just grasping at straws here?
Rolling back to a much older built requires a modification to the misc partition to trick the HBOOT check... which you can only accomplish either with root, or over USB via fastboot.
Rooting FRG83D requires adb USB over USB. UNLESS... can you adapt the rageagainstthecage instructions to run them by typing or pasting meticulously into Terminal Emulator? Maybe that could root it.
Sent from my Nexus One using XDA App
Hmmm, good idea but I don't think anything involving a terminal emulator is likely to work, at least not with my skill set. I've already tried one other method that relied on terminal, and it failed because I couldn't get SU. Without root, I couldn't get super user permissions, without those, terminal was useless.
I just got off the phone with the insurance company (Asurion). I filed the claim and am now waiting to hear back what my options will be. The guy thought that since the N1 is no longer available, I'd be given a choice between a G2, a Vibrant or a Mytouch (not sure if 3g or4g model). And if I don't want any of those, then I'll just keep my N1.
So, the clock is ticking down! ANY ideas whatsoever are greatly appreciated! I'd much rather keep my N1...
JohnHenrySDM said:
Hmmm, good idea but I don't think anything involving a terminal emulator is likely to work, at least not with my skill set. I've already tried one other method that relied on terminal, and it failed because I couldn't get SU. Without root, I couldn't get super user permissions, without those, terminal was useless.
I just got off the phone with the insurance company (Asurion). I filed the claim and am now waiting to hear back what my options will be. The guy thought that since the N1 is no longer available, I'd be given a choice between a G2, a Vibrant or a Mytouch (not sure if 3g or4g model). And if I don't want any of those, then I'll just keep my N1.
So, the clock is ticking down! ANY ideas whatsoever are greatly appreciated! I'd much rather keep my N1...
Click to expand...
Click to collapse
Oops I pressed thanks instead of quote =)
What I was suggesting is that you try looking at the manual instructions for rageagainstthecage and adapting them to Terminal Emulator. Those instructions don't require you to already have root - they *give* you root. But now that I read them over, it seems there's also some adb start/stop/etc commands that I'm not sure you can replicate in Terminal emulator. Back to the drawing board...
If Asurion is willing to give you an MT4G or G2, I say go for it.
Just on a total whim... try booting up your phone without the SD card, or with a different one... does it still fail to recognize over USB?
cmstlist said:
Just on a total whim... try booting up your phone without the SD card, or with a different one... does it still fail to recognize over USB?
Click to expand...
Click to collapse
Ha ha you had me all excited there... first chance to try something new! Alas, no luck. Used the original SD card and tried again without one; still got the exact same Device Not Recognized.
I talked to another rep and they alluded that the MT4G was not going to be an option, but that the 3G probably would. The3G seems inferior, though.
You think the G2 would be a fair trade? How about the HD2 or the Vibrant? Any others come to mind?
Since I'll need to pay a $130 deductible (not to mention the $5 I've been spending every month for the last year) I want to make very, very certain that my new phone is not inferior to my beloved N1.
Thanks again; you've been very generous with the ideas!
Ok, so I promise I've tried to search for a solution, but I really don't even know where to start. Please let me apologize if this has been discussed at exhaustion, but the guys I've asked so far have not seen this issue. Perhaps some of you have.
I'm going to list EVERYTHING I can think of that I've done. Please tell me what I've done wrong.
1. After picking up my NC last night, I tried running the Non-Root SDcard method of running Froyo to try it out. I tried running Rom Manager but wasn't able to do much. I tried Flashing CWM and feel that might have been a mistake. Hopefully, someone can reassure me that was not a problem.
2. I was unable to get GApps (Market most importantly) to show.
2a. After Flashing CWM and removing the SD card, I found that if I tried to force the 1.1.0 update, it would error out and put me into Recovery. That was something I assumed would not be possible, since I was of the understanding that the Non-root SDcard method was restricted solely to the SD card and didn't actually touch the Onboard memory.
3. Assuming the SDcard method might be limited to not having Market access and was more of a pre-root preview. I moved on to actually Root my NC. I did the whole, SD-image method and let my NC auto-reboot. The method I followed didn't mention anything about skipping the Google Account step. So, I tried that with some difficulty and had to back out. I never tried the whole Youtube account sync. I accessed the Market, but none of my downloads will actually go through. Tried multiple reboots, but no luck.
4. I tried to root again to see if something went awry. This time, I didn't have to go through the Android Setup steps??? But, I went ahead and logged into YouTube. Then, I went to Gmail Accounts>Account Setting, but each time it just causes my NC to reboot. Market still doesn't actually download anything.
I know it probably seems like I'm trying to many things, but I'm trying to discover the source of the problem, but behind each corner is another problem. I can't think of anything I'm doing wrong. I'm becoming very agitated. This was supposed to be a simple process, but it is not at all right now.
5. Now, as a last ditch effort, I tried to UnRoot my phone with the 8-Boot-Interruptions method. Problem is, instead of restoring the device to stock, it puts me back into CWM recovery.
Is it possible that Flashing CWM has irreversibly imprinted itself on my NC and I can not get past it to actually move forward with the Market and such? Is there any way to reverse the Flashing of CWM?
Thanks a ton in advance.
My guess is CWM writes to the system folder no matter if it has booted from SDCard or not...
Try this:
http://forum.xda-developers.com/showthread.php?t=931720
I believe that is the correct set of instructions, if not, my apologies.
migrax
For reference, I'm running B&N 1.0.1 and used auto-nooter-2.12.25.
It sounds like you might want to navigate overt to the development forum and do a bit of reading. I'm unsure why you flashed CWM onto your nook, but everything is easily fixable. It really depends on what state you want your nook to be in when it's all said and done. There's a thread in the development forum about restoring back to stock, doing so will remove cwm and let you start over. This is probably the best way to go as the current state of yur nook is questionable. Once you have stock working your best bet for the most functionality is rooting, and the easiest way to do that is autonooter. Definitely read the threads more than once before attempting any of this so you will know what to expect before it happens.
migrax said:
My guess is CWM writes to the system folder no matter if it has booted from SDCard or not...
Try this:
http://forum.xda-developers.com/showthread.php?t=931720
I believe that is the correct set of instructions, if not, my apologies.
migrax
Click to expand...
Click to collapse
Just read through that link. Looks very promising. Dont think I'll have a chance to do it tonight, but I will report back ASAP. I'm hoping to get back to stock and then go straight through the root process as intended. I really feel that my unintentional CWM Flashing experience is the root of my frustration.
I'm hopeful that this will be the end of it.
Thanks again.
Thanks a BUNCH!!! It all worked out. Getting the .img out of the .tar.gz was the most difficult, but once I figured out how to use 7-zip, all was well.
I'm now rooted and have full Market/Gmail access. I'm a very happy boy
I was messing around and forgot to back up my vending.apk before i deleted it. Now i haven't been able to get any market apks i find to work so i am without a market.
Anyone know how i can get this back?
I've tried using some vending.apks i've download like an ones from this thread:
androidtablets.*net*/forum/nook-color-technical/8512-how-setup-new-market-fix-lack-apps-showing-portrait-mode (remove astriks around .net)
But they either get an error through ADB while installing or when it installs and i try to open it up it opens and says "Loading" and then immediatly closes.
I installation errors and certificate errors when trying to install through ADB. Can't find anything on how to get around it.
Bump +
I'm not really sure why you would delete it in the first place *facepalm*. However, the only solution I can seem to find would be to just wipe everything back to stock, re-root it and go about the normal route. Search around for the process to go back to stock and whatnot.
I facepalmed already. It was definitely a stupid point in my career. I hope thats not what i have to do, but i guess i could back up everything i have, go to stock, re-install, then put everything back on.
honestly that's probably the only route at this point. Market is really weird on the nook color. I'd post the link to the requisite threads that talk about similar issues but my post count isn't high enough yet. From what I've gone through, going back to stock, re-rooting, and the whole shebang should only take about an hour. Good luck!
Well i might just go for Honeycomb then. Is honeycomb fast when on internal?
If all you want is the market, you can download the newest market APK from my webserver. The link is:
http://www.r00tyou.com/android/tools/Vending(new).apk
To push it to the device simple connect the device to your computer using ADB and type the following in the console:
adb devices
adb install \path\to\the\downloaded\apk.apk
Click to expand...
Click to collapse
Wait for it to successfully transfer over and install.
The viola, you have the newest market APK.
ALSO, if you are wanting a pretty stable ROM I would use the nookie froyo. However, if you are wanting to do some experimentation I suggest loading up the latest CM7 nightly. I am currently running CM7 Nightly 17 with Bluetooth.