Database Develop

Cyanogen 4.12.2

Ohh man, i was seriously disappointed in this release. All was good til let CM Updater automatically update the firmware, then all of a sudden my SD card was corrupt.
But wait, i go to "Update from any zip" And my previous installs are there.
4.9.* is corrupt, so i do a nandroid backup and b00m theres HERO... OMFG

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

First, this belongs in Q&A and as such has been reported.
But, to be helpful, you can manually flash the system.img and data.img from your backups to make sure that it restores the correct backup via fastboot
If you copy the files to your computer (system.img, data.img, and boot.img) to where-ever you have fastboot then you can run the commands in the bootloader:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata data.img
and this should be the same as a NANDROID/switchrom restore.

couple of thing - wrong section
the 4.2.x are stored in /sdcard/cmupdater/ or thereabouts and its unlikely they are all corrupt
its your own fault for not doing a nandroid of a CM (you may have an old one in there if you went to hero after cm and then back again)
if not, start again with 1.6 then CM
CM doesnt screw your sd, improper use does

I am seriously disappointed with your post.

why-o-why do we let people with less than 50 posts create threads anywhere but the QnA?
ZALGO - that was wrecking-crew-esque....let me shake your hand
i miss those guys....

ohh stfu -- all you, i have been flashing PC bios for years, but i "update" my phone with and automatic update, and you jump on my back. and where so you think i got my information to flash my phone. "YES" xda.. so swallow it up.. Question is there a thread for the new Cyanogen 4.12.2 release, if so point me to it. THANKS!!!

fukin look for it you lazy buggar
its staring you in the face...infact it was 2 under your thread when you first posted
and so what if you flash pc bios(s) all the time, this is even easier, you dont even need to push a button until its finished

I'm new with like no post an I can tell your a tool. Do a little search douch nozzle. I am a noob and I agree garok89, no new threads for noobs outside of Q+A before they can show there not tools like this douch who started the tread

cm updater could do with the option to do a Bart / Switchrom / Nandroid backup though.
I have clicked apply now many times and forgotten to manually reboot and do a backup first.
If it fails I just curse myself, but it would be a nice feature.

the cmupdater can easily have the feature to autonandroid - we have the code for it
only problem is, none of the recovery images support it
the second its supported in cyanogens recovery image (and therefore RAs recovery image as it is based on cyanogens) we will enable the feature

reading is the best way to avoid these types of problems.
but lets face it, this is total....

[Q] Market Problem w/ Custom ROMs

When I flash back to stock, of course the new updated market works. At one point I kept the stock and flashed a new kernal after updating to the current 2.2 and still the new market worked. As soon as I flash a custom ROM such as Serendipity, Fasty, Cognition, or another the market all of a sudden does not work. When I mean does not work, I only mean in the instance that it will not download large apps. I have read on flashable zips, adb shell commands, and other methods such as removing the battery but still none of this works. Is there any way to fix this problem without reverting to the old market??

It's cache size related bug, the problem here is that manufacturers put a cache partition on their devices that is smaller than googles maximum allowed app size for the market, 50MB (which was updated this year from 30mb). Reverting back to the old market will fix that issue and what I'd recommend you is to freeze MarketUpdater in TiBu (titanium backup app) so that it won't allow it to update itself back to the new market.
In case u want to use the new market, u'll have to apply the fix made by corgar - iXNyNe ,but it requires a kernel with init.d script support. If u wanna try it out here's the script, download and extract the file and then copy it in system/etc/init.d folder with a root explorer and modify the permissions of the script to 7-5-5. To do that go to system/etc/init.d folder ,mount r/w (if ur using root explorer) and long press on S95change_cache file, select permissions and make it look like in the pic below and then reboot ur phone in recovery and wipe cache ,dalvik cache and restart ur phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If all went well (u should have a cache.img file under dbdata of 54+ mb) u now can download all the apps from the new market, if it didn't then try with 7-7-7 permissions (like in the pic above only everything checked)
There are other methods , here's a post from Kyuta Syuko that sums it all up. http://forum.xda-developers.com/showpost.php?p=17850944&postcount=9050

