Database Info

Magic bricked

Test methods need to unbrick my magic, so far I've tried one that I have not worked. If someone want to try things that I communicate them and I try.
After an upgrade of radio has been fried. I can not get into recovery, or fastboot. Even so I try to send commands and the command window stays and even restart <waiting for device> clicking to enter recovery fastboot or does nothing.
Excuse the translation but my English is very bad and I use the google translator

edugg said:
Test methods need to unbrick my magic, so far I've tried one that I have not worked. If someone want to try things that I communicate them and I try.
Click to expand...
Click to collapse
wow so much information don't know where to start!!!

hard to say..someone managed to the the phone to respond to fastboot/adb by starting up ADB..
wait for the waiting for device msg, then connect the phone to usb and turn it on.
if all method fails, bring it back to claim for warranty.

edugg said:
Test methods need to unbrick my magic, so far I've tried one that I have not worked. If someone want to try things that I communicate them and I try.
After an upgrade of radio has been fried. I can not get into recovery, or fastboot. Even so I try to send commands and the command window stays and even restart <waiting for device> clicking to enter recovery fastboot or does nothing.
Excuse the translation but my English is very bad and I use the google translator
Click to expand...
Click to collapse
What OS are you using on your computer?

zeroplace said:
What OS are you using on your computer?
Click to expand...
Click to collapse
I tested with Windows 7, Vista and XP and the same.

You know any way to flash as factory?

Will it actually turn on or does it just flash a red led when you press power?

bonesy said:
Will it actually turn on or does it just flash a red led when you press power?
Click to expand...
Click to collapse
Starts, appears the splash but only gets to that point

In that case it isnt bricked its just stuck...Bricked is when it wont turn on at all
Do you have a nandroid backup?
Have you taken the battery out and the power lead so it has no power?
i have had this problem
If you have a backup get it ready, Once you have let the phone power down totally (battery out and no lead) hold back and press power (keep holding back) this should get you into fastboot.if it doesnt unplug the lead and try again.
If thats successful.... using your nandroid files
FASTBOOT COMMANDS
fastboot erase system -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
Sorry if you cant get this to work i have to go out and wont be back to check till tomorrow so just giving you all the info

bonesy said:
In that case it isnt bricked its just stuck...Bricked is when it wont turn on at all
Do you have a nandroid backup?
Have you taken the battery out and the power lead so it has no power?
i have had this problem
If you have a backup get it ready, Once you have let the phone power down totally (battery out and no lead) hold back and press power (keep holding back) this should get you into fastboot.if it doesnt unplug the lead and try again.
If thats successful.... using your nandroid files
FASTBOOT COMMANDS
fastboot erase system -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
Sorry if you cant get this to work i have to go out and wont be back to check till tomorrow so just giving you all the info
Click to expand...
Click to collapse
I have tried many times to do this and nothing ever stays <waiting for device> and does nothing

Phone is not bricked, so this shouldnt be a problem.
If you cant get into fastboot with current setups, then use another recovery image and a custom rom.
(all that stuff is on SD-card.. its not that hard)
Update SDK.

daihiep said:
Phone is not bricked, so this shouldnt be a problem.
If you cant get into fastboot with current setups, then use another recovery image and a custom rom.
(all that stuff is on SD-card.. its not that hard)
Update SDK.
Click to expand...
Click to collapse
Great! And how should the recovery image and custom rom be put into the Magic? Sledgehammer?
The problem that almost everyone seems to not understand is that it's impossible to access fastboot, adb or any other (known) means.
The magic will hang at the first splashscreen no matter which buttons are pushed during power up. If the track ball is pressed during power on, the led lights up blue (still hanging at first splash). All other combos of buttons during power on makes no difference at all.
I have tried keeping fastboot waiting while power cycling the device (as explained in another thread), but there are no reaction. I have tried in xp, vista and linux.
I have also tried with a gold card, but since the phone seems unable to get any further than the first splash, this will not work.
So unless someone has a _NEW_ method to actually enter fastboot/ADB mode, these devices are BRICKED!
People have been discussing what the criteria for calling a phone a brick, but as far as I have care my Magic can only function as a paper weight and can therefore be called bricked.

Help
I have the same problem , the fastboot can not acces, i stay at the vodafone logo.
Any ideas?
HHHHHHHHHHHEEEEEEEEEEEELLLLLLLLLLPPPPPPPPPP.

frankiboy1 said:
Great! And how should the recovery image and custom rom be put into the Magic? Sledgehammer?
Click to expand...
Click to collapse
take out the sd card, put it in a usb adaptor and copy them over.
Also search for a thread "how i unbricked my phone"

