[Q] Recovery Questions and hidden menus - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

1)Hidden menus
Are there any hidden menus on the stock rom? Are there hidden menus on other ROMs?
For example :*#22745927 hidden menu for RMNET + DM + MODEM mode and *#7284# enter to PhoneUtil, LTE is turned on via *#*#4636#*#*
What are these for? How many of them are there?
is this a full list and are they applicable for the S3 i747? http://forum.xda-developers.com/showthread.php?p=25026311
2) Recovery.
What the heck is the difference between CWM vs TWRP vs NV backup vs boot in recovery for nandroid backup?
What are all of these?? what type of backups do each one make?
I think NV is specifically for IMEI, but wont cw, twrp, or nandroid cover this?
Is nandroid a term used for CWM/TWRP backups?
How is the stock recovery?
How does something like this compare with just using twrp or cwm?
INTRODUCING THE SAMSUNG GALAXY S3 TOOLKIT [SNAPDRAGON EDITION] ?
http://forum.xda-developers.com/showthread.php?t=1746665
Thanks, i hope my noob questions werent too bad

mikoal said:
1)Hidden menus
Are there any hidden menus on the stock rom? Are there hidden menus on other ROMs?
For example :*#22745927 hidden menu for RMNET + DM + MODEM mode and *#7284# enter to PhoneUtil, LTE is turned on via *#*#4636#*#*
What are these for? How many of them are there?
is this a full list and are they applicable for the S3 i747? http://forum.xda-developers.com/showthread.php?p=25026311
2) Recovery.
What the heck is the difference between CWM vs TWRP vs NV backup vs boot in recovery for nandroid backup?
What are all of these?? what type of backups do each one make?
I think NV is specifically for IMEI, but wont cw, twrp, or nandroid cover this?
Is nandroid a term used for CWM/TWRP backups?
How is the stock recovery?
How does something like this compare with just using twrp or cwm?
INTRODUCING THE SAMSUNG GALAXY S3 TOOLKIT [SNAPDRAGON EDITION] ?
http://forum.xda-developers.com/showthread.php?t=1746665
Thanks, i hope my noob questions werent too bad
Click to expand...
Click to collapse
You'll have to try out the dialer codes to see which work and which don't. Just be careful as there are a couple that will reset your phone.
Recovery, CWM and TWRP are two different custom recoveries. They allow you to do stuff that the stock e3 recovery won't, like flash custom mods, ROM's, etc. Of the two TWRP is gaining ground as the most popular recovery of choice for the extra options it has over CWM. An NV backup is IMEI specific as that is all it backs up is your IMEI. CWM/TWRP backups (nandroid backup) take a snapshot of your system as is at that moment and can be restored at a later date or if a mod you do doesn't work. Nandroids do not back up modem(radio) or IMEI information.
The toolkit is a computer based program that does all this, except the IMEI stuff, and more but you need to have your phone hooked to the computer in order to use it, the CWM/TWRP recoveries are all phone based.
Hope this info helps a little.

jethro650 said:
You'll have to try out the dialer codes to see which work and which don't. Just be careful as there are a couple that will reset your phone.
Recovery, CWM and TWRP are two different custom recoveries. They allow you to do stuff that the stock e3 recovery won't, like flash custom mods, ROM's, etc. Of the two TWRP is gaining ground as the most popular recovery of choice for the extra options it has over CWM. An NV backup is IMEI specific as that is all it backs up is your IMEI. CWM/TWRP backups (nandroid backup) take a snapshot of your system as is at that moment and can be restored at a later date or if a mod you do doesn't work. Nandroids do not back up modem(radio) or IMEI information.
The toolkit is a computer based program that does all this, except the IMEI stuff, and more but you need to have your phone hooked to the computer in order to use it, the CWM/TWRP recoveries are all phone based.
Hope this info helps a little.
Click to expand...
Click to collapse
Thanks Jethro! I gave you a thanks.
So these are called dialer codes?..... what are they generally used for? I dont want to reset my phone by accident.
If its just a regular phone reset with no data loss then ok, i'll give that a shot and record which ones work with my Rogers i747m model.
So essentially twrp and cwm creates an image called nandroid.
NV collects imei info
What type of files do stock recovery give you?
Oh I also ran across something claled Titanium backup.......how does that compare with twrp and cwm?
As for the toolkit, is that the only difference? Its that
1) its a cpu based program
2) it baiscally has recover, unlock, drivers, and flashing rom all programmed into 1 place?
So I can back up with twrp, cwm, and the toolkit if i wanted to be OCD about it?

