Database Users

[TUTO+VIDEO] Unlock Bootloader-Flash Recovery-Root-Restore Back the N7 FLO- KK 4.4.4

This tutorial All In One is for all owners of the NEW NEXUS 7 FLO (2013 Edition). I've tried to be clear, helpful and simple
....-ox=O=xo-....​POST #1 => [TUTO + VIDEO] AIO Unlock Bootloader, Flash Recovery (TWRP) and Root your Nexus 7 FLO​
....-ox=O=xo-....​POST #2 =>[TUTORIAL]Download Factory Images Nexus 7 FLO - Restore back STOCK with latest KK 4.4.4
....-ox=O=xo-....​POST #3 => [HOW TO] FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND
....-ox=O=xo-....
Warning!
This guide and its guidelines are meant only and only for the new Nexus 7 "FLO" (2013).
Do not attempt to try this on the older Nexus 7 or any other device.
Applying this to any other variant might brick the device.
Read and understand the instructions carefully before proceeding any further.​
Click to expand...
Click to collapse
....-ox=O=xo-....​
Pre-requisites:
Click to expand...
Click to collapse
THIS GUIDE IS ONLY FOR WINDOWS
1) This point is really important. You’re going to lose all your datas on the device including the internal storage. So back everything up.
2) Download and Install 7zip or any other archive manager as WinRAR etc...
3) Download and install Android SDK
OR
3Bis)Download The ADB and Fastboot Tools in the same Tool ==> platform-tools.zip - md5: 15e771613370afe3c70e0be1454d2ef1 - size: 346.8KB
4) Put these 3 files in where your fastboot folder is installed; ex => => disk C: root
Unzipped this file on the folder "platform-tools" and you will find 11 files:
- aapt
- adb
- AdbWinApi.dll
- AdbWinUsbApi.dll
- aidl
- dexdump
- llvm-rs-cc
- fastboot
- dx
- NOTICE
- source.properties
5) Enable USB Debugging Mode on the tablet to connect it with the computer and use Android SDK with it.
{ Press Menu =>> Settings =>> Applications. From there navigate and click on Development option then check the USB Debugging Mode.}
If you don’t see the Development Options, you'll need to open the Settings app and scroll down to the bottom. Once you get there, tap “About Phone”. Scroll to the bottom again, until you see the Build Number entry.
Now tap Build Number a total of seven times. You'll see friendly developer messages starting with the fourth tap. After the seventh, you'll see a message congratulating you for unlocking Developer Options. “Now you are a developer".
6) At least 70% battery power to avoid uncertain shutdowns during the process.
7) The tutorial is compatible only with the Nexus 7 wifi (2013) FLO.
....-ox=O=xo-....
Process to unlock bootloader of your Nexus 7 FLO
Click to expand...
Click to collapse
-1: Connect the Nexus 7 to the computer using USB cable.
-2: Open a Command Prompt window and type the following command to reboot the device into booltoader mode:
Code:
adb reboot bootloader
-3: Type the following command to lauch the unlock process:
Code:
fastboot oem unlock
-4: You will now be prompted with a dialogue to confirm the process, go through it.
Use the Volume buttons to highlight Yes and select it using the Power button
-5: The tablet will go back to the bootloader screen. Press Power button to select Start to reboot into the unlock device
Before to install the TWRP recovery and applying the root, you need to download the latest version of the TWRP recovery and the latest version of SUPER-SU that you need to push to the root of your sd card - For downloading these files follow the links below
Click to expand...
Click to collapse
....-ox=O=xo-....
Process to install TWRP recovery on your Nexus 7 FLO
Click to expand...
Click to collapse
-1: Download the latest TWRP recovery image file
Download link- TWRP
-2: Open the folder where the recovery image file has been downloaded and rename your recovery "recovery-twrp" simply. Re-open your previous Command Prompt window.
-3: Type the following command to flash the recovery image file
Code:
fastboot flash recovery recovery-twrp.img
-4: The recovery will be flashed and the progress could be observed in the CMD window itself.
Note: To boot the Nexus tablet into Recovery, press the Volume keys (up/down) until Recovery Mode is displayed. Use the Power button to select it and the device will reboot into the TWRP recovery Mode.
....-ox=O=xo-....
Process to root your Nexus 7 FLO - Update
Click to expand...
Click to collapse
-1: Download the SuperSU root package for Nexus 7
or you can use Download link: CF-Auto-Root-flo-razor-nexus7.zip
Explanations for understand why you must use CF-Auto Root => Go to read here the Central Post
-2: Download the ZIP file (see the link above) and Extract the ZIP file
-3: Connect the tablet to your PC using USB cable.
-4:Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolDown+Power to turn it on.
-5:Connect your device to your computer using USB
-6: Open a new CMD window and type the following command:
For Windows
Code:
root-windows.bat
For Linux
Code:
chmod +x root-linux.sh
root-linux.sh
For Mac OS X
Code:
chmod +x root-mac.sh
root-mac.sh
Follow the on-screen instructions - watch both the computer and the device !
Note that if your device had not been unlocked before, this procedure will wipe all your datas !
And if you have some problem with the process, go to see HERE
Now your Nexus 7 FLO running on Android 4.4.4. KitKat should have be rooted with latest TWRP recovery installed and bootloader unlocked. :victory: :good:
If you need more help, following my OP and this video from @clozecall
....-ox=O=xo-....
{
"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"
}
ISSUES
Click to expand...
Click to collapse
If you have some problem after to flash the recovery, and you stay stuck on during 5mn + You need to wipe data and factory reset on settings and normally all should be work perfectly after
Click to expand...
Click to collapse
....-ox=O=xo-....
USEFULL FILES:
Click to expand...
Click to collapse
Recovery_Stock_KK-4.4.4.img - Download link - Md5: 0ce33e5478a93f335f9be94c42057557 - size: 7.4MB ==> NEW
Recovery Stock -SS15QR.img - Download link
Recovery Stock -JSS15Q.img - Download link
Recovery_stock_JSS15J.img - Download link
Recovery_stock_ JRW66V - Download link
Google USB Drivers - md5: 1389bb2de0c9cacce27c76f1c71592ef - size: 8 MB
OEM USB Drivers
USB DRIVERS r_06 for Windows 7 & 8​Thanks to @clozecall for his video
and all members for their help
And don't forget to RATE FOR THIS THREAD -
if it's helped you
"Thanks in advance

