After updating, will I be able to restore my backups of ICS?
Also, can I just flash Carbon or CM10.1 over the stock rooted 4.04 rom, or will I have to RSD the update first?
You should be able to just go straight to any aftermarket ROM from ICS.
There is a caveat with GPS, beware of it (well-documented in the threads).
If you have taken a full backup of ICS (IE system and boot and data) then you should be good to restore ICS. I've done it several times... I have backups from many different states
I've accidentally thrown my Note 3 into a bootloop and need to reflash the stock firmware. Will doing this wipe all of my data? If so, is there any method of preventing that? I really don't want to lose any data. I think I'm already running the stock firmware, unless Kingo replaces it automatically, so I'm flashing the same firmware, I think.
If you flash stock firmware thru Odin.... of course you will lose all of your data
Sharm♡♥♡♥ Android 4.1.2 [T3Rom]
REPLY
sharmsy said:
If you flash stock firmware thru Odin.... of course you will lose all of your data
Sharm♡♥♡♥ Android 4.1.2 [T3Rom]
Click to expand...
Click to collapse
I tried it, and didn't lose any data. Thanks anyway.
I am running CM-11 Stable version, which means I am rooted as well as custom recovery. If I update my ROM, will I loose any of my application's data?
e.g. if I upgrade to CM-11 Nightly, will be there any loss of data. Or if I want to install some different ROM's will there be any loss of data.
Is it possible to switch back to Stock ROM (Rooted) without loss of data.
Actually managing phone's data is big pain once you reinstall whole OS, So I am really doubtful here.
anshumangoyal said:
I am running CM-11 Stable version, which means I am rooted as well as custom recovery. If I update my ROM, will I loose any of my application's data?
e.g. if I upgrade to CM-11 Nightly, will be there any loss of data. Or if I want to install some different ROM's will there be any loss of data.
Is it possible to switch back to Stock ROM (Rooted) without loss of data.
Actually managing phone's data is big pain once you reinstall whole OS, So I am really doubtful here.
Click to expand...
Click to collapse
Do you mean with data your storage or your apps, settings? If you install a new rom you always need to wipe data (that is not your internal storage). If you update you only need to wipe cache and dalvik. You can backup apps easily with titanium backup for example
You should always nandroid backup before flashing roms and always keep a local copy of a titaniun backup.
Flashing custom roms dont wipe data. However, you may have to wipe data yourself to get it to boot.
Rule of thumb is:
Upgrading to a new version of the SAME custom ROM, no need to wipe. If you then find something doesnt work, wipe
Changing to a NEW rom, wipe.
This is all covered in the sticky threads. Please click the link in my signature and read the info threads.
Hi! Long time lurker, and I am using my first post to request for help. I haven't had to before, as I am usually able to use existing resources on XDA to fix my previous phones. Right now, I am stuck.
I have a Moto Maxx XT1250. I am using it on T-Mobile. I do not know what information will be useful in resolving this issue, so I am listing anything that might have attributed to the problem.
What I did with the phone:
Received used with stock KK installed. I did not test my SIM.
Unlocked bootloader.
Install TWRP-mod and fully backed-up everything, including modem partition.
(This is where I'm fairly positive I derped hard) Installed Brazil 6.0.1 stock SOAK via TWRP.
Lose IMEI info. I still have not tested my SIM.
Wipe everything in TWRP and restore original full KK backup. IMEI returns.
Installed ResurrectionRemix MM with OpenGAPPS slim first to test. It was OK.
Full wiped RR MM (system, data, cache, dalvik) and installed Mokee MM release w/ OpenGAPPS slim. Liked it!
Customized everything the way I wanted (Xposed, app restore via TitaniumBackup, etc.).
Inserted SIM.
Turned on phone, signal cuts out every few seconds. Always starts at 3 bars, then no service, back to 3 bars, and so on. I can make calls, sometimes receive. Sending and receiving texts is intermittent at best, almost nothing at worst. No data. Checked to make sure APN was correct (it was).
So I'm fairly positive flashing the 6.0.1 Brazil SOAK was my big no-no (against the advice of experienced members like ChazzMatt). Almost definitely messed up something regarding the modem and radio. Everything else works without issue though.
In my attempt to resolve the issue:
Checked forums regarding radio issues. Flashed clear_modem_status.zip first. No go.
Flashed QUARK_LRA_502_RADIO_AND_BOOTLOADER_PACKAGE.zip and it works!
Rebooted phone. Problem comes back.
From here, whenever I flash either the original latest radio zip or the clear_modem_status.zip, I have full service. Once I reboot, I encounter the signal issue again.
Attempted to restore modem via TWRP from clean stock KK backup. No signal.
Tried fastboot oem config fsg-id lra_gsm command. No go.
I am a bit stumped right now. But at this point, I am fairly positive I will have to flash back to stock 5.0.2 via RSDLite, then redo TWRP/flash ROM/Xposed/user customization again. However, I am curious if there is anything else I can try before doing this. I appreciate any response in advance, and can (attempt) to provide any further information I may have neglected to mention.
Update!
Update! So I decided to wipe everything and flash XT1250_QUARK_LRA_5.0.2_LXG22.33-12.27_cid9_subsidy-DEFAULT_CFC.xml via mfastboot. After starting up the phone again:
Going through the setup process, I encountered an issue where the SIM could not be detected. IMEI was also missing, once again.
Dumbfounded, I restored the modem portion of my stock KK backup. Now the SIM is read, the IMEI is present, and I get full service. This persisted through two reboots!
So I flashed the QUARK_LRA_502_RADIO_AND_BOOTLOADER_PACKAGE bootloader, radio, and gpt again... and the SIM/IMEI problem happened again.
I have found that, after restoring the stock KK modem backup:
If I flash the radio, that's when the problem occurs.
If I flash the gpt and/or bootloader, all is well.
I will now try to restore my Mokee MM backup w/ the stock KK modem. Hope it works!
Update 2!
OK. I am now stuck. I have flashed two different firmware files via RSDLite and the LP OTA from KK. These flashes included radio.img, and once these are flashed, my IMEI dissapears. The only way I have my IMEI is with my stock KK backup modem. I can use KK and LP stock without issue after restoring the backup modem, but I still have trouble with Mokee MM.
Any advice would be greatly appreciated, thanks!
Forgive me if I miss a couple of points. I'm not sure I have a total solution, but maybe a couple of suggestions.
alarsama said:
What I did with the phone:
Received used with stock KK installed. I did not test my SIM.
Unlocked bootloader.
Install TWRP-mod and fully backed-up everything, including modem partition.
(This is where I'm fairly positive I derped hard) Installed Brazil 6.0.1 stock SOAK via TWRP.
Lose IMEI info. I still have not tested my SIM.
Wipe everything in TWRP and restore original full KK backup. IMEI returns.
Installed ResurrectionRemix MM with OpenGAPPS slim first to test. It was OK.
Full wiped RR MM (system, data, cache, dalvik) and installed Mokee MM release w/ OpenGAPPS slim. Liked it!
Customized everything the way I wanted (Xposed, app restore via TitaniumBackup, etc.).
Inserted SIM.
Turned on phone, signal cuts out every few seconds. Always starts at 3 bars, then no service, back to 3 bars, and so on. I can make calls, sometimes receive. Sending and receiving texts is intermittent at best, almost nothing at worst. No data. Checked to make sure APN was correct (it was).
So I'm fairly positive flashing the 6.0.1 Brazil SOAK was my big no-no (against the advice of experienced members like ChazzMatt). Almost definitely messed up something regarding the modem and radio. Everything else works without issue though.
In my attempt to resolve the issue:
Checked forums regarding radio issues. Flashed clear_modem_status.zip first. No go.
Flashed QUARK_LRA_502_RADIO_AND_BOOTLOADER_PACKAGE.zip and it works!
Rebooted phone. Problem comes back.
From here, whenever I flash either the original latest radio zip or the clear_modem_status.zip, I have full service. Once I reboot, I encounter the signal issue again.
Attempted to restore modem via TWRP from clean stock KK backup. No signal.
[*]Tried fastboot oem config fsg-id lra_gsm command. No go.
I am a bit stumped right now. But at this point, I am fairly positive I will have to flash back to stock 5.0.2 via RSDLite, then redo TWRP/flash ROM/Xposed/user customization again. However, I am curious if there is anything else I can try before doing this. I appreciate any response in advance, and can (attempt) to provide any further information I may have neglected to mention.
Click to expand...
Click to collapse
Yes, installing soak test for a different Android OS for a phone with a different FCC ID, different internal storage (32GB vs 64GB) is the root of your issues.
I'm surprised you were able to re-flash the Lollipop bootloader and it worked. With the Marshmallow soak test it would seem you were on a Marshmallow bootloader and normally you can't downgrade that. Normally you have to flash everything except for gpt.bin if going back from factory image to a lower Android OS factory image.
The current Mokee, even though Marshmallow actually uses Lollipop bootloader.
[*]Tried fastboot oem config fsg-id lra_gsm command. No go.
Click to expand...
Click to collapse
That would have been one of my suggestions.
alarsama said:
Update! So I decided to wipe everything and flash XT1250_QUARK_LRA_5.0.2_LXG22.33-12.27_cid9_subsidy-DEFAULT_CFC.xml via mfastboot. After starting up the phone again:
Going through the setup process, I encountered an issue where the SIM could not be detected. IMEI was also missing, once again.
Dumbfounded, I restored the modem portion of my stock KK backup. Now the SIM is read, the IMEI is present, and I get full service. This persisted through two reboots!
So I flashed the QUARK_LRA_502_RADIO_AND_BOOTLOADER_PACKAGE bootloader, radio, and gpt again... and the SIM/IMEI problem happened again.
I have found that, after restoring the stock KK modem backup:
If I flash the radio, that's when the problem occurs.
If I flash the gpt and/or bootloader, all is well.
I will now try to restore my Mokee MM backup w/ the stock KK modem. Hope it works!
Click to expand...
Click to collapse
alarsama said:
OK. I am now stuck. I have flashed two different firmware files via RSDLite and the LP OTA from KK. These flashes included radio.img, and once these are flashed, my IMEI dissapears. The only way I have my IMEI is with my stock KK backup modem. I can use KK and LP stock without issue after restoring the backup modem, but I still have trouble with Mokee MM.
Any advice would be greatly appreciated, thanks!
Click to expand...
Click to collapse
Forgive me if I am suggesting something you have already tried.
First, save off all your data you think you need.
Then, in TWRP exhaustively reformat your entire partition. I forget the command, you can look it up, but it's not the "quick" format -- it's the one that takes like 30 minutes. It makes my phone get very hot so I stick it in the refrigerator.
Next, how about flashing the stock 5.0.2 but excluding the gpt.bin? Flash with your SIM card in.
Then after flashing that, re-flash the radio again -- with the SIM card in:
mfastboot flash radio radio.img
fastboot oem config fsg-id lra_gsm
If that doesn't work, try that again this time flashing with gpt.bin. But I'm just hesitant to recommend you flash a lower bootloader partition (Kitkat or Lollipop) since you originally had flashed the soak test (for a different Quark) of Marshmallow. Even though you've already done it several times now. :silly:
If I was adventurous (and I'm not), I might even re-flash the soak test gpt.bin (since downgrading from that is probably what's confusing your system), then flash Mokee + radio, but not the bootloader -- just ROM and radio with the
mfastboot flash radio radio.img
fastboot oem config fsg-id lra_gsm
Somebody like @Skrilax_CZ or @baybutcher27, who has very extensive experience in these matters would be a better advisor. Besides several Nexus devices and a few LG smartphones, my experience flashing my Quarks is mostly desiring to not mess them up. I did flash Moto Maxx XT1225 to Moto Turbo XT1225 to get Lollipop, and flashing CM ROMs, and later re-flashing updated Puerto Rico 5.0.2 radio. But I'm not an msfastboot expert.
Hi ChazzMatt!
It does make sense that the Brazil 6.0.1 SOAK is the root of my issues. Do not apologize, any suggestion is more than welcome!
I have backed up all my important data.
I have looked for TWRP terminal commands with little success. Might general Linux terminal commands work in place?
I actually have flashed the gpt.bin for stock KK and stock LP MULTIPLE times... I'm not sure how much that affects anything >.<
I will otherwise try everything you have suggested and get back with an update. Thanks for your advice and information, it has helped me understand my situation more.
So while I was working on the phone, I realized a few things...
ChazzMatt said:
I'm surprised you were able to re-flash the Lollipop bootloader and it worked. With the Marshmallow soak test it would seem you were on a Marshmallow bootloader and normally you can't downgrade that. Normally you have to flash everything except for gpt.bin if going back from factory image to a lower Android OS factory image.
The current Mokee, even though Marshmallow actually uses Lollipop bootloader.
Click to expand...
Click to collapse
I had installed the 6.0.1 MM Brazil Soak 3 via TWRP with this guide: http://forum.xda-developers.com/moto-maxx/help/tutorial-moto-maxx-6-0-1-brazil-soak-t3340820. In that case, it would not have installed the MM bootloader or partition table (gpt.bin), correct? It would explain why I am still able to flash stock LP (and for some strange reason, stock KK). I think this point is corroborated by the fact that, when I flash gpt.bin for stock LP via fastboot, it is successful. But when I flash gpt.bin for stock KK, it fails. So right now, I am fairly positive I am using the LP bootloader, and this may be why Mokee boots without issue (except the whole signal thing that plagues me).
ChazzMatt said:
Then, in TWRP exhaustively reformat your entire partition. I forget the command, you can look it up, but it's not the "quick" format -- it's the one that takes like 30 minutes. It makes my phone get very hot so I stick it in the refrigerator.
Click to expand...
Click to collapse
So far, I have not been able to find these commands. Could you point me in the right direction?
ChazzMatt said:
Next, how about flashing the stock 5.0.2 but excluding the gpt.bin? Flash with your SIM card in.
Then after flashing that, re-flash the radio again -- with the SIM card in:
mfastboot flash radio radio.img
fastboot oem config fsg-id lra_gsm
If that doesn't work, try that again this time flashing with gpt.bin. But I'm just hesitant to recommend you flash a lower bootloader partition (Kitkat or Lollipop) since you originally had flashed the soak test (for a different Quark) of Marshmallow. Even though you've already done it several times now. :silly:
Click to expand...
Click to collapse
I have done as you have instructed. No go.
ChazzMatt said:
If I was adventurous (and I'm not), I might even re-flash the soak test gpt.bin (since downgrading from that is probably what's confusing your system), then flash Mokee + radio, but not the bootloader -- just ROM and radio with the
mfastboot flash radio radio.img
fastboot oem config fsg-id lra_gsm
Click to expand...
Click to collapse
So I tried a (sort of) variation of these instructions. As I do not have the MM gpt.bin, I full wiped (system/cache/dalvik/data/internal storage), flashed Mokee, then flashed the radio via mfastboot and set the fsg-id to lra_gsm. Upon first boot, the SIM is read, I see my IMEI, baseband is present, etc. However, after a reboot, same issue occurs (no data, weak signal meaning missed calls and texts not sent/received).
I have found that, when I either flash the clean_modem_status.zip or the LP radio, the problem disappears. It's only on the next reboot(s) that the problem comes back. Therefore, this is primarily a modem/radio issue.
ChazzMatt said:
Somebody like @Skrilax_CZ or @baybutcher27, who has very extensive experience in these matters would be a better advisor. Besides several Nexus devices and a few LG smartphones, my experience flashing my Quarks is mostly desiring to not mess them up. I did flash Moto Maxx XT1225 to Moto Turbo XT1225 to get Lollipop, and flashing CM ROMs, and later re-flashing updated Puerto Rico 5.0.2 radio. But I'm not an msfastboot expert.
Click to expand...
Click to collapse
It would be fantastic if they could lend me their aid, and hopefully they view this thread and advise me as well, but I still appreciate the advice you have given.
alarsama said:
So far, I have not been able to find these commands. Could you point me in the right direction?
Click to expand...
Click to collapse
I believe it's the secure erase function of TWRP. It overwrites all bits of your internal memory.
All I can find is an older version of TWRP that does it, uploaded by @baybutcher27
https://androidfilehost.com/?fid=24052804347796742
[QUOTE ] @baybutcher27About secure erase:
Secure erase is:
When a Secure Erase command is sent, data in the
specified memory addresses must be purged from the
physical memory array
“Logical” memory erase is not acceptable.
I determined that in the TWRP secure erase, the only ting be done is to, erase every file after a process start to "purged" fill it block of memory with zero (or one) making impossible to some one to restore any of the previously data.[/QUOTE]
Hi everyone! Before I describe my problem, I need you to know that I'm somewhat a noob when it comes to resolving and tinkering with software on Androids, but have some basic knowledge. I've look into all options and posting here is my last resort, please be patient
So recently, a customer brought in a J320FN. It is running on an older update (J320FNXXU0APH1, August 2016), and a few days back, after updating it to the lastest version the phone seized up. The owner has pictures and contacts that he really want to recover. After surfing through some forums, I saw that some phones, when being flashed with stock ROM via Odin, don't lose personal data, and some do. Before I try to flash this device, I want to make sure I can flash the stock ROM and eventually save the data.
I've tried wiping cache partition, because that's what I usually do when encountering software issues.
Also, the phone boots to the point where I can see the current time, and swipe down the notification bar. After some seconds, the phone reboots and the whole thing just goes on.
So my questions are;
1. Do I flash the latest version of Android or just reflash the current one?
2. Do I lose personal data, such as photos, videos and contacts?
3. Is there anything else I can do, before flashing fresh ROM on the device ?
bregaryevich said:
Hi everyone! Before I describe my problem, I need you to know that I'm somewhat a noob when it comes to resolving and tinkering with software on Androids, but have some basic knowledge. I've look into all options and posting here is my last resort, please be patient
So recently, a customer brought in a J320FN. It is running on an older update (J320FNXXU0APH1, August 2016), and a few days back, after updating it to the lastest version the phone seized up. The owner has pictures and contacts that he really want to recover. After surfing through some forums, I saw that some phones, when being flashed with stock ROM via Odin, don't lose personal data, and some do. Before I try to flash this device, I want to make sure I can flash the stock ROM and eventually save the data.
I've tried wiping cache partition, because that's what I usually do when encountering software issues.
Also, the phone boots to the point where I can see the current time, and swipe down the notification bar. After some seconds, the phone reboots and the whole thing just goes on.
So my questions are;
1. Do I flash the latest version of Android or just reflash the current one?
2. Do I lose personal data, such as photos, videos and contacts?
3. Is there anything else I can do, before flashing fresh ROM on the device ?
Click to expand...
Click to collapse
When it comes to flashing Samsung devices via Odin and whether or not the user data is erased or not, it depends on whether you are flashing a firmware that has an upgraded or downgraded bootloader.
The user data only gets wiped if you flash a firmware that has a bootloader that is older than the one currently installed on the device or if the bootloader is newer than the one currently on the device.
The user data does not get wiped if you flash the exact same firmware that is currently installed on the device, or at least, a firmware that has the exact same version of bootloader as the one currently installed on the device.
So you basically have 2 questions to answer.
1) does the firmware that I want to flash have an upgraded bootloader version compared to the bootloader version that is currently installed on the device?
2) does the firmware that I want to flash have a downgraded bootloader version compared to the bootloader version that is currently installed on the device?
If the answer to either of these two questions is no, then you can flash without it wiping the user data.
If the answer to either of these two questions is yes, then the user WILL be wiped during flashing.
If you want to try to save the user data before flashing the firmware, you can try finding a version of TWRP for J320N and flash it on the device then use the backup feature in TWRP to create a full backup of all data on the device. Then flash the firmware of uour choice via Odin, then the data can be extracted from the backup that was created via TWRP and restored on the device after flashing the firmware.
Sent from my LGL84VL using Tapatalk
Droidriven said:
When it comes to flashing Samsung devices via Odin and whether or not the user data is erased or not, it depends on whether you are flashing a firmware that has an upgraded or downgraded bootloader.
The user data only gets wiped if you flash a firmware that has a bootloader that is older than the one currently installed on the device or if the bootloader is newer than the one currently on the device.
The user data does not get wiped if you flash the exact same firmware that is currently installed on the device, or at least, a firmware that has the exact same version of bootloader as the one currently installed on the device.
So you basically have 2 questions to answer.
1) does the firmware that I want to flash have an upgraded bootloader version compared to the bootloader version that is currently installed on the device?
2) does the firmware that I want to flash have a downgraded bootloader version compared to the bootloader version that is currently installed on the device?
If the answer to either of these two questions is no, then you can flash without it wiping the user data.
If the answer to either of these two questions is yes, then the user WILL be wiped during flashing.
If you want to try to save the user data before flashing the firmware, you can try finding a version of TWRP for J320N and flash it on the device then use the backup feature in TWRP to create a full backup of all data on the device. Then flash the firmware of uour choice via Odin, then the data can be extracted from the backup that was created via TWRP and restored on the device after flashing the firmware.
Click to expand...
Click to collapse
Hey, thanks for the quick response.
I tried what you recommended but the problem still persists. After flashing the current version, the phone did the exact same thing and started looping.
Also tried TWRP but there's an FRP lock, preventing me from flashing it.
Now that the stock rom flash thing failed, guess there's only TWRP left. I did FRP unlocks before, but not on phones that are soft bricked. Is there anyway around it except wiping all data?
I may have forgot to mention, that the phone indeed has a passcode. And god knows what did the owner install/do with the device, that made ot to seize up.