Develop Bugs

endless reboot nothing works so far

I screwed and Updated the wrong NV items of the incredible and Now it just reboots. So far I can only get to the "HBOOT" bootloader screen. All other options causes the Dince to reboot and start the endless process again. also I cannot get to recovery mode because any option that requires me to I get out of bootloader starts the booting process and reboots. I have tried flashing stock rom "3.26.605.1" but after the update finished and rebooted it started the endless reboot again. is there a way I can reset the NV items back to the stock setting? Am I screwed?
Some other info that I hope will help.
I have two backups that I made using rom manager prior to the NV updates. I also have a full backup of the NV items using CDMAWorkshop before I did the update as well. Hopefully there's a way for me to write the NV items back

I'm assuming you can't restore your backups? Sounds like you might have to flash the stock recovery image. WWW.dougpiston.com should have a recovery image you can flash in hboot.
Sent from my ADR6300 using XDA App

Nope, that was the first thing I tried. it tells me everything is update and ask me if I want to reboot. once I reboot it keeps rebooting. The way I see it my issue is a little different than the usual end reboot problem. I think most people screwed up the PPC portion of the device so restoring or flashing a stock rom fixes it. I think I screwed up the phone portion of the device which usually don't get effected by a rom update. Is there anything that will clear everything up and force me to reprovision my phone service cause I think that's the only way i can fix this? or is there a way I can connect to diag mode of the phone without it fully booting?

Ok so I did a little more research and this thread here below seems be the solution I'm looking for but would the "HBOOT" image used for the EVO work on the incredible? I of course won't use the radio rom indicated but I was planning on using the other files. Anyone see anything that wouldn't work on my incredible?
http://forum.xda-developers.com/showthread.php?t=805612&page=3

Hm, I really don't know about NV items and messing with your phone on that level. I'm not that technically inclined, I'm sorry!
I've read through threads before where people get stuck in a bootloop and it seems that flashing the PB31IMG.zip in HBOOT usually fixes the problem and restores the phone to an out-of-the-box state. I don't know if that would work for you but that's about all I can think of. Sorry I can't help more.

SUCCESS!!
after much search I manage to find all the Dinc equivalent files in the EVO fix I posted previously and surprisingly enough it works!! Anyone else that has this problem can find the files and instruction in my post here.
http://forum.xda-developers.com/showthread.php?p=12828082#post12828082

Nice, glad you got it working!

[Q] No ROMs taking, keep getting no MD5 message, phone close to bricked.

I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.

gvazquez82 said:
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
Click to expand...
Click to collapse
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient

MrHaPpY66 said:
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
Click to expand...
Click to collapse
First of all thank you for trying to help me, I hope you are having a good Thanks Giving.
I used the thread you linked to, and downloaded the version with out knox. I followed the instructions
transferred ROM and flashed kernel file to SD card
used odin to flash TWRP,
used twrp to flash rom and kernel file.
and it takes the file thankfully, there's only one issue. My phone can't make or receive calls/texts. Is yours able to?

I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Next Update
the bootloader I flashed apparently flashed to the external sd card? I flashed another one and it is booting from the internal sd. I had to flash a different modem the one in the bootloader/modem file I flashed from the link above didnt take? I got most everything sorted out, but im getting tired, it has been an all night adventure. its 08:23 est now
sorry for the delay in updating this I had to get some rest.

theramsey3 said:
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Click to expand...
Click to collapse
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.

spongdangly said:
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
Click to expand...
Click to collapse
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?

gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.

theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I will give that a shot, but what's an APN, sorry. And how do I create one, and is it needed for me to do so?

gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
It should be, I'm working right now so I don't have time to fine the guide on how to inject your IMEI. If I remember correctly it involves using QPST. If you have an old (or any) working Nandroid backup that should fix the problem.
FYI, make sure you don't use the guide for the international S3 as it has different hardware and folder structure/contents.
As for the APN, it should automatically fill itself in since it reads it off the SIM Card (I might be wrong).

theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I tried it and it work!!!!!!!!!!!!!!!!!
67 texts just came in. Sir, I thank you oh so kindly. You have made this gloomy rainy day oh so joyous.

No problem. Glad I could help you.
The real credit should go to -Mr.X-, loserskater and anyone else(no disrespect there were alot of files) whose stuff I tried to flash lastnight thank you all in the dev community who contribute.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.

gvazquez82 said:
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
Click to expand...
Click to collapse
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.

flexfulton said:
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
Click to expand...
Click to collapse
do you know of a good stable kit kat like ROM I could use for the s3? And any speculation as to why the ROMs werent taking for me?

[Q] Failed rooting of GT-I9195