[TUTORIAL]Download Factory Images Nexus 7 FLO - Restore back STOCK
[TUTORIAL]Download Factory Images Nexus 7 FLO - Restore back STOCK - With latest version KitKat 4.4.4​
Find your Factory image for your N7 FLO - KitKat KTU84P - Download Link - - is very useful if you need to restore back your device to Stock after any modification you’ve made. If you have rooted your N7 Flo, unlocked its bootloader, installed custom recovery and roms and finally you want decided to getting back to official firmware and then to get or accept future OTA updates again. It’s the best way to restore back your device to Stock.
Coming back to stock is also useful if you have some bugs (for fixing it), Bootloop, stuck in boot screen logo and freeeeezzziiiinnnngggg, etc....But before to going back to stock, you need to read completly the tutorial and need to know
Your bootloader will be “LOCKED or UNLOCKED” when you want.​
1 - Where I can can find the right Factory Image for my Nexus 7 Flo and which files I need for proceed ?
But first download and install the necessary files prior to execute this properly. Download the full factory image corresponding to your exact mode which includes the full system, bootloader, recovery, kernel (boot.img).
Unpack the TGZ Version (tar/gz) or Zip Version Archive into its own directory. I use 7-Zip, but you can use any tool that reads gz and tar.
Factory Images "razor" for Nexus 7 [2013] (Wi-Fi) - 4.4.4 (KTU84P) - Download link
If you have already installed those files, just check theirs.
Java Runtime Environment.
Android SDK | Android Developers.
Platform tools
Fastboot files
2 - PREREQUISITES
First make sure that your battery is fully charge 100% and BACKUP ALL YOUR PERSONNEL DATA
[1] - Make sure you have USB debugging turned on. For security purposes, you can turn it off after we're done
[2] - Plug-in USB cable and If you are booted into Android, open a command prompt to your ADB and Fastboot directory,
[3] - In case you are not unlock, you need to unlock your bootloader, enter the following commands:
Code:
fastboot oem unlock
If your tablet hasn't already rebooted automatically, type:
Code:
fastboot reboot
NOW WE ARE READY FOR PROCEED TO RETURN STOCK
3 - RUNNING FACTORY IMAGE
If you want to keep your data intact, don't skip this step, (if you do your data will be wiped )
With your text editor (for me it's Notepad ++,
[1] - Edit (be careful not to run it by accident instead of editing)
[2] - flash-all.bat (if you're on Windows)
[2a] - flash-all.sh (Mac, Linux)
[2b] - and remove "-w" from the fastboot update command
For example, if the line reads fastboot -w update image-razor-ktu84p.zip, it should now read: fastboot update image-razor-ktu84p.zip. The -w option instructs fastboot to wipe data.
Click to expand...
Click to collapse
[3] - Reboot into the bootloader and run the appropriate flash-all script:
Code:
flash-all.bat
​Done, your Nexus 7 Flo is now coming back and running Stock Android KK 4.4.4
In Case you want to come back completely to Stock, for warranty or security purpouses, you need to re-lock your bootloader now.
Enter the following commands
Code:
fastboot oem lock
If your tablet hasn't already rebooted automatically, type:
Code:
fastboot reboot
Done!
And don't forget to RATE FOR THIS THREAD -
if it's helped you and eventually click to "Newsworthy Thread? "Thanks in advance

Reserved

[HOW TO] FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND and FILES
FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND and FILES​
If you have got a problem with your adb or fastboot or recovery....it's very simply and faster
use this:
Download this file "fastboot.zip" or this tool : platform-tools.zip - md5: 15e771613370afe3c70e0be1454d2ef1 - size: 346.8KB
Install this file somewhere in one folder which is named "fastboot" on your PC
=> disk C: root
Unzipped this file on the folder "fastboot" and you will find 3 files:
- adb.exe
- AdbWinApi.dll
- fastboot.exe
OR
Unzipped this file on the folder "platform-tools" and you will find 11 files:
- aapt
- adb
- AdbWinApi.dll
- AdbWinUsbApi.dll
- aidl
- dexdump
- llvm-rs-cc
- fastboot
- dx
- NOTICE
- source.properties
and when you need to push something by the bootloader, you can use it.
Don't forget to push on this folder the file that you need. For exemple: boot.img or a recovery.img, etc...
CD to where your fastboot or platform tools were installed
The line command is :
Code:
[B]C:\Users\R2D2>cd c:\platform-tools[/B]
Code:
[B]C:\platform-tools>[/B]
OR
Code:
[B]C:\Users\R2D2>cd c:\fastboot[/B]
Code:
[B]C:\fastboot>[/B]
Enter
Code:
[B]C:\fastboot>fastboot flash recovery recovery.img[/B]
Enter
If you want to flash the "recovery.img" file
******************************************************************
******************************************************************
If you want to know all lines of command
Code:
c:\fastboot>fastboot
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048

From this part of your procedure:
"-5: The tablet will go back to the bootloader screen. Press Power button to select Start to reboot into the unlock device
Note: Those who wish to install TWRP and root the device further, do not reboot the device. Leave the device at the same screen."
I still say you have to start and boot before you install TWRP. If you don't you get 0 MB Internal Storage on screen and twrp needs password. Can you verify this?
I had to restore my system.img and start over.
Maybe your version of TWRP does not require a reboot (Start) after OEM unlock?

I've always used clockwork on my phones... can you use clockwork in place of twrp on the nexus 7 flo?

Bricked my N7
Not new to flashing, but I made a huuuuuuuuge mistake today. I accidently flashed the wrong recovery image for the 2012 N7 (yeah, I'm an idiot). I can boot into fastboot and recovery mode, but it fails to mount the sd card so I can't do **** anymore. Can't even get it back to stock t this point Any suggestions? I'm on a mac, but have access to PC. Have tried both CWM and TWRP. TWRP just gives me the password screen and 0mb storage. Can't figure out how to get around it or get my storage mounted. Help!

Stuck in boot screen
"I still say you have to start and boot before you install TWRP. If you don't you get 0 MB Internal Storage on screen and twrp needs password. Can you verify this?
I had to restore my system.img and start over."
Androidfr33k, can you specify how to restore system.img? I also do the following steps without rebooting, now I'm stuck in the boot screen.
Thanks in advanced!

Gareee said:
I've always used clockwork on my phones... can you use clockwork in place of twrp on the nexus 7 flo?
Click to expand...
Click to collapse
For the moment, TWRP recovery is the best way for most of my devices.
I've used CWM during a long time with my old devices (Htc Hero - Desire Z) - for my Desire S, I've used 4EXT recovery and now for all devices, it's TWRP
I'm waiting a CWM recovery for see.
But it's just my advice
Wwdcc said:
"I still say you have to start and boot before you install TWRP. If you don't you get 0 MB Internal Storage on screen and twrp needs password. Can you verify this?
I had to restore my system.img and start over."
Androidfr33k, can you specify how to restore system.img? I also do the following steps without rebooting, now I'm stuck in the boot screen.
Thanks in advanced!
Click to expand...
Click to collapse
I've updated the guide, so I advise you to reboot after unlock your Nexus 7, in order to validate the release.

philos64 said:
For the moment, TWRP recovery is the best way for most of my devices.
I've used CWM during a long time with my old devices (Htc Hero - Desire Z) - for my Desire S, I've used 4EXT recovery and now for all devices, it's TWRP
I'm waiting a CWM recovery for see.
But it's just my advice
I've updated the guide, so I advise you to reboot after unlock your Nexus 7, in order to validate the release.
Click to expand...
Click to collapse
Thanks philos64. My problem now is that I couldn't even boot into the OS, I can get into Bootloader mode or Recovery mode, but I couldn't factory reset (says "failed") or boot pass the Nexus screen. (stuck there for more than 15 minutes).
I'm sort of a noob, any help will be appreciated.

Wwdcc said:
Thanks philos64. My problem now is that I couldn't even boot into the OS, I can get into Bootloader mode or Recovery mode, but I couldn't factory reset (says "failed") or boot pass the Nexus screen. (stuck there for more than 15 minutes).
I'm sort of a noob, any help will be appreciated.
Click to expand...
Click to collapse
Ok, if you want you can try this process which works => For Those Who Semi-Bricked Their Nexus 7 0MB Interal Storage

Wwdcc said:
Thanks philos64. My problem now is that I couldn't even boot into the OS, I can get into Bootloader mode or Recovery mode, but I couldn't factory reset (says "failed") or boot pass the Nexus screen. (stuck there for more than 15 minutes).
I'm sort of a noob, any help will be appreciated.
Click to expand...
Click to collapse
this just happened to me. I fixed it by:
1. go into recovery and FORMAT DATA in the wipe menu
2. then FACTORY RESET
3. restart to os
i didnt need to download the system.img like the above link

decksy said:
this just happened to me. I fixed it by:
1. go into recovery and FORMAT DATA in the wipe menu
2. then FACTORY RESET
3. restart to os
i didnt need to download the system.img like the above link
Click to expand...
Click to collapse
Same here, and thanks for the tip!

decksy said:
this just happened to me. I fixed it by:
1. go into recovery and FORMAT DATA in the wipe menu
2. then FACTORY RESET
3. restart to os
i didnt need to download the system.img like the above link
Click to expand...
Click to collapse
Ok sounds good
Thanks :good:
I will insert in my OP asap

decksy said:
this just happened to me. I fixed it by:
1. go into recovery and FORMAT DATA in the wipe menu
2. then FACTORY RESET
3. restart to os
i didnt need to download the system.img like the above link
Click to expand...
Click to collapse
It worked! Thanks so much!

I unlocked and rooted my nexus 4 with this method. I already have SDK and fastboot on my Mac. I can go ahead with the N7, right? I don't need a different fastboot version? I'll make sure my SDK is up to date.
Sent from my Nexus 7

eep2378 said:
I unlocked and rooted my nexus 4 with this method. I already have SDK and fastboot on my Mac. I can go ahead with the N7, right? I don't need a different fastboot version? I'll make sure my SDK is up to date.
Sent from my Nexus 7
Click to expand...
Click to collapse
Yep, you should be all set

If "adb reboot bootloader" works when unlocking the bootloader but "fastboot flash recovery recovery-twrp.img" just sits there in Windows with "waiting for device" try using "adb reboot bootloader" again followed by "fastboot flash recovery recovery-twrp.img" to get the recovery image flashed. I don't take credit for it because it was said somewhere in this forum while trying to figure out the problem. My main rig has this problem but my HTPC does not. Same issue I had with my N7/2012.
Thank you OP!! I'm now running cleanrom 1.1 on my N7/2013. Let the ROM's rain!!!!

Video Tutorial
Hey guys, I've made a pretty simple video tutorial on how to Unlock the Bootloader and Root the new Nexus 7.
Here it is:
I know I don't have a well known name on the forums at all, but I thought it would at least be nice to post this. :good:

This guide worked well for me. I was able to unlock the bootloader, and it appeared that I was able to install the TWRP recovery image. However, when it went to reboot, the Nexus 'X' logo is looping. What's the best way to fix this? I can't access the device through the cmd prompt either.
EDIT: Nevermind, was able to get into the TWRP recovery image (I was panicking and didn't press the right buttons).
Note: I let TWRP install SuperSu for me, instead of downloading it and moving it on internal storage myself. Don't know that had anything to do with my issues but just wanted to share a heads-up.

Adb fastboot shield recovery image flashing instructions (RETURN TO STOCK)

This is Nvidia's own instruictions which I just followed works great! For new members please be aware that you may have to edit a command given in the instructions below which I will point out (depends on what OTA you have downloaded) for example
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb Highlighted in red is the name you may have to change within the extracted ota, Just look in the extracted file and locate the .dtb now just copy and paste the name of your .dtb and change the fastboot command --> example--> fastboot flash dtb tegra144-tn8-p1761-1270-a04-xda-battery.dtb
Please Read Carefully!
Follow here to get OTA
http://forum.xda-developers.com/shield-tablet/general/shield-tablet-otas-t2847116
What you must have
You need a unlocked boot loader instructions further below.
Also in cmw recovery, please wipe all partions! and reboot in to fastboot mode whilst still in recovery!
SHIELD RECOVERY IMAGE FLASHING INSTRUCTIONS
To follow the instructions in this guide, you will need adb and fastboot.
These tools are provided as part of the Android SDK:
http://developer.android.com/sdk/index.html
or you can just download this little .exe Minimal ADB and Fastboot this is what I used.please extract your recovery.zip into where you have installed Minimal ADB and Fastboot example c:\program files x86\Minimal ADB and fastboot.
https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing
Before flashing this recovery image to your SHIELD, connect your SHIELD
via USB to the PC where you downloaded this recovery image example same as above c:\program files x86\Minimal ADB and fastboot.
Next, put your SHIELD into fastboot mode using one of the following methods:
SW method 1:
- Boot to android home screen
- Connect the device to linux/windows system
- Open terminal (on linux); command prompt (on windows).
- Type "adb reboot bootloader" in terminal/command prompt
HW method 2 :
- Turn off the device
- Press and hold "Back"+"Home"+"SHIELD" buttons till device boots
To flash this recovery image to your SHIELD, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader (see
below):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb <---------------------------------------------------------------------
Now restart your device
now wait a min or two and you have just returned to stock!
Unlocking the Bootloader
Your SHIELD may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- Press the Home button on the device to highlight "Unlock".
- Press the Shield button to confirm the unlock. Your device's bootloader is now unlocked.

Also worth noting that on Linux, you can install the "android-tools" package that gives you ADB and Fastboot anywhere.
For example, on fedora 20, run:
$ sudo yum install android-tools
Make sure you run fastboot with su- privileges (not doing this caused me no end of frustration before finding out why my device wasn't detected).

MRobbo80 said:
This is Nvidia's own instruictions which I just followed works great! For new members please be aware that you may have to edit a command given in the instructions below which I will point out (depends on what OTA you have downloaded).
Unlocking the Bootloader
Your SHIELD may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- Press the Home button on the device to highlight "Unlock".
- Press the Shield button to confirm the unlock. Your device's bootloader is now unlocked.
Click to expand...
Click to collapse
Umm having a little trouble unlocking. Am I to understand that you unlock with the device turned on ? because otherwise there isn't a home button...and where is the shield button ? I only have power and volume
buttons. This looks like the unlock method for the Shield not the Shield Tablet.
Sent from my Shield Tab

Wulfpk said:
Umm having a little trouble unlocking. Am I to understand that you unlock with the device turned on ? because otherwise there isn't a home button...and where is the shield button ? I only have power and volume
buttons. This looks like the unlock method for the Shield not the Shield Tablet.
Sent from my Shield Tab
Click to expand...
Click to collapse
Your device should first be turned on. Then connect to PC and open a command prompt in your Android tools folder (where the ADB file resides) and type, "ADB reboot bootloader" (without the quotation marks).

Can I flash a ROW image in a US device?

ROOT Lg K10 MTK Chipset (95% working method)

This method is only for devices with MTK chipset. CONFIRMED WORKING ON K430T, K430DSY and K430dsE
It is based on the gottlasz method published in: http://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807"
Required files:
- Carliv Image Kitchen (search in google)
- SuperSU 2.65 available in: http://downloadmirror.co/L2/BETA-SuperSU-v2.65.zip
- TWRP ported by berkantkz at: http://forum.xda-developers.com/lg-k10/development/teamwinrecoveryproject-3-0-0-0-lg-k10-t3404434
- Time and patience (a lot of patience)
Steps:
1. Enable developer options on the lg K10
2. Enable OEM unlocking and USB debugging
3. Copy twrp.img to disk C: /
3. Go to C: / and open command window. Enter: adb reboot bootloader (phone will start in fastboot mode)
4. Once in the fastboot mode enter the command: fastboot boot twrp.img
5. Once inside TWRP press cancel and then slide to allow modifications.
6. Mount System, data and sdcard.
7. Make BOOT-only backup (uncheck all other partitions)
8. Mount MTP
9. Copy BOOT backup from TWRP folder in our SD card (Boot.emmc.win) and rename bootlz4.img
10. Copy to Boot-resources of CARLIV IMAGE KITCHEN
11. Decompress with Carliv
12. Open bootlz4 folder and find the file "boot.img-ramdisk-compress".
13. Edit "boot.img-ramdisk-compress" with notepad ++ and change "lz4" to "gz"
14. Save
15. Recompress bootlz4.img
16. Go to output folder and look for bootlz4xxxxx.img and rename it as bootgz.img
17. Go to TWRP and restart in bootloader mode
18. Write in command window: fastboot flash boot bootgz.img
18. Then write in command window: fastboot boot twrp.img to return to TWRP
19. Install superSU 2.65
20. Backup BOOT (boot partition only)
21. Copy BOOT backup again (Boot.emmc.win) and rename it to bootgzroot.img
22. Copy to Boot-resources of CARLIV IMAGE KITCHEN
23. Unzip with Carliv
24. Open bootgzroot folder and find the file "boot.img-ramdisk-compress".
25. Edit "boot.img-ramdisk-compress" with notepad ++ and change "gz" to "lz4"
26. Save
27. Recompress bootgzroot.img
28. Go to folder output and rename "bootgzrootxxx.img" to "bootlz4root.img"
29. Copy "bootlz4root.img" to disk C: /
30. Copy bootlz4.img from boot-resources folder into C:/ too
31. Go to TWRP and reboot into bootloader
32. Write in command prompt fastboot flash boot bootlz4.img (this is to avoid bootloops)
33. Write in command window fastboot boot bootlz4root.img (there will be a bootloop and then boot normally)
34. Write in command window adb reboot bootloader
35. Write in command window fastboot boot bootlz4root.img, after boot write in command window adb reboot bootloader (fast because the phone will reboot after some seconds)
36. Write in command window fastboot flash boot bootlz4root.img
37. Start normally.
Ready, you have ROOT!
I am not responsible for any damage caused to your phone, your grandma or your hamster. Cheers!

waiting for ramdump
cpatrick3000 said:
This method is only for devices with MTK chipset.
It is based on the gottlasz method published in: http://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807
Required files:
- Carliv Image Kitchen (search in google)
- SuperSU 2.65 available in: http://downloadmirror.co/L2/BETA-SuperSU-v2.65.zip
- TWRP ported by berkantkz at: https://drive.google.com/open?id=0B0BUe3iVMnzKQnBpeDdTM1plc3c
- Time and patience (a lot of patience)
Steps:
1. Enable developer options on the lg K10
2. Enable OEM unlocking and USB debugging
3. Copy twrp.img to disk C: /
3. Go to C: / and open command window. Enter: adb reboot bootloader (phone will start in fastboot mode)
4. Once in the fastboot mode enter the command: fastboot boot twrp.img
5. Once inside TWRP press cancel and then slide to allow modifications.
6. Mount System, data and sdcard.
7. Make BOOT-only backup (uncheck all other partitions)
8. Mount MTP
9. Copy BOOT backup from TWRP folder in our SD card (Boot.emmc.win) and rename bootlz4.img
10. Copy to Boot-resources of CARLIV IMAGE KITCHEN
11. Decompress with Carliv
12. Open bootlz4 folder and find the file "boot.img-ramdisk-compress".
13. Edit "boot.img-ramdisk-compress" with notepad ++ and change "lz4" to "gz"
14. Save
15. Recompress bootlz4.img
16. Go to output folder and look for bootlz4xxxxx.img and rename it as bootgz.img
17. Go to TWRP and restart in bootloader mode
18. Write in command window: fastboot flash boot bootgz.img
18. Then write in command window: fastboot boot twrp.img to return to TWRP
19. Install superSU 2.65
20. Backup BOOT (boot partition only)
21. Copy BOOT backup again (Boot.emmc.win) and rename it to bootgzroot.bin
22. Copy to Boot-resources of CARLIV IMAGE KITCHEN
23. Unzip with Carliv
24. Open bootgzroot folder and find the file "boot.img-ramdisk-compress".
25. Edit "boot.img-ramdisk-compress" with notepad ++ and change "gz" to "lz4"
26. Save
27. Recompress bootgzroot.img
28. Go to folder output and rename "bootgzrootxxx.img" to "bootlz4root.img"
29. Copy "bootlz4root.img" to disk C: /
30. Copy bootlz4.img from boot-resources folder into C:/ too
31. Go to TWRP and reboot into bootloader
32. Write in command prompt fastboot flash boot bootlz4.img (this is to avoid bootloops)
33. Write in command window fastboot boot bootlz4root.img (there will be a bootloop and then boot normally)
34. Write in command window adb reboot bootloader
35. Write in command window fastboot boot bootlz4root.img (there will be an error related to NFC, accept and allow USB connection)
36. Write in command window adb reboot bootloader
37. Write in command window fastboot flash boot bootlz4root.img
38. Start normally.
Ready, you have ROOT!
I´m not responsible for any damage caused to your phone, your grandma or your hamster. Cheers!
Click to expand...
Click to collapse
sorry for my English. I tried to follow the tutorial, however the Get on the (4. Once in fastboot mode enter the command: fastboot boot twrp.img) The Reset one cell features a Next Message: waiting for ramdump. Is there something I can do to get rid of it? thanks for the help in MTK

MarkiinBRz said:
sorry for my English. I tried to follow the tutorial, however the Get on the (4. Once in fastboot mode enter the command: fastboot boot twrp.img) The Reset one cell features a Next Message: waiting for ramdump. Is there something I can do to get rid of it? thanks for the help in MTK
Click to expand...
Click to collapse
Mmm remove battery and try to turn on again. If It doesnt works reflash stock kdz and before doing the root use adb reboot bootloader and then fastboot oem unlock

MarkiinBRz said:
sorry for my English. I tried to follow the tutorial, however the Get on the (4. Once in fastboot mode enter the command: fastboot boot twrp.img) The Reset one cell features a Next Message: waiting for ramdump. Is there something I can do to get rid of it? thanks for the help in MTK
Click to expand...
Click to collapse
my phone is lg k10 430dsy mtk
I had the same problem
after flash twrp.img
show message: waiting for ramdump
---------- Post added at 08:43 AM ---------- Previous post was at 08:33 AM ----------
cpatrick3000 said:
Mmm remove battery and try to turn on again. If It doesnt works reflash stock kdz and before doing the root use adb reboot bootloader and then fastboot oem unlock
Click to expand...
Click to collapse
remove battery and switch on phone work device without problem
but not work recovery twrp on the 430dsy.
fastboot boot twrp.img in the terminal show message success but show error message: waiting for ramdump in the device
#sorry for my bad english

i got unlocked fastboot
I goto fastboot this command
# adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Click to expand...
Click to collapse
then flash twrp
# fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.596s]
booting...
OKAY [ 0.051s]
finished. total time: 0.648s
Click to expand...
Click to collapse
but show this error waiting for ramdump in the device
i waiting 30 min but nothing happened
please view Attached image

Hi, can you tell us, what is the difference between gottlasz' method and your method? I guess you added a few final flashing and booting steps.

123xdagsm said:
i got unlocked fastboot
I goto fastboot this command
then flash twrp
but show this error waiting for ramdump in the device
i waiting 30 min but nothing happened
please view Attached image
Click to expand...
Click to collapse
This error persists after the fourth step same, I think it must be the twrp or something is passing unperceived. Anyway I'll try another way.

I believe this ramdump thing is TWRP related. There is a 3.0.2 TWRP on berkantkz TWRP thread so the ones who get this error could also try that other one.

Where is that twrp 3.0.2?

wizzardsk said:
Where is that twrp 3.0.2?
Click to expand...
Click to collapse
there
http://forum.xda-developers.com/showpost.php?p=69381986&postcount=126

I still have those bootloop... When I flash with fastboot, the device freezes. When I flashed in TWRP, I got bootloop after restart...

wizzardsk said:
I still have those bootloop... When I flash with fastboot, the device freezes. When I flashed in TWRP, I got bootloop after restart...
Click to expand...
Click to collapse
I believe you need a fresh start... lg up or lg flashtool and full firmware reintall. Lg bridge and hard reset is not enough.
Of course it's just guessing so don't take it for granted.
---------- Post added at 06:46 PM ---------- Previous post was at 06:14 PM ----------
@cpatrick3000, did you manage to make it work after any unsuccesful or succesful attempts on root? I mean if you were rooted before but lost it and you had to make a hard reset or you used lg bridge update error recovery? Or your k10 was fully stock when you rooted it this way, no earlier attempts on root?

wizzardsk said:
Hi, can you tell us, what is the difference between gottlasz' method and your method? I guess you added a few final flashing and booting steps.
Click to expand...
Click to collapse
Hi. The difference is that I found a way to "force" boot of k10. If i don't do these final steps the phone stays on black screen after device corrupt warning (red triangle)

cpatrick3000 said:
Hi. The difference is that I found a way to "force" boot of k10. If i don't do these final steps the phone stays on black screen after device corrupt warning (red triangle)
Click to expand...
Click to collapse
I tried "fastboot flash boot bootlz4.img" and then my phone just freezed. After removing battery I just had something like bootloop. Device corrupt warning, then blank screen. I guess you had not these problems.

wizzardsk said:
I tried "fastboot flash boot bootlz4.img" and then my phone just freezed. After removing battery I just had something like bootloop. Device corrupt warning, then blank screen. I guess you had not these problems.
Click to expand...
Click to collapse
Mmmm thats strange. I think u better flash kdz (ill check my method again)

cpatrick3000 said:
Mmmm thats strange. I think u better flash kdz (ill check my method again)
Click to expand...
Click to collapse
Okay, which kdz do you mean?

wizzardsk said:
Okay, which kdz do you mean?
Click to expand...
Click to collapse
You hace to put your phone into download mode and restore by lg bridge. Here in the forums there's a tutorial. Btw always be sure that u can go back to normal before doing root related stuff (there's always bricking risk)

cpatrick3000 said:
You hace to put your phone into download mode and restore by lg bridge. Here in the forums there's a tutorial. Btw always be sure that u can go back to normal before doing root related stuff (there's always bricking risk)
Click to expand...
Click to collapse
I see. I have no prob going back, thx for your care. I even do not loose my data after restore in lg bridge.

wizzardsk said:
I see. I have no prob going back, thx for your care. I even do not loose my data after restore in lg bridge.
Click to expand...
Click to collapse
Np dude, i was trying to root like during a month, finally i used this method and works always for me (last night i rooted and works fine) hope u find a way to root!

cpatrick3000 said:
Np dude, i was trying to root like during a month, finally i used this method and works always for me (last night i rooted and works fine) hope u find a way to root!
Click to expand...
Click to collapse
You only used lg bridge to recover after root attempts or you tried lg up or lg flashtool?

How to downgrade to OS 1.5 on Remix Ultra tablet?

My Remix Ultratablet current running 2.0.305 keep random restart everyday.
So I wish to downgrade to OS 1.5
I ask for help form office Jide support , they told me I need to
Q1) Problem # stuck on step #1 already , When I ask where is the Remix Ultratablet driver when I install adb and fastboot ? Offical jide support told me I don't need a driver? How so ?
I can't get the tablet connect ??
Note: 1, I connect the tablet with USB to PC
Note: 2, I turn the USB debugging option on Tablet already.
Note: 3, I Test it on pc adb folder by trying "fastboot devices" only get "Waiting for Device" error
Q2) I also try other method (Power key + Volume up) on tablet which show
"Continue
Fastboot Protocol
Recovery Kernel
Reboot
Poweroff
Forced Recovery"
But when i press"Fastboot Protocol" , doesn't do anything ?
For your references:
Steps of instruction I receive from Jide offical support so far....
1) have ADB and Fastboot running, I download the Minimal ADB and Fastboot[/URL])
2)Download Remix OS 1.5 ROM[/URL]
3) Unzip the downloaded zip file ( SK1WG.zip ) and go to the folder
4. Connect the Remix to the computer via USB.
Make sure the fastboot binary is in your PATH ) or that you place the recovery image in the same directory as fastboot.
6. Open a terminal on your PC and reboot the device into fastboot mode by typing adb reboot bootloader or by using the hardware key combination for your device while it is powered off.
7. Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
-If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot documentation for more info.
-If you see "no permissions fastboot", make sure your UDEV rules are setup correctly.
8. Clean the existing data by entering the following command: fastboot -w
9. Flash images onto your device by entering the following three commands:
-fastboot flash system system.img
-fastboot flash recovery recovery.img
-fastboot flash boot boot.img
10. Once the flash completes successfully, run the following command to reboot the device into recovery to verify the installation.
-fastboot reboot

