Related
I just use RSD 5.6 to flash my atrix 2 to 2.3.5 but flash failure .
it is notice that
"Failed flashing process. Failed flashing process. 1/19 flash mbm "allow-mbmloader-flashing-mbm.bin" -> USB error occured while reading/writing.; phone connected."
and then, when i go to FastBoot mode, it is notice that
"AP Fastboot Flash Mode (S) (Flash Failure)
0A.68
Baterry OK
OK to Program
Connect USB
Data Cable."
help me, thanks all
manbk401 said:
I just use RSD 5.6 to flash my atrix 2 to 2.3.5 but flash failure .
it is notice that
"Failed flashing process. Failed flashing process. 1/19 flash mbm "allow-mbmloader-flashing-mbm.bin" -> USB error occured while reading/writing.; phone connected."
and then, when i go to FastBoot mode, it is notice that
"AP Fastboot Flash Mode (S) (Flash Failure)
0A.68
Baterry OK
OK to Program
Connect USB
Data Cable."
help me, thanks all
Click to expand...
Click to collapse
We need more info to help you. which version of the phone? were you on 2.3.6 or 2.3.5 before the flash? do you have drivers installed correctly?
lkrasner said:
We need more info to help you. which version of the phone? were you on 2.3.6 or 2.3.5 before the flash? do you have drivers installed correctly?
Click to expand...
Click to collapse
the first, i use Retail Indian - 5.5.1-EDEM-28-37-SEARET rom (2.3.6). I want to up to Supercharged v5 (following that ). but when completed, my phone just stops at boot screen (i wait 10 minutes but not change).
after that, i go to FastBoot mode and flash to 2.3.5 via RSD Lite. the failure was happended
i use RSD lite 5.6 and Motorola 5.2 Drivers.
ps: I tryed Flashboot following this topic: 2.3.6 from modified 2.3.5 Flashboot: "Invalid CG Version" FIX but nothing change
manbk401 said:
the first, i use Retail Indian - 5.5.1-EDEM-28-37-SEARET rom (2.3.6). I want to up to Supercharged v5 (following that ). but when completed, my phone just stops at boot screen (i wait 10 minutes but not change).
after that, i go to FastBoot mode and flash to 2.3.5 via RSD Lite. the failure was happended
i use RSD lite 5.6 and Motorola 5.2 Drivers.
ps: I tryed Flashboot following this topic: 2.3.6 from modified 2.3.5 Flashboot: "Invalid CG Version" FIX but nothing change
Click to expand...
Click to collapse
go to the noob thread and follow the instructions for replacing files in the fxz, just use the same replace files but the indian fxz that you can download.
lkrasner said:
go to the noob thread and follow the instructions for replacing files in the fxz, just use the same replace files but the indian fxz that you can download.
Click to expand...
Click to collapse
sorry, i don't understand u. i don't have the indian fzx. i'm vietnamese. when i bought atrix 2 at&t, my phone is still on stock 2.3.6.
manbk401 said:
sorry, i don't understand u. i don't have the indian fzx. i'm vietnamese. when i bought atrix 2 at&t, my phone is still on stock 2.3.6.
Click to expand...
Click to collapse
No problem. Just go here: http://forum.xda-developers.com/showthread.php?t=1396650 and read the section on how to flash the FXZ. make sure to look at the bottom part where it tells you to replace some files. you will need to do that. Instead of using the ATT FXZ file like they say use the one that matches your current version (SEARET I think you said) and follow the same directions, but use that file instead. Get if from here: http://sbf.droid-developers.org/edison/list.php
lkrasner said:
No problem. Just go here: http://forum.xda-developers.com/showthread.php?t=1396650 and read the section on how to flash the FXZ. make sure to look at the bottom part where it tells you to replace some files. you will need to do that. Instead of using the ATT FXZ file like they say use the one that matches your current version (SEARET I think you said) and follow the same directions, but use that file instead. Get if from here: http://sbf.droid-developers.org/edison/list.php
Click to expand...
Click to collapse
ok, thanks u. i will try to do follow your help. in vietnam, it's 1 am, i need to sleep .
have a nice day
manbk401 said:
I just use RSD 5.6 to flash my atrix 2 to 2.3.5 but flash failure .
it is notice that
"Failed flashing process. Failed flashing process. 1/19 flash mbm "allow-mbmloader-flashing-mbm.bin" -> USB error occured while reading/writing.; phone connected."
and then, when i go to FastBoot mode, it is notice that
"AP Fastboot Flash Mode (S) (Flash Failure)
0A.68
Baterry OK
OK to Program
Connect USB
Data Cable."
help me, thanks all
Click to expand...
Click to collapse
This is right sbf or FXZ for SEART ROM
http://sbf.droid-developers.org/edison/5.5.1-EDEM-27-SEARET_cfc.xml.zip
Reinstall Drivers and RSD Lite and try flashing it, it should work
prasannapmv said:
This is right sbf or FXZ for SEART ROM
Reinstall Drivers and RSD Lite and try flashing it, it should work
Click to expand...
Click to collapse
can i should replace some file in above zip? because my phone is 2.3.6
Code:
How to flash the FXZ once applying the OTA update and get back to 2.3.5, ONCE YOU UPDATE TO THE OTS 2.3.6 YOU WILL NOT BE ABLE TO FLASH THE 2.3.5 FXZ WITHOUT FOLLOWING THESE STEPS BELOW!!
NOTE: Download this file HERE -
Unzip it and move all the the items in it to the stock fxz. You might get a warning about replacing files, just click OK. NOTE that Windows might not be able to handle the size of the fxz. I have 6 GB RAM but Windows still wasn't able to perform a drag-and-drop through the fxz's zip. I recommend that you just unzip the fxz and then put the files in. (You don't have to rezip it either, RSD Lite will still recognize it and will flash faster).
You should be able to use RSD Lite to flash the file.
lkrasner said:
No problem. Just go here: http://forum.xda-developers.com/showthread.php?t=1396650 and read the section on how to flash the FXZ. make sure to look at the bottom part where it tells you to replace some files. you will need to do that. Instead of using the ATT FXZ file like they say use the one that matches your current version (SEARET I think you said) and follow the same directions, but use that file instead.
Click to expand...
Click to collapse
i've downloaded the india FXZ and the replace file. but the xml file is not same name.
in replace file is InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285, and in india FZX is 5.5.1-EDEM-27-SEARET_cfc
and a question, my phone use code unlock AT&T, so if I flash to india FXZ, any problem happen with my atrix 2?
manbk401 said:
i've downloaded the india FXZ and the replace file. but the xml file is not same name.
in replace file is InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285, and in india FZX is 5.5.1-EDEM-27-SEARET_cfc
and a question, my phone use code unlock AT&T, so if I flash to india FXZ, any problem happen with my atrix 2?
Click to expand...
Click to collapse
Yeah, I was being stupid. Was the phone originally ATT when you bought it, or was it indian. that makes a big difference. you need to know what it said under settings > about phone.
anyways this should fix it, just use which ever fxz is right (from my post in the noob thread:
just thought of an easier way to get you restored. Most of the time you only really need to do system. download the moto-fastboot utility (it's similar to normal fastboot but you MUST use it instead or it will not work) and the fxz for your region. Extract the fxz and put the system.img from it and moto-fastboot in the same folder. open a command prompt in that folder (hold shift and right click) and type
Code:
moto-fastboot.exe flash system system.img
moto-fastboot.exe erase userdata
obviously you need to have your phone in fastboot mode to do that. it does the exact same thing as rsd, just only the 2 important steps, flashing system and wiping data.)
Let me know how that works for you. It may not since you have had flash failures, but we'll see.
moto-fastboot: http://forum.xda-developers.com/attachment.php?attachmentid=635584&d=1308928440 you should actually extract it and put all the things in it in the folder with system.img
Good luck!
lkrasner said:
Yeah, I was being stupid. Was the phone originally ATT when you bought it, or was it indian. that makes a big difference. you need to know what it said under settings > about phone.
anyways this should fix it, just use which ever fxz is right (from my post in the noob thread:
just thought of an easier way to get you restored. Most of the time you only really need to do system. download the moto-fastboot utility (it's similar to normal fastboot but you MUST use it instead or it will not work) and the fxz for your region. Extract the fxz and put the system.img from it and moto-fastboot in the same folder. open a command prompt in that folder (hold shift and right click) and type
Code:
moto-fastboot.exe flash system system.img
moto-fastboot.exe erase userdata
obviously you need to have your phone in fastboot mode to do that. it does the exact same thing as rsd, just only the 2 important steps, flashing system and wiping data.)
Let me know how that works for you. It may not since you have had flash failures, but we'll see.
moto-fastboot: http://forum.xda-developers.com/attachment.php?attachmentid=635584&d=1308928440 you should actually extract it and put all the things in it in the folder with system.img
Good luck!
Click to expand...
Click to collapse
hi, i'm a lucky man. i flashed my phone following Return to Stock 2.3.5 Fastboot SCRIPT. and now, my phone is ok
thanks 4 your help
manbk401 said:
hi, i'm a lucky man. i flashed my phone following Return to Stock 2.3.5 Fastboot SCRIPT. and now, my phone is ok
thanks 4 your help
Click to expand...
Click to collapse
yep, that works pretty well too. It does exactly what I said to do, but more. I do this because it goes faster
want to get back to 2.3.6
plz help me ma phone was on 2.3.6 then i tried to flash indian rom but it says flash error
n i tried several rom bt it didnt work ... all are the same
how can i get back to 2.3.7 ..thank you
i have this 5.5.1 EDEM 27 searet file which is 517 mb
should i flash this or download another 5.5.1 EDEM 28 27 searet WHICH IS 519 mb and will that hard brick my phone if i flash wrong file? im from india and recently purchased this phone and im on 2.3.6
hemanbond said:
i have this 5.5.1 EDEM 27 searet file which is 517 mb
should i flash this or download another 5.5.1 EDEM 28 27 searet WHICH IS 519 mb and will that hard brick my phone if i flash wrong file? im from india and recently purchased this phone and im on 2.3.6
Click to expand...
Click to collapse
Look in settings>about phone..then download accordingly..55.28.37 is the latest in gb 2.3.6..
Sent from my MB865 using xda app-developers app
ye i have 55.28.37 ...so which file should i download?
---------- Post added at 01:30 PM ---------- Previous post was at 01:27 PM ----------
5.5.1-EDEM-28-37-SEARET_cfc.xml.zip
is this the one which ill have to download? and is this 2.3.5 or 2.3.6 and do i need to replace the files in order to flash ...just asking cause im curious...i dont wanna hard brick
hemanbond said:
ye i have 55.28.37 ...so which file should i download?
---------- Post added at 01:30 PM ---------- Previous post was at 01:27 PM ----------
5.5.1-EDEM-28-37-SEARET_cfc.xml.zip
is this the one which ill have to download? and is this 2.3.5 or 2.3.6 and do i need to replace the files in order to flash ...just asking cause im curious...i dont wanna hard brick
Click to expand...
Click to collapse
Yup this is the zip u need..its 2.3.6..no replacing..just flash
Sent from my MB865 using xda app-developers app
Flashed my atrix 2 and fastboot fail
I bought my atrix 2 from US and unlocked it and am using this in india now. I tried to flashboot the phone with "5.5.1-EDEM-28-37-SEARET_cfc.xml". I added the new files thats available in the noob called replace.zip. I also tried the moto fast boot. Now am not able to flashboot and when i run flashboot i get this error "failed flashing process. 11/21 flash ebr "ebr"-> Phone returned fail; Phone connected" .
Please help me.
I just got my ATT Atrix 2 and I think I've already bricked it, soft at least. I used a script to go from 2.3.6 back to 2.3.5 stock, then OTA to 2.3.6, then I flashed the ICS leak and flashed SCV7, it was running horribly, kept crashing and was being extremely unstable so then I tried to use the FXZ script to go from ICS back to GB, and all my phone was doing was showing the Motorola dual core screen and boot looping or just staying on that screen I couldn't tell. I can get into fastboot, when I try to get into recovery there is an icon of a box with an arrow coming out of it and a little android and a yellow progress bar and when that finishes it goes to fastboot and it says "AP FastBoot Flash Mode (S) (Flash Failure) what can I do?
---------- Post added at 07:12 PM ---------- Previous post was at 06:55 PM ----------
The battery is low going by my luck I'm going to assume the phone will not charge while in fast boot. I've been at this for way too many hours, if someone could tell me how to get this phone working I'd appreciate it.
Can anyone post a stock JB recovery image? It would be a very easy way to restore system to stock, RATHER than using RSD Lite..
And yes, I do apologize for polluting the threads if that what this is, however RSD Lite WILL NOT recognize my device anymore (and trust when I say that I have no way of making it happen short of reinstalling Windows)!
A link to a fresh, purely stock JB recovery taken right after and update from a wiped ASA14 system would, I'm sure, help out many users on this site.
If anyone has a recovery image and is willing to share with the community please post. Thank you in advance.
From The Q Of Course!
If you can use fastboot (IE the computer detects the phone while in fastboot mode), I'm betting RSD will still work.
So RSD not work? You don't really seem interested in fixing it tho... I seriously doubt a full reinstall of Windoze is necessary .
Anyhoo, I guess I can upload my system image from stock 4.1.2. Give me a minute.
Edit - or a few.
system.jb.ext4.win
system.jb.ext4.win.md5
galacticservant said:
Can anyone post a stock JB recovery image? It would be a very easy way to restore system to stock, RATHER than using RSD Lite..
And yes, I do apologize for polluting the threads if that what this is, however RSD Lite WILL NOT recognize my device anymore (and trust when I say that I have no way of making it happen short of reinstalling Windows)!
A link to a fresh, purely stock JB recovery taken right after and update from a wiped ASA14 system would, I'm sure, help out many users on this site.
If anyone has a recovery image and is willing to share with the community please post. Thank you in advance.
From The Q Of Course!
Click to expand...
Click to collapse
Hi still new at this I had to reinstall my drivers to get RSD to recognize my device hope this helps
Trust me when I say that I have done EVERYTHING...Moto Device Manager, Moto 5.9.1 Developer Drivers, uninstalled hidden devices in Device Manager, etc, etc, etc...
So, ADB and Fastboot are functional, AND I've even tried Moto-Fastboot as well.
Like I stated, easiest way for me and others would be a stock JB recovery image to flash.
Sent from my Motorola Photon Q LTE using xda premium
galacticservant said:
Trust me when I say that I have done EVERYTHING...Moto Device Manager, Moto 5.9.1 Developer Drivers, uninstalled hidden devices in Device Manager, etc, etc, etc...
So, ADB and Fastboot are functional, AND I've even tried Moto-Fastboot as well.
Like I stated, easiest way for me and others would be a stock JB recovery image to flash.
Sent from my Motorola Photon Q LTE using xda premium
Click to expand...
Click to collapse
When I say I reinstall my drivers FIRST DELETED all old drivers related to motorola photon q 4g even the ADB drivers then install new......
galacticservant said:
Trust me when I say that I have done EVERYTHING...Moto Device Manager, Moto 5.9.1 Developer Drivers, uninstalled hidden devices in Device Manager, etc, etc, etc...
So, ADB and Fastboot are functional, AND I've even tried Moto-Fastboot as well.
Like I stated, easiest way for me and others would be a stock JB recovery image to flash.
Sent from my Motorola Photon Q LTE using xda premium
Click to expand...
Click to collapse
If you can fastboot, worse comes to worse you can do all the commands manually. If you look at the XML file, it is just passing fastboot commands to the phone... So you can do everything RSD does manually thru fastboot.
RSD just scripts it all for you.
arrrghhh said:
If you can fastboot, worse comes to worse you can do all the commands manually. If you look at the XML file, it is just passing fastboot commands to the phone... So you can do everything RSD does manually thru fastboot.
Well, all the files except for the system.img.ext4
This requires the system be flashed in multiple parts (multiflash). Fastboot is not able to do this, and I've also tried Moto-Fastboot which is purported to be able to. It is not possible to multiflash with Fastboot or Moto-Fastboot (RSD must have some script or utility that handles multiflashing of .ext4 partitions. If so than that would seem why using fastboot manually does not work). I've tried using Administrator privileges on windows with both fastboots and even with a persistent root shell on Linux. Trust me, it's not possible. I guess you could always decompile the ext4 system image in some way, and throw it back together as just a system.img and then use fastboot, but that seems rather extensive and beyond my skill level (at the moment).
Sent from my Motorola Photon Q LTE using xda premium
Click to expand...
Click to collapse
galacticservant said:
Well, all the files except for the system.img.ext4
This requires the system be flashed in multiple parts (multiflash). Fastboot is not able to do this, and I've tried Moto-Fastboot which is purported to be able to. It is not possible to multiflash with Fastboot or Moto-Fastboot (unless you wish to re-write the program). I've tried using Administrator privileges on windows and even with root permissions on Linux. Trust me, it's not possible. I guess you could always decompile the
Sent from my Motorola Photon Q LTE using xda premium
Click to expand...
Click to collapse
You're fastboot flashing the files from the FXZ right? Because I only see a system.img in there... which you should be able to fastboot flash no problem.
Here you go:
Original ICS stock ROM - PQ_ICS-Stock.rar (314.9 MB)
Code:
18.04.2013 23:00 10 485 760 boot.emmc.win
18.04.2013 23:00 48 boot.emmc.win.md5
18.04.2013 23:05 319 737 910 system.ext4.win
18.04.2013 23:00 50 system.ext4.win.md5
Stock JB 4.2.1 ROM - PQ_JB-421.rar (522.9 MB)
Code:
27.04.2013 11:55 10 485 760 boot.emmc.win
27.04.2013 11:55 48 boot.emmc.win.md5
27.04.2013 11:54 537 825 792 system.ext4.win
27.04.2013 11:55 50 system.ext4.win.md5
Hope this help :]
I've uploaded the OpenRecovery nandroid of stock Sprint JB release here, some time ago:
http://d-h.st/N0p
kabaldan said:
I've uploaded the OpenRecovery nandroid of stock Sprint JB release here, some time ago:
http://d-h.st/N0p
Click to expand...
Click to collapse
Thank you, I searched and went through threads I figured were relevant and came up empty.
Sent from my Motorola Photon Q LTE using xda premium
arrrghhh said:
If you can fastboot, worse comes to worse you can do all the commands manually. If you look at the XML file, it is just passing fastboot commands to the phone... So you can do everything RSD does manually thru fastboot.
RSD just scripts it all for you.
Click to expand...
Click to collapse
That's handy information there, thanks! I'm on Linux, and I can't get RSD Lite nor Odin (Samsung's RSD equivalent) to recognize a device is connected when I try to use them.
kabaldan said:
I've uploaded the OpenRecovery nandroid of stock Sprint JB release here, some time ago:
http://d-h.st/N0p
Click to expand...
Click to collapse
Hey Kabaldan how do we use the file? I get error status 4 when I try to install the zip in OpenRecovery via update. There is no updater in the file. When i go to nandroid the Q.zip doesnt show up. Thanks for posting though, hopefully I can get it working with some help.
matt2k12 said:
Hey Kabaldan how do we use the file? I get error status 4 when I try to install the zip in OpenRecovery via update. There is no updater in the file. When i go to nandroid the Q.zip doesnt show up. Thanks for posting though, hopefully I can get it working with some help.
Click to expand...
Click to collapse
Extract it to some folder on your device and select nandroid restore
---------- Post added at 12:18 PM ---------- Previous post was at 12:12 PM ----------
Actually, I think you need to put nandroids in ./OpenRecovery/nandroid/ (internal, or external), if I remember correctly.
mrvek said:
Extract it to some folder on your device and select nandroid restore
---------- Post added at 12:18 PM ---------- Previous post was at 12:12 PM ----------
Actually, I think you need to put nandroids in ./OpenRecovery/nandroid/ (internal, or external), if I remember correctly.
Click to expand...
Click to collapse
Thanks - makes sense. The unzipped files werent showing up in the nandroid option so I figured I need to put them in the folder.
Just an FYI - That nandroid got stuck on the "Sprint" boot screen.
Could have been my particular device or flash - disclaimer.
Problems with ROMs
arrrghhh said:
If you can use fastboot (IE the computer detects the phone while in fastboot mode), I'm betting RSD will still work.
So RSD not work? You don't really seem interested in fixing it tho... I seriously doubt a full reinstall of Windoze is necessary .
Anyhoo, I guess I can upload my system image from stock 4.1.2. Give me a minute.
Edit - or a few.
system.jb.ext4.win
system.jb.ext4.win.md5
Click to expand...
Click to collapse
This link doesn't work anymore. Actually takes me to a virus page. Can someone re-up?
Stunherald said:
Here you go:
Original ICS stock ROM - PQ_ICS-Stock.rar (314.9 MB)
Code:
18.04.2013 23:00 10 485 760 boot.emmc.win
18.04.2013 23:00 48 boot.emmc.win.md5
18.04.2013 23:05 319 737 910 system.ext4.win
18.04.2013 23:00 50 system.ext4.win.md5
Stock JB 4.2.1 ROM - PQ_JB-421.rar (522.9 MB)
Code:
27.04.2013 11:55 10 485 760 boot.emmc.win
27.04.2013 11:55 48 boot.emmc.win.md5
27.04.2013 11:54 537 825 792 system.ext4.win
27.04.2013 11:55 50 system.ext4.win.md5
Hope this help :]
Click to expand...
Click to collapse
These appear to be the Sprint Stock ROMs but it looks like they are missing some things (namely the bloatware and ringtones,notifications).
Can someone upload a COMPLETE Sprint Stock ICS and JB Rom that we can flash in recovery please? I can't seem to find these working roms anywhere.
lamentofking said:
This link doesn't work anymore. Actually takes me to a virus page. Can someone re-up?
These appear to be the Sprint Stock ROMs but it looks like they are missing some things (namely the bloatware and ringtones,notifications).
Can someone upload a COMPLETE Sprint Stock ICS and JB Rom that we can flash in recovery please? I can't seem to find these working roms anywhere.
Click to expand...
Click to collapse
i second this, i just now won a epic battle for the sake of updating my prl/profile so my phone app would would work with CM12. it was ridiculous how i followed so many paths correctly and kept running into random issues every time. But why is it that u need a untouched stock rom exactly? i would be more than happy with a twrp flashable stock rom that doesnt overwrite my custom recovery. Wouldnt mind bloatware removal and cpu optimizations on it either lol.
TacticalPower88 said:
i second this, i just now won a epic battle for the sake of updating my prl/profile so my phone app would would work with CM12. it was ridiculous how i followed so many paths correctly and kept running into random issues every time. But why is it that u need a untouched stock rom exactly?.
Click to expand...
Click to collapse
All I could find is that custom roms don't support profile/prl updates. Also I don't believe the Sprint dialer codes (assuming you are using Sprint or Sprint MVNO) are supported either since technically, the custom rom isn't a "Sprint" rom. So all of that support basically goes out of the window. What several users do is just make a backup of a Sprint ROM and their Custom ROM and switch to stock whenever they need to update.
lamentofking said:
All I could find is that custom roms don't support profile/prl updates. Also I don't believe the Sprint dialer codes (assuming you are using Sprint or Sprint MVNO) are supported either since technically, the custom rom isn't a "Sprint" rom. So all of that support basically goes out of the window. What several users do is just make a backup of a Sprint ROM and their Custom ROM and switch to stock whenever they need to update.
Click to expand...
Click to collapse
I was able to use this almost stock sprint rom to do the prl/profile update. The on screen back/home/recent app keys dont pop up but u can just use it to update prl/profile and flash to your rom of choice afterwards. http://forum.xda-developers.com/showthread.php?t=2139547
Greets,
I think I may have bricked my Droid Maxx but I'm hoping someone can verify before I deem it a paperweight. I was on SU-2-3.3 and used Sunshine on it to unlock it and then TWRP to root it. After fully booting up the phone and verifying root, I rebooted into TWRP and ran a full back up w md5. After that, I booted up the phone and used supersu survival mode and then took the OTA update. Now the phone boots to fastboot, but says "boot failed" under any of the options. It won't go into recovery nor will it normally boot up. I tried to use RSD to reflash to the latest version but it just said flash failed at the first file and says something about downgraded security, etc. So now, I can get into fastboot mode and the phone connects and is detected but won't let me flash anything... it was unlocked via Sunshine, but I may have borked it up somehow. Thoughts?
Try a more recent firmware but check your recovery
Sent from my D6616 using Tapatalk
I took the OTA... is there something more recent? Also, I've tried to flash other recoveries but I get "boot failed" at the fastboot menu.
ohhhh you must mean try and use a more recent firmware via RSD. I'll give that a shot
Ok i tried a newer firmware via RSD, now the fastboot mode shows "failed to read signatures for partition aboot" RSD fails at flashing partition gpt.bin
Since I seem to have a partition related error, would this LINK help my situation at all?
Does anyone know of a way I can restore or rewrite the partitions via fastboot?
t3knokon said:
Does anyone know of a way I can restore or rewrite the partitions via fastboot?
Click to expand...
Click to collapse
Okay, So if you think you device is completely bricked, and I mean "NOT RECOVERABLE AT ALL" , you can try this: This may be a long shot, you might want to try uploading 'sbl2.mbn' file. If you are able to flash that, then you can try flashing a "Broken" sbl2 file and try uploading the ROM using Qualcomm emergency downloader. This method is very dangerous, and not for the faint hearted. It is used to root the droids which cannot be rooted by sunshine (post SU4-21) and you may lose your rooting capabilities all together, as this method uploads a non rootable bootloader (SU6-7). If you can get your hands on a copy of the bootloader you already have ( SU-2-3.3) , you should use that to unbrick from the bootloader mode. Try to refer this post for further details.
crack.mech said:
Okay, So if you think you device is completely bricked, and I mean "NOT RECOVERABLE AT ALL" , you can try this: This may be a long shot, you might want to try uploading 'sbl2.mbn' file. If you are able to flash that, then you can try flashing a "Broken" sbl2 file and try uploading the ROM using Qualcomm emergency downloader. This method is very dangerous, and not for the faint hearted. It is used to root the droids which cannot be rooted by sunshine (post SU4-21) and you may lose your rooting capabilities all together, as this method uploads a non rootable bootloader (SU6-7). If you can get your hands on a copy of the bootloader you already have ( SU-2-3.3) , you should use that to unbrick from the bootloader mode. Try to refer this post for further details.
Click to expand...
Click to collapse
well he's not a hardbrick as he can get into fastboot so I don't think he needs to use THIS method just yet.
---------- Post added at 08:30 AM ---------- Previous post was at 08:27 AM ----------
t3knokon said:
Since I seem to have a partition related error, would this LINK help my situation at all?
Click to expand...
Click to collapse
If you can get into fastboot then I don't think you need to go that route just yet. You can try flashing the individual images via fastboot i.e. fastboot flash recovery recovery.img etc. It's been a while but I'd skip flashing the motoboot.img and gpt.bin and flash the boot.img, recovery.img and system.img.
BladeRunner said:
well he's not a hardbrick as he can get into fastboot so I don't think he needs to use THIS method just yet.
---------- Post added at 08:30 AM ---------- Previous post was at 08:27 AM ----------
If you can get into fastboot then I don't think you need to go that route just yet. You can try flashing the individual images via fastboot i.e. fastboot flash recovery recovery.img etc. It's been a while but I'd skip flashing the motoboot.img and gpt.bin and flash the boot.img, recovery.img and system.img.
Click to expand...
Click to collapse
Ok to clarify, after I unlocked via sunsine on 2-3.3, I rooted and I took the over the air so now I'm on the newer bootloader. Post those events I started to receive "failed to erase partition xxxx" I also just tried reflashing individual images from 4.4.4 su6-7 release and I still receive back "failed to erase... failed to flash... etc." I can get into fastboot mode but it seems crippled somehow.
crack.mech said:
Okay, So if you think you device is completely bricked, and I mean "NOT RECOVERABLE AT ALL" , you can try this: This may be a long shot, you might want to try uploading 'sbl2.mbn' file. If you are able to flash that, then you can try flashing a "Broken" sbl2 file and try uploading the ROM using Qualcomm emergency downloader. This method is very dangerous, and not for the faint hearted. It is used to root the droids which cannot be rooted by sunshine (post SU4-21) and you may lose your rooting capabilities all together, as this method uploads a non rootable bootloader (SU6-7). If you can get your hands on a copy of the bootloader you already have ( SU-2-3.3) , you should use that to unbrick from the bootloader mode. Try to refer this post for further details.
Click to expand...
Click to collapse
This sounds like a promising method. If I attempt this method, will I be able to recover root since I was previously unlocked via sunshine prior to bricking/soft-bricking?
t3knokon said:
This sounds like a promising method. If I attempt this method, will I be able to recover root since I was previously unlocked via sunshine prior to bricking/soft-bricking?
Click to expand...
Click to collapse
I don't think you can downgrade from SU6-7 to SU2-3.3. But I guess trying won't hurt. If you are able to flash a new sbl1.mbn and sbl2.mbn files, you might want to try rsd lite / mfastboot to flash the ROM image before you try the more dangerous path (CrashXXL's protocol, intentionally flash the broken bootloader and the using the qualcomm emergency mode to access the partitions) .
And answering your question:This WILL revoke your rooting capabilities and you will no longer have root. Though you can then use CrashXXL's method (same post linked above) to get root. But your bootloader will be locked, so no custom ROMs for you..
Good luck!
---------- Post added at 12:47 PM ---------- Previous post was at 12:42 PM ----------
BladeRunner said:
well, he's not a hardbrick as he can get into fastboot so I don't think he needs to use THIS method just yet
....
Click to expand...
Click to collapse
I think his bootloader is in a conflict as it might be looking for the certificates that are allowed, and sunshine is messing with the new installations. That is why I recommended a clean install of the device. But this is just guess work, I might be completely wrong!
crack.mech said:
I don't think you can downgrade from SU6-7 to SU2-3.3. But I guess trying won't hurt. If you are able to flash a new sbl1.mbn and sbl2.mbn files, you might want to try rsd lite / mfastboot to flash the ROM image before you try the more dangerous path (CrashXXL's protocol, intentionally flash the broken bootloader and the using the qualcomm emergency mode to access the partitions) .
And answering your question:This WILL revoke your rooting capabilities and you will no longer have root. Though you can then use CrashXXL's method (same post linked above) to get root. But your bootloader will be locked, so no custom ROMs for you..
Good luck!
---------- Post added at 12:47 PM ---------- Previous post was at 12:42 PM ----------
I think his bootloader is in a conflict as it might be looking for the certificates that are allowed, and sunshine is messing with the new installations. That is why I recommended a clean install of the device. But this is just guess work, I might be completely wrong!
Click to expand...
Click to collapse
Bummer. I'm not able to flash anything. All I get back is "Failed to erase partition." I did some extensive reading on the BLBroke/Qualcomm method and attempted that and still the bootloader replies back "failed to erase partition." I don't know what I should try next. Thoughts? Is the partitioning or memory bad on the phone?
t3knokon said:
Bummer. I'm not able to flash anything. All I get back is "Failed to erase partition." I did some extensive reading on the BLBroke/Qualcomm method and attempted that and still the bootloader replies back "failed to erase partition." I don't know what I should try next. Thoughts? Is the partitioning or memory bad on the phone?
Click to expand...
Click to collapse
sent you a PM directing you to a different site. Not sure they can help but it's worth a try.
BladeRunner said:
sent you a PM directing you to a different site. Not sure they can help but it's worth a try.
Click to expand...
Click to collapse
Thanks for that. I posted there as well... from a software standpoint, I'm curious to know what would be denying access to the partitions...
I messaged jcase and he looked at logs for the sunshine preinstall and they were clean. It's possibly a hardware failure unless someone else with bootloader knowledge, knows how to get around the partition permissions access. thoughts?
I've tried a myriad of different methods... i just seems the partitions are locked down... "Access Denied" "Flash Failed" I have no idea what else to try. What do ya'll think? Brick city?
t3knokon said:
I've tried a myriad of different methods... i just seems the partitions are locked down... "Access Denied" "Flash Failed" I have no idea what else to try. What do ya'll think? Brick city?
Click to expand...
Click to collapse
the prognosis is not good.
VBlack messaged me about shorting a pin to put the phone in Qualcomm Downloader mode... and then pushing software onto it to at least try to the partitions set up and get the bootloader in a manner which will allow for writing. If that doesn't work, there's nothing else to do. I read up on it extensively, and it's now a last ditch effort. I've never take apart a phone in that manner before, so it'll be a first for me.
Similar boat, here...using a programmer cord, I can flash a ROM onto the Maxx, but it stumble-boots into BP Tools mode after 3 or so failed 0-battery/unlocked bootloader warning screen loops. I can get it into bootloader with program cord, or first thing with factory cord. It won't charge at all, battery is new. Izzit hosed?
Sent from my XT1254 using XDA Free mobile app
Hello,
I neef urgent help, one day i was trying to flash custom recovery to my razr hd, it is i dont know 925 or 926. It is 16gb.
I was unsuccess to flash recovery then i was everytime getting fastboot msg and i had to press normal recovery everytime. Now i tried to factory data reset my mob and it is stuck on logo and time black screen with dots..
I have rsd lite but i think firmware i am not getting exact one thats why it is nog flashing... Please help me what to do. I have attached pics of recovery and fastboot.
I can help you but I need to know if you have correct drivers installed unless your using linux otherwise you need to install the correct drivers for the device. xt925 i think is gsm not sure and the xt926 is cdma 4g. I also need to know what version of android you were using so we flash the correct firmware(e.g, jelly bean, kit kat and so on). I also need to know what version of rsd you have because you might need to use a newer version. After we get your device back to life. I will give you the link to the correct recovery for the device. footnote: you will need to re-root device after it is flashed back to life, then flash correct recovery. You can only flash recovery if you unlocked the bootloader witch you do after device is rooted. 0 means bootloader is locked and 3 means it is unlocked. If you flash any recovery with a locked bootloader than you can soft brick or hard brick the device. If this is what you did and your just stuck at the Moto M than it just needs the correct stock firmware flashed so it can come back to life.
OGdroidster said:
I can help you but I need to know if you have correct drivers installed unless your using linux otherwise you need to install the correct drivers for the device. xt925 i think is gsm not sure and the xt926 is cdma 4g. I also need to know what version of android you were using so we flash the correct firmware(e.g, jelly bean, kit kat and so on). I also need to know what version of rsd you have because you might need to use a newer version. After we get your device back to life. I will give you the link to the correct recovery for the device. footnote: you will need to re-root device after it is flashed back to life, then flash correct recovery. You can only flash recovery if you unlocked the bootloader witch you do after device is rooted. 0 means bootloader is locked and 3 means it is unlocked.
Click to expand...
Click to collapse
Hello,
RSD lite version is: 6.1.5, Drivers i downloaded from motorola website and it detects my device... I was using last kitkat version.
Device has written backside Verizon 4g but i was using gsm network only 3g was working..
Please check attachment of recovery and fastboot screen.
efuzone said:
Hello,
RSD lite version is: 6.1.5, Drivers i downloaded from motorola website and it detects my device... I was using last kitkat version.
Device has written backside Verizon 4g but i was using gsm network only 3g was working..
Please check attachment of recovery and fastboot screen.
Click to expand...
Click to collapse
Thanks for the pics. Your status is zero witch means you tried to flash recovery with a locked bootloader this is your problem. we can fix this cause obviously you can still get to fastboot mode. You had the the first version of kitkat Bootloader. we are going to flash the cdma one then you can find the gsm flashable zip in the forum for this device to flash once you get going. Here is the link for the drivers witch are for 64 bit windows if your running 32 bit than let me know so I can link you to those instead. http://forum.xda-developers.com/attachment.php?attachmentid=3187938&d=1425146663. Here is a newer version of rsd lite. http://forum.xda-developers.com/attachment.php?attachmentid=3388466&d=1435873884 first uninstall the rsd you have now then install drivers then install the rsd lite i linked you to. here is the firmware for your device https://www.androidfilehost.com/?fid=24269982087011673 Let me know when you get going ill give the link to a page that explains root and how to unlock the bootloader.
OGdroidster said:
I can help you but I need to know if you have correct drivers installed unless your using linux otherwise you need to install the correct drivers for the device. xt925 i think is gsm not sure and the xt926 is cdma 4g. I also need to know what version of android you were using so we flash the correct firmware(e.g, jelly bean, kit kat and so on). I also need to know what version of rsd you have because you might need to use a newer version. After we get your device back to life. I will give you the link to the correct recovery for the device. footnote: you will need to re-root device after it is flashed back to life, then flash correct recovery. You can only flash recovery if you unlocked the bootloader witch you do after device is rooted. 0 means bootloader is locked and 3 means it is unlocked. If you flash any recovery with a locked bootloader than you can soft brick or hard brick the device. If this is what you did and your just stuck at the Moto M than it just needs the correct stock firmware flashed so it can come back to life.
Click to expand...
Click to collapse
OGdroidster said:
Thanks for the pics. Your status is zero witch means you tried to flash recovery with a locked bootloader this is your problem. we can fix this cause obviously you can still get to fastboot mode. You had the the first version of kitkat Bootloader. we are going to flash the cdma one then you can find the gsm flashable zip in the forum for this device to flash once you get going. Here is the link for the drivers witch are for 64 bit windows if your running 32 bit than let me know so I can link you to those instead. http://forum.xda-developers.com/attachment.php?attachmentid=3187938&d=1425146663. Here is a newer version of rsd lite. http://forum.xda-developers.com/attachment.php?attachmentid=3388466&d=1435873884 first uninstall the rsd you have now then install drivers then install the rsd lite i linked you to. here is the firmware for your device https://www.androidfilehost.com/?fid=24269982087011673 Let me know when you get going ill give the link to a page that explains root and how to unlock the bootloader.
Click to expand...
Click to collapse
Hello,
Thanks for your help please send drivers for Windows 7 32bit i am using 32bit OS.
efuzone said:
Hello,
Thanks for your help please send drivers for Windows 7 32bit i am using 32bit OS.
Click to expand...
Click to collapse
here is 32 bit drivers http://forum.xda-developers.com/attachment.php?attachmentid=3187936&d=1425146651
I forgot to tell you that for it to flash correctly you can't have a low battery witch I saw on your fastboot. you will need fastbook cable. A fastboot cable is used so you can boot or get to fastboot with or without battery like in your case the battery is to low. I got mine on amazon for 10 dollars. here is the link https://www.amazon.com/gp/aw/s/ref=...43801?k=fastboot+cable&sprefix=fastboot+cable
OGdroidster said:
here is 32 bit drivers http://forum.xda-developers.com/attachment.php?attachmentid=3187936&d=1425146651
I forgot to tell you that it flash correctly with a low battery witch I saw on your fastboot. you will need fastbook cable. A fastboot cable is used so you can boot or get to fastboot with or without battery like in your c
Click to expand...
Click to collapse
Hello,
Thanks are you sure, it wi flash on low battery because last time rsd and fasboot both were giving errors cant flash low battery then i had to charge it but flash was still not success due to firmware mismatch.
efuzone said:
Hello,
Thanks are you sure, it wi flash on low battery because last time rsd and fasboot both were giving errors cant flash low battery then i had to charge it but flash was still not success due to firmware mismatch.
Click to expand...
Click to collapse
You need a fastboot cable i put the link and explanation in previous post
---------- Post added at 08:12 AM ---------- Previous post was at 07:55 AM ----------
OGdroidster said:
You need a fastboot cable i put the link and explanation in previous post
Click to expand...
Click to collapse
I forgot to tell you that for it to flash correctly you can't have a low battery witch I saw on your fastboot. you will need fastbook cable. A fastboot cable is used so you can boot or get to fastboot with or without battery like in your case the battery is to low. I got mine on amazon for 10 dollars. here is the link https://www.amazon.com/gp/aw/s/ref=i...fastboot+cable
OGdroidster said:
I can help you but I need to know if you have correct drivers installed unless your using linux otherwise you need to install the correct drivers for the device. xt925 i think is gsm not sure and the xt926 is cdma 4g. I also need to know what version of android you were using so we flash the correct firmware(e.g, jelly bean, kit kat and so on). I also need to know what version of rsd you have because you might need to use a newer version. After we get your device back to life. I will give you the link to the correct recovery for the device. footnote: you will need to re-root device after it is flashed back to life, then flash correct recovery. You can only flash recovery if you unlocked the bootloader witch you do after device is rooted. 0 means bootloader is locked and 3 means it is unlocked. If you flash any recovery with a locked bootloader than you can soft brick or hard brick the device. If this is what you did and your just stuck at the Moto M than it just needs the correct stock firmware flashed so it can come back to life.
Click to expand...
Click to collapse
OGdroidster said:
You need a fastboot cable i put the link and explanation in previous post
---------- Post added at 08:12 AM ---------- Previous post was at 07:55 AM ----------
I forgot to tell you that for it to flash correctly you can't have a low battery witch I saw on your fastboot. you will need fastbook cable. A fastboot cable is used so you can boot or get to fastboot with or without battery like in your case the battery is to low. I got mine on amazon for 10 dollars. here is the link https://www.amazon.com/gp/aw/s/ref=i...fastboot+cable
Click to expand...
Click to collapse
I have ordered cable, because i am not able to charge mobile correctly, i will try when i will have cable in my hand.
efuzone said:
I have ordered cable, because i am not able to charge mobile correctly, i will try when i will have cable in my hand.
Click to expand...
Click to collapse
The cable doesnt charge phone just use it to flash the phone in fastboot mode and once you get the phone going put it on the charger.
efuzone said:
I have ordered cable, because i am not able to charge mobile correctly, i will try when i will have cable in my hand.
Click to expand...
Click to collapse
Did you recieve the fastboot cable?
OGdroidster said:
Did you recieve the fastboot cable?
Click to expand...
Click to collapse
Hello,
Really not yet i ordered from ebay china seller so still waiting for it
efuzone said:
Hello,
Really not yet i ordered from ebay china seller so still waiting for it
Click to expand...
Click to collapse
OK, that sucks. How you got to wait. Thats gonna take 2 to 4 weeks. At least from what I expierinced when I ordered loca glue on amazon and it was coming from china. If you need some guidence when you get the fastboot cable just send me a message.
OGdroidster said:
Did you recieve the fastboot cable?
Click to expand...
Click to collapse
Hello,
I received cable and now i am trying to flash firmware, it is giving error.
Downgrade security version
update gpt_main version failed
preflash validation failed for GPT
Tried another firmware getting same error, preflash preflash validation failed for gpt
Flash "VRZ_XT926_9.8.1Q-94-1_CFC" it is no on 6 stage showing invalid image size for partition tz
efuzone said:
Tried another firmware getting same error, preflash preflash validation failed for gpt
Flash "VRZ_XT926_9.8.1Q-94-1_CFC" it is no on 6 stage showing invalid image size for partition tz
Click to expand...
Click to collapse
Witch version of rsd are you using and are you flashing from fastboot and also if you can give me in order of steps per say of what you are doing from begining to end. Oh yea did you install the drivers from the link I gave you.
OGdroidster said:
Witch version of rsd are you using and are you flashing from fastboot and also if you can give me in order of steps per say of what you are doing from begining to end. Oh yea did you install the drivers from the link I gave you.
Click to expand...
Click to collapse
Hello,
I have latest drivers, latest RSD which you provided me. I have downloaded firmware which you given me it is giving gpt error, when i tried another one it is giving tz error and then again gpt error.
RSD Version is 6.2.4
efuzone said:
Hello,
I have latest drivers, latest RSD which you provided me. I have downloaded firmware which you given me it is giving gpt error, when i tried another one it is giving tz error and then again gpt error.
RSD Version is 6.2.4
Click to expand...
Click to collapse
You can't downgrade gpt and tz partition. You can only flash same signature version or higher.
rootdefyxt320 said:
You can't downgrade gpt and tz partition. You can only flash same signature version or higher.
Click to expand...
Click to collapse
Hello,
That is what i am looking i dont want to downgrade want to use same but from where i get same firmware?
efuzone said:
Hello,
I have latest drivers, latest RSD which you provided me. I have downloaded firmware which you given me it is giving gpt error, when i tried another one it is giving tz error and then again gpt error.
RSD Version is 6.2.4
Click to expand...
Click to collapse
Try this firmware here. It was the last update by Motorola. Here is the download link. https://www.androidfilehost.com/?fid=24269982087011676
I have a Google version Pixel 2 and have unlocked the bootloader (unlocked/relocked multiple times) and cannot flash any bootloader. I have tried flashing the "production" BL and the Dev Preview BL. I get the same error each time.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38728 KB)...
OKAY [ 0.110s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.125s
I have tried using the fastboot flashing unlock and fastboot flashing unlock_critical commands. I have relocked the BL then booted into the OS and used ADB to reboot to the BL, I still get the same error. I have tried changing the active slot to with no change.. I have tried the google version of platform tools, minimal adb, and another adb version I had from previous phones. I have downloaded the latest drivers from google no change.. I can flash and format other partitions, just not the BL (although I haven't tried format/erase bootloader, and I don't plan to)
I have tried different USB C cables, Google OEM, Samsung OEM, AUKEY .. different USB ports, different computers (although both with Windows 10 64bit).
Any suggestions?
lazarus2297 said:
I have a Google version Pixel 2 and have unlocked the bootloader (unlocked/relocked multiple times) and cannot flash any bootloader. I have tried flashing the "production" BL and the Dev Preview BL. I get the same error each time.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38728 KB)...
OKAY [ 0.110s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.125s
I have tried using the fastboot flashing unlock and fastboot flashing unlock_critical commands. I have relocked the BL then booted into the OS and used ADB to reboot to the BL, I still get the same error. I have tried changing the active slot to with no change.. I have tried the google version of platform tools, minimal adb, and another adb version I had from previous phones. I have downloaded the latest drivers from google no change.. I can flash and format other partitions, just not the BL (although I haven't tried format/erase bootloader, and I don't plan to)
I have tried different USB C cables, Google OEM, Samsung OEM, AUKEY .. different USB ports, different computers (although both with Windows 10 64bit).
Any suggestions?
Click to expand...
Click to collapse
Your not the only one there are others that have had similar issues, though i don't know the fix.
There is a script somewhere on another thread that might help. I will link.
---------- Post added at 05:19 AM ---------- Previous post was at 05:18 AM ----------
Hey you go.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Hopefully something in that will help
Just to be clear, are you using the latest fastboot? That's often an issue.
Some have had trouble with computers with usb-c ports. Have you tried a computer with usb-a and, of course, a usb-a to usb-c cable.
razrlover said:
Your not the only one there are others that have had similar issues, though i don't know the fix.
There is a script somewhere on another thread that might help. I will link.
---------- Post added at 05:19 AM ---------- Previous post was at 05:18 AM ----------
Hey you go.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Hopefully something in that will help
Click to expand...
Click to collapse
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
foosion said:
Just to be clear, are you using the latest fastboot? That's often an issue.
Some have had trouble with computers with usb-c ports. Have you tried a computer with usb-a and, of course, a usb-a to usb-c cable.
Click to expand...
Click to collapse
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
lazarus2297 said:
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
Click to expand...
Click to collapse
I'm not sure if this question will help, are you flashing the bootloader into the correct slot? I had issue early on with this and found that I needed to direct the flash to the correct slot. Just a thought
phonefreedom said:
I'm not sure if this question will help, are you flashing the bootloader into the correct slot? I had issue early on with this and found that I needed to direct the flash to the correct slot. Just a thought
Click to expand...
Click to collapse
Not exactly sure but I have tried changing the active slot to a or b.
I am using the command Fastboot flash bootloader "filename.img" (no quotations) I don't know how I would tell it to flash a specific slot other than whatever is the current active slot..
lazarus2297 said:
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
Click to expand...
Click to collapse
lazarus2297 said:
Not exactly sure but I have tried changing the active slot to a or b.
I am using the command Fastboot flash bootloader "filename.img" (no quotations) I don't know how I would tell it to flash a specific slot other than whatever is the current active slot..
Click to expand...
Click to collapse
+Natahranta had shared the following with me and I hope it helps in your case...
"Download factory image from Google, unpack it, insidebis another zip, there is boot.img file
Flash it to both slots A and B. It must be the same version/update your phone was on.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
If you're not sure which exactly stock rom build your phone is on, use the flash_all.bat to flash the whole image on your phone, to be sure you have no mismatch between system and boot. Just remove "-w" from the bat file so it doesn't erase your user data"
So i got it working here is what I did..
I used the factory image to flash back 100% stock and relocked the bootloader, I then signed my device up for the Dev Preview, and surprisingly I got the notification to install DP pretty quickly. After DP installed I rebooted into the bootloader and noticed that my bootloader version had changed to the DP BL version. I then unlocked with the standard Fastboot Flashing Unlock command and unlocked the bootloader. After the phone rebooted I shut it down and booted into the BL and flashed the stock BL (a downgrade) it was successful, so i flashed the DP BL version and it was successful as well. Rebooted normally into the OS and all is well.
Hopefully this will help anyone else having the same problem.
lazarus2297 said:
I have relocked the BL then booted into the OS
Click to expand...
Click to collapse
I don't have any suggestions for your issue. But don't relock it, ever. You are playing with fire, if it goes bad and it's locked you are done.
lazarus2297 said:
So i got it working here is what I did..
I used the factory image to flash back 100% stock and relocked the bootloader, I then signed my device up for the Dev Preview, and surprisingly I got the notification to install DP pretty quickly. After DP installed I rebooted into the bootloader and noticed that my bootloader version had changed to the DP BL version. I then unlocked with the standard Fastboot Flashing Unlock command and unlocked the bootloader. After the phone rebooted I shut it down and booted into the BL and flashed the stock BL (a downgrade) it was successful, so i flashed the DP BL version and it was successful as well. Rebooted normally into the OS and all is well.
Hopefully this will help anyone else having the same problem.
Click to expand...
Click to collapse
I had this problem and created a thread about it a month ago: https://forum.xda-developers.com/pixel-2/help/failed-remote-command-flash-error-t3701929. A couple other people in that thread are now also reporting the problem.
No one seemed to know what the " FAILED (remote: Command Flash Error)" means. I never figured it out.
At the time of the November update, however, I was able to sideload OTA images with adb without problem. I assume that the OTA method also updates the bootloader, like the Dev Preview did for you. I couldn't tell with the November update, though, because it had the same version of the bootloader in it as the one that shipped with the phone.
So I'm wondering if simply sideloading the current December OTA image with adb would accomplish the same thing you did, without having to lock the bootloader, unlock it again, and go through the pain of wiping the device. I wonder if there was just something weird about the original version of the bootloader. Weirdness like this was discussed early on with the Pixel 2 in this XDA article: https://www.xda-developers.com/pixel-2-failing-flash-factory-images/ If I'm right, then once one sideloads the December OTA image and gets a new bootloader, there may not be an issue flashing bootloaders with fastboot in the future. I assume that the Dev Preview also used the OTA method to update the device.
In other words, I'm wondering if the step of unlocking and relocking the bootloader was not necessary. You just had to do it to get the Developer Preview (right?).
Just guessing here. I haven't had time yet to try this.
Okay, I tried my idea above and I was correct. Simplying sideloading the December OTA image updates the bootloader. After that the problem is solved. I can successfully flash the bootloader .img file directly (from the factory image zip) using fastboot. So I assume going forward there should not be any problems flashing factory images, instead of sideloading OTA images.
This solution also avoids having to lock and unlock the bootloader and wipe the whole device in the process.
cb474 said:
Simplying sideloading the December OTA image updates the bootloader.
Click to expand...
Click to collapse
My problem is that I have TWRP installed and it won't sideload nor flash the OTA file. I am trying to figure out how to flash the factory recovery. Unlike the factory images of before, there is no obvious recovery image in the zip.
-----------
Nevermind. I figured out that recovery is part of boot now. I flashed the factory boot and flashing OTA now.
snovvman said:
My problem is that I have TWRP installed and it won't sideload nor flash the OTA file. I am trying to figure out how to flash the factory recovery. Unlike the factory images of before, there is no obvious recovery image in the zip.
Click to expand...
Click to collapse
I'm not really sure how to solve that problem. Perhaps you should ask in the TWRP thread. I thought that when you install TWRP it backs up the recovery and has a way to restore it. But I could be wrong about that. You're correct that the recovery image does not seem to be included in the factory image zip like it used to be. I have seen other people mention that.
cb474 said:
I'm not really sure how to solve that problem. Perhaps you should ask in the TWRP thread. I thought that when you install TWRP it backs up the recovery and has a way to restore it. But I could be wrong about that. You're correct that the recovery image does not seem to be included in the factory image zip like it used to be. I have seen other people mention that.
Click to expand...
Click to collapse
Thanks for replying. Silly me, I was thinking the old way of doing business, where the recovery had its own image/partition. I figured out that recovery is part of boot, so I flashed boot and got the factory recovery back. I'm on 8.1 now.
snovvman said:
Thanks for replying. Silly me, I was thinking the old way of doing business, where the recovery had its own image/partition. I figured out that recovery is part of boot, so I flashed boot and got the factory recovery back. I'm on 8.1 now.
Click to expand...
Click to collapse
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
cb474 said:
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
Click to expand...
Click to collapse
So you know, TWRP for the first gen Pixels never left beta. They worked well enough... For Pixel 2s, I use the current beta for backups and they are handy for certain things. For now I am booting to TWRP to flash Magisk. For me, it is more convenient than patching.
cb474 said:
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php
kendong2 said:
https://forum.xda-developers.com/showpost.php
Click to expand...
Click to collapse
That link leads to nothing.
---------- Post added at 01:13 AM ---------- Previous post was at 01:11 AM ----------
snovvman said:
So you know, TWRP for the first gen Pixels never left beta. They worked well enough... For Pixel 2s, I use the current beta for backups and they are handy for certain things. For now I am booting to TWRP to flash Magisk. For me, it is more convenient than patching.
Click to expand...
Click to collapse
Yeah, I saw that. I'm just hoping with what was learned from the original Pixel and given that supposedly most phones will eventually use the A/B partition scheme that maybe TWRP will advance further on the Pixel 2. I really miss nandroid backups. I miss LineageOS too. Everything was so much simpler on my old Nexus 4. And I wasn't constantly feeling like I was going to brick my device every time I tried to do something.
cb474 said:
That link leads to nothing.
Click to expand...
Click to collapse
Sorry, did that on the phone. Was supposed to go here: https://forum.xda-developers.com/showpost.php?p=74704694&postcount=155
TWRP 3.2.0.0 final release (as I understand it) has been announced a few days ago. Don't know why the thread title still says beta.
This is freaking weird. Anyway, followed post #11 to sideload DEC OTA zip in stock recovery, and now finally I have a bootloader that is 0066 on both slot a and b. Thanked @cb474 !