Database Info

[Q] Can't flash any ZIP files with ClockworkMod

I was going to install openOptimus on my Optimus One, so I made a backup, wiped mostly everything then partitioned the sd card (512MB ext and 0MB swap) and transferred the backup and the rom back to my sd with an adapter. Then I went to install the zip, but it delivered this message:
E:Can't open /sdcard/update-openOptimus-build-2.202.1-thunder-ciaox-signed.zip (bad)
Installation aborted.
I tried redownloading the zip, which didn't work, so I tried a different one which also didn't work. So I gave up and tried restoring, but that didn't work either. Now I have a phone with nothing to boot into but CWM, and no way to install anything new. I have no idea how to fix this and my phone is useless until I do, so what should I do?

It looks like you'll have to start from scratch again. Use the kdz updater. And download the stock firmware for your phone. When you re-root the phone, make sure you reformat your sd card (slow format) before anything. Then you have the absolute latest version of clockwork installed. The same thing happened to me but with a couple reboots it seemed to read my card. But if this isn't the case for you, then google up those items and start allllll over.
Sent from my T-Mobile G2 using XDA

Thanks for the answer, I appreciate it. But how can I get kdz updater to work on my phone if I can't get past clockworkmod?

Seems simple, but you might also want to try another card. I have to admit to having annoyed myself more than once by not checking to make sure an SD card was in fact good BEFORE driving myself crazy trying everything else.

Doesn't sound good... Redoing all that isn't fun either..

Try downloading the ROM using another web browser on your computer just in case the download gets corrupted.

Its pretty simple..there's a button combo to get into emergency mode!! Google it because I forget lol. Then just update it through kdz while its in emergency mode...all fixed
Sent from my T-Mobile G2 using XDA

Btw when u get your phone up and running. Hit that thanx button
Sent from my T-Mobile G2 using XDA

Thanks a ton, I thought it was done for. Got stock back, rerooted and hopefully it'll work when I update CWM and try to install a custom rom.

Okay, flashing the same rom I was trying before is not working. Same problem. Restore is working now, so at least I won't have to use kdz again. Any possibility that I need a specific CWM to flash the current version (2.202) of openOptimus? Cause I have the latest CWM, but openOptimus was last updated in August.

qs96 said:
Okay, flashing the same rom I was trying before is not working. Same problem. Restore is working now, so at least I won't have to use kdz again. Any possibility that I need a specific CWM to flash the current version (2.202) of openOptimus? Cause I have the latest CWM, but openOptimus was last updated in August.
Click to expand...
Click to collapse
Haha! Grrrreat! your up and running again! When you get a chance check out some of my vids on youtube.....xavicivic
---------- Post added at 02:46 AM ---------- Previous post was at 02:43 AM ----------
xavicivic said:
Haha! Grrrreat! your up and running again! When you get a chance check out some of my vids on youtube.....xavicivic
Click to expand...
Click to collapse
Oh and as for that. Flash the latest version. Ummm check the website or get rom manager. It should be there. Before u install the rom. be sure you wipe data, cache, dalvick cache and your good to go from there

[Q] Messaging Not Working CM10.1.3

Tried to search for hours.
First time flashing to CM 10.1.3 Stable. Came from stock rooted touchwiz.
Created Nandroid backups via twrp. Flashed via goomanager/twrp.
Flashed perfectly fine. But realized I had issues with my contacts backup. Tried to flash back to the nandroid backup and it never worked. It got stuck and the GS3 Cyanogenmod screen. Battery pulled and booted into recovery to flash the CM rom again. Went fine and then realized I could not use text messaging since the messaging app would force close instantly.
Tried to install Go sms since this is what i normally use. Got a -24 error which i solved by deleted com. data from the data/data folder. Was able to install it but now text messaging will not work at all. My backups of texts will complete the restore but it wont show up on the phone.
I tried to update the SMSC number as well to no avail.
I have no idea what to do now.
HELP!

Did you do a full wipe in recovery before you installed the new rom? I am sure you did, just throwing ideas out

