Database Users

[Beginners Guide] Unlock & Custom ROM your TF300

I have been asked to port my "Beginners Guide" from the TF700 forum for the TF300. Since both tablets are very similar, that was not too hard to do
If I have missed to update a link specific for the TF300, do let me know please.
And the standard disclaimer: I am not responsible if you misunderstand instructions I give here, if my instructions are wrong, if you forget to charge the battery and the tablet dies halfway through a flash or if your house goes up in flames. YOU DO THIS AT YOUR OWN RISK
These instructions assume that you are on the latest Asus bootloader: 10.6.1.27.5
To determine which bootloader you currently have:
From an "Off" state, boot the tablet with Volume Down and Power into the bootloader menu. Read the small script in the upper left. You'll see
US_epad-10.6.1.27.5-20130801" or similar.
US or WW, JP, CN is your SKU or region
10.6.1.27.5 is your bootloader version
20130801 is the build date (and immaterial in most cases).
First things first:
Backup everything on your tablet you care about to an external microSD or your PC. Don't worry about your apps. You can always install them from the Play Store.
This is just common sense. It is not inherently risky to flash custom ROMs. But something can wrong at any time and you have to be careful. If you are, this is a safe procedure.
Basically the process of flashing a custom ROM on the TF300 involves three steps:
1) Unlock the bootloader using Asus' Unlock tool
2) Install a custom recovery on the tablet
3) Flash a custom ROM of your choice using said custom recovery​
Unlocking the bootloader
Your tablet should be fully charged at this point!
Make sure "USB debugging" is checked in Settings > Developer Options (if you don't see it, go to About Tablet and tap 7 times on Build Number)
Go to Asus website: https://www.asus.com/support/Download/28/1/0/9/8BmzkQ4yoz5WzBrW/32/
Choose "Android" for OS and look for the "Utilities" on the resulting page.
Download the Asus Unlock Tool v7 (not v8! It says v7 is for ICS but it'll work fine on JB - see below)
The tool downloads as a .rar file which is an archive you have to decompress. 7zip is a free and very good Windows tool that will do it for you
On your tablet, in Settings > Security check "Unknown Sources"
Copy the .apk you extracted from the .rar archive to your tablet.
Find the apk in your tablet's file browser, tap it and let it install
Open the app and follow the instructions. You will loose your warranty as soon as you click "I agree".
Update 2/15: Google added another wrinkle: It now checks even sideloaded apps and refuses to install them if they are considered not secure. The Unlock tool seems to fail their test. v8 does not install at all anymore. v7 will install if you allow "less secure apps" in your Google account settings. On the web - not your Google account on the tablet
July 2015: And another wrinkel... It seems to be pretty consistent now that the Unlock Tool hangs on the Google account password step. I suspect something changed on the Google side. It probably doesn't allow the tool to check/compare the password anymore. There have been quite a few security changes lately and the unlock tool never gets updated so I suspect that Google now is blocking access by the tool to it's servers.
The work-around is easy enough: Delete the Google account from the tablet (Settings > Accounts), then run the tool again. If that doesn't do it, do a factory reset from Settings, reboot and during the initial setup establish a WiFi connection but skip the google account setup, then run the tool
Click to expand...
Click to collapse
This can be a 5 Minute operation that goes without a hitch or a very frustrating experience with lots of error messages. There is no definite rhyme or reason for this. For some people it works like a charm, for others it works after 15, 25 or 55 attempts, for some never.... This problem is widely discussed on several forums. Google it if you hit that roadblock.
To check if you are unlocked, boot the tablet and read the tiny script. It should say:
The device is unlocked.
Installing a custom recovery on your tablet
I highly recommend you choose TWRP as your custom recovery. If you want CWM, you are on your own.
To push TWRP to your tablet you need to set up "Fastboot" between your tablet and your PC. Fastboot is a protocol that enables you low level access to your tablet.
Practice/Background
Power down your tablet and disconnect it from the dock
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in fastboot mode and you will see three icons (I assume again you are on a JB 4.2 bootloader. In older bootloaders you had 4 icons and had to select the USB icon to get into fastboot mode):
RCK - (which should be flashing) is your recovery (the stock recovery at this point, but once TWRP is installed this is one way to get into it)
Android - is your system, selecting it boots you back to into your ROM.
Wipe Data - stay away! Especially with custom software installed never, ever use this option!
To toggle between the three icons use Volume Down, to select one use Volume Up. Try it but do not push Volume Up when the 'Wipe data' icon is flashing!​
Installing ADB and fastboot plus the necessary drivers
For a working ADB/fastboot connection from PC to tablet you need:
a) Asus device drivers – if you connect the tablet to your PC and it's recognized as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it to get the drivers, then uninstall the program from your PC if you don't want it. The drivers will stay.
b) Fastboot and ADB drivers which will be installed if you run the tool below.
Windows Vista, 7, 8, 10:
Download and run this cool little tool [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
The tool installs the adb and fastboot.exe to a folder on your C:\ drive (look for adb) and the corresponding drivers. Takes about 15 seconds.
On Windows 8 and 10 you need to turn off the driver verification feature. Here's a great video on how to do it:
https://www.youtube.com/watch?v=afrvSGiMAtk
Or - even better - here's a quick command line toggle to achieve the same (thank you @Jack_Hardin):
Jack_Hardin said:
If you're running W10, you can disable Device Driver Signing without following the procedure in the linked video, but by (more simply) right-clicking on the Start button, selecting Command Prompt (Admin) and then typing:
Code:
BCDEDIT /set nointegritychecks ON
Doing the same with OFF at the end of the string, as easy to guess as it looks, will reenable them.
Click to expand...
Click to collapse
Jack_Hardin said:
Win XP (and all other Win versions if the above does not work for some reason)
I recommend the "ADB Install Tool" mentioned above or the 'Minimal ADB Fastboot Tool': [TOOL]Minimal ADB and Fastboot [7-18-13] - xda-developers
Either works fine.
If you need the drivers, get them here and install manually in Device Manager:[ADB/FB/APX Driver] Universal Naked Driver 0.72 (We dont need no stinking HTC Sync) - xda-developers
Win7 and Win8 users seem to have the best luck wth the drivers sbdags provided here: http://forum.xda-developers.com/showthread.php?t=2646279
It's fine if you want to use his Recovery Install Tool from that thread. But I highly recommend you familiarize yourself with basic fastboot commands! There are lots of tuturials all over the web.
Linux:Check out this site https://code.google.com/p/adb-fastboot-install/
iOS:[GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!) - xda-developers or:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
The fun begins
Fastboot does not play well with USB 3.0, so use a USB 2.0 port for this. And no hubs and such....
Boot the tablet into fastboot mode and connect it to your computer via the original USB cable
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7/8: Shift + right click and select "Open command window here".
For Win XP click here
select 'Run' from the Start menu, type
Code:
cmd
and hit Enter. In the resulting command prompt type
Code:
cd C:\adb\ [I](or whatever the path to your fastboot folder is..)[/I]
In the command window on your PC type:
Code:
fastboot devices
If that command returns a string of numbers and letters, you are good as gold.
Click me: View attachment 3070087
If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot.
Getting the correct drivers working can be the hardest part of this exercise. If your computer does not "see" the tablet in fastboot, try to uninstall the existing driver (if any) in Device Manager and manually install the drivers I linked to above. And if Windows does not cooperate at all, PM me and I can hook you up with a Puppy Linux live CD with fastboot/adb set up already.
Let's assume everything is good:
On your computer go here: https://dl.twrp.me/tf300t/
Download the latest version of TWRP.
FYI ONLY: If, for whatever reason, you want to format your data partition:
Formatting /data starting with TWRP 2.7.x and later takes a lot longer than in previous versions (up to 90 minutes). LET IT FINISH. DO NOT INTERRUPT THE FORMATTING.
Rename the file to twrp.blob and place it into the same directory as your fastboot.exe. Note: More recent versions of TWRP download with an .img extension. Leave the extensions as is, rename the first part to watever is easy to type
Again check the connection with
Code:
fastboot devices
If you get the connection, in the command window type:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
or
Code:
fastboot -i 0x0B05 flash recovery twrp.img
This will flash the recovery to the recovery partition
If it is successful type:
Code:
fastboot reboot
and let the tablet boot up normally.
You may get a dialog in TWRP offering to root the stock rom. You can accept or cancel it - doesn't matter. I assume you are going to install a custom rom and they are rooted anyway.
Create a nandroid
Your almost there! You are now on the stock ROM with a custom recovery installed.
Power the tablet down and boot into the bootloader menu with Volume Down and Power buttons.
With RCK flashing, push Volume Up and you should boot into TWRP. Familiarize yourself with the many options of the touch based interface without executing anything yet. TWRP is very user friendly. You basically cannot do anything of consequence "by accident", so don't be shy.
To create your Nandroid (a full system backup) touch "Backup", leave the default selection as they are and swipe the button to create a nandroid of your current system.
This is a very healthy habit to develop: You always want to have a nandroid of your last working system squared away so that you can do a simple restore if you flash something that does not work, or something goes wrong during a flash. With a working recovery and a good nandroid you are minutes away from a working system if you soft brick your tablet.
Hint:
It's a good idea to have at least one good nandroid on external media. Sooner or later you will format your data partition and if you're like me, you may forget to backup your nandroids in the heat of the moment..
Installing a custom ROM
From here on out it's as easy as downloading the installation file of your custom ROM, booting into TWRP, choosing "Install" and navigating to the zip of the ROM you want to flash.
If you see a "signed" in the zip file name (best_rom_ever_signed.zip), make sure you check "verify zip signature" under the "Install" menu. Some devs sign their ROM zips - a better way to ensure file integrity than md5 sum.
Whatever you decide to flash: READ THE OP of the corresponding thread and make sure you have the correct bootloader and the required recovery installed! I can't stress this enough! If you are not sure, DO NOT FLASH!
Look for the ROMs in the Development section of the XDA forum for this tablet: http://forum.xda-developers.com/transformer-tf300t/development
It is mandatory to do a Factory Wipe in TWRP before installing a custom ROM or going from one ROM base to another (a so called clean install).
If you choose 'Wipe' in TWRP, all you have to do is swipe the button - 'Factory Wipe' is the default selection under the 'Wipe' menu. You will loose your apps, but it will not wipe your /data/media/ folder where your files, pictures, etc live.
If you do this right before flashing the custom ROM, make sure you have the zip file of your custom ROM on your microSD - not on your internal SD where it may get wiped....
Once you installed a custom recovery NEVER EVER UNDER ANY CIRCUMSTANCES - AND I REPEAT: NEVER! - use the 'Wipe Data' option from the bootloader menu or the "Factory Reset" option in Settings > Backup&Restore.
In your custom recovery you have the option to wipe, backup and restore every partition on your tablet selectively or collectively. Any wiping, any backup and any restore of the system, data, recovery or boot partitions MUST be done in your recovery (or in fastboot)!
You can safely use Titanium Backup or Asus Backup for apps and settings, but that's it. For everything else use your recovery.
FREE ADVICE
There are alternative methods to flash a recovery to your device using apps like GooManager (currently not supported anyway), TWRP Manager or Flashify from the Play Store which do it right from your tablet. These apps "save you the trouble" of getting ADB and fastboot set up and working on your PC. These methods still exist and they do work - mostly - and if you have root. But I would not recommend them.
If you are not willing to invest the time to learn the basics about ADB and fastboot (google "adb fastboot xda tutorial") and install the necessary drivers on your PC, you should not be flashing anything to your tablet!
GET ADB AND FASTBOOT WORKING!
Sooner or later you will do something stupid (I have done it and so will you) and ADB/fastboot may save your bacon IF you had it working when you didn't really need it.
Hit the 'Thanks' button and rate the thread 5 stars if this helped you
Click to expand...
Click to collapse

Save it for later

Mine

sbdags said:
@stamatis could we sticky this please.
Brilliant post Bernd :good:
Click to expand...
Click to collapse
Can we make that happen here to @stamatis
Thx Josh

Nice one Bernd! :good::good:

boot sequence
Hi,
Is normal to see three TUX and some phrases at the power on ?
Can I hide it ?
tnkx
Nicola

You mean the penguins?
That's normal I'd you're running a Rom that uses _that's preinit scripts. You can't hide them - why would you?

thank you SO much
I love you!
Wow, I've never had so much trouble rooting a device before! And days ago, I rooted my T700 without any problems. So, I guess I should have expected the hubby's TF300T to be problematic! Recoveries didn't work, I tried multiple ones. Eventually, I had a recovery that didn't recognize any partitions. I used fastboot to erase them all and put the stock ROM back on--wouldn't boot up. This thread was an immense help! I've moved the other recoveries and ROMs into my non-working folder!
Thanks again!
Lynne

Awesome
What a well written guide! I have a decent understanding of fastboot and adb (although minimal experience), and I perfectly understood every step.
My advice to all newbies like me.... Read stuff ALL of the way through (and understand it), BEFORE stepping off in it.

ok im a bit lost... i have rooted both Nexus 7s, nook hd and hd+, a tf101, and a few tv boxes.. so im not sure why this is hanging up... im trying to root and install the TWRP recovery on a tf300... followed the instructions and even have the char string that means... every thing should be good to go.... have checked that the twrp is in the dir of adb... but when i try to push the twrp.blob to the tf300, it just give me.. this error..
c:\adb>fastboot devices
015d14febf64041b fastboot
c:\adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6800 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
so.. at this point i not sure what else to trouble shoot... the tablet is in fastboot mode.. adb sees the tablet.. at least that is what the char string confirms.... so any help would be very much appreciated.. just a bit lost on this...
chris

scuzzo said:
ok im a bit lost... i have rooted both Nexus 7s, nook hd and hd+, a tf101, and a few tv boxes.. so im not sure why this is hanging up... im trying to root and install the TWRP recovery on a tf300... followed the instructions and even have the char string that means... every thing should be good to go.... have checked that the twrp is in the dir of adb... but when i try to push the twrp.blob to the tf300, it just give me.. this error..
c:\adb>fastboot devices
015d14febf64041b fastboot
c:\adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6800 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
so.. at this point i not sure what else to trouble shoot... the tablet is in fastboot mode.. adb sees the tablet.. at least that is what the char string confirms.... so any help would be very much appreciated.. just a bit lost on this...
chris
Click to expand...
Click to collapse
The bootloader is unlocked yes ?
What is your bootloader version ?
Try a different USB port ?
Thx Josh

lj50036 said:
The bootloader is unlocked yes ?
What is your bootloader version ?
Try a different USB port ?
Thx Josh
Click to expand...
Click to collapse
hello,
bootloader is unlocked or at least it says it is at the boot screen.. "your device is unlocked"..
real time... just swapped ports... its says it pushed the recovery.... so... will continue along this path.... and see how it goes.... i think its good to go... just as you suggested... port swap... cool... i bought this just so i could root it and put the kit kat kis rom on it.... thanks for your help and big ups to OP.... great guide ...
thanks again.!

Nice guide!
I've been wanting to put a custom rom on my transformer for a long time. This guide worked like a charm.
The only problem I had was when I tried to flash TWRP recovery, but switching USB port fixed that problem.
I flashed the latest CM12.1 nightly and it works fine.
Many thanks!

Help please, I'm stuck!
I'm trying to flash recovery,
after typing:
fastboot -i 0x0B05 flash recovery twrp.blob
I got this on tablet screen:
"Starting Fastboot USB download protocol"
for about 25-30 already and nothing happens, any ideas?
thanks

You won't see anything on the tablet screen, but what does the command window say?
Go back, read the guide again, it's all in there....
Sent from my K00C using Tapatalk

berndblb said:
You won't see anything on the tablet screen, but what does the command window say?
The command window didn't say anything, just blinking cursor after my command line
Go back, read the guide again, it's all in there....
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Mishka79 said:
I'm trying to flash recovery,
after typing:
fastboot -i 0x0B05 flash recovery twrp.blob
I got this on tablet screen:
"Starting Fastboot USB download protocol"
for about 25-30 already and nothing happens, any ideas?
thanks
Click to expand...
Click to collapse
Thanks,
After writing the question, I've restarted my tablet and did all the steps again.
The second time everything worked as it should. :good:
thanks for your great guide

Really great guide
Amazing guide thanks for the help

Thank you for this good tutorial but I have one question.
I'm a newbie here, here is my dilemma: I've flashed CM android 5.1.1 successfully from stock 4.2. (Thanks for this detailed tutorial), but I lost my root privileges, now I can't use my root apps. How do I apply root to this ROM? My device is an ASUS TF300T. I've tried Kingo Root and King Root but no success.
I would really appreciate your help and inputs.
Cheers!

ANDROIDYER said:
I'm a newbie here, here is my dilemma: I've flashed CM android 5.1.1 successfully from stock 4.2. (Thanks for this detailed tutorial), but I lost my root privileges, now I can't use my root apps. How do I apply root to this ROM? My device is an ASUS TF300T. I've tried Kingo Root and King Root but no success.
I would really appreciate your help and inputs.
Cheers!
Click to expand...
Click to collapse
I have not used CM in quite a while but I think you have to enable root in Developer Options. I think it is not enabled by default.
If hat does not work you can go to Chainfire's website and download the flashable SuperSU and just flash it in recovery

Thanks and a couple of notes on TF300T
Thanks so much for the great guide. My 300TF was nearly bricked due to slowness and freeze-ups. I'd stopped using it. The process worked and am now running KatKiss. Couple of problems and their solutions for anyone who may have the 300TF:
-When trying to "Unlock Bootloader" I kept getting to "enter Google password" but when I did so (correctly) it was not accepted. The solution was to do another factory reset and NOT install google services. Didn't ask for password after that.
-Used fastboot command line to install "twrp.blob" but nothing happened and it timed out. I had to take out other usb connect programs first (in my case "easy-tether" and my LG phone connect app.) After that everything went as per your guide.
Thanks again
Geneg

[Q][Solved] Where should I begin as a beginner?

Edit:
[Procedure] http://forum.xda-developers.com/showpost.php?p=64841837&postcount=27
Edit/
I am creating this thread dedicated for me and other beginners "noobs".
Where should I begin as a beginner?
I am looking to unlock and root with latest MM that motorola supplies.
Things you should know about me:
I have no idea how to use adb.
I have no idea how to unlock & root or even if I should but I don't like ads.
I have no idea which firmware to use.
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
I am completely lost.
I have not gotten my phone yet, I ordered it this morning and will be here Friday. I am just trying to compile sources and info.
Thanks a bunch guys, I really need help with this.

One piece of advice for starters just since you used the word noob. Never mod your phone on a low battery. You can mess a phone up enough to break offline charging, and without a removable battery that you can swap out or charge in a cradle that could get awkward in a hurry on this phone. I always make sure I'm >75% just in case. You can fastboot your way out of all kinds of trouble; but not if your battery is dead and your phone is so screwed up it is not offline charging.
Your phone will probably show up with Android 5.1.1 installed, at least I got mine about 3 weeks ago and it did. Once it is through initial setup it should want to apply an OTA to Android 6.0 right away; if not check for it in Settings -> About -> System updates and it should find one. Just let it update before you do any setup or app downloading.
Once you're on MM, before you do any setup you have to unlock your bootloader if you intend to root. You'll get all the warnings about voiding warranty and here there be dragons, so be prepared for that. Also, unlocking the bootloader will wipe your internal storage, so don't bother with any setup or app downloading before you do it.
Start with Heisenberg's thread. It is a great guide on how to setup your computer for adb and fastboot as well as all the syntax you need for unlocking the bootloader and installing a custom recovery. Make sure to get the 2.8.7.1 version of TWRP that is patched to work with the MM bootloader.
When you boot to TWRP recovery for the first time it will ask if you want to keep system read only. Keep system read only and make a backup immediately. I usually make one backup of boot, system, and data, and a separate one of just efs; don't worry if you don't understand, you'll figure it out when you get there. TWRP is all touch based and pretty intuitive. This way you have good, untouched system backup to fall back on just in case.
When it comes to rooting MM, don't use the old system install method. Flash a SuperSU from this experimental systemless root thread (I used this instead of the ivcarlos method linked to the Heisenberg thread because it is more automated and easier). I can vouch for the 2.62-20151210170034 version of SuperSU. I've used it to root stock MM on this phone 3 or 4x as I've restored backups and changed kernels. I've heard the 2.64 and above SuperSU versions are not working with this phone on MM, and the older traditional system root methods like the v2.49 version that is linked to the Heisenberg thread are causing bootloops on MM. Don't panic on first boot after the systemless root; it appears to bootloop once but comes up normally the second time.
One other thing, TWRP doesn't seem to be able to detect the systemless rooting method, and it really wants your phone to be rooted. If/when TWRP offers to automatically install SuperSU, don't let it - ever - it will keep asking. It must use the old method that causes bootloops on MM, not the new systemless method linked above.
Once you're all rooted and settled in, if you get sick of the unlocked bootloader warning you can fix it by reading up in this thread. Just be sure to read carefully and get the MM logo and not the LP logo.

Wow, thank you so much for the long type up.
Duly noted and this is a great start. May I continue here if I run into any problems?
I think ima have fun with this phone
I am into tinkering with devices, "sometimes linux" etc, like my PC OS win7x64 is modified big time, so I probably will catch on with unlocking rooting etc very quickly.
I got chillz and cannot wait!

Read a lot. Do a lot of reading on the topic before trying it. Basically learn all the possible errors or negative outcomes before they happen, so your not blindsided and are ready for anything that can happen.

gokart2 said:
Read a lot. Do a lot of reading on the topic before trying it. Basically learn all the possible errors or negative outcomes before they happen, so your not blindsided and are ready for anything that can happen.
Click to expand...
Click to collapse
Will do. I was reading, flashing can screw up the modem,wif and what ever else.
I hope I don't screw it up.

Hitti2 said:
Will do. I was reading, flashing can screw up the modem,wif and what ever else.
I hope I don't screw it up.
Click to expand...
Click to collapse
Good luck :good:
I just noticed one thing that might not be entirely clear in the Heisenberg thread. It says to enable adb in the Settings -> Developer Options menu, but by default you won't have a Developer Options menu.
To get one, go into Settings -> About Phone, scroll all the way to the bottom, and tap on build number about 8 or 10 times. Your phone will say something to the effect of congratulations now you're a developer, and you'll have the menu.
Edit: i just noticed it says how to enable developer options further down the page

ty, I will need it lol.
Dev options were on my S5 too. My pops showed me how to on the S5, kinda hoping it was the same way to enable them, turned out to be. Cool.

gokart2 said:
Read a lot. Do a lot of reading on the topic before trying it. Basically learn all the possible errors or negative outcomes before they happen, so your not blindsided and are ready for anything that can happen.
Click to expand...
Click to collapse
^^^This^^^
and remember what XDA is really for ...http://forum.xda-developers.com/showpost.php?p=2031989
with that, enjoy all the reading, and do not be afraid to look at other sites too, there are even videos around that can help guide you...
and there are fellow members here to help...but most questions have already been asked and answered, so search first! Cheers! :highfive:

This might sound so stupid.
So, I will begin with the recommendation of installing twrp as my first step.
http://forum.xda-developers.com/showpost.php?p=64545146&postcount=131
1) Be sure to get the newest TWRP that has been patched for M.
Click to expand...
Click to collapse
How do I go on installing this TWRP? Does it include flashing TWRP to the phone? Or is an app? I don't understand.
How many ROMs can be flashed to the phone, 2? TWRP & Marshmallow?

