[Q] fastboot broblem - Folio 100 General

hi at all sorry for my english
i have a problem with my folio, i installed mod1.4 and my tab worked very well the i tryed to install mod3.x and cm7
now i want to back at mod 1.4 , i installed update.zip then i wise and i complete installation 1.4 introducing language time zone ecc ecc and my folio start . then if i turn off and i turn on it after toshiba logo my tab show only a black page and dont start mod1.4, if i reset at default or i wise it start correcltly but if i turn off it dont restart. I installed android sdk and i modify ini for install adb driver ant when i type adb i see a serial number, i try to start it in fastboot mode power 3 times then vol up then i connect at my pc and i type fastboot devices but i cant see serial number so i cant use fastboot -w , in adb if i type adb devices i see serial , can anyone help me? if i install stock mod 3.x or cm7 i can turn off and on but in mod 1.4 i cant and i want to use mod 1.4 for my wife.
Many tanks

I've the same problem!!!
Can someone help me?

Related

[Q] HELP

I have tryed to install a new ROM into my ViewPad7 and suddenly the tablet disconnected and got without energy. I did not realized power level before.
Now, it does not start (showing the WELCOME message) and if I would push the Recovery mode it stops with BIRDS image on screen.
Someone can help and send me any instructions to fix it?
My personal email [email protected]
Thanks in advance to the forum
Jorge
Try Adb shell yet?
Sent from my ViewPad7 using xda premium
I have no access to the device. After power the VPad appear the "Birds" on the screen and a few seconds later the "Welcome" message. This message remains on screen until battery runs off.
I tryed accessing the root (pressing both volume and switch on button simultaneously) and it appears "enter Recovery mode" on the upper left corner of the screen together with "Birds". This screen also remains forever until battery discharge completly.
I connected the tablet to the PC but I did not find any executable system file. If I try to copy any new file into the tablet it comes up the message "drive unwritable".
So, how can I access ADB shell?
What can I do to reinstal a new ROM?
Thanks for yr help
If u dont wanna try by yourself , bring it to provider.
But if u wanna try, connect your viewpad to computer.
Setup driver from new drive.
Open adb from new drive or other tools from internet.
You can flash new rom from sut 1.7 or fixed boot, but every way have a detail u must lean.
Sent from my ViewPad7 using xda premium
Can you detail how to access ADB?
I did not understand your explanation.
http://www.youtube.com/results?search_query=how+to+adb+android&oq=how+to+adb+android&aq=f&aqi=&aql=&gs_l=youtube-psuggest.3...91.539.0.695.5.5.0.0.0.0.0.0..0.0.
ADB is tool for u can change(i don't know how much it can do) some file or fix something in you pad.
If u can use ADB login to your pad. I think u can use SUT 1.7 to flash stock rom too.
And u can google for find the way to fix from ADB by yourself. I'm just try to help at first step , with my weak english.

Need help on micromax a56

hello devs,
today i just use a tool name Android platina , its a Varun Chitres Tools, i dont blame him but i got an problem when i try to use this tool
I have Mictromax A56 Devices (Rooted)
i just make an custom splash Image and just write it useing this tool, but mistakenly erased system
now i try to flash it using fastboot method like this
Volum Down Button + Power on
then type this command
on adb ( C/Program Files/Android/android-sdk/platform-tools) using Command Prompt
fastboot flash system system.img but i got an error
here is
failed to send (too many links)
i found a solution im somewhere in internet here in XDA site,
1. try using another usb port on your laptop to connect the phone.
2. try with another USB cable (from your friends NOKIA or SAMSUNG or HTC etc which fits in A56 jack) to connect the phone.
3. Use a different pc to do it. Or format your entire C: drive and reinstall windows again( i.e make your existing pc new one) make sure you have all drivers and windows CD.
4. Use a windows XP/vista machine....(or if you are on vista/xp then change to win7)
5. open fastboot and when it says "waiting for device" then connect your phone. Dont connect it before hand.
i try all of this one by one but no success!
its onl hang on logo
so now anyone can help me to solve this ?
i have all i need Recovery+Boot+System image also system.tar and flasher Qualcomm Flasher call QPST also work in newly released A100 !
someone please help me to solve this.
also if any one have custom recovery for this set and custom ROM for this then provide me here. please i really thank full if got help.

HP 7 VoiceTab 1321RA Bricked without Recovery or Custom Recovery mode accessable

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:

I have a nokia x2 RM1013 which is dead. I need urgent help

I yesterday switched off my phone and when i tried to power onn nothing happened when i put my phone on charging no charging animation was shown. Nothing is working. My phone had cynogen mod. My phone is nokia x2ds RM1013.plz help.. Sry for bad english
Hi , maybe your battery is bad or you need to flash your OS:
here you have example what to do
https://www.youtube.com/watch?v=Ojo7yL6lJFk
I have done something here...
I tried to fix it with Qfil ... i did everything right ... i installed qdloader driver ... but when i try to flash i get error ... here is the log file
Start Download
COM Port number:3
Switch To EDL
Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode
Finish Download
i tried installing emergency download driver but it says you have already new version installed
help
Teddy Lo said:
Hi , maybe your battery is bad or you need to flash your OS:
here you have example what to do
https://www.youtube.com/watch?v=Ojo7yL6lJFk
Click to expand...
Click to collapse
I need more help
sankalp21 said:
I need more help
Click to expand...
Click to collapse
Look if your device is in fastboot recognised , to do that install ADB & fastboot minimal installer , once you installed open adb folder , Hold shift and right click on mouse to Open Command windows here
ADB how to install :
https://forum.xda-developers.com/showthread.php?t=2588979
now once you open command line , plug your device and write fastboot devices and see if is recognized like some numbers , or adb devices is is recognised in fastboot write reboot edl if the command was succsefull re-flash again your device .
Help me with my dead Nokia X2 RM1013
My Nokia X2 RM1013 is in coma since 3 to 4 years from now.... Can anyone please help me....
WhatsApp +918494066641

a blocked Cool 1

hi ,
i have installed a costum rom for my cool 1 c103 android 7.1
then i installed i different twrp so
it blocked when entring recovery mode is block at recovery picture
did not load
i tried to instal correct twrp by apps and root but did not work
Now , phone block and did not load in recover or normal mode
just turn on and stuck
tried adb flashing (cmd adb device not appear even by fastboot devices did nt appear )and by qfile but it seems not detected
all drivers are correct which used in 1st time (when connect phone hear sound of connect & no exclamation mark)

Categories

Resources