Database Info

[Q] HELP! Verizon Galaxy S 5 Bricked / Stuck In Boot Loop

Problem resolved thanks to bweN diorD!

Dark System said:
Hey everyone, I figured this was the right section to post a question, sorry if I was mistaken.
So I recently rooted my phone and tried to install a custom ROM on it, turns out the ROM I selected was probably for the wrong model or something because my screen was just black. So I booted into recovery to try and restore it on the ROM I backed up and it was gone so now I'm kinda ****ed on a phone for now, before I look into buying a new one I wanna see if there's any way I can resolve this and unbrick it.
When I turn the phone on it just loops the booting screen and when I boot into recovery it just has the droid dude with an exclamation mark on it then turns off and does the boot loop.
I was wondering if maybe there's a file I can put on an external drive and it will automatically restore back to stock like on other devices.
I've done a lot stuff like this to my PS3 just never tried it for my phone so I'm just hoping there's a method out there for me, please provide any feedback or questions about it, I'm just trying to get this resolved and I have no time really to research it because of work and a newborn baby plus you guys would know more about it than me so yeah. Thanks!
Click to expand...
Click to collapse
usually when you flash the wrong software to a phone it is toast, but you may be in luck as it still turns on.
video here.
further instruction here.
if that doesnt work... well its not good unfortunately.

Dark System said:
Hey everyone, I figured this was the right section to post a question, sorry if I was mistaken.
So I recently rooted my phone and tried to install a custom ROM on it, turns out the ROM I selected was probably for the wrong model or something because my screen was just black. So I booted into recovery to try and restore it on the ROM I backed up and it was gone so now I'm kinda ****ed on a phone for now, before I look into buying a new one I wanna see if there's any way I can resolve this and unbrick it.
When I turn the phone on it just loops the booting screen and when I boot into recovery it just has the droid dude with an exclamation mark on it then turns off and does the boot loop.
I was wondering if maybe there's a file I can put on an external drive and it will automatically restore back to stock like on other devices.
I've done a lot stuff like this to my PS3 just never tried it for my phone so I'm just hoping there's a method out
for me, please provide any feedback or questions about it, I'm just trying to get this resolved and I have no time really to research it because of work and a newborn baby plus you guys would know more about it than me so yeah. Thanks!
Click to expand...
Click to collapse
Boot into bootloader and flash stock rom using odin..

bweN diorD said:
solution
Click to expand...
Click to collapse
Alright thank you! I'm pretty confident this will work, once the stock ROM file finishes downloading, which it doesn't seem that it wants to work. I've downloaded it 5 times now and every time it's done it's a fail.. I'll keep trying though.

bweN diorD said:
if that doesnt work... well its not good unfortunately.
Click to expand...
Click to collapse
yeah it didn't work, did everything right but when it tries to reboot I get the dead little droid guy.

[Q] Not able to repair brick on m2 2302

Hi everybody!
I'm rather new here and I need help.
I think I soft bricked my device. After getting my unlock code from Sony, I unlocked it via adb. So far so good. After that I installed CWM and a zip. After that I couldn't boot my phone. I've tried everything. Used Flashtool to flash a firmware for my model to make it work again. Unfortunately, after the flashing was done, I ha got another issue. The Sony logo just pops up, goes out, pops up and so on... No I can't access even recovery mode anymore, even though I have a unlocked bootloader...
Can you guys please help me? I'm just 13 and my parents aren't really happy about what I did to my new fancy phone.
I appreciate it, thanks.

Look at this!!
Rasmulus said:
Hi everybody!
I'm rather new here and I need help.
I think I soft bricked my device. After getting my unlock code from Sony, I unlocked it via adb. So far so good. After that I installed CWM and a zip. After that I couldn't boot my phone. I've tried everything. Used Flashtool to flash a firmware for my model to make it work again. Unfortunately, after the flashing was done, I ha got another issue. The Sony logo just pops up, goes out, pops up and so on... No I can't access even recovery mode anymore, even though I have a unlocked bootloader...
Can you guys please help me? I'm just 13 and my parents aren't really happy about what I did to my new fancy phone.
I appreciate it, thanks.
Click to expand...
Click to collapse
Please look at this
http://forum.xda-developers.com/showthread.php?t=2771449

