Related
Hi guys. Ralekdev, Rebellos and Myself have become quite good at hacking the extra roxor out of Samsung devices. We started with The UnBrickable Mod which now spans 15 total devices on the Samsung Galaxy S series. The UnBrickable Mod turned the Galaxy S into a development board. So we moved on to sucessfuly hacking the Qualcomm bootloaders on the Verizon Galaxy S3 and while our exploits for this device have not yet been needed, we have them ready to deploy on several devices and we've learned alot. Today we would like to present to you:
UnBrickable SD-The ultimate in Exynos Necromancy
The UnBrickable SD allows for total resurrection of an otherwise hard-bricked and dead device. It takes a device-specific SDCard, and a jumper to be placed across a tiny resistor. This triggers the device to silently boot at which point it will count to 10 and reload the device's bootloaders. This uses Samsung Official firmware unlike UnBrickable SD Mod (unreleased as of the time of this post) which allows for dual-booting of custom and official.
Why would I need this?
The processor has a small bit of ROM called IROM that tries to initialize the EMMC to load SBOOT. SBOOT then fully initializes the EMMC(Internal and soldered down MMC chip) where it pulls boot parameters, partition tables and all other information for the device to boot. if the SBOOT is damaged, the device will no longer boot and Odin/Factory modes are destroyed and the device is hard-bricked. This failed boot means the device cannot function and is locked up.
How does UnBrickable SD work?
The UnBrickable SD works because the processor is configured to attempt to load SBOOT from EMMC and then fail-over to SD, and finally UART. We've prepared an SDCard via the sdcard command in SBOOT below. By disabling the EMMC during the IROM sequence, this device will automatically fail-over to SDCard boot, check the signatures, see a valid image, and reload the SBOOT onto the EMMC thus enabling Odin.
Instructions
You will need:
The SDCard Image: http://d-h.st/KIV
The Partition Information Table(PIT file)
The Odin Firmware(Heimdall one-click coming soon) http://forum.xda-developers.com/showthread.php?t=2006138
Samsung Kies (for its drivers) http://www.samsung.com/us/kies/
Once you have the required tools, we can begin the procedure.
Create your UnBrickable SD.
Unzip the SDCard Image file from the zip.
Write it to an SDCard
Linux:
Code:
sudo dd if=GCAM-bootable-odin-from-sd-60mb-DDimg.img of=/dev/MYDEVICE
where MYDEVICE is the sdcard (usually SDB or SDC
Windows: use this tool https://launchpad.net/win32-image-writer/ . I'm not going to explain because I use Linux.
Disassemble the device
I've prepared this video which shows how to disassemble the device. You can stop after you remove the LCD. Just pull the EM shields off after that so you can access the resistor.
Insert the SDCard
If you need instructions, you should have stopped long ago
Short the EMMC Resistor
You can use a pair of tweezers or a piece of wire, really anything to conduct electricity from one side of the resistor to the other. Below you can see some needles connected by a piece of wire which I use to short this resistor.
{
"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"
}
Press the power button wait a couple of seconds and release the short
While booting, the device provides a 10 second countdown on the UART2 port. during this 10 second countdown, the EMMC needs to become enabled in order to write the bootloaders back to the device. The entire process takes 30 seconds and you will see nothing on the screen.
Flash with Odin
This procedure is the same as shown in the video below, however you will put the firmware from above in the PDA section instead of CF-AutoRoot and put the PIT from above into the PIT section
Conclusion
You have sucessfully restored your device to stock condition. Please hit the thanks button below this post.
Additional Resources
[R&D] Port SDCard Recovery to Other Exynos4412 Devices: http://forum.xda-developers.com/showthread.php?t=1986887
Would you like to see the UnBrickable SD on your Exynos4 device (GS2, GNote, Gnote2)? I need a working device and a broken device to develop and test.
So similar procedure will also work on Galaxy S3 ?
drraptor said:
So similar procedure will also work on Galaxy S3 ?
Click to expand...
Click to collapse
Yes. the same procedure will work on the S3. I'm also working on bringing this to other devices as well.
What kind of image do you use for restoring the device? Just the stock one? 'Cause I (think) I saw you using a Ubuntu image on the Nexus 7...
u mentioned in the post that 15 devices of galaxy s series support this unbrickable mod which are those 15 devices? is Samsung Galaxy S i9003 included in this list or support this unbrickable mod and does all the the devices have the same procedure to use the unbrickable mod?
mfsr98 said:
What kind of image do you use for restoring the device? Just the stock one? 'Cause I (think) I saw you using a Ubuntu image on the Nexus 7...
Click to expand...
Click to collapse
I made the image using the working device using a UART connection. It consists of an official, Samsung signed SBOOT image that reloads SBOOT onto the EMMC.
pratik_s said:
u mentioned in the post that 15 devices of galaxy s series support this unbrickable mod which are those 15 devices? is Samsung Galaxy S i9003 included in this list or support this unbrickable mod and does all the the devices have the same procedure to use the unbrickable mod?
Click to expand...
Click to collapse
Nope. We only support Samsung Processors. Not OMAP or even Qualcomm for that matter.
AdamOutler said:
I made the image using the working device using a UART connection. It consists of an official, Samsung signed SBOOT image that reloads SBOOT onto the EMMC.
Nope. We only support Samsung Processors. Not OMAP or even Qualcomm for that matter.
Click to expand...
Click to collapse
is there any chance of getting this mod for i9003 in future?
pratik_s said:
is there any chance of getting this mod for i9003 in future?
Click to expand...
Click to collapse
I'm not working on it and I have no plans to do so.
AdamOutler said:
Yes. the same procedure will work on the S3. I'm also working on bringing this to other devices as well.
Click to expand...
Click to collapse
Is it working on galaxy S 2 ?
Sent from my GT-I9100 using xda app-developers app
drraptor said:
Is it working on galaxy S 2 ?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Nope. I need a device. read the inital post.
great
i had to use this method on my Mk1 Galaxy Tab, worked like a dream..
ill be honest it stretched my hardware altering skills to the limit, always goot to keep learning.
Now i just need to actually buy a Galaxy Camera.. suppose i should make sure its a good shooter first !!
Thanks for your endless skills Adam.
Awsome! But do i just put the GCAM-UnBrickable zip file on my sd card? but how will it work if i brick my SG3 and i cant turn anything on? im sorry if its a dumb question, but i dont understand lol
terminal 7 said:
i had to use this method on my Mk1 Galaxy Tab, worked like a dream..
ill be honest it stretched my hardware altering skills to the limit, always goot to keep learning.
Now i just need to actually buy a Galaxy Camera.. suppose i should make sure its a good shooter first !!
Thanks for your endless skills Adam.
Click to expand...
Click to collapse
Are you talking about UnBrickable Mod? This is a bit different. This is a temporary mod and uses SDCard instead of USB.
Guzup said:
Awsome! But do i just put the GCAM-UnBrickable zip file on my sd card? but how will it work if i brick my SG3 and i cant turn anything on? im sorry if its a dumb question, but i dont understand lol
Click to expand...
Click to collapse
follow the instructions. you need to image the card with the image file in the zip.
Hi Adam...
Thank you for your idea,,,,,
But,This is released for officially use samsung service centers.....So.I Think no news here
I Know Your Topic is for Exynos4412 But if you want,i can send you any other SW method for repair many phone witout jtag,
like P7500,P7510,P5100,P5110,P3xxx.,Also I9300 SD_Method....I9250,I9100G,I9020,I9023,etc
Anyway,Thanks for help other pepole
But,Possible for bad understand me? can you explain me for more detail..?
Thank you
(i have any phone in my shop,"work and dead",so if you want,just tell me),Also i'm Product Supporter of "RIFF-BOX"...So,I can check everyting(Possible and supported CPU) with Jtag,,,,
BABAK236 said:
Hi Adam...
Thank you for your idea,,,,,
But,This is released for officially use samsung service centers.....So.I Think no news here
I Know Your Topic is for Exynos4412 But if you want,i can send you any other SW method for repair many phone witout jtag,
like P7500,P7510,P5100,P5110,P3xxx.,Also I9300 SD_Method....I9250,I9100G,I9020,I9023,etc
Anyway,Thanks for help other pepole
But,Possible for bad understand me? can you explain me for more detail..?
Thank you
(i have any phone in my shop,"work and dead",so if you want,just tell me),Also i'm Product Supporter of "RIFF-BOX"...So,I can check everyting(Possible and supported CPU) with Jtag,,,,
Click to expand...
Click to collapse
This isn't i9020/9023, which I designed the UnBrickable Resurrector for repair. This is an undocumented procedure. This isn't NVFlash from those Tegra based devices. This isn't the i9250 and i9100 which use the OMAP specific tool. This isn't JTAG either, I have a box.
The most similar method was released for i9300 but the T-Flash method has never worked properly for myself or others. This is something which did not exist before the first post in this thread.
Keep this in your repair bookmarks for when you need it along side your Riff box. Riff takes 6 wires generally. Every one of the 16 solutions I've come up with has been 1 or less.
How do I image a sdcard? And If my device gets bricked I just pop the card in and power it on? when I image the card will it do something special to the card? Or can i still use it to store stuff on.
Sent from my GT-I9300 using xda premium
Guzup said:
How do I image a sdcard? And If my device gets bricked I just pop the card in and power it on? when I image the card will it do something special to the card? Or can i still use it to store stuff on.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Most of your questions are already answered in the OP. (commands, revive instructions etc.)
Can the sd still be used? No. There is ARM code and a boot image copied to the beginning of your SDCard. This procedure will destroy the file system metadata although, physically, all the files are still present but not accessable anymore.
@Adam
By disabling the EMMC during the IROM sequence, this device will automatically fail-over to SDCard boot
Click to expand...
Click to collapse
Is this what shorting the resistors actualy does?
We've prepared an SDCard via the sdcard command in SBOOT below
Click to expand...
Click to collapse
So the T-Flash Option in Odin basically uses this sdcard command to create the bootloader sd?
Hi Adam
I Want Just helping You.....
So,I think you don't need
Anyway,Thanks
theq86 said:
Is this what shorting the resistors actualy does?
So the T-Flash Option in Odin basically uses this sdcard command to create the bootloader sd?
Click to expand...
Click to collapse
Yes. Shorting the resistor disables the EMMC. The TFlash works differently.
This is different from TFlash. Using TFlash you insert a boot loader from your computer and flash it to the device with Odin. The TFlash is supposed to create a boot loader from an sboot.bin.tar.md5. It has problems and seems not to work... Like ever..
I know the first few posts said the mod will work on the s3.. but since the US versions don't have exynos, I have to ask will this work on the US versions? Including Verizon?
WARNING: This should be the VERY VERY VERY VERY (Am I clear enough about this?) LAST thing you do to try and fix a chromecast. This can possibly fry a chromecast for good, so know going into this that it may not work!
Because of this, Me, XDA, and all other users are NOT RESPONSIBLE for any damage, problems, or issues that may arise from using this method. By using this tutorial, you agree and understand the above warning.
So, I had a Chromecast that I got stuck in "backupsys" boot mode, where it would try to boot the backupsys partition. Issue is, it would not boot, and you can't force it to boot from jumpdrive while it is in "recovery" or "backupsys" mode.
Well after tearing the thing down and getting UART setup, I started messing around, and found a way to FORCE the device to read from USB, regardless to the bootmode.
How this works is during the boot process, you jump 2 select pins on the PCB by the CPU, which causes the device to have a block read error while reading the system flash. When this happens, the device falls back into USB read mode.
Because this causes a read interrupt, it "MAY" have unknown effects on the longevity of your device, so like I said before, this should be a LAST RESORT OPTION ONLY.
What You Need:
Chromecast with Rootable Bootloader
Paper Clip/Needle to jump some TINY pins
UART hooked up to your computer
Jump Drive with the Root Image & USB OTG Cable
Process:
Step 1: Tear down your device, and have it hooked up to UART on your computer.
Step 2: Have the USB OTG Cable and Jump Drive with the root image plugged into the chromecast. Do not have it plugged into power yet.
Step 3: On the top side of the chromecast (Not the side with the UART Pins), carefully remove the RF shield to reveal the WiFi Chip and CPU.
{
"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"
}
Step 4: Have putty open and connected to your UART COM port. Also have "reboot recovery" in your clipboard. (Copy that command so you can right-click in putty to send it quick)
Step 5: Now, prepare to jump pin #26 (shown in photo below, marked with red square on right side of CPU) when you plug in the chromecast to power it.
Step 6: Plug in the chromecast power, and watch the UART output. Once the Chromecast LED turns read, use the paper clip to short pin #26 and you should get the following outout:
Code:
sys_init start. boot_strap=0x00000080 (source=NAND), boot_state=0x0
PG868: leakage=208 vcore=10 sysctl=59
Customer key found, loading customer key...
Loading Secure Customer Key Store is finished
Loading Secure Customer Key Store is finished
Finish loading Customer Key store
bootloader image verified, start...
eureka-b3 BG2CD [Jun 6 2013 12:07:51] ver:9086b04-dirty
OTP status=0x000000FF lkg curr=208 mA
nand_randomizer_init_by_flash_type(chip_id = 0x2C48044AA500): !!! RANDOMIZED !!!
[FASTLOGO] init.
[FASTLOGO] Set CPCB1 output reso 8.[SHOWLOGO] start
showlogo_init_irq, Enable IRQ_dHubIntrAvio0(0x20) for cpu 0
[FASTLOGO] done.
fts: v155 loaded from 0x00268000
Read failed @ 0x7814c000
ERROR: Failed to read CPU image ret -1
Booting from NAND failed, booting from USB....!
timer_clk_freq = 0x47868c0
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
If you do not see "Booting from NAND failed, booting from USB....!", unplug the chromecast, and try again.
Step 7: The chromecast will now try and boot the Jump Drive image. During this, there will be a root shell hiding under all the output. You need to QUICKLY and repeatedly press Enter until you see "/ # " flash on the screen. Once you see that flash, QUICKLY press right-click so putty pastes your clipboard, and then press enter. If you do this fast enough, the kernel will run "reboot recovery" and restart.
Step 8: The device will now try to boot the normal recovery partition. This is fine, because even if it fails, the bootloader will detect this and reset the device to normal boot mode after a few power cycles. After a few power cycles, the chromecast should eventually show the following over UART:
Code:
sys_init start. boot_strap=0x00000080 (source=NAND), boot_state=0x0
PG868: leakage=208 vcore=10 sysctl=59
Customer key found, loading customer key...
Loading Secure Customer Key Store is finished
Loading Secure Customer Key Store is finished
Finish loading Customer Key store
bootloader image verified, start...
eureka-b3 BG2CD [Jun 6 2013 12:07:51] ver:9086b04-dirty
OTP status=0x000000FF lkg curr=208 mA
nand_randomizer_init_by_flash_type(chip_id = 0x2C48044AA500): !!! RANDOMIZED !!!
[FASTLOGO] init.
[FASTLOGO] Set CPCB1 output reso 8.[SHOWLOGO] start
showlogo_init_irq, Enable IRQ_dHubIntrAvio0(0x20) for cpu 0
[FASTLOGO] done.
fts: v168 loaded from 0x0029c000
[SHOWLOGO] stopped
Boot normal GTV image
fts: record v169 commited @ 0x002a0000
Uncompressing Linux... done, booting the kernel.
And congrats, the device is now back to Normal Boot Mode! You can now hold the power button during power on to properly flash the rooted image, and your device should be good to go!
DEVS: If you want to help make this easier, can you make a USB image that just boots the kernel and stops at command line? Would make this process easier.
FAQ:
Q: Why do I need this? I can just hold down the button to boot from a Jump Drive.
A: This is true, but if a Chromecast is in any other boot mode besides normal, then it will be unable to boot from USB. This is just how the bootloader is coded. (I submitted a patch to google regarding this, even though it would never help us out thanks to the updated locked bootloader).
Q: Will this allow be to Downgrade/Root my device?
A: Answer is Probably not, even though this is untested. This is because the bootloader is still loading from the device, so it will still probably check the USB Drives image for a valid signature.
Q: I tried this, but my device still won't boot.
A: Well then there is probably not much else you can do, besides looking for a fix yourself. Remember, its a $35 dollar device so it may just be best to buy a new one.
Reserved
This reminds me of what people did for the xbox 360 with the dual nand chips, or what Adam Outler did with the galaxy camera. He had a switch that would choose whether to boot the default eMMC or a SD card.
Aaron Swartz, Rest in Pixels.
ddggttff3 said:
Reserved
Click to expand...
Click to collapse
Can you explain why you chose pin 26?
Thanks
zackoch said:
Can you explain why you chose pin 26?
Thanks
Click to expand...
Click to collapse
In all honesty, trial and error with a device I didn't think would ever work again.
EDIT: Also, getting very very lucky.
jamcar said:
This reminds me of what people did for the xbox 360 with the dual nand chips, or what Adam Outler did with the galaxy camera. He had a switch that would choose whether to boot the default eMMC or a SD card.
Aaron Swartz, Rest in Pixels.
Click to expand...
Click to collapse
In case anyone didn't pick on my meaning, it would be cool if we could use a switch to boot from USB or eMMC.
Aaron Swartz, Rest in Pixels.
jamcar said:
In case anyone didn't pick on my meaning, it would be cool if we could use a switch to boot from USB or eMMC.
Aaron Swartz, Rest in Pixels.
Click to expand...
Click to collapse
technically this may be possible, but I am not a developer but don't quote me. The fact that we can load a kernel off a jump drive though should mean we have the ability to load and run a system image off of a jump drive.
I just got a second chromecast and am awaiting my USB OTG power cable, I do plan to root this one and work on seeing if my idea is possible.
Aaron Swartz, Rest in Pixels.
How did you get the remainder of the shield off? I got the covers off but I can't get the shield off.
EDIT: I got it. Another question: do you leave your chromecast "naked" or?
jamcar said:
How did you get the remainder of the shield off? I got the covers off but I can't get the shield off.
EDIT: I got it. Another question: do you leave your chromecast "naked" or?
Click to expand...
Click to collapse
You should put the RF shields back on after you do this modification, as they prevent interference and issues. During the dissection of my device though, I fully removed the shields (including the sides), so I have no choice but to run that one naked, but it is sitting on the side as I have another rooted chromecast I use for day to day usage.
Short pin 26 to Ground?
Sent from my XT897 using XDA Premium 4 mobile app
rbeavers said:
Short pin 26 to Ground?
Sent from my XT897 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
To be more clear, you should jump both pins at point 26. I am planning on re-doing this thread now that flashcast is out, and can make this a hell of a lot easier.
Have not used my chromecast since I bought it, prob early August. Used it the first day and put it back in the box. Decided to play with it again and root it. Problem is as soon as you plug it into the TV it starts to update (have/had wifi off just in case). So I assume it downloaded the update way back when I first used it. Not sure if this update patches the root exploit or not and I don't want to find out. Will this method get make out of "update mode"? Anything else I can try? You mentioned Flashcast any way to use it?
Thanks
BB
Bad Bimr said:
Have not used my chromecast since I bought it, prob early August. Used it the first day and put it back in the box. Decided to play with it again and root it. Problem is as soon as you plug it into the TV it starts to update (have/had wifi off just in case). So I assume it downloaded the update way back when I first used it. Not sure if this update patches the root exploit or not and I don't want to find out. Will this method get make out of "update mode"? Anything else I can try? You mentioned Flashcast any way to use it?
Thanks
BB
Click to expand...
Click to collapse
First off, any official OTA for the chomecast will patch the root exploit, so if that update goes through you will be unable to root your chromecast.
As for this method working for you, if you follow the jumping method as stated in OP, then yes, this method would force your chromecast to boot from the USB Cable.
As for using flashcast, thanks to tchebb's help, if you just boot flashcast 1.1.1 on a jumpdrive, it will automatically delete the OTA from the device, and reset the boot mode back to normal. So the need to use UART is no longer required!
ddggttff3 said:
First off, any official OTA for the chomecast will patch the root exploit, so if that update goes through you will be unable to root your chromecast.
As for this method working for you, if you follow the jumping method as stated in OP, then yes, this method would force your chromecast to boot from the USB Cable.
As for using flashcast, thanks to tchebb's help, if you just boot flashcast 1.1.1 on a jumpdrive, it will automatically delete the OTA from the device, and reset the boot mode back to normal. So the need to use UART is no longer required!
Click to expand...
Click to collapse
I've tried doing the root method posted here:
http://forum.xda-developers.com/showthread.php?t=2529903
When I connect the CS to the usb side of the OTG cable it flashs red and then white and that's it.
Might I be doing something wrong?
Thanks
BB
Bad Bimr said:
I've tried doing the root method posted here:
http://forum.xda-developers.com/showthread.php?t=2529903
When I connect the CS to the usb side of the OTG cable it flashs red and then white and that's it.
Might I be doing something wrong?
Thanks
BB
Click to expand...
Click to collapse
Is your device rootable? if it has taken any official google OTA yet, then the device will be unable to use or boot flashcast as google patched the root exploit.
Next time please try to keep questions to the relevant thread, thanks.
ddggttff3 said:
First off, any official OTA for the chomecast will patch the root exploit, so if that update goes through you will be unable to root your chromecast.
As for this method working for you, if you follow the jumping method as stated in OP, then yes, this method would force your chromecast to boot from the USB Cable.
As for using flashcast, thanks to tchebb's help, if you just boot flashcast 1.1.1 on a jumpdrive, it will automatically delete the OTA from the device, and reset the boot mode back to normal. So the need to use UART is no longer required!
Click to expand...
Click to collapse
IIRC, in another thread it was stated that Flashcast made no changes to the Chromecast, it was just to setup the USB drive to flash the Chromcast and it was the Pwnedcast ROM that made the needed changes to prevent the OTA from taking place.
It's mentioned in this post:http://forum.xda-developers.com/showpost.php?p=46307051&postcount=124 or am I misunderstanding what you mean?
wptski said:
IIRC, in another thread it was stated that Flashcast made no changes to the Chromecast, it was just to setup the USB drive to flash the Chromcast and it was the Pwnedcast ROM that made the needed changes to prevent the OTA from taking place.
It's mentioned in this post:http://forum.xda-developers.com/showpost.php?p=46307051&postcount=124 or am I misunderstanding what you mean?
Click to expand...
Click to collapse
That is correct, flashcast makes no changes, but it DOES reset the boot mode of the device back to normal. this is done to ensure that no device gets stuck in recovery mode forever, as well as deletes /cache/ota.zip so if a official google OTA is on the device, it gets deleted.
ddggttff3 said:
That is correct, flashcast makes no changes, but it DOES reset the boot mode of the device back to normal. this is done to ensure that no device gets stuck in recovery mode forever, as well as deletes /cache/ota.zip so if a official google OTA is on the device, it gets deleted.
Click to expand...
Click to collapse
Deleting /cache/ota.zip isn't considered a change? So, if ALL that is done to a 12072 build is to setup the Flashcast USB drive, it can't be updated by Google?
wptski said:
Deleting /cache/ota.zip isn't considered a change? So, if ALL that is done to a 12072 build is to setup the Flashcast USB drive, it can't be updated by Google?
Click to expand...
Click to collapse
No, the device will still be able to update from google if flashcast is ran, flashcast just deletes any already downloaded OTA that has yet to be installed.
Hi,
I am looking for a tablet for HAM radio / Shortwave listeners purposes.
One thing I need is a working OTG interface for attaching USB devices
to that tablet.
I read different/contradictionary informations about whether OTG works
with this tablet I am not sure, whether the tablets, they were talking about
were exactly the one I am on the way to buy.
So:
Does OTG work on a ASUS memopad 7 (ME176CX-1E041A) w/ Android 4.4 ?
And:
I read that Lollipop will install UEFI and will lock me out then, since there is
no rooting method....true?
Thank you very much for any help in advance!
Best regards,
tuxic
tuxic001 said:
Hi,
I am looking for a tablet for HAM radio / Shortwave listeners purposes.
One thing I need is a working OTG interface for attaching USB devices
to that tablet.
I read different/contradictionary informations about whether OTG works
with this tablet I am not sure, whether the tablets, they were talking about
were exactly the one I am on the way to buy.
So:
Does OTG work on a ASUS memopad 7 (ME176CX-1E041A) w/ Android 4.4 ?
And:
I read that Lollipop will install UEFI and will lock me out then, since there is
no rooting method....true?
Thank you very much for any help in advance!
Best regards,
tuxic
Click to expand...
Click to collapse
The rooting method for lollipop is only less noob-friendly, but for future I recommend you updating to lollipop. For rooting whether kitkat or lollipop (the better but a bit harder way), take a look at this thread: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
And OTG works quite good, even thumb drives work natively without some root using workaround.
Mis012 said:
The rooting method for lollipop is only less noob-friendly, but for future I recommend you updating to lollipop. For rooting whether kitkat or lollipop (the better but a bit harder way), take a look at this thread: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
And OTG works quite good, even thumb drives work natively without some root using workaround.
Click to expand...
Click to collapse
Hi Mis012,
thanks a lot for help me to start with all the things.
I want absolutely sure to understand what I am reading in all that tutorials and postings. Are there any "meta"-tutorials, which explain for example all these acronyms and abbreviations like
adb,odin,cvm,twpr,fastboot and a lot more? I want to learn, but what if I even dont understand the abbreviations of the tutorials and howtos? Lost?
Next:
I took a look at the rooting tutorial you linked (THX!) and didnt find my device in the list of supported devices? Out of luck? Or outdated informations? If outdated, how can I be sure, that
it still works?
(This is NO critism in any way, but I dont want "Just another brick in the wall"...
In this forum (or was it androidsforums? dont remember) I read postings of quite a few people who have created paper weights by upgrading to vanilla lollipop...
What are the benefits in comparision to kitkat to take the risk of an update?
Will lollipop fix the battery drain problem in standby of this nice device?
Can I attach a USBtoEthernet device to the usb port an get a net connection instead of using Wifi?
By the way: My ASUS mempad 7 is on the way to me....
Sorry for the bunch of question ... I am driven by a mix of curiosity and anxity...
Best regards and thank you very much for helping a newbie to get the road to
gain knowledge to help others in turn...
tuxic
tuxic001 said:
Hi Mis012,
thanks a lot for help me to start with all the things.
I want absolutely sure to understand what I am reading in all that tutorials and postings. Are there any "meta"-tutorials, which explain for example all these acronyms and abbreviations like
adb,odin,cvm,twpr,fastboot and a lot more? I want to learn, but what if I even dont understand the abbreviations of the tutorials and howtos? Lost?
Click to expand...
Click to collapse
adb - android debug bridge, gives you shell access to your device from computer and more. Search for Minimal ADB installer.
odin - Samsung flashing tool, has nothing to do with our tablet.
cwm - clockworkmod. custom recovery.
twrp - teamWin project recovery. has more functions, but refuses to work with our device
fastboot - something like adb, you use it for flashing partitions if you have unlocked bootloader
tuxic001 said:
Next:
I took a look at the rooting tutorial you linked (THX!) and didnt find my device in the list of supported devices? Out of luck? Or outdated informations? If outdated, how can I be sure, that
it still works?
(This is NO critism in any way, but I dont want "Just another brick in the wall"...
Click to expand...
Click to collapse
It should be in the supported devices list. It's me176cx. I can say it works.
tuxic001 said:
In this forum (or was it androidsforums? dont remember) I read postings of quite a few people who have created paper weights by upgrading to vanilla lollipop...
Click to expand...
Click to collapse
If you soft brick your device like me, you can just return to kitkat, or better go to store and want a rapair. I returned my to the store two days ago, hope they will give me a chance for lollipop. The update should work without problems on a new device.
tuxic001 said:
What are the benefits in comparision to kitkat to take the risk of an update?
Click to expand...
Click to collapse
First of all, it is lollipop vs kitkat - you can read on internet about why lollipop is better.
The best part - UEFI. with UEFI, you can install any computer OS (Windows, linux) on this tablet.
tuxic001 said:
Will lollipop fix the battery drain problem in standby of this nice device?
Click to expand...
Click to collapse
Maybe. there was some tutorial on xda how to fix it.
tuxic001 said:
Can I attach a USBtoEthernet device to the usb port an get a net connection instead of using Wifi?
Click to expand...
Click to collapse
If the OS will support it. I don't know if android can support this.
tuxic001 said:
By the way: My ASUS mempad 7 is on the way to me....
Sorry for the bunch of question ... I am driven by a mix of curiosity and anxity...
Best regards and thank you very much for helping a newbie to get the road to
gain knowledge to help others in turn...
tuxic
Click to expand...
Click to collapse
No problem.
DO NOT DO ANYTHING SUSPICIOUS WITH THE DEVICE UNTIL YOU GET LOLLIPOP!
Otherwise, you may end up with lollipop update not working > warranty or kitkat forever
And here are some links you should read (It' not that much of text, it only looks like that
https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/ - the autor should thank me, I recommend this article to everone here.
http://forum.xda-developers.com/showthread.php?t=2317790 - minimal ADB and fastboot (you do not need it for Temp CWM recovery, it includes it.
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 - Temp CWM recovery
http://forum.xda-developers.com/memo-pad-7/general/asus-memo-7-me176cx-t2814046 - general thread about this tablet
http://doesn't-exist-yet.sorry/ - I will make a nice step by step guide on how to dual boot lollipop and other OS as soon as I will have my tablet back from service and I will have lollipop so I will have UEFI)
Mis012 said:
adb - android debug bridge, gives you shell access to your device from computer and more. Search for Minimal ADB installer.
odin - Samsung flashing tool, has nothing to do with our tablet.
cwm - clockworkmod. custom recovery.
twrp - teamWin project recovery. has more functions, but refuses to work with our device
fastboot - something like adb, you use it for flashing partitions if you have unlocked bootloader
It should be in the supported devices list. It's me176cx. I can say it works.
If you soft brick your device like me, you can just return to kitkat, or better go to store and want a rapair. I returned my to the store two days ago, hope they will give me a chance for lollipop. The update should work without problems on a new device.
First of all, it is lollipop vs kitkat - you can read on internet about why lollipop is better.
The best part - UEFI. with UEFI, you can install any computer OS (Windows, linux) on this tablet.
Maybe. there was some tutorial on xda how to fix it.
If the OS will support it. I don't know if android can support this.
No problem.
DO NOT DO ANYTHING SUSPICIOUS WITH THE DEVICE UNTIL YOU GET LOLLIPOP!
Otherwise, you may end up with lollipop update not working > warranty or kitkat forever
And here are some links you should read (It' not that much of text, it only looks like that
https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/ - the autor should thank me, I recommend this article to everone here.
http://forum.xda-developers.com/showthread.php?t=2317790 - minimal ADB and fastboot (you do not need it for Temp CWM recovery, it includes it.
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 - Temp CWM recovery
http://forum.xda-developers.com/memo-pad-7/general/asus-memo-7-me176cx-t2814046 - general thread about this tablet
http://doesn't-exist-yet.sorry/ - I will make a nice step by step guide on how to dual boot lollipop and other OS as soon as I will have my tablet back from service and I will have lollipop so I will have UEFI)
Click to expand...
Click to collapse
Hi Mis012,
OH WHOW! This drives my curiosity up and my anxity DOWN! A BIG THANK YOU for your patience with a newbie (I have some experience with Linux and embedded devices (Beaglebone Black, AriettaG25(both ARM) though).
AND: My ASUS ME176CX has arrieved!!! YEAH!
And...strictly following your advice I just started to do the least suspicious with it: CHARGING! hahahaha!
Question (as you might already have expected :
The first thing I want to do is to lollipop my board.
Unfortunately there are two things to consider: I have to setup WLAN for my PC (yes, I am of the "generation copper" / Gentoo LInux. This will be some effort
but no unbeatable problem.
Next is: I am living in a house with LOT OF RF noise. My shortwave receiver sounds like an lawn mower when switched on indoors (that the reason for buying a mobile
PC to go outside and still have all decoders, frequency lists and informations available).
So I do not trust any broadcasted data stream that much...especially when it comes to firmware updates (IIIIIEEEEEKKKKSS!).
Is there any way to update via good ole files from a sdcard/internal flash in a non hackish, plain and secure way?
Earphone:
There neither a users manual nor Tech Specs inside the box.
And if I will insert an earphone into the earphone jack I may burn the output drivers of the audio chip inside,
if this earphone has a too low impedance. Mine has 14 Ohms.
Question:
What is the output impedance of the audio port?
Does it support a mic on the earphone (four contacts)?
Thank you very much in advance again for helping an old child to walk in new shoes!
Hopefully I will get around the hurdles in the beginning and can start to give answers.
Best regards,
tuxic
tuxic001 said:
Hi Mis012,
OH WHOW! This drives my curiosity up and my anxity DOWN! A BIG THANK YOU for your patience with a newbie (I have some experience with Linux and embedded devices (Beaglebone Black, AriettaG25(both ARM) though).
AND: My ASUS ME176CX has arrieved!!! YEAH!
And...strictly following your advice I just started to do the least suspicious with it: CHARGING! hahahaha!
Question (as you might already have expected :
The first thing I want to do is to lollipop my board.
Unfortunately there are two things to consider: I have to setup WLAN for my PC (yes, I am of the "generation copper" / Gentoo LInux. This will be some effort
but no unbeatable problem.
Next is: I am living in a house with LOT OF RF noise. My shortwave receiver sounds like an lawn mower when switched on indoors (that the reason for buying a mobile
PC to go outside and still have all decoders, frequency lists and informations available).
So I do not trust any broadcasted data stream that much...especially when it comes to firmware updates (IIIIIEEEEEKKKKSS!).
Is there any way to update via good ole files from a sdcard/internal flash in a non hackish, plain and secure way?
Earphone:
There neither a users manual nor Tech Specs inside the box.
And if I will insert an earphone into the earphone jack I may burn the output drivers of the audio chip inside,
if this earphone has a too low impedance. Mine has 14 Ohms.
Question:
What is the output impedance of the audio port?
Does it support a mic on the earphone (four contacts)?
Thank you very much in advance again for helping an old child to walk in new shoes!
Hopefully I will get around the hurdles in the beginning and can start to give answers.
Best regards,
tuxic
Click to expand...
Click to collapse
Really don't know anything anout earphones, but I think tablets have some kind of protection, the worst what can happen is you will drain your battery faster, or the sound volume might be lower. Theoreticaly.
About the update: sorry that I didn't mention it, the best what you can do is to download the lollipop firmware from asus support site for this tablet, put it on your sdcard and start it up, then there will be a notification saying somethinhg like "do you wanna update?" You will say that you want and that's it. And you can press thanks if you find my posts helpful, I will feel more like a big boss if I will have more thanks, and it pleases my heart If you need to know anything else, just say You would help us all if you could find someone interested in making cyanogenmod (12.1 would be best) for our device. Just share this link where I write how the locked bootloader can be safely ignored by replacing it with another one: http://forum.xda-developers.com/memo-pad-7/help/me176cxk013-how-cyanogen-mod-t3154917
Mis012 said:
Really don't know anything anout earphones, but I think tablets have some kind of protection, the worst what can happen is you will drain your battery faster, or the sound volume might be lower. Theoreticaly.
About the update: sorry that I didn't mention it, the best what you can do is to download the lollipop firmware from asus support site for this tablet, put it on your sdcard and start it up, then there will be a notification saying somethinhg like "do you wanna update?" You will say that you want and that's it. And you can press thanks if you find my posts helpful, I will feel more like a big boss if I will have more thanks, and it pleases my heart If you need to know anything else, just say You would help us all if you could find someone interested in making cyanogenmod (12.1 would be best) for our device. Just share this link where I write how the locked bootloader can be safely ignored by replacing it with another one: http://forum.xda-developers.com/memo-pad-7/help/me176cxk013-how-cyanogen-mod-t3154917
Click to expand...
Click to collapse
THANKS PRESSED! GREAT! I didn't saw that and it is the first forum I visit, which has this feature!
And downloading an update and THAN flashing it, makes me feel a lot more comfortable...WLAN is only "somehow" here...
Here:
http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+MeMO+Pad+7+(ME176C)
I found 1 firmware item to download:
Version WW_V12.10.1.17 (OS upgradesto Android Lollipop 5.0.1)
Now I am a little confused:
"Download device software and Update SOP (From “Manual” Item)" -- what the [] is a "SOP" ? I cannot find any SOP-Manual (or whatever SOP)
"Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW." ("SKU"? "WW"? "CN"? "TW"? ???? IEEEEKKKS! All this acronyms!!!
"Userfriendly" is definetly something completly different!
I need support for the ASUS support, I think
...Since I found in my ME176CX a software revision number starting with WW and the firmware also start with WW, I think I am ok.
I still dont know, what SKU is and I didnt find any SOP.
Will it be ok to put UL-K013-WW-12.10.1.17_KK-user.zip (unpacked???) onto my SDcard (where? The root dictionary of the card?) ,
put the SDcard into my tablet, and switch the tablet on (when fully charged) and "follow the instructions" ?
Sorry if doubling questions, but I feel better when asking question a second time than buying a tablet a second time...dont like Pink Floyd
at this point of my life...
Best regards,
tuxic
tuxic001 said:
THANKS PRESSED! GREAT! I didn't saw that and it is the first forum I visit, which has this feature!
And downloading an update and THAN flashing it, makes me feel a lot more comfortable...WLAN is only "somehow" here...
Here:
http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+MeMO+Pad+7+(ME176C)
I found 1 firmware item to download:
Version WW_V12.10.1.17 (OS upgradesto Android Lollipop 5.0.1)
Now I am a little confused:
"Download device software and Update SOP (From “Manual” Item)" -- what the [] is a "SOP" ? I cannot find any SOP-Manual (or whatever SOP)
"Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW." ("SKU"? "WW"? "CN"? "TW"? ???? IEEEEKKKS! All this acronyms!!!
"Userfriendly" is definetly something completly different!
I need support for the ASUS support, I think
...Since I found in my ME176CX a software revision number starting with WW and the firmware also start with WW, I think I am ok.
I still dont know, what SKU is and I didnt find any SOP.
Will it be ok to put UL-K013-WW-12.10.1.17_KK-user.zip (unpacked???) onto my SDcard (where? The root dictionary of the card?) ,
put the SDcard into my tablet, and switch the tablet on (when fully charged) and "follow the instructions" ?
Sorry if doubling questions, but I feel better when asking question a second time than buying a tablet a second time...dont like Pink Floyd
at this point of my life...
Best regards,
tuxic
Click to expand...
Click to collapse
I think that the description is some weird user-unfriendly way to describe what I said. Just do what I wrote, there should be no problem. I will stay tuned, crossed fingers for you.
Mis012 said:
I think that the description is some weird user-unfriendly way to describe what I said. Just do what I wrote, there should be no problem. I will stay tuned, crossed fingers for you.
Click to expand...
Click to collapse
I did it and: I GOT LOLLIPOP! YEAH!
I find you guilty for being the source of this success!
Is there a way to check, whether the update is complete, valid in whole working?
Are there critical points to check (certain applications/functions)?
Best regards,
tuxic
tuxic001 said:
I did it and: I GOT LOLLIPOP! YEAH!
I find you guilty for being the source of this success!
Is there a way to check, whether the update is complete, valid in whole working?
Are there critical points to check (certain applications/functions)?
Best regards,
tuxic
Click to expand...
Click to collapse
When you connect keyboard using OTG cable, and press F2 during startup, you should boot into UEFI. Did you encounter any problems with lollipop? Disabling "power saver" option in settings should give you smoother experiance, and solves problem with games playing slow. Anyways, I'm glad I could help. For further info, follow this thread: http://forum.xda-developers.com/memo-pad-7/general/asus-memo-7-me176cx-t2814046/page256
Mis012 said:
When you connect keyboard using OTG cable, and press F2 during startup, you should boot into UEFI. Did you encounter any problems with lollipop? Disabling "power saver" option in settings should give you smoother experiance, and solves problem with games playing slow. Anyways, I'm glad I could help. For further info, follow this thread: http://forum.xda-developers.com/memo-pad-7/general/asus-memo-7-me176cx-t2814046/page256
Click to expand...
Click to collapse
Hmmm....F2 does not work for me...
I also tried the easter egg...but I got a lollipop, but no game...
Furthermore I cannot connect the ME176CX to my computer in a way that the computer recognized it as storage device...
"Software version" say "5.0" and not "5.0.1" or anything higher. The firmware I downloaded was marked as "5.0.1"
Did I really got a FULL and VALID update?
Best regards,
tuxic
tuxic001 said:
Hmmm....F2 does not work for me...
I also tried the easter egg...but I got a lollipop, but no game...
Furthermore I cannot connect the ME176CX to my computer in a way that the computer recognized it as storage device...
"Software version" say "5.0" and not "5.0.1" or anything higher. The firmware I downloaded was marked as "5.0.1"
Did I really got a FULL and VALID update?
Best regards,
tuxic
Click to expand...
Click to collapse
It is 5.0.0 they have mistypen. As for the minigame, touching lollipop will change color, but holding will bring the minigame. Maybe F2 only works with powered hub, didn't try it as my tablet is still in service. Alternatively, you can try this:
1.connect usb keyboard with OTG cable
2.enter stock recovery (while powering on the tablet, hold volume down. In droidboot, select recovery using volume buttons and confirm with power button)
3.on the keyboard press and hold F2
4.select reboot to bootloader
5.on the keyboard press ENTER
steps may vary a bit, this method sounds weird to me but you can try. If it will not work, I will point you at a bit harder method.
Mis012 said:
It is 5.0.0 they have mistypen. As for the minigame, touching lollipop will change color, but holding will bring the minigame. Maybe F2 only works with powered hub, didn't try it as my tablet is still in service. Alternatively, you can try this:
1.connect usb keyboard with OTG cable
2.enter stock recovery (while powering on the tablet, hold volume down. In droidboot, select recovery using volume buttons and confirm with power button)
3.on the keyboard press and hold F2
4.select reboot to bootloader
5.on the keyboard press ENTER
steps may vary a bit, this method sounds weird to me but you can try. If it will not work, I will point you at a bit harder method.
Click to expand...
Click to collapse
Hi Mis012,
Ok, got the Lollipop game (just a test, what works -- just to validate my update).
Entered droidboot as a "exercise" only (for getting used to it).
Found my serial number is 012345678012345678 (or similiar counting up).
Does that mean, that someone sold me a refurbished device as a new one? I read of this
kind of "serial number" appearing on devices, which were sent for repair...
Currently I am download&installing (Gentoo installs a wrapper, which one calls to get the whole
thing installed) android_sdk/android_studio to my Linux PC. Oh damn! THAT'S a huge
thing to download...I started 4 hours before and it still downloads (no, I /am/ generation copper,
but I use DSL ... no modem
While that process slowly but surely will fill up my Linux harddisk I was searching for a
GPS app, which DOES NOT LOG me for others, dont read my contacts, and do other, non
purpose related things AND uses openstreetmap (or better: dont use google services),
is able to do all its functions offline and is GPLed.
I testinstalled three...
All claims suspicious rights of accessing for example the microphone.
I deleted all.
Damn!
I think I have to learn A LOT MORE, before feeling halfway comfortable with this kind
of "new world order"
And as always Mis012...thank you very much for your support and patience!
Best regards,
tuxic
PS: Next I will try F2 again...
tuxic001 said:
Hi Mis012,
Ok, got the Lollipop game (just a test, what works -- just to validate my update).
Entered droidboot as a "exercise" only (for getting used to it).
Found my serial number is 012345678012345678 (or similiar counting up).
Does that mean, that someone sold me a refurbished device as a new one? I read of this
kind of "serial number" appearing on devices, which were sent for repair...
Currently I am download&installing (Gentoo installs a wrapper, which one calls to get the whole
thing installed) android_sdk/android_studio to my Linux PC. Oh damn! THAT'S a huge
thing to download...I started 4 hours before and it still downloads (no, I /am/ generation copper,
but I use DSL ... no modem
While that process slowly but surely will fill up my Linux harddisk I was searching for a
GPS app, which DOES NOT LOG me for others, dont read my contacts, and do other, non
purpose related things AND uses openstreetmap (or better: dont use google services),
is able to do all its functions offline and is GPLed.
I testinstalled three...
All claims suspicious rights of accessing for example the microphone.
I deleted all.
Damn!
I think I have to learn A LOT MORE, before feeling halfway comfortable with this kind
of "new world order"
And as always Mis012...thank you very much for your support and patience!
Best regards,
tuxic
PS: Next I will try F2 again...
Click to expand...
Click to collapse
I hope you do not install sdk only because of adb, because you can get adb separetely and it has less the 10 MB.
About GPS, it looks like this tablet cannot fix location without being cannected to wi-fi.
About the serial number, it really seems weird, but you should be able to change it to something else if you want to.
And it looks there is a new OTA, I recommend not to install it, maybe it will remove UEFI acess or something. Now, it looks like a fix for lollipop problems some people had, but a lot of them have no problems after freezing the power saver app.
Mis012 said:
I hope you do not install sdk only because of adb, because you can get adb separetely and it has less the 10 MB.
About GPS, it looks like this tablet cannot fix location without being cannected to wi-fi.
About the serial number, it really seems weird, but you should be able to change it to something else if you want to.
And it looks there is a new OTA, I recommend not to install it, maybe it will remove UEFI acess or something. Now, it looks like a fix for lollipop problems some people had, but a lot of them have no problems after freezing the power saver app.
Click to expand...
Click to collapse
Hi Mis012,
No, no..(.the SDK is still downloading)...
I install the SDK cause I am curious and may (if TIME and BRAIN allows me) be I can
program something. I am on LINUX here (I mean: my PC is a GENTOO box), so often
tutorials are not that straight forward to read (and helper applications on PC side are
not running here).
GPS is only running when WIFI is connected? Holy CRAP...Google wants to be sure,
that tey are able to track """anonymously"""".
Software "problem"/"feature" which was installed with Lollipop or is it a hardware
restriction? Oh damn...one reason for buying this tablet has gone...
Next update will remove/close UEFI? Will be this the next feature, which I will loose?
But still the nice shiny glass surface will remain...(not without sarcasm... )
IF UEFI will be locked/removed...will we have a chance, to get full control over
this tablet again?
Who is checking for the sanity of this new update?
The droidboot/F2 hack does not work with my keyboard (KBtalking PURE 60).
I could reconnect my IBM model M keyboard of my PC to the tablet, but this
beauty will pull over 100mA through the USBtoPS2 converter....
Better not.
I have an USB hub here...will try that next.
Is there anything I definetly should NOT do, when booted into UEFI?
Will OTAs be available as files later or here or somewhere else?
Do you know of people having such a odd serial number AND have
a proofen new device?
Oh, why oh why one needs to check for everything these days???
Best reagards,
tuxic
tuxic001 said:
GPS is only running when WIFI is connected? Holy CRAP...Google wants to be sure,
that tey are able to track """anonymously"""".
Software "problem"/"feature" which was installed with Lollipop or is it a hardware
restriction? Oh damn...one reason for buying this tablet has gone...
Click to expand...
Click to collapse
It's working fine for me without WiFi, tested it last week. I've heard some people reporting problems with the GPS, can't reproduce them personally.
tuxic001 said:
Next update will remove/close UEFI? Will be this the next feature, which I will loose?
But still the nice shiny glass surface will remain...(not without sarcasm... )
IF UEFI will be locked/removed...will we have a chance, to get full control over
this tablet again?
Who is checking for the sanity of this new update?
Click to expand...
Click to collapse
I installed the update yesterday, it updated something in the BIOS or UEFI or however that it called, not completely sure if they patched that. I don't have an OTG adapter (?, the micro USB to USB adapter) yet (ordered one already) so can't say if they broke that. Will test once it has arrived.
tuxic001 said:
Will OTAs be available as files later or here or somewhere else?
Click to expand...
Click to collapse
You can download the latest OTA update from the link I posted it http://forum.xda-developers.com/showpost.php?p=61926393&postcount=2587 (scroll down a bit, the URL starting with fota.asus.com has the OTA update, can't post the link directly here for some reason) and install it using the temp CWM recovery for example. Not sure if you can also simply copy it to your sdcard, never tried that. Just keep in mind, I don't know what ASUS will do with your UEFI/bootloader with this update, it's generally working fine for me though. If you've disabled power saver in the previous lollipop version there is generally no big reason to update, there were only a few minor changes (I noticed nothing)...
tuxic001 said:
Do you know of people having such a odd serial number AND have
a proofen new device?
Click to expand...
Click to collapse
Just checked, I have the same serial number listed there. I don't know but I don't think it's the real serial number so I wouldn't worry about it. I've installed a few updates already and own the device for about a month already so can't tell for sure, but I'm pretty sure I wondered about this serial number already when I got the device a month ago.
tuxic001 said:
Hi Mis012,
No, no..(.the SDK is still downloading)...
I install the SDK cause I am curious and may (if TIME and BRAIN allows me) be I can
program something. I am on LINUX here (I mean: my PC is a GENTOO box), so often
tutorials are not that straight forward to read (and helper applications on PC side are
not running here).
GPS is only running when WIFI is connected? Holy CRAP...Google wants to be sure,
that tey are able to track """anonymously"""".
Software "problem"/"feature" which was installed with Lollipop or is it a hardware
restriction? Oh damn...one reason for buying this tablet has gone...
Next update will remove/close UEFI? Will be this the next feature, which I will loose?
But still the nice shiny glass surface will remain...(not without sarcasm... )
IF UEFI will be locked/removed...will we have a chance, to get full control over
this tablet again?
Who is checking for the sanity of this new update?
The droidboot/F2 hack does not work with my keyboard (KBtalking PURE 60).
I could reconnect my IBM model M keyboard of my PC to the tablet, but this
beauty will pull over 100mA through the USBtoPS2 converter....
Better not.
I have an USB hub here...will try that next.
Is there anything I definetly should NOT do, when booted into UEFI?
Will OTAs be available as files later or here or somewhere else?
Do you know of people having such a odd serial number AND have
a proofen new device?
Oh, why oh why one needs to check for everything these days???
Best reagards,
tuxic
Click to expand...
Click to collapse
About the UEFI acces removal I said maybe. Mayba not. But who knows these days?
And about the gps, it dit it on kitkat and someone said it does this on lollipop too. I would recommend booting in windows and trying then, if it will not work then it will never. But GPS apps for windows? Noooo, who would mess up with that? The next step would be Android-x86.
As for the UEFI, here comes the noob-unfriendly variant:
0. root the tablet (may not be needed, I haven't tried)
1. download the efibootmgr compiled for android http://forum.xda-developers.com/showpost.php?p=61108700&postcount=2083
2. place the file from inside the zip somewhere
3. using android termianl app, cd in folder with efibootmgr
4. with help of this file http://linux.dell.com/files/efibootmgr/efibootmgr-0.5.4/efibootmgr.txt set next boot to UEFI setup utility. You will most likely need root.
5. Power off the tablet and power it on again
6. You should be in UEFI setup utility. Now you may be able to browse the menus.
7. You will most likely still need a powered usb hub to connect keyboard and do anything.
I hope I will not need a powered usb hub, I do not have one.
Mis012 said:
About the UEFI acces removal I said maybe. Mayba not. But who knows these days?
And about the gps, it dit it on kitkat and someone said it does this on lollipop too. I would recommend booting in windows and trying then, if it will not work then it will never. But GPS apps for windows? Noooo, who would mess up with that? The next step would be Android-x86.
As for the UEFI, here comes the noob-unfriendly variant:
0. root the tablet (may not be needed, I haven't tried)
1. download the efibootmgr compiled for android http://forum.xda-developers.com/showpost.php?p=61108700&postcount=2083
2. place the file from inside the zip somewhere
3. using android termianl app, cd in folder with efibootmgr
4. with help of this file http://linux.dell.com/files/efibootmgr/efibootmgr-0.5.4/efibootmgr.txt set next boot to UEFI setup utility. You will most likely need root.
5. Power off the tablet and power it on again
6. You should be in UEFI setup utility. Now you may be able to browse the menus.
7. You will most likely still need a powered usb hub to connect keyboard and do anything.
I hope I will not need a powered usb hub, I do not have one.
Click to expand...
Click to collapse
Hi Mis012,
UEFI:
Thanks for the deeply-hack-mode-variant!
But I will wait with my experiments until it is clear whether we will still have full access to our beloved ME176CX or not.
Here is a little bit of knowledge, which I can give back:
I had asked on xda-developers whether and how it is possible to mount the tablet as storage device.
Now I found a way to do so on Linux.
You need to install on Linux (this is Gentoo notation...other distros may
have similiar nameings)
dev-lang/go-1.4.2
dev-libs/go-usb-9999
dev-libs/go-fuse-0_p20150422
media-libs/libmtp-1.1.8
On the tablet switch off PTP and switch on MTP.
Connect the device with you Gentoo box and start (as root)
go-mtpfs <mountpunt>
(YES! No device name is required here).
After that the mountpoint contains two directories:
drwxr-xr-x 0 root root 0 1970-01-01 01:00 Internal storage
drwxr-xr-x 0 root root 0 1970-01-01 01:00 SD card
which which is, is obvious.
It is ok, that the command "hangs" ... works as designed.
It stops hanging after the umnount (see below).
Now you can add files into these directories as root.
To umount use (again as root)
umount <mntpoint>
This way there is no need of WiFi transfers or fiddling with this
tiny memory chips.
Best regards,
tuxic
tuxic001 said:
Hi Mis012,
UEFI:
Thanks for the deeply-hack-mode-variant!
But I will wait with my experiments until it is clear whether we will still have full access to our beloved ME176CX or not.
Here is a little bit of knowledge, which I can give back:
I had asked on xda-developers whether and how it is possible to mount the tablet as storage device.
Now I found a way to do so on Linux.
You need to install on Linux (this is Gentoo notation...other distros may
have similiar nameings)
dev-lang/go-1.4.2
dev-libs/go-usb-9999
dev-libs/go-fuse-0_p20150422
media-libs/libmtp-1.1.8
On the tablet switch off PTP and switch on MTP.
Connect the device with you Gentoo box and start (as root)
go-mtpfs <mountpunt>
(YES! No device name is required here).
After that the mountpoint contains two directories:
drwxr-xr-x 0 root root 0 1970-01-01 01:00 Internal storage
drwxr-xr-x 0 root root 0 1970-01-01 01:00 SD card
which which is, is obvious.
It is ok, that the command "hangs" ... works as designed.
It stops hanging after the umnount (see below).
Now you can add files into these directories as root.
To umount use (again as root)
umount <mntpoint>
This way there is no need of WiFi transfers or fiddling with this
tiny memory chips.
Best regards,
tuxic
Click to expand...
Click to collapse
On my Arch Linux system with Gnome/Cinnamon and on Linux Mint/Ubuntu (with a few hacks) it is mounting the device automatically without root or any command, I simply connect it to USB and the device is showing up in the file explorer.
cyandro said:
On my Arch Linux system with Gnome/Cinnamon and on Linux Mint/Ubuntu (with a few hacks) it is mounting the device automatically without root or any command, I simply connect it to USB and the device is showing up in the file explorer.
Click to expand...
Click to collapse
Yes, there are distros out there, which has setup the udev-rules and mtp-mimic already.
Gentoo leaves all that as a task (and exercise) for the user.
Unfortunately I received no reply to my question how to access the ME176CX via usb storage.
So I found it myself...
Now I know, how it works
By the way: Is there any way to disable this [CENSORED] auto completion and word guessing "feature"
of the build-in keyboard. I disabled all suspicous settings under "Language and Input" -- but it
does not help.
"cat /proc/cpuinfo" will instantly be corrected to "cat /proc/Clinton"
which does not work in this case
For programming and system peeking purposes this is a total NO GO!
Help me please with the settings...I am over 30 !
Best regards,
tuxic
Hello guys, I have a teclast x98 air3 wich I dont know his condition actually.. I'm desesperated because I am stuck in a EFI shell Version screen.
I am a starter in this scene, and I'm lost. First,sorry for my english.
I thinked that my problem was the bios and I used the @ionini tool to flash the c5j8 bios. I did ok, but I am in the same situation, EFI Shell version.
I tried to flash a new bios for teclast air3 (OP @mrchrister) : http://forum.xda-developers.com/x98-air/general/current-best-rom-bios-x98-air-iii-32gb-t3310436 with Mireks tools, I hit 4, then 2, and the CMD shows 'start daemon sucesfully' and nothing happens.....
I tried to flash the @sikke1 rom : http://forum.xda-developers.com/x98-air/development/teclast-x98-air-iii-air-3g-debloated-t3266740
The MFT recognise my tablet, but i have a fail at 23% : failed to execute oemp/tmp/partition.tbl
I have been looking for a solution, and I have discover this :
Exec manual script
Now, that we understand what we are doing, there is the full set of instructions for manually flash the device (exec each of these commands, step by step):
fastboot flash /tmp/partition.tbl partition.tblfastboot oem partition /tmp/partition.tblfastboot erase cachefastboot erase systemfastboot erase datafastboot erase factoryfastboot erase configfastboot erase logsfastboot oem stop_partitioning
fastboot oem start_partitioningfastboot oem wipe ESP
Until here, we was create a new partition definition, and clean each partition.
Now, the script follows with:
fastboot flash fastboot droidboot.imgfastboot flash boot boot.imgfastboot flash recovery recovery.imgfastboot flash system system.imgfastboot continue
And at this point you get your device flashed. for finishing, do this:
fastboot reboot
Click to expand...
Click to collapse
But i don't have idea if this is my solution..
I have to say that at the beginning of try methods, the Mirek tools could erase recovery,data,factory,etc...and now don't do. CMD is turning red and shows me as FAILED all the erases.
Im desesperated, I think that @ionini tools changed my bios, because now when I press 'ON' appears teclast and a windows mouse a few seconds before EFI Shell Screen.
And I think that before try @ionini tool, the window mouse didnt appear...
I only want to have 32gbs for windows and a normal BIOS and I don'tk know how to do NOW, because I have a many problems to start to do something, I don't know wich step have to be mi first step in this situation..
Please, everyone who can help me. Thank you in advance, and sorry again for my English.
EDIT1 : I edit to say that in all moment I can entry in DNX MODE, without problems, and comand 'fastboot devices' list my tablet.
EDIT2: The fastboot comands of the quote of this post doesn't work for me...
EDIT3: @Mikha777 Can you help me with EFI SHELL? I have read your post... Can i Change to a 2.05 bios again with a keyboard and doing your tutorial?-->http://forum.xda-developers.com/showpost.php?p=62875595&postcount=12835
Any Ideas?
@tecknight And you? : S
ozerec88 said:
Hello guys, I have a teclast x98 air3 wich I dont know his condition actually.. I'm desesperated because I am stuck in a EFI shell Version screen.
I am a starter in this scene, and I'm lost. First,sorry for my english.
I thinked that my problem was the bios and I used the @ionini tool to flash the c5j8 bios. I did ok, but I am in the same situation, EFI Shell version.
I tried to flash a new bios for teclast air3 (OP @mrchrister) : http://forum.xda-developers.com/x98-air/general/current-best-rom-bios-x98-air-iii-32gb-t3310436 with Mireks tools, I hit 4, then 2, and the CMD shows 'start daemon sucesfully' and nothing happens.....
I tried to flash the @sikke1 rom : http://forum.xda-developers.com/x98-air/development/teclast-x98-air-iii-air-3g-debloated-t3266740
The MFT recognise my tablet, but i have a fail at 23% : failed to execute oemp/tmp/partition.tbl
I have been looking for a solution, and I have discover this :
But i don't have idea if this is my solution..
I have to say that at the beginning of try methods, the Mirek tools could erase recovery,data,factory,etc...and now don't do. CMD is turning red and shows me as FAILED all the erases.
Im desesperated, I think that @ionini tools changed my bios, because now when I press 'ON' appears teclast and a windows mouse a few seconds before EFI Shell Screen.
And I think that before try @ionini tool, the window mouse didnt appear...
I only want to have 32gbs for windows and a normal BIOS and I don'tk know how to do NOW, because I have a many problems to start to do something, I don't know wich step have to be mi first step in this situation..
Please, everyone who can help me. Thank you in advance, and sorry again for my English.
EDIT1 : I edit to say that in all moment I can entry in DNX MODE, without problems, and comand 'fastboot devices' list my tablet.
EDIT2: The fastboot comands of the quote of this post doesn't work for me...
EDIT3: @Mikha777 Can you help me with EFI SHELL? I have read your post... Can i Change to a 2.05 bios again with a keyboard and doing your tutorial?-->http://forum.xda-developers.com/showpost.php?p=62875595&postcount=12835
Any Ideas?
@tecknight And you? : S
Click to expand...
Click to collapse
Since you have an Air III you must use a bios/Firmware that is done for the Air III, 2.05 is made for Air II NOT Air III, not using the right firmware can cause lot of trouble and even brick completely your tablet.
Here's the DUAL Firmware/BIOS for X98 Air III
https://mega.nz/#!V5BCgZYZ!wLQ9meYBb1egSknXI7W60U-0KtzZhO46P1HsXr8blvk
Follow carefully the instructions in my tutorial to flash the firmware in the previous link.
Regards !
Mikha777 said:
Since you have an Air III you must use a bios/Firmware that is done for the Air III, 2.05 is made for Air II NOT Air III, not using the right firmware can cause lot of trouble and even brick completely your tablet.
Here's the DUAL Firmware/BIOS for X98 Air III
https://mega.nz/#!V5BCgZYZ!wLQ9meYBb1egSknXI7W60U-0KtzZhO46P1HsXr8blvk
Follow carefully the instructions in my tutorial to flash the firmware in the previous link.
Regards !
Click to expand...
Click to collapse
Thank you, @Mikha777, so you think my tablets its still 'alive'?:victory:
what tutorial exactly? this? http://forum.xda-developers.com/showpost.php?p=62875595&postcount=12835
What is fparts.txt??
You say ' You connect a USB hub to your tablet and connect a Keyboard to the hub and a USB key with the BIOS file + FPT.efi command and the fparts.txt on the USB Drive.'
I have the bios thank to you, and the fpt.efi is in your post, but where is fparts.txt?
EDIT1 : Sorry, its in the zip, sorry.
What the next step to do after this tutorial? Flash a rom with mirek tool?
Thanks in advance
EDIT2 : @Mikha777 the tablet gives me an error ' Image type IA32 is not supported by this x64 shell'
Whats happens?
ozerec88 said:
Thank you, @Mikha777, so you think my tablets its still 'alive'?:victory:
what tutorial exactly? this? http://forum.xda-developers.com/showpost.php?p=62875595&postcount=12835
What is fparts.txt??
You say ' You connect a USB hub to your tablet and connect a Keyboard to the hub and a USB key with the BIOS file + FPT.efi command and the fparts.txt on the USB Drive.'
I have the bios thank to you, and the fpt.efi is in your post, but where is fparts.txt?
EDIT1 : Sorry, its in the zip, sorry.
What the next step to do after this tutorial? Flash a rom with mirek tool?
Thanks in advance
EDIT2 : @Mikha777 the tablet gives me an error ' Image type IA32 is not supported by this x64 shell'
Whats happens?
Click to expand...
Click to collapse
Ok you're on the right track, you receive the error message because on your X98 Air3 the UEFI shell seem to be 64bit and on the X98 Air II it is 32 bit.
Right now you are using the 32Bit version of FPT so you will have to use the 64bit version of FPT and it should work fine
I put the 64 bit version attached to this reply :angel:
Please let me know if it has worked fine !
Regards :cyclops:
Mikha777 said:
Ok you're on the right track, you receive the error message because on your X98 Air3 the UEFI shell seem to be 64bit and on the X98 Air II it is 32 bit.
Right now you are using the 32Bit version of FPT so you will have to use the 64bit version of FPT and it should work fine
I put the 64 bit version attached to this reply :angel:
Please let me know if it has worked fine !
Regards :cyclops:
Click to expand...
Click to collapse
Hello, good Morning!!thanks for the efi64, I have tried before wo go work, and the result is :
'Error 367 : [PFTEFI.efi] Cannot be run on the current platform.
Please contact your vendor
Click to expand...
Click to collapse
Whats happens? I dont understand .....its supposed to be that is x64 shell...the tablet told me after..
EDIT2 : @mysteryman2015 Did you have finally resolve your problem? I am reading your posts... Im stuck in the same situation, I think..
ozerec88 said:
Hello, good Morning!!thanks for the efi64, I have tried before wo go work, and the result is :
Whats happens? I dont understand .....its supposed to be that is x64 shell...the tablet told me after..
EDIT2 : @mysteryman2015 Did you have finally resolve your problem? I am reading your posts... Im stuck in the same situation, I think..
Click to expand...
Click to collapse
Yep, What happen I think is that the BIOS that you flashed messed with the UEFI framework so that's why those errors IMO.
From there the solution is to order a CH341A Programmer to Flash the bios I sent to you, it's easy to do
It cost less than $10 to order the parts but delivery is slow since it's from China. Look in my signature bellow you will find link to CH341A + Clip on ebay and also a tutorial that I've done to learn how to flash with CH341A with all the files you need. :angel:
Regards
Mikha777 said:
Yep, What happen I think is that the BIOS that you flashed messed with the UEFI framework so that's why those errors IMO.
From there the solution is to order a CH341A Programmer to Flash the bios I sent to you, it's easy to do
It cost less than $10 to order the parts but delivery is slow since it's from China. Look in my signature bellow you will find link to CH341A + Clip on ebay and also a tutorial that I've done to learn how to flash with CH341A with all the files you need. :angel:
Regards
Click to expand...
Click to collapse
Im outside this weekend, tomorrow I am going to buy you everything I need.
Im afraid about how dissasembly the teclast. Yesterday I have proved to flash the bios with fastboot and a recovery. img, but nothing happens,apears an error like 'cant boot device handle' or something like that.
Then, I tried to do again your EFI tutorial with a previosly signed (¿you say signed o verified?BIOS with fastboot and md5cc.exe , and when I type 'FPT.efi -f signed_bios' the efi tells me that only will accept signed BIOS , please execute md5cc.exe in your bios to do a......'
[emoji25] [emoji25]
Have a good sunday, @Mikha777.
Enviado desde mi G7-L01 mediante Tapatalk
ozerec88 said:
Im outside this weekend, tomorrow I am going to buy you everything I need.
Im afraid about how dissasembly the teclast. Yesterday I have proved to flash the bios with fastboot and a recovery. img, but nothing happens,apears an error like 'cant boot device handle' or something like that.
Then, I tried to do again your EFI tutorial with a previosly signed (¿you say signed o verified?BIOS with fastboot and md5cc.exe , and when I type 'FPT.efi -f signed_bios' the efi tells me that only will accept signed BIOS , please execute md5cc.exe in your bios to do a......'
[emoji25] [emoji25]
Have a good sunday, @Mikha777.
Enviado desde mi G7-L01 mediante Tapatalk
Click to expand...
Click to collapse
Don't worry it's easy, just take your time and be patient,. :good:
Follow this video to open your Teclast X98: https://www.youtube.com/watch?v=841pMJC_QOk
Regards
{
"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"
}
@Mikha777 , I think I have succedd flashing a signed Bios with fastboot,can you verify me this?
I upload a photos about my bios (I type 'exit' in EFI SHELL) and I entry in Bios..
Something is strange for me...as you can see, in boot devices I haven't anything, is normal this?
I have tried to boot a Rufus usb with a W10 image but when I press intro in the USB, nothing happens.. and if I choose usb as a first bootable device, when I restart I entry in OS selector screen, with 10 seconds countdown, or the tablet switch off, I select windows and nothing happens...
As I said before, I have a partition.tbl error when I try to flash with MFT, and Im triying to flash a rom with fastboot with fastboot comands:
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot format factory
fastboot format system
fastboot format cache
fastboot format config
fastboot format logs
fastboot format data
fastboot oem stop_partitioning
fastboot oem wipe ESP
fastboot oem wipe reserved
fastboot flash ESP esp.img
fastboot flash fastboot droidboot.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot continue
Click to expand...
Click to collapse
But in the second step I have an error '"unknown partition" & "error: cannot determine image filename for "partition.tbl'.
Enviado desde mi G7-L01 mediante Tapatalk
ozerec88 said:
View attachment 3722636View attachment 3722637View attachment 3722638View attachment 3722639
@Mikha777 , I think I have succedd flashing a signed Bios with fastboot,can you verify me this?
I upload a photos about my bios (I type 'exit' in EFI SHELL) and I entry in Bios..
Something is strange for me...as you can see, in boot devices I haven't anything, is normal this?
I have tried to boot a Rufus usb with a W10 image but when I press intro in the USB, nothing happens.. and if I choose usb as a first bootable device, when I restart I entry in OS selector screen, with 10 seconds countdown, or the tablet switch off, I select windows and nothing happens...
As I said before, I have a partition.tbl error when I try to flash with MFT, and Im triying to flash a rom with fastboot with fastboot comands:
But in the second step I have an error '"unknown partition" & "error: cannot determine image filename for "partition.tbl'.
Enviado desde mi G7-L01 mediante Tapatalk
Click to expand...
Click to collapse
You are on the right track !
You are also very lucky I found the solution for your missing boot/eMMC drive: http://techtablets.com/2015/10/teclast-x98-pro-boot-to-bios-missing-emmc-fix-bios-update/
Try it and let me know how it goes after !
Mikha777 said:
You are on the right track !
You are also very lucky I found the solution for your missing boot/eMMC drive: http://techtablets.com/2015/10/teclast-x98-pro-boot-to-bios-missing-emmc-fix-bios-update/
Try it and let me know how it goes after !
Click to expand...
Click to collapse
Oh my god ! @Mikha777
I have read the word file inside the rar and the pictures are the same than mine!!:silly::silly:
You are THE MASTER hahahaha
When I try to flash the @sikke1, I have a partitioning.tbl error, and if I try to flash with fastboot comands, I cant erase neither fastboot, recovery, data,cache..the tablet gives me an error and tells me that its impossible to flash or wipe anything....I think this is the cause, The pc detect the tablet but MFT/Fasboot cant have access to the Emmc.
PD : When I connect the tablet to the charger plug the battery icon an '9c' appears only 2 -3 seconds after dissapear (Its 'normal'?)...and I dont Know never when the tablet is charged, I tell you this because in the tutorial of techtablets say that I need 100%-80% battery...
Goodnight @Mikha777, this is a pic about trying the tutorial, as you can see, with 'afuefi.efi bios.bin /p /b /n /x' the error is Rom image layout detected rom hole is redesigned.
Surfing in webs, I learn about try adding '/l' command like ' afuefi.efi bios.bin /p /b /n /x /l' and the result is '18 - error: Secure flash rom verify fail'
My tablet is crazy:crying:
Maybe My eeprom is write protect?
I have discovered this maybe 'helpful threads' , but I can determine what happens..
https://www.bios-mods.com/forum/Thread-GIGABYTE-GA-B75TN-Bios-Unlock
http://techtablets.com/forum/topic/k9c3-cant-update-bios/
PD : I am seeing in techtablets people who use 'Phoneflashtools' to flash a new bios? it's possible?
http://techtablets.com/2015/10/how-to-convert-the-x98-pro-k9c3-to-dual-boot/ (see the second video)
http://techtablets.com/forum/topic/how-to-dualboot-androidwindows-on-k9c3/
YOU DECIDE MY NEXT STEP
Enviado desde mi G7-L01 mediante Tapatalk
Let me think about it I will come back tomorrow with an Idea to flash the BIOS that repair the eMMC drive
---------- Post added at 11:25 PM ---------- Previous post was at 11:06 PM ----------
ozerec88 said:
Goodnight @Mikha777, this is a pic about trying the tutorial, as you can see, with 'afuefi.efi bios.bin /p /b /n /x' the error is Rom image layout detected rom hole is redesigned.
Surfing in webs, I learn about try adding '/l' command like ' afuefi.efi bios.bin /p /b /n /x /l' and the result is '18 - error: Secure flash rom verify fail'
My tablet is crazy:crying:
Maybe My eeprom is write protect?
I have discovered this maybe 'helpful threads' , but I can determine what happens..
https://www.bios-mods.com/forum/Thread-GIGABYTE-GA-B75TN-Bios-Unlock
http://techtablets.com/forum/topic/k9c3-cant-update-bios/
PD : I am seeing in techtablets people who use 'Phoneflashtools' to flash a new bios? it's possible?
http://techtablets.com/2015/10/how-to-convert-the-x98-pro-k9c3-to-dual-boot/ (see the second video)
http://techtablets.com/forum/topic/how-to-dualboot-androidwindows-on-k9c3/
YOU DECIDE MY NEXT STEP
Enviado desde mi G7-L01 mediante Tapatalk
Click to expand...
Click to collapse
Could you try again with the FPT (EFI Version) utility to flash the New BIOS with the fix for the eMMC ? Let me know the results try the 32bit version first and if it did not work try the 64bit and let me know what happen. I have other ideas if it fail
Just copy the FPT utility on the USB drive to have it available.
Mikha777 said:
Let me think about it I will come back tomorrow with an Idea to flash the BIOS that repair the eMMC drive
---------- Post added at 11:25 PM ---------- Previous post was at 11:06 PM ----------
Could you try again with the FPT (EFI Version) utility to flash the New BIOS with the fix for the eMMC ? Let me know the results try the 32bit version first and if it did not work try the 64bit and let me know what happen. I have other ideas if it fail
Just copy the FPT utility on the USB drive to have it available.
Click to expand...
Click to collapse
Hello @Mikha777 , first I have tried to flash the bios with fastboot, as the last time, I have signed firs the bios with md5add.exe and then upload to eeprom.
RESULT--> My tablet NOW is Hardbrick...dont switch on. Was my last chance... but I'm not sad.
I'll buy you the clip and the programmer , and I will put him again bios.
It is possible to recover the tablet?
Is there any way to put him with this method the new bios repairing EMMC ?
I'm learning a lot these days, and want to continue learning . I do not give up on my desire to revive it.
What do you think ?
I'm crazy ? haha
ozerec88 said:
Hello @Mikha777 , first I have tried to flash the bios with fastboot, as the last time, I have signed firs the bios with md5add.exe and then upload to eeprom.
RESULT--> My tablet NOW is Hardbrick...dont switch on. Was my last chance... but I'm not sad.
I'll buy you the clip and the programmer , and I will put him again bios.
It is possible to recover the tablet?
Is there any way to put him with this method the new bios repairing EMMC ?
I'm learning a lot these days, and want to continue learning . I do not give up on my desire to revive it.
What do you think ?
I'm crazy ? haha
Click to expand...
Click to collapse
Hi,
With the programmer you should succeed at 99% I never see somebody fail till now, just take your time :angel:
The hardest part is to put the clip on the chip correctly, it can take several times to have it right (at least for me) but once the clips is well connected
it's just a matter of minutes to program the Firmware.
I would program the BIOS/Firmware v1.13 to fix the whole thing (eMMC drive not recognized) after that everything should be fine.
Let me know if you have any question !
GL
Mikha777 said:
Hi,
With the programmer you should succeed at 99% I never see somebody fail till now, just take your time :angel:
The hardest part is to put the clip on the chip correctly, it can take several times to have it right (at least for me) but once the clips is well connected
it's just a matter of minutes to program the Firmware.
I would program the BIOS/Firmware v1.13 to fix the whole thing (eMMC drive not recognized) after that everything should be fine.
Let me know if you have any question !
GL
Click to expand...
Click to collapse
Hello, @Mikha777 , I cant buy you the clip and CH, because you dont ship to Spain.
I live in Alicante,Spain.
What I have to do? search another seller? I want to buy you, you helped me. Is the least I can do.
ozerec88 said:
Hello, @Mikha777 , I cant buy you the clip and CH, because you dont ship to Spain.
I live in Alicante,Spain.
What I have to do? search another seller? I want to buy you, you helped me. Is the least I can do.
Click to expand...
Click to collapse
Don't worry, It's not me the seller, this is just the seller that I bought the CH341, it's not me who sells. :angel:
I put the link just for the convenience since users asked me from where I bought the CH341 and clips.
You can buy from anybody all CH341A programmer are the same, so you can buy from any sellers that ship in Spain. :cyclops:
Mikha777 said:
Don't worry, It's not me the seller, this is just the seller that I bought the CH341, it's not me who sells. :angel:
I put the link just for the convenience since users asked me from where I bought the CH341 and clips.
You can buy from anybody all CH341A programmer are the same, so you can buy from any sellers that ship in Spain. :cyclops:
Click to expand...
Click to collapse
Hello @Mikha777 can you verify me this products?
are the same? the things I need? Are from Uk, most cheap than inside Spain and most fast than buy in China.
CH--> http://www.ebay.es/itm/USB-Programa...031663?hash=item542a5d9faf:g:LGsAAOSwQYZWvDCF
CLIP--> http://www.ebay.es/itm/NEW-SOIC8-SO...434099?hash=item3f607843f3:g:qbIAAOxyeZNTV6bP
Do need I a 'plastic tool' to dissasembly the teclast?
Regards.
ozerec88 said:
Hello @Mikha777 can you verify me this products?
are the same? the things I need? Are from Uk, most cheap than inside Spain and most fast than buy in China.
CH--> http://www.ebay.es/itm/USB-Programa...031663?hash=item542a5d9faf:g:LGsAAOSwQYZWvDCF
CLIP--> http://www.ebay.es/itm/NEW-SOIC8-SO...434099?hash=item3f607843f3:g:qbIAAOxyeZNTV6bP
Do need I a 'plastic tool' to dissasembly the teclast?
Regards.
Click to expand...
Click to collapse
Yep they are the same
No really tool needed I used "guitar picks" to open the case look here at my post: http://forum.xda-developers.com/showpost.php?p=63335867&postcount=13250 Plastic tools are often to soft and broke easily guitar pic (in nylon) are more tough and lot less expensive and available in different thickness
The trick is just to take your time for the disassembly, if you are to lose patience just take a break and come back later to pursue We don't open case each day so it's normal to have some difficulty but nothing big :angel: If you have any question or difficulties to flash just send me a reply on this thread .
Regards
Mikha777 said:
Yep they are the same
No really tool needed I used "guitar picks" to open the case look here at my post: http://forum.xda-developers.com/showpost.php?p=63335867&postcount=13250 Plastic tools are often to soft and broke easily guitar pic (in nylon) are more tough and lot less expensive and available in different thickness
The trick is just to take your time for the disassembly, if you are to lose patience just take a break and come back later to pursue We don't open case each day so it's normal to have some difficulty but nothing big :angel: If you have any question or difficulties to flash just send me a reply on this thread .
Regards
Click to expand...
Click to collapse
Hello @Mikha777 , in ebay the total cost was near 20... dont worth for me. The tablet cost me 70 euros, and if I add 20, its 90, and this tablet cost 110-120 if I buy a new one.
So, finally, I have bought them in Aliexpress.
Programmer-->http://es.aliexpress.com/item/Free-...er-DVD-programmer-router-Nine/1840274214.html
Clip-->http://es.aliexpress.com/item/SOIC8...BIOS-24-25-93-Programmer-YKS/32252236712.html
Can you confirm that are the correct 'tools' ?:laugh:
I paid yet.
Regards!
PD : I know we are talking near a two weeks, tree, to receive the tools, dont mind.
Hi,
I always found it saddening to notice EZCast5G (the "original") is updated at first and their knock offs are updated way later (as of writing this, there is 16602000 for EZCast5G, 16403000 for MiraScreen5G).
The update tool let's you easily analyze the update process. And if you fake the reply from this URL with (for example) miniweb to always dish out latest EZCast5G firmware then your knock off will become an original.
These are the requests made for a legit EZCast5G and a MiraScreen5G:
Code:
[COLOR="Purple"]curl http://www.iezvu.com/upgrade/ota_rx.php -d "{\"version\":1,\"vendor\":\"ezcast5g\",\"mac_address\":\"authorshxj\",\"softap_ssid\":\"000000-00000000\",\"firmware_version\":\"16602000\"}"[/COLOR]
[COLOR="Blue"]curl http://www.iezvu.com/upgrade/ota_rx.php -d "{\"version\":1,\"vendor\":\"am8252_nand_mirascreen\",\"mac_address\":\"authorshxj\",\"softap_ssid\":\"000000-00000000\",\"firmware_version\":\"16403000\"}"[/COLOR]
These are the official replys where you need to always dish out the first one and the update tool will do the rest:
Code:
[COLOR="Purple"]{"ota_conf_file":"http://cdn.iezvu.com/upgrade/ezcast5g/ezcast5g-16602000.conf","ota_fw_file":"http://cdn.iezvu.com/upgrade/ezcast5g/ezcast5g-16602000.gz","ota_enforce":true}[/COLOR]
[COLOR="Blue"]{"ota_conf_file":"http://cdn.iezvu.com/upgrade/am8252_nand_mirascreen/am8252_nand_mirascreen-16403000.conf","ota_fw_file":"http://cdn.iezvu.com/upgrade/am8252_nand_mirascreen/am8252_nand_mirascreen-16403000.gz","ota_enforce":true}[/COLOR]
When I opened mine it even read "5G EZCAST V1.4" on it - so I was pretty sure it should work. And it did. So for $17 one year ago I got myself a neat working EZCast5G. The MiraScreen5G gets into bootloader mode by pressing the one and only button right when you plug it into USB - no need to shorten pin 19 and 20 of the AM8252.
Thank you.
Some questions.
How to use this curl command with miniWeb?
Hi,
BUMP
No honestly, could you elaborate how this works ? Have 2 MiraScreen5G dongles...
Ender
Hi,
with some help from Chatty and another forum i got it done !
First i needed to add a line to my hosts file:
(On windows its found in C:\Windows\System32\drivers\etc)
Code:
127.0.0.1 www.iezvu.com
Then i downloaded miniweb and created a file containing the desired server answer.
Miniwebs web root resides in the "htdocs" folder by default, so i created a folder named "upgrade" and in that folder a file named "ota_rx.php.
I edited that file to contain this text:
Code:
{"ota_conf_file":"http://cdn.iezvu.com/upgrade/ezcast5g/ezcast5g-16602000.conf","ota_fw_file":"http://cdn.iezvu.com/upgrade/ezcast5g/ezcast5g-16602000.gz","ota_enforce":true}
I fired up miniweb with the parameter "-p 80" to listen on the stabdard web port.
THEN i started the EZ Updater app, connected my dongle in Flash mode and VOILA it detected the version i wanted it to detect.
So it flashed (took forever with several loops) my MiraScreen5G to a EZCast5G !!!!
After that initial update the dongle detected a newer version and updated okay.
Please note that AFTER the update you cannot get into flash mode by simply pressing the key. I assume that key is not considered existing anymore since the EZCast5G has none as well
So for further flash-fun we need to short the Pin like its descived by Chatty !
THANKS Chatty & all,
Ender
Just opened a K6 mirascreen and found these
nanya nt5cb64m16fp-dh 128mb ddr3 ram
am8272
samsung k9f1g08u0d 16mb flash
the pcb reads S?-EZCAST-8271-V2F
im unable to find a suitable firmware for it and no idea how to enter download mode....
---------- Post added at 06:02 PM ---------- Previous post was at 05:35 PM ----------
the firmware says 1.3707.11 btw
Hey Guys,
If someone knows, please share the knowledge.
Few Months ago when I was updating the firmware, my Dongle died due to power cut.
after reconnecting my PC couldn't read the version of my dongle. Today I wanted to revive my Dongle But have no to little experience on the Windows Debugging. I know my Dongle is not dead and it has no firmware, I also know that EZCast Repair tool can Flash the Firmware to it, I can download the firmware using the OP, I can also see that The App has options for Manually flashing the Firmware.
But I don't know how and what to do to access the areas shown in the Screenshot.
anyone please help me and point me to right direction.
Thanks in Advance.
SweenWolf said:
Hey Guys,
If someone knows, please share the knowledge.
Few Months ago when I was updating the firmware, my Dongle died due to power cut.
after reconnecting my PC couldn't read the version of my dongle. Today I wanted to revive my Dongle But have no to little experience on the Windows Debugging. I know my Dongle is not dead and it has no firmware, I also know that EZCast Repair tool can Flash the Firmware to it, I can download the firmware using the OP, I can also see that The App has options for Manually flashing the Firmware.
But I don't know how and what to do to access the areas shown in the Screenshot.
anyone please help me and point me to right direction.
Thanks in Advance.
Click to expand...
Click to collapse
Have you found any help? I have updated to EzCast firmware but now my dongle doesn't appear on wifi list and on TV only shows EzCast logo..
dLightas said:
Have you found any help? I have updated to EzCast firmware but now my dongle doesn't appear on wifi list and on TV only shows EzCast logo..
Click to expand...
Click to collapse
No I found no help.
All I need is access the flashing area.
I had 2 tools laying around (think i deleted those)
One was older and directly opened the firmware flashing page, but that doesn't have the partition table of My Dongle.
And the other tool which have the partition table, opens on main page (which is automated and does nothing)
If somehow i could access the firmware flashing area on the newer tool then I could revive my dongle.
If your dongle contained older chip of Action Electronics (earlier than 52) then the older tool can flash your dongle.
nostupidthing said:
Just opened a K6 mirascreen and found these
nanya nt5cb64m16fp-dh 128mb ddr3 ram
am8272
samsung k9f1g08u0d 16mb flash
the pcb reads S?-EZCAST-8271-V2F
im unable to find a suitable firmware for it and no idea how to enter download mode....
---------- Post added at 06:02 PM ---------- Previous post was at 05:35 PM ----------
the firmware says 1.3707.11 btw
Click to expand...
Click to collapse
Today there was a firmware upgrade available and after updating it's dead any help
Edit: OK I was able to flash using this tool (https://mirascreen.com/pages/repair-tool-for-chip-8272-products) but still nothing comes up...
Edit 2: The new firmware is 1.10505.52
MiraScreen G9 Plus
=================
[Name Model] , [Vendor String] , [Supported of the "MiraScreen G9 Plus"]
(EZCast5G) - ezcast5g - Not supported
(MiraScreen5G) - am8252_nand_mirascreen - Not supported
(EZCast 2H) - am_8270_ezcast4k-dongle_ezcast2h - Not supported
(EZCast TX) - am_8270_ezcast-tx_nand-std - Not supported
(EZCast 2) - am8271_ezcast2K - Not supported
(EZCast 4K) - ezcastduo - Not supported
(EZCast Band1) - am_8271_ezcast2-dongle_b1 - Not supported
(EZCast Ultra) - am_8275_ezcast-dongle_ultra - Not supported
(AnyCast M100) - sage_8272_mirascreen-dongle_anycast - Supported
(MiraScreen K6) - am_8272_mirascreen-dongle_std - Supported
Check Firmware over http api:
https://api.ezcast.com/api/firmware...mirascreen-dongle_std&firmware_version=1.10.3
https://www.ezcast.com/service/ota/..._8272_mirascreen-dongle_std&rx_version=1.10.3
Current official firmware version for the "Mirascreen G9 Plus": 1.10505.61
Do you know others? I would for the model "Mirascreen G9 Plus"?
"Mirascreen G9 plus" supports alternative Firmware (Firmware tested on the "MiraScreen G9 Plus"):
FW v1.13610.47: http://cdn.iezcast.com/upgrade/am_8...dongle_std_official-1.13610.47-0x99A7C4FD.img
Flash Tool: https://cdn.shopify.com/s/files/1/0017/6553/9884/files/MiraScreen_8272_Repair_Tool.rar
FW v1.10505.3: http://cdn.iezcast.com/upgrade/sage...gle_anycast_official-1.10505.3-0x937AC2AD.img
Flash Tool: https://cdn.shopify.com/s/files/1/2427/2515/files/AnyCast_M100Repair_Tool.zip
Small modification of Wi-Fi antenna:
https://forum.xda-developers.com/t/mirascreen-g9-plus-hw-fw-mods.4391225/
Hi to all, can anyone help me please with my EZ mira app and dongle device associated with it (miracast).
I have tried to upgrade software for my miracast device thru EZmira app, but suddenly Commercials pop up and my upgrade has been stuck at 10% and won't go further , worse after disconnect or reset there is no signal at all anymore it does not start /boot nor emmit wifi signal. What to do (because of stupid commercial)??
I tried to reset device several times but nothing, tried reseting thru PC but it does not load or Windows does not recognoze device to upgrade it thru web tools.
Please can anyone get that firmware back in my device and restore it .
Much appriciated and thanks in advance!
Anton TNT said:
Hi to all, can anyone help me please with my EZ mira app and dongle device associated with it (miracast).
I have tried to upgrade software for my miracast device thru EZmira app, but suddenly Commercials pop up and my upgrade has been stuck at 10% and won't go further , worse after disconnect or reset there is no signal at all anymore it does not start /boot nor emmit wifi signal. What to do (because of stupid commercial)??
I tried to reset device several times but nothing, tried reseting thru PC but it does not load or Windows does not recognoze device to upgrade it thru web tools.
Please can anyone get that firmware back in my device and restore it .
Much appriciated and thanks in advance!
Click to expand...
Click to collapse
Do you have a specific device?
Manufacturing publishes tools to restore some firmware here:
EZCast: https://www.ezcast.com/repair
MiraScreen:
https://mirascreen.com/pages/repair-tool-for-chip-8268-8252-products
https://mirascreen.com/pages/repair-tool-for-chip-8272-products
AnyCast:
https://any-cast.com/pages/repair-tool-for-chip-8268-8258-products
https://any-cast.com/pages/repair-tool-for-chip-8272-products
renda-l said:
Do you have a specific device?
Manufacturing publishes tools to restore some firmware here:
EZCast: https://www.ezcast.com/repair
MiraScreen:
https://mirascreen.com/pages/repair-tool-for-chip-8268-8252-products
https://mirascreen.com/pages/repair-tool-for-chip-8272-products
AnyCast:
https://any-cast.com/pages/repair-tool-for-chip-8268-8258-products
https://any-cast.com/pages/repair-tool-for-chip-8272-products
Click to expand...
Click to collapse
I have trided this solution , but no prevail, like device is dead, nothing just blank screen after failed update
Anton TNT said:
I have trided this solution , but no prevail, like device is dead, nothing just blank screen after failed update
Click to expand...
Click to collapse
This procedure works 100%, completely restores the firmware. If only an incorrect update occurred.
renda-l said:
This procedure works 100%, completely restores the firmware. If only an incorrect update occurred.
Click to expand...
Click to collapse
I'm not shure maybe I'm doing something wrong, but even windows doesn't recognize device
Anton TNT said:
I'm not shure maybe I'm doing something wrong, but even windows doesn't recognize device
Click to expand...
Click to collapse
Yes, of course, if the firmware is faulty, the device is not recognized and does not work. You must follow the Firmware Recovery Procedure. The device will most likely be repaired. Unfortunately, unless you specify a specific type, you can't be specifically advised on how to proceed.
renda-l said:
Yes, of course, if the firmware is faulty, the device is not recognized and does not work. You must follow the Firmware Recovery Procedure. The device will most likely be repaired. Unfortunately, unless you specify a specific type, you can't be specifically advised on how to proceed.
Click to expand...
Click to collapse
It is MIRACAST, I dont know chip number but it is dongle type round shaped eith EZmira app controlled
Anton TNT said:
It is MIRACAST, I dont know chip number but it is dongle type round shaped eith EZmira app controlled
Click to expand...
Click to collapse
Set your device to Recovery mode according to the procedure and use the tool for chip 8268/8252 or 8272. If the response is "device connected", it is a given chip set.
renda-l said:
Set your device to Recovery mode according to the procedure and use the tool for chip 8268/8252 or 8272. If the response is "device connected", it is a given chip set.
Click to expand...
Click to collapse
on which side is pin 7 and 8 ? Chip on my board is square shaped and got pins on all sides. Just to be sure not to fry anything, which side is NAND memory
Anton TNT said:
on which side is pin 7 and 8 ? Chip on my board is square shaped and got pins on all sides. Just to be sure not to fry anything, which side is NAND memory
Click to expand...
Click to collapse
If your device has a button, first try to enter recovery mode, press the button and connect USB.
In the procedure is a photo of the MCU and these pins are shown.