Database Info

stuck on Google logo

After updating around 20 apps (altogether ), I noticed the phone was not functioning normally so I tried to reboot it but now it is stuck on Google logo. I've never unlocked the phone nor used any custom roms. I'm on the latest stock rom 2.3.4
I tried removing the battery and putting it back but didn't work. Vol. up + power and then Recovery didn't work either. It gives me a triangle with ! in it and stops right there.
I also tried the USB Jig that forces the phone into downloading mode but it gave me a screen that asks (Unlock bootloader?) with some warnings but I don't know how to accept that. Niether Vol buttons nor Power button worked there
I didn't want to mess up with the phone until I hear from you guys. Please help

up.......

You might have to actually root it or use the Samsung exe back to factory. That is if you don't want to mess with it because if I ware in your position I'd be going back for a new phone. You did nothing wrong and you have 1 year warranty on it.

FYI, the triangle with ! actually is recovery. The UI is hidden until you hold power and press vol down.

matt2053 said:
FYI, the triangle with ! actually is recovery. The UI is hidden until you hold power and press vol down.
Click to expand...
Click to collapse
Thanks man, I didn't know about that
Is wiping the data (factory reset) going to delete my stuff stored on my SD card? like pic., music, vid. etc?
and do I need to actually wipe the data or will wiping the chache only work?

Factory reset reverts your phone back to the way it was when you got it.
That means all your account settings, device settings, installed applications etc are gone. Everything stored on your SD card will remain there - it's a different storage. The good thing about our Google phones is that you only have to login to Google once and all your stuff is back.
You can try wiping the cache first and see if that works, it won't harm anything. But if that doesn't work, I'm sure a factory reset will.
Good luck.
Greetz

frutelaken said:
Factory reset reverts your phone back to the way it was when you got it.
That means all your account settings, device settings, installed applications etc are gone. Everything stored on your SD card will remain there - it's a different storage. The good thing about our Google phones is that you only have to login to Google once and all your stuff is back.
You can try wiping the cache first and see if that works, it won't harm anything. But if that doesn't work, I'm sure a factory reset will.
Good luck.
Greetz
Click to expand...
Click to collapse
Thanks a lot. I already tried wiping the Cache but it didn't work. I guess I'm going with the factory reset now
Thanks again

the factory reset didn't work !
still stuck on Google logo
any advice?

farisallil said:
the factory reset didn't work !
still stuck on Google logo
any advice?
Click to expand...
Click to collapse
Can you connect your device to your computer via USB and start "adb logcat" at the Terminal/Command prompt? Does it give you any kind of readout at all?

Try doing a hard reset.

GchildT said:
Can you connect your device to your computer via USB and start "adb logcat" at the Terminal/Command prompt? Does it give you any kind of readout at all?
Click to expand...
Click to collapse
I'm not an expert in these things ... is there any post I can follow to do the things you talked about? I'm not sure that I have all the drivers needed on my pc
I do appreciate your help

farisallil said:
I'm not an expert in these things ... is there any post I can follow to do the things you talked about? I'm not sure that I have all the drivers needed on my pc
I do appreciate your help
Click to expand...
Click to collapse
One thing you should consider is just returning the phone, especially if you never flashed or rooted or unlocked bootloader.
Sent from my Nexus S using XDA App

matt2053 said:
One thing you should consider is just returning the phone, especially if you never flashed or rooted or unlocked bootloader.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I would if I was in the States

just unlock it and flash a nice CM7 with Trinity on top
Here's a rooting guide: http://forum.xda-developers.com/showthread.php?t=895545
There's another guide out there for the i9023 (European version).

GchildT said:
Can you connect your device to your computer via USB and start "adb logcat" at the Terminal/Command prompt? Does it give you any kind of readout at all?
Click to expand...
Click to collapse
No. The device doesn't even show up when I type "adp devices"
Is there anything else I should try?

Thanks
I can perform things with Fastboot
I don't want to root or unlock the phone. Is there anything else I can do?
I tried typing Fastboot update update.zip after downloading the stock rom update 2.3.4 and putting it in the SDK tools directory but it gave me the msg "faild to upload update.zip"

