Database Develop

[Q] 2c.6c Bootloader - Stuck Here

I have a Verizon Droid and am stuck at the 2c.6c bootloader:
http://community.vzw.com/t5/image/s...5A88C6BB44/image-size/original?v=mpbl-1&px=-1
I've tried flashing multiple SBF files using RSD Lite, but the program fails while waiting for "Switching device to BP Pass through" because the Droid reboots into the 2c.6c bootloader.
I've also successfully flashed SPRecovery, and can successfully install the stock 2.0.1 update.zip file, but the phone simply reboots into the 2c.6c bootloader once more.
I'm out of ideas. Any guidance would be appreciated.

Any luck?
I recently had the same thing happen to my phone. Did you find a way to resolve the problem? Feedback would be much appreciated, because as you probably know I'm pretty desperate.

onelegchair said:
I recently had the same thing happen to my phone. Did you find a way to resolve the problem? Feedback would be much appreciated, because as you probably know I'm pretty desperate.
Click to expand...
Click to collapse
I spent hours and hours researching a way to solve this problem, and am sorry to say I found nothing. I think the device is truly bricked.

[Q] [SOLVED] Boot looped, Can't use Recovery mode..

Hi everyone.. after hours and hours of reading and studying on this website I really got myself into a mess and I just can't seem to climb out of it.. I desperately need some grade A help..
To be descriptive, I was trying to flash Serendipity 7, I was following the steps, used odin 3 1.7, I put all the files where they needed be, and followed it down to a tee, I pressed start, and then my phone goes into a boot loop... So I google around to look for solutions, and I thought I found one, well after I flash this "P-SBL.tar.md5" some tar file that is meant to fix the 3 button recovery mode issue. (Basically my cappy can't select anything in recovery mode due to it not having a "ok" button..) So I try it.. and not my recovery mode is littered with multi colored lines.. and I can't seem to get them to go away.
If anyone can help me I would forever be in your debt.. I would be happy just to go back to stock 2.2 if possible.. or perhaps advice on getting serendipity 7 to work.
I could make it happen if only I could get my recovery mode to work. D:
Please anyone help, I'm in dire need..
Thanks!

Search for "stock kb2 adam outler"
Then after you get back to stock, stay that way until you have done about 12 more hrs of research and reading. You were lucky that you didn't hard brick your phone, and you don't realize it. Don't just flash something because you"think"it will fix it. Know what you are flashing and what it will do to your phone. And you can call me an a#&h&$#if you want, but i believe most of the regular users here would agree me.

^
+ 100
Totally agree !!
suoh18, If....wow....whoa....dude don't be so trigger happy to flash. You were this " | " <---(that is a thin thin line by the way) to having a brick.

They need to get rid of that 3 button fix, its bricked more phones than I know, it should include both bootloaders and not just the one, I would contact Adam Outler like mrhaley said, to see if he can help, 3 button fix brick may require a jtag.

I know I was.. I was just reading what everyone was saying how easy it was.. it was my first flash and I guess it just back fired on me.. x_x
I really appreciate your help a ton, you have no clue how thankful I am.
I'm downloading what I need right now and I'm praying it works, thank you again so much.

^
Keep us posted on the end result.

I just used the program.. and it very well got my phone back on the right track. The boot looping stopped, it's back on the recovery mode that I can actually use, but after it loads it just goes to a black screen and keeps vibrating, I read that if it doesn't work the first time to check the flash bootloaders button. so I'm going to reboot one more time, then try that.
Thanks a ton guys, you really are great.
EDIT:
Which I think I need to do, because I still have a weird Galaxy S starting screen that appeared after I tried to flash serendipity.
EDIT 2:
Okay, After re-flashing the bootloaders it removed that screen that shouldn't have loaded, but I still get a black screen after the boot and nothing shows up..
I can enter and exit my recovery and download modes fine..
EDIT3:
Okay.. I went back into recovery mode and literally just wiped everything I could.. cache, user data, internal card, and after I rebooted again, viola it worked.
I'm so happy and I am seriously very appreciative. You guys are great and there has always been a reason why I respect this community so much.
Thanks again everyone that helped me, I don't know how much I can say it, but really, thank you so so so much, you are amazing.

[Q] Very bad brick situation

Hi everyone,
I have in the past switched roms on my Galaxy S before, therefore the issue of bricking my phone is something that doesn't intimidate me too much. However, this time i'm really stumped, and I turn to the gurus here at the forums, hoping a solution can be found.
I had just gotten my phone back from getting its screen repaired (which makes this especially irritating), and my carriers had flashed my phone back to their stock version of android, meaning gingerbread with a lot of bloatware. I decided straight away that I wanted to root my phone today, although I was away from my PC. I had my laptop with me (Macbook Air), but I had never done any flashing from it before, not to mention ever using Heimdall before (I had always flashed with Odin). I downloaded everything, and then I made my first mistake: I flashed a speed mod kernel (I believe it was a froyo kernel), and after reboot my phone wouldn't go past the splash screen. I could still get into recovery and download mode. Then I decided to try playing it safe, and I downloaded stock firmware packages for Heimdall fro the forums here. I tried flashing JVS on my phone, going exactly by the instructions written in that same thread that I found the packages, but the flash didn't succeed. Instead, I got an error message saying the PIT file didn't reach the end of the transfer (or something like that...) and the phone rebooted. After that attempt, the phone went black. Nothing works anymore except for download mode. Now I thought that as long as download mode works, I'll be ok, so I tried flashing different packages through Heimdall, and eventually when I got home I tried using Odin on my PC. The problem is, my PC doesn't recognize my phone anymore (even though the drivers are installed and I never had an issue with that before), so I'm pretty much stuck with a brick for now.
I really don't want to go back to my carrier again, and hope to get my phone back in working order without paying too much. I still think there's hope as long as download mode works.
Does anybody have any suggestions what I might be able to do? Since my PC doesn't recognize my phone (and therefore Odin doesn't either), the only semi-working option left is using Heimdall somehow, but as to how to use it, I'm in the dark.
I would really appreciate any help you guys can give me. Thanks a lot!
Aaron

