Related
my phone is stuck in bootloop. im able to get into CWM recovery, but cant restore nandroid or make a nandroid.
keeps looping in google screen
someone please help.
acatabian said:
my phone is stuck in bootloop. im able to get into CWM recovery, but cant restore nandroid or make a nandroid.
keeps looping in google screen
someone please help.
Click to expand...
Click to collapse
Have you tried a wipe from cwm?
Sent from my Galaxy Nexus using xda premium
i wiped data/cache/dalvik and still nothing.
:'(
anyone please, i dont know whats happening
Now that you've wiped it, you won't be able to make a nandroid anyway, you'd be backing up... nothing. When you say you can't restore a nandroid, what exactly is happening when you try? Do you try to restore an existing nandroid and an error stops the process? Does CWM not find any nandroids that should be there? Have you ever restored to a nadroid before that you know there *should* be one that works?
Based on what you've written here I'd suggest just restoring to factory installation and picking up the pieces from there. Before you do, you can try to backup what's on your phone using the command "adb pull /sdcard". If you have a nandroid that might be good but for some reason unusable by your phone right now, it will be copied and you can try to restore it after reverting to factory settings. Otherwise, it should pull off any personal stuff like your photos etc so it's not a total loss.
If you're on a GSM Nexus, follow instructions here.
If you're on a CDMA Nexus, follow instructions here.
It is really the exact same process for either, but you want to make sure you've got the right set of files. This will basically leave you where you were when you first unlocked the bootloader.
JoeSyr said:
Now that you've wiped it, you won't be able to make a nandroid anyway, you'd be backing up... nothing. When you say you can't restore a nandroid, what exactly is happening when you try? Do you try to restore an existing nandroid and an error stops the process? Does CWM not find any nandroids that should be there? Have you ever restored to a nadroid before that you know there *should* be one that works?
Based on what you've written here I'd suggest just restoring to factory installation and picking up the pieces from there. Before you do, you can try to backup what's on your phone using the command "adb pull /sdcard". If you have a nandroid that might be good but for some reason unusable by your phone right now, it will be copied and you can try to restore it after reverting to factory settings. Otherwise, it should pull off any personal stuff like your photos etc so it's not a total loss.
If you're on a GSM Nexus, follow instructions here.
If you're on a CDMA Nexus, follow instructions here.
It is really the exact same process for either, but you want to make sure you've got the right set of files. This will basically leave you where you were when you first unlocked the bootloader.
Click to expand...
Click to collapse
yeah, i ended up unrooting and flashing factory image back. but i did however root and unlock bootloader again.
now, whenever i finish flashing my new rom. it gets stuck looping on the boot animation, not the google logo. is there any reason behind this? could it relate back to what happened before?
acatabian said:
yeah, i ended up unrooting and flashing factory image back. but i did however root and unlock bootloader again.
now, whenever i finish flashing my new rom. it gets stuck looping on the boot animation, not the google logo. is there any reason behind this? could it relate back to what happened before?
Click to expand...
Click to collapse
When you say "it gets stuck", how long are we talking here? Sometimes, depending on what you just wiped/what you're flashing, the phone will just take a longer time to boot. If you assume something's wrong and pull the battery you might just mess it up when really you just needed to be patient and let it finish.
These are probably questions best addressed in threads for specific ROMs, though, where people might have had similar experiences, or the ROM dev might be able to use your feedback. It's especially hard to formulate an opinion that might be useful when you provide barely any specific information to what you're working with.
Hi all,
I recently got a HK N7105 and because it lacked the possibility to use a french keyboard I upgraded to a stock unbranded ROM from Sweden (XXDLL1) and succesfully rooted with the relevant CF_autoroot through Odin. Also installed TWRP 2.3.3.1.
Then, I connected the Note 2 to my corporate exchange server which enforced a full encryption policy (device and external SD card) so I had to type in a password at each boot time (with a "nice" swedish prompt that took ma while to decypher), plus a password to unlock the screen. All was well as the root survived the process.
Next I upgraded to a later stock ROM from France (XXDLL4 from SFR) to try and get rid of the swedish prompt. That worked fine (and root was loast in the process, as expected) but I hated the branded stuff so much I reverted to XXDLL1 until a proper unbranded "english" or "french" ROM is available.
At this point I decided to root again. I was running XXDLL1 like the first time and used the same autoroot tar from Chainfire. Except my Note 2 was still encrypted and after that it would not accept my boot password (a four digit PIN) anymore so I was guted and had to factory reset and root then reinstall everything before reconnecting to the exchange server.
Question 1: Does anyone know of a safe, proven way to root a fully encrypted Samsung device so I can go another upgrade without having to wipe the device first?
Why reinstall everything? Why not backup everything first so you can restore after the wipe? Well, it so happens that no recovery (at least neither CWM or TWRP) can read any encrypted media on the Note 2 at the moment. And no Recovery can actually fully backup the device as well.
Question 2: Does anyone know of a proper way to handle this situation with minimum hassle?
So far, the best I can think of is doing a Titanium backup and FTP the files to my NAS so I can retrieve them later. But (Question 3) will this be enough to restore my phone to the expected state after a stock firmware upgrade?
Thanks in advance,
François
frankieGom said:
Hi all,
I recently got a HK N7105 and because it lacked the possibility to use a french keyboard I upgraded to a stock unbranded ROM from Sweden (XXDLL1) and succesfully rooted with the relevant CF_autoroot through Odin. Also installed TWRP 2.3.3.1.
Then, I connected the Note 2 to my corporate exchange server which enforced a full encryption policy (device and external SD card) so I had to type in a password at each boot time (with a "nice" swedish prompt that took ma while to decypher), plus a password to unlock the screen. All was well as the root survived the process.
Next I upgraded to a later stock ROM from France (XXDLL4 from SFR) to try and get rid of the swedish prompt. That worked fine (and root was loast in the process, as expected) but I hated the branded stuff so much I reverted to XXDLL1 until a proper unbranded "english" or "french" ROM is available.
At this point I decided to root again. I was running XXDLL1 like the first time and used the same autoroot tar from Chainfire. Except my Note 2 was still encrypted and after that it would not accept my boot password (a four digit PIN) anymore so I was guted and had to factory reset and root then reinstall everything before reconnecting to the exchange server.
Question 1: Does anyone know of a safe, proven way to root a fully encrypted Samsung device so I can go another upgrade without having to wipe the device first?
Why reinstall everything? Why not backup everything first so you can restore after the wipe? Well, it so happens that no recovery (at least neither CWM or TWRP) can read any encrypted media on the Note 2 at the moment. And no Recovery can actually fully backup the device as well.
Question 2: Does anyone know of a proper way to handle this situation with minimum hassle?
So far, the best I can think of is doing a Titanium backup and FTP the files to my NAS so I can retrieve them later. But (Question 3) will this be enough to restore my phone to the expected state after a stock firmware upgrade?
Thanks in advance,
François
Click to expand...
Click to collapse
I think using Exynos Abuse apk will do the work
http://forum.xda-developers.com/showthread.php?t=2050297
Thanks for the heads up, I'll look into it. But to be clear, that answers question 1, correct?
Sent from my GT-N7105 using xda app-developers app
frankieGom said:
Thanks for the heads up, I'll look into it. But to be clear, that answers question 1, correct?
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Yes that's a way to root the device.
Regarding encryption, very few people on xda seem to use it. So for that reason you'll have trouble finding out what works... I do use it though through choice so I can help you a bit.
When you encrypt the device, just consider /data to be off limits to anything not booted fully. That's why it asks you for your key in swedish - it can't see what language is in use until you unlock /data.
You will have issues using recovery with the device, since they can't read /data. You can use an external sd to perhaps load data to the device though.
I believe that TWRP might soon support the Samsung encryption on the device, meaning you could use it as recovery. Once you have a recovery that supports Samsung encryption, you should be able to consider it a fairly normal device.
Just be more cautious to backup your data as it is hard to recover if something goes wrong...
If your using stock rom 4.1.2, exynos abuse method of root will not work. It's been patched
Sent from my GT-N7100 using xda app-developers app
pulser_g2 said:
Yes that's a way to root the device.
Regarding encryption, very few people on xda seem to use it. So for that reason you'll have trouble finding out what works... I do use it though through choice so I can help you a bit.
When you encrypt the device, just consider /data to be off limits to anything not booted fully. That's why it asks you for your key in swedish - it can't see what language is in use until you unlock /data.
You will have issues using recovery with the device, since they can't read /data. You can use an external sd to perhaps load data to the device though.
I believe that TWRP might soon support the Samsung encryption on the device, meaning you could use it as recovery. Once you have a recovery that supports Samsung encryption, you should be able to consider it a fairly normal device.
Just be more cautious to backup your data as it is hard to recover if something goes wrong...
Click to expand...
Click to collapse
Fine, I understand. As long as I have a way to recover my data if I need to wipe I'm okay... I just have to hope Titanium backup gives me that until TWRP can manage encruption on the Note 2.
I'm really waiting for a stock rom that boots in English or French now.
Sent from my GT-N7105 using xda app-developers app
vash_h said:
If your using stock rom 4.1.2, exynos abuse method of root will not work. It's been patched
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Not the case with xxdll1. When was it patched, xxdll4 or xxdll7?
Sent from my GT-N7105 using xda app-developers app
frankieGom said:
Not the case with xxdll1. When was it patched, xxdll4 or xxdll7?
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
I am on Stock 4.1.2 and Exynos Abuse did work on my device, it's successfully rooted using the Exynos AbuseAPK on 4.1.2 :good:
OK, now I have been experimenting a bit with backups and upgrade and have trouble restoring my device fully. Let me explain...
I got hold of a TWRP build that seems to handle Samsung encryption fine through one of the TWRP devs (thanks!), so I decided to go back and try to update my device.
Current ROM: N7105XXDLL1_N7105TLADLL1_N7105XXDLK7_HOME.tar (obtained from Samsung Updates)
New ROM: N7105XXDLL7_N7105OLBDLL2_N7105DXDLL1_HOME.tar (obtained from Samsung Updates)
First I performed a complete Titanium Backup on the device and pulled the files to my laptop using ADB.
Then I restarted into TWRP 2.4.0.0 (got a prompt for my password), performed a full backup and pulled the files to the laptop using ADB.
(for some reason, I could not install the new ROM from TWRP (unable to open ZIP), but the ZIP looked OK, as well as after a second download which TWRP since did not like, so I had to use Odin instead).
Next, I flashed DLL7 with Odin. It worked, asked for the password at boot, but the device was unrooted at this point (I expected that).
Then, I flashed CF-Auto-Root-t0lte-t0ltexx-gtn7105.tar from Odin, but the boot up password would not be accepted anymore as I already knew.
Tried to flash DLL7 again from Odin, same thing
Flashed TWRP back on recovery partition, but on startup it would not ask for password anymore and the external sdcard looked empty to it.
I then copied my backup to a different, non encrypted sdcard and could restore from TWRP but the password would still not work after reboot.
I did a factory reset, restored backup, same result.
At this point I decided to factory reset, wipe Dalvik and format /data. The format did the trick and after TWRP restore of my original back up the device booted up, did not ask for password and all my data was there. Except the Exchange account I use for Corporate email wants me to restore encryption in order to work (I expected that too).
Back at DLL1, so I flashed DLL7 again with Odin (OK), rooted the phone, triangled away the flash counter and reflashed TWRP to recovery.
I was where I wanted to be except for one thing: I need to restore Corporate access. But when I let it encryp the phone it does nothing. I let it through the night and nothing). And if I reboot the phone no password is needed at boot time, yet the phone seems to behave as if it thought the device was still encrypted...
I reflashed my original, full, backup (i.e DLL1) succesfully but Exchange still wants to encrypt my device. Isn't restore supposed to restore the encrypted /data I backed up?
At this point I'm left with possibly tryinjg to go back to full factory settings, not use the backup at all, encrypt the device then restore my data from the Titanium backup I made.
Is there a better option?
[edited jan 18 - TWRP/TB behaviour]
My comments apply to encrypted devices only! I am not trying to talk down TWRP or TB here, as they provide splendid performance on non encrypted devices. I have come upon hard time trying to upgrade/restore an encrypted device using thoise tools, that's all
For those considering upgrading & re-rooting encrypted devices, don't!
I am finding the hard way that this is a one way street. At this point, my TWRP made full backup does not restore the device to the expected status. Each time I apply it, subsequent bootup takes several minutes and I end up going through the initial setup procedure. It seems the device for some reasoin goes through a complete reset procedure.
[edit]
Clarification: The TWRP build I use, 2.4.0.0 is an alpha build and I was not current when I restored my backup. I so happens that it was overwriting the encryption header on the partition, which messed things up bad, and had issues writing back the data partition, ending up in a factory reset status!
Using the latest drop as of today (jan 27) I was able to restore my original backup and am now back to my original state. All is well.
[/edit]
Titanium Backup is none better. It keeps telling me that my Android ID has changed, a host of system applications start to fail when I try to restore and generally speaking I have now spent between a good 20 hours trying to simply restore my data.
[edit]
this behaviour is probably linked to encryption. I know for a fact that TB works very well on non encrypted phones. The 20h figure is overall, not just with TB.
[/edit]
The end story is: root before you encrypt, and either don't upgrade or don't re-root if you do! If you do, be prepared for some rough times...
Unless someone has a cleat idea of how to do this properly without losing all your data, that is.
François
frankieGom said:
For those considering upgrading & re-rooting encrypted devices, don't!
I am finding the hard way that this is a one way street. At this point, my TWRP made full backup does not restore the device to the expected status. Each time I apply it, subsequent bootup takes several minutes and I end up going through the initial setup procedure. It seems the device for some reasoin goes through a complete reset procedure.
Titanium Backup is none better. It keeps telling me that my Android ID has changed, a host of system applications start to fail when I try to restore and generally speaking I have now spent between a good 20 hours trying to simply restore my data.
The end story is: root before you encrypt, and either don't upgrade or don't re-root if you do!
Unless someone has a cleat idea of how to do this properly without losing all your data, that is.
François
Click to expand...
Click to collapse
I have had no issues despite doing upgrades, with and without wipes.
Titanium is fine, just stop restoring system app data. Seriously, what data do you have in a system app that you want to restore.
Restore your user apps, their data, and the xml based call, sms, Wifi backups. It will work fine.
Device ID isn't a problem - it's just trying to help you.
pulser_g2 said:
I have had no issues despite doing upgrades, with and without wipes.
Titanium is fine, just stop restoring system app data. Seriously, what data do you have in a system app that you want to restore.
Restore your user apps, their data, and the xml based call, sms, Wifi backups. It will work fine.
Device ID isn't a problem - it's just trying to help you.
Click to expand...
Click to collapse
Sorry if I came across dissing Titanium Backup and/or TWRP. This was not the intent... I am sure both tools work real nice in general cases (and I have had success restoring data on a Jetstream before).
My main issue here is _full device encryption_ enforced by my company's corporate IT to allow me on the corporate exchange server. Do you have full device encryption on?
On my device, even after a full wipe and flashing a fresh stock rom Titanium Backup just did not work as I hoped. When I had to confirm individual popups of apps closing unexpectedly while it was proceeding and got nothing back in the end, what was I supposed to think? It could be that I don't understand how TB works... I was neither able to restore missing apps after the flash (missing apps: 0) nor installed apps data (they would close unexpectedly when started after restoring the back up). So I say: until full operation of TB on encrypted devices is documented, I will stay away from it, even though I am a registered user (and I do not plan to seek reimbursment)!
Anyway, I got to a belated happy ending (previous post edited).
frankieGom said:
Sorry if I came across dissing Titanium Backup and/or TWRP. This was not the intent... I am sure both tools work real nice in general cases (and I have had success restoring data on a Jetstream before).
My main issue here is _full device encryption_ enforced by my company's corporate IT to allow me on the corporate exchange server. Do you have full device encryption on?
On my device, even after a full wipe and flashing a fresh stock rom Titanium Backup just did not work as I hoped. When I had to confirm individual popups of apps closing unexpectedly while it was proceeding and got nothing back in the end, what was I supposed to think? It could be that I don't understand how TB works... I was neither able to restore missing apps after the flash (missing apps: 0) nor installed apps data (they would close unexpectedly when started after restoring the back up). So I say: until full operation of TB on encrypted devices is documented, I will stay away from it, even though I am a registered user (and I do not plan to seek reimbursment)!
Anyway, I got to a belated happy ending (previous post edited).
Click to expand...
Click to collapse
Yup I use device encryption Enabled manually, but it's the same encryption.
You should find that titanium shouldn't even be aware of it - the encryption is transparent!
I wonder... I'm sure lenny had that issue on a recent 4.1.2 "stock" ROM... And he doesn't use encryption...
I personally have had no issues with titanium on an encrypted device anyway
I notice you were using the newest rom - that's the one lenny had issues on.
pulser_g2 said:
Yup I use device encryption Enabled manually, but it's the same encryption.
You should find that titanium shouldn't even be aware of it - the encryption is transparent!
I wonder... I'm sure lenny had that issue on a recent 4.1.2 "stock" ROM... And he doesn't use encryption...
I personally have had no issues with titanium on an encrypted device anyway
I notice you were using the newest rom - that's the one lenny had issues on.
Click to expand...
Click to collapse
Exactly like I thought, encryption should be transparent to Titanium Backup since it runs within the OS.
I have had problems restoring into 4.1.2 DLL1 (the build I came from) and DLL7 (the one I was trying to go to)
The point is moot anyway since the DLL7 I tried was actually branded (Singtel stuff all around the launcher) and did not include French, which is why restoring my TWRP backup was a tempting proposition.
Good to know TB runs fine with encryption as well. What ROM are you running?
François
frankieGom said:
Hi all,
I recently got a HK N7105 and because it lacked the possibility to use a french keyboard I upgraded to a stock unbranded ROM from Sweden (XXDLL1) and succesfully rooted with the relevant CF_autoroot through Odin. Also installed TWRP 2.3.3.1.
Then, I connected the Note 2 to my corporate exchange server which enforced a full encryption policy (device and external SD card) so I had to type in a password at each boot time (with a "nice" swedish prompt that took ma while to decypher), plus a password to unlock the screen. All was well as the root survived the process.
Next I upgraded to a later stock ROM from France (XXDLL4 from SFR) to try and get rid of the swedish prompt. That worked fine (and root was loast in the process, as expected) but I hated the branded stuff so much I reverted to XXDLL1 until a proper unbranded "english" or "french" ROM is available.
At this point I decided to root again. I was running XXDLL1 like the first time and used the same autoroot tar from Chainfire. Except my Note 2 was still encrypted and after that it would not accept my boot password (a four digit PIN) anymore so I was guted and had to factory reset and root then reinstall everything before reconnecting to the exchange server.
Question 1: Does anyone know of a safe, proven way to root a fully encrypted Samsung device so I can go another upgrade without having to wipe the device first?
Why reinstall everything? Why not backup everything first so you can restore after the wipe? Well, it so happens that no recovery (at least neither CWM or TWRP) can read any encrypted media on the Note 2 at the moment. And no Recovery can actually fully backup the device as well.
Question 2: Does anyone know of a proper way to handle this situation with minimum hassle?
So far, the best I can think of is doing a Titanium backup and FTP the files to my NAS so I can retrieve them later. But (Question 3) will this be enough to restore my phone to the expected state after a stock firmware upgrade?
Thanks in advance,
François
Click to expand...
Click to collapse
About a backup : have you tried Online Nandroid (Playstore) (or similar, based on Onandroid) ? This makes a CWM or TWRP compatible backup while the device is running (everything should be unencrypted at this moment).
See http://forum.xda-developers.com/showthread.php?t=1620255
About rooting : you can try the same trick as above, by using ADB-shell and pushing the needed files to root to the device while it is running.
For my S3 there is a Toolkit that automates all this (http://forum.xda-developers.com/showthread.php?t=1703488), maybe there is something similar for your device ?
If not, you should still be able to do it using manual ADB-pushing.
I'm sorry I can't give you detailed instructions about the rooting as I'm not familiar with your device. Search here on XDA and you'll find more details.
pat357 said:
About a backup : have you tried Online Nandroid (Playstore) (or similar, based on Onandroid) ? This makes a CWM or TWRP compatible backup while the device is running (everything should be unencrypted at this moment).
See http://forum.xda-developers.com/showthread.php?t=1620255
About rooting : you can try the same trick as above, by using ADB-shell and pushing the needed files to root to the device while it is running.
For my S3 there is a Toolkit that automates all this (http://forum.xda-developers.com/showthread.php?t=1703488), maybe there is something similar for your device ?
If not, you should still be able to do it using manual ADB-pushing.
I'm sorry I can't give you detailed instructions about the rooting as I'm not familiar with your device. Search here on XDA and you'll find more details.
Click to expand...
Click to collapse
Thanks for the suggestions, and no I had not tried Online Nandroid as I was not aware of it. Anyway, my main issue is now resolved since TWRP has include support for Samsung TouchWiz based encryption in 2.4 and that works well.
For those interested, the only remaining issues I have with TWRP regarding encryption are that if you want to format /data from TWRP (say, to remove encryption) it will fail unless you _do not_ enter the password at boot, and the TWRP formated /data cannot be re-encrypted (you must use stock recovery to factory reset/wipe the device or else the encryption step will sit deat in the water doing nothing). I suppose the second one is a bug that will be fixed in a later version.
I will check Online Nandroid out anyway, being able to make a backup from a live system sounds good!
François
frankieGom said:
Thanks for the suggestions, and no I had not tried Online Nandroid as I was not aware of it. Anyway, my main issue is now resolved since TWRP has include support for Samsung TouchWiz based encryption in 2.4 and that works well.
For those interested, the only remaining issues I have with TWRP regarding encryption are that if you want to format /data from TWRP (say, to remove encryption) it will fail unless you _do not_ enter the password at boot, and the TWRP formated /data cannot be re-encrypted (you must use stock recovery to factory reset/wipe the device or else the encryption step will sit deat in the water doing nothing). I suppose the second one is a bug that will be fixed in a later version.
I will check Online Nandroid out anyway, being able to make a backup from a live system sounds good!
François
Click to expand...
Click to collapse
I have a similar issue. I had the device encrypted and decided to ROOT (using CF-AutoRoot). Unfortunately I cannot bypass the password screen now, although I know that I'm entering the right password. You are saying that if I flash TWRP everything will be fine?
ludovicianul said:
I have a similar issue. I had the device encrypted and decided to ROOT (using CF-AutoRoot). Unfortunately I cannot bypass the password screen now, although I know that I'm entering the right password. You are saying that if I flash TWRP everything will be fine?
Click to expand...
Click to collapse
Two separate things:
Root messing up encrypted touchwiz devices and twrp not handling touchwiz encrypted partitions properly.
The 2nd one, as much as I can tell, is fixed since before 2.5 so if youwork with the latest (2.6) you should be fine.
The first one I haven't played with in a while, but my finding is that you don't want to root a device once it's been encrypted. I've tried several different methods including rooting as you flag as is possible with twrp and all end up the same:the password is not recognised anymore!
The only thing that works for me is rooting before encrypting or only flashing pre-rooted ROMs.
frankieGom said:
Two separate things:
Root messing up encrypted touchwiz devices and twrp not handling touchwiz encrypted partitions properly.
The 2nd one, as much as I can tell, is fixed since before 2.5 so if youwork with the latest (2.6) you should be fine.
The first one I haven't played with in a while, but my finding is that you don't want to root a device once it's been encrypted. I've tried several different methods including rooting as you flag as is possible with twrp and all end up the same:the password is not recognised anymore!
The only thing that works for me is rooting before encrypting or only flashing pre-rooted ROMs.
Click to expand...
Click to collapse
Yes - I had to factory reset the phone and format the SD Card. Never root AFTER encryption :silly:
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.
First root and thought I had everything covered, but of course something hiccuped and now I have Unknown IMEI, Baseband, Hardware version, Software version and can't connect to the network. All my apps and wifi are working.
Before installing TWRP I looked for a way to backup my entire device and could find nothing that would work before rooting or flashing a recovery to replace the stock recovery. I finally just went ahead and flashed TWRP and created a backup with that. There were errors that had to do with the Samsung calendar app data that made the backup fail. I excluded data from the backup and was able to complete what was reported as a successful backup. I did not allow TWRP to install root access before reboot.
I then installed via Odin the Chainfire SuperSU successfully and thought was free and clear. When I rebooted everything worked fine, except the phone would not connect to network and reported "Searching for Service."
Upon investigation into that I discovered the other issues that all seem to be tied to the EFS partition. I tried restoring the EFS partition from the TWRP backup I created immediately after installing TWRP, but that fixed nothing. It seems that the TWRP installation itself was what killed the EFS partition data.
If I understand correctly, flashing the stock Sprint ROM L900VPUCOH3, should fix the problem, but then I would still have to restore the IMEI, which I can't do without a rooted device. Also, even if it worked, I couldn't backup the EFS partition only, without a rooted device. So my logic is that if I could get a functioning TWRP EFS only backup for my device, I could restore that, reset the IMEI and be back in the ballgame.
Before I started down this path my phone was lagging badly and freezing up. I did a soft reset and got the speed back, but then the apps began crashing randomly and intermittently, both the native ones and the downloaded ones. I then did a factory reset and everything worked right. I reinstalled my downloaded apps and kept my speed and stability. It took several days for me to download, configure and add all my accounts back manually and everything remained fast and stable. I would really hate to have to start from scratch all over again.
Any assistance would be appreciated. Below is what I looked like before I got maimed:
Software Version
L900VPUCOH3
Hardware Version
L900.09
Model number
SPH-L900
Android version
4.4.2
Baseband version
L900VPUCOH3
Kernel version
3.0.31-3084104
[email protected] #1
Mon Aug 24 17:13:18 KST 2015
Build number
KOT49H.L900VPUCOH3
SE for Android status
Enforcing
SEPF_SPH-L900_4.4.2_0033
Mon Aug 24 17:29:53 KST 2015
This is what I look like now:
Software Version
Unknown
Hardware Version
(blank)
Model number
SPH-L900
Android version
4.4.2
Baseband version
Unknown
Kernel version
3.0.31-3084104
[email protected] #1
Mon Aug 24 17:13:18 KST 2015
Build number
KOT49H.L900VPUCOH3
SE for Android status
Enforcing
SEPF_SPH-L900_4.4.2_0033
Mon Aug 24 17:29:53 KST 2015
If there is another approach that would rectify the situation then I am all ears. I can fix a computer, but phones are an entirely foreign animal to me. I'll be the first to tell you I don't know enough and welcome the learning experience, I just wish it it wasn't under life or death circumstances.
**UPDATE**
While still investigating possible solutions, something has come to my attention. I do not have the original IMEI info anywhere!! I have the MEID only. I was able to get the serial number from a Samsung registration email, and was able to use a converter to calculate the ESN from the MEID. I tried tap dancing with Sprint to get the IMEI, but all I could get from them was the MEID info I already had.
First of all, please keep away from TWRP since it causes many problems on the N2 from installation to flashing roms.
I suggest you to :
1- Flash with Odin a FULL restore image of stock rom (to restore partitions table, modem, and rebuild your IMEI).
2- Flash with Odin "Philz custom recovery", especially this version.
3- Flash SuperSU flashable Zip with Philz recovery.
Normally, everything should be fine (a working phone with root privilege).
Clarification of Stock ROM Version
zlazaar said:
First of all, please keep away from TWRP since it causes many problems on the N2 from installation to flashing roms.
I suggest you to :
1- Flash with Odin (...too new to even quote an outside url) a FULL restore image of stock rom (oh well...) (to restore partitions table, modem, and rebuild your IMEI).
2- Flash with Odin "Philz custom recovery", especially (...ditto) this version (ditto...).
3- Flash (...ditto) SuperSU flashable Zip (ditto...) with Philz recovery.
Normally, everything should be fine (a working phone with root privilege).
Click to expand...
Click to collapse
The stock ROM you linked to SPH-L900_NE2 causes me a bit of concern as my phone is on L900VPUCOH3. I was already up to 4.4.2 KitKat.
Unless there is some specific reason I should use the NE2 version, I am going to locate an OH3 version and work with that.
Thank you for your help, that was pretty much the route I thought made logical sense with the lack of a patch to my issue, to go back to stock and start over. I wasn't aware of any TWRP issues, so that was also a big help and I already have SuperSU.
While I wait for a response I am going to go and try to do my due diligence to find out more about Philz Recovery, so that I can move on and get back in the game. No phone for New Years Eve will suck a big fat one!!
zlazaar said:
First of all, please keep away from TWRP since it causes many problems on the N2 from installation to flashing roms.
I suggest you to :
1- Flash with Odin ... a FULL restore image of stock rom ... (to restore partitions table, modem, and rebuild your IMEI).
2- Flash with Odin "Philz custom recovery", especially ... this version[/URL].
3- Flash ... SuperSU flashable Zip ... with Philz recovery.
Normally, everything should be fine (a working phone with root privilege).
Click to expand...
Click to collapse
(This response took such a long time because between the holidays, typing the original reply which was lost due to a badly placed refresh touch-button on this keyboard and subsequent issues with the phone, I'm just getting back to it now. This one is much less detailed than the original that was lost.)
As per my previous reply regarding flashing NE2 instead of OH3, I couldn't find a source for the OH3 stock ROM that I was comfortable with, so I just went with your instructions and viola!, all was working again, with IMEI, MEID and everything else back to functioning. I had connection to the carrier network, and after 2 OTA updates, I was back to the OH3 version.
The installation of Philz Recovery and Chainfire's SuperSU went fine. So as far as my original issue, my phone was back to normal, with custom recovery and root added.
Thank you zlazaar for your assistance. Seeing that you were the only one that responded, you truly were a lifesaver for both me and my phone, and though I may have eventually gotten to the process you described by hit, miss or frustration, you save me a lot of time and angst since at that point my biggest concern was a working phone, not the root.
From there it went downhill because I ran into different issues, the only part that relates to this thread is this, should I have used the working TWRP to wipe the ROM before flashing the new stock NE2 ROM to the phone with ODIN? I flashed OVER what was there which might have caused the problems I had later on down the road.
I will post the problems I had after this in another thread when I have a chance and put a link to it here. That way I won't have to retype from the beginning, and anyone this might help can see other issues they may encounter.
On the up side, I think I'm pretty practiced in rooting the SPH-L900 and rooting it. Also, since Sprint couldn't fix or replace my Note 2 after I was done with it, I'm getting a Note 4 as a replacement. (I managed to brick it leaving a KIES error message as the only thing it would do besides Download Mode at power up or starting to recovery.) Worst case, if I brick the new Note 4
On the down side, now I'm going to have a phone I'm going to have to start from scratch learning what can and can't be done to it, as well as deal with the stronger KNOX...and now I have all these Note 2 ROMS (Funny enough, the tech at Sprint said he wanted to try more but they are so restricted on the internet he couldn't download the files he wanted. I said to myself, betcha I have the files he was looking for!!)
Hello, I am currently on PureNexus Rom with twrp 3.0.2RC1 on the pixel xl. I would like to flash back to completely stock because I am having some issues. I found a step by step tutorial but am apprehensive because some steps confuse me. I already got into trouble once when trying to flash PN rom. I don't want to do anything stupid like use a wrong file or anything like that. Is there anyone that could assist me if I run into issues. Also, I have just created a backup but if I flash to stock and run into trouble, I wouldn't be able to restore my backup, would i?? I would think flashing stock removes twrp Which I would need to restore a backup and think i would have a vendor image issue, right?
Any input is greatly appreciated.
What issues do you have?
Maybe no need to flash stock.
I myself flash back to stock every 6 month just to clean things up even it is not necessary.
I pm you my infos
Stock
Dl titanium backup all your apps
Backup that folder to pc
Backup everything else you need back to pc
You need latest Google drivers for flashing stock.
Check out unified Android toolkit helps me get back to stock very easily
mikaole said:
What issues do you have?
Maybe no need to flash stock.
I myself flash back to stock every 6 month just to clean things up even it is not necessary.
I pm you my infos
Stock
Dl titanium backup all your apps
Backup that folder to pc
Backup everything else you need back to pc
You need latest Google drivers for flashing stock.
Click to expand...
Click to collapse
Thanks for the replies. I was having a issue with battery drain. My text messages, if not looked at, would repeatedly wake up the screen every minute. In the course of about 5 hours, Android operating system would chew through 38% battery. I did a factory reset and reinstalled PN and the issue appears to be corrected. Don't know what was causing it, tried to isolate the issue but could not find. So, for now, i will stay on this rom as long as the issue doesn't reappear. I think somehow ambient display was messed up even though it was off.
Sent from my Pixel XL using Tapatalk
Ok if the issue comes back maybe you can try a different rom.