Develop Bugs

Soft brick Gnote 3 Neo???

Hi,
a friend of mine had an issue with his Gnote 3 Neo (N7505XEF). Restart again and again and again.
I saw it and I said that I was able to fix it.
Went to recovery, wipe data/cache.
Reboot, and phone starts an update of sytem.
Before the end, bootloop on "galaxy note 3 lite" screen. Noway to have "samsung" bootanimation.
I ask him if he had installed an app recently. No for 4/5 days, and no issue since.
An OTA came sometimes ago and no issue with it.
So, I took his phone and expect to flash a stock firmware with odin. That what I've done with latest french firmware (5.1.1)
Reboot and.... bootloop
Sometimes, bootanimation "samsung" appears but doesn't go to the end of process, and restart the phone in "galaxy note 3 lite".
I wiped everything, test some others firmwares from 4.4.2 to 5.1.1.
I can always enter recovery and download mode, but the issue is usually the same, bootanimation doesn't finish.
I search everywhere but found nothing.
I remember with my old Gnote 2 that I had to install stock recovery once to solve a starting problem, but here, I can enter recovery, so I don't think that it is the same error.
Perhaps a kernel issue? I don't know, and I can't find them on the web!!
The phone has always been full stock, with no tweaks (root, custom recovery or rom....) The issue arrives without any signs. Hardware problem? Perhaps, but never been drown or wet....
What do you think I can do to solve this? Cause at the moment, I don't see haw I can!!
Thanks for all.
Yoh from France.
Excuse my bad english.

Keep trying and making a factory reset could help after installing a new rom. But I can't see more things.
Excuse my english, I'm french

[Soft-Brick] Stuck at boot screen

Hi guys,
(Samsung S4 Mini GT-i9190)
I could really use some help.
I have been searching all over and perhaps I'm not understanding what is being said so if it sounds familiar and there is a solution then i'm thankful.
So about a week ago, the phone came back from repairs and had the motherboard replaced after the phone was washed by accident. Nonetheless, there hasn't been any hardware defects besides signal loss now and then.
When the phone came back, it had 4.2.2 and it automatically picked up the update to 4.4.2 which I did. The phone worked fine until 2 days ago, where it just stuck at the Samsung galaxy gt-i9190 screen and just freezes there.
I can boot into a custom recovery (Philz) (not stock recovery for some reason) and download mode. I then attempted to install CM 11.0 as I got frustrated. It worked, booted past animated logo and install the apps until i came to the language section where the touchscreen which didn't work (unresponsive). I then reverted back to the stock ROM found at sammobile (i9190xxxCOD2XFA - South Africa), loaded the custom recovery and still no booting past the first screen. The custom recovery touchscreen (Philz) is also non responsive (besides using the volume keys, home button and power for navigation).
I flashed a couple of times, nothing works.
Is there a root cause to these issues? The unresponsive screen, not booting properly?
Some info: KNOX is voided 0x1
Please help!! Thank you in advance

It's not „root“ that cause your problem. You should have to choose right recovery for your model. Flash back to original ROM and look for one of fully supported custom ROM here on the XDA and fallow all steps how to flash it properly. Succes ! Cheers !

Alright, I'll try that. What I did in the meantime was flash, Slimkat 4.4.4 UNOFFICIAL rom for I9190 (http://forum.xda-developers.com/showthread.php?t=2708677).
The rom booted into the andoird system but the touchscreen is still unresponsive.
@Boombastical .. If you can help me by giving me a guide in order to do what you say, then please do help. Even in recovery especially TWRP the touchscreen is unresponsive except for ClockWorkMod and Philz. So i don't know if it is hardware related or I'm doing something wrong.
Its driving me crazy :crying:

Update
So what I did last night:
I loaded the SlimKat rom and based on the stock bootloader and after doing a couple of battery pulls the screen starting functioning properly. However it was just luck or could've been something more technical.
I need help in understanding why that happened.
Then I decided I dont trust my method and reloaded the stock 4.4.2 firmware from sammobile. What then happened, is that it booted past the "Galaxy GT-I9190" screen into the samsung logo and then installed the applications. Come to the choose language screen, the touchscreen became once again unresponsive.
Bear in mind, that when I did a reboot with the stock rom, it didn't want to boot past the screen and just hung there.
So what could my problem be?
Is it the rom that I used? Using Unified Android Tool, I saw my region code is GB which I haven't seen anywhere in the stock roms.
Could the system somehow become corrupted? Emmc, partitions? Could the screen calibration be out of sync?
Must the bootloader always be the stock one? Are there custom bootloaders that one can use?
Please help, thanks

GeezyTab88 said:
So what I did last night:
I loaded the SlimKat rom and based on the stock bootloader and after doing a couple of battery pulls the screen starting functioning properly. However it was just luck or could've been something more technical.
I need help in understanding why that happened.
Then I decided I dont trust my method and reloaded the stock 4.4.2 firmware from sammobile. What then happened, is that it booted past the "Galaxy GT-I9190" screen into the samsung logo and then installed the applications. Come to the choose language screen, the touchscreen became once again unresponsive.
Bear in mind, that when I did a reboot with the stock rom, it didn't want to boot past the screen and just hung there.
So what could my problem be?
Is it the rom that I used? Using Unified Android Tool, I saw my region code is GB which I haven't seen anywhere in the stock roms.
Could the system somehow become corrupted? Emmc, partitions? Could the screen calibration be out of sync?
Must the bootloader always be the stock one? Are there custom bootloaders that one can use?
Please help, thanks
Click to expand...
Click to collapse
Possible solution:
So I thought it could be screen calibration so this is what I did to make my phone work.
I loaded the CARBON Rom as I somehow lost root privileges with SlimKat. It loaded into the OS as per normal but the touch screen didn't work. So after numerous battery pulls, i read this post http://forum.xda-developers.com/showthread.php?t=2353972&page=1 .
So then I connected the phone to the pc (having had the samsung drivers installed as well as adb) and booted into cmd promt as admin.
This is what I did in cmd prompt:
cd adb
adb shell (make sure there is a "#" as that ensures you that your phone is rooted)
echo 0 > /sys/class/sensors/proximity_sensor/prox_cal (did this several times)
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal (did this several times)
@xcxa23
It then still didn't work (the touch screen) then somewhere on one of the pages in the above post, someone mentioned holding home button. I switched the phone off, I then held the home button (until it booted into the OS) and then powered the phone on. The phone booted into the OS and presto the screen worked again. I did a reboot and the screen is still fine.
Again I'm not sure if its that exact method but what I am sure of, is that I did a clean rom install (an option in Philz touch recovery), wiped the cache, formatted the options (boot, system, cache, preload, data) in mounts and storage and then proceeded to install the rom from the sd card.
I haven't tried with the stock rom as yet so if this helps you, goodluck and if you can help improve on this method or help me understand why this is happening, it would also be appreciated.
Thanks