blackwolf77 said:
Did you do a full wipe in recovery before you installed the new rom? I am sure you did, just throwing ideas out
Click to expand...
Click to collapse
Yes via goomanager options right before initiating the flash.
Thanks for the help. Trying to get this fixed.
Just discovered that texts through google voice work. I'm guessing because this is handled via data and not normal sms.
EDIT: Realized that was confusing. I have a seperate google voice number (for work) and the text messages for that work.

Also I am slowly discovering that every app gets the -24 error when I go to install it.
Could this have something to do with it? Typically all I have to do is delete the com.application folder of whatever I am trying to install and it allows me to install it. This worked on go sms for install but sms is still not working.

I would go into recovery, do a full wipe ( I wipe 3 times, probably overkill, but has always faired well for me) reinstall the rom and gapps, then wipe cache before you reboot. Seems like you have something corrupted and you are about going to have to start over to get it right.
---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------
I have never had to delete anything to get go sms to work on cyanogenmod.
Why are you installing an old version of cyanogenmod? Just curious

andfpac any
blackwolf77 said:
I would go into recovery, do a full wipe ( I wipe 3 times, probably overkill, but has always faired well for me) reinstall the rom and gapps, then wipe cache before you reboot. Seems like you have something corrupted and you are about going to have to start over to get it right.
---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------
I have never had to delete anything to get go sms to work on cyanogenmod.
Why are you installing an old version of cyanogenmod? Just curious
Click to expand...
Click to collapse
That sounds like a good idea. I will do that when I get home. Will this delete everything from my phone? Including the external sd card?
I don't want to have to delete anything to get go sms to work. That must be happening because I have old data.
I wanted to start with cyanogenmod on a stable version. 10.1.3 is the most recent stable.

andfpac any
blackwolf77 said:
I would go into recovery, do a full wipe ( I wipe 3 times, probably overkill, but has always faired well for me) reinstall the rom and gapps, then wipe cache before you reboot. Seems like you have something corrupted and you are about going to have to start over to get it right.
---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------
I have never had to delete anything to get go sms to work on cyanogenmod.
Why are you installing an old version of cyanogenmod? Just curious
Click to expand...
Click to collapse
That sounds like a good idea. I will do that when I get home. Will this delete everything from my phone? Including the external sd card?
I don't want to have to delete anything to get go sms to work. That must be happening because I have old data.
I wanted to start with cyanogenmod on a stable version. 10.1.3 is the most recent stable.

I don't know which recovery you have, but as long as you don't select the option to format the external sd card it won't.

blackwolf77 said:
I don't know which recovery you have, but as long as you don't select the option to format the external sd card it won't.
Click to expand...
Click to collapse
I have TWRP. I will make sure that I do not do that.
Thanks for your help and I will make sure that I update when it hopefully is fixed!

Let me know, I hope it fixes your problems.

blackwolf77 said:
Let me know, I hope it fixes your problems.
Click to expand...
Click to collapse
Success! Did exactly what you said and it worked perfectly!
Thanks again for all of your help!

(HELP) Stuck on Bootloop, no issue...

Hey guys, today I don goofed.
I went full flashing frenzy mode after week and weeks of restraining myself in fear of doing irremediable damage to my phone. I rooted it and unlocked boot loader without changing the recovery because I wanted as much as possible "stock" root (don't ask why, this is stupid I know).
So I Updated Binaries, Installed Xposed framework, installed a bunch of modules (I can list them if you need), then I installed all the lollipop apk's I could get my hands on (GPL, Google Play Store, Google Search, Music) and I decided, this isn't enough. I then flashed Franco Kernel R27, and things were going great. As that wasn't enough flashing, I flashed the Smooth Scrool Mod and finale Vomer Tweaks. I think this is where it went south, because I didn't find the file for Vomer (that I was supposed to install), so I flashed It once again. After that, my phone started to bug a bit, so I rebooted, and at first I would get no signal, would not detect my SIM card etc. I tried a factory reset and now my phone is booting, getting to the setup screen, and booting again. At this point I still have access to TWRP, Fastboot etc. I then decided to do I full complete recovery using THIS GUIDE to get "100 stock". I'm still getting the reboot at setup screen. I am know trying THIS METHOD
AND IT ****ING WORKED. Holy ****. I'm leaving this post so I can thank all the great guys that help me save my ass... I learned my lesson and do a Nandroid before doing stupid **** like that (i Know i'm gonna do it again...). I was scared ****less. I'm still curious as towhead happened though. Any clue ?