Try to reset with Odin.

Device unable to mount SD

So I have ran into a big problem. Yesterday I installed CleanROM 6.0 R2 and everything seemed fine until I woke up this morning. My device was turned off so I charged it a bit and powered it on. It was stuck on the HTC boot screen so I decided to use TWRP to recover the ROM. The problem is it says the SD card is unmounted. I got careless and started trying to wipe the SD card, format it, etc. to no avail. Now I can no longer get into TWRP.
Does anyone have any ideas? I am not sure what to do anymore =(
Related post: http://forum.xda-developers.com/showthread.php?t=2187491

Just an update... tried using ruu and getting error 171, using 2 different PCs. Once it tries to reload boot loader the phone doesn't turn on at all. Manually made no difference. Nothing seems to work. And since relocking the bootloader instead of receiving the error mentioned on the top I get a "remote: signature fail". Something else strange is the HTC boot screen no longer appears, instead going straight into the boot loader.
I've gathered with further tinkering when a command needs to reboot the phone it doesn't do it. I'm now trying to unlock the boot loader again, all goes well until it reboots then nothing happens. It's like it fails to write anything. I think earlier when I messed with TWRP before it stopped working I genuinely screwed something up with the SD card.

Try to hookup the phone to a Windows PC, go to Device Manager, and see if you have the option to format the SD.
EDIT: Just saw here that your main problem is communication between the PC and your phone (which would also explain why you can't mount SD). Try to reinstall HTC Sync, and also try another USB port on the PC.

redpoint73 said:
Try to hookup the phone to a Windows PC, go to Device Manager, and see if you have the option to format the SD.
EDIT: Just saw here that your main problem is communication between the PC and your phone (which would also explain why you can't mount SD). Try to reinstall HTC Sync, and also try another USB port on the PC.
Click to expand...
Click to collapse
The only thing I see listed is "My HTC" no option to do so. If you have anymore ideas please let me know!!

USBDeview
use this software to uninstall all the devices you think are related to your phone. it doesn't physically remove the drivers it will just allow your computer to reconfigure them, see if that helps. even if it doesn't it is a great utility to keep around.

DvineLord said:
USBDeview
use this software to uninstall all the devices you think are related to your phone. it doesn't physically remove the drivers it will just allow your computer to reconfigure them, see if that helps. even if it doesn't it is a great utility to keep around.
Click to expand...
Click to collapse
Hmm, messed around with it a bit, still no luck.

Okkoto said:
Hmm, messed around with it a bit, still no luck.
Click to expand...
Click to collapse
once you uninstalled devices and then replugged in phone how many drivers did it try reconfiguring? did you get any errors?

DvineLord said:
once you uninstalled devices and then replugged in phone how many drivers did it try reconfiguring? did you get any errors?
Click to expand...
Click to collapse
It reconfigured Android 1.0 (My HTC) and QHUSB_DLOAD when I try running the RUU software again.. Something worth mentioning is I've tried 3 different PCs all with HTC sync installed.

Okkoto said:
It reconfigured Android 1.0 (My HTC) and QHUSB_DLOAD when I try running the RUU software again.. Something worth mentioning is I've tried 3 different PCs all with HTC sync installed.
Click to expand...
Click to collapse
remember htc sync is pretty much useless always disable it, all you need are drivers. if u have htc sync installed disable or close it before doing anything important.

DvineLord said:
remember htc sync is pretty much useless always disable it, all you need are drivers. if u have htc sync installed disable or close it before doing anything important.
Click to expand...
Click to collapse
It's not open or anything. At first I just had the basic HTC drivers but been told to have the sync software installed. Either way I'm beginning to think the memory is faulty now, have messed with this thing for to long...

RUU Error 171 Stuck on waiting for boot loader

As the title says, RUU attempts booting my phone but it never comes back on. Even selecting restart boot loader in fastboot or a command it doesn't power itself back on. I have read through other forums and nothing has worked for me yet.
EDIT: I should probably clarify fastboot usb WORKS. Ruu must see my phone considering it detects the ROM version and turns the phone off in attempt to reboot. Anything that I do that requires a reboot doesn't work. I have tried unlocking the bootloader again, everything is fine until it comes to rebooting then I must turn the phone on myself and nothing changes...... IT DOESN'T REBOOT ITSELF therefore seemingly nothing wants to work. And the HTC boot screen is gone??
More background information: http://forum.xda-developers.com/showthread.php?p=39046436#post39046436

What we're your steps exactly? Did you relock your bootloader

a box of kittens said:
What we're your steps exactly? Did you relock your bootloader
Click to expand...
Click to collapse
Yes I did through fast boot with the oem lock command. I've tried installing RUU with a Windows 7 laptop (has HTC sync software) and Windows 8 desktop (basic drivers). Both failed, tried using Windows XP/Vista in compatibility modes and running as an admin with the same results.

Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.

iElvis said:
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
Click to expand...
Click to collapse
No luck. And I believe it does see the phone in the beginning of the installation. It makes it reboot to the boot loader and that's where it loses the connection. The phone just isn't booting itself back up. I appreciate the reply, if you have anymore ideas please let me know.

Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?

iElvis said:
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
Click to expand...
Click to collapse
Re-downloaded RUU and still no go. And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.

Does anybody else have some more ideas?

Okkoto said:
And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Click to expand...
Click to collapse
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.

redpoint73 said:
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
Click to expand...
Click to collapse
Fastboot does see it but adb does not. And what I mean by rebooting the phone in my last post is RUU attempts rebooting it from the boot loader which does turn the phone off but it stays turned off. I've used other commands to reboot the phone from the fastboot screen and those too turn off the phone then again it doesn't come back on like a reboot should do.

I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.

Okkoto said:
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Click to expand...
Click to collapse
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.

DvineLord said:
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
Click to expand...
Click to collapse
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.

i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.

Okkoto said:
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
Click to expand...
Click to collapse
when you say it shows connected through fastboot what do you mean?
how are you getting the device into fastboot - through recovery??
oh, and what was on your device before you tried loading the RUU?

kkm68 said:
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Click to expand...
Click to collapse
Yes this + if you're on a usb3 port try usb2. Also make sure you're using the cable that came with the phone as I understand other cables may cause issues like this. Also, avoid using a hub or usb extension.

Solution to error 171
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!

diegoyabishh said:
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
Click to expand...
Click to collapse
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.

jondon156 said:
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
Click to expand...
Click to collapse
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita

Heisenberg said:
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Click to expand...
Click to collapse
hi all..
facing same problem with HTC Desire 816 n 4g... have anyone got any solution??
plz pass it..
thank you

Help - this is a difficult one

Okay from the top, have OPO that had paranoid 4.6 Beta 2 working just fine. Was playing with settings(dumb idea) and changed the runtime to ART like i have on multiple other phones just to try it out. Phone rebooted and upgraded all the apps like it should, but about 5 seconds after it booted, screen froze for a second and then it rebooted. Once it rebooted it was up for 5 seconds again and then rebooted again. thus started a continues reboot loop.
Using the five seconds i had i was able to race through settings and switch the runtime back to dalvik. this caused the normal reboot and fixing of apps however once it finished the boot process it began the reboot loop again and there was nothing i could do to stop it.
I booted to recovery and attempted to reflash the last update, that failed.
attempted to wipe cache and dalvik cache and that failed.
attempted factory data reset, that failed
NOW is when i made a mistake, on TWRP i checked system wipe as well as data and cache. Wiped everything.
So, phone was then entirely devoid of OS which is a slight problem. I was able to get into fastboot however and flash cm11s which i figured would fix it, false. Now when it boots the system ui crashes over and over continuously and it wont become stable. Went back to recovery but my twrp was gone and i just had cyanogenmod simple recovery. attempted to get to fastboot mode but its apparently nonexistent, i tried every combination of commands possible to get there but cant. so now im stuck with an unusable OS and a useless recovery and no way to get to fastboot mode that im at least aware of... if there are any other details that could help feel free to help, ill post pictures once i figure out a way to do that.
please, for the love of God, help me.

If you gold the power button for about 15 seconds then it should turn off. Then hold volume up and then press and hold power while still holding volume up for a few seconds and it should boot fastboot mode. Try erasing userdata from there to see if you can recover from the crashing.

tiny4579 said:
If you gold the power button for about 15 seconds then it should turn off. Then hold volume up and then press and hold power while still holding volume up for a few seconds and it should boot fastboot mode. Try erasing userdata from there to see if you can recover from the crashing.
Click to expand...
Click to collapse
I tried that a hundred times, the problem is once the screen turns off, if you keep holding vol up it never comes back on, its something i have never seen before and its exxtremely frustrating. Its like fastboot doesnt exist.

I wiped out everything on my Oneplus two months ago by mistake. Then my phone wont boot up because it had nothing in it except the TWRP. I tried EVERYTHING, to load a Rom into the phone, but it didn't work. It goes through the motion of loading a Rom into your phone and when you are about to hit the 100% level, it says FAILED. It wants you to check the debugging which you can't because your phone wont boot up. Anyways, I purchased a micro usb flash drive and loaded up the Rom into flash drive from my comp's usb. Then I connected it to my phone from TWRP via the micro usb port. After it loaded up the Rom from the flash drive, it booted up. Hope that works.

grenademasta said:
I wiped out everything on my Oneplus two months ago by mistake. Then my phone wont boot up because it had nothing in it except the TWRP. I tried EVERYTHING, to load a Rom into the phone, but it didn't work. It goes through the motion of loading a Rom into your phone and when you are about to hit the 100% level, it says FAILED. It wants you to check the debugging which you can't because your phone wont boot up. Anyways, I purchased a micro usb flash drive and loaded up the Rom into flash drive from my comp's usb. Then I connected it to my phone from TWRP via the micro usb port. After it loaded up the Rom from the flash drive, it booted up. Hope that works.
Click to expand...
Click to collapse
hey i hadnt thought of that, thanks ill try that as soon as i can get my hands on a micro usb flash drive, will the device find it using cyanogenmod simple recovery? twrp is gone for some reason.

Don't know if it will work without TWRP. I only see "Apply Update" then "Apply from ADB" and "Choose from internal storage". Hopefully the phone might recognize additional storage from the micro usb flash drive. Good luck.

grenademasta said:
Don't know if it will work without TWRP. I only see "Apply Update" then "Apply from ADB" and "Choose from internal storage". Hopefully the phone might recognize additional storage from the micro usb flash drive. Good luck.
Click to expand...
Click to collapse
thanks for your help! ill update as soon as i get one

The latest twrp supports mtp and you can use adb push to push the file to sdcard. Its really worth learning.

ugly_duckling said:
I tried that a hundred times, the problem is once the screen turns off, if you keep holding vol up it never comes back on, its something i have never seen before and its exxtremely frustrating. Its like fastboot doesnt exist.
Click to expand...
Click to collapse
You should let go of the power button after the device turns off. Then vol up+power when the phone is off. This is different than what I read for the device but it works for getting me in fastboot.

Try flashing it by adb?

Overdose1986 said:
Try flashing it by adb?
Click to expand...
Click to collapse
tried using adb to push files but got error: closed, tried adb kill-server etc to try and get it to work but it wouldnt go, trust me i have tried a lot of things
as for the holding of the volume up button, ive tried every combination of holding and releasing i could think of, it just wont work :/

ugly_duckling said:
tried using adb to push files but got error: closed, tried adb kill-server etc to try and get it to work but it wouldnt go, trust me i have tried a lot of things
Click to expand...
Click to collapse
He meant using adb sideload
Sent from my Oneplus One

have you had a look at my thread here? sure sounds like one of the issues listed. Take a peak and decide if it's something you'd like to try

Makrilli said:
He meant using adb sideload
Click to expand...
Click to collapse
ya i tried, it wouldnt connect to the phone, tried multiple tweaks from pc side and device side and couldnt get it to work, im probably messing it up somewhere but i tried to follow various "tutorials" to the letter

markbencze said:
have you had a look at my thread here? sure sounds like one of the issues listed. Take a peak and decide if it's something you'd like to try
Click to expand...
Click to collapse
Hey thats exactly how it started when i first reflashed cm11, but i managed to get through and force disable audiofx, from there though it just kept crashing system ui, i will definitely try this when i get outta class.
is there something different ill need to do based on having already disabled audiofx?

ugly_duckling said:
Hey thats exactly how it started when i first reflashed cm11, but i managed to get through and force disable audiofx, from there though it just kept crashing system ui, i will definitely try this when i get outta class.
is there something different ill need to do based on having already disabled audiofx?
Click to expand...
Click to collapse
Disabling it will not fix your issue. My thread tells you what needs to happen. Generally when people decide to try new ideas without proper knowledge is when they get into trouble

ugly_duckling said:
I tried that a hundred times, the problem is once the screen turns off, if you keep holding vol up it never comes back on, its something i have never seen before and its exxtremely frustrating. Its like fastboot doesnt exist.
Click to expand...
Click to collapse
Just a tip, if u can go in fastboot mode, try to disconnect usb from phone first , and then try

markbencze said:
Disabling it will not fix your issue. My thread tells you what needs to happen. Generally when people decide to try new ideas without proper knowledge is when they get into trouble
Click to expand...
Click to collapse
ya i gotcha, i was just wondering if i needed to re-enable audiofx for stuff to work, my other problem with this method is, and correct me if im wrong, but i believe i need to be in fastboot mode? which for some reason is unattainable at the moment..

ugly_duckling said:
ya i gotcha, i was just wondering if i needed to re-enable audiofx for stuff to work, my other problem with this method is, and correct me if im wrong, but i believe i need to be in fastboot mode? which for some reason is unattainable at the moment..
Click to expand...
Click to collapse
Yes and then follow the directions in my thread

luka1002 said:
Just a tip, if u can go in fastboot mode, try to disconnect usb from phone first , and then try
Click to expand...
Click to collapse
idk why, but i read this post and said "what the hell, ill try it again" out loud to myself. unplugged my phone, held down the volume up key and turned it on, IT WENT STRAIGHT TO FASTBOOT. fml thanks guys, i think i can fix everything from here...i dont know how i managed to never do it correctly even though before this happened i booted into fastboot regularly to flash different ROMS...thank you guys very much for the help

Oneplus One Freezing On Startup

He there, just recently my phone had an update and i said yes to it. After the update completed It rebooted but never started back up.
When turned on, it just get up to the OnePlus One logo screen and stays there. I have tried a factory reset as I can access the recovery menu but the factory reset doesn't seem to do anything. I let the battery drain until the phone died and then charged it but it still will not start. Plugging it into my PC lets it charge but it does not let you access the storage. Its not a driver problem as it was working fine before the update.
I have tried fast boot but it just gets stuck on the fast boot screen.
I tried using OnePlus One Toolkit but it cant find the phone
I have read that I need to flash it but it would seem I need to transfer a file onto the phone but nothing recognizes the phone to transfer it to.
Can anyone help?
Thanks in advance,

Zastarx said:
He there, just recently my phone had an update and i said yes to it. After the update completed It rebooted but never started back up.
When turned on, it just get up to the OnePlus One logo screen and stays there. I have tried a factory reset as I can access the recovery menu but the factory reset doesn't seem to do anything. I let the battery drain until the phone died and then charged it but it still will not start. Plugging it into my PC lets it charge but it does not let you access the storage. Its not a driver problem as it was working fine before the update.
I have tried fast boot but it just gets stuck on the fast boot screen.
I tried using OnePlus One Toolkit but it cant find the phone
I have read that I need to flash it but it would seem I need to transfer a file onto the phone but nothing recognizes the phone to transfer it to.
Can anyone help?
Thanks in advance,
Click to expand...
Click to collapse
Your persist partition might be corrupt. Grab this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/view?usp=docslist_api
Then do this with fastboot:
Code:
fastboot erase persist
fastboot flash persist persist.img

Didn't work sadly. Maybe I should just flash everything?

Zastarx said:
Didn't work sadly. Maybe I should just flash everything?
Click to expand...
Click to collapse
Yeah, it's worth a shot. You can find full instructions in section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471

Yay!
It worked, thanks a lot!