hi, i have question about restoring backups with cwm.
i backuped my phone via cwm stock 4.0.4 ics with root, busybox, cwm installed on it.
after that i downgraded my phone with wotanclient to stock 2.3.4 and installed root, busybox and cwm(apk) again (already backuped with cwm)
if i restore the first backup with stock 4.0.4 will i lost root, busybox and cwm? (im asking because i lost these after downgrading via wotanclient to stock 2.3.4 from ics.)
pizzamitsalami said:
hi, i have question about restoring backups with cwm.
i backuped my phone via cwm stock 4.0.4 ics with root, busybox, cwm installed on it.
after that i downgraded my phone with wotanclient to stock 2.3.4 and installed root, busybox and cwm(apk) again (already backuped with cwm)
if i restore the first backup with stock 4.0.4 will i lost root, busybox and cwm? (im asking because i lost these after downgrading via wotanclient to stock 2.3.4 from ics.)
Click to expand...
Click to collapse
No if you restore the backup, where you had root and busybox and cwm, you will have it again. CWM will restore everything
No you won't. Your device will be same as the time you made the backup
mihahn said:
No if you restore the backup, where you had root and busybox and cwm, you will have it again. CWM will restore everything
Click to expand...
Click to collapse
thanks. has the battery to be fully loaded before doing a restore?
pizzamitsalami said:
thanks. has the battery to be fully loaded before doing a restore?
Click to expand...
Click to collapse
No but as a precaution keep it above 40 percent... It will take some time in CWM for restore and first boot can be long
You could plug it in the charger while restoring, normally it should load when you are in cwm
How long takes the first boot after restoring? ive already restored and it seems like bootloop (15 minutes)
Did you wipe data /factory reset
Try restoring after wiping data /factory reset, cache, dalvik cache
PREDATOR95 said:
Did you wipe data /factory reset
Try restoring after wiping data /factory reset, cache, dalvik cache
Click to expand...
Click to collapse
no, i didnt. ill try. thx :laugh:
pizzamitsalami said:
no, i didnt. ill try. thx :laugh:
Click to expand...
Click to collapse
i did, bootloop again. while bootloop its showing the sony ericsson(2.3.4) lettering instead of sony(4.0.4).
pizzamitsalami said:
i did, bootloop again.
Click to expand...
Click to collapse
You have to flash ics first, to restore the cwm backup you took on ics! So flash ics and restore the backup on ics. Only on unlocked bootloader you could flash the ics kernel and restore
//Versuche erst das Upgrade auf ICS zu machen, gibt ja diverse tutorials wie man upgraden muss um root auch auf ics zu haben (z.B. in der gepinnten Rooting-Anleitung). Wenn du dann auf ics bist, installier cwm und versuch den restore nochmal, es muss klappen. Außer wenn es nen Error beim Backup gab :good:
mihahn said:
You have to flash ics first, to restore the cwm backup you took on ics! So flash ics and restore the backup on ics. Only on unlocked bootloader you could flash the ics kernel and restore
//Versuche erst das Upgrade auf ICS zu machen, gibt ja diverse tutorials wie man upgraden muss um root auch auf ics zu haben (z.B. in der gepinnten Rooting-Anleitung). Wenn du dann auf ics bist, installier cwm und versuch den restore nochmal, es muss klappen. Außer wenn es nen Error beim Backup gab :good:
Click to expand...
Click to collapse
achso, wusste ich nicht. ich wollte mir gerade mit dem backup die arbeit sparen mit dem updaten, rooten etc.
werd ich mal ausprobieren. vielen dank
pizzamitsalami said:
achso, wusste ich nicht. ich wollte mir gerade mit dem backup die arbeit sparen mit dem updaten, rooten etc.
werd ich mal ausprobieren. vielen dank
Click to expand...
Click to collapse
Please answer next time in English, no problem if you just write the same in German again, but we must speek English in this forum
//So schreibe ich immer dasselbe auf Deutsch drunter
Related
Hi
I've installed it on my phone AMARULLZ-dada2sd script.
* Works well.:good:
Only wifi my phone will not start.
* I changed the kernel, but wifi does not turn on.
I did wipe cach and wipe dalvike cach
But my issue is not resolved.:crying:
mu Rom : [CM7.2][RC4] REINCARNATION ROM SERIES pre-Final
Please help me :crying:
TiTaN_88 said:
Hi
I've installed it on my phone AMARULLZ-dada2sd script.
* Works well.:good:
Only wifi my phone will not start.
* I changed the kernel, but wifi does not turn on.
I did wipe cach and wipe dalvike cach
But my issue is not resolved.:crying:
mu Rom : [CM7.2][RC4] REINCARNATION ROM SERIES pre-Final
Please help me :crying:
Click to expand...
Click to collapse
Your wifi was working before flashing that script ??
If yes then the problem is their in script
So flash stock ROM via Odin .
Hitesh2626 said:
Your wifi was working before flashing that script ??
If yes then the problem is their in script
So flash stock ROM via Odin .
Click to expand...
Click to collapse
Both before and after installation scripts worked well.
But after a few days the wifi does not work anymore.
Remove /data/misc/wifi/ , reboot and enter you WIFI password again.
Gesendet von meinem GT-S5830i mit Tapatalk 2
Android-fany said:
Remove /data/misc/wifi/ , reboot and enter you WIFI password again.
Gesendet von meinem GT-S5830i mit Tapatalk 2
Click to expand...
Click to collapse
Not work
Hi Guys,
I have installed CM11 with clockworkmod but i must flash it. And now hi stucks in the loading screen of CM. Do you know how to fix it?
.
Full wipe and dalvik and cash
and Try Clean Flashing,
Nederlander13 je moet full wipen want de vorige files kunnen conflicteren met de cm11 files waardoor het niet kan opstarten dus je moet zoals hij zegt hierboven doen dus system dalvik cache en data factory reset.
Succes verder he
Nederlander13 you need to perform a full wipe cause the previous files could conflict with the files from cm11 what causes that it cant boot. So you need to do the same like mrhow says so wipe system, dalvik cache and wipe data factory reset.
Goodluck further
Sent from my Nexus 4 using Tapatalk
Any way of flashing the rom without having to factory reset the phone.
Mewz said:
Any way of flashing the rom without having to factory reset the phone.
Click to expand...
Click to collapse
Download the android 7 ROM from here https://mega.nz/#!0wY0QTxA!h1SkLNBby...B3IjC6Po-gfEeo
Then flash using SP flash tools and make sure you uncheck userdata. This will flash the new ROM and keep your data
Hat es schon jemand geschafft das Rom zu rooten?
So my bootloader is unlocked and i wanna flash twrp but i have seen threads here that miui is encrypted by default and i need to format data in twrp in order to boot after i flash twrp. So, guide me what should i do as i dont wanna lose my apps and data after flashing twrp
Another question if i flash the older version of miui rom using mi flash tool, will it lock my bootloader back or not?
Hi,
You can easily backup your data & apps with this Miui feature:
Go settings-> additionnal settings-> Backup & reset
I don't think Miui is encrypted by default. Normally you can flash twrp without any lost..
tatouss said:
Hi,
You can easily backup your data & apps with this Miui feature:
Go settings-> additionnal settings-> Backup & reset
I don't think Miui is encrypted by default. Normally you can flash twrp without any lost..
Click to expand...
Click to collapse
Yes i can backup but i won't get the data of apps like game score etc with that backup, i guess
Btw is twrp 3.1.0 working fine with miui 8.2.4 ?
Yes it does. Just install TWRP, Boot into recovery (TWRP) and install LazyFlasher. Now you can boot to system. Voila!
Gesendet von meinem Redmi Note 4 mit Tapatalk
cy_coe said:
Yes it does. Just install TWRP, Boot into recovery (TWRP) and install LazyFlasher. Now you can boot to system. Voila!
Gesendet von meinem Redmi Note 4 mit Tapatalk
Click to expand...
Click to collapse
Already did it. Thanks
Btw i was not able to make a nandriod backup using twrp. It was showing some error at last and thus it failed
aaqib67 said:
Already did it. Thanks
Btw i was not able to make a nandriod backup using twrp. It was showing some error at last and thus it failed
Click to expand...
Click to collapse
Yep, it is a bug with TWRP.
You can't make an nandroid backup with the current twrp, just take efs backup, you're safe.
I made a backup with default settings (system, data and boot) without problems.
Before you make a backup switch off security pattern just in case...
Gesendet von meinem Redmi Note 4 mit Tapatalk
cy_coe said:
I made a backup with default settings (system, data and boot) without problems.
Before you make a backup switch off security pattern just in case...
Gesendet von meinem Redmi Note 4 mit Tapatalk
Click to expand...
Click to collapse
But you din't check all the options in backup like modem etc
and if by chance you phone will have problem u won't be able to restore it using your backup i think
sachin n said:
Yep, it is a bug with TWRP.
You can't make an nandroid backup with the current twrp, just take efs backup, you're safe.
Click to expand...
Click to collapse
I am not sure how efs backup works. I backed up my apps using titaium backup and in case my device won't bootup i will just flash fastboot rom and restore apps via titanium itself until the bug in twrp is fixed!
Thanks
aaqib67 said:
I am not sure how efs backup works. I backed up my apps using titaium backup and in case my device won't bootup i will just flash fastboot rom and restore apps via titanium itself until the bug in twrp is fixed!
Thanks
Click to expand...
Click to collapse
:good:
Check everything but bootloader. Should work.
Gesendet von meinem Redmi Note 4 mit Tapatalk
What xiomi mean by chinese sh!t language which translates to "DEVICE DOES NOT EXISTS"
You might get a proper answer if you ask reasonably.
Gesendet von meinem Redmi Note 4 mit Tapatalk
can you guys help me with the pin lock issue? Phone got messed up due to the new update as i forgot to disable the automatic update on restart option on developer settings. The phone ended up with bootloop , so had to restore from old twrp backup and re-update. However, the pin lock (fingerprint, screenlock) doesnt seem to work anymore. Neither Factory reset nor deleting the locksettings.db solve that pin lock problem. The old backup was encrypted. However after restoring the encryption was gone. That's when the screen lock issue appeared. Is there anyway to fix it without flashing stock rom? Or how do I encrypt the phone again?
What happens when you try to set a pincode?
Have you tried booting into recovery and using the recovery option to wipe and format all data?
Well I tried that but it didn't work. What I did was simply restored the old backup from twrp which was encrypted. However for reason the encryption was lost when formatting and reflashing through twrp. Phone works just fine , the only thing that broke was the lockscreen pin setup. New pin/pattern/password doesn't seem to get set. Now it's like a house without a lock
I had a similar problem. For me the persist partition broke when restoring the TWRP backup. As a result, I couldn't enter a fingerprint. Maybe the problem is similar with you.
I then flashed the "persist.img" separately.
I took it from the TWRP backup and changed the ending from ".emmc.win" to ".img" and then flashed the whole thing via fastboot. Command is "Fastboot flash persist * .img"
Credits to HofaTheRipper
--------------------------------------------------------------------
Ich hatte ein ähnliches Problem. Bei mir ist die persist partition beim wiederherstellen des TWRP Backups kaputt gegangen. Dadruch konnte ich keinen Fingerabdruck eingeben. Vieleicht ist bei dir das Problem ähnlich.
Ich habe dann die "persist.img" separat geflasht.
Ich habe sie aus dem TWRP Backup entnommen und die Endung geändert von ".emmc.win" in ".img" und das ganze dann per fastboot geflasht. Befehl ist "Fastboot flash persist *.img"
Credits to HofaTheRipper
I've had a similar issue with the pin code as well, it seems to be a completely seperate thing to the persist image.
From my understanding the persist partition contains sensor calibration data, which is unique to each and every device, and your camera and fingerprint require that partition to be completely stock and unaltered to work (so if you flash someone else's persist partition or completely wipe the partition, you will need to reflash it using your own device's unique data to get those features working again)
That doesn't appear to be what caused the Pincode issue in my case. (and probably not what caused OP's issue either I'm guessing)
I ran a pseudo-scientific experiment; I reformatted my device using recovery's reformat option; completely wiping all data from the phone. Setting a pincode from this completely stock state worked fine. I then used TWRP to flash in my Data partition only, from a TWRP backup that WAS NOT encrypted; The result was an immediately failure to set a pincode. The symptom was when you try to set a pincode, it never actually gets set; The phone asks you to enter the pincode, then enter it again to verify, and then simply seems to pretend nothing happened and no pincode is applied no matter how often you repeat the process.
So in my case, it was definitely an issue with restoring the DATA partition.
I then ran another experiment flashing in the same DATA partition using fastboot flash commands, and the same thing occurred.
Then finally, I repeated both flashing methods, using a DATA partition from a backup where hte DATA was encrypted (ie had a pincode set), and those resulted in a bootloop, where the phone refused to boot with an encrypted data partition.
I never ended up finding a fix to the phone being unable to set a pincode, so instead I reformatted all data, and set up the phone from scratch again.
Whilst my phone still had it's original data, but no pincode could be set, I simply backed up all photos and notes and other things i knew would be lost, then went ahead and did a final, permanant reformat to stock. Then proceeded to set up the phone from scratch again, reinstalling all apps and configuring all data again; As the phone was reset to scratch, the pincode was working again.
7tyjupiter said:
Zombnombs said:
I've had a similar issue with the pin code as well, it seems to be a completely seperate thing to the persist image.
From my understanding the persist partition contains sensor calibration data, which is unique to each and every device, and your camera and fingerprint require that partition to be completely stock and unaltered to work (so if you flash someone else's persist partition or completely wipe the partition, you will need to reflash it using your own device's unique data to get those features working again)
That doesn't appear to be what caused the Pincode issue in my case. (and probably not what caused OP's issue either I'm guessing)
I ran a pseudo-scientific experiment; I reformatted my device using recovery's reformat option; completely wiping all data from the phone. Setting a pincode from this completely stock state worked fine. I then used TWRP to flash in my Data partition only, from a TWRP backup that WAS NOT encrypted; The result was an immediately failure to set a pincode. The symptom was when you try to set a pincode, it never actually gets set; The phone asks you to enter the pincode, then enter it again to verify, and then simply seems to pretend nothing happened and no pincode is applied no matter how often you repeat the process.
So in my case, it was definitely an issue with restoring the DATA partition.
I then ran another experiment flashing in the same DATA partition using fastboot flash commands, and the same thing occurred.
Then finally, I repeated both flashing methods, using a DATA partition from a backup where hte DATA was encrypted (ie had a pincode set), and those resulted in a bootloop, where the phone refused to boot with an encrypted data partition.
I never ended up finding a fix to the phone being unable to set a pincode, so instead I reformatted all data, and set up the phone from scratch again.
Whilst my phone still had it's original data, but no pincode could be set, I simply backed up all photos and notes and other things i knew would be lost, then went ahead and did a final, permanant reformat to stock. Then proceeded to set up the phone from scratch again, reinstalling all apps and configuring all data again; As the phone was reset to scratch, the pincode was working again.
Click to expand...
Click to collapse
7tyjupiter said:
I had a similar problem. For me the persist partition broke when restoring the TWRP backup. As a result, I couldn't enter a fingerprint. Maybe the problem is similar with you.
I then flashed the "persist.img" separately.
I took it from the TWRP backup and changed the ending from ".emmc.win" to ".img" and then flashed the whole thing via fastboot. Command is "Fastboot flash persist * .img"
Credits to HofaTheRipper
--------------------------------------------------------------------
Ich hatte ein ähnliches Problem. Bei mir ist die persist partition beim wiederherstellen des TWRP Backups kaputt gegangen. Dadruch konnte ich keinen Fingerabdruck eingeben. Vieleicht ist bei dir das Problem ähnlich.
Ich habe dann die "persist.img" separat geflasht.
Ich habe sie aus dem TWRP Backup entnommen und die Endung geändert von ".emmc.win" in ".img" und das ganze dann per fastboot geflasht. Befehl ist "Fastboot flash persist *.img"
Credits to HofaTheRipper
Click to expand...
Click to collapse
Cheers mate, it works . Thanks you're a lifesaver!!!!
Click to expand...
Click to collapse