did u download the correct fastboot? you need Android 5.0 to get Remix 1.5

AmoraRei said:
did u download the correct fastboot? you need Android 5.0 to get Remix 1.5
Click to expand...
Click to collapse
That makes no sense what so ever.
Maybe it would be better to ask what platform he is using to flash his device with, as the instructions he has copy and pasted refer to Linux (udev rules)

it makes sense to me cause you have download the correct Android SDK to work on certain Android platforms.
https://developer.android.com/studio/releases/platforms.html
To compile your application against a particular version of Android, you must use the SDK Manager to download and install the SDK Platform for that release.

AmoraRei said:
it makes sense to me cause you have download the correct Android SDK to work on certain Android platforms.
To compile your application against a particular version of Android, you must use the SDK Manager to download and install the SDK Platform for that release.
Click to expand...
Click to collapse
Thanks of the reply ,
I'm using Win7 amd the Remix Ultratablet current running 2.0.305
I can't post link , but the ADB /Fastboot verson I download is also from xda Title "[TOOL]Minimal ADB and Fastboot [10-22-16]"
I download the "Version 1.4.1 Portable Here" with
MD5 Checksum: D7B1C009C87C77AAF045FA3ED239E591
Thanks for all the help in advance

When u plugged up the tablet to the pc, what did device manager say?
my associate said try this fastboot http://forum.xda-developers.com/showthread.php?t=2588979

