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.

HTC One X Not Power On

Hello All,
Mine one friend is trying to flash custom rom in his AT&T One X and he hard bricked it, the phone is not responding on any key combination and also not booting directly in recovery. He was using TWRP Recovery and trying to flash this rom
http://onexroot.com/one-x-roms/icecoldjelly-aokp-rom-for-rooted-one-x-android-4-1-2/
Can anyone body help me in this regard or tell me any method which will work ?
Any help in this regard would highly appreciated.
Thanks in Advance.
Imk

imk79 said:
Hello All,
Mine one friend is trying to flash custom rom in his AT&T One X and he hard bricked it, the phone is not responding on any key combination and also not booting directly in recovery. He was using TWRP Recovery and trying to flash this rom
http://onexroot.com/one-x-roms/icecoldjelly-aokp-rom-for-rooted-one-x-android-4-1-2/
Can anyone body help me in this regard or tell me any method which will work ?
Any help in this regard would highly appreciated.
Thanks in Advance.
Imk
Click to expand...
Click to collapse
When you plug it into your USB cable do you have the charging light?
Also that rom is for the Tegra One X not the Dual Core Adreno One X, i've done this before and if im still right you can get into download mode you can go back to stock.

MrKickstand said:
When you plug it into your USB cable do you have the charging light?
Click to expand...
Click to collapse
No nothing is happen. Phone is giving no response

imk79 said:
No nothing is happen. Phone is giving no response
Click to expand...
Click to collapse
Hmm... Ok, on your computer go into Device Manager and plug in your phone to the PC and tell me what kind of sound it makes when it connects and if the device shows a triangle with a "!" in it on the device manager.

MrKickstand said:
Hmm... Ok, on your computer go into Device Manager and plug in your phone to the PC and tell me what kind of sound it makes when it connects and if the device shows a triangle with a "!" in it on the device manager.
Click to expand...
Click to collapse
When I connect the device nothing happened and device showed like in the attached screenshot.

imk79 said:
When I connect the device nothing happened and device showed like in the attached screenshot.
Click to expand...
Click to collapse
Ok, im pretty sure you can recover from that, especially since when i bricked mine it made an abnormal sound when i connected the usb and not the normal boobooop. Try ADB rebooting into bootloader mode or plug it into the USB Cable and Hold the Power + UP + DOWN at the same time and it should still push you into recovery mode. Also download the stock RUU, some of them have a bat you can run and itll do most of the work all you need to do is get into bootloader mode.

MrKickstand said:
Ok, im pretty sure you can recover from that, especially since when i bricked mine it made an abnormal sound when i connected the usb and not the normal boobooop. Try ADB rebooting into download mode or plug it into the USB Cable and Hold the Power + UP + DOWN at the same time and it should still push you into recovery mode. Also download the stock RUU, some of them have a bat you can run and itll do most of the work all you need to do is get into download mode.
Click to expand...
Click to collapse
Can you pls guide me about ADB Rebooting how can I perform it also I did Volume Down+ Power and Volume Down + Up + power button but nothing happen

