Database Develop

[GUIDE] Rooting the 10.1 Tab

Here's a quick run through on how to root the Galaxy Tab 10.1. I'm doing this for people (like me) that had a tough time getting the USB drivers to work after getting their Tab at I/O.
Assuming you have adb and the SDK set up on your Win7 machine, proceed.
1. Download the new USB drivers at http://downloadcenter.samsung.com/c...78/Samsung_USB_Driver_P4_Including_Escape.exe
2. Reboot your machine
3. Plug the 10.1 Tab into USB
4. Download the root exploit at http://lts.cr/bqf (or use allidoiswin.zip somewhere else)
5. Then, open up a command prompt ("cmd" under Run...)
6. Run the following commands:
Code:
adb push Samsung_Galaxy_Tab_10.1_root.zip /sdcard/Samsung_Galaxy_Tab_10.1_root.zip
Code:
adb reboot recovery
7. Once you're in recovery, select the zip file, then apply, then reboot.

I was under the impression that the Galaxy Tab 10.1 devices at I/O did not have an SD card. How is it being pushed to one?

keyl10 said:
I was under the impression that the Galaxy Tab 10.1 devices at I/O did not have an SD card. How is it being pushed to one?
Click to expand...
Click to collapse
Great question. Looks like Sammy and El Goog have set up the 32GB on board as the "sdcard". You can push stuff to the personal storage by sending things to /sdcard/.

keyl10 said:
I was under the impression that the Galaxy Tab 10.1 devices at I/O did not have an SD card. How is it being pushed to one?
Click to expand...
Click to collapse
What recovery are you booting into to get an option to flash the update? Not the factory one I suspect

bcmobile said:
What recovery are you booting into to get an option to flash the update? Not the factory one I suspect
Click to expand...
Click to collapse
The stock recovery DOES allow you to choose whatever .zip file you want to flash as well as actually coming stock UNLOCKED. Awesome stuff. Thanks Google.

^ wow thats a first

oxeneers said:
The stock recovery DOES allow you to choose whatever .zip file you want to flash as well as actually coming stock UNLOCKED. Awesome stuff. Thanks Google.
Click to expand...
Click to collapse
Excellent! Anyone dumped an image yet?

oxeneers said:
Great question. Looks like Sammy and El Goog have set up the 32GB on board as the "sdcard". You can push stuff to the personal storage by sending things to /sdcard/.
Click to expand...
Click to collapse
10.1v model without the SD card, it could work with this guide?

worked like a charm, thanks!

johnblade said:
10.1v model without the SD card, it could work with this guide?
Click to expand...
Click to collapse
Not yet, as the 10.1v doesn't have the option to boot into recovery...
Sent from my GT-P7100 using XDA Premium App

thanks for the write up and thanks to drod and birdman as well. My tab is now rooted! woot!

dracoaffectus said:
worked like a charm, thanks!
Click to expand...
Click to collapse
Did you try something need root access
Like screen shot or titanium backup
B.r.
Sent from my GT-P7510 using Tapatalk

hi,
I used the recovery to "execute" the zip file attached to the first post.
It seems to execute correctly, but... I'm not sure that it rooted the tab. In fact If I try the command su in the shell (adb shell) it does nothing... till a timeout expires...
any idea?
EDIT: my fault... I didn't look at the tab screen (waiting for auth) :-D

Nice! Love Root being available before I even get a device (picking up my Google I/O 10.1 tomorrow!).

Wait, so the Tab 10.1's they gave out at I\O don't have SD Card Slots, but the ones that'll be in retail in June DO have expandable SD slots? Seems like a weird thing to do to a device you're giving to DEVELOPERS, right?

so it says i got root privalage and i do see super user but i cannot get titanium backup to run. I've even installed busybox but still not luck. help?

will89 said:
so it says i got root privalage and i do see super user but i cannot get titanium backup to run. I've even installed busybox but still not luck. help?
Click to expand...
Click to collapse
Did you click on Problem? button in TB and install busy box through there? or TB is not running at all?