AmoraRei said:
When u plugged up the tablet to the pc, what did device manager say?
my associate said try this fastboot http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
not exactly,i said to try this ,to install adb drivers.
http://forum.xda-developers.com/attachment.php?attachmentid=2480396&d=1388281089

tailslol said:
not exactly,i said to try this ,to install adb drivers.
http://forum.xda-developers.com/attachment.php?attachmentid=2480396&d=1388281089
Click to expand...
Click to collapse
well thank u for coming here and posting
:victory:

AmoraRei said:
When u plugged up the tablet to the pc, what did device manager say?
my associate said try this fastboot http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
when the tablet plugin to WIN7 , I got pop up windoes "Autoplay"
Name REMIX SK1WG
-Sync digital media file to this device
-Open device to view files
-Import picture and Video
when I click "Open device to view files" , I get to to see tablet "Internal Storage"
Thanks

sfbay998 said:
when the tablet plugin to WIN7 , I got pop up windoes "Autoplay"
Name REMIX SK1WG
-Sync digital media file to this device
-Open device to view files
-Import picture and Video
when I click "Open device to view files" , I get to to see tablet "Internal Storage"
Thanks
Click to expand...
Click to collapse
and what happens when you plug it when the device is in fastboot mode?

tailslol said:
and what happens when you plug it when the device is in fastboot mode?
Click to expand...
Click to collapse
That's the part I'm lost : What is consider "in fastboot mode"
I go to the WIN7 Folder there is unzip the "[TOOL]Minimal ADB and Fastboot [10-22-16] Version 1.4.1 Portable" and type fastboot devices , nothing happen
then I go to the tablet : turn off, then I try other method (Power key + Volume up) on tablet which show
-Continue
-Fastboot Protocol
-Recovery Kernel
-Reboot
-Poweroff
-Forced Recovery"
Nothing Happen ??
Note: I'm a first time ADB/ Fastboot user, but not totally a newbie. thanks