imk79 said:
Can you pls guide me about ADB Rebooting how can I perform it also I did Volume Down+ Power and Volume Down + Up + power button but nothing happen
Click to expand...
Click to collapse
I didnt mean download mode since im still thinking about the S3, but i mean bootloader. But first off i assume you already have ADB and the Android SDK. So go into your android folder -> platform tools -> hold shift and right click in while your in platform tools and click Open Command Window here and once the window is open type in ADB Reboot Bootloader and see what it does. (i assume that while flashing a rom you had debugging enabled." BUT, also go here and download a RUU http://forum.xda-developers.com/showthread.php?t=2119610 , (id use AT&T USA and the 1.85.502.3 RUU, just click right under OTA and to the right you'll see "DOWNLOAD" and run that EXE to see if it works)

MrKickstand said:
I didnt mean download mode since im still thinking about the S3, but i mean bootloader. But first off i assume you already have ADB and the Android SDK. So go into your android folder -> platform tools -> hold shift and right click in while your in platform tools and click Open Command Window here and once the window is open type in ADB Reboot Bootloader and see what it does. (i assume that while flashing a rom you had debugging enabled." BUT, also go here and download a RUU http://forum.xda-developers.com/showthread.php?t=2119610 , (id use AT&T USA and the 1.85.502.3 RUU, just click right under OTA and to the right you'll see "DOWNLOAD" and run that EXE to see if it works)
Click to expand...
Click to collapse
Can you pls give me a link how to install ADB I remember once I have installed for my LG G2x but not sure is still exsist or not ? Can you pls tell me where is this Android Folder in my system ?

imk79 said:
Can you pls give me a link how to install ADB I remember once I have installed for my LG G2x but not sure is still exsist or not ? Can you pls tell me where is this Android Folder in my system ?
Click to expand...
Click to collapse
Here ya go.
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/

MrKickstand said:
Ok, im pretty sure you can recover from that,
Click to expand...
Click to collapse
You would be incorrect. QHSUSB_DLOAD mode after flashing IceColdJelly meant fo the ENDEAVORU is a death sentence. The device is in fact hard bricked, meaning the only fix is sending the phone for JTAG. The exception, is if the phone was originally on hboot 1.09 (somewhat unlikely at this point, unless the phone was pretty old).
http://forum.xda-developers.com/showthread.php?t=1974101
Couple mistakes were made here that led to this fatal condition:
1) Can't say this enough: DO NOT install mods from random websites. As clearly demonstrated here, these other random websites don't clearly delineate between the EVITA and ENDEAVORU, and this can brick your phone. Stick to the proper device forum on XDA.
2) Why did the person try to install a version of ICJ from 8 months ago? Unless you are doing it for a specific reason, installing obsolete firmware is kinda asking for problems, as well.

redpoint73 said:
You would be incorrect. QHSUSB_DLOAD mode after flashing IceColdJelly meant fo the ENDEAVORU is a death sentence. The device is in fact hard bricked, meaning the only fix is sending the phone for JTAG. The exception, is if the phone was originally on hboot 1.09 (somewhat unlikely at this point, unless the phone was pretty old).
http://forum.xda-developers.com/showthread.php?t=1974101
Couple mistakes were made here that led to this fatal condition:
1) Can't say this enough: DO NOT install mods from random websites. As clearly demonstrated here, these other random websites don't clearly delineate between the EVITA and ENDEAVORU, and this can brick your phone. Stick to the proper device forum on XDA.
2) Why did the person try to install a version of ICJ from 8 months ago? Unless you are doing it for a specific reason, installing obsolete firmware is kinda asking for problems, as well.
Click to expand...
Click to collapse
Thanks for the info
Any other solution rather then Jtag ?

imk79 said:
Any other solution rather then Jtag ?
Click to expand...
Click to collapse
If you originally rooted (or later RUUed) to 2.20 firmware or later, than no. If you were on 1.85 or 1.73 firmware, you can try the unbricking thread and/or JET tool. Unbricking thread is linked in the ICJ "warning" thread I posted above. JET tool can be found in the Development forum.

[Q] Softbricked. What to do?

After a bad root-attempt it seems that my bootloader is damaged. It happens when I used Oneplus One toolkit 1.6. I need help!
The phone is stuck I a startup loop. I can’t enter recovery mode but I can come in to fastboot mode. When I use the command “fastboot oem device-info” I can see that the bootloader is tempered but not unlocked. It seems that I cant unlock it. Because when I use the command “fastboot oem unluck” the phone just reboot into a new loop. Under “Unlocking the device” stage 7 is says “A disclaimer will display on the device that must be accepted.” That never happens with my phone.
wiki.cyanogenmod.org/w/Install_CM_for_bacon
What can I do!?

gunvald89 said:
After a bad root-attempt it seems that my bootloader is damaged. It happens when I used Oneplus One toolkit 1.6. I need help!
The phone is stuck I a startup loop. I can’t enter recovery mode but I can come in to fastboot mode. When I use the command “fastboot oem device-info” I can see that the bootloader is tempered but not unlocked. It seems that I cant unlock it. Because when I use the command “fastboot oem unluck” the phone just reboot into a new loop. Under “Unlocking the device” stage 7 is says “A disclaimer will display on the device that must be accepted.” That never happens with my phone.
wiki.cyanogenmod.org/w/Install_CM_for_bacon
What can I do!?
Click to expand...
Click to collapse
I see this is you first post here in xda and wish it was a better one than this but there are threads on how to fix your issue. May I suggest in the future you do a little more research prior to doing anything with your expensive phones. Sorry to sound like an ass but I see this happen so often. Now to help you out
1 Download all the fastboot images for your phone and flash each other to restore your phone to stock http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
2 Here is the thread you should of read and used prior to doing anything http://forum.xda-developers.com/showthread.php?t=2788632
Good luck and be careful

