Database Info

[Q] problem with rooting and drivers

Hi,
I'm kind of a noob at this rooting stuff. I've looked ariund, done my research and everything but it never seems to go smoothly??..
I think the main problem is with the drivers. After following instructions the android drivers still said 'Android 1.0'. So I installed Pda net and then I got 'Android ADB Interface' drivers. Soo the thing is, after searching for 'adb devices' in cmd prompt, It says 'list of devices' but there's nothing in the list....?
For some reason it won't do any commands like 'adb reboot bootloader' or 'fastboot oem lock'. It says not found. I have installed all the sdk and packages...
Would really appreciate some help from you guys. I didn't think rooting would be so complex??...
Thanks

can you post screenshot??

Ok for some reason, after starting the cmd again today and typing adb devices, it has listed my device. But when I type 'fastboot oem lock' (because my bootloader is already unlocked) it says not found as shown in the screenshot.
Am I doing something stupid??...

70 views?... cant anyone help ... please..

soulja786 said:
70 views?... cant anyone help ... please..
Click to expand...
Click to collapse
If adb devices lists your device you're not in the boot loader, the ONLY place fastboot will recognize your device and function or you have a driver issue. You're either in recovery or booted up. Reboot into the boot loader to use fastboot.
If you get into the boot loader and fastboot still doesn't show your device it's a driver issue. Update the driver manually and point it to the SDK USB driver provided with the SDK.
For reference....
Booted into boot loader:
Fastboot OK
ADB NO
Recovery / Fully booted
Fastboot NO
ADB OK

Hi guys,
I really do think this is a driver issue... any idea on how to solve it? I do have PDA Net installed... ?
@krohnjw ... could you please clarify.. Im a bit lost.
Thanks!

Did you try something like oneclickroot?
http://forum.xda-developers.com/showthread.php?t=1138755

Well I also had a lot of issues trying to root my i9020t so let me try to help..
Phone will be recognized with ADB when u select enable debug on developer options. You ll see "Android ADB Interface" on SYS DRV.
On other hand , when U start phone on fasboot mode, it should install something like "Android Bootloader Interface " , if U keep seeing "Android ADB Interface" , its wrong, but took some time to realize that.
That happened to me when I was using WinXP x32 to root my phone, ironically thinking it would be more compatible an less prone to bugs... When done it on W7 x64 , my fastboot driver was discovered correctly (Android bootloader Interface) using x64 PDA drivers, and all went good then!
Hope this may help!

[Q] Waiting... message on cwm root

I would have put this in development but I don't have permission yet.
Situation:
I'm using a Chinese tf300t
I tried to root my tablet using the cwm all firmware compatible method. you can find it on youtube as i am not yet allowed to post outside links.
unlocked my tablet. downloaded sdk and all the applications necessary. followed their directions to the letter. I go to cmd to put in the code and when I hit enter after typing: fastboot -i 0x0blah... i get: "waiting on device"
What I think the problem is:
with the sdk fastboot my computer never makes the usb found sound so i thought maybe something with the fastboot driver might be causing a problem so i looked online and someone with the same problem found that a different version of fastboot fixed his waiting problem. I tried what worked for him and now I get a weird stutter version of the usb found sound and i still get a waiting message when i enter the code in cmd. so i think that there might be a problem with the drivers, but my tablet works fine with my comp when its booted up normally.
good news is that I have always been able to reboot device and run normally.
Anybody got any sugestions?

