Related
I have 2 pre launch models I9505 with extremely old software (and a non-secure bootloader ! )
Could someone point me in the right direction on HOW to extract the partition layout and all firmware related files ?
both devices are on different software
1st device hasn't even got TouchWiz yet, it was delivered on Google software and looks like this:
2nd device has this in download mode:
Can someone help me ?
Obviously this is an effort to get a modded bootloader which will allow us to install the FULL I9505G firmware on our I9505 devices !!
karoolus said:
I have 2 pre launch models I9505 with extremely old software (and a non-secure bootloader ! )
Could someone point me in the right direction on HOW to extract the partition layout and all firmware related files ?
both devices are on different software
1st device hasn't even got TouchWiz yet, it was delivered on Google software and looks like this:
2nd device has this in download mode:
Can someone help me ?
Obviously this is an effort to get a modded bootloader which will allow us to install the FULL I9505G firmware on our I9505 devices !!
Click to expand...
Click to collapse
You must dd all of the things in /dev/block/ I.E.
dd if=/dev/block/mmcblk0p1 of=/sdcard/mmcblk0p1.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/mmcblk0p2.img
Etc...
Sent from my GT-I9505G
System status = Custom
I don't think you will receive OTA with this + are the specs even the same ??? the model is totally different.
Just try..
Sent from my HTC One using Tapatalk 4 Beta
MichelN said:
System status = Custom
I don't think you will receive OTA with this + are the specs even the same ??? the model is totally different.
Click to expand...
Click to collapse
I don't think he's worked about OTA, lol. His model reads GT-i9505. How is that different?
Sent from my GT-I9505G
Fenny said:
I don't think he's worked about OTA, lol. His model reads GT-i9505. How is that different?
Sent from my GT-I9505G
Click to expand...
Click to collapse
Look at the phone model, sammy might have used other chips for the pre-release.
MichelN said:
Look at the phone model, sammy might have used other chips for the pre-release.
Click to expand...
Click to collapse
You mean physically? Yeah engineering devices will often look different than the official release. But usually they have most of the same guts. In this case I am concerned that they would have used an unsigned bootloader and a blown (or not blown as the case may be) efuse. But if that bootloader is signed and insecure... Ooooh baby we could have some fun with that.
I'll try that as soon as i can, but the devices are at work.. so i guess it'll have to wait.. and the hardware is the same, those devices are used to test firmwares and applications
They look different because the design was still confidential
I know both devices will allow flashing the GED software, but i bricked 2 already it's a tricky flash procedure :/
Sent from my SM-T311 using xda app-developers app
karoolus said:
I'll try that as soon as i can, but the devices are at work.. so i guess it'll have to wait.. and the hardware is the same, those devices are used to test firmwares and applications
They look different because the design was still confidential
I know both devices will allow flashing the GED software, but i bricked 2 already it's a tricky flash procedure :/
Sent from my SM-T311 using xda app-developers app
Click to expand...
Click to collapse
Make backups of those partitions for us before you try any of this.
Next, Load the Google edition ROM.
So here would be my method for changing partition layout: boot to a custom recovery adb shell in. Copy the contents of /sbin/ to /system/sbin/. Make a backup using nandroid. Unmount /system/, use parted to resize system to the size in your pit. (You may have to mkfs ext2 before it will do this, if so, just mkfs ext4 after). Advanced restore your system backup to your now smaller partition. Now, dd all of the things after your system partition except the data partition to your sdcard or to your internal storage (risky, back these up to your computer just in case). Proceed to delete, readd, and dd restore all of the partitions until you get to the recovery partition, this is where it is tricky. Delete the partition before the recovery partition (noting the next available block.) Recreate the previous partition in the bounds of the recovery partition. DD the recovery image into that space. Recreate the previous partition again, where it should be. One of two things will happen here. Your pit will immediately take effect, overwriting the partition table, and you will have to boot to recovery, and DD restore your images and nandroid, or you it won't, and you will continue on. Now we need to be in normal mode again, so make sure your ROM is rooted. From the normal rom, delete the recovery partition, and move it to where it should be. Boot back to recovery now. Proceed to move the rest of the partitions, and restore your nandroid to restore the cache, etc.
Sent from my GT-I9505G
Could you please post dumps of the bootloader on the forum it could really help at the verizon s4 scene
Thanks!
You can get the pit by Heimdall. I suggest pulling this too because partitions for engineering devices could be different than release.
Sent from my SPH-L900 using Tapatalk 2
Could you post or pm me the links to the .pit and partitions
This will be amazing.. Hopefully we can get are much needed storage
Sent from my SGH-M919 using xda premium
rajat12345 said:
Could you post or pm me the links to the .pit and partitions
Click to expand...
Click to collapse
This THREAD have system dump wit pit included, also you can contact op of that thread as he stated that he is willing to provide any info.
cheers mate
That isn't the same file Is it?
Sent from my SGH-M919 using xda premium
Sent from my GT-I9505 using XDA Premium HD app
I have a i9505G and the bootloaders is still secure
the pic you sent look to be downloader mode
Send a pic of the screen when you do "adb reboot bootloader"
or hold both volup+voldwn during power up
when need to get that secure boot to disable
look at my Signature for how to dump your rom, that should help
since the partition layout may be different i would like to make sure.
btw are you sure you didn't just get a clone, there has been a few copies out know that look like the real thing.
warwolfx0 said:
I have a i9505G and the bootloaders is still secure
the pic you sent look to be downloader mode
Send a pic of the screen when you do "adb reboot bootloader"
or hold both volup+voldwn during power up
when need to get that secure boot to disable
look at my Signature for how to dump your rom, that should help
since the partition layout may be different i would like to make sure.
btw are you sure you didn't just get a clone, there has been a few copies out know that look like the real thing.
Click to expand...
Click to collapse
I'm sure that the partition layout between i9505 and i9505G are different, the pit files don't match!
I'll look into dumping the rom, although i have my hopes on some tool i found this weekend
and a clone ? dude, are you serious ? i've had these devices since somewhere in february..
karoolus said:
I'm sure that the partition layout between i9505 and i9505G are different, the pit files don't match!
I'll look into dumping the rom, although i have my hopes on some tool i found this weekend
and a clone ? dude, are you serious ? i've had these devices since somewhere in february..
Click to expand...
Click to collapse
Well i hope you can extract everything
karoolus said:
I'm sure that the partition layout between i9505 and i9505G are different, the pit files don't match!
I'll look into dumping the rom, although i have my hopes on some tool i found this weekend
and a clone ? dude, are you serious ? i've had these devices since somewhere in february..
Click to expand...
Click to collapse
Yes, get us some dd images by all means.
Sent from my GT-I9505G
This 9" MID A20 Allwinner tablet had 2.34gb by stock on internal storage. Something went wrong after something I couldn't say what happened.
How do i re-partition the internal storage to 2.34gb again?
Can you link me to a fireware update compatible with this device.
Android - 4.2.2
Firmware - v2.0patch1
Kernel - 3.4.39+
Thursday September 5th : 18:22:06 CST 2013
Build - wing_k70-eng 4.2.2 JDQ39 20130905 test-keys
I can't download anything on play store because it defaults to internal storage wihich is 100% full for some reason?!?
THANKS
1chris89 said:
This 9" MID A20 Allwinner tablet had 2.34gb by stock on internal storage. Something went wrong after something I couldn't say what happened.
How do i re-partition the internal storage to 2.34gb again?
Can you link me to a fireware update compatible with this device.
Android - 4.2.2
Firmware - v2.0patch1
Kernel - 3.4.39+
Thursday September 5th : 18:22:06 CST 2013
Build - wing_k70-eng 4.2.2 JDQ39 20130905 test-keys
I can't download anything on play store because it defaults to internal storage wihich is 100% full for some reason?!?
THANKS
Click to expand...
Click to collapse
This is a faulty busybox installation. Just search for fix, it's just moving some files.
Can you please send me your /vendor/modules/gslx680.ko? Thanks!
I already fixed it, had to do hours of intense research and I found the firmware and the flash utility. Successfully fixed it, then it bricked. Then I successfully fixed the brick.
So these are fun to work with because I know how to fix them so easily now!
$85 tablet on ebay if u pick one up it's 9" 800x480 dual core 512 ram with a keyboard and case. Very neat little device! We hooked up a 1TB usb hard drive directly to it and it detected it and easily played back full 1080p movies which file sizes in the 20GB range... INSANE!
I know how to root these two and the Kernel is unlocked by stock on the AllWinner A20 to 1.488Ghz from the stock of 990Mhz! 1.1Ghz is the most stable but is very nice and fast!
Later
I need firmware for this tablet and I can't found it
Hi
Can you send me the firmware? I'm unable to find it.
Thanks
1chris89 said:
I already fixed it, had to do hours of intense research and I found the firmware and the flash utility. Successfully fixed it, then it bricked. Then I successfully fixed the brick.
So these are fun to work with because I know how to fix them so easily now!
$85 tablet on ebay if u pick one up it's 9" 800x480 dual core 512 ram with a keyboard and case. Very neat little device! We hooked up a 1TB usb hard drive directly to it and it detected it and easily played back full 1080p movies which file sizes in the 20GB range... INSANE!
I know how to root these two and the Kernel is unlocked by stock on the AllWinner A20 to 1.488Ghz from the stock of 990Mhz! 1.1Ghz is the most stable but is very nice and fast!
Later
Click to expand...
Click to collapse
donlotario said:
Hi
Can you send me the firmware? I'm unable to find it.
Thanks
Click to expand...
Click to collapse
It's tough to find but I found the info on this chinese website but all the files are on my friends computer since it was his tablet.. He totally could care less about the thing since it's nearly a nightmare to use...
Too little internal store available and not enough system memory so it lags out and freezes continuously... haha I'd factory reset or whatever if you can and sell it.
anti77 said:
This is a faulty busybox installation. Just search for fix, it's just moving some files.
Can you please send me your /vendor/modules/gslx680.ko? Thanks!
Click to expand...
Click to collapse
Greetings!
Would you please elaborate? My own extensive research has uncovered absolutely nothing about fixing a blown busybox installation.
1chris89 said:
This 9" MID A20 Allwinner tablet had 2.34gb by stock on internal storage. Something went wrong after something I couldn't say what happened.
Click to expand...
Click to collapse
Can you provide more information, perhaps even a link or two, to help the rest of us who have a similar problem?
Thanks!
I have posted a potential solution on this forum located at
https://forum.xda-developers.com/an...10x-tablet-t3878560/post78413347#post78413347
This has been posted elsewhere on XDA however it was suggested that this would be a better location to post so here goes:
'Good day all,
I have the above tablet which has been bricked . (We sell these and a customer has returned a unit to claim warranty so I am not 100% sure what has occurred to make the device what it currently is.) Basically I have another identical unit and have created a backup image with MTK Droid Tools. However when I try to load this image with SP Flash Tools I get errors. These state that the image I have is not correct (as it is from an identical unit I can safely say this is not correct) to the device storage not being available. The second error is the one I believe may be the problem. Is there a way that the internal storage may have been compromised and if is is there a way the storage can be fixed?'
I have tried to study the posts relating to partition dumping but am simply not bright enough to figure it out. Is there a way I can make a 'ghost' image of the working tablets partition table and then tranfer that to the bricked unit?
Thanks in advance for the help and time.
Alternately is anyone able to confirm a partition backup and restore tool?
I had this TV Box I'd bought from Wish. I thought I would share a (nearly) stock image. I pulled it after having to play around with the Google Play Store for a while because it ceased functioning.
I had noticed several other people having issues with obtaining a stock ROM, possibly on other forums.
https://1drv.ms/f/s!AtYTbQWzzbfRiBZEsUFK73q2H-pX
Thought it thru some more today and I'm adding a raw image of boot, bootloader and system. There may be more on this device that someone will find useful, if it's the case, let me know so I can dumped and post it.
File availability
Hi engineerchad
I am seeking the files you previously linked to, however they no longer appear available.
I'd be very grateful if you could make them available again please, if you do not mind?
Thank you
Andy
Link dead
engineerchad said:
Thought it thru some more today and I'm adding a raw image of boot, bootloader and system. There may be more on this device that someone will find useful, if it's the case, let me know so I can dumped and post it.
Click to expand...
Click to collapse
I am searching for this ROM but the link seems to be dead. Can you re-upload it?
abpdora said:
I am searching for this ROM but the link seems to be dead. Can you re-upload it?
Click to expand...
Click to collapse
I will go ahead and put it back up, give me a little bit seems like I lost the files on my online drive so I'll have to go ahead and either pull from a backup or take it off the device again. Check back later today or tomorrow and I should have a new link posted for you.
Onedrive:
https://1drv.ms/f/s!Am__eYU6nzsDgYMcl4D4gdMkAnLIuw
Mega:
https://mega.nz/#F!u8t3ECYS!HH8I-DPraAsc1CwMeTt-1Q
I hope it helps! I would post the link for the TWRP recovery that I used, but it was specifically stated to -please- not link up to it, reproduce, copy, re-upload, etc by the author. I located it with a Google search for "TWRP Amlogic S905W" or something of the like. It doesn't function perfectly (on my high-def TV, it displays on the top half of the screen, with the bottom half just kind of filled with garbage and you NEED a mouse hooked to the box to use it, but it's workable).
engineerchad said:
Onedrive:
https://1drv.ms/f/s!Am__eYU6nzsDgYMcl4D4gdMkAnLIuw
Mega:
https://mega.nz/#F!u8t3ECYS!HH8I-DPraAsc1CwMeTt-1Q
I hope it helps! I would post the link for the TWRP recovery that I used, but it was specifically stated to -please- not link up to it, reproduce, copy, re-upload, etc by the author. I located it with a Google search for "TWRP Amlogic S905W" or something of the like. It doesn't function perfectly (on my high-def TV, it displays on the top half of the screen, with the bottom half just kind of filled with garbage and you NEED a mouse hooked to the box to use it, but it's workable).
Click to expand...
Click to collapse
Pull original recovery and send me a link ill try porting a fully functional version
Ricky Divjakovski said:
Pull original recovery and send me a link ill try porting a fully functional version
Click to expand...
Click to collapse
It should show in both links "recovery.stock.img" is the filename.
The conventions of naming partitions on the box are quite simple /dev/block/system /dev/block/recovery /dev/block/boot etc (I believe. I actually haven't plugged this one in for a minute after I got a slight upgrade for it that I'm using now.) I had originally intended to do this myself, but have been trying for a long time to recover from the mental/physical effects of a quarter million dollar set of injuries last year and it's been pretty brutal.
I see where someone has done an unofficial TWRP in https://forum.xda-developers.com/android-stick--console-computers/amlogic/recovery-twrp-3-0-2-0-touch-recovery-t3454549 for this device with 8GB ROM, so I'm not sure if this would work just as well, or if it needs to be remade (this box is labelled as A95X and it's the amlogic s905x chipset with 2GB/16GB so I'm not sure if it would somehow be different from the link above or not.)
I figured I'd update, it seems like I may have misread the post originally on freaktab the author requested people share this link as opposed to mirroring. Here it is (had to search it up again, by coincidence it's also working for my a95x max + box which is also OTT TV brand I'll try to get an image up from that but my computer shows it has a root trojan in the stock image?)
http://konstakang.com/devices/nexbox_a95x/TWRP/
twrp complete backup
Hi Can you post a full backup with all partitions?
I have a a95x pro s905w too, and lost L1 widevine
Thanks for your support.
Best Regards from Spain
Here you have the last update.zip from the vendor:
A95X(905w2_16)_PRO-7.1.2-201806201412 2018062016101756843 zip
https://drive.google.com/file/d/1aSNU51sA3hm2bI-S1w7fz2l_jrmjD6Ks
try and see if it solve your problem
afaik, the OTT TV BOX stock firmware has a su included. There's just no SuperSU or other app to control access to it from what I've seen (and it's been pretty touchy while trying to install one, IME)
hi
i have A95X R1 Android 7.1 CPU Amlogic S905W 2.0GHz GPU Mali-450MP5 RAM 2G ROM 16G, anyone have a firmware or ROM for it pls??
is-serb said:
hi
i have A95X R1 Android 7.1 CPU Amlogic S905W 2.0GHz GPU Mali-450MP5 RAM 2G ROM 16G, anyone have a firmware or ROM for it pls??
Click to expand...
Click to collapse
seeking that same firmware ..
firmware
deetucks said:
seeking that same firmware ..
Click to expand...
Click to collapse
I have a95x 1g 8g and was at android 6 (this has 2 g 16g as well posted below)
Link posted is for ALL firmwares for the ott nexbox devices. Pretty sure some of you will need this. The listing does not say 7.1.2 but it is. It says 7 or 7.1 no worries. I got it, used it.
It is nexbox... so if you have the nexbox logo on your screen this is your stock 7.1.2 as I have just upgraded my box today.
You can use twrp, but do it from SD and never install it as you don't need to. Put twrp .img file NOT the zip with the blank update zip below. Never need to lose stock recovery.... I think. Not sure about custom roms yet but will lknow in an hour I'd say. Also included a zip of a program that will format your sd card fat32. I had a 64 gig card and windows won't make it fat32. Stupid.
As far as making the bootable sd card, I kept only getting 2 files when I ran the burn card maker you may have seen. That uboot one never was put in. Then by mistake I loaded the main img file after one completion. So not sure if you have to hit make twice or maybe because I used a 64 gig card. But with all 3 files there, I stuck in the sd card, nothing except hdmi plugged in.... held the reset button in and powered on..... got the android guy and a long update bar.......updated!
If you can put stock by SD card... do it! That other method via USB with USB burning tool app? If it works, yay. But I never got it working. That fat32 maker was very handy!
Link if you have nexbox:
https://mega.nz/#F!F9xjTSSa!R0vJfTC2U6Qc2skNMrr1iQ!4wpwzJyS
Has twrp but all crappy like mentioned earlier... pretty sure. But all firmware from 5 to 7 and I got 7 from there.
its not a nexbox..and its 2g 16g.. i cant find its stock rom anywhere,, the ds card thing does not work either ..i tried with numerous custom rom jus dont boot with the ds card,,
deetucks said:
its not a nexbox..and its 2g 16g.. i cant find its stock rom anywhere,, the ds card thing does not work either ..i tried with numerous custom rom jus dont boot with the ds card,,
Click to expand...
Click to collapse
That sucks. The link posted has 2 gig 16 gig. All firmwares... think my board is the same.
hmm.. think it is the same box. I will re-read your specs if you listed them
How did you get firmware to sd card, is it fat32 and only stock will work... so not sure but I think if you try from the link I posted, it won't screw you up? I think?
Ott tv box
model: R1
cpu: Amlogic s905w
ram: 2gb rom :16gb
[email protected]
---------- Post added at 11:45 AM ---------- Previous post was at 11:43 AM ----------
i can always try ,, i definately will look into it and give a try,,
deetucks said:
Ott tv box
model: R1
cpu: Amlogic s905w
ram: 2gb rom :16gb
[email protected]
Click to expand...
Click to collapse
oh you got the w.....have you looked on freaktab? Some site I just discovered. There is a good chance you'll find it there or someone can help.
I just tried looking and there is almost nothing. Weird because I could have sworn I saw a lot of s905w when I first started this.. Now you got me looking.
trust me i,m on freaktab cant find nothing.. request help nothing so far..
---------- Post added at 12:08 PM ---------- Previous post was at 11:55 AM ----------
trust me i,m on freaktab cant find nothing.. request help nothing so far..
I bought a MECOOL KM9 android box from the flea market. The Android on it was something custom from some IPTV service provider. On the bottom it says KM9 so I downloaded firmware from here. Using Aml_Burn_Tool the flashing got stuck at 30%, left it for about two hours didn't budge. After this the computer does not recognize the device (no plug-in sound, tested on two computers) and there is no output on HDMI.
So, I got to method two, which is the SD card burned with Burn Card Maker (multiple versions). Tested several firmware, several SD cards, no luck.
Opened up the device to get the serial output, you can find the output attached. Taking a closer look at the board I saw that is marked as: KM1 X2 DDR3 v1.4. The pcb doesn't look like the KM1's pcb and the SoC is different too. My board has Amlogic S905X2, the KM1 has Amlogic S905X3. Also, the pcb doesn't look like the KM9 board either.
The output log is the same regardless having an SD card or pressing de recovery button. It stops with "sdio read data fail". I don't think the EMMC is broken, earlier in the log it says "Load FIP HDR from eMMC" and there is no error. Also, if I have a bootable SD, shouldn't the EMMC be skipped?
As a last resort I tried shorting pins on the NAND chip, the computer still wouldn't detect it however if i short pins the serial output changes, again file attached.
Any ideas? Can I bring it back to life? At least does anyone have this board and firmware for it?
Thank you,
Alex
fyrewurx said:
I bought a MECOOL KM9 android box from the flea market. The Android on it was something custom from some IPTV service provider.
Click to expand...
Click to collapse
In which country? Do you have the provider information? That information might help identify or locate the original build of the firmware.
fyrewurx said:
Opened up the device to get the serial output, you can find the output attached. Taking a closer look at the board I saw that is marked as: KM1 X2 DDR3 v1.4.
Click to expand...
Click to collapse
It's too late now, but it would have been best to connect the uart and dump the original firmware before flashing anything. I understand that the label on the cover is wrong and that it does not match the board, but if you had a backup you could start over. Now, the drm keys (if any) are probably gone and the wrong dtb seems to have been flashed. Maybe it still can be fixed since the bootloader does still boot somewhat, but that may not be the original bootloader but rather the one that was flashed before the flashing failed.
fyrewurx said:
Also, if I have a bootable SD, shouldn't the EMMC be skipped?
Click to expand...
Click to collapse
There are different types of SD booting. For the lowest level booting, the emmc is skipped only if no bootable bootloader is found on the emmc.
It also will be skipped if the emmc clk resistor is removed. 4R1 may be the emmc clk resistor. Check if it is zero ohms. If it is not zero ohms, check the other side of the board.
Once the device is always booting from the SD card, try various videostrong (not skyworth!) firmware for S905X2 devices, like the KM3 and others (such as the KM9 Pro, which uses the X2). I don't see any information for this KM1 X2 device. It may be a custom variant for OTT providers.
Thank you very much for taking the time to answer.
All I can remember is that it was something Polish. You are right, having the original firmware would have been great. I usually check how much info there is on the internet (mainly xda) about the device I want to flash. If there is a lot, I don't bother with backup. Miiiistake. I didn't knew about the clk resistor and I assume others either because people don't mention on the internet. They recommend shorting the pins which is not a great idea in my mind. I did it with a random 330 ohm resistor to be on the safer side. I will definitely try to get the box to boot from SD and then try firmware from KM1 to KM whatever they got up to with the X2.
From your experience are these devices picky about the SD card? It would be easier if I test only with one card.
The DRM keys you mentioned, would stop the device from booting or the box just wont play Netflix and other streaming services? Even without Netflix I would like to get the box going.
I will have to lookup what a DTB file is, I have no idea. The board looks to be custom as there is one other picture I found about the device here.
Just for my knowledge, the bootloader for these devices is also in the main EMMC? I am used to x86 where you have an external memory to keep first stages of bootloader.
I attached closeups on the EMMC and the back, maybe we need them further on.
Thanks again for the reply,
Alex
fyrewurx said:
The board looks to be custom as there is one other picture I found about the device here.
Click to expand...
Click to collapse
Based on those photos, there is a chance that your board is (or is compatible with the firmware from) the KM9 PRO or the KM9 PRO DELUXE.
If this is the case, the state that your device is in now is probably a result of trying to flash an android 9 firmware image to a device that had an existing installation of android 10. If so, there is a decent chance that you can fix it.
You may be able to get a uart shell prompt by experimenting with shorting the emmc clk at various times, so that the attempt to load the invalid dtb (from the flashed firmware) fails. If you can get a uart shell prompt, you can start burn mode (uart shell command "update"), and then use command line tools to flash the km9 pro or km9 pro deluxe firmware.
Otherwise, remove the emmc clk resistor (once it is located), and raw copy the bootloader (from km9 pro or km9 pro deluxed) to the sd card. It isn't necessary to put the resistor back when you are done, a jumper wire can be used since it is zero ohms.
Functioner said:
Based on those photos, there is a chance that your board is (or is compatible with the firmware from) the KM9 PRO or the KM9 PRO DELUXE.
Click to expand...
Click to collapse
The KM9 devices use DDR4 memory, my board has DDR3. Can the firmware still be compatible?
I don't know. Maybe if the dtb has support for both types of ram. You'd have to check the dtb.
If you flash the dtb while watching the uart output, you'll know if it will work. But first you'd need to be able to start fastboot or have access to the uart shell, in order to flash it.
Support for both types of ram is not uncommon. For example, the sdmc dv8555 (S905x2) has multiple hardware versions, some with ddr3 and some with lpdd4, and both boards use the same firmware.
The original dtb and bootloader on your device are probably gone. They probably were overwritten before the flashing failed at 30%. You don't have much to lose by trying the other firmware, except perhaps a lot of your time.
I will try for sure. As you sad, there's nothing to loose. I probably shouldn't even bother (it was less then 10 dollars), but I hate contributing to e-waste, specially when the hardware is fine, the issue is software. And it's kinda my fault .