Related
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!
I'm been searching the Nexus One Q&A section for an answer to my problems, but I couldn't find a solution. I'm running a stock version of 2.3.3 on my phone. It's never been rooted, and I have never rooted a device as well. I'm entirely new to this and have no idea what I'm doing. My device has no warranty but I'm still concerned about it. Again, I have no experience at all.
Also, I don't know if I would want to unlock the bootloader as I could lose everything. If there is a way to retain everything reliably (I don't know if those back-up applications are the most effective) that would be convenient.
So, can anyone help me root my virgin Nexus One?
Thanks for your time,
Tread Fox
Mybackup pro backs up apps and data. After you root you can use titanium backup. Also smsbackup and restore for your SMS :]
Alright, that's re-assuring. But what about actually rooting the phone?
Hmm I can't help with rooting because I have an Evo, just sharing some backup knowledge :/
You can use this threads wiki for the N1 and the stickies here:
http://www.nexusoneforum.net/forum/nexus-one-development-hacking/
You need to read several guides until you get a good idea of what you are doing and why.
Use the apps mentioned above to back up your phone info, once rooted you can do a complete and immediate phone backup of everything, like a full image pc backup.
If you do the one-click method, make sure it is for you OS, you will be limited in some things you can do, like fastboot commands and will be unrooted if you dl OTA's.
Read, Read, Read!!!
Before you flash a rom read the op page carefully and the last 20 pages for tips, info, issues etc.
Ken
This works for 2.3.3?
EDIT: So my only options are to unlock the bootloader or roll back? Which do you recommend?
You probably saw this in XDA wiki for N1:
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials#Root
I would unlock, more options as you get more into flashing and you can't be unrooted by Google OTA's.
This is good guide for the S, but you can glean steps and maybe better understanding for the process. At the bottom in related posts is a root guide. I like the steps, but things like the fastboot and superuser may not be for the N1. However you can find them online. Just an easy to understand guide.
http://jaxov.com/2011/02/install-android-2-3-3-gingerbread-on-nexus-one-manually/
TreadFox said:
This works for 2.3.3?
EDIT: So my only options are to unlock the bootloader or roll back? Which do you recommend?
Click to expand...
Click to collapse
Sorry man, just got your message (phone died on me, and I've been playing with my other toys anyway...)
Yes, your options are to unlock the bootloader or roll back.
Both options will lose all date, so you need to backup either way.
My preference is to unlock the bootloader, but I can understand why people may not want to. Unlocking the bootloader can effect any warranty that's remaining on the phone (the phone has a 1 year warranty, no matter who owns it).
Thanks for all your help guys. Does anyone have a specific guide for rolling back? I don't need or want a custom rom, just setcpu...
Read my signature, execute PASSIMG method with FRG33. if it doesn't work (and sometimes it doesn't) - you're out of luck.
TreadFox said:
Thanks for all your help guys. Does anyone have a specific guide for rolling back? I don't need or want a custom rom, just setcpu...
Click to expand...
Click to collapse
This is how to go back to FRG33: http://forum.xda-developers.com/showpost.php?p=11745519&postcount=21
But if I were you, I would just unlock your bootloader. Makes life easier.
I'll unlock the bootloader. I saw a guide on the nexusoneforums on how to do this. But it's about a year old. Is there anything that's changed?
I'm sorry I'm being indecisive, I'm trying to take suggestions from anybody!
TreadFox said:
I'll unlock the bootloader. I saw a guide on the nexusoneforums on how to do this. But it's about a year old. Is there anything that's changed?
I'm sorry I'm being indecisive, I'm trying to take suggestions from anybody!
Click to expand...
Click to collapse
No, nothing has changed. You need to have the Android SDK set up properly. Then just boot into the bootloader by holding down the trackball while pushing the power button. Then open a command prompt in the directory where the fastboot.exe file is (probably C:\Program Files\Android\android-sdk-windows\tools) then just type: fastboot oem unlock
Follow this to set up the, it's easier (just the first post):
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA Premium App
I don't know what I'm doing. This is confusing. When I hook up the phone to the pc it says its found new hardware. I'm running XP. What do I do? I think I'm going over my head with this. Also, how do I make sure mybackup will work? I don't want to lose my stuff!
TreadFox said:
I don't know what I'm doing. This is confusing. When I hook up the phone to the pc it says its found new hardware. I'm running XP. What do I do? I think I'm going over my head with this. Also, how do I make sure mybackup will work? I don't want to lose my stuff!
Click to expand...
Click to collapse
If you feel like you are in over your head, you probably are, and have not done enough reading. I just looked at danger-rat's post in the link he provided, and it seems quite straight forward, no? He even tells you how to install the drivers. "Step #3" under "To install the drivers" in the first post TELLS you that windows will detect new hardware and will ask you to install a driver. What seems to be the problem?
I did, and nothing happened. At all. I asked for it to download files from usb driver. Nothing happened at all. Is it something I'm doing wrong?
I have the SDK file on my desktop, I have all of the files inside that are needed. When the computer asks me to download the drivers, I re-direct to the usb driver folder located in the SDK which is located on my desktop. The computer claimed installation was successful, but nothing happened. When I try clicking the fastboot.exe in the tools file, it immediately forcecloses. Is it my pc? Is it the file? Is it the phone? I did read the material and so far nothing has helped.
TreadFox said:
I did, and nothing happened. At all. I asked for it to download files from usb driver. Nothing happened at all. Is it something I'm doing wrong?
I have the SDK file on my desktop, I have all of the files inside that are needed. When the computer asks me to download the drivers, I re-direct to the usb driver folder located in the SDK which is located on my desktop. The computer claimed installation was successful, but nothing happened. When I try clicking the fastboot.exe in the tools file, it immediately forcecloses. Is it my pc? Is it the file? Is it the phone? I did read the material and so far nothing has helped.
Click to expand...
Click to collapse
Well, after you have installed the driver that the computer asked you to install. That's just the driver needed to sync your file and stuff on your sd card. The other driver and adb setup is needed to actually access your phone.
So I asked for it to install the wrong files? What files do I install? Because from that guide it said point to usb driver. I'm only following the guide like you all asked, and nothing happened.
You don't launch fastboot by clicking on it windows.
Sent from my Nexus One using XDA App
I've been trying to install Serendipity to my Captivate. I've been working on this for several hours. Having problem after problem because i came from Windows Mobile ROMS.
I find it hard to find how to instructions for this. diggin in the web to learn about clockworkmod and 2e recovery and Odin (which I still don't konw how to do). Documentation is awful!
Anyway, for well over an hour now my phone has displayed nothing but a Droid digging a hole. Under that it says "Downloading... Do not turn off Target!!!"
What do I do? I think it's stuck. I have read many good thing about Serendipity and wanted to try it. Now I just hope I haven't bricked my phone.
I really love Android, but flashing custom roms to WM phones is much easier and better documented.
try again.
if you don't get a blue bar moving in about 60-90 seconds, chances are it hasn't done ****.
My only suggestion is to follow the serendipity website instructions. I found that if you use odin for master clear then you need to do it while the phone is on with usb debugging.enabled.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
This belongs in Q&A. Download designears one click odin back to stock. Open Odin up. Runs as admin. Put phone in download and plug in usb. Hit start. Make sure u see yellow com port in Odin. Good luck. Hope that helps
Sent from my SAMSUNG-SGH-I897 using XDA App
tweakedlogic said:
I've been trying to install Serendipity to my Captivate. I've been working on this for several hours. Having problem after problem because i came from Windows Mobile ROMS.
I find it hard to find how to instructions for this. diggin in the web to learn about clockworkmod and 2e recovery and Odin (which I still don't konw how to do). Documentation is awful!
Anyway, for well over an hour now my phone has displayed nothing but a Droid digging a hole. Under that it says "Downloading... Do not turn off Target!!!"
What do I do? I think it's stuck. I have read many good thing about Serendipity and wanted to try it. Now I just hope I haven't bricked my phone.
I really love Android, but flashing custom roms to WM phones is much easier and better documented.
Click to expand...
Click to collapse
What I've done when this happened (only happened once), I just unplugged the phone (stupid idea generally), pull the battery then re-insert it. Go to your computer and open up ODIN. Plug in you phone in Downloader mode and reinstall.
tweakedlogic said:
I've been trying to install Serendipity to my Captivate. I've been working on this for several hours. Having problem after problem because i came from Windows Mobile ROMS.
I find it hard to find how to instructions for this. diggin in the web to learn about clockworkmod and 2e recovery and Odin (which I still don't konw how to do). Documentation is awful!
Anyway, for well over an hour now my phone has displayed nothing but a Droid digging a hole. Under that it says "Downloading... Do not turn off Target!!!"
What do I do? I think it's stuck. I have read many good thing about Serendipity and wanted to try it. Now I just hope I haven't bricked my phone.
I really love Android, but flashing custom roms to WM phones is much easier and better documented.
Click to expand...
Click to collapse
The biggest problem that most people have with odin is that the proper sequence is not followed. 1. Run odin as admin 2. set up odin how you want 3. when odin is fully set up and your phone is in a fully off state with no usb pluggged in....THEN hold both volume keys while plugging in the usb and voila. ps like was said this belongs in Q&A
I think... yes, I think I may have it working. I will update later. I need some sleep sometime tonight.
One thing that wasn't clear to me doing this last night for the first time...
When the phone goes into that "downloading..." mode, it won't do anything more until you press 'Start' on Odin. Now I am a noob at this, but others are too so that might clarify things a bit.
http://forum.xda-developers.com/showthread.php?t=884364
There's even a video with step by step instructions.
tweakedlogic said:
I find it hard to find how to instructions for this. diggin in the web to learn about clockworkmod and 2e recovery and Odin (which I still don't konw how to do). Documentation is awful!
Click to expand...
Click to collapse
I know what you mean about documentation, bro! But I had a WM phone as well (AT&T 8525) and it wasn't always that easy to flash that thing either! Once you get the info together, it's prett straitforward. You just have to save those bookmarks! lol
Anyways, regarding your Clockworkmod 2e issue. I just posted a solution to this as I had the same issue just last night and figured it out.
Read this thread:
http://forum.xda-developers.com/showthread.php?t=1002649
This should fix the clockwork signature issue when trying to boot into CWR, if that's the issue you're having. It was a little tricky but if you use the instructons I posted it should work fine. Link to original post is also in that thread.
Once that's installed, you can install rom ZIPs easily from there. Just launch the CWR and select install zips from sd. The next menu will let you choose the actual zip file to install. (as opposed to renaming it update.zip)
Non ZIP roms (.tar files) are usually installed using Odin3. Setting the phone to debug mode and selecting the file .tar from the PDA selection menu in Odin. And you usually have to launch Odin first, then plug in the USB cable to make the app see your phone.
If you hose the phone, you can almost always fall back on the old Loader mode to restore back to original rom using the Odin 1 click Stock rom located here:
http://forum.xda-developers.com/showthread.php?t=731989
It includes full instructions. Then you can start all over from there!
And just to get you going again, here's the link to the Super One Click root.
http://forum.xda-developers.com/showthread.php?t=803682
If anyone feels I'm wrong about anything or am over simplifying, please feel free to post your input. I've been doing a lot of mods on my phone for over a year and this is just a basic summary of what I've come up with.
Hope it was helpful.
-maj
Okay before I get all the "Learn to google" or "Use the search function" let me just go ahead and say, I've searched all over the place before posting.
Okay I recently flashed my phone back to stock to get rid of a few problems. I tried to root with one click root and it failed when I tried to test it with sending the su command so not only was it not rooted it wouldn't allow me to use third party downloads So I am now trying to flash it back to stock again. Now Odin won't recognize my phone at all when its in download mode. I've tried reinstalling drivers and everything and it's like when I use Odin once it won't work again without reinstalling the drivers again.
It's hard to explain my exact problem but basically it's like the drivers keep resetting themselves or something where Odin won't detect my phone. And secondly my one click root no longer seems to work.
Any help would be greatly appreciated, this is getting very frustrating.
Edit: Now I am getting the "More than one device detected" error on the super one click.
Cleimon said:
Okay before I get all the "Learn to google" or "Use the search function" let me just go ahead and say, I've searched all over the place before posting.
Okay I recently flashed my phone back to stock to get rid of a few problems. I tried to root with one click root and it failed when I tried to test it with sending the su command so not only was it not rooted it wouldn't allow me to use third party downloads So I am now trying to flash it back to stock again. Now Odin won't recognize my phone at all when its in download mode. I've tried reinstalling drivers and everything and it's like when I use Odin once it won't work again without reinstalling the drivers again.
It's hard to explain my exact problem but basically it's like the drivers keep resetting themselves or something where Odin won't detect my phone. And secondly my one click root no longer seems to work.
Any help would be greatly appreciated, this is getting very frustrating.
Click to expand...
Click to collapse
You should try superoneclick (SuperUser) - It has never failed me
Also, you do not need to be rooted if you're on stock 2.1 Eclair - You can simply change the name of the ROM to update.zip, go into recovery and reinstal package.
As for Odin, I don't know what to suggest other than you could try using the non-one click one.
Cleimon said:
Okay before I get all the "Learn to google" or "Use the search function" let me just go ahead and say, I've searched all over the place before posting.
Okay I recently flashed my phone back to stock to get rid of a few problems. I tried to root with one click root and it failed when I tried to test it with sending the su command so not only was it not rooted it wouldn't allow me to use third party downloads So I am now trying to flash it back to stock again. Now Odin won't recognize my phone at all when its in download mode. I've tried reinstalling drivers and everything and it's like when I use Odin once it won't work again without reinstalling the drivers again.
It's hard to explain my exact problem but basically it's like the drivers keep resetting themselves or something where Odin won't detect my phone. And secondly my one click root no longer seems to work.
Any help would be greatly appreciated, this is getting very frustrating.
Click to expand...
Click to collapse
a) who said one click root will enable 3rd party apps
edit, you do want super one click root as stated above if you dont have that get it. the thread is by clshortfuse and usese the rage against the cage meathod, works on every phone
b) you need busy box before comands work, it is in the market
c)i dont know what your odin problem is, does the box turn yellow when you plug in the phone with in download mode? is this odin one click? odin one click+3button fix? odin files without bootloaders plus full odin? what version of odin? what series number is the phone under the battery? 1006?1007?ect...
Well the problem with moving the update.zip file manually is that my computer will no longer detect my phone regardless what mode my phone is in. And I was using superoneclick
Edit:
A) The Super one click root allows the option to enable non market apps, which has previously worked in the past but doesn't any more.
B) Can't get busybox without rooting
C) SGH-I897
Cleimon said:
Well the problem with moving the update.zip file manually is that my computer will no longer detect my phone regardless what mode my phone is in. And I was using superoneclick
Click to expand...
Click to collapse
Then it's most likely your computer and not your phone.
Try another usb port, cable;
unistall and reinstall the drivers;
restart your computer.
If none of these work, try on another computer.
After that, it could be the usb port on your phone.
Could I get a link or quick guide on how to uninstall and reinstall drivers.
Cleimon said:
Could I get a link or quick guide on how to uninstall and reinstall drivers.
Click to expand...
Click to collapse
google/youtube it?
lol it is quite simple but I can't help you more than this as I'm at work
Actually, it was the fact that my front USB port was the problem. I used one of the back ports and it seems to be working. Wow I feel like an idiot haha.
Anyway thanks for the help!
BWolf56 said:
Then it's most likely your computer and not your phone.
Try another usb port, cable;
unistall and reinstall the drivers;
restart your computer.
If none of these work, try on another computer.
After that, it could be the usb port on your phone.
Click to expand...
Click to collapse
Should've followed my steps lol hence the 1st one
And no problem!
And now...it's not working again. No longer detecting my phone.
Cleimon said:
And now...it's not working again. No longer detecting my phone.
Click to expand...
Click to collapse
lol What are you doing to it?
Hehe, kidding
Umm - Try a different Odin.. Odin3 one click worked for me before.
You can try a non-one click Odin as well, sometimes it works when the other doesn't.
You don't have to connect to your computer either to flash a rom. download a rom with your phone ... Rename THAT update.zip on the phone ... Boot into recovery reinstall packages ... Its probably your computer like was said not the phone.
I reinstalled drivers, still not working. Any ideas?
Ummm when was the last time you made a restore point on your pc? Restoring from a few days prior worked for me when nothing else would, although it was just the dl mode driver that broke in my case ... You can't get it recognized at all ... But still woth a shot.
Studa,
What about Heimdall? Think it may help him?
mrhaley30705 said:
Studa,
What about Heimdall? Think it may help him?
Click to expand...
Click to collapse
I always forget about that! Whats the other one aio toolbox? Idk ask I've used is odin ... But ill read up on both of those.
studacris said:
I always forget about that! Whats the other one aio toolbox? Idk ask I've used is odin ... But ill read up on both of those.
Click to expand...
Click to collapse
The i9000 forum had an entire thread devoted to Heimdall.
studacris said:
I always forget about that! Whats the other one aio toolbox? Idk ask I've used is odin ... But ill read up on both of those.
Click to expand...
Click to collapse
mrhaley30705 said:
The i9000 forum had an entire thread devoted to Heimdall.
Click to expand...
Click to collapse
the latest version of AIO (3.0) uses heimdall instead of odin. i would recommend it
Okay downloaded the AIO tool box, looks pretty solid from what I can tell, will update to see if this fixes my issues.
Well I rooted with the toolbox and I when I try to run root required apps it says that my phone is not rooted or I haven't accepted superuser permissions. I do not receive a notification to accept these permissions however it does appear superuser is installed.
On the bright side I got all my drivers set up correctly.
I have been looking through the threads, and havent seen what I am looking for. So hopefully i will not get flamed to bad. I tried to install mikeymikes GR12, I got through the first stage of downloading the gingerbread rom to the phone through odin, but then it went south. I lost root and was unable to get back to the download screen. I then tried to use the all in one tool to root the phone, and that put me to the recovery screen where i could not use the ok button, just the volume up and down buttons. I just managed to get the download screen to come back, but i cant get anything else to work. Any suggestions on what to do, where to go from here.
Thank you for your help
I would go back to stock first. I believe your problem lies in the bootloaders. There are two bootloaders in the beginning and if you don't have the gingerbread ones installed, you won't install gingerbread properly.
I would use DesignGears One Click Odin to go back to stock and load the Froyo drivers. http://forum.xda-developers.com/showthread.php?t=731989. Make sure you open up Odin first before plugging in your phone, then hit the Start button.
Once that is done, you can try again, but read about getting the GB bootloaders installed properly before you try to flash a GB ROM. Any of the GB ROM instructions should get you there. Just make sure you know all the steps before you try it again.
Good Luck!!
I don't see why you would be flamed for your question. That is what Q&A is for and you are in a bad spot. The biggest thing to remember is to be as specific as possible when you post a question. This includes what you were trying to do, what steps you took, what was the result, when did the problem occur (which step) and what you have tried to do, if anything to fix it.
One more thing. It is always possible that the USB cable is bad or that the USB port you are plugging into (on the computer) isn't working properly. You might also want to plug into a different USB port.
Sorry these posts are broken up, but as I'm coming up with ideas, I'm posting.
Here's something you should try:
(I wrote this for Team Phoenix, hence the sig.. But it works the same with every ROM. There's a link to a very nice tutorial I suggest you follow).
http://forum.xda-developers.com/showpost.php?p=13503747&postcount=2
Hope it helps
You guys are awesome, Odin one click worked, It's on eclair, but it works! Thank you again
donkeyboy said:
You guys are awesome, Odin one click worked, It's on eclair, but it works! Thank you again
Click to expand...
Click to collapse
Glad it worked!
Make sure you read and understand before going forward with flashing
Otherwise... well.. I'll still be in here ready to help lol
BWolf56 said:
Glad it worked!
Make sure you read and understand before going forward with flashing
Otherwise... well.. I'll still be in here ready to help lol
Click to expand...
Click to collapse
Me too. If we can ... Remember not all things can be recovered from so please read everything twice before ever touching your phone.
10-4. My next question is: where do I get froyo from. Kies sees my eclair version as unregistered, so it wont update. And my ota sees an update is needed, but when i tried, the area im in has crappy signal, so the update failed and now i have to wait 24 hours to do it.
Any suggestions?
Thanks again
are you planning on flashing a custom rom?
if so updating to official froyo is A HUGE WASTE OF TIME
EDIT:are you Canadian by chance? if so check this thread:http://forum.xda-developers.com/showthread.php?t=979133
I only plan to root the official froyo right now, that is what I had before I jacked it up. I am not Canadian.
donkeyboy said:
I only plan to root the official froyo right now, that is what I had before I jacked it up. I am not Canadian.
Click to expand...
Click to collapse
Going on official froyo will get you the signature failed error (which you need the 3e recovery fix if you ever want to flash a custom ROM).
So, basically, if you want more than 2.2 official release. We suggest you don't update. If you're perfectly fine staying on 2.2 Froyo, then there's no problem lol
As for Kies, you shouldn't have any problem using Kies mini. Other than that, there is a 2.2 flash around here. I'm sure you'll find it doing a little search
I had root on my official froyo for a couple of months without a problem. Right now i cant get my phone to go into download mode, it only goes to the battery screen. If i can get to download i can make some headway
donkeyboy said:
I had root on my official froyo for a couple of months without a problem. Right now i cant get my phone to go into download mode, it only goes to the battery screen. If i can get to download i can make some headway
Click to expand...
Click to collapse
If the battery pull way isn't working. You could always go read on abd. It send SU commands and you could get your phone in downlaod mode that way.
Is there an easy way to get adb without getting the sdk. I downloaded the sdk and it keeps saying i need java, when i download the java crap it says the same thing.
donkeyboy said:
Is there an easy way to get adb without getting the sdk. I downloaded the sdk and it keeps saying i need java, when i download the java crap it says the same thing.
Click to expand...
Click to collapse
Did you reboot your pc?
Yes i did, no change
i believe you need microsoft .net framework installed also...
easy adb setup link in my sig.
files and everything needed to get going.
you may want to build a jig yourself or buy one online just in case:
MOD EDIT: No links to commercial products please.