Confirmed for that is
GeezyTab88 said:
Possible solution:
So I thought it could be screen calibration so this is what I did to make my phone work.
I loaded the CARBON Rom as I somehow lost root privileges with SlimKat. It loaded into the OS as per normal but the touch screen didn't work. So after numerous battery pulls, i read this post http://forum.xda-developers.com/showthread.php?t=2353972&page=1 .
So then I connected the phone to the pc (having had the samsung drivers installed as well as adb) and booted into cmd promt as admin.
This is what I did in cmd prompt:
cd adb
adb shell (make sure there is a "#" as that ensures you that your phone is rooted)
echo 0 > /sys/class/sensors/proximity_sensor/prox_cal (did this several times)
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal (did this several times)
@xcxa23
It then still didn't work (the touch screen) then somewhere on one of the pages in the above post, someone mentioned holding home button. I switched the phone off, I then held the home button (until it booted into the OS) and then powered the phone on. The phone booted into the OS and presto the screen worked again. I did a reboot and the screen is still fine.
Again I'm not sure if its that exact method but what I am sure of, is that I did a clean rom install (an option in Philz touch recovery), wiped the cache, formatted the options (boot, system, cache, preload, data) in mounts and storage and then proceeded to install the rom from the sd card.
I haven't tried with the stock rom as yet so if this helps you, goodluck and if you can help improve on this method or help me understand why this is happening, it would also be appreciated.
Thanks
Click to expand...
Click to collapse
Hey guys, just a quick update.
I reloaded Cyanogenmod mod CM13. I can confirm that my screen didn't freeze up and booted perfectly. I also then decided to take a chance adn reload the stock rom 4.4.2 and it also worked perfectly and booted directly into the OS.
I'm guessing the screen calibration was out.
So if this happens to you, I would suggest loading a custom rom and doing the screen calibration reset through adb and then test again with another custom rom. Once you comfortable, you can reload a stock rom.
I used Philz Touch for recovery
Thanks to everyone who put posts up .. Time to rest

Not working again!!
Hey,
So in my previous post I said I got it to work. Well I did, up until a few minutes ago when the phone just decided to freeze up again. I restarted the phone and would you know, back to square one!
I've noticed issues that I'm wondering if they could be the problem:
1) The audio didn't work at all. By audio, I mean the mic. When I did voice recording, it just gave static, whatsapp calls, the other person can't hear you as well as regular phone calls.
2) I just rooted the phone in order to change the audio_policy.cnf and delete lines relating to the above audio problem but then the screen, return, and menu button didn't function. The screen could still rotate until I pressed the power button to lock then unlock and then it didn't unlock :crying:
So once again, some help guys please. Is it rom related, hardware (motherboard, chip) or software that just isn't working right? Could it be KNOX?
Thanks

Am confused, old rom still intact after flashing + Samsung Galaxy tab 3 SM-T111

Hi prospective helpers
I have a Samsung Galaxy tab3 SM-T111, it was given to me by my school loaded with all the uncool school apps and the school logo on startup right before Samsung splash screen. Am graduated now and the tab is fully mine, My little sister wants to use it but the phone and ability to make calls was deactivated by the school.
WHAT I DID:
I was able to successfully flash the tab with heimdall and TWRP (i use Linux Lubuntu), i downloaded the ROM for the tab and using procedures i got online i flashed it. The Tab rebooted and to my frustration it loaded the same school slash screen but all my apps and documents were wiped off. the phone still didnt show up also.
Am sure i didn't miss any steps cos i got the "Flash Successful" after the flash and TWRP screen replaced my default recovery screen (when u press the power + up volume + home buttons together).
Q! What did i do wrong ?
What can i do?
I need to get rid of the old rom completely and install a brand new one with all the features back and working perfectly.
Please Help.
Thanks

Support for SELinux contex
I tried installing the ROM from TWRP recovery, and this is what i get:
Kernel does not have support for reading SELinux contexts.
TWRP version: 2. 7. 0. 1
i also tried flashing with different TWRP recoveries but they didnt load up, same with CWM recoveries.
Only the stock recovery and TWRP v2. 7. 0. 1 worked.
But still not installing the ROM.zip
(Samsung Galaxy tab 3 SM-T111)
Thanks
Ultrapraise said:
Hi prospective helpers
I have a Samsung Galaxy tab3 SM-T111, it was given to me by my school loaded with all the uncool school apps and the school logo on startup right before Samsung splash screen. Am graduated now and the tab is fully mine, My little sister wants to use it but the phone and ability to make calls was deactivated by the school.
WHAT I DID:
I was able to successfully flash the tab with heimdall and TWRP (i use Linux Lubuntu), i downloaded the ROM for the tab and using procedures i got online i flashed it. The Tab rebooted and to my frustration it loaded the same school slash screen but all my apps and documents were wiped off. the phone still didnt show up also.
Am sure i didn't miss any steps cos i got the "Flash Successful" after the flash and TWRP screen replaced my default recovery screen (when u press the power + up volume + home buttons together).
Q! What did i do wrong ?
What can i do?
I need to get rid of the old rom completely and install a brand new one with all the features back and working perfectly.
Please Help.
Thanks
Click to expand...
Click to collapse

