Hi,
After the lastest update the phone got stuck on a bootloop with the led in a solid color that changes from blue to light blue (cyan), but turns off only if I turn off the phone. I tried to do a factory reset, didn't work. I flashed the stock firmware with Odin, but still stuck on bootloop. I was told that the problem could be the motherboard and not the software, is that true? Do you think that flashing a custom recovery (like twrp) and installing the system via the recovery would solve the issue?
Thanks in advance
Good question, I'm not familiar with the flashing light coloration change. You could try and get into recovery/TWRP, and format and then flash. I haven't had much problem at all with TWRP, it's been my best friend.
Is there a 'recovery' firmware for your phone you might try? Have you looked at:
https://forum.xda-developers.com/s7-edge/how-to/recover-bricked-galaxy-s7-edge-sm-g935fd-t3595745
blue light - email
green light - txt message
solid green - when charge is complete
red shows - phone is charging
JeffDC said:
Good question, I'm not familiar with the flashing light coloration change. You could try and get into recovery/TWRP, and format and then flash. I haven't had much problem at all with TWRP, it's been my best friend.
Is there a 'recovery' firmware for your phone you might try? Have you looked at:
https://forum.xda-developers.com/s7-edge/how-to/recover-bricked-galaxy-s7-edge-sm-g935fd-t3595745
blue light - email
green light - txt message
solid green - when charge is complete
red shows - phone is charging
Click to expand...
Click to collapse
The thing is that the bootloop (and the led color as well) appeared after an OTA update. I have never flashed TWRP or a custom rom on the phone. And, as I already said, flashing the stock firmware doesn't really work.
cristobalszk said:
The thing is that the bootloop (and the led color as well) appeared after an OTA update. I have never flashed TWRP or a custom rom on the phone. And, as I already said, flashing the stock firmware doesn't really work.
Click to expand...
Click to collapse
... and you are not able to get into download mode... ?
IS your phone recognized by your PC? adb?
any more info you can share?
JeffDC said:
... and you are not able to get into download mode... ?
IS your phone recognized by your PC? adb?
any more info you can share?
Click to expand...
Click to collapse
Sorry if I wasn't clear with the description of the problem. I'll try to make everything clear.
1- I received the OTA update, did the update
2- After it, the phone got stuck on a bootloop, with the led turned on as I mentioned before
3- I flashed the stock firmware of the phone via Odin (so, it can get into download mode, as well as recovery mode, they both work perfectly). So yes, the phone is recognised by the pc.
So, the problem was not solved by flashing the stock firmware as I expected, so, any alternate solution?
Do you know 'what' the update exactly was?
What model phone?
JeffDC said:
Do you know 'what' the update exactly was?
What model phone?
Click to expand...
Click to collapse
SM-G935F
Don't really know what the update was, I guess just a security patch or something like that because it was not very big (about 200 - 300 mb if I remember correctly).
I'm wondering if you go at your phone at a very low level recovery, perhaps as in this post:
https://forum.xda-developers.com/ga...possibly-6-t3622126/post74646865#post74646865
Based upon how I understand the OP's discussion, this process intercedes before the phone has it's security measures up and running, which allows for the FRP to be solved, and an as 'new' phone to arise from the ashes.
I'll likely be using/trying this method on an S7 Edge, Google locked, I just won in an on-line police auction, which has yet to arrive.
Related
Ohh, where to start. Ok so first off let me apologize in advance if this has already
been posted but I’m a noob when it comes top posting in the forums. Been using
them for years to fix my problems just new to posting. Anyway, a few nights ago I
tried to flash the newest version of the T-Mobile AOKP rom (Kit Kat 4.2.2) onto my
AT&T I337 Samsung Galaxy S4 via the latest version of TWRP recovery. After
attempting to flash AOKP, TWRP failed the flash and had an error message that said
something about the phone not being able to flash a T-Mobile rom on an AT&T
phone. I then tried to flash the AOKP rom again and mistakenly flashed the Loki
kernel instead. I was currently running Cyanogenmod 11. After the Loki kernel
attempted to flash, it once again said failed and gave me a message that said
something about me losing root and asking if I wanted to reinstall superuser. I
agreed to reinstall superuser and used the option to reboot my phone once it was
complete. But….once the phone attempted to reboot my screen went black and all
my phone would do is vibrate every two to three seconds with a blank screen. I
pulled the battery, tried to put it in recovery mode, and download mode but nothing
worked at all. It wouldn’t charge, no battery icon, no LED. After messing with it for a
few hours and randomly pushing buttons I finally got it to go into download mode. I
was so happy. I decided I would flash (Odin) a stock firmware that I had already had
and used plenty of times. But…after flashing Odin would say complete and pass but
when my phone would reboot it done the same thing as before. Black screen and
vibrates every two to three seconds wont charge, no battery icon, no LED, still won’t
go into recovery mode but will still go into download mode. I’ve used every version
of Odin, used different USB ports, different USB cords, reflashed the stock at least
20 times now and still nothing. What have I done and how could I fix this issue. :crying:
Ohhh and before I forget, It may be worth mentioning that when I finally got it in
download mode I noticed it said that I had the stock Samsung firmware, where it
usually says custom when rooted.
I'm assuming you're on MDL firmware. If so Odin flash the stock firmware. You can get it at sammobile.com
You're probably hosed though, sounds like you've tried all this.
Doesn't work
jd1639 said:
I'm assuming you're on MDL firmware. If so Odin flash the stock firmware. You can get it at sammobile.com
Click to expand...
Click to collapse
Like i said in the post. Odin didnt work. It will say pass every time but doesnt fix anything. Screen still stays black and just vibrates every two to three seconds and still cant access recovery mode.
signature
lukethaduke88 said:
Like i said in the post. Odin didnt work. It will say pass every time but doesnt fix anything. Screen still stays black and just vibrates every two to three seconds and still cant access recovery mode.
Click to expand...
Click to collapse
just try whats in my signature
lukethaduke88 said:
Like i said in the post. Odin didnt work. It will say pass every time but doesnt fix anything. Screen still stays black and just vibrates every two to three seconds and still cant access recovery mode.
Click to expand...
Click to collapse
so my gs4 does the same thing how did you fix it ?
juggalo1978 said:
so my gs4 does the same thing how did you fix it ?
Click to expand...
Click to collapse
First observation: nothing here says that he fixed it. If he did, which may not have happened, then he obviously didn't tell us.
I wonder if you really have the same issue. Did you read through the OP? Did your phone get where it is by doing the exact same sequence that he did? If not, and you want someone to help, you will need to give a detailed description of everything that led up to the issue you have, from the time the phone was operating normally. It would also be helpful to know what your phone was running before this happened.
creepyncrawly said:
First observation: nothing here says that he fixed it. If he did, which may not have happened, then he obviously didn't tell us.
I wonder if you really have the same issue. Did you read through the OP? Did your phone get where it is by doing the exact same sequence that he did? If not, and you want someone to help, you will need to give a detailed description of everything that led up to the issue you have, from the time the phone was operating normally. It would also be helpful to know what your phone was running before this happened.
Click to expand...
Click to collapse
I have an i337 and i flashed the AOSP Kt kernel like june or before intern it rebooted and was stock on boot black screen and vibrating trying to turn on or or recovery does the same thing i can get in dl mode and odin says pass nothing stays the same kies wont read it and it dont come up in device manger it is on ether the mdb boot loader or mdl it was running liquid smooth it never got to stock recovery because when it would not boot i tried odin
3.2 ive seem some where it can be fixed with an sd card but i need the debrick image if anyone could help id appreciate it thank you
---------- Post added at 02:17 AM ---------- Previous post was at 01:58 AM ----------
creepyncrawly said:
First observation: nothing here says that he fixed it. If he did, which may not have happened, then he obviously didn't tell us.
I wonder if you really have the same issue. Did you read through the OP? Did your phone get where it is by doing the exact same sequence that he did? If not, and you want someone to help, you will need to give a detailed description of everything that led up to the issue you have, from the time the phone was operating normally. It would also be helpful to know what your phone was running before this happened.
Click to expand...
Click to collapse
I have an i337 and i flashed the AOSP Kt kernel intern it rebooted and was stock on boot black screen and vibrating trying to turn on or or recovery does the same thing i can get in dl mode and odin says pass nothing stays the same kies wont read it and it dont come up in device manger it is on ether the mdb boot loader or mdl it was running liquid smooth 3.2 ive seem some where it can be fixed with an sd card but i need the debrick image if anyone could help id appreciate it thank you
So I'm really into Android developing, I'm always flashing and installing etc, but I got a problem now.
Phone information
LG G2 D802
Rooted
TWRP Recovery 2.7.0.0
Was running 4.4.2, found a kdz file on the internet and flashed it (no regular update from my phone)
What happenedI actually did something stupid, I received an application update from the LG Download Center (or whatever it's called) on my phone and clicked on it. I was planning on flashing Android 4.4.2 again because my firmware was not stable, and I thought this update could help me.
But no, after it finished downloading, I automatically booted into recovery.
What I didSo I tried to reboot and enter my OS, but unfortunately, I was stuck in recovery.
I did everything I could, wiping (Dalvik) cache, factory reset, flashed a new rom, restored Nandroid backup, but no, every time I booted, I got back into recovery again.
I only saw 1 option left, booting into download mode and flashing a new firmware.
I found the Netherlands 16GB kdz file for Android 4.4.2 (because I had a French one first), the one I was looking for.
Looked all over the internet, and all guides pointed me to this guide.
Tried it, but I got multiple errors, one of them was that my phone was not connected while I was at 15% of the flash process.
What happenedAfter that first flashing process, I booted up, but got a Security Error. After the Security Error was showing for 5 seconds, my phone shut down. This is happening every time I try to boot up.
I couldn't access my recovery anymore, nothing. Edit: I can access my recovery right now, and I tried this, but when I boot up I get the Security Error again.
The big problem right now is the Security Error! How do I bypass that?
So can someone please help me out!
Several phones/tablets of mine bricked and I always found a way to get out of it, but not this time, unfortunately...
Have you tried this
Sent from LG-G2 D800 on AEONFLEX 4.4.2
XxZombiePikachu said:
Have you tried this
Sent from LG-G2 D800 on AEONFLEX 4.4.2
Click to expand...
Click to collapse
Yes, I actually have. Didn't mention it, but after I did that I booted and got an LG logo and below it was a text that said 'Security Error' After like 5 seconds the security error goes away and my phone shuts down. I can only enter download mode right now.
I'll edit my first post with this info.
Thanks for the help though!
Edit: I find a way to access my recovery again because at first I couldn't but I figured out that the code in the thread you linked was a bit different than the code I entered at first.
So I used the code you gave me, but now I get the Security Error again!
Hi mate, just like you i downloaded that damn OTA today and messed up my phone, but in my case was because i had totally forgotten it was rooted and had custom recovery installed :silly::silly::silly::silly:
I followed this tutorial to fix the boot secure error http://forum.xda-developers.com/showthread.php?t=2582142 and it worked like a charm except for download mode wasn't working at all.
After doing some research i found this post http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html and got download mode (apparently) working again but Windows didn't recognize it at all so i couldn't use it to flash the .kdz stock firmware.
In the end i just flashed a custom aosp rom and got my phone back to life but the download mode issue it's still there and it's bothering me quite a lot.
Any suggestion is welcome.
EDIT: Don't download the recovery from the post, instead look for the latest version (2.7.0.0) because the one posted there (2.6.3.2) might corrupt your partitions
evilruck said:
Hi mate, just like you i downloaded that damn OTA today and messed up my phone, but in my case was because i had totally forgotten it was rooted and had custom recovery installed :silly::silly::silly::silly:
I followed this tutorial to fix the boot secure error http://forum.xda-developers.com/showthread.php?t=2582142 and it worked like a charm except for download mode wasn't working at all.
After doing some research i found this post http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html and got download mode (apparently) working again but Windows didn't recognize it at all so i couldn't use it to flash the .kdz stock firmware.
In the end i just flashed a custom aosp rom and got my phone back to life but the download mode issue it's still there and it's bothering me quite a lot.
Any suggestion is welcome.
EDIT: Don't download the recovery from the post, instead look for the latest version (2.7.0.0) because the one posted there (2.6.3.2) might corrupt your partitions
Click to expand...
Click to collapse
Thanks! But does my internal storage get whiped? Will all my pictures etc. be gone?
And the first thred removes the security error right? And after that I can just boot into recovery mode (I can boot in recovery btw) and flash a new rom? Just wanted to know this so I don't go through all that trouble for nothing
Edit: You know I can enter both download and recovery mode right?
Ibrahim9999 said:
Thanks! But does my internal storage get whiped? Will all my pictures etc. be gone?
And the first thred removes the security error right? And after that I can just boot into recovery mode (I can boot in recovery btw) and flash a new rom? Just wanted to know this so I don't go through all that trouble for nothing
Edit: You know I can enter both download and recovery mode right?
Click to expand...
Click to collapse
Nope internal SD remains intact, basically what you'll be doing is pushing the right files into the system partitions and yes, in theory you should be able to flash a new rom.
Even if you can boot into recovery you should do it if you're getting that error, and after that you can just push a ROM file to flash (i'll assume you know how to do it) and btw let me know if you decide to flash a stock based rom instead of an aosp like i did.
Good luck with that :good:
evilruck said:
Nope internal SD remains intact, basically what you'll be doing is pushing the right files into the system partitions and yes, in theory you should be able to flash a new rom.
Even if you can boot into recovery you should do it if you're getting that error, and after that you can just push a ROM file to flash (i'll assume you know how to do it) and btw let me know if you decide to flash a stock based rom instead of an aosp like i did.
Good luck with that :good:
Click to expand...
Click to collapse
Thanks man! I'm probably going to save money because of you, awesome!
Ibrahim9999 said:
Thanks man! I'm probably going to save money because of you, awesome!
Click to expand...
Click to collapse
I hope so!
Let me know if you fix the thing :laugh:
evilruck said:
I hope so!
Let me know if you fix the thing :laugh:
Click to expand...
Click to collapse
I just managed to fix it! Thank you so much man!
Can someone help me plz I got flashily got CWM instead of the TWRP and got and lg update it updated and now it's stuck in recovery mode it won't go into download mode it only goes to recovery mode and my computer won't recognize my phone so if any one knows how to fix it can you plz help me out
my pc don't recognize the lg g2 in download mode!
i installed the drivers and the USB is connected but the pc don;t even say that the device is connected . and nothing in device manager at all
Perhaps you might consider sending it in to lg if you still have warranty. But I'd you don't, there are services on eBay/ Craigslist that can help you.
Sent from my LG-D800 using XDA Free mobile app
Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
rionline said:
Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
Click to expand...
Click to collapse
try to flash only the stock recovery.
If it fails, flash the last stock with pit file + factory reset on recovey, if wou're again in bootloop
I did the same thing on my note 10.1
"your partition is corrupt. Would you like to factory reset your device?"
it is still here in bootloop..
Rajada said:
try to flash only the stock recovery.
If it fails, flash the last stock with pit file + factory reset on recovey, if wou're again in bootloop
Click to expand...
Click to collapse
Do you have a recent stock recovery flashible with odin or do you know where to find?
I did flash the recent stock with pit files/repartitioning,...does not help.
iRoNX said:
I did the same thing on my note 10.1
"your partition is corrupt. Would you like to factory reset your device?"
it is still here in bootloop..
Click to expand...
Click to collapse
How do you know the partition is corrupt? I think i already did a factory reset by repartitioning with the pit file. Corrupt partitions i tried to fix by nand erase in combination with repartitioning... this did not help.
I have the same problem, only problem I got some text with red+blue+yellow color, what I did was flash a stock ROM ( SAME ROM I HAD BEFORE ROOT FAIL) and it worked (like)
rionline said:
Do you have a recent stock recovery flashible with odin or do you know where to find?
I did flash the recent stock with pit files/repartitioning,...does not help.
Click to expand...
Click to collapse
any flagship Samsung is bricked if you can get into download mode.
if you want to try, above you have the recovery from the last S1CPC1, flash it at odin:
Rajada said:
any flagship Samsung is bricked if you can get into download mode.
if you want to try, above you have the recovery from the last S1CPC1, flash it at odin:
Click to expand...
Click to collapse
thank you very much. i do not understand your first sentence......btw. i can get into download mode...(just if you meant "can not")
Update: I have virtually flashed every rom > 5.0. No success, no difference. Everytime the odin flash procedure is successful (in all variants, with pit, with nand erase, etc...), but the phone loops everything (normal start, recovery) besides the bootloader.
only new thing i noticed: allthough binary status is official, the device status is and stays custom not matter what i flash.
anyone? anything?
Did you try to flash the stock recovery yet?
Also, what did you exactly flash to cause this?
sunniebeta said:
Did you try to flash the stock recovery yet?
Also, what did you exactly flash to cause this?
Click to expand...
Click to collapse
yes i tried stock recovery already. not sure what caused this. i do remember that i had some problems with 4.8 debloated and then i wanted to flash the hole corresponding stock package as clean base. somewhere in the middle this happenend. i am not quite sure, but maybe, maybe flashed cf-autoroot to this march update. but i am not sure if this was before, after or initially.
however,...what really bothers me, is that there is absolutely no indiciation for an error during the flash process. odin and kies, everything completes just fine, just booting does not work. that's why i fear, that this is just an ugly coincident and the problem is caused by some failing hardware.
maybe and immensly undclocked kernel (odin flashable) could start my phone. because something is still working, when the bootloader and the nand writing is working just fine.
does anybody know how to get a really granpa speedy kernel, or how to make it?
rionline said:
Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
Click to expand...
Click to collapse
Used to happen to me all the time. What I used to do was, after flashing the rom, connected it again to odin, flashed the cwm recovery 5-6 times and then used to give it a try. Also ,after trying this, flash the bootloader-modem file and pretty sure your phone will boot(This is optional)
rionline said:
Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
Click to expand...
Click to collapse
Greetings from Hamburg ☺
I was having also huge bug with dr.ketan rom at first was working flawlessly and 1 month later my phone wouldn't charge at all or recognise any charging cable.
Good thing is you can enter download mode (odin )
That means your phone is only soft bricked.
Flash SM-910F pit file + Latest stock firmware in odin mode all together in 1 flashing process...dont forget to mark repatriation in odin when using pit file.
When you got pass on odin and phone reboot and you see Samsung logo...fast take battery out and wait 1 min , put battery back and hold combo to enter stock recovery and do factory reset.
Good luck :fingers-crossed:
android freek said:
Greetings from Hamburg
I was having also huge bug with dr.ketan rom at first was working flawlessly and 1 month later my phone wouldn't charge at all or recognise any charging cable.
Good thing is you can enter download mode (odin )
That means your phone is only soft bricked.
Flash SM-910F pit file + Latest stock firmware in odin mode all together in 1 flashing process...dont forget to mark repatriation in odin when using pit file.
When you got pass on odin and phone reboot and you see Samsung logo...fast take battery out and wait 1 min , put battery back and hold combo to enter stock recovery and do factory reset.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Thanks guys. I tried yesterday some stuff, nothing was working and i finally got it dead as a stone! Nothing was working anymore. However, i took it to the samsung service center. They were irritated, that they can't get it on at all! ... However, i am curious, how they handle it and how much they want for a repair attempt/or replacement.
Just for info. I did all the things you proposed. Nothing worked. I think this was just a coincidental hardware failing. If you flash all the time, there is a chance that you do it, while something is dying!?
i keep you updated! Thanks for now...
Corrupted eMMC? Probably! Please let us know what the service centre said ultimately and how much they charged you.
ithehappy said:
Corrupted eMMC? Probably! Please let us know what the service centre said ultimately and how much they charged you.
Click to expand...
Click to collapse
So i am back with a fresh note 4 mainboard. they changed it no questions asked, no fee, no problems. i like!
Hello all,
I've got a couple of problems with a J500F. As usual, I rushed into doing things to the phone before reading fully (I've been installing various ROMS on my phones for quite a while now).
First of all, I've managed to install TWRP 3.0.2-0. But it seems that the calibration of the screen is way off what it should be. Clicking the "Install" button actually registers as the "Advanced" button. So I can still do things, I just need to guess where to click. Anyone else had this problem?
Secondly, every ROM I try and install will not work. I get a couple of horizontal lines across the screen, and nothing else.
Any help/suggestions are more than welcome.
Thanks in advance,
Tony.
Tony only tme you should panic is you mess efs . If you hve stock rom flash it via odin this would solve ur calibration issues. And install nickverse version of twrp maybe you installed a version for 6.0.1 instead of 5.1.1
Sent from my SM-J500F using Tapatalk
Thanks for the speedy reply.
I don't have the stock ROM, is it available on this site (I'm having trouble locating it).
tonybod said:
Thanks for the speedy reply.
I don't have the stock ROM, is it available on this site (I'm having trouble locating it).
Click to expand...
Click to collapse
Go and try sammobile or google it ull get it make sure to flash it through odin. Am sure you will be fine. Download the right firmware according to your country and region send me ur device name and region i see if i can share a download link
Sent from my SM-J500F using Tapatalk
The model is SM-J500F/DS, and it's a UK phone. Sammobile does not seem to have any UK image, I'm wondering if it actually came from somewhere else (I purchased it on Amazon UK, but it did not have a UK charger).
tonybod said:
The model is SM-J500F/DS, and it's a UK phone. Sammobile does not seem to have any UK image, I'm wondering if it actually came from somewhere else (I purchased it on Amazon UK, but it did not have a UK charger).
Click to expand...
Click to collapse
Go to settings then send me screen shot of about phone. You can download an app from playstore called Samsung phone info(something like that) can tell you which region its from...
Sent from my SM-J500F using Tapatalk
I cannot get into the settings (cannot get a ROM to boot).
I've just tried the Nick Verse recovery, it continually reboots the phone unfortunately without ever getting to the recovery screen.
I'll try one of the European ROMs from Sammobile, hopefully that will get things working again.
ok, I've got a stock ROM on the phone and it's booting up. But the screen calibration problem is still there which makes it unusable.
Going to see if I can use the app on Google play (not sure how I'm going to connect to the wifi though).
tonybod said:
ok, I've got a stock ROM on the phone and it's booting up. But the screen calibration problem is still there which makes it unusable.
Going to see if I can use the app on Google play (not sure how I'm going to connect to the wifi though).
Click to expand...
Click to collapse
Then you might hve flashed the twrp without unlocking oem.https://boycracked.com/2016/03/30/official-samsung-galaxy-j5-j500f-stock-rom/ try that link.
Sent from my SM-J500F using Tapatalk
When you say unlocking OEM, do you mean for the FRP error? I did unlock that (but don't recall unlocking anything else).
tonybod said:
When you say unlocking OEM, do you mean for the FRP error? I did unlock that (but don't recall unlocking anything else).
Click to expand...
Click to collapse
Yea but its not frp its OEM hehe. Just reflash the stock rom again then try flashing the twrp again.
Sent from my SM-J500F using Tapatalk
---------- Post added at 01:02 PM ---------- Previous post was at 01:00 PM ----------
You need to enable oem to unlock ur bootloader then you can flash twrp. Ensure that usb debugging is on. You might hve missed one of this two
Sent from my SM-J500F using Tapatalk
tonybod said:
ok, I've got a stock ROM on the phone and it's booting up. But the screen calibration problem is still there which makes it unusable.
Going to see if I can use the app on Google play (not sure how I'm going to connect to the wifi though).
Click to expand...
Click to collapse
I'm guessing you probably need to upgrade your rom. Strange lines and out of whack touches are usually due to an incorrect firmware vs kernel.
Ensure you are flashing the latest MM rom for your device if the TWRP you are using was built using a MM kernel.
Try flashing stock via Odin. Guides are available all over XDA on that.
I'm just getting back to this.
I've shot a quick video to show what I mean is happening.
https://www.youtube.com/watch?v=yR5dF9lURcU
Jump to 10 secs, you can see that click location is way off/.
Anyone got any ideas? I've flashed a number of stock images so far, all have the same issue. I've currently got a mouse connected via bluetooth so I can actually do things as trying to work the keyboard like this is impossible.
tonybod said:
I'm just getting back to this.
I've shot a quick video to show what I mean is happening.
Jump to 10 secs, you can see that click location is way off/.
Anyone got any ideas? I've flashed a number of stock images so far, all have the same issue. I've currently got a mouse connected via bluetooth so I can actually do things as trying to work the keyboard like this is impossible.
Click to expand...
Click to collapse
Are you actually allowing the firmware to complete its update?
It must boot into recovery after odin finishes flashing otherwise the install isn't complete.
It should auto reboot to recovery and you should see 'erasing'
Then it will reboot and the update should be completed.
If it does not boot to recovery then this is likely why you have the described issues.
ashyx said:
Are you actually allowing the firmware to complete its update?
It must boot into recovery after odin finishes flashing otherwise the install isn't complete.
It should auto reboot to recovery and you should see 'erasing'
Then it will reboot and the update should be completed.
If it does not boot to recovery then this is likely why you have the described issues.
Click to expand...
Click to collapse
Yes. I've just reflashed to check. It downloads the image to the phone, reboots into recovery where it says erasing, installing system update etc. Then reboots and I get the "Android is upgrading" message where it does all it's "optimizing apps". The touchscreen error still persists .
I did video this (or portions of it) and can upload.
tonybod said:
Yes. I've just reflashed to check. It downloads the image to the phone, reboots into recovery where it says erasing, installing system update etc. Then reboots and I get the "Android is upgrading" message where it does all it's "optimizing apps". The touchscreen error still persists .
I did video this (or portions of it) and can upload.
Click to expand...
Click to collapse
Which firmware are you using and what is your device spec?
I've got a few ROMs that I've tried
SM-J500F_20160812_J500FXXU1BPH1_J500FODD1BPH1_6.0.1
SM-J500F_20160512_J500FXXU1APE1_J500FOXX1APE1_5.1.1
J500FXXU1BPF4_J500FODD1BPF4_SLK
Same behaviour with all of them. I'm not entirely sure what region the phone was originally from, I purchase it on Amazon and believe it came from somewhere in Eastern Europe, so I've been trying images marked as Austrian, Slovakia, even Greece.
If it helps, the following is under the battery.
Model : SM-500F/DS
FCC ID : A3LSMJ500F
SSN : J500F/DSGSMH
tonybod said:
I've got a few ROMs that I've tried
SM-J500F_20160812_J500FXXU1BPH1_J500FODD1BPH1_6.0.1
SM-J500F_20160512_J500FXXU1APE1_J500FOXX1APE1_5.1.1
J500FXXU1BPF4_J500FODD1BPF4_SLK
Same behaviour with all of them. I'm not entirely sure what region the phone was originally from, I purchase it on Amazon and believe it came from somewhere in Eastern Europe, so I've been trying images marked as Austrian, Slovakia, even Greece.
If it helps, the following is under the battery.
Model : SM-500F/DS
FCC ID : A3LSMJ500F
SSN : J500F/DSGSMH
Click to expand...
Click to collapse
Install Samsung phone info and post a screen shot of the CSC info.
It should show your original CSC.
Thanks, I've uploaded the screen. Sorry it took so long, I've been away and forgot the bluetooth mouse that I use on the phone.
It looks like the original CSC is SM2J500FZKDAUT, I cannot seem to find that on Sammobile.
Hi so first of all im kind of a noob when it comes to this so please explain any technical jargon
It all started a few days ago when my note 4 started rebooting on its own, it did occasionally get stuck in bootloop but a battery pull fixed every time, I hadn't rooted it or did anything that could break it that way just normal media consumption. About 2 days later it started to get stuck on bootloop more than half the times it rebooted (again all without a reason) Currently it doesnt even show the boot animation and i can't access recovery mode, I can access odin mode tho but i flashing it twice didn't help
I have the uk O2 version (SM-N910F) with a powerbear battery that doesn't show any signs of wear down
Any assistance in getting my phone's software back to "out of the box" conditions would be GREATLY appreciated.
Thank you for your time and patience
Did you flash stock rom(latest) successfully through odin? Did odin show 'success' message after finishing flashing?
Mufrad said:
Did you flash stock rom(latest) successfully through odin? Did odin show 'success' message after finishing flashing?
Click to expand...
Click to collapse
yes and yes, I used the latest stock rom from sammobile and it did successfully flash but when it tries to go to recovery mode after that it just goes to bootloop again (it shows the "recovery booting..." in blue at the top)
Altrath said:
yes and yes, I used the latest stock rom from sammobile and it did successfully flash but when it tries to go to recovery mode after that it just goes to bootloop again (it shows the "recovery booting..." in blue at the top)
Click to expand...
Click to collapse
I am not sure what's wrong, but I would install a custom recovery and try and install a custom rom to check if everything works right, if it does then maybe try and flash stock through odin again.
Altrath said:
Hi so first of all im kind of a noob when it comes to this so please explain any technical jargon
It all started a few days ago when my note 4 started rebooting on its own, it did occasionally get stuck in bootloop but a battery pull fixed every time, I hadn't rooted it or did anything that could break it that way just normal media consumption. About 2 days later it started to get stuck on bootloop more than half the times it rebooted (again all without a reason) Currently it doesnt even show the boot animation and i can't access recovery mode, I can access odin mode tho but i flashing it twice didn't help
I have the uk O2 version (SM-N910F) with a powerbear battery that doesn't show any signs of wear down
Any assistance in getting my phone's software back to "out of the box" conditions would be GREATLY appreciated.
Thank you for your time and patience
Click to expand...
Click to collapse
Mate, the 910F is a Snapdragon - famous for it's eMMc problem. You may search about this and get more info.
In short, there's a big chance it's not going to get to work again.
Sorry for your loss.
The problem seems to be caused by the eMMc chip
Is there a way to fix or replace it without expensive equiepement?
Mufrad said:
I am not sure what's wrong, but I would install a custom recovery and try and install a custom rom to check if everything works right, if it does then maybe try and flash stock through odin again.
Click to expand...
Click to collapse
btw flashing TWRP or any recovery doesn't work so i'm pretty sure it's the eMMc chip
If it really is your eMMC chip, you are better off trying to get a new device. The eMMC chip isn't removable without a lot of time, effort and risks. Also you'll need a head Gun or something and a new identical chip that will cost you a new device worth.
Altrath said:
The problem seems to be caused by the eMMc chip
Is there a way to fix or replace it without expensive equiepement?
Click to expand...
Click to collapse
try
https://forum.xda-developers.com/note-4/help/100-fix-galaxy-note-4-emmc-error-random-t3859448