Develop Bugs

Galaxy Note 2 Superbork

Where to start...
First, as a disclaimer, I may use language or terms that sound noobish. I have rooted and run custom ROMs on several devices in the past, however generally when I get a ROM I like I stick with it, so I'm not constantly tinkering. I've done my best to search and find solutions so please go easy on me.
17 days ago I was running stock 4.3 on my SGNII when the battery died. Upon charging I found I was stuck in bootloop and had a bad /efs mount. I searched and searched and spent around 15 hours trying this and that but to no avail. I finally threw my hands in the air and got ahold of Josh at mobiletechvideos and he was able to fix the efs mount issue. However, he left me in factory mode which required me to root to get out of, and once I did this I was unable to activate data on my carrier (Ting). I was so happy to have my phone "back" though that I used it like this for 4 or 5 days. I could get on wifi and I could call and send text messages. I had been off the grid so this felt like something I'd fix fully later.
Well I kept reading and found "fix" after "fix", flashed this and that and still no dice. FINALLY, last night, I found this thread: http://forum.xda-developers.com/show....php?t=2086769 which helped immensely. I was able to get TWRP flashed by unchecking the "auto-reboot" option in Odin and pulling the battery after the update took, and via TWRP I was able to install the ROM. I booted up, the device activated, I was running 4.1.2, I made and received some calls, the birds were chirping, the air was sweet...
I had struggled for so long and I had finally achieved success! Then, for seemingly no reason at all, I accepted an OTA update which bricked my Note2. Devastation.
The current state of things...
* Cannot get past the initial "Samsung Galaxy Note 2" screen
* Cannot boot into recovery
* I CAN get into dl mode,
* but, I CANNOT successfully flash anything. TWRP will flash like it took, but upon reboot I'm not able to boot into it. I'm also able to flash a ROM but it fails when it gets to sbin, and upon rebooting I'm greeted by the screen "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I try to use Kies it doesn't find the device. I've installed all of the most recent drivers and I'm running Kies as administrator. I select Tools > Emergency Firmware Recovery, THEN connect my device as instructed.
I'm at the apex of frustration. I beg thee to help!!

I have roughly the same situation. Was rooted and on an MK4 rom, battery ran down super fast yesterday and when charged, only get splash screen and slowly flashing blue light. I can get into Philz recovery but no matter what I try, no dice. Also can get into DL mode, but haven't been able to get anywhere. What the heck happened?

Well i bought another phone because of this problem of unknown baseband and 0 for everything in settings which didnt allow me to connect to sprint. Now when that happen it put me in safe mode . and i couldn't find a fix for months i ended up getting a lg g2 and let my note 2 collect dust. Well I'm using my note 2 and its up in running . my partition was messed up . if you have this issue which it sound like i can help. My phone was running fine then rebooted on its own and rebooted on safe mode with no signal
Sent from my SGH-M919 using XDA Premium 4 mobile app

[Q] Touchscreen and sim reader both stopped working at same time

I have the ATT sgh-i747. I was using it as normal. The battery was low and i could not charge it before it got to 0%. After it died, I connected the charger and started it back up. When the screen came on, the "no sim-emergency calls only" message was there and the touch screen did not work. Also, the time and date were off. it said 3:59 September 15th. I tried the normal reset (take battery out, replace, turn back on) several times and still the same thing. I had just replaced the sim reader a month ago, as well as the rear camera and speaker, and everything was working as normal. I opened the phone up to make sure all connections were set. Still the same message. I did a factory reset and after I turned it on, still, the touchscreen does not work and it says no sim. I find it odd that both these things would stop working at the exact same time. Also the phone is long past its warranty. Any ideas on what this could be?

Anyone?

Have you tried flashing another ROM?

I don't know how to do that, if you could point me in the right direction I'd appreciate it.

Before anyone can give you advice, we need as many details as you are able to provide.
Was your phone running a stock ATT ROM? What ROM was it running? Are you able to boot into download mode?

Stock Rom, phone is not rooted and I can boot to download

What stock ROM? It's important that anything you flash does not try to downgrade the bootloader if you were on stock 4.3 or 4.4.

I'm not 100% sure. I want to say 4.3. There was a software update for the phone that automatically downloaded about a week ago but im not sure if that is related.

