Never even heard of rooting before last week. I decided to buy the Nabi 2 for my sons Christmas gift
Trying to get the thing rooted, Im a total No0b at this
Ill try to explain at what point in the process im at... When i type "adb devices" in the command promt the nabi is listed (some serial number)
but when I type "fastboot devices" i get nothing listed
I tried running the root process and got a andriod guy laying down with a red exclamation point over his corpse, also alot of "cant recognize device" error messages in the command menu
I dont think fastboot is working... can anyone tell me how to enable fastboot?
Thanks so much
Update*
Ok I just tried to run the root installer a different way (last time i was in the bootloader menu)
This time the tablet was fully loaded and screen unlocked. I ran option number "1".
The command promt returned this:
# waiting for device . . .
# If stuck here drivers are not installed
The system cannot find the path specified
# Rebooting device
The system cannot find the path specified
# press enter when you see text on the screen after Nabi logo
# If stuck here drivers are not installed
press any key to continue . . .
What drivers? I used PdaNetZ350 to install drivers... I dont know what im doing wrong
Have you reviewed the jmztaylor method?
Have you reviewed this method?
http://forum.xda-developers.com/showthread.php?t=1905674
Worked for me after I grabbed the drivers from PDAnet.
I have one issue of Android is Updating stuck in loop that some others in that thread have sorted out but I can't quite get working yet!
watchdog153 said:
Never even heard of rooting before last week. I decided to buy the Nabi 2 for my sons Christmas gift
Trying to get the thing rooted, Im a total No0b at this
Ill try to explain at what point in the process im at... When i type "adb devices" in the command promt the nabi is listed (some serial number)
but when I type "fastboot devices" i get nothing listed
I tried running the root process and got a andriod guy laying down with a red exclamation point over his corpse, also alot of "cant recognize device" error messages in the command menu
I dont think fastboot is working... can anyone tell me how to enable fastboot?
Thanks so much
Update*
Ok I just tried to run the root installer a different way (last time i was in the bootloader menu)
This time the tablet was fully loaded and screen unlocked. I ran option number "1".
The command promt returned this:
# waiting for device . . .
# If stuck here drivers are not installed
The system cannot find the path specified
# Rebooting device
The system cannot find the path specified
# press enter when you see text on the screen after Nabi logo
# If stuck here drivers are not installed
press any key to continue . . .
What drivers? I used PdaNetZ350 to install drivers... I dont know what im doing wrong
Click to expand...
Click to collapse
same problem.
I am having the same exact problem. I have reviewed the jmz method and keep getting stuck in cmd saying path not specified. Any solutions. All steps have been followed to the letter.
watchdog153 said:
Never even heard of rooting before last week. I decided to buy the Nabi 2 for my sons Christmas gift
Trying to get the thing rooted, Im a total No0b at this
Ill try to explain at what point in the process im at... When i type "adb devices" in the command promt the nabi is listed (some serial number)
but when I type "fastboot devices" i get nothing listed
I tried running the root process and got a andriod guy laying down with a red exclamation point over his corpse, also alot of "cant recognize device" error messages in the command menu
I dont think fastboot is working... can anyone tell me how to enable fastboot?
Thanks so much
Update*
Ok I just tried to run the root installer a different way (last time i was in the bootloader menu)
This time the tablet was fully loaded and screen unlocked. I ran option number "1".
The command promt returned this:
# waiting for device . . .
# If stuck here drivers are not installed
The system cannot find the path specified
# Rebooting device
The system cannot find the path specified
# press enter when you see text on the screen after Nabi logo
# If stuck here drivers are not installed
press any key to continue . . .
What drivers? I used PdaNetZ350 to install drivers... I dont know what im doing wrong
Click to expand...
Click to collapse
Make sure you are only selecting option #2 in the script, option #1 doesn't work. Follow the on screen instructions exactly. If it isn't recognizing the nabi in the script than the drivers aren't installed or try a different usb port. I couldn't get it to work on my win 8 laptop but was successful on my windows 64bit desktop. Using the pdanet drivers is the key. Just because you can plug the nabi into your computer and see the drive contents doesn't mean the drivers are loaded. Windows sees the nabi as a media device and uses generic mtp drivers that won't work with adb. Once you have successfully rooted your nabi, go back into recovery and install the gapps.zip separately. Enjoy!
Sent from my A500 using Tapatalk
cruise350 said:
Make sure you are only selecting option #2 in the script, option #1 doesn't work. Follow the on screen instructions exactly. If it isn't recognizing the nabi in the script than the drivers aren't installed or try a different usb port. I couldn't get it to work on my win 8 laptop but was successful on my windows 64bit desktop. Using the pdanet drivers is the key. Just because you can plug the nabi into your computer and see the drive contents doesn't mean the drivers are loaded. Windows sees the nabi as a media device and uses generic mtp drivers that won't work with adb. Once you have successfully rooted your nabi, go back into recovery and install the gapps.zip separately. Enjoy!
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
This thread goes through doing it manually, it is written for Ubuntu(linux) but it can be used in windows as well, you just don't use sudo for the commands. Also the package in the following thread already has the updated gapps package that does away with the "android upgrading" on every boot.
http://forum.xda-developers.com/showthread.php?t=2016463
fast boot won't install
Had ''path not specified'' it gets to the if stuck here drivers aren't installed. A window pops up saying ''installing fast boot'' but then says it failed. Thats where im stuck.
4.1.1 OS
2.4 product version
Thinking the 2.4 update is a problem.
Any suggestions?
I know i'm years late here but I really HATE adb and esp. BAT files that are just suppose to do their thing........I'm hitting a wall with this Nabi 2 Bat file for TWRP / ROOT. I've used PDAnet plenty in the past for internet but never for the purpose of just getting drivers so I have no idea I hate that program too. ANYWHO , I'm getting "cannot find specified path" which I probably could fix if I ****ing knew which ****ing path it was looking for. SO if anyone could please enlighten me here , I've installed and uninstalled PDA net some 10 times now , with Samsung selected , with LG selected with OTHER selected , I cannot get this to work. I can do FASTBOOT devices , and poof it shows up , adb works fine all that , show the device but I cannot get this ****ing BAT all in one installion to work. I'm really just about to flash it all manually through ADB but I'd rather use the installer to make sure I get the random WINGS files removed or whatever. Any help would be great , thanks.
Related
Okay so I'm new to Android. I have been trying to update to a new rom but have pretty much got stuck at the first hurdle. I have been trying to follow http://forum.xda-developers.com/showthread.php?t=552591
MoDaCo Custom ROM is here (2 versions based on the 'new update')!
As stated in the first thing to do for a newbie is to Download the patched recovery image linked above and install as detailed in that post.
I have not been able to get pasted this stage
Please please please can someone write an idiots guide for this as by the end of tonight I’m going to be bald as I’m pulling my hair out.
robboy said:
Okay so I'm new to Android. I have been trying to update to a new rom but have pretty much got stuck at the first hurdle. I have been trying to follow http://forum.xda-developers.com/showthread.php?t=552591
MoDaCo Custom ROM is here (2 versions based on the 'new update')!
As stated in the first thing to do for a newbie is to Download the patched recovery image linked above and install as detailed in that post.
I have not been able to get pasted this stage
Please please please can someone write an idiots guide for this as by the end of tonight I’m going to be bald as I’m pulling my hair out.
Click to expand...
Click to collapse
1. make a full nandroid backup
2.download the recovery image
3.turn off your phone and turn on by pressing the on button+the back key (to get into bootloader)
4.open a terminal from the folder which contains the recovery image.
5. type 'fastboot boot cm-hero-recovery.img'
6.type 'adb shell mount /sdcard'
7.type 'adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img'
8.type 'adb shell flash_image recovery /sdcard/cm-hero-recovery.img'
now whenever you want to access the recovery console, you just have to switch your phone on+home key and u'll enter.
To install the rom,
9. download the radio and rom from modaco
10. plug in ur usb and mount sd card
11. copy radio into sd card and rename to update.zip.
12. switch off phone and enter recovery console
13.if you never upgraded the phn , then a wipe is necessary
14. then, select update.zip..
15. u repeat the steps from step9 onwards the same way to update the rom.
hope ie helped.
i mentioned nandroid backup as from step 1 itself.
just came to realise that maybe u have never accessed recovery image from pc.
well dont worry, u can ignore step one but be sure to make the backup after step 8 ..... before installing the new rom
cheers and good luck
Okay so number 4 is my problem. Do o do this from the phone or pc?
robboy said:
Okay so number 4 is my problem. Do o do this from the phone or pc?
Click to expand...
Click to collapse
From the pc. A DOS terminal, if you are on windows.
should I allready have partitioned my sd card before i do this?
This is the error message i get
robboy said:
This is the error message i get
Click to expand...
Click to collapse
As far as I can see, you opened the command-line in the system32 dir from youre PC?! You should open the commandline in the dir where the image-file is. Should look like C:\SDK\tools
See this post to guide you further.
http://forum.xda-developers.com/showpost.php?p=4257045&postcount=38
robboy said:
This is the error message i get
Click to expand...
Click to collapse
To open a terminal( command prompt) from a folder,
1.go to accesories in Windows, copy the command prompt.
2. Go to your folder and paste it there.
3.right click on the command prompt, go on prope
rties.
4. U will find a line containing ' start in : %homedrive%%homepath....'
5. Delete that line so that 'start in' remains blank
6. Apply. And u r good to go
By the way. I supposed u already installed HTC sync right.
okay I thought HTC sync might be causing me problems so i removed it
robboy said:
okay I thought HTC sync might be causing me problems so i removed it
Click to expand...
Click to collapse
You will need to install HTC sync cause it contains the drivers for you phone.
Okay so I have put HTC sync back on. My hero connects to the sync in normal mode as an android USB devices - My HTC . What I'm unsure of now is when I press 'on and back buttons to go into bootloader' should the hero still sync as My HTC or should it be syncing to a different driver. I have been going round in circles all day. I have also removed the android development software as before the hero was syncing as and adb device??
When going to the cdm I now get the error device not found. USB debugging is selected on my device.
I think I’m on the brink of giving up.
okay so now when I'm in the bootloader my device connects as a ADB Interface - HTC Bootloader.
BTW I'm on Vista and i selected the driver that was in x86 folder that I was advised to download. However still no device found
robboy said:
Okay so I have put HTC sync back on. My hero connects to the sync in normal mode as an android USB devices - My HTC . What I'm unsure of now is when I press 'on and back buttons to go into bootloader' should the hero still sync as My HTC or should it be syncing to a different driver. I have been going round in circles all day. I have also removed the android development software as before the hero was syncing as and adb device??
When going to the cdm I now get the error device not found. USB debugging is selected on my device.
I think I’m on the brink of giving up.
Click to expand...
Click to collapse
Yes if your device is recognised as adb ... it's good.
That's how it should be.
Try installing HTC sync before plugging ur phone, then enter bootloader on the phn, plug it in, and then perform the command from the prompt.
P.s try entering bootloader first and only afterwards u plug in ur phone
Try to get the latest driver HTC sync from HTC site. If that doesnt work, try downloading the latest sdk plus drivers. U can find it somewhere on the forum . I think that there is a link on the rooting guide by daysee
I'm a total noob at Android too but theunlockr.com was the easiest and fastest way for me to install the custom Modacco ROM. Check out their site; it'll show you step by step with videos :]
Hello there
My name is Kareem and I'm using a Sony Xperia U 4.0.4 and build number 6.1.1.B.1.10.
So the thing is that I want to update my phone to 4.4 Kitkat and I'm following this thread.
I rooted my device, and I'm now trying to unlock bootloader. My devices says that I'm able to bootload but I still need to unlock it. So I googled around and came across this video which shows me how to unlock bootloader. First I had problems with installing the drivers because I am using windows 8.1 64-bit, but after I disabled “Driver Signature Enforcement” I managed to install the drivers.
And here the problem starts... I have to press the up volume button while plugging in so I can start fastboot. As what I was told, I did and the blue led on the left side turned on. But when I look on my desktop I get a notification that my usb device is not recognized.
Can anyone tell what causes this issue? Otherwise, is there another and maybe an easier way to unlock bootloader?
Kind regards
Kareem
P.s. I'm using that flashtool software to unlock bootloader. It's called "Sony Mobile Flasher by Androxyde".
I prefer to use this.
Is the official method for unlocking the bootloader, includes the drivers and stuff, just follow that tutorial and you're good to go.
Also you have to make sure that your phone can have unlocked bootloader first, if not, then, you have to stick to locked bootloader ROM's.
Now, sorry for saying like this but Windows 8.1 is such a pain in the a**, it always gives error because the drivers isn't signed, if you get problems with that again use this.
USB not recognized, well the solutions for that problem can be:
Use other USB port, if still doesn't work on any of the ports, then can be the slots or bad placement of pins in the motherboard, almost never is a problem of internal dust in the computer but you can try these.
Try other USB cable, may be the cable is failing, try other from another Android phone to complete the process.
Try using other computer with WIndows 7 or Ubuntu.
If you were not able to get working, then tell me.
Thanks for your reply. Both links are the ones I came across too, I used the first one but not the second one. So I'm trying the 2nd link, but I'm troubling with
browse from disk and select "android_winusb.inf" from "...\android-sdk\extras\google\usb_driver" and select "android bootloader interface.
Click to expand...
Click to collapse
There is no android bootloader interface in my usb_driver folder. Do I need to get it from somewhere like the SDK manager or a website?
Kareem
Kareem_XperiaU said:
Thanks for your reply. Both links are the ones I came across too, I used the first one but not the second one. So I'm trying the 2nd link, but I'm troubling with There is no android bootloader interface in my usb_driver folder. Do I need to get it from somewhere like the SDK manager or a website?
Kareem
Click to expand...
Click to collapse
Windows key + R, write devmgmt.msc, enter.
Plug your phone and look if some device is recognized in the list, it may appear as Android or something like that, if you got it, then follow me.
Right click to it, Update driver, select from computer, use a list from the PC, and "Use disk", see if there's something that says like that because I got Windows 7 in spanish so it's different.
In that browse for the folder that has the .inf file and open it, it returns a list that you have to select the interface, next and your driver may be installed.
Understand? I can explain more but I have Windows in spanish so I don't know how is in english.
Okay.
So I got to Device Manager and when I plug my phone when going in fastboot mode it first appeared as Android but then later on it appeared as Other Device(s) and after a split seconds it goes away. That's because the fastboot doesn't last long since fastbood isn't unlocked yet (and yest bootunlocker:yes is stated on my phone when dialing a code).
Secondly to your explanation. So when I still try to update the driver I can choose to let windows find a driver a use my own software to update it. So I clicked on use my own software, chose the path where the usb_driver is located. But only the folders appear, I can't see the ini or inf. files.
Edit: I'm actually going to downgrade back to windows 7. Since I went to 8.1 it gave a lot of troubles like unsupported screen resolutions and this.
Update: I managed to borrow my sister's laptop for one time, her laptop contains windows 7. So I got on her laptop and took my usb with flash-tool on it and a kernel. I connected my phone with cable while holding the buttons to get in fastboot mode, voila it got recognized by flashtool. I'm one step closer to unlocking bootloader with only one trouble a head. So when I try to unlock my bootloader with a kernel I get an error that my phone needs to be rooted first. The thing is that my phone has been rooted already, plus I just test if it is rooted and the test said that it's rooted. What can be the problem? Not having the right kernel? Not having pc companion on that pc?
Kareem_XperiaU said:
Okay.
So I got to Device Manager and when I plug my phone when going in fastboot mode it first appeared as Android but then later on it appeared as Other Device(s) and after a split seconds it goes away. That's because the fastboot doesn't last long since fastbood isn't unlocked yet (and yest bootunlocker:yes is stated on my phone when dialing a code).
Secondly to your explanation. So when I still try to update the driver I can choose to let windows find a driver a use my own software to update it. So I clicked on use my own software, chose the path where the usb_driver is located. But only the folders appear, I can't see the ini or inf. files.
Edit: I'm actually going to downgrade back to windows 7. Since I went to 8.1 it gave a lot of troubles like unsupported screen resolutions and this.
Update: I managed to borrow my sister's laptop for one time, her laptop contains windows 7. So I got on her laptop and took my usb with flash-tool on it and a kernel. I connected my phone with cable while holding the buttons to get in fastboot mode, voila it got recognized by flashtool. I'm one step closer to unlocking bootloader with only one trouble a head. So when I try to unlock my bootloader with a kernel I get an error that my phone needs to be rooted first. The thing is that my phone has been rooted already, plus I just test if it is rooted and the test said that it's rooted. What can be the problem? Not having the right kernel? Not having pc companion on that pc?
Click to expand...
Click to collapse
Tried to unlock the bootloader with the Sony method?
manudo said:
Tried to unlock the bootloader with the Sony method?
Click to expand...
Click to collapse
Okay I'm going to try it right now, at least I want to but there are some steps very confusing for me.
Sony website said:
9. Download and unzip this file. This is the standard android_winusb.inf-file, with a few lines of code added to enable Fastboot to support Sony and Sony Ericsson devices. Make sure you are running Google USB Driver package revision 4 or higher in your Android SDK. You can see current Google USB Driver package revision in the SDK Manager.
10. Place the unzipped file in the usb_driver folder, located in the Android SDK > extras > google folder on your computer. Accept to replace the old android_winusb.inf-file with the new file. If you can't find the usb_driver folder, please install the Google USB Driver Packager using the Android SDK manager.
11. Turn off your device.
12. On your device, push and hold the Fastboot button at the same time as you connect the device to the computer with a USB-cable. The Fastboot button may differ between different device models. See the Fastboot buttons page for more information on what button use on your device.
13. On your computer, you will be asked for drivers. Point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file.
14. Open a command window and go to the tools folder within the Android SDK folder.
15. Enter fastboot.exe -i 0x0fce getvar version, and verify that you get a response back (for example "0.3"). This means your device is connected properly.
Click to expand...
Click to collapse
13. Well when I connect my phone in fastboot mode it doesn't ask for driver installation, it happens automatic i guess. No problem, right?
14. Do I have to do it like the screenshot?
i1362.photobucket. com/albums/r682/klaskareem/Untitled_zps296a1291.jpg (website protocol needs to be placed in front + remove space between . &com
Kind regards
Kareem_XperiaU said:
Okay I'm going to try it right now, at least I want to but there are some steps very confusing for me.
13. Well when I connect my phone in fastboot mode it doesn't ask for driver installation, it happens automatic i guess. No problem, right?
14. Do I have to do it like the screenshot?
i1362.photobucket. com/albums/r682/klaskareem/Untitled_zps296a1291.jpg (website protocol needs to be placed in front + remove space between . &com
Kind regards
Click to expand...
Click to collapse
13. If your phone is recognized in fastboot mode then continue, if not, update the driver.
14. Know the command "cd"? Is for accesing directories, you can use "dir" to see whats in the folder. Example, you downloaded the Android SDK bundle in the Desktop, then "cd" to the "tools" directory, that contains the binary to unlock the bootloader. That's in cmd.
Like:
Code:
cd /SDK/adt-bundle-blah-blah/sdk/tools
And, you're using Windows 8, again, your device is recognized in fastboot mode?
Thank you for the clear explanation, makes sense now ( already knew that cd thing, wasn't sure though).
Uhm don't mind me using windows 8 atm. I'm downloading 32-bit sdk so I can use it on my sisters laptop.
Kareem_XperiaU said:
Thank you for the clear explanation, makes sense now ( already knew that cd thing, wasn't sure though).
Uhm don't mind me using windows 8 atm. I'm downloading 32-bit sdk so I can use it on my sisters laptop.
Click to expand...
Click to collapse
Right, if anything goes wrong, feel free to ask!
By the way. Do I need to make a copy my ROM I already have? Like when something goes wrong I can still go back to my original android 4.0.4
Kareem_XperiaU said:
By the way. Do I need to make a copy my ROM I already have? Like when something goes wrong I can still go back to my original android 4.0.4
Click to expand...
Click to collapse
It's recommended to keep the stock ROM or any other ROM if anything goes wrong.
Sent from my Xperia Sola using XDA Premium 4 mobile app
manudo said:
It's recommended to keep the stock ROM or any other ROM if anything goes wrong.
Sent from my Xperia Sola using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And how can I do that to be honest?
Kareem_XperiaU said:
And how can I do that to be honest?
Click to expand...
Click to collapse
In this post, there are a list with all stock and custom ROM's available in XDA forum, you should download stock and if anything goes wrong then flash the stock ROM with flashtool. You know, flashmode, select kernel, connect to green led, let it boot, and you have stock.
By now, try to unlock the bootloader, if you need help with the flashing then you can ask by here or create another thread.
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:
`Dear Admin,
Hi my Name is Zaki.... i am using HTC Rezound which i purchased in U.A.E
After installing whatsapp i got continious restart problem so i downloaded stock firmware of ICS version. all was good but by mistake i clear internal storage in fastboot mode. and after that i am unable to get into TWRP Recovery mode, it is showing phone with with arrow circle and after few second it converted into phone with triangle (attached screens 2 and 3) please explain me with links how to get TWRP again. and the links for TWRP versions i am not sure which is ok.
Please Reply.
syedzakiabidi said:
`Dear Admin,
Hi my Name is Zaki.... i am using HTC Rezound which i purchased in U.A.E
After installing whatsapp i got continious restart problem so i downloaded stock firmware of ICS version. all was good but by mistake i clear internal storage in fastboot mode. and after that i am unable to get into TWRP Recovery mode, it is showing phone with with arrow circle and after few second it converted into phone with triangle (attached screens 2 and 3) please explain me with links how to get TWRP again. and the links for TWRP versions i am not sure which is ok.
Please Reply.
Click to expand...
Click to collapse
You can't access TWRP because you over-wrote it with the factory RUU firmware image, it isn't there anymore...
Download TWRP image from TWRP official site at https://dl.twrp.me/vigor/ or Flyhalf's build at http://forum.xda-developers.com/showthread.php?t=1902381
Either one is good... then start fastboot, connect usb and flash recovery with the command:
fastboot flash recovery <path/filename of TWRP IMG file>
give it a minute or so, reboot into Hboot and start TWRP.
im having a similar issue but my computer always says waiting for device in command prompt. I have all the drivers installed and the phone says "usb fastboot" or "fastboot usb" (cant recall what order those 2 words are in LoL)
youdoofus said:
im having a similar issue but my computer always says waiting for device in command prompt. I have all the drivers installed and the phone says "usb fastboot" or "fastboot usb" (cant recall what order those 2 words are in LoL)
Click to expand...
Click to collapse
You probably have a driver issue then... Install HTC Sync, connect the phone, then disconnect it, remove HTC Sync and it should work. If that doesn't work, try a different USB port.
Honestly, I switched to Linux a long time ago... I don't have driver issues. If you were running Linux, even a live or USB key distro, you would access it easily.
acejavelin said:
You probably have a driver issue then... Install HTC Sync, connect the phone, then disconnect it, remove HTC Sync and it should work. If that doesn't work, try a different USB port.
Honestly, I switched to Linux a long time ago... I don't have driver issues. If you were running Linux, even a live or USB key distro, you would access it easily.
Click to expand...
Click to collapse
fair point, and i do have ubuntu (of differing flavor dates) on 3 of my machines, so i might just do that. Thanks!! Ill also try the goofy htcsynch (which i forgot about, as im a Sammy guy now) Thanks again!!
Hey guys sorry if this is newb question but I've been looking for hours and just getting overwhelmed.
I have an SPC glow 10.1 cheap tablet purchased in Spain, apparantly a rebranded Chinese tab.
Android version 6.0, tried rooting with Kingoapp APK which was a complete fake waste of time. Tried framaroot, it said the exploits don't work.
Where should I be looking to be able to root something like this? I.e. which app/project like Xposed or Magisk here?
Thanks a lot
androidferret said:
Hey guys sorry if this is newb question but I've been looking for hours and just getting overwhelmed.
I have an SPC glow 10.1 cheap tablet purchased in Spain, apparantly a rebranded Chinese tab.
Android version 6.0, tried rooting with Kingoapp APK which was a complete fake waste of time. Tried framaroot, it said the exploits don't work.
Where should I be looking to be able to root something like this? I.e. which app/project like Xposed or Magisk here?
Thanks a lot
Click to expand...
Click to collapse
Have you unlocked the bootloader?
Augustoandro said:
Have you unlocked the bootloader?
Click to expand...
Click to collapse
No, I have not, how would you do that? There is no info on the Internet if I search for this brand name SPC.
Is there a way to find out which Chinese tab this is a rebrand of perhaps? Thanks
androidferret said:
No, I have not, how would you do that? There is no info on the Internet if I search for this brand name SPC.
Is there a way to find out which Chinese tab this is a rebrand of perhaps? Thanks
Click to expand...
Click to collapse
Please take a backup of ur data before proceeding further.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and ur phone will reboot.
U can now use Kingoroot or any other tool for rooting.
Thanks Augusto, your advice was great,
it worked so far, but it wasn't easy getting there.
Here's what I did for others:
1. Installed adb and fastboot on my computer from Android developers, turn on debugging on tablet
2. Downloaded universal USB driver installer (aka. koush driver)
3. Installed but adb did not see my tablet, turns out the tablet is not in the list for the USB driver installer
4. Downloaded source code for koush driver, had to modify the .inf file as described in one of the comments on the github page,
by copy pasting two of the existing lines in the inf file and replacing with the USB id codes found from Device Manager in Windows 7.
5. After modifying the .inf file was able to install the driver from Device Manager "Update Driver..." for the Android device
6. Finally after this adb was able to see it under "adb devices"
7. Restart to bootloader with the command "adb reboot bootloader", this entered fastboot on my tablet
8. Tried to run "fastboot devices" but again the phone is not seen.
9. Apparently when in fastboot mode, the tablet appears under completely different USB ids which can be seen in Device Manager
10. Had to go back to the same .inf file and add two more lines with the new Device IDs
11. Installed the driver again in Device Manager, "Update driver"...
12. Now fastboot can see it too!
13. Entered the command "fastboot oem unlock", got the message that the unlock failed!
14. Had to restart tablet in normal mode go into Developer Options and set "OEM unlock"
15. Reboot to fastboot, unlock now works! Reboot phone using "fastboot reboot"
A strange thing happened at this point, the little android figure with cogs in his stomach came up for a few seconds, then the OEM logo for a long time,
after waiting a few minutes I force reset it. It started up but the system was completely erased and put into factory state, including completely erasing every single file I had on it,
even pictures, etc., it asked the first install questions from the very beginning. Fortunately I didn't have anything valuable.
So I got this far, now I'd like to root it,
I tried framaroot, not working, I don't trust Kingoroot, any recommendations for the root method from a reliable source?
androidferret said:
Thanks Augusto, your advice was great,
it worked so far, but it wasn't easy getting there.
Here's what I did for others:
1. Installed adb and fastboot on my computer from Android developers, turn on debugging on tablet
2. Downloaded universal USB driver installer (aka. koush driver)
3. Installed but adb did not see my tablet, turns out the tablet is not in the list for the USB driver installer
4. Downloaded source code for koush driver, had to modify the .inf file as described in one of the comments on the github page,
by copy pasting two of the existing lines in the inf file and replacing with the USB id codes found from Device Manager in Windows 7.
5. After modifying the .inf file was able to install the driver from Device Manager "Update Driver..." for the Android device
6. Finally after this adb was able to see it under "adb devices"
7. Restart to bootloader with the command "adb reboot bootloader", this entered fastboot on my tablet
8. Tried to run "fastboot devices" but again the phone is not seen.
9. Apparently when in fastboot mode, the tablet appears under completely different USB ids which can be seen in Device Manager
10. Had to go back to the same .inf file and add two more lines with the new Device IDs
11. Installed the driver again in Device Manager, "Update driver"...
12. Now fastboot can see it too!
13. Entered the command "fastboot oem unlock", got the message that the unlock failed!
14. Had to restart tablet in normal mode go into Developer Options and set "OEM unlock"
15. Reboot to fastboot, unlock now works! Reboot phone using "fastboot reboot"
A strange thing happened at this point, the little android figure with cogs in his stomach came up for a few seconds, then the OEM logo for a long time,
after waiting a few minutes I force reset it. It started up but the system was completely erased and put into factory state, including completely erasing every single file I had on it,
even pictures, etc., it asked the first install questions from the very beginning. Fortunately I didn't have anything valuable.
So I got this far, now I'd like to root it,
I tried framaroot, not working, I don't trust Kingoroot, any recommendations for the root method from a reliable source?
Click to expand...
Click to collapse
I told you to take backup of your data beforehand.
I am recommending Kingoroot because I personally used it to root my phone.
Augustoandro said:
I told you to take backup of your data beforehand.
I am recommending Kingoroot because I personally used it to root my phone.
Click to expand...
Click to collapse
I know about the backup, I just wasn't expecting it to wipe everything, I don't know why it did that.
As for Kingoroot, I installed the official app from play store which was a completely fake and dangerous looking piece of crap,
it showed like 50 ads asked me to rate it and then some weird pop ups kept coming, and then it did nothing. No message whatsoever.
Thank god my phone wasn't rooted because
I don't know what the lowlifes who do KingoRoot would have done with it.
I don't trust this company to install their software on my computer and I can't believe you guys recommend such an obviously
unscrupulous, malware product to others. Why is KingoRoot even on Google Play, they should be among the trojan trash of the every single antivirus and antimalware.
androidferret said:
I know about the backup, I just wasn't expecting it to wipe everything, I don't know why it did that.
As for Kingoroot, I installed the official app from play store which was a completely fake and dangerous looking piece of crap,
it showed like 50 ads asked me to rate it and then some weird pop ups kept coming, and then it did nothing. No message whatsoever.
Thank god my phone wasn't rooted because
I don't know what the lowlifes who do KingoRoot would have done with it.
I don't trust this company to install their software on my computer and I can't believe you guys recommend such an obviously
unscrupulous, malware product to others. Why is KingoRoot even on Google Play, they should be among the trojan trash of the every single antivirus and antimalware.
Click to expand...
Click to collapse
I meant Kingoroot for PC and not Kingoroot Android.
They are different, although from the same company.
Wow it turns out I was using a fake Kingoroot from the Play Store so I take back my comments regarding KingoRoot.
I can't believe the Play Store allows such trash.