Hello friends,
I was using a General Mobile etab4 tablet,
rooted,
bootloader locked,
not backed up, i tried but apps wont recognize the brand,
the stock rom is not available anywhere but I managed to find some custom ones.
This tablet is actually a given by government for educational purposes, and it has no download mode, I can only initiate recovery mode with volume up+power button combo, and there is no sd card in it.
Here is what happened. It was running with problems so I decided to flash a custom rom I find on this forum. First I tried flashing using adb sideload. I got an error message "Installation aborted" with no error codes after verification step but it does not state whether verification is failed or not. I don't know what actually failed. Then I tried to flash it using adb shell as root (the system image was in /sdcard directory). It freezed, I exit the shell using Ctrl+C command. Then whenever I try to start shell i got "error:closed" message. I see my device with adb devices with sideload, but it is not seen in fastboot devices.
When I try to open it, I guess it enters in a small boot loop (screen flickers multiple times with brand name on it) and after some time I got dead android with no command written.
I tried,
reflashing it again with Android AIO Flasher,
use fastboot to unlock bootlader (it says "waiting for device") although adb devices sees it,
re-installing the adb drivers after uninstalling them,
disassembling the device to see if I can detach memory to edit it and to see if disconnecting the battery helps,
I even used a simple jig to see if i can initiate download mode (know it works for specific devices but you know hope)
Apparently, I messed up the device but the hardware must be all fine. So I think there must be a way out. What can you suggest, I wish I have unlocked the bootloader. I can send the pictures of its motheboard it helps,
Thanks in advance.
Hi,
Thanks for using XDA Assist please post here Android Q&A, Help & Troubleshooting
Good Luck!
Related
hello,
I'm hoping someone here can help me sort out my current problem.
I've been trying to root so I can install the latest ICS port, but having problems at the Fastboot screen.
I apologize in advance if some of the references/names I'm using are incorrect.
So, I had originally unlocked my Nexus S sometime early this year. When I restart the phone, the "unlocked" lock picture shows up under the "Google" words, and when I go into fastboot mode, the Lock State is Unlocked.
I'm running 2.3.6 right now on the Tmobile version of the phone.
When the phone is on (not in fastboot mode), I can execute ADB commands and the device is recognized. As soon as I go into fastboot it isn't.
I'm running 64bit Win 7, and I have gone through the various threads that have listed this issue, and installed PDA Net drivers and still there is no solution.
In Fastboot mode, while connected to computer under device manager, it shows up under Universal Serial Bus Controllers as an Unknown Device... I'm unable to update any drivers for it, and even when I try to manually update the drivers by going to the PDANet drivers it does not allow it.
When the phone is on in regular mode in device manager it shows up as Android Phone and within that it has a listing called Android Composite ADB Interface.
As mentioned above, when phone on in regular mode everything is detected.
I installed clockwork app from market, assuming that the phone was "rooted" based on the "unlock state" in fastboot mode, but it immediately says that phone needs to be rooted because it was unable to find SuperUser file etc etc.
I've spent the better part of a few days trying to figure this out by checking all sorts of links, but I haven't found a solution. The main issue is that the phone is not being recognized when in fastboot mode when connected by USB. And I'm unable to install the proper drivers for fastboot mode.
Hopefully this makes sense, and someone can provide some insight.
Thanks in advance!
I'm not positive about this but couldn't you adb push the su binary and apk? I don't own the Nexus but I would think since its unlocked you could just push the files. If this would work I would think it's just a temporary solution to allow superuser permission. As I understand it, fastboot is the preferred method for the Nexus.
Sent from my PG06100 using Tapatalk
Did you try a fastboot command like fastboot devices?
Don't know if this applies to you but I had a similar sounding problem when trying to root my Nexus S where everytime I booted into fastboot mode I had an error message at the bottom of the screen saying something like 'fastboot status-fail Invalid command' and so I couldn't use any fastboot functions.
To get around it I used this one-click root . For some reason I got an error message halfway through for whatever reason and it wouldn't complete the root for me but it booted me into fastboot without receiving the error message and then once I was in I went and rooted manually.
The CWM is out of date on that site though (possibly the super-user zip too) so I replaced them with the latest versions and popped it in my dropbox for you, if you wanna try it out.
http://dl.dropbox.com/u/47770734/One-Click-Nexus-S.zip
Edit: just had a little look through the bat script and the initial commands that got me into fastboot properly is (with your phone in debugging mode):
adb start-server
adb reboot bootloader
Click to expand...
Click to collapse
So you could try that first if you wanna go through manually.
Know that you can't run adb command while in fastboot mode. Boot into your CWM and then you can start an adb shell and you'll be able to push all the files you want and execute all the commands you need.
Fastboot mode is for running fastboot indeed. Try 'fastboot devices' while you're in the bootloader and see if devices pop up. If not, you really have to figure out your drivers issue. Maybe remove the device completely from your PC (including driver files) and reinstall it using the PDAnet drivers.
Greetz
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)
Hey all. Done a lot of searching and have tried a lot of solutions but I'm still having the same problem.
A friend of mine brought me her phone (AT&T HTC One X Plus) that she had soft bricked my trying to root and flash his own rom by herself. Trying to fix it, she accidentally relocked the bootloader and also wiped the recovery from the device. She said she wanted it re-rooted and CyanogenMod 10.1 installed. I told her I could do it for her. I have unlocked the bootloader through htcdev, flashed on the new recovery (using CWM v6.0.2.7) and now all I need to do is transfer the actual ROM to the phone and then install it. I can't, however, for the life of me get this phone to communicate with the computer/ADB. Fastboot recognizes it fine, I can type put the phone in fastboot mode and type 'fastboot oem get_identifier_token' and it will give me the identification number of the phone and other details, so I know it's communicating with it, but when I type 'adb devices', nothing shows up. And it's the "adb push filename.zip /sdcard/" command that I have to use. I have also tried going through the recovery and mounting the /sdcard/ and /data/ and /system/ to the computer, with no luck. Whenever I click on the "mount sd" through the recovery, the page just refreshes and puts my selection back at the top making no changes.
Whenever I plug this phone into any of my computers, all of the drivers install except for the HTC MTP driver, as seen here;
img59.imageshack.us /img59/61/driverh.png (Sorry, going to have to fix that link, can't post pictures yet)
I have plugged an HTC One into the computer and it downloads all the drivers just fine and communicates with adb. Same thing with my Note 2.
Any help would be really appreciated.
Thanks,
John
iBlameLag said:
Hey all. Done a lot of searching and have tried a lot of solutions but I'm still having the same problem.
A friend of mine brought me her phone (AT&T HTC One X Plus) that she had soft bricked my trying to root and flash his own rom by herself. Trying to fix it, she accidentally relocked the bootloader and also wiped the recovery from the device. She said she wanted it re-rooted and CyanogenMod 10.1 installed. I told her I could do it for her. I have unlocked the bootloader through htcdev, flashed on the new recovery (using CWM v6.0.2.7) and now all I need to do is transfer the actual ROM to the phone and then install it. I can't, however, for the life of me get this phone to communicate with the computer/ADB. Fastboot recognizes it fine, I can type put the phone in fastboot mode and type 'fastboot oem get_identifier_token' and it will give me the identification number of the phone and other details, so I know it's communicating with it, but when I type 'adb devices', nothing shows up. And it's the "adb push filename.zip /sdcard/" command that I have to use. I have also tried going through the recovery and mounting the /sdcard/ and /data/ and /system/ to the computer, with no luck. Whenever I click on the "mount sd" through the recovery, the page just refreshes and puts my selection back at the top making no changes.
Whenever I plug this phone into any of my computers, all of the drivers install except for the HTC MTP driver, as seen here;
img59.imageshack.us /img59/61/driverh.png (Sorry, going to have to fix that link, can't post pictures yet)
I have plugged an HTC One into the computer and it downloads all the drivers just fine and communicates with adb. Same thing with my Note 2.
Any help would be really appreciated.
Thanks,
John
Click to expand...
Click to collapse
ADB only works when the rom is loaded with usb debugging on. It's a shell for command line direct to your phone. Furthermore, recovery does not use MTP, it uses generic mass storage device.
It seems you're not the only one having issues mounting with CWM. I don't know much about it because CWM has very little compatibility with the HTC ONEXL(This forum) whereas you seem to have the ONEXPLUS there. Different phone, but if TWRP is compatible with your phone you can try mounting using TWRP instead? I understand that at one point a specific version or set of versions perhaps(like I said, we don't use CWM much for this phone) had issues mounting so you can check to make sure you have the latest version of CWM as I am pretty sure they've since fixed the issue. If you are using the latest version, you can also try issuing "fastboot erase cache" while in bootloader/fastboot to clear cache which may fix your issue.
Good luck. For better help it may be best to post in the one x+ forum subsection.
exad said:
ADB only works when the rom is loaded with usb debugging on. It's a shell for command line direct to your phone. Furthermore, recovery does not use MTP, it uses generic mass storage device.
It seems you're not the only one having issues mounting with CWM. I don't know much about it because CWM has very little compatibility with the HTC ONEXL(This forum) whereas you seem to have the ONEXPLUS there. Different phone, but if TWRP is compatible with your phone you can try mounting using TWRP instead? I understand that at one point a specific version or set of versions perhaps(like I said, we don't use CWM much for this phone) had issues mounting so you can check to make sure you have the latest version of CWM as I am pretty sure they've since fixed the issue. If you are using the latest version, you can also try issuing "fastboot erase cache" while in bootloader/fastboot to clear cache which may fix your issue.
Good luck. For better help it may be best to post in the one x+ forum subsection.
Click to expand...
Click to collapse
Thank you, flashed over twrp and the computer recognizes it. Thanks so much for your help!
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...
well i scrwred my phone , did a factory reset, wiped cache, and messing about like an idiot did some messing wiht the mount /unmounting. obviosuly deleted some important system files. now its stuck in bootloop. it just stays on the logo. MY phone is huawei g620s L01 was running kitkat 4.4.4. i have cwm recovery on it. i have unlocked the bootloader. i have installed all the drivers for my device on windows. i can get into fastboot or recovery. i have downloaded a stock rom but when i type command adb sideload "nameofrom620s.zip" it starts but finishes saying install aborted/??? no explanation ...so i am really stuck, any ideas. i know it connects becasue when i type fastboot dvices, it lists a device number. when i type adb devices a few lines come up one of which is the device number and says recovery. Please can u help? is there some other software i need like a flashing tool or odin(ihave never used odin and know nothingn= about it). I should also mention that although it connects via adb/fastboot, when i check devices in windows, its not listed!? PLEASE please can someone show me the way forward? thanks.
Hi, thank you for using XDA assist. I've found this which may help you get your phone working again, http://forum.xda-developers.com/android/help/restoring-broken-huawei-smartphones-t3047748
No response. Thread closed.