Related
I've been trying to recreate a flashable firmware based on the stock TMobile flash dumps and I have complete success.
Heres how to save your current firmware. It will be saved with all apps and settings except for whats on /sdcard.
I recommend reseting to defaults using "Settings->Privacy->Factory data reset" if you want to give these files to someone else to build a flashable rom for you. That will delete all your personal information.
Note: I just backed up a completely setup AT&T Tab, with tons of apps and customizations and restored it to my stock T-Mobile Tab, perfectly! Every app works, home screen is setup perfect, everything!
Effectively this is equivalent to a nandroid backup.
I'll call it "Roto Backup"!
Code:
mkdir backup
cd backup
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"
adb shell su -c "tar -czvf /sdcard/data.tar.gz /data"
adb pull /sdcard/param.lfs .
adb pull /sdcard/zImage .
adb pull /sdcard/factoryfs.rfs .
adb pull /sdcard/dbdata.rfs .
adb pull /sdcard/cache.rfs .
adb pull /sdcard/modem.bin .
adb pull /sdcard/efs.rfs .
adb pull /sdcard/boot.bin .
adb pull /sdcard/Sbl.bin .
adb pull /sdcard/pit.pit .
adb pull /sdcard/data.tar.gz .
Note you will be prompted for superuser permissions on the Tabs LCD on every dd command.
If you don't have the tar command on your tab, install Busybox Installer from the market.
I just paste the above commands into my command shell window and when im done all the files are siting in my current (backup) directory.
Roto Restore:
First flash the data back:
Code:
adb push data.tar.gz /sdcard/data.tar.gz
adb shell su -c "tar -zxvf /sdcard/data.tar.gz"
adb reboot download
Now flash the dumps with Heimdall:
Code:
heimdall flash --kernel zImage --factoryfs factoryfs.rfs --modem modem.bin --cache cache.rfs --dbdata dbdata.rfs --param param.lfs
Of course you could tar the files right n the Tab and flash via Odin if you really want to:
Code:
adb shell
cd /sdcard
tar -cf mybackup.tar cache.rfs dbdata.rfs factoryfs.rfs modem.bin param.lfs zImage
exit
adb pull /sdcard/mybackup.tar .
Nice
This interesting work, im curious though, what is your ultimate goal?
You want a Tmo firmware dump? to what end?
alias_neo said:
This interesting work, im curious though, what is your ultimate goal?
You want a Tmo firmware dump? to what end?
Click to expand...
Click to collapse
The Tmo dump/restore is a test. I want a solid backup/restore and custom rom creation solution.
Fair enough. But is the custom recovery being developed (and progressing nicely) not a solid enough solution?
I won't know till its functional.
rotohammer said:
I won't know till its functional.
Click to expand...
Click to collapse
Do you not have other android devices? I know of none where it doesn't function. So there is no reason i wouldn't wait a little longer for this to be ported.
alias_neo said:
Do you not have other android devices? I know of none where it doesn't function. So there is no reason i wouldn't wait a little longer for this to be ported.
Click to expand...
Click to collapse
A nandroid backup of my rom isn't something I can post publicly on the net. Regardless, I need to create full custom roms that can be flashed using Odin and Heimdall.
rotohammer said:
A nandroid backup of my rom isn't something I can post publicly on the net. Regardless, I need to create full custom roms that can be flashed using Odin and Heimdall.
Click to expand...
Click to collapse
Exactly, you post update.zips and then people use clockwork to flash the full ROM. On device recovery is much better than Odin method and more accessible to noobs that have an aneurism when they see the Odin iterface.
As for dumping your ROM to customise, well, yes, either this way using dd or decrypt the Odin flash files.
Now we're talking:
http://forum.xda-developers.com/showthread.php?t=850995
It sounds like this guy is new to android and iz trying to reinvent the wheel
Sent from my SGH-T849 using XDA App
miketaylor00 said:
It sounds like this guy is new to android and iz trying to reinvent the wheel
Sent from my SGH-T849 using XDA App
Click to expand...
Click to collapse
No, it sounds like he's trying to do exactly what he says he's doing, and that is to recreate the base TMo firmware from DD dumps!
Why? So that if necessary he could return to complete stock if he wished, and because there is no stock TMo image available.
A Nandroid backup doesn't cut the mustard in this case.
Remember guys - just because you don't see a need for something, it doesn't mean that that need doesn't exist for others!
Regards,
Dave
P.S. If you'd read any of Rotohammers posts in these forums, and looked back over previous activity in other sections, you'd know that he's not new to Android at all!
foxmeister said:
No, it sounds like he's trying to do exactly what he says he's doing, and that is to recreate the base TMo firmware from DD dumps!
Why? So that if necessary he could return to complete stock if he wished, and because there is no stock TMo image available.
A Nandroid backup doesn't cut the mustard in this case.
Remember guys - just because you don't see a need for something, it doesn't mean that that need doesn't exist for others!
Regards,
Dave
P.S. If you'd read any of Rotohammers posts in these forums, and looked back over previous activity in other sections, you'd know that he's not new to Android at all!
Click to expand...
Click to collapse
I forgot entirely that the Tab some people have might be carrier customised, mines a generic one so I can flash any of the generic dumps to put it back to "stock".
So yes, a Tmo stock firmware is useful for you guys.
miketaylor00 said:
It sounds like this guy is new to android and iz trying to reinvent the wheel
Click to expand...
Click to collapse
Yes, I am new to Android but I don't enjoy reinventing the wheel.
Perhaps you can point me to the code that I'm re-inventing that you are obviously familiar with?
Thanks in advance!
rotohammer: I've been looking for the ways to dump the firmware like you are suggesting for the AT&T version, mainly because the only available dump is an older version that stock. So far all I've found is this from another post by you:
I would like to get various Vibrant radio dumps if someone would be so kind to do so. The command from adb shell is:
Code:
dd if=/dev/block/bml12 of=/sdcard/bml12.dump bs=4096
Lets discuss what we've tried in this thread.
Click to expand...
Click to collapse
The instructions seem straightforward enough for anyone who has used dd before. How were you able to ascertain the location of this (and other) pieces of the firmware? (Interested to know prior to trying to enable voice on my Tab by swapping modems and reflashing. I'm familiar with Samsung devices since I have a Captivate, but not too reassured that the newest firmware available to restore to is older than launch date.)
The instructions seem straightforward enough for anyone who has used dd before. How were you able to ascertain the location of this (and other) pieces of the firmware? (Interested to know prior to trying to enable voice on my Tab by swapping modems and reflashing. I'm familiar with Samsung devices since I have a Captivate, but not too reassured that the newest firmware available to restore to is older than launch date.)
Click to expand...
Click to collapse
The Tab follows the flash layout of other previous Samsung phones, so just google them, the info is out there. I stare at hexdumps to identify/prove what each partition contains, no big deal.
I feel that once some more official firmware is released all the need for reconstruction of dumps will eliminated.
Figured I'd chime in here from my experience, since I've gone through it with the Epic 4G....
The .rfs files and .lfs files won't restore with redbend... and don't touch bml1 and bml4... that's the boot.bin and sbl.bin... screwing with those can lead to brick...
Current roms for the Epic 4g use update-script or updater-script (different formats, updater-script requires update-binary. The scripts get flashed with clockworkmod... first, system is formatted, then the system files copied over, then permissions given to the files. The kernel is flashed using redbend, along with modem (ours require updater-scripts and a modem_delta file if not using odin).
I browse .rfs system images by first creating a /mnt folder on the sd card. With busybox, use the following command:
Code:
Busybox mount /sdcard/factoryfs.rfs /sdcard/mnt
[/card]
I've gotten the factoryfs.rfs from the stock tars...
Maybe this is reinventing the wheel, but maybe it'll help.
Sent from my SPH-D700 using Tapatalk
rotohammer said:
The Tab follows the flash layout of other previous Samsung phones, so just google them, the info is out there. I stare at hexdumps to identify/prove what each partition contains, no big deal.
I feel that once some more official firmware is released all the need for reconstruction of dumps will eliminated.
Click to expand...
Click to collapse
Gotcha. Thanks. So, for restores, do you use redbend_ua or does a simple reversal of the dd command work? (admittedly this is an area where I haven't quite dug into yet)
maniac3389 said:
Gotcha. Thanks. So, for restores, do you use redbend_ua or does a simple reversal of the dd command work? (admittedly this is an area where I haven't quite dug into yet)
Click to expand...
Click to collapse
You must use redbend_ua, Odin or Heimdall (theres others too). You can't write to these partitions with dd alone, although there is an app that allows you to use dd too.
DRockstar said:
Figured I'd chime in here from my experience, since I've gone through it with the Epic 4G....
The .rfs files and .lfs files won't restore with redbend... and don't touch bml1 and bml4... that's the boot.bin and sbl.bin... screwing with those can lead to brick...
Current roms for the Epic 4g use update-script or updater-script (different formats, updater-script requires update-binary. The scripts get flashed with clockworkmod... first, system is formatted, then the system files copied over, then permissions given to the files. The kernel is flashed using redbend, along with modem (ours require updater-scripts and a modem_delta file if not using odin).
I browse .rfs system images by first creating a /mnt folder on the sd card. With busybox, use the following command:
Code:
Busybox mount /sdcard/factoryfs.rfs /sdcard/mnt
[/card]
I've gotten the factoryfs.rfs from the stock tars...
Maybe this is reinventing the wheel, but maybe it'll help.
Sent from my SPH-D700 using Tapatalk[/QUOTE]
I'll give that a look, don't know why it didn't dawn on me to give a look at the ROMs for my Captivate again. I've looked inside an update.zip file before, but didn't really delve into the script inside.
As for the actual dumping of the images, when dumping the .rfs files, what's the difference between using, say, /dev/block/stl9 versus /dev/block/bml9? Will one work and not the other?
What I'd like to be able to do is dump a current stock AT&T ROM since the one posted is older (and possibly an engineering ROM from what I recall reading.)
My current resources are:
[URL="http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Partitions"]http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Partitions[/URL]
[URL="http://forum.xda-developers.com/showthread.php?t=794425&page=2"]http://forum.xda-developers.com/showthread.php?t=794425&page=2[/URL]
[URL="http://androidforums.com/behold-2-all-things-root/54424-creating-custom-roms-backups-odin.html"]http://androidforums.com/behold-2-all-things-root/54424-creating-custom-roms-backups-odin.html[/URL]
Click to expand...
Click to collapse
rotohammer said:
Why the failure?
Probably because the file systems were still mounted at the time the dumps were made, the zImage partition and the modem partition are not mounted at runtime.
Click to expand...
Click to collapse
Here is a thought, although I may be completely off base:
I noticed that you can access the ADB shell if you boot into stock recovery, perhaps you can mount the SD and dump a few more RFS images?
Yes, just for you!
After 2 weeks of work, I have recreated an Odin package of the stock T-Mobile firmware.
Flash it in Odin from the PDA button, no .pit file, nothing else.
It contains no bootloader because I don't want anyone to brick their device with a bad flashing.
I would like to thank everyone who has helped me, but especially jtc442 and Deodexed.
http://files.deodexed.com/ModADroid-Galaxy-Tablet/T-Mobile/T-Mobile_Stock.zip
Stock T-Mobile modem.bin: View attachment modem-tmo-stock.zip
Congatulations!
A lot of people will appreciate your work, good job!
Thank you
Omg thank you gonna try it out now
Sent from my GT-P1000 using XDA App
Thank you for the hard work Rotohammer!
thanksss : )
i ll keep it as backup plan.
i am using german T mobile firmware now ( it allows phone calls : ) )
Confirmed works great thx roto now time to return it to t-mobile =) and get it from amazon
jay_jay_n said:
Confirmed works great thx roto now time to return it to t-mobile =) and get it from amazon
Click to expand...
Click to collapse
Great, uninstall z4root from the apps too, I didn't try to take that out of the rom since it uninstalls easy enough. Obviously it needed to be installed while we captured the dumps.
Does it allow calls + 3g?
adamq3b85 said:
Does it allow calls + 3g?
Click to expand...
Click to collapse
Nope, its purpose is to revert to the original non-phone firmware with 3G internet only.
rotohammer said:
Yes, just for you!
After 2 weeks of work, I have recreated an Odin package of the stock T-Mobile firmware.
Flash it in Odin from the PDA button, no .pit file, nothing else.
It contains no bootloader because I don't want anyone to brick their device with a bad flashing.
I would like to thank everyone who has helped me, but especially jtc442 and Deodexed.
http://files.deodexed.com/ModADroid-Galaxy-Tablet/T-Mobile/T-Mobile_Stock.zip
Click to expand...
Click to collapse
think you could do this for Sprint firmware?
phonetec said:
think you could do this for Sprint firmware?
Click to expand...
Click to collapse
I could if someone was willing to do the dumps for me.
If you can explain how to do the 'dumps' for our Sprint SGT and send them to you please explain so I can help. When doing this is any of my information transfered to you?
Can you please tell me what this firmware can do that the stock firmware does not?
vkuber said:
If you can explain how to do the 'dumps' for our Sprint SGT and send them to you please explain so I can help. When doing this is any of my information transfered to you?
Click to expand...
Click to collapse
Its best to do this after a factory reset from recovery (Up & power on), so theres no personal info in any of the dumps. the efs.rfs file contains you imei info, you want to keep that to yourself.
Dumping all your firmware:
cd android-sdk/tools (use your location)
adb shell
su
dd if=/dev/block/bml1 of=/sdcard/boot.bin bs=4096
dd if=/dev/block/bml2 of=/sdcard/pit.pit bs=4096
dd if=/dev/block/stl3 of=/sdcard/efs.rfs bs=4096
dd if=/dev/block/bml4 of=/sdcard/Sbl.bin bs=4096
dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096
dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096
dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096
dd if=/dev/block/bml12 of=/sdcard/modem.bin bs=4096
exit
exit
adb pull /sdcard/param.lfs .
adb pull /sdcard/zImage .
adb pull /sdcard/factoryfs.rfs .
adb pull /sdcard/dbdata.rfs .
adb pull /sdcard/cache.rfs .
adb pull /sdcard/modem.bin .
adb pull /sdcard/efs.rfs .
adb pull /sdcard/boot.bin .
adb pull /sdcard/Sbl.bin .
adb pull /sdcard/pit.pit .
At this point you computer will have all the files.
rotohammer said:
Its best to do this after a factory reset from recovery (Up & power on), so theres no personal info in any of the dumps. the efs.rfs file contains you imei info, you want to keep that to yourself.
Dumping all your firmware:
cd android-sdk/tools (use your location)
adb shell
su
dd if=/dev/block/bml1 of=/sdcard/boot.bin bs=4096
dd if=/dev/block/bml2 of=/sdcard/pit.pit bs=4096
dd if=/dev/block/stl3 of=/sdcard/efs.rfs bs=4096
dd if=/dev/block/bml4 of=/sdcard/Sbl.bin bs=4096
dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096
dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096
dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096
dd if=/dev/block/bml12 of=/sdcard/modem.bin bs=4096
exit
exit
adb pull /sdcard/param.lfs .
adb pull /sdcard/zImage .
adb pull /sdcard/factoryfs.rfs .
adb pull /sdcard/dbdata.rfs .
adb pull /sdcard/cache.rfs .
adb pull /sdcard/modem.bin .
adb pull /sdcard/efs.rfs .
adb pull /sdcard/boot.bin .
adb pull /sdcard/Sbl.bin .
adb pull /sdcard/pit.pit .
At this point you computer will have all the files.
Click to expand...
Click to collapse
Hi Rotohammer:
Congratulations on creating the stock rom for T-mobile.
If I pull the files from a Tab for Bell (provider in Canada), would you please be able to create a stock ROM for this?
Thanks.
T33H00 said:
Can you please tell me what this firmware can do that the stock firmware does not?
Click to expand...
Click to collapse
Absolutely nothing! It is IS the stock firmware.
mv3900 said:
Hi Rotohammer:
Congratulations on creating the stock rom for T-mobile.
If I pull the files from a Tab for Bell (provider in Canada), would you please be able to create a stock ROM for this?
Thanks.
Click to expand...
Click to collapse
Sure, no problem.
Does this mean it's now possible to extract the radio firmware for those of us who used the Russian/European method to get to JK5? I'm not using mine for calls at the moment, it would be nice to have both radio files on hand to flash when needed until we get a 3G+Phone type driver.
martin0641 said:
Does this mean it's now possible to extract the radio firmware for those of us who used the Russian/European method to get to JK5? I'm not using mine for calls at the moment, it would be nice to have both radio files on hand to flash when needed until we get a 3G+Phone type driver.
Click to expand...
Click to collapse
Nope, you could always do that. Just flash back the stock modem.bin (I'm assuming you're on T-Mobile). Modem (radio) files were the one thing that was easy to swap around.
rotohammer said:
Sure, no problem.
Click to expand...
Click to collapse
Hi Roto.
I've pulled the files for Bell. How do I get them to you?
Thanks.
So I installed CM9 nightly and then after a day went back to stock stock.
Did all the copy .img to sd card, using ubuntu did adb shell, su and then dd for all the if and ofs and after I did a hard reset, I don't have LTE anymore!
Everything on the phone works perfect but LTE. I even took it to AT&T store and they had no idea. They changed sim and everything. My sim in other phones get LTE but not in this LG Nitro HD returned to stock from all the img's.
My phone shows:
Model number: LG-P930
Android version 2.3.5
Baseband version P930-MDM9200B-V10f-OCT-31-2011-XX 1 [Oct 21 2011 18:50:29]
Kernel version 2.6.35.11 +
Build number GRJ90
Software version: LG-P930-V10f-OCT-31-2011
Any clues as to what might be wrong or if anyone else is having the same issues?
Thank you.
Edit:
I've done back to stock all 5 images 4 to 5 times and hard reset after every single one.
Edit again:
Just did it again, installed CWM from ROM Manager, did wipe data, cache, dalvik cache.
Went back to stock by dd all images to the phone then turn it off and hard reset and still no LTE.
When I went back to stock from other roms, it worked just fine just not after CM9 when I try to use AT&T PTA APN to get LTE to work. Could it be that I blew something LTE related trying to use LTE in CM9?
Thanks to zombie.raised http://forum.xda-developers.com/member.php?u=780649 for his method mentioned here:
http://forum.xda-developers.com/showpost.php?p=22183407&postcount=7
*Solution*
1. Once you go back to stock rom.
2. Go to the dialer and type in *#*#4636#*#*
3. You will be taken to a menu
4. Go into Phone information
5. Scroll down to the button that says Turn off radio
6. Turn the radio off and then turn it back on
7. ?
8. Profit?
Have you tried the LTE APN settings?
http://forum.xda-developers.com/showpost.php?p=20927392&postcount=6
ok, i restored my original at&t rom and also cannot get an lte signal. i confirmed those apn settings and live in an lte area.
scott0 said:
ok, i restored my original at&t rom and also cannot get an lte signal. i confirmed those apn settings and live in an lte area.
Click to expand...
Click to collapse
Post a radio logcat (adb logcat -b radio -v time), preferrably taken from boot (start logcat first, boot phone second)
aremcee said:
Post a radio logcat (adb logcat -b radio -v time), preferrably taken from boot (start logcat first, boot phone second)
Click to expand...
Click to collapse
I'm not where I can get this done right now.
OP, can you handle this for aremcee?
I am having the same issues. I have just been waiting for someone else to confirm. I have completed all the steps as you have and am still unable to get the LTE back.
I have the exact problem, i think the basebase got damaged by CM9.
dualmax said:
I have the exact problem, i think the basebase got damaged by CM9.
Click to expand...
Click to collapse
CM doesn't touch the baseband. It's some configuration, I just need to figure out why, and nobody's provided a log yet.
Preliminary question: How are you all resetting? From recovery (using Power+Vol counts as recovery), or using stock's own "Factory Reset" option?
I apologize, i cannot provide that log. Could one of y'all who has the lte issue run that for Ricardo?
I am resetting via rom manager backup.
aremcee said:
Post a radio logcat (adb logcat -b radio -v time), preferrably taken from boot (start logcat first, boot phone second)
Click to expand...
Click to collapse
I am sorry, I just got back home...it's been a very busy day.
I am literally a noob when it comes to logcat. So from my understanding, these are the steps I follow?
1. Run adb logcat -b radio -v time
2. Turn off the phone, turn it on and then plug it in using USB while adb says waiting for device?
3. Look for logcat in adb folder?
4. ?
5. Profit?
Thank you in advance. I went to device support center and they will mail me a new one but I'd be more than happy to help fix this issue before moving on to the refurbished unit
Edit: I think I figured it out.
I just attached the logcat.txt file.
Thank you!!
Edit 2:
Try 2 is the file that I waited a little longer for phone to settle and unlocked the screen before stopping.
Thank you.
For anyone else that wants to try it, this is what I did.
1. Turn the phone off.
2. Open up cmd prompt and go to adb folder it you don't have path set.
3. Run adb logcat -b radio -v time > logcatTry2.txt
4. Turn phone on and connect to laptop but make sure you had usb debugging enabled.
5. Once phone boots up all the way and you think you are all set, you can stop it and get the txt file from adb folder.
Thank you.
noobsquared said:
I am sorry, I just got back home...it's been a very busy day.
I am literally a noob when it comes to logcat. So from my understanding, these are the steps I follow?
1. Run adb logcat -b radio -v time
2. Turn off the phone, turn it on and then plug it in using USB while adb says waiting for device?
3. Look for logcat in adb folder?
4. ?
5. Profit?
Thank you in advance. I went to device support center and they will mail me a new one but I'd be more than happy to help fix this issue before moving on to the refurbished unit
Click to expand...
Click to collapse
This happened to me too, I did make a backup of my stock att rom rooted of course...anyways, coming back from cm9, I reflashed hono rom most recent version with kernel in it...then I booted it from there, u should have lte..after that I restored my stock rom...and inwas able to get lte again...try this method and see if it works for u
Sent from my LG-P930 using xda premium
thx noobsquared! And who knows, this could be a clue to help get LTE going in the cm9 eh...............
kumayam said:
This happened to me too, I did make a backup of my stock att rom rooted of course...anyways, coming back from cm9, I reflashed hono rom most recent version with kernel in it...then I booted it from there, u should have lte..after that I restored my stock rom...and inwas able to get lte again...try this method and see if it works for u
Sent from my LG-P930 using xda premium
Click to expand...
Click to collapse
Okay, you were very convincing. I just installed Hono rom with kernel with it.
It says H+ right now. Is H+ the icon for LTE? If not then I think backup would have been the key to get LTE back. I'll keep everyone posted.
H+ is not LTE. That's like 3.5G afaik.
Malnilion said:
H+ is not LTE. That's like 3.5G afaik.
Click to expand...
Click to collapse
Yes. Thank you.
I just went in the phone about me and cheked. It's only getting HSPA.
No more LTE for me
I think I will return it back to stock and send it back to LG/AT&T
Edit:
Trying going back to stock, this is what happened:
su
# dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
20480+0 records in
20480+0 records out
10485760 bytes transferred in 3.688 secs (2843210 bytes/sec)
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
32768+0 records in
32768+0 records out
16777216 bytes transferred in 5.613 secs (2988992 bytes/sec)
# dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
65536+0 records in
65536+0 records out
33554432 bytes transferred in 2.242 secs (14966294 bytes/sec)
# dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
1048576+0 records in
1048576+0 records out
536870912 bytes transferred in 153.581 secs (3495685 bytes/sec)
# dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
[1] Segmentation fault dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p1
4
# dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
[1] Segmentation fault dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p1
4
Turns out the phone turned itself off and now after a hard reset, it's back online.
I will run the commands again to make sure they all went through but I still don't see LTE.
I think that's enough bugging everyone for the night.
Thank you for everyones' help.
hey good news, i bricked my original p930 a couple months ago and have been running a replacement/refurb, it's just as kcik ass as the 1st one.
and isn't att pretty good handling the exchange? I thought so.
kumayam said:
This happened to me too, I did make a backup of my stock att rom rooted of course...anyways, coming back from cm9, I reflashed hono rom most recent version with kernel in it...then I booted it from there, u should have lte..after that I restored my stock rom...and inwas able to get lte again...try this method and see if it works for u
Sent from my LG-P930 using xda premium
Click to expand...
Click to collapse
Worked for me!! Thanks!
Kernelpan1c post this a little while ago:
http://forum.xda-developers.com/showpost.php?p=24379141&postcount=440
Hope it helps.
Worked for me to. I flashed HONO ROM with custom kernel after full wipe, then restored my stock rooted nandroid. I have a note out to RC to see what specific logcat scenarios he wants run.
dnorthington said:
Worked for me to. I flashed HONO ROM with custom kernel after full wipe, then restored my stock rooted nandroid. I have a note out to RC to see what specific logcat scenarios he wants run.
Click to expand...
Click to collapse
Something's strange about this. I just downloaded that ROM and it's your typical cooked stock, nothing major different from the original.
There's one significant difference there: it derives from Bell's stock, not AT&T's. Has anyone tried flashing the Bell stock ROM to see if it has the same LTE-healing effect?
For some reason the I747M.DLL does not work correctly and Im pretty sure about this. If you use the I747M.DLL you will not have Download Mode. I know how to fix this but need SBL1.MBN specifically from Claro PR Unit and Im 100% Sure this one will work in any other USA/Canada Versions. Then for the others SBL2,SBL3,TZ,RPL & ABOOT they are on the stock I747MUMBLL1. Some one can try to make debrick.img from a working I747M rooted with this instructions and also make a backup of .PIT cuz are not the same.
This is the Most Important a Backup of a Good/Working Unit SBL1.MBN, Phone has to be rooted to extract it.
su
dd if=/dev/block/mmcblk0p2 of=/sdcard/sbl1 bs=4096
This is the Second Most Important a Backup of a Good/Working Unit OUT.PIT file, Phone has to be rooted to extract it.
su
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=481 skip=2176
This is for make a Recovery SDC Card:
su
dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128
I already see a lot of Extremely Problems with the I747M Units that is why Im posting this to try between us and fix this situation. The I747M.DLL Is not working as expected. I already have 2 units that show the Qualcomm Hub and dont have Download nor Recovery Menu Available. Yes the units are completly full bricked so for me was useless to make a backup of first 128MBs I need a backup from an Actual Working I747M from Claro PR.
BRs,
Luis Daniel
anyone who can help?
i need the one of 4.4.2
i really screwed up my d850 att g3. found this on a forum. and it fixed my bootloop. flash tool didnt work for me.
Found this on AndroidCentral: Saved my life – it got my phone back to original. Hope this helps others.
*****************************************************************************************************************
What worked for me was from the TWRP terminal command was to type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
it booted up to last rom i put on phone.
jaybird38 said:
i really screwed up my d850 att g3. found this on a forum. and it fixed my bootloop. flash tool didnt work for me.
Found this on AndroidCentral: Saved my life – it got my phone back to original. Hope this helps others.
*****************************************************************************************************************
What worked for me was from the TWRP terminal command was to type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
it booted up to last rom i put on phone.
Click to expand...
Click to collapse
I belive your commands are incomplete.
dd command basically copies something. "if" stands for input file. What you miss is "of" which stands for output file. Could you provide me with a link to your source thread?
i copied it exactly and my phone booted up right after reboot. i tried flash tool around 50 times on 2 computers and different cables and ports
http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
comment about half way down
If you say so... You could look up dd command or test it for yourself. What you or that guy copied is incomplete, idk how it worked.
Found that comment as well, he says he found it somewhere, no source thread there either.
it did work for me. thats all i can say. i don't know anything about command files.i was trying to get phone out of bootloop for 8 hours. seen this comment tried it and now my phone is working with my last rom i put on it which is cyanide.
found the original post.
http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html
comment #5.