Develop Bugs

T-Mobile stock firmware!

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.

Gordita Root: Optimus V exploit March 24th 2012

This is an exploit, I take NO RESPONSIBILITY if this does ANYTHING bad, your fault not mine, it was only tested on the firmware mentioned below. If you redistribute it, republish, work it into a all in one click, please link back and PROPERLY credit me.
Tested on the
ro.build.date=Mon Jan 30 10:42:53 KST 2012
ro.build.version.incremental=ZV9.479A6632
Update for the VirginMobile LG Optimus V
Your phone needs to be updated to the above build, and potentially needs a factory reset before this works, but it works fine. This will allow you to flash recovery without being root. After flashing recovery, flash this zip http://dl.dropbox.com/u/8699733/rootme.zip to install su, superuser and disable re-flashing of the stock re covery
LinuxMac Script + files:
https://github.com/CunningLogic/GorditaRoot
Flash_image:
https://github.com/CunningLogic/GorditaRoot/blob/master/flash_image
Recovery:
http://www.mediafire.com/?vzc5k8taj9smmll (Credit BobZhome)
Windows users run the commands manually
GNU nano 2.2.2 File: Gordita.sh
Code:
#!/bin/sh
echo "GorditaRoot 1.0 by jcase / TeamAndIRC"
echo "for the VM670 Optimus V"
echo "March 21st 2012"
echo "Follow me! http://www.twitter.com/TeamAndIRC"
echo "Donations are optional http://forum.xda-developers.com/donatetome.php?u=2376614"
echo "-"
echo "Recovery taken from http://forum.xda-developers.com/showthread.php?t=1197991"
echo "-"
echo "Pushing recovery to /data/local/"
adb push VM670NH_recovery.img /data/local/recovery.img
adb push flash_image /data/local/
adb shell "chmod 755 /data/local/flash_image"
echo "Removing old sensor config, setting up symlink attack"
adb shell "rm /data/amit/*"
adb shell "ln -s /dev/mtd/mtd2 /data/amit/AMI304_Config.ini"
adb shell "ln -s /dev/mtd/mtd2 /data/amit/AMI304_Config2.ini"
echo "Rebooting to execute symlink attack, to chmod 666 the recovery block device"
adb reboot
adb wait-for-device
sleep 10
adb shell "rm /data/amit/*"
adb shell "/data/local/flash_image recovery /data/local/recovery.img"
echo "Recovery flashed! Enjoy"
Having trouble identifying whether or not you completed the root process? Quickly test for root access with Root Checker Basic

Confirmed working on a phone donated just for this purpose!
Started with stock firmware, Android 2.2.1, baseband VM670ZV4_60401001, generic android recovery
Flashed the VirginMobile Security Update from their website, became VM670ZV9_60401001 ZV9.479A6632
Manually walked through above script by jcase via gtalk, and using the exploit, was able to flash BobZhome's CWM for the VM670, reboot into it and made a backup.
Flashed the su zip, and all is well in Optimus V land again.
HUGE THANKS TO JCASE FOR TAKING THE TIME TO RE-ROOT THE VM670!!!

I only wish I understood what it all meant--so I could be excited, too!

wilberfan said:
I only wish I understood what it all meant--so I could be excited, too!
Click to expand...
Click to collapse
Means ppl who couldnt root before, now can

wilberfan said:
I only wish I understood what it all meant--so I could be excited, too!
Click to expand...
Click to collapse
i was gonna ask the same thing LOL

Hey! Sorry, I'm a ET4G user, just trying to put ICS on my girl's phone so she stops whining
Anyways, I presume there's an update being pushed to all optimus v's? If so would you happen to know how I could update hers? Or would it be easier to stay on the current version ( i belive v5???) and root a different way??
Also, great work on an exploit so soon after a release! Happy to join (kinda) the Optimus family!

jlear3 said:
Hey! Sorry, I'm a ET4G user, just trying to put ICS on my girl's phone so she stops whining
Anyways, I presume there's an update being pushed to all optimus v's? If so would you happen to know how I could update hers? Or would it be easier to stay on the current version ( i belive v5???) and root a different way??
Also, great work on an exploit so soon after a release! Happy to join (kinda) the Optimus family!
Click to expand...
Click to collapse
The update is not being pushed, because the OTA mechanism doesn't work on the OV. You have to go to the VM website and download the update from the phone FAQ.
The only advantage is a new radio, which give slightly improved performance.

