Database Develop

How to downgrade from 5.0.1

I got a used phone i537UCUCOC7 android 5.0.1. What do i do to downgrade and can i when security patch?

cell2011 said:
I got a used phone i537UCUCOC7 android 5.0.1. What do i do to downgrade and can i when security patch?
Click to expand...
Click to collapse
To downgrade to KitKat, download the following file to your PC and extract with 7zip or WinRar: https://www.androidfilehost.com/?fid=23991606952608110
Boot your phone into download mode. This is done by powering the phone off, then holding down vol- and power at the same time. Connect the phone to PC with USB. You have to flash all four files with Odin as shown in the following image:
{
"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"
}
Please be aware that this process will erase any settings, data, and media saved to your phone's internal storage and restore it to its original factory condition, now on KitKat. This process also takes a long time (at least 5 or 10 minutes) and will cause your phone to reboot on its own, and to boot into stock recovery at least once. It is important you leave your phone alone while it is doing so, and definitely do not disconnect it until it boots into the KitKat setup wizard screen.
To apply the security patch, you will now have to flash two files in stock recovery (vol+ and power). First download and extract this file: https://www.androidfilehost.com/?fid=96042739161891196 it should be named 2400258.cfg. You need to rename it update.zip (yes, this involves changing the file type) and save update.zip to your external SD card (it will not work if it's on internal storage).
Finally, you need to download this file to your external storage and flash in stock recovery: https://www.androidfilehost.com/user/?w=settings-dev-files&flid=37222 Please note this file has already been renamed update.zip. They must both be named update.zip for them to work; since this can be potentially confusing I'd advise you to either save them to different folders, or delete the first one after you're done with it.
Follow these steps and you'll be back on KitKat, with that all important security patch. Good luck :good:

[GUIDE] Installing/Flashing Treble ROMs

I am not responsible for people bricking their devices because they haven't made a backup.
Click to expand...
Click to collapse
{
"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"
}
Downloads
TWRP For P10 lite: HERE
ADB & Fastboot: HERE
The first step is to make a backup.
2. Download your Treble ROM, i recommend a GSI ROM.
In my case I'll be using Havoc-OS
Download: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/rom-havoc-os-8-1-t3819050
3. Go into TWRP and do a FACTORY RESET and then reboot into fastboot.
4. The only thing you need to do now is flash the ROM, so get your downloaded ROM & extract the .img file from it (if there is no .img file and you see other files, flash via twrp).
On your PC open the fastboot command prompt and type
fastboot -u flash system <YourImageFileHere>
Click to expand...
Click to collapse
After just type : "fastboot reboot" and wait until your phone boots into the system. You may need to flash google apps afterwards.
It is normal for the phone to reboot a couple times so be patient.
Congratz, your phone is not running a treble ROM with your stock ROM's vendor.
Click to expand...
Click to collapse
Video:

I just need backup Boot, System and data if i want go back to stock?

Bad idea to factory reset with TWRP, it doesn't do it clean enough.
You could get in serious problems by doing it, such as random apps crashing, sd unmounting and worse.
Safer option is to factory reset and wipe cache with stock recovery after every system flash.
I'm telling this from my own experience, I don't want people to mess up like I did :highfive:

Ret-Zero said:
I just need backup Boot, System and data if i want go back to stock?
Click to expand...
Click to collapse
Yes that should be enough, vendor stays the same anyway.. I recommend flashing roms designed for kirins cpus btw because there is a higher chance it will work

[Solved] Help with TWRP and VENDOR

Hello, I am a owner of a ZUK Z2 Pro from Brazil, apologies for my english.
I tried to update the mooke rom to pie, but it wasn't working via central mooke, so I downloaded and tried to flash on TWRP, but I was possesed by a demon and instead of not deleting the internal storage, I delete all files. The problem now is that the mobile isn't reconigze in the computer and the device manager shows this:
{
"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"
}
The USBView show this:
Maybe it's something related to the vendor folder that can't be mount on TRWP. I tried adb push, but don't display my device and I don't have acess to allow the usb debugging. I tried USB OTG, but the pendrive is unrecognized. I don't know what to do anymore, but I don't think the mobile is bricked. May day may day!

In twrp you have to click mount otg to make it visible in the file system (if you already did this you can try different adapters/usb sticks). If you deleted the vendor partition I think you should be able to fix it by going back to stock or finding a vendor image/backup. If the only problem is that you ran the vendor to factory script and now twrp dies not find it you can just update twrp. Updating twrp could also help with the unrecognized usb issue.