sfbay998 said:
That's the part I'm lost : What is consider "in fastboot mode"
I go to the WIN7 Folder there is unzip the "[TOOL]Minimal ADB and Fastboot [10-22-16] Version 1.4.1 Portable" and type fastboot devices , nothing happen
then I go to the tablet : turn off, then I try other method (Power key + Volume up) on tablet which show
-Continue
-Fastboot Protocol
-Recovery Kernel
-Reboot
-Poweroff
-Forced Recovery"
Nothing Happen ??
Note: I'm a first time ADB/ Fastboot user, but not totally a newbie. thanks
Click to expand...
Click to collapse
you should look the picture i gave you in my first message.

tailslol said:
you should look the picture i gave you in my first message.
Click to expand...
Click to collapse
Thanks, I will try the install "15 seconds ADB Installer v1.4.3" tonight when back home.
on side question: anyone know WHEN to use the (Power key + Volume up) on tablet which show
-Continue
-Fastboot Protocol
-Recovery Kernel
-Reboot
-Poweroff
-Forced Recovery"
The reason I ask because when I press "Fastboot Protocol" , it doesn't do anything. !!??
Also , the whole purpose for me to do the ADB/fastboot is to download back to OS 1.5, because my OS 2.0.305 keep random reboot ! So if anyone can tell me how to fix the OS 2.0.305 random reboot ? I might not have to do all this ADB/fastboot things ?
Thanks

