sending 'bootloader' (1536 KB)...
OKAY [ 0.188s]
writing 'bootloader'...
OKAY [ 0.391s]
finished. total time: 0.578s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.531s]
writing 'radio'...
OKAY [ 1.969s]
finished. total time: 3.500s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: 3831EC3B76D900EC
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.000s]
checking version-baseband...
OKAY [ 0.000s]
sending 'boot' (3964 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.609s]
sending 'recovery' (4308 KB)...
OKAY [ 0.547s]
writing 'recovery'...
OKAY [ 0.656s]
sending 'system' (333431 KB)...
OKAY [ 41.797s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 44.156s
Press any key to exit...
harry_01 said:
sending 'bootloader' (1536 KB)...
OKAY [ 0.188s]
writing 'bootloader'...
OKAY [ 0.391s]
finished. total time: 0.578s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.531s]
writing 'radio'...
OKAY [ 1.969s]
finished. total time: 3.500s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: 3831EC3B76D900EC
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.000s]
checking version-baseband...
OKAY [ 0.000s]
sending 'boot' (3964 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.609s]
sending 'recovery' (4308 KB)...
OKAY [ 0.547s]
writing 'recovery'...
OKAY [ 0.656s]
sending 'system' (333431 KB)...
OKAY [ 41.797s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 44.156s
Press any key to exit...
Click to expand...
Click to collapse
did you encrypt your phone? if yes, boot to factory recovery and format the phone from there. then try again.
Nexus HAL said:
did you encrypt your phone? if yes, boot to factory recovery and format the phone from there. then try again.
Click to expand...
Click to collapse
i try but same also i repair my bootloader Jtag
then try to flash when come write system file wait long time but not finish
then try odin also same problem
show write system file 3 green line show then nothing 30 min same no error not complete
now tell me what i do
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.
Hi there
I've got an old Nexus 10 that recently got stuck in a bootloop, so I booted into recovery and did a factory reset. After a few boots and updates everything seemed ok, but then it just died and went into a bootloop again.
I've flashed TWRP recovery, but no partitions are mounted or mountable and attempts to repair file system make the screen go squiggly (corrupted/interference) and then the tablet reboots into bootloader.
Is this likely to be a hardware issue or is there more I can try?
Slainte
mmidders
P.S. also tried flashing the stock ROM using flash-all.sh, output appended:
erasing 'boot'...
OKAY [ 0.022s]
finished. total time: 0.023s
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.097s]
finished. total time: 0.097s
erasing 'recovery'...
OKAY [ 0.029s]
finished. total time: 0.029s
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 0.150s]
finished. total time: 0.150s
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
OKAY [ 0.373s]
finished. total time: 0.373s
target didn't report max-download-size
sending 'bootloader' (1280 KB)...
OKAY [ 0.192s]
writing 'bootloader'...
OKAY [ 0.115s]
finished. total time: 0.307s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.454s
< waiting for any device >
extracting android-info.txt (0 MB)...
extracting boot.img (4 MB)...
target didn't report max-download-size
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (5 MB)...
archive does not contain 'recovery.sig'
extracting system.img (641 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
archive does not contain 'vendor.img'
wiping userdata...
mke2fs 1.44.1 (24-Mar-2018)
/tmp/TemporaryFile-poiJRI: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
Update:
I updated adb and fastboot and ran the flash-all.sh script again with the following output (now waiting for first boot):
Erasing 'boot' OKAY [ 0.022s]
Finished. Total time: 0.025s
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' OKAY [ 0.093s]
Finished. Total time: 0.095s
Erasing 'recovery' OKAY [ 0.025s]
Finished. Total time: 0.027s
******** Did you mean to fastboot format this ext4 partition?
Erasing 'system' OKAY [ 0.150s]
Finished. Total time: 0.153s
******** Did you mean to fastboot format this ext4 partition?
Erasing 'userdata' OKAY [ 0.372s]
Finished. Total time: 0.375s
Sending 'bootloader' (1280 KB) OKAY [ 0.194s]
Writing 'bootloader' OKAY [ 0.132s]
Finished. Total time: 0.330s
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.453s
< waiting for any device >
--------------------------------------------
Bootloader Version...: MANTAMF01
Baseband Version.....: no modem
Serial Number........: R32F200S5XR
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.001s]
extracting boot.img (4 MB) to disk... took 0.018s
archive does not contain 'boot.sig'
Sending 'boot' (4966 KB) OKAY [ 0.745s]
Writing 'boot' OKAY [ 0.118s]
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (5 MB) to disk... took 0.028s
archive does not contain 'recovery.sig'
Sending 'recovery' (5532 KB) OKAY [ 0.851s]
Writing 'recovery' OKAY [ 0.121s]
archive does not contain 'vbmeta.img'
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'super_empty.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting system.img (641 MB) to disk... took 6.544s
archive does not contain 'system.sig'
Sending 'system' (657130 KB) OKAY [ 96.291s]
Writing 'system' OKAY [ 15.845s]
archive does not contain 'system_ext.img'
archive does not contain 'vendor.img'
Erasing 'userdata' OKAY [ 0.371s]
mke2fs 1.44.1 (24-Mar-2018)
/tmp/TemporaryFile-3eTxBH: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
fastboot: error: Cannot generate image for userdata