Develop Bugs

[Q] SM-T210R Problems after update

First this is the kids tablet and I don't spend tons of time on the Samsung side as I am mostly hanging in the HTC parts of XDA. I've spent a lot of time in this forum this week reading up and trying to find a solution but I am getting nowhere.
I have downloaded Odin v 3.09 and have been trying to load the firmware update for the WiFi only version and even though it seems to complete fine with no errors when it boots it seems that most everything generates a force close (settings, start wizard, etc.), or what appears to be system reset (not a full reboot but just the OS resets).
I have redownloaded the update a couple times thinking that perhaps I got a bad download or something but that hasn't made a difference.
I have tried downloading the previous firmware a couple times and loading that but I can't seem to get that to boot as it sticks on boot screen.
I just don't know what to do with this at this point and really need some help from the community to get this functional again (my kids are driving me nuts!!!)
Thanks!
MG

moregadget said:
First this is the kids tablet and I don't spend tons of time on the Samsung side as I am mostly hanging in the HTC parts of XDA. I've spent a lot of time in this forum this week reading up and trying to find a solution but I am getting nowhere.
I have downloaded Odin v 3.09 and have been trying to load the firmware update for the WiFi only version and even though it seems to complete fine with no errors when it boots it seems that most everything generates a force close (settings, start wizard, etc.), or what appears to be system reset (not a full reboot but just the OS resets).
I have redownloaded the update a couple times thinking that perhaps I got a bad download or something but that hasn't made a difference.
I have tried downloading the previous firmware a couple times and loading that but I can't seem to get that to boot as it sticks on boot screen.
I just don't know what to do with this at this point and really need some help from the community to get this functional again (my kids are driving me nuts!!!)
Thanks!
MG
Click to expand...
Click to collapse
Did you do a factory reset before upgrading. The jump from 4.1.2 to 4.4.2 included a lot of changes. If you didn't, try that; then report back.
Our 4.1.2 version roms use the /data/media directory as the "internal sdcard".
4.2+ versions of Android use the /data/media/0 directory due to support for multiple users.
If you switch to a different Android version, you need to be aware of this difference.
I recommend wiping "internal sdcard" also before switching from 4.1.2 to 4.4.2.
Click to expand...
Click to collapse

gr8nole said:
Did you do a factory reset before upgrading. The jump from 4.1.2 to 4.4.2 included a lot of changes. If you didn't, try that; then report back.
Click to expand...
Click to collapse
Thank you for the reply. At some point in the process I did try that but didn't initially before I started. I have tried that again today and then loaded again and still get the force closes, and such. Tablet is really unusable at this point.
Thanks,
MG

[Q] Kernel Panic Upload mode

My SM-T210 (Galaxy Tab 3 7.0 Wifi) XSP region which was running fine for over a year starting giving me the Kernel Panic Upload Mode errors in the last few days.
It is absolutely stock - still running Android 4.1.2, never rooted, etc.
From previous threads on this error, it seems that doing a factory reset in recovery ought to fix this. However, I can't quite seem to do the factory reset. Doing it from Android settings just seems to go into recovery. And from recovery, after telling it to do the data wipe/reset and rebooting, I'm back into Android with all of my apps and settings still in place.
So I'm a newbie and don't know what to do from here. Any suggestions please?
Ok, I've tried to flash the TWRP recovery by following the instructions at http://forum.xda-developers.com/showthread.php?t=2437219. But even after getting "RES OK", I did the reboot into recovery, and went straight back into the stock recovery. wtf... it seems as though writes to the internal storage are accepted but ignored.

Still hoping for some pointers, please...
I'm guessing that the problem is that the writes appear to succeed but actually did not take place at all. To test this, I've booted up, used ES File Explorer to create a "test" file and rebooted. Upon rebooting, the file has disappeared even though the kernel did not panic during this process.
Has anyone seen such symptoms before? My search-fu is lacking, and I can't find appropriate search results.