playya said:
I see this is you first post here in xda and wish it was a better one than this but there are threads on how to fix your issue. May I suggest in the future you do a little more research prior to doing anything with your expensive phones. Sorry to sound like an ass but I see this happen so often. Now to help you out
1 Download all the fastboot images for your phone and flash each other to restore your phone to stock http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
2 Here is the thread you should of read and used prior to doing anything http://forum.xda-developers.com/showthread.php?t=2788632
Good luck and be careful
Click to expand...
Click to collapse
Yes you are absolutely right. I should have read more before trying to root it. What is done is done and now I try to learn from my misstates and save my phone from the garbage can. All help is very appreciated!
Regarding your links, they were unfortunately not helpful in my case. As every other guide I have read they all assume that the bootloader is unlocked or that is possible to unlock it with the “fastboot oem unluck” command. Which in my case seems impossible/hard to do. The question is why I can’t unlock the bootloader or/and how can it be done?

gunvald89 said:
After a bad root-attempt it seems that my bootloader is damaged. It happens when I used Oneplus One toolkit 1.6. I need help!
Click to expand...
Click to collapse
This is what happens when you use "toolkits".
It's much easier to learn what you should do vs clicking a button or hitting "1" on your keyboard.

mbudden said:
This is what happens when you use "toolkits".
It's much easier to learn what you should do vs clicking a button or hitting "1" on your keyboard.
Click to expand...
Click to collapse
^^^This
While toolkits may seem like they make things easier, they're not always reliable, and they allow the user to skip over some really crucial learning experience from doing things manually.
Transmitted via Bacon

http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909 is a good read.

timmaaa said:
^^^This
While toolkits may seem like they make things easier, they're not always reliable, and they allow the user to skip over some really crucial learning experience from doing things manually.
Transmitted via Bacon
Click to expand...
Click to collapse
To replay to the several message that is wrong to use toolkit. I understand you all and obviously now with results to hand it is obvious that it wasn’t the best thing to do. With my prior phone SGS3 I first did everything the manual way and then I was spoiled with a wonderful toolkit from the xda moderator, mskip, that did everything I did but faster.
Please don’t kick a man when he’s down. If someone have any idea to fix this then please write here.

gunvald89 said:
To replay to the several message that is wrong to use toolkit. I understand you all and obviously now with results to hand it is obvious that it wasn’t the best thing to do. With my prior phone SGS3 I first did everything the manual way and then I was spoiled with a wonderful toolkit from the xda moderator, mskip, that did everything I did but faster.
Please don’t kick a man when he’s down. If someone have any idea to fix this then please write here.
Click to expand...
Click to collapse
Try reading this thread http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
I'm not entirely sure what is going on in the thread. It says toggle, so maybe you could toggle the tamper bit closes and try to unlock again.
It would also be possible to boot the recovery without loading it on the phone.
This uses the command "fastboot boot recovery.img" rather than flash. Then from there you could use TWRP's recover to to play with stuff.

abcarter said:
Try reading this thread http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
I'm not entirely sure what is going on in the thread. It says toggle, so maybe you could toggle the tamper bit closes and try to unlock again.
It would also be possible to boot the recovery without loading it on the phone.
This uses the command "fastboot boot recovery.img" rather than flash. Then from there you could use TWRP's recover to to play with stuff.
Click to expand...
Click to collapse
Thanks for your replay! I’m looking in to this now

gunvald89 said:
To replay to the several message that is wrong to use toolkit. I understand you all and obviously now with results to hand it is obvious that it wasn’t the best thing to do. With my prior phone SGS3 I first did everything the manual way and then I was spoiled with a wonderful toolkit from the xda moderator, mskip, that did everything I did but faster.
Please don’t kick a man when he’s down. If someone have any idea to fix this then please write here.
Click to expand...
Click to collapse
On further reading, It seems you'd push the zip to reset the tamper flag:
adb push FILENAME.zip /sdcard/
Then you'd boot TWRP
"fastboot boot recover.img"
Then you'd flash the file.
I've not used this personally, I have booted a recovery through adb, which is how I rooted my phone without unlocking the bootloader.