Hitti2 said:
This might sound so stupid.
So, I will begin with the recommendation of installing twrp as my first step.
http://forum.xda-developers.com/showpost.php?p=64545146&postcount=131
How do I go on installing this TWRP? Does it include flashing TWRP to the phone? Or is an app? I don't understand.
How many ROMs can be flashed to the phone, 2? TWRP & Marshmallow?
Click to expand...
Click to collapse
Sounds like you need to do more studying and reading
TWRP is not a ROM, it is a custom recovery image, which allows you to flash ROMs.
Start here..http://androiding.how/root-moto-x-pure/
Then go here..http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3206883 for a good tool. (May have already been linked above...)

[Q] Where should I begin as a beginner?
At the beginning, of course.
Sorry couldn't resist...

Naddict said:
Sounds like you need to do more studying and reading
TWRP is not a ROM, it is a custom recovery image, which allows you to flash ROMs.
Start here..http://androiding.how/root-moto-x-pure/
Then go here..http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3206883 for a good tool. (May have already been linked above...)
Click to expand...
Click to collapse
Tyvm.
Before I proceed, I need to backup, right? How do I go forth doing a backup?
Also, I am updated on MM, does those two links above work on MM?

Hitti2 said:
Tyvm.
Before I proceed, I need to backup, right? How do I go forth doing a backup?
Also, I am updated on MM, does those two links above work on MM?
Click to expand...
Click to collapse
after you unlock and install custom recovery, you use TWRP (the custom recovery) to create the backup...
as you are on MM, you cannot use the "all in one" application that I provided in the link...so you will have to manually install/flash your rom