I have been trying to root my Galaxy S4 Mini (GT-I9195). I successfully installed clockworkmod recovery (v6.0.4.6) and that seems fine... but I currently have an expensive brick after attempting to root. I've tried GT-I9195_RootKit_v2.zip and S4Mini_RootKit_v2.zip (I don't know the difference between these, they are very different sizes).
Whichever of the two files I use, the rooting appears successful, warranty is now void... install from sdcard complete... etc... but upon reboot it shows the initial screen (phone name & model, with "set warranty bit: kernel"), then screen goes black, startup noise plays (sometimes it cuts out before finishing) and then nothing. I've tried various cache wipes, data wipes / factory resets but no luck.
I'd appreciate any suggestions you may have.

helenst said:
I have been trying to root my Galaxy S4 Mini (GT-I9195). I successfully installed clockworkmod recovery (v6.0.4.6) and that seems fine... but I currently have an expensive brick after attempting to root. I've tried GT-I9195_RootKit_v2.zip and S4Mini_RootKit_v2.zip (I don't know the difference between these, they are very different sizes).
Whichever of the two files I use, the rooting appears successful, warranty is now void... install from sdcard complete... etc... but upon reboot it shows the initial screen (phone name & model, with "set warranty bit: kernel"), then screen goes black, startup noise plays (sometimes it cuts out before finishing) and then nothing. I've tried various cache wipes, data wipes / factory resets but no luck.
I'd appreciate any suggestions you may have.
Click to expand...
Click to collapse
you can try this,it works like a charm:http://forum.xda-developers.com/showthread.php?t=1980683

helenst said:
I have been trying to root my Galaxy S4 Mini (GT-I9195). I successfully installed clockworkmod recovery (v6.0.4.6) and that seems fine... but I currently have an expensive brick after attempting to root. I've tried GT-I9195_RootKit_v2.zip and S4Mini_RootKit_v2.zip (I don't know the difference between these, they are very different sizes).
Whichever of the two files I use, the rooting appears successful, warranty is now void... install from sdcard complete... etc... but upon reboot it shows the initial screen (phone name & model, with "set warranty bit: kernel"), then screen goes black, startup noise plays (sometimes it cuts out before finishing) and then nothing. I've tried various cache wipes, data wipes / factory resets but no luck.
I'd appreciate any suggestions you may have.
Click to expand...
Click to collapse
Which instructions did you follow to root because it should have been these? The GT-I9195_RootKit_V2 zip is not mentioned and should not be used. It sounds like you have wiped your ROM thus it has nothing to run after initial boot, so try to flash any of the ROM's available - don't ask which one is best, if you read some signatures you can see what some folks are using.

MarkAndroid.UK said:
Which instructions did you follow to root because it should have been these? The GT-I9195_RootKit_V2 zip is not mentioned and should not be used. It sounds like you have wiped your ROM thus it has nothing to run after initial boot, so try to flash any of the ROM's available - don't ask which one is best, if you read some signatures you can see what some folks are using.
Click to expand...
Click to collapse
Thanks... easy now you've told me what's wrong! Was thinking I'd probably stick with the stock ROM but seeing as I've wiped that anyway, have stuck cyanogen on there and all good again.
I think I got the file from the instructions here... it was in one of the rar files. http://dottech.org/147716/how-root-samsung-galaxy-s4-mini-gt-i9190-gt-i9195-and-install-cwm-guide/ - would've saved a bunch of time if I'd found the right instructions in the first place. Oh well, it's nice to have a phone again

helenst said:
Thanks... easy now you've told me what's wrong! Was thinking I'd probably stick with the stock ROM but seeing as I've wiped that anyway, have stuck cyanogen on there and all good again.
I think I got the file from the instructions here... it was in one of the rar files. http://dottech.org/147716/how-root-samsung-galaxy-s4-mini-gt-i9190-gt-i9195-and-install-cwm-guide/ - would've saved a bunch of time if I'd found the right instructions in the first place. Oh well, it's nice to have a phone again
Click to expand...
Click to collapse
Thats good:good:, CM should be slicker and easier on the battery than stock (autobright actually works properly for example). If you need to go back to stock you can always find it on the sammobile site
I've never come across that web site you linked to. Best to use xda in all things Android

I've got the same problem
MarkAndroid.UK said:
Which instructions did you follow to root because it should have been these? The GT-I9195_RootKit_V2 zip is not mentioned and should not be used. It sounds like you have wiped your ROM thus it has nothing to run after initial boot, so try to flash any of the ROM's available - don't ask which one is best, if you read some signatures you can see what some folks are using.
Click to expand...
Click to collapse
Exactly the same problem as helenst' one here. After reading for 3 hours, I am stuck and can not understand what is the solution.
Please, help me! This is my mother's phone and I have to fix it till the next morning.
Thanks!
PS: I thought that the problem was due to using the wrong file in ODIN 3.09, that is I clicked on AP, but browsed the recovery-clockwork-6.0.5.1-serranoltexx.tar , which is .ZIP, instead of the the MD5 file.

