Related
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
Hello Community,
so this is not the first time that I am rooting / flashing a Galaxy GT-I**** Device. But this problem is someting bigger in my opinion because nothing helped.
Ok and now the Story:
The Galaxy S3 was on Android 4.1.2 (Germany Vodafone). I rooted the Device to flash Cyanogenmod. There was no problem.
But my brother doesn't want CM, so I decided to flash the newest Stock Rom (4.3 - Germany Vodafone). But then there was the bootloop. I have tried as many things as I can remind and find here at XDA.
First to flash the stock kernel and then flashing the stock rom
Then flash a recovery to format Data / System / Cache
After every flash i made a factory reset and format cache
Do u have an idea to solve that problem ?
Try 4.1.2 stock Rom post result need to wipe data n cache
Sent from my LT26i using Tapatalk
The problem is: if i want to flash 4.1.2, then odin has a problem with the sboot.bin
I have to reset the bootloader in order to flash a rom lower than 4.3 (read in XDA)
I tried a lot. 4.3 Stock, 4.1.2 Stock (sboot.bin failure), 4.3 pre-rooted rom .. nothing helped
Note: if the device is booting up, then there is the bootsound (startsound) with the samsung sound and samsung logo. But the sound is ending too quick, so the sound isn't playing to the end of it.
In recovery format system sdcard data and cache boot to download mode and flash stock rom .
If it fails try a CWM flashable stock based rom .
JJEgan said:
In recovery format system sdcard data and cache boot to download mode and flash stock rom .
If it fails try a CWM flashable stock based rom .
Click to expand...
Click to collapse
I will try it. Is there a chance to get the data on sdcard with adb? Because the usb-debugging is off because i flashed a new rom.
Gesendet von meinem Nexus 5 mit Tapatalk
Ok. I made a bootloader downgrade to flash an older firmware. This time I use a 3 parts firmware without branding and a PIT file to reset the galaxy phone completely
Edit:
Ok now the device is running. The only way to get out of the bootloop was: using a pit file.
Gesendet von meinem Nexus 5 mit Tapatalk
while installing cm 12/custom ROM using twrp i wiped Data, Cache, Dalvik Cache and mistakenly wiped sdcard also in wipe system. so while installing cm12/rom i cant find any files . the problem is i reboot it to system and cant enter into recovery mode and phone is dead.what could be the solution for this (need help)?
Flash it again, With flashtool, Datacable and Computer. And reinstall twrp.
Gesendet von meinem LT22i mit Tapatalk
TWRP Img
Hey. Srr for off-topic, but as you said, do you have TWRP image/kernel for LT22i? please send it, I'm in a situation like you, but I have no TWRP image to flash.
starbird.64 said:
Hey. Srr for off-topic, but as you said, do you have TWRP image/kernel for LT22i? please send it, I'm in a situation like you, but I have no TWRP image to flash.
Click to expand...
Click to collapse
Search. For any kernl and recovery and flash them via fastboot
Hello
Im bored by using android 4.2 from many years, i want something new in my device
im tired of finding how to install cyanogen in lenovo A680
i dont know from where i can get working stock ROM of Lenovo A680
and i dont know how can i port rom perfectly
i hope you can help me !
Hi
For install ROM anywere(cyanogen/MIU/Stock):
Put the firmware(ROM.zip) archive to SD-card,
Switch off your phone
get into recovery (You need to CWM: forum.xda-developers. com/android/general/rooting-twrp-cwm-lenovo-a680-row-t3036490 ):
- Go to the backup and restore, create a backup of the current state of your machine,
- Wipe Data / Factory Reset -> delete all user data
- Wipe Cache Partition -> Wipe cache
- Advanced -> Wipe Dalvik Cache -> Wipe Dalvik Cache
Next Install zip from sdcard -> choose zip from sdcard -> Select the firmware and install and reboot.
OR: Install Stock Rom and put ROOT for unistall apps system, and install Theme/Xposed Modules.
maxnuk said:
For install ROM anywere(cyanogen/MIU/Stock):
Put the firmware(ROM.zip) archive to SD-card,
Switch off your phone
get into recovery (You need to CWM: forum.xda-developers. com/android/general/rooting-twrp-cwm-lenovo-a680-row-t3036490 ):
- Go to the backup and restore, create a backup of the current state of your machine,
- Wipe Data / Factory Reset -> delete all user data
- Wipe Cache Partition -> Wipe cache
- Advanced -> Wipe Dalvik Cache -> Wipe Dalvik Cache
Next Install zip from sdcard -> choose zip from sdcard -> Select the firmware and install and reboot.
OR: Install Stock Rom and put ROOT for unistall apps system, and install Theme/Xposed Modules.
Click to expand...
Click to collapse
Thanks for those step by step answer.!
sure i will follow your step when i will install ROM
oh well, can you tell me from where i can get Cyanogen for Lenovo A680 ?
Do you test: youtu.be/RyVakGPT11I
but I'm not sure...(Backup!)
maxnuk said:
Do you test: youtu.be/RyVakGPT11I
but I'm not sure...(Backup!)
Click to expand...
Click to collapse
Thanks for your help
but according to comments, it seems fake rom ,full of bugs! better I Should not try
hey can you tell me how can I port rom and make it compatible with my device?
I'm interested into cyanogen ,I already downloaded both cyanogen 12.1 and 13
I want to make it compatible with my device
I'll be thankful to you
Port rom... you have very bugs. But, to port rom: https://wiki.cyanogenmod.org/w/Doc:_porting_intro
Ideally you get a ready-rom, like the settings of your device and change.
maxnuk said:
Port rom... you have very bugs. But, to port rom: https://wiki.cyanogenmod.org/w/Doc:_porting_intro
Click to expand...
Click to collapse
I'm Sorry if I bother you
wow your answer is Really so awesome
im going to read all the contents!
Thanks Really!
Your specs: Chipset:Mediatek MT6582 // GPU: Mali-400MP2 // 4 GB Rom, 1 GB RAM.
Try: http://www.mtkroms.com/2016/02/marshmallow-cyanogenmod-13-for-mt6582.html
maxnuk said:
Your specs: Chipset:Mediatek MT6582 // GPU: Mali-400MP2 // 4 GB Rom, 1 GB RAM.
Try: http://www.mtkroms.com/2016/02/marshmallow-cyanogenmod-13-for-mt6582.html
Click to expand...
Click to collapse
you are the boss!
Really your answer is interesting
soon I'll be downloading it
but I afraid little bit, Because just 2 day ago I tried to flash custom rom and it stuck at booting logo
I was unable to boot into recovery too
then I give it to service center, and then my device working today
XD You need not have gone ... Boot loop, that always happens..
maxnuk said:
XD You need not have gone ... Boot loop, that always happens..
Click to expand...
Click to collapse
Haha Thanks dude...hey do you know how can I flash custom rom in computer? using emulators?
so that I can test whether rom is working Fine or not, so that I can avoid risk on my device
Do you have skype ?
maxnuk said:
Do you have skype ?
Click to expand...
Click to collapse
yes I've
Do you use Smart Phone Flash tool ?
maxnuk said:
Do you use Smart Phone Flash tool ?
Click to expand...
Click to collapse
I know how to use it, but I didn't used,Because last time I tried to flash rom using TWRP
you know What was Good wrong?
I did wipe cache and data, after that, I tried to install custom rom zip, and I found it's corrupted!
so, I ended up with bricking my device
that's why I want to flash rom in computer first!! Haha
when you bricked your phone, you could not get into TWRP ?
maxnuk said:
when you bricked your phone, you could not get into TWRP ?
Click to expand...
Click to collapse
yes right!! and even I was unable to get into recovery mode using key combination
just use that Smart Phone Flash tool..
maxnuk said:
just use that Smart Phone Flash tool..
Click to expand...
Click to collapse
Oh Thanks for that.. sure I'll use it next time...but still I afraid of bricking! do you have any idea how can I flash custom rom in computer emulator? so I can make sure rom is working Fine or not
I do not know. I recommend you not flash rom.
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