Wow im so frustrated. I think i give up. There is no guides upto date to do exactly twrp, backup, install w/e n root for ota mm.
I'll donate 30 usd via paypal if someone can.

Hitti2 said:
Wow im so frustrated. I think i give up. There is no guides upto date to do exactly twrp, backup, install w/e n root for ota mm.
I'll donate 30 usd via paypal if someone can.
Click to expand...
Click to collapse
Clearly you are impatient (not trying to be rude here), - XDA truly is not a place to pay for someone to do it for you, XDA is about learning and development, there are several places that a search will get you what you need. Many members have also posted links above to vast amount of information (specifically this post and this entire thread here http://forum.xda-developers.com/showpost.php?p=64183396&postcount=151 and here too http://forum.xda-developers.com/showpost.php?p=64311581&postcount=171) that you should take time to read and then, as you move through these things then you ask questions.
Offering to pay to have someone do it for you is really not what this site is about.
Read, do google searches...it has been done a hundred time already mate, take the time to learn what it is you are doing before actually doing it.

I dont have 400 to spare for for another phone if i brick this one because i was pointed to all kinds of mixed links. Ionno ill wait till someone comes up with a guide then.
Thanks.
Edit:
Let it be known as well, because you know how to milk a cow doesn't mean I know how to milk a cow. Or change a complete motor out of a vehicle etc.

Not being a smartarsh either. I'll prob end up like this guy https://www.reddit.com/r/MotoX/comments/3z2e6g/stuck_rooting_moto_x_pure_on_60/
And I read this, http://forums.androidcentral.com/moto-x-pure-edition/622331-6-0-marshmallow-root.html#post4899736
Dunno which one to go for.
I'm done for today, I'll come back tomorrow to upset with this.

Hitti2 said:
I dont have 400 to spare for for another phone if i brick this one because i was pointed to all kinds of mixed links. Ionno ill wait till someone comes up with a guide then.
Thanks.
Edit:
Let it be known as well, because you know how to milk a cow doesn't mean I know how to milk a cow. Or change a complete motor out of a vehicle etc.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=2031989
Hitti2 said:
Not being a smartarsh either. I'll prob end up like this guy https://www.reddit.com/r/MotoX/comments/3z2e6g/stuck_rooting_moto_x_pure_on_60/
And I read this, http://forums.androidcentral.com/moto-x-pure-edition/622331-6-0-marshmallow-root.html#post4899736
Dunno which one to go for.
I'm done for today, I'll come back tomorrow to upset with this.
Click to expand...
Click to collapse
Looks to me like several folks in there offered suggestions on how to successfully get root ...and again, as my last helpful post here...you really need to read Heisenberg's thread, that guide works, and from what I can tell, you have to use systemless root.

Ok, I will follow
Intro
This thread will serve as a location for basic how-to guides for the Moto X Pure. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
Prerequisites:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You'll find Motorla drivers here, download it and install, then reboot your PC.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
Index
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Make A Nandroid Backup With TWRP Recovery
How To Root Your Stock Rom
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System
1. How To Unlock Your Bootloader
Go into About Phone in Settings, click on Build Number 7 or 8 times until it says you have enabled Developer Options. Go back to Settings and enter the newly opened Developer Options section, scroll and click on the Enable OEM Unlock option.
Power off your phone then boot into fastboot mode (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.
Once you've confirmed your fastboot connection issue this command:
Code:
fastboot oem get_unlock_data
It should return something like this:
Code:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Copy that code (with no spaces between the characters) and paste it somewhere for safekeeping, you'll use it in a minute.
Go to the Motorola bootloader unlocking page. You'll need to create an account with Motorola if you don't already have one. Once you're signed in you can scroll down to step 6 and paste the above code into the text field and hit the “can my device be unlocked” button.
Read the terms and conditions and accept them if you agree (you can't continue unless you accept).
Click the “request unlock key” button and an email with your unlock token will be sent to the email account that you signed up with.
Once you have retrieved the token from the email you can use it within the following command to unlock your bootloader:
Code:
fastboot oem unlock xxxxxxxxxx
(Replace the xxxxxxxx with your unique unlock token)
Your bootloader is now unlocked!
Reboot with this command:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
2. How To Install A Custom Recovery On Your Device
Prerequisites: unlocked bootloader.
Download the recovery of your choice, here's TWRP.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Put the phone in fastboot mode and connect it to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery <filename>.img
(Replace <filename> with the actual filename of the recovery, the recovery filename in the command will change depending on which recovery you're flashing)
Wait for the recovery to flash, it'll only take a few seconds, you'll get a finished message in your command prompt window once it's done.
It's now safe to disconnect your usb cable.
Don't reboot the phone normally, use the volume buttons to highlight recovery and press the power button to select it. This will stop the stock OS from patching it with the stock recovery in boot. Once you've booted into TWRP like this once, you can reboot normally.
3. How To Make A Nandroid Backup With TWRP Recovery
Prerequisites: unlocked bootloader, TWRP recovery.
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
All you need to do is enter TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
Click to expand...
Click to collapse
& I will follow
Hello guys!
I make my own ROOT (systemless, thanks for Chainfire) images for Moto X Style with Marshmallow (build MPH24.49-18). Its use "experimental" systemless SuperSU version 2.56 - more info on http://forum.xda-developers.com/show...35&postcount=2. No need replace bootloader or recovery. Still need unlocked booloader.
Because TWRP didn't work in this version of bootloader (0xA048), I cooked "su.img" in a Linux box and used "/data/local/tmp" as bridge (accessible by ADB).
WARNING! I am not responsible for any harm on your phone. When you're not sure if you can do it, leave it!
For use, you need
1) unlocked bootloader.
2) if your bootloader not unlocked, make sure you have copy of your data, because this process will erase your device.
3) install ADB and FASTBOOT on your pc using minimal ADB or Android SDK.
4) install ADB drivers from Motorola or Universal ADB.
5) download provided files.
6) download SuperSU ver. 2.56 from http://forum.xda-developers.com/apps...ellow-t3219344.
Steps:
1) extract files in a folder of your choice (su.img, boot.img).
2) extract Superuser.apk from SuperSU-v2.56-20151030013730.zip from common folder.
3) enable USB debugging on Android.
4) connect your device on pc.
5) open a command prompt in a new folder.
6) type "adb push su.img /data/local/tmp" without quotes.
7) type "adb install Superuser.apk" without quotes.
8) now reboot your device into fastboot mode by typing "adb reboot bootloader".
9) type "fastboot flash boot boot.img" without quotes.
10) type "fastboot reboot" without quotes.
And enjoy!
Now you have a rooted MotoX Style Marshmallow. To apply any OTAs, you only need reflash stock boot.
Click to expand...
Click to collapse
I still think its going to brick but uhwell.