sfbay998 said:
Thanks, I will try the install "15 seconds ADB Installer v1.4.3" tonight when back home.
on side question: anyone know WHEN to use the (Power key + Volume up) on tablet which show
-Continue
-Fastboot Protocol
-Recovery Kernel
-Reboot
-Poweroff
-Forced Recovery"
The reason I ask because when I press "Fastboot Protocol" , it doesn't do anything. !!??
Also , the whole purpose for me to do the ADB/fastboot is to download back to OS 1.5, because my OS 2.0.305 keep random reboot ! So if anyone can tell me how to fix the OS 2.0.305 random reboot ? I might not have to do all this ADB/fastboot things ?
Thanks
Click to expand...
Click to collapse
when you turn it on,it seems you do not have the minimum knowledge required to flash a device... you should stay away from downgrading it or study adb and fastboot videos and tutorials on google and youtube before doing anything.if you do anything wrong and brick your device,the warranty will not work,any bad flash could void your device warranty.

tailslol said:
when you turn it on,it seems you do not have the minimum knowledge required to flash a device... you should stay away from downgrading it or study adb and fastboot videos and tutorials on google and youtube before doing anything.if you do anything wrong and brick your device,the warranty will not work,any bad flash could void your device warranty.
Click to expand...
Click to collapse
I have try
Connect the Remix to the computer via USB.
fastboot devices
Which show:
xxxxxxxxxxxxxx fastboot
Then I type the following commands
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
ALL successful , then when reboot , it stuck on "Remix" flashing logo forever !!
Any help ?