I'm sure it is just a typo, but as you spelled it several times in this thread like this I just have to ask.
You're not actually typing "fastboot oem unluck" when trying to unlock your phone, are you? :silly:
Cause that would kinda explain why you're so unlocky with it.

gunvald89 said:
To replay to the several message that is wrong to use toolkit. I understand you all and obviously now with results to hand it is obvious that it wasn’t the best thing to do. With my prior phone SGS3 I first did everything the manual way and then I was spoiled with a wonderful toolkit from the xda moderator, mskip, that did everything I did but faster.
Please don’t kick a man when he’s down. If someone have any idea to fix this then please write here.
Click to expand...
Click to collapse
Nobody is kicking you when you're down, just providing good information for people to learn from.
Transmitted via Bacon

I really hope that you will find your solution mate...Just read here and there and be confident.
Anyways, this is my second experience with phone rooting (prior my OPO i had a SGS4) and at the moment of rooting the phone i did not trust all these toolkits, i just dont feel safe using commands written by other people.
I guess i was right...
Best of luck!

gunvald89 said:
Please don’t kick a man when he’s down. If someone have any idea to fix this then please write here.
Click to expand...
Click to collapse
Who's kicking you when you're down?
We're just replying just in case someone else comes by this thread and doesn't understand the risks of "toolkits".
Just because something is faster, doesn't mean it's the best route.
Just like the toll on the highway. Faster but gonna cost you in the end.

[armitage] said:
I'm sure it is just a typo, but as you spelled it several times in this thread like this I just have to ask.
You're not actually typing "fastboot oem unluck" when trying to unlock your phone, are you? :silly:
Cause that would kinda explain why you're so unlocky with it.
Click to expand...
Click to collapse
Hehe that right my spelling is quite bad. Unfortunately that was not the problem here even if my spelling in this thread is really bad… Have to start reading more books or something
Following this guide right now
https://forums.oneplus.net/threads/install-adb-drivers-for-windows-8-1-64-bits.51264/

abcarter said:
On further reading, It seems you'd push the zip to reset the tamper flag:
adb push FILENAME.zip /sdcard/
Then you'd boot TWRP
"fastboot boot recover.img"
Then you'd flash the file.
I've not used this personally, I have booted a recovery through adb, which is how I rooted my phone without unlocking the bootloader.
Click to expand...
Click to collapse
Fist of. Thanks for all your help!
I am trying to push it but now it seems that my mobile isn’t correctly connected. When I run adb devices my phone doesn’t come up the list. It has been there before but I believe I have to fix this before anything else

gunvald89 said:
Fist of. Thanks for all your help!
I am trying to push it but now it seems that my mobile isn’t correctly connected. When I run adb devices my phone doesn’t come up the list. It has been there before but I believe I have to fix this before anything else
Click to expand...
Click to collapse
Download this: theyre the drivers for USB from Google.
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Then unpack the file and go into Hardware manager. Right click on your android device connected with USB and select upgrade drivers. Select the folder that you previously unpacked and select ADB drivers.
Do the same but in this case for Fastboot-bootloader driver version if you cant find your fastboot device after rebooting into bootloader via ADB.
It's not fully detailed as a guide but if you're at least a minimum used to manage peripherals in windows you will not have any problem in using the drivers.

Well done....
The first person who bricked the Opo, writing three lines of code...
Dont know how is that possible

gunvald89 said:
Yes you are absolutely right. I should have read more before trying to root it. What is done is done and now I try to learn from my misstates and save my phone from the garbage can. All help is very appreciated!
Regarding your links, they were unfortunately not helpful in my case. As every other guide I have read they all assume that the bootloader is unlocked or that is possible to unlock it with the “fastboot oem unluck” command. Which in my case seems impossible/hard to do. The question is why I can’t unlock the bootloader or/and how can it be done?
Click to expand...
Click to collapse
The guide I provided does not require you to have a unlocked bootloader. This is to restore phone to 100% stock and is done in fastboot with fastboot commands. Are you sure you read it right
Straight from Cyanogen themselves right here
Code:
Instructions:
First time flashing CyanogenMod 11S on your device, or coming from another ROM (e.g. ColorOS)?
Download the file cm-11.0-XNPH25R-bacon-signed-fastboot.zip to your PC from the links below
Reboot your device into Fastboot mode by holding PWR+VOL-UP
Connect your device via USB to your PC
Unpack the downloaded zip
Open a command prompt (Windows) or terminal (Linux/Mac) and perform the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot update cm-11.0-XNPH25R-bacon-signed-fastboot.zip