So far so good, I've got it unlocked.
I apologize for my ignorance. I am gonna take it a step at a time.
Doing step one "unlocking" was scary but it went good.
Wish me luck!

[UNBRICK] [WORKING AND TESTED 100%] Fix Hardbrick Meizu M2 easily without dongle

I thank Dinolek for creating this tool that allows the Unbrick of this device!
Hi, a few years ago, trying to change the logo partition of my Meizu M2 Mini I corrupted it and it went into HardBrick, I made threads where I asked how to do Unbrick and everyone told me that I had to use a dongle and other applications that were certainly expensive .
I tried with SP Flash Tool and gave authentication and bootrom errors. After a few years the developer Dinolek released a tool called Amonet.
I tried this tool and it brought my hardbricked phone back to life without problems.
This tool uses an exploit at startup that allows you to change the device's memory and, consequently, write the partitions, so if you corrupt the important partitions for booting such as: Logo, Boot or Preloader, you can use this tool for correct that otherwise you cannot access these partitions and the Bootrom.
The bootrom is a Read-Only memory and even if you remove the EMMC on the phone, the bootrom will continue to work.
Requirements:
PC With Linux (Tested) or Virtualbox with Linux (Not Tested)
Obviously the Meizu M2 Mini
Python3 and pyserial (on ubuntu/debian "sudo apt install python3 python3-serial")
And the zip file of the tool that I link to after.
1) Download the file that is in the link below
2) A very important step that, if not performed, does not allow you to use the tool (I had to do it several times)
Run the command "sudo systemctl stop ModemManager" and doing this causes the ModemManager to stop which can interrupt the Unbrick.
3) After extracting the zip of the tool enter the folder and start the terminal. Run the command "sudo ./main.sh -u"
4) At that point it will be looking for the phone bootrom. Switch off the phone press the VOLUME button - (WITHOUT PRESS THE POWER BUTTON! OTHERWISE DOES NOT RECOGNIZE THE DEVICE!) and connect the cable.
5) At that point the Unbrick process starts, at this moment the program is flashing the most important partitions of the device and can take some time. Do not disconnect the USB cable, you could corrupt important partitions, if you do you have to restart from step 3. Unplugging the cable does not corrupt the bootrom and the phone can still be unbrick but it is not recommended to do so and it is very dangerous.
If it happens that at the beginning the Tool does not recognize the device do not worry, turn off the device, run the command "sudo systemctl stop ModemManager",and try again at point 3.
After the procedure the phone will come back to life and it will restart in recovery, from there install the stock rom and your phone will return as before, if the bootloader was unlocked before the brick remains unlocked and you can also flash the TWRP and Custom ROMs without the need to unlock it again. If by chance the bootloader is locked then follow the guide in this link: https://forum.xda-developers.com/meizu-m2-mini/development/tool-amonet-meizu-m2-t3945812.
To download the tool go to this link: https://forum.xda-developers.com/devdb/project/?id=33492#downloads and download the zip file.
Thanks to Dinolek.