Thank you very much!
I installed the update to my (unmodded) backup phone without thinking about whether or not I'd be able to root the handset after applying it. DOH!
I have just been using this phone as a WiFi device so far. I have run the battery down and recharged it once and installed a few apps on it. So I will run it down, recharge it again and then do a factory reset before I try rooting it just to make sure that I don't hose it.

It's a good idea to check all the steps before you start ...
Finally ran my battery down for the second time. So, I recharged, ran a factory re-set and ran the shell script on my Linux box to root the phone.
Oops!
The file VM670NH_recovery.img downloaded as VM670NH_recovery.bin and the system can't find/stat it! Hit ^C and bailed!
Hoping, hoping, hoping ...
Good! It's not bricked!
Renamed the recovery file, re-ran the script. Success!!
Rebooted into recovery, flashed rootme.zip
==> Did a nandroid backup.
Downloaded root check basic app and confirmed that it has worked.
So, for other modders trying this out:
Check your files and file names before you start! When I looked at Gordita.sh the first time I found that what I had downloaded was an HTML file with the script embedded in it. Copied and pasted from the OP and then checked again to make sure I had the right content.
Of course if you are running the adb commands manually then this won't happen to you.
But, as I noted above, I didn't cross-check that the recovery file that the script would be looking for had the right file name extension (.img, not .bin), so don't be me.
That said, jcase: Thank You Very Much!! Not only for developing this root exploit but also for making one that is robust enough for someone like me to goober it up and still come out unburnt!

After all of this , can you make it a hotspot in quick settings?

The setting dialog is there ..
H0daddy said:
After all of this , can you make it a hotspot in quick settings?
Click to expand...
Click to collapse
Once I rooted my phone I installed a modified ROM. And then another one, and then ...
I saw your question a bit ago and since I no longer had the stock ROM installed (and had never used Quick Settings to enable the hotspot feature before) I didn't know. I still don't. Here is the story on that ...
I just restored the ZV9 ROM from backup today and then installed the Quick Settings app. I can say that the app still has the option to enable the hotspot available and that it tries to set it up. However the phone I am using hasn't been activated yet and the 3G network isn't provisioned on it. So all I get is a message saying the network isn't available.
So, it looks somewhat promising. Maybe someone who has an activated phone with the ZV9 ROM can test it out and let you know.
And if I activate this phone before you get a useful reply I'll test it to see if it works.

So happy to see this

Please assist
Got up to step adb shell "chmod 755 /data/local/flash_image"
But got back "no such file."

CWM
Got up to CWM but it won't let me select install zip from sd card. Any suggestions?

knicks791 said:
Got up to CWM but it won't let me select install zip from sd card. Any suggestions?
Click to expand...
Click to collapse
so you have bobz recovery installed?... i assume youve tried rebooting to recovery form the powered off state via the key combo (HOLD home+vol down+power, RELEASE after the LG logo), and tried instal zip from sd again?...
try:
http://forums.projectopencannibal.net/beta-releases-11/lg-optimus-v-v2-1dev1-(10-09-2012)/
http://forums.projectopencannibal.n...1-universal-installer-for-lg-optimus-devices/

[Q] Kindle Fire 2 - Black Screen / No LED /Brick?