webbrowser said:
Still hoping for some pointers, please...
I'm guessing that the problem is that the writes appear to succeed but actually did not take place at all. To test this, I've booted up, used ES File Explorer to create a "test" file and rebooted. Upon rebooting, the file has disappeared even though the kernel did not panic during this process.
Has anyone seen such symptoms before? My search-fu is lacking, and I can't find appropriate search results.
Click to expand...
Click to collapse
I have heard many stories before about kernel panic upload mode. I believe it might be a kernel issue in which changing it would be a good idea or some sort. That's all I know ?
-DUHA

DUHAsianSKILLZ said:
I have heard many stories before about kernel panic upload mode. I believe it might be a kernel issue in which changing it would be a good idea or some sort. That's all I know
-DUHA
Click to expand...
Click to collapse
Roger. I've tried to flash the TWRP recovery via ODIN, but the writes did not seem to work despite "RES OK". Flashing recovering is required before I can change the kernel right?

For what it's worth, my symptoms seem to match the "emmc brickbug".
I've found what appears to be instructions on how to fix this after the brickbug has occured here (these are for different devices, but I suppose it oughta work):
http://forum.xda-developers.com/showthread.php?t=1823918
http://forum.xda-developers.com/showthread.php?t=1667886
Unfortunately, I can't seem to run the zips from my stock recovery, as signature verification fails. And I don't think I can install a custom recovery at this point now, since all writes seem to fail. So I'm still stumped, and I think I have a brick :crying:

Help removing "dm-verity?"

Hey guys,
I've had this phone for a while; bootloader unlock/rooted a few months ago without any issues. I'm looking to sell the phone, and wanted to restore everything back to stock:
So I ODIN'd to stock CPF3. I noticed that the phone was suspiciously laggy, and found out that it's caused by spyware left behind by KingRoot, and is fixable by clearing the EFS folder from root.
So I went back to BPA1, unlcocked BL/rooted, and deleted everything from the efs folder. After reboot, phone was running good as new without any hitches.
The issue arised when I tried to ODIN flash the CPF3 full firmware provided by hsbadr. ODIN would go fine, but when the phone would reboot into the recovery, I'd get a dead Android bot saying "DRK is not installed. Please install DRK" or something along those lines. I ignored it, and the phone booted with no issues.
When I tried to factory reset from within the OS, however, I'd face the DRK and dm-verity verification failure when the phone would boot into the recovery, and it would'nt continue with the factory reset.
Now alarmed, I backed down to BPA1, and when the phone would boot back into recovery after a successful ODIN flash, the process would restart the phone when the progress bar would hit ~1/3 of completion (this happens in the recovery).
Rebooting into the recovery would show an orange "dm-verity failed," and when I try to OTA to CPD1 via external sd, It gives the "cannot update from external sd" error.
Googling the DRK keyword showed that it is KNOX being tripped that caused the issue. So far, neither Google nor the xda-forums have showed how to fix the issue on the 910-V.
I really want to restore the phone to as close-to-factory as possible, and removing this DRK issue would be a great help. Any help is greatly appreciated.
Edit #1: I have tried both this guide and this one to absolutely no avail. What am I missing? DM-Verity refuses to go away
EDIT #2: My brother also has a 910-v, and he hasn't cleared his EFS folder (stupid me for not making a back-up, eh?). Is it safe to clear mine again, and copy-paste his EFS folder into my phone? What are some adjustments I should make to avoid a corrupted IMEI? Any help is appreciated.
EDIT#3: I've tried this method, and it removes DM-verity on the first boot. It returns after factory reset. Currently trying a few different combos of flashing kernels/recoveries etc. to see if I can get it to stick. Permanently. Is it still OK to get by bro's EFS folder?

dm-verity and lagginess
HELP!!!!!!
It is annoying to see the dm-verity failed. The phone works fine but its just at the recovery boot. I am not sure what to do. I have a Galaxy S7 on Verizon. I rooted my phone using ODIN. I unrooted it already and it did not work. I did the Verizon recovery and it did not work either. However, I am not able to access to the recovery menu in my phone. I am rooted and the phone is working fine. It is just slow and it has some glitches on some apps like Snapchat... The video is so laggy it is not even funny. I am not sure if that has anything to do with the dm-verity but I need this 3 issues fixed ASAP. I will forever be grateful. I used my friends S7 that is not rooted and it was SO FAST! I am not sure if the root has anything to do with the lagginess but I doubt it because I have read here in XDA that root actually makes your phone faster.
1) Remove and fix the dm-verity
2) Fix laggy snapchat
3) Laggy phone overall.
My phone is Galaxy S7 on Verizon. SM-G930V