fgfdf

@XRed_CubeX Hello! maybe you still have amonet_mblu2.zip? the original link is invalid. I urgently need to get my brick back into operation. Thanks in advance)

WhiteDevil_ said:
@XRed_CubeX Hello! maybe you still have amonet_mblu2.zip? the original link is invalid. I urgently need to get my brick back into operation. Thanks in advance)
Click to expand...
Click to collapse
Amonet isn't supported anymore, use MTK Bypass Utility

My moto g5 plus is bricked and is stuck at fastboot mode

I have Moto g5 plus xt 1686 Indian variant.I hadn't unlocked my bootloader. The device was working but suddenly one day it got bricked dont know why but it boots only in fastboot mode that to with no information.The only error i am able to verify is "failed to validate boot image"
After trying for around 1 week i have tried these things
1. Used rsd lite earlier it wasnot able to identify my device in windows 10 machine but in windows 7 machine its able to do that but unable to flash the device
2. tried to flash using adb commands but they are also not working
Since i tried to unlock the bootloader through the guide of motorola website then also i am not able to do that and get this error "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
Please help ....

Anubhav074 said:
I have Moto g5 plus xt 1686 Indian variant.I hadn't unlocked my bootloader. The device was working but suddenly one day it got bricked dont know why but it boots only in fastboot mode that to with no information.The only error i am able to verify is "failed to validate boot image"
After trying for around 1 week i have tried these things
1. Used rsd lite earlier it wasnot able to identify my device in windows 10 machine but in windows 7 machine its able to do that but unable to flash the device
2. tried to flash using adb commands but they are also not working
Since i tried to unlock the bootloader through the guide of motorola website then also i am not able to do that and get this error "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
Please help ....
Click to expand...
Click to collapse
You need to install fastboot in pc and then flash the device to make it work.
You can prefer this thread
https://forum.xda-developers.com/g5...-flash-stock-romfactory-t3691396/post74221633

