Related
Thought I'd try out the encryption in AOKP on my Nexus 7 (2013) and decided I didn't like it. I read that a "factory reset" in TWRP was supposed to remove it, although it would nuke all my files, sdcard, apps, etc. No problem, the thing is brand new so nothing really on it. After wiping however, when I boot into recovery now, TWRP is still asking for the encryption PIN. I thought I would just get into the shell over ADB and see what's going on but not able to do that either. I just get "?????????" when trying to view the device with "adb devices". I read something about erasing userdata, system and cache from fastboot and also another piece of info about flashing the stock recovery back to it, but not sure that's the best route. Any thoughts? Thanks.
eris170 said:
Thought I'd try out the encryption in AOKP on my Nexus 7 (2013) and decided I didn't like it. I read that a "factory reset" in TWRP was supposed to remove it, although it would nuke all my files, sdcard, apps, etc. No problem, the thing is brand new so nothing really on it. After wiping however, when I boot into recovery now, TWRP is still asking for the encryption PIN. I thought I would just get into the shell over ADB and see what's going on but not able to do that either. I just get "?????????" when trying to view the device with "adb devices". I read something about erasing userdata, system and cache from fastboot and also another piece of info about flashing the stock recovery back to it, but not sure that's the best route. Any thoughts? Thanks.
Click to expand...
Click to collapse
A factory reset from inside TWRP does NOT wipe internal storage/sdcard. If you want to wipe everything you can either do it from inside TWRP with "advanced wipe" or just do a normal factory reset from Settings/Backup and reset. If you fastboot flash the userdata and cache images that would also be like a factory reset. If you wipe/erase the system you will need to fastboot flash the system image or flash a rom BEFORE you try and reboot.
wantabe said:
A factory reset from inside TWRP does NOT wipe internal storage/sdcard.
Click to expand...
Click to collapse
Sorry, I meant to say I did the advanced wipe and smoked the data partition. I was going to go back and edit my post but it wouldn't let me do it for another five minutes and I went off and did something else. When you say "fastboot flash" the system image, do you mean re-install TWRP with "fastboot flash recovery twrp.img" ?
I tried a different comp and was able to get to the device over ADB so I pushed aokp_flo_jb-mr2_milestone-1.zip over ADB to /sdcard and did the same with gapps-jb-20130813-signed.zip. TWRP installed them OK, but after reboot, the zygote process now keeps trying to restart com.google.android.setupwizard which errors out with a dialog box which says "Unfortunately, Setup Wizard has stopped". I touch "Ok" but the dialog just comes back. Looks like I've made a real mess of things.
Should I just go find the stock OS image and recovery image and flash them over?
eris170 said:
Sorry, I meant to say I did the advanced wipe and smoked the data partition. I was going to go back and edit my post but it wouldn't let me do it for another five minutes and I went off and did something else.
Click to expand...
Click to collapse
I'm pretty sure that wiping data from inside advanced wipe will have wiped everything, that should have been enough to get rid of your encryption.
eris170 said:
When you say "fastboot flash" the system image, do you mean re-install TWRP with "fastboot flash recovery twrp.img" ?
Click to expand...
Click to collapse
No. The system image I was talking about is from the factory image. You have to extract/unzip the factory image a couple times before you can see the zip folder with all the images ( boot (kernel), cache, recovery, system and userdata). You had mentioned in your first post "erasing userdata, system and cache." If you erase system you will need to replace it otherwise your device does not have an os (operating system) anymore. One of many ways to replace it would be to fastboot flash the system image (fastboot flash system system.img) that is extracted from the factory image.
eris170 said:
I tried a different comp and was able to get to the device over ADB so I pushed aokp_flo_jb-mr2_milestone-1.zip over ADB to /sdcard and did the same with gapps-jb-20130813-signed.zip. TWRP installed them OK, but after reboot, the zygote process now keeps trying to restart com.google.android.setupwizard which errors out with a dialog box which says "Unfortunately, Setup Wizard has stopped". I touch "Ok" but the dialog just comes back. Looks like I've made a real mess of things
Click to expand...
Click to collapse
. I've always used the stock rom on my Nexus devices so I'm not much help with anything else. But... just from looking at the names on the zips you installed I'm guessing the "jb" means Jelly Bean and the gapps you installed are almost a year old. So... WTH? ; )
eris170 said:
Should I just go find the stock OS image and recovery image and flash them over?
Click to expand...
Click to collapse
I think in your case the easiest thing to do would be to flash the factory image and start over. You will then need to reinstall TWRP and then use TWRP to install/flash the supersu zip. My advice would be to do lots of research before flashing custom roms and custom kernels. After you get back to the factory rom you really need to use TWRP to do a backup (nandroid) BEFORE you flash any custom roms and kernels, with that done it will be easy as hell to get back to stock after experimenting with whatever! Don't rely on toolkits, install the android sdk and learn adb fastboot commands, it's not hard, hell even I can do it!
[TUTORIAL]Download Factory Images Nexus 7 FLO - Restore back STOCK - With latest version KitKat 4.4.4
I've never used this but looks interesting. [TOOL] 06/22/14 One Click Factory Restore 4.4.4 KTU84P (dead or alive)
wantabe said:
. I've always used the stock rom on my Nexus devices so I'm not much help with anything else. But... just from looking at the names on the zips you installed I'm guessing the "jb" means Jelly Bean and the gapps you installed are almost a year old. So... WTH? ; )
Click to expand...
Click to collapse
Meh.. I like running the older stuff because it's usually faster... I mean as long as there isn't some gaping vulnerability in it.
wantabe said:
I think in your case the easiest thing to do would be to flash the factory image and start over.
Click to expand...
Click to collapse
Thanks for the link that saved me some time! Downloaded an flashed and encryption is finally gone. \o/ . Should be all good now.
eris170 said:
Meh.. I like running the older stuff because it's usually faster... I mean as long as there isn't some gaping vulnerability in it.
Thanks for the link that saved me some time! Downloaded an flashed and encryption is finally gone. \o/ . Should be all good now.
Click to expand...
Click to collapse
One of the great things about android is having the ability to change what you don't like and for the most part it isn't hard to do. I did notice with the update to 4.4 better performance and fluidity on both my N5 and N7 so it might be worth checking out at some point. I didn't care for some of the changes like the ui sounds with the 4.4.1 update but it's all easy to modify. Anyway.. glad you got it sorted out.
Hi XDA friends
I have a Nexus 5x on build MDB08I. It's rooted and encrypted with the encryption-compatible TWRP.
I really want to update to 6.0.1 but I don't want to have any data loss (i made a Nandroid backup recently but it's just a pain in the ass to set up a phone from scratch). Is this safe slash possible currently? I don't care about losing root, I just want to get the update, and keep all data and TWRP intact.
If so, can anyone help me out with what files I need and where to get them? I've got android SDK, familiar with fastboot, etc. but I just don't know what to flash and not flash. I do know that I can't just flash the OTA zips, tried that a few times
From what I've found looking around, it seems possible if I extract the files from the factory image of MMB29K and do the following:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash cache cache.img
wipe cache/dalvic in TWRP
reboot
flash SuperSu in recovery
Click to expand...
Click to collapse
And... that's it? Do I have to flash radio, bootloader, recovery, etc? Will TWRP work with MMB29K? If it fails, I can revert to my nandroid backup. BUT I want to confirm that the above plan does not risk a brick.
Thanks!!
Read this thread http://forum.xda-developers.com/showpost.php?p=64253043&postcount=289
That specific post has the list of steps you should do to upgrade and regain root without losing your data. You can find the modified MMB29K boot.img file in another post on this forum.
solara1973 said:
Read this thread http://forum.xda-developers.com/showpost.php?p=64253043&postcount=289
That specific post has the list of steps you should do to upgrade and regain root without losing your data. You can find the modified MMB29K boot.img file in another post on this forum.
Click to expand...
Click to collapse
I followed that list but my phone has been booting for 20+ minutes. I'll restore from nandroid, but any idea what I did wrong? Should i fastboot flash iteratively from I to L to M and then to K instead of directly from I to K? do i have to boot into the OS after each build flash?
thanks!
edit: hah, wow. didn't even have to nandroid, just re-flashed all the I img's and all is back to normal. next i'll try the L, M, K sequence and report back unless you have any other ideas what i did wrong
You do not need to flash each version if you are flashing the images from the full firmware you download from Google. When you say it takes 20 mins where is it hanging at? It took a while for my 54 apps to get updated after flashing and clearing cache before booting into the system. You should not boot into system until you've flashed everything. You do reboot to bootloader after you flash the new bootloader.
Make sure you flash MODIFIED boot image for MMB29K if you were rooted with /system SU on L, otherwise you'll get boot loop. Also flash new radio too if you want Tmo band 12.
mickey4mice said:
Make sure you flash MODIFIED boot image for MMB29K if you were rooted with /system SU on L, otherwise you'll get boot loop. Also flash new radio too if you want Tmo band 12.
Click to expand...
Click to collapse
oops, that's it -- i had flashed the boot.img from the google image. found another XDA thread w/ modified MMB29K boot.img so trying that
@Solara i left it at the new boot animation for like an hour, the one with the 4 cute circles acting all busy.
also what does flashing cache and then wiping it do? why flash if if your'e gonna wipe it right after? new file format?
thanks so much guys!
edit: all set! did the same thing with the modified boot.img this time. also discovered i had to re-flash TWRP. still wondering what the deal with the cache/dalvik is but i flashed and wiped and everything seems great.
I didn't mean flash the cache image then clear it. I mean flash all the specified images then clear the cache. Just look at that original link I posted. Pretty clear and easy steps.
solara1973 said:
I didn't mean flash the cache image then clear it. I mean flash all the specified images then clear the cache. Just look at that original link I posted. Pretty clear and easy steps.
Click to expand...
Click to collapse
deffo, very simple and it's awesome that this **** is even possible due to all the work devs and volunteers do i've seen elsewhere people saying they flashed cache.img and then wiped it so it sounds like they were flashing it unnecessarily
I know on most devices I've owned you needed a non-encrypted kernel and I had to perform a format of data to remove encryption. I have seen a few posts in a couple of other threads but nothing I saw was definitive. Does anyone know if unencrypting the XL is even possible? If so, which kernel are you using?
I also have the same question, I just want descrpt data partition to avoid risk when I turn to TWRP and MultiROM in future,
So anyone try this? I can not understand why I need Magisk here??
http://androiding.how/disable-verity-force-encryption-pixel-xl-decrypt/
Mike02z said:
I know on most devices I've owned you needed a non-encrypted kernel and I had to perform a format of data to remove encryption. I have seen a few posts in a couple of other threads but nothing I saw was definitive. Does anyone know if unencrypting the XL is even possible? If so, which kernel are you using?
Click to expand...
Click to collapse
Azlun said:
I also have the same question, I just want descrpt data partition to avoid risk when I turn to TWRP and MultiROM in future,
So anyone try this? I can not understand why I need Magisk here??
http://androiding.how/disable-verity-force-encryption-pixel-xl-decrypt/
Click to expand...
Click to collapse
Notice in the attached that it states that TWRP plus SuperSU decrypts file based encryption.... https://www.xda-developers.com/supersu-updated-to-work-with-twrp-on-pixel-and-pixelxl/
cam30era said:
Notice in the attached that it states that TWRP plus SuperSU decrypts file based encryption.... https://www.xda-developers.com/supersu-updated-to-work-with-twrp-on-pixel-and-pixelxl/
Click to expand...
Click to collapse
" Dees_Troy to allow TWRP to decrypt the data partition involves modifying the same init binary " is NOT what I want according developer's
https://plus.google.com/+DeesTroy Pixel update 4 picture.
What I want is need the full device decryption permanently, on Anroid running time, not only on TWRP.
so, I think that is maybe more than TWRP can do, I guess a special boot.img or a kernel patch zip is need to reach what I need.
Mike02z said:
I know on most devices I've owned you needed a non-encrypted kernel and I had to perform a format of data to remove encryption. I have seen a few posts in a couple of other threads but nothing I saw was definitive. Does anyone know if unencrypting the XL is even possible? If so, which kernel are you using?
Click to expand...
Click to collapse
Decrypting your pixel is possible. The process isn't much different than any previous Nexus. It differs due to the removal of the recovery partition thus the recovery fstab is now in the kernels ramdisk. So you must edit out forecencryption in both fstabs. (fstab.marlin,fstab.recovery).
Fastboot format userdata, flash a modified kernel, done..
Haven't seen any custom kernels that remove the flag yet so I modified ElementalX.
http://forum.xda-developers.com/pix...oem-unlock-t3498287/post69733387#post69733387
blueyes said:
Decrypting your pixel is possible. The process isn't much different than any previous Nexus. It differs due to the removal of the recovery partition thus the recovery fstab is now in the kernels ramdisk. So you must edit out forecencryption in both fstabs. (fstab.marlin,fstab.recovery).
Fastboot format userdata, flash a modified kernel, done..
Haven't seen any custom kernels that remove the flag yet so I modified ElementalX.
http://forum.xda-developers.com/pix...oem-unlock-t3498287/post69733387#post69733387
Click to expand...
Click to collapse
I did use your modified Elemental kernel that was in the thread about the ability to show that your bootloader is unlocked.
Here is what I did...
Went into TWRP and did a format data from the wipe menu.
Flashed your kernel via USB SD dongle.
Rebooted.
Took about 5-8 minutes to boot but when I went into "Security" it still showed my phone was encrypted. I did this with every Nexus device I've owned but not sure what I'm doing wrong.
Mike02z said:
I did use your modified Elemental kernel that was in the thread about the ability to show that your bootloader is unlocked.
Here is what I did...
Went into TWRP and did a format data from the wipe menu.
Flashed your kernel via USB SD dongle.
Rebooted.
Took about 5-8 minutes to boot but when I went into "Security" it still showed my phone was encrypted. I did this with every Nexus device I've owned but not sure what I'm doing wrong.
Click to expand...
Click to collapse
Don't you need to format user data with fast boot to decrypt?
Sent from my Google Pixel XL using XDA Labs
T-Mobile V30 H932 20s Stock Collection
Based on OEM 20s KDZ. Extracted and Repacked.
DISCLAIMER
Proceed at your own risk. I am not responsible for any damage to your device.
Flashing LAF WILL REMOVE TWRP from your laf partition and restore stock DL Mode
Bins in these packages are unmodified and you may need to flash no-verity-opt-encrypt and rctd remover after to keep force-encryption away.
REQUIRED
TWRP on LAF or Recovery
Latest Magisk Zip (if performing clean flash)
no-verity-opt-encrypt
rctd remover
FILE BREAKDOWN
None of these Zips flash the Recovery partition.
Besides StockLAF, these Zips DO NOT flash the LAF partition.
If you want to restore DL Mode and Stock LAF, you must flash the StockLAF package separately.
Bootloader: 20s Stock Bootloader ONLY
FullStock: Full 20s Stock Firmware Only (bootloader, modem, boot, system) - Instructions in Section A
Debloated w/Magisk: Boot+Debloated System + Magisk Root (force enc & dm-verity removed) - Instructions in Section B
StockLAF: Individual LAF image for returning to stock DL mode
WARNING
This firmware contains DTS libs and there are related changes within the Bootloader/Modem zips.
Anybody running a custom rom like LOS or RR will have sound problems if you flash these. (until a compatible build is released)
Unless you are already running 20r, anybody running the Debloated zip will have video/sound problems if you DO NOT flash these (FullStock contains both)
Thanks to @ChazzMatt for sharing this helpful info.
Global Instructions
Always make a backup first
If device has been encrypted, see encryption notes at the bottom before continuing.
A - FullStock
If coming from Nougat, Clean Flash is Recommended
Wipe Dalvik, System, Data, Cache... then flash
If coming from previous Oreo versions, Dirty Flash works fine. OS and Apps are updated.
Copy All Zips to SDCard
Flash h93220s_FullStock.zip
Flash Magisk
Flash no-verity-opt-encrypt
Flash rctd remover
Reboot to system and install Magisk Manager (if not installed)
B - Debloated with Magisk
You MUST flash FullStock, or Bootloader and Modem before flashing this to make sure all of your device firmware is up to date.
Be aware
This ROM does NOT flash LAF, recovery, bootloader or modem firmware directly.
Boot image has been patched to remove force encryption and dm-verity
This ROM has had several pre-loaded and system apps removed. If someone wants to send me a list of any additional apps that can be safely removed, i can update the rom to include them.
system/app/CloudPrint
system/app/Drive
system/app/Duo
system/app/EditorsDocs
system/app/EditorsSheets
system/app/Gmail2
system/app/GooglePay
system/app/LGAccount
system/app/LGAirDrive
system/app/LGAmazonAssistant
system/app/LGAmazonAttribution
system/app/Maps
system/app/Music2
system/app/Photos
system/app/YouTube
system/priv-app/CloudHub
system/priv-app/CollageWallpapers
system/priv-app/facebook-installer
system/priv-app/LG360VideoWallpaper
system/priv-app/LG360Wallpaper
system/priv-app/LGEasyHome
system/priv-app/LGEmail
system/priv-app/LGExchange
system/priv-app/LGQHelpService
system/priv-app/LGVVM
system/priv-app/NameID
system/priv-app/TMO_MyAccount
system/priv-app/xtra_t_app
system/vendor/app/facebook-appmanager
system/vendor/overlay/com.lge.easyhome
system/vendor/overlay/com.lge.email
system/vendor/overlay/com.lge.exchange
system/vendor/overlay/com.lge.lgworld
system/vendor/overlay/com.lge.qhelp
system/vendor/overlay/com.lge.qhelp.application
system/vendor/overlay/com.lge.qmemoplus
For best results a clean flash is recommended for this package if you are not already running 20p Debloated
Format data, and remove any apps installed to external sd. Then wipe system, dalvik, cache, data, internal storage
This will ensure no lingering apps are left behind.
If coming from Nougat, Clean Flash is Highly Recommended
Wipe Dalvik, System, Data, Cache... then flash
If coming from previous Oreo Versions
Wipe Dalvik, Cache, and System, and optionally data and internal storage
If you do not perform a clean flash, you may need to manually remove the apps left behind after flashing
Flash h93220s_Debloated.zip
Reboot
DOWNLOADS
Stable v1.0
Project files are hosted on SourceForge
Bootloader - md5:17db9bf058d53ecdd80f79a27b7fe469
Modem - md5:905cb40dc6e9eeb5fa52dd0d8d4f09cb
FullStock ROM - md5:ff32af2c1f3140c3c8c27ddac59e4950
FullStock w/Magisk - md5:9567710ab9f8e1ee4e4e4e36cfd1d2f5
Debloated w/Magisk - md5:fc0b6d9cd357ade5db472f36a10ecc8e
StockLAF - md5:799362769b0712a10818c0f26258efc2
*************************************************************************************************************
Encryption Notes
In Android, a stock device will have it's data encrypted. Often when working in TWRP on an encrypted device, you will be greeted by prompt asking for a passcode in order to decrypt the device. Unless that port of TWRP has been written for your specific device and supports decryption, you will not be able to decrypt the data on your phone. If you cannot decrypt the data, then TWRP cannot mount system and/or other partitions it needs to mount in order to safely flash anything. In order to solve this problem, sadly, you have to format the data partition on your phone (losing all personal data accumulated on the internal storage, so back it all up manually) The steps for this process are Format Data in TWRP, Reboot to recovery (to mount partitions), then flash your rom and root. There are a few tools out there to disable force encryption on your device. See the Required section above for links for this device.
Debloated has been testing via Dirty Flash from 20r.
FullStock, Bootloader and Modem have not yet been tested, but boot and system have been verified and remaining SHA1 hash checks all match with 20r which is working.
If anyone has any issues with one or more of these packages, please let me know. Thank you!
-weakNPCdotCom
XDA:DevDB Information
[STOCK] h93220s, ROM for the LG V30
Contributors
weakNPCdotCom
Source Code: https://sourceforge.net/projects/t-mobile-v30-firmware/files/h932/20s/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: 20s KDZ
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2019-04-02
Created 2019-04-02
Last Updated 2019-04-05
All packages have been released except for debloated. I am going to cook that this afternoon and should have it uploaded by tonight. Ill post an update when it's available.
Debloated Package has been Uploaded
weakNPCdotCom said:
All packages have been released except for debloated. I am going to cook that this afternoon and should have it uploaded by tonight. Ill post an update when it's available.
Click to expand...
Click to collapse
is it possible that the full stock is bad? i flashed it, now im 9008. could be corrupted dl on my end. jjust figured you might want to check
BROKEN1981 said:
is it possible that the full stock is bad? i flashed it, now im 9008. could be corrupted dl on my end. jjust figured you might want to check
Click to expand...
Click to collapse
Sorry man. what do you mean 9008? Any way you can get me your TWRP logs?
I did have to re-upload the fullstock zips after I discovered an issue with the boot image.
Also, id recommend checking the md5 hash after you download to make sure it matches what's in the OP
weakNPCdotCom said:
Sorry man. what do you mean 9008? Any way you can get me your TWRP logs?
I did have to re-upload the fullstock zips after I discovered an issue with the boot image.
Click to expand...
Click to collapse
i flashed the full stock zip, when i did reboot to system, my screen stays black. i plugged it into the computer, the computer made the sound that a device was plugged in.
in device manager its listed as 9008. so its a brick now. i got my RMA with lg. just need to send it out.
also want to make an edit, im not upset, and thank you for what you do for the community. we all take the risk.
BROKEN1981 said:
i flashed the full stock zip, when i did reboot to system, my screen stays black. i plugged it into the computer, the computer made the sound that a device was plugged in.
in device manager its listed as 9008. so its a brick now. i got my RMA with lg. just need to send it out.
also want to make an edit, im not upset, and thank you for what you do for the community. we all take the risk.
Click to expand...
Click to collapse
Yeah but still, I hate that happened to you. Are you not able to boot to DL/LAF?
it looks like the phone being read as 9008 is what happens with a dead boot.
I tried to upload the boot fix as fast as I could. Can you tell me when you downloaded it? I'm going to take the fullstock links down until I can make sure they have the correct boot image
weakNPCdotCom said:
Yeah but still, I hate that happened to you. Are you not able to boot to DL/LAF?
it looks like the phone being read as 9008 is what happens with a dead boot.
I tried to upload the boot fix as fast as I could. Can you tell me when you downloaded it? I'm going to take the fullstock links down until I can make sure they have the correct boot image
Click to expand...
Click to collapse
I tried the button combo, i tried to get to twrp via dl mode on my pc as well.
i called T-mobile around 5pm i think. its now 8:05pm.
only reason im posting now is due to trying to figure out how to lon on XDA with my G-account. i figured out how to take that 2 factor auth off.
BROKEN1981 said:
I tried the button combo, i tried to get to twrp via dl mode on my pc as well.
i called T-mobile around 5pm i think. its now 8:05pm.
only reason im posting now is due to trying to figure out how to lon on XDA with my G-account. i figured out how to take that 2 factor auth off.
Click to expand...
Click to collapse
I was just trying to figure out if you might have downloaded the first upload or the second. but i think I uploaded the new version before 5.
I found a video online for unbricking a v30 phone in 9008 mode. not sure if it works for the H932 but might be worth looking at
Im going to rebuild all the primary zips just to be safe.
I was running debloated 20r and I dirty flashed the debloated 20s and it is working 100%
If you guys aren't already on 20r and don't want to wait on the new zips you can flash one of the 20r packages and then flash the 20s debloated.
weakNPCdotCom said:
I was just trying to figure out if you might have downloaded the first upload or the second. but i think I uploaded the new version before 5.
I found a video online for unbricking a v30 phone in 9008 mode. not sure if it works for the H932 but might be worth looking at
Click to expand...
Click to collapse
i found this, but it may as well be in Greek.
https://innaz2.blogspot.com/2016/06/revised-how-to-unbrick-qualcomm-android.html
BROKEN1981 said:
i found this, but it may as well be in Greek.
https://innaz2.blogspot.com/2016/06/revised-how-to-unbrick-qualcomm-android.html
Click to expand...
Click to collapse
Yeah that looks like a heavy walkthrough. Im really sorry you ended up being the Guinea pig with this one. thank you very much for reporting the issue
I rebuilt all packages and they are now available again.
I have not tested them, but I have verified the boot and system images are good, and all remaining files have SHA1 checksums that match with 20r, which has been verified working.
All zips perform SHA1 checks prior to flashing to ensure each partition image is valid.
These should all be safe to flash going forward.
weakNPCdotCom said:
Yeah that looks like a heavy walkthrough. Im really sorry you ended up being the Guinea pig with this one. thank you very much for reporting the issue
Click to expand...
Click to collapse
ahhh NP man. I just hope i was the first and only person to flash it. its all good man, we all take risk and if it was not for you, i would not have had DTS on 20R
Flashed debloated, work as charm, thanks dev
anyway you can modified it to be flashed on a US998?
BROKEN1981 said:
ahhh NP man. I just hope i was the first and only person to flash it. its all good man, we all take risk and if it was not for you, i would not have had DTS on 20R
Click to expand...
Click to collapse
I was in the same boat when 20r was released. Had my phone unable to boot for a week. Luckily the devs put together a fix for us. But it looks like everything is sorted out here now. I'll be flashing it later tonight. Thanks @weakNPCdotCom
Flashed the 20s bootloader no problem, but got a assert failure on flashing the 20s modem- looked like it was an SHA confirmation issue.
KanBorges said:
anyway you can modified it to be flashed on a US998?
Click to expand...
Click to collapse
No. You cannot flash U.S T-Mobile H932 firmware on US998 or any other V30/V30+/V30S.
You can use US998 on T-Mobile, as-is. We have a lot of US998 T-Mobile users. For instance, @runningnak3d is currently using a US998 on T-Mobile. He's the one who rooted the T-Mobile H932 in the first place.
@weakNPCdotCom - full stock with magisk getting asset error on abl.img
Md5 hash matches what's in OP
Hello !!!
Gsi Rom for realme Q
This is the best version for realme Q.Works well, but fingerprint error, hope someone can fix it
Installation Instructions:
1. Download the GSI from the links above, and uncompress it.
2. Wipe Data, Dalvik, and Cache,system . No wipe vendor
3. Remove Magisk if it was previously installed, by using its uninstaller script. Magisk files are stored in the kernel image, and in the /data/adb folder, which are left untouched when wiping data and flashing the GSI. Another option is to flash your stock rom and manually delete the content of the /data/adb folder.
4. Flash the GSI to system partition (AB devices : flashing a vbmeta.img file for your device may also be required).
5. Boot and perform a factory reset.
6. (Optional) Reboot and flash Magisk, and maybe additional files.
7. Reboot and Enjoy.
If you want to update rom, you can also always try to dirty flash, i.e. wipe Dalvik and Cache (not Data) and flash System image. But if you experience a strange behavior, a clean flash may be required
Note : if flash Gapps you need resize system in teamwin,then flash gapps
Which vendor to use?
1. Always use your actual device's vendor
2. Always use OEM unmodified vendor, not some custom vendor
3. This includes boot.img. boot.img and vendor MUST BE the same version.
Rom download :
Link download android 9 rr7.0 : https://drive.google.com/file/d/1--pQfJlNR2V9OEFeLCoT--tmftT8OFGZ/view?usp=drivesdk
link download android 10 AOSP : Download
Link download Rom Msm 9 : Download
How to fix bug any rom:
Link download fix lag,fix bt audio,fix mtp,fix power rom havoc,magisk stable for android Q and more ..
Folder click here
Great, found your thread on telegram, this is what I need, I am fed up with Color OS
It's not half bad but there are two major problems with the ROM. First it seems it can't read exfat 128 GB as card which is a shame for I won't format it to inferior fat32 to lose all my stuff. Second, whenever I set a screen lock, no matter what kind of it'll tell me that I entered incorrect code. Means I cannot lock the screen with any kind of security measure. I could solve the external as card issue by flashing lineage os boot.img but I couldn't the screen lock issue. Aside these I have no problem. Testing other gsi ROMs.
Edit.: No. Screen lock isn't rom but vendor issue. I accidentally wiped vendor partition before flashing the image.
greenys' said:
It's not half bad but there are two major problems with the ROM. First it seems it can't read exfat 128 GB as card which is a shame for I won't format it to inferior fat32 to lose all my stuff. Second, whenever I set a screen lock, no matter what kind of it'll tell me that I entered incorrect code. Means I cannot lock the screen with any kind of security measure. I could solve the external as card issue by flashing lineage os boot.img but I couldn't the screen lock issue. Aside these I have no problem. Testing other gsi ROMs.
Edit.: No. Screen lock isn't rom but vendor issue. I accidentally wiped vendor partikon before flashing the image.
Click to expand...
Click to collapse
I will note that people do not wipe vendor
29y6145 said:
I will note that people do not wipe vendor
Click to expand...
Click to collapse
I just noticed that I didn't wipe vendor either. It's not even in the wipeable section if you try advanced wipe. For some reason if I go from one gsi to another lock screen password/pattern will not work. I have to flash stock zip first, then wipe data, system, cache, davlik and at last flash gsi image. Between going from one gsi to another you have to do this in order to keep lock screen password function. Right now I'm struggling with Magisk Safetynet. Any good method to bypass?
greenys' said:
I just noticed that I didn't wipe vendor either. It's not even in the wipeable section if you try advanced wipe. For some reason if I go from one gsi to another lock screen password/pattern will not work. I have to flash stock zip first, then wipe data, system, cache, davlik and at last flash gsi image. Between going from one gsi to another you have to do this in order to keep lock screen password function. Right now I'm struggling with Magisk Safetynet. Any good method to bypass?
Click to expand...
Click to collapse
I realized that. Today I tested android Q on realme Q, it worked. I cannot set the screen password, the system only allows swiping. I am looking into this problem.
29y6145 said:
I realized that. Today I tested android Q on realme Q, it worked. I cannot set the screen password, the system only allows swiping. I am looking into this problem.
Click to expand...
Click to collapse
Flashing stock vendor img solved the issue on my device. Although I tried AOSP Pie not Q.
update android 10 and permissiver for andoid 10
Update Installation Instructions .
Hi, awesome thread, congrats to you @29y6145.
I see now that you added two more ROMs, the AOSP10 and the MSM-Xtended 9. Any of them are more stable than the others? I was looking for stability in the entire OS and Camera that any other thing.
By the way, Why you remove the links to TWRP and Permissiver_v5?
I installed the Resurrection Remix 7.0.2 and see that doesn't have Magisk by default. I should install Magisk via your TWRP built-in Magisk installer or from the official Magisk website?
Tmv_Josue said:
Hi, awesome thread, congrats to you @29y6145.
I see now that you added two more ROMs, the AOSP10 and the MSM-Xtended 9. Any of them are more stable than the others? I was looking for stability in the entire OS and Camera that any other thing.
By the way, Why you remove the links to TWRP and Permissiver_v5?
I installed the Resurrection Remix 7.0.2 and see that doesn't have Magisk by default. I should install Magisk via your TWRP built-in Magisk installer or from the official Magisk website?
Click to expand...
Click to collapse
I am editing some posts, and will re upload important files.
Both of the 2 Roms you speak are fine. I will give you a tutorial about the Havoc rom.
I have upload permissiver #1
29y6145 said:
I am editing some posts, and will re upload important files.
Both of the 2 Roms you speak are fine. I will give you a tutorial about the Havoc rom.
I have upload permissiver #1
Click to expand...
Click to collapse
Did you manage to pass safetynet with gsi?
greenys' said:
Did you manage to pass safetynet with gsi?
Click to expand...
Click to collapse
You try
@29y6145
This Petnoire's_SafetyNet_Spoofer_magisk.zip should be used instead of the Realme5ProColorOSMagiskFixBETA.zip?
Or both should be flashed?
Tmv_Josue said:
@29y6145
This Petnoire's_SafetyNet_Spoofer_magisk.zip should be used instead of the Realme5ProColorOSMagiskFixBETA.zip?
Or both should be flashed?
Click to expand...
Click to collapse
You use Petnoire's_SafetyNet_Spoofer_magisk or module safeynet in magisk .
Im use module safety in magisk It works perfectly.
@29y6145
What is exactly the name of that Magisk's Safety module that you mentioned?
I searched in Magisk and only found hackintosh5's SafetyPatch and Didgeridoohan's MagiskHide Props Config.
Is any of them?
My realme Q device has unlocked BL and installed TWRP, while using lineage oS 16 Android P, how to refresh this Android Q GSI image? Is it refreshed directly with TWRP REC?
@TrancyMeng.
*Any ROM in IMG format should be flashed trought Fatboot, but you need to wipe the other installation first, in adb run this to enter in TWRP:
adb reboot recovery
Then in TWRP:
*Wipe > System, Data, Cache, Dalvik
*Reboot > BootLoader (Fastboot)
Then in Fastboot/Bootloader run this command:
fastboot flash system romNAME.img
Reboot to recovery/TWRP and flash:
Permissiver_v5.zip
After refresh the Andrews Q GSI ROM, why the speaker will have a current sound, and call and play the local media file will not. How to troubleshise the patch to do it? Can you trouble with you to provide a patch for the repair sound?
THREAD CLOSED!
@29y6145 Please consult the inbox of your private messages.