hey guys i need some help or any idea, bout this but i was downloading the CM9 nightlys and of course i reboot to recovery, i install the nightlys and once its done i rebooted it n now we have the problem it reboots back, now i was bout to try to do the trick of one of the threads i read with the CMD but now my tablet wont mount. any ideas whats going on and how can i put this back to work and i know its not bricked any help with this
bjudyE thick
Hey,
I've the same problem what do u mean with cmd trick?? with adb shell ?
yea with the ADB shell u can take the bootlooping but for some reason my tablet is not mounting
Did u wipe data????
yea i did all of that its still bootlooping dont know why this never happen to me till now
Clear everything and push a rom to sd card with adb
This will help
I was stuck on that loop too with out any ROMS on the SD card I was only able to use fastboot and Recovery. This tool helped me. This tool will access your tablet even if you are stuck on the splash screen.
http://forum.xda-developers.com/showthread.php?t=1599991
but the thing is that its not mounting to the computer like the computer wont read it but if i put my phone it reads it and the thing is its not letting me fastboot
Related
Hi everyone,
Well I'm in that freak out stage.... where I am sure some of you have been.
Heres my issue...
I have a transformer prime that;
I just unrooted using Vipermod
Then did a factory reset
Now I am stuck in CWM recovery
I attempted to do a restore but after it gets done it brings me back into the recovery
I attempted to ADB but the command prompt opens and closes right away ( I assume from not being in USB debugging, which I cant get into without a rom)
I have no rom's currently downloaded into the prime as I just wiped everything in there as well.
Please i'll gladly pay $5 to anyone who can fix this without it breaking more (hard bricking if I havent already done so)
AHHH please guys help, I'm afraid it will run out of battery soon then I'll be royally screwedddd
anyone?
are you on windows 7?
yes windows 7 professional sp 1 32bit . to reiterate I am stuck in Clockwork mod Recovery without root, and with no roms on the internal SD. I have access to one restore that works but after it completes it reboots back in recovery.
birchnick10 said:
yes windows 7 professional sp 1 32bit . to reiterate I am stuck in Clockwork mod Recovery without root, and with no roms on the internal SD. I have access to one restore that works but after it completes it reboots back in recovery.
Click to expand...
Click to collapse
Turn on your tablet, let it boot into CWM.
Open cmd, cd to the directory with adb (for example cd C:\android), then copy this line of text below and right click > paste in the command prompt window.
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
Click to expand...
Click to collapse
That should get you out of CWM into Android, assuming your restore works fine.
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
can i fastboot push a rom to the internal sd card or better yet can i install a rom from the external SD card via Clockwork mod recovery?
birchnick10 said:
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
Click to expand...
Click to collapse
Navigate to %android sdk folder%\extras\google\usb_driver, open android_winusb.inf and copy the following in the sections
"Google.NTx86" and "Google.NTamd64"
; TF201
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4D01&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4D03&MI_02
;
; Fastboot for all projects
%SingleBootLoaderInterface% = USB_Install, USB\VID_0B05&PID_4DAF
Click to expand...
Click to collapse
Save the file and then try running the adb command I gave again.
Says error device not found. I appreciate the help keep it coming it's keeping my hope alive. I really hope this isnt truly hard bricked.
I cant get ADB to read the transformer prime. When I type adb devices nothing shows up . it starts the daemon successfully but then doesn't show the tfp.
Thank you again for helping. I am honestly going to pay who ever finds the true fix. This stress sucks
birchnick10 said:
Says error device not found. I appreciate the help keep it coming it's keeping my hope alive. I really hope this isnt truly hard bricked.
I cant get ADB to read the transformer prime. When I type adb devices nothing shows up . it starts the daemon successfully but then doesn't show the tfp.
Thank you again for helping. I am honestly going to pay who ever finds the true fix. This stress sucks
Click to expand...
Click to collapse
Try the instructions here. Try using this only as a last-ditch resort.
it wont shut off either... i tried both of the above mentions and cant get adb to recognize the prime
Attempted both and stuck at recovery loop without root. any more ideas? is it possible to flash rom from external sd? or is there a recovery I could fastboot rhat has this feature?
Attempted both and neither work. I need to somehow get usb debugging enabled while in clockwork mod. Or figure out a way to install a rom via external SD card while in CWM. Any more help is appreciated!
birchnick10 said:
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
Click to expand...
Click to collapse
No adb debugging is needed in cwm. Even without any ROM installed. Recovery is different from Android.
Try to long press power (at least ten seconds) to hard reboot, and see if it changes something in device detection.
Did a hard reset and it boots me back into Recovery.
I was able to get a new rom into the internal SD via the emergency/backup.zip method but after it completes and I do a reboot it just boots right back into recovery again.
Any help please is apprecaited.
$5 bounty for a fix via paypal
Oh joy. This one is a spaghetti western in the making.
Okay. Question first : Does Windows 7 RECOGNISE the device in any way shape or form. To find out if this can be done, you need to power up the device and hold the power and volume down buttons, DO NOT press volume up when it suggests a kernel image. If you get three icons, hit vol down once and up once, then plug the USB cable into the PC and the tablet.
If it sees "Something", you've a chance. Download the naked universal USB driver from the dev forum, install it and have your device pick it up on the windows computer. I'm assuming from your comments that you've GOT a working fastboot and adb so I'm going to skip the instructions on that.
If you do have a something, and it's recognised, hit fastboot -i 0x0b05 reboot, if it reboots of it's own accord at this point, you can confirm you have working ADB and Fastboot access. From there you've a few choices. My personal preference would be to ADB push a rom down -after- doing a rebuild of the recovery image via fastboot (I really recommend TWRP for this bit).
http://forum.xda-developers.com/showthread.php?p=26093546#post26093546 - This post here which I wrote will explain how to flash TWRP from fastboot access, presuming you can get it. Once that step is done, wipe EVERYTHING from TWRP, and I mean the whole nine yards, including /system. Raze the memory down to only things it can't actually nuke. Once that's done, reboot to fastboot protocol, get a ROM pushed via ADB and install from inside TWRP.
That -should- get you back in business. Though judging by the tangle you're in, I make no promises.
ADB wont recognize the device. I have installed and uninstalled the drivers about 5 times.
It wont boot into fastboot - just goes directly into Clockwork Mod recovery. Even while holding power and volume down text comes up that says looking for asus recovery. then says clockwork recovery and boots directly into that.
The only way I can get anything into the internal SD card is with MasterZen88's Emergency script tool that puts any 1 file into the internal SD card as backup.zip
It was unrooted prior to all of this as well.
*cringe*
If ADB isn't working -at all- and it's not using the naked USB drivers to get you any kind of workable access. You're starting to smell very much like a hard brick scenario. I'm honestly not sure if there's a way out of that. A lot of the solutions for unbricking absolutely require that the device is able to talk to the outside world, if it's not and the ADB shell is essentially telling you it's talking to dead air, you're in a world of pain.
It's a long shot but it may be worth speaking to ASUS to see if they are willing to, for a fee, restore your tablet to factory settings. Though I can't imagine that will be cheap or simple. If you are able to get an RMA or a means of getting ASUS to poke it, make sure to take photos. Their techies appear to have the worst case of butterfingers in the world.
Go over Pandaball's suggestion, because that's really the last step I can think of before contacting ASUS
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!!
I had NOS Google Play ROM on my phone, but now it won't boot up and I forgot to set a backup file. Now I am stuck in TWRP since I can't boot up the phone. Also, I deleted the ROM file from my phone. Yes call me stupid all you want but I seriously need this fixed.
So what happens is, I boot the phone, goes to the boot screen, and shows it is booting, but it never does boot. It's in some kind of an infinite loop.
On top of that, I can't transfer files in TWRP!!
Does anyone know how to fix this? I know there is a fix to this, but I can't seem to get any to work or most just don't make any sense.
If you have boot loader unlocked (most likely) try fastboot flashing boot.img in fastboot mode
Sent from my DNA
hddr3 said:
I had NOS Google Play ROM on my phone, but now it won't boot up and I forgot to set a backup file. Now I am stuck in TWRP since I can't boot up the phone. Also, I deleted the ROM file from my phone. Yes call me stupid all you want but I seriously need this fixed.
So what happens is, I boot the phone, goes to the boot screen, and shows it is booting, but it never does boot. It's in some kind of an infinite loop.
On top of that, I can't transfer files in TWRP!!
Does anyone know how to fix this? I know there is a fix to this, but I can't seem to get any to work or most just don't make any sense.
Click to expand...
Click to collapse
USB OTG Cable, thumbdrive, rom image on thumbdrive, install from external SD.
Boot into recovery and connect the device to your pc and open a terminal and type in adb devices to make sure the pc recognizes your phone and it should. The just adb push a different Rom to the sdcard wait for that to finish and flash. Or if you can get adb sideload to work you can do that too.
You can use adb push/pull in recovery without mounting anything or at least it works for me...
Sent from my dlx using XDA Premium HD app
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!
could anyone help with a seemingly bricked tab speed 6, attempted to root using kingoroot and it failed causing connection issues to google so i was unable to add a account, after hard reset and booting in to recovery i have wiped the cache and reset to factory, however now the tablet is stuck on checking connection and doesn't go any further with or without sim card.
after searching and searching i have come up with nothing apart from this threadhttp://forum.xda-developers.com/general/xda-assist/stock-rom-vodafone-speed-tab-6-vf-1397-t3329343
it looks as though he is having the same problem.
assuming kingoroot has corrupted the rom and i need to reflash to repair it,
i don't know if it is a generic tablet it appears to be made by alcatel but im unsure.
i also do not know if i could use a firmware from another device or even custom rom, anything will do as long as it doesn't end up in the bin
i also have another which hasnt been messed with and was wondering if it would be possible to back up the rom from it and reflash it to the bricked one, if so could anyone steer me in the right direction
could anyone help me locate as rom and flashing tool that will help
thanks in advance, apologies if this is posted in the wrong place.
You said you had a second one, you don't have to root it, just follow this tutorial and hopefully you should be good to go.
no bootloader
hi thanks for your reply however upon backing up the other tablet, it had still not solved the problem does that tutorial back up the Rom or just system files I created the backup.ab and used adb recovery to no avail...., however, I gave up on this method and was going to use a custom recovery on the the working tablet to back up the rom, however when I tell adb to reboot to the downloader it just reboots the tablet there seams to be no downloader on either tablet, so even if I had the rom it appears I could not flash it via the downloader as I can't get to it, nor sd card as there is no option to flash it, it's really bugging me now as it's obviously only soft bricked, any more help would be greatly appreciated thanks in advance also to add fastboot lists the device but when I tell it write the recovery it says waiting for device
inexperience
thanks for the help I am quiet inexperienced but determined so any help pointing me in the right direction would help thanks
facerolla said:
hi thanks for your reply however upon backing up the other tablet, it had still not solved the problem does that tutorial back up the Rom or just system files I created the backup.ab and used adb recovery to no avail...., however, I gave up on this method and was going to use a custom recovery on the the working tablet to back up the rom, however when I tell adb to reboot to the downloader it just reboots the tablet there seams to be no downloader on either tablet, so even if I had the rom it appears I could not flash it via the downloader as I can't get to it, nor sd card as there is no option to flash it, it's really bugging me now as it's obviously only soft bricked, any more help would be greatly appreciated thanks in advance also to add fastboot lists the device but when I tell it write the recovery it says waiting for device
Click to expand...
Click to collapse
What command do you do to tell adb to reboot to download? What command to you give fastboot to flash the recovery?
hi thanks for the quick reply im ujsing adb reboot-bootloader , it reboots the tablet and then greats me with the vodafone start up logo then asks me which country im in, as for attempting to flash with fastboot ive tried fastboot oem unlock to unlock the bootloader ( says waiting for device) ive also tried adb push c:\adb\backup.ab ( doesnt seam to recognise the psush command as it cycles through all available commands , and attempted to flash recovery with fastboot flash recvovery cwm.zip ( says waiting for device) adb reboot sideload just reboots the tablet same as adb reboot bootloader, thanks for all your help.., ikt is really bugging me i appreciate your time.
I don't know if download mode is accessed differently I've found this post that seems to Suggest hold volume up and down then connect until battery charging appears http://forum.gsmhosting.com/vbb/f272/vf-1397-a-2047715/ this is for unlocking it seems, but don't seam to be able to get it to work, earlier I removed root with kingoroot from kingoroot app, also to no avail and rooted again both root removal and rooting were successful but still tablet stays on the checking connection screen when rebooted, I was hoping the removal may of fixed the issue but no...., I was thinking if I could get back custom recovery on it I could do the same to the working one I have begrudgingly so I could back up the working ones rom and use it to flash the bricked one, but I don't really want to risk bricking that one either, but was considering finding another rom from another model the same chipset and flash it with that but obviously no download mode means I can't do it..
if it's any help The recovery mode states android system recovery <3e>
LMY47V release keys
reboot system now
wipe data/factory reset
wipe cache partition
power down
enable adb
they are the only options,
again thanks for all your time and effort
facerolla said:
hi thanks for the quick reply im ujsing adb reboot-bootloader , it reboots the tablet and then greats me with the vodafone start up logo then asks me which country im in, as for attempting to flash with fastboot ive tried fastboot oem unlock to unlock the bootloader ( says waiting for device) ive also tried adb push c:\adb\backup.ab ( doesnt seam to recognise the psush command as it cycles through all available commands , and attempted to flash recovery with fastboot flash recvovery cwm.zip ( says waiting for device) adb reboot sideload just reboots the tablet same as adb reboot bootloader, thanks for all your help.., ikt is really bugging me i appreciate your time.
Click to expand...
Click to collapse
You can't always unlock the bootloader via that command and you'll need to have the bootloader unlocked to flash a custom recovery, if you can find stock images on the web you can flash them via fastboot.
---------- Post added at 12:44 PM ---------- Previous post was at 12:36 PM ----------
Also to restore an adb backup you do "adb restore filename".
unfortunately there is no stock image anywhere on the Web, is there a good app I could use to save the rom from the working tablet without rooting, really don't want to risk rooting the working tablet
facerolla said:
unfortunately there is no stock image anywhere on the Web, is there a good app I could use to save the rom from the working tablet without rooting, really don't want to risk rooting the working tablet
Click to expand...
Click to collapse
Hello! Remember this?
Also to restore an adb backup you do "adb restore filename".
Click to expand...
Click to collapse
Did it work? I see you left a "thanks" so I assume something happened.
hi, I give up on the tablet, I've been asked to see if I can give it another go, but don't know where to start, I still have a working one but no idea how to get the rom from the working one to the bricked one. thanks for the help you gave me to begin with.
facerolla said:
hi, I give up on the tablet, I've been asked to see if I can give it another go, but don't know where to start, I still have a working one but no idea how to get the rom from the working one to the bricked one. thanks for the help you gave me to begin with.
Click to expand...
Click to collapse
I have a couple tricks up my sleeve and that is, you know how you said when you ran adb reboot bootloader? Run adb shell instead and it should give you a command explorer, from there, type "su" and report results, you should see either a root request on the device or a hash sign in the coommand shell.
Just a quick question
Did you ever manage to get it working if so how did you go about doing it as i attempted to install a custom boot animation and it appears to be stuck in a constant boot loop as such i'm not really sure what to do with it or if it is savable. Any response would be helpful. Thanks.