Related
Hello....
So I am a newbie and have been doing a lot of reading on here. I am still a little confused by some of the terminology. I looked at the stickies and there isn't a place where it has all the terms together. For example, I thought that a ROM is the OS of the phone, so I am not sure how it could not contain a kernel.
Could some of your experts please define the following? And perhaps make it a sticky or add the info to one of the existing stickies.
ROM
Kernel
modem / radio / baseband
Voodoo
Odin
CWM
Thanks!
TheTinRam said:
Hello....
So I am a newbie and have been doing a lot of reading on here. I am still a little confused by some of the terminology. I looked at the stickies and there isn't a place where it has all the terms together. For example, I thought that a ROM is the OS of the phone, so I am not sure how it could not contain a kernel.
Could some of your experts please define the following? And perhaps make it a sticky or add the info to one of the existing stickies.
ROM
Kernel
modem / radio / baseband
Voodoo
Odin
CWM
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=855900
^^ #4 Stickied thread in the Development Forum.
This should have been posted in the Q&A forum btw (by the way)
shorttripp86 said:
http://forum.xda-developers.com/showthread.php?t=855900
^^ #4 Stickied thread in the Development Forum.
Click to expand...
Click to collapse
I read that thread. There is somebody ASKING for definitions but it is not answered.
If this should be in another forum, the I apologize. However, most newbies such as me, will come into the development forum and look for stickies to learn. There are stickies but they dive right into it without defining what these terms mean.
Rom - files used/flashed that overwrite system files and flash new ones for the phone to run.
Kernel - Basically the focal point of performance and stability for the phone, also determines important phone functions.
Modem - software through which the actual radio hardware functions through, determines connectivity of radio to towers
Voodoo - name for the enhancements such as converting rfs to ext4, voodoo color, and sound specifically designed for the Galaxy S family.
Odin - PC application used to flash system files including modem, recovery, and such that the phone may not have permission to flash itself. Also used for complete restoration of phone to stock.
CWM - Clockworkmod, a recovery mode designed by Koush that enables the phone to backup and restore system files, wipe data ans cache, and mainly used to flash normally nonpermitted software (roms, themes). Allows for options not normally permitted in the regular Android recovery.
That's how I see it, anyone else care to correct if wrong?
Sent from my SCH-I500 using XDA Premium App
I might add that the kernel is what acts as a bridge between your phone's hardware and application level.
This Android Dictionary is pretty good:
androidcentral.com/dictionary
I don't have enough posts to hyperlink it.
I hope XDA doesn't mind, but this is also over at AC and will do a much better job than the dictionary of answering your questions.
http://forum.androidcentral.com/ver...nate-beginners-rooting-read-me-3-17-11-a.html
TheTinRam said:
I read that thread. There is somebody ASKING for definitions but it is not answered.
If this should be in another forum, the I apologize. However, most newbies such as me, will come into the development forum and look for stickies to learn. There are stickies but they dive right into it without defining what these terms mean.
Click to expand...
Click to collapse
Alright, I'll try and redeem myself from that douchey response from earlier. I'm sorry for the unneeded grumpiness, but my I'm having phone issues - and I'm sure you'll come to understand this feeling now that you're learning this stuff, and I assume will go on to flash rom's, kernel's, and inevitably recovery files via ODIN.
Here are some definitions I've "kanged" (Kang means to take somebody else's work and put it to good use. Credit is expected but occasionally not given. -djmcnz <Nexus One>) together definitions and definitions from xda members, community write-ups, and general android development guides.
Here we go...
ROMs
"First thing is a ROM - Basically in the phone world these are packages of data that contain mostly all of your stuff on the phone such as apps, settings, contacts, and all sorts of other data. The devs here at XDA develop custom roms that are streamlined and reconfigured to work better than the stock ones. They also remove all the junk apps that Verizon and Samsung include on the phone including satan himself - Bing.
[Deodexing ROMs] is just a way of re-working some of the phone's file system to allow installation of themes and other things that require a deodexed rom, it doesnt affect anything else afaik.
Some ROMs also include themes. Themes are basically just re-skins or recreations of the android UI, which are usually more intuitive and customized than the stock ones. You can always try different themes with almost any rom, its up to you which ones you like."
Kernels
"[Kernels] are essentially the coding and underlying framework that the phone pretty much runs on. They control MANY aspects of the phone and how they work, custom kernels are what really turn the speed up on this phone."
** ROM & Kernel definitions from Bawb3's <Fascinate> Beginner's Guide here: Fascinate Beginner's Guide / FAQ**
---------------
Radio (Modem/Baseband)
"The Radio [Modem/Baseband] is the software part of your device that is powering on/off and controlling your radio interfaces. This includes Bluetooth, 2G/3G Phone, WiFi, GPS..... And it also includes Radio BootLoader and other device specific firmwares needed for using your radio interfaces and for interfacing them with the OS (Windows Mobile/Android)."
**Radio (Modem/Baseband) definition from kholk's <HTC> Radio thread here: (RADIO) The HTC HD2 Master Radio Thread**
Radio (Modem/Baseband) Alternate Description
"The Radio [Modem/Baseband] is the part of the phone that deals with mobile connections. It handles talking to the 3G network, Bluetooth, WiFi and GPS. The radio contains software that controls how it operates, and newer versions of radio firmware are made available from time to time. These updates are transparent to the user, although users who elect to install custom software can update their radio using an update.zip file [or "radio/modem".tar file] made available by members of the modding community.
Flashing the radio is potentially risky, and you should NEVER pull the battery out of a phone that is flashing the radio. If you do so, it is possible your phone will be bricked. Nevertheless, it can give improved battery life, signal strength and data performance, so is often done by users moving to later versions of ROMs.
Care should be taken to only flash the correct type of radio to a phone. NEVER attempt to flash a CDMA phone with a GSM radio or vice-versa. It is likely you will brick the phone if you attempt to do so."
**Alternate <non-xda> Radio (modem/Baseband) definition from here: Alt. VROM Radio Definition**
---------------
Voodoo Lagfix
"In a nutshell, voodoo is a substitute kernel for the Galaxy S i9000 variants, and in due time for the rest of the Samsung Galaxy S family (Captivate, Vibrant etc...). The kernel provides improvements over stock user experience such as :
Lagfix - Convert /data and /system file partitions from RFS to EXT4 to increase performance and virtually kill the lag that we all hate so much.
Display/Color/Sharpness - Enhance and fine tune the amazing Super Amoled screen to provide the best results in different situations.
Sound - Improve Galaxy S sound by leveraging it’s top of the line audio chip, the way it’s meant to be leveraged.
Voodoo comes as “root ready” - You need only to install Superuser from market, and you phone is rooted.
Optimized Samsung TwLauncher - No slowness. (if you already have a different launcher, this will not prevent you from using it.)
ClockworkMod Recovery - Voodoo comes with built in version of CWM. To access it, turn on your phone while pressing VolumeUp+Home+Power
Improved ADB Shell - Support tab compleition and more.
For more info visit http://project-voodoo.org"
**Voodoo Lagfix description from <non-xda> Voodoo Community Write-Up here: Voodoo Community Write-Up (Gdoc)**
---------------
ODIN
"What is ODIN? There is a longer answer, but lets just say what it really is. It's a very simplistic program you install on your PC. With this program and a few files you can very easily restore your phone to stock. Some suggest doing this EVERY time you go from Rom to Rom.
Why do they do this? Because when you are on one ROM and you go to another, there may be "ghosts" from your previous ROM impacting the performance of your new build. That said, I have never done this... and I have never had an issue. Your choice. How to use ODIN will be in the guides section (eventually)."
**ODIN description from s15274n's <Vibrant> guide here: Noob Guide: HOW TO ROOT/ODIN/FLASH/RECOVER**
---------------
ClockworkMod Recovery (CWM)
"ClockworkMod Recovery is based off the eclair recovery image. Features include Nandroid backup, adb shell, advanced update.zip options (ignore asserts and signature checks), and file browser for choosing update.zips (you can now organize your stuff by directory.)"
**CWM Recovery description from Koush's <Nexus One> thread here: ROM Manager & Clockwork Recovery**
---------------
NOTICE:I take ZERO credit for any of the above mentioned programs. All credit goes to the original program developer(s). This is a list of definitions and descriptions. I have included referenced member citation, and links to the original post/thread/site. Original program developer(s) or cited xda member(s), please let me know if you would like something removed from this post.
---------------
TheTinRam, I hope this helps and makes up for for my sour mood earlier.
I have spent days looking for threads so this neewb is about to break something. Well maybe not. I have my daughters Eris 2.1 and am trying to root it for her. I have tried several times with different methods. The issue is that I can get into recovery mode after every 1 click app but nothing I try will let me toggle to unzip to SD, or toggle to anything for that matter, volume wont do it and all track ball will do is let me select reboot. Man my DX was easy compared to the one click method.
HELP PLEASE,
If the trackball is having trouble scrolling, I'd install the trackball-optional custom recovery so you can use other buttons to scroll. There are instructions for doing this here:
http://androidforums.com/eris-all-things-root/214240-amon_ra-1-6-2-custom-recovery-trackball-not-required.html
It sounds like you fall into "Scenario 2" which says you should follow the same method as "Scenario 1" to get rooted using the trackball-optional recovery.
I'll give it a shot, The help is much appreciated,
I am been trying to help him to get this thing to add the Custom Recovery, but every root format has not worked at all. Most are outdated or there are files missing. Specially on the link provided above. The download for the scripts no longer has Root_1 or Root_2, it has a bunch of other stuff there for gscript. Found an link on Droidforums for gscript for rooting and the scripts don't work.
Any complete instructions anywhere?
popfan said:
I am been trying to help him to get this thing to add the Custom Recovery, but every root format has not worked at all. Most are outdated or there are files missing. Specially on the link provided above. The download for the scripts no longer has Root_1 or Root_2, it has a bunch of other stuff there for gscript. Found an link on Droidforums for gscript for rooting and the scripts don't work.
Any complete instructions anywhere?
Click to expand...
Click to collapse
popfan,
I am not aware that any of the above links or files are missing... Can you point-out / tell me specifically which files you cannot access / download / link-to?
The root_part1 and root_part2 files are part of erisuser1's (bftb0's) Universal Root for Dummies! thread that I do reference in my AF thread, but these should still be up, active, and available.
So, I'm not sure if you are speaking about becoming rooted or installing a my trackball-optional custom recovery.
Let us know.
Cheers!
Im sure my kid has shuned me for leaving her Eris with someone so thanks to everyone for the help. Pop is helping me out and after moving file at the point where it says to open and look to see root 1 and root2 they are not there and there are a ton of other stuff. Also the pick look different than on the thread like the app has been updated. Also when doing the ball recovery there is no tools folder to be found. I'm sure pop wont touch it again till tomorrow so any other help / advice is more than welcome or it may cost me my Dx
malloneem said:
Im sure my kid has shuned me for leaving her Eris with someone so thanks to everyone for the help. Pop is helping me out and after moving file at the point where it says to open and look to see root 1 and root2 they are not there and there are a ton of other stuff. Also the pick look different than on the thread like the app has been updated. Also when doing the ball recovery there is no tools folder to be found. I'm sure pop wont touch it again till tomorrow so any other help / advice is more than welcome or it may cost me my Dx
Click to expand...
Click to collapse
LOL, sorry, didn't make/see the connection between your two posts .
Okay, let's try something new here...
Just a week or so ago, I re-packed jcase's 1-click rooting app to include my trackball-optional recovery image in lieu of the original recovery that his app includes.
So, let's have you re-root using the new 1-click app (all credit to jcase, both for his app and his threads both here http://forum.xda-developers.com/showthread.php?t=742228 and over at AF http://androidforums.com/eris-all-things-root/139178-universal-1-click-eris-app-apk-no-pcs-no-scripts-needed-easy.html).
Since you've already used the 1-click app before, then all you'll have to do is grab my new "trackball-optional" version:
https://sites.google.com/site/scaryalienware/downloads/one-click-tbo.apk
MD5 sum: 15763b51cf707c027cc73bc117e1fc39
(the "tbo" in the name stands for "trackball optional" ).
Just follow the same process you did before while running the 1-click app and you should end-up with my trackball-optional recovery installed.
Let me know how it goes (you'll be the first besides me that I know of that has tried it; the user that I created it for to test has not yet responded, LOL).
Cheers!
I tried this link below. It no longer has the root_1 and root_2 in it.
http://www.megaupload.com/?d=774XYFRA
I did use your "updated" 1-click app with tbo and it worked great.
Thanks!!
Too bad this phone was not as easy as my captivate.
popfan said:
I tried this link below. It no longer has the root_1 and root_2 in it.
http://www.megaupload.com/?d=774XYFRA
I did use your "updated" 1-click app with tbo and it worked great.
Thanks!!
Too bad this phone was not as easy as my captivate.
Click to expand...
Click to collapse
Glad that jcase's repackaged app worked for you. I'll update my documentation to make this available to others.
Also, re. the above Megaupload link...it works just fine for me (from my PC and from my Droid X) and includes all of the aforementioned root_part1/2 files.
I think you've fallen prey to a truncated download, which is not uncommon with Megaupload in my experience. This is also why is important to double-check the file sizes and MD5 checksums of files that you download so that you know you got the whole-shebang; notice that erisuser1 did include the MD5 in his thread for this file:
- Download gscript.zip (MD5 92796a8c6e61e8f1ee36e315c0acae7d)
I've often found it helpful to use a different browser other than the stock browser (like Opera Mini) when doing downloads via my Eris since the stock browser does seem to have more issues (timeouts perhaps) than it should.
Cheers!
Thanks to all this tuff till you hooked us up but now on to nightmare 2
I downloaded CyanogenMod7.1.0 RC1 [2.3.5 GingerBread NIGHTLY]
from this thread http://forum.xda-developers.com/showthread.php?t=944430&highlight=ROM
Got it up but it has no market so I can not get to titanium, boot loader or anything... It says to flash google apps after the rom but now Im back to the trackball / volume key issue because it's all in titanium. ??? I did a factory reset and it came back up as the new ROM, ???
EDIT UPDATE!!!!
Sorry for the hassle all, the "green" start call button works as the down after the download.. All is well.. I think..
Again thanks to you all, If I hear of any good deals on an Eris I will know why.
You need to download GAPPS to your sdcard. That is why you don't have market.
http://forum.xda-developers.com/showthread.php?t=944430&highlight=ROM
Its just below link for the rom and save it to your sdcard. Go ahead boot into recovery and wipe data, daliv-cache, cache; Flash Rom again, then flash gapps and reboot.
Hi all,
Hopefully this is something fairly simple to answer, but my dilemma is that I want to flash a different ROM onto my wifi Xoom. I understand the basic process (I flashed the ROM on my old HTC Hero several times), but have been running into trouble on the Xoom and I think it boils down to the fact that Recovery Mode can't mount my SD card. I assume by SD card it means internal storage, but it can't read that or an actual SD card so I'm not sure it matters.
Anyway, after a couple of hours of research, I discovered that the best way to fix this is apparently to re-flash my recovery to version 3.2.0.0 of CWM instead of the 5.8.3.1 the current version of ROM Manager installed. After digging around, I found what I believe is 3.2.0.0, but I can't figure out where to put it so ROM Manager can find it and flash it over the current Recovery image. Also, if anyone has a link to download 3.2.0.0 that they know works, please let me know because I couldn't find a working download link anywhere.
I've also looked into doing it through Fastboot, but can't exactly figure out how to do that, either. I downloaded the fastboot.exe application and installed the Android SDK, but it tells me that it can't start because AdbWinApi.dll is missing. Being a non-developer type, I have no idea where this is supposed to come from, how I should install it, and if there's any other steps I'm missing.
So if anybody can help me out with either of these (preferably using the older version of CMW), that'd be great, but if anyone has an even easier way to do it, please share by all means. I know what I'm doing once I get to the point of installing the new ROM and Gapps, I just need my Xoom to be able to find them first.
Thanks in advance to anyone who can help out!
Stu
Use this thread
http://forum.xda-developers.com/showthread.php?t=1074979
In the future use the search button, it was pretty easy to find with just a little effort.
063_XOBX said:
Use this thread
http://forum.xda-developers.com/showthread.php?t=1074979
In the future use the search button, it was pretty easy to find with just a little effort.
Click to expand...
Click to collapse
Will do...and thanks, that worked.
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...