Yep @markbencze guide has saved my A$$ more than once.

i am having bootloop issue, tried many roms, erased partition too, still no use. continuous bootloops
---------- Post added at 03:04 AM ---------- Previous post was at 03:03 AM ----------
S M G said:
Yep @markbencze guide has saved my A$$ more than once.
Click to expand...
Click to collapse
i am having bootloop issue, tried many roms, erased partition too, still no use. continuous bootloops
---------- Post added at 03:11 AM ---------- Previous post was at 03:04 AM ----------
i am having bootloop issue, tried many roms, erased partition too, still no use. continuous bootloops

[HEEEEEELP]-TWRP stock Backup deleted - Xiaomi mi a2 lite

Hi all,
As you all know Android rolled out the new 9 pie Update on all xiaomi devices.
After updating my mi a2 lite became the crappiest phone on earth as all the bugs started appearing(phone was rebooting multiple times, image was broken, sd xcard not recognised and battery life draining fast as hell).
Because of that I decided to root my phone and install Havoc 2.0. Fair enough, I used the rom for a bit but honestly I am not really happy about it too as doesn't seem really stable at all (many functions are there but not working, the camera app is crap, the volume bar appears every time I touch the fingerprint sensor and the fingerprint lock isn't working as well). At this point I wanted to revert and get back to the stock oreo 8.1 so I booted the recovery twrp to restore the firmware backup that I did at the beginning before installing havoc but this disappeared!!!!!
Reading again the procedure i followed I noticed that one of the steps was to wipe the caches and, as the procedure was saying, the system as well(I know.... I am an idiot for relying on what the procedure said)!
Obviously this deleted my previous backup completely leaving me empty hands without any stock firmware/rom.
Is there any chance to revert back to the stock (maybe downloading all the pieces and then force flashing them?) or I am screwed?
I know, I should have followed one of your tutorial (and I am sorry for asking now for your assistance) but now I think you are the only one that can actually help me.
Best regards,
D.

manna.davide87 said:
Hi all,
As you all know Android rolled out the new 9 pie Update on all xiaomi devices.
After updating my mi a2 lite became the crappiest phone on earth as all the bugs started appearing(phone was rebooting multiple times, image was broken, sd xcard not recognised and battery life draining fast as hell).
Because of that I decided to root my phone and install Havoc 2.0. Fair enough, I used the rom for a bit but honestly I am not really happy about it too as doesn't seem really stable at all (many functions are there but not working, the camera app is crap, the volume bar appears every time I touch the fingerprint sensor and the fingerprint lock isn't working as well). At this point I wanted to revert and get back to the stock oreo 8.1 so I booted the recovery twrp to restore the firmware backup that I did at the beginning before installing havoc but this disappeared!!!!!
Reading again the procedure i followed I noticed that one of the steps was to wipe the caches and, as the procedure was saying, the system as well(I know.... I am an idiot for relying on what the procedure said)!
Obviously this deleted my previous backup completely leaving me empty hands without any stock firmware/rom.
Is there any chance to revert back to the stock (maybe downloading all the pieces and then force flashing them?) or I am screwed?
I know, I should have followed one of your tutorial (and I am sorry for asking now for your assistance) but now I think you are the only one that can actually help me.
Best regards,
D.
Click to expand...
Click to collapse
Wiping system is not what wiped your backup, your backup was stored on internal storage or on external sdcard, it does not get stored in system. The only you could have wiped the backup is if you also chose the option to wipe the internal storage when you wiped cache and system.
Factory reset and the normal wipes in TWRP do not wipe /data/media, /data/media is where your user data is stored. Only specifically choosing the option to wipe internal storage can wipe /data/media.
And you aren't an idiot for following instructions, you're an idiot for following instructions incorrectly. If you had wiped cache and system but left internal storage alone, you wouldn't be in the mess you're in.
Have you tried doing a Google search for:
"Return to stock (your model number)"
If it's available, that should find the instructions, tools and files you need.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Wiping system is not what wiped your backup, your backup was stored on internal storage or on external sdcard, it does not get stored in system. The only you could have wiped the backup is if you also chose the option to wipe the internal storage when you wiped cache and system.
Factory reset and the normal wipes in TWRP do not wipe /data/media, /data/media is where your user data is stored. Only specifically choosing the option to wipe internal storage can wipe /data/media.
And you aren't an idiot for following instructions, you're an idiot for following instructions incorrectly. If you had wiped cache and system but left internal storage alone, you wouldn't be in the mess you're in.
Have you tried doing a Google search for:
"Return to stock (your model number)"
If it's available, that should find the instructions, tools and files you need.
Click to expand...
Click to collapse
Hi, first of all thanks for replying.
Interbal storage hasn't been wiped out, i am sure about it as the proceedure was saying not to do it. (I've selected just the first 3 options and internalbstorage is the 4th so I am def8nitely sure about it). Might be somewhere else then?
I did a second back up now and I see it so at this point I am not really sure where this could be!
Is 12 hours that I am searching proceedures but everything is very confusing.