craftandbuild said:
In twrp you have to click mount otg to make it visible in the file system (if you already did this you can try different adapters/usb sticks). If you deleted the vendor partition I think you should be able to fix it by going back to stock or finding a vendor image/backup. If the only problem is that you ran the vendor to factory script and now twrp dies not find it you can just update twrp. Updating twrp could also help with the unrecognized usb issue.
Click to expand...
Click to collapse
I can't mount otg because twrp don't let me selected the option, I had install all drivers I found of zuk, lenovo and qualcomm and still unrecognizable on the computer, therefore I can flash stock or the vendor image/backup, the version of my twrp is the 3.3.0.0, the most updated. You know if there is a way to force the computer to recognize the device?

Solved doind this.

Question Can't install Xiaomi EU ROM - Stuck without a ROM

I've followed the process outlined here. After installing the ZIP, it rebooted, but went back to recovery. When I said reboot system, it said No OS installed.
So, I tried to start over by formatting data and then copying the zip again via ADB Push. Then the trouble starts. After adb push, which takes about 5 minutes, it says
Code:
failed to copy 'xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip' to '/sdcard/xiaomi.eu.zip': write failed: No space left on device
After that, the data partition seems corrupted. Whenever I go to Install, it shows 0 bytes. Upon Googling I found a solution by formatting to ext2 and back to ext4. Then, it shows again as 100000MB. However, adb push every time fails with same problem.
For some weird reason, I can push to /data. But still running into same problem after installing ROM and rebooting, it goes back into recovery.
I also tried to sideload, but then I run into this issue:
Code:
D:\Tools\ROMs>adb sideload xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip
loading: 'xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip'
* cannot read 'xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip' *
So, I'm stuck with a device without any ROM. Any suggestions please?

Did you ask in the MIUI EU forums as well? Since there would be more ppl familiar with these issues than here.
I'm also interested in this since I prefer EU roms. Also you need a specific TWRP version which I believe is still in alpha stage for the 10 Pro since its still a new device. There should be a TWRP thread somewhere here where you can also ask.
I just got my 10 pro and need to wait a few more days to unlock BL, then I will be flashing an EU rom, hence my interest. Hope you find a solution.

Use TWRP from here:
https://forum.xda-developers.com/t/4248449/
fastboot reboot bootloader
fastboot boot TWRP_file_name.img
Format Data, type yes.
{
"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"
}
Reboot to recovery.
The internal storage should be visible.
Connect phone to PC and put ROM into phone.
Flash ROM, format data, yes
Reboot to system.
If above not work, make your phone under fastboot mode, Mi-Flash, and flash your stock fastboot MIUI. Don't lock your bootloader.

Flashing stock rom RQ3A.211001.001 on Redfin device using Android Flash Tool partial progress, fails to fastbootd when entering flashboot userspace

{
"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 previously successfully installed and ran lingeageOS for a long time. In attempting to flash stock android, I'm getting a part-way successfully then failing to a screen titled 'fastbootd' when the flash script attempts to enter userspace fastboot. I'm running Arch Linux and have android tools installed locally as well with the android-tools package. I can start the device into fastboot mode and see it on my PC with `fastboot devices`:
$ fastboot devices
13091FDD4000GY fastboot
I would prefer to install android 11, but I've also tried android 12 with the same end failure result.
How can I troubleshoot this further? Any help is much appreciated!

brian_says_yas said:
View attachment 5517961
I previously successfully installed and ran lingeageOS for a long time. In attempting to flash stock android, I'm getting a part-way successfully then failing to a screen titled 'fastbootd' when the flash script attempts to enter userspace fastboot. I'm running Arch Linux and have android tools installed locally as well with the android-tools package. I can start the device into fastboot mode and see it on my PC with `fastboot devices`:
$ fastboot devices
13091FDD4000GY fastboot
I would prefer to install android 11, but I've also tried android 12 with the same end failure result.
How can I troubleshoot this further? Any help is much appreciated!
Click to expand...
Click to collapse
Hi Brian, have you tried a different usb cable? I only use windows so I can help more if you get a windows PC or run windows from a usb. I also unlock the bootloader manually with the ADB tools, first before using the flash tool.

So I switched to a macbook and a different USB cable both at the same time, and it worked. I'm speechless lol. Thank you for your help! Honestly the biggest benefit here is that I don't have to use Android 12 yet which was buggy as hell on my Pixel 6 Pro before someone did me the favor of stealing it in Miami.