mikoal said:
Thanks Jethro! I gave you a thanks.
So these are called dialer codes?..... what are they generally used for? I dont want to reset my phone by accident.
If its just a regular phone reset with no data loss then ok, i'll give that a shot and record which ones work with my Rogers i747m model.
So essentially twrp and cwm creates an image called nandroid.
NV collects imei info
What type of files do stock recovery give you?
Oh I also ran across something claled Titanium backup.......how does that compare with twrp and cwm?
As for the toolkit, is that the only difference? Its that
1) its a cpu based program
2) it baiscally has recover, unlock, drivers, and flashing rom all programmed into 1 place?
So I can back up with twrp, cwm, and the toolkit if i wanted to be OCD about it?
Click to expand...
Click to collapse
The dialer codes are "hidden" as they are used by service techs who repair phones and generally aren't suppposed to be used by the end user lol. But then again the end user isn't supposed to root and install custom software either
I don't think stock recovery has an option to back up anything it is just used to install over-the-air updates and official software.
Titanium backup allows you to back up various things in android such as SMS, MMS, call logs apps and thier data(app settings, game saves). You can only back up app data if your rooted. If your going to be flashing ROMs then you will want either Titanium back or My back up root<--does the same stuff as Titanium back only easier user interface.
Right on the money about the toolkit. You can install it on your computer and browse through the menus and stuff without hooking up your phone to see all the stuff it actually does. Even though the option is there I don't think it will back up imei stuff or carrier(SIM) unlock this phone yet.
Yes you can do as many backups as you like lol. Just keep in mind the recovery based back ups are recovery dependant. If you make a recovery with CWM then switch recoveries to TWRP the backup you made with CWM won't be campatible with TWRP. I suggest picking a recovery(hint,hint...TWRP lol) and sticking with it. I seriously advise reading through this thread before doing any major flashing and back up your imei info and saving it a couple different places.
I suggested picking a recovery and sticking with it because even though tiny there is always that chance that something could go wrong during a flash and brick your phone(soft or hard). Flashing ROMs that chance is very slim and if something does go wrong its usually just a soft brick and easy to recover from(restore a nandroid you created usually), unless you flash a ROM from some other device, thats could potentially wreck your phone. Flashing recoveries that chance is still also small but if something goes wrong it will be harder to recover from as now there won't be a recovery and you'll have to flash using odin through download mode and can be a pain. Remember I said slim chances of flashed going bad, just be aware that no matter how slim, it could still happen. The chances of winning the lottery are slim but someone always wins it lol.