manna.davide87 said:
Hi, first of all thanks for replying.
Interbal storage hasn't been wiped out, i am sure about it as the proceedure was saying not to do it. (I've selected just the first 3 options and internalbstorage is the 4th so I am def8nitely sure about it). Might be somewhere else then?
I did a second back up now and I see it so at this point I am not really sure where this could be!
Is 12 hours that I am searching proceedures but everything is very confusing.
Click to expand...
Click to collapse
Mate @Droidriven you're a monster!
I found it in data/media in the internal storage! thanks a lot mate!
I'll run it and see if all comes back as usual.
Infinite thanks!

Good to go.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Good to go.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Do you mind me asking you one last thing?
At this point, having the original backup, I can try another custom Rom before reverting everything to Oreo.
My question are 2:
-Because you seem very driven, do you know any stable custom rom that I can run on this Xiaomi MI A2 lite?
-Do you know if I can Install the old Havoc on and purge this pie version?
Thanks again,
Davide

manna.davide87 said:
Do you mind me asking you one last thing?
At this point, having the original backup, I can try another custom Rom before reverting everything to Oreo.
My question are 2:
-Because you seem very driven, do you know any stable custom rom that I can run on this Xiaomi MI A2 lite?
-Do you know if I can Install the old Havoc on and purge this pie version?
Thanks again,
Davide
Click to expand...
Click to collapse
I don't know anything about any of the ROMs for your device, I don't have your device.
Sent from my LGL84VL using Tapatalk

Bricked my OP7P - Can't decrypt data partition anymore

Hey Guys,
this could propably be posted in r/TIFU as well since I think I screwed up big time today -.-
I basically just wanted to update my rooted OP7P to 10.0.5 (EU) using the latest OTA - so I followed the usual steps as always:
Uninstall Magisk
Install OTA - No Reboot
Install TWRP retention script in Magisk
Re-Install Magisk
Reboot
This procedure worked fine the last 2 times an OTA was released but this time I'm not able to boot into the system anymore. TWRP is still in places but won't read the data partition anymore - it also doesn't ask for my pattern to decrypt it. Problem is that idiot-me of course didn't do a backup before (yea, I know -.-) and obviously doesn't want to loose the data on it.
I of course checked the forum and googled my ass of trying to find a non-destructive way to access the system but couldn't find anything fitting my scenario. So my last resort is to ask you guys directly: Did anybody ever encounter such a situation and if yes, how did you resolve it? Right now any support would be much appreciated
//Edit: Symptoms and current behaviour:
Boot into system (partition A) ends in the OP logo cirling endlessly
Boot into system (partition B) sends me directly to TWRP
TWRP doesn't ask for encryption pattern
The answer to TWRP's initial question (Keep System r/o) is not persisted
Fastboot/ADB are working (but obviously w/o access to /data)
I'm technically running a stock OxygenOS with Renovate ICE. I know technically its instuctions say to install the OTA directly from within TWRP and and then re-flash TWRP and Magisk but that wasn't neccessary the last times... one idea of mine is to just do that now and see where it leads me but I really don't wanna risk my data.

