Related
TO GET TO THE POINT, AND TO AVOID MY *****ING, SCROLL DOWN
OK, imma recent migrating bird from the sinking WinMo ship.
Just got this phone from LG, nice phone, but the flashing guides here aren't so easy to understand
I'll quote a 6 line instruction from the Prime/Megatron ROM thread which is
http://forum.xda-developers.com/showthread.php?t=870640
How to flash:
First, reboot into recovery via 3-button-combo, ADB, terminal, w/e.
Partition SDcard (swap: 0, ext: 512), ext2-ext3, then ext3-ext4 it.
Wipe data (data,cache,dalvik-cache,ext).
Connect the device to PC, copy Megatron over to the SDcard, disconnect.
Flash it via "flash zip from sdcard"
Reboot
Read important notes below
That's it.
Click to expand...
Click to collapse
SERIOUS? THATS IT???????????
I have no idea what all that means, and so are millions of sad puppies who migrates from WinMo's or dreaded Dumb Phones like the ones they sell in 7-11
SO, the point is (you can stop scrolling now)
PLEASE PLEASE PLLLEEEEAAASE make a easy guide for flashing, possibily a video. Or you could make it easy enough for me to understand, and ill make the guide.
BTW, in the long term, it WILL educate FURTHER n00bs.
Thanks in advance. Sorry for the *****ing. Love u guys
OK, OK, OK, you have got me!! I will prepare some "dictionary" for all noobs. Maybe it will sounds crazy, but when I logged-in I had no idea what android is. OO is my first android phone. I have got everythink from whole this forum, but I was there since thread about P500 started so it wasn't too hard catch and read every post here. So, all informations are there, but sometimes is not possible find them.
So i just have to read everything? Optimus One Android Dev or General?
Great! Thanks a lot
But gonna go to sleep.. I'm sorry lol this is my last week of winter break and its midnight. Bye!
dongimin2 said:
So i just have to read everything? Optimus One Android Dev or General?
Click to expand...
Click to collapse
About 95% of posts it will be useless because there are also some question, helps, and another stuff. There is too much words and useless trash. You also need know basics of unix-like systems to understand what are guys (and you) trying to do in adb shell, what is root and for what it is, what # mean in command line, and so on.
custom ROM is mainly for experienced user. At least, experienced in unix-like system, because android is based on it. Tools like busybox bringing next tools known from unix and some programs needs it for running. And another and another words and name what is normal for advanced user, not for n00bs here.
Because that all stuff it takes some time that I will have some usable noob dictionary.
This is a good and pretty much complete guide.
forum.androidcentral.com/lg-optimus-s-roms-hacks/48543-idiots-guide-rooting-custom-roms-optimus-s-edition.html
Rooting is the same, you just have to change some commands for the custom recovery but once you get there you'll know. And I recommend rooting via Adb, its easier for later.
btw, don't know if its a problem posting the link, if it is, sorry.
One thread is enough!
Do not do this again or you will have an infraction for spam.
Cheers
Im missing clockwork recovery, i think its a wonderfull tool. And i think life on the Folio would be much easier with it. I dont have the skills my self to make it happen. I dont even know if its possible. But i thought i put the question out there to see if something happens. And i must say we all own Dexter a big thanks, because he seams to be the only one with any rom cooking skills for the Folio. Ican say that its only because of him that i bought the Folio. I also saw in the Tnt0.4 thread a question about Cyanogen and if we wanted it, HELL YEEAAAH!!!! I know tthat GTab have a beta for it. And also read that GTab and Folio are very close hardware wise so maybe a port is possible. But again i dont have the skills
No one? Am i the only one wanting these things? I thougt if we could get a thread going on the matter we might inspire someone with the skills to do a Cyanogen port for the folio. Cyanogen is almost ready to start the nightlies on CM7 so maybe we could have Gingerbread.
Clockwork recovery would be nice to have its alot easyer to do things with it, im still waiting for stable CyanogenMod on my galaxy s to be able to say if i want it on my tablet i have no idea how to get clockwork to work though and if its even possible
i'm sure its possible, but reading the Gtab thread on Cyanogen i'm waiting for a stable release before i would consider wasting time on it, and currently my "compiling" environment is still VMWare based, and i simply dont like compiling in it, since it takes like 30x the time i got on my debian..(will be ubuntu very soon)
It sounds promissing that you keep track on the development of the Cyanogen rom for Gtab. There seams to be some more work being done over Irc on freenode. Its a beta 6.2 thats been released there, but it seams to have some issues. But for sure Cyanogen would be exellent. Im currently running Gridlocks "Crackflashers" CM7-Rc0 on my Desire HD, and Gingerbread is so smooth and it runs so well. And Koush has a guide on how to get clockwork recovery on to new devices on his site. But hey, i dont got the skills. I just enjoy all the Devs work and try to help out with some beta testing if needed.
nickwarn said:
And Koush has a guide on how to get clockwork recovery on to new devices on his site. But hey, i dont got the skills. I just enjoy all the Devs work and try to help out with some beta testing if needed.
Click to expand...
Click to collapse
i was considering testing the Gtab edition, and modify the parts that point to wrong partitions and make it folio compatible.. thats probably the easy one..
but maybe i should check that site? you got a link? or should google help?
Dexter_nlb said:
i was considering testing the Gtab edition, and modify the parts that point to wrong partitions and make it folio compatible.. thats probably the easy one..
but maybe i should check that site? you got a link? or should google help?
Click to expand...
Click to collapse
Yes its "Koushikdutta.com" he has a guide its called "Porting clockwork recovery to new devices" Its a little hard to find. Just go to bottom on the site and click on 2010 articles and scroll down and there it isorting Clockwork Recovery to New Devices
I pasted the begining of the guide:
It is difficult for me to port recovery for a device I don’t have. So, people can attempt to port it using this guide. However, if you want it done properly, and probably quicker, you can loan the device to me personally at:
Koushik Dutta
2721 1st Ave 507
Seattle, WA 98121
The package must include:
The rooted phone.
A return packing slip to your address.
A signed statement saying: “I, <your name here>, am lending this device, <name of device>, to Koushik Dutta so that he can try to port Clockwork Recovery to the device. I understand that rooting a phone voids the warranty and tampering with the software may render the device nonfunctional. I realize and accept that the phone may not be functional when it is returned. Koushik Dutta is not liable for any damages to the device.”
And so on, have a look.
The folio seem to be very close to the Gtab, what about Advent Vega? because the guys in Gtab thread are using Vega rom and it also has a clockwork recovery. I dont know , but maybe having a look at that would help. If looking aat the differrent parts of recovery.img and where they differ one can see where changes need to be made? I dont know, just trying to help. I really want this clockwork rec, i think we all and the folio would take a step forward. And maybe have a look at VeganTab rom, if possible to port?
I've used clockworkmod recovery since G1 era and it has saved my b*tt several times. The built-in nandroid support, permission fixing, unsigned zip flashing, etc are very useful and user-friendly.
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
nickwarn said:
Yes its "Koushikdutta.com"
Click to expand...
Click to collapse
ok, will check it out this weekend.
That would be great dexterr
I just read in the Avent Vega forum that Apache14 maid a port of GTab cyanogen for them and it seems to work ok. And he also said that he is now concentrating on Gingerbread, proberly that means CM7. And judging from the work Apache14 has done for us with Desire HD, Z, G2. This sounds really promising
Hi,
I'm trying to port ClockworkMod Recovery v3.0.0.5.
For now it's partially working. I can't mount some part.
This is my recovery.fstab :
Code:
# mount point fstype device [device2]
/boot auto /dev/block/mmcblk0p5
/cache auto /dev/block/mmcblk0p2
/data auto /dev/block/mmcblk0p6
/misc auto /dev/block/mmcblk0p3
/recovery auto /dev/block/mmcblk0p7
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk0p8
/system auto /dev/block/mmcblk0p1
/sd-ext auto /dev/block/mmcblk1p2
/boot and /recovery don't mount.
any idea is welcome
wolfx said:
/boot auto /dev/block/mmcblk0p5
/recovery auto /dev/block/mmcblk0p7
/boot and /recovery don't mount.
Click to expand...
Click to collapse
you should not mess with 5 and 7, those are in a stock rom boot and recovery images, not a filesystem. so they cannot be mounted.
wolfx said:
Hi,
I'm trying to port ClockworkMod Recovery v3.0.0.5.
For now it's partially working. I can't mount some part.
This is my recovery.fstab :
Code:
# mount point fstype device [device2]
/boot auto /dev/block/mmcblk0p5
/cache auto /dev/block/mmcblk0p2
/data auto /dev/block/mmcblk0p6
/misc auto /dev/block/mmcblk0p3
/recovery auto /dev/block/mmcblk0p7
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk0p8
/system auto /dev/block/mmcblk0p1
/sd-ext auto /dev/block/mmcblk1p2
/boot and /recovery don't mount.
any idea is welcome
Click to expand...
Click to collapse
I dont know, but im glad someone taking the first step. Maybe you could mail Koush, its a link in the guide for porting clockwork recovery. I dont know how much support he does. But writes that one can send ones device to him and he will port it, so i think if hes willing to that kind of work, he probably answers some question. I wish you the best of luck and i will follow your progress with great interest
My port of the ClockworkMod recovery is about fully working.
update from .zip, wipe, backup and restore ... are working but i still have some minor issue.
Partitions don't automatically mount and actually backup of boot part don't work.
I'm asking if bootloader could be the problem.
wolfx said:
My port of the ClockworkMod recovery is about fully working.
update from .zip, wipe, backup and restore ... are working but i still have some minor issue.
Partitions don't automatically mount and actually backup of boot part don't work.
I'm asking if bootloader could be the problem.
Click to expand...
Click to collapse
yes, according to DerArtem, you cannot see the partitions which contain that information its located outside of the mmc.
but sounds great you got it running, alot will appreciate it...
Rom cooking
moved.............
Maybe I'll make a stupid question ... but .. not really for serving or clockwork recovery that can help.
Can anyone explain to me that extra utility of this tool?
thanks
i just started hacking my Legend some time ago and got the liking of RomManager. my friend have a as100 rooted and flashed rom manually. Clockwork port to this device will be great on the go.
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
For now simply follow the instructions and use the provided file download from the link posted below
http://forum.xda-developers.com/showpost.php?p=48392009&postcount=1
I have personaly tested this method in full on My AT&T Samsung Galaxy S4 ZOOM SM-C105AUCUAMJ2 (4.2.2 Jelly Bean)
although it should be safe to use on any AT&T Samsung Galaxy S4 ZOOM running an android version prior to Kit-Kat
All Credit for this, "exellent completely safe", Root method goes to its creator k1mu
And please Know that it is only being shared with you via his explicit permission.
EDIT:
Q&A for [ROOT] Saferoot: Root for AT&T Galaxy S4 ZOOM SM-C105AUCUAMJ2_On 4.2.2 JB
Please if you are not on an AT&T Galaxy S4 ZOOM C-150a, Feel Free to Read
but Do not seek help,instruction, or any other type of advice by posting in this thread as it is hard enough to find information about a specific device when the said device does not have a dedicated forum. Thank You for your Understanding in this.
Instructions & Advice
If ?'s arise
and time allows I will add device specific instruction as well as any advice, Please bear with me. Same as above Q&A Link
Will this same method also work on the SM-C105AUCUAMJ2?
kbracing6 said:
Will this same method also work on the SM-C105AUCUAMJ2?
Click to expand...
Click to collapse
Most Definitely as this was the reason for my post
Hey @Phatboyj420, as far as converting a raw OTA file to Odin files, here's what I can tell you. The OTA file should be filename.cfg, i.e. a cfg file. Believe it or not, this can be manipulated like an archive (like zip or rar or tar) so open that cfg file in 7zip, WinRar, or whatever. You're going to want to extract the files like (I can't guarantee this a full list, just the ones I can remember) modem.bin, NON-HLOS.bin, boot.img, recovery.img, aboot.mbn, rpm.mbn, sbl1.mbn, sbl2.mbn, sbl3.mbn (you might not have all 3, idk), and tz.mbn. Again, there may be others you need, and/or not all the ones I just listed might be necessary, they're just the ones I remember dealing with before. Oh, you're going to need to make sure the system, cache, and persdata partitions are all packed into .img.ext4 files, idk if they're like that in the OTA cfg archive.
Here's where it gets even hazier for me. So, I know from personal experience that you can take any of these files (I'll just use recovery.img for this example). In a linux terminal (I use Ubuntu for convenience's sake, my laptop has windows and ubuntu partitions) run this command:
Code:
tar -H ustar -c recovery.img > recovery.tar
So that's how you can take any one of those files I mentioned last paragraph and pack it into an Odin-flashable tar. I'm still a n00b when it comes to the linux terminal, so I can't really say the syntax for packing more than one at once.
So I guess I haven't really given you the complete process, but hopefully this is at least a decent starting point. Honestly I consider myself a hobbyist at best, not an expert. muniz_ri, who Devo7v mentioned earlier, did all the heavy work in this regard so he can probably help you much more, I just didn't want to volunteer him for the job
thisisapoorusernamechoice said:
Hey @Phatboyj420, as far as converting a raw OTA file to Odin files, here's what I can tell you. The OTA file should be filename.cfg, i.e. a cfg file. Believe it or not, this can be manipulated like an archive (like zip or rar or tar) so open that cfg file in 7zip, WinRar, or whatever. You're going to want to extract the files like (I can't guarantee this a full list, just the ones I can remember) modem.bin, NON-HLOS.bin, boot.img, recovery.img, aboot.mbn, rpm.mbn, sbl1.mbn, sbl2.mbn, sbl3.mbn (you might not have all 3, idk), and tz.mbn. Again, there may be others you need, and/or not all the ones I just listed might be necessary, they're just the ones I remember dealing with before. Oh, you're going to need to make sure the system, cache, and persdata partitions are all packed into .img.ext4 files, idk if they're like that in the OTA cfg archive.
Here's where it gets even hazier for me. So, I know from personal experience that you can take any of these files (I'll just use recovery.img for this example). In a linux terminal (I use Ubuntu for convenience's sake, my laptop has windows and ubuntu partitions) run this command:
Code:
tar -H ustar -c recovery.img > recovery.tar
So that's how you can take any one of those files I mentioned last paragraph and pack it into an Odin-flashable tar. I'm still a n00b when it comes to the linux terminal, so I can't really say the syntax for packing more than one at once.
So I guess I haven't really given you the complete process, but hopefully this is at least a decent starting point. Honestly I consider myself a hobbyist at best, not an expert. muniz_ri, who Devo7v mentioned earlier, did all the heavy work in this regard so he can probably help you much more, I just didn't want to volunteer him for the job
Click to expand...
Click to collapse
Thanks My guy,
This definately gives me a good jumping off point.
The phone shipped with JB-4.2.2 and I think there has been an AT&T OTA for KK so it would have to be a complete Firmware so thats good news.
I'm working on several projects at once so I don't know exactly when I'll get to this but when I do the first thing will be to verify whether the .img's for data/system/cache are img.ext4 or not and if not how to produce correctly.
Also I don't have a Linux Dev setup yet I'm running Windows On a 2011 Dell XPS-17_L702x with an intel 2720 quad core. So from your post I take it Ubuntu would be your suggestion for Linux Distro. and should I make a separate Linux Partition and run from it, or run from a VM-Box inside of windows? Which do you think would be most efficient?
Now that I think of it I'm going to start a dedicated thread for development discussion for this specific device. If I start the thread in the Development section for the general S$-ZOOM but title it specifically for the " AT&T-C105a_ZOOM " do you think the mods would want to move it to the general Q&A section?
" I would hope that, as it would pertain directly to the development of the specific device they would see fit to leave it in the development section.
Sorry for the randomness of my thoughts but I will link you to the thread when I get around to starting on it.
For now I'm going to get back to work on the S4_Active for My daughters B-day I intend to have it Rooted and rommed out for her. When I get that done I'll make my way back to this Project, and start the dedicated thread.
Thanks again,
" I look forward to future collaboration as it seem we share a similar Hobie at the least ",
Phatboyj
Unfortunately for the few lonely SM-C105a users still hanging on out there this does not appear to be a completely effective root. I get this in dmesg: <3>[ 2130.920856] c0 Restricted changing UID. PID = 11580(su) PPID = 11575(sh)
capt_planit said:
Unfortunately for the few lonely SM-C105a users still hanging on out there this does not appear to be a completely effective root. I get this in dmesg: <3>[ 2130.920856] c0 Restricted changing UID. PID = 11580(su) PPID = 11575(sh)
Click to expand...
Click to collapse
What is your build # because this is a fully effective root method for the ATT SM-C105a running build# SM-C105AUCUAMJ2
Please elaborate on where your dmesg is coming from.
Is it from running Saferoot to obtain Root?
Or is it from some other function you are attempting after obtaining root?
@Phatboyj420 Great to see you here--when I'm sure your S4 Zoom is long gone. Yeah, that's my build and I should point out that I get that in dmesg only for certain operations in the system folder (trying to copy modules I think). No biggie, for day to day this method works fine. I'm more interested in whatever happened with that unbrick image you were trying to make from dd. Did you ever test it? Was it effective? My current efforts are focused on developing a reliable unbrick method for our phones. Rather than the complete image I think we may need to extract and flash the original bootloader in many cases. Can you provide any feedback on this?
capt_planit said:
@Phatboyj420 Great to see you here--when I'm sure your S4 Zoom is long gone. Yeah, that's my build and I should point out that I get that in dmesg only for certain operations in the system folder (trying to copy modules I think). No biggie, for day to day this method works fine. I'm more interested in whatever happened with that unbrick image you were trying to make from dd. Did you ever test it? Was it effective? My current efforts are focused on developing a reliable unbrick method for our phones. Rather than the complete image I think we may need to extract and flash the original bootloader in many cases. Can you provide any feedback on this?
Click to expand...
Click to collapse
@ capt_planit
while I have moved on from using my [email protected] S4-Zoom, I do still have it and the dd dumps of it the problem with providing said dumps publicly is that some "idiot would inevitably flash the complete dd.image to there phone giving them an exact clone of my phone explicitly the IMEI via EFS parition are my concerns.
That being said if I know that the dd.images were to be used in a proper manner, by say a knowledgeable Dev. I would gladly supply them to further /Kickoff Development,
It sounds as if we are of like mind but I found myself at a stand still and did not recieve any response from the plea in my Sig.
But rest assured if there is something I can do to assist I will.
as far as an unbrick.img for the Zoom c105a
I did make one but have had no reason to use it to know if it works or if the SD unbrick method even works for the Zoom like it does on the Galaxy S3 that the method was originally discovered on.
Even if it does work the SD-Unbrick method only gets you to a state where Download
mode works SO unless I am mistaken and you can access adb through Download Mode witch I'm pretty sure you cant, we would still be at a stand still as there is no stock firmware publicly available for our device " Ludacris I know " but true none the less.
Edit:
1 thing we need is the OTA update from JB to KitKat available for our device we need some one to extract it before updating then and only then might we be able to create an install-able firmware for our device.
if I'm not mistaken after you download the OTA update you should be able to find it in /cache/fota just zip the entire fota folder move it to your sd-card and make it available to me and we'll make it happen from there.
If you don't want to except the update just delete it at this point and reboot.
...
...
I think this user @awwar describes an inability to access download mode>here. In anycase, I think that thread would be a great place to post your unbrick. image. I think your dd image seems too small. But if you still have it, that is what @moomoo was asking for when he started that thread. I can't provide mine, except as separate img files. My understanding is that flashing an efs image won't provide a real IMEI. I think flashing some combination of boot, system, cache (I'm surprised this would be necessary) and recovery should get the operator some kind of system. But so far it doesn't seem to work that way. Your help getting some working phone flash would be greatly appreciated. I believe, BTW that the OTA is dead...
Hello everyone,
After spending what feels like the last few days searching and reading and generally driving myself into a state of absolute frustration, I thought I was ask here, because I think if it can't be answered by the XDA crowd, it probably can't be answered. I posted this question in the T-Mobile G3 Q&A forum and while it got 30+ views, no one has replied -- so I'm thinking that perhaps I needed to ask in a more general forum. My apologies if I'm breaking some sort of cross-posting rule (if so I'll remove it no problem).
The phone I'm working with is an LG D851, bootloader unlocked, rooted and currently running the latest LiquidSmooth ROM. The attempts I've made to access these partitions was done under (rooted) stock, PAC ROM, and LS. It doesn't seem to matter, though, as whatever I'm doing wrong is wrong across all of them!
Basically...I can't for the life of me figure out how to mount either /modemst1 or /modemst2 (/dev/block/mmcblk0p21 and /dev/block/mmcblk0p22, respectively).
I'm rooted (of course) and have attempted to do so via both terminal emulator and ADB Shell (both as su/root) -- neither has worked.
I have a sneaking suspicion that the problem is me, and that I can't seem to figure out the correct combination of mount options and locations to get it to work.
Either that, of I have failed to understand something about /modemst1 and /modemst2 which makes mounting them while Android is running impossible (or at least unlikely). If that's the case, is it possible to extract the contents of these directories from one of the /efs image backups that are oh-so-necessary? Or perhaps from a TWRP backup of /efs? Yes, I'm grasping at straws here, but my instincts tell me that you should be able to at least view the contents of these partitions -- and frankly I see no reason why the contents can't be extracted and explored. Or is there something I've failed to grasp there?
Can someone that actually knows what they're doing please enlighten me? I'm feeling really...well, dumb right now, because I know once I see the solution I'm going to be really humbled that my search-fu and my google-fu -- which is normally quire strong -- has failed me...and you have NO IDEA how badly it's failed me, I've literally spent hours researching this. But this time, the dragon has won.
So, XDA Brothers and Sisters...I await your enlightenment!
Thank you in advance...