bella92108 said:
Wait, so the Tab 10.1's they gave out at I\O don't have SD Card Slots, but the ones that'll be in retail in June DO have expandable SD slots? Seems like a weird thing to do to a device you're giving to DEVELOPERS, right?
Click to expand...
Click to collapse
I thought so too, but, I am not going to complain
It's a free device. The mobile bands and SD slot would have been nice, but hey they gave us the 32gb version when 16gb would have been plenty IMO.
I don't see why you'd need an SD card slot to develop for it. I've been writing just fine without it
Thanks to the people that got it rooted and such already. I never even bothered checking because I (stupidly) doubted anyone there would have bothered yet, but I decided to today to get rid of the crap loaded on. I wish it was just a basic image, but, again -- not complaining.
Thanks Google, Samsung, and the XDA devs!

keyl10 said:
I was under the impression that the Galaxy Tab 10.1 devices at I/O did not have an SD card.
Click to expand...
Click to collapse
That doesn't mean Android (or any Linux based OS) can't have an 'sdcard' partition

Anyone else having the issue where your windows machine or Mac doesn't see the device?
SGT 10.1 uplink initiative

[Q] Help with rom installation?

Hey everyone!
I am new to everything about android and just rooted my phone a couple weeks ago. I want to install the decrapified rom burin not 100% sure how to do it. I need CWM to do this right? Can I get back to my original rom if I don't like it or something goes wrong? I also hear some users talking about backing up the device. How do we do this? I know that there are lots of questions and I know some person (maybe two lol) could point me in the right direction. Thank you!
Torin

Torin_93 said:
Hey everyone!
I am new to everything about android and just rooted my phone a couple weeks ago. I want to install the decrapified rom burin not 100% sure how to do it. I need CWM to do this right? Can I get back to my original rom if I don't like it or something goes wrong? I also hear some users talking about backing up the device. How do we do this? I know that there are lots of questions and I know some person (maybe two lol) could point me in the right direction. Thank you!
Torin
Click to expand...
Click to collapse
Android Development is not for questions or Problems
Please post in the correct Forums
Moving to General