the.cybertronic said:
Hey Guys,
this could propably be posted in r/TIFU as well since I think I screwed up big time today -.-
I basically just wanted to update my rooted OP7P to 10.0.5 (EU) using the latest OTA - so I followed the usual steps as always:
Uninstall Magisk
Install OTA - No Reboot
Install TWRP retention script in Magisk
Re-Install Magisk
Reboot
This procedure worked fine the last 2 times an OTA was released but this time I'm not able to boot into the system anymore. TWRP is still in places but won't read the data partition anymore - it also doesn't ask for my pattern to decrypt it. Problem is that idiot-me of course didn't do a backup before (yea, I know -.-) and obviously doesn't want to loose the data on it.
I of course checked the forum and googled my ass of trying to find a non-destructive way to access the system but couldn't find anything fitting my scenario. So my last resort is to ask you guys directly: Did anybody ever encounter such a situation and if yes, how did you resolve it? Right now any support would be much appreciated
//Edit: Symptoms and current behaviour:
Boot into system (partition A) ends in the OP logo cirling endlessly
Boot into system (partition B) sends me directly to TWRP
TWRP doesn't ask for encryption pattern
The answer to TWRP's initial question (Keep System r/o) is not persisted
Fastboot/ADB are working (but obviously w/o access to /data)
I'm technically running a stock OxygenOS with Renovate ICE. I know technically its instuctions say to install the OTA directly from within TWRP and and then re-flash TWRP and Magisk but that wasn't neccessary the last times... one idea of mine is to just do that now and see where it leads me but I really don't wanna risk my data.
Click to expand...
Click to collapse
The bad news is once twrp loses access to data. The only fix is to format data and everything will be fixed.

So... you're basically telling me I ****ed up completely and my data is gone? Never was a profile picture more fitting than yours right now :/
What I'm wondering is that, from a technical perspective and on a working phone, the decryption takes place not during the boot but only after you've entered your code/passphrase/pattern on OS level. Meaning the system should theoretically be able to boot up to there without /data access. TThat's why I had the idea to flash a clean stock Oxygen from TWRP (no root), boot the system and hopefully be able to access the data this way. Respectively any encryption can be broken somehow, can't it? Even if it might take quite some time to do so this should theoretically be possible...
I mean... I definetly don't know enough about Android internals to understand its encryption mechanics completely but from a technical perspective it should be possible.... like the saying "there is no such thing as 100% security"

