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:
Hi,
I got update for my htc nexus 9(7.1 Update). It automatically updated and when i woke up the phone was bricked.Its in welcome screen and touch isnt working at all. volume,Power keys are working.
So i tried to unlock the bootloader and flash a new rom.
Note: device isnt rooted.Oem is not unlocked and usb debugging not enabled in developer option.
contacted htc service centre but its of no use.they wont service tabs and they dont even touch usa products.
Tried different videos.Downloaded rom,recovery and installed fastboot and adb drivers in my pc.
when i try using the command prompt, its showing under fastboot devices but it isnt showing under adb devices.
adb is showing the commands,but no adb command is working for the device.
Need help in unlocking bootloader and installing custom rom.
Am not a pro or a coder. I just root for fun. dont have any knowledge about these things.
So someone please guide me in solving the issue.
Hello sir. Sorry to hear about your device.
First adb doesn't work in fastboot. Everything is well fastboot
My advice to you is Dw about any of that. Run over to a really helpful guy, called wugfresh. He has a hole tool kit. I use it all the time it's excellent. It should sort you out no problem . If it doesn't give me a shout and I'll see if I can be of assistance
braga94 said:
Hi,
I got update for my htc nexus 9(7.1 Update). It automatically updated and when i woke up the phone was bricked.Its in welcome screen and touch isnt working at all. volume,Power keys are working.
So i tried to unlock the bootloader and flash a new rom.
Note: device isnt rooted.Oem is not unlocked and usb debugging not enabled in developer option.
contacted htc service centre but its of no use.they wont service tabs and they dont even touch usa products.
Tried different videos.Downloaded rom,recovery and installed fastboot and adb drivers in my pc.
when i try using the command prompt, its showing under fastboot devices but it isnt showing under adb devices.
adb is showing the commands,but no adb command is working for the device.
Need help in unlocking bootloader and installing custom rom.
Am not a pro or a coder. I just root for fun. dont have any knowledge about these things.
So someone please guide me in solving the issue.
Click to expand...
Click to collapse
you can try flashing the full OTA update
then do a factory reset.
https://developers.google.com/android/ota
1. boot into recovery
2. adb sideload "location of the OTA"
3. reboot into recovery
4. factory reset
Hello everyone, I hope one of you could help me.
I've been using a 8.1 LOS ROM for some time but I want to get back to stock to use Android Pay and avoid a lot of the bugs I've been experiencing lately.
To be able to flash Oreo, I remember I had to install a modified kernel, so I don't know if it has anything to do with it.
My PC nor my Mac were able to detect my phone on ADB or fastboot anymore, so I flashed the most recent system.img and boot.img provided by erfanoabdi on androidfilehost and was able to get a stockish phone, but no OTA, since I still have TWRP.
I tried uninstalling and reinstalling phone drivers, ADB and fastboot too, but nothing happens when I connect my phone to the PC.
I have revoked ADB permissions but even so I don't get the prompt to allow USB debug when I connect it, even though I have the option enabled under developer menu.
I really don't know what else to do and have tried many of the suggestions here, but maybe the problem might be something else entirely.
Guys, I installed the ROM Pixel Experience. This one:
https://forum.xda-developers.com/mi-pad-4/development/rom-pixelexperience-t3878616
I am having a huge issue with this rom. I installed it and it works fine, however, since it doesn't support USB, I decided to install the MIUI stock rom back. Well, in order to do that, you have to have the device in FASTBOOT mode.
When I go to the prompt and type fastboot devices, I get a result, showing that my computer can detect the device.
However, every time I am in FASTBOOT mode, after 30 seconds (exactly!) it reboots. So, I am afraid to start flashing it and then the device reboots and my installation gets corrupted.
Any ideas on how to solve this? I just need the FASTBOOT mode to last as long as necessary for me to install the older room back.
Can you explain what you mean by "Doesnt support USB"?
And the fastboot issue is definitely weird. That should not be happening. Does this happen when the device is plugged in only? What happens if the device is not plugged to the computer?
Hi,
I've got a problem where my phone is stuck in bootloop and I cannot go into recovery mode. All I can get into is fastboot mode. I know there's a way to get into recovery from fastboot mode using ADB but I do not know what to do or what steps to follow as I really don't know much about modding phones apart from flashing a ROM that I wan't to use via recovery (which I assume even a ten year old would be able to do effortlessly after seeing it being done once or twice).
I am using the global 4/64 Redmi Note 4 running the latest version of Android Open Source Illusion Project.
Any help would be appreciated. Thank you.
laneofmagic said:
Hi,
I've got a problem where my phone is stuck in bootloop and I cannot go into recovery mode. All I can get into is fastboot mode. I know there's a way to get into recovery from fastboot mode using ADB but I do not know what to do or what steps to follow as I really don't know much about modding phones apart from flashing a ROM that I wan't to use via recovery (which I assume even a ten year old would be able to do effortlessly after seeing it being done once or twice).
I am using the global 4/64 Redmi Note 4 running the latest version of Android Open Source Illusion Project.
Any help would be appreciated. Thank you.
Click to expand...
Click to collapse
Did you try combo key? Holding Power and Volume+ buttons?
If this doesn't works, you have to set up ADB bridge on your PC. Here is the guide: https://www.xda-developers.com/install-adb-windows-macos-linux/
When you do that, type the command via ADB while being in fastboot mode:
fastboot reboot recovery
This should take you into the recovery mode.
Any help please Im stuck in a boot loop and recovery and fastboot are inaccessible, so i cant send any commands? im forking on Mac OS but even ive installed a virtual PC to try some of the countless programs but no seams to work since the phone is not recognized.