DuckMcQUack said:
Download this: theyre the drivers for USB from Google.
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Then unpack the file and go into Hardware manager. Right click on your android device connected with USB and select upgrade drivers. Select the folder that you previously unpacked and select ADB drivers.
Do the same but in this case for Fastboot-bootloader driver version if you cant find your fastboot device after rebooting into bootloader via ADB.
It's not fully detailed as a guide but if you're at least a minimum used to manage peripherals in windows you will not have any problem in using the drivers.
Click to expand...
Click to collapse
Thanks your suggestion. I tried that and is just says that I have the same driver installed. Also tried to uninstall every driver that has anything to do with google android and phones and then reinstall. I also tied to install from my Android SDK folder but I got the same message.
playya said:
The guide I provided does not require you to have a unlocked bootloader. This is to restore phone to 100% stock and is done in fastboot with fastboot commands. Are you sure you read it right
Straight from Cyanogen themselves right here
Code:
Instructions:
First time flashing CyanogenMod 11S on your device, or coming from another ROM (e.g. ColorOS)?
Download the file cm-11.0-XNPH25R-bacon-signed-fastboot.zip to your PC from the links below
Reboot your device into Fastboot mode by holding PWR+VOL-UP
Connect your device via USB to your PC
Unpack the downloaded zip
Open a command prompt (Windows) or terminal (Linux/Mac) and perform the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot update cm-11.0-XNPH25R-bacon-signed-fastboot.zip
Click to expand...
Click to collapse
Oh nice. I will try that after i get the drivers up and running!

Partially Bricked Nexus 5

I never tried flashing a custom kernel before on my phone, but I downloaded Code Blue last night latest (615 I think) and I tried flashing it this morning. I have MultiROM installed with TWRP. When I rebooted my phone, MultiROM came up and I selected my internal 4.4.4 stock ROM. It then went to a black screen and stayed there for about 5 minutes until I rebooted the phone. Now I am currently sitting at a "Google" logo and the phone is completely stuck and won't move. I'm guessing the kernel wiped MultiROM or it wasn't compatible and now it's trying to boot something that is corrupted.
What's weird is, if I go into TWRP and go to MultiROM, it tells me it isn't installed.
Does anyone know how to fix this

I tried downloading MultiROM uninstaller tool and lo and behold, my data wont mount in TWRP on my laptop or desktop to put it on there :'(
Is there anyway to install the uninstaller without it on my internal

snappycg1996 said:
I tried downloading MultiROM uninstaller tool and lo and behold, my data wont mount in TWRP on my laptop or desktop to put it on there :'(
Is there anyway to install the uninstaller without it on my internal
Click to expand...
Click to collapse
Hello,
use wugs nexus toolkit, you can flash back to stock with this tool.
There ist a point named flash stock and unroot, there you must set the point by current status, bricked/bootloop.

Freddy Krüger said:
Hello,
use wugs nexus toolkit, you can flash back to stock with this tool.
There ist a point named flash stock and unroot, there you must set the point by current status, bricked/bootloop.
Click to expand...
Click to collapse
Thank you for the reply just to ensure, this will wipe everything right is there any way to save my data

I really don't know much about multitom.. But just use adb to pull your sdcard data then factory reset.
You could return to stock but please don't use toolkit as mentioned above. I'm really not sure why people insist on this being then answer.
2 links in my signature. 1 about why toolkits are not the answer. Another about guides and info threads. You can read about fastboot and adb. There and never think about pesky toolkits again.
Also no such thing as partially bricked. Its either bricked or not. This is not. Just a boot loop

do not use root toolkits. the reason you listed your phone as "partially bricked" is because you dont know better. a phone is either completely bricked or not. you do not learn how to do things using root toolkits. root tooolkits are not meant for noobs. what you want to do is flash the factory img via fastboot while you are in the bootloader.