Finally! i was able to install a new rom
But the phone itself still doesn't work, can't make calls or receive calls only sms

Note 4 Touch problem

I have Sprint Galaxy Note 4 which is behaving very weird. When I touch with finger the response is not where the finger is but at some other location.
If I use Pen everything is perfect. I have tried resetting is, Had screen protector which removed. but no Luck
Any help will be appreciated.

Sounds like you need to recalibrate the touch screen. Flash the wrong recovery, maybe? Either way, recalibrate it by downloading following the sequence below. If it fails the first time, you may need to Odin the stock tar and redo the steps at earliest opportunity.
Open dialer type *#2663# and then tap TSP FW update.
Sent from my SM-N920P using Tapatalk

Im getting the same issue... but the dialer codes dont work...
I flashed the Emotion 7.1 update and now my screen is all messed up. It wont select unless I press in odd areas of the screen. Its like the screen calibration is way off. I think I might have installed the wrong TWRP. I have installed the correct one now, but cant seem to fix the screen issue. Can anyone help?

Tenacious--M said:
Im getting the same issue... but the dialer codes dont work...
I flashed the Emotion 7.1 update and now my screen is all messed up. It wont select unless I press in odd areas of the screen. Its like the screen calibration is way off. I think I might have installed the wrong TWRP. I have installed the correct one now, but cant seem to fix the screen issue. Can anyone help?
Click to expand...
Click to collapse
The dialer code works with stock or stock-ish ROMs. You'll have to revert to stock with Odin to fix it.
Edit: you can find the Sprint Note 4 stock tars here:
https://forum.xda-developers.com/showthread.php?p=63868221
You may have to wipe internal memory in order to get stock tar to boot after being on CM. Not sure but it could cause a boot loop booting after Odin flash.
The latest TWRP for Note 4 is here:
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Flash that in Odin in AP slot to get back to custom ROM or CM. Don't forget to uncheck auto reboot and pull battery, wait at least and boot directly into recovery to get TWRP to stick on subsequent boots to recovery.
Sent from my SM-N920P using Tapatalk

Samep... you saved my life, thank you! I have been at this all day and could have been a week. The piece I was missing was a stock-ish rom to get to the menu. The post you made was so helpful, saved me countless hours. Once I had the Sprint stock rom tar installed via Odin, the code worked and the menu popped up. Back in action...Thank you, thank you!

Not booting even after flashing stock