Thanks, but will this work on 2302, too?
kum4423 said:
Please look at this
http://forum.xda-developers.com/showthread.php?t=2771449
Click to expand...
Click to collapse
I used almost that same file just for my model, and it was the one that made my phone not able to use recovery mode, but thanks:

replace 「D2305」 for 「 D2302」
Rasmulus said:
I used almost that same file just for my model, and it was the one that made my phone not able to use recovery mode, but thanks:
Click to expand...
Click to collapse
replace 「D2305_18.0.A.1.30_Global Generic」 for 「 D2302_18.0.B.1.23_Global Generic」
D2302_18.0.B.1.23_Global Generic.ftf
DL:ttps://yadi.sk/d/2Gf6ZgrbTjMyA
Please use it at your own risk.

Didn't work
kum4423 said:
replace 「D2305_18.0.A.1.30_Global Generic」 for 「 D2302_18.0.B.1.23_Global Generic」
D2302_18.0.B.1.23_Global Generic.ftf
DL:ttps://yadi.sk/d/2Gf6ZgrbTjMyA
Please use it at your own risk.
Click to expand...
Click to collapse
But thanks for your effort.

You could try flashing a KK ftf (18.3.xxxx) instead of JB (18.0.xxxx). Either download one from the index thread or download yourself using xperifirm and pack it with flashtool.

Thanks! I'll give it a try
Crim Soukyuu said:
You could try flashing a KK ftf (18.3.xxxx) instead of JB (18.0.xxxx). Either download one from the index thread or download yourself using xperifirm and pack it with flashtool.
Click to expand...
Click to collapse
I think that might be it because I already updated android to Kitkat 4.4 :good:
Edit: It worked! Thank you so much!

[Q] [HELP] I can't turn on my 1+1 (no fastboot, adb, just 1 vibrate)

