Related
hi all,
Sorry I have to return my handset as its faulty I think, it crackles from the speaker all the time on the handset only, presume this is not a normal fault, i havent found it anyway .so i need a replacement.
I installed nandroid and rooted the phone when I got it, but have forgotten it all lol, I did take a backup of the original os, and i kept it on the standard sd card (2gb) .
I then took that out and did the update with a new card, kept the old one separate. So I am thinking to return to the orange rom, I would put the old card back in (sd) and then just use nandroid to reflash the rom, but then how do i remove the nandroid rooting??
also i have used backup for root users to backup everything, and will re root the new phone hopefully this will restore everything or more things, I am using modaco 2.2
thanks
another thought would chooosing the option
wipe data/factory reset restore the phone to how it came? or restore to fresh install 2.2?
also would backing up the current install using the option nandroid 2.2backup also backup all the data/apps and stuff?
thx
jason4656 said:
hi all,
Sorry I have to return my handset as its faulty I think, it crackles from the speaker all the time on the handset only, presume this is not a normal fault, i havent found it anyway .so i need a replacement.
I installed nandroid and rooted the phone when I got it, but have forgotten it all lol, I did take a backup of the original os, and i kept it on the standard sd card (2gb) .
I then took that out and did the update with a new card, kept the old one separate. So I am thinking to return to the orange rom, I would put the old card back in (sd) and then just use nandroid to reflash the rom, but then how do i remove the nandroid rooting??
also i have used backup for root users to backup everything, and will re root the new phone hopefully this will restore everything or more things, I am using modaco 2.2
thanks
Click to expand...
Click to collapse
there is a way to unroot your phone, but because you are stuck with the modified recovery img you installed you wont have a standard orange hero
my suggestion is to flash a rom with
stock recovery
stock radio
stock rom
I would suggest try using the updates HTC.com has provided for us, that should return you back to stock firmware!
"Make sure you flash correct update, I am not responsible for any bricks or damages to your phone!"
how do you mean since i am stuck with modded rom? I said I backed up my orange rom before i used the update feature of the nandroid root, so my question is about 1 restoring it, and then 2 removing the root feature?
thanks for ur advice
ok i have managed to restore to factory orange rom so never mind that, how do i remove the ability to boot to the nandroid backup/loader feature?
to "unroot" and get back to Orange stock you will need to do a full flash, use the HTC Orange Update as its Orange verified, a normall restore wont remove the Custom recovery image you have installed
ok how do i do that? thx
dont worry, have done it, but thanks
glad to hear it
job done
all sorted
thread closed
Hi All,
I am a new member to the xda developers forum. also, i am a noobie for android os and using an android phone myself. before i describe the problem i am facing, i will describe on my phone description. i am using stock rom (not rooted) and currently using SIS set (original set) in Malaysia. SIS is the sole distributor of HTC phones in Malaysia - original set. btw, my phone is not used more than a year. also, i checked the xda developers forums for my problem and didnt find any answers to my problems, so i posted a new one here.
yesterday, i have a very very very serious problem with my phone.my htc desire crashed and rebooted automatically due to overheating problems. so, i left my phone off to cool down my phone for 1 hour. when i switch on my phone from there (my phone is already cooled down by then), my htc desire got stuck on the htc logo for long time - about 5-10 minutes) and does not go to android at all. i tried removing the battery and inserting it again but still stuck at the htc logo. additional note, i can go to the bootloader by pressing the volume down and the power button though. from there, i think its the software problem and not the hardware problem since i still can switch on my phone...i have tried removing the sim card and microsd card and booted it again but to no avail
i have not done the clear storage option in the bootloader screen since i want to recover my data - contacts, calendar, sms messages before i can factory reset my phone.
so my question is as follows:
1. how can i backup / recover my phone data (contacts, calendar, sms messages) without voiding my warranty with SIS - (rooting phone void warranty immediately)? i am desperate to get my data from my phone as it is precious to me...
2. if i go to the bootloader, can i recover my data from there? i see the recovery menu in the bootloader, can i use that to recover my data?
First, make a copy of the memory card to your pc. This will at least keep some fotos. Then re-install the card back to the phone.
Then you can go into recovery, and "should" be able to restore your phone. You can also do a backup from the recovery section (although I'd think you'd just be backing up an already corrupted system).
Can't say much about anything stored on the phones memory though, such as contacts, user data, etc.
It's always desireable to sync you phone to your pc on a regular basis.
Also, there is a program called titanium backup, which backs things up to the sd card.
There are reports however, of people placing their phones (minus battery) in the freezer in a plastic baggie for 10 min. And it allowed them to get past the frozen htc screen. Not advisable in my book though. (last ditch effort)
And rooting a phone, Will void the warranty.
for those putting phones in freezer, those are for heating issues, but mine is not the heating issue anymore...
Titanium backup needs root so that won't work. Don't think there is a way to back up data when unrooted. But keep in mind contracts and calendar are backed up with your gmail account (if you have set it up).
Sent from my HTC Desire using XDA Premium App
I would pull the SD card and copy contents to PC via card reader, then try restoring via the recovery option in the bootloader.
If that doesn't work, you could factory reset via bootloader (this will wipe everything):
1. Power off your phone (or take out the battery, if it is non-responsive)
2. Holding the [Volume -] key, press the power button once. Hold it until you see three skateboarding Androids at the bottom of the screen
3. Use the Volume buttons to navigate.
4. Select "Bootloader"
5. Select "Clear Storage"
6. Follow the on-screen instructions if you want to factory reset
and try to boot the phone normally. If that doesn't work I would return the handset for warranty repair - should be fine as you have not rooted etc. yet.
I think that's good, but would someone more experienced confirm the steps?!
what does recovery mode exactly do in htc desire?
Beyonder2000 said:
what does recovery mode exactly do in htc desire?
Click to expand...
Click to collapse
For the stock recovery I'm not sure to be honest as I never had cause to use it! I think it only lets you apply official rom updates.
Usually, recovery will run the update.zip, which is normally on the root of the SD card. This should be the last ROM from the manufacturer.
Running this in recovery, will usually install pretty much to the last good ROM that was installed.
Wether or not it will delete your user data, well, ify-ify. But, it's usually the first thing to do on a stock system, and generally works.
Considering you are not rooted, and probably do not have a "gold Card" (usually required on half of the Desires), your options are limited at this time.
You should take a look at your SD card, and see what files are on the root of the card.
Beyonder2000 said:
for those putting phones in freezer, those are for heating issues, but mine is not the heating issue anymore...
Click to expand...
Click to collapse
As I said, a last ditch effort. And I personally, would not try it.
00droid said:
For the stock recovery I'm not sure to be honest as I never had cause to use it! I think it only lets you apply official rom updates.
Click to expand...
Click to collapse
can i flash a rom, and keep my data intact at the same time?
If it's a signed and factory update, it "should" keep your data.
No promises.
But, you can either fix your phone (which has probably lost most of your data anyhow), or, wait for a miracle.
Unfortunately, phones are like PC's, it you never back up your important data, eventually, it bites you when you least expect it.
But surely, you have an old phone, that has most of the contacts. You can copy them to sim (if you have a gsm ph), then transfer them after you get your android going again.
how to repair
Moscow Desire said:
If it's a signed and factory update, it "should" keep your data.
No promises.
But, you can either fix your phone (which has probably lost most of your data anyhow), or, wait for a miracle.
Unfortunately, phones are like PC's, it you never back up your important data, eventually, it bites you when you least expect it.
But surely, you have an old phone, that has most of the contacts. You can copy them to sim (if you have a gsm ph), then transfer them after you get your android going again.
Click to expand...
Click to collapse
how do i go about fixing the issue?
is it getting the rom (RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe - is this fr malaysia sis version?) ,putting it on my sd card and doing recovery based on this os?
and yes, i regretted doing the backup recently...
That's the correct stock version, but, am not sure about the ".exe". I distinctly remember a .zip extension.
Gimmie a few min.
What you actually need, is the 2.2 ota froyo update.
Unfortunately, having a hard time finding it!!!! (link)
I have one on my system, but rather large to e-mail.
You can google, and find. But the instructions will tell you to rename the zip file, to "update.zip" (not update.zip.zip)
What you have, is the whole thing.
http://darrenrichie.blogspot.com/2010/08/how-toflash-your-desire-to-22.html
But am not sure if you can use this, as your's stuck at the htc screen and not sure if htc sync will detect your phone.
If you pm me with your e-mail, I'll send you the update file (28mb), it may, or may not work. Basically, you'll copy it to the sd root, boot into recovery, and recover the zip.
I received a replacement galaxy nexus today from Amazon. I made a nandroid backup using CWM recovery on the old Galaxy Nexus phone. Pulled the sim card from the new phone, put it in the new phone to confirm it worked. I then tried to connect my old phone to the PC to copy over the nandroid, but now the computer will not mount the phone and i am unable to see anything on the phone. I tried putting a new sim card in the phone but the computer still does not see the phone. I have the galaxy nexus toolkit kit installed but it does not show it attached currently.
All i'm trying to do is copy the nandroid backup i created on the old phone to the new phone. Any help you can provide would be greatly appreciated.
Thanks
Chris
TurbineTester said:
I received a replacement galaxy nexus today from Amazon. I made a nandroid backup using CWM recovery on the old Galaxy Nexus phone. Pulled the sim card from the new phone, put it in the new phone to confirm it worked. I then tried to connect my old phone to the PC to copy over the nandroid, but now the computer will not mount the phone and i am unable to see anything on the phone. I tried putting a new sim card in the phone but the computer still does not see the phone. I have the galaxy nexus toolkit kit installed but it does not show it attached currently.
All i'm trying to do is copy the nandroid backup i created on the old phone to the new phone. Any help you can provide would be greatly appreciated.
Thanks
Chris
Click to expand...
Click to collapse
Most likely you need to disable "USB fast charge" and the comp will recognize your phone again. As far as the restore, why not use TiBu?
Thank you so much, disabling fast charge did the trick.
I must confess that even though i have the Pro TiBu, I don't really understand all of what it can do. I was under the impression that it simply backed up the apps and system data. Does it also back up music etc similar to a CWM nandroid backup?
TurbineTester said:
Thank you so much, disabling fast charge did the trick.
I must confess that even though i have the Pro TiBu, I don't really understand all of what it can do. I was under the impression that it simply backed up the apps and system data. Does it also back up music etc similar to a CWM nandroid backup?
Click to expand...
Click to collapse
You can use your nandroid.
I used to pop old nandroids from my DX onto it's refurbished brothers without problem.
Does the replacement phone have to be unlocked and rooted prior to installing the old phone's nandroid or will the nandroid carry over the unlock and root status? Thanks!
The new phone needs to be unlocked with a custom recovery if you want to restore the nandroid. Root will come with the nandroid.
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:
I have recently acquired a Telus/Koodo GSM HTC One V and successfully installed Shpongle. I noticed there were problems when connecting the phone to my computer, it appears as two removable devices and a CD drive. I never did try connecting the phone to a computer in its stock condition, I assumed transferring files to the phone would not be an issue. Anyway, I decided to restore the backup I created of the stock ROM installation to see if there is a greater hardware issue with the phone. The result of the backup is a phone that hangs on the splash screen.
What I have done to the phone up to this point.
Unlock the bootloader
Root
Flash Recovery - TWRP v2.3.3.0
Backup Stock ROM with TWRP
Install custom ROM (shpongle_primou-20130521) and Kernel (boot-HELLBOY-20130514 )
Install GAPPS
Noticed problem with when trying to copy files to the phone.
Restore backup of stock ROM - failed
I can still get to the bootloader and the recovery.
If the connectivity issues can be resolved with a simple fix then I do not mind going back to the custom ROM. If there is no fix or it is too late to implement, I would very much like to get the phone back to the stock condition and test the connectivity issues. What are the appropriate next steps to remedy this situation?
You need a kernel change. Titanium kiss might work. There is also a stock kernel linked in one of these threads somewhere. Not sure, but I may have downloaded it
Thanks mrcorey for the insight on the kernel incompatibility.
I downloaded the RUU and found instructions to extract and flash the ROM and kernel to the phone. After upgrading it by running the RUU completely, I had a working phone again. Everything is back to stock as far as I can tell and USB connectivity is as it should be. Once connected to a PC and selecting the disk drive option on the stock HTC ROM both the internal memory and the microSD card are available in windows explorer. Why is the internal memory and card not accessible in windows when I had Sphongle installed on the phone? Is there a option that was not set right to get things to work properly?