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.
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.
Hi comrades!
Ihave unlocked prime 32dock.
Yesterday I tried to flash the firmware KJY2010 Primalicious 9.4.2.21.
1) First, I installed the CWM 5.8.2.0 - successfully
2) rebooted several times - everything was OK. The factory firmware loaded.
3) Then I found the instructions KJY2010 Primalicious 9.4.2.21 - is successfully established.
4) The new firmware is loaded. I set up wifi, google account and decided to reboot.
5) After rebooting, I was constantly load in the CWM.
I go to instruction Brick 1a
adb give me this result:
Code:
c:\Tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
c:\Tools>
I try 2 other Prime usb driver - result the same. (In device manager Asus transformer Prime set OK, whithout any warnings)
I try do this under Linux - result the same.
What else can i do in this situation?
I have backup image and i try do restore - result the same.
I try wipe data - result the same.
Please HELP.
See this thread to get your Prime recognized by adb:
http://forum.xda-developers.com/showthread.php?t=1426502
thanks
tedr108 said:
See this thread to get your Prime recognized by adb:
http://forum.xda-developers.com/showthread.php?t=1426502
Click to expand...
Click to collapse
big thanks.
I already tried this driver yesterday, but was inattentive. did not remove the old drivers first.
Who made everything clear to the user manual (deleted the driver and rebooted the computer).
It worked! Thank you and the author of the driver! My tablet is restored.
I had this problem with my prime with it 1a bricked. so i tried it on my laptop instead of my desktop and was able to adb. Think my desktop needs a reimage but i was not in the mood to do it.
yurmala22 said:
big thanks.
I already tried this driver yesterday, but was inattentive. did not remove the old drivers first.
Who made everything clear to the user manual (deleted the driver and rebooted the computer).
It worked! Thank you and the author of the driver! My tablet is restored.
Click to expand...
Click to collapse
FIXED!
Hiya mate, any chane you can write down your procedure if thats cool, ive got the exact same issue as you,
- ive deleted anything that looks like a driver pack from asus in my add remove program (im on xp)
- ive uninstalled the driver from the listing in the device manager (Android Phone > Asus Transformer Prime ADB Interface) which comes up when i hook up the tab while its in CWM
-restarted comp, connect my tab, point xp's driver install program to the universal naked driver folder
- all set, yet still getting the device not found
I have adb folder in C:\ directory
CMD into the run menu
CD change C:\
cd adb
adb shell
daemon not running. starting it now on port5037
daemon started successfully
error: device not found
Been looking around for a while now, pulling my hair out, a few snippets here and there, some have been successfull, but no detail on how they got it fixed
Out of all of them, your situation best describes the one im in at the moment, am i missing something?
Hoping you or anyone really, have a solution, and perhaps help anyone else who might get into a similar situation
By the way, for the record, my brick occured because i stupidly Factory/Reset using the ROMS ( Virtuous Prime/Stock kernel) menu, rather then CMW's Factory/Reset
Any help would be mucho appreciated
Edit: Sorry ive just realised how old the thread is, hope no one minds, if not
-Tried asus sync
-Tried pdanet?(is that right?) drivers
- Hoping for a solution that doesnt involve deleting internal sd card content as ive got 1 or two nand backups im in the process of streamlining, if thats possible that is
Edit 2
Ok, managed to get past the device not found part,
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Installed another version of adb(link above, follow instructions), i guess the adb i was using was a dud
Edit 3
Fiiinaly fixed it, problem was adb, for anyone who might have similar symptoms try installing and following the instructions in the link just up there ^^^^
And to be thorough, follow the instructions written by Diamondback (option 1a)
http://forum.xda-developers.com/showthread.php?t=1514088
Heres the snippet, if Diamondback dont mind?
Once adb's installed correctly
Now do the following:
Make sure your Prime is in Recovery mode (CWM)
Open a cmd line on your pc
Type: "adb shell"
You should see a "#" now
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter]
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
There you go folks, if a noob like me can do it.......well, you get the idea
Hi,
im really stuck, been trying and searching for 2 hours.
my prime got wipes, so everything wiped. not usually a problem but when in twrp recovery i adb does not detect the device. it will detect it when attempting to coldboot linux but when u use adb push i get permission denied. ive tried cwm recovery too and no luck, its the same thing, under adb devices, i cannot find the device.
ive tried 3 computers and i for sure have the usb drivers installed correctly
i dont know how to flash roms through fastboot so any ways of doing that would be great.
so right now im stuck with a device i cannot push a rom to to flash and i cannot turn it off, its getting really hot so any help asap would be great!
thanks!!
hi,
i have installed the viper venom modified twrp recovery software and it all works and i can get inside however when i press mount usb storage and wait for a few mins nothing happpens. phone does not show on computer. i tried adb sideload and adb push command but no luck, not sure where im going wrong. absolutely new to this. please can someone help? all my sync and sdk files are up to date. i wanna move a boot file to my phone.
thanks
1) This is an MTP Device.
2) for adb go to hboot
Sent from my HTC One X+ using Tapatalk 4
When ur phone is connected to PC while in recovery...try "adb devices" command that will show whether ur device has been recognized or not...If it's recognized try adb sideload or adb push.....
And for mounting the partition that will not work on one X+ ...the explanation for that is given herehttp://forum.xda-developers.com/showthread.php?t=2002156
Sent from my HTC One X+
awesome guys i did not know i had to be in Hboot. thanks alot guys! im gonna try it.
ok guys i made progress. adb detected my phone. it seems i pushed boot into sdcard because the ls command shows boot.img inside twrp in sdcard. but apparently recovery installs stuff that are zips. anyway i can install boot thats an img file? or does it have to be zip. im confused. pls help.
many thanks
ok guys its all done, thanks alot for all your help. i figured out how it all works. amazing how it becomes common sense later somehow!
Hi!
First off let me say thanks to R_a_z_v_a_n for redirecting me and hope that I'll find my answer here ^^
So I Have this device called HP 7 VoiceTab 1321RA (not with Slate just HP 7 Voicetab), wanting to have a custom recovery then I tried to flash a CWM Custom Recovery for HP Slate 7 VoiceTab because I thought it was the same and ends up bricking my phone. It ends up in a bootloop which only shows HP sign for a few seconds and dead. But I managed to find out that I can access the recovery menu (or so I thought it is), but the options was choosing between Fastboot Mode, Normal Boot, Recovery Mode, and VART Mode.
I tried to enter Fastboot Mode before and tried to access it via PC but somehow I can't find the device by entering adb devices and fastboot devices. Anyways, I have downloaded a stock update.zip for it but not the original KitKat one which I get from the first time I bought it but rather the JB ones. I think by flashing this would help me recover the device but the only problem is I don't know which method should I use to Flash it. Since I don't have the Stock Recovery or ANY kind of recovery at all, I guess I'm stuck. And it won't start to the home page so I can't set the USB debugging options. Please guide me through this >.<
Thanks a lot!
Been fighting with it for 2 days now and still no result came.
So here's the update so far....
I tried on my other device in order to understand how my PC reads ADB and now I kinda gets it. But the problem is now can't get the device to enable USB Debugging because I can't access options at all.
Secondly, since I left it on for the night because charging seems to trigger the bootloop too, now I can't access the fastboot mode like I was last night. And it constantly repeating this sequence: [battery scene with the "charging battery" symbol] > [HP Powered by Android screen] repeated for 2-3 times > [low battery need charging screen] > repeat. And once I tried to connect to the PC, it goes to the same sequence too. When I tried to access the boot options (the screen which displays Fastboot Mode, Normal Boot, Recovery Mode, and UART Mode which I mention in Thread Starting post), it shows the low battery need charging scene and then repeating the same sequence as mentioned above.
I seem to figure out how to fix this but I still can't manage to access the fastboot mode yet. Will give update once I can try to.
Anyone can help me on this?
Thanks a lot!
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
I found my self in a deadlock!
PLEASE HELP :crying:
Could you unbrick yours
What service centre says about that problem i also ran in this problrm but i m trying to go to service centre for that
first off install drivers in your PC as admin
then use the official flashtool to flash ur stock firmware by entering fastboot or flashmode simple as that
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
Dude urs is a mtk device so sp flash tool should do the trick.... Just don't forget to install correct drivers....run both drivers and flash tool as admin..... Tell me when it's solved k
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
That is what im trying. To tell you urs is a mediatek device the official flashtool is sp flashtool
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
try to push the update.zip via adb sideload (Choose "update via ADB sideload" on recovery mode)using adb terminal on PC,as long as your tab can access the recovery mode.remember to backup all your data before u do it.
have a try it's 100% work on me
where I can download update.zip file? anyone can help?
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
can you explain how did you managed to charge the device??? please its a request......jst help me out :crying::crying: