Related
was trying the 10 min video root process again right now for the 200th time. i took battery out to try it again, went to turn the phone on to put into airplane mode and it went directly to the phone red triangle page. i pulled the battery 5 more times and everytime i try to start my phone it goes to that page. please tell me i didnt brick it and how to fix this. PLEASE
Not sure if this is the bestish area to post.
Dont know much about things , but until someone gets to ya try to remove the SD Card and booting up by chance?
Just pull battery, no usb for about 5 minutes, then power up... all should be well.
Sent from my ADR6300 using XDA App
The recovery screen is there to bring your phone back from the dead in the unlikely event the phone doesn't boot properly, to fix this there are options in this menu
try holding down power/vol - to bring up the list of options, choose reboot to see if it will boot into the phone
and as for the root method, try this one (after you get the phone to boot hopefully)
Here's what i did (also puting the phone in airplane mode does help)
1. Hold down the power/ - Volume buttons until the Hboot screen appears (make sure the SD card is ejected)
2. Use the volume - key to select recovery, then hit power to select it
3. When you see the white screen that says "HTC Incredible" wait until you hear the disconnect sound on the PC and right after insert the SD card, be sure to insert it right before the black screen or this won't work.
**If you didn't get in, take out the battery, and start over at step 1**
also note that sometimes for whatever reason, the phone will still stay on even with the battery removed, to fix that, just disconnect the USB and plug it back in before turning it back on.
4. Loop should bring up that oh so tempting mistress that is, the error everyone likes seeing on there command prompt.
Note: Once you do get all this done, be sure to use unrEVOked2 to flash your recovery, once that is all done, it'll be easy as pie to upload new goodies in recovery
Anyone can correct me if i missed anything
If this helped anyone, and your feeling really really generous, feel free to send me a donation for a mountain dew code red or whiteout . Not really required, Thanks are all good too
That screen is normal, when it fails to load a recovery.
Go have a look at the last couple of pages on the "Incredible root process" thread in this forum. Several people posted detailed instructions, including me. One thing I didn't do (but which seems to have helped some) is to format the SD card (or have another SD formatted this way to swap in) as something besides FAT32, e.g., NTFS, just prior to booting recovery. It takes the phone longer to try (and fail) to mount it, apparently extending your window of opportunity.
[Q] Tried to install Beatmod ICS, stuck on "screensaver" usb and recovery won't work
Hi guys,
I've watched the n00b video and been googling for the last few hours as well as reading through various pages on the XDA forum. I've found a lot of problems that are kinda similar and tried various solutions but don't seem to be quite getting there.
Basically I had Virtuous Affinity as the OS and clockworkmod installed (should be the most up to date versions of both, they were put on no more than a week ago) as well. I also had a backup of current OS and so on on the SD card, as well as the original zip of the rom.
I decide I want to give ICS a go and so I downloaded the betamod ICS and then loaded it. It asked me if I wanted to do a dalvik cache wipe, a dalvik cache + data wipe and a third option I don't recall. I went with the dalvik cache wipe (at the time I was under the impression that was the correct course of action) then put it back in my pocket while ICS installed.
I get my phone out of my pocket later and it's kinda stuck on what looks like (but logically isn't, I'm guessing it was meant to be a splash screen type thing while ICS installed or some such) a screensaver which just loops endlessly. The only thing you can really do is take the battery out and turn her on again, in which case you once again end up in the endless screensaver loop.
I've tried booting to recovery using volume - and the power button and unfortunately it just boots straight into the looping screensaver again.
Getting a bit worried and feeling adventurous I tried seeing what I could do with ADB, however the computer seemed unable to recognise that any device was connected with ADB devices not listing anything.
I've read up a lot and I'm at a loss as to what to do - there's a rom on the SD card and there also should have been a backup but I just can't get it into recovery.
I do have the ability to view the SD card on another device and interact with it, so if there's a potential SD fix, that's certainly not out the window.
But yeah, I'm clueless how to proceed here and very green at the whole rom business. Can anyone advise what I might try to do from here? I don't care what state I end up going back to, or if I lose my data, I can get all that back, I just want the phone in some semblance of basic operation.
I'll be keeping an eye on the thread, if I've left out any pertinent data ask away and thanks in advance for anyone with a clue how I can fix this mess .
EDIT: Post may be better off in ICS thread above and I do apologise if so, I would move it but I seem unable to delete it.
Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.
ik222 said:
Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.
Click to expand...
Click to collapse
I have, it doesn't work. I've left the battery out for a fairly long period. Volume - + power still just brings it back to the "screensaver" loop.
Thanks for the suggestion though.
Turn the phone off completely; pull the battery out for a bit then replace it and don't touch anything. Don't try to turn it on. Plug the phone by usb to your pc (still turned off). At the command prompt in the folder containing adb.exe type "adb reboot recovery" - the phone should power on and go to recovery where you can wipe properly and reflash whatever you want.
You should be able to boot to recovery using the volume down + power button combo (hold the volume-down key, then press and hold the power button and keep both held until you get to the bootloader menu); the only thing that's wrong with your phone is that you've flashed one ROM over another without wiping it first, so the ROM can't load but this shouldn't affect your bootloader or recovery.
Worst case you can flash a RUU which will restore it to the official firmware; you'll then need to re-root and re-install a recovery image to be able to flash custom ROMs again.
Very helpful post, thanks! I'll try all that and see how I go, I'll post if I still have trouble.
Yeah I dunno why I can't boot to recovery it's weird. The volume button wasn't working, so I removed it and am pressing in the volume down portion of the volume button with a pen while holding down the power button. It's possible perhaps I'm not successfully depressing volume down, but I'm 99% sure I am and that that's not it. I am however doing it as you and other guides advise, depress volume down, hold it and then depress power and hold both for about three seconds, no joy!
Anyway, as said, I'll try what you're recommending and see how I go. Thanks!
hopscotchjunkie said:
At the command prompt in the folder containing adb.exe type "adb reboot recovery"
Click to expand...
Click to collapse
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.
Ethicistabdiel said:
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.
Click to expand...
Click to collapse
Yeah that was what I meant; I've got a feeling that that only works when the phone is powered off if you had USB debugging activated on the phone beforehand, so if that's not working that might be why.
c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.
Accidental double post, sorry.
You need to try get into recovery mode, where you can do a full wipe and see if that fixes anything.
Firstly, remove your battery then re-install it, your phone should still be turned off at this stage. Press and hold the volume down button, then additionally press and hold the power butter, until something appears on the screen. If the bootloader appears, you can then boot into recovery from there.
If the above fails to work, report back with your results and hopefully something else will be suggested.
Ethicistabdiel said:
c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.
Click to expand...
Click to collapse
Your only other option to get into recovery is the volume-down/power-on combination. Like I said, I can't think why that's not working unless it's related to your missing volume button (maybe it's not maintaining a constant pressure on the button when you're using whatever to press through the hole).
If you still can't get that to work, I would suggest finding a stock RUU and flashing that. It's an .exe file that runs from your PC and will return your ROM, bootloader and radio back to stock. Obviously that means you'll lose root and your custom recovery so you'll need to do all that again from scratch. There's a sticky in the dev section with a link to a thread with various RUUs (it's named something along the lines of "shipped & test ROMs" - I'll check that and link to it once I've dragged myself out of bed to the computer). You'll lose all your data, but if you took a backup beforehand you can restore that once you're back up and running.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.
http://forum.xda-developers.com/showthread.php?t=824357&page=5
Guessing you mean that as far as the ruu thread. Am downloading a stock rom atm, with shaped internet till tomorrow, meh! Will see how I go. Have a feeling phone was probably Vodafone branded at stock though, so that could make for extra fiddling but yeah, fingers crossed.
If you are able too install a stock-rom you can work from their than install 4EXT recovery
touch than you doen't need the volume buttons.
I downloaded the most recent stock rom on the link above. When I try to install it though, phone off or on, it advises a USB connection error. Is this likely to be because I originally had vodafone stock and need to make a gold card, or should it still at least be recognising it? It does advise not to run any programs on the phone or anything when while installing the update, but of course, as long as my phones turned on it's stuck on the damned screensaver loop.
http://forum.xda-developers.com/archive/index.php/t-841890.html
Gonna give that a go, fingers crossed!
D'oh, just found out my mobile was Three at stock and not Vodafone, the search continues .
Gah, I'm about tearing my hair out here, I want my damned phone back . Stuck using a $79 Huwawei Vodafone thing at the moment and it's so so so awful.
Anyway. I was under the impression that making a goldcard would mean I could RUU a non-Three stock rom on the phone. I made a goldcard following these instructions; http://www.addictivetips.com/mobile/how-to-make-gold-card-for-htc-desire-hd/
Then I turned the phone on as the RUU advises, (meaning it's scrolling through the feckin' "screensaver") and start the process and once again get a USB connection error.
What's the better process at this stage, try and take it back to Three stock? I don't see how I can at the moment, the only Three stock I can find seems to be rom, not RUU, meaning I'd need to load from the phone, which I can't due to no recovery. Or should I keep trying to get the goldcard thing to work, maybe try some different RUU's or something?
I'm open to any other suggestions as well. Had a bit more of a fiddle around with my volume down button, no matter what I do though, I can't get recovery mode. Always boots first to the white HTC screen and then starts the infernal "screensaver" loop.
Ethicistabdiel said:
Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.
Click to expand...
Click to collapse
How come the volume down button be broken. When you were using Affinity Rom weren't you able to use your volume button for music. Remove SD card from phone then press "First - Volume down gently for 2 sec" & press-hold power button when it goes into bootload place your sd card back select option "REBOOT RECOVERY". I think your panicking too much just be patient nothing is wrong, i think your just hurrying it up...
The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .
Ethicistabdiel said:
The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .
Click to expand...
Click to collapse
The only option i can think of is "Fix your volume button from your nearest Service centre". Without that you cant do anything. I am Sorry....
So it all started out rather stupidly. I was attempting to flash a new ROM to my phone and I was deleting everything and accidentally deleted the OS by accident (mis-touched in recovery mode). I panicked and I attempted to push a file through adb but it was halting between 4MB - 8MB on a 200MB file. I knew this wasn't right. I ran cmd in administrator mode and tried again and got the same results.
I then moved to ODIN to attempt to flash the ROM. I ran ODIN in administrative mode. Bootloader was unlocked. I attempted to flash the new ROM but it stopped at about 1/8th of the progress (as shown in the download mode). This led to my phone having communication issues with my PC (displayed the phone with a hazard sign on the cord to the PC). I assumed it was bricked after googling around.
I then tried to use OMAPFlash as suggested by other people with the same issue. I did this, followed instructions perfectly, installed certificates. It got to the point where it was attempting to download a file. After 2 hours of waiting, I stopped it stupidly because it was making no progress.
Now my phone is completely black. I have no OS and I am not even sure if I have any files on it. Screen is black, phone not responding to button pushes and it isn't being recognised by my PC. I have tried unplugging it, removing battery and then plugging it in and inserting the battery again and that has failed.
I don't know what else to do. OMAP isn't picking up the phone anymore even though I have followed the instructions perfectly again. The one sign that my phone is still alive is the beeping noise from windows as I insert it meaning something must be happening. This however is soon followed by "Your device is unrecognised".
Can anyone help me on the situation as the phone is in perfect condition (physically) and I can't really afford a new decent phone at the moment.
Here is all the information you may need:
[Before incident]:
ROM: CM11
Rooted: Yes
Bootloader Unlocked: Yes
Ask for anything else.
[Attempted to change to]
ROM: XenonHD
Ask for anything else.
first off, why odin?
its a nexus you can flash back to stock from fastboot. I would suggest you download the factory images for the phone from here:
https://dl.google.com/dl/android/aosp/takju-jwr66y-factory-5104ab1d.tgz
then extract the images into a folder - remove the battery from the phone, put it back in the phone, power up while holding down vol + and vol - to get into fastboot
hopefully you have android sdk installed and fastboot working. use the flash-all script to flash every partition of the phone back to 4.3 stock.
good luck.
Well first thing, did you select the right zip file for your Gnex when flashing XenonHD. Bcz in my case few days ago i stupidly selected the wrong zip file (ROM for Nexus 5) to flash, but luckily i was saved by the CWM via "Status 7 Error".
But your case is more complicated i would suggest you to use Gnex toolkit with Google Factory Images, i hope that it will come for your rescue . Also try this method http://www.androidrootz.com/2012/08/how-to-restore-galaxy-nexus-i9250-to.html maybe it will do some miracle for you. Best of luck.
Progress
So after sleeping on it and spending some time deeply reflecting on the derp that I had made, I successfully managed to use omap to restore my device to the Phone-Exclamation mark sign as posted by another XDA user who ended up sending his phone back. If you search galaxy nexus brick in google images, you will see what I am talking about (can't post image).
I guess the best way to explain it is: [] -- /_\ -- [ ]
Basically it is a phone connected to a yellow exclamation mark sign and then that is connected to a computer.
Is there a way to force my phone into download mode from here. I can't seem to do anything. Some good news is that ODIN is now picking up my device. It is however crashing whenever I attempt to flash the stock ROM (either "odin3 communicator has stopped working" or "odin3 downloader has stopped working").
Any help fixing this?
hey everyone! new to the forum. needed help bad.
i have been running CM 10.2.0 for awhile now, pretty much since it was released without any issues. yesterday for whatever reason while surfing the net my phone restarted. now it keeps restarting every 15-20 secs. my main concern at this point is saving my photos before i reset my phone and start from scratch. any ideas as to how to back up photos?
some notes on my rebooting condition.:
phone keeps rebooting even when booted up in safe mode.
-in safe mode i do have more time before it reboots itself
phone does not reboot itself when in bootloader mode or recovery mode
i tried to back up to sdcard while in recovery mode but it fails when it tries to back up data. i also tried using nexus root toolkit but to no avail.
any help would be much appreciated. feels weird to not have a phone.lol. thanks in advance
lilzed_747 said:
hey everyone! new to the forum. needed help bad.
i have been running CM 10.2.0 for awhile now, pretty much since it was released without any issues. yesterday for whatever reason while surfing the net my phone restarted. now it keeps restarting every 15-20 secs. my main concern at this point is saving my photos before i reset my phone and start from scratch. any ideas as to how to back up photos?
some notes on my rebooting condition.:
phone keeps rebooting even when booted up in safe mode.
-in safe mode i do have more time before it reboots itself
phone does not reboot itself when in bootloader mode or recovery mode
i tried to back up to sdcard while in recovery mode but it fails when it tries to back up data. i also tried using nexus root toolkit but to no avail.
any help would be much appreciated. feels weird to not have a phone.lol. thanks in advance
Click to expand...
Click to collapse
Hate when a rom just goes bad for some reason.. Could you supply the error messages you get when your backup fails? I'm guessing it might have to do with file names having weird symbols. Also you might want to backup different folders of your sdcard at a time to avoid failure; i.e., "adb pull /sdcard/Download <some_directory_on_computer>".
7175 said:
Hate when a rom just goes bad for some reason.. Could you supply the error messages you get when your backup fails? I'm guessing it might have to do with file names having weird symbols. Also you might want to backup different folders of your sdcard at a time to avoid failure; i.e., "adb pull /sdcard/Download <some_directory_on_computer>".
Click to expand...
Click to collapse
thanks for the reply. system backup finishes then it goes to back up data. after while it says that there's an error making backup image of /data
is it possible to just to use command prompt to just pull my pictures? would it just be adb pull /sdcard/dcim <some directory>?
also for some reason i am unable to communicate with my phone using adb prompts. yesterday i typed in adb devices and my phones serial number would come up as connected. today under "list of devices" its just blank....not sure what to do.
UPDATE: i was able to get my pictures off of my phone. i launched CMD through the nexus toolkit and it seemed to detect my phone.
i flashed my phone back to stock using the toolkit. for some reason after everything was said and done my phone wasnt actually set back to stock. my phone still has all my apps etc. it still restarts every few seconds.
i tried a couple force flashes using the toolkit again but still same phone. nothing has changed or been fixed. not really sure what my next plan of attack should be. any guidance is very much appreciated.
lilzed_747 said:
UPDATE: i was able to get my pictures off of my phone. i launched CMD through the nexus toolkit and it seemed to detect my phone.
i flashed my phone back to stock using the toolkit. for some reason after everything was said and done my phone wasnt actually set back to stock. my phone still has all my apps etc. it still restarts every few seconds.
i tried a couple force flashes using the toolkit again but still same phone. nothing has changed or been fixed. not really sure what my next plan of attack should be. any guidance is very much appreciated.
Click to expand...
Click to collapse
Glad to hear you got your pictures off. As far as wiping your phone. If you got everything off your sdcard that you want, you can do a fastboot wipe.
-press volume up + volume down + power to get to fastboot mode
-connect the phone to your computer and enter in the command window "fastboot devices" to see if it's connected
-enter "fastboot -w" to do a full erasure of the phone's /data partition
Then use nexus toolkit, recovery, or fastboot to flash a new rom from there. This has saved me in the past in a similar situation. Definitely make sure you have everything off your sdcard you want to keep before trying this though.
7175 said:
Glad to hear you got your pictures off. As far as wiping your phone. If you got everything off your sdcard that you want, you can do a fastboot wipe.
-press volume up + volume down + power to get to fastboot mode
-connect the phone to your computer and enter in the command window "fastboot devices" to see if it's connected
-enter "fastboot -w" to do a full erasure of the phone's /data partition
Then use nexus toolkit, recovery, or fastboot to flash a new rom from there. This has saved me in the past in a similar situation. Definitely make sure you have everything off your sdcard you want to keep before trying this though.
Click to expand...
Click to collapse
thanks so much for the help so far. unfortunately everything you have told me so far has not worked.lol. i followed the steps like u said but the phone just stays on the "google" screen after i install a stock rom. left for 2.5 hours in hopes of it doing its thing.lol. had to pull battery and start it up. nothing changed, phone still restarts i also tried using toolkit to flash stock + unroot (both in bricked mode and normal mode), flashed zip stock images and installing in recovery mode. i also used CMD to push stock images to my phone and installing but still nothing.
i also followed the instructions extactly on this forum http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1
all of the steps successfully completed but after a reboot my phone was left unchanged.
i may have screwed up my description of the problem earlier. the phone restarts after my phone stop responding/freezes. i also find that there almost always is a program that stops working. i find handcent sms is having the most errors. tried to uninstall but phone freezes. tried in fastboot/adb but nothing happens.
thanks again for the help so far.
Hi everyone, today my Elephone p8000 with stock rom (no root nor recovery installed) proposed me an OTA update, and I did it.
After installing the update the phone is stuck at the boot animation logo. If I boot in factory mode (volume down + power button) I am presented with a bunch of options in Chinese, which I don't understand. If I go in recovery mode (volume down + power button) it says "no command".
What can I do? What are my options? Is it bricked?
Yup mine too. Mine has root, with no custom recovery. Get the same boot loop and the sad open Android 'no command'.
Haven't had a chance to dig around for a solution but I suspect it is a case of using the flash tool to wipe and load a standard ROM? Hopefully an easier way.
kevvyboy said:
Yup mine too. Mine has root, with no custom recovery. Get the same boot loop and the sad open Android 'no command'.
Haven't had a chance to dig around for a solution but I suspect it is a case of using the flash tool to wipe and load a standard ROM? Hopefully an easier way.
Click to expand...
Click to collapse
Damn. I had huge problems with the flash tool in the past (I don't have a Windows PC) and the idea of spending the weekend trying to get the damn thing work is not a fun one.
Got this issue too this morning on way to work, I guess my phones useless today until I get home to try and flash it.
seem to be able to get to the boot select screen but nothing is different anyway, also managed to get into a "PCBA" mode that did a load of tests to the phone but thats it.
it now just died, not powering on, think its bricked :crying:
skea said:
it now just died, not powering on, think its bricked :crying:
Click to expand...
Click to collapse
Probably just out of power. Try charging it for a while and/or download and flash entire rom using sp flash except for data-partition so as you don't lose your data.
pitrus- said:
Probably just out of power. Try charging it for a while and/or download and flash entire rom using sp flash except for data-partition so as you don't lose your data.
Click to expand...
Click to collapse
thanks it was out of power lol
I just had the same problem. Did you solved it?
Like, exactly the same... Crazy
Another one
My p8000 also in bootloop after ota update. Only have an old vista PC w8ll dust it off tonight and see what happens
mines doing the same i thought it was too good to be true and it was lol
Cannot get pc (win 10) to install all the drivers, PC cannot see the phone so unable to run flash tool.
Suggestions? I presume the ROM cannot be flashed through the recovery (standard)?
EDIT: Driver package installed by disabling 'driver verification' setting in Windows. Phone only recognised as a MTP USB Device in devide manager, and flash tool does not seem to want to do anything. Might try this on a Win 7 laptop tomorrow. HJow you guys getting on with this?
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
pitrus- said:
download and flash entire rom using sp flash except for data-partition so as you don't lose your data.
Click to expand...
Click to collapse
I have the same boot loop after ota. I did no backup before, so data partition contains my apps right ?
I never used the flash tool , where should I start , any good link for beginners ?
I read some things about the flash options months ago, must I disable/uncheck some options ?
Thanks for help.
same issue
Hi everyone!
I've got the same issue: I allowed the OTA update to 20151105 firmware release from previous version (20150725), after the upgrade, the phone keeps in a bootloop with a new colored Elephone logo.
I can't find a valid set of drivers, I tried a lot over the night, but windows don't recognize the phone.
PLEASE some kind soul could link a valid driver package to use SP tool ?
thanks a lot in advance!
mr..speed said:
I have the same boot loop after ota. I did no backup before, so data partition contains my apps right ?
I never used the flash tool , where should I start , any good link for beginners ?
I read some things about the flash options months ago, must I disable/uncheck some options ?
Thanks for help.
Click to expand...
Click to collapse
kevvyboy said:
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
Click to expand...
Click to collapse
kevvyboy said:
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
Click to expand...
Click to collapse
pretty much did the same thing and it worked!! Cheers!! (also had the rage and it took ages to find english on the tool lol :laugh: )
when you get the android with the "no command" message, let go of the volume and power buttons. Then hold the POWER BUTTON for 1-2 seconds and TAP VOLUME UP while still holding the power button. this will open the recovery options
omg!!
disabling the Windows install signed drivers only setting!!
i thought we wouldnt have to do things like this since Windows 95
Lol
Worked for me
Had I only found this tutorial before yesterday... it took me hours to figure this out.
I can, however, now confirm this works.
Regarding point 5):
(i) Power down phone (ii) start flash tool/go to download tab (iii) select scatter file (iv) hit "download" with no phone attached (v) attach the powered down phone
...and things will be fine. Doing anything fast is not required.
The point is to install SP_Drivers_v2.0 first, as described here. After this, everything goes smooth.
kevvyboy said:
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
Click to expand...
Click to collapse
What if no Windows?
Edit: Never mind, I got myself a windows computer and succeeded. Thanks for all the orientation!
Hi all,
Thanks a lot for posting a solution to this problem so quickly. I am affected by the same issue. Looking to buy some LSD to better enjoy the psychtrip my phone seems to be stuck in. Also looking to fix the phone.
Unfortunately, I'm running Ubuntu 14.04 LTS. I did find a guide to use the flash tool on Ubuntu, but my phone does not seem to connect. I'm guessing this has something to do with that pack of drivers 2.0, for which I have no equivalent. I would really appreciate any ideas!
I might end up returning my phone to Amazon, though. It's only been a few days since I've had it, and you can imagine that although I was really liking it, I'm beginning to change my mind.
Your advice?
EDIT: I am getting the following error message:
BROM ERROR: S_COM_PORT_OPEN_FAIL (1013)
[COM]: Failed to open COM port.
[HINT]:
I did some googling, but didn't find anything worth mentioning.
yslsl said:
Had I only found this tutorial before yesterday... it took me hours to figure this out.
I can, however, now confirm this works.
Regarding point 5):
(i) Power down phone (ii) start flash tool/go to download tab (iii) select scatter file (iv) hit "download" with no phone attached (v) attach the powered down phone
...and things will be fine. Doing anything fast is not required.
The point is to install SP_Drivers_v2.0 first, as described here. After this, everything goes smooth.
Click to expand...
Click to collapse
Ahh good stuff. Connect phone last after hitting download - thanks for the heads up. Got my wife's p8000 today so will be doing some flashing later.
Cheers!