jethro650 said:
The dialer codes are "hidden" as they are used by service techs who repair phones and generally aren't suppposed to be used by the end user lol. But then again the end user isn't supposed to root and install custom software either
I don't think stock recovery has an option to back up anything it is just used to install over-the-air updates and official software.
Titanium backup allows you to back up various things in android such as SMS, MMS, call logs apps and thier data(app settings, game saves). You can only back up app data if your rooted. If your going to be flashing ROMs then you will want either Titanium back or My back up root<--does the same stuff as Titanium back only easier user interface.
Right on the money about the toolkit. You can install it on your computer and browse through the menus and stuff without hooking up your phone to see all the stuff it actually does. Even though the option is there I don't think it will back up imei stuff or carrier(SIM) unlock this phone yet.
Yes you can do as many backups as you like lol. Just keep in mind the recovery based back ups are recovery dependant. If you make a recovery with CWM then switch recoveries to TWRP the backup you made with CWM won't be campatible with TWRP. I suggest picking a recovery(hint,hint...TWRP lol) and sticking with it. I seriously advise reading through this thread before doing any major flashing and back up your imei info and saving it a couple different places.
I suggested picking a recovery and sticking with it because even though tiny there is always that chance that something could go wrong during a flash and brick your phone(soft or hard). Flashing ROMs that chance is very slim and if something does go wrong its usually just a soft brick and easy to recover from(restore a nandroid you created usually), unless you flash a ROM from some other device, thats could potentially wreck your phone. Flashing recoveries that chance is still also small but if something goes wrong it will be harder to recover from as now there won't be a recovery and you'll have to flash using odin through download mode and can be a pain. Remember I said slim chances of flashed going bad, just be aware that no matter how slim, it could still happen. The chances of winning the lottery are slim but someone always wins it lol.
Click to expand...
Click to collapse
wait so you are not recommending me to back up a twrp and then back up a cwm?
Cant twrp still restore with twrp and cwm with cwm?

Yes you can do both but they arent compatible with each other. You are right twrp with twrp and cwm with cwm. The point I was trying to make is that you should pick one recovery or the other and stick with it. Nandroid are fairly large in size and will eat up a lot of space. Not to mention having to flash back and forth between recoveries. In the end thier is no reason why you can't except the inconvenience of dealing with two recoveries thag arent compatible with each other.

Related

Restoring Backups from TWRP or CWM

Hello Forums,
I recently upgraded my Evo 3d and my wife's blackberry (Verizon) to 2 Sprints Galaxy s3. My wife decided she wanted hers rooted for tweaks for better battery life. I rooted mine so I could use custom firmware for the device. I have ran into a problem...
1. Whichever recovery I use (TWRP or CWM) on either device; when restoring the backup I have made; we must do a factory reset in order to have functionality for anything. It boot loops even after wiping all partitions multiple times, and restoring backups.
2.Tried to restore, factory data reset, and data partition restore. bootloops(more than likely not to work but figured I would try)
I am wanting to test out different Roms and My wife if her phone decides to freeze and needs to restore were screwed. Even while using Titanium Backup to restore data. As it is quite bothersome when you have to set up our phones every time after a restore....
Am I going to have to use ODIN, Mobile ODIN or would there be a way to use custom recoveries without having to reset our phones.
PS:
It seems to me to reside in how any recovery is backing up the data partition. Either that or something on our phones may be locked (that I am not aware of)as far as reading the data from recovery.
Seems like I ha e made a noob mistake. Have to unlock bootloader on devices...
Hey moderators you can close this thread thank you!

Help... I will PAY for help!