Anubhav074 said:
I have Moto g5 plus xt 1686 Indian variant.I hadn't unlocked my bootloader. The device was working but suddenly one day it got bricked dont know why but it boots only in fastboot mode that to with no information.The only error i am able to verify is "failed to validate boot image"
After trying for around 1 week i have tried these things
1. Used rsd lite earlier it wasnot able to identify my device in windows 10 machine but in windows 7 machine its able to do that but unable to flash the device
2. tried to flash using adb commands but they are also not working
Since i tried to unlock the bootloader through the guide of motorola website then also i am not able to do that and get this error "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
Please help ....
Click to expand...
Click to collapse
You cannot unlock bootloader anymore. So try flashing normally. If your hardware is not damaged then you might me able to make it work.

debdeep98 said:
You cannot unlock bootloader anymore. So try flashing normally. If your hardware is not damaged then you might me able to make it work.
Click to expand...
Click to collapse
Since it is booting into fastboot mode i dont think its damaged.But the problem is its my first time for flashing so i dont know very much about it.
What i know is that , i installed adb in my system ,and then through command prompt i tried to detect my device But its not getting detected.So if you can please provide me a brief guide for flashing phone.

Anubhav074 said:
Since it is booting into fastboot mode i dont think its damaged.But the problem is its my first time for flashing so i dont know very much about it.
What i know is that , i installed adb in my system ,and then through command prompt i tried to detect my device But its not getting detected.So if you can please provide me a brief guide for flashing phone.
Click to expand...
Click to collapse
K.. install adb(https://www.androidfilehost.com/?fid=745425885120698566 ). If you had installed moto assistant then you'll have the drivers. If not then google motorola drivers and install them(http://www.motorola.com/getmdmwin ).
Once it's done. Open the folder where adb is installed.
Hold shift and right click>open command promt here.
At this point boot into the bootloader on your phone (fastboot mode).
On cmd type fastboot devices.
If your device is detected then it will show on screen.
If you get to this part.
Start flashing thru fastboot.
Get the files from google( or https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL)
Instructions to flash are in xda.
If you get failed to flash: security version downgrade then you're probably flashing an older firmware. Download the latest.
If you get failed to flash: preflash validation failed then there's not much you can do. Or atleast i don't know a solution to that.

its not detecting my device
Actually the problem is that it is not detecting my device when i give this command, although i have installed device drivers and adb also....This is is the problem

Anubhav074 said:
Actually the problem is that it is not detecting my device when i give this command, although i have installed device drivers and adb also....This is is the problem
Click to expand...
Click to collapse
Did you lenovo moto smart assistant to flash the device, you can try that as it will flash the device for you.

riyan65 said:
Did you lenovo moto smart assistant to flash the device, you can try that as it will flash the device for you.
Click to expand...
Click to collapse
yeah i tried that but when it is not verifying my phone when i select id (which is xt 1686) it says that phone can not be verified try again.i have tried every given id but it is refusing to accept my device.

Anubhav074 said:
Since it is booting into fastboot mode i dont think its damaged.But the problem is its my first time for flashing so i dont know very much about it.
What i know is that , i installed adb in my system ,and then through command prompt i tried to detect my device But its not getting detected.So if you can please provide me a brief guide for flashing phone.
Click to expand...
Click to collapse
Here's a guide to flash stock firmware.
Try the linked Mini ADB & Fastboot, if your device isn't recognised try to connect it to another usb port or use another usb cable.
Are you sure that you're in fastboot mode when you type the commands?
Read the guide carefully.
You need:
Latest signed stock firmware:
Europe (RETEU):
https://drive.google.com/file/d/13WuhoogtAdoincAyTwCLvRj0d-Z9kL0P/view?usp=sharing
India (RETIN):
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
US (RETUS):
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
flashallO.bat:
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
Motorola drivers:
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view?usp=sharing
Mini ADB & Fastboot
https://drive.google.com/file/d/1lLYfimKN1U5CJ9cfpTCkhtMiuG8EfXBZ/view?usp=sharing
1) Download the 8.1.0_OPS28.85-17-6-2 Indian firmware (it's the last one for the Moto G5+ (potter).
2) Install Mini ADB & Fastboot (best place is the root directory of C:/ or how the partition/hard drive is named where your OS resists), not in program files or another folder.
3) Extract the firmware to that ADB & Fastboot folder.
4) Download my "flashallO.bat" and move it to that folder too.It removes the need for you to manually flash all partitions, just double-click it and it'll run all the commands for you.
5) Download and install Motorola device drivers.The program is called "Motorola Device Manager".
6) Reboot your phone to the bootloader. To do this, turn it off, then hold down the power and volume down buttons until you see a bugdroid undergoing open-heart surgery.
7) Connect the phone to your PC with your USB cable. Type
Code:
fastboot devices
to check if your device is connected. A serial number should be shown.
8) Run the flashallO.bat script. (Caution: This will wipe your device completely!) It will take some time to flash, just be patient and don't worry.
NOTE: If the command window appears for a brief moment then disappears, device drivers may not be installed. Ask again then.
9) Once the command window closes, it should have completed the flashing process and you are safe to press the power key on the phone to start Android. Just make sure that the text near the buttons reads "START".
Sent from my Moto G5 Plus using XDA Labs

Followed your guide this time my device is getting detected and when typed command adb devices its giving some number also but the image you provided is not flashing it.Dont know why please help

Anubhav074 said:
Followed your guide this time my device is getting detected and when typed command adb devices its giving some number also but the image you provided is not flashing it.Dont know why please help
Click to expand...
Click to collapse
You're always talking about ADB commands, it's Fastboot that you have to use, it's described above how you get there.
What image do you mean when you say it's not flashing?
The guide is complete, read it carefully.
You have to download a zip file, in your case the Indian (RETIN) variant:
XT1686_POTTER_RETIN_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unpack it to fastboot folder, use the flashallO.bat to flash the firmware.
Please clarify what image you're talking about and if you do the fastboot flash like described above please provide the recovery.log , you can do that in TWRP->advanced->copy log, if TWRP is installed.
Try to flash the firmware and immediately after that grab a log and attach it here.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
You're always talking about ADB commands, it's Fastboot that you have to use, it's described above how you get there.
What image do you mean when you say it's not flashing?
The guide is complete, read it carefully.
You have to download a zip file, in your case the Indian (RETIN) variant:
XT1686_POTTER_RETIN_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unpack it to fastboot folder, use the flashallO.bat to flash the firmware.
Please clarify what image you're talking about and if you do the fastboot flash like described above please provide the recovery.log, you can do that in TWRP->advanced->copy log, it will be stored in your internal storage.
Try to flash the firmware and immediately after that grab the log (with TWRP file manager) and attach it here.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Sry it's fastboot not adb .But the image i am trying to use is indian(retin) as you provided.And i followed all steps as they were given.
But i dont know how to get log files.
Also i would like to mention that this is my first time trying flashing a phone and as per my knowledge we have to install twrp recovery which i haven't done.its a normal phone with locked oem.
So please guide me how to get log files.