notsonerd said:
HELP!!!!!!
It is annoying to see the dm-verity failed. The phone works fine but its just at the recovery boot. I am not sure what to do. I have a Galaxy S7 on Verizon. I rooted my phone using ODIN. I unrooted it already and it did not work. I did the Verizon recovery and it did not work either. However, I am not able to access to the recovery menu in my phone. I am rooted and the phone is working fine. It is just slow and it has some glitches on some apps like Snapchat... The video is so laggy it is not even funny. I am not sure if that has anything to do with the dm-verity but I need this 3 issues fixed ASAP. I will forever be grateful. I used my friends S7 that is not rooted and it was SO FAST! I am not sure if the root has anything to do with the lagginess but I doubt it because I have read here in XDA that root actually makes your phone faster.
1) Remove and fix the dm-verity
2) Fix laggy snapchat
3) Laggy phone overall.
My phone is Galaxy S7 on Verizon. SM-G930V
Click to expand...
Click to collapse
You might want to go to the verizon S7 forums for that. These are the 910-V forums. Sorry for not being able to help.
Look for how to ODIN flash full stock recovery/firmware in the S7 forums. That is all I can say.

SirLaughsalot said:
You might want to go to the verizon S7 forums for that. These are the 910-V forums. Sorry for not being able to help.
Look for how to ODIN flash full stock recovery/firmware in the S7 forums. That is all I can say.
Click to expand...
Click to collapse
I have a vzw note 4 and I'm getting the dm verity verification failed when I try to a factory reset...been at this for a week so I'm pleading for help.
I posted on dr.cools attempt to fix this before I saw this post. sorry for double posting.
edit--I'm attempting the OP's number 3. will report back. Downloading BOG5 because that's what my version shows on the phonw
Question--Right now I'm stuck at BOG5. Do I need to do anything special to get to PA1 so I can start the root/unlock process again?
edit--just flashed firmware and modem and was able to do a factory reset...now back to rooting and bootloader unlock, hopefully.

Totally wiped my samsung galaxy sm-t111nq device. HELP!!!!

hello everyone,
recently i wanted to upgrade my Samsung galaxy tab 3, model:sm-t111nq device to see if it would install the telephony functionality on my device because it was running on a customized stock firmware (from samsung i guess) with no telephony functionality which means i can't make or receive calls. I flashed the firmware with odin two times but it got interrupted the second time, so it couldn't boot up. i searched for solutions on the internet, any time i tries to flash the firmware using odin it stops at file analysis and every time i try flashing with recovery it says "E:/ could not mount system" or something like that, then i installed twrp recovery to see if i could remove the firmware and flash it again still the same error. Now this is where i messed up, I initially wanted to just wipe the cache completely at first following a solution online but after doing this it still didn't work and so i felt i needed to wipe more than just that, and with no backup i went ahead to wipe the whole thing including EFS, system, data, preload, i basically selected all the boxes there :crying:. now i really dont know what to do seems like i'm the only one that messed up this bad. Please help me out. Can i use the back up of another of the same type of device to restore it and get it running. Please help, just wanna use it again even if its not gonna come with the complete functionalities.

Sprint galaxy s3 e:failed to mount /es (invalid argument)

