Develop Bugs

G-Slate root

There's no G-Slate forum yet, so this goes here.
How to root your T-Mobile G-Slate
This process works under Linux. The hard part under Windows would be mounting a file as an ext4 filesystem, but if you can do that you win.
You need:
The four files in the gslate_root.zip archive attached to this post.
To root:
Put those four files in a directory and open a terminal to there.
Shut down your G-Slate and plug it into your computer via USB.
Hold down both volume buttons and press the power button. The G-Slate will not appear to turn on, but it'll go into APX mode.
Running "lsusb" should show an entry "0955:7820 NVidia Corp."
Run the command "sudo su" to get a root shell. Running "ls" should still show the four files.
./nvflash --bl bootloader.bin --getpartitiontable ptable.txt
./nvflash -r --read 8 system-orig.img
Wait while 400 meg of data copies.
cp system-orig.img system.img
mkdir system
mount -o loop system.img system
cp su system/bin
chmod 4755 system/bin/su
cp Superuser.apk system/app
umount system
./nvflash -r --download 8 system.img
Wait while it copies back.
./nvflash -r --sync
Press the reset button under the sim cover to reboot.
There's your rooted G-Slate. Making that process "one click" is going to suck.
Troubleshooting:
You may need to install the package libstdc++6 or lib32stdc++6 to get nvflash to run.
You may need to use "sudo" on the nvflash commands.
If you want to try to make this work on Windows, the nvflash.exe binary and the APX USB drivers are are available from nvidia.com

This is unbelievable! Can't wait to give it a shot.

EDIT: For future reference, DO NOT use Virtual Box to try and root your device. There are issues getting the drivers to work properly. Lsusb will not work. The following methods have been tested and work:
1. Wubi install of Ubuntu Linux
2. VMware install of Ubuntu Linux
3. Dual-boot install of ""
4. Dedicated Linux box (duh)
And remember: If at first you don't succeed, try try again. Then visit our IRC channel.
Trying this on Windows 7 is gonna be a trip. Never workt with ext4 before.

Install Ubuntu and you can dual boot into Windows or Ubuntu. That's what I do.
Sent from my LG-V909 using XDA Premium App

This method is confirmed working. Thank you so much for the hard work Chandon. It wasn't very hard to complete on Linux. I can't believe my G-Slate is rooted!!!! Hell yes! Oh and the device is not wiped during the process either just to let everyone know!

Some More Help
Would it be possible to pull the recovery partition off now?
Why I ask. I am in a bit of a pickle. My slate will get to the first LG boot screen and then freeze. It does not even go to the boot animation. I can still get into fastboot and APX mode and it is seen by my computer.
How did i get here. While poking around in fastboot I am pretty sure i wiped they recovery partition D'OH.
I was able to complete the steps listed (for root) with out issue but still cannot get past the boot screen since this is only modifying the system partition.
I am thinking that if that could be pulled from the device i could flash it to mine and bring my slate back to life?
Am I way off on this one?

SmellyTunic -
Attached are all the reasonably small partitions that I could pull off my device with nvflash. This should be everything except /system, /cache, and /data.
I suggest backing everything up before flashing any of these, on the off chance that there's some difference between devices.

Thanks so much for this! Is there a good linux live cd(or bootable usb flash drive) someone could suggest where this could be accomplished easily? Not ready to take the plunge actually installing linux on my system yet >.>

Here you go
shinkinrui
Info and steps can be found here http://www.ubuntu.com/download
Pretty easy to set up a dual boot machine.
Chandon,
Any chance you know off hand which one of those partitions is the recovery?

