A Couple Problems After Root and Cyanogenmod Install - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Hi,
I finally decided to root my phone and flash Cyanogenmod (1/10/2013 nightly) on my S3 today, and I've run into a couple problems. First, the phone won't connect to 4G lte -- it only connects to 3g. When I try and change the network preferences, the changes don't stay, and changing the APN doesn't make any difference either.
This brings me to my second problem -- Since I couldn't get the phone to connect to lte, I decided to restore my phone to the backup I set up through clockworkmod before I installed Cyanogenmod. However, when I tried to restore, clockworkmod said that it couldn't find any backup files. I checked in the clockworkmod/backup folder, and the backup was there, but it was dated as 2/5/70! Did something go wrong with the backup?
Can anyone help me with these issues?

So I found out the problem; apparently it was somewhat widespread. the 4.2 update created new user profiles which changed the location of the backup files. I ended up using the file manager to move the backup file to sdcard0/ from sdcard0/0/. I was able to restore from the backup, but it seemed to be taking a long time to boot, so I pulled the battery as I thought it was stuck in a bootloop. I tried flashing a the rooted stock firmware from one of the Galaxy S3 root guides (because it was already on my computer) to see if that would make a difference, and the phone eventually was able to boot up. It turned out the backup restore had worked, as my previous apps were on the phone. However, almost none of them work, because the sdcard0/0 directory still exists, and this previous version of Android doesn't recognize the location (at least I think this is the problem).
Anyway, does anyone know if I can just get my phone back to the way it was before I installed the custom recovery and ROM? Is there any way to install firmware that gets rid of this sdcard0/0/ directory so I can restore from backup properly? I'm in way over my head here (I shouldn't have even attempted this in the first place) and would really appreciate some help.

Related

Problems after restoring backup

I have recently acquired a Telus/Koodo GSM HTC One V and successfully installed Shpongle. I noticed there were problems when connecting the phone to my computer, it appears as two removable devices and a CD drive. I never did try connecting the phone to a computer in its stock condition, I assumed transferring files to the phone would not be an issue. Anyway, I decided to restore the backup I created of the stock ROM installation to see if there is a greater hardware issue with the phone. The result of the backup is a phone that hangs on the splash screen.
What I have done to the phone up to this point.
Unlock the bootloader
Root
Flash Recovery - TWRP v2.3.3.0
Backup Stock ROM with TWRP
Install custom ROM (shpongle_primou-20130521) and Kernel (boot-HELLBOY-20130514 )
Install GAPPS
Noticed problem with when trying to copy files to the phone.
Restore backup of stock ROM - failed
I can still get to the bootloader and the recovery.
If the connectivity issues can be resolved with a simple fix then I do not mind going back to the custom ROM. If there is no fix or it is too late to implement, I would very much like to get the phone back to the stock condition and test the connectivity issues. What are the appropriate next steps to remedy this situation?
You need a kernel change. Titanium kiss might work. There is also a stock kernel linked in one of these threads somewhere. Not sure, but I may have downloaded it
Thanks mrcorey for the insight on the kernel incompatibility.
I downloaded the RUU and found instructions to extract and flash the ROM and kernel to the phone. After upgrading it by running the RUU completely, I had a working phone again. Everything is back to stock as far as I can tell and USB connectivity is as it should be. Once connected to a PC and selecting the disk drive option on the stock HTC ROM both the internal memory and the microSD card are available in windows explorer. Why is the internal memory and card not accessible in windows when I had Sphongle installed on the phone? Is there a option that was not set right to get things to work properly?

[Q] Older MD4 NAND backup applied to MK3 or ND8 phone