HI All,
i have a major problem hoping one of you might be able to give me a little help. I looked through tons of posts and threads however have trouble finding an answer.
I rooted my Kindle fire 2. No Problem here. However I have been experiencing severe problmes in installing a bootloader or a recovery. So after clicking my way trough the internet and trying nearly every method there is i came to this one:
i executed the follwing commands over adb (yes adb was working fine)
adb shell
su
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/mmcblk0p5
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
getting the follwowing output
D:\.android>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p5
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p5
/dev/block/mmcblk0p5: write error: No space left on device
129+0 records in
128+0 records out
65536 bytes transferred in 0.038 secs (1724631 bytes/sec)
1|[email protected]:/ # dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
422+1 records in
422+1 records out
216164 bytes transferred in 0.097 secs (2228494 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ $ reboot
reboot
reboot: Operation not permitted
1|[email protected]:/ $ adb reboot
adb reboot
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $ exit
exit
D:\.android>adb reboot
So after rebooting nothing happens. The screen just stays black. I get no LED when i plug the device into the pc or charger. I even tried hardrestes (pressing the button for 20 sec) but nothing. Adb wont work anymore and iam slowly starting to get frustrated. I know I should not have tried a method other than the ones discussed in this forum but after trying so much even goomanager did not work i just though "**** it" lets give it a go. So here I am. Bricked device and not a clue what to do. I also tried the Kindle Fire Unbrick Utility V1.1!
I am running win XP Pro or Mac OS whatever is better to get this sorted out. I am looking forward to hearing from you.
Your desperate Androidschima

Just as a start- do you have a kindle fire TWO?
1. The recovery you flashed isn't correct
2. The kindle fire UNBRICK tool doesn't exist for this device.
3. I'm pretty sure the partition structure you are using is from a different device also.
4. No idea what u-boot.bin is... Doesnt apply to this device
5. Goomanager WONT work.... Our recovery isnt there
Essentially it looks like you flashed the wrong TWRP to the wrong partition.
As of right now.... I dont think it cam be fixed with the tools we have.
The only thing i can suggest is to use a fastboot cable and hope it goes into fastboot mode... But i have a feeling that wont work
--
Sent from my Kindle Fire 2, CM 10.1

mindmajick said:
Just as a start- do you have a kindle fire TWO?
1. The recovery you flashed isn't correct
2. The kindle fire UNBRICK tool doesn't exist for this device.
3. I'm pretty sure the partition structure you are using is from a different device also.
4. No idea what u-boot.bin is... Doesnt apply to this device
Essentially it looks like you flashed the wrong TWRP to the wrong partition.
As of right now.... I dont think it cam be fixed with the tools we have.
--
Sent from my Kindle Fire 2, CM 10.1
Click to expand...
Click to collapse
Im pretty sure it is a KF2. It was shipped at xmas 2012. I used openrecovery-twrp-2.4.1.0-blaze.img to flash.
Any chance if i get a factory cable?

androidschima said:
Im pretty sure it is a KF2. It was shipped at xmas 2012. I used openrecovery-twrp-2.4.1.0-blaze.img to flash.
Any chance if i get a factory cable?
Click to expand...
Click to collapse
WHERE did you get the recovery? Not from the kf2 forums for sure.
Maybe with a factory cable, but i think you trashed the partitions by using the wrong ones.. Maybe for the kf1? Its possible you may have overwritten fastboot
Edit: IF you get it working again there are TWO and ONLY two methods to put recovery on our device. I recommend the first one.
1. http://forum.xda-developers.com/showthread.php?t=2106463
2. http://forum.xda-developers.com/showthread.php?t=2100963
Edit2: and here is a link to others that did something's similar:
http://forum.xda-developers.com/showthread.php?t=2141914
Edit3: and HERE is the info you need to restore back to stock IF you can get in to fastboot.
http://forum.xda-developers.com/showthread.php?t=2096888
--
Sent from my Kindle Fire 2, CM 10.1

mindmajick said:
WHERE did you get the recovery? Not from the kf2 forums for sure.
Maybe with a factory cable, but i think you trashed the partitions by using the wrong ones.. Maybe for the kf1? Its possible you may have overwritten fastboot
Edit: IF you get it working again there are TWO and ONLY two methods to put recovery on our device. I recommend the first one.
1. http://forum.xda-developers.com/showthread.php?t=2106463
2. http://forum.xda-developers.com/showthread.php?t=2100963
Edit2: and here is a link to others that did something's similar:
http://forum.xda-developers.com/showthread.php?t=2141914
Edit3: and HERE is the info you need to restore back to stock IF you can get in to fastboot.
http://forum.xda-developers.com/showthread.php?t=2096888
--
Sent from my Kindle Fire 2, CM 10.1
Click to expand...
Click to collapse
Thank you ever so much for your fast reply. I will look into the mentioned links! Thanks a million!

:) Re: [Q] Kindle Fire 2 - Black Screen / No LED /Brick?
androidschima said:
Thank you ever so much for your fast reply. I will look into the mentioned links! Thanks a million!
Click to expand...
Click to collapse
Don't waste your time.
Besides not doing the appropriate amount of research before attempting to modify your device (ahem), here's where you went wrong...
androidschima said:
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
Click to expand...
Click to collapse
You flashed an unsigned bootloader on a High Security OMAP device, therefore, you are pretty much out of options.

