Database Users

Help!! messed up updating cyanogenmod! Bricked??

I really need some help please! I think I may have done something very bad. I have a tmobile mytouch 3g. I was trying to update from cyanogenmod 4.2.1.9. I was using a darkstar theme from ringer nation.
Here’s where I think i screwed myself. I am fairly new to all this stuff so I was trying to find a guide on how to update the mod and instead of doing it properly by adding the files to the sd card, doing a wipe, and then installing everything. I instead messed up and did an install of sapping.nbh and basically followed all the directions to originally root the phone. Including formatting the sd card and everything. When I realized that i was doing this all wrong I was still able to load my os and everything seemed ok. I was getting a sd card error that said that the card was blank or had an unsupported file system, but I was able to mount it so, I erased everything off the card and then put the cyanogen update and the drc83_base file and attempted to load into recovery and do the update.
I loaded into and did a wipe. I attempted to follow the instructions on upgrading from the cyogen page. (God I wish I had found that page first) But after I did the wipe and I attempt to Apply any from SD I get “error: sd card is not mounted”
When I attempt to reboot the phone it goes to the tmobile mytouch logo, THEN it goes to my them logo from Ringer Nation, then it just goes to a black screen I let it sit there for like 5 minutes to see what would happen, but nothing. So I took out the battery and sim. I can get into recovery though so I hope that someone can help me figure out where to go from there.I thought that since I had done a wipe that the theme would have been deleted as well? This is weird.
I did do a nandroid backup before. Hopefully that will prove to be helpful. Sorry for the long post, but I wanted to dump as much useful information about this problem so that hopefully someone will be able to help! BTW I'm using a mac with the latest snow leopard software.
As I am desperate for help, please reach out to me via aim – icolinirie or via email
Thank you in advance for everything. This is a great community, and all of Cyanogen’s work is greatly appreciated!!
EDIT: I really need some help! Here's some more information. I have a Magic 32B. Its running Cyanogenmod v1.4 + JF Recovery.
From what I have gathered I need to adp into my phone in order to get it to mount. Anyone know how to do this on a mac. I am trying, but I don't fully understand. I have created the .bash_profile from terminal and typed the following "export PATH=${PATH}:/Users/itunes/Documents/android-sdk-mac_86/tools" which is the path to the tools file in the sdk. I am just stuck at this point. I don't know what to do from here.