Question for those of you who may know more than I do.
I have…well had, a Sprint Samsung Galaxy S3 that got a shower over the weekend. The USB port is definitely fried, and who knows what other damage may have occurred, but the phone still turns on and works fine. I decided to buy a used S3 to replace mine rather than try to fix the port not knowing if that was the only problem.
Now my question, my phone was rooted at the L710VPBMD4 OTA level, I have 4.2.2 CM v10.1.2 installed on the phone, and would like to keep it that way till I make sure everything is working the way I had it.
If the new (used) phone I receive has received either the L710VPUCMK3 or L710VPUCND8 OTAs will I have any problems loading my NAND backup and TB backups to recover my phone to the point it was wet?
(luckily the phone still had enough battery power to get these done)
Added: I also used CWM Recovery v6.0.3.0 for My NAND backups, do I have to continue to use this version to recover properly from, or will it work with Philz Recovery?
If there is a problem just straight loading my backups to the phone, is there anything I can do to make it work?
I know there is a root method difference for the L710VPUCMK3 or L710VPUCND8 OTAs, I’m just concerned about being able to recover my backups at the level they are at. Right now I don’t want to have to upgrade CM until I make sure everything is right, even then I will probably only upgrade to 10.2.1, as CM11 doesn’t seem quite ready…at least from what I’ve experienced on other phones/tablets.
Thanks in advance….
n00bhackin said:
Question for those of you who may know more than I do.
I have…well had, a Spring Samsung Galaxy S3 that got a shower over the weekend. The USB port is definitely fried, and who knows what other damage may have occurred, but the phone still turns on and works fine. I decided to buy a used S3 to replace mine rather than try to fix the port not knowing if that was the only problem.
Now my question, my phone was rooted at the L710VPBMD4 OTA level, I have 4.2.2 CM v10.1.2 installed on the phone, and would like to keep it that way till I make sure everything is working the way I had it.
If the new (used) phone I receive has received either the L710VPUCMK3 or L710VPUCND8 OTAs will I have any problems loading my NAND backup and TB backups to recover my phone to the point it was wet?
(luckily the phone still had enough battery power to get these done)
If there is a problem just straight loading my backups to the phone, is there anything I can do to make it work?
I know there is a root method difference for the L710VPUCMK3 or L710VPUCND8 OTAs, I’m just concerned about being able to recover my backups at the level they are at. Right now I don’t want to have to upgrade CM until I make sure everything is right, even then I will probably only upgrade to 10.2.1, as CM11 doesn’t seem quite ready…at least from what I’ve experienced on other phones/tablets.
Thanks in advance….
Click to expand...
Click to collapse
Well.....as long as the bootloader and modem weren't backed up you should be able to restore the CM11 as long as you use the same recovery......that being said you won't be able to restore the stock rom cause i believe the bootloader and modem get backed up with that one. Also it could come with the NJ3 update in which case you won't be able to root at all. I also wan't to add that i have no faith in TB for restoring app data cause that will cause problems with your phone.
6th_Hokage said:
Well.....as long as the bootloader and modem weren't backed up you should be able to restore the CM11 as long as you use the same recovery......that being said you won't be able to restore the stock rom cause i believe the bootloader and modem get backed up with that one. Also it could come with the NJ3 update in which case you won't be able to root at all. I also wan't to add that i have no faith in TB for restoring app data cause that will cause problems with your phone.
Click to expand...
Click to collapse
I will be restoring a CM10.1.2 mod, not CM11, if that makes a difference.
So I will need to use CWM 6.0.3.0, and can not use Philz Recovery. .. Just verifying.
I’m not worried about using my old stock rom backup, I can get a new one with the new phone, my old one never had anything on it, as I loaded CM the day I got the phone new.
How can I tell if the Boot loader/Modem are a part of the NAD backup? The files I have in the NAND are:
boot.img 10,240 KB <--- would this be the boot loader?
cache.ext4.tar 0 KB
cache.ext4.tar.a 54, 238 KB
data.ext4.tar 0 KB
data.ext4.tar.a 976,563 KB
data.ext4.tar.b 976,569 KB
data.ext4.tar.c 728,600 KB
nandroid.md5 1 KB
recovery.img 10,240 KB
system.ext4.tar 0 KB
system.ext4.tar.a 350,522 KB
Is NJ3 a Sprint released OTA? It was not in their list, ND8 was listed as current. The phone I’m getting should be a sprint phone, but I won’t know what level the phone is at till it gets here Wednesday.
As for TB restore, I shouldn't have to since my NAND is current, but so far I’ve been lucky with TB.
@bilgerryan do you have any advise for this person i have reached the limit of the help i can give with the experience that i have on this version of the phone....
Thanks for your help, I'm trying to get as much information as I can on this before I get my "new" phone and brick it with what I am trying to do.
Once I have the phone it may not be an issue if it hasn't received OTAs, the best scenario is that is at the MD4 level, but I doubt I will be that lucky. I expect it has been updated to MK3 or ND8, which is why I am asking what I'm asking.
OK, my guess is that boot.img is not the boot loader, as I see that file in CM ROM zip files, and CM ROMs do not contain a boot loader, can anyone confirm that this is correct?
n00bhackin said:
Thanks for your help, I'm trying to get as much information as I can on this before I get my "new" phone and brick it with what I am trying to do.
Once I have the phone it may not be an issue if it hasn't received OTAs, the best scenario is that is at the MD4 level, but I doubt I will be that lucky. I expect it has been updated to MK3 or ND8, which is why I am asking what I'm asking.
OK, my guess is that boot.img is not the boot loader, as I see that file in CM ROM zip files, and CM ROMs do not contain a boot loader, can anyone confirm that this is correct?
Click to expand...
Click to collapse
no problem and if anyone can help you more then me it's Ryan since he still has the Sph-L710 and he's a Developer.....while i have the newer Sph-L710T and im on Boost Mobile
Few follow-up questions:
1) Will CWM 6.0.3.0 work fine with the phone has been updated to MK3 or ND8?
2) If not, can I restore a backup made on CWM 6.0.3.0 with CWM 6.0.4.5? (seems to be the latest version)
3) If the “new” phone is on MK3 or ND8 can you still use a previous android version, like 4.2.2? (This is basically what I will be doing, but using a NAND backup to restore the phone)
4) Will a NAND backup contain the boot loader or modem? How can I tell if mine does?
This would prevent me from being able to recover with my NADN backup, from what 6th_Hokage said, and from what other information I’ve read on this. It would brick.
Still hoping I can using my NAND backup from MD4 phone to recover to a phone that may be at a higher level. So far from all the reading I am doing on this I should be able to, as long as I don’t try to flash the firmware back to MD4. Which isn’t an issue if my NAND will work, if it won’t then I’ll just be forced to rebuild from scratch, which I am REALLY hoping to avoid.
Ok, after reading as much as I could last night…my head hurts…
But it looks like I can do what I hope to do, if the planets and stars align.
Best case scenario, the “new” phone I get is at MD4 and is the SPH-710 variant. (doubt I can get that lucky)
If the phone is the SPH-710T – It goes back and I’m out of luck, as it’s a crap shoot buying a used phone when they don’t make a distinction between the 710 and 710T (Thanks 6th_Hokage, when you mentioned the 710T and on Boost Mobile, I figured it was a variant for them and VM, not for sprint, I’ve found out it is a sprint branded phone too)
If the phone is a 710 variant and even if it has been upgraded to MK3 or ND8 I should still be able to use my NAND backup to recover my old ROM (4.2.2 CM v10.1.2).
I should be able to use either CWM 6.0.3.0 or CWM 6.0.4.5 on the new phone to restore my NAND that was made with CWM 6.0.3.0… even if the phone is at MK3 or ND8.
My NAND should not contain the boot loader or modem, but I’m not sure how to tell. If it does, I’ll need to figure out how to make a NAND that exclude them. How can I tell if my NAND contains these? (because if it does and I restore, it will brick, if on MK3 or ND8)
If anyone can provide some insight on this that would be great.
Thanks,
Next on the list of my research findings.
I have found conflicting information, in one post I found that I would get an asset error if I try to install CM 10.1.2 (or I think any 10.x version) when on either MK3 or ND8. Then in another port I read that there should not be a problem installing any version of CM when on MK3 or ND8.
Can anyone confirm either post? Can CM10x work on MK3/ND8? Or will an assert error get thrown?
If an assert error is thrown only during install, I wonder if I bypass this by using a NAND restore like I plan, since the “install” of CM has already occurred, and I am just restoring a backup.
You may ask yourself why I am going through all this to recover an older version of CM. Well my phone was completely stable where it was, it did everything I needed to without error. While I’ve considered upgrading, that always seems to introduce issues, and I needed a smooth working phone over some of the stated benefits of CM11.
n00bhackin said:
My phone was rooted at the L710VPBMD4 OTA level,
I have 4.2.2 CM v10.1.2 installed on the phone
and would like to keep it that way till I make sure everything is working the way I had it.
If the new (used) phone I receive
has either the
L710VPUCMK3
or
L710VPUCND8 OTAs
will I have any problems loading my NAND backup and TB backups to recover my phone to the point it was wet?
(luckily the phone still had enough battery power to get these done)
Thanks in advance….
Click to expand...
Click to collapse
Yes, I was able to restore the NAND backup with my S3.
I had a NAND backup of
CyanogenMod 10.2.1
that was on MD4 before
on my Sprint S3 SPH-L710.
I was able to restore
the NAND backup of
CyanogenMod 10.2.1
that was on a MD4 modem before
on my S3
with the new
ND8 modem update
using
TWRP 2.8.1.0
Great to hear it will work, now just have to hope they didn't send me a 710T variant...Will know tomorrow.
Hopefully it will work the same with CWM, as that is what my backup was made by, I've read that CWM and TWRP backups are not compatible.
n00bhackin said:
I've read that CWM and TWRP backups are not compatible.
Click to expand...
Click to collapse
Correct, not to mention TWRP doesn't mount or storage correctly anyway. I suggest using Philz, it's a zero issue recovery.
Will Philz correctly restore a CWM backup?
If not I'll have to stick with CWM until I get everything back working.
n00bhackin said:
Will Philz correctly restore a CWM backup?
If not I'll have to stick with CWM until I get everything back working.
Click to expand...
Click to collapse
Well PhilZ is literally a touchscreen CWM and every time I made a backup with it the folder where the backup was is called "Clockworkmod" or "CWM" I can't remember the exact wording cause I've been using a beta TWRP made for the L710T
OK partial success, significant failure.
New phone received, it was an SPH-710 model, but was at ND8. But from what people have commented and what I read this wasn’t going to be a problem.
SO I rooted the device, all went well.
Restored my NAND backup, all went well.
Restored back to stock for activation, trouble started. IMEI information is gone !!
Restored back to CM10.1.2, IMEI information is there, but it contains the previous owner’s phone number.
I am able to activate the phone, everything seems to go fine.
I reboot and get data, I can receive data. I rejoiced.
I tried a text, fail.
I tried a call, fail…the rejoicing ended.
Checking phone status the person’s old phone number is still associated with the phone.
Normally this would be taken care of in stock by doing a profile reset. So Im not at a loss..
I need to see if I can recover the IMEI information in CM and transfer to Stock to do a reset on the phone to get it to activate right.
Any Ideas? I'm going to start a new thread just on this question, as this one was more about recovering my old phone to the new one.
n00bhackin said:
OK partial success, significant failure.
New phone received, it was an SPH-710 model, but was at ND8. But from what people have commented and what I read this wasn’t going to be a problem.
SO I rooted the device, all went well.
Restored my NAND backup, all went well.
Restored back to stock for activation, trouble started. IMEI information is gone !!
Restored back to CM10.1.2, IMEI information is there, but it contains the previous owner’s phone number.
I am able to activate the phone, everything seems to go fine.
I reboot and get data, I can receive data. I rejoiced.
I tried a text, fail.
I tried a call, fail…the rejoicing ended.
Checking phone status the person’s old phone number is still associated with the phone.
Normally this would be taken care of in stock by doing a profile reset. So Im not at a loss..
I need to see if I can recover the IMEI information in CM and transfer to Stock to do a reset on the phone to get it to activate right.
Any Ideas? I'm going to start a new thread just on this question, as this one was more about recovering my old phone to the new one.
Click to expand...
Click to collapse
I'm glad you were able to restore your
NAND backup of
CyanogenMod 10.2.1!
+ev
indigofilipino said:
I'm glad you were able to restore your
NAND backup of
CyanogenMod 10.2.1!
+ev
Click to expand...
Click to collapse
Not exactly, while I was able to restore the NAND backup, it was not usable, I could not activate the phone because in stock all the IMEI information was blank. I was able to recover from that. So now I am trying just to load a fresh CM10.2.1 onto the phone, but it's giving me issues. Starting HERE at post #1848.