Hey guys, been reading through the threads and not really finding a clear answer or solution to this problem. This is a completely stock sprint sph-l710. I started getting this box with yellow lettering overshadowing the primary display of which I've learned indicates the phone is in 'factory mode'. I thought performing a factory reset would fix this but it did not. I noticed when you boot the phone in recovery mode I see the efs error. I am thinking the underlying issue is with fixing the efs problem. Now that I have reset the phone I no longer have data network access, im guessing because of this factory mode. I am new to this and not real understanding of the lingo everyone uses. From what I've read Im worried im going down a rabbit hole if i start tinkering. I am looking for clear instructions to repair what I think is corrupted software (I'm guessing the operating system software). The instructions I've seen seem to skip steps that are probably rudimentary to everyone else but leaves me without a starting place. I have downloaded oden but i am not certain again without precise instructions that I am not going to permanently mess up my phone.. there appear to be a number of variations of this device and i want to make sure the instructions I get will work on mine. I will take any advise on getting this resolved. I am not opposed to rooting the phone either if that fixes the problem (no idea how to do this, never tried, but some threads on here I think I can follow to do it safely). With that said, different threads also seem to indicate (emphasize 'seem to') that team win recovery can fix this but there are no clear responses regarding my issue of a solid fix. Thank you for any help

timbow4 said:
Hey guys, been reading through the threads and not really finding a clear answer or solution to this problem. This is a completely stock sprint sph-l710. I started getting this box with yellow lettering overshadowing the primary display of which I've learned indicates the phone is in 'factory mode'. I thought performing a factory reset would fix this but it did not. I noticed when you boot the phone in recovery mode I see the efs error. I am thinking the underlying issue is with fixing the efs problem. Now that I have reset the phone I no longer have data network access, im guessing because of this factory mode. I am new to this and not real understanding of the lingo everyone uses. From what I've read Im worried im going down a rabbit hole if i start tinkering. I am looking for clear instructions to repair what I think is corrupted software (I'm guessing the operating system software). The instructions I've seen seem to skip steps that are probably rudimentary to everyone else but leaves me without a starting place. I have downloaded oden but i am not certain again without precise instructions that I am not going to permanently mess up my phone.. there appear to be a number of variations of this device and i want to make sure the instructions I get will work on mine. I will take any advise on getting this resolved. I am not opposed to rooting the phone either if that fixes the problem (no idea how to do this, never tried, but some threads on here I think I can follow to do it safely). With that said, different threads also seem to indicate (emphasize 'seem to') that team win recovery can fix this but there are no clear responses regarding my issue of a solid fix. Thank you for any help
Click to expand...
Click to collapse
Odin will flash the factory firmware for you. Get firmware from sammobile. Look for sph L710 device, and firmware with NJ2 in the name. Put phone in download mode, (power off then hold power+home+volume down) plug in phone to pc. Wait till Odin says added. Click AP in odin, select firmware you downloaded, click start. When it's done, unplug phone, remove battery, put it back in and reboot.
This may not fix your efs partition, but it's the first thing to try.
Odin
I found the thread for nj2 firmware here

issue still persists
Hey Madbat, thank you so much for reaching out to me and giving me the advise. Installing the firmware through odin was really easy. Thank you for that! However, it did not fix the issue. When the phone came back up it still has the exact same problem. I am going to attach a couple pictures to show you what i am seeing... Really appreciate your time and help!
hell, sorry it says im a new user and wont let me post the pictures...

timbow4 said:
Hey Madbat, thank you so much for reaching out to me and giving me the advise. Installing the firmware through odin was really easy. Thank you for that! However, it did not fix the issue. When the phone came back up it still has the exact same problem. I am going to attach a couple pictures to show you what i am seeing... Really appreciate your time and help!
hell, sorry it says im a new user and wont let me post the pictures...
Click to expand...
Click to collapse
Sorry, I never had that issue. Maybe someone else will chime in with experience on the efs partition. That's not a triband s3 is it? (Sph l710t?) T at the end means triband. Second thought, I don't think the firmware would have flashed if it was triband.
How did you wipe your efs?

Its not a tri band. Just SPH-L710. Wish this forum would let me post the pictures of what my phone is doing.. Since the firmware doesnt correct the issue I would think then its a problem with the operating system itself. I have been scouring the web and have found various threads specifically about efs repairs but they entail doing things that seem awful complicated. And i dont know if those things work on my model phone. Maybe rooting the phone gets deep enough to over write or repair the issue. Is there not a way to restore the operating system itself maybe or is that what a replacement ROM does? I am thinking of trying my hand at rooting the phone and seeing what happens. One thread indicated TWRP would backup and restore the EFS file. Im thinking if it backs up a corrupt efs file what good is that, maybe it fixes it too. Found an excellent video on XDA for rooting the S3. Hopefully it or I dont make it worse. Love to get this one fixed but i guess the reality is the phone is old. Thank you for the input

timbow4 said:
Its not a tri band. Just SPH-L710. Wish this forum would let me post the pictures of what my phone is doing.. Since the firmware doesnt correct the issue I would think then its a problem with the operating system itself. I have been scouring the web and have found various threads specifically about efs repairs but they entail doing things that seem awful complicated. And i dont know if those things work on my model phone. Maybe rooting the phone gets deep enough to over write or repair the issue. Is there not a way to restore the operating system itself maybe or is that what a replacement ROM does? I am thinking of trying my hand at rooting the phone and seeing what happens. One thread indicated TWRP would backup and restore the EFS file. Im thinking if it backs up a corrupt efs file what good is that, maybe it fixes it too. Found an excellent video on XDA for rooting the S3. Hopefully it or I dont make it worse. Love to get this one fixed but i guess the reality is the phone is old. Thank you for the input
Click to expand...
Click to collapse
Backing up and restoring it won't help. You already installed a new operating system ( that's what the firmware is).the efs is part of your radios. If I remember correctly it contains your imei and other important things specific to your phone.
You may be out of luck there dude. Don't know how you wiped your efs.
Rooting this phone is simple. Just flash TWRP with Odin. Download the Twrp image from their site. Same as flashing the firmware, only you select recovery instead of AP in odin and select the Twrp image.tar instead of the firmware tar.
https://dl.twrp.me/d2spr/
Use the top on the page. (Newest)
And then use twrp to flash either SuperSU, or Magisk.
Done.
Flashing a custom rom will not fix your issue. You need a working efs. Flashing any operating system will not fix it (you already flashed the whole operating system).
Twrp can restore an efs, but only if you have a working one to backup first. You were right about backing up yours now and restoring will do nothing.
Has it ever been activated?

Prior to this, every once in awhile when i changed a battery out and turned the phone on it would have a pop-up screen tell me something was bad and the phone needed to be reset (something along those lines) and i always just turned the phone back off and on and it booted up fine each time. That may have been an indicator that something, file or system file maybe was corrupted. Then a few week ago when it booted up it started doing this whole thing. Prior to me factory restoring the phone here recently it was completely functional but since the restoration it will no longer connect me to the network. If you goto settings and click on some system features it will turn the network on for that specific function (temporarily) but does not give me any other access. It tells me that the network works but it being blocked (maybe because of the factory mode issue). The wifi works and i can make and receive calls. Still manageable but very annoying. Im going to try your instructions with installing TWRP. If i am successful then maybe i can also get into the system files and possibly restore the broken one.. Thanks again

update
So I have successfully rooted the phone by intstalling TWRP ver 3.2.1 and using TWRP to flash SuperSU ver 2.82. I also installed root explorer to get access to system files. I gained access to the EFS folder and it is empty. So now I'm not understanding if the folder is completely empty how does the phone still work at all? More research led me to a XDA developer that put together a program called EFS Professional which is supposed to backup and restore efs or imei data. Really slick program, basically takes the complication out of locating and backing up the EFS information yourself. (I would include a link but I still cant..) It includes an ADB shell and the ability to make some changes to the phone including directly turning off factory mode . It also had me install an application called BusyBox Pro which is also a very handy tool for getting access to system files. What I don't understand is that the EFS Professional program seems to locate the efs information on my phone and backups it up and then restores it from said backup however when I look at the efs folder its empty. Perhaps not all the efs information is located in the efs folder. And of course since that folder is empty the function of turning factory mode off fails because it cant find the files. I have found a few threads that has very simple instructions once you have super user access you can go right into the efs folder to factory mode and simply turn it off. Mine is empty.. So again the problem continues. Possibly with access to the ADB shell and more help from folks on here I can figure out a way to restore my efs information. I don't know if the efs information can be used from a another same model phone, I'm guessing not if it has a specific imei identification. Im working hard on this but still unsolved. I know way more at this point then I did but I think I still know just enough to be dangerous. Thankfully my phone is still functional at this point..