Develop Bugs

(Problem) system uid's inconsistent

Hey guys,just tried Tod flash the New codenameandroid Rom,but i geht a weird message after the reboot. Your system uid's are inconsistent.you need zog wipe your data partition unless your device will be unavailable. and just a button with i'm feeling lucky.tried Tod Format /data but it didnt help.
Also tried other Roms but same Problem.
After that i wanted Tod restore a backup via cwm but it stopped with: error restoring /data.
Could both relate To thr same issue?
I really dont know what to do now.
I googled the Problem but didnt find a real fix for that.
Hope someone has an idea.
Cheers
Gesendet von meinem Galaxy Nexus mit Tapatalk 2

try mount /data in recovery, wipe data/factory reset, reflash rom.
Sent from my i9250

Probably the cleanest solution HERE

Try flashing the factory image over fastboot. Make sure your device is unlocked, adb is installed on your computer, and your device is connected to your computer booted into fastboot mode. On the computer, load fastboot and type: fastboot erase system, then: fastboot erase data,and at last: fastboot erase cache. Then install the factory image by extracting it and running the flash-all script. If you still need help, see the google factory image webpage.

[Q] Hardware navigation buttons do not work on some ROMS after clean install

Hi,
I'm finding with some ROMs (SlimBean, ProBAM, CM Domination) after an install on my HOX that the hardware navigation keys don't work anymore. I have to enable the soft keys in order to be able to use the phone - obviously not desirable as it wastes screen space.
I've done a crapload of googling, searching the forums, etc and can only find info on disabling the buttons. Is there some obscure setting I am missing somewhere?
The process I use is the same as is recommended on most of the other posts:
- fastboot erase cache
- fastboot flash boot boot.img (of the rom I am installing)
- in CWM, delete userdata, format cache/dalvik
- install rom
- reboot
When the phone boots up - straight away the capacitive buttons no longer work.
Reflash with a different ROM (CM10, Blade) and they are fine.
Can anyone help?
Thanks

I've had that happen on probam/slimbean if I don't flash Gapps.
Sent from my HTC One X using Tapatalk 4 Beta

sinkster said:
I've had that happen on probam/slimbean if I don't flash Gapps.
Sent from my HTC One X using Tapatalk 4 Beta
Click to expand...
Click to collapse
Aha - thanks for the suggestion, I'll give it a go. From memory I probably hadn't installed Gapps at that stage since I was just checking the ROM out..
thanks man

Gapps would have no bearing on such a problem, coincidence. And to prove a point, gapps are included in the ProBAM rom and the fault still occurred. I would suggest you change slightly the method of wiping between roms.
From CWM recovery, format data,system and cache. Then mount usb storage and format the sdcard to fat32 from your pc or laptop, but change the allocation unit size from 16 to 32 in the dropdown. Then while usb is mounted copy over the rom, and gapps if required. Just to be sure wipe dalvik cache in recovery then reboot the bootloader and flash boot image in fastboot and fastboot erase cache.
Very important to erase cache in fastboot.
Once that is done, back to recovery and flash rom and gapps if required and your done. This is the method I use every day and never have a problem.
Just re-read OP and I noticed that you fastboot erase cache before flashing boot image, you must also erase cache after flashing boot.
sent from my shorts

nogotaclue said:
Gapps would have no bearing on such a problem, coincidence. And to prove a point, gapps are included in the ProBAM rom and the fault still occurred. I would suggest you change slightly the method of wiping between roms.
From CWM recovery, format data,system and cache. Then mount usb storage and format the sdcard to fat32 from your pc or laptop, but change the allocation unit size from 16 to 32 in the dropdown. Then while usb is mounted copy over the rom, and gapps if required. Just to be sure wipe dalvik cache in recovery then reboot the bootloader and flash boot image in fastboot and fastboot erase cache.
Very important to erase cache in fastboot.
Once that is done, back to recovery and flash rom and gapps if required and your done. This is the method I use every day and never have a problem.
Just re-read OP and I noticed that you fastboot erase cache before flashing boot image, you must also erase cache after flashing boot.
sent from my shorts
Click to expand...
Click to collapse
notgotaclue, thanks for the detailed response - I will most definitely give this a go when I get some time over the next few days. Cheers mate

@nOtgotaclue: I went through your process and it did work for me with CM10 Domination - but not ProBam or Slimbean, they still had the same problem with hardware keys not working.
I've ended up flashing another kernel (TripNDroid v15 AOSP) and it has fixed the issue (for SB at least, yet to try it on ProBam).
Thx again for your help

[Q] Flashed 4.3 - What happened to my GNex ?