Have u tried stopping the market and clearing all data in the all apps menu?
Sent from my SGH-I897 using xda premium

He can try that too, but that's useful when ALL downloads aren't starting/apps aren't updating. But the 30mb+ download issue ,insufficient space error, is cache related.
I can confirm (and others did as well) that the script works.

Thanks for the help but I did search like I posted. None of the options worked. But I did figure out a way around it. Just disable the VooDoo Lagfix and system lagfix. Download perfectly afterwards. Defintely beats reverting to older markets and the methods described. Although this worked for me, hopefully someone will find luck with the methods you all posted. But yeah I tried everything besides reverting to the market and enabling a script change. That was going to be my last option.

Good to hear u managed to get it work, btw could u pls check if Third Blade downloads without an error. Thx

The item boot.emmc.win could not be read.

formatted and repaired everything in TWRP
I thought I was having problems with my USB c otg so I took it back. Now I'm getting this message just trying to copy and paste the twrp backup on my internal storage as well. When I move it with a file explorer app it fails. When I move it with the built in storage explorer it moves it but its a 0 byte file. Is it a TWRP issue or a CM13 issue or OnePlus issue?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Using the file manager in twrp I can copy and paste the file just fine. I'm on my second different USB c OTG and it's the same problem. boot.emmc.win from my TWRP backup just won't copy over and it even erases everything off my flash drive when failing to transfer. Anyone else have this issue?

I have that issue, too.
Cant find any solution

belek1979 said:
I have that issue, too.
Cant find any solution
Click to expand...
Click to collapse
Me either it's scary enough to stop me from even plugging in my otg storage completely. 1 cable OK maybe, 2 cables, now we have a serious problem and I'm not trying to lose anymore data.

It's a bug in TWRP that makes the file get created with the wrong permissions. (You don't see this if you look at the permissions in the normal place because of how mounting works on Android.) See https://github.com/TeamWin/Team-Win-Recovery-Project/issues/749 for details.

Any chance it gets fixed? That message was 5 months ago. It would be nice to be able to backup to USB otg without everything getting erased.

954wrecker said:
It would be nice to be able to backup to USB otg without everything getting erased.
Click to expand...
Click to collapse
This never leads to anything being erased, and you can easily work around it by fixing the permissions in TWRP.

When Im moving it with the built in file manager or fx explorer it erases everything off my otg flash storage. 50% of the time it erases everything the other 50% of the time it simply copies it as a 0 byte file.

954wrecker said:
When Im moving it with the built in file manager or fx explorer it erases everything off my otg flash storage.
Click to expand...
Click to collapse
That sounds like an unrelated issue.

I think it's the exact same issue I don't think it's a coincidence its always after it gets to that exact file everytime
I was just hoping I didn't have to manually change permissions in recovery, just to be safe in case I ever forgot.

In recovery > ADB I can copy that file to PC without any problems

Yeah I can do it anyplace but when booted into the phone system. It's getting fixed soon so I won't have to worry anymore.

Any hope for me?

I have nothing but bootloader. No system. No recovery. I've attached a screenshot. Do I have any hope?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You should be fine, because your device is unlocked. The only way you likely would have screwed yourself is if the OEM Unlocking toggle in Developer Options within Android was turned off.
EDIT: Using Fastboot you should be able to flash TWRP, which will give you your recovery. From there, flash a ROM and you should be good.

spastico said:
I have nothing but bootloader. No system. No recovery. I've attached a screenshot. Do I have any hope?
Click to expand...
Click to collapse
Go here DL the latest shamu factory image and follow the instructions. It will delete everything though.

Thanks guys. I'll let you know how it goes.
I'll be using a Mac.

Still struggling, but made a little progress.
I'm using a mac with terminal.
I don't know the terminal commands, but searching around the forums By doing this: ./fastboot boot twrp.img I now have twrp recovery working. But I still can't figure out how to flash.
Browsing around my nexus using twrp, it looks like I have no system partition.
Any more advice?

