Related
I know, I know: First use the board-search and google...
I did that and I couldn't find anything useful for my issue.
I'm trying to update my HTC Prophet G4 to WM6.1...
I wanted to use SoftSPL and after executing the SPL.lnk the screen turns white as it should, but after that Windows XP doesn't recognize my phone anymore as connected.
I tried different USB-Ports, but the "ROMUpdateUtility_NV_G4.exe" keeps telling me "Error 260" which means it couldn't connect to my phone.
I'm really desperate cause I've already tried to upgrade for some days...
So if anyone knows how to fix that plz write =D English and German are okay with me
mickgrand said:
I know, I know: First use the board-search and google...
I did that and I couldn't find anything useful for my issue.
I'm trying to update my HTC Prophet G4 to WM6.1...
I wanted to use SoftSPL and after executing the SPL.lnk the screen turns white as it should, but after that Windows XP doesn't recognize my phone anymore as connected.
I tried different USB-Ports, but the "ROMUpdateUtility_NV_G4.exe" keeps telling me "Error 260" which means it couldn't connect to my phone.
I'm really desperate cause I've already tried to upgrade for some days...
So if anyone knows how to fix that plz write =D English and German are okay with me
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=353547
Thanks for posting, but as I already told you: I did my research...
So I already tried different FlashingTools, like ProphetTools etc.
When I SoftSPL, I get to the whitescreen but i cannot make my pc recognize the phone at my usb-port.
When I enter the 3-Colored-Screen manually it shows the usb-connectivity, but I cannot update the ROM...
There was a way (I cannot remember anymore which way I did it, cause I really tried very often) I entered the 3-Colored-Screen and there was "RUU" written in the right upper corner of the screen. But then again the connectivity doesn't work...
Also tried different usb-ports and cables...
I could say that I'm feeling like a weirdo, cause upgrading a rom seems easy and still makes my day miserable xD
//EDIT:
Didn't see the "Lazy_Tool" at the first glance, but now after trying I still get the same error...
//EDIT2:
Realized that the error-code could be useful^^ --> "Error[260]: Update Error" (Sth like that^^)
I had a similar issue. When your PC reports it cannot connect to the phone - does the phone restarts?
mickgrand said:
Thanks for posting, but as I already told you: I did my research...
So I already tried different FlashingTools, like ProphetTools etc.
When I SoftSPL, I get to the whitescreen but i cannot make my pc recognize the phone at my usb-port.
When I enter the 3-Colored-Screen manually it shows the usb-connectivity, but I cannot update the ROM...
There was a way (I cannot remember anymore which way I did it, cause I really tried very often) I entered the 3-Colored-Screen and there was "RUU" written in the right upper corner of the screen. But then again the connectivity doesn't work...
Also tried different usb-ports and cables...
I could say that I'm feeling like a weirdo, cause upgrading a rom seems easy and still makes my day miserable xD
//EDIT:
Didn't see the "Lazy_Tool" at the first glance, but now after trying I still get the same error...
//EDIT2:
Realized that the error-code could be useful^^ --> "Error[260]: Update Error" (Sth like that^^)
Click to expand...
Click to collapse
260 IS A KIND OF CONNECTION ERROR,
PLEASE SOFTRESET AND TRY AGAIN!!!
1. FLASH NVID FIRST,
2. LAZY TOOL TO HAVE THE JOB DONE.
dwizard said:
I had a similar issue. When your PC reports it cannot connect to the phone - does the phone restarts?
Click to expand...
Click to collapse
If u want to know if I bricked the phone then no =) I can restart it and everythings fine^^
If u meant sth else plz specify your question a bit
@ dioxda2:
Ok I'll experiment a bit^^ I'll get my new hardware soon, so maybe the error won't be a problem^^ We'll see =)
mickgrand said:
If u want to know if I bricked the phone then no =) I can restart it and everythings fine^^
If u meant sth else plz specify your question a bit
Click to expand...
Click to collapse
OK, rephrasing: the problem I had with my phone was that while a ROM update was running the phone would restart and I got the same error you did.
It turned out the battery was at fault, after replacing it with a new one - it works great.
If u do as dioxda2 says all should be fine. He is right in saying 260 is a connection error. That means unplugging all usb devices out of ur machine. It also means disabling all other connection software, like my raspberry program that display device screen when active sync'd. I always disable my anti virus and firewall (make sure ur not connected to internet at time).
i always ensure that the flashing tool is on the root drive, not in many folders (so place flash tool direct on ur main hard drive in its folder as uve unzipped) this itself can cuase connection errors. Ensure battery is 50% min too.
Good luck
Hey, after rooting my phone and installing a few different custom roms, my USB connection has stopped working. whenever I connect the phone to a PC via USB, the device is unrecognised, and mass-storage doesn't work. It's definitely a hardware error, since trying a variety of different roms on a variety of computers, hasn't solved the problem, and even the recovery image doesn't allow mounting the SD card.
Research has suggested that it's affected other people in the past, with the only fix being to replace the motherboard. Hence, I'm looking for advice on un-rooting, rather than advice on fixing (but thank's for your good intentions!).
So I need to un-root my phone (and set it back to factory defaults), so that I can return it to T-mobile and have them fix it under warranty. Of course, because USB isn't working, I can't un-root the "traditional" way, by just installing the RUU update.
So I'm trying to figure out how to set the phone back to its original software, and I thought I'd ask for some advice before I make a mess of things...
As far as I know, there are 2 things that need to be done:
Flash the stock rom back on
- This bit is pretty straightforward; I just use the stock update.zip files found on the Modaco Forums (can't share a link here due to new account), and use the recovery image to update. The lack of a USB connection isn't a major issue for this bit, as I can transfer the zip files using the WebSharing Lite app (which allows me to upload to the phone over wi-fi)
Remove the Amon_Ra recovery image
- This is where I'm having issues. How do I go about clearing the recovery image, without a working USB connection? I'm not really sure how I put the recovery image on in the first place!
If someone could give me advice on how to remove the recovery image (or reset it to the stock one... I'm not sure if there was one initially), I'd really appreciate it. Also, please let me know if I'm missing out anything important.
Assuming everything works, later I'll write out a proper guide for anyone else who's ever in the same position.
Thanks in advance
Maybe this thread could help you?.... Read the last post on the 1st page, something about re-enabling USB.
Worth a shot?
EDIT,..... The link would help wouldn't it,.... Nandroid restore left other stuff around? (No ADB, No SD) [SOLVED]
thanks for your suggestion, but it didn't seem to work. apparently the issue has cropped up for other users, and the only long-term fix is to replace the motherboard under warranty, which is why I'm asking about un-rooting.
k28 said:
thanks for your suggestion, but it didn't seem to work. apparently the issue has cropped up for other users, and the only long-term fix is to replace the motherboard under warranty, which is why I'm asking about un-rooting.
Click to expand...
Click to collapse
You sure?... Have you started your phone in fastboot (hold vol- and power)? Try that to make sure if you haven't already. Once it comes up with the white screen and skateboarding androoids it'l say to press back or vol- (not sure which one so read it) to put into fastboot.
But if you have done that already,... Unfortunately I dont know how you can run an RUU .exe without USB.
yep, tried the whole fastboot thing, didn't work. I can connect to fastboot, but using the command "fastboot oem boot" , everything is normal - usb/sdcard are not disabled
(i didn't copy the exact output, and I don't have sdk on this laptop.. but yeh, that person's advice didn't match my situation).
hopefully someone else will have some ideas/comments?
k28 said:
yep, tried the whole fastboot thing, didn't work. I can connect to fastboot, but using the command "fastboot oem boot" , everything is normal - usb/sdcard are not disabled
(i didn't copy the exact output, and I don't have sdk on this laptop.. but yeh, that person's advice didn't match my situation).
hopefully someone else will have some ideas/comments?
Click to expand...
Click to collapse
What?.... It DOES connect in fastboot?... Says fastbootUSB (or something similar) on the screen?
I had same kind of problems with my usb. Try cleaning the "usb-hole"
lol, tried cleaning it but no luck.
from the research I've done, I've sorted out how to put the main ROM in place.
now I just need to find a copy of the recovery image of a T-mobile G2 Touch, and flash it using flashrec
can anyone help with that?
1. recovery - put regular hero recovery od sdcard and try to flash it using flashrec
2. root apk - delete it using root explorer
Im running stock Gingerbread, never been rooted.
What I am looking for is a simple one click method to root the phone for a few minutes so I can make a few tweaks and then unroot it.
Yes, Im aware that I can use the Odin method to root without tripping the flash counter, make my tweaks, and then use another Odin package to unroot it, however, there are a few problems with this, in order to keep this brief, I dont want to go into all the details but suffice it to say, I dont want root constantly enabled, I just want to enable it briefly and I dont want to install CWM so I can reset the flash counter and then (if its even possible) have to re-install the 3e recovery menu EVERY time I need root for something briefly.
Im looking for something along the lines of Super One Click (shortfuse.org) or UnlockRoot (www.unlockroot.com) where I can hit root, the phone reboots, I do what I need to do, hit unroot and the phone reboots unrooted. Both of these tools, needless to say, do NOT work (even tho they are listed as supported devices). Remember also, this is the ATT Note SGH-I717 so when looking thru the device lists supported by other software, make sure to look for the right Note .
i don't think those methods exist like they did with say the Samsung infuse. I used the Odin way, just as easy as super one click...but you mentioned you didn't want to use it so I'm not sure what you can do. Why not just stay rooted? And there is a flash counter reset just so you know
Sent from my SAMSUNG-SGH-I717 using Tapatalk
I used odin super fast and easy
Sent from my SAMSUNG-SGH-I717 using xda premium
Im well aware of how easy the pre-rooted kernel is to flash via Odin, its the unrooting process that is a pain.
I dont want to stay rooted and I dont want to use Odin, the process of reverting back to unrooted is too much of a pain in the ass.
My guess is that there is no easy one click process or it would have been posted already.
Its a shame, one of the huge benefits with Android was how easy it was to gain root to tweak OS level things and then revert back to an unrooted state.
I used SuperOneClick without any issues whatsoever? What, is it not supposed to work or something?
juzz86 said:
I used SuperOneClick without any issues whatsoever? What, is it not supposed to work or something?
Click to expand...
Click to collapse
Erm, ok, Id love to know how you did...
First, what phone do you have (carrier). I am using the ATT Note.
If we are on the same page there, what settings do I need to enable on the phone and/or SuperOneClick?
On my phone, I enabled USB Debugging, in SuperOneClick, I left everything default, I click the Root button and on step 7 a bunch of gobbly gook appears (there is no log created so I cant just copy and paste some of the text) and it just stops. I left it sitting for a few minutes and nothing happened to either the phone or SuperOneClick.
littlewierdo said:
Erm, ok, Id love to know how you did...
First, what phone do you have (carrier). I am using the ATT Note.
If we are on the same page there, what settings do I need to enable on the phone and/or SuperOneClick?
On my phone, I enabled USB Debugging, in SuperOneClick, I left everything default, I click the Root button and on step 7 a bunch of gobbly gook appears (there is no log created so I cant just copy and paste some of the text) and it just stops. I left it sitting for a few minutes and nothing happened to either the phone or SuperOneClick.
Click to expand...
Click to collapse
I have two Notes. The N7000 I rooted using SoC on GB, doing exactly what you've done. The i717 was exactly the same. USB debugging enabled, plugged in and USB not mounted. MY computer is picky about USB ports so I use the same port and cable for every phone.
Grab the latest SoC (my sig has a link) and extract. Install Kies to get the USB drivers, then uninstall Kies and leave the drivers installed. Plug in the phone and let it install. Once it's done, run SoC (not as an administrator), select 'auto' for the exploit and click 'root'.
You'll get the usual 'found a gingerbread', 'sending 149 zerglings' etc. Then it tells you the 'overseer found a path' and after a few more steps reboots with root. Took me all of about 40 seconds.
I use AT&T phones unlocked in Australia, so we are using the same handset. This method doesn't work for ICS, you'll need to flash SU with CWM for that.
Let me know if I can help any more
Yea, unfortunately, it doesnt work for me.
I have the Samsung drivers installed (I know because when I plug in my phone under device manager, it shows my phone as correctly installed and I get a pop up from windows asking me whether I want to open a folder to browse the phones' contents - and Kies sees the phone).
I even tried uninstalling Kies but keeping the driver installed (Windows still asks me whether I want to browse the phone contents).
I also tried removing the sd card, altho this should not affect the process.
When I run SOC, I maximize the window so I can read the text and basically, when it gets to step 7, it sends 149 zerglings, then it waits 40 seconds, then it sends 189 zerglings, waits 40 seconds, then it says that it doesnt have write permissions and asks me whether I have root or not (not in a dialog box but in the text on the right hand side of the screen - I can only assume that it is initially trying to get a shell/temporary root so that it can do what it needs to for a permanent root), then it tries to push some files to the phone and then just completely stops. I let it sit for Id say 10 minutes with no progress.
The only thing that maybe is creating a problem is that the phone seems to be automounting, when I plug in the storage, it doesnt ask me what I want to do, it just mounts the device. I poked around in the settings and couldnt find any setting to disable this but Im not 100% sure this is a problem as the Captivate did the same, when you enabled USB debugging, it would automount the device.
Oh, and when I plug in the USB cable, the notifications bar shows 'MTP Initializing' and a few seconds later, 'MTP Mode'.
And Im using Super One Click version 2.3.3
littlewierdo said:
Im running stock Gingerbread, never been rooted.
What I am looking for is a simple one click method to root the phone for a few minutes so I can make a few tweaks and then unroot it.
Yes, Im aware that I can use the Odin method to root without tripping the flash counter, make my tweaks, and then use another Odin package to unroot it, however, there are a few problems with this, in order to keep this brief, I dont want to go into all the details but suffice it to say, I dont want root constantly enabled, I just want to enable it briefly and I dont want to install CWM so I can reset the flash counter and then (if its even possible) have to re-install the 3e recovery menu EVERY time I need root for something briefly.
Im looking for something along the lines of Super One Click (shortfuse.org) or UnlockRoot (www.unlockroot.com) where I can hit root, the phone reboots, I do what I need to do, hit unroot and the phone reboots unrooted. Both of these tools, needless to say, do NOT work (even tho they are listed as supported devices). Remember also, this is the ATT Note SGH-I717 so when looking thru the device lists supported by other software, make sure to look for the right Note .
Click to expand...
Click to collapse
Did you ever get a working solution to your question? I am in the same position: wanting to temporarily root my phone, do my tweaks and then re-root it so that I can run the POS enterprise mail application that has a policy to check for "root".
I would think that this should be much easier than it seems, but perhaps not
Thanks,
aus
I havent found any solutions yet...
SuperOneClick did not work for me either. I have used it on 3 other phones with no issue so I dunno.
Hi all, it's my first post here
My Galaxy S II (stock ROM/recovery) has fallen into a reboot loop while I was texting and I'm positive I didn't install new apps recently, so I can't really tell it's an app bug. Last thing I did before texting was disabling Swype.
All I know is that TouchWiz now crashes after boot displaying its usual dialog window.
In addition to that, I've just broken the display, so I can't see anything going on screen...
How can I recover pictures from the internal storage? How can I stop the reboot loop long enough to back up everything with Kies?
I've tried booting in safe mode but the phone keeps on rebooting and I have no visual feedback of successful activation of safe mode. Prior to breaking the screen I could access the stock recovery, so I guess I can still do it, if needed.
TIA,
Andrea
Recovery should be enough if it works. So try getting into recovery and connecting it via ADB. Then you can get data with "adb pull <location-on-phone>"
Explorer23 said:
Recovery should be enough if it works. So try getting into recovery and connecting it via ADB. Then you can get data with "adb pull <location-on-phone>"
Click to expand...
Click to collapse
Thank you for your reply!
When you say "recovery", you mean stock recovery or a more advanced one (CWM, etc.)?
I've never used ADB, I'll try to set it up as per these instructions: http://forum.xda-developers.com/showthread.php?t=1917237
EDIT: Do I need to enable debugging on the phone? It's currently disabled and I can't do anything about it because of the reboot loop...
don't know
I don't think that it's possible to recover the data on your device's internal storage now. Rest if anything works do post your experience here with respective procedure or snapshots.
For more attractive deals "Just Dial":- +1 516 515 9871
lo_Spocchioso said:
Thank you for your reply!
When you say "recovery", you mean stock recovery or a more advanced one (CWM, etc.)?
I've never used ADB, I'll try to set it up as per these instructions: http://forum.xda-developers.com/showthread.php?t=1917237
EDIT: Do I need to enable debugging on the phone? It's currently disabled and I can't do anything about it because of the reboot loop...
Click to expand...
Click to collapse
Oh crap ... yes, i think you need to have debugging ON (never actually tried without it). Well, you can still check it. So set up ADB (hope those instructions are good, I can't help you there as I don't know how things work on Mac) and type in "adb devices". If everything's OK, you should get one device listed (some weird number). Then type in "adb pull <location on phone> <location on computer (optionally)>. If you want more info about commands, just type "adb" and you'll get everything listed. That should be it ... if it works in first place :fingers-crossed:
EDIT: Stock recovery should do fine.
Explorer23 said:
Oh crap ... yes, i think you need to have debugging ON (never actually tried without it). Well, you can still check it. So set up ADB (hope those instructions are good, I can't help you there as I don't know how things work on Mac) and type in "adb devices". If everything's OK, you should get one device listed (some weird number).
Click to expand...
Click to collapse
Yeah, I've tried with another (working) S II and it seems you really need debugging turned on...
Is it possibile to use a custom recovery to copy data from internal memory to the SD? I could try to do it blindfolded :cyclops:
lo_Spocchioso said:
Yeah, I've tried with another (working) S II and it seems you really need debugging turned on...
Is it possibile to use a custom recovery to copy data from internal memory to the SD? I could try to do it blindfolded :cyclops:
Click to expand...
Click to collapse
Possible ... maybe. But that would mean you need a recovery with file manager - and file managers are usually touch-based. So you can't do much if your screen is broken. I suggested ADB because it was the only option that would work for sure and you don't need screen for it ...
But ... maybe there still is a way ... You could try reinstalling ROM via ODIN and syncing with Kies. Download stock ROM for your country and carrier from www.sammobile.com/firmwares, get your phone into download mode and insatall via Odin. This should work. You're not doing any factory resets, wipes or anything - just "dirty flashing" the ROM over existing one, so data and (most) apps remain untouched. Then you can try connecting with Kies. From there I don't know exactly how stuff works (don't have a Samsung device), but hope it can launch without touching anything on the phone.
I suggest removing the SIM card before trying, so it doesn't get stuck on PIN unlock screen.
This is really your last chance ...
Your next option is changing the screen
Good luck
Explorer23 said:
Possible ... maybe. But that would mean you need a recovery with file manager - and file managers are usually touch-based.
Click to expand...
Click to collapse
You're right but, if I'm not mistaken, CWM "touch" file manager can also be used with the physical buttons. I've never tried that, can anybody please confirm?
You could try reinstalling ROM via ODIN and syncing with Kies.
Click to expand...
Click to collapse
That's actually an excellent idea! Now, I only need to be sure that, after re-flashing, the device will be immeditely accessible by Kies straight after boot without further intervention...
Your next option is changing the screen
Click to expand...
Click to collapse
True, but I'd rather grow brain cells than shell out money
First off,i would like to apologize for being such an amateur.This is my first post on this forum,so don't get angry on me for breaking some rules (forgive me im new ,idk if i should post this here or somewhere else,don't worry i will be polite ).Anyway as the title says,im having a bit of a problem,or to be more precise a huge one.
So lately i was trying to root my phone,Huawei U8500 which was so buggy,so i decided to root it,install cwm and flash a new ROM.But the problem is i can't get it rooted.I've tried many methods from XDA but none of them worked.Z4 root loads until it displayed acquiring root access,and then the app crashes (closes itself).I've tried Framaroot,but it didn't work either.It said 'try another exploit',but the thing is it displayed me only one.I also tried poot.apk,but it also failed.Telling me '(-) can't get a handle on it:-1 Permission denied'.
(note that all the time my USB Debugging was enabled ! ) All of the apps are at latest version!
So after so many failed attempts with pc-less methods i've decided to try a PC one.The first method i used was Superoneclick,which didn't work.I thought that was because the phones model was not supported.All until a friend of mine told me that he rooted his phone using the same program (he has as well huawei u8500).Every time i try to root with superoneclick it is stuck at the second step(as in screenshot).Then i started googleing and google-ing,until i found a thread with a program called SRSroot,thinking it will safe me from this nightmare that is haunting me for days.But it failed again.The program told me 'ADB Device not found',which made me think about checking the drivers.I've installed the google usb drivers and SDK Manager with all drivers.But still the same happens.So i decided to see if my computer(later many others) recognize my device.After i typed in ADB 'adb devices' it showed me blank.Later i tried to do the same with my other phone and it displayed the device.Another thing i've noticed lately is my computer sees my device as a cd device in windows device manager.It happened with all computers i tried. I've tried it also at my friends(plural,which means more computers).I've tried it on Win7,win XP,and WIN8 and it is still displayed as cd drive.(which is not the case with other phones i've tested!)
I hope someone will read this and help me.I would also like to add, this is not my first time rooting,so i knew what i was doing.
Im so confused,idk what to do,developers pls HELP ME!!!
I will also post screenshots from all the things mentioned above.Hope this helps you figure out the problem
On the adb devices, are you sure it is setup correct, because it needs a set of rules basically. I don't have time right now. But if you search 'adb' in the xda portal (not forum) you will find a windows universal adb installer. That should fix the adb issue. But apart from that I don't know what else you can do.
Sent from my ST18i
tried
Guynan said:
On the adb devices, are you sure it is setup correct, because it needs a set of rules basically. I don't have time right now. But if you search 'adb' in the xda portal (not forum) you will find a windows universal adb installer. That should fix the adb issue. But apart from that I don't know what else you can do.
Sent from my ST18i
Click to expand...
Click to collapse
I did what you said,but the problem is the same.The rest of my phones get recognized as androids,but only this unique Huawei is recongized as CD-Drive,pls anyone help?
Here i took a screenshot after trying to update "cd drive''
Beatit123456 said:
I did what you said,but the problem is the same.The rest of my phones get recognized as androids,but only this unique Huawei is recongized as CD-Drive,pls anyone help?
Here i took a screenshot after trying to update "cd drive''
Click to expand...
Click to collapse
Gosh that is so confusing. Could you reset your phone or do you have data you want to keep? Because you could perform an ADB backup and try a factory reset and hope that all is righted.
I did factory reset,i also did hard reset,but still nothing works
Guynan said:
Gosh that is so confusing. Could you reset your phone or do you have data you want to keep? Because you could perform an ADB backup and try a factory reset and hope that all is righted.
Click to expand...
Click to collapse
Already did it,still the problem persists.Anyone here have any idea?
Beatit123456 said:
Already did it,still the problem persists.Anyone here have any idea?
Click to expand...
Click to collapse
Short of a new phone, I got nothing. Unless you could get into a recovery, try format the system, causing a brick, flash a 2.3 ftf and then a 4.04 after that, clearing data each time.
pls read my question thoroughly
Guynan said:
Short of a new phone, I got nothing. Unless you could get into a recovery, try format the system, causing a brick, flash a 2.3 ftf and then a 4.04 after that, clearing data each time.
Click to expand...
Click to collapse
Since im unable to root my phone,i can't flash a custom ROM.I'm trying to root but no success,pls some1 help????