I have successfully rebranded my device from L-09GBRC to L-29C432. One of steps was to backup OEM info. I did this in twrp. I saw a thread by Lwanna about sharing OEM information with other users but they are flashable zip files.
I was wondering if there is a way to convert my twrp backup to that format so others can benefit with returning back to original state of device - before rebranding.
Yes you have to rename oeminfo.win to bin, that all
Related
There's lot of threads about flashing recovery images that you download from somewhere, and how to customize your roms, etc. but i couldn't find any about dumping my current phone image to restore later if so I desire.
Is it possible?
I want to start using Cyanogen, but I also would appreciate the idea of being able to restore 100% of my previous phone software. I have an unlocked N1.
There's no info on how to actually generate your own image on the restore thread http://forum.xda-developers.com/showthread.php?t=614057
neither over the wiki http://forum.xda-developers.com/wiki/index.php?title=Nexus_One
I run the following script (AT YOUR RISK!):
1. Boot into recovery (don't worry nothing flashed):
Code:
adb wait-for-device
adb reboot bootloader
fastboot boot recovery-RA-passion-v2.2.1.img
echo ... Waiting for recovery image load
while [ -z adb shell pwd 2> /dev/null` ]
do
sleep 1
done
2a. To backup:
Code:
adb shell nandroid-mobile.sh --backup --defaultinput --norecovery
2b. To recover use the menus
gcbxda said:
There's lot of threads about flashing recovery images that you download from somewhere, and how to customize your roms, etc. but i couldn't find any about dumping my current phone image to restore later if so I desire.
Is it possible?
I want to start using Cyanogen, but I also would appreciate the idea of being able to restore 100% of my previous phone software. I have an unlocked N1.
There's no info on how to actually generate your own image on the restore thread http://forum.xda-developers.com/showthread.php?t=614057
neither over the wiki http://forum.xda-developers.com/wiki/index.php?title=Nexus_One
Click to expand...
Click to collapse
The quickest way is to create a nandroid backup. Basically this will backup either selected or all partitions on the phone and can be restored easily. You can access this via either Amon_RA or Clockworkmod recovery. You'll need to use one of these to flash CM7 anyhow. Depending on whether you are on 2.3.3 or 2.3.4 the method to flash the recovery image differs. Either post back here with your rom version or have a good read on the Nexus one wiki Also, to understand nandroid have a read here. The process to creating a backup is a little different but the principle behind it is the same.
Install a recovery like Amon_RA's that supports Nandroid. Dead simple.
This is in the wiki.
thanks everyone.
just explaning why at the time i thought it wasn't in the wiki: it mentions the phone will be erased. i assumed it would erase the Whole nand when i installed amon_ra (so, what's the point of having a backup dump of a already erased phone?) but aparently it will only wipe out your data when enabling fastboot oem unlock.
Hello J3 Pop users. I have here a "backup" of the PL1 firmware made using TWRP. This flash procedure may be necessary if one can not flash the Odin ROM because of any number of failures (there seems to be a common problem with this). I am not positive if this is stock, or pre-rooted.
If you're looking for an Odin file, check here https://forum.xda-developers.com/general/general/rom-pl1-samsung-galaxy-j3-emerge-sm-t3580396
First off, DISCLAIMER: This is not a factory approved flash method, and if you haven't done so already, may void your warranty, or brick your device. Use at your own risk.
Now, with that out of the way, you will need to install TWRP, if you haven't already. That can be obtained from this link:
https://forum.xda-developers.com/ga...overy-twrp-3-1-0-1-samsung-galaxy-j3-t3573607
Just follow the flash instructions, but you don't need to attempt to root it... that part might fail in this case anyways.
Download the file from this link. you will need to extract the folder inside to ".\TWRP\BACKUPS\{device serial}" on your SD card. If you don't see this folder, just create any kind of backup from inside TWRP, even just the "EFS" partition will create the folder you need.
With the files and SD card in place, select "restore" inside TWRP. Select the partitions to restore, and there are two partitions labeled with system, i would recommend restoring both. The "EFS" and "EFS2" partitions should never be restored unless you know beyond a shadow of a doubt that those partitions are corrupted (it rarely happens, even when a device is bricked).
https://drive.google.com/open?id=0BxL3I-2U6frBOFRaSG1UYXd3WWc
So is this flashable via TWRP recovery, or Odin?
Schmitin said:
So is this flashable via TWRP recovery, or Odin?
Click to expand...
Click to collapse
clearly it is flashable via twrp (the last link)
thepcwiz101 said:
clearly it is flashable via twrp (the last link)
Click to expand...
Click to collapse
so on TWRP when I go to flash the recovery nothing shows. is there anyway to fix that?
EDIT: I fixed it. I put it in the wrong folder.
Hey! I really need this file! please send me if you have a backup, I would really appreciate it!
@Greaper88 Please give me access
Hello, I created a backup for my MOTO G5S a lonng time ago, and I cannot find the files for it. Low and behold, I am having issues with my phone not registering on the 4G Network.
Does anyone have their EFS and Persist backup (preferably for an XT1806) that they could lend me? At this point, if I can't fix this phone then i'm going to get another one. So if it bricks it, then i'll deal with it.
Sorry for the multiple posts in this thread, I just need some help. I really appreciate what the community does here.
Other device's efs backup will not going to work on your device.
Recommendation: Take a full backup before doing anything including efs.
Is your IMEI Number OK..?
If yes, install an Oreo custom ROM.
Use these two Commands.
fastboot erase modemst1
fastboot erase modemst2
I can help you bro.
Kannutanti said:
I can help you bro.
Click to expand...
Click to collapse
please can you share that file
(1) flash the stock rom.
(2) install team recovery.
(3) copy the file to the recovery folder.
(4) reboot in recovery mode.
(5) then restore.
(6) after that restart the phone.
https://drive.google.com/file/d/1sGQCl4KEkvS1hEBN67G4aFxgSeRGMdL7/view?usp=drivesdk
Kannutanti said:
(1) flash the stock rom.
(2) install team recovery.
(3) copy the file to the recovery folder.
(4) reboot in recovery mode.
(5) then restore.
(6) after that restart the phone.
https://drive.google.com/file/d/1sGQCl4KEkvS1hEBN67G4aFxgSeRGMdL7/view?usp=drivesdk
Click to expand...
Click to collapse
thanks for sharing ... tried restoring it in stock rom but didnt work
I have flashed gpt.bin file of Potter and I am unable to downgrade or move back to sanders in my Moto G5s Plus (Sander). Help Please!!
khatrimann said:
I have flashed gpt.bin file of Potter and I am unable to downgrade or move back to sanders in my Moto G5s Plus (Sander). Help Please!!
Click to expand...
Click to collapse
I was assited with a dev on here named pizzaboy192
He had me for load oem.img through the terminal commands.
He uploaded the oem.zip and he has a special recovery.img file to use to do a proper oem backup.
Here is a quote of our converstation.
After all that i am still not perfect. I used a twrp backup of oreo I found. It is the only way I can load anything on my phone is though a backup/restore.
I can't flash anything, and I can't adbside load anything either.
You can download the twrprecovery file from his post.
"Visit my XDA profile (I'm on mobile right now) and find my post about TWRP for stock. It's a special version I threw together to backup the OEM partition properly since TWRP normally doesn't.
What we're going to do is fastboot boot TWRP (not flash it) and then restore a backup of the Oreo OEM partition using TWRP.
Then fastboot flash all other Oreo partitions. Any Oreo ROM will work just to get you running, and it should take otas too."
next message:
"OK we're going to force OEM onto it.
https://drive.google.com/file/d/1WUw...ew?usp=sharing
That is the OEM partition but compressed. It should extract to a 768MB file (roughly that size)
copy it somewhere on the phone (TWRP should allow you to mount the internal storage as a USB drive, if that doesn't work, try ADB Push and push it to somewhere like \tmp
Then you will need to use adb to do the following (TWRP is broken for ADB and the stuff it spits out to your computer is garbled. I wasn't ever able to fix it.)
type adb shell and it should dump you down into some garbled mess
hit enter a few times to make sure you're at the shell (it's a root user)
load up notepad, paste the following into it and edit it so it shows the right path for the extracted .img file on your phone
dd if=/tmp/oemoreoaug.img of=/dev/block/bootdevice/by-name/oem
Copy that string and paste it into the adb window on your computer and hit enter. It will take a while to process it and then return an error about it running out of space before you hit the end of the file. that is OK (since your partition is too small)
Once it's finished, copy that result and send it to me just so I can have a clear idea what is going on.
Reboot into fastboot, reflash the oreo firmware but skip the line for OEM (it's kinda global, but not 100% but since moto hasn't released any updates since the oreo one and they don't seem to care, who cares as long as it works, right?) and then see if it boots. "
so if you get that to work,
then I was only able to do a restore using this file
MotoG5sPlus_Sanders_Android8.1Oreficial(ByYoungRockTech).rar
after that I did a full backup using Pizzaboys recovery, and now I am able to restore it at anytime.
Hyde1234 said:
I was assited with a dev on here named pizzaboy192
He had me for load oem.img through the terminal commands.
He uploaded the oem.zip and he has a special recovery.img file to use to do a proper oem backup.
Here is a quote of our converstation.
After all that i am still not perfect. I used a twrp backup of oreo I found. It is the only way I can load anything on my phone is though a backup/restore.
I can't flash anything, and I can't adbside load anything either.
You can download the twrprecovery file from his post.
"Visit my XDA profile (I'm on mobile right now) and find my post about TWRP for stock. It's a special version I threw together to backup the OEM partition properly since TWRP normally doesn't.
What we're going to do is fastboot boot TWRP (not flash it) and then restore a backup of the Oreo OEM partition using TWRP.
Then fastboot flash all other Oreo partitions. Any Oreo ROM will work just to get you running, and it should take otas too."
next message:
"OK we're going to force OEM onto it.
https://drive.google.com/file/d/1WUw...ew?usp=sharing
That is the OEM partition but compressed. It should extract to a 768MB file (roughly that size)
copy it somewhere on the phone (TWRP should allow you to mount the internal storage as a USB drive, if that doesn't work, try ADB Push and push it to somewhere like \tmp
Then you will need to use adb to do the following (TWRP is broken for ADB and the stuff it spits out to your computer is garbled. I wasn't ever able to fix it.)
type adb shell and it should dump you down into some garbled mess
hit enter a few times to make sure you're at the shell (it's a root user)
load up notepad, paste the following into it and edit it so it shows the right path for the extracted .img file on your phone
dd if=/tmp/oemoreoaug.img of=/dev/block/bootdevice/by-name/oem
Copy that string and paste it into the adb window on your computer and hit enter. It will take a while to process it and then return an error about it running out of space before you hit the end of the file. that is OK (since your partition is too small)
Once it's finished, copy that result and send it to me just so I can have a clear idea what is going on.
Reboot into fastboot, reflash the oreo firmware but skip the line for OEM (it's kinda global, but not 100% but since moto hasn't released any updates since the oreo one and they don't seem to care, who cares as long as it works, right?) and then see if it boots. "
so if you get that to work,
then I was only able to do a restore using this file
MotoG5sPlus_Sanders_Android8.1Oreficial(ByYoungRockTech).rar
after that I did a full backup using Pizzaboys recovery, and now I am able to restore it at anytime.
Click to expand...
Click to collapse
Thanks for your help. I'll give it a shot and will revert back to you ASAP
PS: the google link isn't working
Corrupted google link
Hyde1234 said:
I was assited with a dev on here named pizzaboy192
He had me for load oem.img through the terminal commands.
He uploaded the oem.zip and he has a special recovery.img file to use to do a proper oem backup.
Here is a quote of our converstation.
After all that i am still not perfect. I used a twrp backup of oreo I found. It is the only way I can load anything on my phone is though a backup/restore.
I can't flash anything, and I can't adbside load anything either.
You can download the twrprecovery file from his post.
"Visit my XDA profile (I'm on mobile right now) and find my post about TWRP for stock. It's a special version I threw together to backup the OEM partition properly since TWRP normally doesn't.
What we're going to do is fastboot boot TWRP (not flash it) and then restore a backup of the Oreo OEM partition using TWRP.
Then fastboot flash all other Oreo partitions. Any Oreo ROM will work just to get you running, and it should take otas too."
next message:
"OK we're going to force OEM onto it.
https://drive.google.com/file/d/1WUw...ew?usp=sharing
That is the OEM partition but compressed. It should extract to a 768MB file (roughly that size)
copy it somewhere on the phone (TWRP should allow you to mount the internal storage as a USB drive, if that doesn't work, try ADB Push and push it to somewhere like \tmp
Then you will need to use adb to do the following (TWRP is broken for ADB and the stuff it spits out to your computer is garbled. I wasn't ever able to fix it.)
type adb shell and it should dump you down into some garbled mess
hit enter a few times to make sure you're at the shell (it's a root user)
load up notepad, paste the following into it and edit it so it shows the right path for the extracted .img file on your phone
dd if=/tmp/oemoreoaug.img of=/dev/block/bootdevice/by-name/oem
Copy that string and paste it into the adb window on your computer and hit enter. It will take a while to process it and then return an error about it running out of space before you hit the end of the file. that is OK (since your partition is too small)
Once it's finished, copy that result and send it to me just so I can have a clear idea what is going on.
Reboot into fastboot, reflash the oreo firmware but skip the line for OEM (it's kinda global, but not 100% but since moto hasn't released any updates since the oreo one and they don't seem to care, who cares as long as it works, right?) and then see if it boots. "
so if you get that to work,
then I was only able to do a restore using this file
MotoG5sPlus_Sanders_Android8.1Oreficial(ByYoungRockTech).rar
after that I did a full backup using Pizzaboys recovery, and now I am able to restore it at anytime.
Click to expand...
Click to collapse
Could you send the link again? For the same is corrupted
I did the same thing, flashed potter firmware on my sanders, and now ican't revert. Please help, also, the google link isn't working.
After seeing another user on here (hopefully soft) brick their Maven 3 from trying to root using ZPST and the rooting guide here, as well as myself, I want to warn anyone else to not attempt to use any other tool other than the QFIL application from the Qualcomm QPST (the v2.7.480 should be good) software package.
QFIL can backup and flash any partition on the device, negating the need to use any other tool, including ZPST. I am not sure if it is enabled by default, but on the (new) Maven 3 board I have, the devinfo partition did already have the necessary bits for the bootloader to be unlocked (guide for that can be found here). I was able to successfully backup the boot partition (boot.img), put it on my device from my computer, then build a modified Magisk boot.img from the Magisk Manager app. With that, I flashed it as a boot.img partition and it works fine. I can write a full tutorial if there is interest.
But the most important information you should take from this thread is to backup all of your partitions before doing anything to the phone using QFIL. Once you do this, I don't think you can hard-brick your phone, as, if necessary, you can short two solder joints by the SD card slot (message me if you need a picture) to automatically put your device in a functional EDL mode in order to flash your original partition(s) back to the device.
do you have backup files for the phone, I can get into edl mode only. My backup file will not restore the phone
xecutionkrk said:
do you have backup files for the phone, I can get into edl mode only. My backup file will not restore the phone
Click to expand...
Click to collapse
What partitions do you need? boot? I know there seems to be different bootloader versions and stuff
000Nick said:
After seeing another user on here (hopefully soft) brick their Maven 3 from trying to root using ZPST and the rooting guide here, as well as myself, I want to warn anyone else to not attempt to use any other tool other than the QFIL application from the Qualcomm QPST (the v2.7.480 should be good) software package.
QFIL can backup and flash any partition on the device, negating the need to use any other tool, including ZPST. I am not sure if it is enabled by default, but on the (new) Maven 3 board I have, the devinfo partition did already have the necessary bits for the bootloader to be unlocked (guide for that can be found here). I was able to successfully backup the boot partition (boot.img), put it on my device from my computer, then build a modified Magisk boot.img from the Magisk Manager app. With that, I flashed it as a boot.img partition and it works fine. I can write a full tutorial if there is interest.
But the most important information you should take from this thread is to backup all of your partitions before doing anything to the phone using QFIL. Once you do this, I don't think you can hard-brick your phone, as, if necessary, you can short two solder joints by the SD card slot (message me if you need a picture) to automatically put your device in a functional EDL mode in order to flash your original partition(s) back to the device.
Click to expand...
Click to collapse
can you please writ a tutorial on how you did it and also which 2 points to solder in case its needed?