Hi,
I tried to install the new 5.1.1 Android version, but I have a issue :
1°) my Device States is locked
2°) my Device doesn't not start I have the animation + Android is uprading your app + Starting your app in loop, but no access to the devs mod and activate oem install in the devs option.
My Question is :
How can i fix this ^^ ?
Ncisboys said:
Hi,
I tried to install the new 5.1.1 Android version, but I have a issue :
1°) my Device States is locked
2°) my Device doesn't not start I have the animation + Android is uprading your app + Starting your app in loop, but no access to the devs mod and activate oem install in the devs option.
My Question is :
How can i fix this ^^ ?
Click to expand...
Click to collapse
Sent from my Nexus 9 using XDA Free mobile app
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
Ncisboys said:
Hi,
I tried to install the new 5.1.1 Android version, but I have a issue :
1°) my Device States is locked
2°) my Device doesn't not start I have the animation + Android is uprading your app + Starting your app in loop, but no access to the devs mod and activate oem install in the devs option.
My Question is :
How can i fix this ^^ ?
Click to expand...
Click to collapse
How did you try to install the update? By OTA or other means? Can you boot into recovery?
Sent from my Nexus 9 using XDA Free mobile app
---------- Post added at 07:20 PM ---------- Previous post was at 07:19 PM ----------
Ncisboys said:
Hi,
I tried to install the new 5.1.1 Android version, but I have a issue :
1°) my Device States is locked
2°) my Device doesn't not start I have the animation + Android is uprading your app + Starting your app in loop, but no access to the devs mod and activate oem install in the devs option.
My Question is :
How can i fix this ^^ ?
Click to expand...
Click to collapse
How did you try to install the update? By OTA or other means? Can you boot into recovery?
Sent from my Nexus 9 using XDA Free mobile app
I try by the factory file with the script
Some others informations. I try the recovery mod a the command adb sideload 5.1.1 version OTA file. I have an issue during the sending (expected a previous version). I don't remember the exact message but it failed
Ncisboys said:
Some others informations. I try the recovery mod a the command adb sideload 5.1.1 version OTA file. I have an issue during the sending (expected a previous version). I don't remember the exact message but it failed
Click to expand...
Click to collapse
We can't help you without the error message. Try it again and write it down.
Package*expects*build fingerprint of google/volantis/flounder: + Version Number
Ncisboys said:
Package*expects*build fingerprint of google/volantis/flounder: + Version Number
Click to expand...
Click to collapse
The OTA will only work if you are currently on 5.0.2. What version is currently on your N9?
5.0.2. But something strange. On the bootloader I can see Os n/a ... It is normal?
Maybe can you explain how can I unlock oem without having access to the development option. If I can unlock it maybe I can flash factory image again
Simple answer.. You can't.
Ncisboys said:
Maybe can you explain how can I unlock oem without having access to the development option. If I can unlock it maybe I can flash factory image again
Click to expand...
Click to collapse
"Enable OEM Unlock" is an option within Developer Options that needs to be enabled in order to unlock the bootloader.
IMHO the 1st three things everyone who owns this device should do immediately is :
1.) Enable Developer Options ("how to's" are all over the place on the net and easily found.)
2.) Put a check box in "Enable OEM Unlock" in Developer Options
3.) Put a check box in "Enable USB debugging" in Developer Options.
So I can't use my nexus 9 anymore?
Assuming you grabbed the factory image from the google developer site you should have seen following the instructions on that page...
To flash a system image:
1.) Download the appropriate system image for your device below, then unzip it to a safe directory.
2.) Connect your device to your computer over USB.
3.) Start the device in fastboot mode with one of the following methods:
Using the adb tool: With the device powered on, execute:
adb reboot bootloader
4.) If necessary, unlock the device's bootloader by running:
fastboot oem unlock
STEP 4 is critical ...
What isn't mentioned here is that on the Nexus 9, in order for this command to be successfully executed, "Enable OEM Unlock" must 1st be checked off under Developer Options in the OS.
So you are now in a chicken and egg situation,,, You need to flash the factory image to get your device back up and running but unfortunately you need to have a device up and running to enable oem unlock in the 1st place.
You will likely have to RMA your device.
Ncisboys said:
So I can't use my nexus 9 anymore?
Click to expand...
Click to collapse
What is RMA?
Google it please.
Ncisboys said:
What is RMA?
Click to expand...
Click to collapse
I saw it after asking. I thought I was a manipulation...
Ncisboys said:
I saw it after asking. I thought I was a manipulation...
Click to expand...
Click to collapse
Ha, very funny. (although I'm sure it's not to you).
Yup, you'll have to return the device for service and/or replacement.
Thank you for the help.
Related
Hello everyone. I just sold my Moto X so I will no longer be updating this toolkit. I will try and help anyone with questions/problems when needed.
Back by popular demand...
I have had some people asking for links for my previously deleted toolkit.
So I have decided to revamp the toolkit for dev edition devices only. (Currently only supporting GSM dev (AT&T and T-Mobile) and VZW Dev)
With this toolkit you will be able to the following...
1) Root your device (unlock bootloader, install TWRP, install superSU)
2) Unroot your device
3) Return to stock
4) Debloat (google, moto, vzw stuff)
5) Activate mobile hotspot (VZW only)
6) reboot (recovery, bootloader, device)
7) Customize (bootanimation, bootlogo, ringtones, notifications)
How to use
1) Click download below
2) Extract zip file
3) Turn you phone on
4) Make sure USB debugging is enabled
5) Plug your phone into the computer.
6) Run moto_x_mac_tools.tool
7) FOLLOW ONSCREEN INSTRUCTIONS
Screenshots
See attachments...
Download
Moto X Toolkit v2.03
Change Log
v2.01 - Fixed some bugs with restoring back to stock, removed ReadWrite status (with dev edition this status is not needed)
v2.02 - Added downgrade from 4.4.2 to 4.4
- When returning to stock, or downgrading, USER DATA will be erased (no longer an option)
- There are only 2 variants of the dev edition so I changed to Verizon and GSM
v2.03 - Updated to latest supersu and TWRP
Please do not redistribute/mirror this toolkit. If you would like to link it in any other thread, please include a link back to this thread, give proper credit.
As with anything you will find on XDA, I am not responsible for anything that occurs to your phone or computer by using this toolkit.
Credits
DHacker29 / Hashcode - TWRP
Chainfire - SuperSU
imnuts - VZW tether
Google
Motorola
Awesome, I used your old toolkit to flash stock recovery (so I could take the ota) and then back to TWRP. It was so easy! I'm sure others will appreciate this as well.
iamjackspost said:
Awesome, I used your old toolkit to flash stock recovery (so I could take the ota) and then back to TWRP. It was so easy! I'm sure others will appreciate this as well.
Click to expand...
Click to collapse
Toolkit is ready for download!!
unlock with moto first?
Do I need to unlock my bootloader with Motorola before using the toolkit? I do have a VZW Dev device, but wanted to confirm.
This utility is amazing and a must for anyone with a Mac! Thanks x100!
moonzilla said:
Do I need to unlock my bootloader with Motorola before using the toolkit? I do have a VZW Dev device, but wanted to confirm.
Click to expand...
Click to collapse
You can either unlock before using the toolkit. Or you can use the toolkit to guide you through the unlock. If you go to root device. The 1st question is if you are unlocked or not. If not, it will guide you through the process of unlocking the bootloader (semi-automatic). Let me know if you have any questions.
Mike
Thank you for re-posting this tool.
I am trying to go back to stock 4.4 to get the OTA (I have a Dev Ed VZN Moto X). I followed the on screen directions and downloaded the VZN 4.4 file (640 MB file). Then the phone reboots to bootloader (ReadWriteMode is 0). I press ENTER since the device has booted into FB mode and it says USB connected, the ReadWriteMode reads error: device not found (I did not unplug the phone from the computer).
Is there a fix for it? The same thing happens when I try to download 4.4.2.
Thanks
wmjchoi said:
Thank you for re-posting this tool.
I am trying to go back to stock 4.4 to get the OTA (I have a Dev Ed VZN Moto X). I followed the on screen directions and downloaded the VZN 4.4 file (640 MB file). Then the phone reboots to bootloader (ReadWriteMode is 0). I press ENTER since the device has booted into FB mode and it says USB connected, the ReadWriteMode reads error: device not found (I did not unplug the phone from the computer).
Is there a fix for it? The same thing happens when I try to download 4.4.2.
Thanks
Click to expand...
Click to collapse
When in fastboot mode. The readwrite will say device not found. An ADB command is used to check the readwrite status. And ADB commands do not function while in fastboot mode.
You are ok to continue.
mjphillips1981 said:
When in fastboot mode. The readwrite will say device not found. An ADB command is used to check the readwrite status. And ADB commands do not function while in fastboot mode.
You are ok to continue.
Click to expand...
Click to collapse
Thanks.
I pressed enter to continue but my phone just reboots and restore does not work.
But when I tried to flash the stock recovery, readwrite says 0 and works like a charm. The problem only occurs when I try to restore the device.
wmjchoi said:
Thanks.
I pressed enter to continue but my phone just reboots and restore does not work.
But when I tried to flash the stock recovery, readwrite says 0 and works like a charm. The problem only occurs when I try to restore the device.
Click to expand...
Click to collapse
I will test on my device. I will let you know what I find out.
mjphillips1981 said:
When in fastboot mode. The readwrite will say device not found. An ADB command is used to check the readwrite status. And ADB commands do not function while in fastboot mode.
You are ok to continue.
Click to expand...
Click to collapse
mjphillips1981 said:
I will test on my device. I will let you know what I find out.
Click to expand...
Click to collapse
Thank you!!
wmjchoi said:
Thanks.
I pressed enter to continue but my phone just reboots and restore does not work.
But when I tried to flash the stock recovery, readwrite says 0 and works like a charm. The problem only occurs when I try to restore the device.
Click to expand...
Click to collapse
I found a typo in the script. I am trying it now. Should see a new download shortly. Thanks for pointing this out.
mjphillips1981 said:
I found a typo in the script. I am trying it now. Should see a new download shortly. Thanks for pointing this out.
Click to expand...
Click to collapse
Not a problem. Again, thank you for making a great tool! I will test out the new version and report if there are any problems. Let me know when the new one is up.
wmjchoi said:
Not a problem. Again, thank you for making a great tool! I will test out the new version and report if there are any problems. Let me know when the new one is up.
Click to expand...
Click to collapse
v2.01 is ready for download.
mjphillips1981 said:
v2.01 is ready for download.
Click to expand...
Click to collapse
It worked. I was able to upgrade to 4.2.2. Thank you so much. One thing though, the color on the screen is off. So far it looks like the color red is off. This might be my device only. I am going to flash 4.2.2. again and see if it happens again.
wmjchoi said:
It worked. I was able to upgrade to 4.2.2. Thank you so much. One thing though, the color on the screen is off. So far it looks like the color red is off. This might be my device only. I am going to flash 4.2.2. again and see if it happens again.
Click to expand...
Click to collapse
I just did the factory restore to 4.4.2 and all of my colors are ok.
Make sure you erase user data when it asks you. But this will erase everything.
mjphillips1981 said:
I just did the factory restore to 4.4.2 and all of my colors are ok.
Make sure you erase user data when it asks you. But this will erase everything.
Click to expand...
Click to collapse
I did the factory restore again to 4.2.2 but I still have the same issue. I think something is wrong with my display. I think I need to call vzn and have them send me another unit.
---------- Post added at 07:24 PM ---------- Previous post was at 06:47 PM ----------
mjphillips1981 said:
I just did the factory restore to 4.4.2 and all of my colors are ok.
Make sure you erase user data when it asks you. But this will erase everything.
Click to expand...
Click to collapse
Should i downgrade to 4.4? Or is it a bad idea?
wmjchoi said:
I did the factory restore again to 4.2.2 but I still have the same issue. I think something is wrong with my display. I think I need to call vzn and have them send me another unit.
---------- Post added at 07:24 PM ---------- Previous post was at 06:47 PM ----------
Should i downgrade to 4.4? Or is it a bad idea?
Click to expand...
Click to collapse
Here is what I would do...
Just install TWRP and install Eclipse 3.2.1. This is the ROM that I use. It is great!! See if that fixes your color issue. If it does not. They I would say your device is f-ed up.
http://forum.xda-developers.com/moto-x/development/rom-eclipse-moto-x-blur-based-v2-2-t2521509
mjphillips1981 said:
Here is what I would do...
Just install TWRP and install Eclipse 3.2.1. This is the ROM that I use. It is great!! See if that fixes your color issue. If it does not. They I would say your device is f-ed up.
http://forum.xda-developers.com/moto-x/development/rom-eclipse-moto-x-blur-based-v2-2-t2521509
Click to expand...
Click to collapse
I tried flossing Eclipse 3.2.1 and the color was still off. My camera is not working as well. Maybe I will lock up the boot loader and restore it to 4.2.2 again. But your tool works great.
Currently on the phone with Motorola...
I should not downgrade to 4.4, right?
wmjchoi said:
I tried flossing Eclipse 3.2.1 and the color was still off. My camera is not working as well. Maybe I will lock up the boot loader and restore it to 4.2.2 again. But your tool works great.
Currently on the phone with Motorola...
I should not downgrade to 4.4, right?
Click to expand...
Click to collapse
I am not sure if you can downgrade or not with a dev edition. I have never tried. I know some people that have a consumer VZW (locked bootloader) cannot downgrade.
So lg released the unlock tool for lg v10 europe market
I have the czech lg v10 H960A but i live in middle east
I registred and enter the serial number and device serial
When i press unlock bootloader there is a popup that say servics unavailable please contact site administrator .....
Any idea about the problem?
I tried many times from many browsers with no luck
the problem is solved
vip57 said:
the problem is solved
Click to expand...
Click to collapse
So now we can root h960a with android 6 ?
rowihel2012 said:
So now we can root h960a with android 6 ?
Click to expand...
Click to collapse
Yes you can
You can view the steps in this link
http://forum.xda-developers.com/lg-v10/development/recovery-twrp-v3-0-2-0-unofficial-t3387783
vip57 said:
Yes you can
You can view the steps in this link
http://forum.xda-developers.com/lg-v10/development/recovery-twrp-v3-0-2-0-unofficial-t3387783
Click to expand...
Click to collapse
You must be on newest stock Marshmallow: H960A20a_00_0316.kdz
what that mean ? means the android 6 ?
rowihel2012 said:
You must be on newest stock Marshmallow: H960A20a_00_0316.kdz
what that mean ? means the android 6 ?
Click to expand...
Click to collapse
Sorry i don't know i unlocked the bootloader only didn't root yet you need to ask from the thread
It is for sure android 6 but i don't know if you need to be on a specific build
vip57 said:
Sorry i don't know i unlocked the bootloader only didn't root yet you need to ask from the thread
It is for sure android 6 but i don't know if you need to be on a specific build
Click to expand...
Click to collapse
The build version should be MRA58K. It's the latest/only build for Android 6/MM which is available for the european version of the V10 (AFAIK) where the bootloader can be unlocked. If you updated your phone via LG Bridge you can be fairly sure the installation of TWRP works.
cyvr1 said:
The build version should be MRA58K. It's the latest/only build for Android 6/MM which is available for the european version of the V10 (AFAIK) where the bootloader can be unlocked. If you updated your phone via LG Bridge you can be fairly sure the installation of TWRP works.
Click to expand...
Click to collapse
i have h960a with MRA58K :good:
rowihel2012 said:
i have h960a with MRA58K :good:
Click to expand...
Click to collapse
Then go for it. :laugh:
But make sure you follow the steps mentioned on the page linked above.
You will not brick your phone if you don't but perform a factory reset and loose all data.
Maybe do a backup on a micro SD card prior to trying to flash TWRP.
If you have not unlocked your bootloader yet you need definitely need to backup your data as the bootloader unlock will also perform a factory reset.
vip57 said:
the problem is solved
Click to expand...
Click to collapse
why cant enter bootloader
after
adb reboot boatloader
phone reboot to soft
---------- Post added at 03:55 PM ---------- Previous post was at 03:49 PM ----------
cyvr1 said:
Then go for it. :laugh:
But make sure you follow the steps mentioned on the page linked above.
You will not brick your phone if you don't but perform a factory reset and loose all data.
Maybe do a backup on a micro SD card prior to trying to flash TWRP.
If you have not unlocked your bootloader yet you need definitely need to backup your data as the bootloader unlock will also perform a factory reset.
Click to expand...
Click to collapse
after adb reboot boatloader phone reboots to software not bootloader
how to fix this?
rowihel2012 said:
why cant enter bootloader
after
adb reboot boatloader
phone reboot to soft
---------- Post added at 03:55 PM ---------- Previous post was at 03:49 PM ----------
after adb reboot boatloader phone reboots to software not bootloader
how to fix this?
Click to expand...
Click to collapse
If you really typed "adb reboot boatloader" it is not surprising that the phone reboots because the parameter "boatloader" is unknown. The command executed by the phone is then "adb reboot".
"adb reboot bootloader" should solve the problem.
if "boatloader" is just a typo (though you typed it twice) check if "USB debugging" in the developer options is really enabled. Maybe disable and enable it again.
One other thing I forgot and it is not mentioned in the LG tutorial for unlocking the bootloader if I remember correctly:
I needed to enable the option "Allow OEM unlock" under developer options to be able to perform the unlock command with the unlock.bin file received by mail from LG. After the unlock is done and the phone rebooted disable this option again. Otherwise the fingerprint sensor is not working correctly. you can register fingerprints but not unlock your phone with it.
cyvr1 said:
If you really typed "adb reboot boatloader" it is not surprising that the phone reboots because the parameter "boatloader" is unknown. The command executed by the phone is then "adb reboot".
"adb reboot bootloader" should solve the problem.
if "boatloader" is just a typo (though you typed it twice) check if "USB debugging" in the developer options is really enabled. Maybe disable and enable it again.
Click to expand...
Click to collapse
i did that
adb reboot bootloader
---------- Post added at 04:11 PM ---------- Previous post was at 04:09 PM ----------
now
adb reboot bootloader
rebooted to soft
vip57 said:
the problem is solved
Click to expand...
Click to collapse
cant enter bootloader do you know why?
I've a H960A, but when I try to update the phone, LG bridge provides me the new version H96020a and says that my model number is h960! (without "A") Does it mean, that I can not unlock the bootloader?
bangkokguy said:
I've a H960A, but when I try to update the phone, LG bridge provides me the new version H96020a and says that my model number is h960! (without "A") Does it mean, that I can not unlock the bootloader?
Click to expand...
Click to collapse
if you are sure 100% that your phone is H 960A it will never be changes after update
bangkokguy said:
I've a H960A, but when I try to update the phone, LG bridge provides me the new version H96020a and says that my model number is h960! (without "A") Does it mean, that I can not unlock the bootloader?
Click to expand...
Click to collapse
Open the phone settings / About phone / Hardware info. What model number is shown there?
If it is in fact a H960 (without A) you can't unlock the bootloader.
Also there seem to be some problems with the H960A for some users. Meanwhile I suspect that those are phones which were not meant to be sold in Europe but somehow found their way here. Therefore some internal flag might prevent those phones from booting into bootloader / fastboot mode.
H960 in android 5.1, H960A in 6.0
bangkokguy said:
I've a H960A, but when I try to update the phone, LG bridge provides me the new version H96020a and says that my model number is h960! (without "A") Does it mean, that I can not unlock the bootloader?
Click to expand...
Click to collapse
vip57 said:
if you are sure 100% that your phone is H 960A it will never be changes after update
Click to expand...
Click to collapse
again a late reply, but for followers :
I also have a (32GB) H960A (bought from a german store), now unlocked and rooted.
The model number shown in settings when still in android 5.1 was also : Model : LG-H960
It's only after succesfull update (with LG Bridge) that the model shown in the settings became LG-H960A...
edit : I notice now that it is still detected as H960 by some
tools :
oleg77 said:
again a late reply, but for followers :
I also have a (32GB) H960A (bought from a german store), now unlocked and rooted.
The model number shown in settings when still in android 5.1 was also : Model : LG-H960
It's only after succesfull update (with LG Bridge) that the model shown in the settings became LG-H960A...
edit : I notice now that it is still detected as H960 by some
tools :
Click to expand...
Click to collapse
Hi.. Did u manage to solve your problem? We both have the same one..
I don't see this as a problem : the model is well H960A, it's just shortened in the set up menu. If you have a 32GB model, I don't think you could get something else.
I'm pleased to get it rooted, but sad to see so few development because of LG reluctance to let the community work on it.
Below you will find instructions how to root this device.
The following procedure has been tested up to firmware MMB29K.J320AUSC2AQA1
KNOX should remain 0x0
However you undertake this at your own risk.
(NOTE: This procedure will also work for the SM-J320AZ (Cricket))
Issues:
Wifi passwords not remembered (fix below)
Stock Flashlight app not working.
Model number may be missing from build.prop (fix below)
Instructions
1.Download the eng boot image.
This is a special boot image normally used by engineers, it allows selinux to be booted in permissive mode with relaxed root restrictions.
Do not replace this image with the stock image after rooting your device or you will possibly soft brick your device.
(See below for how to recover)
ENG_BOOT_J320A_PG1
2. Flash the boot image:
Download Odin v3.11.1
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the ENG_BOOT_J320A_PG1.tar to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
3. Install and run Kingroot:
http://www.apkmirror.com/apk/kingro...-release/kingroot-5-0-5-android-apk-download/
You may need to run Kingroot several times to gain successful root.
4. Install and run SuperSU me to remove Kingroot and convert to SuperSU (not required) :
https://play.google.com/store/apps/...ore&pcampaignid=APPU_1_uzPDVbGyFcGNyATHrqmoCA
Alternative (free) method to replace Kingroot:
Follow Steps 3 to 12.
https://forum.xda-developers.com/ga...ide-how-to-root-tripping-knox-kitkat-t3129484
Don't flash the boot partition with Flashfire, uncheck.
You will also need to flash the system version of SuperSU not EverRoot.
When you get to step 12, don't flash the firmware. Disable EverRoot and just flash this:
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
5. Wifi fix:
modify the line below in /system/build.prop:
ro.securestorage.support=true to false
6. Model number fix:
http://www.techgainer.com/change-fake-android-device-model-number-and-brand-name/
7. To fix “Unauthorized actions have been detected”
disable 'Security log agent'
Enjoy your rooted device.
Recovering from a soft brick:
Flash the stock firmware provided below wirh ODIN in the AP slot.
https://www.androidfilehost.com/?fid=745425885120713788
J3 forum link: https://forum.xda-developers.com/t/galaxy-j3-2016
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Thanks bud. Your post in the other thread convinced me to purchase this device... so far so good
To everyone else, I had to use the patched version of supersu me to remove kingroot
Bugs in the system
So i reflashed the stock rom, everything was great. when i reflashed the file you gave us, debugging has failed to work as well as the flashlight. other than that no issues so far
bobbyp1086 said:
So i reflashed the stock rom, everything was great. when i reflashed the file you gave us, debugging has failed to work as well as the flashlight. other than that no issues so far
Click to expand...
Click to collapse
What do you mean debugging does not work? Adb is enabled by default, it's an engineering boot image.
ashyx said:
What do you mean debugging does not work? Adb is enabled by default, it's an engineering boot image.
Click to expand...
Click to collapse
instead of it asking if i want the computer to read i get this
bobbyp1086 said:
instead of it asking if i want the computer to read i get this
Click to expand...
Click to collapse
What response do you get for
adb devices
In adb?
Think the dous firmware has issues on our devices.
I'll upload j320aucu2apj2 shortly
DamienMc said:
Think the dous firmware has issues on our devices.
I'll upload j320aucu2apj2 shortly
Click to expand...
Click to collapse
How is an older firmware going to be better when most people will already be running AQA1 firmware?
ashyx said:
What response do you get for
adb devices
In adb?
Click to expand...
Click to collapse
The generic. But then i set the directory to sdk/platformtools and it worked.
But flashlight gone. Keyboard,google services and cell gone. Cant uninstall kingroot with every method out there and my phone is glitching
---------- Post added at 10:04 PM ---------- Previous post was at 10:02 PM ----------
DamienMc said:
Think the dous firmware has issues on our devices.
I'll upload j320aucu2apj2 shortly
Click to expand...
Click to collapse
Mine is stock duos, i love the stock rom, but my conputer died this morning,no hopes of odin
bobbyp1086 said:
The generic. But then i set the directory to sdk/platformtools and it worked.
But flashlight gone. Keyboard,google services and cell gone. Cant uninstall kingroot with every method out there and my phone is glitching
---------- Post added at 10:04 PM ---------- Previous post was at 10:02 PM ----------
Mine is stock duos, i love the stock rom, but my conputer died this morning,no hopes of odin
Click to expand...
Click to collapse
King root can be replaced with supersu me or the script. It can also be easily uninstalled via its settings.
What did you actually install?
My system went haywire. I need a command thru terminal on android to factory reset, can't boot into recovery.
bobbyp1086 said:
My system went haywire. I need a command thru terminal on android to factory reset, can't boot into recovery.
Click to expand...
Click to collapse
Just hold POWER + HOME + VOL DOWN until the device reboots then immediately change to POWER + HOME + VOL UP to get in to recovery mode or in Terminal type
su
reboot recovery
.
Thats a no go, can't boot up. kingroot seems to have killed my phone i just get "unfortunatley System UI has Stopped" when i power up. I will reflash withwork comp and update in a few hours...
bobbyp1086 said:
Thats a no go, can't boot up. kingroot seems to have killed my phone i just get "unfortunatley System UI has Stopped" when i power up. I will reflash withwork comp and update in a few hours...
Click to expand...
Click to collapse
You can't possibly have lost the recovery, nothing has touched it. It does take a short while for stock recovery to boot.
ashyx said:
Just hold POWER + HOME + VOL DOWN until the device reboots then immediately change to POWER + HOME + VOL UP to get in to recovery mode or in Terminal type
su
reboot recovery
.
Click to expand...
Click to collapse
ashyx said:
You can't possibly have lost the recovery, nothing has touched it. It does take a short while for stock recovery to boot.
Click to expand...
Click to collapse
Iam lost as to how it happened as well lol but its ok, just a tester phone for fun 3rd time i have done something wrong :laugh:
---------- Post added at 04:33 PM ---------- Previous post was at 04:12 PM ----------
Reflashed Stock Firmware, regained access to recovery, factory reset and back up and running. i actually noticed some new features in recovery. i can actually apply update from sd now, whereas before i could not access files on sd, looks like dm-verity is also gone, or at least not showing up in recovery as before (maybe because it was a failed test) also the start up of the phone has skipped the initial set up (no add account or set up password) and the main screen is way more crisp and clear than what i had on before, even with the other 3 reflashes i have previously done. so far so good though
DamienMc said:
Thanks bud. Your post in the other thread convinced me to purchase this device... so far so good
To everyone else, I had to use the patched version of supersu me to remove kingroot
Click to expand...
Click to collapse
How did the patch work? mine keeps opening saying licence validated and closing....going to try script version
bobbyp1086 said:
How did the patch work? mine keeps opening saying licence validated and closing....going to try script version
Click to expand...
Click to collapse
The model number missing is a known issue. You just need to edit the build.prop and put it back.
See this link for more info: http://www.techgainer.com/change-fake-android-device-model-number-and-brand-name/
bobbyp1086 said:
How did the patch work? mine keeps opening saying licence validated and closing....going to try script version
Click to expand...
Click to collapse
Used an old version, 9.7.4P
And I only got the script to work once :/
DamienMc said:
Used an old version, 9.7.4P
And I only got the script to work once :/
Click to expand...
Click to collapse
ok so the script is working but there is a different way
1. install kingroot 4.5 from apk mirror
2. Run script
3. update Su
4. update Binary
(i had to reinstall kingroot and deny kingroot root permission before binary would update and uninstall and keep root)
it seems denying kingroot root permission keeps the root on the device, letting su take over for root permission and uninstall of kingroot.
i know it seems weird but it works, the hang up was updating su, which you can do from google play
---------- Post added at 05:14 PM ---------- Previous post was at 04:56 PM ----------
Anyone have a stock "Build.prop" for this model
bobbyp1086 said:
Anyone have a stock "Build.prop" for this model
Click to expand...
Click to collapse
I'll upload it later.
I know some Stylos are able to obtain root. What's the scenario for the 3/3 Plus series?
AidenSurvival said:
I know some Stylos are able to obtain root. What's the scenario for the 3/3 Plus series?
Click to expand...
Click to collapse
dont know yet but the plus series is ure best bet from history speaking
as of rite now theyre no methods on any of the 3s
of coarse u can try king/kingo root prob be best bet
The Plus models from MetroPCS and TMobile have unlockable bootloader's, so all that's needed is TWRP to flash root
Sent from my LGMP450 using Tapatalk
Nice to know there will be an option in a month or two. I hear development on Stylos don't take too long considering their popularity.
I would love to know what's needed to attempt root on a device...I mean from scratch...like what is needed to access the /data file...and how to break thru the lock LG has to stop someone from mounting and rewriting certain files
Sent from my LG-TP450 using Tapatalk
SoonersChuck said:
I would love to know what's needed to attempt root on a device...I mean from scratch...like what is needed to access the /data file...and how to break thru the lock LG has to stop someone from mounting and rewriting certain files
Sent from my LG-TP450 using Tapatalk
Click to expand...
Click to collapse
Do the devices have fast boot. If so a oem unlock. Some one said metro and t mobiles where unlocked or unlockable
I'm no programming/root expert but in developer options you enable oem unlock.. then connected o the pc you type fastboot oem unlock from a command prompt.. the phone then says its unlocked .. that's as far as I went. Aso after that, when you boot the phone, it literally complains that it is missing security before it boots.
gregvolt said:
I'm no programming/root expert but in developer options you enable oem unlock.. then connected o the pc you type fastboot oem unlock from a command prompt.. the phone then says its unlocked .. that's as far as I went. Aso after that, when you boot the phone, it literally complains that it is missing security before it boots.
Click to expand...
Click to collapse
thats it you should be able to either flash su from fastboot or temp run a twrp image until one is made i think
TheMadScientist420 said:
thats it you should be able to either flash su from fastboot or temp run a twrp image until one is made i think
Click to expand...
Click to collapse
If this works for the previous poster, let me know. Rooting this thing would be a dream.
AidenSurvival said:
If this works for the previous poster, let me know. Rooting this thing would be a dream.
Click to expand...
Click to collapse
well I screwed it up. I erased the system partition. wait for an official to come out. had to go buy another phone. if anyone knows how to take the system partition from another phone and make a fastboot flashable copy of it. please by all means, fill me in so I can get the phone working again.
AidenSurvival said:
If this works for the previous poster, let me know. Rooting this thing would be a dream.
Click to expand...
Click to collapse
as stated may not be possible til a actuall twrp image is made
i know other devices with unlockable bl didnt have to flash twrp but run it in fast boot long enought to flash su then upon new reboot stock recov was still there but rooted
can u enable oem unlock the abd usb debugging then abd reboot fastboot?
you also can try coimmand in fastboot to either fastboot oem unlock or just oem unlock
but if u click yes in the fastboot dialouges ure device will be unlocked and wiped
---------- Post added at 09:29 AM ---------- Previous post was at 09:27 AM ----------
gregvolt said:
well I screwed it up. I erased the system partition. wait for an official to come out. had to go buy another phone. if anyone knows how to take the system partition from another phone and make a fastboot flashable copy of it. please by all means, fill me in so I can get the phone working again.
Click to expand...
Click to collapse
try my lg firmwares they normally carry metro and tmob firmwares to flash through download mode
---------- Post added at 09:31 AM ---------- Previous post was at 09:29 AM ----------
also guys as previous poster wiped system partition if im not mistaken there is a way to back up all patitions from fast boot i dont know commands but a quik google of backup device from fastboot should lead u rite then someone should be able to upload a system partition for said previous poster
---------- Post added at 09:35 AM ---------- Previous post was at 09:31 AM ----------
gregvolt said:
well I screwed it up. I erased the system partition. wait for an official to come out. had to go buy another phone. if anyone knows how to take the system partition from another phone and make a fastboot flashable copy of it. please by all means, fill me in so I can get the phone working again.
Click to expand...
Click to collapse
im waiting in the g4 threads to see if a few friends might be able to help us and u out if we can get a full device back up in fastboot then get it uploaded then there should be a command to reflash it through fastboot
im waiting in the g4 threads to see if a few friends might be able to help us and u out if we can get a full device back up in fastboot then get it uploaded then there should be a command to reflash it through fastboot[/QUOTE]
Great I can still get to fastboot so if I could get an image, I could flash it.
TheMadScientist420 said:
as stated may not be possible til a actuall twrp image is made
i know other devices with unlockable bl didnt have to flash twrp but run it in fast boot long enought to flash su then upon new reboot stock recov was still there but rooted
can u enable oem unlock the abd usb debugging then abd reboot fastboot?
you also can try coimmand in fastboot to either fastboot oem unlock or just oem unlock
but if u click yes in the fastboot dialouges ure device will be unlocked and wiped
---------- Post added at 09:29 AM ---------- Previous post was at 09:27 AM ----------
try my lg firmwares they normally carry metro and tmob firmwares to flash through download mode
---------- Post added at 09:31 AM ---------- Previous post was at 09:29 AM ----------
also guys as previous poster wiped system partition if im not mistaken there is a way to back up all patitions from fast boot i dont know commands but a quik google of backup device from fastboot should lead u rite then someone should be able to upload a system partition for said previous poster
---------- Post added at 09:35 AM ---------- Previous post was at 09:31 AM ----------
im waiting in the g4 threads to see if a few friends might be able to help us and u out if we can get a full device back up in fastboot then get it uploaded then there should be a command to reflash it through fastboot
Click to expand...
Click to collapse
LG might have removed the ability to boot an image without flashing it like they did with the Stylo 2 plus, and I don't think there is a kdz available yet as I been looking for one every couple of days but haven't found one.
Sent from my LGMP450 using Tapatalk
gregvolt said:
im waiting in the g4 threads to see if a few friends might be able to help us and u out if we can get a full device back up in fastboot then get it uploaded then there should be a command to reflash it through fastboot
Click to expand...
Click to collapse
Great I can still get to fastboot so if I could get an image, I could flash it.[/QUOTE]
so there is no way to make a backup through fastboot it is said that waiting for a kdz or .tot firmware and restoration through download mode with lg flash tool or lgup or support tool is best bet
do u still have download mode?
gregvolt said:
im waiting in the g4 threads to see if a few friends might be able to help us and u out if we can get a full device back up in fastboot then get it uploaded then there should be a command to reflash it through fastboot
Click to expand...
Click to collapse
Great I can still get to fastboot so if I could get an image, I could flash it.[/QUOTE]
https://forum.xda-developers.com/g4/help/one-help-fastboot-commands-t3623171
An existing fastboot does not mean that it support flashing custom recovery, check lg g6 threads to know what I'm talking about.
I want to purchase one of these from metro to use on my h20 account. If I flash a new rom will it get rid of that stupid unlock policy that makes you use the app after 90 days to unlock?
Anyone know if or when any updates even security patches will roll out for this device?
Sent from my LG-TP450 using Tapatalk
My bet is the situation is similar with G Stylo 2+.
Even with the latest 7.0 ROM, I still could flash TWRP and install SuperSU (not Magisk unfortunately).
roblox84 said:
I want to purchase one of these from metro to use on my h20 account. If I flash a new rom will it get rid of that stupid unlock policy that makes you use the app after 90 days to unlock?
Click to expand...
Click to collapse
There is no roms for this phone no root nothing yet
---------- Post added at 08:40 AM ---------- Previous post was at 08:38 AM ----------
mingkee said:
My bet is the situation is similar with G Stylo 2+.
Even with the latest 7.0 ROM, I still could flash TWRP and install SuperSU (not Magisk unfortunately).
Click to expand...
Click to collapse
Thats what it seems all the plus models eccept cricket. Seem to be rootable.
Ofcoarse no plus for me. Just the reg. So again just like g4 and many other devices i will not be able to get root
Hello Everyone,
I am using my Lenovo Tab M8 (FHD) (TB-8705F) as a monitor to control a Mavic 2 Pro drone.
When connected to the controller unit it drains the inbuilt battery of the controller, which significantly decreases operation time. I enabled developer options and under "Default USB Configuration" I selected "File Transfer". However, each time the DJI GO4 app is launched this setting is over-ridden and it starts charging the tablet.
There are a few apps available that can turn off charging if the device is rooted.
I searched all over the internet and could not find a way to root my Lenovo Tab M8 (FHD) (TB-8705F).
Please suggest any links on how to go about this process.
Some of the processes I found need the stock-ROM, but no-one has uploaded a stock-ROM yet anywhere.
So I looked at how I can make a stock-ROM. To use those method I have tried to use MediaTek SP Flash Tool (ver 5.1944.10).
Still NO-GO. It does not support MediaTek Helio P22T Tab Octa-core 2.3G platforms yet.
Now I am in a bind. Please suggest an alternative way to root this device.
Some additional details of this tablet:
Lenovo Tab M8 (FHD) (TB-8705F)
Android Version: 9
Build Number: TB-8705F_S100058_191112_BMP
Kernel Version: 4.9.117+ #2 Wed Nov 13 05:11:41 CST 2019
Hardware Version: Lenovo TB-8705F
Software Version: TB-8705F_RF01_191112
Custom Built Version: alps-mp-p0.mp1-V5.140
RAM: 3.00 GB
ROM: 32.00 GB
CPU: MediaTek Helio P22T Tab Octa-core 2.3G
Display: 1920x1200
Camera: Front 5MP/Rear 13MP
Thanks in Advance.
My bootloader is unlocked.
and I have tried these methods without much success, any suggestions on how I can make a ROM backup?
I tried these two tutorials to take a ROM backup, however, without much success.
https://android.stackexchange.com/q...nd-full-rom-without-root-for-mediatek-devices
https://forum.hovatek.com/thread-21970.html
The first issue I noticed with Wwr_MTK (I downloaded the latest version I could find: WwR_2.51_Eng) is that it did not have a drop-down option for the Mediatek MT6762.
It had options for MT6761 & 6763, but not for 6762. So it did not have a pre-configured scatter file format to choose from. So I used the option-2 and modified the Template.ini file to include it into the drop down menu options.
The second issue I came across was that Smart Phone Flash Tool (I downloaded the latest version I could find: SP_Flash_Tool_v5.1944) did not support MT6762 either. It has support for MT6761, though.
So I am not able to use SP Flash Tool to make a backup for the stock firmware.
Any suggestions on how to get past this roadblock?
You can try downloading the full firmware using the Lenovo Moto Smart Assistant.
Yaryk777 said:
You can try downloading the full firmware using the Lenovo Moto Smart Assistant.
Click to expand...
Click to collapse
https://forum.xda-developers.com/attachment.php?attachmentid=5001289&stc=1&d=1587547098
I just tried that. Problem is that the M8 (FHD) TB-8705F isnt available to choose in the list of devices. On ROMDevelopers there is mirror of {Mod edit: Link removed - Oswald Boelcke, Moderator} available which I'm unable to download because I have no membership. Maybe some can upload the file somewhere else. Guessing from the filename the URL on the official lenovo server should be https://rsdsecure-cloud.motorola.com/download/TB-8705F_USR_S100058_1911122350_V5.140_BMP_ROW.zip but since I have no download permission which is only granted through Lenovo Moto Smart Assistant I cant download it either. This is such a ****show
la_tristesse said:
https://forum.xda-developers.com/attachment.php?attachmentid=5001289&stc=1&d=1587547098
I just tried that. Problem is that the M8 (FHD) TB-8705F isnt available to choose in the list of devices. On ROMDevelopers there is mirror of ... available which I'm unable to download because I have no membership. Maybe some can upload the file somewhere else. Guessing from the filename the URL on the official lenovo server should be https://rsdsecure-cloud.motorola.com/download/TB-8705F_USR_S100058_1911122350_V5.140_BMP_ROW.zip but since I have no download permission which is only granted through Lenovo Moto Smart Assistant I cant download it either. This is such a ****show
Click to expand...
Click to collapse
Found this randomly, not sure if it's legit:
https://support.halabtech.com/index.php?a=downloads&b=folder&id=69457
Edit nvm doesn't work
i need the same
hi dear.
did you get any chance to root it.
please help i need to root the same device
Yaryk777 said:
You can try downloading the full firmware using the Lenovo Moto Smart Assistant.
Click to expand...
Click to collapse
Please excuse the late reply to this thread. I was "locked-away" from my desktop computer as I had traveled out of state and a country wide lockdown was imposed here in India, right after I left--which was close to two and a half months--we were not allowed to travel beyond our neighbourhoods on most occasions, forget between cities in the same state, or even between states. It was a heavy handed lock-down of the entire country. I had left the tablet back at my hometown, so I could not pursue rooting it further for this duration. Just got back two days back and am going through the replies.
Yaryk777 is correct. I just checked (and downloaded) the stock firmware available through Lenovo Moto Smart Assistant (LMSA), which I did.
Not sure how to go about rooting the device from here, if anyone can suggest how to root a Mediatek device when a stock firmware is available I would really appreciate it. I had links to a few methods, but have forgotten them now since I have been away. I tried the two methods mentioned in my earlier post, and both did not work.
TWRP does not have a supported recovery for this device.
Any suggestions how to go about it?
Ashok.Vardhan said:
Any suggestions how to go about it?
Click to expand...
Click to collapse
You need to copy boot.img into your tablet and patch it with magisk. Then flash patched boot file. That's all
How do you do that?
Yaryk777 said:
You need to copy boot.img into your tablet and patch it with magisk. Then flash patched boot file. That's all
Click to expand...
Click to collapse
How do you flash the patched boot file then?
I bought the same tablet to replace the 2013 nexus 7 I have running in my honda fit. For the lenovo to work I need the tablet to support otg charging. On the nexus 7 I installed timur's kernel to make that work. On this as far as I can tell, I need to update a flag in the kernel per these docs, https://android.googlesource.com/ke...-marshmallow-dr/Documentation/usb/msm_otg.txt (search for ID_C in the ACA section). Any help would be appreciated on accomplishing that.
Thanks,
Peter
Ashok.Vardhan said:
Yaryk777 is correct. I just checked (and downloaded) the stock firmware available through Lenovo Moto Smart Assistant (LMSA), which I did.
Click to expand...
Click to collapse
What were the steps you used to get the firmware?
PyroMike said:
How do you flash the patched boot file then?
Click to expand...
Click to collapse
Flash it with fastboot from your PC..
I did it and my device is now rooted.
---------- Post added at 12:28 PM ---------- Previous post was at 12:27 PM ----------
Isrgish said:
What were the steps you used to get the firmware?
Click to expand...
Click to collapse
To answer my question you can download thru the program "Rescue and Smart Assistant" from Lenovo on the rescue tab.
Isrgish said:
Flash it with fastboot from your PC..
I did it and my device is now rooted.
---------- Post added at 12:28 PM ---------- Previous post was at 12:27 PM ----------
Click to expand...
Click to collapse
I tried to root it, but it couldn't detect my device when I was in Fastboot mode. Can you tell me how you did it?
PyroMike said:
I tried to root it, but it couldn't detect my device when I was in Fastboot mode. Can you tell me how you did it?
Click to expand...
Click to collapse
Do you have the firmware?
Isrgish said:
Do you have the firmware?
Click to expand...
Click to collapse
I downloaded it through Rescue and Smart Assistant.
PyroMike said:
I downloaded it through Rescue and Smart Assistant.
Click to expand...
Click to collapse
Now to root.
1. Install Magisk Manager on your device.
2. Copy the boot.img file (this is in the firmware) to your internal storage.
3. Run Magisk Manager and select Install. Then select patch file.
4. copy this patched file to your PC and flash to your device.
That's all there is too it.
Isrgish said:
Now to root.
1. Install Magisk Manager on your device.
2. Copy the boot.img file (this is in the firmware) to your internal storage.
3. Run Magisk Manager and select Install. Then select patch file.
4. copy this patched file to your PC and flash to your device.
That's all there is too it.
Click to expand...
Click to collapse
The issue that I am having, is that my device isn't detected while it is in Fastboot mode.
PyroMike said:
The issue that I am having, is that my device isn't detected while it is in Fastboot mode.
Click to expand...
Click to collapse
In Device Manager do you see an item that has a yellow triangle (Check this while you are in fastboot)?
How do you get to fastboot?
Isrgish said:
In Device Manager do you see an item that has a yellow triangle (Check this while you are in fastboot)?
How do you get to fastboot?
Click to expand...
Click to collapse
I open up PowerShell and use "adb reboot bootloader" to enter fastboot. When I type in "fastboot device" to check and see if the tablet is there, it just says "<waiting for device>".
PyroMike said:
I open up PowerShell and use "adb reboot bootloader" to enter fastboot. When I type in "fastboot device" to check and see if the tablet is there, it just says "<waiting for device>".
Click to expand...
Click to collapse
Are on Microsoft Windows?