Hi I quote.
Install SDK utilities you need to connect your PC to your phone
You can download the full SDK from the Android Developer website for your platform
http://developer.android.com/sdk/index.html
You'll need to download the SDK appropriate for your platform and extract it into a directory somewhere. I'm going to assume you're using Windows here and suggest you extract it into a folder called
C:\AndroidSDK\
on your hard disk. You can put it anywhere you like really, but if you do you'll need to substitute it for the folder above.
Add the tools directory to your system path for easy access
In Windows it's easy to add the Android SDK Tools directory to your system path. Doing this lets you use the Android SDK tools anywhere and makes it easier for you.
On Windows XP: Go to Control Panel->System, Choose the 'Advanced' tab and then click 'Environment Variables' To do this on Vista/Windows7: Simply go to Control Panel->System and choose 'Advanced System Settings' and then 'Environment Variables'
Now that you've got here locate Path under System Variables and click Edit, then add the following to the end of the string displayed:
;C:\AndroidSDK\tools\
Then click OK until you get out of the menus.
Now that you've done this you should be able to bring up a command shell and type 'adb' and it should run straight away without needing to change path.
Please note that you can skip this step completely if you find it too complicated - however you will need to CD to the ?AndroidSDK\tools every time you open up a command prompt so it's worthwhile doing. I'm going to assume you have made the change above in all further examples as it gets too complicated really. If you're not confident in a DOS shell, I'd suggest you do a little bit of reading up on basic navigation in DOS first.
Enable Debugging mode on the phone before connecting to PC and installing the ADB driver
Menu > Settings > Applications > Developement > USB Debugging
Install the USB drivers correctly - check using "adb devices".
If you have already connected your phone to your computer before then the USB drivers are probably already loaded. If you're lucky then typing 'adb devices' in a command prompt will produce something like:
C:\AndroidSDK>adb devices
List of devices attached
XXXXXXXXXXXX device
Where XXXXXXXXXXXX is the serial number of your phone. If it doesn't produce that line, then you need to check Device Manager and ensure the device drivers for your phone were installed correctly.
If you are having issues installing the ADB driver, you need to connect your phone then go into Device Manager and check the ADB device properties. Check the following property and it'll look something like:
Device Instance Id: USB\VID_0BB4&PID_0C02&MI_01\7&293A7D0D&0&0001
To fix the driver installation problem, you need to edit the driver's .ini file and change all the references of 0C03 to 0C02, or 0C02 to 0C03 if your device property states your Device Id is 0C03.
Note: After flashing a new ROM, your Device Id may change again to either 0C03 or remain as 0C02. So you need to update the .ini file again as above to refelect the change and re-install the driver. Another known way to fix the above issue is to download and install HTC Sync - this seems to install the correct drivers.
How to use ADB
ADB stands for Android Debugging Bridge - it's a useful way of talking to your handset while it's running. ADB provides commands for copying files to and from your phone, installing packages and debugging your Android applications.
Useful commands include:
adb devices - lists which devices are currently attached to your computer
adb install <packagename.apk> - lets you install an Android application on your phone
adb remount - Remounts your system in write mode - this lets you alter system files on your phone using ADB
adb push <localfile> <location on your phone> - lets you upload files to your phones filesystem
adb pull <location on your phone> <localfile> - lets you download files off your phones filesystem
adb logcat - starts dumping debugging information from your handset to the console - useful for debugging your apps
adb shell <command> - drops you into a basic linux command shell on your phone with no parameters, or lets you run commands directly
How to use Fastboot
Fastboot is another boot method and is used to drop the phone into a safe mode to load/flash alternate roms. You need USB debugging turned on before you can use Fastboot mode - so I'd recommend you do this first (under Settings->Applications->Development->USB Debugging). You will also need to power off your phone first (hold down Power and select Power Off) and then hold down the Back+Power Buttons to start the phone in Fastboot mode. You will need your USB cable connected to be able to issue any commands and assuming your drivers are correct you should be able to issue:
C:\AndroidSDK>fastboot devices
List of devices attached
XXXXXXXXXXXX fastboot
Other commands in this mode include - we'll cover these below in subsequent sections.
fastboot boot <filename> - boots a rom stored on your pc specified by the filename
fastboot flash <partition> <filename> - flashes a rom stored on your pc, partition can be one of {boot, recovery, system, userdata}
fastboot binaries for mac and linux can be found here.
3. Learn how to use fastboot and boot a recovery rom
Download a recovery rom for your device
There are several different recovery roms available for the HTC Magic devices.
Amon_RA has created several nice recovery roms available from http://forum.xda-developers.com/showthread.php?t=530492 and get the Recovery Rom appropriate for your device - these recovery roms have Nandroid Backup and Nandroid Restore and are perfect for the average user.
You can also use Cyanogen's 1.3.1 Recovery ROM available for: PVT32A devices and PVT32B devices - this rom has some additional options for partitioning your SD card for ?Apps2SD/Swapper/etc.
Fastboot the recovery rom
Fastbooting a rom doesn't write anything to your device - it just loads it directly from your PC - so it's a completely safe way of fixing/recovering/backing up your existing rom. To fastboot a rom you need to first drop your phone into Fastboot mode and check that it's working. Now drop into a command shell and make sure the recovery image you're wanting to load is in the same directory that you're running this in. If it's called something other than recovery-rom.img then substitute that instead.
C:\AndroidSDK> fastboot boot recovery-rom.img
If you are having problems changing the directory in the command prompt, just make a copy of the command prompt .exe itself, and place it in the folder that contains the recovery rom, then run the above command.
And once again, if you have a perfected SPL which does not allow remote fastboot, you will have to fix it first.
Use the Recovery Rom to Backup your current ROM with Nandroid
Once you've booted to a recovery rom - you can use the Nandroid Backup option. If you get a 'cannot mount /dev/mkblkxxx error' when you do this then check your microSD card is inserted correctly and if so, wait a few seconds for it to register to the recovery rom correctly. If at first you don't succeed, try, try again (sdcard can take a few seconds to mount!)
You do not need to be a rocket scientist to do this.
you can use the ADB to put in recovery again by fast boot
http://forum.xda-developers.com/showthread.php?t=530492

