Related
Code:
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: Unable to satisfy all constraints on the partition.
Anyone seen this issue? I have tried unmounting to make sure nothing was mounted both in CWM and by force:
Code:
umount /data
umount /cache
Thanks for trying.
I thought I explained it for you in the PM. mmcblk0 is not a normal disk device at all (it's a NAND device, quite different), it does not have a "standard" partition table (in fact it does not have a partition table at all, the partitioning is done internally in the kernel), so parted doesn't know how to work with that.
ravilov said:
I thought I explained it for you in the PM. mmcblk0 is not a normal disk device at all (it's a NAND device, quite different), it does not have a "standard" partition table (in fact it does not have a partition table at all, the partitioning is done internally in the kernel), so parted doesn't know how to work with that.
Click to expand...
Click to collapse
My apologies, I logged in today and didnt see any response.
The concern I have is that others have ran the above command and did not have the response I got. Oh well.
My data partition is locked somehow in a read only state. Nothing I do causes it to wipe, I thought parted could help but it appears not.
ravilov said:
I thought I explained it for you in the PM. mmcblk0 is not a normal disk device at all (it's a NAND device, quite different), it does not have a "standard" partition table (in fact it does not have a partition table at all, the partitioning is done internally in the kernel), so parted doesn't know how to work with that.
Click to expand...
Click to collapse
Ah, thanks for that. Is there any way to access/read the partition table handled in the kernel? Not necessarily with parted, but through terminal some how?
The kernel dev team (namely Krystian) has been able to work something out regarding this but nothing has been published yet.
According to this thread
http://forum.xda-developers.com/showthread.php?t=1959445
Parted using the print or p command should bring back this
Code:
/ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Disk /dev/block/mmcblk0: 31268536320B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
-------------------------------------------------------------------------------
Number Start End Size FS-Type Name Flags
-------------------------------------------------------------------------------
1 4194304B 67108863B 62914560B modem
2 67108864B 67239935B 131072B sbl1
3 67239936B 67502079B 262144B sbl2
4 67502080B 68026367B 524288B sbl3
5 68026368B 70123519B 2097152B aboot
6 70123520B 70647807B 524288B rpm
7 70647808B 81133567B 10485760B boot
8 81133568B 81657855B 524288B tz
9 81657856B 82182143B 524288B pad
10 82182144B 92667903B 10485760B param
11 92667904B 106954751B 14286848B ext4 efs
12 106954752B 110100479B 3145728B modemst1
13 110100480B 113246207B 3145728B modemst2
14 113246208B 1686110207B 1572864000B ext4 system
15 1686110208B 30337400831B 28651290624B ext4 userdata
16 30337400832B 30345789439B 8388608B ext4 persist
17 30345789440B 31226593279B 880803840B ext4 cache
18 31226593280B 31237079039B 10485760B recovery
19 31237079040B 31247564799B 10485760B fota
20 31247564800B 31253856255B 6291456B backup
21 31253856256B 31257001983B 3145728B fsg
22 31257001984B 31257010175B 8192B ssd
23 31257010176B 31262253055B 5242880B grow
I am extremely interested in this as I need to find the boot partition for my device... But I am having the same issue as the OP, with the same response from parted
atmu5fear said:
According to this thread
http://forum.xda-developers.com/showthread.php?t=1959445
Parted using the print or p command should bring back this
Code:
/ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Disk /dev/block/mmcblk0: 31268536320B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
-------------------------------------------------------------------------------
Number Start End Size FS-Type Name Flags
-------------------------------------------------------------------------------
1 4194304B 67108863B 62914560B modem
2 67108864B 67239935B 131072B sbl1
3 67239936B 67502079B 262144B sbl2
4 67502080B 68026367B 524288B sbl3
5 68026368B 70123519B 2097152B aboot
6 70123520B 70647807B 524288B rpm
7 70647808B 81133567B 10485760B boot
8 81133568B 81657855B 524288B tz
9 81657856B 82182143B 524288B pad
10 82182144B 92667903B 10485760B param
11 92667904B 106954751B 14286848B ext4 efs
12 106954752B 110100479B 3145728B modemst1
13 110100480B 113246207B 3145728B modemst2
14 113246208B 1686110207B 1572864000B ext4 system
15 1686110208B 30337400831B 28651290624B ext4 userdata
16 30337400832B 30345789439B 8388608B ext4 persist
17 30345789440B 31226593279B 880803840B ext4 cache
18 31226593280B 31237079039B 10485760B recovery
19 31237079040B 31247564799B 10485760B fota
20 31247564800B 31253856255B 6291456B backup
21 31253856256B 31257001983B 3145728B fsg
22 31257001984B 31257010175B 8192B ssd
23 31257010176B 31262253055B 5242880B grow
I am extremely interested in this as I need to find the boot partition for my device... But I am having the same issue as the OP, with the same response from parted
Click to expand...
Click to collapse
You need to find the boot partition, but you can't look at the chart you provided and find the word boot?
palmbeach05 said:
You need to find the boot partition, but you can't look at the chart you provided and find the word boot?
Click to expand...
Click to collapse
Obviously... except that's not from my phone. That's an example as quoted from the thread I linked to, as to what SHOULD come back from the parted print command. My phone returns the exact same error message as the OP of this thread... So thanks for the condescending reply, but if you actually read my comment, well, it's pretty clear. Sorry to sound like an ass, but I've been looking into this for days, thanks, don't need critical comments from someone who doesn't actually read the post...
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
First of all, if all you need is to find the boot partition, then you clearly do NOT have the same issue as the OP. Read his second post to find out why.
Second, why are you messing with parted anyway? What's wrong with this?
ravilov said:
First of all, if all you need is to find the boot partition, then you clearly do NOT have the same issue as the OP. Read his second post to find out why.
Second, why are you messing with parted anyway? What's wrong with this?
Click to expand...
Click to collapse
i agree with @ravilov. And why are you messing with parted to get the boot.img, when you can open a ROM package or a nandroid backup and retrieve said boot.img?
Sent from my MB860 using xda app-developers app
ravilov said:
First of all, if all you need is to find the boot partition, then you clearly do NOT have the same issue as the OP. Read his second post to find out why.
Second, why are you messing with parted anyway? What's wrong with this?
Click to expand...
Click to collapse
First of all, remind me of the title of this thread? If the OP is typing a command in parted and it's returning an error message, and I am also typing that same command and getting the same error message, that clearly we ARE having same issue. The second post is nothing more than his reason for using parted in the first place. So yes, his reason may be different than mine, but the issue is the same. Secondly, I ended up on this thread by searching the error message parted turned in Google. I do not have a Motorola Atrix, therefore your partition table that you spent so much time researching for the thread the link you provided is useless to me. That's what's wrong with it. After trying every command I could find to give me a partition table, with no success identifying the boot partition, I decided to try with parted. Which, by the way, returns a very clear table on my t989, just not my s730m which gives me the error message. So I guess your theory about mmcblk0 not having a partition table pretty much goes out the window. Thirdly, I don't recall saying I needed a boot.img, I said I needed to know the boot partition. Big difference, especially when one is writing a updater-script in which one needs to know the mmcblk0p_ to write the boot.img to. This info may be easy to find for a lot of phones including your Motorola, but not so much for phones that don't have a single flashable ROM out them, custom OR stock. There is one on the works by a member here, and myself for the s730m, but nothing currently available and thus needing to know the boot partition to write to, well, seems a bit important... I was able to find the info, which was more of a stumble across after using adb to pull the recovery.log from the device and viewing it on my laptop. Haven't pulled a recovery log for some time, totally forgot that all of the partition info is available on the first lines the log. I can honestly say that you two are the first people I've encountered on xda who have been rather ignorant, condescending, and critical instead of offering any sort of help or suggestions. Do I have your permission to continue my research and/or seek help and guidance when I get stuck or is that breaking some sort of unwritten rule? Not all of us are born knowing everything like the two of you obviously were, or at least think you were. Is that enough reason as to why I was "messing around with parted" and needed to know my boot partition (not needing to extract a boot.img), or would you like me to elaborate with every command I used, every Google search I performed, and every thread I read regards to the matter. Thanks again for pretending to know everything and criticize others who are simply out to learn and further their android knowledge though, that's great you guys...
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
atmu5fear said:
I do not have a Motorola Atrix, therefore your partition table that you spent so much time researching for the thread the link you provided is useless to me.
Click to expand...
Click to collapse
This fact alone means your question doesn't even belong here. The forum is organized into specific subforums and boards for a very good reason. No reason to disrespect that just because you happened to have stumbled across this thread through some search on Google. If your question does not pertain specifically to Atrix 4G, then you need to ask it elsewhere.
ravilov said:
This fact alone means your question doesn't even belong here. The forum is organized into subforums and boards for a reason. If your question does not pertain to this specific device, then you need to ask it elsewhere.
Click to expand...
Click to collapse
Like I said I searched "parted unable to satisfy constraints" on Google, it brought me here. And since this error message has nothing to do with the Atrix itself, but with parted and any device that runs parted (potentially all android phones), I feel it's perfectly acceptable post here. The OP's question pertains to parted, not the specific device. Since there was already a topic with the question that I was looking for an answer to, why would I ask it elsewhere, further cluttering the forums with unnecessary threads?
Also the s730m does not have a device specific sub forum, I don't have much of and option but to search for the same issues with other devices.
Why do you feel the need to troll threads and criticize people with legitimate questions? These forums are here for people to ask questions and help each other out, not to troll and criticize. If you don't have any help to offer someone, why criticize the question?
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
---------- Post added at 06:20 AM ---------- Previous post was at 06:04 AM ----------
For anyone else looking for their partition table and getting this error message.
In adb type:
adb pull /tmp/recovery.log
This will pull the log file from your device (Motorola, Samsung, Sony, etc, anything with a custom recovery) and will show you exactly what mmcblk0p_ for each partition is; boot, system, data, cache, etc.
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Like I said, however you managed to get here is irrelevant. This is a board for Atrix 4G ONLY, questions about other devices have no business here even if the topic doesn't seem device-specific. I'm sorry if your device doesn't have its own board but that doesn't give you any right to try and hijack someone else's thread with inquiries about a completely different situation (trust me, when it comes to things such as partition tables, just the fact you have an entirely different device makes a world of difference).
To reiterate - your question does not belong here. There is the general Android section, you could've tried there instead.
ravilov said:
Like I said, however you managed to get here is irrelevant. This is a board for Atrix 4G ONLY, questions about other devices have no business here even if the topic doesn't seem device-specific. I'm sorry if your device doesn't have its own board but that doesn't give you any right to try and hijack someone else's thread with inquiries about a completely different situation (trust me, when it comes to things such as partition tables, just the fact you have an entirely different device makes a world of difference).
To reiterate - your question does not belong here. There is the general Android section, you could've tried there instead.
Click to expand...
Click to collapse
Ya... anyway... To the OP or to anyone else who might end up here via Google, use the aforementioned adb command. If using Windows, type:
Code:
adb pull /tmp/recovery.log C:\Users\YourName\Desktop
I should mention you need to be in recovery when using this command. So reboot your device into recovery, then use the pull command to pull the recovery log.
This will pull the recovery log to your desktop, open it with notepad++ (you can use notepad but it's not at all organized) and the first dozen or so lines will tell you exactly what you need to know about your partition table. Hope it helps!
And no not really "like I said" in this case, being you didn't already say "how you got here is irrelevant". But regardless, sorry that you think you own the thread and the forum for the atrix and feel you have some sort of authority here over other people. (Trust me when it comes to things such as policing this forum and having authority, just the fact that you think you know everything doesn't actually mean that you do). I wasn't hijacking the thread, I was explaining that the parted command SHOULD bring back a partition table. In fact even the OP says it works for others, just not him.
To reiterate, I didn't ask a question, I made a statement, and then through my own research/tinkering, provided an answer to the OP's partition table identifying issue, and to anyone else who may view this thread with the same or similar issue, which is more than you can say about what you've contributed to this thread. So have a good one, enjoy trolling and criticizing others who are only trying to learn, and policing threads you don't have authority over, the rest of us will continue to offer whatever assistance we can, regardless of whether or not a few trolls feel it's in the appropriate sub forum or not. Good night
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
atmu5fear said:
Ya... anyway... To the OP or to anyone else who might end up here via Google, use the aforementioned adb command. If using Windows, type:
Code:
adb pull /tmp/recovery.log C:\Users\YourName\Desktop
I should mention you need to be in recovery when using this command. So reboot your device into recovery, then use the pull command to pull the recovery log.
This will pull the recovery log to your desktop, open it with notepad++ (you can use notepad but it's not at all organized) and the first dozen or so lines will tell you exactly what you need to know about your partition table. Hope it helps!
And no not really "like I said" in this case, being you didn't already say "how you got here is irrelevant". But regardless, sorry that you think you own the thread and the forum for the atrix and feel you have some sort of authority here over other people. (Trust me when it comes to things such as policing this forum and having authority, just the fact that you think you know everything doesn't actually mean that you do). I wasn't hijacking the thread, I was explaining that the parted command SHOULD bring back a partition table. In fact even the OP says it works for others, just not him.
To reiterate, I didn't ask a question, I made a statement, and then through my own research/tinkering, provided an answer to the OP's partition table identifying issue, and to anyone else who may view this thread with the same or similar issue, which is more than you can say about what you've contributed to this thread. So have a good one, enjoy trolling and criticizing others who are only trying to learn, and policing threads you don't have authority over, the rest of us will continue to offer whatever assistance we can, regardless of whether or not a few trolls feel it's in the appropriate sub forum or not. Good night
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have to say, @ravilov does have a point here, this is the section for the Atrix 4G, however, I am happy that you searched for the error, before opening a new thread
Now, if I understand you correctly, all you need is a partition table, right?
So run the following commands:
Code:
adb shell
ls -a | grep fstab
exit
adb pull /<result_of_the_ls_command> ~/<result_of_the_ls_command>
If you happen to have more issues about this, feel free to PM me, or open a thread in your device's section, but let's stop the discussions now
Thanks
Ive been searching for a while for a forum that explains how to root the new nabi 24" BIG TAB HD. trying to install clockworkmod on the tablet.. if anyone can point me in the direction of what I'm looking for that would be greatly appreciated.
jmmac said:
Ive been searching for a while for a forum that explains how to root the new nabi 24" BIG TAB HD. trying to install clockworkmod on the tablet.. if anyone can point me in the direction of what I'm looking for that would be greatly appreciated.
Click to expand...
Click to collapse
As far as I know nobody has talked about it on here except you.
Depending on what kernel patches or android security fixes it has you might be able to try some root programs. There certainly will not be a clockworkmod or TWRP for it yet.
If none of the root methods work it might be possible to use the Dreamtab TWRP.(http://forum.xda-developers.com/android/development/recovery-twrp-2-7-1-0-nabi-dreamtab-hd8-t2813917) If it's like the previous Nabi tablets the bootloader will be unlocked, and you could try booting from that TWRP. The screen and the landscape/portrait might be messed up but it could work. In the last software update to the dreamtab they locked the bootloader so the BIG TAB might be as well. It could be unlocked by
Code:
fastboot oem unlock
^^^ This will ERASE all the data on the tablet.
If you want to try the TWRP way let me know but of course there are dangers involved.
If you try it alone be aware that if you try the dreamtab TWRP load it by
Code:
fastboot boot recovery.img
and NOT
Code:
[STRIKE]fastboot flash recovery recovery.img[/STRIKE]
or you will overwrite your current stock recovery.
also interested! any further info would be great!
schlager said:
also interested! any further info would be great!
Click to expand...
Click to collapse
Do either of you have one? Or just asking?
aicjofs said:
Do either of you have one? Or just asking?
Click to expand...
Click to collapse
i plan to buy one in the next few weeks. mainly need it so i can have two sheets of music in front of me. if there is another tablet that can do that, let me know.
aic, I got one for the kids for Xmas. The Nabi2's have been good but wont last forever, I liked the multi user option and big ass screen on the big tab. Well see how it works out! Once they open and spend time with it I'll be interested in rooting for adaway and such.
codest3r said:
aic, I got one for the kids for Xmas. The Nabi2's have been good but wont last forever, I liked the multi user option and big ass screen on the big tab. Well see how it works out! Once they open and spend time with it I'll be interested in rooting for adaway and such.
Click to expand...
Click to collapse
I have no idea about the BigTab but if it's like the DreamTab it will update when you boot it up. It's hard to get around it. If it does it will likely patch a lot of the more recent exploits that can gain you root. There is the option to try the dream tab recovery like I said above but be really careful with that.
Also one of the Dreamtab updates locked the bootloader. This isn't a big deal as it was unlockable via fastboot. However, if you let the kiddoz, or you start installing a whole bunch of stuff, when you unlock the bootloader you will wipe the tablet back to factory(normal behavior). Best to unlock it as soon as possible.
I own the big tab 20" was able to root using http://forum.xda-developers.com/showthread.php?t=2473747
I did have to unlock the bootloader and tried booting the dream tab recovery from fastboot no dice there so wasn't gonna risk flashing it.
The process took about 20 mins maybe less fully automated it froze at some point so I reset the big tab and tried again at which point kingo program told me I was already rooted download SU was able to update the binary's normal method and been good to go since. Word of warning it does preform a factory reset when you unlock the bootloader so be prepared for that.
I have been working on compiling CWM for the Nabi big tab 20" I'm close but I can't seem to figure out the path for the sdcard currently the recovery boots but can't back anything up with out the correct path entered into the recovery.fstab. This particular tablet does not have a real sdcard nor does it have a slot for an external one. Any help on this would be appreciated when I get it sorted out will add a link for the recovery.
this is what I currently have in my recovery.fstab.
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,data=writeback,nodelalloc,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MDA /metadata emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,data=ordered,noauto_da_alloc,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/TRD /app ext4 defaults wait
/dev/block/sda1 /sdcard vfat defaults voldmanaged=sdcard:auto
When I boot into recovery and attempt to perform a backup to sdcard I get E:Can't mount backup path.
You could download and try a rooting apk like towelroot framaroot or z4root if it has a low android firmware like 2.3.6 or something but only for z4root
I already got it rooted using Kingo root, these tablets are new on the market running kitkat 4.4.4, the end goal I am trying to achieve is making a custom rom but a neassacery first step is to get a working custom recovery so I can backup my stock rom just in case I blow up my tablet =)
lmortal said:
I have been working on compiling CWM for the Nabi big tab 20" I'm close but I can't seem to figure out the path for the sdcard currently the recovery boots but can't back anything up with out the correct path entered into the recovery.fstab. This particular tablet does not have a real sdcard nor does it have a slot for an external one. Any help on this would be appreciated when I get it sorted out will add a link for the recovery.
this is what I currently have in my recovery.fstab.
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,data=writeback,nodelalloc,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MDA /metadata emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,data=ordered,noauto_da_alloc,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/TRD /app ext4 defaults wait
/dev/block/sda1 /sdcard vfat defaults voldmanaged=sdcard:auto
When I boot into recovery and attempt to perform a backup to sdcard I get E:Can't mount backup path.
Click to expand...
Click to collapse
Did you get that from pulling the stock recovery and extracting the recovery.fstab from the ramdisk?
The internal is likely on /data/media, or data/media/0 if it's like all the other Nabi's. Pretty sure /dev/block/sda1 to mount sdcard is not going to work. I'm not as knowledgeable at CWM as I enjoy TWRP so I'm not sure if there is a boardconfig.mk change you can do or if you need to symlink it in an init.rc file.
aicjofs said:
Did you get that from pulling the stock recovery and extracting the recovery.fstab from the ramdisk?
The internal is likely on /data/media, or data/media/0 if it's like all the other Nabi's. Pretty sure /dev/block/sda1 to mount sdcard is not going to work. I'm not as knowledgeable at CWM as I enjoy TWRP so I'm not sure if there is a boardconfig.mk change you can do or if you need to symlink it in an init.rc file.
Click to expand...
Click to collapse
There was something else there originaly but it didn't work either so I ended up using the following from cat /proc/mounts:
/dev/fuse/mnt/shell/emulated /sdcard fuse rw,nosuid,nodev,realtime,user_id=1023,group_id=1023,default_permisions,allow_other nonremovable
Using the above line in the recovery.fstab allowed cwm to see the sdcard but was still unable to mount it. I have been playing around with different things but I am fairly new to this so my knowledge is limited.
lmortal said:
There was something else there originaly but it didn't work either so I ended up using the following from cat /proc/mounts:
/dev/fuse/mnt/shell/emulated /sdcard fuse rw,nosuid,nodev,realtime,user_id=1023,group_id=1023,default_permisions,allow_other nonremovable
Using the above line in the recovery.fstab allowed cwm to see the sdcard but was still unable to mount it. I have been playing around with different things but I am fairly new to this so my knowledge is limited.
Click to expand...
Click to collapse
I'm not really sure without seeing any of your code(device tree), finished recovery or any of the stock recovery.
I haven't made CWM in so long. Something like?
/dev/null /sdcard datamedia defaults recoveryonly
dd the mmcblock0pX for the recovery and boot and we can make something work. How much space is the recovery partition?
aicjofs said:
I'm not really sure without seeing any of your code(device tree), finished recovery or any of the stock recovery.
I haven't made CWM in so long. Something like?
/dev/null /sdcard datamedia defaults recoveryonly
dd the mmcblock0pX for the recovery and boot and we can make something work. How much space is the recovery partition?
Click to expand...
Click to collapse
I sent you a pm with a drop box link with my files in the mean time gonna try compiling with your suggestion and see what happens.
---------- Post added at 04:17 PM ---------- Previous post was at 03:36 PM ----------
I tried compiling with:
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
/dev/null /sdcard fuse datamedia,recoveryonly defaults
It compiled successfully and I was able to flash it, the sdcard showed up in the mount menu but was not mountable still.
---------- Post added at 05:10 PM ---------- Previous post was at 04:17 PM ----------
Okay so my latest build using:
/dev/block/sda1 sdcard fuse defaults nonremovable
Allowed backup to the sdcard of everything with the exception of /data got "Error while making a backup image of /data!"
Also still unable to mount sdcard under the mounts and storage menu.
I believe the reason for the error while backing up data was due to available space when I restarted the tablet there was only 99.59MB available and I think the data would have needed more space then that.
I kept running into problems with CWM recovery but with the help of aicjofs I was able to compile a working TWRP with usb drive support, I don't yet have enough post to make an outside link so if some one can pm me I can give the link to be posted here with the recovery I made.
Working TWRP 2.8.1.0 for Nabi BigTab 20
Here is a TWRP recovery 2.8.1.0 for the Nabi BigTab 20" model
TWRP 2.8.1.0 for NV20A(BigTab20)
Built by @lmortal. We spent a lot of our Sunday sorting all the issue so click the thanks button for Imortal in the post above this one!
aicjofs said:
Here is a TWRP recovery 2.8.1.0 for the Nabi BigTab 20" model
TWRP 2.8.1.0 for NV20A(BigTab20)
Built by @lmortal. We spent a lot of our Sunday sorting all the issue so click the thanks button for Imortal in the post above this one!
Click to expand...
Click to collapse
Fixed an error where /addon was not mounting. re uploaded recovery image to the above link.
I can't unlock my bootloader.
lmortal said:
I own the big tab 20" was able to root using http://forum.xda-developers.com/showthread.php?t=2473747
I did have to unlock the bootloader and tried booting the dream tab recovery from fastboot no dice there so wasn't gonna risk flashing it.
The process took about 20 mins maybe less fully automated it froze at some point so I reset the big tab and tried again at which point kingo program told me I was already rooted download SU was able to update the binary's normal method and been good to go since. Word of warning it does preform a factory reset when you unlock the bootloader so be prepared for that.
Click to expand...
Click to collapse
I've ben trying to root my Big Tab 24". You said you had to unlock the bootloader. I can't get it into bootlad mode or unlock the bootloader. I tried fastboot. I tried every button combination I could think of. (not too many considering it only has three physical buttons) I tried rooting it with Kingo without unlocking the bootloader. Nothing is working. Please help. What am I doing wrong or not doing right?
Fastboot is the boot loader make sure you have USB debugging enabled and connect the tab to a PC you can then use the command "adb reboot-bootloader" the command to unlock is "fastboot OEM unlock"
Hi! I am actually on a Samsung Galaxy S7 (Oreo 8.0) and i have it rooted w/ supersu 2.82. So i am trying to push gdb and gdbserver into /system/bin to later use with the terminal emulator.
I know the original problem is that /system is on read-only permissions but still when i change them i am still not able to push the files, this is what i've done so far:
Code:
adb shell
su
mount -o rw,remount /system
I check if it actually changes:
Code:
/dev/block/sda14 on /system type ext4 (rw,seclabel,noatime,norecovery)
then i exit the shell and try to push it via
Code:
adb push F:\test\gcoregdb\bin\gdb /system/bin/
but i get that the directory is still read only:
Code:
adb: error: failed to copy 'F:\test\gcoregdb\bin\gdb' to '/system/bin/gdb': remote couldn't create file: Read-only file system
F:\test\gcoregdb\bin\gdb: 0 files pushed. 34.4 MB/s (982920 bytes in 0.027s)
I am now wondering that if i exit the shell it automatically mounts /system back to RO. Thanks!
Delshire said:
Hi! I am actually on a Samsung Galaxy S7 (Oreo 8.0)....
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=3341138
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Ibuprophen said:
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=3341138
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
I will thanks for the info!
Delshire said:
I will thanks for the info!
Click to expand...
Click to collapse
Just keep in mind that, if you have a device that has a dedicated area on the forum, your best bet in locating/posting a resolution somewhere within it.
Also, most (unfortunately not all) of the big developments like TWRP, LineageOS, etc... Will have a dedicated thread that's specifically for instructions, support and member guidance.
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Hi there,
Adb is installed on the external disk and the device was rooted.
When I ran
Code:
adb pull /dev/block/mmcblk0p43 43.img
it returned
Code:
adb: error: remote object '/dev/block/mmcblk0p43' does not exist
mmcblk0p43 is the userdata partition of the device.
However,
Code:
adb shell "su -c cat /dev/block/mmcblk0p43" > 43.img
managed to pull mmcblk0p43 into the external disk.
Why did adb pull /dev/block/mmcblk0p43 43.img fail to pull userdata partition?
Thanks in advance.
we are running in circles...
adb pull /dev/block/... requires 'adb root'
aIecxs said:
@wenyendev the answer applies to all your following questions:
adbd cannot run as root in production builds. you have three options. 1) use adb root in TWRP recovery mode. 2) use insecure adbd daemon 3) use adb shell su shell instead. that's it.
Click to expand...
Click to collapse
aIecxs said:
we are running in circles...
adb pull /dev/block/... requires 'adb root'
Click to expand...
Click to collapse
Thanks for your reply.
But how could you expect me to know in advance that adb pull command requires adb root?
Because you already did...
We expect you can remember your previously working commands (you have written in post #1
in the quoted thread just to name example):
wenyendev said:
In addition
adb pull /dev/block/mmcblk0p43 43.img
It returned
adb: error: remote object '/dev/block/mmcblk0p43' does not exist
[...]
adb pull /dev/block/mmcblk0p43 43.img worked.
Click to expand...
Click to collapse
So how it comes that you're asking about exact same command just 7 days later again?
I have asked you to read old thread(s) for good reason.
aIecxs said:
please stop posting multiple threads.
please start reading answers in old threads.
Click to expand...
Click to collapse
While it may true, by opening new threads you may get more attention, please understand that threads on XDA are problem-focused, not question-based. This is not a Q&A site where each single minor issue belongs to new question (and even on Q&A sites they would just close your repeating questions as duplicates).
This is a forum where you should keep your problem in one single thread, avoid spreading pieces of information over multiple threads.
your issue is to recover deleted files from unencrypted rooted device. do not open new thread for every little step, ask your questions in the same thread that belongs to the (real) problem.
You will benefit when you're focused to keep every information in one thread. Other people trying to help will read the history of what has already been asked, and can offer better help.
kindly read this post
*** read before you post ***
I am not to be embroiled myself in heated arguments here.
Thanks again for your answer.
Hello. I've got a backup of
Code:
mmcblk0
It's probably encrypted, but I'm not sure. If it is, I do have the password, but then I wouldn't know where to insert it.
Is there any detailed tutorial on how to mount this file and work with it? If it's a Linux solution then preferably some guide or tutorial on how exactly to figure out this mess.
Thanks for any help.
RecoverVery said:
Hello. I've got a backup of
Code:
mmcblk0
It's probably encrypted, but I'm not sure. If it is, I do have the password, but then I wouldn't know where to insert it.
Is there any detailed tutorial on how to mount this file and work with it? If it's a Linux solution then preferably some guide or tutorial on how exactly to figure out this mess.
Thanks for any help.
Click to expand...
Click to collapse
Hello and good morning, @RecoverVery
Welcome to XDA! I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
[Read Before Posting]QUESTIONS DO NOT BELONG IN GENERAL
Hello Everybody, In order to attempt to keep this forum neat and tidy the moderation team is asking you to post your questions into the Questions and Answers (Q&A) forum and not into the General section. You can find the Q&A forum by clicking...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
I don't know what's the goal but you can extract the userdata partition from disk image with dd. the output of parted is in bytes, must divided by block size of your choice (bigger bs is faster)
Code:
parted mmcblk0 unit B print
dd if=mmcblk0 of=userdata.img skip=$off count=$len bs=$bs
another way is boot into TWRP from fastboot and pull the partition image directly.
Code:
fastboot devices
fastboot boot twrp-3.6.2_9-0-lavender.img
adb devices
adb pull /dev/block/bootdevice/by-name/userdata
Note: even if the partition image is mountable, the files are encrypted and manually decryption requires healthy keystore (not included in mmcblk0) and the device of origin itself.
Mate 9 - how to retrieve encrypted files from a broken system (userdata partition)
It's surprising that a bunch of people are interested in this article. But I have to say that some processes I mentioned in this article just happened to work. I don't necessarily understand why they work, which also means they probably cannot be...
forum.xda-developers.com