[Q] Root Issues - Are these known? Are there fixes?

I purchased my Pixel 2 XL from the Google store. I had just upgraded to the 8.1 OTA a few days before when i came across this video and used it to root my phone:
https://youtu.be/nFD9sa-WdUM
Here's the basic steps i took:
Unlock dev options and turn on OEM Unlocking
Boot to stock recovery
Go to his highonandroid site and download TWRP 3.1.1 beta2 (img and zip), an outdated fastboot.zip, magisk 14.5, and the USB drivers which i didnt download because my computer is already recognizing my device just fine.
Extract the fastboot files to a new folder and copy the twrp img file to the fastboot folder.
In CMD, unlock the bootloader with fastboot and reboot phone.
Connect phone as storage device, copy over twrp zip file and magisk 14.5 zip files to root folder on the phone, reboot into recovery
Use fastboot to boot the twrp image that we copied to fastboot folder to get into twrp
Unhook the USB cable, set TWRP to read only, install TWRP, hit home button, then install Magisk and reboot
Once booted up, get into Magisk, download proprietary software, run checks and done.
Once this was done, my fingerprint scanner and wifi no longer worked. I could turn wifi on but it would never find anything. I also received the error when rebooting the phone that says "There's an internal problem with your device. Contact your manufacturer for details." When this message is on the screen, if i dont touch the phone and the screen times out, it flickers really bad and never actually shuts off until i unlock it and hit the OK button.
So i decided to give it another go and ran into some big issues. I figured that i used 8.0 instructions on 8.1 and there was enough things different that it caused problems, so i used this link to reroot:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
I went through the first 10-15 pages and the last 10-15 pages and did some searches on the thread and never found any of my issues, but found that a lot of people used different sets of steps and pretty much everything was successful as long as you didnt miss anything and used the most updated stuff. So i did, i went to googles website and downloaded the newest SDK with fastboot, adb, and all that good stuff, as well as the newest 8.1 image (there was a newer version but it had a carrier label on it so i didnt get that one), and the newest magisk and twrp.
I flashed 8.1 and the phone wouldnt boot, nor would it get into TWRP anymore, so i had to use fastboot to boot the twrp image and reinstall the recovery and magisk but it still wouldnt boot. I ran through several different steps and eventually got it to boot up with recovery working. Its the newest 8.1 image, the newest magisk, and the newest twrp, and since then magisk has updated a couple times.
Now on to my issues!
I still get the "Internal problem" popup when booting
I get a lot more random reboots
Sometimes random things just wont work, like streaming plex to my tv or loading an app or something on an app and i have to reboot and it works fine
I've seen numerous times that the "Internal problem" thing is just a mismatch between the system and vendor build.prop files. I dont know what exactly is mismatching between the two but i've tried reflashing them and all sorts of things and nothing ever fixes it.
Does anyone know if there's a fix to any of these three issues, or if maybe looking at my steps i clearly did something wrong? I'm willing to do the whole thing over again if there's a good suggestion, but once i flashed the 8.1 image and went that route, i rerooted successfully 4 times total before i quit doing it again just because of that internal problem popup, i kept figuring something went wrong or i did something wrong. I had no security or anything set before rooting or flashing or anything, and each time i reflashed the operating system, but when i flashed the OS, i had to extract the system file because i would constantly get an error that it was too big and it failed to truncate it, so i've always had to manually install it by first copying it to my phone and installing it through TWRP. Its been an adventure, but these problems suck!

PMad said:
...Its been an adventure, but these problems suck!
Click to expand...
Click to collapse
It's called training. For the error, you just need to fastboot flash the stock dtbo.img. This was fixed on the 15.1 version of Magisk so you shouldn't have that problem anymore. I can tell you that rooted, kernel and a few root apps and I have never had ANY random reboots, so one of your apps is causing it or you didn't start from a completely blank slate. Run your phone in Safe Mode for a while to see if you stop the reboots 100%. If so, one of your apps is the cause. If you still get reboots in Safe Mode, you're gonna need to re-install. I suggest using the instructions on the Google web page where you got the full image. (and try to distill your posts down a little, ffs)

