Related
Yesterday my phone started acting up. All running process crashed and not many was able to start. I had to constantly click "force close". I think this started after I installed the Google+ app, but not sure.
I have tried uninstalling all unnecessary apps, without luck. I then tried wiping to factory settings by using the Android menu, but without any changing. I then tried by holding vol+ and power, going in to recovery and wiping both to factory and app cache. This doesn't change anything either. By googling I can see some suggests to hold vol- and power, to get to a another wiping-functionality but this just boots my Nexus S to normal state - no menu appears.
Has anybody an idea of what I can do?
Edit: more info; if I click "Report" and investigate the message sent to Google, I see that error has something to do with SQLite-relatet classes. Which makes some sense, alot of my changes are reset each time the phone is rebooted. For instance did I miss a call a couple of hours before the phone went crazy - this is shown at each boot in the notification area eventhough I clear the area and/or goes to missed call section
Factory reset via menu does delete all your "custom" apps, so I'd say it's not one of the existing apps causing problems.
The way you describe function after your factory reset sounds like factory reset didn't work properly.
If you feel safe I'd recommend rather flashing 2.3.4 again using either Odin or the OTA zip from Google (requires open bootloader).
I think you're right that factory reset doesn't do what is expected. Once I click it, the phone reboots and shows the Android guy next to an unwrapping package. This lasts only 2 seconds, then it reboots itself again and goes into normal phone mode (where all the app-crashing starts again).
I have not flashed or rooted my phone before, but I will consider this now since my NS is pretty much a brick. Thank you for your swiftly response.
Edit: Shouldn't I get a menu, when I push and hold vol- button, while turning on the device? Right now it just boot as normal.
Before you use odin....try going into rom manager a reflashing clockwork! Ive had that android dude on my screeen but reflashibg via rom manager always fixed it. Try that
Sent from my Nexus S using XDA Premium App
Wow my Nexus has totally shut me out.
I cannot use ClockworkMod unfortunately since I am not able to root my phone. It is not detectable via USA (when I use vol+/pwr and connect USB). I am unable to check the USB Debugging option on the phone. Each time I check it, go to home-screen and back to the menu, it has de-selected it again. Also I noticed when I read the info that is sent to Google for all those app-crashes I get, I see SQLiteException and error in an SQLite.java file. So it seems like some database layer is broken.
I read one could copy the ClockWork.img to my phone and use the standard recovery option to flash the img (I think). But when I go into the recovery menu, the file is gone. When I boot the phone again, it has deleted the .img file - eventhough if I copy it to several different folders, they are all gone :-(.
I feel pretty screwed at the moment. How can I else wipe all data?
I'd recommend to check if your device is correctly identified in windows. Missing USB drivers might cause problems. Get the latest drivers and a guide from here.
If you succeed booting into fastboot properly (vol up and power) you can follow this guide. Get the latest cwm recovery.img here.
Last option would be to boot into download mode (vol up + vol down + power + plugging in usb cable) and use Odin from samfirmware.com
--
All options require correctly working USB drivers.
I managed to unlock the bootloader, by quickly turning on USB-debugging (before any processes started to crash) and install the drivers from this post:
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
A reboot later, I got this message:
"System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Right below was a button saying "Im feeling lucky" (??)
I installed ClockworkMod using fastboot and tried "Fixing permissions" with no luck. I will try some ROM later on, and hope it will bring my phone back
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
rentaric said:
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
Click to expand...
Click to collapse
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
DennisRP said:
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
Click to expand...
Click to collapse
See I'm no expert on this whole thing. At this point I'd just flash a whole new system via Odin. Prolly not the smartest or safest option, but that's what I'd do because I don't know better. If that wouldn't fix it either, I'd return the phone on warranty
I was looking at Odin from the start, since nothing else seemed to be working.
So right now I got started on Odin. Followed the .pdf steps and flashed the bootloader at first succesfully. I was asked to remove the battery and re-connect my NS. Began downloading "pda" and "phone", but at around 10% a big fat red "fail" message appeared and now I just see the Google-logo on startup. I still cant flash any roms via fastboot.
Im too tired too right now, been working with this for 14 hours straight. I will look at it tomorrow evening. Thanks for your help rentaric
Weird, you're not the first one who had trouble running Odin using their guide.
Overall it's pretty simple.
Enter download mode. Vol up vol down and power at the same time while plugging in the USB cable. Start Odin, should show a yellow colored box with a port number. Uncheck everything but reset timer and auto reboot. Unzip the correct zip file from samfirmware.com (check if you got i9020 or i9023 and get the universal Odin exe), apply file from the folder accordingly. Bootloader and bootloader. Phone and modem. Pda and pda. Csc can remain empty (will change carrier info in fastboot).
Double check md5 hash to avoid broken files.
Sent from my Nexus S using XDA App
rentaric said:
Weird, you're not the first one who had trouble running Odin using their guide.
Click to expand...
Click to collapse
Of course I did not go to bed, how should I be able to sleep with a broken phone .
The firmware suggested on samfirmware.com for my phone, was 2.3.3 and some other version (my phone was 2.3.4.2/GRJ22 or something similar, I suspect that might be the cause. Also I unchecked everything, that might also have been of importance). The flash will always fail when everything was downloaded - it then said something about "remote" and "Loke" and then fail. But as I mentioned, I had succesfully flashed boot.img (2.3.3) thus no boot occured now. I googled the correct bootloader, used fastboot and was booting succesfully again.
I began looking more into the sdcard, as error-messages was leading me this way. To compress 4 hours of investigations into a few lines, it seems as my PBA is malfunctioning as other xda-members have experinced. Only solution is sending the phone to Samsung for a PBA replacement. I purchased the phone in Bestbuy USA and the danish Samsung partners are not too joyfull about this - I will contact Samsung and hope they can help me.
I experinced the exact same thing as this poor guy - http://forum.xda-developers.com/showthread.php?t=993403
Every thing you try to do to /sdcard is worthless.
Formatting (USB/using CWM/using adb shell linux commands) says "Succes" but nothing happens.
Copying files says "Succes" but nothing happens. If I boot phone into CWM, mount usb and upload new rom/apk/whatever and try to do a "install update.zip" it fails with some mounting errors.
Im ready to go cry in a corner - I really want this to be fixable via software, but I probably have to realize that this is a hardware issue.
Apparently Samsung doesn't offer worldwide warranty for cellularphones :´(. God it sucks to pay repair-expenses on a 1 month old mobile.
I was attempting to get root access to my galaxy tab 2 10.1 running android 10.2.1 (or whatever the latest Samsung update was it is 10.2 on my phone but am sure it was 10.2.1 on the tablet.
I was following this guide that someone here recommended
http://www.ibtimes.co.uk/articles/4...-p5113-android41-jellybean-android404-ics.htm
I set usb debug and made sure the drivers were on my pc and made sure KIES was completely not running
Followed the instructions to the letter but should have worried when I found the instructions to get to download were wrong - I found on videos that it was reboot using power and right volume key. That was successful
It connected to ODIN fine and the yellow box came up
I made sure the two boxes were ticked and then searched for the file
CF-Auto-Root-espresso10wifi-espresso10wifibby-gtp5113.zip and started ODIN
it seemed to be going fine until suddenly a red box came up with update failed
Now all I can get on the device is "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
No matter how I try to restart this I get the same screen and imagine I couldn't connect to kies even if I should
Can anyone help as I am worried that I have bricked my device - I was looking for a simple way to get root without flashing a whole rom - or is that what I was doing anyway?
Here is a link that may can help you : http://forum.xda-developers.com/showthread.php?t=1722745
Try to do the point A to install CWM Recovery and root correctly the tab then do the point E to install the stock Android 4.0.4
ps : if you want to do something to your tab, try to search here before other websites, big community, good informations/tips (personnal advise) :good:
Maybe file you downloaded is corrupted , redownload it from xda or sammobile and do steps again
n0is said:
Here is a link that may can help you : http://forum.xda-developers.com/showthread.php?t=1722745
Try to do the point A to install CWM Recovery and root correctly the tab then do the point E to install the stock Android 4.0.4
ps : if you want to do something to your tab, try to search here before other websites, big community, good informations/tips (personnal advise) :good:
Click to expand...
Click to collapse
I will take a look but so far the only thing I get is the message to connect to KIES and it wont of course connect - cant get into any other modes - you would think they would have some kind of hard boot recovery button that gets you to basic screen to download the latest firmware.
And I did start here and believe that this led from a post here - I was trying to find the least complicated method of getting root access without changing what I already had too much - the only other process that I found on here seemed to have lots of people reporting problems if it wasn't a 3g model
It is beginning to look like I may have found out what bricking is - thanks for the reply anyway
would like to do that
mjrshark said:
Maybe file you downloaded is corrupted , redownload it from xda or sammobile and do steps again
Click to expand...
Click to collapse
In fact the instructions do say if it doesn't work first time, to run it again with the boxes unticked - the problem is that I cant get back to download mode, or any mode other than the message to connect to kies, so have no way of doing this. So looks like it may have bricked - is there any way of unbricking a tablet?:crying:
It's going to be an expensive mistake especially as I haven't even had the £50 cash back from Samsung yet and I would have to pay full price now to replace it,
So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium
not optamistic but will try!
samsgun357 said:
So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I will try but I don't think it is going to work. Whenever I connect the tablet by USB I get the usb connecting sound followed immediately by the USB disconnect sound - this just continues to happen every 4 seconds or so all the time that the device is connected. At the moment I have it on charge as once the error screen comes on it doesnt seem to go off for a very long time and then it wont start unless I charge it first. After a few minutes on charge - The firmware upgrade encountered an issue message comes up. I am going to leave it a while until I am sure it is fully charged and then try what you suggest - not optamistic though since I now realise that it is not even connecting properly. I just have a bad feeling about this. I had to disconnect it from the power yesterday because the error screen stays on continuously and the device starts to get warm
Assuming that I ever manage to get a stock image installed will this mean I can go back to normal kies updates - all I really wanted was the standard samsung android O/S but with super user added.
Unfortunately I had read the linked article a while back and what made me more confident was the statement that said it was "virtually impossible to brick this device"
Since it's still going into Charging mode and spitting out error messages, it's not completely bricked. It's just in a reboot loop (a.k.a. soft brick).
Keep trying to get it into Download mode. Sometimes the timing is a little tricky if it's in a boot loop.
1. Disconnect it before trying to get it into Download Mode. If it's plugged in (charger or PC), the device will go into Charging mode instead.
2. Hold the Power button for 10 seconds to make it reboot.
3. When you see the screen turn off, let go of Power and then press and hold Power and Volume Right/Up.
4. If done correctly, it will immediately go into Download Mode. If you see the Samsung logo instead, repeat from Step 2.
some progress but still stuck - any more ideas please
samsgun357 said:
So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Hi well thanks -
when I connected Odin it did show up yellow and so I downloaded the P5110 stock from from the other thread - all went well and it reported all OK and re-booted - saw the animated sequence but now it has stalled on the samsung logo and still wont connect to kies
So still stuck but at least it has moved on - The instructions on the other page were a little unclear about one stage
It said if there was pit file included to set something and tick repartition - this was all in one line and so I assumed part of the pit instruction - as there was no pit file I did not tick re-partition - I wonder if I should have done?
I have just reconnected to ODIN and the ID Com is still lit up yellow so presumably I could try running it again, or should I look on here for another stock rom - I am wondering if I have somehpw scewed up the bootloader and if so how I go about restoring it
ODIN is the only thing it connects to right now
Hi,
I rooted my brandnew GT-P3110 with cf, flashed pacman and cwm recovery. I do not blame anybody alse for my issues but myself. I guess I messed up the restoring of NON-system-apps:
After a day of troublefree use the tablet randomly rebooted and came back with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". No booting into recovery possible, no booting into download mode, no regular boot. Just the same message over and over again. Battery is unremovable.
I installed Kies, updated it, it downloaded drivers but under "emergency recovery" my tablet didn't appear. I then followed the "Firmware Upgrade and Initialization" procedure wich downloaded the necessary files but aborted with a korean text shown in the attachment after replugging the tablet. I tried this with 2 different USB-cables on several USB-ports. Kies btw asked me to remove the battery (not possible) after entering device number and serial-number. I turned off by pressing the off button instead and it turned on again.
I uninstalled Kies, rebooted, installed the samsung drivers manually, rebooted. I installed odin 1.85 (and later 1.3) and downloaded my contry's stock firmware (and later a newer version of the same firmware and another country's stock) from sammobile. I tried to flash them first without "repartition" ticked, later with it ticked but without a pit file (i can't find it!). I got four different errors, two are attached, the third was somethign like "cant write (line 1876)" and "cant write (line 1440)".I tried three stock firmwares with two version of odin with two USB cords on everal ports on ONE computer. I remove the tablet every time, exited odin every time, run it as admin, disabled firewall, xp-antispy and antivirus. I'm on Windows 7.
Besides a million other threads I found this one, but I wasn't able to solve my issue with it: http://forum.xda-developers.com/showthread.php?t=1652398
For 48 hours i tried to solve this problem by myself. Now I hope to find out if there's a point in continuing or if I can give up and throw away the piece of samsung.
Cheers,
404
android404 said:
Hi,
I rooted my brandnew GT-P3110
404
Click to expand...
Click to collapse
Try odin 1.61 1.85 sometimes itll jar it loose
vizionforever said:
Try odin 1.61 1.85 sometimes itll jar it loose
Click to expand...
Click to collapse
I am having the same problem with a P5113. Started with stuck at the Samsung logo. Then I tried a flash from Odin that didn't work. That led to the "Firmware error" screen telling me to use Keis. Keis fails to find the tablet. Odin still sees it but doesn't get a good write.
Now all I get is the battery icon when plugged in but that's it.
Things I have tried:
1) Two versions of Odin
2) Different USB ports
3) Different PC
I also let the device sit over the weekend to completely discharge. Still nothing.
Did you (or anyone else) resolve this issue?
vizionforever said:
Try odin 1.61 1.85 sometimes itll jar it loose
Click to expand...
Click to collapse
Thanks but it didn't work.
wd5gnr said:
I am having the same problem with a P5113. Started with stuck at the Samsung logo. Then I tried a flash from Odin that didn't work. That led to the "Firmware error" screen telling me to use Keis. Keis fails to find the tablet. Odin still sees it but doesn't get a good write.
Now all I get is the battery icon when plugged in but that's it.
Things I have tried:
1) Two versions of Odin
2) Different USB ports
3) Different PC
I also let the device sit over the weekend to completely discharge. Still nothing.
Did you (or anyone else) resolve this issue?
Click to expand...
Click to collapse
Mine is still bricked. Good luck.
facing same problem in my samsung tab 2 p3100 after root
wd5gnr said:
I am having the same problem with a P5113. Started with stuck at the Samsung logo. Then I tried a flash from Odin that didn't work. That led to the "Firmware error" screen telling me to use Keis. Keis fails to find the tablet. Odin still sees it but doesn't get a good write.
Now all I get is the battery icon when plugged in but that's it.
Things I have tried:
1) Two versions of Odin
2) Different USB ports
3) Different PC
I also let the device sit over the weekend to completely discharge. Still nothing.
Did you (or anyone else) resolve this issue?
Click to expand...
Click to collapse
Dude had the same issue on my galaxy S2 and resolved it. I downloaded the
The .pit file for my gt-i9100g (http://data.hu/get/4697903/omap4_all_20110627_emmc.pit)
The stock ROM from sammobile. (http://www.sammobile.com/firmwares/2/)
The JB Bootloader
The stock JB kernel.
Opened odin v1.85.
Then i used the vol down+home+lock keys together to try to open the download mode ( but ended up in the "Firmware error " page) and connected phone to the pc. It shows "Added!" in the message box.
Repartition with the .pit and it will reboot.
Disconnect
Get into download mode and install the bootloader and it should reboot when done. Disconnect.
Get into download mode and connect
Installed the kernel through odin and reboot
Download mode again and install the ROM through odin.
If the phone gets stuck in boot loop (samsung logo over and over),
get into recovery mode ( for s2, vol up+home+lock, it needs to be pressed intermittently)
Then do a full format along with wipe cache.
And then the phone finally booted completely. :laugh: . Good Luck.
Note: I'm not sure to boot into recovery and download are the same key combos as it was for the i9100g.
novjean said:
Dude had the same issue on my galaxy S2 and resolved it. I downloaded the
The .pit file for my gt-i9100g (http://data.hu/get/4697903/omap4_all_20110627_emmc.pit)
Click to expand...
Click to collapse
Thanks. Well, I understand the theory. I have had trouble finding a PIT file that I am sure is for my device. I did save a PIT file but I think it is corrupt because using it requires me to let the battery die afterwards to get back to download mode. Same for the bootloader. I have a few things I've tried, but not sure I have one that is exactly for the GT-P5113 (in fact, I never did find a JB for the 5113 just the 5110 and it never would load).
Well no amount of coaxing has put life back into the tab
I may try again out of curiosity, but rather than invest more time I went out and bought a 32G Nexus 7 (2013 version). I would still like to get the Galaxy Tab alive again -- it has corrupted the flash twice before and each time I was able to bring it back to life. Not sure if this is an actual hardware failure or if it is just beyond partitioning.
I have a feeling if I had the right PIT and the right bootloader I could get back in business.
I can do each thing you mentioned, but my device is not getting detected by my PC. When I insert USB it says USB not recognized and it is not detected by Odin, adb and anything else. I am stuck on Boot Logo for my P3100 and when I go into recovery, it says USB not recognized. Fully messed up. Can you help me out here.
novjean said:
Dude had the same issue on my galaxy S2 and resolved it. I downloaded the
The .pit file for my gt-i9100g (http://data.hu/get/4697903/omap4_all_20110627_emmc.pit)
The stock ROM from sammobile. (http://www.sammobile.com/firmwares/2/)
The JB Bootloader
The stock JB kernel.
Opened odin v1.85.
Then i used the vol down+home+lock keys together to try to open the download mode ( but ended up in the "Firmware error " page) and connected phone to the pc. It shows "Added!" in the message box.
Repartition with the .pit and it will reboot.
Disconnect
Get into download mode and install the bootloader and it should reboot when done. Disconnect.
Get into download mode and connect
Installed the kernel through odin and reboot
Download mode again and install the ROM through odin.
If the phone gets stuck in boot loop (samsung logo over and over),
get into recovery mode ( for s2, vol up+home+lock, it needs to be pressed intermittently)
Then do a full format along with wipe cache.
And then the phone finally booted completely. :laugh: . Good Luck.
Note: I'm not sure to boot into recovery and download are the same key combos as it was for the i9100g.
Click to expand...
Click to collapse
2 years later .... did you ever unbrick this? I'm dealing with a P5113 now that's stuck at the "Firmware upgrade encountered an issue" screen. <sigh>
wd5gnr said:
Well no amount of coaxing has put life back into the tab
I may try again out of curiosity, but rather than invest more time I went out and bought a 32G Nexus 7 (2013 version). I would still like to get the Galaxy Tab alive again -- it has corrupted the flash twice before and each time I was able to bring it back to life. Not sure if this is an actual hardware failure or if it is just beyond partitioning.
I have a feeling if I had the right PIT and the right bootloader I could get back in business.
Click to expand...
Click to collapse
No. I finally sent it to one of these ebay guys who will JTAG it since I was too lazy to wire up one of my JTAG probes. They worked on it and said it was simply dead and the only alternative would be to replace the flash chips.
Bought a Nexus 7.
I've got the pit files for P311x and P3100 on my website https://sites.google.com/site/jrc2swebsite/downloads/samsung-galaxy-tab-2-70-p31xx
Dear XDA users,
I got a P5110 from my grand parents. Its barely used and looks like new. It dead,dead,dead,dead,dead. At first i would only charge up.
I tried to revive it with odin, but now it says Firmware has encounterd an issue).
What it does now:
It take 5 Minutes until it connects to the computer, and show "Firmware upgrade has ..." and windows makes the USB disconnected noise, and USB error noise.
It has no recovery, I tried many things but it only shows the Firmware upgrade issue, so im trying to install a custom recovery trough odin.
Trying to put Philz on it, but when Odin has finished and reset the tablet, its dead again , and nothing happend.
Wont turn on by the power button, only after 5min connected to a PC.
I have the feeling the internal storage has crashed and broke.
I OFFER 50EURO to the Person that can revive this!
Good luck.
Just a wild idea. I have a 5113 (virtually identical to yours) that my daughter stopped using about 4 months ago. When there was a screen time out, the Tab would turn off. I did a factory reset and it solved the problem. When I loaded rootbuster, the problem returned and I did a factory reset, and it again solved the problem.
Would add that it is very confusing in that there is a USB driver connection to the Tab's download mode (development driver), and a simple USB connection to the computer that allows you to copy files. If factory reset doesn't work, you should go back to the development driver and see if you can use ODIN. Here is link for development/download mode driver. http://developer.samsung.com/technical-doc/view.do?v=T000000117
decijp said:
Just a wild idea. I have a 5113 (virtually identical to yours) that my daughter stopped using about 4 months ago. When there was a screen time out, the Tab would turn off. I did a factory reset and it solved the problem. When I loaded rootbuster, the problem returned and I did a factory reset, and it again solved the problem.
Would add that it is very confusing in that there is a USB driver connection to the Tab's download mode (development driver), and a simple USB connection to the computer that allows you to copy files. If factory reset doesn't work, you should go back to the development driver and see if you can use ODIN. Here is link for development/download mode driver. http://developer.samsung.com/technical-doc/view.do?v=T000000117
Click to expand...
Click to collapse
Thanks for the reply,
I already have the latest drivers, and im using ODIN to try to flash things to it. I tried flashing a recovery, so i can install a ROM, and see if that works but no succes.
ilikecars said:
Dear XDA users,
I got a P5110 from my grand parents. Its barely used and looks like new. It dead,dead,dead,dead,dead. At first i would only charge up.
I tried to revive it with odin, but now it says Firmware has encounterd an issue).
What it does now:
It take 5 Minutes until it connects to the computer, and show "Firmware upgrade has ..." and windows makes the USB disconnected noise, and USB error noise.
It has no recovery, I tried many things but it only shows the Firmware upgrade issue, so im trying to install a custom recovery trough odin.
Trying to put Philz on it, but when Odin has finished and reset the tablet, its dead again , and nothing happend.
Wont turn on by the power button, only after 5min connected to a PC.
I have the feeling the internal storage has crashed and broke.
I OFFER 50EURO to the Person that can revive this!
Good luck.
Click to expand...
Click to collapse
What version of windows are you using? I remember having the same problem when I tried using ODIN on Windows 8.1 as that does some weird things with drivers.
Make sure to not install KIES - uninstall if installed.
"Firmware has encounterd an issue" - Odin works on that screen
In Odin uncheck auto-reboot.
Flash latest TWRP.
Wait 2 min, now unplug the tab from PC.
Press the key combo to boot into recovery directly.
Where are you from?
Hey guys!
So basically I will start from the top:
1. Device is Samsung Galaxy Note 10 Lite (SM-N770F) (F/DS if it matters really)
What happened is:
I've wanted to install Android 11 update on my phone - downloaded SamFirm app, searched for correct firmware for my region (I've made sure to select appropriate device and region).
Then I've downloaded Odin (3.14.1), loaded all files correctly - no errors or anything, started the process in Odin and after some time I got an error on the phone - Custom Binary(SUPER) Blocked By OEM Lock.
Now what happens is that I can't do literally anything with my device - it's turned on constantly on the same screen, on the top I can see the above error in red font, while on the center of the screen there is message "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." - which I of course did, but Smart Switch doesn't even see the device or anything.
I can't turn off the device - while I press power and volume down button, it just goes black for a moment and comes right back up on the same screen no matter what.
Although, I think it's in downloading mode - Odin still sees it correctly (when I plug it in or out I can see changes in Odins screen).
Tried downloading older versions through SamFirm, other versions of Odin, other USB in computer, other cable - no luck at all.
Did I fully bricked the device? Or is it just soft bricked? Is there anything I can do now? Can Samsung center help me? I've tried chatting with them but they just sent me to their facility.
I'd do literally anything to fix this. Please help me, I'm desperate.
If you can get into recovery, i would try factory reset there. Then go to downloadmode and try complete new flash of newest version with csc (not home_csc). But im not sure, wether it is possible to flash with odin if bootloader is not unlocked in this new samsungs. I allways used odin with unlocked bootloader.
can't get into recovery - only thing I see is the above mentioned screen and there is 0 possibility of going anywhere else
priamusx said:
Hey guys!
So basically I will start from the top:
1. Device is Samsung Galaxy Note 10 Lite (SM-N770F) (F/DS if it matters really)
What happened is:
I've wanted to install Android 11 update on my phone - downloaded SamFirm app, searched for correct firmware for my region (I've made sure to select appropriate device and region).
Then I've downloaded Odin (3.14.1), loaded all files correctly - no errors or anything, started the process in Odin and after some time I got an error on the phone - Custom Binary(SUPER) Blocked By OEM Lock.
Now what happens is that I can't do literally anything with my device - it's turned on constantly on the same screen, on the top I can see the above error in red font, while on the center of the screen there is message "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." - which I of course did, but Smart Switch doesn't even see the device or anything.
I can't turn off the device - while I press power and volume down button, it just goes black for a moment and comes right back up on the same screen no matter what.
Although, I think it's in downloading mode - Odin still sees it correctly (when I plug it in or out I can see changes in Odins screen).
Tried downloading older versions through SamFirm, other versions of Odin, other USB in computer, other cable - no luck at all.
Did I fully bricked the device? Or is it just soft bricked? Is there anything I can do now? Can Samsung center help me? I've tried chatting with them but they just sent me to their facility.
I'd do literally anything to fix this. Please help me, I'm desperate.
Click to expand...
Click to collapse
I experienced similar situation, but in my case, even my phone stuck in download mode screen, ODIN did not detect my phone, even PC wasn't response when plug in USB cable. As same as you say, when I tried to power off, it was power on itself and "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software" message appear on screen.
Then I tried to enter download mode again in download mode screen, by pressing power off, and after screen go black press immediately volume up+down. After that phone enter the download mode screen (again), it was looks like the same, but this time I was able to install firmware. Actually I really dont understand why this method work but you can give a try.
Unfortunately, still no luck.
But I've thought about other thing. Do you think it's possible to use .PIT file and re-partition option in Odin?
From what I've read everywhere this will wipe all partition data (so basically it should wipe every single thing) from the device, so it should be possible to overcome this oem lock, shouldn't it? Or will I just brick the device even further? I'm kinda desperate here as the phone is about 2-3 months so it's as brand new...
Edit: I think I've found another issue here. My device model is SM-N770F/DS so it's a Dual Sim model, while everywhere I only see firmware for SM-N770F so without dual sim. May it cause problems as well? How about the above option with flashin firmware with pit file and wiping partitions?
If you have figured it out by now good for you. If not, that emergency screen you see is nothing to fear. You can flash firmware with Odin from that screen...no worries your not bricked. Just do as you would if the device were in download mode..flash away.
Was your bootloader unlocked?