Hi All !
I have a Samsung Galaxy Note 10.1 GSM 3G tablet [N8000 model]. Right now it comes with stock Samsung Android 4.1 and stock Android recovery.
I have a trouble installing ClockWorkMod and root it.
What I did ?
1. Installed Samsung USB drivers + ADB + fastboot + Odin.
2. Enabled USB debug
3. adb devices
E:\Smartphones\Android\GalaxyNote_10.1\ADB_Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
4107764d436ccf47 device
4. fastboot devices
E:\Smartphones\Android\GalaxyNote_10.1\ADB_Fastboot>fastboot devices
[empty]
5. fastboot flash recovery [imagefile]
E:\Smartphones\Android\GalaxyNote_10.1\ADB_Fastboot>fastboot flash recovery E:\S
martphones\Android\GalaxyNote_10.1\recovery-clockwork-6.0.4.6-n8000.img
< waiting for device >
...
Basically adb "sees" my device, but fastboot does not see it.
I tried this procedure when Android is booted ans also when it is in "download" mode.
Host is: Windows 7 x64, Intel Core i7 4770. I have installed
Another problem: Odin 3.0.9 sees my device, and it does not accept *.img files from CWM, but requires .tar instead. Why so ?
Any ideas ?
Please help.
-Technologov
Related
I've been trying to root with viperboy's Primetime but when I connect my TF201 to my computer it shows up in device manager only as the TF201 and not as any sort of ADB interface. I've tried all the drivers I can find including those included with viperMOD and Asus Sync. I've followed all the other instructions to the letter. Video tutorials aren't helping because they all seem to effortlessly get ADB going. My firmware is 2.13 and yes, I do have USB debugging ticked on (when I toggle it back and forth device manager does refresh but doesn't seem to connect or disconnect any devices). I've also tried adding legacy hardware and under the Android Phone category there are drivers listed from both Asus and Google for ADB interfaces among other things, but when I try any of them the device ends up with a code 10 (cannot start). I've already spent hours trying just to get ADB going, please help me if you can.
Please help!
fezir said:
I've been trying to root with viperboy's Primetime but when I connect my TF201 to my computer it shows up in device manager only as the TF201 and not as any sort of ADB interface. I've tried all the drivers I can find including those included with viperMOD and Asus Sync. I've followed all the other instructions to the letter. Video tutorials aren't helping because they all seem to effortlessly get ADB going. My firmware is 2.13 and yes, I do have USB debugging ticked on (when I toggle it back and forth device manager does refresh but doesn't seem to connect or disconnect any devices). I've also tried adding legacy hardware and under the Android Phone category there are drivers listed from both Asus and Google for ADB interfaces among other things, but when I try any of them the device ends up with a code 10 (cannot start). I've already spent hours trying just to get ADB going, please help me if you can.
Click to expand...
Click to collapse
I hate to sound like a noob, but I am having the same problem!!!!
I went through the developer forum and found a response from "Ciddy", on the matter, this is the link { http://forum.xda-developers.com/showpost.php?p=21049320&postcount=89 } , this seemed to work for several other people, but not me.
This is what happens:
1. Uninstall Asus Sync (BTW Asus Sync does not detect the TP for me either).
2. Hit Win+R, enter "devmgmt.msc" (no quotes), brings up device manager.
3. Connect the prime, when it shows up in device manager, select it and hit Del.
Then search for new hardware and install the supplied drivers.
4. After the first reboot of the prime, check the device manager, it should show Asus MTP device [ THIS IS WHERE THE DEVICE MANAGER DISPLAYS Transformer Prime TF201, NOT Asus MTP device] with a notification; update its driver from the Viper pack.
ADB does not detect the TP in command promt. Windows 7 64x. Everything is updated, I have ADB from rooting HTC's and several other android device's. I have reset the TP to factory default's twice. and I have read and read, and have not found anything, PLEASE HELP!
** PS. I am only able to transfer files with Windows Explorer.
*** Calling Asus Support was pointless, they aren't even familial with ADB.
I have the Android SDK/Eclipse loaded on my machine so ADB is fine for me, of course. So, cannot help in your situation.
I wonder if you have considered downloading the Android Terminal Emulator from the market and just entering your commands directly on the Prime? The first time I rooted a phone, that's the way I did it, since I had no clue what ADB was. Not a permanent solution to your problem, but perhaps it can get you by for now.
Of course, I may be missing something as to why this won't work...
Edit: I read up on the TPSparky root and Viperboy's tool ... pretty sure at this point that what I am saying above will not work.
Resolved
I resolved the issue. There is still something blocking me from ADBing into the tablet with my Windows PC but I tried on an Ubuntu box and it worked perfectly. I am now successfully rooted.
How did you solve it?
yoinjo said:
How did you solve it?
Click to expand...
Click to collapse
I used a computer running Ubuntu. Never got it working with my Windows laptop.
I installed http://forum.xda-developers.com/showthread.php?t=1426502 drivers and now my TF201 shows under Android Devices (Asus Transformer Prime ADB Interfaces). ADB however still returns error: device not found
So I've solved the problem too.
I've used an old 32bit XP computer with 2.0 USB
I had that problem....i sovled it.......it was me...i forgot to go into settings on the TP and under dev options make sure USB debugging is checked.....after i did that everything went smooth
Sent from my Transformer Prime TF201 using Tapatalk
I'm having a similar problem. I've spent the last three days on-and-off trying to get this thing to show up in ADB.
So far, I've tried using both Ubuntu and Windows 7 (both x64), both detect the device and Windows shows it in Device Manager as "Asus Transformer Prime ADB Interface" - using the Univeral Naked Driver Beta 0.6.
Unfortunately, when I do adb devices, all I get is
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
It's probably worth noting that I previously rooted using mempodroid but (like an idiot) didn't install RootKeeper and when I got the OTA from 9.4.2.11 to 9.4.2.14, I lost root, and haven't been able to make it show in adb ever since.
Can anyone shed some light on this issue? I'm rather missing root.
Any update on this?
When having started the tab normally it gets recognised with device id.
When in fastboot mode - nothing
I installed several driver but the tab does not get recognised (2PCs win7)
YodaDaCoda said:
I'm having a similar problem. I've spent the last three days on-and-off trying to get this thing to show up in ADB.
So far, I've tried using both Ubuntu and Windows 7 (both x64), both detect the device and Windows shows it in Device Manager as "Asus Transformer Prime ADB Interface" - using the Univeral Naked Driver Beta 0.6.
Unfortunately, when I do adb devices, all I get is
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
It's probably worth noting that I previously rooted using mempodroid but (like an idiot) didn't install RootKeeper and when I got the OTA from 9.4.2.11 to 9.4.2.14, I lost root, and haven't been able to make it show in adb ever since.
Can anyone shed some light on this issue? I'm rather missing root.
Click to expand...
Click to collapse
i got here same problem, any progress on this one? did you already found a way to fix this issue? thanks.
YodaDaCoda said:
I'm having a similar problem. I've spent the last three days on-and-off trying to get this thing to show up in ADB.
So far, I've tried using both Ubuntu and Windows 7 (both x64), both detect the device and Windows shows it in Device Manager as "Asus Transformer Prime ADB Interface" - using the Univeral Naked Driver Beta 0.6.
Unfortunately, when I do adb devices, all I get is
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
It's probably worth noting that I previously rooted using mempodroid but (like an idiot) didn't install RootKeeper and when I got the OTA from 9.4.2.11 to 9.4.2.14, I lost root, and haven't been able to make it show in adb ever since.
Can anyone shed some light on this issue? I'm rather missing root.
Click to expand...
Click to collapse
Sorry for asking an obvious question but are you in recovery when you are trying to do adb? If you are then download the nvflash file from dev thread, unzip it, open the folder until you see the adb.exe file.
Press and hold shift on the keyboard, right click in the window and select command prompt here.
Now do adb devices it should show up.
I am having the same problem. I have tried all available drivers on internet from number of forums. Still no luck . I have also tried from Windows 8 64 Bit and Windows 32 Bit laptops. From the same laptop, I was able to connect my Xperia U and it showed under "adb devices". What am I missing? I need to install custom ROM. Please help.
Did anyone solved this problem? I have Win 7 64-bit and have been following a thread on installing Crombi-KK
After adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard, Hairybean TWRP was installed and now i need to boot into fastboot
but adb is no longer working.
I tried reinstalling drivers for TF201 but no adb access.
update1:
Ok. I managed to solve the first problem with no ADB access. In recovery I clicked to Reboot, and clicked System. While system was rebooting I was holding Power Down and got into fastboot mode. I lost ADB access but apparently still have fastboot access so I have proceeded with the instructions to flash blob
fastboot -i 0x0b05 flash recovery ne0zone75_tf300t.blob, then
fastboot -i 0x0b05 reboot-bootloader
In recovery the instructions say format next, so now I am currently formatting, so I will update everyone who need this.
I still don't know why I lost ADB access which I had. Some people here suggested ubuntu but I don't have it.
After formatting I will need ADB to push crombi to device, but I twrp recognizes SD card so if I don't get ADB access after formating I will
try to copy crombi-kk to SD card and then flash it from recovery. I will write what happened when formatting is done.
update2:
After format which took 30 minutes I suddenly have ADB access. Wtf??? Anyway I pushed crombi-kk zip on the tablet and flash it. After 5 minutes of flashing everything working great. Will send a donation. Tablet with stock 4.1.1 was slow 4.4 is great. Thanks everyone who made it possible.
Hello. I have a sony tablet s wifi only, which had rooted ICS, installed with condi's AIO.
Today it got stucked on boot screen, so after many tries of soft reset I went to recovery mode(which btw is rev.29 <3e>) and wiped all data.
Now, I'm trying to install a new software using AIO and Flasher but the app gets stucked on this message:
Code:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Please! Can someone help me?
bycxc said:
Hello. I have a sony tablet s wifi only, which had rooted ICS, installed with condi's AIO.
Today it got stucked on boot screen, so after many tries of soft reset I went to recovery mode(which btw is rev.29 <3e>) and wiped all data.
Now, I'm trying to install a new software using AIO and Flasher but the app gets stucked on this message:
Code:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Please! Can someone help me?
Click to expand...
Click to collapse
1. recovery.
2. make sure that you have correct adb driver installed.
3. download prerooted doubleFLASH fw from my signature.
4. flash via AiO - flash custom [straight from recovery] option.
br
condi
message
condi said:
1. recovery.
2. make sure that you have correct adb driver installed.
3. download prerooted doubleFLASH fw from my signature.
4. flash via AiO - flash custom [straight from recovery] option.
br
condi
Click to expand...
Click to collapse
Thank you, condi, for your answer.
1.Recovery - can reach it - rev.29 <3e> with some errors becuase of the system and data wipe.(errors like: "E:Fail to read boot logo flag" , "E::Can't open /dev/block/mmcblk0p5(No such file or directory)" , "E:Can't mount /cache/recovery/command" , "E:Fail to mount /sdcard(No such file or directory)" );
2.adb is installed using "Sony Tablet ADB Driver Automated Installer", Composite Adb Interface in recovery and looks fine;
3.
4.Well , here is the real problem. AiO is displaying this
Code:
[*] Enter recovery (power + vol-up) and run _hack_recovery.zip
Wait for assert error..
The problem is that as you can see from "1) Recovery errors", my memory card can't be mounted so I can't use that _hack_recovery.zip from recovery. Also I don't have that hack_recovery file.
Here is a screenshot with the recovery screen, dropbox link: /u/43085866/20130223_140402.jpg
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)
(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.
Hello,
I tried to flash the viper one x+ rom on my device but it turned out terrible. I folowed the process but finally i couldn't flash the rom i don't know why. After a few tries my phone started to not get signal and i couldn't turn on wifi. Somehow i made it work but after that i got a very stupid idea. I wanted to copy the files of the rom on my phone using the venom recovery (TWRP). Now there is no OS on my phone and from my storage everything is missing escept the TWRP folder. I thought there will be my backup but it disappeared. Can anyone help me please?
http://forum.xda-developers.com/showthread.php?p=35897865#post35897865
this post might help you a bit
read post #4
also try to search hasoon toolkit to help you fix you prob
:fingers-crossed:
It didn't work. When I'm trying now it sais that my phone is not connected but it must be connected because I could flash the recovery.
so my computer is recognizing my phone as an adb device but the adb sideloader can't find the device. And writes this: * daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
i dont know what to do :/
I made it! Using just cmd. If you put the rom in the sdk platform tools and start there a cmd and in twrp recovery on your phone go to advanced adb sideload start it and in cmd write adb devices it should write that your device is in sideload then write adb sideload <rom name>.zip (that must be put in the sdk folder) and it will sideload your rom. If adb devices cant find your phone or it writes that it is in recovery reply the command a few times until it writes sideload. After that you are ready to go. I hope it will help somone.