First person to help gets paid for your time...
Problem: I have a s3 i747 from att.
it has 4.3 stock.
I use srs to unlock all my phones.
well when I went to unlock this one it said it had new security.
Usually when this happens I odin this file that downgrades the modem.
well I did it and now I have null imei and unknown baseband
I tried restoring to stock, didn't help. Through kies and odin.
I need to put it back the way it was... can someone please help..... ill paypal you as soon as its working again...thanks
So you're currently at stock, unlocked? Does the phone boot at all?
These threads may help:
http://forum.xda-developers.com/showthread.php?t=2658486
http://forum.xda-developers.com/showthread.php?t=2722660
yes it is still stock 4.3. no its not unlocked. everything works and boots fine. just no signal because of null imei and unknown baseband.
I think I need to just flash a modem via odin....I just don't know which one
http://forum.xda-developers.com/showthread.php?t=1831898
There's seems to be a rash of this happening in the past month. You'll probably find that link helpful but first check and see if others found a better solution.
Yes. Flash the 4.3 modem.
As of 4.3, flashing any older modem will no longer work, resulting in an unknown imei and baseband version. Flashing back to the correct modem nearly always solves this issue.
It will be like this from now on btw. You cannot use any modem except the one which matches your current firmware build.
This means our free unlock method no longer works unfortunately. But you can get unlocked for just a few bucks using one of the many services online. I know some are on ebay, but google will find others as well.
I installed cwm and downloaded the modem but im lost from there.
do I rename it update.zip?
Nope, just flash like you would any other rom.
Because you asked about renaming it to update.zip though, I have to ask if you are certain you are in cwm? If you had previously updated via ota it may restore the stock recovery every time you reboot. If this is happening, reflash cwm in Odin, but uncheck auto reboot. Wait until it says PASS, then unplug and pull the battery.
Next put the battery back in and boot to recovery. (Volume up, home, power. Release power only after it vibrates)
If you are sure you are in cwm though, just flash the modem normally.
Yes im sure its cmw. when I open recovery and look for the zip its nowhere to be found. that's why I was asking if I should change the name.
I did try it by changing the name but the file still doesn't show up.
It's an IMEI problem. If you haven't made a backup of the IMEI folder you can't do anything.
Sent from my SM-G900H using XDA Free mobile app
daddydv said:
Yes im sure its cmw. when I open recovery and look for the zip its nowhere to be found. that's why I was asking if I should change the name.
I did try it by changing the name but the file still doesn't show up.
Click to expand...
Click to collapse
Make sure the sdcard is mounted. Have you tried getting to it on both internal and external cards?
Thin_Bezel said:
It's an IMEI problem. If you haven't made a backup of the IMEI folder you can't do anything.
Sent from my SM-G900H using XDA Free mobile app
Click to expand...
Click to collapse
Not true. 90% of unknown baseband and imei problems ive helped people with lately just needed the correct modem. And even if it were the imei, I can still help with that. Im convinced in this case its just the modem though.
Thanks doc... that was the problem...imei and baseband are back. donation has been sent....thanks again.
Hey thanks man! I do appreciate it, but I am just glad I could help! I will definitely put it to good use though! (Broke the lcd on my S3 a while back and haven't had the disposable funds to fix it. Something always comes up...lol!) Will be adding it to my savings for this purpose!
Anyway, since we were slightly on the IMEI topic, there is a backup you should do if you haven't already. (Root is required for this to work though.)
Its super simple and will create an on device backup of your nv data. The backup will be stored on a couple of partitions we never touch, not even with firmware flashes. This essentially makes it a permanent backup. The cool thing about it is every time you reboot, the system checks for any corruption, and if detected, it will automatically restore from this backup. So if it were to ever happen, you probably wouldn't ever even notice it!
Install the Terminal Emulator from the play store. Open and enter this:
su
reboot nvbackup
Thats it! Device will reboot and create your backup. This should prevent you from ever suffering from a lost IMEI!
DocHoliday77 said:
Hey thanks man! I do appreciate it, but I am just glad I could help! I will definitely put it to good use though! (Broke the lcd on my S3 a while back and haven't had the disposable funds to fix it. Something always comes up...lol!) Will be adding it to my savings for this purpose!
Anyway, since we were slightly on the IMEI topic, there is a backup you should do if you haven't already. (Root is required for this to work though.)
Its super simple and will create an on device backup of your nv data. The backup will be stored on a couple of partitions we never touch, not even with firmware flashes. This essentially makes it a permanent backup. The cool thing about it is every time you reboot, the system checks for any corruption, and if detected, it will automatically restore from this backup. So if it were to ever happen, you probably wouldn't ever even notice it!
Install the Terminal Emulator from the play store. Open and enter this:
su
reboot nvbackup
Thats it! Device will reboot and create your backup. This should prevent you from ever suffering from a lost IMEI!
Click to expand...
Click to collapse
You can also use qpst to backup imei. Windows app. Free. Lots of walkthroughs around for those less comfortable with cli.
Nvm. 10char
azuziel said:
You can also use qpst to backup imei. Windows app. Free. Lots of walkthroughs around for those less comfortable with cli.
Click to expand...
Click to collapse
I know, I already have it and have used it and other tools to help fix at least 700-800 S3's, probably more! (No, i do not charge for my help either.) I dont tell about it or give it out unless its absolutely needed for a legitimate imei restore though. Too many people try to use it illegally and Im not willing to take the chance. Its the main reason most of the info has been deleted from everywhere. Only a few threads here and there get by the mods it seems.
Anyway, to my knowledge, no one who has run this backup has ever lost their IMEI. It even seems to help for those occasions after flashing a cm rom where the imei displays "unknown". (Apparently, at least on the T999, cm sometimes has problems reading the nv data. If rebooting several times doesnt solve, stock firmware does).
At this point I believe if you run this backup, you will have no need for a .qcn or .txt file backup, which is why I just dont mention it anymore. And if it does happen, people can pm me and ill be happy to help fix it.
Because of how I understand this backup to function, I do believe if it had been run during first boot, we would've never seen so many imei problems to begin with! I just dont understand why Samsung refuses to do this!
Anyway, that's why I dont mention those tools anymore. If you have any questions about any of it, please feel free to PM me and ill try to explain better.

[Q] Debloating Tab S 10.5 LTE

Hello, I just rooted my device and I'd like to start freezing the useless apps that come with it.
Where can I find a list of apps (and system apps) I can safely freeze for this device?
http://forum.xda-developers.com/showthread.php?t=2861180 hope this helps
DUHAsianSKILLZ said:
http://forum.xda-developers.com/showthread.php?t=2861180 hope this helps
Click to expand...
Click to collapse
Awesome thanks!
Best option is to flash a debloated rom.
Nah then i cant install some of the stock apps i want. Some roms that are debloated wont work with some stock apps like kids mode. I prefer stock so i can pick the apps i dont wont.
pibach said:
Best option is to flash a debloated rom.
Click to expand...
Click to collapse
I've been looking for some time, I couldn't find any - not that I'm an expert at this.
Besides, I don't even know how to handle roms and recoveries and stuff.
Now I manually deleted the multi-window apk, and I see some improvement - though it may be psychological.
Random fact, putting the apk file back in there doesn't make the multi-window work anymore - not that I care, but still.
What kind of lte model you have on your tab s. And to debloat properly use titanium backup so if something goes wrong when deleting the apk, you can restore it back. Tell me your model and what carrier your on. There may be a recovery for you to backup your whole rom in case of a problem you get.
DUHAsianSKILLZ said:
What kind of lte model you have on your tab s. And to debloat properly use titanium backup so if something goes wrong when deleting the apk, you can restore it back. Tell me your model and what carrier your on. There may be a recovery for you to backup your whole rom in case of a problem you get.
Click to expand...
Click to collapse
I do use Titanium Backup to freeze apps, now it's pretty much stock android.
However the multi-window apk wasn't present in TB, I had to move the apk itself from system/app.
My model is SM-T805 Exynos, without really a carrier. It's only like this here in Italy.
As for roms, I honestly couldn't understand how to work with them. I couldn't even find how to setup a custom recovery on this device.
For TWRP Recovery just install TWRP Manager from Play Store. It does install its Recovery by just a click. Root required though.
To install any ROM just download the zip-file, start TWRP Manager, and click install zip. It will do the rest. It is just some clicks. Adding a kernel zip is just the same. Very easy.
I've installes Selamba ROM (T-705). Much snappier, just by some debloating. For T-805 there are some other, similar ROMs around here.
pibach said:
For TWRP Recovery just install TWRP Manager from Play Store. It does install its Recovery by just a click. Root required though.
To install any ROM just download the zip-file, start TWRP Manager, and click install zip. It will do the rest. It is just some clicks. Adding a kernel zip is just the same. Very easy.
I've installes Selamba ROM (T-705). Much snappier, just by some debloating. For T-805 there are some other, similar ROMs around here.
Click to expand...
Click to collapse
Thanks, but the whole process of recoveries is still very unclear to me lol.
Anyway I managed to get the multiwindow feature back to work by editing its apk permission to be the same of the other system apps. And I found out that it's called flashbarservice, which allowed me to find it and freeze it in Titanium Backup, so now it's all ok.
Just one problem, since when I started messing around with debloating, my wifi settings reset every reboot, and I can't find why.
(and my wifi connection seems to drop a lot, too - but not sure if it's because of what I touched)
There are 3 partitions to boot into:
a) regular
b) recovery
c) download mode
Recovery can do recoveries (obviously), and can also install custom images to the regular partition.
Anyway, you don't need to know much about internals. TWRP Manager does it in the background, you just do some clicks - no messing around with the recovery directly. Installing new ROM is much easier than freezing several Apps and Services. Also you get several tweaks plus the updated ROM version (this one for your T-805 is based on NG2).
To find out what device you got to install twrp, is to install an app called cpuz,then go the the systems tab and it should say sm-t805( model name). The (modelname) is what model you would choose when install twrp. Twrp was pretty safe for me to install. I just had to pick my model and install and reboot into recovery then bam its there. Im not sure if there is twrp for t805 models. But ill do a google search. Hope this helps! To fix your wifi yoj probaly have to install another rom. If you can, can you list the things u debloated.
Nope no twrp for lte. Sucks!
The 8.4 wifi twrp works also for the LTE version. So I guess it is the same for the 10.5 LTE tab, at least, for the Exynos version.
With best regards, maris
DUHAsianSKILLZ said:
Nope no twrp for lte. Sucks!
Click to expand...
Click to collapse
use the TWRP for T800, works great with T805, I run it myself... use the 2.7.1.1 version.
[email protected] said:
use the TWRP for T800, works great with T805, I run it myself... use the 2.7.1.1 version.
Click to expand...
Click to collapse
Ok I've installed TWRP and made a backup. Now I wonder, I put the backup on my PC otherwise the tablet storage would be completely full.
What will I do in the case my tablet will not boot so I won't be able to put the backup into the tablet to restore it?
update: Backup of 4gb has been going for a good 3h, I'd imagine something has gone wrong lol.
rebooted, tried again, took 3 mins now lol.
When backing up your tab s i put compression on so the file can be smaller. I also made a copy to my pc in case some goes wrong with my tab s. It case your tab s doesnt boot, wait till battery dies then charge it. After it has been charged, hold the power, volume up and home key at the same time to get into twrp. Then hit restore and pick you backup. There has been problems backing up with sd card so i wouldnt suggest that.
DUHAsianSKILLZ said:
When backing up your tab s i put compression on so the file can be smaller. I also made a copy to my pc in case some goes wrong with my tab s. It case your tab s doesnt boot, wait till battery dies then charge it. After it has been charged, hold the power, volume up and home key at the same time to get into twrp. Then hit restore and pick you backup. There has been problems backing up with sd card so i wouldnt suggest that.
Click to expand...
Click to collapse
No I mean I moved the backup from tablet to PC, and deleted it from the tablet afterwards. How would I be able to use that backup if I can't even boot to paste it inside?
Anyway, I did make a compressed backup just now, and just to try, I wanted to see if moving it from tablet to pc, and then back to tablet would still be recognizable, and here is the problem, windows explorer won't let me paste the backup folder. what do lol
You can paste it inside. It has to do something with adb or transferring it to twrp,backups. In twrp you can paste stuff into it even though your bootlooped. As long you can get into twrp you be fine. Not sure about the copying and pasting part but ill try to find more info on it and post it here. Theres a way to transferr the file from your pc to twrp. And when you backed up in twrp did you check every box (boot, cache, recovery, etc) because i found out that if you dont, you may have an problem with connecting to your carrier and would have to take it back to get it fixed. Anyway ill take a look at transferring files and get back to you
DUHAsianSKILLZ said:
You can paste it inside. It has to do something with adb or transferring it to twrp,backups. In twrp you can paste stuff into it even though your bootlooped. As long you can get into twrp you be fine. Not sure about the copying and pasting part but ill try to find more info on it and post it here. Theres a way to transferr the file from your pc to twrp. And when you backed up in twrp did you check every box (boot, cache, recovery, etc) because i found out that if you dont, you may have an problem with connecting to your carrier and would have to take it back to get it fixed. Anyway ill take a look at transferring files and get back to you
Click to expand...
Click to collapse
I figured I'd be able to just paste it inside, but something was wrong with my tablet after I stupidly tried the Fix Permissions tool in TWRP. It made me a sub-user or something, I couldn't even delete my own files like pictures. Scary thing was that it retained through a factory reset. Seems to have been working now after doing a complete wipe.
However when I restore the backup I was talking about in the post above, it makes my permissions broken there too, even if I'm sure it was all ok by when I made that backup.
I don't understand. I'm worried that if I make another backup of the stable situation now it will revert back to faulty permissions or something lol.
(I did manage to get the backup files in the tablet by putting them into a rar and transferring it, and decompressing it through the tablet itself - because moving the folder directly gave me an error - no, not about size)

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

