Hi everyone
I recently got my first android phone - Samsung Galaxy W.
I decided to install a custom rom. Before that i had to root my phone which i did without any problems. After that i had to flash ClockworkMod v5.5.0.4. I downloaded the file which was in zip however i didn't extract it (which is what i should have done) and copied into my phone's memory. After that i put this code in the command promt
adb shell
$su
#dd if=/sdcard/
recovery-clockwork-5.5.0.4-ancora.zip of=/dev/block/mmcblk0p13
After rebooting the phone i can only get into the download mode in which nothing happens. And when i connent the phone to my pc the computer doesn't detect that my phone is connected. What shall i do now? Is my phone a brick now?
Okay i found out that my pc detects my phone however it is marked as unspecified device which means that i can't do anything with it.
Tommorow i install ubuntu and see if i will be able to connect to it.
Any other suggestions?
I'm new to rooting and all of this type of thing, i figured I would first start with my HTC Flyer. I successfully unlocked the bootloader, and installed SuperUser, upon installing greenify and i tried to install the Xposed Framework, and my device now is stuck in a boot loop.
When enter the bootloader and do a factory reset or try to enter factory it completely freezes, and when i try to connect it to my PC via fastboot the PC says that the USB device that is connected cannot be recognized and fastboot will not work. Did i completely fry this device? Also if you have time I couldnt figure out a proper way to flash a custom rom so if anyone has a guide for that I would appreciate a link to that as well.
Thank you so much!!
AH **** I REALLY MESSED UP! I unlocked my bootloader then later on I wanted to try out a different version of CM so I went ahead and booted into my CWM touch and I never did replace that v6.bin yet so my touch screen is wonky still. I installed CM 10.2 by BobZhome and now I can't get back into CWM to cat the v6.bin file to fix the touch screen. I also don't have any gapps installed and when I plug in my phone to my computer it won't let me transfer files to the phone memory storage. I also don't have a SD card now because I lost it. I was able to use the fastboot trick to flash the cwm recovery but it still won't let me back into recovery.. I think because the internal memory is blank because of me installing cm 10.2.. I also tried enabling usb debugging mode on the phone with cm 10.2 so I could try to adb and get a shell but it won't work it keeps saying the device is offline... WHAT SHOULD I DO SOMEONE PLEASE HALP ME!!!
CygnusBlack said:
AH **** I REALLY MESSED UP! I unlocked my bootloader then later on I wanted to try out a different version of CM so I went ahead and booted into my CWM touch and I never did replace that v6.bin yet so my touch screen is wonky still. I installed CM 10.2 by BobZhome and now I can't get back into CWM to cat the v6.bin file to fix the touch screen. I also don't have any gapps installed and when I plug in my phone to my computer it won't let me transfer files to the phone memory storage. I also don't have a SD card now because I lost it. I was able to use the fastboot trick to flash the cwm recovery but it still won't let me back into recovery.. I think because the internal memory is blank because of me installing cm 10.2.. I also tried enabling usb debugging mode on the phone with cm 10.2 so I could try to adb and get a shell but it won't work it keeps saying the device is offline... WHAT SHOULD I DO SOMEONE PLEASE HALP ME!!!
Click to expand...
Click to collapse
I had never succeded in unlocking my P768, but everytime i messed up this bad with the phone, the only way to fix it was by reinstalling the software with LG Tool. I don't know if this "locks" the bootloader again, it shoudn't but at least you will have a phone by doing this. Not even adb is accessible in your case, complicated..
My advice is reflash stock rom via LGTool, then you install CM/CWM againwith the screen fixed
back at it again
Ok I just got off work again and I was messing around with it again. I am able to reboot into the touch recovery from CM 10.2 because I was able to enable the developer options and then enable reboot into recovery option from reboot menu. I tried enabling debugging mode but the computer will not recognize the device at all. I use to be able to use adb from CWM Recovery by changing the driver to adb in the device manager however now my device manager is not even showing adb as an option to install now! LOL! I was trying to use the terminal emulator in CM 10.2 but it's ****ing impossible to use with that wonky touch screen. I wrote a shell script and uploaded it to a SD card I got today and then I ran the terminal emulator and managed to do the su command and then I did cd into the external sd card and I tried to bash the script by doing ./a.sh
cat v6.bin > ../../../../../../sys/devices/virtual/input/lge_touch/firmware
then it told me permission denied even though I was SU! LMFAO!!!!!
I'm at my wits ****ing end with this thing I mean HOLY ****! I just can't be bothered with it anymore. I think I'll take it outside later and smash it to pieces.
unless someone knows of anything I can do?! Please don't say to restore original rom because for some reason the computer just won't recognize this ****ing thing.. even in S/W upgrade mode it doesn't install the driver!
CygnusBlack said:
Ok I just got off work again and I was messing around with it again. I am able to reboot into the touch recovery from CM 10.2 because I was able to enable the developer options and then enable reboot into recovery option from reboot menu. I tried enabling debugging mode but the computer will not recognize the device at all. I use to be able to use adb from CWM Recovery by changing the driver to adb in the device manager however now my device manager is not even showing adb as an option to install now! LOL! I was trying to use the terminal emulator in CM 10.2 but it's ****ing impossible to use with that wonky touch screen. I wrote a shell script and uploaded it to a SD card I got today and then I ran the terminal emulator and managed to do the su command and then I did cd into the external sd card and I tried to bash the script by doing ./a.sh
cat v6.bin > ../../../../../../sys/devices/virtual/input/lge_touch/firmware
then it told me permission denied even though I was SU! LMFAO!!!!!
I'm at my wits ****ing end with this thing I mean HOLY ****! I just can't be bothered with it anymore. I think I'll take it outside later and smash it to pieces.
unless someone knows of anything I can do?! Please don't say to restore original rom because for some reason the computer just won't recognize this ****ing thing.. even in S/W upgrade mode it doesn't install the driver!
Click to expand...
Click to collapse
cant you fastboot recovery and do it that way?
Cobra11Murderer said:
cant you fastboot recovery and do it that way?
Click to expand...
Click to collapse
I already used the fastboot trick to flash recovery. I flashed the CWM touch.img then in cyanogenmod i can make it reboot into cwm recovery. But the thing is now my computer will not recognize the drivers for this device so I can't get adb to work with it. ADB will also not work in cyanogenmod for me because of the drivers not being recognized. ADB doesn't even show up in my device manager in windows when I tried to force it to be recognized as an adb interface. Now I think I need adb to work in CWM recovery because that's the only way I can cat the v6.bin file to fix the wonky touch screen. I can't use the terminal emulator to cat the bin file while within cyanogenmod because it's being used while in cyanogenmod that's why I got a permission denied result when I tried to run the command.
I also don't have a backup of my rom or I would have already restored backup from cwm to get the computer to recognize the drivers and then I would have reinstalled the original rom/firmware with lg flash tool.
It won't even let me restore the rom/firmware while in S/W upgrade mode because the lg tool won't recognize the device!
The only way I see out of this now is to get someone here to make me a CWM backup of their europe open rom so then I can download your backup put it on my sd card and restore it from there.. then drivers will recognize and I can flash back to stock rom with lg tool then reroot, rerecovery install and then install cyanogenmod 11 kitkat.
So if someone could do that for me I would be eternally grateful.
FIXED IT!!!
Nevermind. I was able to find a flashable zip that fixes the touch screen issue. Thank God I found that and was able to get a new SD Card otherwise I wouldn't have been able to flash that touch screen fix from the CWM Recovery! Woo! Now I can complete my other guide so no one else comes across these problems!
hello, sorry if I will open new threat but I am super lost... and sorry for my english.. I am from Slovenia... Yesterday I just root my lg g2 d802... But when I was wanted to install bootloader my phone write me some error... but this is not important because I was repaired in ubuntu with terminal.. so I am now stuck in TWRP bootloader... Whatever I want to do nothing is possible.. I was done everything... wipe, erase, hard reset reboot even writing codes in TWRP terminals... I cant get it fastboot because I always get same errors... When I am in cmd i write adb devices and I get some serial number and recovery mode... even if I try reboot bootloader I get same respond... I am without hope not... I was trying everything what I was see on the youtube and xda forums... I am now without options and with my precious phone stucked in twrp ... ohh yea one more thing... I have instaled all drivers and everything even adb universal drivers... my computer does not recognized my phone in download mode... please respond and help me saving my little precious :crying::crying:
Kdz installation with usb connected to the pc and flashtool _ easy way
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: