ZTE Blace V220 / Avea Intouch 4 [root success] - Blade General

[edit]: Succesful root thanks to @mseskir advice [edit]
Hello everyone.
I just replaced my old Samsung Galaxy S3 Mini (i8190) by a new ZTE Blade V220 (nifty hardware at nifty price, EURO 140, WOOT).
I chose it because I didn't want to make a great spent, only to find out that there is no development on this model and that it doesn't even appear on ZTE webpage, so I can't "root" it or change the recovery.
As per Mseskir, this phone is the same than "Avea Intouch 4", a phone sold by a turkish brand.
Below are the hardware details:
- Qualcomm MSM8916 quad core 1'2 Ghz
- 800/900/1800/2100/2600 Mhz CAT 4
- 5" IPS screen (1280 x 720), looks nicer than the super AMOLED S3 mini screen
- 1 Gb RAM + 8 Gb storage (2 gb already spent for OS, even though it brings no bloatware at all)
- Bluetooth 4.0, GPS, WIFI, SD card slot
- 13 Mpx back camera with autofocus, and 5 mpx front camera (not top-notch quality, but good enough for me)
- 2100 mAh battery
- 139 x 71,5 x 9,5 mm (the back is too curvy for most hard covers ).
- Android KITKAT 4.4.4
ROOT steps:
A) I had to use the ZTE ADB drivers bundled with the phone (just mount USB in "driver mode" option
and run the bundled exe in your mobile storage).
The drivers will be installed in "C:\Program Files\ZTE_Handset_USB_Driver". Remember this directory.
B) Download "Root-SuperSU-v2.37.zip" from file from mseskir's yandex drive, within the "root"
folder. You can find the link in his post below. Upload without unzipping to your mobile internal memory.
You will need it later.
C) Download the "IT4_Recovery_Yukleme_Programı.exe" file from mseskir's yandex drive, within the "root"
folder. You can find the link in his post below.
D) Unzip "IT4_Recovery_Yukleme_Programı.exe" and get "recovery.img" (recover with TWRP) or
"recovery_stock.img" (if you prefer stock recovery) from the "tools" folder.
I will use "recovery.img" because I have been using TWRP since my old Xperia Neo V.
Copy the your "recovery.img" of choice to the folder where the USB ADB drivers was installed.
Copy the "fastboot.exe" file there too.
E) Enable "USB ADB debug" in android "Developer Options". Ensure that Windows detects and installs
the drivers properly.
F) Open command prompt and go to "C:\Program Files\ZTE_Handset_USB_Driver"
G) Type "adb devices", if everything goes well you will see your phone serial number listed
there. If you receive some error while starting the daemon, ensure that no other ADB app
is running in the background or try another ADB drivers.
You can check your phone serial number in the mobile itself: Phone Information --> Status
H) Type "adb reboot bootloader" in command prompt. The phone will reboot and will get stuck in boot image
with the notification led in red (scary, but don't worry, it's all fine).
I) Type "fastboot devices" in command prompt. You will see again the phone serial number in the window.
The phone screen will remain unchanged, like if it where frozen, but don't worry, everything is still fine.
J) Ensure that you have copied "recovery.img" in the same folder than adb.exe and fastboot.exe
( "C:\Program Files\ZTE_Handset_USB_Driver", as I mentioned earlier).
Then, type "fastboot flash recovery recovery.img". If you copied the "recovery.img" and the "fastboot.exe"
to the driver folder you will see the flash progress. It will take one or two seconds and give you an "ok" message.
K) Type "fastboot reboot" and the mobile will reboot. Let it boot till the end. Disconect USB cable and
shutdown the mobile completely.
L) Push and maintain "volume up". While you maintain "volume up", push "power" button a few seconds
to start the mobile. Keep maintaining "volume up" until TWRP boot screen appears.
M) Flash "Root-SuperSU-v2.37.zip" with TWRP. You should have already copied it to mobile storage if you followed my advice in point "B". Reboot to system and it's done.
I leave this here so if anyone searches for this phone like me, he will know how to succesfully root it.
Thanks to everyone in advance.

Root
Hi, your phone is same like my phone "avea intouch 4" this is my files link
https://yadi.sk/d/8GHocBtnfTp7A
Go to root folder, download the IT4_recovery_yukleme_programi.exe
Run it, turn usb debugging on in your phones devoloper options then connect your phone select twrp recovery yukleme in the programs menu, a message will pop up on your phone, select "ok" then it will reboot to bootloader and flash twrp recovery to device. After reboot open the twrp recovery and firstly backup your device to sdcard1 and copy it to your pc then install supersu package from my root folder. Thats all.
But first you must install drivers.
If anything goes wrong i will help you as i can.
If you cant use the program (its language is Turkish) i will make an english program tomorrow.
---------- Post added at 04:02 PM ---------- Previous post was at 03:48 PM ----------
Our Turkish forum link is
http://mobile.donanimhaber.com/showTopic.asp?m=100770257&p=1
We are trying to port roms. And i'm using a custom rom right now.

mseskir said:
Hi, your phone is same like my phone "avea intouch 4" this is my files link
Go to root folder, download the IT4_recovery_yukleme_programi.exe
.... /QUOTE]
Thanks @mseskir, I have tried it without luck.
When using option 2, I receive "sonraki asamaya gecmiyorsa suruculeri tekrar yukleyiniz" which means
something like "Your driver does not pass to the next stage reload".
So I uninstalled the ADB drivers that came bundled within the phone storage, and installed the ones on your link,
but still the same even after reboot and complete clean.
Any suggestion?.
Click to expand...
Click to collapse

Ok. Can you try this;
open my exe file with 7zip and extract
open tools folder
click right mouse button with shift (from keyboard) pressed
select open command prompt here
in command prompt;
type adb device
on your phone screen a warning will pop up, select ok
then you will see your phones serial number in cmd window
then type;
adb reboot bootloader
your phone will reboot to bootloader,
type;
fastboot devices
if you cant see serial number; go to my yandex folder, in tools folder; AdbDriverInstaller.exe download it and run it. it will install the fastboot drivers
then type "fastboot devices" again, if you can see your serial number type;
fastboot flash recovery recovery.img
then type "fastboot reboot"
if you dont want twrp recovery you can use cwm recovery, it is inside my root folder IT4_Root_Anlatımı.zip (extract it, there is cwm recovery)
if something goes wrong tell me..