frankiboy1 said:
Great! And how should the recovery image and custom rom be put into the Magic? Sledgehammer?
The problem that almost everyone seems to not understand is that it's impossible to access fastboot, adb or any other (known) means.
Click to expand...
Click to collapse
Think before answering.
Btw, question answered by htcmagic.

daihiep said:
Think before answering.
Btw, question answered by htcmagic.
Click to expand...
Click to collapse
I repeat: The problem that almost everyone seems to not understand is that it's impossible to access fastboot, adb or any other (known) means.
Having a recovery image and a custom rom on the SD card is useless if you are not able to get the phone accessing those files.
I have tried the "how I unbricked my phone" method (like I wrote in my first post) without any success. If you read the whole "how I unbricked my phone" thread you can see that there are several guys that did not have success with this method.
I have done a lot of thinking.... and searching...
Thanks

http://forum.xda-developers.com/showthread.php?t=571457 try there

Wrong HBOOT = real brick
Guys,
With a wrong HBOOT (what happend to me), the phone is a real brick...
And they refused to repair it... I bought a new phone. But I keep the old one in case someone break his screen. Then I can get the mobo.

just curious.
superkikim said:
Guys,
With a wrong HBOOT (what happend to me), the phone is a real brick...
And they refused to repair it... I bought a new phone. But I keep the old one in case someone break his screen. Then I can get the mobo.
Click to expand...
Click to collapse
How did you brick it?
Btw, have you tried to run any RUU update?
At least singapore one.

[Q] Can't unbrick. Tried nigh everything.

Greetings! First of all, I would like to thank anyone who takes the time to help me diagnose and resolve this issues, let alone anyone who takes the time to read this thread.
I've been having issues with my Xoom (ICS 4.0.0) for about 3 weeks now.
A brief history of the issue's occurrence:
-I unrooted the device and returned it to stock.
-Everything was fine and dandy until one day it spontaneously said something along the lines of 'Android is upgrading..', and then performed a reset.
-Since resetting, it bootloops.
The device only turns on when plugged into a charger and hard reset.
The device only turns off when allowed to boot loop for minutes and then hard reset (it simply does not reset, and just turns off).
I'm not the most technically-savvy person with android devices but here are some things I've done/noted.
When trying to use adb commands, it does not recognize the device or properly issue commands.
I've tried wiping data/clearing cache to no avail.
EDIT: I've tried fastbooting, but the bootloader will not unlock. When trying to unlock, it simply resets and then acts as though it was never unlocked.
I have no idea how to return it to a stock image. All I know is that I have a micro-SD and some spare time.
Could anyone help me understand what exactly is going on with my Xoom?
If I can provide you with any more information, please let me know.
Thanks again. (=

If it was stock and spontaneously upgraded it sounds like a bad OTA upgrade. I've been rooted from the start so never have taken an OTA upgrade...don't you need to accept it or can it just upgrade on it's own?
Anyway, can you get it into fastboot mode?
Volume up and power, then at dual core screen, press volume down...if you see something like "entering fastboot mode" you're not bricked. You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
If you haven't done so, just google 'recovering Xoom using fastboot' and you should get some good information.
Good luck!

Remember to grab the MZ604 files if you have the Wifi only version of the Xoom.
http://developer.motorola.com/products/software/ <------ Grab the files here. The files are for the US version of the Wifi Xoom only.
Instructions to return it to stock
1) First you need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
Should have these drivers installed if you have rooted your Xoom before.
2) Make sure you have the latest SDK - adb and fastboot should be in /platform-tools -
http://developer.android.com/sdk/index.html
Should have the android SDK if you have rooted your Xoom before.
3) Place all the downloaded stock image files into the SDK Tools folder.
4) If you are booting up from scratch, you can get the Xoom in fastboot mode by doing the following. Use command prompt to perform the rest of the steps
Hold VolDown and Power button will boot unit for fastboot mode
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
If you Xoom is booted up already follow the commands below using command prompt to perform the steps
adb reboot bootloader <---- reboots the Xoom into fastboot mode.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
As Always If This Was Helpful Hit the Thanks!

Yeah, what Mjamocha said...

okantomi said:
Yeah, what Mjamocha said...
Click to expand...
Click to collapse
LOL Thanks.

okantomi said:
Anyway, can you get it into fastboot mode?
Click to expand...
Click to collapse
Yes, I can. But so far nothing has been successful in terms of fastboot commands.
okantomi said:
You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
Click to expand...
Click to collapse
When I try to execute fastboot commands such as 'fastboot flash boot boot.img'.. it says the following:
Device still locked. Device must be unlocked first. Failed to process command error(0x8)
Whenever I try to unlock the bootloader, it appears to be successful at first and then the device reboots. But it just reboots to a bootloop, and the bootloader still says its locked. Perhaps I made a mistake in communication. The bootloader is currently locked and will not unlock, as just described.
When I try to unlock it and it reboots, even if I access the fastboot menu right away, it still says the device is still locked.
Thoughts?

Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.