Anubhav074 said:
Sry it's fastboot not adb .But the image i am trying to use is indian(retin) as you provided.And i followed all steps as they were given.
But i dont know how to get log files.
Also i would like to mention that this is my first time trying flashing a phone and as per my knowledge we have to install twrp recovery which i haven't done.its a normal phone with locked oem.
So please guide me how to get log files.
Click to expand...
Click to collapse
You don't need logs. Your phone is locked so you cannot flash twrp. Only thing you can do is flash using fastboot commands. Just download the firmware.. extract. Put all of those files in the adb folder and run the flashall.bat or individual commands like fastboot flash recovery recovery.img which ever you feel is easier for you.

Anubhav074 said:
Sry it's fastboot not adb .But the image i am trying to use is indian(retin) as you provided.And i followed all steps as they were given.
But i dont know how to get log files.
Also i would like to mention that this is my first time trying flashing a phone and as per my knowledge we have to install twrp recovery which i haven't done.its a normal phone with locked oem.
So please guide me how to get log files.
Click to expand...
Click to collapse
debdeep98 said:
You don't need logs. Your phone is locked so you cannot flash twrp. Only thing you can do is flash using fastboot commands. Just download the firmware.. extract. Put all of those files in the adb folder and run the flashall.bat or individual commands like fastboot flash recovery recovery.img which ever you feel is easier for you.
Click to expand...
Click to collapse
That´s what I´ve said. If you would have TWRP you would be able to send a recovery.log but all you want to do is to flash a signed fastboot firmware. That´s possible without TWRP or unlocked bootloader, just by fastboot. Unzip the indian firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
into your Mini ADB & Fastboot folder, place the flashallO.bat there too and double-click it, everything in fastboot mode as described before.
What happens when you do that? Are the commands executed in the command window of your Windows PC?
Can you make a screenshot of it? The guide I posted has everything you need in it, you have to tell me what happens when you try to flash the unzipped firmware.
Just to be clear, the firmware and everything has to be on your PC, not your moble device!

i tried to take screen shot of it but was unable to do it but was successful in copying the complete commands log in text file so here it is
View attachment batch.txt

Anubhav074 said:
i tried to take screen shot of it but was unable to do it but was successful in copying the complete commands log in text file so here it is
Click to expand...
Click to collapse
Ok, that doesn't look to good.
The whole process is failing right at the start when the device is trying to build the partition table.
Have you tried different USB cables and ports?
Imo there are only two possible solutions:
Your device isn't working with fastboot correctly or its a hardware failure, the eMMC (the internal SD) may be corrupted. As your device is locked and hasn't been modded in any way this is the most plausible scenario also because it crashed out of the blue.
The only thing you can try yet is to use a different ADB and Fastboot tool, this one for example:
Minimal ADB & Fastboot:
https://drive.google.com/file/d/10NEzpxKpYWfq-HdK42ctwoEnCg-BfsRQ/view?usp=drivesdk
If all that changing of ports, cables and tools doesn't help you have to bring your device to a service center, they will most probably change the motherboard which isn't a cheap repair so if your device isn't under guarantee anymore you have to consider it it's worth the money.
Good luck!
Sent from my Moto G5 Plus using XDA Labs

So i tried with different fastboot software which you provided but i get the same errors .On phone when these commands run i get these messages failed to validate bootloader image and some thing called piv is also not able to be validated.
So i think its the end of my testing journey. Now can you please tell me how much chances are there for software issue. And is there any thing else i could.Any way i got to learn so many things through this but if is there anything left. Or should i go to service center

Anubhav074 said:
So i tried with different fastboot software which you provided but i get the same errors .On phone when these commands run i get these messages failed to validate bootloader image and some thing called piv is also not able to be validated.
So i think its the end of my testing journey. Now can you please tell me how much chances are there for software issue. And is there any thing else i could.Any way i got to learn so many things through this but if is there anything left. Or should i go to service center
Click to expand...
Click to collapse
I think you've done everything that's possible.
The device wasn't rooted,modded,unlocked or something.
It showed the failure out of the blue.
You tried different fastboot tools, cables, ports and the correct firmware.
I asked someone with more knowledge about your log and the whole case and he is thinking the same as I do.
So the chance for a software problem is really small. I told you everything I know, maybe a service center has more options for software checks but as far as I know they use the good old Lenovo Motorola Software Assistant.
So I would recommend to go there and ask (before they do anything) what you have to pay if your eMMC is broken. Here in Germany they always change the whole motherboard, the costs are about the half of the price you paid for the device here.
If your still under guarantee it's a different story.
I'm sorry, I told you everything I know and I flashed my Moto G5+ several times.
My opinion is that the device has a hardware failure and visiting the service center is the only thing you could do now.
I really would like to give you better news.
Sent from my Moto G5 Plus using XDA Labs

Hi, please help.
I have factory unlocked Moto G5 plus. I never did anyrhing to. All factory.
Recently its stuck in bootloop.
I really want to save all my pictures and texts.
Please help
Thanks

phone crazy said:
Hi, please help.
I have factory unlocked Moto G5 plus. I never did anyrhing to. All factory.
Recently its stuck in bootloop.
I really want to save all my pictures and texts.
Please help
Thanks
Click to expand...
Click to collapse
Read this thread. You can flash signed Motorola firmware like discribed. If you don't want to lose your data you can try to omit the "erase user data" command. Just delete it out of the flashallO.bat.
https://forum.xda-developers.com/g5...ked-stuck-fastboot-mode-t3996599/post80792213
Sent from my Moto G5 Plus using XDA Labs

LG G4 H81520p bootloader unlocked, Download mode avaliable, cant flash anything

Hello everybody. Im asking for help and im pretty desperate for my issue.
I have LG G4 h815 20p which was rooted few years back. Then the phone died and got re-balled recently and it works now. But i can not access twrp by using Volume Down and Power buttons combination. I can go to Download mode where i can updated firmware using LG UP and it will be processed to the end and after the required reboot phone stays black and recognized only as qualcom device in device manager.
I can not use ADB as it will never show any devices under adb device neither fastboot devices. Drivers are installed. Tried bunch of different versions on both win10 and win7 but no luck. I also tried installing those on ubuntu, where the phone is seen as a device under lsusb but not under fastboot or adb.
I just want to get the phone up and running. NO matter if i unroot or keep it rooted. It wont be used as daily phone but im eager to fix it.
The phone lists bootloader unlocked on the top of the screen together with LG logo and then comes the android robot animation for 3-4 seconds then loops the same 2-3 times then goes black screen (shows as qualcom device in device manager).
Tried LG UP, LG flash tool neither helped. LG Flash tool wont even end as LG UP finishes but wont boot after the reboot when process is completed.
Any help please will be extremely highly appreciated. I am also willing to arrange team viewer if necessary for easiness.