soupmagnet said:
Don't waste your time.
Besides not doing the appropriate amount of research before attempting to modify your device (ahem), here's where you went wrong...
You flashed an unsigned bootloader on a High Security OMAP device, therefore, you are pretty much out of options.
Click to expand...
Click to collapse
That's kind of what I thought too... Glad to have an expert confirm it, but sorry dude is SOL.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Time to RMA
mindmajick said:
That's kind of what I thought too... Glad to have an expert confirm it, but sorry dude is SOL.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Sounds like it is time to send it back to Amazon. That is pretty bricked.

soupmagnet said:
Don't waste your time.
Besides not doing the appropriate amount of research before attempting to modify your device (ahem), here's where you went wrong...
You flashed an unsigned bootloader on a High Security OMAP device, therefore, you are pretty much out of options.
Click to expand...
Click to collapse
Any Chance of Amazon finding out that i acted like a noob dumb ass and bricked my device?
If no - i still could send it back could i not?

Just ship it back. usually amazon will send out a new one. Just say it doesn`t come on when you try to start it..

Help i bricked my f240k!! And my imei and model number is gone on the phone

1 ok using olleh f240k
2 flash singapore 988 rom on it
3 was ok but no network and some how my imei and model is not found in info
4 use lg support tool to do stock recovery
5 phone back to olleh stock firmware but still no network and got glish with some app
6 do 3 to 4 times of factory reset (still the same
7 try a couple of time flash stock olleh rom until the last try it stop half way and brick
8 now cant on my f240k but only can on to download mode only
9 still can be detected by pc and lg software soo try reinstall and recovery install hailf way 30% to 70% then it stop and say that lost connection on phone ect.....
Soo now my f240k lost its imei number and model number and only can on to download mode
pls helpppp
how do i recover my imei when i can get to the android os on my phone or is ther any onther way to fix this ???

boiflame said:
1 ok using olleh f240k
2 flash singapore 988 rom on it
3 was ok but no network and some how my imei and model is not found in info
4 use lg support tool to do stock recovery
5 phone back to olleh stock firmware but still no network and got glish with some app
6 do 3 to 4 times of factory reset (still the same
7 try a couple of time flash stock olleh rom until the last try it stop half way and brick
8 now cant on my f240k but only can on to download mode only
9 still can be detected by pc and lg software soo try reinstall and recovery install hailf way 30% to 70% then it stop and say that lost connection on phone ect.....
Soo now my f240k lost its imei number and model number and only can on to download mode
pls helpppp
how do i recover my imei when i can get to the android os on my phone or is ther any onther way to fix this ???
Click to expand...
Click to collapse
item 9 above, probably best is to try change your cable and reflash stock firmware.
NOTE: after you reflash and able to bootup the phone.... it probably will have 2 issue
1) imei not found and unable to connect to your mobile provider
2) your storage will show only 16GB
IMPORANT: did u do backup for the below block partition ? IF NOT, guess you can only use the phone as tablet.
adb.exe shell su -c "mkdir /sdcard/System/"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p12 of=/sdcard/System/12m9kefs1.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p13 of=/sdcard/System/13m9kefs2.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p15 of=/sdcard/System/15DRM.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p22 of=/sdcard/System/22eksst.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p21 of=/sdcard/System/21encrypt.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p26 of=/sdcard/System/26persist.img"

silentdrum said:
item 9 above, probably best is to try change your cable and reflash stock firmware.
NOTE: after you reflash and able to bootup the phone.... it probably will have 2 issue
1) imei not found and unable to connect to your mobile provider
2) your storage will show only 16GB
IMPORANT: did u do backup for the below block partition ? IF NOT, guess you can only use the phone as tablet.
adb.exe shell su -c "mkdir /sdcard/System/"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p12 of=/sdcard/System/12m9kefs1.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p13 of=/sdcard/System/13m9kefs2.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p15 of=/sdcard/System/15DRM.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p22 of=/sdcard/System/22eksst.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p21 of=/sdcard/System/21encrypt.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p26 of=/sdcard/System/26persist.img"
Click to expand...
Click to collapse
ok I got it working again soo I do not have a back up anyway to fix the network and imei?

There is an app for reinstating imei numbers in the gs3 forum but I don't know if it would work for you.
Sent from my LG-E980 using xda app-developers app

boiflame said:
ok I got it working again soo I do not have a back up anyway to fix the network and imei?
Click to expand...
Click to collapse
1) fast method
probably u can ask ppl with backup of the 240K to send u those backup files
NOTE: if restore from other ppl's backup file you will probably have the same IMEI as the person send u his backup files.
2) long tedios method
its kinda hard to explain here .. but involved using QPST, pull out or backup a .qcn file from your phone and manual edit the IMEI then push it back into your phone.
its a long shots.... but worth a try.
if your phone now still showing 16GB, u can have the 32gb back by formatting the partition.
adb shell
su
stop
/sbin/make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/userdata
reboot
NOTE: above command basically will
1) get adb shell
2) login root shell
3) stop/freeeze the system
4) formate the userdata using ext4 (note all of userdata will be gone)
5) reboot the phone
after reboot you should able to see back the 32gb storage.

merinko was
silentdrum said:
1) fast method
probably u can ask ppl with backup of the 240K to send u those backup files
NOTE: if restore from other ppl's backup file you will probably have the same IMEI as the person send u his backup files.
2) long tedios method
its kinda hard to explain here .. but involved using QPST, pull out or backup a .qcn file from your phone and manual edit the IMEI then push it back into your phone.
its a long shots.... but worth a try.
if your phone now still showing 16GB, u can have the 32gb back by formatting the partition.
adb shell
su
stop
/sbin/make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/userdata
reboot
NOTE: above command basically will
1) get adb shell
2) login root shell
3) stop/freeeze the system
4) formate the userdata using ext4 (note all of userdata will be gone)
5) reboot the phone
after reboot you should able to see back the 32gb storage.
Click to expand...
Click to collapse
my fone show 32 gb only network and imei

Trouble Restoring Backed Up Stock ROM & WiFi Won't connect using LOS 15.1

Most of my the question/topic was explained here.
@steadfasterX
Re the WiFi pls share also the boot logs (see LOS faq).
Click to expand...
Click to collapse
I couldn't pull a boot log from TWRP, I'd get "Sbin/sh: adb: not found". That output seems to be haunting a lot of my adb attempts, it appears when I try "adb sync" as well.
Ok the choose "format" data in twrp and try to boot first without your userdata backup into stock. Lemme know if that works.
Click to expand...
Click to collapse
I tried, I unfortunately get a solid wall of bootloop. I still have everything from my SALT backup in case anything may or may not be needed. I just had a though, could the problem be that this backup was from before I USUed my phone (I can't remember if I said that in the first place)?

emperordogma said:
Most of my the question/topic was explained here.
@steadfasterX
I couldn't pull a boot log from TWRP, I'd get "Sbin/sh: adb: not found". That output seems to be haunting a lot of my adb attempts, it appears when I try "adb sync" as well.
I tried, I unfortunately get a solid wall of bootloop. I still have everything from my SALT backup in case anything may or may not be needed. I just had a though, could the problem be that this backup was from before I USUed my phone (I can't remember if I said that in the first place)?
Click to expand...
Click to collapse
The confusing part is we talk about 2 different things here:
1) WiFi. This is related to LOS and so when asking for logs l always assume you're on LOS. TWRP must match the LOS version.
2) booting stock. To make TWRP work it must be the matching TWRP installed of your stock release. Is that the case? If not do that first.
So re stock. Its strange that it does not boot with formatted data. Could you also flash magisk here and then try to boot?

steadfasterX said:
The confusing part is we talk about 2 different things here:
1) WiFi. This is related to LOS and so when asking for logs l always assume you're on LOS. TWRP must match the LOS version.
2) booting stock. To make TWRP work it must be the matching TWRP installed of your stock release. Is that the case? If not do that first.
So re stock. Its strange that it does not boot with formatted data. Could you also flash magisk here and then try to boot?
Click to expand...
Click to collapse
1) I'll worry about the WiFi if/when I can get stock up and running. But I was/am using LOS 15.1 (here's the version "lineage-15.1-20210608-UNOFFICIAL-h812_usu"), and my TWRP was "twrp-3.4.0-PREVIEW-230_g4_O".
2) I downgraded my TWRP to "twrp-3.3.1-PREVIEW-196_g4_MM", and same result, I get to the LG screen and the notification light stays on, then nothing. When inputting these dd commands:
Code:
adb shell
dd if=/external_sd/boot.img of=/dev/block/bootdevice/by-name/boot bs=512
dd if=/external_sd/system.img of=/dev/block/bootdevice/by-name/system bs=4096
dd if=/external_sd/userdata.img of=/dev/block/bootdevice/by-name/userdata bs=4096
adb shell sync
When I put "adb shell sync" in I get "/sbin/sh: adb: not found"
I tried clearing the cache after I put it in, then tried formatting, as well as tried installing Magisk. And when mounting the data partition, everything seem to be there (hard to tell exactly since it's not the way I'm used to seeing it).
Edit: I just tried getting a boot log using:
Code:
adb pull /cache/debug/boot_lc_crash.txt
adb pull /cache/debug/boot_lc_full.txt
adb pull /cache/debug/boot_lc_kernel.txt
And the first one comes back with /sbin/sh: adb: not found

emperordogma said:
1) I'll worry about the WiFi if/when I can get stock up and running. But I was/am using LOS 15.1 (here's the version "lineage-15.1-20210608-UNOFFICIAL-h812_usu"), and my TWRP was "twrp-3.4.0-PREVIEW-230_g4_O".
2) I downgraded my TWRP to "twrp-3.3.1-PREVIEW-196_g4_MM", and same result, I get to the LG screen and the notification light stays on, then nothing. When inputting these dd commands:
Code:
adb shell
dd if=/external_sd/boot.img of=/dev/block/bootdevice/by-name/boot bs=512
dd if=/external_sd/system.img of=/dev/block/bootdevice/by-name/system bs=4096
dd if=/external_sd/userdata.img of=/dev/block/bootdevice/by-name/userdata bs=4096
adb shell sync
When I put "adb shell sync" in I get "/sbin/sh: adb: not found"
I tried clearing the cache after I put it in, then tried formatting, as well as tried installing Magisk. And when mounting the data partition, everything seem to be there (hard to tell exactly since it's not the way I'm used to seeing it).
Edit: I just tried getting a boot log using:
Code:
adb pull /cache/debug/boot_lc_crash.txt
adb pull /cache/debug/boot_lc_full.txt
adb pull /cache/debug/boot_lc_kernel.txt
And the first one comes back with /sbin/sh: adb: not found
Click to expand...
Click to collapse
Ok so first of all: adb shell sync must be executed from without the shell you're in. That wasn clear described. So in other words after the dd command you just need to write "sync". That's it. It will not give any output when finished.
So here the next steps:
Try to mount system in TWRP and browse with the file manager if there are any files in /system/apps .
Use bs=512 for all dd commands.
Share your stock boot img here.
What data do you need exactly btw? App data like settings etc? Or just specific files?

steadfasterX said:
Ok so first of all: adb shell sync must be executed from without the shell you're in. That wasn clear described. So in other words after the dd command you just need to write "sync". That's it. It will not give any output when finished.
So here the next steps:
Try to mount system in TWRP and browse with the file manager if there are any files in /system/apps .
Use bs=512 for all dd commands.
Share your stock boot img here.
What data do you need exactly btw? App data like settings etc? Or just specific files?
Click to expand...
Click to collapse
Ahhhh, I assumed everything I saw was in a "copy/paste" format so, I didn't think to even try to exclude the adb from it.
I was able to mount system, and browse apps, there was stuff in there.
I used the "bs=512" method, and it gave the same result. I'm starting to think I'm just boned honestly. I'll upload my boot.img here in a few (in case you see this before I do).
I was hoping I could back up my texts/call logs (I was able to salvage a few, but I'm missing about a months worth), properly backup WhatsApp, get my Nova settings, and make sure I'm not missing anything else (I had a list, but can't think of it now). And I was hoping by doing it, it would fix the annoying Wifi bug.
Edit 1: I don't think it's "bootlooping", because I read that you could boot into TWRP while it's doing it (if your timing is good), I tried and couldn't get into TWRP at all, it's "stone walling" at the LG screen.
Edit 2: My stock Boot.img

ok so .. the boot image you send is not from the STOCK ROM. That is from LOS it seems. Pls upload the stock one which you are trying to flash with dd

steadfasterX said:
ok so .. the boot image you send is not from the STOCK ROM. That is from LOS it seems. Pls upload the stock one which you are trying to flash with dd
Click to expand...
Click to collapse
Huh, I am not sure how that happened. I'm starting to wonder if after the first try with adb push if I was even using my Stock Boot.img, magisk must've messed with me (they said the recommend way to to patch a boot.img) and I got them mixed up? Or at least that's the only thing I can think of.
Anyways, this should be the right one. Boot.img

@steadfasterX
I was able to boot back to Stock using the correct boot.img, unfortunately I lost some very important WhatsApp texts because it had to "re-verify", but other than that, everything seems to be in order. My apologies for confusing us both with the wrong boot.img. When I was messing around with Magisk, I must've gotten the two confused. I won't know if the wifi is fixed in LOS until later (I have to wait a while before I can use WhatsApp again).

emperordogma said:
@steadfasterX
I was able to boot back to Stock using the correct boot.img, unfortunately I lost some very important WhatsApp texts because it had to "re-verify", but other than that, everything seems to be in order. My apologies for confusing us both with the wrong boot.img. When I was messing around with Magisk, I must've gotten the two confused. I won't know if the wifi is fixed in LOS until later (I have to wait a while before I can use WhatsApp again).
Click to expand...
Click to collapse
yea that was my assumption after seeing that wrong boot.img.. all users were able to boot STOCK this way so it was either a mistake or bad flash. glad you figured it out.
when your WiFi does not come back on LOS later attach the boot logs then.
cheers

steadfasterX said:
yea that was my assumption after seeing that wrong boot.img.. all users were able to boot STOCK this way so it was either a mistake or bad flash. glad you figured it out.
when your WiFi does not come back on LOS later attach the boot logs then.
cheers
Click to expand...
Click to collapse
Everything appears to be working fine now, including the WiFi (you were right about fixing it by going back to stock), which appears to be better than it was before! I decided to upgrade to Lineage 16, because you had just updated it recently so, best to stay where the active development is (or at least last update), in case anything goes wrong. Thank you so much for your assistance, sorry about mixing up the boot.imgs. And thank you continuing support for the G4 (in some capacity).
I also just found out my phone had "OEM Unlock" in the developer settings, so I don't think I needed to use USU (if I read about that tight), pretty annoyed with myself for not paying attention properly.

emperordogma said:
Everything appears to be working fine now, including the WiFi (you were right about fixing it by going back to stock), which appears to be better than it was before! I decided to upgrade to Lineage 16, because you had just updated it recently so, best to stay where the active development is (or at least last update), in case anything goes wrong. Thank you so much for your assistance, sorry about mixing up the boot.imgs. And thank you continuing support for the G4 (in some capacity).
I also just found out my phone had "OEM Unlock" in the developer settings, so I don't think I needed to use USU (if I read about that tight), pretty annoyed with myself for not paying attention properly.
Click to expand...
Click to collapse
If your device is not a h811 or h815 international(!) then this option in dev settings will just do.....nothing. If it would be THAT easy there were never the need for UsU so you did it all right

steadfasterX said:
If your device is not a h811 or h815 international(!) then this option in dev settings will just do.....nothing. If it would be THAT easy there were never the need for UsU so you did it all right
Click to expand...
Click to collapse
Then what the heck is the point of that button/switch??? I figured because mine was a frankenstien device that maybe almost all of them had it, or I just got "lucky".

emperordogma said:
Then what the heck is the point of that button/switch??? I figured because mine was a frankenstien device that maybe almost all of them had it, or I just got "lucky".
Click to expand...
Click to collapse
Its just there by mistake. Not by LG but the OEMs. The OEMs like verizon, etc are not doing a good job but that's not new..