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
Guys i have bricked my phone by restoring MK1 efs backup created with efs professional tool. Few days ago i upgraded it with android 4.4 version with ota. I restored all partitions with efs pro tool except user data and system. Now it's in qhsusb_dload mode. I tried i9205 debrick image from this forum and it's not working. I do not know how to make debrick image form stock rom or any other way. Can anyone help me to fix this?
Thanks
Finally unbricked it with DarkAngel's help. Many thanks to him.
For unbrick your phone please read all post's by DarkAngel.
ashikrobi said:
Guys i have bricked my phone by restoring MK1 efs backup created with efs professional tool. Few days ago i upgraded it with android 4.4 version with ota. I restored all partitions with efs pro tool except user data and system. Now it's in qhsusb_dload mode. I tried i9205 debrick image from this forum and it's not working. I do not know how to make debrick image form stock rom or any other way. Can anyone help me to fix this?
Thanks
Click to expand...
Click to collapse
Have you tried to Odin the Official Firmware available for the L600? It can be done via Kies as well.
L600VPUBNE4
I tried odin and kies
DarkAngel said:
Have you tried to Odin the Official Firmware available for the L600? It can be done via Kies as well.
L600VPUBNE4
Click to expand...
Click to collapse
Yes i tried but in qhsusb_dload mode odin cannot find the phone. It cannot be powered up bro so how can kies detect it? Do you know how to fix this issue? Please help.
ashikrobi said:
Yes i tried but in qhsusb_dload mode odin cannot find the phone. It cannot be powered up bro so how can kies detect it? Do you know how to fix this issue? Please help.
Click to expand...
Click to collapse
Which version of Odin are you using?
odin 3.09 and 3.04
DarkAngel said:
Which version of Odin are you using?
Click to expand...
Click to collapse
I tried with these versions. They do not detect the device. If you have a working phone, you can make a debrick image for me. Please install busybox and a terminal emulator. Then issue this command from the terminal and you will get the debrick image in your sd card.
su
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128
Make sure you have SPH-L600 and android version 4.4 or the image will not work for me.
Please upload
Thanks
installed automatic upgrade stuck in boot loop
I have a Galaxy Mega SPH-L600 and i replaced the screen about a week ago and it was running fine opened it up 2 days ago and there was an update said needed to be done so hit ok and installed update it went to 100% and shut off and turned back on went to Samsung splash screen and shut off and turned back on did this for about a half hour so i tried to do the hard boot with power button,volume up and home button droid comes up and it says installing upgrade and goes back ito boot loop tried to hook up to laptop but can not get it to show up on my Windows 7 unit tried alot of stuff nothing works need some help from anyone that can point me in the right direction and thank you in advance
ashikrobi said:
I tried with these versions. They do not detect the device. If you have a working phone, you can make a debrick image for me. Please install busybox and a terminal emulator. Then issue this command from the terminal and you will get the debrick image in your sd card.
su
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128
Make sure you have SPH-L600 and android version 4.4 or the image will not work for me.
Please upload
Thanks
Click to expand...
Click to collapse
The only problem I have with the debrick image is if the 128mb will include my EFS information. I have to mount it to an extra SDcard I have and check it's content before I give it out or post it up for grabs.
Thank you for the how too but I am familiar with making a debrick image using TE. I have one made for all my devices although I haven't bothered checking to see what was exactly on this one being it is at 128mb ( as my SGS3 needs only just about half of the requested to work ) so I can provide the needed files.
Just to make things clear not all images being from other carriers will work on other devices of the same model. They may be partitioned a different way than the L600. Also you PM'd me that you tried to recover your EFS info using the created backup from one of a MK1. I wouldn't have tried that. You already upgraded to 4.4 and have the newest Knox bootloader which will not allow you to downgrade the Bootloader at all.
Thanks for the reply
DarkAngel said:
The only problem I have with the debrick image is if the 128mb will include my EFS information. I have to mount it to an extra SDcard I have and check it's content before I give it out or post it up for grabs.
Thank you for the how too but I am familiar with making a debrick image using TE. I have one made for all my devices although I haven't bothered checking to see what was exactly on this one being it is at 128mb ( as my SGS3 needs only just about half of the requested to work ) so I can provide the needed files.
Just to make things clear not all images being from other carriers will work on other devices of the same model. They may be partitioned a different way than the L600. Also you PM'd me that you tried to recover your EFS info using the created backup from one of a MK1. I wouldn't have tried that. You already upgraded to 4.4 and have the newest Knox bootloader which will not allow you to downgrade the Bootloader at all.
Click to expand...
Click to collapse
Thanks DarkAngel for your reply. My sprint mega was reprogrammed by myself with dfs tool. I didn't provisioned it with any commercial way. I just changed it to use uim to get operator information and it was working. But after i changed the rom to slimkat i lost esn from efs. That's why i tried to restore efs backup after 4.4 ota update.
I knew you are an expert or an android developer so i requested help from you. Because you have some threads that maybe possible by a developer. I am in a horrible situation. I took my phone the other day to my local jtag repair center an they failed to repair it. They said there is no support for this phone still now. Brother please help me to fix my phone. Thanks.
ashikrobi said:
Thanks DarkAngel for your reply. My sprint mega was reprogrammed by myself with dfs tool. I didn't provisioned it with any commercial way. I just changed it to use uim to get operator information and it was working. But after i changed the rom to slimkat i lost esn from efs. That's why i tried to restore efs backup after 4.4 ota update.
I knew you are an expert or an android developer so i requested help from you. Because you have some threads that maybe possible by a developer. I am in a horrible situation. I took my phone the other day to my local jtag repair center an they failed to repair it. They said there is no support for this phone still now. Brother please help me to fix my phone. Thanks.
Click to expand...
Click to collapse
Well not an expert but I read a lot on here and do what I can when I can.
This is what I got from my Mega:
Code:
L600 Output
====================
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
[U]
Number Start End Size File system Name Flags[/U]
[B] 1 4194kB 67.1MB 62.9MB modem
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm
7 70.6MB 71.2MB 524kB tz
8 71.2MB 84.3MB 13.1MB pad
9 84.3MB 92.7MB 8389kB param[/B]
[COLOR=Red][B]10 92.7MB 107MB 14.3MB ext4 efs[/B][/COLOR]
11 107MB 110MB 3146kB modemst1
12 110MB 113MB 3146kB modemst2
13 113MB 124MB 10.5MB boot
14 124MB 134MB 10.5MB recovery
15 134MB 145MB 10.5MB fota
16 145MB 152MB 7332kB backup
17 152MB 155MB 3146kB fsg
18 155MB 155MB 8192B ssd
19 155MB 164MB 8389kB ext4 persist
20 164MB 176MB 12.6MB ext4 persdata
21 176MB 2324MB 2147MB ext4 system
22 2324MB 3058MB 734MB ext4 cache
23 3058MB 3079MB 21.0MB ext4 carrier
24 3079MB 15.8GB 12.7GB ext4 userdata
pit file of my mega
DarkAngel said:
Well not an expert but I read a lot on here and do what I can when I can.
This is what I got from my Mega:
Code:
L600 Output
====================
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
[U]
Number Start End Size File system Name Flags[/U]
[B] 1 4194kB 67.1MB 62.9MB modem
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm
7 70.6MB 71.2MB 524kB tz
8 71.2MB 84.3MB 13.1MB pad
9 84.3MB 92.7MB 8389kB param[/B]
[COLOR=Red][B]10 92.7MB 107MB 14.3MB ext4 efs[/B][/COLOR]
11 107MB 110MB 3146kB modemst1
12 110MB 113MB 3146kB modemst2
13 113MB 124MB 10.5MB boot
14 124MB 134MB 10.5MB recovery
15 134MB 145MB 10.5MB fota
16 145MB 152MB 7332kB backup
17 152MB 155MB 3146kB fsg
18 155MB 155MB 8192B ssd
19 155MB 164MB 8389kB ext4 persist
20 164MB 176MB 12.6MB ext4 persdata
21 176MB 2324MB 2147MB ext4 system
22 2324MB 3058MB 734MB ext4 cache
23 3058MB 3079MB 21.0MB ext4 carrier
24 3079MB 15.8GB 12.7GB ext4 userdata
Click to expand...
Click to collapse
Take a loot at my pit file previously created with efs professional tool. Same like yours. I hope your debrick image will work for my mega. Please upload when possible. Do not worry about efs partition. I have my efs backup. I will restore mine. I have a question, if my phone becomes useable after using your debrick image and i restore only efs partition from efs backup will it brick again?
Thanks.
SPH-L600 sprint mega bad ESN
so as not to make a new topic, I decided to write here
I recently bought SPH-L600 sprint mega with a bad ESN, he came to me activated on Sprint and Sprint have sim I played settings and activation dropped sprint
but I live in another country and I can not activate it!
help somehow activate it! I bought an unlock code network, but said that he needed seller activation sprint!
any help would be much appreciated!
ashikrobi said:
Take a loot at my pit file previously created with efs professional tool. Same like yours. I hope your debrick image will work for my mega. Please upload when possible. Do not worry about efs partition. I have my efs backup. I will restore mine. I have a question, if my phone becomes useable after using your debrick image and i restore only efs partition from efs backup will it brick again?
Thanks.
Click to expand...
Click to collapse
Yes, they should be the same thing as we both have L600's. I didn't have a chance to look it over but I will try and get it to you later on today.
All you need is for your Mega to be able to get to Download Mode. Then and only then you will have to Odin a copy of the Official Firmware L600VPUBNE4 for it not to stay bricked but you probably already know that. As far as becoming usable that would be up to you, being able to restore your EFS data. In theory it should not brick but you need to only restore the EFS portion of the data.
Here is all the info I gathered from using Terminal Emulator in case you need it for file locations:
EFS is located: /dev/block/mmcblkop10
As you can see msm_sdcc.1 is specific to our device ( I noticed that it was the same on my SGS3 but not my SGN2 on KitKat ) so one can locate the by-name file to get the list below.
The second picture shows GNU Parted being run in my Terminal Emulator. You would need the Parted Binary file located here at the end of the Original Post.
Just extract the parted binary manually and then copy and paste it to the /system/bin folder with any File Explorer with Root access. After you paste the binary you will need to set the permissions to the parted binary you pasted to rwxr-xr-x or (0755). You can do this to any device you have and run it either in Terminal Emulator and even via ADB on your computer. Really handy to have sometimes.
Once you get the debrick image, below are two guides that I saved in my subscriptions that may help you. You may have them already.
deBricker
gTan64
---------- Post added at 05:31 AM ---------- Previous post was at 05:29 AM ----------
Ura535 said:
so as not to make a new topic, I decided to write here
I recently bought SPH-L600 sprint mega with a bad ESN, he came to me activated on Sprint and Sprint have sim I played settings and activation dropped sprint
but I live in another country and I can not activate it!
help somehow activate it! I bought an unlock code network, but said that he needed seller activation sprint!
any help would be much appreciated!
Click to expand...
Click to collapse
Actually this is an entirely different topic from Debricking a phone. You have a phone with a bad ESN. With that I can not help. If the previous owner ( or seller in your case ) "maybe" did not pay his bill, then your phone is locked out until it is released from his/her account by Sprint. If there is a way around this, I may not know.
I had this happen to me once before with my wife's Sprint SGS4. It was a pain but eventually two days later the seller finally came through and the phone was released for activation.
You should start a separate thread to see if you can get the right help and not get your question lost in this thread. I am sorry I couldn't help you any further.
Sorry you misunderstood
DarkAngel said:
Yes, they should be the same thing as we both have L600's. I didn't have a chance to look it over but I will try and get it to you later on today.
All you need is for your Mega to be able to get to Download Mode. Then and only then you will have to Odin a copy of the Official Firmware L600VPUBNE4 for it not to stay bricked but you probably already know that. As far as becoming usable that would be up to you, being able to restore your EFS data. In theory it should not brick but you need to only restore the EFS portion of the data.
Here is all the info I gathered from using Terminal Emulator in case you need it for file locations:
EFS is located: /dev/block/mmcblkop10
As you can see msm_sdcc.1 is specific to our device ( I noticed that it was the same on my SGS3 but not my SGN2 on KitKat ) so one can locate the by-name file to get the list below.
The second picture shows GNU Parted being run in my Terminal Emulator. You would need the Parted Binary file located here at the end of the Original Post.
Just extract the parted binary manually and then copy and paste it to the /system/bin folder with any File Explorer with Root access. After you paste the binary you will need to set the permissions to the parted binary you pasted to rwxr-xr-x or (0755). You can do this to any device you have and run it either in Terminal Emulator and even via ADB on your computer. Really handy to have sometimes.
Once you get the debrick image, below are two guides that I saved in my subscriptions that may help you. You may have them already.
deBricker
gTan64
---------- Post added at 05:31 AM ---------- Previous post was at 05:29 AM ----------
Actually this is an entirely different topic from Debricking a phone and on yours, you have a bad ESN. With that I can not help. If the previous owner ( or seller in your case ) "maybe" did not pay his bill, then your phone is locked out until it is released from his/her account by Sprint. If there is a way around this, I may not know.
I had this happen to me once before with my wife's Sprint SGS4. It was a pain but eventually two days later the seller finally came through and the phone was released for activation.
You should start a separate thread to see if you can get the right help and not get your question lost in this thread. I am sorry I couldn't help you any further.
Click to expand...
Click to collapse
Dark Angel you misunderstood my message i don't have bad esn. I lost esn number or corrupt it with dfs cdma tool. Dfs shows my esn but status from efs shows cps_na error. I didn't bought this phone second hand. My cousin send it from USA and she bought it new.
Thanks and i am waiting for your reply.
Off Topic Post / Misunderstanding .....
ashikrobi said:
Dark Angel you misunderstood my message i don't have bad esn. I lost esn number or corrupt it with dfs cdma tool. Dfs shows my esn but status from efs shows cps_na error. I didn't bought this phone second hand. My cousin send it from USA and she bought it new.
Thanks and i am waiting for your reply.
Click to expand...
Click to collapse
Yes I know, please disregard the quote and answer from the previous person responding above my post, right after the pictures I posted ( you will see the quote ). It was an off topic post and the forum combined them for some reason in the response for you ( probably because they were so close in time frame when I posted ) ..... I tried separating them in different posts but it still combined them together.
That is why off topic posts should be posted in a new thread/topic to avoid confusion......
DarkAngel said:
Yes I know, please disregard the quote and answer from the previous person responding above my post, right after the pictures I posted ( you will see the quote ). It was an off topic post and the forum combined them for some reason in the response for you ( probably because they were so close in time frame when I posted ) ..... I tried separating them in different posts but it still combined them together.
That is why off topic posts should be posted in a new thread/topic to avoid confusion......
Click to expand...
Click to collapse
Wow!!! Dark Angel, you are the man i was looking for. You know linux like a pro. Linux is my favorite operating system. I didn't know parted was available for android also. How do you learn these things?
By the way sorry, i though your message about bad esn was for me.
Thanks
ashikrobi said:
Wow!!! Dark Angel, you are the man i was looking for. You know linux like a pro. Linux is my favorite operating system. I didn't know parted was available for android also. How do you learn these things?
By the way sorry, i though your message about bad esn was for me.
Thanks
Click to expand...
Click to collapse
Well not a Pro..... I still have much more to learn but Linux is my favorite OS to use for anything Android related. A lot I still do on Windows.
Debrick Image......
Okay try this image.......
I burnt this image several time over on a class 4, 8 gig card and it wrote the image on it perfect. I don't know if you will have to use a 16gig card for your Mega or not but try what you have 16 gig or less. Trial and error at this point.
You can probably add more to it if need be from the Official Firmware by dragging and dropping ( if I am not mistaken ) by just opening ( and not extracting ) the tar.md5 with WinRAR or 7zip. I can't remember if one was able to do this.......
L600 Debrick Image
Not working
DarkAngel said:
Okay try this image.......
I burnt this image several time over on a class 4, 8 gig card and it wrote the image on it perfect. I don't know if you will have to use a 16gig card for your Mega or not but try what you have 16 gig or less. Trial and error at this point.
You can probably add more to it if need be from the Official Firmware by dragging and dropping ( if I am not mistaken ) by just opening the tar.md5 with WinRAR or 7zip. I can't remember.
L600 Debrick Image
Click to expand...
Click to collapse
DarkAngel I wrote the img file to a 16gb sdcard and tried to boot my phone but it's not working. I waited 5 min and tried several times. I also used a usbjig to boot into download mode but failed.
Have a look these terminal output:
sudo dd if=/home/tails/Downloads/debrick.img of=/dev/sdc
174080+0 records in
174080+0 records out
89128960 bytes (89 MB) copied, 75.5075 s, 1.2 MB/s
[email protected]:~/Downloads$ sudo parted /dev/sdc print
Error: Invalid argument during seek for read on /dev/sdc
Retry/Ignore/Cancel? Ignore
Error: The backup GPT table is corrupt, but the primary appears OK, so that will be used.
OK/Cancel? ok
Backtrace has 8 calls on stack:
8: /lib/i386-linux-gnu/libparted.so.0(ped_assert+0x29) [0xb773ad19]
7: /lib/i386-linux-gnu/libparted.so.0(+0x4649c) [0xb777749c]
6: /lib/i386-linux-gnu/libparted.so.0(ped_disk_new+0x55) [0xb7742275]
5: parted() [0x804ea2b]
4: parted(non_interactive_mode+0x8c) [0x8055c4c]
3: parted(main+0x1970) [0x804d5b0]
2: /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0xb753aa83]
1: parted() [0x804d6e2]
You found a bug in GNU Parted! Here's what you have to do:
Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:
Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:
http://ftp.gnu.org/gnu/parted/
Please check this version prior to bug reporting.
If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:
http://www.gnu.org/software/parted
for further information.
Your report should contain the version of this release (2.3)
along with the error message below, the output of
parted DEVICE unit co print unit s print
and the following history of commands you entered.
Also include any additional information about your setup you
consider important.
Assertion (last_usable <= disk->dev->length) at ../../../libparted/labels/gpt.c:994 in function _parse_header() failed.
By the way is there any other way to recover from this state? I found qpst finds my phone after installing qhsusb_dload driver. Please help me.
Thanks
You are using an installed version of Linux correct? Are you on 13.04? Well I know the GNU Parted is just the program from Linux but the image still wrote on the SD card.
After the image was written to the SDcard, were you able to see the image content inside? For me it showed about 60MB of actual space written from the 85mb image. After it wrote, I just wrote over it and wrote over it and wrote over it again. Funny thing is I could not see the image at first so I then removed the card from my computer and re-inserted it and was then able to see it. I even inserted it on a Windows 8 tablet I have from a co-worker and it read it fine.
I did this while just using the "Install CD" and trying Ubuntu ( don't have it re-installed yet on my Notebook yet ). I did it using 14.04 LTS though. Try updating your GNU Parted ( your at 2.3 ), if it hasn't already been done, to the most current and re-write the image again.
DarkAngel said:
You are using an installed version of Linux correct? Are you on 13.04? Well I know the GNU Parted is just the program from Linux but the image still wrote on the SD card.
After the image was written to the SDcard, were you able to see the image content inside? For me it showed about 60MB of actual space written from the 85mb image. After it wrote, I just wrote over it and wrote over it and wrote over it again. Funny thing is I could not see the image at first so I then removed the card from my computer and re-inserted it and was then able to see it. I even inserted it on a Windows 8 tablet I have from a co-worker and it read it fine.
I did this while just using the "Install CD" and trying Ubuntu ( don't have it re-installed yet on my Notebook yet ). I did it using 14.04 LTS though. Try updating your GNU Parted ( your at 2.3 ), if it hasn't already been done, to the most current and re-write the image again.
Click to expand...
Click to collapse
Yes i am using an installed version of ubuntu 14.04. I was also not able to view partitions after i wrote the image to sdcard. But after i reinsert the card it showed all partitions and maybe mounted modem partition contents. I could view partitions with windows 7 also.
But when i try to boot the phone with this sdcard nothing happened. I tried several times but failed. What can i do now? DarkAngel please tell me a way to unbrick my phone.
Thanks
[Q&A] [ROM][DISCONTINUED] Huawei U8836D / Ascend G500 Pro (MT6577) custom ROMs (ICS)
Q&A for [ROM][DISCONTINUED] Huawei U8836D / Ascend G500 Pro (MT6577) custom ROMs (ICS)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][DISCONTINUED] Huawei U8836D / Ascend G500 Pro (MT6577) custom ROMs (ICS). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
SD card not mounting...
bgcngm said:
Initial notes:
Make sure that you have a full nandroid backup of your current ROM. If not, boot into recovery mode and make one. This is very important if you want to restore userdata after internal memory is re-partitioned.
Also make sure that you have a backup of your internal sdcard because it will be fully erased and disabled.
Warning: the package includes preloader, but there's no need to flash it. Make sure that your selection is according to the screenshot bellow.
Instructions:
Copy disable_internal_sdcard.zip to external sdcard (read note bellow)
Shutdown the phone
Open SP Flash Tool v3.1222.00 (or higher) and load the scatter file
Flash MBR, EBR1 and RECOVERY as shown on the next image first):
After flashing is complete, boot into recovery mode and format /data
Optionally, if you want to restore previously saved userdata, go to nandroid backup / restore and restore data (advanced restore feature)
Install disable_internal_sdcard.zip file through recovery mode (read note bellow)
Reboot your phone and enjoy your extended userdata partition
Important update: All the new ROM updates which include AROMA installer also include a script to automatically disable internal sdcard if extended userdata partition is detected. Dismiss the part of the instructions that refers to the installation of disable_internal_sdcard.zip file. All the rest of the procedure is still valid and must be done before installing the ROM. That said, if you are going to apply this modification, you must re-install the ROM.
Please also note that this mod should only work with my custom ROM installed. Be warned and please do not blame me if you run into some problem while applying the mod over stock or any other custom ROM
Click to expand...
Click to collapse
(links on quote removed cause i'm a new user)
Hello Bruno, wondering if you still monitor this... but anyway, I have tried and succeeded in doing the memory repartitioning but, after this, no matter what, the sd card never mounts (samsung 16gb neo on the microSD slot). I can force the mount on the recovery utility at the boot, but after when booting normally I have the extended internal memory but no SD is detected.
Is there a detail or trick I am missing?
Regards
Thanks
No, there's not trick at all. The sdcard should be mounted fine. Could you please paste here the contents of your /system/etc/vold.fstab so that I can check?
Discontinued
sip/voip and non-functioning microphone?
i realise this is a discontinued model (thread, etc), but I do have a question for a ROM developer for this phone may be able to easily answer.
It concerns SIP stack, VOIP. I cannot find any sip/voip settings options on this phone (flashed with the 3.0 ROM). I have loaded a 3rd party app and it *seems* to work apart from one issue....I can hear everything from the other end, but the party at the other end cannot hear me. It seems that the microphone does not work when making sip/voip based calls from *any* app I have tried. Is this a known issue (it seems there are questions out there) and is it something that can be easily sorted ? Thanks if anyone can provide a quick pointer. If not, thanks for reading - even at this late stage. Peace and best wishes.
Q&A for exFAT and NTFS fuse drivers easy build for any platform
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for exFAT and NTFS fuse drivers easy build for any platform. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Trying on 4.2.1.... It does not work. I got "volume operation failed" after manually run "recovery-update2.sh."
DeepInSleep said:
Trying on 4.2.1.... It does not work. I got "volume operation failed" after manually run "recovery-update2.sh."
Click to expand...
Click to collapse
If you manually run the script, be sure you run it as su, and provide it any parameter, e.g.
/system/etc/recovery-update2.sh test
For troubleshooting, edit the script to uncomment the logging and try to figure out the problem from the log file.
Lurker0 said:
If you manually run the script, be sure you run it as su, and provide it any parameter, e.g.
/system/etc/recovery-update2.sh test
For troubleshooting, edit the script to uncomment the logging and try to figure out the problem from the log file.
Click to expand...
Click to collapse
Problem solved I deleted this part (the script does not run with him. I do not know why)
Code:
#!/system/bin/sh
logfile0=/data/local/tmp/exfat_mount.log
#logfile=$logfile0
logfile=/dev/null
if [ -e $logfile0 ]; then
logfile=$logfile0
I also changed the mount point from the /mnt/media_rw/sdcard1 to /mnt/sdcard2. With a device=/dev/block/mmcblk1p1 some programs have not seen hardware sdcard, only storage/sdcard1 patch. Then I replaced it on device=/dev/block/vold/179:97. Now it works fine for me
UPDATE: crashing with multiple read/write operations. Tested in bittorrent app
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