On VS98510B, just want to upgrade to latest android, please help.

I have a VS985 LG G3. I was running marshmallow yesterday, but after trying to root and unlock mobile tethering and hotspot (because I am on unlimited data) I managed to brick my phone while typing in adb commands because my phone decided to randomly shut off. So after plugging it into the USB and figuring out a way to put it into download mode, I flashed it to VS98510B. After that, I rooted with Stump Root and installed SuperSU, following some guides. It works fine once again but I'm not where I want to be.
After multiple times trying to open adb shell and get it to just recognize my device, I'm done. I know there are people out there who know this stuff by heart, so please, at this point, just tell me what to do step by step so I can do it and move on with my life. I have spent hours upon hours on this and it never seems to just work. Please.
All I want is to be able to install the latest TWRP or whatever is recommended., and then install either the SkyDragon Rom or the stock marshmallow VS98546A rom, but with the verizon apps disabled since in one guide it warns that those report for modified device, which I am not sure what that means but it doesn't sound good.
I'm on VS98510B. Rooted and SuperSU installed.
I want to be able to use mobile hotspot and tethering.
There's just information overload to the extreme, I'm overwhelmed.
Thanks again if any help is possible.
If you're already rooted with TWRP installed, the hard part should really be over. You shouldn't need to be plugging into a computer and running adb commands at this point. You also said you need step by step instructions, and to really spell it all out would be a lot, but considering how far you already got I don't think you really need every little detail, so I'll give you the general idea then if you have questions I can try to fill those gaps.
Basically you'll need to find and download the new ROM you want. The easiest thing to do is download it directly from your phone so you don't have to mess around with transferring it from your computer to your phone. Many custom ROMs will also require Gapps, but if you're flashing a stock ROM (or a custom ROM based on stock) you don't need to do this because it's included in the ROM.
After you've downloaded the ROM (should just be a zip file), you need to reboot to recovery (TWRP). If you don't know how to do this, there's an app called Quick Reboot that can do it for you (01400) personally haven't used it but I assume it works).
Once you're in recovery, you normally want to make a backup first in case anything goes wrong. This is done by selecting the backup button. After you have a backup, you want to "wipe" data before installing. Select the wipe button, then I click advanced and select everything except internal data and external data. This will wipe all apps, settings, etc. from your phone so make sure you're ok with that before you do it,
After wiping, you're ready to install. Back at the first main screen of TWRP, select Install, then browse to where you downloaded the ROM and select it, then select the Install button and swipe to confirm. Assuming all goes well, when it's finished it'll give you the option to reboot. Do this and it should start booting up to your new ROM.
Also, you mentioned SkyDragon, but I just wanted to point out that this isn't the latest version of Android, I believe that's still Lollipop (not Marshmallow). You also mentioned not wanting your rooted status to be reported to Verizon, but if you're currently on stock, rooted, and don't have any apps disabled, then you already are running this risk.
Let me know if you have any questions. I think this will be easier than me trying to walk you through every detail and confirmation screen.
I don't have TWRP installed. What is the best course of action to take to install it?
As far as disabling verizon apps, is it as simple as just going into the application manager and disabling them or is there a tool I need to download?
Thanks for all the help so far!
I see, it's been a couple years since I installed TWRP and I was thinking it was part of the rooting process. I believe this is the post I followed to install TWRP: http://forum.xda-developers.com/lg-...mp-unlock-lg-g3-twrp-d852-d852g-f400-t2900614
Like I said, this was a few years ago and it's kind of a one-time thing. I don't know if there's something better available now or what, and I don't remember the details. I don't remember running into any problems, so if you happened to have any I'm not sure how good I could help.
As for disabling things, the things that need to be disabled are system apps and can't just be disabled from the stock application manager (Verizon doesn't want to make it easy for you to disable their software ). There are different ways this can be done, but I personally use Titanium Backup to disable (or "freeze" as they call it) apps. It will let you freeze anything, which also means it gives you the ability to break things, so don't just go in freezing random things. I don't remember if freezing requires the paid version of the app or not, but you can get it from the play store and find out.
Sent from my VS985 4G using Tapatalk
As far as Titanium Backup goes, is it along the same lines as TWRP? Like do they do the same things? Do you recommend I do one over the other?
Also as far as verizon apps reporting root, what do they do and what does that matter?
Also, I'm currently dealing with the LG DemiGod Crash Handler problem that seems to have started up on my phone the other day. I'd never rooted or messed with my phone in any way and that started happening, I thought perhaps flashing a new ROM might fix it, but I guess not. If you have any sort of tips on how to fix that, other than replace the battery (which I have not yet done, but supposedly that can solve the problem) I'd be grateful.
Titanium Backup and TWRP are two different things. Titanium Backup is a "normal" app that you can get from the Play store, while TWRP is a custom recovery and isn't ran from within your ROM. TWRP lets you do full image backups of your phone (like your entire phone in a single backup) and can also be used to install ("flash") ROMs. Titanium Backup lets you backup, freeze, and uninstall specific apps.
I use them both because they both serve a specific purpose. You have to use TWRP to install ROMs, then as far as backups, I use TWRP to make a backup of everything in case I flash a ROM that I end up not liking (I can use the backup to easily go back to my previous ROM and still have apps and everything all setup just like they were). If I do like the new ROM I flashed, I'll use Titanium Backup to restore a lot of my apps/data to the new ROM (ex. text messages, my alarm clock app, etc.)
As far as Verizon knowing about your root status, honestly I'm not sure what all that would mean. I'm sure they wouldn't like it, rooting voids your warranty so you probably couldn't get things replaced under warranty, if you have insurance through Verizon they would maybe use your root status as a reason to deny a claim, etc. I don't think you'd have to worry about them calling you up or cancelling your service or anything like that, but getting them to assist you with problems might be more frustrating than usual
Regarding the demigod crash thing, I know what you're talking about but I don't really know much about it. A while ago I would get those every once in a while and it was frustrating. I think at the time I kind off wanted to try a new ROM anyways and I think I did but I still got it occasionally. Now that you mentioned it though I haven't had one in quite a while. I'm not sure if those ROMs both happened to cause it, if it was a Lollipop thing (doesn't seem like I've had it since Marshmallow), or if it's all just a coincidence or I've just been lucky. I haven't gotten a new battery though, so that's definitely not it (for me anyways).
Sent from my VS985 4G using Tapatalk

Categories

Resources