Develop Bugs

Nexus 7 2013 wifi FLO 32gb not showing Internal memory in windows 10 pro

Hello guys,
When I connected this nexus 7 to computer it will show nexus 7 but it will not SHOW INTERNAL MEMORY of nexus 7, I can not transfer files into nexus 7.
1 . I have enabled USB debugging and all options are enabled
2. I am running CM13 custom ROM. THERE IS NO CONNECTION MANAGER IN THIS ROM OR USB SETTING TO ALLOW MTP./
3, I tried going to recovery and then i connect to this windows 10 and it wont show INTERNAL MEMORY.
I have tried all drivers but it will not OPEN NEXUS 7 INTERNAL MEMORY.
my samsung s6 work FINE IN SAME COMPUTER
please look screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I THINK ITS NEXUS SETTING OR PROBLEM, WHY SAMSUNG S6 WORK PERFECTLY??
Any help is appreciated. Thank you

Hi, on CM13 pull down notifications and change 'USB for charging' to MTP.

k23m said:
Hi, on CM13 pull down notifications and change 'USB for charging' to MTP.
Click to expand...
Click to collapse
ok, it worked in CM13 but how to make it work when its in recovery???

Administr4tor said:
ok, it worked in CM13 but how to make it work when its in recovery???
Click to expand...
Click to collapse
I note you're using the obsolete CWM recovery but if you try TWRP it will work for sure.

k23m said:
I note you're using the obsolete CWM recovery but if you try TWRP it will work for sure.
Click to expand...
Click to collapse
I have tried twrp latest for my model but soon aas I flash twrp it goes into TWRP and twrp starts rebooting again and again. so I flashed cwm just to make things work, anyways I think, I have to live with it like this.
Thank you

update v12.0.3.0.QJZMIXM for Redmi Note 9 Pro

anyone updated to the latest update care to comment, thanks in advance

I can't do it (on a rooted device: Note 9 Pro)
The update file is 616.8MIB
miui-blockota-joyeuse_global-V12.0.2.0.QJZMIXM-V12.0.3.0.QJZMIXM-41e0213a6b-10.0.zip
Impossible with the MIU installer or with TWRP 3.5.0_10-0
Always a error message
I also need some help
{
"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"
}

vin100 said:
I can't do it (on a rooted device: Note 9 Pro)
The update file is 616.8MIB
miui-blockota-joyeuse_global-V12.0.2.0.QJZMIXM-V12.0.3.0.QJZMIXM-41e0213a6b-10.0.zip
Impossible with the MIU installer or with TWRP 3.5.0_10-0
Always a error message
I also need some help
View attachment 5296013
Click to expand...
Click to collapse
I'm not sure where this OTA update could be used with custom recovery. even for the stock recovery it seems the whole recovery flash image is required

Thanks @koshikas , I've found a fastboot update
joyeuse_global_images_V12.0.3.0.QJZMIXM_20210419.0000.00_10.0_global_0801ff7d09.tgz
Will I lose all my data with it?

vin100 said:
Thanks @koshikas , I've found a fastboot update
joyeuse_global_images_V12.0.3.0.QJZMIXM_20210419.0000.00_10.0_global_0801ff7d09.tgz
Will I lose all my data with it?
Click to expand...
Click to collapse
i think so, although i havent done that myself

vin100 said:
Thanks @koshikas , I've found a fastboot update
joyeuse_global_images_V12.0.3.0.QJZMIXM_20210419.0000.00_10.0_global_0801ff7d09.tgz
Will I lose all my data with it?
Click to expand...
Click to collapse
no

just know that fastboot and recovery update methods are not the same

Thanks @koshikas, I know. That's why I'll wait some more experienced people here. I'm afraid to loose some data in the operation. If you've a good link for a ultra safe backup & easy restore I'll love it

vin100 said:
Thanks @koshikas, I know. That's why I'll wait some more experienced people here. I'm afraid to loose some data in the operation. If you've a good link for a ultra safe backup & easy restore I'll love it
Click to expand...
Click to collapse
MiFlash has options to flash with & without wiping. You can backup with the built-in tool or try Alpha Backup on play store.
Your recovery is outdated and is the reason for the failed flash. Try orangefox or dungphp's TWRP/Pitchblack.
Finally you can force a download of the full rom and not just the update from the updater app. It's in the menu at the top right. If you don't see it tap the 'currently installed' text a bunch.
Or just click here to download

[RECOVERY] TeamWin Recovery Project 3.5.2 [UNOFFICIAL]