Hey! First off Thanks for the reply! I really appreciate someone chiming in to throw some advice my way! But while reading your thread you described the instructions for windows. In this case I have a macbook pro running snow leopard.
I did download the android sdk to my documents folder and I understand that I need to execute some scripts from the terminal on my mac to get things running. But I really dont know what those scripts are or what exactly to do.
I can get into the recovery mode on the MyTouch by holding power and home when powering on. So do I open the console from the recovery screen on the mytouch and then run the scripts on the terminal from my macbook? And which scripts should I run to get the sd card mounted onto my desktop (that is what I'm trying to do). Im not too sure what to do from there either. I want to get the phone back to stock android 1.5 os so that I can root again. My sd card has to be corrupted because it keeps giving me an error saying that it wont mount when I try to do a fix file systems or try anything from that menu. What to do??

What!
can you get in the recovery?

Yeah I can get into cyanogen v1.4 recovery. I'm just stuck from there.

Ok ok If I understand this correctly then you are not briced. you do not have any imag on your phone.
if you do not have anything nadroid recovery on sdcard you must enter a new ROM on the sdcard and flash it
remember full wipe.!

Yes this is what I believe I must do. But I need to either find a way to mount my SD card from the phone while it is in recovery mode (cyanogen v1.4). That's my problem.. I wish there was an easier way to get it mounted onto my mac from the recovery screen. I think I'm just going to go to best buy tomorrow and get a micro sd card reader and maybe another sd card just in case.
Once I have done that though. What files should I put onto the sd card in order to flash it back to original factory android 1.5.
What do you think?

Good idea
I have never used cyanogen v1.4 recovery
I use the recovery-RA-sapphire-v1.5.2H.img and ther you can use USB togle in recovery mode, You must go to the store to buy the adapter that fits on your Mac, I have two adapters for your Mac, you can borrow

Yeah that's the plan for tomorrow. Thanks for the offer man. But I'm in Los Angeles, Ca LOL!! Where are you?

icolinirie said:
Yeah that's the plan for tomorrow. Thanks for the offer man. But I'm in Los Angeles, Ca LOL!! Where are you?
Click to expand...
Click to collapse
Bergen . norway.
http://maps.google.no/maps?f=s&utm_...o-google-gm&utm_medium=ha&utm_term=google map

OMG! WOW! Looks like a beautiful place! LA is a concrete jungle but beautiful in its own respects. Bergen looks like a very comfortable place! I enjoy finding out about these things. Maybe someday I'll visit. I'd definitely love to!

icolinirie said:
OMG! WOW! Looks like a beautiful place! LA is a concrete jungle but beautiful in its own respects. Bergen looks like a very comfortable place! I enjoy finding out about these things. Maybe someday I'll visit. I'd definitely love to!
Click to expand...
Click to collapse
it is sick cold. I'll take one picture out the window

Problems with ADB

So I'm not a novice ADB user and have used it to root at least 5 or 6 phones. I'm attempting to root my kindle fire right now and running into problems. I built a new PC since the summer and never bothered to reinstall ADB. I just downloaded the Google SDK and from my memory that includes ADB and you can usually get it going from there. I read some tutorials on how to set it up but after following them perfectly I can't get it to even start the ADB server. Anytime I type any ADB commands in it says adb.exe not found or it not being a valid command.
Any quick advice?

Get_Out_and_Push said:
So I'm not a novice ADB user and have used it to root at least 5 or 6 phones. I'm attempting to root my kindle fire right now and running into problems. I built a new PC since the summer and never bothered to reinstall ADB. I just downloaded the Google SDK and from my memory that includes ADB and you can usually get it going from there. I read some tutorials on how to set it up but after following them perfectly I can't get it to even start the ADB server. Anytime I type any ADB commands in it says adb.exe not found or it not being a valid command.
Any quick advice?
Click to expand...
Click to collapse
Download Kindle Fire Utility...
http://forum.xda-developers.com/showthread.php?t=1399889
It has a batch file that will install the necessary ADB drivers and you'll find the fastboot/adb executables in the tools directory.

That's what I thought was weird. I ran the drivers.bat, it says they're all installed and I still can't start the adb server or communicate with it. And the kindle shows up as it's supposed to when the adb drivers are installed under devices.
PS thanks for the quick response.

Get_Out_and_Push said:
That's what I thought was weird. I ran the drivers.bat, it says they're all installed and I still can't start the adb server or communicate with it. And the kindle shows up as it's supposed to when the adb drivers are installed under devices.
PS thanks for the quick response.
Click to expand...
Click to collapse
That's a new one to me. I think the adb server should be able to start even without the device attached. Maybe your original SDK install went wrong and it did something funny to your system? Sorry... I got nothing.

kinfauns said:
That's a new one to me. I think the adb server should be able to start even without the device attached. Maybe your original SDK install went wrong and it did something funny to your system? Sorry... I got nothing.
Click to expand...
Click to collapse
Don't want to sound too simple, but have you changed to the directory that adb.exe is installed in before trying to run it?

Yeah I changed the directory. I got it up and running kind of but now when I try the adb devices command it pops up as "connected devices" with nothing showing under it. The kindle fire utility also shows the adb server as not running always. Odd?

This happened to me its supposed to show up as Android composite adb interface its just a problem in that .android hidden file
Sent from my R800a using Tapatalk

Sorry I dont have my laptop with me and this happened like 2 months ago so my memorys rusty
Sent from my R800a using Tapatalk
---------- Post added at 10:09 PM ---------- Previous post was at 09:53 PM ----------
my adb_usb.ini http://www.box.com/s/e74b32cff87b7c9363fb
http://www.box.com/s/d785bcc0969b7c0999f0 -androidwin.cfg
http://www.box.com/s/da267d41c04c6284f084 -ddms.cfg
http://www.box.com/s/242c14da6a4fa8f2664d -repositories.cfg
to use these click my computer then at the search bar on the top left type in %userprofile% make sure hidden folders are sshown go to the .android folder and put these files in their. if it still doesnt work try superoneclick connect your kindle and go to the advanced tab and click update drivers
if none of this works follow the first half of this tutorial-http://www.youtube.com/watch?v=f409qNgpzSA

jeffbud98 said:
Sorry I dont have my laptop with me and this happened like 2 months ago so my memorys rusty
Sent from my R800a using Tapatalk
---------- Post added at 10:09 PM ---------- Previous post was at 09:53 PM ----------
my adb_usb.ini http://www.box.com/s/e74b32cff87b7c9363fb
http://www.box.com/s/d785bcc0969b7c0999f0 -androidwin.cfg
http://www.box.com/s/da267d41c04c6284f084 -ddms.cfg
http://www.box.com/s/242c14da6a4fa8f2664d -repositories.cfg
to use these click my computer then at the search bar on the top left type in %userprofile% make sure hidden folders are sshown go to the .android folder and put these files in their. if it still doesnt work try superoneclick connect your kindle and go to the advanced tab and click update drivers
if none of this works follow the first half of this tutorial-http://www.youtube.com/watch?v=f409qNgpzSA
Click to expand...
Click to collapse
Thanks I appreciate the help. Once I get home I'll try this and report back on how it works. I'm glad someone else experienced the same problem a d got around it.

The youtube video did it for me. I appreciate the time taken to help point me in the right direction.

TWRP freeze on SD card access - help!

Hi, I'm editing this thread.
I was browsing, and the kindle freeze, so I reboot it, and it never came back.
What I can do :
# go in TWRP
E: Cant mount /cache/recovery/command
E: Cant mount /cache/recovery/log
E: Cant open /cache/recovery/log
# see the bootanimation in loop.
What I can't do
# accessing th SD with TWRP ( freeze)
#accessing SD with pc (freeze)
# adb devices
adb shell
error : device not found
I have :
#normal cable : device manager/Android composite ADB Interface
#factory cable : device manager/Android ADB Interface
I can go in fastboot, but it doesnt help... kfu says ''offline'' but I can reboot in different mode.
#drivers are installed
I'm lost, I tried almost everything

edittt

Try uninstalling any drives that are named kindle, kindle fire, android device etc. Then reinstall them with Kfu. Dot you have fff1.4 already?
sent from my Nokia 5110

pbailey212 said:
Try uninstalling any drives that are named kindle, kindle fire, android device etc. Then reinstall them with Kfu. Dot you have fff1.4 already?
sent from my Nokia 5110
Click to expand...
Click to collapse
yes fff 1.4a.
Drivers are tested with kfu and the one came with sdk package (add kindle device manually)
I tried it on win7 with a recent pc usb2, and tried on winXP on a p3 USB1.
thanks

oVeRdOsE. said:
yes fff 1.4a.
Drivers are tested with kfu and the one came with sdk package (add kindle device manually)
I tried it on win7 with a recent pc usb2, and tried on winXP on a p3 USB1.
thanks
Click to expand...
Click to collapse
The 2 drivers might be conflicting each other. I had to uninstall all drivers related to kf and android and install them again.
sent from my Nokia 5110

pbailey212 said:
The 2 drivers might be conflicting each other. I had to uninstall all drivers related to kf and android and install them again.
sent from my Nokia 5110
Click to expand...
Click to collapse
understand.
What was your problem?
I've tested it also on ubuntu. I can barely do some stuff...
++ On xp, when I'm mounting the SD with TWRP, I can see all my folders and files in it for about 5 seconds. After the computer can't see the mass storage anymore...:crying:

oVeRdOsE. said:
understand.
What was your problem?
I've tested it also on ubuntu. I can barely do some stuff...
++ On xp, when I'm mounting the SD with TWRP, I can see all my folders and files in it for about 5 seconds. After the computer can't see the mass storage anymore...:crying:
Click to expand...
Click to collapse
I wonder if your battery is dead. Have you tried plugging it in to the wall charger that came with it for a couple hours?
sent from my Nokia 5110

pbailey212 said:
I wonder if your battery is dead. Have you tried plugging it in to the wall charger that came with it for a couple hours?
sent from my Nokia 5110
Click to expand...
Click to collapse
The battery is ok, the kindle can bootloop for ever, twrp nerver shut down, it just freeze. On twrp it has battery meter, so i'm always around 80% when I'm playing (well repairing) with it.

oVeRdOsE. said:
The battery is ok, the kindle can bootloop for ever, twrp nerver shut down, it just freeze. On twrp it has battery meter, so i'm always around 80% when I'm playing (well repairing) with it.
Click to expand...
Click to collapse
You tried going to boot normal on the fff1.4a screen right? Sorry I'm trying to narrow down your issue
sent from my Nokia 5110

pbailey212 said:
You tried going to boot normal on the fff1.4a screen right? Sorry I'm trying to narrow down your issue
sent from my Nokia 5110
Click to expand...
Click to collapse
thanks for your help, it make me think about something new.
So far, twrp IS the problem.
#1 reinstall sdk (I started from a fresh pc with winXP)
#2 open a cmd windows from sdk tools folder, not the platform-tools, just tools and run this:
android uptade adb
#3 then go to user folder c:\users\username there should be a folder named .android in there, open adb_usb.ini and add this line at the bottom
0x1949
save close
#4 update driver kindle manually from ''Kindle Fire Utility'' while its in twrp. (the one a lot of people seem to be missing after you select the android_winusb.inf file you have to (in win 7) UNCHECK the "show compatible hardware"
tickbox and select the Android Composite ADB Interface driver. if you don't uncheck that box it will install the wrong one for you automatically. )
#5 reboot kindle in recovery in FASTBOOT(with a factory cable) and INSTALL CWM with KFU!!!! it wont freeze anymore !!!
#6 -boot to CWM
- test adb with "adb devices"
- open shell -> "adb shell"
- issue "echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file"
- now the sdcard should mount to the computer
- windows will probably respond that the volume/device needs formatted before using it
#7- choose quick format and let it format it as fat32 block size 4096
#8 drop a rom in sd card
#9 reinstal twrp?
#10 intall fresh rom

Lol and I was talking to you like you didn't know what you were doing. Now that you have adb working, put kfu in the same directory and use that to try and boot normal
sent from my Nokia 5110

pbailey212 said:
Lol and I was talking to you like you didn't know what you were doing. Now that you have adb working, put kfu in the same directory and use that to try and boot normal
sent from my Nokia 5110
Click to expand...
Click to collapse
well, I have a desire Z , so the only way to root is with adb.
I started with that and I took all the information from a site to and other. I came with that.
with CWM I can finally format cache, and data ( twrp freeze).
I can now put ROM.zip to the sdm but can't install it (error status 7).
I'll try to install with TWRP, and see.
If its not working, I'll try the hardware method with kindle kit and ubuntu.
next step>> garbage! (or selling it for parts)

I probably miss something :
- I reinstalled TWRP
- Tried to install : jandycane_otter-v1.7.2.zip
Got this message :
symlink : some symlinks failed
E:error in /tmp/sideload/package.zip
(status7)
FAILED
maybe I need the stock rom?

oVeRdOsE. said:
I probably miss something :
- I reinstalled TWRP
- Tried to install : jandycane_otter-v1.7.2.zip
Got this message :
symlink : some symlinks failed
E:error in /tmp/sideload/package.zip
(status7)
FAILED
maybe I need the stock rom?
Click to expand...
Click to collapse
Try downloading and transferring it again. Make sure signiture verification is not checked. Status 7 is usually caused by a bad download or transfer
sent from my Nokia 5110
---------- Post added at 09:01 PM ---------- Previous post was at 08:51 PM ----------
And you are far from a hard brick, as long as you don't screw up your partitions, or use the old version cwm that locked up the mmc chip, these things are virtually unbrickable
sent from my Nokia 5110

Well, I'm using the CWM from the kfu, I believe is the last one.
I understand that I cant flash 3.0 kernel roms.
I tried to install CM7.2 hella fire
no luck: black screen.
and I had to format again because it crashes AGAIN under twrp.
well I'm tired. I'll try again in few days.
thanks

So , I push update.zip (from kfu) to the SD, I installed it with CWM, and same problem. BLACK SCREEN on rom loading.
Then I dont have fff and recovery anymore, so go back in fastboot mode ( factory cable) and reinstall fff and CWM.
Now, trying to reinstall a rom, after a full wipe ( dalvik, factory reset, system wipe, data wipe).
black screen

[Q] ADB error:device not found

Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?

theminikiller said:
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
Click to expand...
Click to collapse
plug the phone, open a terminal as administrator/root and type
adb stop-server
adb start-server
adb devices
the last command must return your device name-id
If not there is smth wrong with your installation

The device didn't show up do you know what I could have done wrong? Do I have to turn on mass storage? Could it have something to do with my drivers, can't remember installing any... And in the device manager I see four android with a orange triangle with am exclamation mark inside.
Sent from my U8800 using Tapatalk 2

theminikiller said:
The device didn't show up do you know what I could have done wrong? Do I have to turn on mass storage? Could it have something to do with my drivers, can't remember installing any... And in the device manager I see four android with a orange triangle with am exclamation mark inside.
Sent from my U8800 using Tapatalk 2
Click to expand...
Click to collapse
No you don't need to enable mass storage, but you need to enable USB debugging from dev settings from the device. Use these drivers
https://www.dropbox.com/s/ryn7l7z0nfc842g/u8800_pc_drivers.zip

emmm... feeling kinda stupid right now... but how do i install the drivers? xD

theminikiller said:
emmm... feeling kinda stupid right now... but how do i install the drivers? xD
Click to expand...
Click to collapse
You have to install them manually from device manager.
Sent from my U8800

After i choose the folder with the drivers i only get a message saying it didnt find any drivers. Do you know why i cant install them?

Is it the same drivers when I'm using aurora ics as gingerbread roms?
Sent from my U8800 using Tapatalk 2

theminikiller said:
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
Click to expand...
Click to collapse
I had the same issue. This tutorial worked for me: http://goo.gl/OS3Vi
Hope it helps

kross666 said:
I had the same issue. This tutorial worked for me: http://goo.gl/OS3Vi
Hope it helps
Click to expand...
Click to collapse
Thanks alot! That worked perfectly, now i can start using adb on my phone xD
btw i have a question for adb... what does reboot to download mode mean? is that pink screen?

theminikiller said:
Thanks alot! That worked perfectly, now i can start using adb on my phone xD
btw i have a question for adb... what does reboot to download mode mean? is that pink screen?
Click to expand...
Click to collapse
I think its safe mode
Sent from my Impulse 4g running vPure Professional CM7.

kross666 said:
I had the same issue. This tutorial worked for me: http://goo.gl/OS3Vi
Hope it helps
Click to expand...
Click to collapse
Thank you the instructions in the link provided worked for me. I am able to see my listed by adb device command...

help
i have been trying to root my acer iconia tablet A100 for a week now, i ve tried and followed a dozen of ways. this is were it has brought me,
Device connected. Preparation for executing of the main script.
mkdir failed for /data/local/tools, Permission denied
push: tools/su -> /data/local/tools/su
failed to copy 'tools/su' to '/data/local/tools/su': No such file or directory
Unable to chmod /data/local/tools/*: No such file or directory
remote object '/data/local/tools/mempodroid' does not exist
The file "mempodroid" isn't created!
-
Not getting root!
-
Error!
-
Press any key.
please help me, what did i do wrong
thanks in advanced

jakk181571 said:
i have been trying to root my acer iconia tablet A100 for a week now, i ve tried and followed a dozen of ways. this is were it has brought me,
Device connected. Preparation for executing of the main script.
mkdir failed for /data/local/tools, Permission denied
push: tools/su -> /data/local/tools/su
failed to copy 'tools/su' to '/data/local/tools/su': No such file or directory
Unable to chmod /data/local/tools/*: No such file or directory
remote object '/data/local/tools/mempodroid' does not exist
The file "mempodroid" isn't created!
-
Not getting root!
-
Error!
-
Press any key.
please help me, what did i do wrong
thanks in advanced
Click to expand...
Click to collapse
this is not the forum for ur device..

then please tell then where is the correct forum.
i only when to this one because google brought me here, and it was on adb, which is what i am have trouble with.

Re: Adb - device not found (I had same problem) Fixed
theminikiller said:
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
Click to expand...
Click to collapse
I had the same issue updating my Nexus 7 in adb download mode device not found. You will also notice in system setting device driver is showing an error. You can download Adb driver installer which should detect any missing driver and fix the issue.
It worked for me straight away otherwise I had no way round getting to solve the problem. Fheww!! hope it works for you
Many Thanks.
adbdriver.com/downloads
---------- Post added at 05:55 PM ---------- Previous post was at 05:43 PM ----------
You may be missing the device driver when switching to USB Debugging mode using ADB Command prompt device not found.
Please download and intsall adb driver installer. It found my device and installed missing driver straight away problem fixed now I dont seem to have any issue.
adbdriver.com/downloads/
Glory be to Almighty God. Thank you!!

theminikiller said:
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
Click to expand...
Click to collapse
same problem...

[HOW TO] Root Yoga Tablet 2 [STEP-BY-STEP] [NOOB FRIENDLY]

Hi?
I'm posting this thread for all those who want to root their tablet but need a step by step guide for the same. I have condensed the information from many threads and put it into one. All the credit goes to the respective thread owners who have posted the guides. Let's begin:
NOTE: Im not responsible if you brick your device. You are solely responsible for what happens. If you follow the steps correctly it is unlikely that it will harm your device. If you face any issues you can post it here and I will try to solve them ( or someone else will). All good.
Scary stuff apart, let's begin to root your device ?
1. On your device, Go to Settings, Developer Options, and click on Enable USB Debugging. If there is no Developer Options in Settings, Click on About Phone and click 7 times on Build Number. This will give u the option.
2. Once you have enabled it, connect your device to your computer via USB cable.
3. Install the device drivers from the autoplay options.
4. Right click on My Computer and click on Manage
5. A new window will open called Computer Management, under which u have to click on Device Manager.
6. A list of devices connected to your computer will be shown on the right hand side.
If your device is listed under heading Android, as Android ADB Composite Device, then there is no need to download and install adb/fastboot drivers, and you can go ahead with the rooting process.
But its most likely your device will be listed under Other Devices. Under that it will be as MTP device or by the name of your device itself. This means you have to download and install adb/fastboot drivers on your computer before rooting it.
7. Open your browser and click on http://adbdriver.com/upload/adbdriver.zip which will download the adb installer on your computer. Run through the setup and install it. Run the program, it will automatically detect your device and install the necessary adb/fastboot drivers for it on your computer.
Alternatively, you can click on http://forum.xda-developers.com/showthread.php?p=48915118 through which you can install the same. I did it with the first method for my device.
Download and install it in [C drive].
8. Once the drivers are installed, go to Device Manager again (Step 4 and 5), and check on the list of devices. Your device should be listed under the heading Android, and showing as Android ADB Composite Device.
9. Open up C drive, there should be a folder named 'adb' under it. Open that folder and right click anywhere and open a command prompt.
U can also press 'Win+R' keyboard keys and type in 'cmd.exe' to open up a command prompt and use the cd command to come into the right folder. Once your into the adb folder in the command prompt (it should show as "C://adb>".
Type in command 'adb devices' and press enter (without the colons).
This should show you that your device is connected by the name of your chipset as Baytrail******. If it doesn't show this it means the adb drivers are not installed or ur device is not connected to the computer. Only once after it detects your device you have to go ahead with your rooting process.
10. After you have successfully completed all the above steps you are now ready to root your device.
11. Click on this link forum.xda-developers.com/showpost.php?p=57543871&postcount=1 from where you will have to download 'Intel Fastboot Tethered Temporary Recovery Session Launcher' onto your computer and extract it to some folder.
12. Download the UPDATE SuperSU zip file to your device and store it in your internal memory so you can find it easily later.
13. Now open the folder where you have extracted the Intel Fastboot Tethred Temporary Recovery Session launcher. Double click the launcher.bat file to start and 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.
It will ask for the type of recovery u would prefer to run. Options 1-4 will be TWRP recovery and 5 will be CWM. I selected the CWM recovery. So enter number '5' and press enter.
14. It will display the list of triggers to be selected for the rooting process. Select the trigger to launch the Temporary CWM Recovery Session.
The list will be as follows:
T1 oem startftm ( very few devices support this command , but its the original used so )
T2 oem backup_factory ( limited devices support this command )
T3 oem stop_partitioning ( should work on alot of kitkat builds )
T4 oem stop_partitioning ( probably works on all devices that are supported (Jellybean , KitKat , Lollipop)
15. Select trigger 'T4' if you have upgraded your tablet to Lollypop Android 5.0.1. After selecting the trigger your device should reboot into 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.
16. The temporary cwm recovery session will start at this point on your device.
17. Select install zip from the recovery menu using vol up / vol down to navigate and power to select.
18. 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
19. Confirm the installation.
20. After install completes reboot your device*through the reboot device option in the recovery menu itself.
21. It's going to take a while for the device to reboot. 'Android is upgrading' window will pop up once the screen gets on. After the boot is complete open all apps to see Super SU installed in it.
Now you have successfully rooted your Yoga Tablet 2. Enjoy ☺
NOTE: Follow all steps carefully and correctly so it becomes highly unlikely that you may brick your device. Make sure there is no powercut to your computer during the rooting process if you are not using a laptop or a UPS for your system. You can post any queries or questions in the thread.
All credit goes to the original thread owners, social-design-concepts, workdowg for helping all yoga tablet users to be able to root their devices.
A lot of work has gone into making this NOOB friendly step by step guide. Hit thanks if this helps you. Much appreciated. Have fun rooting.☺
Posted from my Rooted Lenovo Yoga Tablet 2 (830LC).

Much appreciated for this noob guide.

Thanks for the tutorial.
I did all the steps as you said. I am at step 15 and selected t4 and then the command prompt showed waiting for device and then my tab rebooted itself and then came to a fastboot mode.
Now n TAB its showing error that "E: No valid installer medium found"
now when i press the volume keys, the boot option changes and then the error message changes to
"could not open /sys/devices/virtual/backlight"
Please help

Thanks........ successfully rooted yt2 1050L
Sent from my YOGA Tablet 2-1050L using Tapatalk

anilkumar247 said:
Thanks for the tutorial.
I did all the steps as you said. I am at step 15 and selected t4 and then the command prompt showed waiting for device and then my tab rebooted itself and then came to a fastboot mode.
Now n TAB its showing error that "E: No valid installer medium found"
now when i press the volume keys, the boot option changes and then the error message changes to
"could not open /sys/devices/virtual/backlight"
Please help
Click to expand...
Click to collapse
Did u check that ADB/fastboot drivers installed correctly? Try to reinstall those drivers and check again. Did u select the UPDATE SuperSU zip file and install it?

AndroMAN said:
Did u check that ADB/fastboot drivers installed correctly? Try to reinstall those drivers and check again. Did u select the UPDATE SuperSU zip file and install it?
Click to expand...
Click to collapse
How can i make sure they are installed correctly ?
I have reinstalled them and tried again, but still getting the same error.
I am not getting the update Super SU option, or any options to get it installed.

@AndroMAN any idea why my 64gb sdcard is not recognized.
Sent from my YOGA Tablet 2-1050L using Tapatalk

anilkumar247 said:
How can i make sure they are installed correctly ?
I have reinstalled them and tried again, but still getting the same error.
I am not getting the update Super SU option, or any options to get it installed.
Click to expand...
Click to collapse
Step 8 and 9. Check under command prompt. It should show the name Baytrail***** when you type in the command "adb devices". Only then u can go ahead.

sajsaj7829 said:
@AndroMAN any idea why my 64gb sdcard is not recognized.
Sent from my YOGA Tablet 2-1050L using Tapatalk
Click to expand...
Click to collapse
Have you rooted your tablet? Was it detecting it earlier?

AndroMAN said:
Have you rooted your tablet? Was it detecting it earlier?
Click to expand...
Click to collapse
Hv rooted...Yes 32gb was working perfect but 64gb it says blank sdcard
Sent from my YOGA Tablet 2-1050L using Tapatalk

Hi
yes, its showing the device ID
prntscr.com/948uzk
prntscr.com/948ybk
I have blackened the device ID

sajsaj7829 said:
Thanks........ successfully rooted yt2 1050L
Sent from my YOGA Tablet 2-1050L using Tapatalk
Click to expand...
Click to collapse
Good? All the best and enjoy your rooted device. Have you installed Xposed Framework on it yet?

sajsaj7829 said:
Hv rooted...Yes 32gb was working perfect but 64gb it says blank sdcard
Sent from my YOGA Tablet 2-1050L using Tapatalk
Click to expand...
Click to collapse
Try formatting the new sd card via the tablet, even I have put a 64GB card and I had to format it before it could detect.

anilkumar247 said:
Hi
yes, its showing the device ID
prntscr.com/948uzk
prntscr.com/948ybk
I have blackened the device ID
Click to expand...
Click to collapse
Sorry to hear your facing issues. There are already people saying they have successfully rooted their device using this guide. So there must be some step u might have missed or done incorrectly.
Send me the details of your device, model of tablet, which Android version.

AndroMAN said:
Good? All the best and enjoy your rooted device. Have you installed Xposed Framework on it yet?
Click to expand...
Click to collapse
Thanks.. cld u please link me to ver of xposed working on yt2.
---------- Post added at 11:25 AM ---------- Previous post was at 11:21 AM ----------
AndroMAN said:
Try formatting the new sd card via the tablet, even I have put a 64GB card and I had to format it before it could detect.
Click to expand...
Click to collapse
@AndroMAN somebody hv made a exfat binary zip to be flashed via teetherd recovery.... any idea how to go into twrp recovery.

anilkumar247 said:
Hi
yes, its showing the device ID
prntscr.com/948uzk
prntscr.com/948ybk
I have blackened the device ID
Click to expand...
Click to collapse
AndroMAN said:
Sorry to hear your facing issues. There are already people saying they have successfully rooted their device using this guide. So there must be some step u might have missed or done incorrectly.
Send me the details of your device, model of tablet, which Android version.
Click to expand...
Click to collapse
Hey i think i have the solution for your problem because everytime i am facing the same issue
That means at first adb drivers are shown as installed correctly within the window of the 'Intel Fastboot Tethered Temporary Recovery Session Launcher' tool. But after my tablet reboots into fastboot via method t4 it always says "No valid installer medium found".
Note: I have these adb drivers installed http://forum.xda-developers.com/showthread.php?t=2588979
So here is my solution that works for me: (this is my first post so i cant provide any screenshots.. )
1. let the tablet stay within the fastboot mode
2. in windows: navigate to the device manager --> there you should see the symbol "android phone" with a yellow triangle
3. right click on this symbol and choose the first option "update drivers" (sry i don't know if i translated it correctly xD)
4. choose the option "search on pc .."
5. there you select the second option "choose from a list.."
6. within the list you select 'android device'
7. within the next list you select 'google nexus adb device'
8. after that the drivers are installing and the recovery starts on your tablet :fingers-crossed:

1subw00fer1 said:
Hey i think i have the solution for your problem because everytime i am facing the same issue
That means at first adb drivers are shown as installed correctly within the window of the 'Intel Fastboot Tethered Temporary Recovery Session Launcher' tool. But after my tablet reboots into fastboot via method t4 it always says "No valid installer medium found".
Note: I have these adb drivers installed http://forum.xda-developers.com/showthread.php?t=2588979
So here is my solution that works for me: (this is my first post so i cant provide any screenshots.. )
1. let the tablet stay within the fastboot mode
2. in windows: navigate to the device manager --> there you should see the symbol "android phone" with a yellow triangle
3. right click on this symbol and choose the first option "update drivers" (sry i don't know if i translated it correctly xD)
4. choose the option "search on pc .."
5. there you select the second option "choose from a list.."
6. within the list you select 'android device'
7. within the next list you select 'google nexus adb device'
8. after that the drivers are installing and the recovery starts on your tablet :fingers-crossed:
Click to expand...
Click to collapse
That might just work :fingers-crossed:

1subw00fer1 said:
Hey i think i have the solution for your problem because everytime i am facing the same issue
That means at first adb drivers are shown as installed correctly within the window of the 'Intel Fastboot Tethered Temporary Recovery Session Launcher' tool. But after my tablet reboots into fastboot via method t4 it always says "No valid installer medium found".
Note: I have these adb drivers installed http://forum.xda-developers.com/showthread.php?t=2588979
So here is my solution that works for me: (this is my first post so i cant provide any screenshots.. )
1. let the tablet stay within the fastboot mode
2. in windows: navigate to the device manager --> there you should see the symbol "android phone" with a yellow triangle
3. right click on this symbol and choose the first option "update drivers" (sry i don't know if i translated it correctly xD)
4. choose the option "search on pc .."
5. there you select the second option "choose from a list.."
6. within the list you select 'android device'
7. within the next list you select 'google nexus adb device'
8. after that the drivers are installing and the recovery starts on your tablet :fingers-crossed:
Click to expand...
Click to collapse
Hello
That worked
But instead of google nexus adb device in the list, i got only motorola ADB device, but still it worked .
Thanks to both of you for the help.

sajju73 said:
Thanks.. cld u please link me to ver of xposed working on yt2.
---------- Post added at 11:25 AM ---------- Previous post was at 11:21 AM ----------
@AndroMAN somebody hv made a exfat binary zip to be flashed via teetherd recovery.... any idea how to go into twrp recovery.
Click to expand...
Click to collapse
There is no working mode of Xposed on YT2 as far as I have seen. Still have to look into it.
Go to recovery the same way u did last time, through 'Intel fastboot launcher:

Congratulations @anilkumar247. I hope your device is rooted and working well. And thanks to @1subw00fer1 for helping out and contributing to this thread. Great work guys. All good ☺