mseskir said:
Ok. Can you try this;
open my exe file with 7zip and extract...
Click to expand...
Click to collapse
I got TWRP (i'm used to it) working and root by working following your instructions, thank you very much.
But I have had to use my own adb files taken from zte drivers installer (bundled with the mobile)
as replacement from the ones bundled in your zip file, which always errored out for me when trying
to start the service.
The only scary moment was when I issued "adb reboot bootloader" and the mobile got stuck on ZTE boot image. I was waiting for a while for bootloader to appear, but it didn't happen, so I proceed with next step.
When I have some time tomorrow or weekend, I will update the first post for the proper steps to attain root.

helpful thanks

lollipop update
avea intouch4 original 5.0 update files
http://www.avea.com.tr/web/android5update/update.zip
How to update zte blade v220 Download update zip that link. And move sdcard then settings-Phone information-System updates and press OK
It shows recovery wait here.
Later Phone will start and 'll boot 5.0.2

I would advice to avoid updating the phone to V5.0.2 with the update file because of the following:
A) You will lose your existing root. You will have to root again Use http://www.kingroot.net/ for easy and clean root.
B) You will have trouble connecting to previously working WLAN networks (I'm suffering it right now, lots of people complaining about this, just click here "https://www.google.es/webhp?sourcei...8#q=android 5.0.2 wifi authentication problem" to see what I mean). Using "Wifi Fixer" app it sometimes works well, sometimes it disconnects itself, I need to check further.
C) Only English, German, French and Turkish languages are available in the update. Although I miss the Spanish language, I could live with english. Partly fixed with "Set Locale and Language" app from Google Play
D) I'm still trying to figure out how to flash TWRP to restore my 4.4.4 backup.
E) Fastboot support with 5.0.2 is crimpled so I can't use it to reflash TWRP. I can't seem to find a valid TWRP version to flash with "TWRP manager" either.
F) Don't know if it's a bug or not, but screen switches on and off when idle and locked without any reason that I can find. It bothers me a lot!.
G) Just discovered that this update also locks bootloader. That's the reason I can't flash recovery.img back.
Be warned.

I give up with this!
Well, after a few days trying different solutions to install a TWRP recovery to recover my stock backup, I have messed it up to the point that I'm now stuck in the following status:
The phone gets stuck in bootloop with Avea logo. It heats up a lot but doesn't boot no matter how long you wait.
Before messing it up, I managed to install Phil6 recovery version 6.57.9 (I still can access it with VOL+ and power button).
This Phil6 version I got seems to be compiled for "sprout" hardware, so it will always error up when trying to flash roms for msm8916 hardware.
Any other roms I try to flash that don't error up with sprout message will always fail with "error: 0". I have tested a few roms with two different SD cards, so it's not a badly downloaded rom.
Restoring my TWRP backup with Phil6 doesn't error out, but the phone still doesn't pass the avea logo.
I first went for a 6" Sony Xperia C5 Ultra, but the main camera quality was terrible and it heated up a lot, enough to unglue the screen protector.
So I returned it to the shop and picked a Huawei Ascend P8.
Much better hardware than V220, much better still camera, slightly worse video recording quality (IMHO), and twice as expensive as the V220, but it really flies compared to the V220, gentlemen.
Thanks everyone.

Thanks to @ozgurharan's rom, I have been able to bring back to life my ZTE Blade V220.
This is his rom's link, I got his permission to post it here: https://yadi.sk/d/uv3bhb0knX8nn
Too bad that I still can't restore my TWRP backup or the original KitKat rom with spanish language, but something is better than nothing.
Be warned that this rom has only English, French, Turkish and Deutsch languages.
Thanks a lot @ozgurharan

Hello. I have already upgraded my Avea In Touch 4 to 5.0.2 before reading this post. Now I cannot root my phone. I have followed every step on this post but in bootloader mod when I try fastboot flash recovery the recovery.img I get an error like "writing recovery... failed (remote: unknown command). I tried to install the last rom you have shared but still not working. I just want to root my phone and have the last version of stock rom for my phone if avaliable. Can you please help me?:crying::crying::crying:

TheSuburban said:
Hello. I have already upgraded my Avea In Touch 4 to 5.0.2 before reading this post. Now I cannot root my phone. I have followed every step on this post but in bootloader mod when I try fastboot flash recovery the recovery.img I get an error like "writing recovery... failed (remote: unknown command). I tried to install the last rom you have shared but still not working. I just want to root my phone and have the last version of stock rom for my phone if avaliable. Can you please help me?:crying::crying::crying:
Click to expand...
Click to collapse
Use kingroot. It worked for me.

@mseskir, do you happen to still have the previous TWRP version for Avea Intouch 4 (I think it was 2.7.0.3 or around it)?.
I have flashed your current TWRP 2.8.6.1 to root the phone but this version can't mount SD card, so I can't flash zip files from SD card.
The File Explorer shows SD card as 0 Mb, but if I boot the phone SD card is recogniced and will work well.
Or if you have a newer version than 2.8.6.1 that doesn't fail to mount SD card will be fine too.
NOTE: Long story short with my previous struggles with Blade V220 and horrible Android 5.0.2 update. Doing some tests I did a very bad flash and f##ked the phone completely,
so I had to send it to ZTE tech support. The phone was still on warranty so they replaced the phone PCB with a new one that has Android 4.4.4.
Thanks in advance.

Related

