Hello all,
I have a Zenfone 2 (ze551ML aka Z00A), with TWRP 3.02, with a broken usb port, so I can't connect it to a computer.
I'm trying to upgrade my bootloader, from a Lollipop bootloader to a Marshmallow Bootloader. (in order to upgrade to Lineage 14.1)
To do this, I have some files, which are supposed to be flashed using fastboot. The script is as follow:
Code:
fastboot flash splashscreen splashscreen_551.img
fastboot flash token bom-token_ze551ml_4_21_40_134.bin
fastboot flash dnx dnx_ze551ml_4_21_40_134.bin
fastboot flash ifwi ifwi_ze551ml_4_21_40_134.bin
fastboot flash fastboot droidboot_4_21_40_134.img
fastboot reboot-bootloader
flash recovery TWRP-3.0.3-M3-Z00A.img
Since I can use that, I'l trying to do it from within TWRP, using it's Terminal.
1) The TWRP terminal provides a "flash_image" binary.
I guess I can do :
Code:
flash_image splashscreen splashscreen_551.img
flash_image fastboot droidboot_4_21_40_134.img
flash_image recovery TWRP-3.0.3-M3-Z00A.img
Is that correct ?
2) Is there a way to flash the other bin files ?
My TWRP doesn't have any binary like flash_token, flash_ifwi, or flash_dnx.
But maybe I can do flash_image token bom-token_ze551ml_4_21_40_134.bin ? (and so on)
3) The updated TWRP version I'm flashing (3.0.3-M3-Z00A) is supposed to be only compatible with the M bootloader.
Is it safe to only issue the commands listed in 1), or am I at risk of having an "incomplete" bootloader, by not flashing the ".bin" files ?
While I'm pretty sure that the ifwi is only baseband related, I don't know what bom_token and dnx are for.
Thanks for reading !
PS: Apologies is not the right forum to post. I feel like it is more related to TWRP than Zenfone2, but I can move to the Zenfone2 sub-forum if needed.
Related
Hi all!
Occasionaly flashed blue spark twrp v41 (for OOS 3.x) while on Sultans ROM with locked bootloader.
No root access, didn't flash supersu. Kingroot and other 'on one click' methods somehow don't work.
Now, when I try to use fastboot to flash recovery it denies as bootloader is locked. When I try to unlock bootloader using 'oem unlock' it tries to boot recovery which doesn't boot (stucks on logo).
Any chance to solve without hardbricked solution?
I'm on OOS 2.2.2 and have done the same thing (flashed blu spark v41)... same result as you though, a phone I can only boot into fastboot mode
This was the advice I was given (from OnePlus forums)...
https://forums.oneplus.net/threads/...lus-logo-help-me-please.462406/#post-15248530
Here are the steps to get TWRP without messing up your recovery partition
>> Grab Bootloader file (emmc_appsboot.mbn) from OxygenOS Lollypop stock rom
>> Place it in Adb& fastboot folder and flash it via fastboot
fastboot flash aboot emmc_appsboot.mbn
>> Now Type
fastboot reboot-bootloader
>> Now temporarily boot TWRP official recovery for OPX with fastboot
fastboot boot "yourTWRPfileNAME.img"
You should be able to boot to TWRP recovery now
After Flashing and stuff reboot to fastboot and
>> Grab Bootloader file (emmc_appsboot.mbn) from Oxygen OS Marshmallow stock rom
>> Place it in Adb& fastboot folder and flash it via fastboot
fastboot flash aboot emmc_appsboot.mbn
Reboot and enjoy
Click to expand...
Click to collapse
Edit: Maybe you'll need to flash the emmc_appsboot.mbn file from the Sultans ROM though???
The above didn't work for me. I had to UnBrick
You cannot install a recovery on locked bootloader,your phone is not going into stock recovery because of some boot failure, just turn off your phone remove battery if its removable then try again to go into recovery
Sent from my HUAWEI TIT-AL00 using XDA Forums
Download link: https://drive.google.com/file/d/1gLshzM9zYEvR0Cknl4eh6KI32nEZbL5O/view?usp=sharing
I tried backing up the userdata.img, but that kept filling up my device storage. It was going beyond 19GB in size. So I cancelled the operation.
Enjoy these files, they will be useful for ROM porting, system restore, or system downgrade.
Editing these files can lead to a brick or a non booting state. So be careful.
I pulled all of these files from my device's system partitions.
What did you do to dump these? Did you use dd to dump them or any other method? I dumped a few partitions from my BNTV460 a while back, but I'm unsure if I did it properly, so I was curious of how you dumped it from your BNTV650.
turtleletortue said:
What did you do to dump these? Did you use dd to dump them or any other method? I dumped a few partitions from my BNTV460 a while back, but I'm unsure if I did it properly, so I was curious of how you dumped it from your BNTV650.
Click to expand...
Click to collapse
I temp rooted the Nook. Then I pulled the firmware files with ADB.
I saw that global MediaTek root tool posted earlier, I was just going to dump the partitions myself. Thank you for posting these OP! Does anyone know if there's a TWRP image for our devices? There's one posted for a "Barnes & Nobel Nook Tablet", but I haven't a clue if it's for the BNTV650.
I did make a TWRP for this device.
tgp1994 said:
I saw that global MediaTek root tool posted earlier, I was just going to dump the partitions myself. Thank you for posting these OP! Does anyone know if there's a TWRP image for our devices? There's one posted for a "Barnes & Nobel Nook Tablet", but I haven't a clue if it's for the BNTV650.
Click to expand...
Click to collapse
How to unlock the bootloader:
1) allow OEM unlocking in developer options in the device settings
2) download ADB onto your computer https://developer.android.com/studio/releases/platform-tools.html
3) cd to the directory in CMD
4) enter this command: adb reboot bootloader
5) once the device is in fastboot mode, do: fastboot oem unlock
How to flash the stock OEM recovery:
1) fastboot flash recovery STOCK_recovery.img
How to flash the tested buggy TWRP recovery:
1) fastboot flash recovery TESTED_recovery.img
How to flash the untested TWRP recovery:
1) fastboot flash recovery UNTESTED_recovery.img
How to reboot back into the OS:
1) fastboot reboot
Downloads:
- Stock: https://drive.google.com/file/d/1Z7AJH6fSbeOkLLWt2JVwsCKiwxt0vlYK/view?usp=sharing
- Tested: https://drive.google.com/file/d/1R4ph5Z5mofsac0Qd352H_BEEz9JS4wBA/view?usp=sharing
- Untested: https://drive.google.com/file/d/1zP81MuR5LLvdYuDvYQHPVCJlgCOUBPlt/view?usp=sharing
secretwolf98 said:
How to unlock the bootloader:
1) allow OEM unlocking in developer options in the device settings
2) download ADB onto your computer https://developer.android.com/studio/releases/platform-tools.html
3) cd to the directory in CMD
4) enter this command: adb reboot bootloader
5) once the device is in fastboot mode, do: fastboot oem unlock
How to flash the stock OEM recovery:
1) fastboot flash recovery STOCK_recovery.img
How to flash the tested buggy TWRP recovery:
1) fastboot flash recovery TESTED_recovery.img
How to flash the untested TWRP recovery:
1) fastboot flash recovery UNTESTED_recovery.img
How to reboot back into the OS:
1) fastboot reboot
Downloads:
- Stock: https://drive.google.com/file/d/1Z7AJH6fSbeOkLLWt2JVwsCKiwxt0vlYK/view?usp=sharing
- Tested: https://drive.google.com/file/d/1R4ph5Z5mofsac0Qd352H_BEEz9JS4wBA/view?usp=sharing
- Untested: https://drive.google.com/file/d/1zP81MuR5LLvdYuDvYQHPVCJlgCOUBPlt/view?usp=sharing
Click to expand...
Click to collapse
Oh, there are recoveries? Thanks! What's wrong with the buggy version?
I will try to update this thread soon with the latest software update. If I can remember how I pulled the system files.
secretwolf98 said:
I will try to update this thread soon with the latest software update. If I can remember how I pulled the system files.
Click to expand...
Click to collapse
Did B&N release a software update?
tgp1994 said:
Did B&N release a software update?
Click to expand...
Click to collapse
Yep. It is v1.0.21. With the build date of June 2020. And with the security patch of May 5, 2020.
so there is no twrp or custom rooted rom for this device?
root: for A.87 stock rom
Unlock bootloader and place the mentioned two files to Platform tools folder on your pc.
Download "vbmeta.img" and "Magisk_patched.img"
• adb devices
• adb reboot bootloader
•fastboot devices
• fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
• fastboot flash boot magisk_patched.img
• fastboot reboot
+++±+++++++
Guide to flash Recovery
- Connect your phone to PC, Allow USB Debugging. Now Type These Commands.
adb reboot bootloader
fastboot devices
fastboot reboot bootloader
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery recoveryname.img
fastboot reboot recovery
To keep custom recovery flash twrpkeep.zip when's booted to recovery :
Bro my device is a.89 ..is this vbmeta working...?
qeb said:
Bro my device is a.89 ..is this vbmeta working...?
Click to expand...
Click to collapse
Yes it work on all a10 update
@albatron34000
Please change "fastboot flash bootj magisk_patched.img" for "fastboot flash boot magisk_patched.img" thank you
ALSO
>fastboot erase recovery
>fastboot reboot recovery (?)
misiek998 said:
@albatron34000
Please change "fastboot flash bootj magisk_patched.img" for "fastboot flash boot magisk_patched.img" thank you
ALSO
>fastboot erase recovery
>fastboot reboot recovery (?)
Click to expand...
Click to collapse
oh, thank's men. edited.
Hello, Can I use the VBMeta on android 11 or no? thanks!
Ryeeeeel said:
Hello, Can I use the VBMeta on android 11 or no? thanks!
Click to expand...
Click to collapse
Can't root rui 2.0 (Android 11), and can't install custom recovery except "los recovery" but can't do any thing with it just wiping cache and data partition.
do not try to flash custom recovery on realme ui 2.0 , it will brick your device
I need to ask, this guide will work with A88/A89 update?
sorry for noob question - I'm not familiar with mediatek devices and rooting/flashing stuff. Currently I'm running crdroid. What steps are neccessary to get rooted stock? is it:
- flash original firmware (how? SPTool?)
- issue all the commands from OP?
Or do I need anything else?
adamuadamu said:
sorry for noob question - I'm not familiar with mediatek devices and rooting/flashing stuff. Currently I'm running crdroid. What steps are neccessary to get rooted stock? is it:
- flash original firmware (how? SPTool?)
- issue all the commands from OP?
Or do I need anything else?
Click to expand...
Click to collapse
Yes. Just flash the original firmware using SP Flash-Tools. However, youmust make sure it is the full 7-8 GB ROM, and not an OTA file. Also, ensure that you are flashing the correct ROM for your model. If your model is an RMX2155, you'll need to follow this guide steps 1-through-to-10 (inclusive):
[GUIDE] REALME 7 RMX2155 GLOBAL BOOTLOADER UNLOCK
WELCOME, ALL. After a very tiring process of swapping between ROMs and changing regions, APKs, et cetera, we have finally been able to perfect the method for unlocking the bootloader of the RMX2155! This is a detailed guide aimed to give you an...
forum.xda-developers.com
If it is any other model, just do what is said to work. Unfortunately, I don't know much about the other versions.
thanks the explanation.
I've found a 2155 ROM or at least a file that's said to be - ie. I've found a file 'RMX2155export_11_C.09_2021070809260000', extracted that, there was a huge file 'RMX2155export_11_C.09_2021070809260000.ofp' inside; using oppo-decrypt from github I've got bunch of files with names that seem to be SPFlashTool ROM.
Assuming it's a proper ROM: if I have already unlocked the bootloader, do I have to flash the rom and do the 10 steps from the tutorial or could I replace recovery.img and magisk-patched boot.img and flash rooted rom immediately? Sorry if it sound noobish, but I don't want to brick the phone.
I'm curious to try to go back to stock ROM for a while, because of call quality (I believe changing it to Vietnam needed for unlock made the call quality worse) and to check the camera and it's libraries - I'm running crdroid, photo quality is disappointing no matter what GCam/settings/tweaks I use and there are only imx682/imx471 libs on the phone there are samsung libs, but diagnose apps like aida show the main sensor is imx682, but the EU version of realme 7 is said to have different back camera sensor (GM1). Not sure if RMX2151 ROMs would include proper GM1 libs if that's true about sensor differences between RMX2151 and 2155.
I have bricked my X3 SZ and worked 1 week to get it unbricked (bricked after update of Android 11) myself, even the service centre not able to restore it and told me that may be Motherboard Problem. Finally by flashing Android 11 Stock images (created using OFP to CMD file converter), I restore the phone. I tried with unlocked Bootloader mode, don't know about locked bootloader state.
Simply download the stock images from the link and boot into bootloader mode, connect to PC, open Minimal ADB Fastboot and flash with fastboot commands. Required USB, Realme, Android Drivers to be installed in the PC. All your data will be lost and do it at your own risk.
Download all the images (userdata, recovery, boot, vbmeta & dtbo) and copy to the Minimal ADB Fastboot folder, run the CMD prompt and run the following commands:
fastboot devices (to check whether phone connected successfully or not)
fastboot erase userdata
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash userdata userdata.img
fastboot flash dtbo dtbo.img
fastboot reboot
Done.. your X3 SZ must reboot and starts, if not you need to work around or contact SC.. Good Luck
Link Deleted
Thx
EDIT: Very informative and useful!
Cant get magisk_boot.img to work. Going to try orangefox recovery to install Magisk (root).
Tried numerous times to install it (here) took 3-4 hours to get Python to work in windows 7 (cus missing libraries, and newer version dont work). Its bricked the phone 3 times now.
I tried to install TWRP but failed, after I tried Orangefox, successfully installed but not able to boot, rebooting into recovery only, then I flashed only boot image using fastboot and able to boot but lost Custom Recovery. After all I stopped trying anything on X3 SZ
please provide new link
Hi there ,
I am currently having an issue and would appreciate some help .
What I want:
A new OS on my Android device. I actually dont care which OS, so i just chose LineageOS (In order to get rid of a Stock-ROM-Error)
[Rooting would also solve the Problem, but I cant get to either solution, see below]
What I have:
Lenovo Yoga Tab 3 Pro 10 (YT3-x90f)
Android 6.0.1
OEM unlocked
Bootloader unlocked
adb and fastboot connection to Win10 PC works
What I did:
Before I can install another OS, I need another Recoverysystem.
To achieve that I tried:
1.
start cmd with admin
"cd <PathFile to fastboot.exe and .img-file>
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery twrp.img"
reboot to recovery
2.
start cmd with admin
"cd <PathFile to fastboot.exe and .img-file>
adb reboot bootloader
fastboot flashing unlock
fastboot boot twrp.img"
In the pictures I used Powershell instead of CMD (But that was due to an fastboot Error, that I could solve with existing posts in the forum )
And here comes the current Main-Problem:
In CMD I can flash or boot any .img file to the android device without error messages.
But on my tablet I ALWAYS get the following Error:
"bzimage kernel corrupt
couldnt load boot image: invalid parameter"
I tried the following .img files:
TWRP
- 3.6.2
- 3.6.1
- 3.1.1
- 3.0.2
- 2.8.7
- 2.5.0
OrangeFox
To Outrule an Error or an Incompatibility in the img file from TWRP I tried OrangeFox and got the same message.
Thanks a lot in advance for your time
Sven_Wolf said:
Hi there ,
I am currently having an issue and would appreciate some help .
What I want:
A new OS on my Android device. I actually dont care which OS, so i just chose LineageOS (In order to get rid of a Stock-ROM-Error)
[Rooting would also solve the Problem, but I cant get to either solution, see below]
What I have:
Lenovo Yoga Tab 3 Pro 10 (YT3-x90f)
Android 6.0.1
OEM unlocked
Bootloader unlocked
adb and fastboot connection to Win10 PC works
What I did:
Before I can install another OS, I need another Recoverysystem.
To achieve that I tried:
1.
start cmd with admin
"cd <PathFile to fastboot.exe and .img-file>
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery twrp.img"
reboot to recovery
2.
start cmd with admin
"cd <PathFile to fastboot.exe and .img-file>
adb reboot bootloader
fastboot flashing unlock
fastboot boot twrp.img"
In the pictures I used Powershell instead of CMD (But that was due to an fastboot Error, that I could solve with existing posts in the forum )
And here comes the current Main-Problem:
In CMD I can flash or boot any .img file to the android device without error messages.
But on my tablet I ALWAYS get the following Error:
"bzimage kernel corrupt
couldnt load boot image: invalid parameter"
I tried the following .img files:
TWRP
- 3.6.2
- 3.6.1
- 3.1.1
- 3.0.2
- 2.8.7
- 2.5.0
OrangeFox
To Outrule an Error or an Incompatibility in the img file from TWRP I tried OrangeFox and got the same message.
Thanks a lot in advance for your time
Click to expand...
Click to collapse
There is only one working TWRP recovery available for this tablet here (the data enabled one in post #2). If you have any questions about it, go to this thread.