Related
I manage to relock my XT925 Bootloader.
Process is very simple
THIS IS FOR WINDOWS ONLY!!!! Thanks @skeevydude
Warning!!!
The process will delete User Data so backup First.
Please do not attempt on XT926
Requirement
1. Original SBF/XML (latest recommended if available) get it here
2. Motorola Fastboot Get it here (taken from Moto G forum) Credit to the Owner
3. Motorola Device Manager (for drivers)
4. For Boot Logo Fix Please refer here
5. Flash script (Attached Below)
FASTBOOT STATUS WILL CHANGE FROM
Device is Unlocked Status Code: 3 To Device is Locked Status Code: 2
Steps
1. Download and extract the original SBF/XML
2. Download and extract the Motorola Fastboot.
3. Download and extract the Flash Script
4. Copy all the files from original SBF/XML to fastboot folder and also copy the flash script to fastboot folder
5. Put the phone into AP Fastboot Mode then execute the flash script "XT925_erase_userdata"
6. Wait until the flash process finish.
7. Now your bootloader is locked.
For Boot Logo Fix Please refer here
Please feel free to Edit/Delete the thread
Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my C6802 using Tapatalk
kumeipark said:
I manage to relock my XT925 Bootloader.
Process is very simple
Warning!!!
The process will delete User Data so backup First.
Please do not attempt on XT926
Requirement
1. Original SBF/XML (latest recommended if available) get it here
2. Motorola Fastboot Get it here (taken from Moto G forum) Credit to the Owner
3. Motorola Device Manager (for drivers)
4. For Boot Logo Fix Please refer here
5. Flash script (Attached Below)
FASTBOOT STATUS WILL CHANGE FROM
Device is Unlocked Status Code: 3 To Device is Locked Status Code: 2
Steps
1. Download and extract the original SBF/XML
2. Download and extract the Motorola Fastboot.
3. Download and extract the Flash Script
4. Copy all the files from original SBF/XML to fastboot folder and also copy the flash script to fastboot folder
5. Put the phone into AP Fastboot Mode then execute the flash script "XT925_erase_userdata"
6. Wait until the flash process finish.
7. Now your bootloader is locked.
For Boot Logo Fix Please refer here
Click to expand...
Click to collapse
so all that's necessary to type "mfastboot oem lock", or is the flash back to stock for safety reasons....listing steps isn't that helpful if the reasons aren't posted.
and have you tested "mfastboot oem unlock" or does the exploit need to be ran again to unlock the bootloader?
....shouldn't post about locking the bootloader without saying if it can be unlocked again or not.
EDIT:
And label or mention that this is for Windows Only
Check the flash script with notepad and I hope you will understand.
Please feel free to edit
Thanks
Sent from my C6802 using Tapatalk
kumeipark said:
Check the flash script with notepad and I hope you will understand.
Please feel free to edit
Thanks
Sent from my C6802 using Tapatalk
Click to expand...
Click to collapse
Other than oem lock begin, it doesn't look that different than any other automated flashing setup. Basically, are those signed partitions necessary to lock the bootloader on this phone (Nexus 4 can fastboot oem lock while running CM), or would a fastbooted factory reset good enough to lock the phone running a custom rom? And can the phone be unlocked, exploit, fastboot, or other, after doing this -- I think that's the most important question.
Not trying to nitpick or whatever, but some of my questions are important to know before doing something like intentionally locking the bootloader w/o knowing if it can unlock again or not (I assume it can, but still, it would be nice to have that confirmed before doing this...not that I am, I don't even have a 925...but I do get asked a lot of questions about every single 8960 phone...it's what happens when you're a helpful RC)
skeevydude said:
Other than oem lock begin, it doesn't look that different than any other automated flashing setup. Basically, are those signed partitions necessary to lock the bootloader on this phone (Nexus 4 can fastboot oem lock while running CM), or would a fastbooted factory reset good enough to lock the phone running a custom rom? And can the phone be unlocked, exploit, fastboot, or other, after doing this -- I think that's the most important question.
Not trying to nitpick or whatever, but some of my questions are important to know before doing something like intentionally locking the bootloader w/o knowing if it can unlock again or not (I assume it can, but still, it would be nice to have that confirmed before doing this...not that I am, I don't even have a 925...but I do get asked a lot of questions about every single 8960 phone...it's what happens when you're a helpful RC)
Click to expand...
Click to collapse
Yes you're right!
the only difference is the oem lock begin and oem lock.
You need those signed partitions
By the way you can unlock the bootloader again from motorola website.
Thanks for correcting me.
kumeipark said:
Yes you're right!
the only difference is the oem lock begin and oem lock.
You need those signed partitions
By the way you can unlock the bootloader again from motorola website.
Thanks for correcting me.
Click to expand...
Click to collapse
So basically this method should only be done by phones that can officially be unlocked by Motorola? Personally, I don't want to be the one that finds out a hack unlocked phone can't go from status 2 to status 3...but that's what random idiots who flash anything they see are for...(un)fortunately for us, there's a lot of them...
Seeing as how a ton of us are running hacked unlocked phones, including myself, and how not everyone here actually has a RAZR HD, including myself...anything discussing bootloaders and locking them needs to be well documented, if only to cover your ass when some dipcrap does this and screws their self. Though it does say XT925 in the thread title and don't do this on a 926 in the thread...
To clear all doubts I took the liberty to unlock my bootloader after relocking it
Code:
C:\Users\xxxxx\Desktop\New folder\RAZR HD Fastboot>mfastboot oem get_unlock_data
...
(bootloader) 3A24528415225372#54413234303032
(bootloader) 49523300000000000000000000#2144
(bootloader) 9FCE87F32A6179FAAA0D23AD8BCCF85
(bootloader) E5675#1660910902000100000011110
(bootloader) 0000000
OKAY [ 0.272s]
finished. total time: 0.273s
C:\Users\xxxxx\Desktop\New folder\RAZR HD Fastboot>mfastboot oem unlock VZJUGTAYKHYZA5KXXXXX
...
(bootloader) Unlock completed! Wait to reboot
Now relocking again!
Code:
C:\Users\xxxxx\Desktop\New folder\RAZR HD Fastboot>XT925_erase_userdata.bat
Flashing bootloader images ...
So as to use latest flash capabilities
...
(bootloader) Ready to flash signed images
OKAY [ 0.273s]
finished. total time: 0.274s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'partition' (32 KB)...
OKAY [ 0.012s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
OKAY [ 0.349s]
finished. total time: 0.364s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'sbl1' (101 KB)...
OKAY [ 0.018s]
writing 'sbl1'...
OKAY [ 0.482s]
finished. total time: 0.500s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'sbl2' (127 KB)...
OKAY [ 0.019s]
writing 'sbl2'...
OKAY [ 0.892s]
finished. total time: 0.913s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'sbl3' (512 KB)...
OKAY [ 0.046s]
writing 'sbl3'...
OKAY [ 1.076s]
finished. total time: 1.124s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'rpm' (140 KB)...
OKAY [ 0.023s]
writing 'rpm'...
OKAY [ 0.472s]
finished. total time: 0.496s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'tz' (192 KB)...
OKAY [ 0.024s]
writing 'tz'...
OKAY [ 0.495s]
finished. total time: 0.521s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'aboot' (256 KB)...
OKAY [ 0.029s]
writing 'aboot'...
OKAY [ 0.773s]
finished. total time: 0.804s
Flashing modem SW...
(bootloader) Variable not supported!
target max-download-size: 30MB
Multi-Flash is enabled!
sending 'modem' (30720 KB)...
OKAY [ 2.278s]
writing 'modem'...
OKAY [ 1.160s]
sending 'modem' (17412 KB)...
OKAY [ 4.233s]
writing 'modem'...
OKAY [ 1.190s]
finished. total time: 8.865s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'fsg' (2852 KB)...
OKAY [ 0.218s]
writing 'fsg'...
OKAY [ 1.371s]
finished. total time: 1.591s
erasing 'modemst1'...
OKAY [ 0.770s]
finished. total time: 0.770s
erasing 'modemst2'...
OKAY [ 0.749s]
finished. total time: 0.750s
Flashing AP Images...
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'logo' (1709 KB)...
OKAY [ 0.134s]
writing 'logo'...
OKAY [ 1.429s]
finished. total time: 1.565s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'devtree' (512 KB)...
OKAY [ 0.047s]
writing 'devtree'...
OKAY [ 0.515s]
finished. total time: 0.564s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'boot' (10240 KB)...
OKAY [ 0.762s]
writing 'boot'...
OKAY [ 4.136s]
finished. total time: 4.900s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'recovery' (10240 KB)...
OKAY [ 0.762s]
writing 'recovery'...
OKAY [ 3.165s]
finished. total time: 3.928s
(bootloader) Variable not supported!
target max-download-size: 30MB
Multi-Flash is enabled!
sending 'system' (30720 KB)...
OKAY [ 2.275s]
writing 'system'...
OKAY [ 3.718s]
sending 'system' (30720 KB)...
OKAY [ 5.234s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.234s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.225s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.257s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.249s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.250s]
writing 'system'...
OKAY [ 1.359s]
sending 'system' (30720 KB)...
OKAY [ 5.235s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.227s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.246s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.256s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.240s]
writing 'system'...
OKAY [ 1.365s]
sending 'system' (30720 KB)...
OKAY [ 5.085s]
writing 'system'...
OKAY [ 1.361s]
sending 'system' (30720 KB)...
OKAY [ 5.210s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.245s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.230s]
writing 'system'...
OKAY [ 1.359s]
sending 'system' (30720 KB)...
OKAY [ 5.238s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.241s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.259s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.247s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.234s]
writing 'system'...
OKAY [ 1.361s]
sending 'system' (30720 KB)...
OKAY [ 5.248s]
writing 'system'...
OKAY [ 1.361s]
sending 'system' (30720 KB)...
OKAY [ 5.240s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.249s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.250s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.219s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (4659 KB)...
OKAY [ 3.300s]
writing 'system'...
OKAY [ 0.641s]
finished. total time: 174.838s
(bootloader) Variable not supported!
target max-download-size: 30MB
Multi-Flash is enabled!
sending 'cdrom' (30720 KB)...
OKAY [ 2.274s]
writing 'cdrom'...
OKAY [ 3.178s]
sending 'cdrom' (22538 KB)...
OKAY [ 4.625s]
writing 'cdrom'...
OKAY [ 2.594s]
finished. total time: 12.675s
erasing 'tombstones'...
OKAY [ 0.905s]
finished. total time: 0.906s
erasing 'cache'...
OKAY [ 1.223s]
finished. total time: 1.224s
Erasing userdata...
erasing 'userdata'...
OKAY [ 4.437s]
finished. total time: 4.438s
Locking Bootloader...
...
FAILED (status read failed (Too many links))
finished. total time: 21.883s
All images flashed. Check logs for errors!
Press any key to continue . . .
C:\Users\xxxxx\Desktop\New folder\RAZR HD Fastboot>
While relocking bootloader it says
Code:
Locking Bootloader...
...
FAILED (status read failed (Too many links))
But the device will locked
Please note: Some text are altered for privacy concern
I thought the status code for locked was 0?
Sent from my RAZR HD using XDA Free mobile app
peladoro said:
I thought the status code for locked was 0?
Sent from my RAZR HD using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I read in another forum about an user has "discovered this re-lock method", and asked in Motorola's forum about the status code and the meanings and the answer was something like this
Status code 0 =locked with warranty
Status code 3 = unlocked without warranty
Status code 2= relocked but also without warranty
And I don't remember very well if status code 1 is for developers edition phones and it means relocked but with warranty..
Enviado desde mi RAZR HD mediante Tapatalk
Thanks!
Thanks, man!
The outcome of the procedure was perfect! Thanks a lot!
I have only one question: After travarmos the device, we can update via OTA?
Hugs!
No issue on OTA with Locked or unlocked bootloader.
If rooted there's issue
Sent from my C6802 using Tapatalk
joaomanobrown said:
Thanks, man!
The outcome of the procedure was perfect! Thanks a lot!
I have only one question: After travarmos the device, we can update via OTA?
Hugs!
Click to expand...
Click to collapse
kumeipark said:
No issue on OTA with Locked or unlocked bootloader.
If rooted there's issue
Sent from my C6802 using Tapatalk
Click to expand...
Click to collapse
Yup, as @kumeipark stated, no issue with taking OTA just because you are unlocked.
Just remember, rooting is a software change on your phone, so that will mess up taking OTAs as you've modified the /system directory.
In the case of unlocking the bootloader, that is a physical change in the phone firmware itself. It does not modify the OS software in any way, hence the OTA will take since you didn't modify the OS in any way.
The reason the OTA's check for modification is to prevent bricking a device that may have modified the OS software in some way which could result in a device that boot loops. This way, they know for a fact that the software is either completely stock or it's been modified which means that the OTA cannot patch the software correctly, especially if some system files have been modified or removed altogether (or bloat apps as well).
Thanks!
Thank's guy's!
nice
Please, how do I unlock again ... at the motorola site was unable
HugoTJB said:
Please, how do I unlock again ... at the motorola site was unable
Click to expand...
Click to collapse
Previously how you unlock your BL??
Is your model XT925??
iBolski said:
Yup, as @kumeipark stated, no issue with taking OTA just because you are unlocked.
Just remember, rooting is a software change on your phone, so that will mess up taking OTAs as you've modified the /system directory.
In the case of unlocking the bootloader, that is a physical change in the phone firmware itself. It does not modify the OS software in any way, hence the OTA will take since you didn't modify the OS in any way.
The reason the OTA's check for modification is to prevent bricking a device that may have modified the OS software in some way which could result in a device that boot loops. This way, they know for a fact that the software is either completely stock or it's been modified which means that the OTA cannot patch the software correctly, especially if some system files have been modified or removed altogether (or bloat apps as well).
Click to expand...
Click to collapse
I read your post months ago before having my phone updated, and I read it now after having updated On The Air.
What do you mean with "will mess up taking OTA" exactly?
It goes without saying you can't get OTA updates if you're running on modified version of OS; but if you have an unlocked bootloader as mine and you are on an official motorola build, you can still get OTA and update them without problems.
Here's the story:
- bought my xt925 last year and it mounted the build 4.1.2 the one with the camera shutter always (and forced) on, by the grace of American lawmakers (I am in Italy);
- since the 4.1.2 is slow as hell, I unlocked the bootloader early in january this year and put on the cyanogen something;
- I tried the cyanogen mod for two months then I flashed back this one: Android 4.1.2
Blur_Version.98.21.26002.XT925.Orange.en.GB
- on october 7th I got the OTA message to uptade to kitkat 4.4.2, then I updated the phone and now I am working on 4.4.2.
There are a couple of things I don't get: how do I relock bootloader without flashing 4.1.2 and what happens if I do a factory reset from recovery.
Graf Schmidt said:
I read your post months ago before having my phone updated, and I read it now after having updated On The Air.
What do you mean with "will mess up taking OTA" exactly?
It goes without saying you can't get OTA updates if you're running on modified version of OS; but if you have an unlocked bootloader as mine and you are on an official motorola build, you can still get OTA and update them without problems.
Here's the story:
- bought my xt925 last year and it mounted the build 4.1.2 the one with the camera shutter always (and forced) on, by the grace of American lawmakers (I am in Italy);
- since the 4.1.2 is slow as hell, I unlocked the bootloader early in january this year and put on the cyanogen something;
- I tried the cyanogen mod for two months then I flashed back this one: Android 4.1.2
Blur_Version.98.21.26002.XT925.Orange.en.GB
- on october 7th I got the OTA message to uptade to kitkat 4.4.2, then I updated the phone and now I am working on 4.4.2.
There are a couple of things I don't get: how do I relock bootloader without flashing 4.1.2 and what happens if I do a factory reset from recovery.
Click to expand...
Click to collapse
Uh, reflashing doesn't lock the boot loader. Also, I never said you can't take an OTA with an unlocked bootloader. I said you won't be able to take an OTA if you are rooted, since that messes with the system files.
As you know, you unlock the XT925 via the Moto tools. As for relocking it, I have no idea. I do know with the Nexus 7, flashing a new image doesn't relock it. I have to actually do it via the ADB command, so I believe it's the same thing with the XT925. You get an unlock code from Motorola and you use that to unlock the bootloader and have to use the command to relock it.
Doing a factory reset won't relock it.
Looks like mfastboot check patitions checksum/size with GPT partition (patition_signed)
Sent from my XT925 using Tapatalk
Manually flashing a a stock rom as the flashall.bat freaks out and this is what happens,.
sending 'boot' (5898 KB)...
OKAY [ 0.922s]
writing 'boot'...
OKAY [ 0.297s]
finished. total time: 1.219s
sending 'recovery' (6398 KB)...
OKAY [ 1.250s]
writing 'recovery'...
OKAY [ 0.359s]
finished. total time: 1.609s
sending 'userdata' (98413 KB)...
OKAY [ 3.864s]
writing 'userdata'...
OKAY [ 5.012s]
finished. total time: 8.876s
sending 'system' (523357 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 420.405s
Have you tried to change USB ports/ cables?
Bouncer5 said:
Manually flashing a a stock rom as the flashall.bat freaks out and this is what happens,.
sending 'boot' (5898 KB)...
OKAY [ 0.922s]
writing 'boot'...
OKAY [ 0.297s]
finished. total time: 1.219s
sending 'recovery' (6398 KB)...
OKAY [ 1.250s]
writing 'recovery'...
OKAY [ 0.359s]
finished. total time: 1.609s
sending 'userdata' (98413 KB)...
OKAY [ 3.864s]
writing 'userdata'...
OKAY [ 5.012s]
finished. total time: 8.876s
sending 'system' (523357 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 420.405s
Click to expand...
Click to collapse
Have you tried just flashing the system.img on its own? Is it just me, or does that system image seem excessively large for a stock image? I would try a new cable, and maybe try redownloading the system img just in case.
ariesgodofwar said:
Have you tried just flashing the system.img on its own? Is it just me, or does that system image seem excessively large for a stock image? I would try a new cable, and maybe try redownloading the system img just in case.
Click to expand...
Click to collapse
Yea it is quite large, I have tried flashing the system.img on its own, It also eventually times out. I have also tried different system.img files. I have tried different USB cables, different USB ports, heck last night I even tried a different computer and OS! Still always fails.
At this point the only thing I was able to do with my phone was get Ubuntu Touch on it so it is just slightly more useful than a paperweight.
With Ubuntu Touch I have managed to get Cyanogenmod.zip onto the phone reflash the recovery and install the .zip I am now back on android, I cannot however get back to a stock image.
Download: https://developer.android.com/preview/download.html
Credit to @skaforey for the scoop over at the Pixel2 XL forum, and at this point just about every other android tech site.
Interesting change to the navigation bar. Looks like they're trying to reduce the burn in problem people are getting.
Does this use visualcore
It keeps telling me I don't have any eligible devices.. as I type this on my fully stock Pixel 2.
Edit: I'm now able to enroll!
TLDR; Make sure you update your fastboot first!
I flashed the 8.1 beta using an old fastboot (that didn't know about slots) and now I'm stuck in the bootloader. I can't get android to boot, and I can't even get into the stock recovery or download options.
I've tried flashing the stock image several times, but that didn't do any good.
Any Help would be greatly appreciated!
Thanks!
pvillegeek said:
TLDR; Make sure you update your fastboot first!
I flashed the 8.1 beta using an old fastboot (that didn't know about slots) and now I'm stuck in the bootloader. I can't get android to boot, and I can't even get into the stock recovery or download options.
I've tried flashing the stock image several times, but that didn't do any good.
Any Help would be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Download the factory and flash-all.bat?
Chronzy said:
Download the factory and flash-all.bat?
Click to expand...
Click to collapse
I tried that. It appeared to flash correctly, but didn't help.
Code:
platform-tools>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38728 KB)...
OKAY [ 0.125s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
(bootloader) Updating: partition:1 @0000D000 sz=0000B000
(bootloader) Updating: partition:2 @00018000 sz=0000B000
(bootloader) Updating: partition:3 @00023000 sz=0000B000
(bootloader) Updating: partition:4 @0002E000 sz=0000B000
(bootloader) Updating: partition:5 @00039000 sz=0000B000
(bootloader) Updating: cmnlib64 @00044000 sz=00049000
(bootloader) Updating: cmnlib @0008D000 sz=00038000
(bootloader) Updating: devcfg @000C5000 sz=0000F000
(bootloader) Updating: hyp @000D4000 sz=00040000
(bootloader) Updating: keymaster @00114000 sz=00046000
(bootloader) Updating: lockbooter @0015A000 sz=00016000
(bootloader) Updating: pmic @00170000 sz=0000D000
(bootloader) Updating: rpm @0017D000 sz=0003A000
(bootloader) Updating: tz @001B7000 sz=001DB000
(bootloader) Updating: xbl @00392000 sz=003A2000
(bootloader) Updating: apdp @00734000 sz=00004000
(bootloader) Updating: msadp @00738000 sz=00004000
(bootloader) Updating: hosd @0073C000 sz=01E31000
(bootloader) Updating: abl @0256D000 sz=00065000
OKAY [ 1.016s]
finished. total time: 1.141s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 0.172s]
writing 'radio_a'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.547s]
finished. total time: 0.734s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 57071874048
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13933563
Block groups: 426
Reserved block group size: 1024
Created filesystem with 11/3489792 inodes and 265112/13933563 blocks
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00122-1708311414
Serial Number........: FA79C1A05734
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
OKAY [ 0.016s]
sending 'boot_a' (32768 KB)...
OKAY [ 0.109s]
writing 'boot_a'...
OKAY [ 0.297s]
erasing 'system_a'...
OKAY [ 0.188s]
sending sparse 'system_a' 1/4 (524284 KB)...
OKAY [ 2.219s]
writing 'system_a' 1/4...
OKAY [ 4.782s]
sending sparse 'system_a' 2/4 (524284 KB)...
OKAY [ 2.109s]
writing 'system_a' 2/4...
OKAY [ 4.813s]
sending sparse 'system_a' 3/4 (524284 KB)...
OKAY [ 2.219s]
writing 'system_a' 3/4...
OKAY [ 4.798s]
sending sparse 'system_a' 4/4 (322300 KB)...
OKAY [ 1.328s]
writing 'system_a' 4/4...
OKAY [ 2.954s]
erasing 'system_b'...
OKAY [ 0.203s]
sending sparse 'system_b' 1/2 (524284 KB)...
OKAY [ 2.188s]
writing 'system_b' 1/2...
OKAY [ 4.798s]
sending sparse 'system_b' 2/2 (80600 KB)...
OKAY [ 0.359s]
writing 'system_b' 2/2...
OKAY [ 0.750s]
erasing 'vendor_a'...
OKAY [ 0.188s]
sending 'vendor_a' (346964 KB)...
OKAY [ 1.062s]
writing 'vendor_a'...
OKAY [ 3.188s]
Setting current slot to 'a'...
OKAY [ 0.031s]
erasing 'userdata'...
OKAY [ 0.750s]
sending 'userdata' (140906 KB)...
OKAY [ 0.438s]
writing 'userdata'...
OKAY [ 1.516s]
rebooting...
finished. total time: 41.536s
Press any key to exit...
pvillegeek said:
I tried that. It appeared to flash correctly, but didn't help.
Click to expand...
Click to collapse
Read up over at the 2XL forum: https://forum.xda-developers.com/pixel-2-xl/how-to/8-1-developer-images-available-t3694556/page3
Some talk about having to extract and flash files individually. Maybe that'll help. I've had to do that on devices in the past.
dude, beware flashing this, thought I bricked my device, had to manually flash everything.... wtf google
I'm waiting for the OTA tomorrow. Looking forward to the colored nav bar and fading buttons! It's nice to see Google taking action on something rather than having to enable an accessibility service for a 3rd party app to color the navigation bar, and the fading buttons are a nice touch.
Chronzy said:
Read up over at the 2XL forum: https://forum.xda-developers.com/pixel-2-xl/how-to/8-1-developer-images-available-t3694556/page3
Some talk about having to extract and flash files individually. Maybe that'll help. I've had to do that on devices in the past.
Click to expand...
Click to collapse
Thanks, I tried that, but still no luck. I ended up contacting google support and they are sending a replacement.
pvillegeek said:
Thanks, I tried that, but still no luck. I ended up contacting google support and they are sending a replacement.
Click to expand...
Click to collapse
Wow, that's quite the hook up. Do you have the insurance?
Has anyone noticed a difference in the HDR+ processing speed or something like that? (preliminary Pixel core was enabled with this 8.1 DP1)
www.androidpolice.com/2017/10/26/an...ual-core-chip-now-enabled-developers-can-use/
Who's received the update via OTA after signing up for the beta? I'm still waiting here on my Pixel 2.
quakeaz said:
Who's received the update via OTA after signing up for the beta? I'm still waiting here on my Pixel 2.
Click to expand...
Click to collapse
Also waiting here.
pvillegeek said:
Thanks, I tried that, but still no luck. I ended up contacting google support and they are sending a replacement.
Click to expand...
Click to collapse
You fastboot flashing unlock_critcal? I doubt it's bricked.
Sent from my Nexus 6 using Tapatalk
quakeaz said:
Who's received the update via OTA after signing up for the beta? I'm still waiting here on my Pixel 2.
Click to expand...
Click to collapse
Still waiting...
The developer preview from Pixel 2 is at moment down, I think they make changes.
Gesendet von meinem Pixel 2 mit Tapatalk
How stable are the developer previews, in general?
cb474 said:
How stable are the developer previews, in general?
Click to expand...
Click to collapse
In general they are rather stable, but there are exceptions.
As to any particular phone, you can wait a couple of days and see if there are many reports of problems.
---------- Post added at 05:51 AM ---------- Previous post was at 05:50 AM ----------
Does anyone have the direct link to the OTA they are pushing out?
See https://forum.xda-developers.com/showpost.php?p=74307421&postcount=88 for the link for the Pixel 2 XL.
Hi bro's , today i tried to flash a rom using a script , then i was without internal space then i repair that , later i recovered from the fullbrick with the bankflash , and now i try to flash the rom and only i get these errors.
In the bootloader logs it says : 'fastboot reason : Failed to initialize partition table'
and in the console of commands
Script by @evogp ...
Flashing GPT and bootloaders ...
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
Security version downgrade
Image primary_gpt failed validation
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.075s
error: cannot load 'motoboot.img'
Flashing Modem SW ...
sending 'modem' (76954 KB)...
OKAY [ 2.510s]
writing 'modem'...
Invalid partition name modem
FAILED (remote failure)
finished. total time: 2.517s
Flash AP images ...
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
Security version downgrade
Image primary_gpt failed validation
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.068s
sending 'logo' (2186 KB)...
OKAY [ 0.074s]
writing 'logo'...
Invalid partition name logo
FAILED (remote failure)
finished. total time: 0.084s
sending 'boot' (16384 KB)...
OKAY [ 0.538s]
writing 'boot'...
Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.547s
sending 'recovery' (16484 KB)...
OKAY [ 0.538s]
writing 'recovery'...
Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.545s
sending 'system' (261013 KB)...
OKAY [ 9.481s]
writing 'system'...
Invalid partition name system
FAILED (remote failure)
finished. total time: 9.489s
sending 'system' (250842 KB)...
OKAY [ 8.065s]
writing 'system'...
Invalid partition name system
FAILED (remote failure)
finished. total time: 8.072s
sending 'system' (254485 KB)...
OKAY [ 8.779s]
writing 'system'...
Invalid partition name system
FAILED (remote failure)
finished. total time: 8.787s
Wipe Cache and Data ...
erasing 'userdata'...
Permission denied
FAILED (remote failure)
finished. total time: 0.011s
erasing 'cache'...
Permission denied
FAILED (remote failure)
finished. total time: 0.008s
Installation Complete!
What script are you using? A script with motoboot.img seems pretty old...
Also, which stock firmware are you trying to flash? The firmware must be as new or newer than your bootloader, else you'd get the security downgrade and pre-flash validation errors.
i once deleted my bootloader by accident. followed this guide. see this
https://forum.xda-developers.com/mo...4-plus-hardbrick-solved-guide-t3657761/page32
Hi everybody!
I installed Xiaomi.eu 12 stable few weeks ago and the device worked perfectly until this morning. When I unlocked the screen and clicked on the toggle wifi to activate it, the device stopped working. Totally freezed.
I tried with a reboot but the device was stuck to the boot logo. So I've tried to enter the recovery mode (Orange Fox in my case) and also it was stuck in the Orangefox logo. The only thing which works is fastboot.
So I decided to try to reset the phone, without success in all the cases. Here all my attempts:
1) Install other recoveries with fastboot (Orangefox, TWRP, Stock recovery) and depite the installation succeed, none of them worked; when I try to enter the recovery mode, it's still stuck into OrangeFox logo (also after I've installed other recoveries).
2) Install MIUI global fastboot rom with MiFlash tool. It reports error xbl.
3) The last thing I tried: several attempts with fastboot and MIUI global fastboot ROMs. In all the cases the reported error was the write protection of xbl.
NB: I used both command prompt of linux and windows without success.
Code:
[[email protected] lavender1]$ sudo ./flash_all.sh
product: lavender
Sending 'antirbpass' (8 KB) OKAY [ 0.005s]
Writing 'antirbpass' OKAY [ 0.000s]
Finished. Total time: 0.013s
Sending 'xbl' (2512 KB) OKAY [ 0.075s]
Writing 'xbl' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'xblbak' (2512 KB) OKAY [ 0.076s]
Writing 'xblbak' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'tz' (1924 KB) OKAY [ 0.061s]
Writing 'tz' OKAY [ 0.013s]
Finished. Total time: 0.082s
Sending 'tzbak' (1924 KB) OKAY [ 0.060s]
Writing 'tzbak' OKAY [ 0.014s]
Finished. Total time: 0.076s
Sending 'rpm' (219 KB) OKAY [ 0.015s]
Writing 'rpm' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'rpmbak' (219 KB) OKAY [ 0.011s]
Writing 'rpmbak' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'hyp' (272 KB) OKAY [ 0.011s]
Writing 'hyp' OKAY [ 0.002s]
Finished. Total time: 0.016s
Sending 'hypbak' (272 KB) OKAY [ 0.011s]
Writing 'hypbak' OKAY [ 0.003s]
Finished. Total time: 0.016s
Sending 'pmic' (38 KB) OKAY [ 0.006s]
Writing 'pmic' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'pmicbak' (38 KB) OKAY [ 0.002s]
Writing 'pmicbak' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'keymaster' (305 KB) OKAY [ 0.012s]
Writing 'keymaster' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'keymasterbak' (305 KB) OKAY [ 0.010s]
Writing 'keymasterbak' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'cmnlib' (216 KB) OKAY [ 0.010s]
Writing 'cmnlib' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'cmnlibbak' (216 KB) OKAY [ 0.011s]
Writing 'cmnlibbak' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'cmnlib64' (267 KB) OKAY [ 0.015s]
Writing 'cmnlib64' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'cmnlib64bak' (267 KB) OKAY [ 0.011s]
Writing 'cmnlib64bak' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'mdtpsecapp' (1053 KB) OKAY [ 0.030s]
Writing 'mdtpsecapp' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'mdtpsecappbak' (1053 KB) OKAY [ 0.035s]
Writing 'mdtpsecappbak' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'modem' (111873 KB) OKAY [ 3.123s]
Writing 'modem' OKAY [ 0.745s]
Finished. Total time: 3.876s
Sending 'dsp' (16384 KB) OKAY [ 0.454s]
Writing 'dsp' OKAY [ 0.110s]
Finished. Total time: 0.571s
Sending 'bluetooth' (556 KB) OKAY [ 0.024s]
Writing 'bluetooth' OKAY [ 0.004s]
Finished. Total time: 0.031s
Sending 'storsec' (48 KB) OKAY [ 0.004s]
Writing 'storsec' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'storsecbak' (48 KB) OKAY [ 0.012s]
Writing 'storsecbak' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'devcfg' (47 KB) OKAY [ 0.011s]
Writing 'devcfg' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'devcfgbak' (47 KB) OKAY [ 0.012s]
Writing 'devcfgbak' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'abl' (148 KB) OKAY [ 0.012s]
Writing 'abl' OKAY [ 0.002s]
Finished. Total time: 0.016s
Sending 'ablbak' (148 KB) OKAY [ 0.012s]
Writing 'ablbak' OKAY [ 0.002s]
Finished. Total time: 0.016s
Sending 'dtbo' (8192 KB) OKAY [ 0.251s]
Writing 'dtbo' OKAY [ 0.055s]
Finished. Total time: 0.310s
Sending 'dtbobak' (8192 KB) OKAY [ 0.228s]
Writing 'dtbobak' OKAY [ 0.055s]
Finished. Total time: 0.286s
Sending 'vbmeta' (4 KB) OKAY [ 0.004s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.012s
Sending 'vbmetabak' (4 KB) OKAY [ 0.003s]
Writing 'vbmetabak' OKAY [ 0.001s]
Finished. Total time: 0.006s
Sending 'boot' (65536 KB) OKAY [ 1.860s]
Writing 'boot' OKAY [ 0.437s]
Finished. Total time: 2.301s
Sending 'recovery' (65536 KB) OKAY [ 1.836s]
Writing 'recovery' OKAY [ 0.437s]
Finished. Total time: 2.276s
Sending sparse 'system' 1/5 (786428 KB) OKAY [ 22.248s]
Writing 'system' OKAY [ 0.000s]
Sending sparse 'system' 2/5 (786428 KB) OKAY [ 22.449s]
Writing 'system' OKAY [ 0.000s]
Sending sparse 'system' 3/5 (786428 KB) OKAY [ 21.480s]
Writing 'system' OKAY [ 0.000s]
Sending sparse 'system' 4/5 (786428 KB) OKAY [ 21.680s]
Writing 'system' OKAY [ 0.000s]
Sending sparse 'system' 5/5 (327952 KB) OKAY [ 9.250s]
Writing 'system' OKAY [ 0.000s]
Finished. Total time: 97.119s
Sending sparse 'vendor' 1/2 (786428 KB) OKAY [ 21.900s]
Writing 'vendor' OKAY [ 0.000s]
Sending sparse 'vendor' 2/2 (57832 KB) OKAY [ 5.300s]
Writing 'vendor' OKAY [ 0.000s]
Finished. Total time: 29.298s
Sending 'userdata' (367876 KB) OKAY [ 10.647s]
Writing 'userdata' OKAY [ 0.000s]
Finished. Total time: 10.944s
Sending 'mdtp' (17390 KB) OKAY [ 0.483s]
Writing 'mdtp' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'cache' (128 KB) OKAY [ 0.005s]
Writing 'cache' OKAY [ 0.002s]
Finished. Total time: 0.017s
Sending 'splash' (26594 KB) OKAY [ 0.760s]
Writing 'splash' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Erasing 'ddr' OKAY [ 0.001s]
Finished. Total time: 0.003s
Erasing 'misc' OKAY [ 0.001s]
Finished. Total time: 0.002s
Erasing 'apdp' OKAY [ 0.001s]
Finished. Total time: 0.003s
Erasing 'msadp' OKAY [ 0.001s]
Finished. Total time: 0.003s
Sending 'cust' (248280 KB) OKAY [ 7.047s]
Writing 'cust' OKAY [ 0.000s]
Finished. Total time: 7.064s
Rebooting OKAY [ 1.574s]
In windows, when I do "flash_all" it stops at write error in xbl; but when I try with linux, the terminal follows all the script, writing down all the errors. As is possible to see in the code above, there are other errors of "write protection";
Any suggest of how to proceed?
[UPDATE]
I tried the test of emmc as suggested below and the result is that the memory is broken. Thanks for the support!
probably broken emmc ? could you access data partition using fastboot, try to paste 1gb of data to there, restart the phone enter fastboot again and copy the data to your pc, use sha256 to verify the data, if its not broken then its not the emmc
Rifaldi34 said:
probably broken emmc ? could you access data partition using fastboot, try to paste 1gb of data to there, restart the phone enter fastboot again and copy the data to your pc, use sha256 to verify the data, if its not broken then its not the emmc
Click to expand...
Click to collapse
How can I get access to data partition with fastboot?
flashing it using miflash and edl mode using test point...