Related
Thanks to Trekfan422991 for cluing me in on the Optimus 3D recovery.
Working:
Nandroid
ADB (after special driver install, need to tweak recovery for it to work with normal drivers)
Mounting USB to computer
Flashing zip files
Dangerous:
Fix Permissions (caused lots of crazy issues, fix by wiping data if you use it)
Sdparted (the sdcards are mount incorrectly, this will probably destroy your device)
I am in the process of making a recovery specifically for our device, it is mostly done and will be posted here when it is ready!
What you are going to need:
ADB (and know how to use it, don't ask in here)
Rooted Phone (again, that will not be covered, don't ask in here)
Optimus 3D recovery image [Download]
If you don't understand something in that list, DO A SEARCH AND LEARN, don't clutter the thread with crap!
Lets get started!
Lets start by getting the recovery.img file on the phone. Open up a cmd prompt and type:
Code:
adb push recovery.img /data
The rest of this will be done on the phone shell. In the cmd prompt type:
Code:
adb shell
We will need to have su access, In the cmd prompt type:
(If you haven't allowed shell su in SuperUser now would be a good time to accept the root request on the phone.)
Code:
su
Now we are going to backup your current recovery to your sdcard. In the cmd prompt type:
(make sure your sdcard is not mounted to your computer)
Code:
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
After that is done we are going to flash ClockWorkMod Recovery! In the cmd prompt type:
Code:
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
Congrats! You now have ClockWorkMod Recovery! In the cmd prompt type:
(each line is single command)
Code:
rm /data/recovery.img
reboot
How to enable ADB access: (only if it's not working already)
Download and install: (unzip and install the 2 exe files)
http://www.mediafire.com/?j5m1plnvzb8r0zc
While booted into ClockWorkMod Recovery, go into your device manager, you should see an "LGE Android Composite Device" with a yellow triangle on it.
right click on it, update driver software...
select browse my computer for driver software
select let me pick from a list of device drivers on my computer
click the "Have Disk" button
click the "browse" button
browse to;
for 64bit:
C:\Program Files (x86)\LG Electronics\LG Android Driver\64BitADB
for 32bit:
C:\Program Files\LG Electronics\LG Android Driver
and select lgandadb.inf
click "ok"
From that list select "Android Sooner Single ADB Interface"
click "next"
click "yes" on the popup
Click to expand...
Click to collapse
Awesome Great Work. Did you figure out the Bootloader? Or is there even one should more be the question I suppose. Good thing I am having issues with permissions with this didn't notice the SD Card Mounting issue till just now. That I can't deal with atm.
malickie said:
Awesome Great Work. Did you figure out the Bootloader? Or is there even one should more be the question I suppose.
Click to expand...
Click to collapse
I found a few modes, but no drivers yet so I don't know what they are. Even if we break stuff the kernel and recovery are separate, so technically we should always be albe to get back into recovery to fix stuff.
thankyou DG for getting this started..
so now with my clockworkmod i just made a backup of stock rom... if i say change the framework and I get boot loop.. will this clockwork mod be able to restore the original rom without any problems???
tiny problem... might just be missing something... but after i made my backup and i choose reboot system now... it just goes back to recovery... how do i boot up my phone!!!
sorry if it is obvious... im super tired...
Trekfan422991 said:
tiny problem... might just be missing something... but after i made my backup and i choose reboot system now... it just goes back to recovery... how do i boot up my phone!!!
sorry if it is obvious... im super tired...
Click to expand...
Click to collapse
I got mixed up as to what partition to flash, you just flashed a recovery image over the kernel... its ok tho.
follow my instructions to the su part, then do this.
// this will restore the kernel
dd if=/sdcard/mmcblk0p5.backup of=/dev/block/mmcblk0p5 bs=4096
// this will backup recovery
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
// this will flash cwm
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
OP is fixed!
edit--
and you have no adb access, this is going to get interesting!
haha... i shoulda noticed
____
LET THIS BE A LESSON FOR ALL OF YOU!!!!
THIS IS WHY YOU ALWAYS ALWAYS MAKE BACKUPS!!!!!!
NEVER SKIP THE BACKUP STEP!!!! haha
Trekfan422991 said:
LET THIS BE A LESSON FOR ALL OF YOU!!!!
THIS IS WHY YOU ALWAYS ALWAYS MAKE BACKUPS!!!!!!
NEVER SKIP THE BACKUP STEP!!!! haha
Click to expand...
Click to collapse
LOL! For sure that is why I always say, " Save early, save often, save to multiple locations!" haha.
47r0n1n said:
LOL! For sure that is why I always say, " Save early, save often, save to multiple locations!" haha.
Click to expand...
Click to collapse
sorry just side note:
how you liking your thrill compared to the evo 3d???
designgears said:
What you are going to need:
ADB (and know how to use it, don't ask in here)
Rooted Phone (again, that will not be covered, don't ask in here)
Optimus 3D recovery image [Download]
Click to expand...
Click to collapse
Thanks so much to DG & Trekfan, I've been looking everywhere for CWM!
I cannot find the download link to the recovery - in the quote above from the OP, where it says download, is that supposed to be a download link? I don't know if there's a typo or if I'm just missing something, but the "download" word doesn't link to anything for me. Instead, I thought I'd try searching for it in the optimus 3d forums, but search is down too Does anyone have a link?
Komodo Rogue said:
Thanks so much to DG & Trekfan, I've been looking everywhere for CWM!
I cannot find the download link to the recovery - in the quote above from the OP, where it says download, is that supposed to be a download link? I don't know if there's a typo or if I'm just missing something, but the "download" word doesn't link to anything for me. Instead, I thought I'd try searching for it in the optimus 3d forums, but search is down too Does anyone have a link?
Click to expand...
Click to collapse
I took it down for now, working on some issues.
Woohoo, got Trekfan422991 all fixed!
its true... i tested out my framework mod and it works great!!! look sway better then stock!!!
designgears said:
I took it down for now, working on some issues.
Click to expand...
Click to collapse
Ah, gotcha. I thought I was going crazy Thanks!
Let's rom this baby dg . I assume you also bought this with plans to possibly exchange it when the AT&T Galaxy S II comes out? I'm very impressed by the performance and build quality so far. The main thing it needs is a better theme... yikes!
designgears said:
Dangerous:
Fix Permissions (caused lots of crazy issues, fix by wiping data if you use it)
Sdparted (the sdcards are mount incorrectly, this will probably destroy your device)
Click to expand...
Click to collapse
After CWM is installed and working on our device, would it be safe to fix permission in "ROM Manager," or does that just fix permissions through whichever recovery is currently installed?
I'm guessing someone here knows how ROM manager works in this regard, but if not, I'd be happy to be a guinea pig... after all, I can make/restore backups now! : )
gtg465x said:
Let's rom this baby dg . I assume you also bought this with plans to possibly exchange it when the AT&T Galaxy S II comes out? I'm very impressed by the performance and build quality so far. The main thing it needs is a better theme... yikes!
Click to expand...
Click to collapse
Sorry for being OT but I must agree: if designgears made a Thrill ROM that's Cognition-esque then I'd consider keeping my Thrill, but considering he already has a ROM for the GSII, I imagine he's going to get the AT&T Galaxy S II? Side note, you know you've really earned some serious nerd-cred when other nerds (who you don't even know) speculate what your next cell is going to be
Komodo Rogue said:
Sorry for being OT but I must agree: if designgears made a Thrill ROM that's Cognition-esque then I'd consider keeping my Thrill, but considering he already has a ROM for the GSII, I imagine he's going to get the AT&T Galaxy S II? Side note, you know you've really earned some serious nerd-cred when other nerds (who you don't even know) speculate what your next cell is going to be
Click to expand...
Click to collapse
Not waiting on dg here. Think you missed the "let's" part. Working on a Thrill ROM as we speak. Just got the Thrill about an hour ago and I already dumped the system image, de-odexed it, created an updater-script, added root and busybox, removed bloat, and updated a few apps. Time to start theming, modding framework, and tweaking.
Im also working on a ROM but if we cannot flash zips with CWM then how am I supposed to flash the ROM? Are you going to flash it with Heimdall or something?
gtg465x said:
Not waiting on dg here. Think you missed the "let's" part. Working on a Thrill ROM as we speak. Just got the Thrill about an hour ago and I already dumped the system image, de-odexed it, created an updater-script, added root and busybox, removed bloat, and updated a few apps. Time to start theming, modding framework, and tweaking.
Click to expand...
Click to collapse
Oh, good to hear! Man I really have to sit down and try to learn some more technical stuff sometime, because ROM creation, and not even just the theming aspects, is so appealing to me.
Maybe you can create a thread placeholder and describe what you've done so far? We're really getting OT, sorry all.
timbrendelaz said:
Im also working on a ROM but if we cannot flash zips with CWM then how am I supposed to flash the ROM? Are you going to flash it with Heimdall or something?
Click to expand...
Click to collapse
Oh, I thought you could flash zips through adb after doing the fix? Or no? (((edit: wait, no, I was thinking about pushing .apks through ADB, not flashing .zip files))) Hopefully this is something DG's new recovery might address. If no to both, could you distribute ROMs via nandroid backup files of a fresh ROM installation? It would be incredibly inefficient, but it would work, right?
hello
is there any way to extract the whole firmware from a i9000?
a friend of mine just bought a i9000 from the same carrier that i have.. and i want the original rom. is there any way to get it untouched (vanilla)??
Not really untouched, you'd always need root to grab the firmware, so that's flashing a different kernel or trying other ways to get (temporary) root.
But don't let that stop you, the kernel probably won't be any different than the standard Samsung one, so you can put it back later.
the thing is... i cant find the original kernel around, i have searched all over, and there is no where to be found. so.. if i change the kernel, and take it in for warranty related stuff the carrier people will notice that i have changed it.. and they'll say.. sorry you void the warranty!!
so... is there any way to extract a vanilla rom??
Use check fus downloader. Google it or look around xda. You will be able to get your ROM direct from Samsung.
Sent from my GT-I9000 using Tapatalk
Is it me or are you confusing kernel and ROM ? The kernel is the stuff that makes it boot and talk to the hardware and stuff, like a bios from a pc. The rom is the operating system which does everything else.
Can you post the kernel version ?
EDIT: Since you did not quote I am assuming you are replying to my post. If not please just ignore my bantering.
Bubble-be said:
Is it me or are you confusing kernel and ROM ? The kernel is the stuff that makes it boot and talk to the hardware and stuff, like a bios from a pc. The rom is the operating system which does everything else.
Can you post the kernel version ?
Click to expand...
Click to collapse
It's just you. I know what a kernel is, do you know what a rom is? The kernel is included with the rom. If you get the rom, you have the kernel.
Also, the kernel technically does not make your device boot. It is, however, used during the boot process to perform some hardware initialization (initializing IRQs, setting up the scheduler, starting the dynamic module loader).
It is nothing like a BOIS from a PC. This point is illustrated by the fact that a PC running linux requires both a BIOS and a kernel. They are mutually exclusive. The kernel is a part of the OS, the BIOS is a part of the device.
Like I said, get the ROM and you get the kernel. The kernel is simple to extract, and you also have the added bonus of having the complete, unadulterated rom should you need it in the future.
since i`m new to everything here can you help me with smth that is bothering me
i got a i9000 2 months ago and since then i`ve been messing around with rooting and flashing around without understanding o lot but i've been doing exactly what others say step by step
i like this galnet miui rom (the only one i've tried so far) but i have battery drain issues
can you tell me a good combination of kernel and/or bootloader with this galnet so i would not have a battery drain
now i'm using official 2.3.5 and i have a full day battery usage
but i like some features that galnet has
thanks in advance
xxbeanxx said:
EDIT: Since you did not quote I am assuming you are replying to my post. If not please just ignore my bantering.
It's just you. I know what a kernel is, do you know what a rom is? The kernel is included with the rom. If you get the rom, you have the kernel.
Also, the kernel technically does not make your device boot. It is, however, used during the boot process to perform some hardware initialization (initializing IRQs, setting up the scheduler, starting the dynamic module loader).
It is nothing like a BOIS from a PC. This point is illustrated by the fact that a PC running linux requires both a BIOS and a kernel. They are mutually exclusive. The kernel is a part of the OS, the BIOS is a part of the device.
Like I said, get the ROM and you get the kernel. The kernel is simple to extract, and you also have the added bonus of having the complete, unadulterated rom should you need it in the future.
Click to expand...
Click to collapse
xxbeanxx said:
EDIT: Since you did not quote I am assuming you are replying to my post. If not please just ignore my bantering.
Click to expand...
Click to collapse
I did not quote, but was answering to the OP.
Sorry if that was confusing.
It's just you. I know what a kernel is, do you know what a rom is? The kernel is included with the rom. If you get the rom, you have the kernel.
Click to expand...
Click to collapse
Well yes, but I can't imagine a provider customizing the kernel. They do however customize the rom to include their own bootscreen, apps, theme. My previous phone was that way for example. I looked long and hard for the original firmware. But unless you're with one of the really big providers (Orange or the like), the rom is not available on the interwebs.
Showing up at a provider's service center with a bog standard rom can look suspicious that way.
Also, the kernel technically does not make your device boot. It is, however, used during the boot process to perform some hardware initialization (initializing IRQs, setting up the scheduler, starting the dynamic module loader).
It is nothing like a BOIS from a PC. This point is illustrated by the fact that a PC running linux requires both a BIOS and a kernel. They are mutually exclusive. The kernel is a part of the OS, the BIOS is a part of the device.
Click to expand...
Click to collapse
Thanks for clearing that up. I was aware of most things, but decided to paint a simpler picture for the OP.
enushi2002 said:
...can you tell me a good combination of kernel and/or bootloader with this galnet so i would not have a battery drain
...
Click to expand...
Click to collapse
The bootloader has no affect on your battery life.
Also don't assume the kernel is the biggest contributing factor to your battery drain. It very well may be, but there are a lot of other things that could also cause it. It would be better to try to investigate the cause of your battery drain rather than just switching kernels to try to fix it.
To directly answer your question, no I can't tell you a good kernel to use with MIUI. I am running CM7.1 currently with stock kernel and get decent battery life.
Are you on 3G data often? CM (and thus MIUI) has trouble with 3G, causing bad battery drain (so called RIL bug).
---------- Post added at 09:34 AM ---------- Previous post was at 09:27 AM ----------
Bubble-be said:
...the rom is not available on the interwebs.
Showing up at a provider's service center with a bog standard rom can look suspicious that way.
Click to expand...
Click to collapse
If you can update your phone via KIES you can get your ROM via check fus downloader. The rom you download using this tool will be what KIES uses to update your phone. So it is not "bog standard," it is what your provider puts on your phone, complete with provider customizations. It is impossible for a service center to tell the difference.
I had CyanogenMod on my phone when the touchscreen malfunctioned. I downloaded my provider's latest rom using check fus downloader, flashed it with odin, performed a factory reset, and brought it back and they replaced it no questions asked. As far as they knew I had only ever used the "proper channels" (ie: kies) to update my phone.
xxbeanxx said:
Use check fus downloader. Google it or look around xda. You will be able to get your ROM direct from Samsung.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Hi, thanks, but it did not found it..
in the result box says
Product Code: GT-I9000HKTVMT
no firmware info retrieved for given data
the firmware info would be:
Product code: GT-I9000HKTVMT
PDA: I9000TUBJPA
CSC: I9000TVMTJP6
Phone: I9000TUBJPA
Is a froyo 2.2.1 for a galaxy I9000T from movistar venezuela
I guess i'll keep looking for it
francescopp said:
I guess i'll keep looking for it
Click to expand...
Click to collapse
Wow that's strange. Well anyway, you could try this..it won't work without root but if you don't mind rooting first you can do this to get your kernel, then unroot.
Code:
adb shell su -c "dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096"
If you want to backup your entire rom:
Code:
adb shell su -c "dd if=/dev/block/bml1 of=/sdcard/boot.bin bs=4096"
adb shell su -c "dd if=/dev/block/bml2 of=/sdcard/pit.pit bs=4096"
adb shell su -c "dd if=/dev/block/stl3 of=/sdcard/efs.rfs bs=4096"
adb shell su -c "dd if=/dev/block/bml4 of=/sdcard/Sbl.bin bs=4096"
adb shell su -c "dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096"
adb shell su -c "dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096"
adb shell su -c "dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096"
adb shell su -c "dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096"
adb shell su -c "dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096"
adb shell su -c "dd if=/dev/block/bml12 of=/sdcard/modem.bin bs=4096"
To verify the dumps you can mount them in linux or use MagicISO in windows (the .rfs ones at least).
You can then turn these files into a full fledged rom with a bit of tinkering. This might be your only option.
No matter what downloaded package I tried to open with heimdall to install on my Captivate (i896), heimdall gave me the error:
Tar header contained and invalid file size
I installed ClockworkMod, and rooted the phone, had an issue and installed the stock Rogers (Canada) firmware. Since then, heimdall isn't detecting my phone at all.
$ heimdall detect
Failed to detect compatible download-mode device.
I'm willing to work with any of the heimdall developers to resolve these two issues, or does anyone have any ideas on how to resolve?
Thanks in advance!
acanuck said:
No matter what downloaded package I tried to open with heimdall to install on my Captivate (i896), heimdall gave me the error:
Tar header contained and invalid file size
I installed ClockworkMod, and rooted the phone, had an issue and installed the stock Rogers (Canada) firmware. Since then, heimdall isn't detecting my phone at all.
$ heimdall detect
Failed to detect compatible download-mode device.
I'm willing to work with any of the heimdall developers to resolve these two issues, or does anyone have any ideas on how to resolve?
Thanks in advance!
Click to expand...
Click to collapse
Firstly, please before you do anything else make sure you're using Heimdall 1.3.1 instead of 1.3.2. 1.3.2 introduced issues for some previously well-supported devices. The issues introduced shouldn't hard-brick any devices, but it can cause flashes to fail, and that can be a daunting experience.
The error you've received seems to indicate that the type of file you're trying to flash is not a Heimdall Firmware Package. Chances are the file you have is an archive that when extracted contains 3 other archives for use with Odin. Heimdall Firmware Packages are much simpler than this but unfortunately haven't been heavily adopted by the community just yet.
Nonetheless, Heimdall is extremely flexible. If you wish to flash the files you've downloaded please refer to the README included in the Heimdall DMG (also available here). In particular please refer to the section on performing a Custom Firmware Flash.
However, before you do all that you're going to need to ensure your device is being detected. Aside from the obvious "make sure you're in download mode" there are several reasons why you device may not be detected in OS X. They are as follows:
1. Permissions/ownership are set incorrectly for the codeless kext used by Heimdall. Open a terminal and run the following in order to ensure this is not the problem:
Code:
sudo chown -R root:wheel /System/Library/Extensions/heimdall.kext/
sudo chmod 755 /System/Library/Extensions/heimdall.kext/
sudo chmod 0644 /System/Library/Extensions/heimdall.kext/Contents/Info.plist
After doing this you will need to reboot your machine.
2. There are other kexts on your system interfering with Heimdall's codeless kext. Typically this would occur if you've tried to install Kies for Mac as Samsung's kernel extensions are given higher priority. If the Samsung's kext does exist it can be removed using the following command:
Code:
sudo rm -rf /System/Library/Extensions/ssuddrv.kext/
Again, after running this command you will be required to reboot your machine.
3. Your running an old faulty bootloader...
This is a much more serious problem. Samsung originally released several devices with a secondary bootloader that included a faulty implementation of the USB protocol. Unfortunately this means OS X will be totally unable to recognise your device. As such you will have to flash your phone using either Windows or Linux. However, once you flash a working secondary bootloader onto your device you will be able to use OS X for any other flashing later on.
Once you've completed 1 and 2 from above you'll be able to ask Heimdall to detect your device again. If it doesn't work this time around chances are you're running a faulty secondary bootloader.
$ heimdall version
v1.3.2
I did have the ssuddrv.kext/, which once I deleted and rebooted also asked me about tethering upon USB connect. Also, the heimdall Info.plist from was 755 permissions for some reason. This is all resolved now.
adb is showing the device, but heimdall is still not.
I was able to flash new kernels using heimdall flash on the command line a few days ago, until I went back to a stock image. My issue is, without being able to flash the ClockworkMod recovery kernel now, using heimdall, I'm not sure how to move forward. Perhaps I can can install a zImage with adb or something else? There doesn't appear (from reading the forums) to be FASTBOOT on the Captivate.
There must be a way I can boot another zImage using osx as I've done before?
I have now successfully rooted my device by downloading the firmware, unpacking system.img.md5, adding the su binary, making an ext4 sparse image and installing that to the device using heimdall. Problem was, that on my first attempts the system became unstable, the UI restarted repeatedly, especially when manually switching WiFi and Data Mode. After double and triple checking everything I found that I could create a perfectly stable system image by following the same steps but just not adding the su binary. One further attempt placing the su binary in /system/usr/bin (does not exist) and using it as a backdoor to install the binary to /system/bin/su I now seem to have a stable and rooted system.
It appears that something has been detecting my initial and straightforward attempt to tamper with the system image and made the system to become unstable. I have seen a lot of errors from PackageManager in my logs but nothing conclusive.
Tom
RealBorg said:
I have now successfully rooted my device by downloading the firmware, unpacking system.img.md5, adding the su binary, making an ext4 sparse image and installing that to the device using heimdall. Problem was, that on my first attempts the system became unstable, the UI restarted repeatedly, especially when manually switching WiFi and Data Mode. After double and triple checking everything I found that I could create a perfectly stable system image by following the same steps but just not adding the su binary. One further attempt placing the su binary in /system/usr/bin (does not exist) and using it as a backdoor to install the binary to /system/bin/su I now seem to have a stable and rooted system.
It appears that something has been detecting my initial and straightforward attempt to tamper with the system image and made the system to become unstable. I have seen a lot of errors from PackageManager in my logs but nothing conclusive.
Tom
Click to expand...
Click to collapse
Hi Tom! I managed to root my s advance with this method, but in guide that I have read, was said that I should put the su binary on "/system/xbin/". I used that steps, by Xanonus. Over here everything gone right and after flashing, I got Supersu from Play store. If help you, please thanks Xanonus.
Sorry for bad English
johnnybr said:
Hi Tom! I managed to root my s advance with this method, but in guide that I have read, was said that I should put the su binary on "/system/xbin/". I used that steps, by Xanonus. Over here everything gone right and after flashing, I got Supersu from Play store. If help you, please thanks Xanonus.
Click to expand...
Click to collapse
Xanonus unnecessarily copies everything out from system to new_system, you can just add the su binary to the loop mounted image.
/bin/su is the location of the su binary on every Unix system and Superuser also installs the su binary to /system/bin/su. I wonder if it would make a difference (avoid instability) to place it in /system/xbin/su.
Tom
RealBorg said:
Xanonus unnecessarily copies everything out from system to new_system, you can just add the su binary to the loop mounted image.
Click to expand...
Click to collapse
I really suspected that, like you said, part of all that stuff was unnecessary.
About the place of su binary, well, I just wanna to help. I don't know nothing about linux and less of unix. But normally, while you are dealing with this kind of stuff, you should try. Cause things sometimes work when they shouldn't and don't work like they should. I can only say: God knows why...:silly:
Thread moved to General section, post in the relevant section next time.
Why use Heimdall to flash ? Odin3 works better
"None forget the bite.....of Viper...."
CallMeVentus said:
Why use Heimdall to flash ? Odin3 works better
Click to expand...
Click to collapse
heimdall is the method of choice when you are on linux and works like a charm
much easier than Odin which needs the image to be put into a .tar.md5 file
Tom
RealBorg said:
heimdall is the method of choice when you are on linux and works like a charm
much easier than Odin which needs the image to be put into a .tar.md5 file
Tom
Click to expand...
Click to collapse
I have tried heimdall but I can't make it work on Windows (7 X64, it never get to comunicate between pc and mobile). So when I was messing with my rom I have to try zillions of ways to make a image to work with Odin. In the end, make the image with ext4_utils and compress with tar on my virtual machine running ubuntu did the trick. If you don't put any md5sum verification or "md5" in the name of the file, Odin never check the file.
This was me trying to root hahhaa!!
I guess everyone that want play with Android should learn to use linux. ubuntu at least. I intend to learn linux, but I can't right now.
Sorry, crap english from google translator!
johnnybr said:
I have tried heimdall but I can't make it work on Windows (7 X64, it never get to comunicate between pc and mobile). So when I was messing with my rom I have to try zillions of ways to make a image to work with Odin. In the end, make the image with ext4_utils and compress with tar on my virtual machine running ubuntu did the trick. If you don't put any md5sum verification or "md5" in the name of the file, Odin never check the file.
This was me trying to root hahhaa!!
I guess everyone that want play with Android should learn to use linux. ubuntu at least. I intend to learn linux, but I can't right now.
Sorry, crap english from google translator!
Click to expand...
Click to collapse
Seriously?
How can hemidall work on windows when its designed for linux!
Sent from my GT-I9070 using xda premium
Shaaan said:
Seriously?
How can hemidall work on windows when its designed for linux!
Click to expand...
Click to collapse
Actually it has a windows version. Even Mac has a version of Heimdall. Take a look: http://www.glassechidna.com.au/products/heimdall/
Indeed I can't make it work... Perhaps on windows x86 it can work...
Hi Guys, I flashed a wrong radio by accident, could someone be so nice to extract his radio from a XT1092 and send it to me? Theres a beer in it for you
if you can tell me how to extract i will do it for you.
and, if you can help me, i need the system image of the build kxe21.187-42. should be yours as well.
i made another mistake with the messaging app, and now i have to reset all my moto x XT1092 (european)
Andariel636 said:
if you can tell me how to extract i will do it for you.
and, if you can help me, i need the system image of the build kxe21.187-42. should be yours as well.
i made another mistake with the messaging app, and now i have to reset all my moto x XT1092 (european)
Click to expand...
Click to collapse
You have to have USB Debugging enabled, then check adb for your device, type the following:
1. adb shell
2. su
2.1 Grant su permission on your phone
3. dd if=/dev/block/mmcblk0p7 of=/sdcard/modem.bin bs=4096
4. Choose a file explorer you like and grab the modem from the sd card. its probably in /sdcard. +
If you could do that, i would be SOOOOOOOOOOOOO thankful. I dont have the System Image, i could give you a nandroid backup though
Tomorrow i try this. Is possible to do this only with titanium backup?
Otherwise i have to find a windows pc, i have only a macbook.
Radixtrator said:
Hi Guys, I flashed a wrong radio by accident, could someone be so nice to extract his radio from a XT1092 and send it to me? Theres a beer in it for you
Click to expand...
Click to collapse
Hi my friend!
Don't know if this help, but try to extract from the sbf image or reinstall the entire rom again.
Try this link:
http://sbf.droid-developers.org/phone.php?device=37
Sent from my XT1097 using XDA Premium HD app
Radixtrator said:
Hi Guys, I flashed a wrong radio by accident, could someone be so nice to extract his radio from a XT1092 and send it to me? Theres a beer in it for you
Click to expand...
Click to collapse
Here you go, had to put it in a folder (but extract, it's not flashable), hope it helps.
Andariel636 said:
Tomorrow i try this. Is possible to do this only with titanium backup?
Otherwise i have to find a windows pc, i have only a macbook.
Click to expand...
Click to collapse
If you have adb installed on your macbook, you can do this from the terminal
fnut6969 said:
Here you go, had to put it in a folder (but extract, it's not flashable), hope it helps.
Click to expand...
Click to collapse
Sadly it didnt.. Your phone was an US phone correct? It stil shows no Sim no reception.. IMEI is gone too from the info screen
Could you try doing this for me ?
su (press Return)
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512 (press Return)
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512 (press Return)
I remember my script deleted thos, and maybe that will do the trick
Radixtrator,
What exactly you flashed as wrong radio: NON-HLOS.bin ? fsg.mbn? Both ? Please explain in more details.
And how you flashed modem file, provided by fnut6969?
Radixtrator said:
You have to have USB Debugging enabled, then check adb for your device, type the following:
1. adb shell
2. su
2.1 Grant su permission on your phone
3. dd if=/dev/block/mmcblk0p7 of=/sdcard/modem.bin bs=4096
4. Choose a file explorer you like and grab the modem from the sd card. its probably in /sdcard. +
If you could do that, i would be SOOOOOOOOOOOOO thankful. I dont have the System Image, i could give you a nandroid backup though
Click to expand...
Click to collapse
Here it is!
a nandroid backup shuld be usefull? or i can use it to extract only the messaging app?
Radixtrator said:
If you have adb installed on your macbook, you can do this from the terminal
Sadly it didnt.. Your phone was an US phone correct? It stil shows no Sim no reception.. IMEI is gone too from the info screen
Could you try doing this for me ?
su (press Return)
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512 (press Return)
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512 (press Return)
I remember my script deleted thos, and maybe that will do the trick
Click to expand...
Click to collapse
My apologies, I now notice you were looking for the XT1092 modem, I guess that shows how important it is to actually read posts thoroughly.
fnut6969 said:
My apologies, I now notice you were looking for the XT1092 modem, I guess that shows how important it is to actually read posts thoroughly.
Click to expand...
Click to collapse
No problem
Radixtrator said:
Hi Guys, I flashed a wrong radio by accident, could someone be so nice to extract his radio from a XT1092 and send it to me? Theres a beer in it for you
Click to expand...
Click to collapse
I thought the factory images where available on the motorola site but I see now that they aren't. Maybe you can tell me how to create a system dump to return to stock (I have an xt1092)
godutch said:
I thought the factory images where available on the motorola site but I see now that they aren't. Maybe you can tell me how to create a system dump to return to stock (I have an xt1092)
Click to expand...
Click to collapse
The absolutely most awesome thing you could do is give me a Full Nandroid Backup ( without data) especially including the EFS Partition, because i believe thats whats wrong with my phone... That would be incredibly awesome
I don't want to unluck just yet. I didn't even know btw moto has an efs partition too, I can't see it
godutch said:
I don't want to unluck just yet. I didn't even know btw moto has an efs partition too, I can't see it
Click to expand...
Click to collapse
In twrp you can definitely select EFS as a backup able partition
Radixtrator said:
In twrp you can definitely select EFS as a backup able partition
Click to expand...
Click to collapse
I can't boot twrp witp a locked bootloader and I am sorry but I don't want to publish my efs, my imei might get blocked but I can try to make a system dump
i did find this thread http://forum.xda-developers.com/showthread.php?t=1960918
or this one:
http://forum.xda-developers.com/showpost.php?p=45881991&postcount=86
godutch said:
i did find this thread http://forum.xda-developers.com/showthread.php?t=1960918
or this one:
http://forum.xda-developers.com/showpost.php?p=45881991&postcount=86
Click to expand...
Click to collapse
Well the fella in the first link seemed to have fixed it by flashing the Original Firmware...
The Problem is, there is no german firmware ANYwhere on the Internet.
Radixtrator said:
Well the fella in the first link seemed to have fixed it by flashing the Original Firmware...
The Problem is, there is no german firmware ANYwhere on the Internet.
Click to expand...
Click to collapse
Well one suggestion is to factory reset without the sim and set up the phone with no sim. It won't hurt to try