Database Develop

Ota update from l10_b126 to b133

Hi,
I received the official update for my l10 from b126 to b133.
But after download I receive a checksum error.
Any ideas? Also the downloaded update.zip cannot be opened with zip viewers.
PS: rooted but stock recovery
{
"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"
}
Edit: solved by deleting the HWOUC folder on external SD and initiated update again

Almost the same problem for me, once it reaches the recovery to install the update, it gives error.

Worked for me then, don't forget to be on stock recovery

Yeah I was on TWRP but then I restored the stock recovery taken from this post to install this OTA update:
http://forum.xda-developers.com/showpost.php?p=53980121&postcount=4
But no matter what after everything is downloaded and I give the 'ok' to install it, it stops at the recovery giving a 'FAIL' message big a quarter of the screen.

I'm using the same. Maybe its worth to download again by deleting the folder and initiating the download again.
Any hint on why it fails?

May I know how did you install the stock recovery?
I did the following:
-Connect phone to PC by debug mode
-adb reboot bootloader
Then phone goes into bootloader, flash mode:
-fastboot flash boot boot.img
-fastboot flash recovery recovery.img
-fastboot flash recovery2 recovery2.img
I noticed that in the archive of the stock recovery, there's also a build.prop file. Am I missing something perhaps?
Anyway the "FAIL" error appears when the recovery is attempting to install the update at the 2/10 of the status bar, therefore after the checksum which means the update file is not corrupted.
I also tried several times to delete and re-download the update as you said but still no success..

No, I only flashed recovery.img via flashify.
So maybe it is due to recovety2.img? Just a guess

I just tried to flash just the recovery.img but still the same error.
I honestly can't think of any other solution now than a a lot of time wasting full wipe..

I had the same problem. Tried deleting folder etc.
What worked for me was updating using HiSuite. Connect phone with cable with pc/laptop and use HiSuite for update. Made backup just to be sure but wasn't needed.

I was trying to do a nandroid backup and update via HiSuite like you suggested but then I encountered this.
Surely something is wrong my system partition lol, any ideas of why is it so huge? The previous backups were just 1.5 GB.
Perhaps I'll just do a backup of the apps with Helium and move on.

That's strange. For your information. I had already the original recovery in place. So I did the backup from HiSuite (It came with this option). I didn't made a backup with TWRP or Nandroid backup.

I'll try again this weekend and let you know the results, thanks anyway!

TWRP / Encryption / Mount issue when trying to root [OP3T]