[Solved] Issues activating SGS3 SPH-L710 on Sprint with Custom ROM + lots of problems

Hello all!
This is my first foray into the world of custom Android systems, and I'm having a hell of a time with it... if somebody would be able to help me out, I would greatly appreciate it.
First off, the situation:
I am on Sprint, and I recently bought a Samsung Galaxy S3 (SPH-L710) from Sprint to use as a backup phone, I used it for a while on Stock, then deactivated it so I could give it to my wife. First though, I wanted to put a custom ROM on it, and experiment/play around a bit and see what this world of options could do for me. Long story short, I ended up flashing an AICP ROM, and everything seemed to go smoothly, but when I went to activate the phone on my account again and it would not work no matter what I tried (details below). I figured maybe I could activate on the stock setup then just restore my custom setup, so I tried to revert to my stock ROM backup and I couldn't do anything because I was constantly getting messages that various programs had closed... Then I tried to wipe and restore my custom ROM backup and I get stuck in a boot loop... so I tried to flash a stock recovery and I get stuck in a boot loop... I'm out of ideas here, and now I'm stuck with a phone I can't use or do anything with, and I can't activate.
Details:
The initial rooting/install process seemed to work ok, and was fairly straightforward. I followed various guides on http://galaxys3root.com/ to get my phone rooted and backed up (Don't recall which ones now, but I've read through so much by now I don't know if it matters...).
My phone:
Samsung Galaxy S3 (Sprint) SPH-L710
Modem: L710SPRDNJ2
My Desktop:
Debian Linux
Here's the steps I performed:
Rebooted phone in Odin mode
Downloaded CWM S3 Sprint Recovery from the http://galaxys3root.com/ website (can't find the link any more)
Flashed the CWM recovery using Heimdall then rebooted phone into CWM
Installed SuperSU through CWM, then rebooted
Checked that the phone was rooted successfully (it was), then ran Titanium Backup on the whole device to my SD card, then copied the backup files to my desktop computer
Rebooted into CWM, and performed a backup through CWM, then rebooted and copied the CWM backup to my desktop.
Downloaded AICP Rom for my phone from here: http://downloadandroidrom.com/file/GalaxyS3Sprint/roms/AICP/aicp_d2spr_lp-10.0-RELEASE-20150707.zip, put it on my SD card, then installed it through CWM and rebooted
At this point, I was happy with how everything was working, so I did some minor theme customizations then made another backup through CWM, and copied it to my computer, but I did NOT run Titanium this time...
After all of this, I tried to go ahead and activate it through the Sprint web service. This process failed continuously with an unhelpful error message of "Sorry, this device can't be activated right now". I then got on Chat to see if they could activate it manually, and then the problems began. They did their thing activating the phone, but when I booted up I got no data connectivity, and couldn't make calls, and the SIM was not changing over to the new number. I was on the chat with them for over an hour trying to get the situation resolved, but that finally ended when they started asking me to punch in ## codes, because I discovered that none of them worked on my custom ROM. Some quick research told me that this was non-trivial to get around so I had them switch everything back and I started researching the issue.
I found this thread: http://forum.xda-developers.com/showthread.php?t=1626638&highlight=sph-l710 that looked like it would let me do what I needed from the custom ROM, but I couldn't tell if it would fix my problem for sure, so I figured "I'll just restore my stock setup from that backup I took, activate it and update, then start over". This is when things got really frustrating...
First I rebooted into CWM, went to 'backup/restore', and restored my stock backup
Rebooted, and as soon as I got past the lock screen, I get inundated with messages of various apps being closed unexpectedly.
I researched a bit, discovered the issue may be caused by stale dalvik cache, so I rebooted into CWM, cleared the dalvik cache, formatted the /cache partition, then tried to restore the stock backup again, but this time I get stuck in a boot loop.
I then rebooted into CWM, tried to restore the backup of my AICP ROM, only to be stuck in a boot loop as well.
Trying to get into any usable system, I rebooted to CWM, cleared dalvik cache, then formatted /cache, /data, and /system just to be sure, and re-flashed the base AICP ROM I started with. This worked fine, and before long I had stock AICP back
Since I still couldn't get the phone to activate in the custom ROM, and my backups are apparently completely useless, I rebooted into CWM, wiped dalvik, /cache, /data, and /system again and tried to install a different stock ROM I found in the XDA forums (here: http://forum.xda-developers.com/galaxy-s3-sprint/development/stock-rom-4-4-2-t3010642) only to be greeted by another bootloop
At this point I've spent well over 24 man-hours trying to get this to work, reading, researching, flashing, etc all to no avail. Nothing I do seems to work, and it seems like every article, tutorial, or forum thread I read either has nothing to do with my device, is too old, or doesn't describe my problem.
I'm at wits end, and am so frustrated I'm ready to just give up and smash this device and buy a new one... My questions to the community are as follows:
I know I screwed up on a couple of things, but in my initial research of doing this there was no indication that these were even things I needed to watch out for... Is there any more organized sources of information for doing this sort of thing?
Does anybody else out there use Sprint on a custom ROM, and if so how you you pull this off
Where else have I screwed up, and how can I fix this situation? (My end goal is still to get the S3 onto Sprint with a custom ROM)
What can I do differently next time? I would like to figure this out and do it to other phones and devices I have, but if it's this much trouble every time, I just don't have the time to mess with it.
Thank you in advance, and I appreciate any information that the community can provide.
This sounds like a CWM problem to me. If I were you, I'd boot the phone into Odin Mode and flash TWRP ( www.twrp.me ) then try flashing the latest aicp nightly downloaded from the official site ( www.aicp-rom.com ). Check the md5sums on everything! Then maybe try flashing a touchwiz ROM and activating your phone. Remember that you need to wipe the internal storage when you go between KitKat and lollipop.
I'm fairly certain you have to do activation with the stock Touchwiz roms -- once the phone is activated you can flash a custom.
You should go into recovery and wipe everything (System/data/etc) EXCEPT for the External SD Card
Power off - pull the battery for a few - power on directly into download mode
Odin NJ2 back onto the phone and reboot and activate it (skip through most of the setup since you'll flash a custom after)
Once you know it's activated and working under the stock Touchwiz, then again power off and Odin TWRP recovery
Then you can go back into recovery, wipe everything except External SD, and flash the custom rom back on.
Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!
afarris01 said:
Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!
Click to expand...
Click to collapse
Get rid of them. TWRP can't restore CWM even if the backup is good

Galaxy Note 10.1 2014 (LTE) not working after failed backup

First of all, hi @ all
Today I rooted my Tablet sucesfully using Odin3 with CF-Auto-Root-lt03lte-lt03ltexx-smp605.tar.md5
After this I tryed to backup all important stuff using TWRP so in case that flashing CM fails I could return to android without problems.
Becourse of a problem with the newest twrp message I got an information that the backup is going to be safed on the intern memmory (so I later would have to move it manually to the externSD card). Well that did not sound like a problem so I started the backup function, it bootet in the recovery mode.
Well I expected it to run automaticly after choosing wich partitions it should backup so I did not knew what to choose in the menu and decided to reboot wondering if I missed some explenation.
It looks like that was a bad idea, after the Samsung logo I just get a blackscreen and dozens of messages that xzy was terminated. Rebooting doesnt help.
So ironicly I crashed my device while trying to backup
At least I have absolut 0 personal data on it so I lost at least nothing.
Now my Questions:
A)To return to use my device again with android I can still use this? sammobile.com/firmwares/download/40784/P605XXUCNL1_P605BTUCNL2_BTU.zip
And is there somewhere a faster download?
Or is there a chance that after wipe data/factory reset I can use it again?
B) If I get techsoncall.wordpress.com/2015/03/30/installing-cyanogenmod-on-galaxy-note-10-1-2014 this right I actualy could just clear now the entire intern memory of my tablet, cpy the Cyanogenmod (and may gaps) on the sdcard and flash then install it to get my tablet running CM?
I would admire every comment, Im going to fly in few days so I'm actually a little bit stressed course of this fail
Well a hardreset helped but the problem was that I just installed the TWRP app and did not install the recovery mod with this app.
After doing that everything runs fine.

Samsung Tab 3 7.0 (Sprint Version) sm-T217s

I started to prepare for flashing this device. I went to my recovery and backup.
Soon after the device was flashed I realized the device's wifi and data was broken. I looked into the "about phone" in settings eventually and found that the IMEI, baseband, and the Software version are all unknown. As i rebooted back to recovery in order to go back due to possible ROM error, I got a notification that the EFS could not be mounted. So, in attempt to put things back to the way they were, i attempted to restore the backup i made for the ROM. The backup wouldn't even show up as an option for restore. Ugh... So i downloaded the stock and solved it that way. Using ADB I installed recovery, busybox, and SuperUser again. I currently have 3 files I downloaded that are suppose to restore the EFS. The problem is that I don't know what to do with these files. File names: nvrebuild1.bin, nvrebuild2.bin, and efs.img.ext4
Odin did not help to install these files. I looked in EFS and SD for a backup, but to no avail. Matter of fact, the EFS folder was completely empty.
Anyone please help me?
Hi there,
I will move your thread in the correct forum dedicated to Tab 3 Q&A for more relevant answers.
Good luck

Categories

Resources