[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

[REF] [ROOT] [RECOVERY] [BOOT LOADER] Metro PCS LG K7 LGMS330 [Guide For Dummies]

I have not been on this site since posting my guide, i do want to let any future people reading this know that, I am not a professional. everything in this guide is using stuff from other peoples threads.... this thread is just step by step directions on how i rooted (and installed TWRP on) MY lg k7 (MetroPCs). Also i had to root before i unlocked the boot loader. Which is not safe, you should probably unlock the boot loader before you root, but i couldn't figure out how to unlock it without root access.
I AM NOT RESPONSIBLE FOR ANY THING THAT HAPPENS TO YOUR DEVICE!
YOU AND ONLY YOU CAN BE HELD RESPONSIBLE​
~BACK UP FILES ON PC, YOUR PHONE WILL BE RESET TO FACTORY SETTINGS DURING THIS TUTORIAL~
Step One: Enable Dev Options
A) open settings>about phone>software info then tap "Build Number" really fast about 10 times
B) open settings>Developer Options, then check the box labeled "Enable OEM Unlock", and the box Labeled "USB Debugging"
Step Two: Install Android SDK/ADB/USB drivers
A) go to http://developer.android.com/sdk/index.html in your browser, and click download...
B) go to https://www.microsoft.com/net/default.aspx in your browser, and click the big blue button that says .NET
Framework 4.6.1 or X.X.X depending on when your reading this...
C) go to http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html scroll down until you get to the first box, labeled Java SE Development Kit 8u91 or XuXX Depending on when your reading this, then find your OS (ex: Windows x86, Mac OS, Linux, Etc..), then select the download link
Step Three: Installing LG K7's USB Driver's
A) unlock your phone
B) plug your phone into you Computer via USB
C) pull down your notifications, Tap on the USB icon which should be labeled "Media Device (MTP)," "Send Images (PTP)," or "Charge Phone"
D) if a dialogue box pops up asking to install drivers tap install, if not proceed to step E
1) Your PC should ask you if you want to auto run, Either auto run or open the folder and run LG_PC_Programs.exe then proceed to Step Four
E) select "Media Device (PTP)," if not already selected
1) click the three vertical dots next to the magnify glass in the upper right hand corner, select install pc drivers, then tap install
Step Four: Installing Java SE
A) return to the folder where you downloaded the files in step two, install the file which contains the word java in it
Step Five: Installing Microsoft .NET 4 Framework
A) now in the same folder as step four, install the with the name "NDP461-KB3102438-Web," the name might be different then mine depending on when you are reading this
B) if it is already installed it will notify you and you can proceed to the next step
Step Six: Installing Android Studio 2.0 (SDK/ADB Drivers)
A) in the download folder from step four & five, double click the remaining file, the name should contain the words "android", and "studio" in it
B) when the dialogue box opens requesting admin rights, select allow
C) click next
D) click next
E) make sure all boxes are checked and click next
F) read the license agreement, (unless your the 99.9% that doesn't) click i agree
G) you may click next or choose where you'd like to install android studio, and where you'd like to install SDK, for this tutorial i will change make a new folder in my docs named SDK then change the SDK install dir to My Docs
H) click next
I) it will take a moment to install so just wait
(note: the progress bar will fill up, then reset, as it is installing in two separate locations)
J) when finished, click next
K) uncheck the box and click finish
Step Seven: Root your device
(Note: I rooted before i unlocked my boat loader, as i could not get it to boot into boot loader mode until i rooted it)
A) go to http://www.kingroot.net/wap on your android device and download the apk file
B) go to settings>security and check the box labeled "Unknown Sources"
C) install the apk
Video tutorial for king root here: https://www.youtube.com/watch?v=tG_ruuTPVpU
(Not my channel or video)
D) open the king root app
E) make sure you have a charged battery or your phone is plugged in as the rooting process time may vary (better safe then sorry)
F) swipe up until you see a "TRY IT" button click it
G) under "Root Access not available" tap "Get Now
H) do not turn off your phone
I) when it is done you can tap optimize now if you wish, otherwise close the app
Step Eight: Replacing KingRoot with SuperSU ~ W0lfDroid Method
A) go to http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
B) scroll down until you see the word "download:" (should be right above the related posts
C) click on the "new link" next to "Replace_Kingroot_With_SuperSU.zip"
D) extract the .zip so that the "MRW" folder is on your internal storage
(Easiest way is to download it on PC and open up your k7 in "my computer" and select internal storage and drag the MRW folder inside the .zip there)
E) go to google play and search "terminal emulator for android" or use this link if your reading this on your phone https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
F) install the first one, or use this link if your reading this on your phone https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
G) open terminal emulator
H) type "su" without the quotations
(everything typed in the terminal is case sensative)
I) type "sh /sdcard/mrw/root.sh" without the quotations
J) you might see a few errors, that is fine
K) wait until it says finished
L) when SU opens, select "update" "install" or what ever pops up
M) when it asks to uninstall, uninstall it, it is not uninstalling SuperSU it is uninstalling Kingroot,
O) if 30 minutes pass and it is still uninstalling then exit the app and then reboot the phone
DO NOT STOP HERE ~ YOU HAVE TO UNLOCK THE BOOTLOADER, and OPTIONALLY FLASH TWRP
Step Nine: Unlocking The Bootloader
A) refer to step one and double check the OEM unlock is enabled and USB debugging is turned on
(If not then please enable them)
B) search quick boot on the google play store download the first app it should be a circle with a lightening bolt
C) open quick boot
D) when asked to "allow root access?" tap allow
E) if an add pops up close it with the ex in one of the corners
F) tap on the word boot loader
G) at the top of your phone you should see " * Welcome To Fast Boot Mode : "
H) now go to your SDK dir, in my case it is C:\Users\USER\Documents\SDK
I) hold shift, then right click on the "platform-tools" folder, then select "open command window here"
J) in the CMD window type "fastboot devices" - without quotations
(everything is case sensative)
K) then type "fastboot oem unlock" - without quotations
L) then type "fastboot getvar unlocked" if that doesn't work try "fastboot getvar" or "fastboot getvar unlock" to confirm if it is unlocked
(if non of the getvar commands work you did something wrong, and i wont be able to help you, but if you followed the tutorial you shouldn't have any issues as these are the exact steps i took)
M) then type "fastboot reboot"
LEAVE THE CMD OPEN OR YOU WILL HAVE TO REPEAT steps H-I
Step Ten: Flashing TWRP
A) go to http://forum.xda-developers.com/general/general/qa-metro-pcs-lg-k7-lgms330-t3331678 and click on the latest download for twrp for me it is BETA1
if the links on that page dont work then use the links here http://forum.xda-developers.com/showpost.php?p=66282525&postcount=42
B) extract the download into your SDK folder on your PC
C) in the sdk CMD window from Step nine
D) type "fastboot devices" - without qoutation
E) ~optional, HIGHLY RECOMENDED~
1)type fastboot "boot twrp-image-3.img" - this will boot up twrp WITHOUT flashing it, just so you can make sure everything is working right
in my case it was twrp-image-3.img check your twrp file name and replace fastboot boot twrp-image-3.img with
fastboot boot INSERT YOUR FILE NAME HERE.img
2)in twrp tap reboot>bootloader
F) when bootloader mode opens back up
G) type "fastboot flash twrp-image-3.img" or "fastboot boot INSERT FILE NAME HERE.img" depending on your file name
H) when finished flashing type "fastboot reboot"
Step eleven
A) follow instructions on step one
B) the reason you must do this is because when you flash TWRP it erases your entire phone and resets it
Congrats you have Successfully Rooted, Unlocked Your Bootloader, and Flashed TWRP, to your LG K7
Well done, my friend. Well done indeed.
[QUOTE
Congrats you have Successfully Rooted, Unlocked Your Bootloader, and Flashed TWRP, to your LG K7[/QUOTE]
is this ok with the gapps 5.1 instsall .zip for twrp install or should i use a different? also, do you have a suggested camera app? awesome thread btw. Nevermind simple twrp install fixed everything.
I have tribute 5 and can't access bootloader or install SuperSU.....always fails.
How can I get this to work?
Today backup important files you need!
Is this a real method BC everybody having problems rooting this device so I ask can u make a video and add screenshots
Sent from my LG-D800 using Tapatalk
I can confirm this method works. The only different thing i did was purchase Supersume pro from playstore. Worked like it said it would. The Ls675 is rootable. But no bootloader unlock or bootloader at all for that matter. Im running MS330 with TWRP full root and have twrp backups and fastboot flashable backups via flashfire....
---------- Post added at 02:28 AM ---------- Previous post was at 02:20 AM ----------
https://mega.nz/#!CRAVWAyI!QIbo20-0ZnVqlREs7ZXF66aB_Eh3UjCEMVQbLuP1Zec
https://mega.nz/#!zBoxGIQR!buXvorPkA14Vr2Idn7uhNPHanOL6wbvcEav3MhRdjv8
https://mega.nz/#!yQBg1ayC!r3qvWfLjCAKg0e8t91J1IEtae8_EwhvYTXjawv7b_2A
Screen shots of root, flashfire backups, and device info
While it does work I can find no method using the buttons to get into twrp all the instructions I find for recovery fail so I can only boot back to it after the phone boots, thus it's worthless at this point. Also the command is fastboot flash recovery imgagename.img and you'll need to remove kingroot from administrators to uninstall.
Anyone else been able to boot directly into twrp from the off position?
zgauthier8286 said:
I can confirm this method works. The only different thing i did was purchase Supersume pro from playstore. Worked like it said it would. The Ls675 is rootable. But no bootloader unlock or bootloader at all for that matter. Im running MS330 with TWRP full root and have twrp backups and fastboot flashable backups via flashfire....
---------- Post added at 02:28 AM ---------- Previous post was at 02:20 AM ----------
https://mega.nz/#!CRAVWAyI!QIbo20-0ZnVqlREs7ZXF66aB_Eh3UjCEMVQbLuP1Zec
https://mega.nz/#!zBoxGIQR!buXvorPkA14Vr2Idn7uhNPHanOL6wbvcEav3MhRdjv8
https://mega.nz/#!yQBg1ayC!r3qvWfLjCAKg0e8t91J1IEtae8_EwhvYTXjawv7b_2A
Screen shots of root, flashfire backups, and device info
Click to expand...
Click to collapse
can you please help me i have 2 MS330 that are bricked
callihn said:
While it does work I can find no method using the buttons to get into twrp all the instructions I find for recovery fail so I can only boot back to it after the phone boots, thus it's worthless at this point. Also the command is fastboot flash recovery imgagename.img and you'll need to remove kingroot from administrators to uninstall.
Anyone else been able to boot directly into twrp from the off position?
Click to expand...
Click to collapse
Try to do the factory hard reset trick but say no at the second screen. I haven't tried it out yet but I've been reading around several sites and that's a possible solution
zgauthier8286 said:
Try to do the factory hard reset trick but say no at the second screen. I haven't tried it out yet but I've been reading around several sites and that's a possible solution
Click to expand...
Click to collapse
Just reboots. Think we're going to have to change something? Boot image? Kernel?
callihn said:
Just reboots. Think we're going to have to change something? Boot image? Kernel?
Click to expand...
Click to collapse
I'm no developer by any means but I have Linux and windows on my laptop. I'm familiar with kernel building on bunt and have the source code for MS330 on my laptop. I have a backup of my boot img as well. If you can get to fastboot u can probably flash my boot img if you want me to send it. I have recovery img as well which is twrp. Let me know if you have any ideas on what u need or i can do as far as possibly doing a fresh build kernel later tonight and getting a zImage out of it
Does anyone know a way to successfully root this phone? Not just recover?
Sent from my LGMS330 using Tapatalk
callihn said:
Just reboots. Think we're going to have to change something? Boot image? Kernel?
Click to expand...
Click to collapse
Of other interest 5.1 is very dendent on Google apps and move app updates to the system via TB or Link2SD fails more than it succeeds, shows they moved but app inaccessible afterwards hence brick. Mine went down trying to integrate play services and reinstalling from adb didn't help. FYI if you relock the BL it'll lock the phone with a security error too. Moving play services causes unending error screens so you can't really see if it's done moving, but I waited a good 5 minutes before reboot. Issue on fails could have been the system not being r/w. Needless to say backup, backup, backup as I hadn't because I've never had a serious issue doing that and considered it a trivial task. Anyone had good success with integrating updates and cache? Anyone restored from twrp yet?
JayCouture.com said:
Does anyone know a way to successfully root this phone? Not just recover?
Sent from my LGMS330 using Tapatalk
Click to expand...
Click to collapse
Yes! Just follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=66456635&postcount=1
zgauthier8286 said:
I'm no developer by any means but I have Linux and windows on my laptop. I'm familiar with kernel building on bunt and have the source code for MS330 on my laptop. I have a backup of my boot img as well. If you can get to fastboot u can probably flash my boot img if you want me to send it. I have recovery img as well which is twrp. Let me know if you have any ideas on what u need or i can do as far as possibly doing a fresh build kernel later tonight and getting a zImage out of it
Click to expand...
Click to collapse
Can you figure out why we can't boot to recovery via hardware buttons? That's critical for tinkering and testing on the go since I always have my phone but not my laptop for booting into recovery with adb. Not sure exactly where to look, probably start with a search for the words "recovery" and "safe mode" for the buttons and "security error" in the boot.img files.
callihn said:
Can you figure out why we can't boot to recovery via hardware buttons? That's critical for tinkering and testing on the go since I always have my phone but not my laptop for booting into recovery with adb. Not sure exactly where to look, probably start with a search for the words "recovery" and "safe mode" for the buttons and "security error" in the boot.img files.
Click to expand...
Click to collapse
If your rooted u can dl a reboot recovery app on the play store I have one that works like a charm. But im gonna take a look through Linux at the kernel options using make menu_config and see if there's anything I can see in there.
zgauthier8286 said:
I'm no developer by any means but I have Linux and windows on my laptop. I'm familiar with kernel building on bunt and have the source code for MS330 on my laptop. I have a backup of my boot img as well. If you can get to fastboot u can probably flash my boot img if you want me to send it. I have recovery img as well which is twrp. Let me know if you have any ideas on what u need or i can do as far as possibly doing a fresh build kernel later tonight and getting a zImage out of it
Click to expand...
Click to collapse
im having a problem w the security 9 error boot loop. only seem to b able to get it into download mode , not bootloader or recovery. would your boot and recovery img's help me at all ya think ? thanks !
goitalone said:
I have tribute 5 and can't access bootloader or install SuperSU.....always fails.
How can I get this to work?
Click to expand...
Click to collapse
Thanks again. For anyone that has a soft bricked LG K7 see this man! He brought my S#!? To life through teamveiwer. Thanks again. From my LG K7.
Maybe just my experience, but regarding step 10. I had to have the twrp image in SDK>platform tools, also when you get to fastboot flash twrp-image-3.img, I couldn't get it to work, until I typed it as fastboot flash recovery twrp-image-3.img. Hope this helps anyone else getting errors during this part. Thanks for the writeup.

Doogee X5 Max Pro Root Recovery OTA

******************Root Recovery Doogee X5 max pro*******************
Your waiting Time IS Now Finished Here is Complete Guide to Root Doogee X5 Max Pro install twrp And More,
Hit :good:
ADB & Fastboot
Before doing most things mentioned below you will need "adb" and "fastboot" installed. Two of your options are to install the Android SDK Tools or the Minimal ADB and Fastboot tool. If you are somewhat new to this I highly recommend the second one. Go here, download the latest version (1.3.1 as of this writing), and install it. When setup is complete you should have an icon for the Minimal ADB and Fastboot tool.
Note: I highly recommend you add "C:\Program Files (x86)\Minimal ADB and Fastboot" to your PATH variable in Windows. This way you can open a Command Prompt anywhere and use adb or fastboot.
1) Unlock Bootloader
Power on the phone and skip through all of the setup options
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
Type fastboot oem unlock
Press Volume Up to say Yes and wait for this to finish
Type fastboot getvar all and look for (bootloader) unlocked: yes
Type fastboot reboot
You should see your phone reboot a couple times as it erases the phone
Install twrp-
Power on the phone
You can configure your phone now or just skip through all of the setup options and do that later
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt to wherever you extracted the .img file
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly, rename twrp to recovery.img
type fastboot flash recovery recovery.img to flash recovery
Type fastboot reboot
Rooting-
Download BETA-SuperSU.zip and save it to the phone's internal memory or an inserted microSD card
Plug the phone in to your PC
Open a Command Prompt
Type adb reboot recovery
You should now be in twrp. Go to Install zip, find SuperSU.zip, and install it
When it finishes go to Go Back -> Reboot Phone -> No
Once the phone boots up launch SuperSU and configure it as you like
Other Solutions-
i have doogee x5 max-s (i geuss limited editon in algeria ) with mtk6735 . i do evrything and all steps but when i reboot to recovery mode i have ( no command ) in the screen .... how to fix that ? sorry for my ****ty english XD
I had the same Issue but i have found a solution!
After you have flashed the twrp recovery, dont reboot the phone! the "recovery.sh" will replace the twrp on every boot!
Just pull off the battery after flashing, disconnect usb and put the battery back in to the phone.
Now get in to the recovery by pressing volume up and power button together until the select bootmode menue appears.
select recovery with the volume up button and enter with the volume down button.
and now you should be in the twrp main menue.
i hope it works for you too!
greetz from the lizard
It does not work from step 12, all the drives are correctly installed and windows recognizes the cell, the recovery image is in the internal memory and also in the sd but of the error "can not load Recovery.img". I tried all the tutorials on the net to do root and nothing worked.The flash does not recognize to pass the recovery also the installed drivers because windows recognizes the cell phone.
pitro1 said:
It does not work from step 12, all the drives are correctly installed and windows recognizes the cell, the recovery image is in the internal memory and also in the sd but of the error "can not load Recovery.img". I tried all the tutorials on the net to do root and nothing worked.The flash does not recognize to pass the recovery also the installed drivers because windows recognizes the cell phone.
Click to expand...
Click to collapse
use sp flash tools to flash recovery, scatter also added with twrp
Flash does not pass the file in the download only option, the process does not start. I reinstalled ROM by firmware mode all ok, but the process of passing recovery on command 12 and 13 of the error message. I manually copied the recovery to the sd and internal memory but also from the error. Does not find the file speaks that it is not a command found.
pitro1 said:
It does not work from step 12, "can not load Recovery.img".
Click to expand...
Click to collapse
Don't use Capital R's
fastboot flash Recovery Recovery.img
Code:
fastboot flash recovery recovery.img
Doogee X5 Max Pro - Update 01/16/2017 + TWRP-3-0-2 & SuperSU-v2.79
Working root for Update 01/16/2017
Title: Doogee X5 Max Pro
Listed: 01/19/2017 11:21 pm
ROM Version: ROM Android 6.0
Doogee X5 Max Pro - Update 01/16/2017
TWRP-3-0-2 + SuperSU-v2.79
Use This Version Flashtool
SP_Flash_Tool_v5.1620.00.000
XN Logos said:
use sp flash tools to flash recovery, scatter also added with twrp
Click to expand...
Click to collapse
Until today I could not do root on x5 max pro. In the method below even downloading the twrp when starting with the power + volume down button start with a menu in Chinese and if you start with volume up + power goes in the default recovery mode.
Same as Pitro1 I am on 16.01 update and I cannot install twrp no matter what I try.
I tried x32 and x64. I tried rebooting directly on recovery or first load system and then adb reboot recovery. I tried to format all first (now I lost my Imei and so on lol). I downgraded and updated again. Downgrading works only with 26.12 version. All others are giving me Colorado lines on the screen and nothing else...
OEM unlock, file transfer, adb, fastboot, drivers detection, are all working good. Only I cannot install twrp...
Also I cannot write nvram nor with SN Writer 2.1504 nor with Imei & SN Writer 1.7.2, MetaAP mode fails all the time...
I'm just about to send it back...
How i rooted my Doogee X5 Max Pro
How i rooted my Doogee X5 Max Pro
- Unlock Bootloader tutorial in the first post By XN Logos.
- Updated ROM to Android 6 with SP FLASH TOOLS V.5.16.20
- boot phone for 1st start and activate Developer and USB debugging
- Installed TWRP-32x + SuperSu with SP FLASH TOOLS V.5.16.20
i returned the phone as i had no imei anymore.
i got a new one, i did not put any sim or whatsoever, i just unlocked bootloader, and updated to 16.01 version
then i tried to install twrp via fastboot and it did not work, i did it with sp flash tools as advised and removing the battery prior (don't forget to!). it worked !
Stripe_nl said:
How i rooted my Doogee X5 Max Pro
- Unlock Bootloader tutorial in the first post By XN Logos.
- Updated ROM to Android 6 with SP FLASH TOOLS V.5.16.20
- boot phone for 1st start and activate Developer and USB debugging
- Installed TWRP-32x + SuperSu with SP FLASH TOOLS V.5.16.20
Click to expand...
Click to collapse
How old is your phone and what build version was it at before you started? Because this doesn't work on mine. Which of the "Android 6" ROMs did you flash to start with as I've tried flashing mine back to an earlier one in case it's something with the later stuff that my phone has come with but they either don't make a difference or they won't even boot.
I tried the method in the first post here and the phone wouldn't even boot (switch on and you get the Doogee logo in silver for a few seconds then it reboots and does the same again). I had to flash the stock ROM from NeedROM to get it working again.
I've tried flashing TWRPx32 and x64 available NeedROM both with SPFlash tools and with ADB. Generally flashing it with ADB from the command line leaves the phone in that boot-loop. If I flash it with SPFlash when you try to boot into Bootloader afterwards you get the Doogee logo in silver for a few seconds then it seems to reboot again on it's own and boot normally - you don't even get the menu to choose Fastboot, Recovery or Normal. From then on trying to boot to the Bootloader gives you the menu but choosing Recovery gives you the standard recovery.
It's almost as if something is overwriting the recovery partition with the original after I flash TWRP onto it.
Anyone got any suggestions about where I might be going wrong or a way around whatever additional security they might have put in there?
Hi. I have tried to root my x5 max pro with flash tools to load TWRP, but it always restarts normally and the TWRP does not come out. I found you and I started to try this method to load the TWRP. Does everything good, unload bootloader and load recovery, but loading the TWRP gives me error .:
Device unauthorized.
This adb's $ ADB_VENDOR_KEYS is nor set; Try adb kil-server if that seems wrong
what I do?
rooting X5 Max pro in Ubuntu 16.04
Hi all, this is my first china phone and I basically bought it only to experiment, I'm a linux power user but this is the first time I 'play' with an android OS.
thanks to multiple guides and posts on this and other forums I'm getting somewhere and learning a lot about how to manage an android OS, I'm sharing a bit of info I unovered about doing this under ubuntu but I'm also stuck and in need of guidance, please help me.
Linux specific issues:
I'm running ubuntu 16.04 LTS, installed fastboot and adb tools from ubuntu repos, with these tools and no other modification to my system I could follow the tutorial on how to unlock the OEM bootloader with adb and fastboot.
accordingly to this post about SP flash tool in linux you might need to blacklist a modem manager module in order for SP flash tool to connect to the phone, you also need to install usb development tools (package libusb-dev) and check through dmesg that your linux OS can actually properly read mediatek usb devices.
After following the above mentioned instructions (both the linux sp flash tool tutorial and the bootloader unlocking howto) I could get SP flash tool linux (multiple version) to see the phone after you connect it while SP flash is downloading the new recovery image and flash it with an ok message.
If you get stuck with a BROM error 1013 remember to start sp flash tool with root privileges.
Phone specific issues:
I can get SP flash tool to flash my phone recovery with an ok message confirmation but the phone keeps rebooting with doogee recovery and not twrp. I'm on the newest stock ROM update (20170116) as of current post date. I've been using 32 bit TWRP images from multiple sources and linux version 5.1620 of spflash tool from their website
so my questions are as following:
1) after reading other posts I think I might have to play with different versions of SP flash tool and TWRP until I get the right combination, I think I might be using 64bit spflash tool for linux to flash a 32bit rom or something like that, can anybody confirm precise version number of the stock rom, TWRP and SP flash tool that worked out for you?
2) should I try to install the whole stock ROM posted in this chinadevices thread before trying to flash only TWRP recovery? please also check the linked thread for multiple custom ROM being ported to this phone, please also note that the full stock rom this poster uploaded (it's in the "all firmware" link) contains another flashing tools with chinese instruction called MultiDownloadTool.
www.china-devices.com/forum/index.php?threads/doogee-x5-max-pro-mt6737-custom-roms.20527/
3) I don't have access to a windows installation right now, but I do have a Win10 VM under Vmware workstation 12 pro, so I could try windows version of sp flash tool, do you guys think that USB passthrough would work?
ibrooks said:
How old is your phone and what build version was it at before you started? Because this doesn't work on mine. Which of the "Android 6" ROMs did you flash to start with as I've tried flashing mine back to an earlier one in case it's something with the later stuff that my phone has come with but they either don't make a difference or they won't even boot.
I tried the method in the first post here and the phone wouldn't even boot (switch on and you get the Doogee logo in silver for a few seconds then it reboots and does the same again). I had to flash the stock ROM from NeedROM to get it working again.
I've tried flashing TWRPx32 and x64 available NeedROM both with SPFlash tools and with ADB. Generally flashing it with ADB from the command line leaves the phone in that boot-loop. If I flash it with SPFlash when you try to boot into Bootloader afterwards you get the Doogee logo in silver for a few seconds then it seems to reboot again on it's own and boot normally - you don't even get the menu to choose Fastboot, Recovery or Normal. From then on trying to boot to the Bootloader gives you the menu but choosing Recovery gives you the standard recovery.
It's almost as if something is overwriting the recovery partition with the original after I flash TWRP onto it.
Anyone got any suggestions about where I might be going wrong or a way around whatever additional security they might have put in there?
Click to expand...
Click to collapse
Same here. May a work around would be finding out the oem commands in fastboot. I have seen a tutorial to get them, but you have to be root: https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/
I search a simple method
Why all so complicate? I am searching for a simple way to root.
For my old Doogee X5, I discovered just
update-ROOT-DOOGEE_X5.zip
Copy the zip to the micro-SD-card
Settings -> Phone info -> Update -> menu "update local" -> choose zip from micro-SD-card.
Start update.
That's all!
Now I search for such a simple solution for my new Doogee X5 MAX pro.
I do not want any methods with "volume down power", because my X5 MAX pro has the menus after "Volume down power" start in Chinese language.
Recovery TWRP x32
http://www.needrom.com/download/twrp-x32-rom/
http://www.needrom.com/category/doogee/serial-x-doogee/x5-max-pro/
This version finally works ! Thank you
Neaw said:
Recovery TWRP x32
http://www.needrom.com/download/twrp-x32-rom/
http://www.needrom.com/category/doogee/serial-x-doogee/x5-max-pro/
Click to expand...
Click to collapse
Hi there,
I just tried the first file you posted, (twrp-x32-rom), and this one works for me after all previous attempts to boot up TWRP failed. Thanks for the link !
What I had tried before:
I have a relatively new X5 Max Pro, which I ordered a week ago. I updated the firmware to the newest version (20170116) using the OTA update function.
Then I tried to flash TWRP using the files from "needrom.com" which seem to have worked on older versions of the phone/firmware, but did not work for the newer versions.
I tried 32bit and 64bit TWRP versions and flashed them with SP flash tool, but when pressing Vol+/Power the phone would not boot into TWRP recovery. Insted, when selecting "Recovery" from the boot menu, the phone would show the Doogee logo in silver, then blink once, then boot up normally. When repeating this process, then phone boots into Stock recovery, indicating that the TWRP I flashed was replaced by stock recovery.
However, I just flashed the recovery.img from "TWRP LATEST" (the first file posted by Neaw) with SP flash tools and was finally able to boot into TWRP. I installed the superSU-zip 2.79 included in the link, and I am now rooted. Once again, thanks for posting this :good:
Greetz, Ollek74
Doogee X5 MAX! SERIUS PROBLEM......
Hello Guys i have a serious problem with my phone.....i have Malware on it and i cant uninstall it or anything alse.....the worst thing is that my phone not responding in any connection except that charging.....i can't have access on my storage cause this is not allowed or gives the choice! i tried everything but nothing nor the usb debugging or anything else please give me your help!!!!