{
"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"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Instructions
Download TWRP-3.5.2-RMX182X.img from the download link
Place the file in adb folder
Power off your device
Go to fastboot mode by holding Power and Volume Down buttons
Connect your phone to PC
Flash recovery by typing this command
Code:
fastboot flash recovery TWRP-3.5.2-RMX182X.img
Boot into recovery by typing this command
Code:
fastboot reboot recovery
Requirements
Realme 3 Device
PC with fastboot drivers installed or bugjager in another android device
Recovery image
Download
TWRP-3.5.2-RMX182X.img
What's Working?
Decryption
MTP
Flashing images and zips
Backup and Restore
Wiping and Formating
Everything else
Bugs
None
Tell me if you find any
Sources
Recovery Source : https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-10.0
Device Tree : https://github.com/Maanush2004/android_device_realme_RMX1821/tree/twrp-10.0
Screenshots
Spoiler
Thanks to testers
Spoiler
Their Telegram usernames are given below
HELLINFIX
ct_world
Omkarv
TrueTech21
S11K4M4K4N
supremacy_kraken
azharmansoori22

What your custom Rom work? Or you recommend ?

Geri:) said:
What your custom Rom work? Or you recommend ?
Click to expand...
Click to collapse
I am also wondering which ROM I can use as a daily driver too..

Agent Lu said:
I am also wondering which ROM I can use as a daily driver too..
Click to expand...
Click to collapse
Yeah me too, base on your flashing which one is good for gaming and stable? im flashing my realme 3 so i can give the phone to my son.

Will it work on Android 10? If not , can u make one that can be flashed on Android 10. Thnx.

OnePlus 7T Nethunter installation help

Hello Guys,
I was trying to install Nethunter On my OnePlus 7T Europe with Android 10
10.0.9-EUROPE-OnePlus7TOxygen_14.E.11_OTA_011_all_2003271950_b7c5bfe612-FASTBOOT.zip​ using following instruction:
Installing NetHunter On the OnePlus 7 | Kali Linux Documentation
From a reset to running NetHunter in 4 steps: Flash latest Android 10 with the unbrick tool Flash TWRP and Magisk Disable force encryption of data partition Install NetHunter Disable OnePlus update service 1. Flash latest stock (OOS) Android 10 1.01. Download and unzip...
www.kali.org
But I had used:
Twrp:
Download TWRP for hotdog
Download TWRP Open Recovery for hotdog
eu.dl.twrp.me
Magisk:
Release Magisk v23.0 · topjohnwu/Magisk
This release is focused on fixing regressions and bugs. Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 only supports Android 5.0 and higher. Bug Fixes [App]...
github.com
I am unable to install with error from screen:
{
"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"
}
Error Failed to mount /system_ext also appears on Magisk and decrypt tool installation.

I saw that a lot of people have seen this, but no one has commented, so I'll just throw you a few guesses. 1. Possibly a bad download of either Kali or your Recovery. 2. However, you said it happens with Magisk too, so I'm thinking it also might be the wrong recovery, are you sure that you have the right recovery.img for your model number? And if so, is it a reliable recovery.img? I know that there is guacamole, guacamoleb, hotdog and hotdogb and there were a handful of unstable TWRP builds due to the force encryption. More information about your device and resources would help, what's your model number, what version of platform tools are you on?
P.s. I'm also assuming that the photo of the log isn't of an instance where you were flashing it through Magisk as a module because you said it happens with Magisk too.
P.s.2 I know you said your phone is the Europe variant, but I'd assume not to many people memorize every model number for devices that they don't own, I'd say that's why we have codenames like guacamole, lol.

Question Rooted Pixel 6 Pro - no longer receiving updates

Hi all, I have rooted my pixel 6 pro since day 1 and always used the magisk way of patching and restoring images for updates, since the February update Google tells me updates are no longer supported on my device per screenshots, anyone else had this issue and know how to resolve it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You might want to backup, uninstall magisk in the app, reboot. Then full reset/wipe and reboot. Then manually update to the latest May 2022 version using adb or the android flash tool. Something has gone awry with your software. Better to be safe than sorry.

Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.

Gytole said:
Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.
Click to expand...
Click to collapse
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?

zamarax said:
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?
Click to expand...
Click to collapse
Nope! Quite the opposite if I get stuck in a bootloop I just use the flash tool to fix it. No loss of data, but you need to re-boot the magisk boot image then reflash in magisk afterwards as it will completely remove magisk

So I did what you suggested and now my device is stuck in a boot loop with corrupt data, I did however patch the boot.img previously when I tried to send it to the device via ADB so I'm going to try to push that now and see what happens. Here are the options I selected for Android Flash Tool.

Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!

zamarax said:
Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!
View attachment 5608917
Click to expand...
Click to collapse