Woohoo!
Reading these forums, I figured out how to sideload the rom using ./adp with twrp sideload adb.
Back up and running.
All of this started while I was trying to switch from SuperSU to Magisk.
I still want to move to Magisk, but I obviously need to do some more reading.

For some reason I couldn't get the factory images to sideload. It kept saying invalid zip. So I sideloaded PureNexus.
All is good, but I just don't have a radio.
Off to do more reading.

Got a radio and posting from my Nexus.
Thanks again guys.
./fastboot flash radio radio.img

Great read, seeing the progress reported on like that. Thanks for updating.
If you ever want to move to the stock factory image, you don't sideload it. You'll need to run the flash-all.bat file (edit it and remove the -w flag to keep your data) or unpack it and use fastboot to flash each separate image (skip userdata and if you want to have TWRP installed to your device also recovery).
And if you have further issues with getting Magisk running, check out the Magisk guide.

@spastico @Didgeridoohan
To sideload a stock image on an N6, you have to use a full OTA image as compared to using fastboot flash (or the flashall.bat) with a Google factory image.
The instructions for each are well written right on the linked page from google.
@spastico, you commented that with TWRP booted, you didn't see a system partition. System is not mounted in TWRP, but you can manually mount it if you choose. As you discovered, mounting isn't necessary to flash an image.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

Awesome! I keep forgetting about those full OTAs. They weren't around when I used stock factory images on my Nexus...

Thanks for the additional advice.

Phone does not recognise encrypted storage, please help!

Hi,
There is this bug on LOS16 that if the pop up camera is up and then the device switches off, the camera stays up permanently until a stock rom is reflashed. I had this issue before, so I restored a backup I made on MIUI 10.3.16 using TWRP, but the device was stuck in a bootloop, and the camera was still stuck, so after restoring different backups I made, I decided to finally use MiFlash to fastboot flash MIUI 10.3.16, and I chose the 'keep user data' option, however this also bootlooped and went into MIUI recovery. I reflashed TWRP and now I face this issue:
TWRP does not recognise that my phone is encrypted, and does not ask for my password, so I can see that my files are here, but they have random folder and file names. (example shown below)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I managed to get MIUI running, however it does not ask me for my password, only my Mi account password.
I restored a LOS16 backup I made ages ago, and that also does not ask me for my password - the files I see in the file manager are all encrypted like TWRP.
I attempted the 'twrp decrypt' command, but that does not work either.
I attempted flashing backups and custom roms from a USB, using PitchBlack recovery, OrangeFox, and two TWRP versions.
All I want is for either a recovery or a rom to ask for my unlock password, so it can use that to decrypt my files.
I am not 100% sure if using MiFlash is what caused this, but is there anything else I could try? Are all my files gone? I cannot copy my encrypted files over to my PC and Windows returns an error when trying to do so. Are there any 3rd party tools I can use to decrypt my stuff?
I know I could just wipe my storage and start again, but I do not really want to do that until I know for sure that my files are gone.
I was thinking that MiFlash wiped the decryption keys from my device, but wouldn't a backup restore them?
If it is not possible to save my files, could someone explain why, so I do not make the same mistake again?
Any help would be appreciated.

Format Data, you cant go from miui to aosp or vice versa without doing that. backup your data to pc before or whatever cuz it wipes all internal.

Best thing to do is to fastboot flash again, but use the clean all option.
It's never a good idea to dirty flash when doing anything other than updating a ROM. You might sometimes be OK if flashing from one AOSP ROM to another AOSP ROM.
If your going from MIUI to a custom ROM, or from a custom ROM to MIUI, then it's not worth the aggro you'll most likely get by dirty flashing. Just spend the extra time backing up your data and save the headache.
As for the data, try installing a different TWRP and see if that will then ask for a password to decrypt the phone, before you do a clean install of MIUI.