Related
Hello guyzz,
Yesterday i accidentally factory reset my phone...and also i dont have a latest backup...but my previous old backup was there with me...but when i triwd to restore from that backup using recovery it says
checking md5 sums
Md5 mismatch
then after trying a lot it says
Restoring boot
Restoring system
But restoring data failed...
Then i rebooted phone and i got a little heart attack:crying::crying:
THE TOUCH WAS NOT WORKING AND PHONE GOT STUCKS AT LOCK SCREEN
SO is there anyway to restore data from backup ysing windows or recovery...always md5 match fails...plzzz help me....
My data was very important so i need to restore it at any cost...
happened to me if i tried to install any other rom that wasn't 4.3...so i was able to adb a 4.3 rom and was good to go...
slick5657 said:
happened to me if i tried to install any other rom that wasn't 4.3...so i was able to adb a 4.3 rom and was good to go...
Click to expand...
Click to collapse
Thnxx bro...can u plz tell me how to adb 4.3 rom...?
Locking as you have a thread already for this. Moving to QA.
Sorry for this being lengthy, I wanted to make sure I gave enough info.
Neither of the two most popular recovery tools are working for me. They both state the backups are successful but the restores have flaws. Is anyone experiencing the problems I am? If so, does anyone know what to do about them?
CWM Recovery Touch (and non-touch): Data restores leave certain things not working. I'm not sure what processes are stopping because it flashes and disappears to fast. I know that it causes the ROM Manager for CWM, Titanium Backup Pro, Google Play, and likely more to crash (disappear) immediately upon opening. Chrome browser *might* bright up the keyboard on the first click but it won't work then it will disappear and not come back (but the keyboard does work in other areas, I use Swype Keyboard). I've tried clearing cache and/or data on all 3, uninstalling them then re-installing via APK and various other things. This occurs regardless of whether a factory reset (data/cache) wipe is performed before the restore. However, if I restore with CWM Recovery *then* do a factory reset, Google Play will work and nothing crashes, nor are their long delays.
TWRP does not boot after a restore. It will pass the initial screen showing the phone model, the phone carrier splash screen, then sit on Samsung with the LED solid bright blue and hang.
My goal is to simply trust my backups. The CWM Recovery problem is workable in a terrible situation since my Titanium backups will get my phone *almost* to where it was (barring widgets, which are pain to re-setup, and a few other things).
Titanium Backup Pro question: Is it normal when you remove a system app with Titanium Backup Pro, then do a restore in CWM for that app to still be gone? Since I use the Swype keyboard I removed the other once, did a restore with CWM, had the problem so I did a factory reset and my stock keyboard was missing still (I think it's a Samsung keyboard)
App Details:
CWM Recovery Touch 6.0.4.7 (for Samsung Galaxy S3 LTE (GT-I9305))
TWRP 2.6.3.0 (for Samsung Galaxy S3 LTE (International i9305))
Phone Details:
Carrier: T-Mobile (Germany)
Model number: GT-I9305
Android Version: 4.3 (stock from Kies, so I do have Knox and it's disabled via SuperSU 1.91 from chainfire)
Baseband version: I9305XXUEMK1
Kernel version: 3.0.31-2051278
Build number: JSS15J.I9305XXUEML5
Titanium Backup Pro question: Is it normal when you remove a system app with Titanium Backup Pro, then do a restore in CWM for that app to still be gone?
No a Nandroid backup wipes the phone .
make a Nandroid then in recovery format system sdcard data cache .
You now have an empty phone and restoring the Nandroid should return exact same state .
All this reads as you are doing something wrong .
JJEgan said:
All this reads as you are doing something wrong .
Click to expand...
Click to collapse
I hope it is as simple as that. I'm booting up in recovery mode (Volume Up + Home + Power) choosing the backup or restore option, then backing up to the External SD card. Then on the restore I'm doing the same except selecting restore from the SD card (I've re-created the CWM problem 5 times, once was with advanced restore of just data the rest were basic restores doing everything). I'm not really sure what I could be doing wrong.
I have the 4.3 stock ROM before I did any custom stuff to the phone (which installed KNOX). I used chainfire's tar.md5 auto root image with Odin 3.09 in download mode when I root the phone, and I've installed CWM Recovery with ROM Manager and with an Odin tar flash in download mode. The install of TWRP was from an Odin 3.09 tar flash in download mode too.
With regard to the TWRP and CWM Recovery, I'm not really sure how easy it is for me to have messed up that part. Do you have this same model phone? Is it possible KNOX is involved in my issues? Maybe I should downgrade one of the recovery tools?
Downgrade your recovery and try again.
jonesjw362 said:
Downgrade your recovery and try again.
Click to expand...
Click to collapse
That's what I was thinking might be the best solution. Since the flaw in the restores with CWM Recovery are workable for me, I figured I may just wait until I have a need to restore to do that though. Once I do, I'll probably do a bunch of tests until I find something that works solid.
I've already restored my backups and widgets etc. a couple of times and don't really want to do it over again only to test. If there's a way to restore all of that without my having to set it up myself then I'll do it. Right now my Titanium restores don't include wallpaper (except lock screen), most of my widgets (maybe all, can't remember), and I think there was one other thing.
Advanced restore in recovery restore data only .
JJEgan said:
Advanced restore in recovery restore data only .
Click to expand...
Click to collapse
I tried that once, that's why I believe the CWM Recovery issue to be specifically with data. I'm going to do it again right now though and if things are messed up again I'm going to try jonesjw362's suggestion.
Downgrading didn't help (6.0.3.6 had a constant barrage of 4-5 apps re-crashing over and over again during the process).
I tried the following with CWM Recovery Touch 6.0.3.6, 6.0.4.5 and 6.0.4.7:
Factory reset wipe, open and test Google Play (more things break but that's the one I chose to test). Reboot into recovery mode and backup to the SD Card (not the external). Immediately advance restored data only (no wipe). Booted up, Google Play crashed, rebooted back into recovery and factory reset (data/cache) and advance restored data again with the same result.
I didn't try a downgraded version of TWRP (probably won't for now). I'm back to 6.0.4.7 and restoring my backups to get my phone back fully. Hopefully CWM Recovery comes out with a new version sometime in the near future that works for me or someone has some insight into what I can do to fix it with the existing (I'm out of ideas).
Issue Samsung stock 4.3 ROM
I ended up switching to CM 10.1.3 (was going to hold off until 11 was stable) but the Samsung stock 4.3 ROM was destroying my battery. After switching, I tested a NANDROID backup and restore with CWM Recovery Touch 6.0.4.7 (same version I was having problems with). The restore worked as it should, no problems.
End Result: As far as I can tell, the cause of the CWM Recovery data partition problem is due to the Samsung 4.3 ROM.
Edit: I was going to mark the post Resolved but I can't seem to find the drop down to do so (at least not in the same place I thought it was).
Hello,
I flashed CM11 yesterday and everything went alright. This morning I noticed I had an update for it and proceed to do it.
After the instalation and optimizing all apps it asked me for my simcard PIN and after I unlocked the phone it just went back to the cyanogenmod logo over and over.
I tried to reboot phone but it didn't help.
I've tried to search for similar threads but since i'm a newbie (first time I ever flashed anything) to this I decided to create this thread.
What should I do?
Thank you!
try to use flashtool. google it on how to use flashtool or check other threads.
So I guess i have to flash a stock ROM with flashtool and do it all over again right?
And btw, any reason you guys might think It got stuck in bootloop after I updated CM11? I came from a fresh stock rom. I'm kinda scared it might happen again after the reinstall.
Can't you enter recovery to flash a nandroid backup? (If you have one)
If not, you have two options to choose from.
Fastboot or flash a kernel with CWM or TWRP.
ADB push a zip file of a ROM and flash that.
Flash an FTF file using flashtool and start all over again.
There are many reasons why you're stuck in bootloop at the moment.
With the info you provided, there's no way of telling what caused it for you.
Well, i flashed stock ROM with flashtool, installed CM11 and I had no problems.
Went to settings and OTA update was available. Downloaded it and installed it, stuck in loopboot again. I just can't figure out what's wrong. My phone has bootload unlocked.
Might just do it all over and not update, is that a problem?
Don't use OTA, just download and flash updates manually using recovery.
In the future, for your ease, if this happens again just wipe the phone very clean (cache, /system, /data etc except /boot) and then re-flash the CM zip that you have.
It is a good practise if you make a nandroid backup before flashing a newer version of zip, in case of breaks. Or, you can have Titanium Backup to backup your apps automatically (pro version) everyday, so that you can be ready if there will be something bad happen.
hi all, i made an xda account because i really cant understand whats going on with my phone
HTC One M8 running Android 6.0 (rooted)
so after rooting my phone, i proceeded to install xposed.
i flashed the zip - no problem
i installed the apk, and after choosing 4/5 modules that i wanted, i went ahead and enabled them all and rebooted to activate them.
this is where the problems started. my phone booted, however it kept on flashing a screen with the deafult One M8 wallpaper at me. after a few seconds, it came up with an error "com.android.systemui has stopped"
not sure what was going on, i went to twrp and directly restored my nandroid backup, but after waiting for 15 mins, i realised my phone was in bootloop, so i went back to twrp and did a factory reset and restored my nandroid. but again, it went into bootloop. i tried factory resetting and restoring 3 times before giving up.
my phone isnt connecting to my laptop anymore either, but if i need to flash anything i can do it with my sd card.
im not a complete noob but im still learning and ive never not been able to restore my nandroid.
thanks in advance for any help i can get
chaitra26 said:
hi all, i made an xda account because i really cant understand whats going on with my phone
HTC One M8 running Android 6.0 (rooted)
so after rooting my phone, i proceeded to install xposed.
i flashed the zip - no problem
i installed the apk, and after choosing 4/5 modules that i wanted, i went ahead and enabled them all and rebooted to activate them.
this is where the problems started. my phone booted, however it kept on flashing a screen with the deafult One M8 wallpaper at me. after a few seconds, it came up with an error "com.android.systemui has stopped"
not sure what was going on, i went to twrp and directly restored my nandroid backup, but after waiting for 15 mins, i realised my phone was in bootloop, so i went back to twrp and did a factory reset and restored my nandroid. but again, it went into bootloop. i tried factory resetting and restoring 3 times before giving up.
my phone isnt connecting to my laptop anymore either, but if i need to flash anything i can do it with my sd card.
im not a complete noob but im still learning and ive never not been able to restore my nandroid.
thanks in advance for any help i can get
Click to expand...
Click to collapse
*. Flash xposed uninstaller zip and try booting your device. Link here - http://dl-xda.xposed.info/framework/uninstaller/
-->> use this» make a full wipe from recovery, then restore nandroid backup.
*.While restoring nand. from recovery, make a full wipe like wipe system etc.. Then restore your nand. Then you're good to go.
thanks a ton for your reply
i already tried flashing the uninstaller - didnt work
but ill try your second method. thanks once again
chaitra26 said:
thanks a ton for your reply
i already tried flashing the uninstaller - didnt work
but ill try your second method. thanks once again
Click to expand...
Click to collapse
Hey, the 1st one won't works, Cuz you'd already did a factory data reset, so that's gonna be won't work. And you'd tried restoring nandroid over that, so that's failed.
I hope second one will works.
sachin n said:
*. Flash xposed uninstaller zip and try booting your device.
-->> use this» make a full wipe from recovery, then restore nandroid backup.
*.While restoring nand. from recovery, make a full wipe like wipe system / data etc.. Then restore your nand. Then you're good to go.
Click to expand...
Click to collapse
Um i think i seriously screwed up - i deleted everything including system and data and stuff - but now my nandroid is gone
what can i do now i dont even have a nandroid!
oh my god my phone doesnt have an os anymore... what have i done wrong?????
chaitra26 said:
Um i think i seriously screwed up - i deleted everything including system and data and stuff - but now my nandroid is gone
what can i do now i dont even have a nandroid!
Click to expand...
Click to collapse
Deym!!
So, look at the One m8 forums, you'll get the workarounds.
I've found one here - https://forum.xda-developers.com/ht...k-twrp-t3086860?_e_pi_=7,PAGE_ID10,5801529172
@chaitra26, either DL any custom ROMs and flash it via custom recovery [Twrp].
Look here for custom ROMs - https://forum.xda-developers.com/htc-one-m8/development?
Regarding that '' no OS installed'' error, that's common when you try to reboot your device from twrp without installing any system images /ROMs.
FYI - when you full wipe your device and tries to power up you'll get the same warning.
Hey guys,
hope someone can help. I had a screen crack 2 weeks ago. I was on Alexndr CSD2 DBT with TWRP. So I have a full TWRP backup. Sent it to Samsung. These smart asses reflashed my phone without any need of doing so. On arrival it was on stock with funktional LTE Sim connection.
So I checked OEM Unlock, went to download mode and flashed TWRP. Went to TWRP and formatted everything and restored ALL partitions of my backup. On reboot my PIN was not accepted anymore - this is not concerning, I am willing to reinstall all by hand. But I lost IMEI/baseband - so deleting the key files I can enter the phone but I have no DATA connection via SIM anymore.
So I reflashed stock CSD2 .... no IMEI.... so I restored EFS only .... boot loop.
I installed CSD Alexndr fresh and restored EFS only .... no IMEI
Wtf is going on? Any ideas I can fix this without sending it back and starting all over and maybe getting stuck again?
Thnx
Peter
Trying flashing the modem, that alexndrs rom utilizes, solely, in TWRP .
CynicalHeight00 said:
Trying flashing the modem, that alexndrs rom utilizes, solely, in TWRP .
Click to expand...
Click to collapse
Thank you, tried it, did not change the situation unfortunately. He says I think it was included in the rom anyway.
Hmm, if you installed the rom again to install the modem- that's not what I meant.
Alexndrs rom makes a backup of your efs; Find the post and see what you have type in twrp terminal.
Then try the modem flash, solely.
I had the same issue, but it was fixed with modem flashing; however, everytime I reinstall a rom I need to do a separate modem flash.
CynicalHeight00 said:
Hmm, if you installed the rom again to install the modem- that's not what I meant.
Alexndrs rom makes a backup of your efs; Find the post and see what you have type in twrp terminal.
Then try the modem flash, solely.
I had the same issue, but it was fixed with modem flashing; however, everytime I reinstall a rom I need to do a separate modem flash.
Click to expand...
Click to collapse
Hey thanks for your answer.
I flashed the BL...zip solely and also tried to restore EFS and baseband partition only, besides trying full stock odin flash and full TWRP restore with all partitions.
I read:
"EFS restore command (TWRP -> Advanced -> Terminal):
gunzip -c /external_sd/.backup/efs/efs_recent.img.gz | dd bs=4096 of=/dev/block/sda3"
I did, it flashed it and still the same problem. This was the SD from my S8plus. I didn't know Alexndr is overwriting EFS backup every goddamn flash. So my old EFS backup says Aug 2018 - so it is of my S8plus. And the recent one got overwritten by the few flashing attempts. So the rom did overwrite EFS backup I suspect.
So I maybe left with the TWRP backup of EFS only. Why is it not working, to restore the EFS TWRP backup - it should have all data cause it was done when the phone was running well? Is there a way to restore EFS/IMEI/Baseband from that backup? I dont understand how baseband gets lost while having full TWRP backup?
phoenX80 said:
Hey guys,
hope someone can help. I had a screen crack 2 weeks ago. I was on Alexndr CSD2 DBT with TWRP. So I have a full TWRP backup. Sent it to Samsung. These smart asses reflashed my phone without any need of doing so. On arrival it was on stock with funktional LTE Sim connection.
So I checked OEM Unlock, went to download mode and flashed TWRP. Went to TWRP and formatted everything and restored ALL partitions of my backup. On reboot my PIN was not accepted anymore - this is not concerning, I am willing to reinstall all by hand. But I lost IMEI/baseband - so deleting the key files I can enter the phone but I have no DATA connection via SIM anymore.
So I reflashed stock CSD2 .... no IMEI.... so I restored EFS only .... boot loop.
I installed CSD Alexndr fresh and restored EFS only .... no IMEI
Wtf is going on? Any ideas I can fix this without sending it back and starting all over and maybe getting stuck again?
Thnx
Peter
Click to expand...
Click to collapse
phoenX80 said:
Thank you, tried it, did not change the situation unfortunately. He says I think it was included in the rom anyway.
Click to expand...
Click to collapse
phoenX80 said:
Hey thanks for your answer.
I flashed the BL...zip solely and also tried to restore EFS and baseband partition only, besides trying full stock odin flash and full TWRP restore with all partitions.
I read:
"EFS restore command (TWRP -> Advanced -> Terminal):
gunzip -c /external_sd/.backup/efs/efs_recent.img.gz | dd bs=4096 of=/dev/block/sda3"
I did, it flashed it and still the same problem. This was the SD from my S8plus. I didn't know Alexndr is overwriting EFS backup every goddamn flash. So my old EFS backup says Aug 2018 - so it is of my S8plus. And the recent one got overwritten by the few flashing attempts. So the rom did overwrite EFS backup I suspect.
So I maybe left with the TWRP backup of EFS only. Why is it not working, to restore the EFS TWRP backup - it should have all data cause it was done when the phone was running well? Is there a way to restore EFS/IMEI/Baseband from that backup? I dont understand how baseband gets lost while having full TWRP backup?
Click to expand...
Click to collapse
It's not bl file you flash. Also, that terminal code is for recent , which , i think is a backup of efs now flashed, not the one you had prior to the flash. Meaning, check for the efs- backup. That file is hidden on your external sd card.
In theory, that's what I suppose as well but it didn't work for me either- restoring via twrp.
CynicalHeight00 said:
It's not bl file you flash. Also, that terminal code is for recent , which , i think is a backup of efs now flashed, not the one you had prior to the flash. Meaning, check for the efs- backup. That file is hidden on your external sd card.
In theory, that's what I suppose as well but it didn't work for me either- restoring via twrp.
Click to expand...
Click to collapse
Yeah, I know, I just had the file open and quoted wrong. It is
gunzip -c /external_sd/.backup/efs/efs_backup.img.gz | dd bs=4096 of=/dev/block/sda3
The command worked to restore the EFS but since it is the backup of my S8plus IMEI is still not recognized....
Initialization via SmartSwitch returned that the device is not supported...great.
So the only backup I have is TWRP. I need a way to rescue from TWRP. Since full resore ends in broken IMEI I may be screwed since a full restore should render the phone running but it is not for whatever reason. I am disappointed that the full TWRP backup doesnt seem functional to backup and restore EFS.
Is efs formatted the proper way?
I had also wiped clean everything in twrp.
CynicalHeight00 said:
Is efs formatted the proper way?
I had also wiped clean everything in twrp.
Click to expand...
Click to collapse
TWRP doesnt offer to wipe EFS separately?
phoenX80 said:
Yeah, I know, I just had the file open and quoted wrong. It is
gunzip -c /external_sd/.backup/efs/efs_backup.img.gz | dd bs=4096 of=/dev/block/sda3
The command worked to restore the EFS but since it is the backup of my S8plus IMEI is still not recognized....
Initialization via SmartSwitch returned that the device is not supported...great.
So the only backup I have is TWRP. I need a way to rescue from TWRP. Since full resore ends in broken IMEI I may be screwed since a full restore should render the phone running but it is not for whatever reason. I am disappointed that the full TWRP backup doesnt seem functional to backup and restore EFS.
Click to expand...
Click to collapse
phoenX80 said:
TWRP doesnt offer to wipe EFS separately?
Click to expand...
Click to collapse
I think it should be included under system?
I wiped all available partitions and restored again. Unfortunately still no change. No LTE no IMEI.
You have to check whether or not the format , ex. Ets4 or whatnot, is what is needed for efs to operate
Did you fix it?
No, I am stuck.
There is only a way to format System - which I did. Nothing changed.
I tried to odin flash CSD2 to have the phone update on its own to CSDE to maybe gain baseband on this update. But no luck.
phoenX80 said:
No, I am stuck.
There is only a way to format System - which I did. Nothing changed.
I tried to odin flash CSD2 to have the phone update on its own to CSDE to maybe gain baseband on this update. But no luck.
Click to expand...
Click to collapse
What's the recourse?
What do you mean?
phoenX80 said:
What do you mean?
Click to expand...
Click to collapse
What will you try to fix it?
I am out of ideas. I have to send it to Samsung I guess....
Since I know my IMEI shouldn'T it be possible to HEX edit another backup to reflash mine? I chekced that when I restore the S8s EFS the serial number actually changes but the IMEIs stay unknown. Shouldn't the IMEI of the S8 pop up?
phoenX80 said:
Since I know my IMEI shouldn'T it be possible to HEX edit another backup to reflash mine? I chekced that when I restore the S8s EFS the serial number actually changes but the IMEIs stay unknown. Shouldn't the IMEI of the S8 pop up?
Click to expand...
Click to collapse
could you figure it out to this day?