i would like to suggest you to copy these files: fastboot + cwr into 1 new folder, then run fastboot again ( do this while your device is showing ""waiting on device", don't need to reboot it)

[Q] Padfone 2 bricked: invalid kernel

After a lot of reading on Xda and Modaco I am still not much further.
After rooting with Framaroot and installing TWRP through Goomanager I bricked my phone because I forgot to unlock the bootloader....
Is there any hope for this phone?
The phone cannot get into fastboot: power button + volume up.
Recovery menu (power button + volume down) is non-functional > I get the "invalid kernel" message again.
ADB and Fastboot and cmd in Windows are all very new to me but I have nothing to loose.
Thanks in advance for any advice.

"invalid kernel !!!" - I bricked my phone
Hello,
I have exactly the same problem... I've also red a lot without finding any suitable solution...
I rooted with Framaroot, installed TWRP and thats it - I bricked my phone (probably because I forgot to unlock the bootloader?)....
Same problem for me: the phone won't get into fastboot (Power+VolUp).
Recovery menu (Power+VolDown) doesn't work: I always get "invalid kernel !!!"

Hi Vakilando,
It seems we're on our own with this problem. Either no one has an answer or all knowledgeable people never had to deal with this problem.
We also choose a not-so-popular phone. The tablet-phone combi is too expensive and the tablet of mediocre specs.
I went for the too-good-to-be-true price for the phone-only... and after a lot of reading found out that quit a few people had problems with their phone.
Perhaps some code monkey (no disrespect) could tell me if we have more options when the phone is connected to a Linux system? Android is Linux based, so that would be a compatible pair. Windows can only see one partion on a flash card and, but I might be wrong, Windows cannot read EXT 3, 4 partitions.
Windows device manager does recognize the phone as "ASUS Android Bootloader Interface" so the phone is not completely non-responsive.
I also posted on a German site; Android-Hilfe where there's a dedicated forum with knowledgeable people so perhaps that gives more options.

do this!it will work!!!
gentle_giant said:
After a lot of reading on Xda and Modaco I am still not much further.
After rooting with Framaroot and installing TWRP through Goomanager I bricked my phone because I forgot to unlock the bootloader....
Is there any hope for this phone?
The phone cannot get into fastboot: power button + volume up.
Recovery menu (power button + volume down) is non-functional > I get the "invalid kernel" message again.
ADB and Fastboot and cmd in Windows are all very new to me but I have nothing to loose.
Thanks in advance for any advice.
Click to expand...
Click to collapse
jUst flash a cwm recovery with fastboot mod!it will work!my padfone 2 brick like this but now his alive

Sorry, for not well-advanced users - could you please describe step-by step how to flash phone in "invalid kernel" condition CWM recovery with fastboot? Tnanks!

Ola Goldenval, try this link, it worked for me.

This is first link I found in google & tried to follow. My problem is that PC (W7 ultimate) doesn't see the phone. So cmd window is hanging on message "waiting for device" forever. Problem isn't in PC, as I tried different PC, where another similar phone had been seen some time ago.

Hi Goldenval,
the onlything I can tell you is that it didn't work out for me the first time, just like you now. Then I found another, German, website with lots of information on the subject and I gave it another try. Second time I succeeded...
it is a long time since it happened so I can't recall all the details but keep on trying and you will succed.

Update
Instruction here : w.w.w.modaco.com/topic/365818-padfone-2-invalid-kernel/
If You upgrade to kitkat and bricked you phone .You have to download latest
update h.t.t.p://dlcdnet.asus.com/pub/ASUS/Mobile_Phone/PadFone2/WWE_PadFone2_user_11_8_4_12_UpdateLauncher.zip unzip and rename with instruction. Help for me
I can't put outside link I am under 10 posts .

Download last usb driver for padfone 2 and then u will see cmd work properly

Hi all,
sorry to resurrect this thread, but I have the same problem and cannot solve it.
I followed the instructions in modaco.com but no luck.
My phone keep rebooting with the Invalid Kernel...

[Q] Galaxy R unbrick problem

Hi, Guys!
I've bricked my phone the other day with NO KERNAL message in download mode. So now i'm trying to flash bootloader using this method (STEP 2 to be exact) http://forum.xda-developers.com/showthread.php?t=1706572 So i got the device connected in Device Manager. When I run GTI9103.bat then type 1, and hit Enter nothing happens, the window disappears immediately with the message "cannot find the path specified". Does anyone know what might be the problem???:crying:

Ronnie1990 said:
Hi, Guys!
I've bricked my phone the other day with NO KERNAL message in download mode. So now i'm trying to flash bootloader using this method (STEP 2 to be exact) http://forum.xda-developers.com/showthread.php?t=1706572 So i got the device connected in Device Manager. When I run GTI9103.bat then type 1, and hit Enter nothing happens, the window disappears immediately with the message "cannot find the path specified". Does anyone know what might be the problem???:crying:
Click to expand...
Click to collapse
you shouldnt have tried that method in first place.
You were able to enter into download mode and in that case your device is not bricked!
If odin is detecting your device, then flashing a recovery/stock rom fixes the problem many times.
You can give it a try to this if odin is not detecting your device!
Good luck!

Failed to restore fastboot following petrov.0's GUIDE

Hi everyone,
I have received my new Idol 3 4.7 (6039Y, european version) yesterday. I was stupid enough to apply all proposed updates before reading the forums thoroughly, so I got stuck with a 01005 build, with fastboot disabled.
I followed petrov.0’s guide to restore fastboot: http://forum.xda-developers.com/idol-3/development/6039-guide-how-to-return-fastboot-t3201077 or at least I tried.
I chose the files for "6039Y (repartitioned by following the repartitioning guide)" in the hope that it would save me some further work. QFIL seemed happy, but on restart, there was a message complaining about something like "unencryption failed", then saying that it was necessary to wipe the memory and perform factory reset. Then the phone spent some time wiping the data, and reboot took me to the stock recovery with a big nasty red error message.
So I used Alcatel Mobile Upgrade to restore the stock system, which went fine, but I was still stuck with a 01005 build. Then I tried again to follow petrov.0’s instructions, now using the files for "6039Y (8GB stock partition sizes)". According to QFIL's log, all went fine (except it waited forever in the final step, after the phone rebooted).
Once rebooted, the phone works ok, "adb devices" lists the phone, but "fastboot devices" still doesn’t.
Does anyone have the same problem? Any idea on how to solve it?
P.S.: this is my first post so I can't reply to petrov.0’s thread, and I couldn't find a Q&A thread on this subject, so here it is.

Fastboot -i 0x1bbb devices should be the right syntax. You have to directly adresy the devices by add “-i 0x1bbb“. Next zimě try to use search and read a little before posting stupid questions.
?

DallasCZ said:
Fastboot -i 0x1bbb devices should be the right syntax. You have to directly adresy the devices by add “-i 0x1bbb“. Next zimě try to use search and read a little before posting stupid questions.
Click to expand...
Click to collapse
No need to be rude : of course, I also tested the "fastboot -i 0x1bbb devices" with no more success.
(AFAIK, the -i option is just a filter: am I wrong?)

Turns out I was even more stupid than DallasCZ thought: my problem was that I used the fastboot commands in recovery mode rather than fastboot mode!
In case anyone as dumb as I passes by: use "adb reboot-bootloader" before trying any fastboot command.
And I confirm that the phone is NOT listed if I omit the -i option. The man page is really not clear about that: maybe the XDA-University guide about fastboot http://forum.xda-developers.com/showthread.php?t=2277112 could mention this kind of quirk?
Sorry for the noise.

I really have failed to restore fastboot commands using @petrov.0 's guide.
The problem I had having failed at flashing a modified OTA update file...well to cut a long story short I resorted to using Alcatels Mobile Upgrade Q 4.9.2 to fix my phone. I have no windows so was running the program on Linux host using VirtualBox. After loads of trouble with the drivers with 64 bit windows XP finally got everything to work using Windows 7.
I thought it would now be simple to restore fastboot commands using QFIL and to get my awesome 16GB internal memory back but despite phone definitely being in download mode and the phone showing up as Android HS-USB QDLoader 9008 on COM6 and QFIL automatically choosing COM6 etc and following everything in the guide as it should be I got an error when I hit the download button. Something about the phone not being in Firehose mode. I tried again and this time the error was about Sahara.
Anyone have any ideas?! Is it perhaps just not possible through Virtualbox?
Please help me! I want my 16GB internal memory back!
(phone is 6039Y-2AALWE7 and Upgrade Q updated it from 1AB2AZ22 to 1AJEAZE0)

fastboot - no permisions
deleted - found a simple solution.... for fastboot command in linux you need "sudo"!
Thank you

deleted
please a moderator wipe this post

gridmuncher said:
I really have failed to restore fastboot commands using @petrov.0 's guide.
The problem I had having failed at flashing a modified OTA update file...well to cut a long story short I resorted to using Alcatels Mobile Upgrade Q 4.9.2 to fix my phone. I have no windows so was running the program on Linux host using VirtualBox. After loads of trouble with the drivers with 64 bit windows XP finally got everything to work using Windows 7.
I thought it would now be simple to restore fastboot commands using QFIL and to get my awesome 16GB internal memory back but despite phone definitely being in download mode and the phone showing up as Android HS-USB QDLoader 9008 on COM6 and QFIL automatically choosing COM6 etc and following everything in the guide as it should be I got an error when I hit the download button. Something about the phone not being in Firehose mode. I tried again and this time the error was about Sahara.
Anyone have any ideas?! Is it perhaps just not possible through Virtualbox?
Please help me! I want my 16GB internal memory back!
(phone is 6039Y-2AALWE7 and Upgrade Q updated it from 1AB2AZ22 to 1AJEAZE0)
Click to expand...
Click to collapse
Any progress with this ?!? I'm a Linux user too, but I must admit that for this process I had to start my dusty Windows installation. As for the second attempt ... if the first one fails you must restart the phone in download mode again.

petrov.0 said:
Any progress with this ?
Click to expand...
Click to collapse
Sadly no. I don't understand why Upgrade Q would work in Virtualbox but QFIL doesn't. Still get the firehose error:
NOP: Fail Code: 10
Unable to send FireHose NOP, Device is not in Firehose mode!
Download Fail: System.Exception: Failed to send Firehose NOP to the phone
As I said before the phone is definitely in download mode and shows up in device manager correctly. I tried altering the USB filter in Virtualbox to be less device specific and a few other things, plugging unplugging, different usb cable, different usb port on laptop etc but no luck.
I might try a different Windows version but I think I'll probably resort to using a friends computer at some point.
Don't want to dual-boot windows as my laptop HDD is toooooooooo full and it would involve altering a few of my partitions etc.