I just rooted my Nexus 4 using Ubuntu 12.04.
The instructions I found weren't quite what I'd liked them to be, none of them were for Linux and I had to do quite a bit of trial and error.
I know that a few years ago I wouldn't have been able to do it with those instructions.
So I thought I'd write down what I did so others can do it easier and faster than me.
To be able to easily understand this guide you need to know the basics about using a terminal, but other than that I'm trying to not to require the reader to know anything.
If you use another Linux distro everything should work pretty much exactly the same, but for the additional packages I had to install, but their name should be easy to guess because they are usually similar across distributions and how you install them should be explained in the documentation of your distro.
Connect your Nexus 4 to your computer using an USB cable.
First I downloaded the ADT Bundle from there developer.android.com/sdk/index.html and unpacked it into a new folder. Doesn't matter where, I'll use ~/androidSDK in those instructions. The tools which you need to root your phone are ~/androidSDK/adt-bundle-linux-x86-20130514/sdk/platform-tools/adb and ~/androidSDK/adt-bundle-linux-x86-20130514/sdk/platform-tools/fastboot
"x86" means I downloaded the 32bit version and "20130514" is the date of when the version I'm using was published, that will most likely be different for other people.
Now most likely adb and fastboot won't run yet (if you run them it will tell you something like "~/androidSDK/adt-bundle-linux-x86-20130514/sdk/platform-tools/adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory"). To fix this you need to install the packages "lib32ncurses5" and "lib32stdc++6". You can run the following command to do that:
Code:
sudo apt-get install lib32ncurses5 lib32stdc++6
(got that from there: stackoverflow.com/questions/10005907/eclipse-android-plugin-libncurses-so-5)
For adb to work you also need to activate USB debugging: Go to Settings->About phone and tap "Build Number" until it says you are developer. Then a new entry will appear in "Settings", called "{ } Developer options". Check the box next to "USB debugging", confirm with ok.
Now you need to backup everything on your Nexus 4 because it will be wiped while rooting. You can do this by running:
Code:
cd ~/androidSDK/adt-bundle-linux-x86-20130514/sdk/platform-tools
(in the future I'll assume you stayed inside that directory)
Code:
./adb backup -apk -shared -all -system
Before this command can finish you need to confirm on your Nexus 4 that it's okay to do that backup (just do what it says on it's screen).
This will put a file named backup.ab in the current directory. You can change the name and location of that file using the -f paramter, if you want.
Run
Code:
./adb reboot bootloader
to boot into the bootloader. After a moment the Nexus 4 should display something like 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"
}
(image stolen from reviews.cnet.co.uk/mobile-phones/how-to-root-your-google-nexus-4-50010361/)
Now the actual unlocking happens: Enter
Code:
sudo ./fastboot oem unlock
Maybe try without sudo first (just leave it out), but it only worked with sudo for me; without sudo it displayed "waiting for device" forever and I needed to abort with Ctrl+C.
Download SuperSU from there http://download.chainfire.eu/supersu (at the moment "CWM-SuperSU-v0.98.zip").
Put that file on your Nexus 4 any way you want, one possible way is to do:
Code:
./adb push ~/CWM-SuperSU-v0.98.zip /sdcard/
That assumes you downloaded SuperSU to your home directory. For that to work you need to activate USB debugging again (it was deactivated during unlocking).
Download the Nexus 4 "Touch Recovery" from www.clockworkmod.com/rommanager.
I guess you shouldn't need the touch version, but it's more comfortable for sure. When I downloaded it the file was named "recovery-clockwork-touch-6.0.4.7-mako.img" and that's what I'm going to use when I give you commands to run.
This "Touch Recovery" needs to be installed to the Nexus 4. To do this first boot into the bootloader again:
Code:
./adb reboot bootloader
And then flash the file using the fastboot utility:
Code:
sudo ./fastboot flash recovery recovery-clockwork-touch-6.0.3.1-mako.img
(if it needed sudo the last time it will need it again, if not, not)
Now go to the recovery mode (use volume buttons to navigate and power to confirm).
Tap "install zip from sdcard"
Tap "choose zip from sdcard"
Tap "0/"
Find the SuperSU .zip file you put on the phone earlier (tip: scrolling works as usual by swiping or if you want with the volume buttons) and tap on it.
Confirm that you really want to install it.
Boot into Android again and restore the backup you made earlier (if you made one).
Code:
./adb restore backup.ab
You need to confirm that command on the Nexus 4.
As you are now finished you can of course disconnect your Nexus 4 from your computer.
You should be finished now. Unless I remembered something wrongly when writing this because I mostly wrote this from memory, after rooting my Nexus 4. If something doesn't work as I claim then please tell me and I'll fix it (possibly eventually).
I myself followed those instructions http://forum.xda-developers.com/showthread.php?t=2018179 as far as possible and then googled what didn't work or just tried around for a bit.
Edit: As of now (18.8.14), those instructions should still work.
Related
First:
Warning! This is only for A70B/A70IT2 Honeycomb model, It won't work on Froyo model!
Here is a package that enables unofficially SDE menu in recovery and install a rooted stock firmware with busybox and SuperUser.Apk
Pre-Requisite:
- Adb must be enabled on tablet and PC driver+adb command must be working. You can test on pc with "adb shell", it should give you a '$' prompt. If you don't have this, first make it work. There are multiple links around to help if needed.
Instructions:
- Unzip files on your pc in adb.exe directory.
- Launch enable_sde.bat on your pc. It's better to do it in a cmd.exe window, you'll be able to copy-paste log here if anything goes wrong.
- Follow instructions in the cmd window. Basically, script reboots tablet multiple times, you have to press enter when tablet is completely booted each time.
- Congratulation, your device is sde enabled and has a rooted sde firmware. Please read below for more information.
Upgrades:
If you already installed a first version and enabled sde already, here is how to install new rooted firmware:
- Optional: flash updated stock firmware. I always recommend to match stock firmware, it avoids dalvik-cache rebuilds and bootloaders may have been updated in new firmwares.
- Boot rooted firmware. You should be running rooted firmware if you want upgrade script to work. To be sure of that, you should see SuperUser app in your apps menu.
- Unzip files on your pc in adb.exe directory
- Launch upgrade.bat (or upgrade.sh for linux)
- Tablet reboots at the end to rooted firmware and should be upgraded to new version.
SDE information:
1) What is SDE?
SDE (Special Developer Edition) is basically a dual boot mechanism. It allows us to dual boot Archos stock firmware and our custom ones.
2) How does it work ?
I won't give much details on how to use it, I should do a separate topic about this one someday. Until then, here is some basic information:
- At the end of this script, you are booted with sde firmware, superuser should be in your start menu and you should be root with adb or any root app.
- If you reboot or boot, press volume up while booting, it will display the dual boot menu. Select "Developer Edition", it will start the rooted build (check here point 9 to see how it looks).
- If you missed volume key or don't do anything during reboot, you will go back to unrooted stock firmware. You have to press the volume up key during boot to get the boot menu.
- Warning: booting stock firmware is harmless except that you will loose your SuperUser.apk preferences. As it's not part of stock firmware, Android clears it.
- You can boot straight to rooted firmware by deleting the stock firmware kernel in recovery. Check here, do point 4,5, and on screen 6, select "Remove Android Kernel". Make sure that you have properly working SDE firmware before doing that. If you want to re-enable back stock firmware, just flash it from recovery again.
Downloads:
3.2.80 can be downloaded here: Mirror 1 (Mediafire), Mirror 2 (Sendspace).
3.2.81 can be downloaded here: Mirror 1 (SendSpace) (bat fixed)
Sorry, Mediafire no longer let me upload without signup, if you know one good upload location without registration and allowing more than 200 MB, let me know.
*reserved*
Registered just to say thank you!
Worked like a charm, and no problems using the shell script (I run Arch Linux)
Keep up the good work!
Thanks
I mean real thanks
Sent from my ARCHOS 70it2 using xda premium
EDIT:
Beautiful man, beautiful. Works splendidly
Thanks again
LeTama
Have a beer or two on me, 84G89322WT2139701.
Thanks again for your Rom.
Hi mrew42,
Thanks a lot! Much appreciated!
Tomorrow, my 70b return at home
I testing that !
but my 70bit2 is with 3.2.81
Letama, can you may be make the same for 3.2.81?
Yes, it will come soon...
3.2.81 is up and instructions on first post updated if you upgrade.
Great
http://www.jbmm.fr/?p=27601
{
"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"
}
cajl said:
Great
Click to expand...
Click to collapse
Nice job! Thanks for the article on jbmm!
Thanks, will try it out soon.
Thanks letama, this is just what I wanted. Awsome work!
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Keep up the good work and thanks again.
ColinTaylor said:
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Click to expand...
Click to collapse
Ah! Right! Thanks for pointing it, I'll fix that and re-upload when I find time to do it.
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Click to expand...
Click to collapse
Yes, this is normal, this one is only needed when enabling sde first time. local.prop is coming from temp root and won't be there anymore.
I finally had time to try it out tonight, all seemed to be installed fine, but I don't see the Superuser in the apps list... I can boot into developers fw menu though. Did I miss something or should I just try to reinstall the SDE again by running that bat file again?
No, as ColinTaylor said, there is a typo in script, you just need to push the ext4.update at root of storage.
Just type this command in the directory you unzipped the files:
Code:
adb push android_32.ext4.update /data/media/
then boot sde.
Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!
hello, first of all thanks for your work.
I am having some problems with the upgrade file.
it says that it cannot stat 'zImage':no such file or directory
and secondly it cannot open the kernel file (no such file or directory) mkf lashimage failed.
could you please provide some help with this?
thanks!
lozano.markp said:
Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!
Click to expand...
Click to collapse
adb is a developer tool from android sdk that let you execute commands on your tablet from your PC. You have to install android sdk to get it, you need to enable it on the tablet and have a proper driver.
Easy Installer
{
"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"
}
What is Easy Installer?
Easy installer is a windows RUU imitate that helps you as user to install your Rom's with only 2 clicks. Fully automated!
For devs Easy installer helps to provide Rom's alternate to the recovery zip archive.
Click to expand...
Click to collapse
How does Easy installer work?
Thats easy. The developer create a system img file of his rom and configure Easy installer easily with one config file. The package can provide like a normal rom.
The user run a little exe-file and the RUU installs the rom fully automated! If something runs false, the RUU gives the user an error and a explanation what he can to do now.
Click to expand...
Click to collapse
What i need for Easy installer
For now, Easy Installer works only with image files, so you need your Rom as a image file. You can create a image file of your rom easily with mkyaffs.arm (find in attachements).
The config file is easy to understand. An example here (found in package too):
Code:
;The config file is neccessary for the RUU. Here you define all file namens.
[functions]
;imgfile specify, if you want to flash a image or a zip file (0=zip-file, 1=img-file). For now, only img files working, sry :(
imgfile=1
;waitbl set the time the RUU wait for the bootloader (fastboot). Some devices take a while to reboot to bootloader. Set the time here, in generally the time 10 is enough
waitbl=10
;the img-name specify the name of the image file without the file extension!
img-name=system
;zip-name is for one of the next versions, when it is possible to flash zip files. If you want, you can delete this
zip-name=HC_MIUI3.2
;boot-name specify the name of the boot.img without extension.
boot-name=boot
;set the name of the clockworkmod recovery file for your device here.
cwm-name=cwm
;rec-name is the original recovery of HTC that must be inserted for img-files. Put the name here without extension
rec-name=recovery
[labels]
;specify the shown rom-name in the RUU
rom-name=.sense
;the device name is the full name of the device the rom is for
device-name=Wildfire S
;some devices has more versions (marvel, marvelc, marvelct e.g.). Specify for what device your rom is.
device-code=marvel
The picture in the RUU is namend "PHONE.bmp" in package, you can replace with your own.
Click to expand...
Click to collapse
How to create the system.img?
Well, thats is easy
1. Install your Rom you want to use in Easy Installer at your phone via the Recovery (don't start the Rom!!!)
2. Go to recovery, connect your phone via USB-Cable to computer
3. Download the mkfs.arm.zip (see attachements)
4. Create a new directory in your SD-Card (example: "build")
5. Copy the extracted file "mkfs" of the downloaded archive into the folder "build"
6. Insert the SD-Card into the phone
7. In recovery go to: "mounts&storage->mound /sdcard" or run following adb-command: adb mound /sdcard
8. run the following commands in adb one after one:
adb shell
cd /sdcard/build
./mkfs /system /sdcard/build/system.img
9. Wait for the "Build OK."-message
10. Exit the adb shell via exit command and turn off the phone
11. Take the SD-Card of the phone and insert it into your PC
12. in the SD-Card's folder /build you will find a "system.img". Use this file for the easy installer
Click to expand...
Click to collapse
Changelog
v0.0.1
- first version, basic install function
Click to expand...
Click to collapse
Download
See the attachements (WSWizard.zip)
Click to expand...
Click to collapse
Will this work for all devices?
Any chances of bricking? Because many of users of Micromax A70 bricked their phone by a chinese flashing tool.
Burned from my laser torch using pencil cells
Sorry, i see now, that i posted this in false section. In genarally it works only for HTC devices which are unlocked or S-OFF, not for others!
How can I use the mkfs.arm?
it works only on ARM-based devices, like the HTC phones.
You must copy the file onto your sd-card e.g.:
adb push mkfs.arm /sdcard/build
After this you install your Rom on the device or copy the /system-files to the sd-card. Now you run following command:
adb shell
cd /sdcard/build
./mkfs.arm /system /sdcard/system.img
ODER
./mkfs.arm /sdcard/build/system /sdcard/system.img
Then the file will build a system.img and copy it onto the sdcard for next use
Would like to know if this would work to ONelll123
Wipe everything
Flash Rom
Make Nandroid
Use Nandroid as ROM's Images
It seems much easier to me than having to go to shell and all Not meant to be an insult, just a recommendation/question
Hmm, it ia qn idea, but idk in what filesystem the backups are saved. If it is yaffs2 it can be that this works.
But you must do shell commands too. Its for secruity reasons and that this method used works.
Sent from my HTC Wildfire S A510e using XDA
ONeill123 said:
it works only on ARM-based devices, like the HTC phones.
You must copy the file onto your sd-card e.g.:
adb push mkfs.arm /sdcard/build
After this you install your Rom on the device or copy the /system-files to the sd-card. Now you run following command:
adb shell
cd /sdcard/build
./mkfs.arm /system /sdcard/system.img
ODER
./mkfs.arm /sdcard/build/system /sdcard/system.img
Then the file will build a system.img and copy it onto the sdcard for next use
Click to expand...
Click to collapse
Thanks I will be try this when htc one x gets adb working recovery
OK, I just did another rescue script, it's using the files from the final release but it will install them one at a time using your computer instead of trying to install the rom.
THIS GUIDE IS FOR WINDOWS ONLY!
If someone else wants to convert it for Linux/OSX feel free but please make a new thread with a similar format to the title as this one but with [Linux/OSX]
Bear in mind this script will also install the compatible TWRP version 3.0.2.0 which will work with the final OOS3 and also with the new codebase in CM13 unless you sideload the complete rom in which case that will install the default OnePlus recovery. You can always install TWRP using the files within after this anyway
Anyone who wants to give it a go can download it at the link below, remember IT'S NOT A FLASHABLE ZIP, it's the files packaged into a zip.
Download here from Android FileHost : https://www.androidfilehost.com/?fid=24580943222146240
Carry out the following instructions as I have entered them.
Unpack the zip file into a folder, possibly on your desktop so you can see all the files easily.
Reboot your phone into fastboot mode by holding down the VOLUME UP button while holding the POWER button until you see fastboot mode show, obviously make sure you have connected the phone to your computer via usb cable.
If you have not unlocked your phone then immediately go watch the video below to find out how to do so then come back and continue the instructions from step 4.
https://www.youtube.com/watch?v=KZaajUEybNM
Open an elevated prompt window in the folder you unpacked the zip into (elevated means it has administrator privileges), to do this, right click in the folder (not on a file) while holding the SHIFT key, then choose "Open command window here", see below:
{
"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 may be prompted to allow admin privileges, say yes.
In the command window you opened type the following:
fastboot devices
You should then see something similar to the screenshot below:
If you don't see a number followed by fastboot then you need to install or re-install your drivers. (I've uploaded the latest version to Android FileHost here : Download, remember to restart the computer before proceeding)
If you do see something similar to the above, then type the following into the command window:
fixoos
Then press enter, now adb will flash the different new versions of the partitions needed to either install the rom or reboot into the new version of TWRP.
It should look like this (I've shrunk the text to try to fit it all in) :
The last 2 steps in the script are going to flash the new compatible TWRP as your recovery partition and then it will also reboot into that version of TWRP.
All of this presumes that you were able to copy whichever rom you want to install onto your phone.
If you did not copy the rom onto your phone then download it the link below :
https://www.androidfilehost.com/?fid=24580917854994435
Copy the file into the same folder as the rest of the files and then run the following in the command window :
adb sideload OnePlus2Oxygen_14_OTA_019_all_1606041303.zip
(If you start typing the filename and press TAB it should autocomplete the name as long as the zip file is in the same folder as you opened the command window in)
Now press enter and ADB should install the full release rom itself, bear in mind, this will NOT include the new TWRP as TWRP is not a part of the default rom.
Please post any problems you have below, however, as long as you follow the instructions properly you should be ok.
djsubterrain said:
OK, I just did another rescue script, it's using the files from the final release but it will install them one at a time using your computer instead of trying to install the rom.
THIS GUIDE IS FOR WINDOWS ONLY!
If someone else wants to convert it for Linux/OSX feel free but please make a new thread with a similar format to the title as this one but with [Linux/OSX]
Bear in mind this script will also install the compatible TWRP version 3.0.2.0 which will work with the final OOS3 and also with the new codebase in CM13 unless you sideload the complete rom in which case that will install the default OnePlus recovery. You can always install TWRP using the files within after this anyway
Anyone who wants to give it a go can download it at the link below, remember IT'S NOT A FLASHABLE ZIP, it's the files packaged into a zip.
Download here from Android FileHost : https://www.androidfilehost.com/?fid=24580943222146240
Carry out the following instructions as I have entered them.
Unpack the zip file into a folder, possibly on your desktop so you can see all the files easily.
Reboot your phone into fastboot mode by holding down the VOLUME UP button while holding the POWER button until you see fastboot mode show, obviously make sure you have connected the phone to your computer via usb cable.
If you have not unlocked your phone then immediately go watch the video below to find out how to do so then come back and continue the instructions from step 4.
https://www.youtube.com/watch?v=KZaajUEybNM
Open an elevated prompt window in the folder you unpacked the zip into (elevated means it has administrator privileges), to do this, right click in the folder (not on a file) while holding the SHIFT key, then choose "Open command window here", see below:
You may be prompted to allow admin privileges, say yes.
In the command window you opened type the following:
fastboot devices
You should then see something similar to the screenshot below:
If you don't see a number followed by fastboot then you need to install or re-install your drivers. (I've uploaded the latest version to Android FileHost here : Download, remember to restart the computer before proceeding)
If you do see something similar to the above, then type the following into the command window:
fixoos
Then press enter, now adb will flash the different new versions of the partitions needed to either install the rom or reboot into the new version of TWRP.
It should look like this (I've shrunk the text to try to fit it all in) :
The last 2 steps in the script are going to flash the new compatible TWRP as your recovery partition and then it will also reboot into that version of TWRP.
All of this presumes that you were able to copy whichever rom you want to install onto your phone.
If you did not copy the rom onto your phone then download it the link below :
https://www.androidfilehost.com/?fid=24580917854994435
Copy the file into the same folder as the rest of the files and then run the following in the command window :
adb sideload OnePlus2Oxygen_14_OTA_019_all_1606041303.zip
(If you start typing the filename and press TAB it should autocomplete the name as long as the zip file is in the same folder as you opened the command window in)
Now press enter and ADB should install the full release rom itself, bear in mind, this will NOT include the new TWRP as TWRP is not a part of the default rom.
Please post any problems you have below, however, as long as you follow the instructions properly you should be ok.
Click to expand...
Click to collapse
Linux version -> http://forum.xda-developers.com/oneplus-2/help/linux-fixing-script-boot-looping-oos-3-t3395736
Note to staff: I'm new to XDA, so I'm sorry if this guide is posted in the wrong place or if it's inadequate. Please PM me if there are problems with it.
Note to users: I am NOT responsible if the restore process damages your phone. You are doing this at your own risk. Be sure to follow the steps carefully.
In this guide, I will share the best method of backing up your phone to your PC.
Recently I flashed a stock firmware on my SM-J730F and debloated it. Somehow I managed to soft-brick the device after a few weeks and I had to re-flash the firmware, and debloat it all over again. I found out a good method of backing up my entire phone so that I don't have to do that again. I will share that method with you guys.
This works with any phone, not just the J7.
Requirements:
1. Any phone
2. PC
3. An USB cable
4. ADB - Download Here
5. Root Access - Guide on how to root SM-J730F here || Other Phones - If your device is rooted, continue. If not, please leave.
6. FlashFire App - Install Here
Instructions:
1. Have your USB cable near you;
2. Download FlashFire from the link above;
3. Enable USB Debugging from Settings -> Developer Options;
4. Download the ADB from the link above, and extract everything inside the archive to C:\ADB (create a new folder);
5. Connect your USB cable from your phone to your PC - if you get an access request on your phone from your PC's fingerprint, accept it;
6. Open a Command Prompt and type: cd C:\ADB
7. Type adb devices in the command prompt to confirm that it detects your phone; you should get something like 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"
}
8. Now open FlashFire on your phone and grant it root access;
9. Tap on the plus sign and tap on Backup:
10. Select Full - All Partitions:
11. On this screen, DO NOT select the partitions that have "(protected bootloader partition)" or "(protected partition)" under them; they might cause the restore process to be unstable:
(TIP: There are more partitions if you scroll down on the list of partitions. Just be careful not to select the protected one. Everything else, select.)
12. After that tap on the V button at the top right of the window, and now just scroll to the bottom of the page and tap on FLASH:
13. Your phone is going to reboot now. DO NOT intrerrupt this process, and DO NOT disconnect the USB cable.
14. Once your phone has rebooted, a list of files will start to load, and you will see FlashFire at the top of the screen. On the bottom, the last line should be this:
Start: adb backup go -f filename.zip
This means that FlashFire is waiting for your input from the Command Prompt on your PC.
15. If you see that line, then go on your PC, go into the Command Prompt and type the following command to start the backup process:
adb backup go -f backup.zip
16. Press Enter and the backup process will start on your phone. Wait until it is complete. Your phone will reboot when it's done.
And that's it!
You should have a Backup.zip file in your C:/ADB folder. The size of the file depends on how much data you have on your phone.
Congrats; You have created a full backup of your phone.
Below is a tutorial on how to restore the backup that you have just created.
1. Open ADB on your PC and verify if your device is detected, as I've explained above;
2. Open FlashFire, tap on the plus sign and tap on Restore:
3. On the window that opened select Restore from ADB:
4. Select all the partitions (except the protected partitions) (there are more if you scroll down), and then tap on the V sign at the top right:
5. Tap on the FLASH button and wait for your phone to reboot:
6. Once it's rebooted to that screen with two lines, you should see something like this:
7. Now type the following command into the Command Prompt on your PC:
adb push backup.zip /restore
8. Press Enter and wait for the restore process to finish. Your phone will reboot and hopefully everything is how it should have been when you backed up the phone.
And that's it! You're done restoring the backup.
I hope this guide has helped you; if it did hit the "Thanks!" button at the bottom right of this post, more guides about rooting the J7 and unbricking it available now..
And again, this is my first legit post on this site, so I'm sorry if something is wrong. Please leave constructive criticism, and don't be immature if you have a problem. Thanks
I tried backing my phone up and after step #13, nothing happened? Help please? It just rebooted.
hello i want to know that can i backup my phone (only rom and its update) without root if yes pls tell me...
Hello, first of all I apologize for my English if you don't understand me somewhere, I'm learning English. Greetings from Peru.
Files and programs you need to downloadTHIS PROCESS WORKS WITH ALMOST ALL DEVICES, ONLY IF THEY HAVE THE BOOTLOADER CORRECTLY UNLOCKED WITHOUT THE NEED OF A TWRP.
In the computer1- Lenovo Rescue and Smart Assistant, will help you in 2 things: In case your device is frozen or in a loop, there you can recover it and right there you can find and download the ROM of your device for free.
As you can see in this image my device is already selected and the ROM is already downloaded (just follow the steps and your device will be fine again)
{
"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"
}
Here you will find the ROM
as you can see, location, folder and files of the ROM (it is necessary that you know where it is since you will need some files later)
2-You need to have ADB/FASTBOOT installed to be able to install the ROOT (remember that this is the safe way, there is no risk of your device freezing or in a loop, but everything is possible).
Link : https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
on device1- First of all, you have to have the bootloader unlocked, here I leave the guide since it is somewhat long to read
Link : https://www.mobilewithdrivers.com/download/unlock-bootloader/lenovo-tab-m10-fhd-plus-tb-x606f
2- After unlocking the bootloader, you have to have Magisk.apk installed on your device
Link : https://github.com/topjohnwu/Magisk/releases
3- After installing Magisk, on the main screen you have to see if Ramdisk is "yes" or "no".
It says "si" because my native language is Spanish.
4- Go back to the computer and in the ROM folder you have to find the file "boot.img" and copy it to your device
5- within Magisk where it says "install", they give it to install and something similar to this will come out:
6- They only give the following next "siguiente " and select the option of Select file "seleccionar y parchar un archivo" (I repeat again ignore if it comes out in Spanish, you in English)
7- from there the explorer will open and they will look for where they copied the "boot.img" and select it.
Once the selector is given to start or let's start "comencemos"
the process has to be something similar to the image that I will post below, you can several certain lines but at the end it has to say "done!" without any error.
8- Now to finish the process on your device, copy the file that appears in your magisk "the patched file". Copy and paste it into the ADB/FASTBOOT folder
we return to the computer
1- First of all, you have to enable "usb debugging" on your device
Link : https://www.embarcadero.com/starthe...bling_usb_debugging_on_an_android_device.html
2- Now go to your ADB/FASTBOOT folder and in a blank part open "powershell",
Now go to your ADB/FASTBOOT folder and in a blank part open "powershell" .
Holding SHIFT and right clicking open POWERSHELL
now they write "cmd" without quotes so that inside PowerShell you can use it as cmd
3- Here I will explain it in a long but correct way without errors, do not turn off the computer and leave it on since you will write an ADB command to order the device to enter Fastboot mode.
By typing "adb devices" you will find out if the drivers are correctly installed and your computer, cmd and adb/fastboot should recognize it.
now type "adb reboot-bootloader" , this will command your device to reboot into "bootloader" mode
Now this part is important that you pay attention as some people make mistakes.
Once your device has rebooted and you get to the "fastboot mode" screen, you will type the following in powershell :
fastboot devices
If the following appears, it is because your computer detects your device in fastboot mode.
Now comes almost the end of this guide, to install root do the following.
To root your device they usually tell you to type the following "fastboot flash boot boot.img", but sometimes there are errors.
what you will do is the following :
once you have written the following
you are going to drag the "magisk patches" file to the poweshell
and you will have to leave the path where the saved file is (this is a safe way so that you do not get errors)
now you just hit "enter" and it will be installed on your device
Now to finish, restart the device, install "root checker" and you will realize that you have it activated.
attached image of my device "Tab M10 FHD 2nd TB-x606x" with the latest ROM installed, having ROOT, MAGISK and modules installed
THIS PROCESS WORKS WITH ALMOST ALL DEVICES, ONLY IF THEY HAVE THE BOOTLOADER CORRECTLY UNLOCKED WITHOUT THE NEED OF A TWRP.
If the guide helped you, please comment, if it didn't work for you, please comment as I will try to help you solve the problem.
Currently I will not be contributing more to the community since I do not have my own computer, the computer I use will only be there for a few days, after that they will take it away.
when I have a new computer, I will be sharing RecoveryTWRP for some devices modified by me or some other help that I am able to carry out and finish as a project.
I thank XDA for creating this space to help, guide and for everyone to learn in the process.
I send you greetings from Peru.
Nice, thank you very much, sir.