Your phone isn't bricked at all, it can be easily fixed.
1) Downlaod 4.4.4 stock rom for nexus 5 on the offical site : https://developers.google.com/android/nexus/images
2) Unzip the folder and click the "flash all.bat" file inside the folder. This will install 4.4.4 on your nexus 5. (connect nexus 5 to your computer first)
3) You're done. (During the installation process from flash.all, all your data will be deleted).
So next time you get bricked, you can rely on that flashall bat but in the future, read the general info in the forums about how to use adb and fastboot without flashall.bat so you can unbrick your phone in minutes.
Link for all the general info you need to know : http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527
EDIT: Nvm, others have already explained above

rootSU said:
I really don't know much about multitom.. But just use adb to pull your sdcard data then factory reset.
You could return to stock but please don't use toolkit as mentioned above. I'm really not sure why people insist on this being then answer.
2 links in my signature. 1 about why toolkits are not the answer. Another about guides and info threads. You can read about fastboot and adb. There and never think about pesky toolkits again.
Also no such thing as partially bricked. Its either bricked or not. This is not. Just a boot loop
Click to expand...
Click to collapse
How could I go about pulling the sdcard and resetting that would save data
I have no idea at all how to do those things, kind of in the dark without being able to mount anything. I just don't want to lose anything if it's possible, and if I wipe the phone, I have a feeling MultiROM will still be there. I'll check out the links

snappycg1996 said:
How could I go about pulling the sdcard and resetting that would save data
I have no idea at all how to do those things, kind of in the dark without being able to mount anything. I just don't want to lose anything if it's possible, and if I wipe the phone, I have a feeling MultiROM will still be there. I'll check out the links
Click to expand...
Click to collapse
Like I said, there's a guides and info link in my signature. If you click that and then read "adb and fastboot. What is it?" - all your answers are there..

rootSU said:
Like I said, there's a guides and info link in my signature. If you click that and then read "adb and fastboot. What is it?" - all your answers are there..
Click to expand...
Click to collapse
Thank you so much for your help, I really do appreciate it. however I installed abd and I went into TWRP and went to abd sideload and I typed in CMD "abd devices" and it don't show my phone, it shows "adb devices attached" but no serial numbers. Is there something I must do before it will show up
btw, I always typed abd wrong lol and it never showed up. I felt dumb when I realized it's actually adb.
EDIT fastboot works just fine showing serial numbers adb still nothing..

snappycg1996 said:
Thank you so much for your help, I really do appreciate it. however I installed abd and I went into TWRP and went to abd sideload and I typed in CMD "abd devices" and it don't show my phone, it shows "adb devices attached" but no serial numbers. Is there something I must do before it will show up
btw, I always typed abd wrong lol and it never showed up. I felt dumb when I realized it's actually adb.
Click to expand...
Click to collapse
No idea what happens when you enter adb sideload. That's not what you should be doing. Just test adb from the main menu of TWRP. If no devices, driver, USB issue.

rootSU said:
No idea what happens when you enter adb sideload. That's not what you should be doing. Just test adb from the main menu of TWRP. If no devices, driver, USB issue.
Click to expand...
Click to collapse
When I enter recovery on my laptop and desktop, it makes the "usb failed sound" the du du dun. Not sure if that is my problem. Is there anyway to fix the issue I think it isn't possible with fastboot to put stuff on any storage.

snappycg1996 said:
When I enter recovery on my laptop and desktop, it makes the "usb failed sound" the du du dun. Not sure if that is my problem. Is there anyway to fix the issue I think it isn't possible with fastboot to put stuff on any storage.
Click to expand...
Click to collapse
Fix the drivers

rootSU said:
Fix the drivers
Click to expand...
Click to collapse
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.

snappycg1996 said:
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.
Click to expand...
Click to collapse
Its all in my "adb and fastboot" thread. I thought you were reading it?

snappycg1996 said:
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.
Click to expand...
Click to collapse
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2

jmtjr278 said:
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
The universal naked driver is already linked in my thread that he was supposed to be reading

jmtjr278 said:
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
LOL. They're directly linked in rootSU's thread.
EDIT: rootSU beats me to it again. One day my friend, one day, I'll learn to type faster.