Hi All. Complete newbie to the forum here......in search of advice!
I've just got my new OnePlus 3T, so wanted to get it all set up and rooted before switching over from my Galaxy S5.
After reading several guides I followed the below steps:
Completed the OTA update to OOS 4.0.2
Unlocked the boot loader
Flashed TWRP 3.0.3
Booted into Recovery and TWRP asked for the encryption password (which was the same pattern I used in normal mode)
Internal memory was accessible so I proceeded to flash no-verity-opt-encrypt zip and SuperSu.zip. (I couldn't tell if they flashed successfully).
Rebooted
When the phone tries to reboot, I eventually get a screen saying 'Encryption Unsuccessful' and suggests I need to factory Reset.
When I select to reset, it boots back in to TWRP, but there is no request for the encryption pattern this time, and internal memory doesn't seem to mount. (showing as 0mb).
I'm wondering what my next step should be?
Should I try to flash the latest TWRP (3.0.4) via ADB?
Or would I be better off trying to flash back on stock recovery and the stock OOS 4.02 rom, and then wait for a newer TWRP before trying to get root access again?
.......Or will none of the above work?!
All I was really looking to do was root the phone. I'm not planning on changing from the stock OOS rom. I also don't mind if its encrypted or not encrypted.
I have had a look through some of the threads, but cant find examples of this scenario. Any help appreciated!

Which SuperSU file did you flashed?

The-Wexican said:
I proceeded to flash no-verity-opt-encrypt zip and SuperSu.zip.
Click to expand...
Click to collapse
I hope you didn't flash in that exact order. That could possibly be the reason for your issue. Also, you don't need the verity zip if you're flashing SuperSU.

Thanks for the feedback. Below is a link to the guide I followed on the Oneplus forums:
[GUIDE] OnePlus 3T: How to Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup and More !! (It wont let me link the thread as I'm a new user, but Google will show it!
That suggested to flash them in that order, I think.
SuperSU-v2.79-201612051815.zip was the SuperSU I used.

All, just to add, I don't need to recover any data or anything like that. I'm just looking for the best way to get out of this bot loop (of sorts).
I'm kinda thinking that because TWRP Recoveryseems to load OK, I could maybe flash back on the stock recovery and then side load the stock rom?
Any thoughts?
Or is it worth a shot at updating to the latest TWRP first (3.0.4)?

Below is the message I see when I try to boot the phone normally now (not in recovery)........
{
"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-Wexican said:
Below is the message I see when I try to boot the phone normally now (not in recovery)........
Click to expand...
Click to collapse
I did what you did 2 days ago with success.
I recommend you flash back to stock and do the following:
-New devices boot
-Received OTA 7.0, 4.0.2 OOS
-fastboot oem unlock routine
-Flashed TWRP 3.0.4-0 - follow every step of: https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391 - read this 5 times, step 11 only requires you pick A) OR B), do not flash both
-Flash UPDATE-SuperSU-v2.79-20161211114519.zip (if you picked Step 11 A), that's what I did).
-Reboot
-Success

stephlal said:
I did what you did 2 days ago with success.
I recommend you flash back to stock and do the following:
-New devices boot
-Received OTA 7.0, 4.0.2 OOS
-fastboot oem unlock routine
-Flashed TWRP 3.0.4-0 - follow every step of: https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391 - read this 5 times, step 11 only requires you pick A) OR B), do not flash both
-Flash UPDATE-SuperSU-v2.79-20161211114519.zip (if you picked Step 11 A), that's what I did).
-Reboot
-Success
Click to expand...
Click to collapse
Awesome!
That worked. Thanks for your help!
Now running OP3T with OOS 4.0.2, TWRP recovery, rooted with SuperSU, and I even cleared the DM-Verity nag screen by booting into bootloader and running:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Very happy now!

brick p20 pro

Hello,
I have a problem with my device.
I made the command "erase all data / decrypt internal storage" via tool in one, since I can not boot normally anymore.
I try to flash a custom rom via erecovery
I try to flash a custom rom via tool in one
I try to flash a custom recovery via fastboot but it does not take the custom
i try a wipe userdata data via fastboot is erecovery but it can not.
an idea?
please help me

winny067406 said:
Hello,
I have a problem with my device.
I made the command "erase all data / decrypt internal storage" via tool in one, since I can not boot normally anymore.
I try to flash a custom rom via erecovery
I try to flash a custom rom via tool in one
I try to flash a custom recovery via fastboot but it does not take the custom
i try a wipe userdata data via fastboot is erecovery but it can not.
an idea?
please help me
Click to expand...
Click to collapse
try reflash factory system via erecovery not a custom rom!

spityu85hun said:
try reflash factory system via erecovery not a custom rom!
Click to expand...
Click to collapse
the boot recovery properly,
it download the rom but hangs on the wipes data,
yet I have already done wipes data via tool in one (erase all data, decrypt internal storage).
I also perform wipes data via the terminal "fastboot boot erase datauser"

winny067406 said:
the boot recovery properly,
it download the rom but hangs on the wipes data,
yet I have already done wipes data via tool in one (erase all data, decrypt internal storage).
I also perform wipes data via the terminal "fastboot boot erase datauser"
Click to expand...
Click to collapse
help me please

{
"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"
}

second screen command

