My device is Amazon Kindle Fire HDX GU045RW 64GB Black 8.9" Wifi 3rd Generation Tablet, and it has had a keeping restart issue since last week, the device is not rooted, and firmware version is 4.5.5.2. I think a factory reset might bring it back to work, but I forgot to back up my pictures and videos in the DCIM folder.
so far the device can start the fire OS for around 10 seconds and restarts again when it is powered by a PC, which recognizes it as a portable device and I can explore the internal storage for a very short time, but when it is powered by a charger, it rarely enter into the main menu, looks like the USB storage enumeration would pend the restart a little bit longer, I am not sure if such info is helpful to narrow the possible causes, just hope anyone who met similar issue would give me some hint about it. Thanks in advance for any comment!
I have managed to install the kindle adb driver on my laptop, and could run "adb devices" and serial number showed , is there any adb command I could use to diagnose my device? Thanks in advance for any suggestion
godhand_sh said:
My device is Amazon Kindle Fire HDX GU045RW 64GB Black 8.9" Wifi 3rd Generation Tablet, and it has had a keeping restart issue since last week, the device is not rooted, and firmware version is 4.5.5.2. I think a factory reset might bring it back to work, but I forgot to back up my pictures and videos in the DCIM folder.
so far the device can start the fire OS for around 10 seconds and restarts again when it is powered by a PC, which recognizes it as a portable device and I can explore the internal storage for a very short time, but when it is powered by a charger, it rarely enter into the main menu, looks like the USB storage enumeration would pend the restart a little bit longer, I am not sure if such info is helpful to narrow the possible causes, just hope anyone who met similar issue would give me some hint about it. Thanks in advance for any comment!
I have managed to install the kindle adb driver on my laptop, and could run "adb devices" and serial number showed , is there any adb command I could use to diagnose my device? Thanks in advance for any suggestion
Click to expand...
Click to collapse
Tough nut to crack. There is no adb magic that will assist in diagnosing/remedying the situation without root access. You can not utilize adb nor see the DCIM folder unless FireOS is running and USB debugging enabled; I believe the latter resets on every reboot. Given the stability window (10-15 sec) there is barely sufficient time to navigate to the option under settings before the device restarts. You could root and unlock but the limited FireOS run time presents an insurmountable obstacle as the procedure takes some time.
I don't think a factory reset will resolve the issue but is likely the only recourse. Sorry to share the bad news ...
Davey126 said:
Tough nut to crack. There is no adb magic that will assist in diagnosing/remedying the situation without root access. You can not utilize adb nor see the DCIM folder unless FireOS is running and USB debugging enabled; I believe the latter resets on every reboot. Given the stability window (10-15 sec) there is barely sufficient time to navigate to the option under settings before the device restarts. You could root and unlock but the limited FireOS run time presents an insurmountable obstacle as the procedure takes some time.
I don't think a factory reset will resolve the issue but is likely the only recourse. Sorry to share the bad news ...
Click to expand...
Click to collapse
Thanks for the information! I have connected my device with adb shell command, and also measured the time from adb server on to device reset, it was around 30 seconds, is it enough to perform the root with adb assistance? I think 30 seconds is enough for moving the jpg files out one by one, but might be insufficient for the mp4 files because some of them are over 1GB.
I can make the device enter FireOS original recovery and it never restarts, so I am thinking maybe it is possible to replace it with some custom recovery like TWRP which supports mount function and adb connection as well, but per my research from the forum, the custom recovery needs a unlocked bootloader, which needs the device to be rooted at first.
BTW, I found the jpg and mp4 files in /sdcard/DCIM/Camera, would it be affected by the factory reset? Or just data and cache would be affected? I know TWRP can perform a factory reset without affecting the internal storage, but not sure what the original recovery would do. Please kindly refer to the attached snapshot for more details.
Thanks in advance for any help
godhand_sh said:
Thanks for the information! I have connected my device with adb shell command, and also measured the time from adb server on to device reset, it was around 30 seconds, is it enough to perform the root with adb assistance? I think 30 seconds is enough for moving the jpg files out one by one, but might be insufficient for the mp4 files because some of them are over 1GB.
I can make the device enter FireOS original recovery and it never restarts, so I am thinking maybe it is possible to replace it with some custom recovery like TWRP which supports mount function and adb connection as well, but per my research from the forum, the custom recovery needs a unlocked bootloader, which needs the device to be rooted at first.
BTW, I found the jpg and mp4 files in /sdcard/DCIM/Camera, would it be affected by the factory reset? Or just data and cache would be affected? I know TWRP can perform a factory reset without affecting the internal storage, but not sure what the original recovery would do. Please kindly refer to the attached snapshot for more details.
Thanks in advance for any help
Click to expand...
Click to collapse
Unfortunately, your research is accurate. Device must be rooted (and usually unlocked) to install a custom recovery. Rooting requires a functioning ROM and typically takes some time (more than 10-30 sec) to complete.
As I recall a stock factory reset is comprehensive including contents of the DCIM folder. So you'll want to move out whatever you can before going that route. I also think the chances are small a reset (basically a user app/data wipe) will resolve the looping problem as it does not touch the system partition.
As a test turn off your AP before powering up the HDX. Outside chance establishing a WiFi connection is somehow contributing to the boot loop. Graphing at straws - not much else you can do in the absence of root.
I would also reach out to Amazon given the value of the device ($400+ USD). While likely out of warranty they may provide some accommodation if you play your cards right and get a compassionate agent. Highly unlikely you'll get anything close to full value but perhaps something.
Davey126 said:
Unfortunately, your research is accurate. Device must be rooted (and usually unlocked) to install a custom recovery. Rooting requires a functioning ROM and typically takes some time (more than 10-30 sec) to complete.
As I recall a stock factory reset is comprehensive including contents of the DCIM folder. So you'll want to move out whatever you can before going that route. I also think the chances are small a reset (basically a user app/data wipe) will resolve the looping problem as it does not touch the system partition.
As a test turn off your AP before powering up the HDX. Outside chance establishing a WiFi connection is somehow contributing to the boot loop. Graphing at straws - not much else you can do in the absence of root.
I would also reach out to Amazon given the value of the device ($400+ USD). While likely out of warranty they may provide some accommodation if you play your cards right and get a compassionate agent. Highly unlikely you'll get anything close to full value but perhaps something.
Click to expand...
Click to collapse
Thanks for the suggestion! I have moved all the pictures and part of mp4 files out of that device by adb pull command, and I found the time from adb connection built to device restarting allows around 300MB data transfer, so the mp4 files more than 300MB are still left in the device. I am thinking if it is possible to copy busybox into my device, and use split command to divide large files into files less than 300MB. Is it ok to use the one from https://busybox.net/downloads/binaries/1.21.1/ directly? Thanks in advance for any comment
godhand_sh said:
Thanks for the suggestion! I have moved all the pictures and part of mp4 files out of that device by adb pull command, and I found the time from adb connection built to device restarting allows around 300MB data transfer, so the mp4 files more than 300MB are still left in the device. I am thinking if it is possible to copy busybox into my device, and use split command to divide large files into files less than 300MB. Is it ok to use the one from https://busybox.net/downloads/binaries/1.21.1/ directly? Thanks in advance for any comment
Click to expand...
Click to collapse
Shouldn't be a problem download from that source. Splitting large files is a good idea.
Regardless of what eventually happens with your device I suspect there will be a take away regarding performing regular backups against personal files. Even something simple like drag/drop of important files/folders on occasion.
Davey126 said:
Shouldn't be a problem download from that source. Splitting large files is a good idea.
Regardless of what eventually happens with your device I suspect there will be a take away regarding performing regular backups against personal files. Even something simple like drag/drop of important files/folders on occasion.
Click to expand...
Click to collapse
Yeah! I did it! Thanks for the powerful busybox, which can continue to split large files even when it is interrupted by device restarting. With this feature I could pull any file out of a keeping restart device given there is enough disk space for storing the split files. The following shares my process & scripts used in the backup. Hope that helps others might meet the similar case.
1. move busybox in the device
adb push busybox /data/local/tmp/
adb shell chmod 755 /data/local/tmp/busybox
2. split the large file
adb shell /data/local/tmp/busybox split -b 300m /sdcard/DCIM/Camera/%%i /sdcard/tmp/split /*used in a DOS bat file*/
3.pull the files out
for /f %%i in (%1) do if not exist .\kindle\tmp\%%i adb pull /sdcard/tmp/%%i .\kindle\tmp\ /*used in a DOS bat file*/
4.combine the split files into what it should be.
cat splita* > a.mp4
Related
Okay guys, so here's a weird one.
My g-tablet was working great. Was running VEGAn-Tab Build, BETA 5.1.1, no reason to update it, because it did everything I needed. I finally had it to where I wanted it, then it all kind of started falling apart. Here's how.
I power it on and notice my home screen got all messed up for some reason (using launcher pro). All of the settings defaulted to the original. I tweaked it back to more or less how I wanted it, and when I had it back to normal, thought nothing better of it. Must have glitched out some how.
Then I notice a bunch of things starting to force close, specfically android market, amazon market, titanium backup, google services framework, launcher pro, etc. Odd thing is it would do it one at a time, but otherwise my tablet would carry on as normal.
I go ahead and restart the tablet, to see if that helps at all, and what do you know, the homescreen is messed up again! I thought launcher pro might have been the culprit, so I un-installed the app and rebooted... And launcher pro is still there.
I go ahead and delete it again and start deleting other apps, restarting the tablet, and no matter what I do, everything stays the same. time for some clockwork mod action. I go into clockwork mod, and try to do the factory reset option, thinking what the hey, I'll try anything right now. Hit it, mourn the loss of my user data, and reboot the system... and again, everything is still the same.
I hook up my tablet to the computer via usb, and it looks like I'm able to at least delete misc. files that way. But when I return to good old Tabatha (my nickname for Gtab) everything is stuck just the way it is.
Needless to say, it feels like I'm stuck in the twilight zone.
I know I should have researched it by now, but I'm going to finally look it up to see if I can recover with NVFlash (I know I know, very noobish of me, using strange roms and not knowing any of the basics).... but I'm increasingly worried I've got some kind of a hardware malfunction on my hands. Could it be the memory? The internal SD card?
Oddly enough, my tablet still functions... I can browse the web, hook it up to my computer, etc etc, but no matter what I do I can't alter the data I already have on my tablet. Can't delete things, can't change settings, update apps, etc. etc. Which makes it pretty much useless for what I wanted to use it for.
I finally realized what this is like. The movie groundhog day, and I'm stuck in the same day, over and over again.
Any help or input that might get me out of this mess would be greatly appreciated.
Phil: "I was in the Virgin Islands once. I met a girl. We ate lobster, drank piña coladas. At sunset, we made love like sea otters. *That* was a pretty good day. Why couldn't I get *that* day over, and over, and over..."
This is now the second time that I've seen this exact same problem. I was in the process of troubleshooting the original one when the user returned his gTablet for replacement. If you can stand the deja vu, read this thread.
Do not nvflash your tablet--nvflash cannot fix SD-card related problems. Read this post for why not.
Instead, do this for me: Reboot the gTablet, then open a Terminal, or, use adb and run this command:
Code:
$ dmesg > /mnt/sdcard/dmesg.txt
Attach that dmesg.txt which will contain messages from the kernel to your next post.
I'll check this thread in the evening.
rajeevvp said:
This is now the second time that I've seen this exact same problem. I was in the process of troubleshooting the original one when the user returned his gTablet for replacement. If you can stand the deja vu, read this thread.
Do not nvflash your tablet--nvflash cannot fix SD-card related problems. Read this post for why not.
Instead, do this for me: Reboot the gTablet, then open a Terminal, or, use adb and run this command:
Code:
$ dmesg > /mnt/sdcard/dmesg.txt
Attach that dmesg.txt which will contain messages from the kernel to your next post.
I'll check this thread in the evening.
Click to expand...
Click to collapse
Thanks for the direction, at least I know it isn't an isolated incident. It's 1:45 AM where I am right now, and I have to wake up for work in about 5 hours... So I probably won't be able to get in depth with the follow up on this stuff untill after work tomorrow night (so long as the wife doesn't hog the computer )
Again thanks for the quick response, I appreciate you pointing me into some sort of direction. Can't wait to try to get this sorted out!
Currently trying to figure out how to get ADB going.... pretty intimidating, but I'm trying. I got the Java JDK installed, installing the SDK, but can't find the "SDK Setup.exe" file or even a USB driver folder in the SDK directory. Got a good resource for getting ADB set up?
Save yourself some trouble. Got to http://www.knoppix.org/ and download the latest Knoppix live CD image.
Burn it, boot it, then use the adb executable from this post. For simple things like just running adb, you don't need the entire Android SDK.
Get me a dmesg while inside ClockworkMod:
Code:
$ [B]sudo ./adb shell dmesg > dmesg.txt[/B]
ADB commands documentation
Thanks, I'll try it out sometime this weekend!
Well, I really screwed myself now. I got the Linux distro loaded but still couldn't figure out how to get ADB to work. For whatever reason, When I boot from the DVD, I can't download the zip from within linux (get errors) and I could not open the ADB command by navigating to where I have it extracted in my hard drive. [Do I need to load the OS onto a flash drive instead?]
So I started messing with some stuff in clockwork mod. I apparently really goofed it, and I got a "Magic Value Mismatch" error everytime I tried to boot it up.
I looked up Magic Value Mismatch, and from there it pointed to using NVFlash to try to fix that problem. So tried that. After I flashed it, I thought for sure I finally had it back to stock, as the intro screen started to show the tap n tap logo... but i basically got stuck in a boot loop, tap n tap, then "n", then tap n tap, then "n", etc, until it dies.
I looked up this issue and apparently the key is to get into clockwork mod and do factory reset, reset cache, and partition the SD card to 2048 and 0, which I did... (per post #4 on this thread: http://www.slatedroid.com/topic/17501-helpstuck-in-bootloop/ ) but still no dice.
Not sure where to go from here, or if I can even get it to interface with ADB in its current state. Looks like I'm done for
Thanks for trying though
On second thought, I may have had a breakthrough, at least in getting ADB to see my tablet!!! Woohoo! It finally sees the device and has a serial number. Was following the device on this thread:
http://www.androidtablets.net/forum/viewsonic-gtablet-technical/5377-adb-g-tab-step-step.html
7. under the "[Google.NTx86]" section, paste the following:
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
save the file and exit.
But I have a 64 bit machine, so I finally figured it out and plopped that into the 64 bit portion of the .inf file. DOH!
So now let me see what I can drum up through the previous commands above.... though the parameters have changed now to be sure... Due to my haste things may have taken a turn for the worse.
To recap, now my tablet is stuck in a boot loop after having done NV Flash, after having screwed up some settings in clockwork mod trying to fix a "Magic Value Mismatch" error.
Tried:
$ dmesg > /mnt/sdcard/dmesg.txt
I just run this in the cmd prompt at my platform-tools directory where the adb is correct?
All it says is, "The system cannot find the path specified."
Am I doing something wrong, or is my tablet that messed up?
Okay, this is slightly weird. So I was browsing around in clockwork mod, and lo and behold, the original zip flies for vegan tab are all STILL THERE. So I reloaded them... And My tablet zips back to exactly the way I had it before!
Only this time, so far no force closes. This looks way too good to be true after what I've been through. I'm going to try modifying some files and settings and restart my tablet to see what it does. I'm pretty sure I can't be out of the woods yet. Allthough it is 3:33 AM as this is happening... magic hour. I may be going insane.
EDIT: Nope, was definitely way too good to be true. All my data is as stuck as it was ever was. But at least now I can get into it again. But now we're back to square one. Lemme figure out this dmesg business and get back to you. X(
So I would try issuing the following exactly in the command line at the adb platform tools folder:
$ dmesg > /mnt/sdcard/dmesg.txt
Is that code supposed to be copy and paste in? I don't seem to be getting anything. I can do the following command and get the info to pop into the command interface:
adb shell dmesg
But I can't figure out how to save that to a text file. And you want me to do that while the g tablet is in recovery, correct?
FYI, trying to do it through Windows 7. Would that command only operate in the linux environment via knoppix?
Thanks
titobetlogs said:
I can do the following command and get the info to pop into the command interface:
adb shell dmesg
But I can't figure out how to save that to a text file.
Click to expand...
Click to collapse
Redirect the output to a file:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
titobetlogs said:
I got the Linux distro loaded but still couldn't figure out how to get ADB to work. For whatever reason, When I boot from the DVD, I can't download the zip from within linux (get errors) and I could not open the ADB command by navigating to where I have it extracted in my hard drive.
Click to expand...
Click to collapse
I suggested using Knoppix just because it is so easy to use adb in Linux. Broken-down steps for future reference:
1. Download and burn the latest Knoppix Live CD iso image. Check the downloaded file size. The .iso file should be ~700MB in size. Also, test the CD by booting it and then typing at the boot prompt: knoppix testcd
2. Boot Live CD and skip the creation of any partition or file to store user data. After all, we just want to run adb.
3. After Knoppix has booted into the desktop, run a browser, right click on the adb.zip attachment in this post, then select "Save Link As..." and save the zip file into /tmp.
4. Connect the gTablet to the PC via the USB cable.
5. Open a terminal window, then type in it:
Code:
hostpc$ [B]cd /tmp[/B] [I]Change to the dir. where adb.zip was saved[/I]
hostpc$ [B]unzip adb.zip[/B] [I]Unzip zip file[/I]
hostpc$ [B]ls -l adb[/B] [I]Check if the adb program was extracted OK[/I]
-rwx------ 1 rvp rvp 159620 Dec 1 22:23 adb
hostpc$ [B]chmod 555 adb[/B] [I]Make adb executable.[/I]
hostpc$ [B]sudo ./adb shell dmesg > dmesg.txt[/B]
Note 1: do not type in the shell prompt, 'hostpc$'. It is only there to show you what the screen should (roughly) look like.
Note 2: If adb says something like "device not found", just unplug the USB cable from the PC, wait a few moments, then re-plug the cable and re-run the adb command again.
6. Go back into the browser and attach the dmesg.txt file that is there in /tmp. You will have to tell the Noscript plugin to allow scripts from xda-developers to enable attachments. Right click on the page, then select the Noscript menu item, then choose "Temporarily allow xda-developers.com".
I thought for sure I finally had it back to stock, as the intro screen started to show the tap n tap logo... but i basically got stuck in a boot loop, tap n tap, then "n", then tap n tap, then "n", etc, until it dies.
Click to expand...
Click to collapse
I'm not surprised. If the files on the internal SD card cannot be modified then that boot loop behaviour is to be expected. Here's why:
Android requires certain partitions to exist on the system. These partitions can be either on the flash or on SD cards. The partitions are:
/system: This is where the binaries and system apps that come with the firmware are stored. This partition is usually mounted read-only to protect it. On the gTablet, this partition is on the 512MB built-in NAND flash chip.
/cache: As the name indicates, this is the partition used to speed up the execution of the Java apps. Temporary files are also created here. This partition too is on the built-in NAND flash chip.
/data: This is where user-downloaded apps are stored by default, and also where Android stores its system configuration data. This partition, on the gTablet, is on the internal SD card.
/sdcard: This is where user content like media files, books, and the apps moved to SD card are stored. This partition too is on the internal SD card.
The first 3 partitions are critical and Android won't come up without them being present (or, if there are any errors on them). Among these 3, only /system needs to be correctly populated (When you install a ROM, new stuff is copied here). The other 2 partitions, /data and /cache can be empty and the system will boot up fine--with defaults. In fact, when you select "wipe data/factory reset" in CWM, /cache and /data are re-formatted--effectively, wiped clean.
(There are 2 other important partitions on the NAND flash chip, but, these are not mounted because they don't contain a proper filesystem. You have to use special tools to create the contents of these 2 partitions.
The first of these is the "boot" partition. This one and "system" are re-written when you install a new ROM. The "boot" partition holds the Android Linux kernel. If you install a new kernel, only the "boot" partition is rewritten.
The second is the "recovery" partition. This contains a separate, and usually different (and safe), Linux kernel and a mini filesystem image. This is a fail-safe partition. Stock recovery and ClockworkMod sit here.)
In your case, nothing on the internal SD card can be modified, so the stuff in /data will still be from your old ROM. (nvflash also cannot modify SD card contents, as I mentioned before.) When the stock firmware boots up, it will find incompatible stuff in /data. Critical apps will then die. Android will restart them, they will die again. This is your boot loop.
Get me the dmesg output and then we'll run a few tests using CWM, but, judging from your previous posts, I don't think your internal SD card can be fixed. You have 2 options:
1. Return the tablet for a replacement.
2. If you can't return it, I can switch the internal and external SD cards on your ROM so that you can boot and use the system (almost) normally. But, this is a custom solution and you will need to have an external SD card in its slot always. Read through this thread.
Wow, you really know you're stuff! I'll see what I can get you later on in the day with regard to the dmesg, I'm currently still at work.
I had suspected a hardware error... bummer. I'll definitely be interested in seeing if I can just use the external micro sd slot to sub out for the internal sd card. I would at least like this thing to be functional again, though I suppose I'll never be able to try any of the honeycomb roms when those get past alpha. Oh well.
Do you know if this thing takes 32 gb micro sd cards? That would be pretty awesome, I at least wouldn't feel too limited on space.
By the way, thanks for all your help on this, I know I'm a huge noob. I greatly appreciate your patience and taking the time to break everything down for me. I have absolutely zero background in programming or anything computer related, though I do find this stuff extremely fascinating! If I could rewind the clock and study this stuff in school, I would do it in a heartbeat.
Again, thanks so much, can't thank you enough.
titobetlogs said:
I would at least like this thing to be functional again, though I suppose I'll never be able to try any of the honeycomb roms when those get past alpha. Oh well.
Click to expand...
Click to collapse
No, you should be able to run whatever ROM you want. I'll send you an installable zip file, in a few days, which should get you going again on Vegan-Tab, at least. You'll just need to remember to flash this zip file right after you've flashed the ROM (of your choice).
Right now, I don't know if I need one zip file for each kind of ROM in existence for the gTablet, or, if I can use some scripting and do the internal/external SD card switch using just a single installable zip file. I'll look into this on the weekend.
Do you know if this thing takes 32 gb micro sd cards?
Click to expand...
Click to collapse
Yes, it does.
By the way, thanks for all your help on this, I know I'm a huge noob...
Click to expand...
Click to collapse
I was a complete noob to Android myself back in April of this year. I've picked all of this up in just a few months. I'm pretty sure you can do it too, with a bit of poking around in the system. Of course, having a background in Unix/Linux helps a lot.
In your honor, below are some inspiring lyrics from the Karate Kid soundtrack:
You’re the best!
Around!
Nothing’s gonna ever keep you down
You’re the Best!
Around!
Nothing’s gonna ever keep you down
You’re the Best!
Around!
Nothing’s gonna ever keep you dow-ow-ow-ho-how-ho-own
INSPIRING GUITAR SOLO
Dude! you're embarrassing me -- I haven't send you the zip file yet... and, you haven't sent that dmesg output I wanted.
I know I've been stuck at work and family functions every day this week so far. Hopefully I'll get to it soon
Finally got to this! Here you go! Thanks again!
titobetlogs said:
Finally got to this! Here you go!
Click to expand...
Click to collapse
Can't see any problems in that dmesg output. Time for some tests on the internal SD card.
Boot into CWM, then run on PC (on Linux run: sudo ./adb shell):
Code:
C:\SOME\PATH> [B]adb shell[/B]
~ # [B]mount /dev/block/mmcblk3p1 /sdcard[/B] [I] Mount internal SD card partition[/I]
~ # [B]mkdir -p /sdcard/a/b/c[/B] [I]Make a directory tree[/I]
~ # [B]echo test > /sdcard/a/b/c/test.txt[/B] [I]Create a file[/I]
~ # [B]cat /sdcard/a/b/c/test.txt[/B] [I]Read it back again[/I]
test [I]Correct[/I]
~ # [B]echo 3 > /proc/sys/vm/drop_caches[/B] Flush kernel caches
~ # [B]cat /sdcard/a/b/c/test.txt[/B] Read it back again
test Correct
~ # [B]umount /sdcard[/B] [I]Unmount[/I]
~ # [B]mount /dev/block/mmcblk3p1 /sdcard[/B] [I]Remount /sdcard[/I]
~ # [B]cat /sdcard/a/b/c/test.txt[/B] [I]Reread file[/I]
test [I]You should see "test" here[/I]
~ # [B]umount /sdcard[/B]
You should see "test" after the kernel flush and the remount.
Next, reboot the tablet--back into CWM, then run the cat command again. `cat' should output "test", again, if the SD card is OK.
Here's a screen of the commands I entered and what I got back. Did I do anything wrong? Looks like something's a bit off.
I have messed up my tablet, my tablet is rooted i went and replaced couple of the system apps by using root explorer and that completely made my system go crazy so i then did a system reset and now i keep getting unfortunately, setup wizard had stopped and i cant go anywhere from there. my boot loader is not unlocked. is there any way to reinstall the stock ROM like from adb or something. please any help is appreciated. I have also tried to reset the rom by holding down power and vol down and wipe data from there, and still the same thing. when i plug it in the computer i am still able to see the transformer so i can transfer files to and from the transformer i just cant get it passed the welcome screen.
spencerj2001 said:
I have messed up my tablet, my tablet is rooted i went and replaced couple of the system apps by using root explorer and that completely made my system go crazy so i then did a system reset and now i keep getting unfortunately, setup wizard had stopped and i cant go anywhere from there. my boot loader is not unlocked. is there any way to reinstall the stock ROM like from adb or something. please any help is appreciated. I have also tried to reset the rom by holding down power and vol down and wipe data from there, and still the same thing. when i plug it in the computer i am still able to see the transformer so i can transfer files to and from the transformer i just cant get it passed the welcome screen.
Click to expand...
Click to collapse
Does adb on your computer see your device, since it's not fully booted?
Connect your tablet with USB cable.
On your PC, in the same folder as your adb files, open a command prompt in that location (shift+right click).
Type "adb devices" and see if yours come up as connected.
I doubt it will though, sounds like how I bricked my first prime, when I pushed a deodexed framework to it.
Might also want to try looking in the Dev section, under the how to unbrick your device thread, and see if you can attempt to revert to a different firmware via installing a blob file, but if you can't access your internal or external SD cards, to read/write the blob file (b/c your device won't fully boot) you may be SOL.
Next time unlock the boot loader first an make a nandroid backup, before messing w/ system files, that way you can easily restore. If your still in your 30 day window of purchase, you might consider a quick return/swap... would be the eaisest thing to do.
Sent from my CM7 Atrix 4G
no adb does not see my device but i can access the internal sd card
Swiftks said:
Does adb on your computer see your device, since it's not fully booted?
Connect your tablet with USB cable.
On your PC, in the same folder as your adb files, open a command prompt in that location (shift+right click).
Type "adb devices" and see if yours come up as connected.
I doubt it will though, sounds like how I bricked my first prime, when I pushed a deodexed framework to it.
Might also want to try looking in the Dev section, under the how to unbrick your device thread, and see if you can attempt to revert to a different firmware via installing a blob file, but if you can't access your internal or external SD cards, to read/write the blob file (b/c your device won't fully boot) you may be SOL.
Next time unlock the boot loader first an make a nandroid backup, before messing w/ system files, that way you can easily restore. If your still in your 30 day window of purchase, you might consider a quick return/swap... would be the eaisest thing to do.
Sent from my CM7 Atrix 4G
Click to expand...
Click to collapse
spencerj2001 said:
no adb does not see my device but i can access the internal sd card
Click to expand...
Click to collapse
If you can access the internal card, its weird that adb can't see your device... oh well... try reverting to a earlier/different firmware via a blob. See thread in dev section.
Sent from my CM7 Atrix 4G
i did exactly the same mistake: i uninstalled some system apps (the asus preinstalled apps, with titanium) without unlocking the bootloader, and after a wipe from the stock recovery i'm not able to go beyond setup configuration, it always stops. but i can see and use internal and external memory from my computer. did you find a solution?
Today I tried to flash the CyanogenMod 9 Nightly 06-30-12, coming from Build 35 of AOKP and after factory resetting and clearing Dalvik I went to install the zip and while flashing it I got a build-prop related error!
All of my NANDROIDS gave me a data error when flashing and now I am pretty f'd! I /really/ need to fix this ASAP but have no idea how.
-Samsung Galaxy Tab 10.1 Wifi-
-CWM 4-
On a second note, does anywhere know where I can get my screen replaced for cheap? I dropped my tab a few months back and the screen got MAJOR cracked, though it still does technically work (I still use the screen, it works but it's cracked is all...) and after calling Samsung and waiting for over 1 and a half hours they told me they wanted $150 to fix it, which if I recall is about half of what I payed for it anyway...
To be honest, I'd be lying if I said I was happy with Samsung over all.
I mean, bad customer support, the proprietary connection cable, and lack of official updates (along with the ugly TouchWiz that I'm not sure /who/ likes ) don't make me that happy...
Anyway, can anyone help me please?
Thanks in advance!
Update your recovery: http://droidbasement.com/db-blog/?p=2655
If you have a GT-P7510 (p4wifi), in this post are flashable zips (with your current recovery) of CWM and TWRP, in case you prefer this method: http://forum.xda-developers.com/showpost.php?p=28051448&postcount=29
After that, flash your ROM like always.
Yeah, thanks, were it so easy. I fired up ODIN multiple times, no matter what, unsuccessful. Like always, my computer would not recognize my tablet. Yes, I have the bloody Samsung drivers, yes I've tried reinstalling them (several times in the last few months), yes I've tried using different USB ports! And what? Nothing. Nothing at all. For the last few months I have not been able to transfer movies/music to my tablet via file transfer and I can't even get the stupid odin download thing to work. To be honest, I really am pissed off with this broken pile of trash. Would trade it in for a similar tablet any time.
Did you try any of the flashable zips for a new recovery?
About the USB, it sounds like a different problem, but for the file transfers, are you sure you have MTP selected? (answer #5 --> http://forum.xda-developers.com/showthread.php?t=1642009 )
If you haven't tried it yet, you could use a different computer, another OS (some Linux distro and check that adb works), change the USB cable.
I can't use a flashable zip since I can't copy files onto the tablet >.>
Also, yes, for file transfers I /do/ have MTP selected always and it doesn't work eitherway.
Essentially, I am stuck with a $300+ ugly and broken thing that I can only use as a paperweight for the huge mess I call my desk. Yay.
>Rage sidenote; Samsung, go take the money I payed for **** and shove it.
And I guess you don't have your old ROM (AOKP build 35) in your tab.
Try with adb (in recovery), but if you can't get a working USB connection (using other computers or OS), maybe there's something physically wrong with your tablet.
No, I don't. I'm stupid enough to delete the ROM zip after flashing it to save space on the tablet...
How do I do this ADB thing? I've heard of it before alot but never used it or looked into it...
Read this: for windows -> http://forum.xda-developers.com/showthread.php?t=1387527 , for Ubuntu -> http://forum.xda-developers.com/showthread.php?t=921169
After everything is installed, boot your tablet into recovery and try running in your command line application (CMD for windows):
adb devices
If it shows that a device (and ID number and the actual state, e.g. recovery) is connected, your golden!
If you have another android device, try it too, to be sure that is working.
To transfer a file the command is
adb push /path/to/file /path/in/tablet
In windows I guess is something like this:
adb push C:\path\to\file /path/in/tablet
so I'd do something like
adb push C:\ADB\CWM-5.5.0.4-p4wifi.zip mnt/sdcard/ ?
Im dling the ADB files right now
adb push C:\ADB\CWM-5.5.0.4-p4wifi.zip /mnt/sdcard/
You need the slash at the star and end of the path of the tablet.
While installing PdaNet it failed, said it couldnt connect through to the device or w/e
Also,I don't recall having ADB on when I had the tablet. I might've but I don't think I kept debugging on for the general time...
This is so frustrating >.>
I'm not sure about that error in PdaNet, I can help you with adb but I don't use Windows, so there's things I can't test.
If you didn't select ADB debugging in your ROM it doesn't matter, you're doing this from recovery.
BTW, do you have other android device?
adb seems to be working and copying, but I can't find the file in Recovery while doing choose a zip to apply!
Yes, I have an LG Optimus V on Virgin Mobile running tdm's AMAZING Quattrimus Alpha 10 on Ice Cream Sandwich/ Android 4.0.4
this is what I get
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>adb devices
List of devices attached
43C800340009517 recovery
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>adb push C:\CWM-5.5.0.4-p4wifi.zip
43C800340009517\sdcard\download
1328 KB/s (4147569 bytes in 3.048s)
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>
If you connect your phone and execute
adb devices
What's the output?
If you do the same with your tablet, what's the output?
with the tablet it's
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>adb devices
List of devices attached
43C800340009517 recovery
with my phone it doesn't wanna show up in Recovery or not.... Hmm.
Well, it shows fine, then you should be able to transfer the files
First, in your recovery, go through the steps to install some zip file, but just go as far as selecting the directory, then go back
Now in your PC try running something like this, change your path in windows:
adb push C:\CWM-5.5.0.4-p4wifi.zip /sdcard/
The in your recovery, select install and should show there. The thing is that most likely the sdcard wasn't mounted in your tab
Edit, to mount your sdcard in recovery do: mounts and storage > mount /sdcard > Go back
The do the transfer in your PC.
Hmm
While I was holding it to my gut, pushing the end of the cable into my stomach (It was the only way to get it to be recognized) I fooled around and went into download mode, hoping that on the contrary I could do that, turn it off, and when I went back into Recovery it would be there when it finally said the cable WAS connected and then I rushed to open Odin and wrote it through, and it frickin' wrote CWM v5 right on and it worked, I'll be damned!
Maple, I can not thank you enough for helping me with this, I am in great debt.
You're welcome, I'm glad it worked. Knowing how to use adb is really useful. And now you know that something is wrong with your cable.
Or in the connector pins or w/e of the tablet... The cable works fine for charging though....
You are my savior, bro.
Hi everyone
My first post here, hopefully someone can help me.
I have (had) a HTC Flyer P510e tablet. When I got it I went through the process of rooting, unlocking, etc, and if my memory serves was running Andoid 2.3.4.
A while ago I dropped it, broke the screen and rendered it useless. Digitizer not responsive, so I cant unlock the screen, or quite frankly do anything with it.
There is some important info on there I need to get off. I have already managed to pull off the contacts, calender, documents, apk's i needed, etc. The problemis as follows:
I have been using Garmin Mechanic to record all my fuel purchases, and PhoneTrack Explorer to record mileage use, site time, etc. I have backups of these apps and the data from January, but I am needing the Feb & March data from both these apps.
I was previously using TitaniumBackup for this, and from examining the backup files I can see the databases for these apps were stored as follows:
\HTC Backup\External\data\titaniumbackup\co.uk.journeylog.android.phonetrack-20130110-124837.tar.gz\co.uk.journeylog.android.phonetrack-20130110-124837.tar\data\data\co.uk.journeylog.android.phonetrack\.\databases\
\HTC Backup\External\data\titaniumbackup\com.garmin.android.apps.mech-20130110-124624.tar.gz\com.garmin.android.apps.mech-20130110-124624.tar\data\data\com.garmin.android.apps.mech\.\databases\
I have tried various commands, sequences and other suggestions using ADB, none which have worked. Tthe failures I get on ADB commands mainly are Permission Denied when trying to issue the su or root command, read only or read errors trying to mount, browse or copy, etc, etc. I have followed about 15 suggestions from different XDA pages, other sites, and more, with no luck so far.
I have tried Moborobo, MyPhoneExplorer and APK Batch Installer, with not much luck.
Things I do have which could be of use:
I have done a full clockworkmod backup and have the current image files.
I have already downloaded the Android SDK kit.
Is there any way I can get hold of these files so I can submit my expenses? Is there an easy way to pull them using ADB?
I was considering if there was a way to use the Android SDK to create a virtual Android device, add the clockworkmod recovery to the virtual device, then use the image backups I have to restore my broken device's load, then do a backup or export of the information I am needing?
Any help or suggestions would be greatly appreciated!
Thanks very much.
Did you try to re-install the HTC drivers? What is the response if you type:
adb devices
If no device is listed, it might just be a driver problem. Or just try another USB port, or another computer (if available).
redpoint73 said:
Did you try to re-install the HTC drivers? What is the response if you type:
adb devices
If no device is listed, it might just be a driver problem. Or just try another USB port, or another computer (if available).
Click to expand...
Click to collapse
It's not a communication problem. adb devices does list the device serial number. adb shell launches the shell and I can browse around and perform various commands, but I am always getting the permission denied errors when I try to access the system protected folders, and those hidden folders.
Hi guys, I have the Rock Jaw Vi phone which by all sense and purpose seems to be a clone of the HTC One. It's Quad Core with 2 mega pixel camera on the front and 8 mega pixel on the back. The case and all outward appearances are that of the HTC, the phone info screen displays the following ...
Model Number = RJViJGTL32SM
Andoid version 4.2.1
Baseband version = moly.wr8.w1248.md.wg.mp.v6.p8,2013/08/12 15:55
Kernel version 3.4.5 [email protected] #1 Mon Aug 19 16:54:14 CST 2013
Build Number = 0502H026_20130819
I can get into the boot options screen by doing the On/Volume Down press but the menu's are all in Chinese and just seem to go through self diagnostics and tests. I can drag n drop file from Mac OSx but none of the apps I have found so far will communicate with the phone via USB. I am trying to get root so i can do a full back-up and then to try and put HTC Android 4.3 on it.
Do you guys have any idea on how I can achieve this or to get the phone to display it's boot options in English ?
I am pretty much clueless and stuck, any advice, tips, hacks etc would be really appreciated
I did follow a link at one stage on the web that went to SRSroot but their tool was windows only
Hmmm More messing with the phone has revealed power on with volume up depressed gets me to some very small text menu with the options;
Boot Normal
Fastboot
Boot(UART)
Boot UART is all the test screens that I was getting in Chinese but now they are touch screen buttons and labeled in english ao that's good to know.
Using fastboot-mac from HTCRootOne tries to talk to it but comes back with error: could not clear input pipe; result -536854449, is this something that's platform specific, ie it's not a true HTC so the version of fastboot-mac is no good and needing a non specific version ?
Ok that error is generated to the oem get_identifier_token...
If i do a fastboot-mac devices i get the reply "mt6589_phone_720pv2 fastboot" ...
I'm getting there slowly
Done some more digging with the phone attached to the Mac here and checking my systems profile I see that the phone is listed under usb connections as seen in the screen grab, still referring the as a HTC. Getting a new usb cable delivered to see if the phones usb cable provided is for charging only. If anyone here has any other suggestions I would be all ears or eyes as the case might be
Done more grubbing around and have found it to be a HDC One, HTC One clone .... Now to go see if any are rooted on here
Can anyone help me
Well i am pretty much stuck here so if anyone is reading this and wants to offer some help and advice I could do with it
I have looked around on the phone and can't see any bin or system folders even with show hidden i can't find them.
adb wont give me a remote shell, it complains that there is no bin/bash
when i try and do an adb backup i get 0 byte files grrrrr!!
I still need to find a way of getting root
This phone is a tricky beast for a learner - lol
Install some file explorer that allows you to browse from the top folder (/). I'm pretty sure you'll find at least /system there.
gbl08ma said:
Install some file explorer that allows you to browse from the top folder (/). I'm pretty sure you'll find at least /system there.
Click to expand...
Click to collapse
Thanks Gbl08ma - I have have it opened in Mac osx finder with show all files hidden or otherwise - The phone shows as two "No Name" devices and get mounted immediately on connection ....
I used sideload to push a package file over using adb and then went back to use Finder, and I can't see the file anywhere - hidden partition perhaps ? Can you do that with Android ?
Even the Android SDK file transfer app wont see the phone when it's connected, I am all very confused - lol
Thanks for the reply - Wonder if i can use disk utility to so some probing and at least get an ISO image file incase I goof things real bad - lol
TpwUK
tpwuk01 said:
Thanks Gbl08ma - I have have it opened in Mac osx finder with show all files hidden or otherwise - The phone shows as two "No Name" devices and get mounted immediately on connection ....
I used sideload to push a package file over using adb and then went back to use Finder, and I can't see the file anywhere - hidden partition perhaps ? Can you do that with Android ?
Even the Android SDK file transfer app wont see the phone when it's connected, I am all very confused - lol
Thanks for the reply - Wonder if i can use disk utility to so some probing and at least get an ISO image file incase I goof things real bad - lol
TpwUK
Click to expand...
Click to collapse
/ does not get mounted over USB so you won't see /bin, /system, /data or anything other than the SD card and the internal FAT32 "user" partition when entering USB transfer mode.
You must do it on the device. And for adb to work, USB debugging must be enabled in the settings.
gbl08ma said:
/ does not get mounted over USB so you won't see /bin, /system, /data or anything other than the SD card and the internal FAT32 "user" partition when entering USB transfer mode.
You must do it on the device. And for adb to work, USB debugging must be enabled in the settings.
Click to expand...
Click to collapse
I already had the phone in usb debug mode. Had to set the phone to use usb as MTP and not mass storage device connection type. Now it allows me to get in to the blighter with adb, fastboot still errors with pipes. That method allows me to get adb shell running and i can get android file transfer .... back to the reading part again
Thanks for the information gbl08ma - if i can find a way to back-up the rom i will share it somewhere
Hmm yummy - lots of interesting things in there .... Forgive my ignorance again please, but if i can create an update.zip file from the shell on the device that compresses all files from \ and all subdirs would that be the same thing as a safe ROM backup ? i wanna be safe before i attempt to root the phone as someone on here has a lower spec version of this phone and says it's a partial brick now.
TpwUK
Rooted
This phone is easily rooted with the motochopper
http://forum.xda-developers.com/showthread.php?p=40747604
Now should I push my luck further and go for the ROM - lol
TpwUK
I believe i own the same mobile
@tpwuk01
I also asked the same here; http://forum.xda-developers.com/showthread.php?t=2180425&page=92
but i was only able to root using frama root app, and it worked like a charm, but thats the only thing i could achieve, dont know but it seems theres no official thread of developement going on for any cloned device, mine runs the MOLY.WR8.W1248.MD.WG.MP.V6.P8 2013/08/12 15:55 Baseband.
After root i just installed some root apps, ads blockers, cant get any recovery to work, (Playing safe actually not to brick this now, since no support yet) but would have appreciated trying out kitkat on it, using antutu to view up specs, its impressive, i got to find out our 13MP camera at the back can do a great job than it currently is we only need to figure out how to change the image compression, the one i stumbled upon online was the blast, the 13MP was great also the flash light was tweaked to be 50X its current brightness, our 1GB application space was increased to 3.5GB, GPS and the rest was also modded to work really great.
Would like to hear any new updates you stumble upon bro.
Still a nice and featured packed device.