sfbay998 said:
I have try
Connect the Remix to the computer via USB.
fastboot devices
Which show:
xxxxxxxxxxxxxx fastboot
Then I type the following commands
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
ALL successful , then when reboot , it stuck on "Remix" flashing logo forever !!
Any help ?
Click to expand...
Click to collapse
yea you forgot to wipe your device...
return to fastboot if you can then use those commands:
fastboot -w
fastboot reboot

update:
Now when i type
fastboot devices
I got :
xxxxxxxxxxxxxxxxxxxxxxxxxxxx fastboot
When I type: adb devices
I got:
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
On the Tablet side:
Bootloop only
But I can still press "Vol up + Power" and see the following menu
-Continue
-Fastboot Protocol
-Recovery Kernel
-Reboot
-Poweroff
-Forced Recovery"
Any help would be appreciated !!
Thanks

sfbay998 said:
update:
Now when i type
fastboot devices
I got :
xxxxxxxxxxxxxxxxxxxxxxxxxxxx fastboot
When I type: adb devices
I got:
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
On the Tablet side:
Bootloop only
But I can still press "Vol up + Power" and see the following menu
-Continue
-Fastboot Protocol
-Recovery Kernel
-Reboot
-Poweroff
-Forced Recovery"
Any help would be appreciated !!
Thanks
Click to expand...
Click to collapse
go to fastboot protocol ,hook it to your pc and proceed with the command i told you,but anyway caution,i told you you could brick your device...