Hi guys,
I have flashed latest firmware for cm12 by boeffla (23rd JANUARY) on cm11s (because kernel doesn't work without it) and there was bugged one thing ... For now you will facepalm yourself a lot. I was disappointed from the bugged logo which i wanted to fix by flashing logo from 44S. I thought that this flash will solve that, but the reality is bad, i have bricked it (phone just vibrate on start, no fastboot/adb). I read about this and the only way to fix it (I think, thread "?is saying that?") is JTAG.
Can I fix it only with JTAG (I hope that the way is real) or is there other way to solve this ? (I know, I have bricked it for stupid reason, I am beginner and sorry for my bad english.).
Thanks

iD PropheCy said:
Hi guys,
I have flashed latest firmware for cm12 by boeffla (23rd JANUARY) on cm11s (because kernel doesn't work without it) and there was bugged one thing ... For now you will facepalm yourself a lot. I was disappointed from the bugged logo which i wanted to fix by flashing logo from 44S. I thought that this flash will solve that, but the reality is bad, i have bricked it (phone just vibrate on start, no fastboot/adb). I read about this and the only way to fix it (I think, thread "?is saying that?") is JTAG.
Can I fix it only with JTAG (I hope that the way is real) or is there other way to solve this ? (I know, I have bricked it for stupid reason, I am beginner and sorry for my bad english.).
Thanks
Click to expand...
Click to collapse
This may sound obvious but can you somehow reach the recovery?

Watermelons said:
This may sound obvious but can you somehow reach the recovery?
Click to expand...
Click to collapse
Hmm, I tried it few times, but it doesn't work....
I was reading some threads and I think that I found solution, I will try it.

iD PropheCy said:
Hmm, I tried it few times, but it doesn't work....
I was reading some threads and I think that I found solution, I will try it.
Click to expand...
Click to collapse
If you are able to solve it please post the answer here so you can help people with similar problems.
Good luck!

Watermelons said:
If you are able to solve it please post the answer here so you can help people with similar problems.
Good luck!
Click to expand...
Click to collapse
This is the solution :highfive: :
http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136
Thanks a lot @netbuzz and @darkobas !

iD PropheCy said:
This is the solution :highfive: :
http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136
Thanks a lot @netbuzz and @darkobas !
Click to expand...
Click to collapse
That solution by @netbuzz now has a dedicated thread too:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Transmitted via Bacon

iD PropheCy said:
Hi guys,
I have flashed latest firmware for cm12 by boeffla (23rd JANUARY) on cm11s (because kernel doesn't work without it) and there was bugged one thing ... For now you will facepalm yourself a lot. I was disappointed from the bugged logo which i wanted to fix by flashing logo from 44S. I thought that this flash will solve that, but the reality is bad, i have bricked it (phone just vibrate on start, no fastboot/adb). I read about this and the only way to fix it (I think, thread "?is saying that?") is JTAG.
Can I fix it only with JTAG (I hope that the way is real) or is there other way to solve this ? (I know, I have bricked it for stupid reason, I am beginner and sorry for my bad english.).
Thanks
Click to expand...
Click to collapse
I have the same problem as you. My OPO will not show anything on the screen, when I hold the power button I get one vibrate and that is it! Where you able to recover? I am very very interested in knowing? If so, I have looked at the guide up and down and I cannot understand the guide that was posted, It seems that the program MSM8764 tool does not work or does not like me. I look forward to your reply. Thank you greatly.

gcampo703 said:
I have the same problem as you. My OPO will not show anything on the screen, when I hold the power button I get one vibrate and that is it! Where you able to recover? I am very very interested in knowing? If so, I have looked at the guide up and down and I cannot understand the guide that was posted, It seems that the program MSM8764 tool does not work or does not like me. I look forward to your reply. Thank you greatly.
Click to expand...
Click to collapse
Your computer must recognize OPO as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008 (try to turn it on/off a lot of times by clicking volup and power (10s) until your PC will recognize it) then you need to install drivers from Color.zip (It is in drivers.iso, extract it, auto installation is chinese (I had to disable driver signature enforcement on win 8.1.)) and you will be able to run chinese utility which will flash ColorOS. I did it like this and my OPO is fully working.

Not recalled one, APX mode!! HELP!!!

Hello, everybody!
My new tablet, it is not recall one, i received from nvidia because i have a recalled tablet, it is already killed.
But now, my new tablet also sticking in APX mode, i used a nvidia toolbox from a person to flash the first version about this tablet, when it finished, i rebooted my tablet, the screen became black, and never show anything, can't enter fastboot mode, my PC show APX!
What i can do now???:crying::crying::crying:

What toolbox and what firmware? What did you do, step by step, to get in this state?

lafester said:
What toolbox and what firmware? What did you do, step by step, to get in this state?
Click to expand...
Click to collapse
A Chinese man uploaded it on a website, he said this toolbox can flash the first version of this tablet, when i run the flash.bat, the cmd window showed many, system.img is 900+M but was separated as 90+m and flashed many times, also userdata.....
I want to show you a picture about the cmd window when i flash this img, but i don't know how to upload a picture.....sorry:crying::crying::crying:

nobody......

wyy1993 said:
nobody......
Click to expand...
Click to collapse
Have you tried forcing boot into fastboot with volume down?
Was the replacement a K1 and did you flash a ROM for the original?
Anything else you can tell us about this mysterious Chinese man's website? Maybe post a link.
Still got that pic of the console output or a text version?
Any other info that can help us to help you?

durgis said:
Have you tried forcing boot into fastboot with volume down?
Was the replacement a K1 and did you flash a ROM for the original?
Anything else you can tell us about this mysterious Chinese man's website? Maybe post a link.
Still got that pic of the console output or a text version?
Any other info that can help us to help you?
Click to expand...
Click to collapse
I can't forcing boot into fastboot, i tried power button and volume down, nothing happened, the screen always black...
I think the partition is broken, i don't know the replacement is or not K1, but i flashed the original version....
I used this toolbox: http://bbs.gfan.com/android-8245744-1-1.html V2.3
Thanks for your attention!

wyy1993 said:
I think the partition is broken, i don't know the replacement is or not K1, but i flashed the original version....
I used this toolbox: http://bbs.gfan.com/android-8245744-1-1.html V2.3
Click to expand...
Click to collapse
I think you might be right about the partitions being wrong. The easiest way to distinguish the tablet is that the original has a stylus and K1 does not.
I couldn't read much on that forum, but it specifically calls out "nv-recovery-image-shield-tablet-k1-factory0_0_0.zip". So you might have flashed a recovery/rom for the wrong device and bricked it.

durgis said:
I think you might be right about the partitions being wrong. The easiest way to distinguish the tablet is that the original has a stylus and K1 does not.
I couldn't read much on that forum, but it specifically calls out "nv-recovery-image-shield-tablet-k1-factory0_0_0.zip". So you might have flashed a recovery/rom for the wrong device and bricked it.
Click to expand...
Click to collapse
so, do you think my tablet is broken? Forever broken?

wyy1993 said:
so, do you think my tablet is broken? Forever broken?
Click to expand...
Click to collapse
Someone else may come along with a better idea, but I think it's is beyond my abilities.

durgis said:
Someone else may come along with a better idea, but I think it's is beyond my abilities.
Click to expand...
Click to collapse
Okay...anyway, thanks for your reply!

[Q][**IMP**] Weirdly Hard Bricked my OnePlus One [Non Recoverable]

Hey guys,
I recently bricked my OnePlus One. I can boot into fastboot but not in recovery, so I did what most of you guys would do, flashed the fastboot ROM through fastboot. Still I wasn't able to boot into recovery, but just fastboot. (I'm still stuck in OnePlus logo if booted normally).
So what I tried next is the Hard Brick guide. Again the same problem.
I don't know what the problem is now. Can anybody please find a solution for this or suggest something?
I'm really worried, I just bought OnePlus One an year back, it's been 1 yr 2 month, now that I don't have my warranty I don't know what to do.
Any suggestions are welcome.

Minimilised_MR said:
Hey guys,
I recently bricked my OnePlus One. I can boot into fastboot but not in recovery, so I did what most of you guys would do, flashed the fastboot ROM through fastboot. Still I wasn't able to boot into recovery, but just fastboot. (I'm still stuck in OnePlus logo if booted normally).
So what I tried next is the Hard Brick guide. Again the same problem.
I don't know what the problem is now. Can anybody please find a solution for this or suggest something?
I'm really worried, I just bought OnePlus One an year back, it's been 1 yr 2 month, now that I don't have my warranty I don't know what to do.
Any suggestions are welcome.
Click to expand...
Click to collapse
You can try this guide, i can open the spoiler in EDGE browser , is one of the orange steps
---------- Post added at 05:07 PM ---------- Previous post was at 05:02 PM ----------
kapetz25 said:
You can try this guide, i can open the spoiler in EDGE browser , is one of the orange steps
Click to expand...
Click to collapse
cant post link because im a new user )))), the info is on the oneplus forum, you can search in google for full "guide setting drivers up unlocking bootloader lashing recovery roms kernels rooting" , by DaxNagtegaal

