I can't seem to get TWRP or Cyanogen Recovery to flash succesfully CM12.1. They refuse to flash ROM zips, but do flash Gapps. I've tried ADB sideload to flash CM12.1, but ADB doesn't find my E3 no matter what I do. I go to recovery, and choose ADB sideload. Then I do adb devices and it just says "List of devices attached", but no devices. I can only use fastboot succesfully, which that made me think that I could decompress the zip and make the boot.img, system.img, and userdata.img out of it to flash through fastboot. I got all the required filesfrom the zip to make userdata.img and system.img (boot.img was already in there). I only have one problem: I haven't found a way to re-pack the files into the correct img format to be able to flash it through fastboot.
So, back to my question:
Has anyone managed to flash the CM12.1 zip successfully? If so, how?
Or, can someone show me how to repack the system files into system.img and the userdata files into userdata.img?
Can someone help me with a LENOVO TAB 3 TB3-850M stock rom or custom rom that i can flash ? I cannot find anywhere. Installed TWRP and file system got messed up, needed to repartition . Or a TB3-850F, they are pretty much the same
tzmst said:
Can someone help me with a LENOVO TAB 3 TB3-850M stock rom or custom rom that i can flash ? I cannot find anywhere. Installed TWRP and file system got messed up, needed to repartition . Or a TB3-850F, they are pretty much the same
Click to expand...
Click to collapse
Here is a link to my TB3-850F Stock Firmware Images. (/system, /boot, /recovery, /logo). You will need an unlocked bootloader, Minimal ADB & Fastboot v1.4 installed on your PC, proper USB Device Drivers, and the ability to boot into fastboot mode (or recovery mode, and boot into fastboot mode from there). Once you have downloaded my firmware images and are in fastboot mode, open a command window in your adb/fastboot directory with your Tab 3 properly connected to your PC. Type "fastboot devices" - if you are properly connected to your PC with the requisite drivers, the command window will return with your device serial number under "Connected Devices." Once you have ensured a proper connection, execute these commands to install the stock firmware:
fastboot oem fb_mode_set
fastboot flash system system.img
(At this point, because the system.img is a 3GB file, fastboot will automatically condense the file into a series of "sparsechunk" images, which fastboot will flash to your device in series until completed. Note, this process can take a few minutes so be patient. Also, ensure you are using the minimal adb & fastboot from my link (v1.4 or newer) to ensure proper sparsechunk conversion)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash logo logo.img
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
You should now be restored to pure stock firmware condition. Note: this stock firmware is for the Lenovo Tab 3 8"/TB3-850F and has not been tried on the TB3-850M variant. You flash these images at your own risk. Good luck.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
Updated Stock 6.0 ROM posted. Force encryption and dm-verity disabled. TWRP flashable zip.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-t3617594
How to update your phone even after unlocking your phone without losing data in Lenovo K8 Plus?
There is a pretty simple trick for those who wanted to update to latest firmware & already unlocked their device.
First unroot & if you flashed xposed then xposed uninstaller too then use fastboot to flash stock recovery, boot & system & then do the OTA update & Voila your data will not loose and you just get update.
To do it download stock firmware click below
HTML:
https://drive.google.com/uc?id=1YexKxunNYF_RemzFmvHpoSgp8eELebqY&export=download
Password:-
[email protected] Developers
Extract this firmware.
Then you'll find several files there just copy system.img, boot.img, recovery.img to adb folder and then put your phone in fastboot mode and then type:-
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
After this power it up download the update and install it.
Note:- This trick is only tried on manning as of now. But I'm pretty sure that it'll work on marino too.
Credits:- Dhruv , Prem & Me?
Thanks man
I have realized that there isn't a guide to root the G91 PRO (not the max, for whatever reason that got rooted before the pro...) anyway, I figured out how to do it, and I'm probably not the first one. Since I haven't been able to find the stock rom on the internet, I strongly advise you backup your stock rom with mtkclient.
This is an A/B device, so we need to flash to both slots.
First, dump your stock rom with this tool: https://github.com/bkerler/mtkclient
This is mtkclient. It reverse engineers BROM or Preloader mode so that we can pull down the flash. Once you put your phone in BROM mode, use this command to back up the whole flash. (To put your phone in BROM mode, power off your phone and hold down volume up, down, and power and the same time while plugging in a USB-C cable)
python3 mtk rf flash.bin
Now that we've made a backup, we can start screwing around with the phone. If you ever need to restore your backup then all you need to do is:
python3 mtk w flash.bin
Inside of that flash bin you can find all the partitions inside of it. I use 7zip to look inside of the archive. Look for boot_a.img. After you find it, use magisk manager to root the stock boot.img.
If you don't want to look inside of the archive and would prefer to just dump the boot images, then just run these commands instead.
python3 mtk r boot_a boot_a.img
python3 mtk r boot_b boot_b.img
Now we can also use this mtkclient software to unlock the bootloader. We don't have to use mtkclient, we could use bootloader mode after enabling oem unlocking in developer options, but we can do this too.
We first have to erase metadata, userdata, and md_udc.
python3 mtk e metadata, userdata, md_udc
Now we can unlock the bootloader.
python3 mtk da seccfg unlock
After unlocking the bootloader, you can now flash partitions. Flash your patched boot.img in bootloader mode.
fastboot flash boot_a (patched boot.img)
fastboot flash boot_b (patched boot.img)
Inside of the mtkclient folder, you will find a file called vbmeta.img.empty. This is a patched vbmeta (its blank haha) so that we can disable verified boot. we need to flash it to both slots.
fastboot flash vbmeta_a (vbmeta.img.empty)
fastboot flash vbmeta_b (vbmeta.img.empty)
That's all!
Edit: I decided to attach my rooted and non rooted boot img for those who want to do it quickly. You can flash magiskboot_a.img to both slots, as they are the same. I caution you though, only flash my provided boot.img if your build number and custom build number matches the one in the screenshot I provided. Build number can be checked in Settings>About Device>Build Number and Custom Build Info. Make sure to also flash the empty vbmeta so you don't have any dm verity errors!
is build id same as build number?and can i flash that boot_a.img in bugjaeger app?
ziyad45 said:
View attachment 5620469is build id same as build number?and can i flash that boot_a.img in bugjaeger app?
Click to expand...
Click to collapse
This is not the same phone. You can't flash the boot.img. However, the specs are identical. You could probably follow the method I used to root this phone.
dtingley11222 said:
I have realized that there isn't a guide to root the G91 PRO (not the max, for whatever reason that got rooted before the pro...) anyway, I figured out how to do it, and I'm probably not the first one. Since I haven't been able to find the stock rom on the internet, I strongly advise you backup your stock rom with mtkclient.
This is an A/B device, so we need to flash to both slots.
First, dump your stock rom with this tool: https://github.com/bkerler/mtkclient
This is mtkclient. It reverse engineers BROM or Preloader mode so that we can pull down the flash. Once you put your phone in BROM mode, use this command to back up the whole flash. (To put your phone in BROM mode, power off your phone and hold down volume up, down, and power and the same time while plugging in a USB-C cable)
python3 mtk rf flash.bin
Now that we've made a backup, we can start screwing around with the phone. If you ever need to restore your backup then all you need to do is:
python3 mtk w flash.bin
Inside of that flash bin you can find all the partitions inside of it. I use 7zip to look inside of the archive. Look for boot_a.img. After you find it, use magisk manager to root the stock boot.img.
If you don't want to look inside of the archive and would prefer to just dump the boot images, then just run these commands instead.
python3 mtk r boot_a boot_a.img
python3 mtk r boot_b boot_b.img
Now we can also use this mtkclient software to unlock the bootloader. We don't have to use mtkclient, we could use bootloader mode after enabling oem unlocking in developer options, but we can do this too.
We first have to erase metadata, userdata, and md_udc.
python3 mtk e metadata, userdata, md_udc
Now we can unlock the bootloader.
python3 mtk da seccfg unlock
After unlocking the bootloader, you can now flash partitions. Flash your patched boot.img in bootloader mode.
fastboot flash boot_a (patched boot.img)
fastboot flash boot_b (patched boot.img)
Inside of the mtkclient folder, you will find a file called vbmeta.img.empty. This is a patched vbmeta (its blank haha) so that we can disable verified boot. we need to flash it to both slots.
fastboot flash vbmeta_a (vbmeta.img.empty)
fastboot flash vbmeta_b (vbmeta.img.empty)
That's all!
Edit: I decided to attach my rooted and non rooted boot img for those who want to do it quickly. I caution you though, only flash my provided boot.img if your build number and custom build number matches the one in the screenshot I provided. Build number can be checked in Settings>About Device>Build Number and Custom Build Info. Make sure to also flash the empty vbmeta so you don't have any dm verity errors!
Click to expand...
Click to collapse
My g91 pro doesn't seem to work with mtk client it but I have the same build as you.
To root my phone I need to have boot image a and b? I noticed just image a is attached and I can't find a rom download for the g91 pro anywhere.
Did you use img a for both?
Any help would be great.
Thanks
Longdelayecho said:
My g91 pro doesn't seem to work with mtk client it but I have the same build as you.
To root my phone I need to have boot image a and b? I noticed just image a is attached and I can't find a rom download for the g91 pro anywhere.
Did you use img a for both?
Any help would be great.
Thanks
Click to expand...
Click to collapse
You might not be entering brom correctly. The rom is not available on the internet. You only need boot_a because the boot imgs are the same for both slots. You can flash it to both a and b with no issue.
Hey do you think this would work on the G61S?
have tried to disassemble the boot.img and recovery.img to create custom TWRP, but the bloody files won't unpack. Have used AIK, adb and fastboot
flash payload.pin
Download the firmware files from redmagic's support site and use Fastboot Enhance to flash the payload
Bricked my phone couple of hours ago fixed this way