Related
Excited.....
India Finally got R2BA023 from R1FA16 Firmware as Over the Air
Sony Ericsson has updated its SE Update Service (SEUS) software over the last week to version 2.10.7.15. There’s no way of trying to run the older version as SEUS will automatically update it once started. One of the main changes appears to be a fix that SE has implemented to stop people debranding their handsets.
The guide below shows you how to unbrand the handset.
new guide on debranding your handset ( Step -* 8*)
1) Download one of the following files depending on which region you are in. Each download contains two files (a +100MB one and a +10MB one).
Download link on POST #3
Please note:
Flashing your Xperia X10i to X10a (and vice versa) will result in SEUS not being able to update your phone for future updates.
2) Delete contents of db folder (C: –> Program Files –> Sony Ericsson –> Update Service –> db).
3) Run the Sony Ericsson Update Service (SEUS) to update your Xperia X10
4) Go to C: –> Program Files –> Sony Ericsson –> Update Service –> db –> 13740270 –> blob_fs.
5) Sort files by date in descending order (latest date at top). The two files at the top will be +100MB and one around 15MB.
6) Backup these two original files into a different directory. This is an optional step but means you can revert back to the branded firmware if needed.
7) Now find the two files that you downloaded in Step 1. Rename the largest file with the same name as the largest one in blob_fs. Do the same with the second.
8 ) IMPORTANT: Please read this step fully before executing it.
Run the Sony Ericsson Update Service (SEUS) again. It should say that you already have the latest update, click on the reinstall button anyway. The program will then start to re-download the same files. The trick here is to replace the files that are being re-downloaded with your new files from Step 7.
Open up Windows Explorer and navigate to the blob_fs folder. SEUS will first re-download the smaller (+10MB) file. Constantly monitor this folder to find out when the smaller (+10MB) file has been fully downloaded again. Once it has, immediately move your smaller file from Step 7 into the blob_fs folder and overwrite the file.
Now for the larger file. Keep an eye on the download progress bar in SEUS. Once the download is very near to completion you will need to copy the larger (+100MB) file from Step 7 into the blob_fs folder and overwrite the file. Time the file transfer for when there is literally around 1/2MB left to be downloaded.
If successful, the installation will carry on as normal. If not, try again. Don’t worry you will not brick your phone if it doesn’t work. It will simply tell you that the installation failed.
9) Voila! Your Xperia X10 is unbranded.
Download link for R2BA023
Download link for R2BA023
Rapidshare
http://rapidshare.com/files/406213898/X10i_Generic_R2BA023.rar.html
Hotfile
http://hotfile.com/dl/53877279/03ebccc/X10i_Generic_R2BA023.rar.html
but in india , what branding does it comes with ?
I mean we dont have airtel / reliance brading na... just a doubt , correct me if am wrong...
i too think in india the phone is unbranded.
we don't need to do these steps.
we just need to root the device.
You wouldn't happen to have the generic X10a firmware as well, would you?
indian R2BA023 firmware was released by last webnesday itself by OTA and its available in SEUS and PC companion from thursday onwards.........
Its not for any specific Provider ..
its jsut the latest Update !
Candy[MAN] said:
You wouldn't happen to have the generic X10a firmware as well, would you?
Click to expand...
Click to collapse
http://www.megaupload.com/?d=IK1HOS43
Believe that's it.
Android Variations: Check em out!
Hay All.,
I just downgread my x10i to previous version i.e. R2BA20 to R1FA016.
And then use the update service absolutely under Setting to update my set to R2BA023.
Really very happy now to see the performing improvement.
Sent from my X10i using XDA App
mspl said:
Hay All.,
I just downgread my x10i to previous version i.e. R2BA20 to R1FA016.
And then use the update service absolutely under Setting to update my set to R2BA023.
Really very happy now to see the performing improvement.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Just doing the same ...
80% Complete with the new firmware (after downgrading)
The SEUS update gave me quite the sacre..thought i will be forever stuck with the O2 branded firmware
I swear I will never be impatient again & quitely wait for regional updates to become available
farhan032 said:
Just doing the same ...
80% Complete with the new firmware (after downgrading)
The SEUS update gave me quite the sacre..thought i will be forever stuck with the O2 branded firmware
I swear I will never be impatient again & quitely wait for regional updates to become available
Click to expand...
Click to collapse
Dude!
Its bit tricky.
Downgrading is tricky .. follow the Step - 8 carefully;
i tried foe 6 times.. finally its work for me.
Cant I just use the update option under settings ? Or just use SUES for updating ? I dont want to mess around with dad's phone but would like update in legal and safe way.
Aparently ota updates around 40mb n seus updates around 140mb.. people are claiming the seus update have improved their x10s better than the actual ota updates through personal experiences..
Sent from my X10i using XDA App
Hi Im Running My x10a 2.1 Bulid Number 2.1.A.0.435
I Need A Generic 1.6 Firmware for The x10a or AT&T's 1.6 Can anyone Help Me With Downgrading And Doing This And The Files I Need Thank You
re:
x10iNick said:
Hi Im Running My x10a 2.1 Bulid Number 2.1.A.0.435
I Need A Generic 1.6 Firmware for The x10a or AT&T's 1.6 Can anyone Help Me With Downgrading And Doing This And The Files I Need Thank You
Click to expand...
Click to collapse
I think you can find it here http://forum.xda-developers.com/showthread.php?t=872298 just flash using flashtool, i think it will work...
Search and you will find the answer, but I will help you out this time!
http://forum.xda-developers.com/showthread.php?t=872298
The problem when I had went back to 1.6 was that it would not install correctly via flashtool. I had to use the old non-gui flashtool to get back correctly. I think it's included in the above link. Otherwise you can probably go into J's CM7 thread and download the baseband 52 in his mirror/fileserve account. Just put the files into the firmware folder, replacing the baseband files and you should be good.
Restoring back to AT&T 1.6 Branded 1237-4604 Firmware with Root Explorer:
Your phone must be rooted. Make sure you run a backup first as this will wipe data. You need the app Root Explorer set to write permissions R/W (at top of the screen) then go into system/build.prop file and long press on build.prop file and open in text editor. Then change the SI number from 1234 - 4820 back to 1237-4604 in every place you find it. I think it appears 2 maybe 3 times. Then save and close. REBOOT! Then run repair software via SEUS or PC Companion. *If you have run SEUS or PC Companion since you updated to 2.1, you need delete the contents inside the folder "db" found inside the update service program wherever it is saved on your computer. **It will say that you have the latest software, but REPAIR ANYWAY! Reboot, setup, reinstall your Backup app from market, Restore. DONE!
*Root Explorer costs a couple $, but well worth it. If you have problems finding Root Explorer or do not have a paypal account, send me a PM. I will help you.
Would this be the same process on a Rogers phone? Or would the SI numbers be different?
Different numbers, but same process. There is a thread with all the SI and CDA numbers.
I downloaded [OFFICIAL ROM UPDATE] Gingerbread 2.3.3 Update for HTC EVO Shift 4G from here http://forum.xda-developers.com/showthread.php?t=1127499
and I cant figure out how to install it. I put the file in the root file of my sd card then went into bootloader and nothing.
I'm going to ask this, but I'm pretty sure I already know the answer: are you rooted?
If not, and you don't care about root at this time, just go to HTC Software Updates, under Menu, settings, system updates, htc software update, and click check now.
Otherwise, two things disturb me about the link. The size of the file only shows 9.5 mb in the parenthesis next to the file name. It's actually 248 mb. Also, it's not in the correct name format, to just update from the bootloader. It needs to be PG06IMG.zip. But you can't just rename the file in the link above to PG06IMG.zip. It just won't work.
Or just go to shipped roms (shipped-roms.com) and download the latest ruu, and then connect the phone to your computer, and run the exe.
I tried the htc updates in setting and it said there were no updates for my phone. I gave up I found an ruu file and did it like you said and it worked great thanks. I was rooted but i only did it for wireless teather and i never used it so unrooting was not a problem.
By the way i used this ruu http://forum.xda-developers.com/showthread.php?t=1128410 to update and it work great
Sup everyone,
I finally got around to updating my TMO DVP. It's been stuck on 7720 this whole time and want to bring it up to Tango.
My question is: what exactly are the steps to upgrading???
Here are the threads I'm trying to follow in order:
http://forum.xda-developers.com/showthread.php?t=1103011
http://forum.xda-developers.com/showthread.php?t=1497142&nocache=1
http://forum.xda-developers.com/showthread.php?t=1736993
From what I understand it:
Install Windows Phone Support Tool
Install WP7 Backup 1.6
Install WP7 Update Cab Sender
Then???
I don't get it. I've installed WP Support tools which doesn't make sense. I have Win7-64bit. The downloads available are x86 or amd64. My computer is intel based, so which do I use? x86 doesn't install, makes sense. I installed amd64.
My next problem is, are there different versions of WP Support Tools? My Zune is up-to-date 4.8.2345.
After installing WP Support Tools:
WPSupportTools.exe is version 0.0.0.0, date modified 4/1/11
UpdateWP.exe is version 6.1.7600.16385 date modified 4/1/11
Microsoft.WindowsMobile.DeviceUpdate.dll is version 4.7.1404.3 date modified 4/1/11
When I run WP Support Tool, I get:
UpdateWP version 4.7.1404
Error: The installed version of the tool (4.7.1404) needs to be updated to match the Zune version (4.8.2345). Please install the tool version 4.8.2345.
Click to expand...
Click to collapse
What do I do?
UpdateWP.exe Information: 0 : 12/25/2012 12:48:25 AM: Device Manager Initializing
UpdateWP.exe Information: 0 : 12/25/2012 12:48:26 AM: Device Manager Initialized
UpdateWP.exe Information: 0 : zune-tuner://windowsphone/5e7a3cc3%20-%20ebd23705%20-%202fd2d1be%20-%20b9b323c8
UpdateWP.exe Error: 0 : 12/25/2012 12:48:26 AM: Update Exception: System.Runtime.InteropServices.COMException (0x801812C0): Exception from HRESULT: 0x801812C0
at Interop.ZuneWmduLib.WmduFirmwareUpdaterClass.StartFirmwareUpdate(IFirmwareUpdateCollection pUpdates, IFirmwareUpdateCallback pCallback)
at Microsoft.WindowsMobile.DeviceUpdate.Device.Microsoft.WindowsMobile.DeviceUpdate.IDevice.Update(String[] URIs, UpdateType UpdateType, Action`1 progressMadeCallback, Object context)
Click to expand...
Click to collapse
Log from when I got somewhere and nothing happened.
I've uninstalled and deleted everything. If anyone can help me out from square one it'd be much appreciated.
KnightmareCS said:
Log from when I got somewhere and nothing happened.
I've uninstalled and deleted everything. If anyone can help me out from square one it'd be much appreciated.
Click to expand...
Click to collapse
It's been a while since I did this. But you did right, AMD64 is correct. And try the file I attached as that's the newest version to match your Zune software. Let us know if you run into anything :good:
(and no, I didn't create the file. I just have it archived from a working cab sender upgrade so credits go to the original poster)
Ok,.
So I installed WP Support Tools.
Copied the files you gave into the Zune directory.
Copied WP7 Backup 1.6 into the Zune directory.
Tried running a backup.
Attached is the error message I got.
I tried the cmd method and that gave the same error.
GoodDayToDie said:
I ran into this issue too.
First question: Is your Zune install in the default location? The support tool installer seems kind of... stupid. It always installs in \Program Files\Zune even if Zune isn't actually installed there. You can copy the files from that location to wherever Zune is installed, if not. Be careful of overwrites.
Next question (really the important one, but the question above can be the reason for the problem): Is there a file called wm7updatelib.dll, or similar, in the folder with your UpdateWP.exe? If so, is it the same version (exactly, down to the build number)? If not, you may need to re-install the support tool (I suggest uninstalling it first, using appwiz.cpl).
Click to expand...
Click to collapse
Looking at this post.
I have wm7update.dll (not wm7updatelib.dll). It is file version 1.0.0.1 /product version 7.0.0.0.
Can you post the right library file?
Thanks
-
Attached are a list of my files and versions in Zune folder. (Ignore the dual Microsoft and UpdateWP, I just added garbage text to the originals)
Backing up now.
Copied the files attached.
wm7update.dll
Interop.wm7updatelib.dll
Interop.ZuneWmdulib.dll
BEASSSSSSSSST running 8773!
KnightmareCS said:
BEASSSSSSSSST running 8773!
Click to expand...
Click to collapse
Good work Glad to see you figured it out. Might want to share your experience if you ran into specific problems in case others have it?
Thanks.
All it was, was making sure I had the right file versions for the right files. Those of which I posted above.
aleunge said:
Good work Glad to see you figured it out. Might want to share your experience if you ran into specific problems in case others have it?
Click to expand...
Click to collapse
I've just update to 8773 myself as well. However, I want to ask you a question: whether we could re-write the firmware version also? My OS version is 7.10.8773.98, but firmware is 2250.1800.7720.219.
No idea. I noticed that too, but haven't seen anything about it just yet.
KnightmareCS said:
No idea. I noticed that too, but haven't seen anything about it just yet.
Click to expand...
Click to collapse
Yeah, maybe it's not necessary enough for us to consider that. However, I just noticed that while updating via Zune, this firmware version string is changed, but not with CAB sender. So, I just guess there might be a way to do it by ourselves too!
please note that the firmware package contains the bootloader drivers etc.etc.
Dell will probably not update those any more. The latest o.s. updates are provided by microsoft and they don't include any drivers whatsoever.
As long as the OS version is the most recent, you're good.
work in progress! (not working yet)
Current status: does not work (but should!), exact reason unknown (to me).
If you managed to "brick" your MOTO Z Play it enters a fail-safe mode as a last resort provided by the chipset manufacturer (Qualcomm). There are packages out there called "blank-flash" that use this mode to restore a proper bootloader that in turn re-enables the use of the fastboot method to write the other flash files and restore full operation - provided the personalized partitions are still present and in good health (or you have a backup of them at hand).
Look at this thread and download the Nougat file. It contains "blank-flash" files. These "should work" but they don't (any more). As I don't have a Z Play, I cannot research the matter myself and instructing helpful others via email exchange is ... complicated.
The thing with failing updates/flash packages is that they usually fail because they do not allow downgrading - even if they allow downgrading of some sort (e.g. OS), they may limit downgrading the second stage bootloader, the signed GPT (partitioning table) etc. As I don't know if and what's the case with the Z Play, I just assumed that *if* it works, it may require the most recent files.
If you run the blank-flash files (qboot) with --debug=2 option you see that after the programmer code is sent to the phone it doesn't send a valid / expected response and ultimately causes the process to fail.
There are many programmer files out there. Most do not work, because they need to be digitally signed with the proper keys. Some are signed with Quallcomm-keys, some with Lenovo-, Motorola- and other with test-keys. And then again, they have to fit with the qboot program that's sending the data to be flashed.
A blankflash archive consists of the following files:
qboot, blank-flash.sh ; Linux
qboot.exe, qboot.dll, blank-flash.bat ; Windows
singleimage.bin ; Both
There are different versions of the qboot program. I've found the versions 2.4, 3.37 and 3.40.
The file "singleimage.bin" contains the flash files and directions crammed into a single file, thus the name:
cmnlib.mbn
cmnlib64.mbn
devcfg.mbn
emmc_appsboot.mbn
gpt_main0.bin
index.xml
keymaster.mbn
programmer.mbn
prov.mbn
rpm.mbn
sbl1.mbn
singleimage.default.xml
singleimage.pkg.xml
tz.mbn
The XML files contain the instructions (the 'recipe'):
index.xml:
Code:
<?xml version="1.0"?>
<index>
<board id="70" name="MSM8953" storage.type="eMMC"/>
<package compatible="cpu.name:MSM8953 protocol:qboot" filename="singleimage.pkg.xml"/>
</index>
singleimage.pkg.xml:
Code:
<?xml version="1.0"?>
<package>
<programmer filename="programmer.mbn"/>
<recipe filename="singleimage.default.xml"/>
</package>
singleimage.default.xml:
Code:
<?xml version="1.0" ?>
<recipe>
<configure MemoryName="eMMC"/>
<!-- Flash GPT -->
<print what="Flashing GPT..."/>
<flash partition="partition:0" filename="gpt_main0.bin" verbose="true"/>
<print what="Re-initializing storage..."/>
<storage operation="reinit"/>
<!-- Flash bootloader -->
<print what="Flashing bootloader..."/>
<flash partition="aboot" verbose="true" filename="emmc_appsboot.mbn"/>
<flash partition="rpm" verbose="true" filename="rpm.mbn"/>
<flash partition="tz" verbose="true" filename="tz.mbn"/>
<flash partition="devcfg" verbose="true" filename="devcfg.mbn"/>
<flash partition="cmnlib" verbose="true" filename="cmnlib.mbn"/>
<flash partition="cmnlib64" verbose="true" filename="cmnlib64.mbn"/>
<flash partition="keymaster" verbose="true" filename="keymaster.mbn"/>
<flash partition="prov" verbose="true" filename="prov.mbn"/>
<flash partition="sbl1" verbose="true" filename="sbl1.mbn"/>
</recipe>
These files usually do not need to be modified.
programmer.mbn is the flash application that is sent to the phone.
I've compiled the following package, including all the qboot executables:
http://frickelbude.net/moto/blankflash[addison][D61DC5C7][25.211.10][1.07][2017-04-13].zip
D61DC5C7: crc32-checksum of programmer.mbn file (original, motorola signed) (find others here)
25.211.10: firmare package origin of the bootloader files
1.07: bootloader version
2017-04-13: time stamp of bootloader file
This didn't work with recently bricked Z Play phones as some testers confirmed. We also tried all the different programmer executables linked above just to be sure but no luck.
Outlook: you may want to try out Qualcomms QFIL (part of QPST package) (look e.g. at the download section of androidbrick).
However, that requires some handywork - you need to build some XML files, provide the proper programmer file etc. Maybe grab a firmware package e.g. for a Xiaomi phone that has all these files and try and deduce a proper layout for your Z play... and hope, any of the programmer files will actually run and communicate with the pc end.
(Usually the blank-flash files operate in 'sahara' mode/protocol and send the programmer.mbn to the phone. Then it waits for a positive response from the phone to enter 'firehose' mode in order to send all the flash data...)
/update 2017-06-10 a
I've created a blank-flash package based on the files @lozada81 linked below:
bootloader files extracted from: OTA tester Android 7.1.1 BRASIL patch june - Blur_Version.26.1.22.addison.retail.en.US.zip
blank-flash package: http://frickelbude.net/moto/blankflash[addison][D61DC5C7][26.1.22][C1.12][2017-05-22].zip
(Bootloader version: C1.12, GPT layout version: 0x000A)
/update 2017-06-10 b
Same package as above, but with a different programmer.mbn, taken from an older blank-flash package that came with an Android 6.0.1 package @lozada81 linked below.
http://frickelbude.net/moto/blankflash[addison][C0A0D740][26.1.22][C1.12][2017-05-22].zip
Well, it either fails with the infamous io-error or it finally works.. please test & report back!
Thanks OP for putting this together. I hope someone can help get what we need (someone smarter than me ). I've had to go back to my Nexus 6P, but the battery life is just horrid. I ended up ordering another Moto Z Play online. This time I'm going to keep the bootloader locked, keep the stock software, etc. I might be done with the rooting/flashing part of my life.
Moto Z Play Brick
Good afternoon.
I am from Brazil and I have a Moto Z Play XT1635-02 and downgraded from Android 7 to 6 and until then, I did the bootloader, root and installed TWRP and followed dowgrade procedures.
The problem happened after the downgrade removed the root I reinstalled the original recovery and downloaded through the mobile the update of the android January 7 via ota and after downloading began the installation and when restarting the cell phone he died and did not call any more and when connecting On the computer only the message in the device manager "Qualcomm HS-USB QDLoader 9008" no solution for now to resuscitate the device?
If someone has the solution and can help, thank you.
giba_11 said:
Good afternoon.
I am from Brazil and I have a Moto Z Play XT1635-02 and downgraded from Android 7 to 6 and until then, I did the bootloader, root and installed TWRP and followed dowgrade procedures.
The problem happened after the downgrade removed the root I reinstalled the original recovery and downloaded through the mobile the update of the android January 7 via ota and after downloading began the installation and when restarting the cell phone he died and did not call any more and when connecting On the computer only the message in the device manager "Qualcomm HS-USB QDLoader 9008" no solution for now to resuscitate the device?
If someone has the solution and can help, thank you.
Click to expand...
Click to collapse
Same with my case
Definitely going to be watching this thread. Thank you.
Sent from my SM-G955U using Tapatalk
AC
I also have my Z play stopped = (
Thanks for putting those info together, keep fingers crossed
Sent from my XT1650 using Tapatalk
Fingers crossed! Same thing with me!
I have this problem too, I'm refreshing that lenovo russian forum every 5 minutes, I'm desperate!
firmware android 7.0 update abril - compilation version NPNS25.137-24-1-9
https://www.androidfilehost.com/?fid=961840155545567726
OTA Blur_Version.25.231.4.addison.retail.en.US brasil patch may
http://motorola.erfanabdi.ir/index.....25.211.10.addison.retail.en.US&carrier=retbr
OTA tester Android 7.1.1 BRASIL patch june - Blur_Version.26.1.22.addison.retail.en.US.zip
https://drive.google.com/file/d/0B-9vIY9eZnVqY3BGM0NUdTdsclE/view
I hope util
lozada81 said:
OTA tester Android 7.1.1 BRASIL patch june - Blur_Version.26.1.22.addison.retail.en.US.zip
https://drive.google.com/file/d/0B-9vIY9eZnVqY3BGM0NUdTdsclE/view
Click to expand...
Click to collapse
I've compiled a new blank-flash package in case anyone would like to try it out (see update in 1st post).
However, I doubt it will work better than the other files. If it keeps on failing with:
Code:
FAILED: qb_flash_singleimage()->sahara_download()->IO error
then there's still something wrong with the communication between qboot and the programmer file. I.e. we would need a programmer file that works with more recent bootloader revisions.
(I assume that the blank-flash packages out there did actually work at some time in the past).
benzinerwin said:
I've compiled a new blank-flash package in case anyone would like to try it out (see update in 1st post).
However, I doubt it will work better than the other files. If it keeps on failing with:
then there's still something wrong with the communication between qboot and the programmer file. I.e. we would need a programmer file that works with more recent bootloader revisions.
(I assume that the blank-flash packages out there did actually work at some time in the past).
Click to expand...
Click to collapse
Where is the Download link ??
giri.shiva said:
Where is the Download link ??
Click to expand...
Click to collapse
People who can't read aren't supposed to download, sorry. It's too dangerous, they could flash something without knowing what it does.
Ok, I'll give you a hint: search for update and 1st post
Edit: no, not in the thread. Only in your quote.
giri.shiva said:
Where is the Download link ??
Click to expand...
Click to collapse
Ok, I'll give you a hint: search for update and 1st post
tag68 said:
People who can't read aren't supposed to download, sorry. It's too dangerous, they could flash something without knowing what it does.
Ok, I'll give you a hint: search for update and 1st post
Edit: no, not in the thread. Only in your quote.
Click to expand...
Click to collapse
I tried those already
I thought you had updated another blankflash file
No offense
benzinerwin said:
I've compiled a new blank-flash package in case anyone would like to try it out (see update in 1st post).
However, I doubt it will work better than the other files. If it keeps on failing with:
Code:
FAILED: qb_flash_singleimage()->sahara_download()->IO error
then there's still something wrong with the communication between qboot and the programmer file. I.e. we would need a programmer file that works with more recent bootloader revisions.
(I assume that the blank-flash packages out there did actually work at some time in the past).
Click to expand...
Click to collapse
in this pic, we see error do package, do recipe, do configure, buffer read , this with two firmware of lenovo.ru
https://www.mediafire.com/?eichzw02lsc9kyd
Master, firmware contain blankflash in mbm folder and work programmer until package error or work more that Previous
firmware Oficial XT1635-02_7.0_NPN25.137-24-1 - i n mbm folder blankflash file
https://cloud.mail.ru/public/HoLU/D1tHfMFQY
this two firmware contain blankflash in mbm folder and work programmer until package
firmware Oficial XT1635-02_7.0_NPN25.137-24-1
firmware XT1635-02_6.0.1_MPN24.104-44_47
http://lenovo-forums.ru/files/category/140-moto-z-play/
Thanks for the links. Actually, the older package...
lozada81 said:
firmware XT1635-02_6.0.1_MPN24.104-44_47
Click to expand...
Click to collapse
...did contain an old (duh..!) blank-flash package but also wrapped up with a different programmer.mbn, that I didn't know of before. Maybe you give this a try. I've repacked a blank-flash with this programmer.mbn and the most recent bootloader files (see update in 1st post)...
benzinerwin said:
Thanks for the links. Actually, the older package...
...did contain an old (duh..!) blank-flash package but also wrapped up with a different programmer.mbn, that I didn't know of before. Maybe you give this a try. I've repacked a blank-flash with this programmer.mbn and the most recent bootloader files (see update in 1st post)...
Click to expand...
Click to collapse
Very much to the cortrario, you are using your valuable time, your great knowledge and your ability to help us out of this huge bache called blankflash since update android 7.0 April update, unfortunately I leave my device at home and until late hours can test.
* But the other partners help them by testing and reporting their results to make it easier and faster the info required @benzinerwin
benzinerwin said:
Thanks for the links. Actually, the older package...
...did contain an old (duh..!) blank-flash package but also wrapped up with a different programmer.mbn, that I didn't know of before. Maybe you give this a try. I've repacked a blank-flash with this programmer.mbn and the most recent bootloader files (see update in 1st post)...
Click to expand...
Click to collapse
Thanks for your amazing work, Unfortunately, this package doens't work either. I get ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
hanks for your support
benzinerwin said:
Thanks for the links. Actually, the older package...
...did contain an old (duh..!) blank-flash package but also wrapped up with a different programmer.mbn, that I didn't know of before. Maybe you give this a try. I've repacked a blank-flash with this programmer.mbn and the most recent bootloader files (see update in 1st post)...
Click to expand...
Click to collapse
First of all I thank you for the help provided as well as your time, I commented that I have the 2 files that I uploaded today and in both I get the following
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error