Mine was bricked too after downgrading from pie 195 to oreo 161.... Fastboot detected but black screen and red led. Flashed everything through fastboot kernel, recovery_ramdisk, system but no way to boot or enter erecovery. Sent to warranty last Tuesday and took it back Saturday with motherboard + screen changed. I'm lucky but unfortunately I have new imei and no more bootloader unlocked.
Thinking of selling it for oneplus 7 or xiaomi mi9.....

deltaman83 said:
Mine was bricked too after downgrading from pie 195 to oreo 161.... Fastboot detected but black screen and red led. Flashed everything through fastboot kernel, recovery_ramdisk, system but no way to boot or enter erecovery. Sent to warranty last Tuesday and took it back Saturday with motherboard + screen changed. I'm lucky but unfortunately I have new imei and no more bootloader unlocked.
Thinking of selling it for oneplus 7 or xiaomi mi9.....
Click to expand...
Click to collapse
flash stock rom via tool in one, ( generic stock rom)

winny067406 said:
help me please
Click to expand...
Click to collapse
just flash stock huawei recovery in recovery_ramdisk and format again. this will bring back the partition table that you deleted.
i hope while trying to unbrick that you didn't flash any s-hit you found around....
if you flashed many s-hit then you must use the update function using an external usb. the update will flash all partitions and unbrick you

[SOLVED] Redmi 9 (lancelot) System Destroyed + Locked Bootloader problem

{
"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"
}
my friend's phone, he said it happen after updating firmware
anyone have an idea how to fix it ?
bootloader locked btw, and no mi account associated to the devices
already try this but no success, still need auth
Redmi 9 brick problem solution.
1.if you are above v11.0.8.0 then go and follow below link... https://forum.xda-developers.com/t/disable-authorization-and-unbrick-your-redmi-9.4228213/ ================================== 2.Else follow it...
forum.xda-developers.com

Can you get into fastboot mode with power+volume down button?

cqkhai06 said:
Can you get into fastboot mode with power+volume down button?
Click to expand...
Click to collapse
yes, but when i flash official firmware, it said not allowed because bootloader is in locked state

SOLVED
i follow this video
use the tool provided on that video
and flash lancelot_global_images_V11.0.4.0.QJCMIXM
then on SP Flash tool i select Format All + Download scheme then hit Download button
connect the phone USB, and hold Volume +, Volume -, Power Button
until MediaTek USB Port detected on Device Manager
then Flashing progress started automatically, and BOOM!!! done

co2thunderboy said:
yes, but when i flash official firmware, it said not allowed because bootloader is in locked state
View attachment 5330193
Click to expand...
Click to collapse
Try to download the official Mi flash tool and flash the fastboot miui rom in fastboot mode. The method which you're following is used for hard brick device that cant get into fastboot mode.

get another flashtool and download bypass auth.
if imei null or error.
i managed to make 2 imei redmi 9.
1. unlock bootloader, flash rom eng!!! or assembled rom.
2. After completing write IMEI using Maumeta version 10.
3. install twrp and backup nvram and nvdata on rom eng!!!, copy the twrp backup results to the computer.
4. flash format & download global rom, then unlock bootloader again, turn on the phone until the start menu, then turn off the phone and install twrp, then put the backup results into twrp and restore, then install the kernel from strombreaker v1.0, when finished immediately reboot the system.
goodluck, it worked 1000%

Is it important to the install kernel ?
hckbkl said:
get another flashtool and download bypass auth.
if imei null or error.
i managed to make 2 imei redmi 9.
1. unlock bootloader, flash rom eng!!! or assembled rom.
2. After completing write IMEI using Maumeta version 10.
3. install twrp and backup nvram and nvdata on rom eng!!!, copy the twrp backup results to the computer.
4. flash format & download global rom, then unlock bootloader again, turn on the phone until the start menu, then turn off the phone and install twrp, then put the backup results into twrp and restore, then install the kernel from strombreaker v1.0, when finished immediately reboot the system.
goodluck, it worked 1000%
Click to expand...
Click to collapse