tailslol said:
go to fastboot protocol ,hook it to your pc and proceed with the command i told you,but anyway caution,i told you you could brick your device...
Click to expand...
Click to collapse
Will try
but just want to check When I type: adb devices , iy did not list my drvice number , does it matter since I will be using "Fastboot -W" only?

sfbay998 said:
Will try
but just want to check When I type: adb devices , iy did not list my drvice number , does it matter since I will be using "Fastboot -W" only?
Click to expand...
Click to collapse
don't forget fastboot reboot and yes it matter,if the computer does not see the device the device can't receive commands...

HTC U Ultra stuck in bootloop..Can you experts validate the STEPS to solve the issue?

So, my HTC U Ultra got stuck in bootloop just 3 days after warranty ended(tough luck level : 100).
My phone runs on everything stock and no root.
I press all the buttons when powered off and it goes into bootloader mode. It displays options to boot into recovery mode, boot into download mode and power down, all of which(except power down) gets device into bootloop again.
THE PRIORITY OF GOALS IS : DATA RECOVERY > PHONE BOOTING AND WORKING PROPERLY AGAIN
I did a little research and figured out some sort of procedure by putting bits and pieces together :
1. Download ADB/Fastboot toolkit || universal driver from koush github // I have HTC Sync manager installed as well || twrp custom recovery image for htc u ultra || new ruu from htc support for rom update.
2. Now I put my phone into fastboot mode (since it doesn't show up on adb devices), connect to pc using usb.
3. I type in cmd : "fastboot devices" --> My device shows up there --> Again in cmd : "fastboot boot recovery mytwrp.img" --> the twrp boots into my phone
I was able to put this many steps together and after the last step, i have an abstract idea of what to do :
Enable USB Debugging using twrp recovery --> Use ADB Pull Command to get my all my data from phone to pc --> Use adb wipe the old Firmware (Not sure which command) --> Use adb again to flash new RUU (again not sure how, I've got an .exe file as RUU || should I get it in zip or img or any other format ? || Please help on this too) --> Finally Boot and hopefully everything turns out smooth and secure.
CAN YOU EXPERTS HELP ME TO PUT TOGETHER REMAINING STEPS (AND MODIFY ERRORS, IF ANY, OF EXISTING STEPS ) OF THIS PROCEDURE...???

Only to clarify: ADB and Fastboot are 2 completely different things.
ADB
is a protocol that allows you to communicate with an Android device that got booted, means its main Android OS is running
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb <ANY_SUPPORTED_ADB_SUBCOMMAND>
FASTBOOT
is a program used to manipulate (list, install, erase) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode with the fastboot protocol enabled.
IMPORTANT: Fastboot will only work if the OEM/Carrier has included support for the Fastboot protocol.
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot <ANY_SUPPORTED_FASTBOOT_SUBCOMMAND>

jwoegerbauer said:
Only to clarify: ADB and Fastboot are 2 completely different things.
ADB
is a protocol that allows you to communicate with an Android device that got booted, means its main Android OS is running
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb <ANY_SUPPORTED_ADB_SUBCOMMAND>
FASTBOOT
is a program used to manipulate (list, install, erase) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode with the fastboot protocol enabled.
IMPORTANT: Fastboot will only work if the OEM/Carrier has included support for the Fastboot protocol.
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot <ANY_SUPPORTED_FASTBOOT_SUBCOMMAND>
Click to expand...
Click to collapse
@jwoegerbauer Yes, thank you for the description, I understood the difference later on. Do you think the fastboot and adb steps I've mentioned will work properly ?

noobie12112 said:
@jwoegerbauer Yes, thank you for the description, I understood the difference later on. Do you think the fastboot and adb steps I've mentioned will work properly in my case?
Click to expand...
Click to collapse
Android boot loop error does not come out of thin air. There are several cases that may cause the Android is starting loop. If phone didn't get physically damaged then an action of the user is the main reason .
To answer your question: NO.
As already said:
ADB is integral part of Android OS hence if Android OS isn't started you can't make use of ADB, Fastboot is integral part of phone's bootloader ( comparable to a Windows PC's UEFI/BIOS ) means you can't access Android OS - will say its folders and files.

jwoegerbauer said:
Android boot loop error does not come out of thin air. There are several cases that may cause the Android is starting loop. If phone didn't get physically damaged then an action of the user is the main reason .
To answer your question: NO.
As already said:
ADB is integral part of Android OS hence if Android OS isn't started you can't make use of ADB, Fastboot is integral part of phone's bootloader ( comparable to a Windows PC's UEFI/BIOS ) means you can't access Android OS - will say its folders and files.
Click to expand...
Click to collapse
@jwoegerbauer Thank you for the insight. In my case, the phone wasn't physically damaged, the bootloop occurred out of the blue one day. Now, what I presumed I should do, is to flash a custom recovery (twrp) using "fastboot boot recovery.img" command, and using twrp (Can I enable USB Debugging using twrp ?) to access files, backup and then flash a new RUU. But I found that I need to unlock bootloader, is there any way to use command "fastboot oem unlock" and not lose data, or any other method to unlock bootloader, where i don't lose data?
Thank you for your help.

Unlocking phone's bootloader always causes complete loss of data.
Forget the TWRP thing, it's not helpful at all in your case.
Try to flash phone's Stock ROM by means of ADB - what requires ADB got installed on Windows computer and USB debugging got ( manually !!! ) enabled on phone.