Related
Hello All,
I am a noob and recently learned how to root, unlock or re-partition, install blackrose etc but using your blogs and wikicynogemod.
I am trying to update my phone to Texas ICS using blog by OP- http://forum.xda-developers.com/showthread.php?t=1366897
I was able to reach till the step mentioned below :
i.e.
fastboot flash hboot hboot_brcrust_220-10-206-ICS.nb0
fastboot reboot-bootloader
fastboot -w
and now my phone shows TexasICS on the second line that mans it flashed correctly.
I downloaded the tar file "Evervolv-Perdo-2.2.0a6" but I am clueless about the next steps.
1. To build Evervol --> How and where as repo command doesnt work on my computer undert android sdk directory
2. tar xjf --> I am using windows 7 and hence no tar on my laptop.Meanwhile I am downloading the zip file also and see if unzip works.
But I am curious where to run these commands- either on cmd prompt under android-sdk directory or the phone emulator.
And interestingly, android-sdk dont have unzip/tar command and I have no access to phone now, its not booting.
Also I cant login to my phone now, when I boot it, its stuck at the Nexus One startup logo, not going further, so I believe I can't put anything in the SD card now.
Kindly help as my phone is not accessible now and I am kind of handicapped because of that
FYI : Recently I upgraded the phone to 2.3.7 using Cynogenmod, clock recovery.
you might have lost ur recovery
so fastboot any preffered recovery.img . put .zip in sd and flash it
or you can fastboot system.img, boot.img n recovery.img
Sent from my Nexus One using Tapatalk
If you have a custom recovery like clockworkmod just turn on your device holding trackball or something (I don't remember exactly) and you'll be in recovery or fastboot. Anyway, go to recovery and restore your nand backup. After that you can keep trying (or read below).
If you don't have a backup you can insert the SD card directly into the computer and copy the Evervolv latest version (.ZIP). Then go to recovery and wipe data & cache then install the zip from sd card.
You don't need to pay attention to the building Evervolv part of the post as it's not needed for the install. Don't forget to flash gapps later if you want to.
Sorry for my English and I hope this helps as I'm a bit noob also
Sent from my GT-P7510 using xda app-developers app
flash recovery
Flash recovery by
booting in fastboot
fastboot flash recovery recoveryNAME.img
then reboot to recovery u will get recovery the flash ICS.zip rom
downloaded all the goodies, gapps, rom, everything, went into CWM recovery (photon Q) followed steps exactly as followed, idk what the hell happened. Everything is wiped, tried rsd lite 5.7 with batakang stock and i get XML error every time. Ive flashed many roms since atrix 4g came out and so on, Can anyone please oblige me on this issue, im not a complete noobie.
asser failed: getprop("ro.product.device") == "xt925"
blah blah blah
E: error in /sdcard/Downloads/pac-mb886v22.zip
(status 7)
Installation aborted.
Any Help
BFRAPV42 said:
downloaded all the goodies, gapps, rom, everything, went into CWM recovery (photon Q) followed steps exactly as followed, idk what the hell happened. Everything is wiped, tried rsd lite 5.7 with batakang stock and i get XML error every time. Ive flashed many roms since atrix 4g came out and so on, Can anyone please oblige me on this issue, im not a complete noobie.
asser failed: getprop("ro.product.device") == "xt925"
blah blah blah
E: error in /sdcard/Downloads/pac-mb886v22.zip
(status 7)
Installation aborted.
Any Help
Click to expand...
Click to collapse
You must either A: install cwm (razr hd); or B: extract the zip, then go to Meta-inf > Com > Google > Android > Updater-Script, change "updater-script" to "updater-script.txt" then delete all the assert lines at the top, then save as "updater-script.file" then rename it to "updater-script" with no file extension again, and put it back in the same directory as the previous updater-script was, then repack the zip and install it. (I'm talking to you in detail because you apear to be new with one post, no offense if you know how to script it with note pad++ without detailed instructions. )
flashing error
Codex01 said:
You must either A: install cwm (razr hd); or B: extract the zip, then go to Meta-inf > Com > Google > Android > Updater-Script, change "updater-script" to "updater-script.txt" then delete all the assert lines at the top, then save as "updater-script.file" then rename it to "updater-script" with no file extension again, and put it back in the same directory as the previous updater-script was, then repack the zip and install it. (I'm talking to you in detail because you apear to be new with one post, no offense if you know how to script it with note pad++ without detailed instructions. )
Click to expand...
Click to collapse
i was on here prior but its been a while i appreciate the help. my issue theres no system on my AHD so how to get pacman rom redownloaded to my pc and no im not super BA at scripting. ya i can delete a few getvar lines to flash back to stock jb and start over again but syste.img wont even flash there while in AP Fastboot.
Thanks man
Trying to go to stock jb now, i had root and have unlocked bootloader, when usign rsd lite v5.7 i flash the xml after editing it and taking the 2 getvar lines out and now system wont flash, it says phone "Fail flashing process" "system.img" phone returned fail. flashing everything fine till it gets to the system.img file.
(Originaly Posted By: SkeevyDude)
Instructions Install Stock Fastboots JB
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img
fastboot -w
fastboot erase cache !
fastboot reboot
Don't use RSD Lite, its too complicated.
Codex01 said:
(Originaly Posted By: SkeevyDude)
Instructions Install Stock Fastboots JB
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img
fastboot -w
fastboot erase cache !
fastboot reboot
Don't use RSD Lite, its too complicated.
Click to expand...
Click to collapse
And the erase commnds with ! don't work for us.
I installed CM10.1 by manually formatting /system and /data before flashing. Can't fail a build.prop check if there is no build.prop to check
stock jb
skeevydude said:
And the erase commnds with ! don't work for us.
I installed CM10.1 by manually formatting /system and /data before flashing. Can't fail a build.prop check if there is no build.prop to check
Click to expand...
Click to collapse
so i downloaded stock att jb rom from xda, went to the directory C:\user\costco\desktop and to the stock jb folder open command prompt and typed the code.(phone is in fast boot currently as well) Cmmnd prompt says is not recognized as an external or internal command,operable program or batch file. Maybe my head is just to busy to focus i must be messing up somewhere. You guys are so freaking awesome for being patient with me and helping me, ill buy the brews haha
Not an issue with bootloader already unlocked i assume cause once im back on stock im gonna be 1000 times more careful when rerooting again to get back where i was.
idk if its terminal for vista or if its the download i got, i got it from a link on here from, I leave the "getvar lines on the xml file when i do it through terminal right?
Check out my reply in this post. I had the same problem and got it figured out...
http://forum.xda-developers.com/showthread.php?t=2209660
Atrix HD - PACman ROM
RSD wouldn't flash system.img for some reason and wouldn't exit AP fastboot mode until I successfully flashed. So with the working fastboot files (check out skeevydudes posts, don't use the SDK fastboot) make a folder w fastboot.exe, fastboot api, the stock zip for rsd (remove the getvar and system.img lines of course), epinter's recovery (skeevydude made a recovery flash that contains this), and system.img (extracted from the stock RSD flash zip). Then open terminal or command prompt. cd to the folder you just made... fastboot flash system system.img then it will reboot when it flashes, reboot back to AP fastboot and then cd to fold again and then fastboot flash recovery recovery.img Then from epinter's CWM you can flash the ROM as instructed in the OP wo having to edit anything. Please excuse my mess doing all this from my phone
Droid4Drew said:
Check out my reply in this post. I had the same problem and got it figured out...
http://forum.xda-developers.com/showthread.php?t=2209660
Atrix HD - PACman ROM
RSD wouldn't flash system.img for some reason and wouldn't exit AP fastboot mode until I successfully flashed. So with the working fastboot files (check out skeevydudes posts, don't use the SDK fastboot) make a folder w fastboot.exe, fastboot api, the stock zip for rsd (remove the getvar and system.img lines of course), epinter's recovery (skeevydude made a recovery flash that contains this), and system.img (extracted from the stock RSD flash zip). Then open terminal or command prompt. cd to the folder you just made... fastboot flash system system.img then it will reboot when it flashes, reboot back to AP fastboot and then cd to fold again and then fastboot flash recovery recovery.img Then from epinter's CWM you can flash the ROM as instructed in the OP wo having to edit anything. Please excuse my mess doing all this from my phone
Click to expand...
Click to collapse
no man its all good i need all the tutorial help i can get, never have bricked a phone and worried i did so, i can make sense of most of it but my head is full of tht sdk stuff, trying to forget it and get this working, i feel like an idiot asking for step by step crap but how am i to get it quicker than asking for a little help. learning from this is major for me. Thanks man hopefully i get it ok.
still no bueno
BFRAPV42 said:
no man its all good i need all the tutorial help i can get, never have bricked a phone and worried i did so, i can make sense of most of it but my head is full of tht sdk stuff, trying to forget it and get this working, i feel like an idiot asking for step by step crap but how am i to get it quicker than asking for a little help. learning from this is major for me. Thanks man hopefully i get it ok.
Click to expand...
Click to collapse
still a no go, have the new folder with all 5 items needed, pulled up command prompt and its giving same issue. F WORDDDDDDDDDs
C:\Users\Costco>fastboot flash system system.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
same error.
You need these fastboot binaries in the folder also, sorry I couldn't think of the word binaries earlier when I was typing... This I what I ment by the exe and api, just put the two files from the windows folder of the zip into the folder you made and try again... http://www.batakang.com/ftp/devs/mattlgroff/snapdragon-fastboots.zip
Atrix HD - PACman ROM
Droid4Drew said:
You need these fastboot binaries in the folder also, sorry I couldn't think of the word binaries earlier when I was typing... This I what I ment by the exe and api, just put the two files from the windows folder of the zip into the folder you made and try again... http://www.batakang.com/ftp/devs/mattlgroff/snapdragon-fastboots.zip
Atrix HD - PACman ROM
Click to expand...
Click to collapse
i have the snapdragon fastboot .exe and .api in the folder already. along with the system.img , epinters recovery.img and MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
i took a screen shot of the directions you gave with the command prompt open and the folder with the files in it but couldnt upload it unfortunately.
Make sure adb.exe and fast boot.exe are set to run as admin. Right click them and set them to be admin. Then try again.
Sent from my MB886 using xda app-developers app
TTLayland said:
Make sure adb.exe and fast boot.exe are set to run as admin. Right click them and set them to be admin. Then try again.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
fastboot.exe is admin api doesnt have an option in advanced for run as admin, i opened terminal and cd to where the file was on c: drive and typed [fastboot flash system system.img] hit entere and it worked but the phone never rebooted after it completed, when i typed [fastboot flash recovery recovery.img] with is epinters recovery it says ERROR cannot load recovery.img
Scratch that I'm actually replying to this from stock jb, thank all you guys for all the help.
Sent from my MB886 using xda app-developers app
So my advice worked?
Sent from my MB886 using xda app-developers app
Ya it work but It wouldn't with battery under 60% when I charged it up it flashed with ease. I'm on stock 4.1.1 gonna try epinters cwm to flash and then finally pacman
Sent from my MB886 using xda app-developers app
BFRAPV42 said:
Ya it work but It wouldn't with battery under 60% when I charged it up it flashed with ease. I'm on stock 4.1.1 gonna try epinters cwm to flash and then finally pacman
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
I found that the advice I gave you was the only thing that was not in the instructions. Good stuff that you got it working though.
Sent from my MB886 using xda app-developers app
Got a ? about Atrix HD flashed with Pac Man v22
I flashed Pac Man and everything looks great, and works well tiny lag issues but I love it so thank you to all the devs involved.
But...I have seemed to lose root access. I have tried to reinstall the root access with one click and it stops at Daemon started successfully *
any ideas thanks in advance!
Install a superuser zip through cwm.
Sent from my PACMAN MATRIX HD MAXX
Hi , so I was messing around with the updated roms of 4.2.2 and I had formatted the SD card after installing the latest version of insertcoin, after which I mistakenly cleared all the data as well including the current rom installed... dumb I know.
So now I'm stuck with only recovery and fastboot access, is there a way to install a new ROM, or stock image using fastboot? Recovery can no longer mount storage due to some recent changes so like I said I'm stuck.. any help is appreciated.
Look for an RUU if your phone has them. You can do that from fastboot.
Sent from my HTC One V using xda app-developers app
I downloaded an RUU but ended up not using it, I was finally able while in recovery to use adb push in order to copy the files, It did not work for me until I renamed the rom to something short like "rom"
This is the command I used while the phone was in the home screen of recovery using TWRP
C:\htcone>adb push rom.zip /sdcard
After entering that command the prompt remain there for about 3minutes until it showed this message:
3583 KB/s (1001782246 bytes in 273.002s)
Once this was done I was able to flash normally and the phone is back in business
So i kind of got a situation here , i originally wanted to be rooted and have my nexus 6 non encrypted so i had unlocked and rooted my phone. After i ran the "./fastboot erase userdata" command i flashed the custom recovery again and booted into it. From there i thought i would be able to "./adb sideload" a stock custom rom non encrypted but for some reason i was having difficulty running that command. My laptop was not seeing the phone, so after about 30 min of playing around with it trying to get it to work i figured id just start over fresh. From this point i dont have an OS installed so i knew i would have to download the appropriate files for the nexus 6 so i did. I tried both methods, the "./flash-all.sh" command and flashing everything one by one rebooting the bootloader in between flashes and still kept getting this same error
fastboot(1561,0xa04aa1d4) malloc: *** mach_vm_map(size=1681293312) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1679613116 bytes
error: update package missing system.img
and now im stuck in fastboot mode at least, but cannot revert back to stock unless im missing something here. Can someone help please
AnthonyAldrete said:
So i kind of got a situation here , i originally wanted to be rooted and have my nexus 6 non encrypted so i had unlocked and rooted my phone. After i ran the "./fastboot erase userdata" command i flashed the custom recovery again and booted into it. From there i thought i would be able to "./adb sideload" a stock custom rom non encrypted but for some reason i was having difficulty running that command. My laptop was not seeing the phone, so after about 30 min of playing around with it trying to get it to work i figured id just start over fresh. From this point i dont have an OS installed so i knew i would have to download the appropriate files for the nexus 6 so i did. I tried both methods, the "./flash-all.sh" command and flashing everything one by one rebooting the bootloader in between flashes and still kept getting this same error
fastboot(1561,0xa04aa1d4) malloc: *** mach_vm_map(size=1681293312) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1679613116 bytes
error: update package missing system.img
and now im stuck in fastboot mode at least, but cannot revert back to stock unless im missing something here. Can someone help please
Click to expand...
Click to collapse
it looks like the script is looking for a file that is not in the proper directory
the flash all script has never worked for me I have always had to manually flash the images.
looks like you are on a mac since you are using the ./with the command
follow the directions below and you should get back to stock
since you are already in bootloader mode
Download the required factory image files to your computer and extract them
Create an empty directory. All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory; (it is easier this way)
Download the version of Android you want to your new directory. Make sure you are using a nexus 6 image.
Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt. In Ubuntu or MAC just cd to the directory.
Type in the commands into the command prompt
Make sure your computer recognizes your device by typing: fastboot devices
Flash the bootloader: fastboot flash bootloader bootloader-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the radio: fastboot flash radio radio-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the system partition: fastboot flash system system.img
Flash the data partition: fastboot flash userdata userdata.img
Flash the kernel/ramdisk: fastboot flash boot boot.img
Flash the recovery partition: fastboot flash recovery recovery.img
Erase the cache partition: fastboot format cache
Reboot: fastboot reboot
Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked.
No you can root or decrypt. Search for directions on the forum or the internet.
funny i just did this exact same thing like you instructed and was about to reply to this post saying i resolved it hahah. Thanks anyways though =), i dont understand why i was getting that though because i had every file in the same place
No worries glad you got it working
qnc said:
No worries glad you got it working
Click to expand...
Click to collapse
Also found out that you Dont do the ./fastboot erase userdate command because it puts 0s in and leaves the phone unbootable which was my root cause for my phone being stuck. Instead, after flashing the boot.IMG you do the ./fastboot partition userdata instead and it will do a factory reset and when booting it will not encrypt the phone.
qnc said:
it looks like the script is looking for a file that is not in the proper directory
the flash all script has never worked for me I have always had to manually flash the images.
looks like you are on a mac since you are using the ./with the command
follow the directions below and you should get back to stock
since you are already in bootloader mode
Download the required factory image files to your computer and extract them
Create an empty directory. All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory; (it is easier this way)
Download the version of Android you want to your new directory. Make sure you are using a nexus 6 image.
Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt. In Ubuntu or MAC just cd to the directory.
Type in the commands into the command prompt
Make sure your computer recognizes your device by typing: fastboot devices
Flash the bootloader: fastboot flash bootloader bootloader-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the radio: fastboot flash radio radio-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the system partition: fastboot flash system system.img
Flash the data partition: fastboot flash userdata userdata.img
Flash the kernel/ramdisk: fastboot flash boot boot.img
Flash the recovery partition: fastboot flash recovery recovery.img
Erase the cache partition: fastboot format cache
Reboot: fastboot reboot
Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked.
No you can root or decrypt. Search for directions on the forum or the internet.
Click to expand...
Click to collapse
And I was having the same issues executing the flash all command too until I opened the command in a text editor and for every command put the "./" in front and was able to execute it but this is the first time I've gotten an error. My nexus5 worked with this command no problem
worked for me but still could not decrypt
qnc said:
it looks like the script is looking for a file that is not in the proper directory
the flash all script has never worked for me I have always had to manually flash the images.
looks like you are on a mac since you are using the ./with the command
follow the directions below and you should get back to stock
since you are already in bootloader mode
Download the required factory image files to your computer and extract them
Create an empty directory. All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory; (it is easier this way)
Download the version of Android you want to your new directory. Make sure you are using a nexus 6 image.
Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt. In Ubuntu or MAC just cd to the directory.
Type in the commands into the command prompt
Make sure your computer recognizes your device by typing: fastboot devices
Flash the bootloader: fastboot flash bootloader bootloader-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the radio: fastboot flash radio radio-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the system partition: fastboot flash system system.img
Flash the data partition: fastboot flash userdata userdata.img
Flash the kernel/ramdisk: fastboot flash boot boot.img
Flash the recovery partition: fastboot flash recovery recovery.img
Erase the cache partition: fastboot format cache
Reboot: fastboot reboot
Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked.
No you can root or decrypt. Search for directions on the forum or the internet.
Click to expand...
Click to collapse
so all of this worked for me and its back up and running, but my phone still says that its encrypted
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.