[Q] Temp Rooting - You must do this first - Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting

I have a problem with downloading the Step 1 and Sep 2 files.
1. Install the ADB drivers, using my other thread here (WINDOWS ONLY)
2. Make sure you have the Android SDK installed and have access to adb
3. Open up a command window (Windows key + R, type cmd and hit enter)
4. Type, with your tablet plugged in:
Code: adb devices
Your device should appear. If not, repeat steps 1-4 until it does. You may need to restart your computer
5. Download Step 1 and Step 2 Note: (this link seems not working)
what kind of files are these and is there an other way of getting them?
Kind Gegards Edwin
------------------------------------------------------------------------
I took some time to finally get the files and working (or trying) to root my Archos 101 G9 Turbo.
An other thing everybody must know is that when you have Ice Cream (pre) installed on you tabled (version 4.04) it is wise to down grate to a lower Firmware.
This you can do by downloading firmware from the Archos website :
Download Archos 80/101 G9 OS v 3.2.80 (179826Kb)
Make an backup (if needed)
Boot Archos with power and volume + (recovery menu)
Delete and format system on tablet (so no firmware is on it anymore)
Make sure that you have installed the ADB drivers, using my other thread here (WINDOWS ONLY)
Boot up your tablet connected to your computer via USB-cable.
into the Recovery menu choose update firmware.
An popup on computer will appear, open the drive en copy the firmware..aos file on this drive.
Press power button on tablet so the firmware can install itself.
With this version you are able to root your tablet without any errors.
When you are done rooting you van easily do the update to Ice Cream using : clic on this
Kind Regards

the links work, scroll down to the bottom and click the big
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

have you the good win_usb.inf ?

Related

[Q] I need HELP With my Asus Memo Pad ME172V Softbrecked

Hello XDA Guys,
I have my Memo Pad ME172V broken while I was trieng to Root it and I have used the command "adb reboot bootloader"
so it went down and did not came back again
when I start it it goes directly to this screen " No USB cable connected"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and when I connect it to My PC I find in device manager uninstalled device "WM8950 USB Device"
I tried to install a driver for it it only accept Android ADB driver and APX driver but not running as one so I can not use ADB command with it or APX mode
After I install the driver the logo on the screen changes to a green android man with a yellow helmet and written "Ready for download"
I tried everything I know till now
Using power and volumes button in many different combinations
also tried to use Easyflash
changing the USB windows Driver
but no luck at all
PLEASE HELP ME
Thanks
Same issue here man - a friend has given me theirs to try and fix. Did you sort it out?
I've tried multiple Fastboot drivers, but fastboot devices doesn't see anything.
Any Help From XDA Profissionals
Hey Guys, any one here Can help Me
I am not an expert, but does the device still recognise external SD?
If so, maybe this will work:
1. Download a stock util from here https://www.mediafire.com/folder/23ycdy8i4f8mu/ASUS-me172v
(I previously used http://www.mediafire.com/download/3rn6cnzh95va6np/SD_RESTORE_UTIL_20130724_STOCK.ZIP)
2. Format external SD in FAT32 (so at least 4GB microSD card)
3. Extract contents of the stock util zip to the root of the SD
4. Put SD in the device and hope it'll boot from there, so you can restore a previous flash.
Maybe the device has to be rooted for this to work, in that case look here: http://forum.xda-developers.com/showthread.php?t=2216390&page=27 and search Google for Me172vRootUtil_v0.1.zip
I hope this works, and if not, maybe someone else can help you!
hi guys..
same condition.anyone has solve it..? device was working but i only went to fastboot mode then "ready for download"..

How to get Android 4.4.4 on your Nexus 5

In this tutorial we'll show you how to manually install the Android 4.4.4 OTA file on your Nexus 5.
When a new Android update is released it never takes long to appear on the Google Developer's page as factory images and binary files. Using these generally means wiping your device though, so waiting for the over the air file to appear is a better option for some. However, waiting for it to arrive can take days, so flashing it manually is a much quicker option. Flashing an OTA file also means that all of your data and apps are untouched, along with any custom recovery or root. Here's how to do it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Prerequisites:
To do this process you need a couple of things:
Download - > ADB Tools installed on your computer (direct download).
Download - > Android 4.4.4 update for your Nexus 5 (direct dwonload from Google)
:highfive:
Now, you're getting the KTU84P firmware update specifically for a Nexus 5 running Android 4.4.3 KTU84M. If you do not have this installed already (go to Settings > About Phone > Build Number to check), make sure you get it first.
Once you've downloaded the firmware to your computer you'll want to rename it something convenient like Android-444-OTA.zip and move the zip file to the same folder that ADB Tools are in. Ensure you have USB Debugging enabled in Developer Options first and as always, if you're at all concerned, back up your apps and data beforehand just to be safe.
How to install Android 4.4.4 on the Nexus 5:
1. Turn off your Nexus 5.
2. Press and hold Volume Down and Power until you see the Fastboot screen.
3. Use the volume buttons to highlight ''Recovery mode'' and press Power to confirm.
4. Using the volume buttons again, highlight ''Apply update from ADB'' and press Power.
5. On your computer, hold Shift and right click in a blank area of the ADB Tools window (in Windows Explorer). Select ''Open command window here''. This will open the command prompt window.
6. Connect your Nexus device with a USB cable.
7. Go to the command prompt window and enter the following (using the file name of the OTA zip, whatever you chose to call it):
adb sideload Android-444-OTA.zip
8. Wait for the install to complete and your Nexus 5 to reboot.
If you have any issues, you can then do a factory reset before restoring your apps and data. Post A Reply And Tell Us its Working or Not ? :fingers-crossed::fingers-crossed:
Warning :Dont Copy This Post

[Q] Help with nextbook nx868qw8g

Hello everybody,
want to ask your advice in re: following issue
I am going to use nextbook NX868QW8G tablet as an embedded advertisement solution ie it should start when external power gets plugged in. I can find a normal tech desc of this model in the internet even on the official site.
It have almost the same look&hardware as NX785QC8G availabe at wallmart but have slightly another cpu mtk8382 and embedded 3g modem which was the decisive factor since we need tablets to be updated remotely.
Here are system settings:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have done the following:
1) rooted device via cydia impactor - root check apps from gplay are saying its rooted now + it has auto instaled chainfire SU to the tablet. For some reasons cydia impactor thinks its HTC ONE X. I have installed a PdaNetA4150 and it also considers it as HTC phone. I have tried to install drivers for nextbook8 I have found in internet but window doesnt recognize them as appropriate. At the moment device is recognized as unknown MT65XX Android phone
2) run adb reboot-bootloader
3) run fastboot oem unlock
4) run fastboot oem off-mode-charge 0
I have tried doing it manually and through cydia impactor but in both cases the command thread for #3 and #4 seems to be in an infinite sleep - just displays "..." in command line shell and cydia impactor simply gets frozen for a couple of minutes then throws timeout exception.
I think its waiting my input after #3 however the screen remains black and it does nothing when I press on vol up/down/power buttons. Fastboot prints "OK [X sec]" when I call fastboot reboot from another shell window.
In regards to the adb drivers and etc - device is visible through both 'adb devices' and 'fastboot devices' commands. For some reasons
Please advice in which direction to seach and digg.
Any help will be highly appreciated,
Max

I lost the TWRP Recovery!!

Guys, I installed the OS lineage on my Sony Z2 D6543. Perfect, except that in this process I lost the recovery, I used TWRP, now I have the 7.1 Nougat android, which is a good one. But I can not access recovery anymore. And do not even root on my device. Do you have any solutions for my problem? If so, I wanted to kindly pass the step by step, because I'm still kind of "Noob" in these processes. Thank you very much in advance!
First thing, reboot and login to recovery with pressing volume up button (not volume down).
If the above mentioned step didn't work for you then you can go further a flash a recovery image using "Minimal ADB Fastboot".
1- Make sure you have installed Sony Xperia Z2 D6503 PC drivers in order for your device to be recognized as an ADB device.
2- Install "Minimal ADB Fastboot" and make sure you make a desktop shortcut to make things easier.
3- Download a TWRP image from the official website.
4- Rename the image to "recovery", right click on the minimal ADB shortcut and open file location then move the image you've renamed to the folder.
5- On your device, go to settings/ about phone / click build number 7 times /step back, open developer options and enable USB debugging.
6- Open "cmd" and type the following command :
adb devices (to make sure your device is recognized)
7- Turn off your device and remove USB cable.
8- Press the power button with volume up simultaneously. (Blue LED indicate you're in Fastboot mode)
9- Type the following command :
fastboot flash recovery recovery.img
10- Power off and see if your device boots to recovery with either volume up or down.
Thank you for your attention and willingness to help. But in my case did not work, when I press the power button and volume + it turns on the blue led, but does not enter fastboot, it is only restarting. Until I release the key and it reboots and enters the system normally. I'm sending some prints of the fastboot program. If there's anything else I can do, thank you in advance!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Doogee S88 pro - <waiting for device> during fastboot commands

Hello everyone!
This is my first post here so I hope everything I try to explain is according to the rules as far as I read it.
I need to root my Doogee S88 pro mobile since I need test and develop some AR stuff. The standard apps are not accesible by the playstore so I need to bypass that. For doing that I need to root my phone (this is what I read at least).
So... I installed the doggee usb drivers from their website for my phone, usb debugging is activated and OEM is activated as well. I downloaded the most recen platform tools and the usb-cable should be fine since I find the phone with
Code:
adb devices
I execute the following commands:
Code:
adb devices
adb reboot bootloader
fastboot devices
I get the small Fastboot text in the lower left corner. Then if I try to execute
Code:
fastboot flashing unlock
or
fastboot flashing unlock-critical
I only get back <waiting for device>
As said I installed the usb drivers provided by doogee. But: In the device manager I can see the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also I periodically (every 10 seconds) hear the sound as if a usb-device is disconnected. Afterwards the device manager refreshes the list.
So... it is a driver issue? I tried updating the drivers but picking manually the folder where driver files are located leads to no result. Automatic search as well. If it is a driver issue - where can I get the appropriate driver files? Thank you for any hint.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Unfortunately that didnt help either. Dunno... What I did was: I switched to my Lnux OS and over there it worked out of the box (only needed to install adb and fastboot from repositories).

Categories

Resources