Develop Bugs

[GUIDE] Restoring Swype the Easy Way

This post DOES NOT CONTAIN SWYPE BINARIES, and presumes that you have backed up your original Swype.apk and libSwypeCore.so files. If you forgot to, you can get them by doing an unyaffs on the system.img from any of your nandroid backups that would contain swype, or the G2's PC10IMG.zip, and extracting the files from system/lib/libSwypeCore.so and system/app/Swype.apk.
You can also check this post for other methods of attaining your old Swype files: http://forum.xda-developers.com/showthread.php?t=841603
DO NOT USE THIS ARCHIVE WITHOUT FIRST ADDING THE SWYPE FILES. BAD THINGS MAY HAPPEN. I'M NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE EITHER WAY.
TO RESTORE THE SWYPE FILES FROM A NANDROID BACKUP:
See this post http://forum.xda-developers.com/showthread.php?t=835971 for the original PC10IMG.zip file that should theorietically also contain it - though I have not yet figured out how to extract files from its system.img
1. Locate your nandroid backup that you know you made when you had Swype​2. Find the system.img in the nandroid backup (probably in /sdcard/ClockworkMod/backup/)​3. Open an adb shell and execute the following:
mkdir /sdcard/system
cp /sdcard/ClockworkMod/backup/YOUR-BACKUP-NAME/system.img /sdcard/system/
cd /sdcard/system
unyaffs system.img​4. Mount your sdcard on your PC and navigate to the system/app folder and copy Swype.apk to your desktop​5. Navigate to the system/lib folder and copy libSwypeCore.so to your desktop​You can now safely delete the system folder on your sdcard (it's taking up a lot of space).​
Now you should have Swype.apk and libSwypeCore.so ready to go.
Once you get those files, you're ready to create the update zip:
1. Download the FixSwype.zip attached to the bottom of this thread, and edit it with your favorite archive editor (I prefer 7-Zip, because it's open-source and fully-featured).
You should see:
system
META-INF​
2. Browse to the system/app directory, and paste in your Swype.apk
then, go back up to the system/lib directory, and paste in the libSwypeCore.so​
3. Move the new FixSwype.zip to your SD Card, either via mounting it on your PC and manually copying it, or by "adb push FixSwype.zip /sdcard/"​
4. Reboot to recovery. Navigate to "apply zip from sdcard" or equivalent function, and select your FixSwype.zip.​5. You're done! Reboot the phone, go to Settings, Language & keyboard, and check "Swype". Enjoy! You now have a permanent Swype-restoring patch.​
Of course, you'll have to re-run this process any time you install a new ROM, as the new ROM will overwrite your existing /system partition, where Swype lives.
So, whenever you install a new rom just...
1. apply the new ROM's .zip file
2. apply the FixSwype.zip file
wash, rinse, repeat!​
Want to buy me a beer? Click here!

There's not really any need for this if you're using CM. Once you have Swype on your phone, create a file in /system/etc/ called custom_backup_list.txt. Each line in the file should be the path to a file that you want preserved when you flash a new version, with the leading /system/ removed. So, for swype, your /system/etc/custom_backup_list.txt would have:
app/Swype.apk
lib/libSwypeCore.so
(I also added app/Quickoffice.apk, along with the modified files for the fixed keymap.)
Once you have this file in place, Swype (and whatever else you list) will be preserved automatically for you every time you flash a new CM.

itp said:
There's not really any need for this if you're using CM. Once you have Swype on your phone, create a file in /system/etc/ called custom_backup_list.txt. ...
Click to expand...
Click to collapse
itp,
This is really good info to have! Thanks. I've heard rumors (unconfirmed by myself) that Rom Manager does not honor this file, so I'll leave my post up for the time being, for people who may find it useful or don't feel comfortable playing in /system.

how do i do a unyaffs on my stock backup rom so i can get the swype keyboard back? Also does this work on virtuous roms?

hate to break your heart, but the easier-est way is already made just by 3 clicks in an apk.
http://forum.xda-developers.com/showthread.php?t=841603
just download the apk in the link of mediafire through your phone or from computer move it to your sd card.
use a file manager/browser to locate and install the file.
open, look for the swype which it only shows that file...click and it will do the rest for you by itself.
oh and make sure you check it in the keyboard settings and uncheck any other keyboards you might have installed.

mbergh22 said:
how do i do a unyaffs on my stock backup rom so i can get the swype keyboard back? Also does this work on virtuous roms?
Click to expand...
Click to collapse
I just now updated the post above with directions for this. Oh, and yes it should work for any/all ROMs.

GunToYoMouth123 said:
hate to break your heart, but the easier-est way is already made just by 3 clicks in an apk.
http://forum.xda-developers.com/showthread.php?t=841603
Click to expand...
Click to collapse
Neat...I had seen that post before but not since it was updated with the apk. Cool.

does that apk work with virtuous roms? and which unayffs file do i download and where do i store it?

unyaffs is a command that is built in to Android

It says unyaffs not found
Sent from my HTC Vision using XDA App

mbergh22 said:
It says unyaffs not found
Click to expand...
Click to collapse
Hmm, make sure you're spelling it right... otherwise, not sure. It's possible (but unlikely) the ROM you're using doesn't include it. It's definitely in cyanogenmod...
Edit: here's a screenshot of when I used 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"
}

From what I remember, unyaffs will not work on Mac. Are you on a Mac?

rraxda said:
From what I remember, unyaffs will not work on Mac. Are you on a Mac?
Click to expand...
Click to collapse
Nope windows 7 and I have even tried it through the terminal on my phone. I am using the latest virtuous rom.

rraxda said:
From what I remember, unyaffs will not work on Mac. Are you on a Mac?
Click to expand...
Click to collapse
This command is executed on the phone, not on the computer, so it wouldn't matter if it's Mac, Windows, Linux, BSD, etc...

mbergh22 said:
does that apk work with virtuous roms? and which unayffs file do i download and where do i store it?
Click to expand...
Click to collapse
Unfortunetly the apk i sent doesn't work for sense roms,you should ask the original poster . I tried on sense roms, and it says no swype found in back-up file. But for cm and froyo roms,it does work.
Sent from my HTC Vision using XDA App

Weaseal said:
This command is executed on the phone, not on the computer, so it wouldn't matter if it's Mac, Windows, Linux, BSD, etc...
Click to expand...
Click to collapse
Weaseal said:
Open an adb shell and execute the following:
mkdir /sdcard/system
cp /sdcard/ClockworkMod/backup/YOUR-BACKUP-NAME/system.img /sdcard/system/
cd /sdcard/system
unyaffs system.img[/INDENT]
Click to expand...
Click to collapse
My bad... I thought that when you said "open an adb shell" you were speaking of running adb shell from cmd? Is that wrong?

[Q] Wiped OS need help to sideload zip file

I just messed up big time.
I have been rooted for a couple of months now and played around with a couple of roms. I noticed my free storage shrinking when there apparently should have been nothing on my Nexus 7 except for the system files. What I did was delete my system,storage and cache with Clockworkmod Recovery leaving me with a blank tablet. Unfortunately now I can't install any zip from my sdcard as there is just emptiness on my tablet meaning I have no OS. I had initially thought I would be able to just install the OS from my usb stick but I couldn't find any way to mount my usb stick in recovery mode and I have reason to believe it just isn't possible.
As far as my research has taught me the only way to install a OS now is via sideloading it. I have spent like 2 hours reading through several threads and various other sites how to sideload a zip file onto my tablet but I'm having trouble with that. I downloaded ADB tools and I looked into this thread: http://forum.xda-developers.com/showthread.php?t=2380913
My current state is that I am in recovery mode and selected 'install zip from sideload' I have ADB tools and the OS but can't sideload it onto my tablet. When I use the command 'adb devices' my N7 is not listed. When I go to device manager the N7 is listed but there is also a warning sign displayed.
{
"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 desperately need help to resolve this issue, I love my Nexus 7 and can't bear the thought of having bricked it for good because of my own stupidity.
Much thanks in advance.
P.S. It is already late at night in Germany so I won't answer in the next few hours.

I think you are on the wrong sub-forum, this is the Nexus 7 - 2013 (2nd revision) sub-forum.
However to answer your question, personally I would boot into the bootloader and use the factory images here:
http://developers.google.com/android/nexus/images
Pick nakasi or nakasig depending on whether you have wifi or mobile version

You need to install this to use ADB while in recovery. You can use fastboot to flash the stock ROM.

sfhub said:
I think you are on the wrong sub-forum, this is the Nexus 7 - 2013 (2nd revision) sub-forum.
However to answer your question, personally I would boot into the bootloader and use the factory images
Click to expand...
Click to collapse
I'm sorry I wasn't aware of this being the wrong sub-forum.
Thanks for your submitted fix, it sounds very simple yet I don't know how to perform it. Do you mean I have to select 'Restart bootloader' on my N7?
How do I then get the factory image onto my tablet?

I'll just summarize, the factory restore is in .tgz (tar.gz) formst. Using 7-zip to open the .tgz and extract the tar file. Open the tar file in 7-zip again the get the factory image directory. Within that directoy is a batch file called flash-all.bat. It needs fastboot.exe to work. Easiest way, copy these files from your platform-tools (adb directory)
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
into the factory image directory.
Reboot your tablet into bootloader (power down, then power+vol- until bootloader menu comes up) That's the button sequence on N7 2013. I don't know about N7 2012
then just type flash-all in a command prompt. It will do the rest.
Make *sure* you get the right version of the factory restore (wifi or mobile).
Alternatively do as Username mentioned. You'll need to delete your existing drivers and install the one he pointed you to. This should get the adb connection recognized. From there you can do the adb sideload you've been attempting.

sfhub said:
I'll just summarize, the factory restore is in .tgz (tar.gz) formst. Using 7-zip to open the .tgz and extract the tar file. Open the tar file in 7-zip again the get the factory image directory. Within that directoy is a batch file called flash-all.bat. It needs fastboot.exe to work. Easiest way, copy these files from your platform-tools (adb directory)
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
into the factory image directory.
Reboot your tablet into bootloader (power down, then power+vol- until bootloader menu comes up) That's the button sequence on N7 2013. I don't know about N7 2012
then just type flash-all in a command prompt. It will do the rest.
Make *sure* you get the right version of the factory restore (wifi or mobile).
Alternatively do as Username mentioned. You'll need to delete your existing drivers and install the one he pointed you to. This should get the adb connection recognized. From there you can do the adb sideload you've been attempting.
Click to expand...
Click to collapse
The ADB/Fastboot driver from SDK only works when in bootloader and booted into ROM. Without the Naked Driver 0.72, his computer would show "Nexus 7" under Unknown Devices in the Device Manager while in recovery. He needs to install it in addition to the SDK driver for his computer to recognize the device while in recovery to Sideload or ADB push.

sfhub said:
...
Alternatively do as Username mentioned. You'll need to delete your existing drivers and install the one he pointed you to. This should get the adb connection recognized. From there you can do the adb sideload you've been attempting.
Click to expand...
Click to collapse
Username invalid said:
The ADB/Fastboot driver from SDK only works when in bootloader and booted into ROM. Without the Naked Driver 0.72, his computer would show "Nexus 7" under Unknown Devices in the Device Manager while in recovery.
Click to expand...
Click to collapse
That's why I suggested he follow your post to install the naked drivers if he wanted to use adb sideload in recovery instead of using fastboot and the images.
Username invalid said:
He needs to install it in addition to the SDK driver for his computer to recognize the device while in recovery to Sideload or ADB push.
Click to expand...
Click to collapse
According to the OP for naked drivers, he suggests removing old drivers. I just relayed what was in that post.
1wayjonny said:
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Click to expand...
Click to collapse

merchants oicedBri
Update:
Thanks for your helpful answers, I figured it out now.

[TOOL] Verizon HTC One Splash Image Creator

With all the splash screen discussion and threads popping up, I decided it was time to make a tool which could help users create and flash their own splash screens.
Verizon HTC One Splash Image Creator
This simple Windows command-line tool allows the creation of splash images, which are automatically converted to zip files and placed in the 'flash' folder, ready to be flashed, which can be flashed by the second option. It also allows the backing-up of your current splash image, as well as extracting the image from custom '.img' files.
Instructions:
S-OFF is required for this to function!
Everything needed is included aside from the image you want to be a splash screen, and the on-screen directions are quite straight-forward.
Unzip it to a location you can easily find and run 'splash.bat'. If necessary, run it as Administrator.
Make sure you maintain the folder structure as it is in the zip.
DISCLAIMER:
This tool consists of several files, most of which I didn't create. Specifically, it includes the most up-to-date ADB and Fastboot files, along with the FFMPEG free software licensed under GPL, as well as 7-Zip, also licensed under GPL. I am not making money from this tool, therefore everything should be copacetic. All I'm doing is collecting them in one place, making it significantly easier to perform its specific function.
I can not be held responsible for your use of this tool. Flashing custom images generally can't brick your device, but if it does, the fault lies with you, the user. I am not liable. Use this tool at your own risk. This is for the Verizon HTC One only!
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"
}
Known Issues:
When creating a splash image, sometimes it asks you to specify whether the destination is a file or directory. It's a directory. I have overwrite and quiet mode on, so it shouldn't pop up and ask that. It only does it about 2 out of 30 times.
When flashing the splash zip, it sometimes tells me that fastboot flash isn't a valid command, despite it working without changing anything since the last time I ran it. I also tested it about 30 times, and it also only gave me that error twice. It immediately reboots and works again right after that without any modification.
Potential Limitations:
I have only been able to test this on the 1.10.605.8 software release. I don't know if you need to change the text in the android-info.txt file in the '/tools/' folder to the updated version or not. I would appreciate it if someone would test that for me who is currently on the new update.
Changelog:
Code:
v1.01 - Bux fix regarding folder structure.
v1.0 - Initial release.
Download:
http://d-h.st/OTD
Please let me know if you discover any bugs, or if you think you know why I have the two I have now. Also, let me know if it works on the .10 software update.

RESERVED

This isn't working for me. Its saying that '/tools/adb.exe' does not exist.

sebastianraven said:
This isn't working for me. Its saying that '/tools/adb.exe' does not exist.
Click to expand...
Click to collapse
Are you maintaining the folder structure as it is in the zip?
EDIT:
I did leave a bug in there regarding folder structure. I was operating from C:\ during testing, and left "C:" in there as part of the test for whether the needed files existed. If you were operating on a drive letter besides C:, it would throw that error. I removed that drive letter requirement. Please download version 1.01 and try it again from any drive letter you like.

IceDragon59 said:
Are you maintaining the folder structure as it is in the zip?
EDIT:
I did leave a bug in there regarding folder structure. I was operating from C:\ during testing, and left "C:" in there as part of the test for whether the needed files existed. If you were operating on a drive letter besides C:, it would throw that error. I removed that drive letter requirement. Please download version 1.01 and try it again from any drive letter you like.
Click to expand...
Click to collapse
Ok. Here's what I did:
Redownloaded the zip.
Unzipped and moved it to my C: drive to make this as simple as possible.
Ran as Administrator
Selected #2.
Got the same error.

sebastianraven said:
Ok. Here's what I did:
Redownloaded the zip.
Unzipped and moved it to my C: drive to make this as simple as possible.
Ran as Administrator
Selected #2.
Got the same error.
Click to expand...
Click to collapse
That's very odd. Are you placing a picture in the 'image' folder, using option #1 and converting it to the flashable zip, then trying to flash it? If there's no zip to flash, it throws an error, even though that's the wrong error.

ak074 said:
if this creates the .img to be flashed via hboot, then the android-info.txt will need to be changed to reflect the current version of the phone.
Click to expand...
Click to collapse
I know there is a way to fix it but yea it's better to be safe than sorry
on rezound I accidentally flashed a leaked one, so i couldn't flash any of these, we eventually figured out a way to fix it thankfully but it was a lesson learned

Good job man!
Worked great for me.
Thanks!

I would like to start using this tool, but I am using santods modded no-text hboot from the latest OTA...
What should the android-info.txt file have? do i just change the mainver?

peteschlabar said:
I would like to start using this tool, but I am using santods modded no-text hboot from the latest OTA...
What should the android-info.txt file have? do i just change the mainver?
Click to expand...
Click to collapse
I've used this with multiple ROMs and HBOOT versions, including the newest one, without altering anything in this program, and all worked without a problem. While I can't guarantee that that will always be the case, I haven't come across any problems as of yet. Flashing a splash image generally can't screw your phone up, but there are always exceptions. I really should update this tool with more specific instructions. Maybe I'll do that while I'm off over the holidays. To be specific in what I've tested it with, I've listed everything that I recall testing it with. I haven't seen it fail yet, and I haven't updated it since the original version.
ROMs tested with:
1.08.605.8
1.08.605.10
1.08.605.15
2.10.605.1
CM 10.2
HBOOTs tested with:
1.08.605.8 HBOOT 1.54.0000
1.08.605.10 HBOOT 1.54.0000
1.08.605.15 HBOOT 1.54.0000
2.10.605.1 HBOOT 1.55.0000
Santod's modded HBOOT 1.54.0000
RegawMOD Bootloader Customizer HBOOT 1.54.0000

Thanks! Worked great on 1.55hboot ViperOne 4.2.1 rom. Great work.

[GUIDE] Flash 'fastboot ROMs' for Lenovo Z6 Pro

Disclaim
All steps described here have been many times tested and proved to be safe but, you may know that sometimes in life unexpected things happen. I'm not responsible for any damage in your devices, do things at your own risk.
Introduction
Thanks to xda user @alexeei we can install almost every Z6 Pro stock ROMs using the Fastboot Mode. You always should check the package content and the installation script(s) to be sure that you know exactly what is gonna be installed. You can find all the ROMs listed and linked in this index.
Let's go with the guide.
0. Pre-requirements
- The Bootloader must be unlocked.
- Lenovo drivers installed in your computer. You can download them here . Thanks @benjieb
1. Download and extract the ROM
You cand find many of them here. Extract the downloaded file and a folder will be created with these contents:
- All the files required for the installation in Fastboot Mode.
- The ROM files.
- The .bat file(s) which contain(s) all the actions that will be performed during the installation.
{
"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 always should check the content of the .bat file(s). Read post #2 to get more info about this.
2. Reboot your device in Fastboot Mode
Shut down your device and boot it holding pressed both Volume Down + Power buttons until the Fastboot Mode menu appears. You can navigate in the Fastboot Mode menu with volume buttons to choose the options and the Power button to confirm, but at this point you don't need to do any action in this menu.
3. Connect the device to the computer with USB cable
4. Execute the .bat file
Just execute the .bat file with a double click and a CMD window will be opened and the installation will start. Only a few lines will appear at the beginning and then nothing will happen, it will seem to be stopped but actually it's not, just be patient because this screen could last around ten minutes. So despite of the 'Invalid sparse file format at header magic", keep the faith and don't do anything but wait.
The device will reboot once the installation is done.
5. Errors in the log. No voice in calls.
Some errors may appear in the CMD window during the installation, this is because some partitions are 'critical' and we're not allowed to modify them via fastboot. Usually this is not a problem because these "small partitions" don't prevent the new ROM to work normally, except if you're installing Android 10 from Android 9. If you change Android version with this method you will find that your micro doesn't work in calls. You can fix it installing these "small partitions" from TWRP.
Any correction, info or advise about this post will be very welcome.

About the .bat file(s):
You always should check the content of these files before doing any installation, specially with recent fastboot installers including several .bat files for diferent uses. Just open the .bat file with right click and select Edit to view the actions included in the file.
None of Alexei's fastboot installers have never included any command to erase Data, but I'd say it's mandatory to check twice the .bat file to be sure that you're not going to affect an undesired partition. In case e.g. the .bat file includes the line 'fastboot flash system system.img' but you don't want System partition to be installed, just delete this line from the file and Save before closing it.
Maybe you want to edit the file to include in the batch any other thing, a custom recovery for instance. Just drop your custom recovery file in the rom folder (the fastboot installer folder) and make sure that the line in the .bat file regarding the recovery matchs with your recovery file name.
Also you can notice that recent fastboot installers include more than one .bat file. They are named in a descriptive way like "UpdateZUI.bat" or "UpsateAOSP", but you should check them anyways. Let's say you're using any of the Q aosp-based custom ROMs (they include Boot and System partitions) and you want to update the vendor and/or the firmware. You should check the .bat files to find which of them suits better with your needs.

descarao81 said:
About the .bat file(s):
You always should check the content of these files before doing any installation, specially with recent fastboot installers including several .bat files for diferent uses. Just open the .bat file with right click and select Edit to view the actions included in the file.
None of Alexei's fastboot installers have never included any command to erase Data, but I'd say it's mandatory to check twice the .bat file to be sure that you're not going to affect an undesired partition. In case e.g. the .bat file includes the line 'fastboot flash system system.img' but you don't want System partition to be installed, just delete this line from the file and Save before closing it.
Maybe you want to edit the file to include in the batch any other thing, a custom recovery for instance. Just drop your custom recovery file in the rom folder (the fastboot installer folder) and make sure that the line in the .bat file regarding the recovery matchs with your recovery file name.
Also you can notice that recent fastboot installers include more than one .bat file. They are named in a descriptive way like "UpdateZUI.bat" or "UpsateAOSP", but you should check them anyways. Let's say you're using any of the Q aosp-based custom ROMs (they include Boot and System partitions) and you want to update the vendor and/or the firmware. You should check the .bat files to find which of them suits better with your needs.
Click to expand...
Click to collapse
Thanks for your instruction. Will this method work on other lenovo devices. I have a lenovo tablet running android 10 chinese stock rom, now I would like to flash global stock rom

hilary trump said:
Thanks for your instruction. Will this method work on other lenovo devices. I have a lenovo tablet running android 10 chinese stock rom, now I would like to flash global stock rom
Click to expand...
Click to collapse
It depends on the rom package. The packages made to be installed using fastboot are usually very similar, but you should check the .bat files. I could take a look if you provide a link.

descarao81 said:
It depends on the rom package. The packages made to be installed using fastboot are usually very similar, but you should check the .bat files. I could take a look if you provide a link.
Click to expand...
Click to collapse
Thanks. The rom has not released yet. I just pre-ordered a chinese variant tablet P11 pro TB-J706F

descarao81 said:
It depends on the rom package. The packages made to be installed using fastboot are usually very similar, but you should check the .bat files. I could take a look if you provide a link.
Click to expand...
Click to collapse
I found the link as follows
mirrors.lolinet.com/firmware/lenovo/ Tab_P11_Pro/TB-J706F/TB-J706F_S210002_201015_ROW.zip
But inside the package there is no BAT file though

How To Guide Simple Guide How To Root

Alright so a lot of people seem to have issues with rooting their device and creating a lot of spam on this forum because they don't know how to read.
This guide is for Windows PCs and will be for the people who don't want to read complicated guides.
What you Need:
A Device that has an unlocked Bootloader
The Factory Image of the ROM you are using or updating to Download Here
The Latest STABLE Magisk Download Here, if you are opting for a Beta/Canary then have fun.
7-zip or similar file extractor
ADB and Fastboot, I use Minimal ADB and Fastboot but this Script Here will download the latest version and add it to your PATH.
Way to Transfer Files to Phone (USB Cable?)
Steps:
Update to the Latest ROM. This can be done via Sideloading (personal preference) or OTA
Confirm you are on the same version as the factory image. Current is SP2A.220305.013 aka March 2022 Update
Extract the Zip File to a Folder. Current filename is raven-sp2a.220305.013.a3-factory-87b3bf0a.zip
Go in to the folder and extract the Image ZIP into a Folder. Current Name is image-raven-sp21.220305.003.zip
Find the Boot.img and transfer it to your device.
Install the Magisk Manager APK on the Device
Open Magisk and press Install.
Select "Select and Patch a File" and select the Boot.img you transferred to your device.
Magisk will patch the file and place the new .img file in your downloads. The filename will look like "magisk_patched-24300_abcde.img".
Transfer the patched file from your Downloads folder to your PC.
Reboot your phone to Fastboot mode Youtube Tutorial
Locate the patched .img file and press SHIFT+RightClick, click the option "Copy as Path"
On your PC open Command Prompt. If you dont know how to do this, you shouldn't be rooting your device.
In command prompt type "fastboot flash boot" and then paste the location of your patched .img file.
The whole command should look like "fastboot flash boot "C:\Users\Admin\Downloads\magisk_patched-24300_abcde.img"
Reboot the phone with the command "fastboot reboot"
Once the device is booted up, go to Magisk and see if you are rooted.
If there is enough demand, I can provide photos to help.
If I messed up along the way, let me know and I can change the guide.

Saved

{
"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 can't find my Downlaods folder. Idk what that is.

Gytole said:
View attachment 5574243
I can't find my Downlaods folder. Idk what that is.
Click to expand...
Click to collapse
Fixed lol

vassosman said:
Alright so a lot of people seem to have issues with rooting their device and creating a lot of spam on this forum because they don't know how to read.
This guide is for Windows PCs and will be for the people who don't want to read complicated guides.
What you Need:
A Device that has an unlocked Bootloader
The Factory Image of the ROM you are using or updating to Download Here
The Latest STABLE Magisk Download Here, if you are opting for a Beta/Canary then have fun.
7-zip or similar file extractor
ADB and Fastboot, I use Minimal ADB and Fastboot but this Script Here will download the latest version and add it to your PATH.
Way to Transfer Files to Phone (USB Cable?)
Steps:
Update to the Latest ROM. This can be done via Sideloading (personal preference) or OTA
Confirm you are on the same version as the factory image. Current is SP2A.220305.013 aka March 2022 Update
Extract the Zip File to a Folder. Current filename is raven-sp2a.220305.013.a3-factory-87b3bf0a.zip
Go in to the folder and extract the Image ZIP into a Folder. Current Name is image-raven-sp21.220305.003.zip
Find the Boot.img and transfer it to your device.
Install the Magisk Manager APK on the Device
Open Magisk and press Install.
Select "Select and Patch a File" and select the Boot.img you transferred to your device.
Magisk will patch the file and place the new .img file in your downloads. The filename will look like "magisk_patched-24300_abcde.img".
Transfer the patched file from your Downloads folder to your PC.
Reboot your phone to Fastboot mode Youtube Tutorial
Locate the patched .img file and press SHIFT+RightClick, click the option "Copy as Path"
On your PC open Command Prompt. If you dont know how to do this, you shouldn't be rooting your device.
In command prompt type "fastboot flash boot" and then paste the location of your patched .img file.
The whole command should look like "fastboot flash boot "C:\Users\Admin\Downloads\magisk_patched-24300_abcde.img"
Reboot the phone with the command "adb reboot"
Once the device is booted up, go to Magisk and see if you are rooted.
If there is enough demand, I can provide photos to help.
If I messed up along the way, let me know and I can change the guide.
Click to expand...
Click to collapse
It should be fastboot reboot

fil3s said:
It should be fastboot reboot
Click to expand...
Click to collapse
Good call, I was writing this on the fly and wasn't actually doing it as I was writing the guide.

fil3s said:
It should be fastboot reboot
Click to expand...
Click to collapse
Rather than saying they don't know how to read", it might be that they don't understand the "meta-language" of any given discussion or explanation!

EdBurger l said:
Rather than saying they don't know how to read", it might be that they don't understand the "meta-language" of any given discussion or explanation!
Click to expand...
Click to collapse
Goodo bruh.

vassosman said:
Saved
Click to expand...
Click to collapse
Do you really think this guide is too hard to follow? It's thoughtful that you typed out the steps but is it really less confusing or difficult?
[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com

Is the whole vbmeta / boot verification thing no longer necessary?
I tuned out from all the root stuff because I only unlocked in the beginning and didn't want to wipe.

.

dmarden said:
Is the whole vbmeta / boot verification thing no longer necessary?
I tuned out from all the root stuff because I only unlocked in the beginning and didn't want to wipe.
Click to expand...
Click to collapse
They are not required to change if you plan on running Magisk 24.3. I did not change anything when I updated my P6P (bought in Feb) and rooted it.

dmarden said:
Is the whole vbmeta / boot verification thing no longer necessary?
I tuned out from all the root stuff because I only unlocked in the beginning and didn't want to wipe.
Click to expand...
Click to collapse
not needed anymore with latest magisk

That's great news, I've been missing it.

I am going to do this on S3B1.220218.006 (QPR3 Beta 1.1). Fingers crossed!

Worked perfectly, the only thing I might add is a link to the Google USB Drivers (since they must've updated). I had them installed originally (to have unlocked my device in the first place) but needed to update them.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Thanks a ton! I would've never noticed that the wipe step was no longer needed.

I recognize I am replying a lot, haha... sorry about that.
Presumably the update method for this should work exactly like past Pixel devices, yeah?
For me, this method was as follows:
1. Download the full image and edit the script to remove the "-w"
2. Install the modified image
3. Boot up once
4. Then basically follow the original procedure from this thread again
I know on OnePlus devices I was always able to uninstall Magisk root via the Magisk app, take the OTA, then reinstall Magist root via the Magisk app before rebooting, but that never seemed to work on Pixel devices (at least for me).

Just to share...
I decided to give the Magisk restore images, OTA, install again before reboot method a try and it worked perfectly going from QPR 1.1 to 2.

Thank you for this post. I would like to root my phone. I am a noob and it’s a little intimidating. If you would add pictures, I for one, would really appreciate that. Thanks again!