Since you received an update a week ago, you may be on KK.
I suggest flashing Philz Touch recovery via Odin and see if you can boot into recovery. In recovery you can see if the digitizer responds.
Flash the latest tar version from here in Odin: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/

[Q] Sprint Samsung Note II flash to Metro PCS gone wrong.

Good morning,
A friend of mine went to one those cell phone repair booths in the mall. One of the employees said that he can flash his Sprint Samsung Galaxy Note II to Metro PCS. He charged him 60 dollars and messed up his phone. The employee does not work there anymore and I beleived he did on the side not through the actual store. The cell worked for awhile then started to lag until it would not boot it would stay on the SAMSUNG logo until the battery would die. It seems he flashed without installing recovery and also no usb debugging. When I tried using Android tool kit it asks me to set up usb debugging but since the phone does not fully boot I can't acccess to do it. I tried using odin to install firmware and I started it last night and I checked this morning and it hadn't progressed past 1%. I disconnected it it and now I get this message Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. I know this is due to disconnecting. I still can get into download mode. Is there any solution for this problem I must be missing something I've tried Kies Odin and Android toolkit. Please help I would like to fix the phone for my friend he doesn't have a lot of resources and can't affod another phone.
Thanks.

[Q] help - i think my phone is temporary bricked

hi,
so i just got my s6 edge for sprint shipped to me (it wasn't activated to any service when i got it). here is the order of events i took:
1) tried to activate my service, but there was a delay in porting the #
2) while waiting for them to port it, i rooted it, installed twrp and a rom (this was when it was on 5.0.2)
3) they called and said they were ready to port, but the new rom didn't have the activation software in it. so i stalled them and said i would call back. i then reverted back to stock using odin.
4) got the number ported and was fine using the phone at that point.
5) this is where the day turned bad...... i didn't realize that coincidentally today, a new firmware was released to 5.1.1 and the phone auto-updated to it while i wasn't looking
6) i went to go re-root it using the same 5.02 root and now my phone is stuck. it's sitting on the "Samsung Galaxy S6 Edge, Powered by Android" screen and in the top left in red it says "RECOVERY IS NOT SEANDROID ENFORCING"
7) i tried to restore it back to the stock using odin, but it errored in the download mode (i don't remember the error off hand)
i can get into download mode, and that's about it. i had to let the phone's battery die on it's own to turn it off (this phone gets super hot, btw)
so i guess what i need to know is how to restore back to factory default again, now that it thinks it's on 5.1.1. is there any hope?

I'm in the same boat as you, I think the only hope is to wait until the firmware is available to download and install it via Odin. Let me know if you've had any luck getting it up and running again. I had to switch back to my old phone for the time being.

bbacon said:
I'm in the same boat as you, I think the only hope is to wait until the firmware is available to download and install it via Odin. Let me know if you've had any luck getting it up and running again. I had to switch back to my old phone for the time being.
Click to expand...
Click to collapse
check this post, download the tar and flash it in odin. it worked for my phone!
http://forum.xda-developers.com/showpost.php?p=61650724&postcount=142
it got me into a recovery image that worked and i was able to factory reset in there. my phone is booting properly now. (after it reboots when done, it took a bit on the first title screen to do anything, just be patient)

Thanks man, that worked great. Although I found out in the process of trying to fix it the past few days, I must have flashed a non-compatible kernel because once it boots the touch screen is unresponsive. I guess I'll have to wait until the firmware download is available after all. Thanks again for the help though

My GT-9195L is not working

Hello,
A couple days ago I let my Galaxy S4 mini charging and I went to sleep. When I woke up i found that my phone didn't turn on at all, just vibrated when plugged to the power outlet. After going through hundreds of threads, I got into Download Mode, but I'm stuck since then. I tried flashing Stock ROM and Recovery from Odin, Heimdall and Kies, but no luck, I switched USB ports and cables, switched OS and machine but I couldn't get to flash anything.
When I try to flash from Odin, It detects my phone (I see that "added!" sign) but when it starts, it gets stuck at Initialzation, or SetupConnection. I decided to use Heimdall instead, but it said "couldn't initialise protocol" and it wouldn't do nothing. As a final resource, I installed Kies and used that "Emergency System Restore" or something like that. It downloaded the firmware but at the moment of installing it got stuck at 0%.
I'm running out of ideas and patience, because I can't really know what happened when my phone suddenly stopped working.
Any ideas? I was running stock KitKat 4.4.2 ROM.
Cheers