. I opened in regular CMD. I opened file directory of adb with desired Rom inside and typed adb sideload (update.bin) (was supposed to be stock firephone Rom )
Loading......
Bla.....
Pressed reboot.
Oy, now fone won't turn on and when I plug it into the computer the computer shows several disks each with a message that they need to be formatted in order to be used. but when I try to it fails and says the disk is read only. Only disk I had some stuff on it
Any hope or is my phone GONE?
Hi,
Thanks for writing to us at XDA Assist.
You can post your question in your device forum help section to get further help:
Fire Phone Q&A, Help & Troubleshooting
Good luck!
Related
TABLET: Fusion5 Premium+ (Re-branded yuandao N90 II dual core RK3066)
ISSUE: The tablet is now stuck in recovery mode (red triangle black exclamation) Stock 3e recovery after a failed firmware upgrade which I think was due to me selecting 'upgrade' and not 'restore'.
Details:
Before this failure rkbatch tool could see my device.
I have now tried rkbatch tool on 4 different PC's with different OS'es (Win8 x64, Win7 x32, Win XP x32, Linux x32) and at least 5 different USB cables using the latest driver_assist and batch tools or Linux equivalents.
Can not get rktools to see device in flash mode on any of them.
All the PC's can see it in ADB though.
“adb devices” reports device in recovery mode.
There's no fastboot and no shell which reports *“exec*'/system/bin/sh' failed:*No*such file or directory” but sideload appears to work.
“adb ls” of /sys /system /data etc show they are all empty.
I have the found the following firmwares specifically for this device
:LINK withdrawn
:LINK withdrawn
PM for the links
Unfortunately both of these updates are *.img files which as I can't connect using rkbatch
tool, I can't flash.
I have tried zipping them and flashing from sideload or from SDCARD both both fail, from sdcard the error is “no update found”. In sideload mode it reports “installation aborted” after the verifying the update stage. I'm quite sure there is more to creating a working update.zip but unsure of the details.
My question is does anybody no of a way to convert these supplied .img files into a format, prbably update.zip, that I can either install via sideload OR from sdcard?
Thanks
Hi,
XDA has no section for your device, therefore this would be the best place to ask for help....
>*Android Development and Hacking*>*Android Q&A, Help Troubleshooting
Good luck!
Hopefully you'll find help there. It's in the right section. This is not where to get help, only direction. ?
Hi.
I have done something stupid
Some website claimed that rom manager from clockworkmod would not work unless twrp was installed. (I guess they meant "for getting the CWM Recovery Boot Menu to work").
I had already rooted my device (Denver Tablet TAQ-80053 ARMv7 with Android 4.1.1) but I thought why not flash to TWRP with the file: "CWM-based-Recovery-v6.0.3.3-signed.zip" ?? BAD idea
Now "Recovery Mode" is only the "TeamWin Logo" then BLACK SCREEN and nothingness ??
Everything else is somewhat normal:
1) I can boot normally into the start screen of Android 4.1.1 and run applets etc.
2) I can connect to Windows 7 (x64) and get file access to everything.
But: Any flashing tool for windows cannot "see" my device, and I very much doubt that it could be a driver problem since I get full access to drives and files on the tablet (USB-connected to Windows 7 x64).
Do you have any thoughts about that ? Because to me it seems logical that a working windows-driver would also work with ADB or ... ?
I also tried the ADB installation with SDK etc. Everything installs fluently with no errors but when I do the "adb devices" command no devices are listed at all ?? The command "ADB Shell" returns an error.
Since I know about the settings needed on the tablet I have: set USB Debug Mode to ON and everytime I plug it in I select "Mass Storage Mode" to get file access from Windows; and it works fine.
As stated above, everything works except "boot into recovery mode" and ADB being able to "see" my device. Not even CWM Rom Manager can boot into recovery mode ??
I want to be able to flash a new OS but recovery mode seems to be the only way apart from the USB to Windows. I cannott accept the notion that the device is "almost bricked" just from installing the wrong
recovery image and now I cannot go back .....
I have spent too much time already and I have discovered that I am not the only one with this problem but I cannot find any solution (that actually works) anywhere. So writing to you guys must be my last
hope. The alternative is getting an axe and chop it to pieces just to be shure that it's completely dead and my $150 lost forever; gone out the window :\
Can anyone please advise me what to do ??
/Pete
PS: OMG captcha is unreadable 30 times or more . . . and then the session ran out. Great
Hi there,
I'm sorry but I can't find anything related to your question/device.
Please post that in the forum bellow for more answers from the experts but first you must register an account on XDA forum:
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck
C:\Program Files\Whatsapp_Xtract_V2.2_2012-11-17>rem If you want to decrypt android
whatsapp msgtore.db.crypt files, then you need to run this (after installingActivePython).
If you get errors then try to do this: rightclick on this !install pyCrypto.bat and choose "run as administrator"!
_
Could not find the Python directory. Please make sure that ActivePython is insta
lled in either C:\Program Files\Python27 or C:\Program Files\Python32
_
Press any key to continue . . .
giving me an error . i have install active python on c drive on computer. i try to in install "!install pyCrypto" batch file in whatsappxtract
Help me!!!!! plzz
:crying:
Hi
Thanks for writing to us at XDA Assist. I can't find anything relating to your question on XDA, please ask your question here:
Android Q&A, Help & Troubleshooting
Thread closed, thanks.
Hi, XDA,
I own a Samsung tablet (GT-n5110) which is in bootloop (the same that is being called "soft brick" - it loops on Samsung frame and doesn't leave it).
I don't have a data backup (yes, I'm an idiot). It enters Recovery Mode (HOME+VOLUME UP+POWER), but before wiping it to factory configuration I am desperatelly trying to back the data up.
The device isn't rooted. I read in many foruns that it could be possible to back it up through ADB (in Linux, through $ sudo adb backup -all). I use Linux (ubuntu), but the device isn't recognized by ADB [$ sudo adb devices]. I have alredy updated UDEV rules with the correct idVendor and idProduct and I have alredy restarted ADB server.
I have no problem on connecting to Windows in case it is needed in any way. But untill now I haven't found a way to do it neither in Linux nor in Windows.
When I connect the device to the computer, it is recognized and charges, but it isn't possible to access the files (which alredy happened before the bootloop and surely indicated that something was wrong). In Linux, it says the computer cannot access the files because of some MTP failure (I have alredy installed and updated mtp-tools). In Windows, it simply says it cannot access the device.
Is there a way to do it? Should I keep looking?
Or is it simply impossible that a device on bootloop could be recognized by the computer to back the data up?
Thanks A LOT, I really need this help!
Hello and thank you for using XDA Assist,
please create an account and ask your question in this section. The experts there should know the best about your device.
Kind regards and good luck
Trafalgar Square
XDA Assist
I'm having some trouble mounting a Kindle Fire in Fastboot mode on my system which is running Ubuntu 14.04.
I am new to any kind of Android development and have been following the excellent guides here by @kinfauns. Specifically I have the 5-scecond boot loop problem related to the power draw issue. The solution I'm pursuing is to swap the stock bootloader for FireFireFire. The guide says to do it with fastboot, since the conventional flash recovery method could be interrupted by the shutdown cycle.
So now, just when I think I have a solution to my real problem, I get out the fastboot cable, connect the kindle to my PC, and I get an error in Nautilus: Unable to open MTP device '[usb:001,006]'. Attempting mtpfs at the terminal returns:
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=1949 and PID=0007) is a Amazon Kindle Fire (ID1).
Found 1 device(s):
Amazon: Kindle Fire (ID1) (1949:0007) @ bus 1, dev 6
Attempting to connect device
LIBMTP PANIC: Unable to find interface & endpoints of device
Unable to open raw device 0
I tried following a tutorial on Ubuntu forums for getting MTP to work. It involves using lsusb command to get the device id, making entries in /etc/udeb/rules.d and /lib/udev/rules.d, supposedly to allow MTP to access the device with proper credentials. However nothing worked.
Now, on the other hand, when the device is NOT in Fastboot mode, it mounts just fine, both in Nautilus and for purposes of checking with the adb devices command.
Seems to me that what I want is for it to mount in file transfer mode instead of MTP mode when in fastboot. The fix for this exact issue in Windows (as reported on other sites) is to change the driver in Windows Device Manager.
Can anybody help with this problem?
Thanks
Hello and thank you for using XDA Assist,
please create an account and ask your question here:
Kindle Fire Q&A, Help & Troubleshooting
Kind regards
Trafalgar Square
XDA Assist