Hi All
I got myself a Mediapad 10 FHD two weeks ago, 1.2MHz 1GB Ram, 8GB Rom, Wifi.
It looks like I cannot get root nor custom recovery installed on the device. I have tried all I could find so far, without any luck.
What I have tried so far is:
Hi Suite Setup v1.7.00.1006
Hi Suite Setup v1.8.10.1506
custom USB driver from Team Android
standard Linux ADB driver (which work on my Nexus 4)
Windows XP in a virtual box running the driver above
standalone Windows XP computer running this drivers
toolboxes for ADB / root
Genotools v2.0
Root with Restore by Bin4ry22
auto recovery installer for huawei mediapad
root with repair
Genotools seems to work for some people, no luck here.
When I follow the steps for root manually from a Linux console I can move all the needed files onto the device but cannot change permissions or dont have access to the desired folders.
The weird thing is that that I cant access the device when in recovery at all, while access with ADB debugging is ok.
adb reboot bootloader boots the device into recovery
afterwards fastboot devices doesnt show anything
fastboot flash recovery cwm.img just waits for the device forever
Anybody have an idea what else I can try?
Recoveries in that installer are ONLY for 7" mediapad (hws7300)
Related
After installing chainfire my tablet cant boot, even recovery mode does not work. Adb has never worked with this device. Do you know any tools auto-launched from sd to reflash my device?
rk3066, Android 4.1.1
I will be grateful for any help
UPDATE:
I have found .tar file : http://intenso.de/downloads.php?kategorie=33&produkt=1367995940 3rd file. Can I push it with Linux Live CD ?
UPDATE 2:
standard adb does not work but after I'd installed Shuame everything has gone fine removed cf3d with adb
I have a rooted Google Nexus 10 tablet with Clockwork Mod and Android 4.4.2. The Google USB driver worked fine on my Windows 7 laptop and I was able to use adb to push files to my tablet. I foolishly let the automatic 4.4.3 OTA download and install. Now, my tablet is stuck in bootloop AND Windows has completely forgotten my Google USB driver and thus adb can't see the tablet, so I can't transfer over the 4.4.3 image or flash in Clockwork Mod via sideload. Yes, Clockwork Mod works great and I can boot into recovery mode. I've seen a thousand postings that all talk about stuff you do from Android like enabling USB debugging, etc, but this is all worthless when you can't boot Android. In retrospect, I wish I had kept a backup image on my SD card. So three questions:
1. How can I get the update image onto my tablet, either by sideload or adb push?
2. Is the factory image (4.4.3 (KTU84L) ) correct or since I'm rooted, am I supposed to use a modified one?
3. Would the manual update method be as simple as copying over the factory OTA to my SD Card ahead of time, booting into recovery mode and flashing?
Thanks in advance to anyone who can help.
Well, no response from anybody. I just saw this on another post: "Having USB Debugging ticked WHILE IN ANDROID has absolutely no effect on whether or not your computer can see the device WHILE IN RECOVERY OR FASTBOOT. "
This is very informative. I just wonder if "adb devices" ever shows anything if you're in recovery mode. I wonder also if the Windows 7 driver is supposed to work. I have a feeling this driver is based on communicating with Android itself, so of course it won't work. So maybe fastboot is the way to go? That's what I'll try next.
fastboot
This looks relevant - it has a ton of fastboot commands:
http://forum.xda-developers.com/showthread.php?t=2024259&page=3
I was upgrading the current Stock rom on my ZTE Nubia Z5s Mini, I went through the recovery mode to load the new rom and got a message saying that the rom installed correctly, I rebooted the device and now its stuck at the MIUI logo or if I try to load the recovery mode I get the Nubia logo just to load back to the miui logo again. I got the rom from the MIUI site its v5.
I've left the phone for over an hour hoping it was just loading up but no change, the phone heats up and even has a charger screen when plugged in.
Anyway to get back into the recovery mode to load the original rom again or any other way of fixing this? help :crying:
I've no idea how to help you with this but I'm bumping the thread because I know how you feel.
Sent from my HUAWEI Y536A1
I'm trying to flush the rom by using adb but with an issue, even thou my device is recognized as Nubia Z5s Mini in device manager it still gives a driver error "these have been installed" and in cmd adb it does not see the device.
Update : Got drivers for install from Clockwordmod website but it will only accept the drivers if I set the phone as a modem in device manager when installing them, still not recognized by adb using CMD.
Solved driver issue and qusb_download issue, ADB drivers are done through all drives in device manager pointing to the Google USB drivers and select adb interface then run CMD from within the Google SDK program folder in platform-tools to read the device.
Now using emmc but need to generate EMMCBLD.HEX & 7x30_msimage.mbn if anyone can help, I can enter adb using recovery mode but blocked from making changes in fastboot mode, currently in download mode which can see a drive H but need the two files to proceed any further.
(Q) Root Dell venue 3840,
I've tried the Guide with the boot image for 4.4.4, with 4.4.4 and I tried the tether method. doesn't work....(stuck on CWM fastboot waiting.....) tried T3, T2, T1.... please help me!!!!
how can i root? and provide clear instructions?
thanks, sorry for being an ass...
Windows or Linux?
Edit: OK windows:
social-design-concepts said:
Thread still under construction
Intel Android Devices Root / Temp CWM Session
CLICK HERE DONATE NOW : AND MAKE MY LIFE EASIER BY HELPING BUY ME AN UNLOCKED DEVICE
Tethered Temporary CWM Recovery Session :
Note : This is a Temporary CWM Recovery Session for some Intel Devices with locked bootloaders, This recovery is not installed to the devices and has to be launched from a computer ( tethered ) each time you need to access the CWM Recovery. . .
WARNING : This Temporary CWM Recovery Session is for some Intel Devices with locked boot loaders , it is not intended for installing custom roms as if the devices has a locked bootloader the device will fail to boot the unsigned images
Intel Fastboot Tethered Temporary Recovery Session Launcher download :
IntelAndroid-FBRL-01-17-2015.7z
Changes :
Fixed recovery.fstab generation should work for almost every device i can't guarantee for all devices if device uses some funky mounting point or a block device other than /dev/block/mmcblk1xx but after reviewing more than 50 different recovery.fstab from various fastboot.img i think i covered all the common intel devices.
If needed you can always include your own custom recovery.fstab in the recovery.zip
fstab generation automatically marks reserved / hidden partitions fs_types as emmc to prevent recursive mount loops this has the added benefit for devices that use traditional mount points for boot / recovery they are now able to be backed up too.
fixed adb on devices that don't have adbd as a service in fastboot.img init.rc
Note : WORKING
backing up to external storage / internal storage
unsigned .zip installation
adb root shell
you tell me
Note : KNOWN BUGS
installing using adb side-loading of zips doesn't work and breaks adb
you tell me
Generic Instructions for use better instructions coming later just wanted to get the thread up :
notes :
make sure you have downloaded and installed the adb / fastboot drivers for your device . . .
make sure you have enabled developer options / adb debugging under settings on your device . . .
make sure you have download the latest : UPDATE-SuperSU-vX.Xx.zip and place it on your internal or external_sd
1 : download and extract IntelAndroid-FBRL-01-17-2015.7z some where on your computer.
2 : double click the launcher.bat file to start , type " ACCEPT " case sensitive without quotes to continue
check that the tool is reporting as either :
DEVICE STATUS: ADB-ONLINE
DEVICE STATUS: FASTBOOT-ONLINE
If " DEVICE STATUS: UNKNOWN " please check your cable connection and driver installation under Windows Device Manager
If " DEVICE STATUS: UNAUTHORIZED " please check if your devices is displaying an authorization prompt be sure to check Always allow from this computer and then press ok
3 : select the trigger to launch the Temporary CWM Recovery Session support fastboot oem triggers are :
T1 oem startftm ( very few devices support this command , but its the original used so )
devices supported : coming soon
T2 oem backup_factory ( limited devices support this command )
devices supported : coming soon
T3 oem stop_partitioning ( should work on alot of kitkat builds )
devices supported : coming soon
4 : after selecting the trigger your device should reboot in to fastboot and begin to copy files to your device
note : if your device hangs at the waiting-for-device screen and you see droidboot CMD Waiting on your devices double check that the fastboot driver installed correctly.
note : if you see unknown oem command the trigger isn't supported by your device.
5 : The temporary cwm recovery session should be started at this point select install zip from the recovery menu using vol up / vol down to navigate and power to select
6 : select install zip from sdcard / external_sd depending on where you placed the file and select the UPDATE-SuperSU-vX.Xx.zip you downloaded earlier
7 : confirm the installation
8 : after install completes reboot your device
note :
some devices have limited space under /system and the supersu app wont install
if you don't see the supersu app on your device attempt to install it from the playstore
more than likely the su binary installed correctly but there want enough room on the device for the app.
This recovery uses the CWM Recovery @vampirefo built for the Dell Venue 8 3830 NoModem original thread : Dell Venue 8, CWM, unsecure boot/recovery
CLICK HERE DONATE NOW : AND MAKE MY LIFE EASIER BY HELPING BUY ME AN UNLOCKED DEVICE
Click to expand...
Click to collapse
T3 don't be in a rush! It says failed but then will load anyways. Wait for it! Use the very first link here. To root ¿ well when in recovery, flash superuser zip. Wait for it! Reboot from the cwm menu. In windows you can leave the device on normal and when you execute the launcher bat it'll put the tab in its proper mode. Just choose T3 and flash super user zip and then reboot.
it's android. i am using a windows 7 machine...
it boots into droidboot and just sits at cmd waiting.... i waited about 10 minutes. i am missing a step. can someone create a youtube video to follow by? i am willing to donate 10 bucks. thanks
mrazndead said:
it boots into droidboot and just sits at cmd waiting.... i waited about 10 minutes. i am missing a step. can someone create a youtube video to follow by? i am willing to donate 10 bucks. thanks
Click to expand...
Click to collapse
Sorry I didn't get back sooner , the issue is the fastboot driver installed as an adb driver seems to happen to most Intel devices.
Anyways with the device booted into droidboot open windows device manager select the adb device and right click and update driver software. Select browse my computer. select let me pick. then select the bootloader driver .
No donation required gotta get back to playing with my little girl i'll add pics later.
ok thanks man, pics will help me, i'm not too bright.
i will try that. as the device is waiting on droidboot, i will open device manager, and load the driver (where can i download this driver?)
Thanks for trying to help me guys. I give up. Too hard.
Yes! I did it! the social concepts step was what i was missing... thanks man i am rooted
Perfect!!
justlovejoy said:
Windows or Linux?
Edit: OK windows:
T3 don't be in a rush! It says failed but then will load anyways. Wait for it! Use the very first link here. To root ¿ well when in recovery, flash superuser zip. Wait for it! Reboot from the cwm menu. In windows you can leave the device on normal and when you execute the launcher bat it'll put the tab in its proper mode. Just choose T3 and flash super user zip and then reboot.
Click to expand...
Click to collapse
I follow all the steps and I sucessfull root my device (Dell Venue 8 HSPA+ 3830-A30P)
Tks!!!
Here is full rooting method which i share with you from Dell Venue 8 3840 Manual. I hope this is easiest and result-oriented method:
Download and install the Intel Phone Flash Tool Lite on your PC. Also download the venue_3840_droidboots.zip.
Run Intel Phone Flash Tool as administrator and connect Dell Venue 8 to PC using OEM USB cable.
Browse and choose venue_3840_droidboots.zip file.
Select ‘1-502_droidboot_and_firmware.xml‘ from the drop down menu and click on start.
Reboot Dell Venue 3840.
Hi guys,
i'm reading for quit a week now in this forum. And i have to say there are a lot of good informations and "how tos" for every error which can pop up on a nexus 10 .
For more than a week i try to install Ubuntu Touch on my Nexus 10 16GB.
My first way was to use the "step by step" instructions from ubuntu with a Ubuntu machine.
So i installed ubuntu via parallels on my Mac, installed all tools and hit the command for install ubuntu touch.
But after a few pushes of .img files i get an error and my nexus only boots into a chip icon with a crossed circle.
I googled the error and somebody said this is because ubuntu installs on kitkat only. After this i installed kitkat 4.4.4 with fastboot on my android and tried it again.
But when i get into the bootloader with "
Code:
adb reboot bootloader
" and than hit the command for installing ubuntu
Code:
$ ubuntu-device-flash touch --channel=ubuntu-touch/devel/ubuntu --bootstrap
i get the error "adb can't find a devices." And thats it.
So i started to look for solutions for this error, but adb kill-server didn't work and putting the id on the adb list didn't either.
I looked up other ways to install ubuntu on my nexus 10. And a common way is to dualboot ubuntu.
Ubuntu created a "how to" for dualboot also.
I followed this instructions and the script runs till the end. But after rebooting only SuperSU is on my android installed.
Ok next dead end.
But on my search for methods to get ubuntu touch on android devices, i found the ubuntu touch preinstalled section. And there were images with manta in it. Ok that looked nice. I searched for ways to install ubuntu with this img. But all ways need a .zip Ubuntu Touch version. The most links for a .zip img run into a 404.
So my question is:
What is the best way to get ubuntu touch work on my nexus 10 in the year 2016.
The most posts are from 2013 and shows instructions, for the Ubuntu Touch developer preview.
thx
links because this is my first post.
developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/
wiki.ubuntu.com/Touch/DualBootInstallation
cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/current/
Any solutions?
I'd see what's going on that you can't use ADB first, your device SHOULD connect when in recovery, but you should add --device=manta to your ubuntu-device-flash command so that you install the correct image for the nexus 10. You can also reboot into fastboot and use --bootstrap at the end which will await a device in fastboot to be connected.
Some additional questions:
- Have you enabled ADB on this device before and has it worked?
- Have you recently changed USB cables if it has previously worked? It could easily be a cabling issue.
- Does the command "adb devices" show anything? even if it shows a device with the info "?????????????? unauthorized" <--This means that your system is missing udev rules to allow a standard user access to ADB.
You can use rootstock-ng to install ubuntu touch.
Also, are you in recovery when running adb commands?