Hi All,
two days back i flashed the 4.3 factory image (because the OTA was downloaded but installation resulted twice in Robot with the red triangle and the error message "error"), rooted, restored the apps/settings with Titanium Backup.
Yesterday the device behaved normal.
This morning the device got no GPS fix and i restarted the device.
Since then i experience these strange things:
- No Notifications
- No QuickSetings
- Not able to receive incoming calls (SIM card is working in other phone)
- Home button triggers vibration and shows optical feedback, but doesn't switch back to the home screen
- "Shutdown dialog" only shows option for Shutdown. No option to change sound profile, flight mode etc
- No Screen-Lock
Wiped the cache partition and the dalvik cache - Without success.
Can anybody help me to heal my GNex ?

Yes, do this:
Fastboot erase boot
Fastboot erase recovery
Fastboot format cache
Fastboot format system
Fastboot format userdata
Then flash a factory image and don't use your titanium backup.
Sent from my Galaxy Nexus using xda premium

Judge584 said:
Yes, do this:
Fastboot erase boot
Fastboot erase recovery
Fastboot format cache
Fastboot format system
Fastboot format userdata
Then flash a factory image and don't use your titanium backup.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
you can restore apps, but do not restore system data using TitaniumBackup. if you restore from a google account then most of your settings will be restored anyway. when you do restore however quickly go to the play store and cancel all the downloads, then restore the apps from Titanium

[Guide] How to Remove Device Encryption to Flash Custom ROMs