Minimilised_MR said:
Hey guys,
I recently bricked my OnePlus One. I can boot into fastboot but not in recovery, so I did what most of you guys would do, flashed the fastboot ROM through fastboot. Still I wasn't able to boot into recovery, but just fastboot. (I'm still stuck in OnePlus logo if booted normally).
So what I tried next is the Hard Brick guide. Again the same problem.
I don't know what the problem is now. Can anybody please find a solution for this or suggest something?
I'm really worried, I just bought OnePlus One an year back, it's been 1 yr 2 month, now that I don't have my warranty I don't know what to do.
Any suggestions are welcome.
Click to expand...
Click to collapse
What caused the device to brick?

Mr.Ak said:
What caused the device to brick?
Click to expand...
Click to collapse
Water damage.

Minimilised_MR said:
Water damage.
Click to expand...
Click to collapse
https://forums.oneplus.net/threads/...ol-restore-stock-cm11s-fix-bricks-etc.237827/
This is probably the best get.I always use this in case fastboot doesn't work.
Important-Always use win7 or winXp and run the program as Administrator.
Good Luck!

If it was damaged by water, some hardware could be permanently damaged, so you cannot fix it by software.
By the way, good luck.

Hugomm said:
If it was damaged by water, some hardware could be permanently damaged, so you cannot fix it by software.
By the way, good luck.
Click to expand...
Click to collapse
Yes I know. I just got it checked, it's the Motherboard. So it's no use repairing it now. RIP OnePlus One