And now what i do with my Axon 7?

Hello everyone. Meanwhile you excuse me for imperfect English but I use translator, my English language is rusted...
I have a A2017G, I have managed to unlock the bootloader, install TWRP and SuperSu on 6.0.1 version But then I have had the nice idea to update to 7.1.1 then have put update. zip file (renamed), in SD card, turn off the terminal, enter into TWRP but it Disappear!!! Only Originale...io recovery make flash and device updated to B09.
I want to install TWRP and SuperSu and put alternative ROMs but I can't do anything! If I open PowerShell window in adb folder and command "ADB reboot bootloader", the device reboot and appear a screen where to " your devices software can't be checked for corruption, please lock the bootloader", ecc ecc, If I squeeze volume on, it will get into recovery, if I don't do anything it reboot normally.
I can not get into fastboot mode, I fail to install TWRP. What is the best way to go back? or reset everything and start again? I have tried to downgrade from Nougat to MM via SD but after about 1 minute of analysis I aborted the installation....
However the phone will work normally even without all these things but I have purchased ZTE for modding and I don't bear to have half fatto...in work the most difficult thing to be unlocking the bootloader and I do this thing...
Let me link you my ingenious, allmighty Axon 7 Companion Thread.
Try to install twrp with MiFlash if you can enter edl mode
macerf said:
Hello everyone. Meanwhile you excuse me for imperfect English but I use translator, my English language is rusted...
I have a A2017G, I have managed to unlock the bootloader, install TWRP and SuperSu on 6.0.1 version But then I have had the nice idea to update to 7.1.1 then have put update. zip file (renamed), in SD card, turn off the terminal, enter into TWRP but it Disappear!!! Only Originale...io recovery make flash and device updated to B09.
I want to install TWRP and SuperSu and put alternative ROMs but I can't do anything! If I open PowerShell window in adb folder and command "ADB reboot bootloader", the device reboot and appear a screen where to " your devices software can't be checked for corruption, please lock the bootloader", ecc ecc, If I squeeze volume on, it will get into recovery, if I don't do anything it reboot normally.
I can not get into fastboot mode, I fail to install TWRP. What is the best way to go back? or reset everything and start again? I have tried to downgrade from Nougat to MM via SD but after about 1 minute of analysis I aborted the installation....
However the phone will work normally even without all these things but I have purchased ZTE for modding and I don't bear to have half fatto...in work the most difficult thing to be unlocking the bootloader and I do this thing...
Click to expand...
Click to collapse
Your phone works normally
You don't have fastboot
You have stock recovery
If this is the case then most surely you have EDL working...
Install TWRP from EDL mode:
This is taken from Controllerboy's guide
BE SURE THAT WINDOWS SHOWS FILE NAME EXTENSIONS!
A) Flashing TWRP Recovery to your device.
Q: Why do I need TWRP?
A: TWRP is a custom recovery system. It lets your backup your system in case anything goes wrong. It also lets you flash custom ROMs and zip files containing patches like viper4android or A.R.I.S.E. (audio) and root your device via SuperSU.
0) Boot up a windows computer with a 64bits processor. Verify your Axon 7 is charged at least 75%. Temporarily disable your antivirus software to allow axon7tool to work.
1) Backup all the data of your phone's internal memory that you don't want to lose. Copy it to your PC
2) Download the axon7tool from here: http://www.filedropper.com/axon7tool-15-win64
3) Download minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=457095661767103465
4) Unzip the minimal adb and fastboot file, place the folder with the files in it somewhere you can easily find it
5) Place the axon7tool exe in the same folder as adb.exe and rename it to "axon7tool.exe" (it's easier to work with that way)
6) Download the TWRP .img and .bin files from here: https://drive.google.com/open?id=0B4...nlaZU1NRldoRjA
7) Place the TWRP .img file in the same folder as "adb.exe" and "axon7tool.exe", rename it to "recovery.img"
8) Make a copy of the "recovery.img" file and name it "recovery.bin". Leave it in the same folder
9) Go to settings in your phone and go to "About Phone". Tap "Build Number" 7 times to make the Developer Options available
10) Go to "Developers options" and tick "Allow OEM unlock" and "Android Debugging"
11) Connect your Axon 7 to your PC
12) Open a command window by holding shift and right-clicking in a blank space in the folder where the "adb.exe", " axon7tool.exe", "recovery.img" and "recovery.bin" files are located. Click "Open command window here"
13) Type "adb devices" and hit enter. You should see one device with some code listed
14) Type "adb reboot edl" and hit enter. Your device will reboot to EDL mode. It appears to be off, but it is in fact in EDL mode.
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK"
16) In command, type "axon7tool -r gpt boot recovery" and hit enter
17) After it is executed, your phone will reboot. Wait until it has fully booted.
18) In command, type "adb reboot edl"
19) Verify you now have 3 backup files in your ADB folder for gpt, recovery and boot. These are backup files in case something goes wrong
20) In command, type "axon7tool -w recovery"
21) Wait until it finishes
22) Your phone should reboot
23) Shut down your phone and boot it to TWRP by holding both the power and volume up button to verify you have TWRP
24) TWRP might ask you for a password. If it does, simply tap cancel. It will ask you if you want to modify system. Swipe to agree
NOTE: if you have problems connecting to your phone as QUSB_BULK, download Zadig and replace your drivers with WinUSB ones. If axon7tool doesn't recignise your device even when connected as QUSB_BULK, try killing adb.exe via task manager before retrying.
Hello and thanks for the guide.
I have tried this system... be gone everything OK up to number 16... when I type "Axon7tool -r gpt boot recovery ", the command window should be written "Failed to connect "... and yet the device is in EDL mode.
Be all right, on Device Manager be seen as "QUSB_BULK ", the cable being original, all steps 1 to 16 be ok...io no longer know what to do.
macerf said:
Hello and thanks for the guide.
I have tried this system... be gone everything OK up to number 16... when I type "Axon7tool -r gpt boot recovery ", the command window should be written "Failed to connect "... and yet the device is in EDL mode.
Be all right, on Device Manager be seen as "QUSB_BULK ", the cable being original, all steps 1 to 16 be ok...io no longer know what to do.
Click to expand...
Click to collapse
Easy. Hold all 3 keys (power, vol up and down) until Device Manager refreshes (you'll see it as the list of devices contracting), and close CMD. Open it again and do step 16 again
Choose an username... said:
Easy. Hold all 3 keys (power, vol up and down) until Device Manager refreshes (you'll see it as the list of devices contracting), and close CMD. Open it again and do step 16 again
Click to expand...
Click to collapse
Hello and thanks for the advice. Unfortunately it does not change anything.. I have done exactly as you say but the result does not change anything...io have connected the device, Open command window, type "adb devices ", is viewed as "Cd07b2e9 device ", I type "adb reboot EDL ", it restarts in EDL, then go to management Devices and is viewed as "QUSB_BULK ", Run command "Axon7tool-r GPT boot recovery " but it says "Failed to connect ", then I'll return to Device Manager, hold volume up & Down & Power, Icon disappears and returns after a few seconds, close window and launch command "Axon7tool-r GPT boot recovery " but still give "failed to connect "...
So, recapping: I have bootloader unlocked, I can get into EDL but PC does not see device although on Device Manager it exists...
I now launch device into the wall... problem solved.
if you really slammed it against the wall, i would love to buy the back housing and speaker grills. hopefully, you were just illustrating frustration (it is a frustrating scenario), and will reach a resolution, but if you actually did smash it, i could use some parts.
kitcostantino said:
if you really slammed it against the wall, i would love to buy the back housing and speaker grills. hopefully, you were just illustrating frustration (it is a frustrating scenario), and will reach a resolution, but if you actually did smash it, i could use some parts.
Click to expand...
Click to collapse
Of course I'm kidding... have just purchased this device, have a great hardware but the software does not go well for nothing. I have had a dozen phones, I changed about 60 ROMs, so for me it is not difficult to change the software...ma in this case have problems. Is it possible that I fail to solve this problem? Be a way to reset everything and start from scratch? Okay, the bootloader be unlocked but not be any other way to go back? I have seen many guides but not able to solve the problem. I fail to make flash of TWRP, fail to do downgrade to MM....io hope someone help me... thanks.
are you using a USB 2.0 or 3.0 port? it may not apply to this scenario, but with Motorola and RSD Lite, I always had to use usb 2.0 ports or it wouldnt see my device when flashing.
also, the steps @choose an username listed out are the best way to start from scratch, but obviously you have to be able to have your computer see the phone in the desired mode.
@DrakenFX has several guides in the axon 7 forums that should help once the computer sees the phone as well.
I use USB 3.0 with original cable ... but if you now tell me that maybe this is my problem, then I use USB 2.0. Thank you...
Good morning...
Nothing to do... I put the original cable on USB Port 2.0, have redone procedure from window PowerShell, on command "adb devices " Everything OK, on command "adb reboot EDL " It enters EDL mode, but then all the procedures are failed... if command "Axon7tool-R recovery GPT boot "I always get out of the inscription " Failed to connect ", it remains in EDL and I just have to reboot... I replaced the drivers with Zadig 2.3 but did not change anything... are there any other moors to make flash of TWRP? exist lthough an app that do this? I remember that for LG G3 I'll fix everything with an app...

[GUIDE] How to root, install TWRP, ROMs and mods on a G3s/G3 beat d722 in 2020?

*After I wrote this whole thing as a DM i figured it might be helpful for a couple of people that are struggeling to root and install a custom recovery on their d722.*
Before we start you will need a PC with internet connection and a USB cable.
If you get stuck or need something about the device you can find it here. It's an XDA thread about the d722, it's mods, roms... : https://forum.xda-developers.com/lg-g3/general/lg-g3s-beat-d722-thread-t3110048
First you will need to flash your phone back to 4.4 kitkat firmware to ensure maximum compatibility (this is the only way my device would root) ( find it here: https://lg-firmwares.com/ (type in your model and download a 4.4 firmware closet to your region, language...)). We will do that with the lg flash tool (find it here: https://lgflash.com/download/) + also install lg drivers if you don't have them already (https://www.lg.com/us/support/help-library/lg-mobile-drivers-and-software-CT10000027-20150179827560).
1. First enable developer options in phone settings by tapping the build number 7 times. Go to the developer options and there tick usb debugging. Than you want to turn you device off. Hold volume up and plug it into you computer. You will get into download mode. On your PC extract and open the lg flash tool. There you will chose your kdz firmware file you downloaded previously and click normal fash. Choose other instead of korean and your preferred language. When you flash it the tool might report an error but just ignore it and wait for the phone to reach 100% download. It will reboot itself when finished. After that you can close the flash tool and continue to the next step.
2. Now you will root your phone. You will do that with lg one click root (found here: https://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951). Download the latest GUI version, install it onto your PC and open it. When your redy plug your phone into the computer (turned on no apps open) and click start. Wait for it to be done. It's normal for it to restart a few times.
3. Now we will instal the custom recovery to be able to flash ROMs. To do that you will need to dowbload this zip file from here and extract it with 7zip (https://forum.xda-developers.com/showpost.php?p=61220755&postcount=100) and install ADB (remeber install folder) (from here: https://forum.xda-developers.com/showthread.php?t=2588979). Paste aboot file into /sdcard folder (or folder of choice with adjusted path in command) ob your phone uding file manager. Than open CMD and type in
cd *path of your folder*
adb shell
su
dd if=/sdcard/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
If you get an error that says there is no aboot file or something similar than you nees to change this command : dd if= *your phones path*/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot For me it was : dd if=/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
4. This should have installed a basic version of TWRP on your phone ane booted into twrp recovery but we will be updating it.
To get into recovery from off state hold volume down + power button until you see the LG logo. Relese both for a split second and hold both down again (volume down + power) until you see an option to factory reset (wont actualy reset anything if you did all steps correctly). Click yes and yes again by using volume and power buttons and you will be booted to TWRP.
Alternative is to go to playstore and download root app that boots you to recovery if you do it often.
This version is quite old and not capable of flashing newer ROMs so we will be flashing an updated version (download it here: https://vasy.ru/TWRP/jagnm/ and rename it to .img if it isnt named like that alredy). Easiest way is to download it to your PC and transfer it via USB if your PC detects the phone while in TWRP. If not boot it up transfer the files and boot back to recovery. Now just flash the .img file and reboot.
5. At this point you have root privilages (super SU) and a custom recovery. Now all theres left to do is to flash ROMs and mods.
You boot to TWRP recovery, connect your phone to the PC and transfer the .zip files you want to flash. Tha you click flash in twrp chose your ROM files and click add more, your GAPPS click add more and the mod (if you want to try it of course). Than you flash them, wair for it to finish and click reboot.
If it takes longer than 15 min+ than you probaboy have a bootloop. To fix it take out the battery put it back in and boot into recovery (volume down + power until LG logo pops up, release for half a second hold again, yes and yes). Try factory reseting (type yes). And than just flash the ROM and boot. If it boots go back to recovery and flash GAPPS and mod and it should normaly boot into android.
If nothing fixes your issue you can alway use the firmware and lgflashtool to go back to default unrooted kitkat or lolipop.
My recomendations:
I personaly use this liniage (14.1) 7.1 ROM as it's still getting updates (I also tried 8.1 but it's buggy, laggy and gapps don't work):
https://forum.xda-developers.com/lg-g3/development/cyanogenmod-14-1-lg-g3s-t3508224
And of course you want google apps to go along with it:
https://opengapps.org/ (pick ARM, android version of ROM (7.1 in this case) and how many preinstalled apps (I use nano))
I also have this mod installed which makes colours of your display a bit better:
http://www.mediafire.com/download/6z9yg1d3gooyz37/Sony_Bravia_3.zip
From here you can also get Exposed framework, root apps like LSpeed to speed up your phone even more, greenfy and amplify to improve battery life. Again every mod for this phone along with overclocking and other mods is or was discussed here at one point so dont be afraid to join the conversation in this thread:
https://forum.xda-developers.com/lg-g3/general/lg-g3s-beat-d722-thread-t3110048
And ofcourse google is your friend if you get into any issues. Hope this helps, typed it on my G3s .
Thanks
---------- Post added at 12:28 PM ---------- Previous post was at 11:44 AM ----------
It would be better for our phone to release an android 9 custom, it would be great. Here is the same phone as our processor and video accelerator. Android 9 would work great on our phone https://4pda.ru/forum/index.php?showtopic=633150&view=findpost&p=36961339
Thanks for the guide!
I bought a G3s D722 cheap off ebay to experiment with. I tried to flash four different kitkat roms many times on 2 computers and each time the phone went into boot loop (start tune and logo over and over) so I flashed the first UK Lollipop on the list and all went fine, there are not UK kitkat roms in the link.
The UK kitkat roms must be different is all I can determine anyone know where I can get one?
The preflash OS was V20e-EUR-XX and now its V20d
Any thoughts or suggestions anyone?
Thanks!
I couldn't get this to work so tried the very easy no PC method in the link and it works great!
LG G3/G3s/G3 Beat telekom,orange or any other operator
Hi everyone, I want to show u how to upgade your LG G3s/beat to adroid 7.1.1 lineage OS. It has taken me some time to find and to gather all needed files but i was succesfull :D So I had my lg running on android 5.1 Lollipop but I had problem...
forum.xda-developers.com

Categories

Resources