Related
I hate to do this but I this is my last resort to getting my phone back working. I currently can not get pass splash screen. Phone was already rooted running cm7 and I wanted to go back to one of my old nandroid so I flashed CW 2.5.1.2. It was working fine but was running slow so I did a data format and wipe cache and ever since then it will not boot up. I am getting a E:Cant' mount CACHE:recovery/command and log message when recovery loads up.
I can get into fastboot and recovery fine but I cant seem to flash any of my nandroids anymore. I have about 5 of them and none work. I can't flash any roms either. It seems as if my root may be gone because when Im in adb shell and run su it does not give me root and I cannot mount any systems in recovery. I tried everything from trying to flash to stock through hboot and even flashing new recovery in fastboot but that did not work since I do not have ENG HBOOT. Tried rerooting and unrooting it again but I always have to go into that /data/local but I am never able to gain access. I do still have S-OFF but that seems to be about it. Oh yeah and I cant even do a wipe data/factory reset. Says E:format_root device: can't find mmc partition.
So if someone knows anything else I could try to get this resolve that would be cool.
Ok lets start don't panic all is not lost yet you can still have root with S-OFF and have access fastboot and recovery. I am not sure why you reverted back to older CWMR2.5.1.2 as if you had CWMR3.0.0.6 you could have done it without fastboot but makes no diff now.
First go try "fastboot erase system -w" and then boot in to recovery and do full factory wipe and then flash as you normally would do.
BlackSHELF said:
Ok lets start don't panic all is not lost yet you can still have root with S-OFF and have access fastboot and recovery. I am not sure why you reverted back to older CWMR2.5.1.2 as if you had CWMR3.0.0.6 you could have done it without fastboot but makes no diff now.
First go try "fastboot erase system -w" and then boot in to recovery and do full factory wipe and then flash as you normally would do.
Click to expand...
Click to collapse
I reverted back to that one thinking that it would enable me to flash a none cm7 rom.
Here is what I got. From my understanding I am getting this because I do not have ENG HBOOT but please correct me if Im wrong
C:\android-sdk-windows\tools>fastboot erase system -w
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.020s
Hmmm I just reread your OP and you saying you somehow lost root trying to unroot and reroot, so I am not sure about the current status.
NOMRAL CASE:
http://forum.xda-developers.com/attachment.php?attachmentid=516463&d=1297577207
^ download that and unzip it and get the recovery.img for 3.0.0.6 and try "fastboot flash recovery recovery.img" as that would do if not try the below.
EXTREME CASE:
http://www.filefactory.com/file/caa....140e_26.03.02.26_M_release_155771_signed.zip
File: PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.1 40e_26.03.02.26_M_release_155771_signed.zip
MD5: 49D07F0EE7DE1765A6A84CB12FA53110
Size: 312 MB
^ go download the file and then rename it from "PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60. 140e_26.03.02.26_M_release_155771_signed.zip" to "PD15IMG.zip" (make sure its not PD15IMG.zip.zip) and put it in root of your SDCard. Go in to bootloader and follow the instructions. This will get you to stock rom/radio from there you can redo all your stuff.
BlackSHELF said:
Hmmm I just reread your OP and you saying you somehow lost root trying to unroot and reroot, so I am not sure about the current status.
NOMRAL CASE:
http://forum.xda-developers.com/attachment.php?attachmentid=516463&d=1297577207
^ download that and unzip it and get the recovery.img for 3.0.0.6 and try "fastboot flash recovery recovery.img" as that would do if not try the below.
EXTREME CASE:
http://www.filefactory.com/file/caa....140e_26.03.02.26_M_release_155771_signed.zip
File: PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.1 40e_26.03.02.26_M_release_155771_signed.zip
MD5: 49D07F0EE7DE1765A6A84CB12FA53110
Size: 312 MB
^ go download the file and then rename it from "PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60. 140e_26.03.02.26_M_release_155771_signed.zip" to "PD15IMG.zip" (make sure its not PD15IMG.zip.zip) and put it in root of your SDCard. Go in to bootloader and follow the instructions. This will get you to stock rom/radio from there you can redo all your stuff.
Click to expand...
Click to collapse
C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (3426 KB)...
OKAY [ 1.159s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.180s
The other file did not work either. It had "Fail-PU" for all the files it tried to flash
Did you try the PD15IMG.zip from bootloader? Download it make sure its not corrupted that is why I provided you with md5 hash to verify. Then put the file in root of your sdcard and then boot in to bootloader, it will scan it and follow the instruction to revert back to original.
BlackSHELF said:
Did you try the PD15IMG.zip from bootloader? Download it make sure its not corrupted that is why I provided you with md5 hash to verify. Then put the file in root of your sdcard and then boot in to bootloader, it will scan it and follow the instruction to revert back to original.
Click to expand...
Click to collapse
Yes I just verified it and it is not corrupt. Thats the way I did it and came up fail-pu
lilterro said:
Yes I just verified it and it is not corrupt. Thats the way I did it and came up fail-pu
Click to expand...
Click to collapse
Hmmm never seen or heard of that I am taking fail pu means failed partition update. What does your HBOOT ver say on the screen? I am not sure what happened but seems like it soft-brick ATM still not sure how you lost root. Hopefully someone who has little more knowledge can shed some light.
BlackSHELF said:
Hmmm never seen or heard of that I am taking fail pu means failed partition update. What does your HBOOT ver say on the screen? I am not sure what happened but seems like it soft-brick ATM still not sure how you lost root. Hopefully someone who has little more knowledge can shed some light.
Click to expand...
Click to collapse
Ok thanks anyway. I am normally able to wok my out of alot of these issues that come up with flashing but this one got me stumped to.
HBOOT-0.86.0000
perm-brick no fix
lilterro said:
Ok thanks anyway. I am normally able to wok my out of alot of these issues that come up with flashing but this one got me stumped to.
HBOOT-0.86.0000
Click to expand...
Click to collapse
I am having the very same problem i am very good at fixing my mistakes but this one is impossible i get that same fail-pu but only difference is mine is s-on and it was never rooted only temp-root i was trying to perm-root and that's when it crashed will not boot up any more and i can't boot into recovery because it never been rooted and i don't know how to do ( C:\android-sdk-windows\tools>fastboot flash recovery recovery.img ) looks like something for the pc and i tried factory reset it will just freeze with the 3 androids skating i go to fastboot and i see bootloader, reboot, reboot bootloader and power down but those did nothing i even offered $100 through paypal to the first person how fixes it but it's an impossible task so there is a full brick out there people say its not but i see different.
perm-brick no fix
Any help is appreciated
Which partition does radio go in? Boot vendor system or other and newest boot loader I'm assuming goes in boot partition. I'm on 89D and can't find any flashable zips only .img
bossofindy said:
Which partition does radio go in? Boot vendor system or other and newest boot loader I'm assuming goes in boot partition. I'm on 89D and can't find any flashable zips only .img
Click to expand...
Click to collapse
Whoa, man, slow down! Probably shouldn't be messing with these things if you don't know what you're doing, you're gonna brick your phone. Bootloader doesn't go in the boot partition, it goes in the bootloader partition. Radio goes in the radio partition. You don't flash any of these things with recovery anyway, you flash them with fastboot. Look at my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Thanks I got it all figured out via fastboot but now I get an error at startup saying there is an internal error with my device please contact manufacturer for details
bossofindy said:
Thanks I got it all figured out via fastboot but now I get an error at startup saying there is an internal error with my device please contact manufacturer for details
Click to expand...
Click to collapse
It's impossible to help you without all of the details.
Thanks for the help I got it all figured out I flashed the 29 vendor over 89D that's when I got internal error. I then I upgraded bootloader and radio via fastboot then flashed pure nexus all is running good now
Since I lost everything from the boot to the recovery to the system part to anything, i haven't been able to boot the phone;
I can access erecovery but when I try to recover the phone it stops at downloading and then says couldn't connect to servers so that's dead;
I can access TWRP but when I try to flash MM, it returns errors saying that it couldn't mount partitions (Vendor, cust and other...)
I can access fastboot mode. Some people suggested that I should try recovering using dload but the transfert rate to the sd card is taking forever;
Now I extracted everything from update.app using huawei firmware extractor (see http://imgur.com/MWeCCXi ) what should I flash (via fastboot) and in what order?
I would really appreciate the help.
algnerd said:
Since I lost everything from the boot to the recovery to the system part to anything, i haven't been able to boot the phone;
I can access erecovery but when I try to recover the phone it stops at downloading and then says couldn't connect to servers so that's dead;
I can access TWRP but when I try to flash MM, it returns errors saying that it couldn't mount partitions (Vendor, cust and other...)
I can access fastboot mode. Some people suggested that I should try recovering using dload but the transfert rate to the sd card is taking forever;
Now I extracted everything from update.app using huawei firmware extractor (see http://imgur.com/MWeCCXi ) what should I flash (via fastboot) and in what order?
I would really appreciate the help.
Click to expand...
Click to collapse
Boot.img , recovery.img , cust.img , system.img.
Claleale said:
Boot.img , recovery.img , cust.img , system.img.
Click to expand...
Click to collapse
Are those the correct commands?
Fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
?
algnerd said:
Are those the correct commands?
Fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
?
Click to expand...
Click to collapse
Yes
Claleale said:
Yes
Click to expand...
Click to collapse
Flashing cust and system returned failes
For cust: (failed remote: partition error)
For syst: (failed remote: sparse flash write failure)
Since I was running nougat before messing up the phone, it had to be System and Boot extracted from the nougat update
By Nougat I assume you mean the file that has been digged out somewhere in the web and that is floating around here in the forums?
Well we all don't really know what this build exactly is, which makes it very hard to reconstruct your errors and give you advice... I would never flash that but okay, that's why we are here
Do you have a TWRP backup that you can restore (and if no, maybe somebody can upload you a clean TWRP restore file)?
Have you tried flashing CM / AICP?
Schlengge said:
By Nougat I assume you mean the file that has been digged out somewhere in the web and that is floating around here in the forums?
Well we all don't really know what this build exactly is, which makes it very hard to reconstruct your errors and give you advice...
Do you have a TWRP backup that you can restore (and if no, maybe somebody can upload you a clean TWRP restore file)?
Have you tried flashing CM?
Click to expand...
Click to collapse
Indeed, the same build that was floating in here.
I was able to resurect my phone from the dead by flashing boot, system and recovery from nougat build then I downgraded to MM untill a more stable release;
Thanks for your support anyway.
(If you know how to close this thread, you're more than welcome to do it )
algnerd said:
...
(If you know how to close this thread, you're more than welcome to do it )
Click to expand...
Click to collapse
You have to use the report button on your own OP. In the report text box, just ask mods to close your thread. The mod who is assigned to this forum will handle your request.
algnerd said:
Indeed, the same build that was floating in here.
I was able to resurect my phone from the dead by flashing boot, system and recovery from nougat build then I downgraded to MM untill a more stable release;
Thanks for your support anyway.
(If you know how to close this thread, you're more than welcome to do it )
Click to expand...
Click to collapse
Hi there. Earlier I spent a few painful hours in the same boat you were in. I've managed to get back to a fresh install of the Nougat build from this thread, but can't seem the downgrade to MM using the (translated from Spanish) instructions found here (linked from that first thread). How did you manage to get back to MM?
(I should add that I tried to flash boot, system and recovery via fastboot without any success).
Cheers
thomasedwardbullen1986 said:
Hi there. Earlier I spent a few painful hours in the same boat you were in. I've managed to get back to a fresh install of the Nougat build from this thread, but can't seem the downgrade to MM using the (translated from Spanish) instructions found here (linked from that first thread). How did you manage to get back to MM?
(I should add that I tried to flash boot, system and recovery via fastboot without any success).
Cheers
Click to expand...
Click to collapse
May god have mercy on your soul.
For the downgrade, I didn't use the b161 directly. I flashed some oeminfo provided in the same folder as the TWRP. Then used b150 ans the three boutons method. Worked like a charm.
Hope it will help you downgrade your phone.
I have the same problem, someone could explain it to me step by step, please
ask help
Hello
My name is EL HADJI MODOU SOW.I request your help concerning a big problem that I meet with my phone huawei P9 lite vns-l31c113b364 (these is the serial number 4TE0216B08004097) .in fact I wanted to activate the second sim then j I made a mistake handling the shot the system is corrupt and now I can not use my phone. I tried to flash it but I can not find a good frimeware. All the flash files that I find are working except the cust.img , vendor.img and product.img. what happens when I flash the cust.img (H: \ SRKToolHuawei-Lod-Chong-V2.0-20161002> fastboot flash cust CUST.img
target reported download size of 471859200 bytes
sending 'cust' (435462 KB) ...
OKAY [10.711s]
writing 'cust' ...
FAILED (remote: partition error)
finished. total time: 10.729s).
please help me I'm really teriified
this is my email:[email protected]
Just an FYI type thing that may save people a bit of digging around sometime.
I tried to get the update that just came out, but as i had TWRP as recovery, no good. Anyhow, in my trying i completely bollixed the phone. Would start, but always booted to TWRP and had various conniptions. Could not even get a TWRP backup to load. Strange not encountered before by me stuff............
Anyhow, recovered by the following method to stock and am back in business.
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Not my own work, adapted from this thread by t-bon3
https://forum.xda-developers.com/showthread.php?t=2542219
which I found thanks to eens post18 at this thread
https://forum.xda-developers.com/g5/how-to/npp25-137-33-stock-firmware-moto-g5-t3577084/page2
After this, Motorola system update installed. On Australian XT1676 is build number NPP25.137-15-7
Patch level 1-May-2017
Still get the I cant be trusted page on power up as have unlocked bootloader.
Many thanks to all at XDA, its a resource that can certainly get you into trouble, but then out of it again.
where do you get the stock firmware?
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
We're you able to revert to a locked bootloader after this, I am looking forward to do so
We're you able to revert to a locked bootloader after this, I am looking forward to do so
Click to expand...
Click to collapse
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.
astmacca said:
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.
Click to expand...
Click to collapse
I can confirm what you said, but I am asking because I am sick of the warning before the device starts
ap4ss3rby said:
I can confirm what you said, but I am asking because I am sick of the warning before the device starts
Click to expand...
Click to collapse
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
TheFixItMan said:
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
Click to expand...
Click to collapse
Thanks, but this is why I made a Google pixel themed logo.bin and used a matching boot animation to go with it some time earlier
downgrade
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance
distclean said:
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance
Click to expand...
Click to collapse
No you cannot downgrade (same firmware version or newer required)
Yes - unlocked bootloader not required
As long as your phone still goes into the bootloader
You should flash all sparsechunks in number order
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
You maybe able to - there are different variants of the same phone
As long as the firmware is the same or newer (as in the bootloader and API version) it may flash
It will either flash or error out
There's only one way to find out - if your phone is dead anyway it's not going to make alot of difference
No - generally you can never downgrade firmware - doing so would be dangerous and you may loose the bootloader for good
thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.
distclean said:
thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.
Click to expand...
Click to collapse
You can write in adb
Code:
adb shell
cat /proc
cat /proc/partitions
Hello,
Does anyone know where can I download the latest firmware for Moto G5 XT1676 baseband Version: m8937_ 8000.122.02.40 R
Thanks
astmacca said:
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Click to expand...
Click to collapse
You're partially right. These commands won't work for our files. You have to flash the firmware according to the instructions contained within the "flashfile.xml" file within the archive. For example we have no "motoboot" partition
I've flashed every stock package available now (4 I think) and haven't been offered an update once. I've ran a couple of custom ROMs but they're just not right in one way or another. Might be time to move on.
distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
I upgraded to this and since then can't downgrade the phone to the stock roms available online. From memory trying to flash gpt.bin gave a "Security version downgrade" error. So I wouldn't assume you'll be able to downgrade and until there is a copy of this particular firmware, you won't be able to flash back or relock the bootloader
astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Is this ROM is good to my XT1676 Baseband: M8937_11.16.02.51R ?
astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Hi, i own the same model of moto g5, i do this in fastboot window
fastboot erase userdata
now the phone only boot in twrp and show a message "failed to mount /data". i think that delete my userdata partition, how could i fix it?
once i can avoid this loop in twrp, i follow these steps to flash stock rom
thanks in advance
juan
I am getting the "No Sim" Error and was told that I needed the boot and bootloader from opp4, does anyone have this?
Thanks
idbl_fanatic said:
I am getting the "No Sim" Error and was told that I needed the boot and bootloader from opp4, does anyone have this? Thanks
Click to expand...
Click to collapse
How is flashing an older boot.img and bootloader.img going to help? There are plenty of places to find the old image file, just unzip and extract.... but don't think that's going to solve anything. Are you on the current stock .019 build?
v12xke said:
How is flashing an older boot.img and bootloader.img going to help? There are plenty of places to find the old image file, just unzip and extract.... but don't think that's going to solve anything. Are you on the current stock .019 build?
Click to expand...
Click to collapse
Doesn't matter now anyway, it started boot looping, had to get an RMA