first try reinstalling the drivers and try again. if you can get download mode, should be repaired.

Thank you very much!!!
I knew that download mode was a good sign, but I started freaking out as soon as Odin wouldn't recognize my phone, since it never has had that problem. Reinstalling the drivers did the trick, and flashing worked.
Sometimes the simplest solution is the best. Again, thanks a lot!

commandozzz said:
Thank you very much!!!
I knew that download mode was a good sign, but I started freaking out as soon as Odin wouldn't recognize my phone, since it never has had that problem. Reinstalling the drivers did the trick, and flashing worked.
Sometimes the simplest solution is the best. Again, thanks a lot!
Click to expand...
Click to collapse
We are here to help.

Need help with bricked Galaxy Note5

Ok so here is some extra information I just learned. I am freaking out a little bit and am stressed over my broken Galaxy Note 5. First off let me explain how this happened my cousin was suppose to download something called SuperSu from this website. He said to flash Supersu into the phone after putting it on the boot mode. Then download stop ROM then flash it in then flash super set download carrier. I am not really sure what any of this means. He was suppose to unlock the phone for me so I could use the phone from sprint to AT&T, but he only got the supersu started and didn't get to finish any of the rest of the downloads at all. I know this information because I got to talk to him before he went away and now I am stuck doing it, but am pretty much clueless the phone is currently stuck like this when it is turned on and I don't know how to fix it. I haven't been on this site to much and am not very familiar so please cut me some slack when helping me. Thank you for any help. Currently the phone just turns on and sits at the Galaxy Note5 loading screen and does nothing else and never finishes turning on.

Try flashing stock ROM via Odin. Just search Google on how to do it. There are plenty of guides that you can find. Make sure to flash the correct stock ROM depending on your device's model

Noob here - screwed up my T-Mobile One M9?

Hi XDA community,
I'm scared out of my mind. Tried rooting for the first time ever, but don't actually know what I'm doing. Using various guides I found in these forums, I:
1. Used HTCdev to unlock the bootloader
2. Used ADB to install TWRP 3.0.2-0
3. Used TWRP to install UPDATE-SuperSU-v2.76.zip
Once that finished, my phone tried booting up (the white HTC logo) but now it has the red development build text at the bottom.... and then it gets into an infinite boot loop.
I don't know how to fix my phone. Please someone here with guidance, please help.

I've got the same identical issue.
I was able to get out of the boot loop by holding volume up and power, and I got back to download mode. From there, since the SU update I tried to install boot looped me (I was following this tutorial), I jumped ahead and just installed cm13 as I was planning to.
This install went fine, but then I ran into the issue of the rom not recognizing my sim card. I've been researching this problem and I guess I need to update my baseband? I tried for hours but I do not know how to accomplish this, and couldn't figure it out for the life of me. This thread on the cyanongenmod forum seemed to be the closest thing to help I could find, but still it didn't help very much.
So at this point now I'm trying to back out and unroot my phone and get everything back to factory settings; it doesn't feel worth it anymore to me since I've just had trouble every step of the way. I've been trying to follow this post to get back to at least a usable factory rom. But I can't even get this one to install because I cannot access my phone through adb while it's in download mode. Furthermore the instructions are just confusing me because I'm not so versed in the nomenclature of these procedures.
Is there anyone that can help me get back to complete stock t-mobile sense? Or if not, help me get my cm13 rom to recognize my sim card so I can at least have my phone working in some capacity? I'd be tremendously grateful of either. I'm really in over my head here and quite scared I won't be able to figure this out.