I suggest doing a Wubi install [1], where Ubuntu pretends to be a Windows app (which you can then uninstall like any other app later). Alternatively you could try using VirtualBox [2], but that's less guaranteed to work.
The only reason I wouldn't do this with a Live CD is that you'd risk losing your backup of the stock /system partition when you reboot. It would also make losing power in the middle of the flash really annoying.
[1] https://wiki.ubuntu.com/WubiGuide
[2] (edit: virtual box doesn't easily see the USB device)

Thanks guys, reading about that Wubi solution looks like the simplest way to have a dual-boot system. I like it! I'll be getting my root on later tonight

i prefer Ubuntu just cause you can install it in windows then simply restart and boot into Linux or Windows. This way you don't need to worry about not having Linux again.

SmellyTunic said:
Any chance you know off hand which one of those partitions is the recovery?
Click to expand...
Click to collapse
I'm sure that /system is 8 and the kernel is 13, but don't know about anything else. You might be able to figure it out by reading the ptable.txt file generated by the --getpartitiontable command - it's pretty clear except for the part where it uses 3 letter partition names.

Thanks. I will take a look when i get home from work.
Sent from my GT-I9000 using XDA App

While we are on the topic of development, we really need a forum over here at XDA for the G-Slate!

deez1234 said:
While we are on the topic of development, we really need a forum over here at XDA for the G-Slate!
Click to expand...
Click to collapse
I definitely concur.

thengkiu so much
works like a charm

I have no idea why I'd ever need/want to root my G Slate, I'm fairly simple in my desires for my device - but I have to say I'm delighted to see it is possible and am ever so grateful for folks who figure this stuff out because it keeps moving G Slate towards legitimacy.
Thank you!!

The hard part under Windows would be mounting a file as an ext4 filesystem, but if you can do that you win.
Click to expand...
Click to collapse
No kidding. Since the linux method failed miserably for me, I've decided to press forward with trying to do it on Windows. Problem is, I have yet to find any way to mount an ext4 filesystem on Windows. There are several options out there that will allow you to read ext4 filesystems on Windows, but not write. Any suggestions?

my friend will be happy to see that this is possible.

[Q] SD card can't be mounted - Desire PVT4 after rooting

Hi guys,
I got a problem:
I rooted my Desire PVT4 with unrevoked and AmonRa-Recovery under Linux Mint Live CD. Everything went fine.
Next, I wanted to prepare for flashing a new rom. I did a Titanium Backup and downloaded Rom Manager. I proceeded to do a nand-backup, which it did, I guess. After that, however, my desire didn't recognize my sd card anymore.
Connecting to Windows 7 didn't work either. (It did work before)
So I went and bought a new sd card. I formatted it and put it in my device. Still, no sd card detected.
Along with the new sd card, I got an adapter, so I can now stick the sd card directly into my computer.
Surprise: I could now see both sd cards in Windows. Still, I formatted both after backing up the files on it.
The Desire wasn't able to boot anymore, though. So I went into recovery mode and partitioned the card manually with AmonRa recovery 2.0.1. This did work.
I can boot the Desire now, but it still won't detect the sd card.
Mounting it with AmonRa doesn't work either.
I read, that the problem might be caused by using RomManager on a PVT4 device.
Installing the HTC drivers didn't help and I can't install the google USB drivers. When I try to do so it says that there were no drivers found in the specified directory (""C:\android-sdk-windows\google-usb_driver")
In the device manager it shows 3 "Qualcomm CDMA Technologies MSM" (bought it in Germany, so shouldn't it read "GSM"?). All of them are marked with a yellow question mark. Upon trying to update the drivers I selected "Install software from a list or source" and specified ""C:\android-sdk-windows\google-usb_driver". I clicked "proceed" but Windows tells me that it couldn't find the drivers. Tried that on Win7 and on my WinXP laptop.
I desperately need help. I'm no pro. Actually I am a complete noob I searched on google but I couldn't find any solution so far.
Since I can't access my sd card (except partitioning in AmonRa, that did work somehow) I can't access any .zip on my sd card.
e. Additional information:
Upon trying to mount in Amonra recovery it says:
""Can't mount /sdcard"
Same, when trying to flash a .zip from sd.
hboot version is 0.93 I think.
I tried the following:
Just fixed it... i think the problem erupted because i have AmonRA recovery and used Rom manager (Clockwork mod recovery based) .. there were several reports
that this may cause a usb brick. ... any way... i searched for how to unbrick it.. and used a clone cd from modaco ((Tinycore.img)) which is linux based to boot from it (with phone connected to fastboot usb) .. and
entered the following commands :
Quote
sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom
cd /mnt/cdrom/root
/mnt/cdrom/root/fastboot oem enableqxdm 0
and it enabled the sdcard... i checked the sdcard workability from the recovery (i hadn't format it yet) then thought : WTH, why not to try and restart the phone to see if it will log in normally .. and it did (naturally
because the sdcard block was the thing that prevented it from booting from the very start)...
Click to expand...
Click to collapse
Except that I used Linux Mint Live CD.
All I got was:
Code:
sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom
mount: block device /dev/sr0 is write/protected, mounting read-only
sudo mount /dev/cdrom /mnt/cdrom
mount: block device /dev/sr0 is write-protected, mounting read-only
mount: /dev/sr0 already mounted or /mnt/cdrom busy
mount: according to mtab, /dev/sr0 is already mounted on /mnt/cdrom
cd /mnt/cdrom/root
bash: cd: /mnt/cdrom/root: No such file or directory
Must I use TinyCore? I read somewhere that it only works for Hboot 0.8 and lower? What exactly is TinyCore anyways?
I almost know nothing about linux

No one?
Now I can't even get a signal anymore. I could cry...

Have you tried this procedure?
http://forum.xda-developers.com/showthread.php?t=691639
It worked for me when i bricked (pvt1 s-off). The problem seems to lie in the misc partition, which you have patch with the edited img file...

When I get into fastboot mode, where is the option to "'fastboot oem boot'"?
e. Also, my PC does not recognize the desire when pluggin into USB.

Eiskrem-Kaiser said:
When I get into fastboot mode, where is the option to "'fastboot oem boot'"?
Click to expand...
Click to collapse
You type that into cmd prompt window on your PC.
There are some instructions on SD card fix in this thread:
http://forum.xda-developers.com/showthread.php?t=691639

It happened to me when I partitioned the SD card in windows. Could you chech if your partitions on your SD are both set as primary and also uncheck "Take ownership of filesystem" (or something like that) when you are using the HD utility in linux.
Basically what happened was that the partitions were logical in stead of primary. Banged my had in the wall for two days before I figured this out. Hope it helps.

I'll try the Usb-brick-fix first. But how do I find out which rom version I have? I managed to get my CID by typing "fastboot oem boot" in the command prompt.
e. This is what I get upon writing the command:
http://www.abload.de/img/unbenannt7njw.jpg
e. I noticed, it says "board_bravo.disable-sdcard=1"
what does that mean?

Eiskrem-Kaiser said:
I'll try the Usb-brick-fix first. But how do I find out which rom version I have? I managed to get my CID by typing "fastboot oem boot" in the command prompt.
e. This is what I get upon writing the command:
http://www.abload.de/img/unbenannt7njw.jpg
e. I noticed, it says "board_bravo.disable-sdcard=1"
what does that mean?
Click to expand...
Click to collapse
I guess it means that sdcard can't be mounted...anyway, have you done the hexeditor thing already?

I just put the two files on the sd card and rebooted in fastmode. However, I'm not sure about my rom version. Where can I find out which one I have?
e. I just typed "cat /sdcard/flash_image > /data/flash_image" in ConnectBot, but it says "cannot create /data/flash_image: permission denied"
e.. When I type in "su" first, it still says "/sdcard/flash_image: No such file or directory"

Eiskrem-Kaiser said:
Where can I find out which one I have?
Click to expand...
Click to collapse
Oh sorry, i didn't read that...well i remember i was confused about that too at this point...too bad i can't remember how i found out.
Anyway, i found another solution on modaco:
"2. Enable the SD Card functionality. Boot your phone in FASTBOOT mode (back + power), and enter this command: 'fastboot oem enableqxdm 0' . This will re-enable your SD card.
3. Put THIS (attached) update.zip on your sdcard.
4. Reboot into recovery.
5. Apply sdcard:update.zip.
6. This will automatically fix your MISC partition with the correct CID. Reboot, and your done!"
Try this and tell me if it works in the while

I just booted into fastmode again and typed "fastboot oem enableqxdm 0" into the command prompt.
Now the Desire detects the sd card again :thumbsup:
Now I will try to use the cat command again.
e. I just did the thing with the "update.zip". Rebooting now.
e. I got my sd card back and a phone signal. That's great so far. Now what?

Still, when typing
"cat /sdcard/flash_image > /data/flash_image"
I get
"/sdcard/flash_image: No such file or directory"

I guess you're done if it worked...are you able to connect normally to your pc now? You should be :s
Also, those commands are meant to be used in a terminal emulator, not on your pc, i hope you didn't misread...anyway if you used the modaco tip you shouldn't need that anymore.
When you're done remember to copy your misc folder to a safe place, it will be enough to replace it via root explorer or similar if someday you'll brick again...

Nope, can't get it to connect to my PC quite yet. But I hope I will get that to work after rebooting the phone and/or windows or installing the htc drivers again.
I can not thank you enough right now. I was going crazy about this. Just bought my desire recently, upgrading from the Legend, with the little spare money I had. It would have been bad, if it was broken now.
So: THANK YOU VERY MUCH.
Also, someone tried to call me yesterday, while my phone signal didn't work. Now everytime I start the Phone, it shows me my missed call.
My girlfriend has a similar problem with a message I sent her. Everytime she boots her phone, she gets that message (fortunately it's "I love you" ).
So, I guess, it has something to do with the SIM?

Hmm, if you can't connect it might mean that the usb isn't fully restored...could you turn off the phone, plug it to pc, turn it back on and see if drivers get installed properly? Just to make sure...

I am stupid.
Hold on, it might work now. I had to switch to "local" in ConnectBot. Thought the app would remember that, but it didn't

Hmm.
Do I have to be in fastboot mode to type in those commands? Because I did type them in and rebooted, but Windows still will not detect my Desire :/
or should I type them in the windows command prompt?

Eiskrem-Kaiser said:
Hmm.
Do I have to be in fastboot mode to type in those commands? Because I did type them in and rebooted, but Windows still will not detect my Desire :/
or should I type them in the windows command prompt?
Click to expand...
Click to collapse
Sorry, i'm not sure i got ya. How would you run connectbot while you're in saftboot mode?? Because that's what i did, to make it clearer:
1. Downloaded image file "mtd0.img" and "flash_image" (from here http://forum.xda-developers.com/showthread.php?t=691639) and put them on sdcard (ofc i edited mtd0.img with my CID using some free hex editor before)
2. Installed Android Terminal Emulator app (from market), but connectbot should be the same.
3. Opened emulator, typed "su" command, accepted to give root permissions
executed this commands:
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/misc.img > /data/misc.img
chmod 755 /data/flash_image
/data/flash_image misc /data/misc.img
4. Rebooted phone, connected to pc.
5. Success
Is this exactly what you did?

Yes. I typed exactly that. I just wanted to type it in again, but now it tells me again, that there is no such file or directory on /sdcard. But I can see the file with Astro being on the sdcard.
e. Maybe I used the wrong rom version number?
e.. Someone suggested to run in fastboot mode and type "fastboot oem eraseconfig". What exactly would this do? Which config would be erased?
What exactly is fastboot?

Eiskrem-Kaiser said:
Maybe I used the wrong rom version number?
What exactly is fastboot?
Click to expand...
Click to collapse
You just need the CID, not the rom version for this...
Anyway, please note that when i write misc.img i mean mtd0.img, that's what you typed right? Sorry if i confused you.
I guess there's no need to mess further with fasboot, i didn't need it, except for mounting sdcard.
If this still fails, you can always move mtd0.img and flash_image to /data manually via root explorer app, then go on from the chmod command.

[Q]How to fsck /data or /system?

Does anybody know of a way to fsck the system or data partitions? I've run into a few times where I had data errors on /data, and the only way I could think of to fix them was to do a backup and restore. I was worried about losing data during the backup process, as the filesystem was already questionable.
I have e2fsck in my rom, but I can't run it from a normal shell as the filesystems are already mounted. Is there a way to make a rom automatically check and repair the filesystems on boot, and if so, how can I control the options it passes to fsck? Are there other ways to get to an unmounted system or data partition? Does clockworkmod have any kind of shell or fsck utilities built in? Are there other recovery programs that may have something like that?

You should be able to boot into CWM, unmount the partitions, connect with adb and run it from there. At least if your version of CWM has fsck in it.
Sent from my SPH-D700 using xda premium

You should be able to do it while booted into recovery through ADB.
Boot to recovery
connect usb cable to PC
run `adb shell`
Code:
unmount /data
unmount /system
fsck /dev/block/stl9
fsck /dev/block/stl10
syntax for above commands needs to be checked.

toadlife said:
You should be able to do it while booted into recovery through ADB.
Boot to recovery
connect usb cable to PC
run `adb shell`
Code:
unmount /data
unmount /system
fsck /dev/block/stl9
fsck /dev/block/stl10
syntax for above commands needs to be checked.
Click to expand...
Click to collapse
Just tried this out myself. Here's the correct syntax for the fsck command:
Code:
e2fsck -fv /dev/block/stl10
EDIT: Forgot to mention also that unmount should actually be umount. Or you could just use the CWR menus to unmount partitions.

zman0900 said:
Just tried this out myself. Here's the correct syntax for the fsck command:
Code:
e2fsck -fv /dev/block/stl10
Click to expand...
Click to collapse
How bout mtd?
sent from my always aosp epic

Please consider posting questions in Q&A next time. Thank you.

Sorry for the "newbie spam"! But that worked perfectly - I didn't realize that adb shell worked when booted from cwm. That's exactly what I was looking for.

zman0900 said:
Just tried this out myself. Here's the correct syntax for the fsck command:
Code:
e2fsck -fv /dev/block/stl10
EDIT: Forgot to mention also that unmount should actually be umount. Or you could just use the CWR menus to unmount partitions.
Click to expand...
Click to collapse
Thanks for this, this is why i love xda!
I have e2fsck in my /bin
On a samsung galaxy s2 i9100
How do i identify my /system & /data blocks
I cant remember how to find out!
So mine would be
e2fsck -fv /dev/block/????
Thanks

Colliebudz said:
Thanks for this, this is why i love xda!
I have e2fsck in my /bin
On a samsung galaxy s2 i9100
How do i identify my /system & /data blocks
I cant remember how to find out!
So mine would be
e2fsck -fv /dev/block/????
Thanks
Click to expand...
Click to collapse
If you run mount with no arguments, it will show a list of mounted partitions like "xxx on /system".

Colliebudz said:
Thanks for this, this is why i love xda!
I have e2fsck in my /bin
On a samsung galaxy s2 i9100
How do i identify my /system & /data blocks
I cant remember how to find out!
So mine would be
e2fsck -fv /dev/block/????
Thanks
Click to expand...
Click to collapse
Better to do /dev/block/platform/(your processor)/by-name/xxxx. Less chance of error

Colliebudz said:
Thanks for this, this is why i love xda!
I have e2fsck in my /bin
On a samsung galaxy s2 i9100
How do i identify my /system & /data blocks
I cant remember how to find out!
So mine would be
e2fsck -fv /dev/block/????
Thanks
Click to expand...
Click to collapse
the easiest was to find what /system and /data mount points actually are
cat /etc/fstab
to see a list of mount points.

toadlife said:
You should be able to do it while booted into recovery through ADB.
Boot to recovery
connect usb cable to PC
run `adb shell`
Code:
unmount /data
unmount /system
fsck /dev/block/stl9
fsck /dev/block/stl10
syntax for above commands needs to be checked.
Click to expand...
Click to collapse
How do I get the Moto X in Recovery mode to accept the adb command?
Because when I put in Recovery (Android Robot lying down) mode, the command adb and fastboot are not recognized.

rod.gui said:
How do I get the Moto X in Recovery mode to accept the adb command?
Because when I put in Recovery (Android Robot lying down) mode, the command adb and fastboot are not recognized.
Click to expand...
Click to collapse
Flash a custom recovery first. (CWM/TWRP)
Sent from Motorola Photon Q 4G LTE @ CM11

My phone is Huawei G525. It doesn't have CWM or any custom stuff, just rooted.
My problem is that it reports an imagic flagged inode and it recommends to fsck the partition (/system). The logs are saved in sdcard folder.
I can use adb and fastboot, but fastboot shell doesn't work and /system is mounted when i can use adb.
Is there any solution for me to run e2fsck on /system partition?
Or is there the case to worry about that error? The phone works fine...no random reboots, no crashes, no force closes.
Another thing...I've tried to make a romdump and system archive is damaged. Cannot be opened even with 7-zip.

mandgeo said:
My phone is Huawei G525. It doesn't have CWM or any custom stuff, just rooted.
My problem is that it reports an imagic flagged inode and it recommends to fsck the partition (/system). The logs are saved in sdcard folder.
I can use adb and fastboot, but fastboot shell doesn't work and /system is mounted when i can use adb.
Is there any solution for me to run e2fsck on /system partition?
Or is there the case to worry about that error? The phone works fine...no random reboots, no crashes, no force closes.
Another thing...I've tried to make a romdump and system archive is damaged. Cannot be opened even with 7-zip.
Click to expand...
Click to collapse
G525 DOES have CWM recovery available, find and install one so that you can fsck from recovery using adb.
Sent from Google Nexus 4 @ CM11

AndyYan said:
G525 DOES have CWM recovery available, find and install one so that you can fsck from recovery using adb.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
As far as I understand from here... http://bbs.dospy.com/thread-16432606-1-823-1.html , the bootloader needs to be unlocked. I've submitted for an update code and i'll wait. The chinese guy talks about U8950, but there are five different types. I've selected the first one, U8950-1. Maybe i'm lucky.
I've also tried to boot directly into the recovery found here... http://www.needrom.com/mobile/huawei-g525-u00/ , but that command is not allowed, maybe because the bootloader is locked. That was the only recovery i found that seems to be in english.
I'll try the same procedure to boot into recovery (fastboot boot recovery.img) because i don't want to mess things more that they are. I didn't found any tutorial in english and google translate is confusing.
Thanks!
LE. Does anybody know if Huawei rewrites the custom recovery if it's not the stock one.

mandgeo said:
As far as I understand from here... http://bbs.dospy.com/thread-16432606-1-823-1.html , the bootloader needs to be unlocked. I've submitted for an update code and i'll wait. The chinese guy talks about U8950, but there are five different types. I've selected the first one, U8950-1. Maybe i'm lucky.
I've also tried to boot directly into the recovery found here... http://www.needrom.com/mobile/huawei-g525-u00/ , but that command is not allowed, maybe because the bootloader is locked. That was the only recovery i found that seems to be in english.
I'll try the same procedure to boot into recovery (fastboot boot recovery.img) because i don't want to mess things more that they are. I didn't found any tutorial in english and google translate is confusing.
Thanks!
LE. Does anybody know if Huawei rewrites the custom recovery if it's not the stock one.
Click to expand...
Click to collapse
Well, you know this forum is dedicated for discussion about Samsung Epic 4G, not Huawei G525... But to help you out I might be able to dig in a bit more later this week when I have time. I'm a Chinese myself and can (hopefully) understand these procedures.
Sent from Google Nexus 4 @ CM11

AndyYan said:
Well, you know this forum is dedicated for discussion about Samsung Epic 4G, not Huawei G525... But to help you out I might be able to dig in a bit more later this week when I have time. I'm a Chinese myself and can (hopefully) understand these procedures.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
My phone is a Note 2 LTE N7105 - I realise not the same as this thread, but this is the only thread I have found that is discussing this. My /data partition needs an fsck, however, while I can adb to the phone when it is booted, I can't when it is in recovery.
I have TWRP 2.7.1.0 installed, and everything else works fine. When the phone is booted, I get the GT-N7105 driver appearing in portable devices in device manager, but when recovery is booted, I just get t0lte in "other devices".
Seems like the Samsung USB driver only works when the phone is properly booted, and doesn't match when booted to recovery.
Any ideas how to work around this?

paulkoan said:
My phone is a Note 2 LTE N7105 - I realise not the same as this thread, but this is the only thread I have found that is discussing this. My /data partition needs an fsck, however, while I can adb to the phone when it is booted, I can't when it is in recovery.
I have TWRP 2.7.1.0 installed, and everything else works fine. When the phone is booted, I get the GT-N7105 driver appearing in portable devices in device manager, but when recovery is booted, I just get t0lte in "other devices".
Seems like the Samsung USB driver only works when the phone is properly booted, and doesn't match when booted to recovery.
Any ideas how to work around this?
Click to expand...
Click to collapse
Yes, the workaround is to not use stupid Windows.
Works fine on linux.

run terminal app:
su
touch /forcefsck
Then reboot. It might depend on your ROM, but give it a go.

Kindle Fire Brick Utility not working

So i think I bricked my kindle fire. It is rooted and when trying to install a new ROM, i accidentally selected the fastboot option. Now, when I power it on, all i get is the logo and it never loads. I cannot get into the boot manager to try anything. I have tried the Kindle Unbrick utility from this link: http://forum.xda-developers.com/showthread.php?t=1428428 and it says waiting for device when I run the stuck on logo option. Is there anything else I can do? I really dont want to get another one. Any help would be appreciated! I can't post in the development forum so thats why i posted here. Thanks everyone.

What version of Windows are you using?

Read the WHOLE first post of the Unbrick Utility thread. It's a driver problem.

Thanks I got it to work now but now when I plug it into the USB, it does not show that I can open it and drop files. I go into TWRP and try to mount the USB and it will not let me and I am unsure what to do!

roykurka said:
Thanks I got it to work now but now when I plug it into the USB, it does not show that I can open it and drop files. I go into TWRP and try to mount the USB and it will not let me and I am unsure what to do!
Click to expand...
Click to collapse
If you're using an ICS ROM I don't believe mounting "mass storage" works on all of them.
Does it saying anything when trying to mount USB in TWRP? What does "won't let me" imply? Windows or TWRP throws an error message?

When I go into TWRP and go to MOUNT and then try to select Mount SDCard it will not let me check the box. I have a ROM running on it now but I cannot access the SD card when I plug it into the computer.

roykurka said:
When I go into TWRP and go to MOUNT and then try to select Mount SDCard it will not let me check the box. I have a ROM running on it now but I cannot access the SD card when I plug it into the computer.
Click to expand...
Click to collapse
What ROM are you using?

nchevaux said:
What ROM are you using?
Click to expand...
Click to collapse
i am using CyanogenMod 9.0.0-RCO-otter-UNNOFFICIAL
Also, when i go to the about tablet on the Kindle and look at Model Number, it shows Galaxy Nexus.....

Any other suggestions or help?

roykurka said:
Any other suggestions or help?
Click to expand...
Click to collapse
Boot into TWRP and get to a prompt using adb shell. Then use this command to open parted...
Code:
parted /dev/block/mmcblk0
When you get to the "(parted)" prompt...
Code:
print
The last line, the media partition, is what gets mounted as /sdcard on your device. It should have a "fat32" file system type. If you don't have that, you need to make a new filesystem on that partition.
Code:
mkfs 12 fat32
12 is the partition number and fat32 is the filesystem type you want to use to format the partition. If memory serves, parted will ask you for this information again to confirm. Remember... 12 and fat32. Once you are done, you can...
Code:
quit
Once you've done that, TWRP should be able to see the partition and allow you to mount it on your host computer. You might have to restart TWRP... I don't remember.

I have not been able to get adb to run. When i boot to TWRP and go to the command prompt and type adb devices it says " 'adb' is not recognized as an internal or external command, operable program or batch file."
I set the path to where the android sdk is located and it still doesnt work.
Im sure I sound like a newb or something but I am just not as tech savy with these kind of things. thanks everyone for your help with this.

roykurka said:
I have not been able to get adb to run. When i boot to TWRP and go to the command prompt and type adb devices it says " 'adb' is not recognized as an internal or external command, operable program or batch file."
I set the path to where the android sdk is located and it still doesnt work.
Im sure I sound like a newb or something but I am just not as tech savy with these kind of things. thanks everyone for your help with this.
Click to expand...
Click to collapse
Find the adb executable through Windows Explorer. Once you find the folder containing adb, shift-right-click inside that folder and select "Open command window here" and then you'll be able to use the adb command.
Another way to do it is to download the Kindle Fire Utility distribution and follow the third post in this link...
http://forum.xda-developers.com/showthread.php?t=1552547
You don't have to set the path to anything special if you do it one of those two ways.

roykurka said:
I have not been able to get adb to run. When i boot to TWRP and go to the command prompt and type adb devices it says " 'adb' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
It seems you have set your path incorrectly. I found it easiest to just copy the entire platform-tools folder to the root of C:\ and run adb from there (You could also use a Windows shortcut to cmd with "start in" filled out, or use shift-right click through explorer).
Definitely try to get adb working; when I first rooted my Kindle it took me an hour to fix a boot-loop without adb (damn drivers), and only seconds with adb.

kinfauns said:
Boot into TWRP and get to a prompt using adb shell. Then use this command to open parted...
Code:
parted /dev/block/mmcblk0
When you get to the "(parted)" prompt...
Code:
print
The last line, the media partition, is what gets mounted as /sdcard on your device. It should have a "fat32" file system type. If you don't have that, you need to make a new filesystem on that partition.
Code:
mkfs 12 fat32
12 is the partition number and fat32 is the filesystem type you want to use to format the partition. If memory serves, parted will ask you for this information again to confirm. Remember... 12 and fat32. Once you are done, you can...
Code:
quit
Once you've done that, TWRP should be able to see the partition and allow you to mount it on your host computer. You might have to restart TWRP... I don't remember.
Click to expand...
Click to collapse
When i try the first command, i get the same response saying parted is not recognized as an internal or external command, operable program or batch file.
I have the kindle in TWRP and connected to the PC. What do I do now?

roykurka said:
When i try the first command, i get the same response saying parted is not recognized as an internal or external command, operable program or batch file.
I have the kindle in TWRP and connected to the PC. What do I do now?
Click to expand...
Click to collapse
okay... I'm going to make this super easy for you... get ADB working...
1. Download attached "adb.zip"
2. Extract adb.zip to a folder
3. Double-click "CLICK ME!!!"
4. Type "adb" and see instructions come up
5. Type "adb devices" and see a 12-digit code
now reread your own thread and try all those instructions again in ADB
P.S. type "ADB shell" before trying the instructions from kinfauns

When I type the adb devcies it says "list of devices attached but does not show anything.
I apologize for probably something so simple

roykurka said:
When I type the adb devcies it says "list of devices attached but does not show anything.
I apologize for probably something so simple
Click to expand...
Click to collapse
I think you should back up a bit and read this...
http://forum.xda-developers.com/showthread.php?t=1552547
Start at post #1... follow the steps in #2 and confirm your device drivers are getting loaded properly... study #3 for fastboot and adb commands.
#2 is going to be the most important for you because it looks like there's a problem with your device drivers or you are missing a necessary initialization file. Following the directions there will get you fixed up.
After doing all that, go back to my previous post.

It works, I got to mount the SD card and everything. Thank You everyone for all of your help!

Galaxy S2 broken screen CWM recovery help

As title states. i recently broke the screen on my galaxy s 2 and i cant access the internal storage.
first of all the phone has the latest cwm recovery and latest nightly. when i connect the phone to the computer i cant access the sd card or the internal storage because its password protected and opens via the media device transfer. so i heard u had to do it via adb in the recovery/
i have tried this method https://plus.google.com/112476065271141473049/posts/BDghkbfpHEp
but it says that adb is unable to connect for backup. i do have the latest ADB as well.
i also tried manually pulling from adb with these " adb pull /sdcard/ C:\sdcard-backup\ " but nothing happens. says that its generating a file list but stays there forever.
my question is how can i go about removing my pictures from this phone with broken screen?
is there a cm nightly that anyone knows of that doesnt use the MTP ?
pretty much what i would like to be able to do is flash new rom and connect to pc and be able to extract my internal storage files, or find an alternate way of removing files.i have also tried a nandroid backup, but that didnt save my internal files, only data.
any help is appreciated.
also tried using this tool but couldnt really figure it out. thanks.
http://anddisa.tk/

You could try to use the A.R.T. to do a backup of the UMS partition (/sdcard) and then loop mount the resulting img-file. First you need to be sure that the recovery mode is started and your device is recognized, i.e.
Code:
art.sh -devices
should list your device connected to your pc. If this is the case, you can try to do a backup of your sdcard-partition, i.e.
Code:
art.sh -backup -i -bd /tmp -tsf yyyy-MM-dd-hh-mm UMS
Be sure to have enough space on the partition / device you are writing your backup file, because it will be have around 12GB.
If all went well, you will find a file named UMS.img which is an image backup of your phones /sdcard partition. Now you can mount loop this file to read / extract the files you want, i.e.
Code:
mount -o loop UMS.img /mnt
Now an
Code:
ls -l /mnt
should give you a file listing of the root directory of the /sdcard partition.
bootleg16 said:
As title states. i recently broke the screen on my galaxy s 2 and i cant access the internal storage.
first of all the phone has the latest cwm recovery and latest nightly. when i connect the phone to the computer i cant access the sd card or the internal storage because its password protected and opens via the media device transfer. so i heard u had to do it via adb in the recovery/
i have tried this method https://plus.google.com/112476065271141473049/posts/BDghkbfpHEp
but it says that adb is unable to connect for backup. i do have the latest ADB as well.
i also tried manually pulling from adb with these " adb pull /sdcard/ C:\sdcard-backup\ " but nothing happens. says that its generating a file list but stays there forever.
my question is how can i go about removing my pictures from this phone with broken screen?
is there a cm nightly that anyone knows of that doesnt use the MTP ?
pretty much what i would like to be able to do is flash new rom and connect to pc and be able to extract my internal storage files, or find an alternate way of removing files.i have also tried a nandroid backup, but that didnt save my internal files, only data.
any help is appreciated.
also tried using this tool but couldnt really figure it out. thanks.
http://anddisa.tk/
Click to expand...
Click to collapse

AndDiSa said:
You could try to use the A.R.T. to do a backup of the UMS partition (/sdcard) and then loop mount the resulting img-file. First you need to be sure that the recovery mode is started and your device is recognized, i.e.
Code:
art.sh -devices
should list your device connected to your pc. If this is the case, you can try to do a backup of your sdcard-partition, i.e.
Code:
art.sh -backup -i -bd /tmp -tsf yyyy-MM-dd-hh-mm UMS
Be sure to have enough space on the partition / device you are writing your backup file, because it will be have around 12GB.
If all went well, you will find a file named UMS.img which is an image backup of your phones /sdcard partition. Now you can mount loop this file to read / extract the files you want, i.e.
Code:
mount -o loop UMS.img /mnt
Now an
Code:
ls -l /mnt
should give you a file listing of the root directory of the /sdcard partition.
Click to expand...
Click to collapse
I am having trouble setting up ART on windows. I downloaded the cmd script but don't know exactly what to do via cmd.

The cmd takes the same parameters as the .sh. To get it working, the easiest way is to have the latest android development tools installed and have the tools / platform tools directory within your path. Otherwise you need to define the path to the tools directory (-td parameter). Probably it will help you, too, to have a look at the sources, which are located on Github.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
The cmd takes the same parameters as the .sh. To get it working, the easiest way is to have the latest android development tools installed and have the tools / platform tools directory within your path. Otherwise you need to define the path to the tools directory (-td parameter). Probably it will help you, too, to have a look at the sources, which are located on Github.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
attached is an image.
im not sure how to define the path but i always manually set it by cd C:\android-sdk\platform-tools
then from here i can use adb. but im still having issues with your script. everytime i run it it just opens up the notepad document

environment variable set and still this

i went ahead and redownloaded the art.cmd file and ran it from the browser and i got this for the first time and then it automatically closes the cmd screen

The first images you attached shows me, that you do not have java within your path (but you have installed as a plugin of your browser, that s the reason why it's working from there). Add the java/bin directory to your path: on the cmd window enter the following:
PATH=%PATH%;<path to java.exe>
(otherwise within the PATH environment variable within the windows system settings). After that the art.cmd should work from the cmd line, too.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
The first images you attached shows me, that you do not have java within your path (but you have installed as a plugin of your browser, that s the reason why it's working from there). Add the java/bin directory to your path: on the cmd window enter the following:
PATH=%PATH%;<path to java.exe>
(otherwise within the PATH environment variable within the windows system settings). After that the art.cmd should work from the cmd line, too.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i applied the path as showed on screenshot, but i get either an incorrect syntax or is i click the batch file the command prompt window opens but closes rapidly. i managed to capture it.

bootleg16 said:
i applied the path as showed on screenshot, but i get either an incorrect syntax or is i click the batch file the command prompt window opens but closes rapidly. i managed to capture it.
Click to expand...
Click to collapse
the first error i get is unable to access jar file. jar file is in same directory as adb, along with the .sh and .cmd

bootleg16 said:
the first error i get is unable to access jar file. jar file is in same directory as adb, along with the .sh and .cmd
Click to expand...
Click to collapse
this is what i got now

bootleg16 said:
this is what i got now
Click to expand...
Click to collapse
Use it without the wrapper, i.e. "java -jar art.jar" is perfect. The wrapper was only ment to easy the call.
The Nullpointer-Exception within the "-info" call could be due to the fact, that you have a SGH-T989 and not a i9100. In that case there is a chance, that the parameters which are to be read do not exist / cannot be read.
The call before, i.e. where you tried to do the backup, has a wrong parameter: "<C:\...>" is not a correct path, you need at least remove the "<" and ">".

i cant figure out why i keep getting this error.
what is
/tmp ?

'/tmp' is a directory where you would like to get written the backup file(s), I.e.
java -jar art.jar -backup -i -bd <backup-dir> ...
Probably it would help you to have a look at the sources? You can find them on my GitHub repository.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
'/tmp' is a directory where you would like to get written the backup file(s), I.e.
java -jar art.jar -backup -i -bd <backup-dir> ...
Probably it would help you to have a look at the sources? You can find them on my GitHub repository.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Did u take a look at the screenshot.? My backup directory is c:android-sdk.
If u see the argument I changed i get a different error. Why? And yes I did lookbat your sources, with only Unix examples.

But why did you put /tmp as an additional parameter?
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
But why did you put /tmp as an additional parameter?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
See I did it with the /tmp and without also. When I did it without it said invaded partition name for UMS. As seen on screenshot.

as seen on this screen shot, doing this,
java -jar art.jar -backup -i -bd C:\android-sdk\ -tsf yyyy-MM-dd-hh-mm
i get nothing. its just returns. what can be wrong.
if i add UMS to the end, it says that unknown partition.
adding UMS based on what u wrote earlier.
art.sh -backup -i -bd /tmp -tsf yyyy-MM-dd-hh-mm UMS

Could you first try to do a
java -jar art.jar -info
Which should give you some detailed information of the device and, if possible, a list of available partitions.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Could you first try to do a
java -jar art.jar -info
Which should give you some detailed information of the device and, if possible, a list of available partitions.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i get a nullpointer exception
what can be causing this?
does it matter if use "cd C:\javalocation" ?