Related
Ok this might sound retarded but I just installed a new rom (temasek's KANG)on my phone after some of you guys suggested it to me.
Anyways, it worked fine, but the ROM doesn't include Google play or Gmail app? wtf? Why would that not be included? I can't do anything without google play I can't install any of my apps...
I tried installed the APK files for google play and when I start it it says :
"You must add an account to the device to continue. Do you want to add one now ?" When I click Yes, the app just closes back to home screen....
The gmail app crashes in a similar way
I've on this for hours.. you can't imagine how much I've been messing with my phone for stuff to work properly and there is always something retarded like this not working... :|
edit:
also I can't seem to be able to delete apps, why is this?
You need to flash a separate addon called gapps which includes essential google files and the market (play store). Gmail is downloadable from market.
Download gapps from here and flash from recovery.
http://www.mediafire.com/download.php?115vksf8fc32ve6
I also installed the latest Temasek's build but I'm having a problem with battery drain. Back when I used stock based roms and horsepower kernel my phone would lose about 7% battery while it was idle during the night. Now I got to bed and when I wake up my phone has lost 20-30% of its battery. I know this isn't the right forum but since I can't post in dev section and Temasek has replied to this thread maybe I could get a little help?
Help, please!
I'm new here and the first ROM I've tried installing was RC1 91 but after I finished the procedure, my phone doesn´t leave LG home screen and rebooting. What did I do wrong?
Steps:
- Root;
- Download the ROM;
- Copy in external memory;
- Power off the phone;
- Boot in recovery;
- Backup current ROM;
- Wipe cache partition and wipe data/factory reset;
- Wipe dalvik cache
- Finally, flash ROM and reboot.
And the restore isn´t work too.
For those who have myphone uno plss help me it won't update
If someone kind enough to share the link of
ota zip I can just flash It in stock recovery
gabisonfire98 said:
For those who have myphone uno plss help me it won't update
If someone kind enough to share the link of
ota zip I can just flash It in stock recovery
Click to expand...
Click to collapse
Ok lmy47o patch zip is just 23 mb
guys,
i also have a myphone uno rooted but no custom recovery as of now. i had no problem updating the previous system updates. the recent one came in just fine. then now, the phone (every time it connects to wi-fi) would offer a new sys update. but when this is applied, the procedure results with an ERROR. i wonder if you guys are getting similar results.
bodega1968 said:
guys,
i also have a myphone uno rooted but no custom recovery as of now. i had no problem updating the previous system updates. the recent one came in just fine. then now, the phone (every time it connects to wi-fi) would offer a new sys update. but when this is applied, the procedure results with an ERROR. i wonder if you guys are getting similar results.
Click to expand...
Click to collapse
i have the same problem. my current system is version is 5.1.1. i'm using stock recovery. my phone is rooted using superSU.
guys,
i've recently just tried doing a FACTORY RESET (myPhone UNO), Android 5.1.1, and to no avail: still an error when updated a 18MB update. either the update file has an error or my rooted settings are preventing a clean OTA update.
bodega1968
dude,
I finally resolved the update issue. will give you the instructions soon. got to go... but will get back to you once I have composed the procedures... I believe the cause is having rooted and changed some data in the system cache.
bod98
SOLVING [one solution] OTA PROBLEMS in myPhone UNO (sprout)
Background.
Phone model: myPhone UNO (sprout hardware)
Android 5.1.1
*Problem: OTA update failure.
*Log message:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
VErifying current system...
"/system/bin/app_process32" has unexpected contents.
E:Eror in 0/cache/recovery/block.map
(Status 7)
*Possible Cause: Occurred after rooting with anil293 (Android Root Kit here). I’m not saying that this program is bad, but only to caution anyone who may want to root and possibly lose OTA updates.
Solution. (*This worked for me since I had done a previous NANDROID backup (NB) of the phone prior to any system changes (i.e. rooting, custom recovery, etc.). The following steps were written to help those who may not be too familiar with some basic non-GUI (graphic user interface) commands in order to restore one’s device to it’s original and working condition.
Step 1: I chanced upon DEVAM30’s wonderful contribution on how to run RECOVERY without installing it ‘permanently’ into the phone. Check out his page here. This allowed me to make my NB. Download from this page the PHILZ8.img (*This will be the 'virtual' recovery file which you will boot into in order to make your NB)
Step 2: Assuming that you have a previous NB, this (huge file) should be located in the clockworkmod folder in your SDCard. You will refer to this once you have successfully booted in the PHILZ8 recovery.
Step 3: Set your phone to allow USB Debugging. (*This can be done in the Developer’s Section) NOTE: Prior to all this, make sure you BACKUP your critical personal files (i.e. contacts, SMS, data, etc. GOOGLE this to find out how to backup your personal data. The next steps will ERASE everything in your phone. I will not be responsible for any data lose or the bricking of your phone.
Step 4: Boot your device in FASTBOOT mode (FM). (*Power OFF the device, then after 5-10 seconds, press POWER ON + VOL UP. When screen turns on, release VOL UP followed by POWER ON). MENU comes up. Use VOL UP to SCROLL among the choices, and when you have selected FM, press VOL DOWN and the phone should pretty much be in FMode.
Step 5: While your phone is in FM. In your PC you should have ADB/FASTBOOT functions already set up. Check the link here on how to install and work in fastboot mode. When you have properly installed everything in this STEP, you must copy the PHILZ8.img into the adb/fastboot folder. You may rename it into something simpler like recovery.img
Step 6: Connect your phone (*already in FM) to the PC.
Step 7: In your PC, in adb/fastboot folder (*check if your device is connected properly – adb devices or fastboot devices). If your device is detected some number should appear in the screen. Then you type: fastboot boot philz8.img or the name you gave to the .img file.
Step 8: Wait for the PHILZ8 recovery to kick in. Once it boots up you’re now ready to do a RESTORE of your NB. You will see a TOUCH menu in your screen. You will carry out two important steps. (a) wipe the cache and (b) restore the NB image from the SDCard.
Step 9: Choose the wipe menu. In my case, I chose to WIPE (*Choose wipe cache options) cache and the dalvik cache. The former one will take a while, and the latter only takes a few seconds. Once done, +++GO BACK++ to the main menu and then TAP on RESTORE. It will ask you where you will restore the image from. Choose SD card. If it doesn’t do this automatically, you may have to navigate to the clockworkmod folder where your NB image is located. Choose that image and you’re good to go!
Step 10: Once the entire procedure is over (*be patient, it may take some time to finish the entire restoring of the image), you will now opt to REBOOT the SYSTEM. Now, this is critical (in my opinion) because the virtual recovery (PHILZ8) will ask if you wish to install root. Choose NO! Otherwise, it may make some changes in the system settings that will conflict with the OTA updates we want to work.
The device will reboot and you will pretty much be back to its original settings (more than a simple factory reset). And your phone will update a few times and no error will come out.
For those of your who don’t have or have not been able to make a CLEAN NB, I uploaded this RAW image phone (it does not contain any personal data or programs) . You may download it here.
bod68
*updated 9IX15
LINK to my NANDROID BACKUP
gabisonfire98 said:
Ok lmy47o patch zip is just 23 mb
Click to expand...
Click to collapse
gabisonfire98,
dude, if you're patient enough to follow my 'SOLUTION' to regaining OTA updates, check out the procedure i outlined below, september 4, i believe it was.
the link to my NANDROID BACKUP which could be RESTORED to your device (*Using the wonderful procedure outlined by DEVAM03)!
Download the image here
Just email me if you find some of the instructions confusing, just email me.
bod68
Recently got a kindle fire 7" and wanted to root it and flash a rom onto it, but having troubles with that part.
Using this guide https://forum.xda-developers.com/amazon-fire/general/root-t3471289
Rom:
https://forum.xda-developers.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714
Usb debugging/install from unknown sources/kingroot done
Process:
Stock firmware (5.3.1) after amazon recovery tool
Kingroot root
Supersu-me
Update su
Tried once with and without rebooting
Rootjunky super tool, installed google play store
Install Flashfire (from play store) ver. .55
Also tried with an apk file ^ (ver. .53)
Set up a wipe for (dalvik, system, 3rd party)
Tried with and without mounting
Crashes after and starts a boot loop going into the amazon logo only
I'm new in regards for rooting, sorry if I'm a bit slow with this.
Thanks in advance for the help!
Check the rom you downloaded is not corrupted, verify hash value. Store it on the tablet not an sd card when flashing.
Reboot the tablet after you install supersu and flashfire. Before you flash the rom, make sure you remove the usb cable.
Don't use auto mount. Make sure you follow the flashfire instructions below. Make sure to move wipe to top of the order !
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear
Mr McBoatface said:
Check the rom you downloaded is not corrupted, verify hash value. Store it on the tablet not an sd card when flashing.
Reboot the tablet after you install supersu and flashfire. Before you flash the rom, make sure you remove the usb cable.
Don't use auto mount. Make sure you follow the flashfire instructions below. Make sure to move wipe to top of the order !
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear
Click to expand...
Click to collapse
Still nothing, leads me into another boot loop.
New things:
Rebooted after installing flash fire
Verified the hash
Move the rom onto the internal drive (flashed from there)
No Automount
Any other ideas?
IIRC, I had similar issues when first installing a ROM onto my Fire, but that was many months ago, and my memory is a bit fuzzy... IIRC, it had to do with the location of the ZIP. I believe I had to put the zip on my SD card, and then when I wiped my system, I also wiped my data volume. Speaking of wiping...
Shugumi said:
Process:
Stock firmware (5.3.1) after amazon recovery tool
Kingroot root
Supersu-me
Update su
Tried once with and without rebooting
Rootjunky super tool, installed google play store
Install Flashfire (from play store) ver. .55
Also tried with an apk file ^ (ver. .53)
Set up a wipe for (dalvik, system, 3rd party)
Click to expand...
Click to collapse
Maybe I'm reading this wrong, but are you saying you're installing the zip, and THEN wiping the system? That's going to erase the installation you just flashed. You should be wiping the system, and THEN flashing the zip. The original instructions are here:
ggow said:
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear
Click to expand...
Click to collapse
IIRC, if you put the ZIP onto the internal storage, it puts it in the Data volume, which is then going to be wiped. FF wipes the data, and then can't find the zip (because it just deleted everything...). Does that make sense?
crazyates said:
IIRC, I had similar issues when first installing a ROM onto my Fire, but that was many months ago, and my memory is a bit fuzzy... IIRC, it had to do with the location of the ZIP. I believe I had to put the zip on my SD card, and then when I wiped my system, I also wiped my data volume. Speaking of wiping...
Maybe I'm reading this wrong, but are you saying you're installing the zip, and THEN wiping the system? That's going to erase the installation you just flashed. You should be wiping the system, and THEN flashing the zip. The original instructions are here:
IIRC, if you put the ZIP onto the internal storage, it puts it in the Data volume, which is then going to be wiped. FF wipes the data, and then can't find the zip (because it just deleted everything...). Does that make sense?
Click to expand...
Click to collapse
Had the zip on storage and wiped before flash, nothing :/
Was kingroot fully removed and SuperSU correctly installed ? Are you using the latest nexus ROM dated Feb 2017 ?
Try again this time use fire flash 0.53 included in super tools. Don't install play store or upgrade SuperSU, use the SuperSU included in super tools. Again make sure you restart the tablet after installing SuperSU and after installing fire flash.
With flashfire 0.53 make sure automount is deselected. Include wipe cache options too.
So wipe System data, 3rd party apps, Dalvik cache and cache , flash the nexus ROM. Again make sure before you hit the flash button the wipe action is moved to the top of the list. Make sure no USB cable connected to the device too
In my experience 0.53 flashes really quick , 0.55.1 "can" show a black screen, you might think its failed but it's working in the background but might take 5 mins to flash.
0.53 sometimes fails to open and crashes but i have only seen that when it was used on a device with a custom ROM already flashed on it. It should be fine for flashing on the fire OS system.
Mr McBoatface said:
Was kingroot fully removed and SuperSU correctly installed ? Are you using the latest nexus ROM dated Feb 2017 ?
Try again this time use fire flash 0.53 included in super tools. Don't install play store or upgrade SuperSU, use the SuperSU included in super tools. Again make sure you restart the tablet after installing SuperSU and after installing fire flash.
With flashfire 0.53 make sure automount is deselected. Include wipe cache options too.
So wipe System data, 3rd party apps, Dalvik cache and cache , flash the nexus ROM. Again make sure before you hit the flash button the wipe action is moved to the top of the list. Make sure no USB cable connected to the device too
In my experience 0.53 flashes really quick , 0.55.1 "can" show a black screen, you might think its failed but it's working in the background but might take 5 mins to flash.
0.53 sometimes fails to open and crashes but i have only seen that when it was used on a device with a custom ROM already flashed on it. It should be fine for flashing on the fire OS system.
Click to expand...
Click to collapse
I might disagree with a few things you said there...
You only have to remove KingRoot if you're using v5.0 or newer. If you can use 4.9.6 to root, which I believe is what the SuperTool uses, then you can download SuperSu from the play store, update SU binary, then uninstall KingRoot with no issues.
As far as FF is concerned, the ROM developer says 0.55.1 is required, so I wouldn't stray from that.
The only other thing I would recommend is using the not-newest version of the ROM. For the last 6 months, the ROM has been based on a 5.3.2 boot.img, and recently switched to a 5.1.4 boot.img. Maybe the newer firmwares don't like the downgrade? I would try the Feb-2-2017 version of the ROM and try again.
Steps:
Restore to stock 5.3.2 (NOT 5.3.2.1)
SuperTool to install KingRoot 4.9.6 & GPlay
Kingroot to root
Install SuerSU (newest) & FF (newest) from Gplay
Use SuperSu to update SU binary
Put Feb-2-2017 zip on SD card
Use FF to wipe System, Data, Cache, Dalvik, 3rd party apps, & then install zip from SD.
Let sit for 5-10 minutes & do it's thing.
Having 2 root managers is not a good idea.
Kingroot uses it's own su binaries which may cause problems and clash with SuperSU. Using the script in supertools is a better option as it replaces the superuser su binary with a SuperSU compatible one.
The version of flashfire shouldn't matter, but he is having issue so best to rule it out. The behavior of 0.53 is different to 0.55.1 . it flashes a lot quicker and is fine to use. I've used it several times in the last fortnight with the latest ROM.
The current ROM is fine, boot image and binary change won't cause the issue experienced here. The older ROMs are broken , in so far as either the camera or screen cast won't work. The latest ROM with the proven and stable binary is a better option, everything works
EDIT , also there are reports of several users losing supersuser seemingly random after upgrading to the latest SuperSU , hence why I suggested sticking with the current one on supertools.
I also suggested wiping cache, just incase an amazon update has downloaded while rooting and attempts to install at the same time at the nexus ROM is being flashed.
I have a Fire running Nexus Fire ROM (2/8/17), and my fiance has a Fire running stock 5.1.2 with root, OTA updates disabled, Nova Launcher, and Gplay Store. I wanted to flash hers from Stock to Fire Nexus, and ran into the same issues I had before.
FF was supposed to Wipe System Data, 3rd party apps, Dalvik, and Cache, then install zip, then inject SuperSU. When it did the wipe, it deleted the ZIP on the Internal Store, so FF sat there for 15 minutes not doing anything, and I didn't have a system to reboot into anymore.
I had to do a sideload recovery of 5.1.2, root, install FF, and do all the same steps as above, but this time install the zip from an SD card. Worked great.
Mr McBoatface said:
Kingroot uses it's own su binaries which may cause problems and clash with SuperSU. Using the script in supertools is a better option as it replaces the superuser su binary with a SuperSU compatible one.
Click to expand...
Click to collapse
I used the SuperTool to root, and this is what I did also. Afterwards, I used the Gplay to update the SuperSU, which updated to the newest binary. I haven't seen any problems as of yet.
Unless internal storage was selected that shouldn't have happened, unfortunate that it did for you. The only time I've seen FF hang was when wipe was in the wrong order or when the USB cable was connected..... Don't know why the USB cable has that effect but I've seen it on 2 devices, other people have not had any problems.
Not seen the issue with SuperSU myself but read plenty of reports about it.
It seems users are affected by several random issues even if following the same instructions.
@Shugumi any update ?
Been swapping out roms and trying each suggestion but its been giving me the same boot loop.
So, I returned the kindle fire, and am waiting to try it on the new coming device :/, but thanks to everybody that replied to this thread. Even though we didn't get to root my kindle, it was great help! Thanks everybody.
NOTICE: crDroid 7.x (Android 11) is now in maintenance-only release mode, and will probably be End-Of-Life'd soon.
I'll be merging monthly Android Security Bulletins from upstream as they're available, and pushing releases, but they're blind builds at this point and I don't have time to troubleshoot them any longer.
Please consider updating to crDroid 9.x (Android 13):
crDroid 9.x XDA thread - OP 6/6T
{
"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"
}
crDroid is built on top of LineageOS, and is designed to increase performance and reliability over stock Android for your device, while also attempting to bring you many of the best features in existence today.
Features
A quick glossary and primer on flashing & slots for A/B devices (like ours):
Spoiler: Show/Hide
- "Clean flash": Removing device protection & clearing user settings before installing a bootable system install zip (usually by either wiping or formatting data, see below).
- "Dirty flash": Flashing a ROM zip (usually upgrading to new version, sometimes just re-flashing the existing one) without wiping data or anything first.
- "Wipe data": Synonymous with "factory reset", accomplished from TWRP recovery by selecting "Wipe", then performing the "Slide to factory reset". Clears user data without erasing any partitions, removing encryption, or deleting contents of internal storage.
- "Format data": Formats the data partition itself, resets all file-based encryption keys, loses all contents of internal storage, and in fact deletes all "user 0" directories (this has some implications for internal storage before & after first boot).
- "User 0" directories are a series of directories that store userdata for the primary user, "Owner", and get created in various places throughout the filesystem on first system boot if they don't exist already. Anything you copy to "internal storage" while booted in recovery after "formatting data" will actually be copied to /data/media/ instead of /data/media/0/, and will become invisible to regular file browsing after first boot once the system has created /data/media/0, since the system will prefer to use that path for internal storage from then on (so you'll need a root file browser to delete things from /data/media, or just ADB sideload things instead of copying after formatting but before booting).
- "OTA package": Originally an abbreviation for "over the air", referring to how a software update could be delivered (as opposed to having to take your phone to a carrier's store for a firmware update via serial/USB connection). The common usage in Android circles is any installation zip file that actually includes a bootable system.
- Some partitions are duplicated (system, vendor, boot, and probably a couple others, but not data) and have a "slot A" & "slot B" copy.
- "Slot A" and "slot B" are absolute designations, but most installer zip scripts use the relative designations: "active" and "inactive". Whichever slot you're booted from currently is "active", and the other one is "inactive".
- Installing a zip file that's flagged as being an OTA package will 1) install the contents to the "inactive" slot, and then 2) flag the bootloader to switch which slot is considered "active" (and booted from) and "inactive" upon next reboot.
- The OxygenOS full OTA zip files and all custom ROM installer zip files are considered "OTA packages" and will trigger a slot switch on next boot after installation.
- You can install multiple OTA zip packages one after the other without rebooting in both the stock recovery and TWRP; they will all get installed into the correct partitions in the "inactive" slot, one on top of the other, and then it will swap active & inactive upon reboot.
- We don't use what are called "delta" updates, which can patch existing partitions by block or by file; we use full filesystem images. So for us, OTA zip packages are really just a bunch of partition filesystem image files all wrapped up into a "payload.bin" with some extra instructions & metadata/checksums, so when you flash a ROM, it overwrites entire partitions at a time instead of individual files or filesystem blocks within that partition. So if you've changed something in a partition like system that gets written as part of flashing an OTA zip, all your changes are gone. The only thing in the system partition afterward will be what was in the system.img that was included in the ROM zip payload.
- The partitions that crDroid, LineageOS, and most custom ROMs for OnePlus 6 & 6T install to when flashing are boot (contains recovery & kernel), dtbo, system, and vbmeta. Some ROMs (like Syberia) build the vendor partition from source instead of just trying to work with the existing OEM vendor partition, so they flash that one too when installing. So you definitely need to flash stock vendor before switching from Syberia or another source-built vendor ROM to one like Lineage or crDroid that uses prebuilt.
- "Prebuilt vendor" vs. "source-built" vendor partitions: when first trying to get a custom ROM working on a new device now that we have separate system & vendor partitions & Google's "Project Treble" is a thing, you'll often just leave the contents of the vendor partition alone, because that's where all the proprietary or device-specific stuff lives (manufacturer specific hardware drivers & interfaces, any DRM libraries, custom frameworks & selinux policies for talking to them), and you make a compatibility map of what framework versions you're compiling against in system and what vendor version they're compatible with or supersede or you overlay updated things that should replace stuff in the vendor partition and keep it in system_ext instead. But you're also limited in that if there are some things in vendor, you CAN'T work around it from the ROM side (like, OnePlus Camera working correctly). So often, once the basics are functioning, the goal is to move to building the contents of the vendor partition from source, because you then have the freedom to fix problems with sepolicy, library/framework mismatches, etc. and make things work with the custom ROM instead of only working with the OEM's flavor of Android, and you can still copy individual pre-compiled files from the stock vendor filesystem image if needed (like if there's no open-source equivalent for some driver). Unfortunately, OnePlus SDM845 (enchilada & fajita, the OP6 & OP6T) never got a proper source-built vendor bringup by the LineageOS team (upon which crDroid is based). And while Syberia has had source built vendor in Android 11 (possibly 10?), it was only done for enchilada and NOT fajita, it's not trivial to unroll & commonize what they've done to apply to other ROMs, and some of the proprietary files they keep are imported from other similar devices/similar chipsets rather than source-built (presumably because the OnePlus ones are modified in a weird way that the open-source components can't hook into, but still not ideal). So for fixing a lot of the issues we still face with lack of things working quite right, or hardware features not available in custom ROMs (especially compared to newer OnePlus devices like the 7, 8, or 9 series), we're kinda stuck, because you can't just implement it against the stock prebuilt vendor.
- "Updating firmware" simply means we're flashing updated contents from the manufacturer into all the OTHER partitions besides the ones that the ROM OTA zip touches. There are another dozen or more of those, besides system & boot, that the full OxygenOS OTA zip would normally write to when you install it. The contents of the system partition in custom ROMs for our device are generally built against a particular version of OxygenOS (mostly the contents of the OEM vendor partition), and we've recently had an entire major Android version update come through from OxygenOS. Some people are still on older firmware that is now dramatically different than what the current custom ROM was intended to deal with (that is, all the stuff from OxygenOS is still based on Android 10, while the ROM is expecting compatibility with Android 11), and while I tend to agree that OxygenOS 10 was better than the current state of OOS 11, that doesn't matter when you're talking about installing the custom ROM over it. So please, keep an eye out in the release notes for what the recommended/required firmware versions are, and remember to update (procedure below).
Notes on custom recoveries with OxygenOS 11 firmware:
Spoiler: Show/Hide
- My understanding (from people smarter than me) is that the android-11 tree of TWRP is kind of a mess at the moment. I had made some 3.6.0_11-0 unofficial builds for both enchilada & fajita, but now they don't even seem to boot and I don't know why. TWRP android-11 tree refuses to mount the system partition where it belongs, and so addon.d OTA survival scripts don't work correctly any longer (which means you're hosed if you use NikGapps and update while booted from a TWRP version ending in "11-0", or if you have Gapps installed as a module and forget to reboot recovery & re-flash Magisk after flashing an update from TWRP).
- Trying to `fastboot boot` an Android 9-based TWRP image (like official 3.5.2_9-0 twrp.img) after installing OxygenOS 11 doesn't work, and will drop you into Qualcomm Crash Dump mode. Don't try to flash it as your boot partion, either.
- Meanwhile, stock LineageOS-based recovery, for all its shortcomings, has working fastbootd (aka "Userspace fastboot", which is what happens when you go to "Advanced", then choose "Enter fastboot" and the background colors go from purple to orange) that lets you flash both slots at once and unlocks critical partitions, while the OnePlus OEM bootloader (where it says "Fastboot Mode" in a square, then goes to the big green "START" text over white & dark red terminal font type text) can't be used to flash every partition to update firmware. Personally, I still think of it as wannabe-class and not a "real" custom recovery until the Lineage team 1) implements userdata decryption so you can manage files in /data and install updates from internal storage, and 2) allows for a factory reset the way we've always all understood it ("wipe data") WITHOUT nuking the contents of internal storage for no good reason ("formatting data"). But since crDroid is LineageOS-based, it's what we've got, and fastbootd is the best way to update firmware.
- With all that being said, since it's likely TWRP will only get MORE broken with Android 12 looming large, we're officially only going to support the built-in LineageOS-based recovery & OTA updater moving forward, until things change dramatically. If you want to try different custom recoveries (new builds of TWRP, OrangeFox, PBRP, whatever), feel free; and let us know how it works! But you're on you're own doing that.
- And on the system update side, applying system OTA updates seems to work correctly using the built-in Updater tool (Settings > System > Updater) both with new OTA releases and when choosing a file from "Local Installation". It executes OTA survival scripts correctly from /system/addon.d/ as well. I've personally tested and it correctly preserved Magisk v23 canary and MindTheGapps & NikGapps (on tester fajita) and MinMicroG "system" install package on my daily driver enchilada.
- ...however it has an accidental dependency on Magisk, due to things beyond my control upstream in the ROM. Whoops. Won't work if you don't have Magisk installed.
- FLASHING the old official TWRP 3.5.2_9-0 INSTALLER zip (or newer) on top of OOS 11.x DOES seem to work for now, but you need to be in a recovery environment that allows you to flash that installer in the first place (either by booting into an already-installed TWRP recovery before updating firmware, or by having an Android 11 compatible recovery boot.img to be able to `fastboot boot`). I don't know if it'll keep working in Android 12 or with crDroid 8.
- Look, if you really want to stick with TWRP, I don't blame you. I made bootable Android 11 compatible TWRP images for enchilada & fajita back at 3.5.2, and they still work well enough to `fastboot boot` them and then flash the old official 3.5.2_9-0 installer zips. Look at the attachments at the end of post #2. Also, you may want to try one of Siddhesh's custom recoveries; they probably work even better.
- TL;DR: I prefer TWRP too but current official releases are kinda broken and it's a chore to get the old version installed correctly, so built-in LineageOS-based recovery and Updater app are the supported way to install & update moving forward.
Prerequisites:
- Make sure your bootloader is unlocked (and don't plan on relocking it ffs).
- Make sure you have a reasonably-current, working installation of android platform tools (adb & fastboot command line binaries & necessary drivers) on your computer, with a known-good USB cable (see links in post #2).
- Make sure you've downloaded the most recent full OxygenOS OTA installer zip (11.1.2.2), crDroid zip, matching crDroid boot.img, and whatever Magisk/GApps/microG installation packages you want to use to your computer (see links in post #2).
- Make sure you've backed up whatever data you want to keep to somewhere that's not on your phone; for a new install, we're going to format the data partition and you're going to lose everything from internal storage.
Let's get started!
Updating firmware:
- Reboot to bootloader (no USB cable connected).
- If you're not already using the stock (LineageOS-based) recovery, you'll need to `fastboot flash boot path/to/boot.img`, substituting in the path & filename for the current crDroid boot.img that you downloaded as part of the prerequisites.
- Reboot to bootloader again (actually loads new bootloader that you just flashed).
- Use Vol +/- buttons to select "Recovery mode" and press Pwr button to boot stock recovery.
- Tap "Advanced", then tap "Enter fastboot" (the already-selected first option).
- Follow the instructions for extracting the partition images from the official OxygenOS Updater full OTA zip you already downloaded using the "payload-dumper-go" utility, and flashing them one at a time, from https://wiki.lineageos.org/devices/enchilada/fw_update, except for the very last command ("fastboot reboot").
- Since those instructions were updated for Android 12, and this is still Android 11-based & depends on using the OxygenOS prebuilt vendor partition contents, you'll also need to run fastboot flash --slot=all vendor vendor.img at the end of the list of commands in the linked LineageOS Wiki article above.
- If you're only updating firmware and were already on crDroid, you can just "fastboot reboot" which will go back to system. If this is part of coming to crDroid from another ROM, continue with the instructions below.
First time installing crDroid to your OP6, coming from stock OxygenOS 11.x or another ROM (stock LOS-based recovery):
- Update to OxygenOS 11.1.2.2 firmware as described above if you haven't already.
- At the end of that procedure, (re)flash the crDroid boot.img to the `boot` partition of both slots, then reboot to recovery.
- Once you're rebooted into stock recovery, ADB sideload the crDroid installation zip. It might prompt you with "Install anyway?" on the phone, so don't just walk away from it.
- After the adb sideload has finished and the purple menu at the top comes back, hit the back arrow, then choose "Wipe data" (which WILL format internal storage -- you backed up as noted above, right?).
- Reboot to recovery (causes it to switch slots so any further installations will be on top of the slot that it just installed crDroid into).
- ADB sideload Magisk and/or any GApps packages you want to use. Please note that any time you install something via ADB sideloading, that the install file is technically renamed "sideload.zip" in transit by the ADB protocol, which might cause problems with installers that try to get too clever for their own good and alter behavior based on renaming the installation zip (like MinMicroG), so you might have to get even MORE clever with changing up installation order (like flash MinMicroG/GApps before Magisk so it won't install as a module. I dunno, talk to the package installer authors to get them to just build multiple packages or talk to the LineageOS devs to allow you to decrypt internal storage, copy stuff to internal storage via MTP, and install stuff from internal storage like a proper custom recovery (or at least maybe `adb push` to an unencrypted temp dir in the data partition).
- Reboot system.
- ???
- Profit!
OTA updating from Updater app with OOS 11.x firmware (recommended):
- This is the preferred way now. You just go to Settings > System > Updater, and... install an update. It processes addon.d OTA survival scripts correctly (tested with Magisk, MinMicroG, MindTheGapps, and NikGapps).
- Please note that there's currently an accidental depencency on Magisk being installed for this to work. I don't know if this will get fixed; that's definitely above my pay grade. This appears to have been fixed; huzzah!
- If you're trying to do a "Local Install" of the downloaded zip, please note you NEED to download on a computer & transfer to internal storage via USB cable; downloading files from an app on the phone associates it with a particular app thanks to Android 11+ Scoped Storage/SAF bull**** and will cause the file to be unreadable to the updater app process.
-- Old TWRP-based instructions below the fold (not recommended, but keeping for historical value... probably not accurate but I'm not going to update them more) --
Spoiler: Show/Hide
OTA updating from TWRP with OOS 11.x firmware:
You don't need to remove device protection; it works fine with PIN. Be sure you have a PIN set, or have looked up whatever that arcane chart of pattern > numeric incantations in case of pattern unlock. It's awful.
- Boot into TWRP recovery.
- Choose install, then select crDroid.zip, select additional zips, choose the TWRP installer zip, then slide to confirm flash.
- Reboot recovery.
- Choose install, then select Magisk zip (if using), select additional zips, choose GApps/microG (if using), slide to confirm flash.
- Please keep off of the grass, shine your shoes, wipe your... dalvik.
- Reboot system.
OTA updating from TWRP with OOS 10.x firmware:
- Don't. Update firmware to 11.1.2.2 first.
Reporting bugs:
I'm a parent of three young kids whose industry disappeared in the pandemic and is now full-time house husband & parent-in-charge while my wife is teaching full-time, I'm trying to save my small live-event-turned-streaming-studio company in my spare time. I'm doing in-home caregiving for a family member overnight one day a week. This is the back-up spare-spare-time hobby. I'm not a software developer nor do I know any programming languages, I just wanted a ROM with signature spoofing support and more customization than the unofficial microg-compatible LineageOS builds. So if there are bugs or feature requests, I go over to the crDroid dev chat and ask if someone has time to hold my hand & help. Don't make me get yelled for annoying them, mmkay? That said...
- Logs/screenshots/recordings or it didn't happen. Either the built-in Matlog app, or Syslog (free, open source, available on Play store and F-droid) are your friends here.
- I try to keep an organized notebook of roadmap, feature reqeusts, bug reports, etc. I won't always be able to fix it, but I'll at least look and do my best to ask the actual devs.
- I don't sign into XDA much, so if I haven't said anything, check out the Telegram group. Lots of helpful folks there.
- Please keep your questions in this thread instead of PMing me with them directly, so that the entire class can benefit from the discussion and you can find out if it's just you or if this is a widespread issue.
It's your device to use the way you want of course, and I use Magisk & microG and like to tweak things myself. But don't expect much support if you:
- didn't do a clean flash.
- aren't using the built-in kernel.
- are using extensive modifications (besides Magisk) like Xposed/Riru, Dolby Atmos, Viper4A, etc.
- immediately start using "finalize.zip" or flashing migrate restore zips instead of following the actual instructions.
- are running decrypted.
- re-locked your bootloader for some reason... you're on a custom ROM; don't do that.
crDroid Website - Download here!
Donate - Support development!
Telegram Oneplus6/6t group - Share your best cat pictures!
Source Code:
- Device tree: https://github.com/crdroidandroid/android_device_oneplus_enchilada/tree/11.0
- OP6/6T Common device tree: https://github.com/crdroidandroid/android_device_oneplus_sdm845-common/tree/11.0
- hardware/oneplus/ HALs: https://github.com/crdroidandroid/android_hardware_oneplus/tree/11.0-op6
- Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sdm845/tree/11.0
Notes:
- crDroid 7.x (based on Android 11 & LineageOS 18.1) is no longer being actively developed, and I don't know how long someone on the dev team will keep merging monthly security updates. I'll try to keep building releases as long as there are updates, but all my limited time is focused on 9.x/Android 13 bringup now. We're in maintenance mode now, so any outstanding bugs are likely to just remain for perpetuity.
- Yes it supports package signature spoofing permission for microG compatibility out of the box (but will work without ANY GApps/microG implementation installed as well).
- Maintainer does not use GApps, so cannot answer questions about which packages work best from firsthand experience. In general, go with the smallest package you can and then install other Google apps from the Play Store. Please note that if you replace the stock dialer with Google Dialer, you may lose access to the Phone Info menu (*#*#4636#*#*) until you install another dialer. For recommendations, see https://wiki.lineageos.org/gapps.
- Requires OOS 11.1.2.2 firmware (last official release). You should consider using an Android 10 ROM if you want to continue using Android 10 firmware.
- Tested against latest Magisk 24 canary (with zygisk instead of magiskhide), works well.
- No there won't be official builds with inline GApps; please don't ask.
crDroid 7.30 - May 2023 ASB release notes/changelog:
Changelog since v7.29 official release:
- Merged May 2023 Android Security Bulletin from upstream.
- Whatever the ROM dev team changed upstream in LineageOS and crDroid sources (not much? they're busy with Android 13+).
- No changes to device-specific files.
Known issues:
- No f2fs-formatted userdata support, sadly. Doesn't work with the prebuilt vendor partition required for this version of Android. You'll need to reformat data to ext4 before being able to boot (you can fastboot flash the crDroid 8.x or 9.x boot.img if you need a recovery that will let you choose).
- Google Hotword recognition might be kinda broken right now (on more than one custom ROM/device, not just us), and may cause some screw-up that prevents microphone audio from being allowed to go anywhere else if it's enabled.
- If you are stuck at "Android is starting..." looping endlessly, then press power, reboot to bootloader, and follow the instructions for updating firmware to OxygenOS 11.1.2.2 in the first post. It doesn't wipe data, you shouldn't lose anything.
- Some screen-off gestures may not work, due to limitations beyond my control; don't use those gestures. Sorry.
Helpful links:
Download ROM
Android platform tools (adb & fastboot)
OxygenOS 11.1.2.2 Full OTA
Firmware update instructions (LineageOS Wiki)
(Please note that since crDroid 7.x/Android 11 for this device depends on the prebuilt OxygenOS vendor partition, you'll also need to add fastboot flash --slot=all vendor vendor.img to the list of commands in the instructions, just before the final fastboot reboot.
MSMTool (oh now you're in trouble - use latest unless you have a good reason to intentionally downgrade)
Magisk (use latest)
Official TWRP 3.5.2_9-0 install zip (good luck)
Looking forward on this one, thank you for the effort!
Hopefully android auto and face unlock are working. Thanks in advance.
gray_wolf said:
Hopefully android auto and face unlock are working. Thanks in advance.
Click to expand...
Click to collapse
Can't say anything about Android Auto, but Face Unlock works just fine!
MaWalla99 said:
Can't say anything about Android Auto, but Face Unlock works just fine!
Click to expand...
Click to collapse
Great, will test and report about the android auto and overall Rom. Thanks again.
DC dimming seems to be missing
Welcome back team with a11...even with initial build rom is so stable , like this rom simplicity with so many customisations thankyou
Screenshot ???
vindipi said:
Screenshot ???
Click to expand...
Click to collapse
This Rom has latest Android security patch of January and for screenshots open and scroll down this website
crDroid.net - increase performance and reliability over stock Android for your device
official crDroid ROM blog
crdroid.net
what gapps
DRAKOITYU said:
what gapps
Click to expand...
Click to collapse
I personally used nikgapps...may be all are compatible
gray_wolf said:
Hopefully android auto and face unlock are working. Thanks in advance.
Click to expand...
Click to collapse
After running the Rom for 5 days now I can confirm that it's very stable and has tons of customization. Unfortunately though android auto is not working. face unlocking, camera, etc works fine. Would appreciate it if you could fix the android auto issue in the future build.
Anyone else having issues with GPay? I'm using Magisk, hidden, and GPay still won't work.
Is it possible to update crDroid from 6.13 to 7.2 without data formatting (keeping application and data)?
MaWalla99 said:
Download ROM
TWRP (use 3.5.0 or higher)
Magisk (use 21.2 or higher)
Click to expand...
Click to collapse
Hey, I have the twrp-3.3.1-18-enchilada-Q-mauronofrio TWRP installed on my Oneplus 6, do I still need to upgrade it to the one which you are recommending? I'd rather go with the one that I currently have and not go through the hassle of updating the recovery. That being said, obviously you would know much better.
Please guide
TIA
mahroze said:
Hey, I have the twrp-3.3.1-18-enchilada-Q-mauronofrio TWRP installed on my Oneplus 6, do I still need to upgrade it to the one which you are recommending? I'd rather go with the one that I currently have and not go through the hassle of updating the recovery. That being said, obviously you would know much better.
Please guide
TIA
Click to expand...
Click to collapse
Twrp 3.3 should work fine with the rom. You can keep using it if you want to. However, there is no extra step to use 3.5 vs 3.3. You have to flash twrp after flashing the rom so you can upgrade to 3.5 by just flashing it instead of 3.3.
Quick questions, this rom have smart charging feature?
Firstly, I just want to say this is the most awesome ROM I've tried and i've sat here for a week trying every rom I could get find on the net. It's almost flawless... except for a few hugely killer problems that will sadly make this ROM unusable for me... even though I love it soooo much and if only these things worked... this would be the most amazing ROM ever.
1. After installing GPS doesn't work.
2. When I get a phonecall... I hear the ring... but nothing happens on the screen... so I can't pickup the call. I see after i got a missed call... but i can't answer calls when they're calling... even if I go to the homescreen from whatever app i was using when i got the call... click on the phone icon.... still nothing. Can't answer the call.
3. Text messages simply don't arrive. If I flash the rom back to stock Oxygen OS ... then the text message comes through. But it's a bit late when you're trying to get a verifiaction SMS sent to you to open an messanging app. Can't use the app because i can't get the verification SMS.
If these three things get fixed... omg this will literally be the best ROM ever.
There is a 4th issue... and for me it's important... but it's probably not any fault really of crDroid ROM to be fair...
Very surprisingly... and I just wanted to see if it would work.... kali nethunter for Oxygen OS which is for droid 10 installs over the top of this rom which is droid 11... to much surprise! ...and almost flawlessly... only issue is it doesn't recognise HID interface.
Man... with these 4 things working... this ROM together with nethunter would make for the most badass hacker pentester phone on the planet... save only for the exact same thing on a oneplus 7 or 8 pro.
Many thanks to the devs of this awesome ROM... who hopefully can get 1, 2, and 3 working in the not too distant future... pretty please?
4 is more of a hope and a prayer... but it would be soooo freaking awesome.
not_the_droid_ur_lookin4 said:
Firstly, I just want to say this is the most awesome ROM I've tried and i've sat here for a week trying every rom I could get find on the net. It's almost flawless... except for a few hugely killer problems that will sadly make this ROM unusable for me... even though I love it soooo much and if only these things worked... this would be the most amazing ROM ever.
1. After installing GPS doesn't work.
2. When I get a phonecall... I hear the ring... but nothing happens on the screen... so I can't pickup the call. I see after i got a missed call... but i can't answer calls when they're calling... even if I go to the homescreen from whatever app i was using when i got the call... click on the phone icon.... still nothing. Can't answer the call.
3. Text messages simply don't arrive. If I flash the rom back to stock Oxygen OS ... then the text message comes through. But it's a bit late when you're trying to get a verifiaction SMS sent to you to open an messanging app. Can't use the app because i can't get the verification SMS.
If these three things get fixed... omg this will literally be the best ROM ever.
There is a 4th issue... and for me it's important... but it's probably not any fault really of crDroid ROM to be fair...
Very surprisingly... and I just wanted to see if it would work.... kali nethunter for Oxygen OS which is for droid 10 installs over the top of this rom which is droid 11... to much surprise! ...and almost flawlessly... only issue is it doesn't recognise HID interface.
Man... with these 4 things working... this ROM together with nethunter would make for the most badass hacker pentester phone on the planet... save only for the exact same thing on a oneplus 7 or 8 pro.
Many thanks to the devs of this awesome ROM... who hopefully can get 1, 2, and 3 working in the not too distant future... pretty please?
4 is more of a hope and a prayer... but it would be soooo freaking awesome.
Click to expand...
Click to collapse
You have been positing this in more than one thread. This has nothing to do with any rom, and is related to what you are doing with your phone or the phone itself. Telephony is flowless on every Android 11 custom rom for Oneplus 6. And so is GPS, which literally connects in seconds.
First thing you should do is: disable wifi calling, because if your provider doesn't have the feature (or you are not provisioned for it), that could cause your problems. Next, uninstall any mode you might have. Try calling without Gapps.
Also, if you ever used Syberia Rom, you got custom /vendor, which would not work with other custom roms that use stock /vendor. So, you need to re-flash full stock rom onto both slots, which is a pre-requisite for flashing most custom roms. Then follow directions for installing a custom rom.
Would it be possible to backup different images from different GSI ROMs to be able to test and restore each one without losing all the apps, configuration, etc. in the process.
For example:
1. Install "GSI name1" configure it, install apps, my Google account, etc.
2. Somehow, make a backup of the required partitions "backup name1" (At the computer?)
3. Install "GSI name2" configure it, install apps, my Google account, etc. (Not necessarily the same apps than before).
4. Somehow make a backup of the required partitions "backup name2".
5. Continue testing other GSI or restoring one of the previous ones from the backups and be able to use the phone as it was before, including apps, configuration, etc.
I can imagine two ways to face this task:
A. Using a custom recovery to backup partitions to SD card.
B. Using fastboot or mtk_client to backup partitions to the PC.
Would be easy? Possible? Not recommendable for some reason?
I am new on this flashing-bricking-sweating-unbricking thing, so I would appreciate feedback.
Thank you!
Hi
If your goal is to test the GSIs, it's easier to use the DSU-sideloader instead of the backup.
This app enables you to dual boot.
You will be able to move back and forth between images. Even if you get into a boot loop, you can return to the original image just by rebooting.
If you have root, this app will be easier because there will be less operations.
https://github.com/VegaBobo/DSU-Sideloader
I have been taking a look to the DSU concept. It is interesting, but not what I want. Also, it requires the main ROM to be stock ROM (maybe in future is fine to use with custom ROMs).
DSU would be perfect if you want to keep romA and romB working in parallel in your daily life (for example, one for work and business and the other one for gaming and social apps).
What I want to do is to test romA for a while, move to romB for a while, if I prefer romA, reinstall it and forget about romB (literally, delete it). Maybe in few months, backup romA again and check romC for a while...
As I do not want to be swapping from one to another in daily life, it does not make sense to reserve space for having both simultaneously ready to work on the phone.
By now I have been learning about adb and recovery backup options. I need to check more during the next days, but I noticed that from Recovery, I can also use adb (it says not authorized device, but that is for not being rooted yet, I suppose). If it is possible to use adb from recovery after rooting, it would be easy to have a PC software for backing up ROMs easily (system, data and userdata partitions?).
I will keep researching about it...
The DSU does not have to be a stock rom.
It's just desirable.
Currently I have crdroid GSI as the first OS and the second OS is trying several OSs.
If you try it, you'll notice how easy it is.
Currently, TWRP does not support backup or encryption on Android 12. It is the same even if it is the official latest of other models.
I have a 128GB model, so it took too long to back up using mtkclient and I quit halfway through.
The problem is time and encryption, keep them in mind.
Currently, TWRP does not support backup or encryption on Android 12. It is the same even if it is the official latest of other models
Click to expand...
Click to collapse
Well, definitely untrue now as most devices have got it sorted out with decryption, Android 12 being a pain some devices got 13 done before 12, but as of the time you wrote this post my device Motorola stylus 22 5g Qualcomm, we hadn't figured out the decryption yet but you could definitely just patch your fstab in vendor either by hand or with DFE neo, to disable the encryption and TWRP would run fine. You would just have to make that first format reboot back to recovery immediately and while it still stays the data from a fresh format flash the other handy RO2RW re zip and DFE neo. Honestly the boot times are so much better without decryption I don't think I would go back as long as I've got a password on orange fox or whatever.