Torin_93 said:
Hey everyone!
I am new to everything about android and just rooted my phone a couple weeks ago. I want to install the decrapified rom burin not 100% sure how to do it. I need CWM to do this right? Can I get back to my original rom if I don't like it or something goes wrong? I also hear some users talking about backing up the device. How do we do this? I know that there are lots of questions and I know some person (maybe two lol) could point me in the right direction. Thank you!
Torin
Click to expand...
Click to collapse
1 yes, you need cwm to put decrapified
2 once u install cwm, make sure ur battery is full (at least 50%, but i'll just say full) and make a backup using cwm of ur current system
3 see: 2
Sent from my VS910 4G using Tapatalk

S.Meezy said:
1 yes, you need cwm to put decrapified
2 once u install cwm, make sure ur battery is full (at least 50%, but i'll just say full) and make a backup using cwm of ur current system
3 see: 2
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
Awesome thanks. Now I cant get the adb shell to work. ive done it on my dads phone before so im kinda familiar with it but the sdk still seems to be updating or whatever. Should it work when its finished?
Like when I type "adb devices" it says nothing can be found.

What operating system is ur computer on? Make sure you have installed the LG drivers if Windows.. also, doesn't hurt to be up to date w the sdk...
Sent from my VS910 4G using Tapatalk

Running windows 7 sdk updated drivers installed.
Im typing
cd C:\android-sdk\tools\
adb devices
nothing pops up. It says it isnt recognized?

1. install and update adb sdk.
2. Plug your phone in and install the drivers so it is recognized by windows as the revolution.
3. once 1 and 2 are done set your phone to internet only and turn on debugging.
4. now try adb

Torin_93 said:
Running windows 7 sdk updated drivers installed.
Im typing
cd C:\android-sdk\tools\
adb devices
nothing pops up. It says it isnt recognized?
Click to expand...
Click to collapse
also it is cd c:\android-sdk\platform-tools\

Haxcid said:
also it is cd c:\android-sdk\platform-tools\
Click to expand...
Click to collapse
I just figured out it was\platform-tools\
Like wtf they moved it? lol
I also forgot about internet mode. Im going to give it a go and if I bump into any problems I will let you know

Once I try to get su access (after checking adb access) it says not recognized. Why?

Torin_93 said:
Once I try to get su access (after checking adb access) it says not recognized. Why?
Click to expand...
Click to collapse
we're still getting cwm on...? and u already put recovery-cwm-pr1.img on ur sd?

S.Meezy said:
we're still getting cwm on...? and u already put recovery-cwm-pr1.img on ur sd?
Click to expand...
Click to collapse
Yes its there
But the su command wont work
You have skype? I could screen share.

Torin_93 said:
Yes its there
But the su command wont work
You have skype? I could screen share.
Click to expand...
Click to collapse
Make sure your screen is on when you type su so you can accept super user permission on your phone.
Sent from my VS910 4G using XDA Premium App

After I type adb devices I get the list then its:
C:\android-sdk\platform-tools>su
Right?
Cause it says not recognized

No type, adb shell, then at the next line enter su
Sent from my VS910 4G using XDA Premium App

mtmichaelson said:
No type, adb shell, then at the next line enter su
Sent from my VS910 4G using XDA Premium App
Click to expand...
Click to collapse
Great thanks!!! Im in

cat /dev/zero > /dev/block/mmcblk0p14
write: no space left on device
cat /sdcard/recovery-cwm-pr1.img > /dev/block/mmcblk0p14
no such file or directory.
Im so confused. Now what.
Thanks for everyones help so far You guys are amazing!

Torin_93 said:
cat /dev/zero > /dev/block/mmcblk0p14
write: no space left on device
cat /sdcard/recovery-cwm-pr1.img > /dev/block/mmcblk0p14
no such file or directory.
Im so confused. Now what.
Thanks for everyones help so far You guys are amazing!
Click to expand...
Click to collapse
If you are copying it in Windows, copy it to the drive marked "internal." If not, then this is telling you that file isn't on your sdcard. You need to move it there.

Its in the internal. Should it go in a folder? What about the fact that it says no space left on device?
I have plenty of space?

Torin_93 said:
Its in the internal. Should it go in a folder? What about the fact that it says no space left on device?
I have plenty of space?
Click to expand...
Click to collapse
It shouldn't need to go in a folder. The error message about space is normal (expected).

[Solved]Mount storage with broken screen?

Hello all. Searching didn't get me an answer. I'm curious if there's a way to mount the internal storage to a PC with a cracked screen. Phone definitely turns on but screen is shot. Any ideas are welcome. Thanks in advance.
Sent from my LG-P999 using XDA App

Are you lucky enough to have cwm recovery? You van mount it through there with just button presses. Done it myself, granted I had a second phone to guide me through how many times I needed to press the buttons, but it worked like a curse!

studacris said:
Are you lucky enough to have cwm recovery? You van mount it through there with just button presses. Done it myself, granted u had a second phone to guide me through how many times I needed to press the buttons, but it worked like a curse!
Click to expand...
Click to collapse
Unfortunately no. Its a friends phone so it was never rooted. Does stock recovery have that option?
Sent from my LG-P999 using XDA App

Well....damn.
I'm pretty sure it's not in stock recovery.
Was usb debuging turned on? You can use adb to pull everything from /sdcard

Not sure its worth a shot.
Adb pull /sdcard?
Sent from my LG-P999 using XDA App

No luck with adb what is download mode? Any way to use that?
Sent from my LG-P999 using XDA App

No. download mode is for flashing software onto the phone.

Been a while since I messed with my captivate but couldn't he use Odin to flash a kernel with recovery and go from there?

newter55 said:
Been a while since I messed with my captivate but couldn't he use Odin to flash a kernel with recovery and go from there?
Click to expand...
Click to collapse
****, you are exactly right!!
note to self:dont answer questions until you've had your morning coffee!!
op grab a .tar from this thread http://forum.xda-developers.com/showthread.php?t=893880&highlight=speedmod
and research how to use odin. then you will need a screen shot of cwm to guide you through how many button presses you need.

And this wont wipe the internal SD?
And I don't need root first?
Sent from my LG-P999 using XDA App

doesn't touch the internal SD
and download mode happens outside the OS no root needed.

Ill give it a go tonight or tomorrow will report back.
Sent from my LG-P999 using XDA App

ok after flashing the kernal through odin the phone is found in adb. what is the command to pull the files from the internal sd and save them to my desktop?

http://developer.android.com/guide/developing/tools/adb.html#commandsummary
Adb pull /mnt/sdcard c:\users\(you)\desktop
I believe or something like that. I honestly don't use adb too often.
if you boot into recovery (with adb reboot recovery) it should be volume down 6 times, then power, vol up twice then power and that should get you to mount the sdcard so you an just use windows gui to copy everything over instead of a command prompt

Got it! Thank you very much! For reference its /mnt/sdcard.
Sent from my LG-P999 using XDA App

Awesome man!
Glad to hear.

I am in the same situation but the phone is rooted and has a custom rom.

fapulous said:
I am in the same situation but the phone is rooted and has a custom rom.
Click to expand...
Click to collapse
If you can get adb to recognize the phone the command is adb pull /mnt/sdcard
Sent from my LG-P999 using XDA App

After having a really bad day at work I ended up putting my phone into a wall as hard as i could - the result: A destroyed screen
The instructions here work like a charm & I was able to copy the entire contents of the SD card over to my computer - adb pull /mnt/sdcard Ti Backup is a little outdated but I am not complaining. Thanks all!

studacris said:
if you boot into recovery (with adb reboot recovery) it should be volume down 6 times, then power, vol up twice then power and that should get you to mount the sdcard so you an just use windows gui to copy everything over instead of a command prompt
Click to expand...
Click to collapse
THANK YOU! Worked like a charm.

[SOLVED] Some Help please? A Strange Brick...

So last night, I was beta testing a ROM. After playing with it for a while, decided to go back to my previous setup and work on something. I rebooted into TWRP, wiped my Dalvik Cache, data, cache, and system partitions, and tried to flash the nandroid of Kinology I had been running before testing the beta ROM. I rebooted... only to discover that my Kindle wouldn't boot past the 2nd bootloader.
I thought, "okay, no biggie, I can fix this. I tried wiping and then flashing a couple of other ROMs I had on my SD card. Didn't work. I rebooted the bootloader and flashed a trio of images I had on my hard drive via fastboot. Nope. I tried sideloading CM10.2. Still nope. I tried mounting USB and pushing a ROM to my SD card and flashing from there. Again, no (anyone noticing a pattern?).
No matter what I do, I can't flash anything or get anything to transfer over to my device.
Help!!

Why do I get the feeling this has something to do with the boot image... Does it ever boot to the point you can logcat? Also I thought I read about some issues restoring nandroid's after the system was using selinux, though I haven't experienced this with mine. You tried cm 11? I know it had full selinux support. If you can't get the logcat to work I think there's a module that gets dumped that you can access in twrp over adb. And of all things to ask, if you flash the ROM in testing back does it still boot? If so that would make me think something weird is going on with the boot image. Also what version of twrp are you using?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Why do I get the feeling this has something to do with the boot image... Does it ever boot to the point you can logcat? Also I thought I read about some issues restoring nandroid's after the system was using selinux, though I haven't experienced this with mine. You tried cm 11? I know it had full selinux support. If you can't get the logcat to work I think there's a module that gets dumped that you can access in twrp over adb. And of all things to ask, if you flash the ROM in testing back does it still boot? If so that would make me think something weird is going on with the boot image. Also what version of twrp are you using?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for answering. "adb logcat" doesn't work. It only shows "-waiting for device-". I tried flashing CM11 this morning, but the install failed. I also tried re-flashing your ROM again this morning, but same result. I've got TWRP 2.6.0.0. I've been meaning to flash the latest one from @Hashcode, but it slips my mind every time I think of it.
Something weird: whenever I push anything to the device over ADB, I push it to the SD card. But when I run "ls /sdcard/" in ADB shell, there's nothing there (even though it says it has been successfully pushed).
EDIT: Okay, I flashed the latest version of TWRP (2.6.3.1). I flashed CM11, and it reported that the flash was sucessful. But when I rebooted... nope.

This is weird... So weird. I'm almost at a loss, have you tried flashing a boot.IMG via fastboot corresponding with whatever ROM you flashed? I know I keep saying I think it's this without any real proof but this is kinda bizarre and if no ROM's are working and all you see is the kindkle logo I would assume that the init.RC scripts never got passed the pvrsrvinit or somewhere around that, possibly even before that since adb isn't working when the device is on the logo. You using adb from windows or Linux?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Ph0enix_216 said:
No matter what I do, I can't flash anything or get anything to transfer over to my device. Help!!
Click to expand...
Click to collapse
After I read this, I decided to try and restore and everything restored just fine *whew*. What I do know is that when ever this situation has come up (and a few people have stated they had this problem) only a complete factory restore fixed the problem. You're gonna have to break out the fastboot cord.

stunts513 said:
This is weird... So weird. I'm almost at a loss, have you tried flashing a boot.IMG via fastboot corresponding with whatever ROM you flashed? I know I keep saying I think it's this without any real proof but this is kinda bizarre and if no ROM's are working and all you see is the kindkle logo I would assume that the init.RC scripts never got passed the pvrsrvinit or somewhere around that, possibly even before that since adb isn't working when the device is on the logo. You using adb from windows or Linux?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
The init.RC scripts are still there, no matter how much I wipe in TWRP. I can see them using TWRPs file explorer. I haven't tried flashing the boot.img, I will try that. As for ADB, I'm using it on Windows 8, of all things.

LinearEquation said:
After I read this, I decided to try and restore and everything restored just fine *whew*. What I do know is that when ever this situation has come up (and a few people have stated they had this problem) only a complete factory restore fixed the problem. You're gonna have to break out the fastboot cord.
Click to expand...
Click to collapse
As I said before, I tried flashing two different sets of images via fastboot. Thanks for the response though. What all did you do in your restore process?

UPDATE
Okay, I tried re-installing CM10.2, and then flashing the boot.img from it via fastboot. Still no dice.
Is there any hope of recovering from this? It's been longer than a year, so I don't think Amazon will simply switch it out under warranty.

Agh, I was going to ask hashcode about it on the irc earlier and I forgot about it because my friend asked me to fix his pc...
Also remind me to slap this phone's spell check. It took me way longer to write the previous statement than it should have.
Edit: he's still in there but I think he's afk right now.
Sent from my LG-P769 using xda app-developers app

Ph0enix_216 said:
As I said before, I tried flashing two different sets of images via fastboot. Thanks for the response though. What all did you do in your restore process?
Click to expand...
Click to collapse
I just wiped and then restore 4.3 PA nandroid. That was another thin I forgot to mention.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
---------- Post added at 04:18 AM ---------- Previous post was at 04:14 AM ----------
LinearEquation said:
I just wiped and then restore 4.3 PA nandroid. That was another thin I forgot to mention.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was gonna suggest to flash CM10.2 first and then move up to CM11 because that was the route those with this problem had to go (4.3 then 4.4.) Restoring CM11 right off the bat did not seem to work for some reason. That's why I keep a 4.3 nandroid in TWRP, for just such a case. But I see you tried that.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

LinearEquation said:
I just wiped and then restore 4.3 PA nandroid. That was another thin I forgot to mention.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's weird, because I wiped then tried to restore my Kinology nandroid. Am I looking at an irreparable brick, or do I want to look into investing in a new tablet?

Wait until Monday, think you might get more info on a weekday... I have a theory of something that might fix your kindle but it could potentially hard brick it as well so I don't want to explain it yet until it's a last resort.
Edit: just talked to hashcode, he says to "adb pull /sdcard/ ." your sdcard and wipe internal storage, he also said because of kinology kernel not having selinux that if you want to use it you will have to downgrade twrp first and wipe everything again, you might find it easier to do it after flashing cm11 first. So basically back up the sdcard and wipe everything, check off everything including internal storage then push a Rom and flash it.
Sent from my LG-P769 using xda app-developers app

stunts513 said:
Wait until Monday, think you might get more info on a weekday... I have a theory of something that might fix your kindle but it could potentially hard brick it as well so I don't want to explain it yet until it's a last resort.
Edit: just talked to hashcode, he says to "adb pull /sdcard/ ." your sdcard and wipe internal storage, he also said because of kinology kernel not having selinux that if you want to use it you will have to downgrade twrp first and wipe everything again, you might find it easier to do it after flashing cm11 first. So basically back up the sdcard and wipe everything, check off everything including internal storage then push a Rom and flash it.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Checked everything. Wiped it all. Pushed a ROM via ADB. Not working.
I did some exploring with TWRP's built in file explorer. Despite wiping internal storage, I can still see some things I had on there previously. At the root of my device, however, I can also see this:
Code:
boot
cache
data
dev
efs
etc
license
proc
recovery
res
root
sbin
sdcard
supersu
sys
system
tmp
vendor
default.prop
file_contevts
fstab.bowser
fstab.goldfish
init
init.rc
property_contexts
seapp contexts
sepolicy
ueventd.bowser.rc
ueventd.goldfish.rc
ueventd.rc
I may be mistaken, but isn't that some of Firefox OS's stuff? The init.rc files you were talking about? It all may just mean nothing. Also, all my SD contents seem to be preserved in "/data/media/". I tried flashing CM11 from there as well. The flash was successful, but at boot... nada.
Still, thank you all for trying

Umm sorry I'm a little late to the party... Or funeral(if we cant fix your kindle) I was testing stunt's FireFox OS too and after testing I flashed back to my CM11 back up just fine, why not use the system image restore tool in the development section (minimize error, the tool is 99.9% fool proof) bailed me out multiple times when I thought my kindle was a goner(i know you manually flashed images. But why not try a tool?), and I have a theory... Stunt PMd me instructions on how to get the kindle to pick up/read the SD card I didn't try implementing the code because I'm not that techy but did you try it? What if the solution messed with your internal SD card since Firefox OS and Android Have their differences? Or something went wrong will modifying the commands stunts gave you?
And no...I'm not trying to insult Stunt's work or defame it, nothing is perfect and anything is possible so sorry if my response seems a bit disrespectful to the devs work.
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app

I still think this has something to do with selinux... I would know more if you had a serial hookup to the kindles motherboard but I don't even have that, if I had some kernel output it would be useful... Those files you saw that I mentioned aren't Firefox OS specific, they are Linux specific, they are going to always appear there because they are loaded from the initial ram disk in the boot.IMG, since android uses a Linux kernel you have init.rc files and such. Some of those directories are from recovery, the folders that should know appear empty I think are /data, /cache, /system and I can't remember the rest offhand. I will have to ask hashcode about this more tomorrow. I can think of something you might do from fastboot that might fix this but I don't know the specifics and it might wipe the boot loader, which wouldn't necessarily be bad as long as you reflash it before rebooting, but I'd like to avoid my idea because it seems rather risky, anyways I will ask about this tomorrow, so don't look into my concept idea....
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

when you said your sdcard contents are preserved, did you mean even after wiping internal storage that the sdcard's contents were still there?

stunts513 said:
when you said your sdcard contents are preserved, did you mean even after wiping internal storage that the sdcard's contents were still there?
Click to expand...
Click to collapse
Correct. Not only are they still there, but I can't seem to add anything to it. Pushing via ADB is successful on the PC end, but if I check the SD card, no change. Also, everything I had before the brick on my SD card is still in "/data/app", if that tells you anything.
Thanks for taking time to they and help me
>>>Sent from my ZTE Valet Z665C<<<

Ph0enix_216 said:
Correct. Not only are they still there, but I can't seem to add anything to it. Pushing via ADB is successful on the PC end, but if I check the SD card, no change. Also, everything I had before the brick on my SD card is still in "/data/app", if that tells you anything.
Thanks for taking time to they and help me
>>>Sent from my ZTE Valet Z665C<<<
Click to expand...
Click to collapse
ok um at this point hashcoed is helping me out and i tink i can fix it but it will be easier if i can msg you on skype or in the irc, whatever works best for ya, because this will involve some trial an error over an adb shell... i would try it on my own but it will involve me backing up quite a bit of data and you already have done that so i thought this might be easier than me formatting my own in the process...
Edit: Ok actaully try this first and see what happens, boot into recovery and run this in an adb shell
Code:
umount /data
mke2fs -T ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata
that should actually format the userdata partition and hopefully fix this. though make sure that the unmount worked first, you don't want to try to format a partition while its mounted.
2nd edit:actually i'm a moron, you don't even need to umount /data, just uncheck it in the mount section, you can tell i'm way to used to normal linux... always a good idea to run mount and double check its not on the list but it shouldn't be.

SUCESS!!!
stunts513 said:
ok um at this point hashcoed is helping me out and i tink i can fix it but it will be easier if i can msg you on skype or in the irc, whatever works best for ya, because this will involve some trial an error over an adb shell... i would try it on my own but it will involve me backing up quite a bit of data and you already have done that so i thought this might be easier than me formatting my own in the process...
Edit: Ok actaully try this first and see what happens, boot into recovery and run this in an adb shell
Code:
umount /data
mke2fs -T ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata
that should actually format the userdata partition and hopefully fix this. though make sure that the unmount worked first, you don't want to try to format a partition while its mounted.
2nd edit:actually i'm a moron, you don't even need to umount /data, just uncheck it in the mount section, you can tell i'm way to used to normal linux... always a good idea to run mount and double check its not on the list but it shouldn't be.
Click to expand...
Click to collapse
SUCESS!!! I did what you said and formated the data partition, and I was able to successfully push CM11 to my Kindle. I flashed it, it reported the flash as successful, and I rebooted.. I was greeted by new CM11 boot animation (right now, it's one of the most beautiful things I've ever seen.
Thank you to everyone who responded to this thread. It's nice to know that there are people nice enough out there to take the time and help someone in need.
Some questions though:
1.) With this SELinux or whatever, can I still switch ROMs as easily as I did before? Or am I now limited to CM11 and such?
2.) What exactly happened? I've never had this happen before, where my /data partition derped out and TWRP wouldn't flash anything.

I'm not to familiar with how selinux works but from we hat I remember I think it was something like this. You had a recovery that I think may have supported selinux but I'm not positive about that. The kinology ROM you had on there had no selinux support in the kernel. My ROM has some selinux support in it since I based it on 4.3, and I have no idea what happened that messed it up after that, all I can tell based on what you had to do to fix it is that the xattributes for selinux were not getting cleared off the partition and for some reason the ROM's that could handle selinux didn't seem to like it either. If you want to run kinology again you may need to downgrade twrp so you can reformat the partition again so it reformats without selinux but I'm a bit confused on this myself, this isn't my best field in computers.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Wiped everything. Please help

So like an idiot I wiped all data and system on my n6 and do t know what to do. There is no os to reboot to. Twrp. I downloaded a Rom and gapps to try and move it to the storage but it won't let me. Any ideas?
Sent from my HTC One using XDA Free mobile app

whozilla said:
So like an idiot I wiped all data and system on my n6 and do t know what to do. There is no os to reboot to. Twrp. I downloaded a Rom and gapps to try and move it to the storage but it won't let me. Any ideas?
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
I believe you will have to use "ADB push" to move the files to your phone.

Use adb to push to internal....boot to twrp and flash the rom. ..simple

If your nexus drivers are properly installed in your Windows, you can get storage even in twrp, just download any Rom, move it to storage and flash it, but you've to hav drivers installed to get storage in recovery

Could use the toolkit to download a factory image to push to it also.

Another thought as well, if he only wiped, hook to PC and his internal storage may show up as well, won't need to push thru ADB but could copy/paste the ROM to the unit.
I did the same thing to my old GNex getting it ready for my daughter, had loaded up a ROM, but in recovery thought I may as well wipe it all out... Doh!
but hooked to my PC, the internal was seen and given adrive letter, so I cut/paste the files needed and reflashed in recovery, all good.

Don't need adb. TWRP has an "enable MTP" button, so you can drag and drop just like in android

I was having trouble using adb. Huge cluster of mistakes I made. What solved it was using the toolkit to unroot and go back to stock.
Sent from my Nexus 6 using XDA Free mobile app

rootSU said:
Don't need adb. TWRP has an "enable MTP" button, so you can drag and drop just like in android
Click to expand...
Click to collapse
I totally forgot that, root to the rescue, even though he seemed to have solved it.

You don't have to do adb push when you are in custom recovery and plug your phone into a computer your phone comes up on the folder section down load a ROM and drag and and drop
---------- Post added at 02:22 AM ---------- Previous post was at 02:21 AM ----------
rootSU said:
Don't need adb. TWRP has an "enable MTP" button, so you can drag and drop just like in android
Click to expand...
Click to collapse
Best me to it