slacka-vt said:
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
Click to expand...
Click to collapse
Yes, I can get into android recovery. However, within a second of switching into recovery mode, the robot falls down and there appears to be a red triangle caution sign containing an exclamation point.
When trying to do a factory reset, it says all data is wiped (as normal). Upon rebooting, it continues to bootloop. So essentially the factory reset and cache clear options in the Android Recovery menu do not produce the expected results.
Pretty odd. I didn't mess with the Xoom at all prior to this issue.

Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.

slacka-vt said:
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
Click to expand...
Click to collapse
Yeah, just tried it to no avail. Thanks so much for your help anyway. (=
I'm not sure what to do now.

I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.

slacka-vt said:
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
Click to expand...
Click to collapse
I hear ya. I've tried 2 different cords and 3 different computers. I'm using a Mac (10.6.8) right now, but have used 2 PCs (Vista + 7).

Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?

slacka-vt said:
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
Click to expand...
Click to collapse
I got the 'device still locked' error. Weird, huh?

How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.

slacka-vt said:
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
Click to expand...
Click to collapse
Yeah I tried that. Won't lock or unlock successfully. Locking produces no difference, and unlocking produces the same 'device still locked' error. This is getting out of hand! Thanks so much for your advice. You think I should open it up?

I hate to be so persistently annoying about this, but could anyone possibly suggest a method of working around the locked bootloader?
Is there anything I can do with an SD card to remedy the device's stubborn foolery?

I think you should give it a try, I have bricked my xoom a few times and have always been able to flash the stock imagine to recover. You really have nothing to lose by pulling the battery pin just be careful.
Sent from my Xoom using xda premium

I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?

cherlamperter said:
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
Click to expand...
Click to collapse
I have looking for a utube how to guide but no luck, I just might make one for you so you will know what to expect. Give me a few and I will get back to ya.
Sent from my Xoom using xda premium

Need help getting to stock recovery

Need help...
Was messing the around with the screen density in the buildprop.. after reboot, "systemui keeps FCing" making it unusable and I cant do anything. Attempting to do a hard button combo to go into stock recovery but cant seems to get it to work.. Googleing tells me to, hold volume down and power till the LG logo, release power and rehold again.. it just reboots again.. holding all 3 brings me to a korean menu that I cant read.. holding up and power brings me to a recovery menu that I think only the service centre can use, there's no option in there, only asking me to reboot.
Any kind souls please....

scpion said:
Need help...
Was messing the around with the screen density in the buildprop.. after reboot, "systemui keeps FCing" making it unusable and I cant do anything. Attempting to do a hard button combo to go into stock recovery but cant seems to get it to work.. Googleing tells me to, hold volume down and power till the LG logo, release power and rehold again.. it just reboots again.. holding all 3 brings me to a korean menu that I cant read.. holding up and power brings me to a recovery menu that I think only the service centre can use, there's no option in there, only asking me to reboot.
Any kind souls please....
Click to expand...
Click to collapse
I've been trying to get into my stock recovery for some time now trying all sorts of button combos but to no avail. Previously I had the g2 and when it updated from jellybean to kitkat, the combo for entering stock recovery changed however, this new combo doesn't seem to work on the G Pro 2 either
You should be able to revive your device back to stock using the LG pc Suite however, after tampering with the system, it is often necessary to perform a factory reset after the pc suite has done it's work which will need you to enter stock recovery.
If you are completely stuck, I would suggest restoring your device using the pc suit and, all being well, your device will boot sufficiently for you to perform a reset through the phone settings menu. If you are really lucky, it may boot properly and you may not need to perform any reset however, it would still probably be a good idea to do so.

bobsie41 said:
I've been trying to get into my stock recovery for some time now trying all sorts of button combos but to no avail. Previously I had the g2 and when it updated from jellybean to kitkat, the combo for entering stock recovery changed however, this new combo doesn't seem to work on the G Pro 2 either
You should be able to revive your device back to stock using the LG pc Suite however, after tampering with the system, it is often necessary to perform a factory reset after the pc suite has done it's work which will need you to enter stock recovery.
If you are completely stuck, I would suggest restoring your device using the pc suit and, all being well, your device will boot sufficiently for you to perform a reset through the phone settings menu. If you are really lucky, it may boot properly and you may not need to perform any reset however, it would still probably be a good idea to do so.
Click to expand...
Click to collapse
I cant use the LG Suite... the screen doesnt allow me to choose the connection type.. It just FC constantly.. I am screwed..:crying::crying:

scpion said:
I cant use the LG Suite... the screen doesnt allow me to choose the connection type.. It just FC constantly.. I am screwed..:crying::crying:
Click to expand...
Click to collapse
Think the only option is to send it in officially and say I dun know what happened......

Help
Has anybody found the way to hard-reset D838 from a bootloop? I really cant reach the recovery mode

manas.neo said:
Has anybody found the way to hard-reset D838 from a bootloop? I really cant reach the recovery mode
Click to expand...
Click to collapse
I had tried everything.. Even adb command to reboot into recovery. It just brings me to a broken Android with red triangle. I am starting to think there is no stock recovery built in that is accessible to users..

I am now at the service centre. Well the guy can detect that its rooted.. voids warranty.... But will try to see if he can help to reflash the firmware.. If not have to change hardware and will be chargeable....... Fingers crossed. He did say users are not able to access the recovery..
Guys.. Until there's custom recovery, pls dun mess with it.....

That is really bad. I am stuck at bootloop and unable to reach the recovery mode. I wonder how entire web just talks about a hardreset process that doesnt even work
scpion said:
I had tried everything.. Even adb command to reboot into recovery. It just brings me to a broken Android with red triangle. I am starting to think there is no stock recovery built in that is accessible to users..
Click to expand...
Click to collapse

manas.neo said:
That is really bad. I am stuck at bootloop and unable to reach the recovery mode. I wonder how entire web just talks about a hardreset process that doesnt even work
Click to expand...
Click to collapse
I know.. I was desperate too... There's 2 versions, the other model is f350 or something.. Anyway at the service he did flash the phone again for me foc. BUT! He stamp a big NO WARRANTY as well... Goodbye to my balance 10 months warranty.. Buy hey.. I am grateful that I have my phone working again..I think.
I confirm with him again.. Yes, there is no stock recovery users can access....

scpion said:
I know.. I was desperate too... There's 2 versions, the other model is f350 or something.. Anyway at the service he did flash the phone again for me foc. BUT! He stamp a big NO WARRANTY as well... Goodbye to my balance 10 months warranty.. Buy hey.. I am grateful that I have my phone working again..I think.
I confirm with him again.. Yes, there is no stock recovery users can access....
Click to expand...
Click to collapse
Glad you were able to get your phone back. I have some positive news. I am trying out a recovery method as we speak. Using the LG Software update & USB driver tool I found the option for a update recovery. So I gave the IMEI and it prompted for a connection to the device which wasnt there as the phone is stuck in a boot loop. So I thought if it is going to restore the firmware from PC ( and not OTA) then it at some point of time will take the phone to download mode. So I just put the phone in download mode and VOILA it recognised the connection. And right now it is downloading the recovery firmware. The firmware being downloaded is around 1.5GB which is exactly what size I expected it to be. I have my fingers crossed. Just hope it goes through fine.

manas.neo said:
Glad you were able to get your phone back. I have some positive news. I am trying out a recovery method as we speak. Using the LG Software update & USB driver tool I found the option for a update recovery. So I gave the IMEI and it prompted for a connection to the device which wasnt there as the phone is stuck in a boot loop. So I thought if it is going to restore the firmware from PC ( and not OTA) then it at some point of time will take the phone to download mode. So I just put the phone in download mode and VOILA it recognised the connection. And right now it is downloading the recovery firmware. The firmware being downloaded is around 1.5GB which is exactly what size I expected it to be. I have my fingers crossed. Just hope it goes through fine.
Click to expand...
Click to collapse
As I mentioned in an earliar post on this thread, you can usually get the device into a booting state using the lg pc suite. You will probably have to perform a factory reset but, hopefully, after using the tool, you can access the software factory reset in the settings menu. From past experience with other lg devices, it can often help if you run the recovery more than once in the pc suite.

bobsie41 said:
As I mentioned in an earliar post on this thread, you can usually get the device into a booting state using the lg pc suite. You will probably have to perform a factory reset but, hopefully, after using the tool, you can access the software factory reset in the settings menu. From past experience with other lg devices, it can often help if you run the recovery more than once in the pc suite.
Click to expand...
Click to collapse
Hi Bob,
Yes I think the same option is there in the LG PC Suite as well. But unless you do what I have tried to do it wont recognise a device that has not booted yet. Devices soft-bricked or bootlooping wont be recognised by the PC suite for recovery. But thanks for the tip. I'd keep that in mind and see if it'd need another factory reset after recovery. But it seems like it will be a hard reset done by the recovery happening right now

manas.neo said:
Hi Bob,
Yes I think the same option is there in the LG PC Suite as well. But unless you do what I have tried to do it wont recognise a device that has not booted yet. Devices soft-bricked or bootlooping wont be recognised by the PC suite for recovery. But thanks for the tip. I'd keep that in mind and see if it'd need another factory reset after recovery. But it seems like it will be a hard reset done by the recovery happening right now
Click to expand...
Click to collapse
Good luck. If no joy just try the pc suit. I'm fairly sure I had a success on my old g2 with a similar problem to yours. Can't remember exactly what I did but I kept trying things and eventually the pc suit recognised and sorted my device. Perhaps try to adb reboot recovery with the pc suit on screen??

PC suite and the software update thing didn't work for me. It just refuse to recognize my device. Hope things work out for u!

bobsie41 said:
Good luck. If no joy just try the pc suit. I'm fairly sure I had a success on my old g2 with a similar problem to yours. Can't remember exactly what I did but I kept trying things and eventually the pc suit recognised and sorted my device. Perhaps try to adb reboot recovery with the pc suit on screen??
Click to expand...
Click to collapse
Thanks. I was able to revive my phone. No loss of apps and data. Just the root was lost. Can you tell me what issues you have witnessed after such a recovery that made you to do a factory reset? The phone looks fine at the moment but wonder if it'd end up in a boot loop again.

manas.neo said:
Thanks. I was able to revive my phone. No loss of apps and data. Just the root was lost. Can you tell me what issues you have witnessed after such a recovery that made you to do a factory reset? The phone looks fine at the moment but wonder if it'd end up in a boot loop again.
Click to expand...
Click to collapse
You shouldn't have a problem. I just like to have a clean start and to make sure that there are no alien files left from my previous tampering.

bobsie41 said:
You shouldn't have a problem. I just like to have a clean start and to make sure that there are no alien files left from my previous tampering.
Click to expand...
Click to collapse
It went all smooth. I'd like to shout out to all LG G Pro 2 users to make a note of this method and try it whenever they soft-brick their phones.

service
scpion said:
I know.. I was desperate too... There's 2 versions, the other model is f350 or something.. Anyway at the service he did flash the phone again for me foc. BUT! He stamp a big NO WARRANTY as well... Goodbye to my balance 10 months warranty.. Buy hey.. I am grateful that I have my phone working again..I think.
I confirm with him again.. Yes, there is no stock recovery users can access....
Click to expand...
Click to collapse
Hi there,
I am in the same situation, I can not do the factory reset in any way was mentioned here (pc suite, lg update) in the forum, because there is no connection between the pc and the mobile.
Where you from anyway and which mobile service did you take your phone, how much was the service cost?
THX

david_csaba said:
Hi there,
I am in the same situation, I can not do the factory reset in any way was mentioned here (pc suite, lg update) in the forum, because there is no connection between the pc and the mobile.
Where you from anyway and which mobile service did you take your phone, how much was the service cost?
THX
Click to expand...
Click to collapse
Did you try this:
VOL DOWN + POWER
when LG logo appears release booth keys and wait 2 sec then
VOL DOWN + VOL UP
you should get factory reset screen

[GUIDE] How to recover from OnePlus soft bricked?

I decided to write a guide on how to recover from a bricked OnePlus One. This is my first guide.
About me: I am a newbie on Android.However, the XDA community has taught me a lot about my Android phone for the first month of using it. That's right! I have only been using Android for less than one month so take this guide with a grain of salt. But if you happen to soft brick your One, this is the guide to turn to. I have created two mind-bending/heartbreaking/frightening scenarios that I have experienced. Though, resolved thanks to this community.
Note: This will wipe your phone!
Scenario 1:
Soft bricked, (CM gear keeps spinning but won't boot to lock screen)
Scenario 2: Updated kernel on a non-compatible firmware.
Soft bricked, screen on 1+ logo and won't boot to lock screen.
Solution:
1. Download the toolbox from: (Make sure you download your version)
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
2. Install the file.
3. Disconnect your OnePlus One from computer and power off your phone.
4. Go into Fastboot Mode (Volume Up + Power button) wait on vibrate
5. Plug in your OnePlus One.
6. Locate and open the OPO Toolbox.
7. Click Flash CM XNPH22R.
8. You should see command prompt open, just wait until it finishes doing it's thing.
9. Unplug and power off your phone.
10. Power ON your phone and wait until it prompts you re-setup your phone.
Congrats you have just fixed your phone from a soft brick. Simply follow the video from the link provided on step 1 to re-root your phone.
Note: If you have unlocked your bootloader, you do not need to unlock it again.
How to find out if you have unlocked bootloader:
1. Locate the folder where you installed the OPO Toolbox.
2. Hold Shift and right click on ANY white area within the folder.
3. Left click 'Open command window here'
4. Type:
fastboot oem device-info
If it returns True on tampered. Then you have unlocked your bootloader.
I hope this guide helps solve your soft-bricked problem. Good luck!

I suggest that a mod moves this to the General section

pandasa123 said:
I suggest that a mod moves this to the General section
Click to expand...
Click to collapse
Report the thread if you think its necessary.

Well I got this FAILED in the command line, and afterwards didnt got a re- setup...
what am I doing wrong here?:crying:

Digital Arm said:
Well I got this FAILED in the command line, and afterwards didnt got a re- setup...
what am I doing wrong here?:crying:
Click to expand...
Click to collapse
You don't have an unlocked bootloader.
Transmitted via Bacon

timmaaa said:
You don't have an unlocked bootloader.
Transmitted via Bacon
Click to expand...
Click to collapse
Thx got it:cyclops:

Scenario 2: Updated kernel on a non-compatible firmware.
Soft bricked, screen on 1+ logo and won't boot to lock screen.
Solution:
1. Download the toolbox from: (Make sure you download your version)
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
2. Install the file.
3. Disconnect your OnePlus One from computer and power off your phone.
4. Go into Fastboot Mode (Volume Up + Power button) wait on vibrate
5. Plug in your OnePlus One.
6. Locate and open the OPO Toolbox.
7. Click Flash CM XNPH22R.
8. You should see command prompt open, just wait until it finishes doing it's thing.
9. Unplug and power off your phone.
10. Power ON your phone and wait until it prompts you re-setup your phone.
Congrats you have just fixed your phone from a soft brick. Simply follow the video from the link provided on step 1 to re-root your phone.
Note: If you have unlocked your bootloader, you do not need to unlock it again.
Hi i am stuck in scenario 2...I did all a u said but i cant flash CM XNPH22R ...where do i find this file...i cant find it on my phone either ..pls help ??

Thank god for this thread omg, saved my life

Locked Bootloader
This didn't work...
My phone is Soft Bricked (oneplus logo freeze) locked bootoader and usb debuging is not enabled.
What can I do to fix it??

RiccoSuave said:
This didn't work...
My phone is Soft Bricked (oneplus logo freeze) locked bootoader and usb debuging is not enabled.
What can I do to fix it??
Click to expand...
Click to collapse
But why happened this ? Whats the last actions attempted to do with the phone before the brick?
Tecleado desde mi 1+1.

Champi12301 said:
But why happened this ? Whats the last actions attempted to do with the phone before the brick?
Tecleado desde mi 1+1.
Click to expand...
Click to collapse
I did an ota update and it went in to a boot-loop, so I went into fast-boot and accidentally locked the boot-loader.
I think I have to try to hard-brick it and try the hard-brick solution with the qualcom drivers.

RiccoSuave said:
I did an ota update and it went in to a boot-loop, so I went into fast-boot and accidentally locked the boot-loader.
I think I have to try to hard-brick it and try the hard-brick solution with the qualcom drivers.
Click to expand...
Click to collapse
Then first you need to unlock the bootloader via fastboot,but that action erases all data. I assume,if you modified the boot via fastboot, USB DEBUGGING is working,so after try to do the softbrick tutorial of the thread.
Tecleado desde mi 1+1.

how do i know which tool box version is mine ?
---------- Post added at 07:42 PM ---------- Previous post was at 07:26 PM ----------
i tried the fastboot method, i successfully run alll the commands but still stuck in the bootloop.
i even tried adb, but i cant go into recovery mode for my computer to detect it. The weird thing is i can easily go into the fastboot mode but for some reason i can go into recovery mode. i tried turning of the phone by holding power button too long and then vol down + power button, still no luck, now im stuck with 2 options,
1. the toolkit solution
2. the qualcom thingy. It's been two days without my opo, and i feel so lost ! PLS if anyone sees my comments plss respond to me PLS! i willl forever be grateful to you!

deanwinchester370 said:
how do i know which tool box version is mine ?
---------- Post added at 07:42 PM ---------- Previous post was at 07:26 PM ----------
i tried the fastboot method, i successfully run alll the commands but still stuck in the bootloop.
i even tried adb, but i cant go into recovery mode for my computer to detect it. The weird thing is i can easily go into the fastboot mode but for some reason i can go into recovery mode. i tried turning of the phone by holding power button too long and then vol down + power button, still no luck, now im stuck with 2 options,
1. the toolkit solution
2. the qualcom thingy. It's been two days without my opo, and i feel so lost ! PLS if anyone sees my comments plss respond to me PLS! i willl forever be grateful to you!
Click to expand...
Click to collapse
Did you find a solution ?
I'm facing the exact same issue on my OPO.
>> bootloader locked
>> no recovery
>> impossible to unlock the bootloader
>> OPO stuck at 1+ logo and keep rebooting agin and again and again...
....i think my OPO is dead T_T
Is it a way to force the bootloader unlock ?
Please HELP !!!

Didn't work for me
I'll give the background first as it might help. I long while back I did a manual upgrade to CM12s using the guide in this video "How to Install CM12S on OnePlus One - No Root or TWRP Required, No Data LOSS" from the oneplus exclusive Youtube channel.
It worked great no problems.
I recently I got the OTA update to CM13. There were several features I didn't like so I decided to go back. I repeated the process shown in the video but now my phone gets stuck on the CM logo screen and won't go past. I tried again but the same result. Then (I can see heads shaking, sorry) I tried a factory reset from the recovery screen, still the same goes past the 1+ logo but gets stuck at the CM logo. Then I found this guide, downloaded the toolbox but when I try to plash it says "fastboot is not recognized as an internal or external command.
Any ideas?
Found a link on one of the threads here that said a guide on Reddit was useful, that didn't work as well. I am trying.

All done
davmeva said:
I'll give the background first as it might help. I long while back I did a manual upgrade to CM12s using the guide in this video "How to Install CM12S on OnePlus One - No Root or TWRP Required, No Data LOSS" from the oneplus exclusive Youtube channel.
It worked great no problems.
I recently I got the OTA update to CM13. There were several features I didn't like so I decided to go back. I repeated the process shown in the video but now my phone gets stuck on the CM logo screen and won't go past. I tried again but the same result. Then (I can see heads shaking, sorry) I tried a factory reset from the recovery screen, still the same goes past the 1+ logo but gets stuck at the CM logo. Then I found this guide, downloaded the toolbox but when I try to plash it says "fastboot is not recognized as an internal or external command.
Any ideas?
Found a link on one of the threads here that said a guide on Reddit was useful, that didn't work as well. I am trying.
Click to expand...
Click to collapse
No one replied to this but never mind, took me two days but I now have a working phone. So you can call in the dogs, cheers

hi davmeva
did you fixed your oneplus one till now or not because i have also same situation here and no success till now .
i did by mistake all this stuff and now nothing work still same condition
if you got any solution please share it

Phone will only enter Fastboot, cannot get phone into Flashmode to unbrick

Let me start off by saying that I just got this phone and decided to install a custom recovery and rom on it. As I do with all my phones that allow me to do so. I got the phone with android 4.4.4 on it, rooted it with Kingroot, and proceeded to use the XZDualrecovery tool to install TWRP. After that was all done, I downloaded the Z5 Expierience Rom, and I'm going to take a long shot here and say that I must have majorly missed something. Because after flashing that Rom in TWRP, my phone will do next to nothing. All went fine with the install of the ROM itself. Wiped Dalvik/Cache before restart.
If i hold down the power button I get a single vibration and then the phone does nothing (Does not even turn on backlight). If I plug the phone into my computer the phone will start a sequence of Red (LED), Green (LED), Vibrate. It does this aobut once every second. I can access Fastboot if I hold the volume + button, the LED then goes solid blue and the phone stops the LED - Vibration sequence. The only problem I have, as far as just not being able to Flashtool it back to life is, not being able to get the phone to go into Flashmode. No matter what I do, the phone will not let me get it into Flashmode. Im sure there is a good reason for this, I am just not sure what it is.
I've been flashing Roms and Recoveries since G1 days. I'm usually pretty decent at figuring this kind of thing out, but this thing has got me puzzled. I clearly went terribly wrong somewhere here, hopefully someone who knows this phone much better than I can point me in the right direction and hopefully get my less than 10 hour phone working again.
P.S. - If the phone is plugged into the wallcharger is does something similar to when it is plugged into my computer, but instead of a Sequence of Red - Green - Vibrate, I just get a steady red blink folled by a vibration. The phone will continue to do so until unplugged from the charger.
All help is very appreaciated!

I'm having the same issue. Anyone with the fix would be appreciated

Not sure what to try at this point!
I've been looking non-stop in my free time for a fix for this thing, and no matter what I do I keep getting the same results. Not really sure where to go from here, I have tried Flashtool, Emma, and PC Compainion out of desperaity. I tried all three options on teo seperate computers (One Windows 10 and the other Windows 7.) I have also tried multiple cables. No matter what I do all this thing will do is blink at me and vibrate. Is this thing hard bricked? I read its close to impossible to hard brick one of these phones. I'm wiling to accept that I have if that is the case. Just would like an opinion from someone who has some knowledge with these.

Same here, someone plz help.
If is only a change of batery or the phone is dead completly, an the stop trying to revive it.
Thanks .

Nick1801 said:
Let me start off by saying that I just got this phone and decided to install a custom recovery and rom on it. As I do with all my phones that allow me to do so. I got the phone with android 4.4.4 on it, rooted it with Kingroot, and proceeded to use the XZDualrecovery tool to install TWRP. After that was all done, I downloaded the Z5 Expierience Rom, and I'm going to take a long shot here and say that I must have majorly missed something. Because after flashing that Rom in TWRP, my phone will do next to nothing. All went fine with the install of the ROM itself. Wiped Dalvik/Cache before restart.
If i hold down the power button I get a single vibration and then the phone does nothing (Does not even turn on backlight). If I plug the phone into my computer the phone will start a sequence of Red (LED), Green (LED), Vibrate. It does this aobut once every second. I can access Fastboot if I hold the volume + button, the LED then goes solid blue and the phone stops the LED - Vibration sequence. The only problem I have, as far as just not being able to Flashtool it back to life is, not being able to get the phone to go into Flashmode. No matter what I do, the phone will not let me get it into Flashmode. Im sure there is a good reason for this, I am just not sure what it is.
I've been flashing Roms and Recoveries since G1 days. I'm usually pretty decent at figuring this kind of thing out, but this thing has got me puzzled. I clearly went terribly wrong somewhere here, hopefully someone who knows this phone much better than I can point me in the right direction and hopefully get my less than 10 hour phone working again.
P.S. - If the phone is plugged into the wallcharger is does something similar to when it is plugged into my computer, but instead of a Sequence of Red - Green - Vibrate, I just get a steady red blink folled by a vibration. The phone will continue to do so until unplugged from the charger.
All help is very appreaciated![/QUOTE
!st question is did you flash the correct rom for your device?
If you can go to recovery, then try to flash another rom,
Or use adb/fastboot to try and flash recovery img and use fastboot to reboot recovery.
Alternatively you may have to flash a kernel relevant to your rom.
Click to expand...
Click to collapse

Try this and see if it helps.........
If your phone is unbranded, i.e. not locked to a carrier, download a any generic(customized) firmware for your device through Xperifirm and flash it through Flashtool. It will wipe all your data (excluding your microSD, of course) but you don't have any other choice. This is most probably unbrick it...... So, try it and all the best.:good:
EDIT: If you've tried it, then go for this. Luckily you've fastboot still working, right? So, go to fastboot mode and flash a recovery image through it. It may take a lot of time but if recovery works, you can install a stock based rom for your device and then go back to stock firmware through Xperifirm and Flashtool.....

The phone is a Verizon model. I've tried to unlock the bootloader using command prompt following the sony instructions, after recieving my unlock key. I am able to connect to the phone and all of the fastboot commands work until I try and run the one to actually unlock the bootlaoder. That says the it is "not allowed." I think that is because I never enabled OEM Unlocking in the developers menu though. Not sure if there is a stock kernel I should try an flash through fastboot. Or if there is a stock recovery file that is flashbable through fastboot with a locked bootloader. The phone is definetley working in fastboot and somehow still knows how to charge. Im pretty sure at this point the problem is that the phone has a custom rom on it but the bootloader is still locked. I cannot unlock the bootloader because I can't get in Android to enable the proper options. Have also tried Flashtool for unlock the bootloader, along with extracting kernel sins from a stock 4.4.4 and a stock 5.0.1 FTF and trying to flash them. Since the begining I have still seen no change in the phone behavior.

Nick1801 said:
The phone is a Verizon model. I've tried to unlock the bootloader using command prompt following the sony instructions, after recieving my unlock key. I am able to connect to the phone and all of the fastboot commands work until I try and run the one to actually unlock the bootlaoder. That says the it is "not allowed." I think that is because I never enabled OEM Unlocking in the developers menu though. Not sure if there is a stock kernel I should try an flash through fastboot. Or if there is a stock recovery file that is flashbable through fastboot with a locked bootloader. The phone is definetley working in fastboot and somehow still knows how to charge. Im pretty sure at this point the problem is that the phone has a custom rom on it but the bootloader is still locked. I cannot unlock the bootloader because I can't get in Android to enable the proper options. Have also tried Flashtool for unlock the bootloader, along with extracting kernel sins from a stock 4.4.4 and a stock 5.0.1 FTF and trying to flash them. Since the begining I have still seen no change in the phone behavior.
Click to expand...
Click to collapse
dude I'm from the Verizon side yea like you have an bootloader status unlock no so your not going to change that and you can only flash Verizon z3v stuff you are really lucky if you can still get to fastboot after doing this. Use flashtool and flash a Verizon ROM from the z3v section only and pray it works.