v12xke said:
It's called training.
Click to expand...
Click to collapse
Every new phone is a new adventure, they are all the same but unique at the same time!
v12xke said:
For the error, you just need to fastboot flash the stock dtbo.img.
Click to expand...
Click to collapse
I'll give this a shot! Thank you!
v12xke said:
This was fixed on the 15.1 version of Magisk so you shouldn't have that problem anymore.
Click to expand...
Click to collapse
15.1 is the version i'm on now but nothing has changed. Which issue was this supposed to fix?
v12xke said:
I can tell you that rooted, kernel and a few root apps and I have never had ANY random reboots, so one of your apps is causing it or you didn't start from a completely blank slate.
Click to expand...
Click to collapse
My concern here is that my settings and apps are literally exactly the same as before root, except for magisk, its my only new app, which would lead me to believe that something Magisk is changing is causing the problem, or something else is happening that i'm not realizing yet.
v12xke said:
Run your phone in Safe Mode for a while to see if you stop the reboots 100%. If so, one of your apps is the cause. If you still get reboots in Safe Mode, you're gonna need to re-install. I suggest using the instructions on the Google web page where you got the full image.
Click to expand...
Click to collapse
The reboots are typically 1 reboot every 1 to 3 days, so its not a terrible issue but its happening and it shouldnt. For flashing the OS, after the first failure when trying to install it, those are the only instructions i've used, but i get that error when trying to install the OS that says something about how it failed to truncate the system.img file and so it wasnt installed, so my work around was to copy the file to the phones root folder, install the 8.1 image then immediately go and manually install the system.img file in twrp since its the only thing that fails, but i still have issues. What is this truncate issue?
v12xke said:
(and try to distill your posts down a little, ffs)
Click to expand...
Click to collapse
I agree! hahaha i just wanted to be clear and include all the details, otherwise everyone would have asked me question after question that i could have just included. It ends up being long, a lot happened!
I'll give that dtbo.img a shot and see what that clears up, then if there's issues with rebooting still i'll try safe mode for a few days and see what that does.
Thank you v12xke! (how do you pronounce that? haha)

PMad said:
...I'll give that dtbo.img a shot and see what that clears up, then if there's issues with rebooting still i'll try safe mode for a few days and see what that does.
Thank you v12xke! (how do you pronounce that? haha)
Click to expand...
Click to collapse
Your dtbo.img got patched by Magisk somewhere along the line and that is why the OS is throwing the error. Extract that img file from the full Google image and fastboot flash it, and the error will go away. There is a long thread around HERE on random reboots you should read. The v12xke is a car (Jaguar E-Type) I once owned.

v12xke said:
Your dtbo.img got patched by Magisk somewhere along the line and that is why the OS is throwing the error. Extract that img file from the full Google image and fastboot flash it, and the error will go away. There is a long thread around HERE on random reboots you should read. The v12xke is a car (Jaguar E-Type) I once owned.
Click to expand...
Click to collapse
So i just tried to do this and ran into one of the issues i had when originally trying to root it... I get into TWRP and it will not take any button presses, like the touch screen has become a screen (minus the touch). Is there a fix for this or do i just need to install TWRP before i use it each time it does this?

PMad said:
So i just tried to do this and ran into one of the issues i had when originally trying to root it... I get into TWRP and it will not take any button presses, like the touch screen has become a screen (minus the touch). Is there a fix for this or do i just need to install TWRP before i use it each time it does this?
Click to expand...
Click to collapse
1. You don't use TWRP to flash dtbo.img, you fastboot it while the phone is in bootloader mode.
2. TWRP works just fine if you install it and leave it installed. Make sure you are using 3.2.1-0 (img and zip).

v12xke said:
1. You don't use TWRP to flash dtbo.img, you fastboot it while the phone is in bootloader mode.
2. TWRP works just fine if you install it and leave it installed. Make sure you are using 3.2.1-0 (img and zip).
Click to expand...
Click to collapse
I was getting into TWRP to create a backup of everything and it popped up asking for my password, and i remembered reading that we have to get rid of all of our security before making a backup, so i tried to hit buttons to cancel it and nothing worked, i had to hold the power button. So i eliminated all of my security and went back thinking it was a 1 time issue but it happened again, it took me straight to the main menu but nothing would work. I'm using 3.2.1-0 like you mentioned and i cant press any buttons. I'd like to back everything up before flashing this or anything else.

PMad said:
I was getting into TWRP to create a backup of everything and it popped up asking for my password, and i remembered reading that we have to get rid of all of our security before making a backup, so i tried to hit buttons to cancel it and nothing worked, i had to hold the power button. So i eliminated all of my security and went back thinking it was a 1 time issue but it happened again, it took me straight to the main menu but nothing would work. I'm using 3.2.1-0 like you mentioned and i cant press any buttons. I'd like to back everything up before flashing this or anything else.
Click to expand...
Click to collapse
You don't need a backup before re-flashing the STOCK dtbo (or boot) partitions, haha. READ UP.

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..