The Issue
The device does not allow to use the newly flashed Custom ROM as it is Encrypted thereby asking for Password every time the phone boots up and wiping Data Partition with a Custom Recovery also does not work.
The Solution
Step 1 - Type anything as Password when the device asks for it after booting up. Be Quick as the device will shut down if you don't type anything within a few seconds.
Step 2 - Check whether it says Decryption was successful but the data is corrupted and also instructs to do a factory reset by tapping the Reset button. If Yes then go to the next step as the subsequent steps will resolve the issue. If No then this guide can not help you.
Step 3 - Do not touch that Reset button and reboot the device to Recovery by long pressing the Power button and then pressing Power and Volume Down simultaneously and choosing to go to Recovery from the Fastboot/Bootloader Menu.
Step 4 - Now connect the phone to your PC and transfer everything from your internal storage (if you didn't do it before flashing the Custom ROM) using MTP as the next steps will wipe the internal storage. Eject your SD Card from the device.
Step 5 - Download the Platform Tools from the link : [url]https://drive.google.com/open?id=1LEcF5iAjRdno2_aPKv9DYdOYtviC5xB7[/URL] and after extracting the folder place it in the C drive.
Step 6 - Install Motorola Device Manager from the link : [url]https://drive.google.com/open?id=12k2joSx5G08oourGlYLdtLEdTuOC9CVb[/URL] on your PC.
Step 7 - Download the Stock Recovery from the link : [url]https://drive.google.com/file/d/1_gogMT_GgSvg6FKpe2q4Z51gh22ftUdt/view[/URL] and place it in the platform-tools folder.
Step 8 - Assuming that your phone is still connected to the PC go to the Fastboot/Bootloader menu on the device by using Reboot to Bootloader option from the Recovery.
Step 9 - Go to the platform-tools folder on the C drive of your PC and open a Command Prompt window there by holding Shift key while Right clicking on the mouse and choosing the option. Enter the command fastboot devices to ensure that your phone is connected to the PC.
Step 10 - Enter the command fastboot flash recovery recovery.img to flash the Stock Recovery on the phone.
Step 11 - Reboot the device and enter anything as Password when the device asks for it. Now tap the Reset button to do Factory Reset. The phone will reboot to Stock Recovery and ask you to perform Factory Reset. Choose Yes to proceed and it will take a few seconds to do so. Voila!!! Your phone is successfully Decrypted and now you can boot into the Custom ROM you flashed.
Step 12 - As the phone is already Decrypted there is no need to keep the Stock Recovery. You can flash the Custom Recovery of your choice by going to the proper website and following the instructions to flash it on your device.
N.B : It took me a couple of hours to figure out the solution to this issue when I faced it and I wrote this guide so that it will help people who face the same issue in future. A Thanks! is much appreciated .

I work with "format data" in twrp

kuzo said:
I work with "format data" in twrp
Click to expand...
Click to collapse
That didn't work in my case.
Otherwise it's the easiest way to do so.

I also do not work the "format data" the first time. you have to do it once and gives error, then restart , go to twrp and do it again and there if it works. and reinstall the rom again ... after that you can change rom normally

kuzo said:
I also do not work the "format data" the first time. you have to do it once and gives error, then restart , go to twrp and do it again and there if it works. and reinstall the rom again ... after that you can change rom normally
Click to expand...
Click to collapse
I did it at least four or five times and was unsuccessful.
The phone was only booting up normally with Stock ROM but always asked for Password if any custom ROM was flashed.
Then only I came up with the idea I posted here and was successful to remove the encryption.

data on the phone will not be deleted?

whitetornado said:
data on the phone will not be deleted?
Click to expand...
Click to collapse
Step 7: ". . . the next steps will wipe the internal storage. Eject your SD Card from the device."
You should expect that data will be deleted.

whitetornado said:
data on the phone will not be deleted?
Click to expand...
Click to collapse
Yes!
Step 10 will wipe the Internal Storage and the SD Card too if it is still in the device.
It's a safe practice to eject the SD Card before doing any operations.

Is this still required for Pie ROMs? I've unlocked my bootloader, installed TWRP and called it a day, didn't have to change anything, but I'm still on stock Oreo.

io_gh0st said:
Is this still required for Pie ROMs? I've unlocked my bootloader, installed TWRP and called it a day, didn't have to change anything, but I'm still on stock Oreo.
Click to expand...
Click to collapse
If you're still on stock and haven't flashed any custom ROMs in the past or decrypted your data by using the "format data" command in TWRP after unlocking the BL (like I did) your data partition should be still encrypted. Most custom ROMs, regardless if they're Oreo or Pie don't work with an encrypted data partition. If the developer of the ROM you'd like to flash doesn't recommend anything else you can decrypt by using the format data option in TWRP (the one you have to confirm with "yes") or maybe by following this guide, for me that was never necessary, you just may have to use "format data" twice to make it stick.
To prevent your system from re-encrypting you can flash magisk or use a disabled dm verity force encrypt zip:
https://yadi.sk/d/HLr5vjnkA8gaqw
This one can be found on
https://zackptg5.com/android.php
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
If you're still on stock and haven't flashed any custom ROMs in the past or decrypted your data by using the "format data" command in TWRP after unlocking the BL (like I did) your data partition should be still encrypted.
Click to expand...
Click to collapse
The only time I've formatted /data was when I unlocked my bootloader. Immediately after this I've flashed TWRP, booted into it, installed magisk and restarted my device. It didn't asked for password or anything, this is why I'm confused. Since I haven't formatted using TWRP, it should be encrypted, right?
Wolfcity said:
Most custom ROMs, regardless if they're Oreo or Pie don't work with an encrypted data partition. If the developer of the ROM you'd like to flash doesn't recommend anything else you can decrypt by using the format data option in TWRP (the one you have to confirm with "yes") or maybe by following this guide, for me that was never necessary, you just may have to use "format data" twice to make it stick.
To prevent your system from re-encrypting you can flash magisk or use a disabled dm verity force encrypt zip:
https://yadi.sk/d/HLr5vjnkA8gaqw
This one can be found on
https://zackptg5.com/android.php
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
So since I installed magisk, then it shouldn't be encrypted, is that it? Sorry to sound soo noobish, but its been a while that I'm not flashing stuff and the last time I would just flash anything with no issues with encryption.

io_gh0st said:
The only time I've formatted /data was when I unlocked my bootloader. Immediately after this I've flashed TWRP, booted into it, installed magisk and restarted my device. It didn't asked for password or anything, this is why I'm confused. Since I haven't formatted using TWRP, it should be encrypted, right?
So since I installed magisk, then it shouldn't be encrypted, is that it? Sorry to sound soo noobish, but its been a while that I'm not flashing stuff and the last time I would just flash anything with no issues with encryption.
Click to expand...
Click to collapse
If you look into Settings->Security (see attached screenshots) what do you see there? (Mine is rooted and decrypted).
Edit: Check screenshots in the next post
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
If you look into Settings->Security (see attached screenshots) what do you see there? (Mine is rooted and decrypted).
Click to expand...
Click to collapse
Sorry, wrong screenshots.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
If you look into Settings->Security (see attached screenshots) what do you see there? (Mine is rooted and decrypted).
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
It shows that my device is encrypted. So, to decrypt it, I have to wipe /data from TWRP, right? To make sure that it won't get encrypted again I have to wipe twice, or just flash the script you linked?

io_gh0st said:
It shows that my device is encrypted. So, to decrypt it, I have to wipe /data from TWRP, right? To make sure that it won't get encrypted again I have to wipe twice, or just flash the script you linked?
Click to expand...
Click to collapse
To decrypt it format/ data (not wipe, that's not enough, it's the option where you have to confirm with "yes"). As I did that I formatted data and after that flashed magisk. It doesn't work at first attempt so I went into TWRP and did it again.
Normally magisk should prevent your device from re - encrypting, if not flash the attached zip.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
To decrypt it format/ data (not wipe, that's not enough, it's the option where you have to confirm with "yes"). As I did that I formatted data and after that flashed magisk. It doesn't work at first attempt so I went into TWRP and did it again.
Normally magisk should prevent your device from re - encrypting, if not flash the attached zip.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
By 'the attached zip' I believe you meant the one you've talked about a few posts ago?

io_gh0st said:
By 'the attached zip' I believe you meant the one you've talked about a few posts ago?
Click to expand...
Click to collapse
Exactly. Here's the latest one:
https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
Sent from my Moto G5 Plus using XDA Labs

Link is broken but I got the one from the other link made just a few months prior... Was there much a difference between that and the latest?
Thanks

itcanbdone said:
Link is broken but I got the one from the other link made just a few months prior... Was there much a difference between that and the latest?
Thanks
Click to expand...
Click to collapse
@Zackptg5 seems to have changed his side a bit, here's the actual link:
https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
To decrypt it format/ data (not wipe, that's not enough, it's the option where you have to confirm with "yes"). As I did that I formatted data and after that flashed magisk. It doesn't work at first attempt so I went into TWRP and did it again.
Normally magisk should prevent your device from re - encrypting, if not flash the attached zip.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Do I need to select "Format Data" under "Wipe" to decrypt it? On TWRP, I see Wipe -> Format Data. If yes, do I need to remove SD card that has my system backup and custom ROM? Thanks.
---------- Post added at 03:14 AM ---------- Previous post was at 03:02 AM ----------
kuzo said:
I also do not work the "format data" the first time. you have to do it once and gives error, then restart , go to twrp and do it again and there if it works. and reinstall the rom again ... after that you can change rom normally
Click to expand...
Click to collapse
Are you referring to the "Format Data" tab under "Wipe" (that is, Wipe -> Format Data next to Advanced Wipe)? If yes, do I need to take out a SD card where I have a backup and custom ROM? Thanks.

Stuck at boot animation on multiple custom ROMs [ Redmi Note 8 ] [ ginkgo ]

I thought of having a new ROM installed on my phone and it is not the first time I'm doing it.
Device: Redmi Note 8 [ ginkgo ]
These are the steps that I followed:
Moving to bootloader and rebooting to TWRP recovery
Wiping the cache, system, data and dalvik cache
Moving to install option and installing the CustomROM1.zip from the Internal Storage
But the screen is stuck at boot animation
Using my laptop I tried to do the following:
5.1. fastboot erase system and fastboot erase recovery
5.2. Flashed TWRP recovery again using fastboot flash recover twrp.img
Moved the CustomROM2.zip file in the Internal Storage and tried to flash resulted in boot animation loop
I even tried to ADB sideload and flash the zip but resulted in the same error.
CustomROM1 = Havoc-OS-v3.7-20200708-ginkgo-official.zip
CustomROM2 = AncientOS-CIVILIZATION-v3.0.1-ginkgo-PRIMEVAL-20200331-0828.zip
Any sort of help to get out of this would be totally appreciable. And thank in advance.

You have to format data in recovery (format where you have to type yes not wipe). Ideally do this before installing ROM.
So wipe everything, format data then install ROM

Tim-developer said:
You have to format data in recovery (format where you have to type yes not wipe). Ideally do this before installing ROM.
So wipe everything, format data then install ROM
Click to expand...
Click to collapse
I format
Dalvik / ART Cache
Cache
System
Vendor
Data
but same problem

arnobzit said:
I format
Dalvik / ART Cache
Cache
System
Vendor
Data
but same problem
Click to expand...
Click to collapse
That is the 'wipe' screen options. NOT the format screen options.
Please read again. What is said for you to do.
In twrp.
Go to wipe menu
At bottom press format
This gives you screen that says to format, type "yes"

mrmazak said:
That is the 'wipe' screen options. NOT the format screen options.
Please read again. What is said for you to do.
In twrp.
Go to wipe menu
At bottom press format
This gives you screen that says to format, type "yes"
Click to expand...
Click to collapse
Thanks a lot.......................problem solved.....................too much happy thanks brother

Tim-developer said:
You have to format data in recovery (format where you have to type yes not wipe). Ideally do this before installing ROM.
So wipe everything, format data then install ROM
Click to expand...
Click to collapse
Thanks you too

mrmazak said:
That is the 'wipe' screen options. NOT the format screen options.
Please read again. What is said for you to do.
In twrp.
Go to wipe menu
At bottom press format
This gives you screen that says to format, type "yes"
Click to expand...
Click to collapse
Hey bro I did but nothing goes well....
Look I was on stock miui 12.0.2.0 , my device is whyred.
And I was trying to flash a miui Rog port rom so I installed the custom recovery and format the data from advance wipe menu, and then I flashed the rom but it shows "error 7" .....and you know what happened then....

Adnaan21 said:
my device is whyred
Click to expand...
Click to collapse
Ask in whyred forums