the.cybertronic said:
So... you're basically telling me I ****ed up completely and my data is gone? Never was a profile picture more fitting than yours right now :/
What I'm wondering is that, from a technical perspective and on a working phone, the decryption takes place not during the boot but only after you've entered your code/passphrase/pattern on OS level. Meaning the system should theoretically be able to boot up to there without /data access. TThat's why I had the idea to flash a clean stock Oxygen from TWRP (no root), boot the system and hopefully be able to access the data this way. Respectively any encryption can be broken somehow, can't it? Even if it might take quite some time to do so this should theoretically be possible...
I mean... I definetly don't know enough about Android internals to understand its encryption mechanics completely but from a technical perspective it should be possible.... like the saying "there is no such thing as 100% security"
Click to expand...
Click to collapse
Dude try flashing the stock rom from twrp onto both slots by mounting an otg drive..or adb sideload(very slow I think..still worth a try if you don't wanna lose data)..stock rom can manage the encryption I suppose.
Encryption is an issue when you flash different roms(I think so..I am no expert,just my experience so far).
Breaking encryption is not like what you think..it might take ages to break using brute force (again from what I heard..I lost my data a lot of time flashing roms without twrp backup..nowadays I just backup my apps using tb coz restorings the apps is really a pain in the ass process)

the.cybertronic said:
So... you're basically telling me I ****ed up completely and my data is gone? Never was a profile picture more fitting than yours right now :/
What I'm wondering is that, from a technical perspective and on a working phone, the decryption takes place not during the boot but only after you've entered your code/passphrase/pattern on OS level. Meaning the system should theoretically be able to boot up to there without /data access. TThat's why I had the idea to flash a clean stock Oxygen from TWRP (no root), boot the system and hopefully be able to access the data this way. Respectively any encryption can be broken somehow, can't it? Even if it might take quite some time to do so this should theoretically be possible...
I mean... I definetly don't know enough about Android internals to understand its encryption mechanics completely but from a technical perspective it should be possible.... like the saying "there is no such thing as 100% security"
Click to expand...
Click to collapse
The reason that format is the only answer is because when twrp does not ask for password. It believes you are unencrypted. What has happened is the file that store your password and encryption key is corrupted so any answer you give is wrong.

There's nothing you can do but format data. I've encountered this issue already.

You can try to salvage personal photos and videos using an otg drive (external ssd, hdd, sd card reader...), also back in 6t days I had this encryption problem twice, I remember that one time flashing the stock rom from the otg fixed it but I don't remember if I rebooted to recovery of the other slot.
Anyway, for the others, if he used DM verity removal and so decrypted data, he would have never face this problem again?

Joker123## said:
Dude try flashing the stock rom from twrp onto both slots by mounting an otg drive..or adb sideload(very slow I think..still worth a try if you don't wanna lose data)..stock rom can manage the encryption I suppose.
Encryption is an issue when you flash different roms(I think so..I am no expert,just my experience so far).
Breaking encryption is not like what you think..it might take ages to break using brute force (again from what I heard..I lost my data a lot of time flashing roms without twrp backup..nowadays I just backup my apps using tb coz restorings the apps is really a pain in the ass process)
Click to expand...
Click to collapse
vegetaleb said:
You can try to salvage personal photos and videos using an otg drive (external ssd, hdd, sd card reader...), also back in 6t days I had this encryption problem twice, I remember that one time flashing the stock rom from the otg fixed it but I don't remember if I rebooted to recovery of the other slot.
Anyway, for the others, if he used DM verity removal and so decrypted data, he would have never face this problem again?
Click to expand...
Click to collapse
I just tried flashing the stock Oxygen yesterday but to no satisfying result... afterwards it just showed a clean default-structure on the SD. Long story short: I accepted the fate that my data is gone and learned a valuable lesson... first thing I installed after rooting was Titanium^^
Zhuang zhuang said:
There's nothing you can do but format data. I've encountered this issue already.
Click to expand...
Click to collapse
As hard as it is to admit, you were completely right... I just lost 6 months worth of photos incl. my last vacation in Vietnam - fml.

the.cybertronic said:
I just tried flashing the stock Oxygen yesterday but to no satisfying result... afterwards it just showed a clean default-structure on the SD. Long story short: I accepted the fate that my data is gone and learned a valuable lesson... first thing I installed after rooting was Titanium^^
As hard as it is to admit, you were completely right... I just lost 6 months worth of photos incl. my last vacation in Vietnam - fml.
Click to expand...
Click to collapse
For future reference, brick means a brick. Like, can't boot to fastboot/twrp/or use msmtool

the.cybertronic said:
As hard as it is to admit, you were completely right... I just lost 6 months worth of photos incl. my last vacation in Vietnam - fml.
Click to expand...
Click to collapse
In the recent OS (10.0.5 & beta 13) I think Oneplus they add something that prevent user from using the TWRP retention script. I always use this solution for lower version and have no issue but with both 10.0.5 and beta 13 have the same issue

Zhuang zhuang said:
In the recent OS (10.0.5 & beta 13) I think Oneplus they add something that prevent user from using the TWRP retention script. I always use this solution for lower version and have no issue but with both 10.0.5 and beta 13 have the same issue
Click to expand...
Click to collapse
damn, good to know if I ever install OOS again - I now switched to Havoc... even though I had to skip rooting it all together after I couldn't get Magisk running with the latest safety net changes (thanks Google -.-)