yess
Sorry I can't reply because my account was hacked.
to write 2 imei you must use kernel,
on boot if not use kernel custom Redmi9 will bootloop,
if you want to use 1 imei my advice use version 11.0.4.0 better in communication.

Are you sure the phone is not stolen?

How To Guide Guide to Flash Miui_VILIGlobal_V13.0.1.0.SKDMIXM_e7e8f0ef90_12 and use Magisk

Hello All,
Quick and dirty guide.
Warning!
I'm not responsible for any damage to you, to your device or to your data. Do this at your OWN RISK! If you don't know what you are doing, STOP now!
Steps to flash the ROM using TWRP:
Be on Android 11 (MIUI 12.5) and flash TWRP. There is a guide here on how to do it, so i'm not posting that.
Obviously, you'll need unlocked bootloader so if it's not unlocked, your case is lost
Download the ROM in the title from here and copy it to your phone
Reboot to TWRP
If you want, i guess you can wipe data - i haven't done this
Flash the ROM like you would any other (install and select the zip you copied over from the above link)
At the end, it'll give you mounting error but it's all good, reboot
Wait for the ROM to settle if you wish - you can stop here
For Magisk, follow the below steps
Enable developer settings and USB debugging
Install the Magisk Manager app (latest version 24.1 at the time of writing this little guide)
Turn off the phone and boot it into fastboot mode
Start the fastboot app of your choice from your pc and connect your phone via USB (I'm using Minimal ADB and Fastboot, you can find it on XDA)
issue the following commands in the same order:
Code:
fastboot devices
if you don't get as a response a few digits of your device ID with the fastboot text next to it, you'll doing something wrong (driver might be or you are not in fastboot mode)
Code:
fastboot flash boot_a patched_boot.img
if the command completes you'll get a finished message
Code:
fastboot flash boot_b patched_boot.img
patched_boot.img is the full path of the patched boot.img file
Code:
fastboot reboot
wait for the device to boot.
Patched boot.img is attached but if you wish, you can extract it from the rom yourself using payload dumper and patch it on your phone with Magisk. The attached boot.img is patched with Magisk 24.1, this is what you'll need as well - this is the current version. You need to unzip the attached file of course!
Enjoy.

{
"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"
}

Just flashed by TWRP and reset to the factory. So far there is no fastboot image, only recovery one, and normal way it is not possible to flash it as it is only for Mi Pilot people.

Pichulec said:
Just flashed by TWRP and reset to the factory. So far there is no fastboot image, only recovery one, and normal way it is not possible to flash it as it is only for Mi Pilot people.
Click to expand...
Click to collapse
what do you mean with "no fastboot image"?

There are two types of images - recovery and fastboot.

Hello, im trying your guide but my phone stuck on fastboot mode and when im try to enter twrp, it stuck on frozen screen i cant swipe to unlock twrp....any idea?(

Yuditkiichi said:
Hello, im trying your guide but my phone stuck on fastboot mode and when im try to enter twrp, it stuck on frozen screen i cant swipe to unlock twrp....any idea?(
Click to expand...
Click to collapse
Hi, if TWRP worked before, it should as well now.

donjamal said:
Hi, if TWRP worked before, it should as well now.
Click to expand...
Click to collapse
Any idea how to solved my twrp problem? Or should i reflash it with pc?

Yuditkiichi said:
Any idea how to solved my twrp problem? Or should i reflash it with pc?
Click to expand...
Click to collapse
I would probably relfash twrp as long as I'm still on 12.5.

Yesterday received OTA update for my 11t pro. I'm not in Pilot Programm..

Yuditkiichi said:
Any idea how to solved my twrp problem? Or should i reflash it with pc?
Click to expand...
Click to collapse
for now twrp not working for a12.
wait for update

All can download rom here https://xiaomifirmwareupdater.com/miui/vili/stable beta/V13.0.1.0.SKDMIXM/
and use updater to update it.. that dont need any mi pilot.. i just installing it.. yeeah!