sbelcovski said:
Hello everybody. Im asking for help and im pretty desperate for my issue.
I have LG G4 h815 20p which was rooted few years back. Then the phone died and got re-balled recently and it works now. But i can not access twrp by using Volume Down and Power buttons combination. I can go to Download mode where i can updated firmware using LG UP and it will be processed to the end and after the required reboot phone stays black and recognized only as qualcom device in device manager.
I can not use ADB as it will never show any devices under adb device neither fastboot devices. Drivers are installed. Tried bunch of different versions on both win10 and win7 but no luck. I also tried installing those on ubuntu, where the phone is seen as a device under lsusb but not under fastboot or adb.
I just want to get the phone up and running. NO matter if i unroot or keep it rooted. It wont be used as daily phone but im eager to fix it.
The phone lists bootloader unlocked on the top of the screen together with LG logo and then comes the android robot animation for 3-4 seconds then loops the same 2-3 times then goes black screen (shows as qualcom device in device manager).
Tried LG UP, LG flash tool neither helped. LG Flash tool wont even end as LG UP finishes but wont boot after the reboot when process is completed.
Any help please will be extremely highly appreciated. I am also willing to arrange team viewer if necessary for easiness.
Click to expand...
Click to collapse
Boot to fastboot and exec
fastboot format userdata
(will obviously erase the whole device including photos etc)
If that does not help you can use SALT to flash TWRP to the BOOT (!) partition. For that you must start SALT from the cli with --experimental argument. If you plan to use SALT I recommend using the latest mAid njghtly which has all already installed.
For flashing with SALT you also must do a custom backup of the sbl1 partition and place the twrp image in the same dir where the sbl1 backup is.
Sent from my OnePlus 7T Pro using XDA Labs

steadfasterX said:
Boot to fastboot and exec
fastboot format userdata
(will obviously erase the whole device including photos etc)
If that does not help you can use SALT to flash TWRP to the BOOT (!) partition. For that you must start SALT from the cli with --experimental argument. If you plan to use SALT I recommend using the latest mAid njghtly which has all already installed.
For flashing with SALT you also must do a custom backup of the sbl1 partition and place the twrp image in the same dir where the sbl1 backup is.
Sent from my OnePlus 7T Pro using XDA Labs
Click to expand...
Click to collapse
Hey, Thank you.
I found your stuff uploaded, but i really cant figure it out. Whenever i press Volume UP and Power button to keep them 6-7sec then plug usb cable, the phone misses the chance to go into download mode. So i have no opportunity to go into fastboot. But i can go in download mode but neither fastboot or salt finds the device.
Could you please provide some more info?

sbelcovski said:
Hey, Thank you.
I found your stuff uploaded, but i really cant figure it out. Whenever i press Volume UP and Power button to keep them 6-7sec then plug usb cable, the phone misses the chance to go into download mode. So i have no opportunity to go into fastboot. But i can go in download mode but neither fastboot or salt finds the device.
Could you please provide some more info?
Click to expand...
Click to collapse
fastboot and download mode are complete different things. you cannot use fastboot commands in download mode.
you have to provide more info:
how do you run mAid? VirtualBox or from an USB stick (recommended)
share the debug log of SALT when your device is in download mode (Advanced menu -> debug log -> upload button -> share just the link)
boot your device in download mode and THEN start mAid first could also help
.-

steadfasterX said:
fastboot and download mode are complete different things. you cannot use fastboot commands in download mode.
you have to provide more info:
how do you run mAid? VirtualBox or from an USB stick (recommended)
share the debug log of SALT when your device is in download mode (Advanced menu -> debug log -> upload button -> share just the link)
boot your device in download mode and THEN start mAid first could also help
.-
Click to expand...
Click to collapse
Hello again.
I figured mAid out. I run from live usb, and i can connect to phone and get the device information through Salt..
What i did:
- i use experimental flag with root privileges and device is read and comes info that my Laf fw does not support direct flashing. (i cant figure it out how this works),
- i made backup of sbl1 partition, downloaded twrp image twrp-3.3.1-PREVIEW-196_g4_MM.img, placed the twrp image in same folder where the backup of sbl1 is.
- Now i dont know how to flash the the twrp to the boot partition. I tried to find some guides but no luck. Yesterday for some reason i had Flash button in salt on the bottom, today it is not there. The way i start salt is by browsing inside /home/android/Desktop/LG directory and use sudo ./SALT.desktop --experimental command. I use the latest mAid from your file server 4.19.126-1-MANJARO - mAid_v2020-07-14_23-43_x86_64_forgetful.iso.
3 attachments are uploaded bellow. The debug log from salt was unable to upload and gave bunch of package errors, so it is attached bellow in a txt file as well.
The phone keeps stable connection in download mode.
Please advice. I am very grateful.

sbelcovski said:
Hello again.
I figured mAid out. I run from live usb, and i can connect to phone and get the device information through Salt..
What i did:
- i use experimental flag with root privileges and device is read and comes info that my Laf fw does not support direct flashing. (i cant figure it out how this works),
- i made backup of sbl1 partition, downloaded twrp image twrp-3.3.1-PREVIEW-196_g4_MM.img, placed the twrp image in same folder where the backup of sbl1 is.
- Now i dont know how to flash the the twrp to the boot partition. I tried to find some guides but no luck. Yesterday for some reason i had Flash button in salt on the bottom, today it is not there. The way i start salt is by browsing inside /home/android/Desktop/LG directory and use sudo ./SALT.desktop --experimental command. I use the latest mAid from your file server 4.19.126-1-MANJARO - mAid_v2020-07-14_23-43_x86_64_forgetful.iso.
3 attachments are uploaded bellow. The debug log from salt was unable to upload and gave bunch of package errors, so it is attached bellow in a txt file as well.
The phone keeps stable connection in download mode.
Please advice. I am very grateful.
Click to expand...
Click to collapse
you start SALT in experimental mode as this in a terminal:
Code:
~/programs/SALT/salt --experimental
anyways the problem is that your LAF version is 100004 so flashing will likely not be possible.. You can try it anyways by using the above cmd which will bring up the flash buttons.
before doing that rename the twrp image to recovery.img to ease up things.
then you select flash (folder) and ensure that anything else then the recovery image is selected (e.g. do not flash sbl1 etc).
also ensure that the target partition is named "recovery" then choose flash.
as said it will likely not work though as your download mode (LAF) is too new though. you could downgrade with LGup to Lollipop which will allow flashing with SALT for sure.
but back to the initial description, you mentioned that:
[...] after the required reboot phone stays black and recognized only as qualcom device in device manager.
[...]The phone lists bootloader unlocked on the top of the screen together with LG logo and then comes the android robot animation for 3-4 seconds then loops the same 2-3 times then goes black screen (shows as qualcom device in device manager).
These indicates very very likely the beginning of the ILAPO. you can check my signature for some workarounds though there is no proper way to fix it other then by replacing the mainboard.
.-