Hi All,
My wife's Galaxy Note 10.1 (2014 ed.) is not booting to android.
It began boot looping seemingly out of nowhere, she had not attempted rooting or flashing.
I have tried quite a lot of things to fix this. I could still get to recovery mode so tried those options first. I performed all functions (inc. Wiping and resetting to factory, and wiping cache).
This didn't fix the problem. I then tried flashing stock firmware for our region (BTU), this made no difference. I then flashed the XAR region as this was recommended somewhere ( can't remember where), I then flashed stock recovery to see if that would fix it.
The tablet started performing an update (android symbol with torso door open with blue polyhedron rotating in, but hung on "erasing..." for over an hour. I held power to reset the device. The second restart seemed to perform the erasing procedure nearly instantaneously.
When turned on, the device currently displays: "Samsung Galaxy Note 10.1 2014 Edition", this then disappears as if about to display android, but just hangs on the black screen. It no longer loops back to the "Samsung Galaxy Note 10.1 2014 Edition" screen as it originally did.
We have left the device on this screen for many hours without it successfully booting.
I was reading that I may need to reflash the kernel, but I'm not sure about this, so I would be grateful for some advice.
If I can successfully fix the booting problem I would like to use Skipsoft's Unified Android Toolkit to flash TWRP and possibly a lighter OS to try and make the device a little more zippy/improve the very slight s-pen input lag.
Thanks in advance for any help,
Dan

Interesting Problem
DaimyoDan said:
Hi All,
My wife's Galaxy Note 10.1 (2014 ed.) is not booting to android.
It began boot looping seemingly out of nowhere, she had not attempted rooting or flashing.
I have tried quite a lot of things to fix this. I could still get to recovery mode so tried those options first. I performed all functions (inc. Wiping and resetting to factory, and wiping cache).
This didn't fix the problem. I then tried flashing stock firmware for our region (BTU), this made no difference. I then flashed the XAR region as this was recommended somewhere ( can't remember where), I then flashed stock recovery to see if that would fix it.
The tablet started performing an update (android symbol with torso door open with blue polyhedron rotating in, but hung on "erasing..." for over an hour. I held power to reset the device. The second restart seemed to perform the erasing procedure nearly instantaneously.
When turned on, the device currently displays: "Samsung Galaxy Note 10.1 2014 Edition", this then disappears as if about to display android, but just hangs on the black screen. It no longer loops back to the "Samsung Galaxy Note 10.1 2014 Edition" screen as it originally did.
We have left the device on this screen for many hours without it successfully booting.
I was reading that I may need to reflash the kernel, but I'm not sure about this, so I would be grateful for some advice.
If I can successfully fix the booting problem I would like to use Skipsoft's Unified Android Toolkit to flash TWRP and possibly a lighter OS to try and make the device a little more zippy/improve the very slight s-pen input lag.
Thanks in advance for any help,
Dan
Click to expand...
Click to collapse
Hey Man ! Hope you're doing well
About the problem not being fixed even after re flashing a stock ROM , I'd say this might be due to a problem with the flasher itself . could you please check if the "Nand Erase All" option is ticked in Odin for you in your Odin or not ? ( you're using Odin right ? :laugh: )
Regards
Hitman1376​

hitman1376 said:
Hey Man ! Hope you're doing well
About the problem not being fixed even after re flashing a stock ROM , I'd say this might be due to a problem with the flasher itself . could you please check if the "Nand Erase All" option is ticked in Odin for you in your Odin or not ? ( you're using Odin right ? :laugh: )
Regards
Hitman1376​
Click to expand...
Click to collapse
Hi thanks for the response, I don't remember ticking/unticking any options at all in odin. But I'll check this evening.
Dan

DaimyoDan said:
Hi thanks for the response, I don't remember ticking/unticking any options at all in odin. But I'll check this evening.
Dan
Click to expand...
Click to collapse
Just checked over lunch. The only options ticked in Odin (v3.12) are "Auto Reboot" and "F. Reset Time".
I reflashed stock ROM again and am back to bootloop.
I have access to both download mode and recovery mode, and I have been able to flash TWRP ( but that's currently been replaced by stock when I reflashed)
Thanks,
Dan

DaimyoDan said:
Just checked over lunch. The only options ticked in Odin (v3.12) are "Auto Reboot" and "F. Reset Time".
I reflashed stock ROM again and am back to bootloop.
I have access to both download mode and recovery mode, and I have been able to flash TWRP ( but that's currently been replaced by stock when I reflashed)
Thanks,
Dan
Click to expand...
Click to collapse
Okay , So , let's see ... First , get your tablet factory reseted by the stock recovery. Then, flash TWRP and wipe all your partitions again using TWRP. Then, get yourself a custom ROM ... If you're on the Lollipop bootloader, get a LOS or RR as they are usually faster ; If on KK, try a KK compatible ROM for your model ( if you're having a P600/1 , I recommend the NOTE S ROM or Hydronium as they are my favorites :laugh: and are good indeed ) If you flash these , you wouldn't need to flash any Kernal as they have their own ones. But if really wanna flash a kernel , maybe go with Xluco ( for KK Roms ) or Prime ( for Lollipop Roms ). I hope this fixes your problem . Waiting for your reply
Regards
Hitman1376​