rootSU said:
Its all in my "adb and fastboot" thread. I thought you were reading it?
Click to expand...
Click to collapse
Maybe my phone is just done for. I download that driver and another one from a different thread and everytime I try to update it is says "nothing is found for your Nexus 5". If I'm in the bootloader it shows "Android Composite Device" with no yellow exclamation mark, however when I try to update there is just says everything is up to date. So I know the drivers work, but what I don't get is why it won't update.

theesotericone said:
LOL. They're directly linked in rootSU's thread.
EDIT: rootSU beats me to it again. One day my friend, one day, I'll learn to type faster.
Click to expand...
Click to collapse
Maybe one day you'll have as little to do on a Sunday as me and you'll beat me tonight

Softbricked my nexus 5? Any help?

So i'm not super competent in adb and what not, but just competent to use wuggs toolkit. I went to google's website to download lollipop 5.0 for my nexus 5. Then i set the phone back to stock, flash 5.0 and its running well. Then i go back in to settings, developer options, and to root my nexus 5 and install TWRP on it through wuggs. Now it has twrp, but will not boot up past the google name with the unlock. I only have the fastboot page and TWRP. The big kicker here is that my pc says does not recognize device and it flickers back and forth with connection every two seconds to my PC. When i go into device manager it shows android device though. So well hey i figure since i have a softbricked nexus i'll just click the button for it and reset. Well it wont do it, it pulls up fastboot.exe goes through a few commands, some saying it failed then it stops and windows tells me to close fastboot.exe
Any help from the very respected XDA?

oh, gawd.. fastbooting a factory img would have been so much faster. sorry, toolkit, i cant help you with it.

hayden55 said:
So i'm not super competent in adb
Click to expand...
Click to collapse
There's your answer right there. That's how ppl like Op brick their devices everyday

Do some research, read read and lastly Read
If you can adb the factory image you can adb a recovery. Google how to. Its literally one comand line.
Stop tossing the word bricked around, a brick is a phone that doesn't turn on and don't blame other things if you don't know how to use them.
Google is your best friend. No one is going to hold your hand.

jayRokk said:
Do some research, read read and lastly Read
If you can adb the factory image you can adb a recovery. Google how to. Its literally one comand line.
Stop tossing the word bricked around, a brick is a phone that doesn't turn on and don't blame other things if you don't know how to use them.
Google is your best friend. No one is going to hold your hand.
Click to expand...
Click to collapse
aww but i really wanted a hand hold.

hayden55 said:
aww but i really wanted a hand hold.
Click to expand...
Click to collapse
here is an extra long :highfive: for your hand holding

chapelfreak said:
here is an extra long :highfive: for your hand holding
Click to expand...
Click to collapse
Hey thanks bud! Problem was it couldnt connect to the computer for more than 5 seconds...
SOO.... i messed with mounting an OTG jump drive and it had my old TWRP back with android 4.4.4. IT Worked!
p.s. i tried just mounting system data etc... the turn on mtp connection button and it Would show up better than just plugging in but couldnt download anything big. and no adb connection

dicecuber said:
There's your answer right there. That's how ppl like Op brick their devices everyday
Click to expand...
Click to collapse
i do not need your input if you aren't going to contribute to the problem just antagonize the op

Current problem at hand: phone now will only connect to pc for 5 seconds at a time. What could do this and how do I reflash to normal?

Still using toolkits?

hayden55 said:
i do not need your input if you aren't going to contribute to the problem just antagonize the op
Click to expand...
Click to collapse
It's a suggestion

Disclaimer: I use OS X/Terminal to fix these things normally and honestly found that after the initial learning curve, it's easier than using Windows or Wugfresh. I'm not a developer, just a hobbyist user.
Make sure you're using an OEM cable to connect to the computer if you're getting dropouts. Also, attempt to uninstall and reinstall OEM drivers (I believe Wugfresh has instructions on how to do this) for Windows.
If you have confirmed that you have TWRP 2.8.1.0 installed, try to boot to TWRP --> ADB Sideload. Connect phone to computer, open Terminal/Console and type the command 'adb devices' (without the apostrophes. I haven't used Windows since I stop using Wugfresh, so the command probably differs). If the device can be seen through this, you should be able to return to the bootloader and start issuing fastboot commands to flash the image.
Let me know how I can help!