Unable to root chromecast - Google Chromecast

Dear fellow members, I followed the rooting Directions to the letter, and for some reason everytime I try to flash the chromecast root rom , the chrome cast lights up red and stays red and then when I take the flash drive off the cable and put it back on to the computer in order to finish the last part of the rooting process, the flash drive does not say flashcast , it says( removable disk E ) and will not let me paste the last part of the rom and will not open . I keep getting a disk needs to be formatted message. I reformatted this flash drive like 4 times and tried to flash this rom and it wont work , what do you think is wrong ? also I have never connected it to the internet or let it update. thank you in advance

Hi Wilspeak,
Just in case you don't see my post in the Eureka-ROM thread in reply to you.
Really sorry to be the bearer of bad news however the Chromecast you have purchased is not within the Rootable Serial Number range and therefore cannot be rooted at this time (as it comes from factory with a software version with no currently known exploit)
Unfortunately the highest serial numbers we are aware of working for rooting are 3922xxx and as such your 3Axx will not work. (this has been confirmed by XDA users @mrdelriego and @pandacookie)
My condolences,
Kyonz

I feel your pain man. I was planning on rooting mine but I stupidly plugged it in first and it updated.
I wanted be able to change the dns to be able to grab content from other countries without having to go through checking my router.
Bummety
Sent from my Nexus 4 using xda app-developers app

I want to know if the Team would try to develop a root method for the chromecast's that cant be rooted at this time ?

Kyonz said:
Hi Wilspeak,
Just in case you don't see my post in the Eureka-ROM thread in reply to you.
Really sorry to be the bearer of bad news however the Chromecast you have purchased is not within the Rootable Serial Number range and therefore cannot be rooted at this time (as it comes from factory with a software version with no currently known exploit)
Unfortunately the highest serial numbers we are aware of working for rooting are 3922xxx and as such your 3Axx will not work. (this has been confirmed by XDA users @mrdelriego and @pandacookie)
My condolences,
Kyonz
Click to expand...
Click to collapse
Senior Member - OP
Thanks Meter 5
Posts: 106
Join Date: Jul 2011
Location: ga
MORE INFO >
I want to know if the Team would try to develop a root method for the chromecast's that cant be rooted at this time ? Thank you

Related

LG 4xHD not registered

I have just managed to root my old LG P880/4xHD using advice from this forum. Thought I would try on an old phone first. One reason I tried is because I cannot update Android via the usual About phone, Software updates, Check now for updates. The Android version installed is 4.0.3. I am in Australia and it is possible the phone is an overseas model (got it from a friend in LG). Has "Not for Resale" stamped inside the back cover. When I try to update Android, I get an error message "Registered Error - Your device is not registered yet." I had hoped rooting would get around this but it hasn't. Have looked up old forum posts and there is talk of using .kdz files and all sorts of other things. Can anyone help me get around this registration issue but please be aware I am a novice and most of the older posts I read, I couldn't understand so simple explanations please. Thanks.
What you have is developer or test device and it is a bit different from normal ones. Try googling more but you will have hard time....
Sent from my microwave.
dimi89 said:
What you have is developer or test device and it is a bit different from normal ones. Try googling more but you will have hard time....
Sent from my microwave.
Click to expand...
Click to collapse
Could it be that it has overseas firmware, I read in a two or three year old post that this can happen but there was a way to get around this.
PD
pdonahue said:
Could it be that it has overseas firmware, I read in a two or three year old post that this can happen but there was a way to get around this.
PD
Click to expand...
Click to collapse
So...Did you try flashing kdz file and updating it that way or ... ?
pdonahue said:
I have just managed to root my old LG P880/4xHD using advice from this forum. Thought I would try on an old phone first. One reason I tried is because I cannot update Android via the usual About phone, Software updates, Check now for updates. The Android version installed is 4.0.3. I am in Australia and it is possible the phone is an overseas model (got it from a friend in LG). Has "Not for Resale" stamped inside the back cover. When I try to update Android, I get an error message "Registered Error - Your device is not registered yet." I had hoped rooting would get around this but it hasn't. Have looked up old forum posts and there is talk of using .kdz files and all sorts of other things. Can anyone help me get around this registration issue but please be aware I am a novice and most of the older posts I read, I couldn't understand so simple explanations please. Thanks.
Click to expand...
Click to collapse
Its a year old phone, its not like its the nexus one or samsng galaxy s2...
Try flashing 4.12 with kdz. Google is your friend, try kdz flash 4.1.2 Optimus 4x hd.
Funny thing, when I bought my phone, only google asked me to register the phone, the usual Google Play thing. SO what do you exactly mean with REGISTER?
i think the whole phone isn't registred by LG for consumers, like dimi89 said it has to be a dev device. they aren't registred and cannot be updated/used the normal way. the serial number of this phone isn't present in the LG databases i think. Just flash kdz and everything is fine. You know that you don't get any support or warranty on that phone but you should know that.

[Q] TF701 bricked to APX. blob file issue.

Dear All,
I hope somebody can help me with hard bricked TF701T.
My sad story: I was very happy when bought brand new TF701. It came with US 4.22 android and with non working RCK, so I was not able to make a proper backup. Device has the following problems before my first upgrdae to 4.3:
1. Periodically, screen slightly blinking (5-10 percent of normal to little more dark and back, for one-two second).
2. Several times my tab was restarting by itself, especially when I was using file manager (ES explorer)
3. Also, when lot of people was able to make an upgrade using asus menu, my tab always replied me that SW is new and upgrade is not needed.
That's why I downloaded the official "US_epaduser_10_26_1_18_UpdateLauncher.zip" from asus site, putted it into the root / and after restart, system message came - new version is available. So I did it, upgrade to 4.3 was successful.
After that, screen stop to blink. But problem with non working RCK still present. So my next step was installation of CWM, using fastboot ADB. Everything was fine, but my first test backup has been not completely fine - after system & files, md5 checksum was generating for more than one hour, and backup was not completely performed (I've interrupted the process after one hour "md5")
My last successful step was rooting of my poor tab..
Finally, I obtained the 4.3 with root access, working CWM and no more 3 of listed above problems. The only md5 issue was pending.
Than I have performed my FATAL error.. I start playing with nvram - thanks to easy flasher tool (but it is my fault, no question)
As result, I have TOTALLY DEAD TF701. Boot loop with ASUS logo, fastboot (- & power) is not available anymore;
The only thing I have it is APX availability, but according to my internet research there is no chance to unbrick tf701t for now. At list NvFlash is not recognized my device. Latest version of NvFlash tool answering me:
*************************************************************
C:\nvflash-tools-win32>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x2000000016ff0440
[-] Failed to read RCMVERS from blob file.
*************************************************************
(If smb knows what must be in the RCMVERS file - digital signature, CPU info or what? pls reply me)
Please, if somebody has same problem and there is any chance to unbrick my tab, reply me!!!
Btw, I have tried to call asus support, the only help I obtain was a negative experience.
stream1313 said:
Dear All,
I hope somebody can help me with hard bricked TF701T.
My sad story: I was very happy when bought brand new TF701. It came with US 4.22 android and with non working RCK, so I was not able to make a proper backup. Device has the following problems before my first upgrdae to 4.3:
1. Periodically, screen slightly blinking (5-10 percent of normal to little more dark and back, for one-two second).
2. Several times my tab was restarting by itself, especially when I was using file manager (ES explorer)
3. Also, when lot of people was able to make an upgrade using asus menu, my tab always replied me that SW is new and upgrade is not needed.
That's why I downloaded the official "US_epaduser_10_26_1_18_UpdateLauncher.zip" from asus site, putted it into the root / and after restart, system message came - new version is available. So I did it, upgrade to 4.3 was successful.
After that, screen stop to blink. But problem with non working RCK still present. So my next step was installation of CWM, using fastboot ADB. Everything was fine, but my first test backup has been not completely fine - after system & files, md5 checksum was generating for more than one hour, and backup was not completely performed (I've interrupted the process after one hour "md5")
My last successful step was rooting of my poor tab..
Finally, I obtained the 4.3 with root access, working CWM and no more 3 of listed above problems. The only md5 issue was pending.
Than I have performed my FATAL error.. I start playing with nvram - thanks to easy flasher tool (but it is my fault, no question)
As result, I have TOTALLY DEAD TF701. Boot loop with ASUS logo, fastboot (- & power) is not available anymore;
The only thing I have it is APX availability, but according to my internet research there is no chance to unbrick tf701t for now. At list NvFlash is not recognized my device. Latest version of NvFlash tool answering me:
*************************************************************
C:\nvflash-tools-win32>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x2000000016ff0440
[-] Failed to read RCMVERS from blob file.
*************************************************************
(If smb knows what must be in the RCMVERS file - digital signature, CPU info or what? pls reply me)
Please, if somebody has same problem and there is any chance to unbrick my tab, reply me!!!
Btw, I have tried to call asus support, the only help I obtain was a negative experience.
Click to expand...
Click to collapse
As far as I am aware the nvflash tools are not yet released for the TF701T, so who knows what bootloader you have now flashed. Unless some miracle happens you look hard bricked
I'm guessing you didn't notice the devices nvflash supports which is an unfortunate and costly mistake.
sbdags said:
As far as I am aware the nvflash tools are not yet released for the TF701T, so who knows what bootloader you have now flashed. Unless some miracle happens you look hard bricked
I'm guessing you didn't notice the devices nvflash supports which is an unfortunate and costly mistake.
Click to expand...
Click to collapse
Thank you for reply. Definitely it's my fault for 100%, because I've not checked the nvflash possibility, before I start playing with blob Really stupid story, especially I have already performed all the needed things as rooting, update, CWM.
The main reason I'm posting here is to check, does anybody who has a deep knowledge of such devices design, already experienced with TF701T recovery?
I hope at list single person in the world (not counting asus engineers, as far as their company politic became similar to microsoft or oracle) knows the backdoor way to this tab recovery..?
Help needed
stream1313 said:
Thank you for reply. Definitely it's my fault for 100%, because I've not checked the nvflash possibility, before I start playing with blob Really stupid story, especially I have already performed all the needed things as rooting, update, CWM.
The main reason I'm posting here is to check, does anybody who has a deep knowledge of such devices design, already experienced with TF701T recovery?
I hope at list single person in the world (not counting asus engineers, as far as their company politic became similar to microsoft or oracle) knows the backdoor way to this tab recovery..?
Click to expand...
Click to collapse
Hey people... Nobody can help me?
Asus help us
Hello ASUS !!!
You have to HELP us, in order to keep your consumer with you. Other vice people will start to think that your ASUS brand is not a trustful brand anymore. Using such tricks as providing consumer with possibility to open a "Pandora's box" with bootloader unlock, and after you pushing consumer to pay about 300 $ for "motherboard replacing".
Following such kind of policy you will collect some money but definitely you will loose much more.
Sincerely,
Stream1313
PS: I was started to use the "unlock" etc not because I do not have other business t do but because of the serious problem in your DEFAULT STOCK software.
To: Moderator - please do not delete this post, hopefully some ASUS people will read it.
This is not asus' fault at all. When you unlock your bootloader you void your warranty, as with all devices not just asus transformers. When you modify your device, and tamper with it, its no longer what asus sold it to you as. If you used easy flasher which is for the tf101 and not 701, there is no one to blame for this mistake but yourself. Especially when you flash a bootloader for a different device. Unless you have a JTAG theres not much to do. Even then who knows. Im not bashing you here, just so you know. Good luck with your device, although im afraid its a pretty expensive paperweight by now.
Sent from my GS3 on PAC 4.4 using Tapatalk 4
lol
ebildude123 said:
This is not asus' fault at all. When you unlock your bootloader you void your warranty, as with all devices not just asus transformers. When you modify your device, and tamper with it, its no longer what asus sold it to you as. If you used easy flasher which is for the tf101 and not 701, there is no one to blame for this mistake but yourself. Especially when you flash a bootloader for a different device. Unless you have a JTAG theres not much to do. Even then who knows. Im not bashing you here, just so you know. Good luck with your device, although im afraid its a pretty expensive paperweight by now.
Sent from my GS3 on PAC 4.4 using Tapatalk 4
Click to expand...
Click to collapse
Dear ebildude123,
Seems you have some relationships with ASUS, is it? See, I'm not trying to say that it's not a my fault. If you read my post carefully, it is clearly described that I'm confirming - it is 100% my fault. but I want to say about other things:
At first, I started because of the following ASUS DEFAULT PROBLEM's: suddenly screen was blinking, w/o any reason; tab was restarting by itself, at list once per 2-3 days; Default backup was not working, battery life time was low etc.
My main message is: ASUS distributed the unlock SW on site, together with USER LEVEL SW. It is incorrect, IMHO. They should distribute it within advanced users and developers, using some more safe mechanism. As minimum they have to sign this download as potentially DANGEROUS for unexperienced user.
But currently it is open to everybody so it is like a Pandora's box, which is asking - "open me" and as result many of people getting hard bricked tabs. Then, ASUS forcing them to pay 300$ or whatever. Actually, I do not crying too much for my bricked device (I have my laptop and desktop with me, as well as my linux server) Also I know that I just need to wait a little more for compatible nvflash.. ...but I do not think that I will purchase another ASUS device in the future..
IMHO - if you DISTRIBUTING on your site the bootloader unlock tool, you have to provide nvflash or any other way to restore the tab / phone, but not pushing stupid idea about "mainboard replacement" for almost device price itself. So you have your opinion - and it is mine. Ok? Good luck
stream1313 said:
Dear ebildude123,
Seems you have some relationships with ASUS, is it? See, I'm not trying to say that it's not a my fault. If you read my post carefully, it is clearly described that I'm confirming - it is 100% my fault. but I want to say about other things:
At first, I started because of the following ASUS DEFAULT PROBLEM's: suddenly screen was blinking, w/o any reason; tab was restarting by itself, at list once per 2-3 days; Default backup was not working, battery life time was low etc.
My main message is: ASUS distributed the unlock SW on site, together with USER LEVEL SW. It is incorrect, IMHO. They should distribute it within advanced users and developers, using some more safe mechanism. As minimum they have to sign this download as potentially DANGEROUS for unexperienced user.
But currently it is open to everybody so it is like a Pandora's box, which is asking - "open me" and as result many of people getting hard bricked tabs. Then, ASUS forcing them to pay 300$ or whatever. Actually, I do not crying too much for my bricked device (I have my laptop and desktop with me, as well as my linux server) Also I know that I just need to wait a little more for compatible nvflash.. ...but I do not think that I will purchase another ASUS device in the future..
IMHO - if you DISTRIBUTING on your site the bootloader unlock tool, you have to provide nvflash or any other way to restore the tab / phone, but not pushing stupid idea about "mainboard replacement" for almost device price itself. So you have your opinion - and it is mine. Ok? Good luck
Click to expand...
Click to collapse
Haha no relationship with Asus. I guarantee it. While I agree unlock tool shouldn't be thrown around, that's not what bricks your device, it's what you flash that does. Personally I think they should use fastboot unlock instead but meh. Yes of course everyone has their own opinions. I respect yours and hope you respect mine as well. Good luck with nvflash but I have doubts your current blob would work even if they made a tool compatible with tf701 tegra4.
Sent from my GS3 on PAC 4.4 using Tapatalk 4
lol, hope your post do not really had any Asus roots)
now I need advice, if possible..
what do you think about Linux installation, which is described in network, according to them even bricked tf701 is recoverable?
Pls, if somebody already experienced, reply me!
Sent from my Xperia Arc S using xda app-developers app
stream1313 said:
lol, hope your post do not really has any Asus roots)
now I need advice, if possible..
what do you think about Linux installation, which is described in network, according to them even bricked tf701 is recoverable?
Please, if somebody already experienced, reply me...
Sent from my Xperia Arc S using xda app-developers app
Click to expand...
Click to collapse
anybody here?
stream1313 said:
anybody here?
Click to expand...
Click to collapse
APX mode with no nvflash blobs = hard bricked device. Your device needs specific blobs encrypted with the key. You can't even boot to working bootloader.
Even Asus don't **** around with them they just replace the mother board.
Suggest you do the same, it's THE ONLY WAY you are going to get your device back. Linux will not help you here.
sbdags said:
APX mode with no nvflash blobs = hard bricked device. Your device needs specific blobs encrypted with the key. You can't even boot to working bootloader.
Even Asus don't **** around with them they just replace the mother board.
Suggest you do the same, it's THE ONLY WAY you are going to get your device back. Linux will not help you here.
Click to expand...
Click to collapse
Hi sbdags,
Thanks for your message, currently I just trying to keep my brick charged, to prevent battery dead.. Will wait till smb from ASUS or from outside will broke the bloody encrypted bootloader, because I do not have possibility to replace he main board ((
Well, three years later and my TF701 bricked itself over night. Only thing I see is APX in the windows device manager. I managed to get a driver for that but am now stuck with the next steps, if there are any at all.
Kashban said:
Well, three years later and my TF701 bricked itself over night. Only thing I see is APX in the windows device manager. I managed to get a driver for that but am now stuck with the next steps, if there are any at all.
Click to expand...
Click to collapse
yep!
maybe i got a solution, but untested for mass unbrick)
i'm already unbrick few devices.
need someone with bricked device and tech skills to test for public use.
mr.bin said:
yep!
maybe i got a solution, but untested for mass unbrick)
i'm already unbrick few devices.
need someone with bricked device and tech skills to test for public use.
Click to expand...
Click to collapse
Sorry for being late.
That would be great and yes, I do have the tech skills. What do you want me to test?
Kashban said:
That would be great and yes, I do have the tech skills. What do you want me to test?
Click to expand...
Click to collapse
Sent PM with instuctions.
Please keep inform about results.
mr.bin said:
yep!
maybe i got a solution, but untested for mass unbrick)
i'm already unbrick few devices.
need someone with bricked device and tech skills to test for public use.
Click to expand...
Click to collapse
I also have recently experienced a hard brick on an asus tf700t running KatKiss-7.1_TF700T_026
APX mode & only a TWRP backup
I would also like to try your method to unbrick
Thanks in advance
perpetualxda said:
I also have recently experienced a hard brick on an asus tf700t
Click to expand...
Click to collapse
my solution works only for tf701t not tf700t
mr.bin said:
my solution works only for tf701t not tf700t
Click to expand...
Click to collapse
I have a bricked tf701t and good tech skills if you need additional testers. I'm looking forward to the progress of your solution.
jeneral69 said:
I have a bricked tf701t and good tech skills if you need additional testers. I'm looking forward to the progress of your solution.
Click to expand...
Click to collapse
Sent PM with instuctions.
Please keep inform about results.
If your tab "soft" bricked, then that must help...

[Q] ASUS memopad 7 (ME176CX-1E041A) OTG?

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

Hacking MiraScreen5G dongle to become EZCast5G dongle

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.

update ASUS TF701T (k00c) android to latest version

Hi All.
I trust you well. I was wondering if I could request your assistance with updating my TF701T to a new version of android. I have tried many methods and none has worked. I am actually more confused now as to where to start and what to download and install. :silly:
If possible maybe direct me where I could get a step by step guide with the links to the correct downloads/procedure.
I imported the pad from USA to South Africa and barely used it.
Kind Regards
Rob
(h-tee-tee-pee-s) androidbiits.com/root-asus-transformer-pad-tf701t-easily/
probably use the versions of magisk + twrp that are linked at the site, as they are tested with that hardware -- the latest versions may not work. i do not own that particular device and am not a programmer -- just trying to help you out. search the web for info if anything is confusing in the instructions -- i can't really walk you through it, but the person at that site may be able to help you out if you get stuck.
you'll need to connect the asus pad to a computer, so you'll need the usb data cable & adb installed on the computer.
you will likely also need open gapps to get the play store + apps working. select processor type, android version, then variant. you can find it here ==> (h-tee-tee-pee-s) opengapps.org <== but i'm not sure how long that will be functional, as hosting is apparently migrating to sourceforge.
please note that there are no w's in either address mentioned previously.
here's an explanation of gapps ==> (h-tee-tee-pee-s + w's) androidfreeapks.com/apk/download-gapps-for-android/
...and there are also download links for various variations at that last address too. cheers!
you will not be able to install *the latest* version of android (it's just plain not out there as a mod for a device this old) but you *can* get something a bit newer than the stock version on it.
best of luck!
one last thing (pertaining to the very first thing you have to do) is unlock the bootloader.
(h...s + w's) asus.com/us/Tablets/The_New_ASUS_Transformer_PadTF701T/HelpDesk_Download/
you will find the utility to do so at the above site. select Android, then under "Utilities"
click "See All Downloads" - therein, the 2nd thing from the bottom in that section is the unlock tool,
which says: Unlock Device App. V1.o (there's only one thing with that name. size is 448.82 kb)
and it will only work from the stock Android version, which i assume is still functional on your device.
Magisk is apparently a newer replacement for SuperSU, which doesn't flag the system as altered...
therefore you *may not* need to install Gapps if using Magisk - that seems logical to me, but i am not certain.
thanks for the assistance Dorkus.........this is killing me....but I will keep the faith and try again
I am trying myself and cannot get the unlock tool to work, performed wipe data reset without google account and still "network error occurred" . Android version 4.4.2
bobwho said:
I am trying myself and cannot get the unlock tool to work, performed wipe data reset without google account and still "network error occurred" . Android version 4.4.2
Click to expand...
Click to collapse
Same here. I tried to contact Asus but no hope... We're completely blocked unless they do something? No other way to unlock?
greetings all, it is i, dorkus, of the house of mallorcus. haha. my name is actually reni.
xda keeps locking me out for some reason. i've now created 2 accounts (3 including the one from which this comment is posted) one even with a dedicated e-mail address just for this, but if i try to log in with either one, i get some "invalid" whatever message. admins: what have i said that was grossly incorrect? those links may not be presented in absolutely the most coherent way, but they're the best reasonable explanations of the procedure involved that i could find with about an hour or 2 of research, which i did because of intending to get one of these devices myself (which has now occurred! yay). besides that, who else with greater experience has chimed in on this thread? yes, i've reset my password, on both accounts. after i do so, both times: same "invalid" message. it's wasted over an hour of my time, when i'm just trying to help these people. it's highly annoying & if it continues, well, they'll just have to go it on their own.
to the point:
as luck would have it,
i was able to acquire one of these devices, still in superb condition, for a great deal from ebay. i have been in contact with Asus support & the word is: it's an EOL product, so the unlock servers have been shut down & there is currently no recourse end users have for unlocking their devices. i feel it's doubtful that they'll fire up a server again, but maybe we can pester them enough to develop a fastboot unlock tool? it sure would have been nice if it worked like that in the first place, but oh well, like the song says:
you can't always get what you want.
i will surely let you all know if am able to make any progress on unlocking my TF701T.
footnote: i also have a TF700 model which is in fact unlocked, has TWRP installed, and is running Android 5.1.1 {zombie-pop} which works a bit better than the Cyanogen mod flavor that it came to me with: somewhat improved user experience, maybe a little snappier too, but speed improvement is fairly minimal. most importantly, almost all of my apps work on it - a few don't even have an installer for Android 4 at the Play Store. the 701 is noticeably more responsive than the 700 model, even running 4.2.2 - the main issue with it for me is not being able to run all of my apps, some of which are purchased. i'd probably sell the 700 if i could get everything on the 701. oh well. it's an excellent reader + portable video viewing device even at stock. it's definitely worth what i paid in the condition received, but it'd be even better if i could unlock the bootloader & get a newer version of Android on it! i could possibly even be so happy that i'd float a couple bux Tim Duru's way, the guy primarily responsible for porting Android 6+7 (the latter of which apparently does not have a working camera) to this device.
footnote #2: the first day i got the 701, i tried to do a firmware update (proper region, latest available. full battery charge. the battery in the one i picked up is in fantastic condition, the thing is practically brand new + functions nicely... but now Asus won't let me unlock it, even though it's well out of warranty! grrrrr) which crashed mid-way & then it proceeded to get into an update / crash boot loop. i was pretty sad for a while, but did not give up & found a way to restore the original firmware (which turned out to be a very minor upgrade) from the SD card, thanks to information in a post here in the xda forums. that post is the link which follows. my thing would still go into fastboot (albeit slightly corrupted) + recovery mode, which enabled an SD card firmware flash to happen {...and lo, my little slab of Jelly Bean was resurrected...} so i did not require the NvFlash tool at all... but it's still there at the provided links in that thread.
to summarize the procedure:
1) format an SD card to fat32
2) download the appropriate firmware from Asus [**please note the region: if you flash the firmware from a wrong region onto your device, you will -hard- brick it + will then be required to use the NvFlash tool**]
3) un-zip the firmware (not completely, just remove nesting - so you have only one zip file)
4) rename the one remaining zip file: t4_sdupdate.zip
5) put that file on the root directory of SD card, then into the tablet (while turned off)
6) invoke recovery mode (power + vol down) & choose the recover [RCK] box (hit volume up, while it's the selected of the 3 choices) and from there the firmware update happens automatically. you can apparently upgrade to any official firmware by this method, but **cannot** downgrade... so i'd suggest leaving it at 4.2.2 until we are 100% sure that there are zero bootloader unlock options, because apparently the unlock tool, from what i understand, only works from the original 4.2.2
without further ado:
https://forum.xda-developers.com/transformer-tf701/tf701t-nvflash-unbrick-solutiontested-t3742848
it's now a few hours later from my original post, near bedtime for me, and the xda gods let me log into this account to make this edit... and it's even allowing URLs now! will wonders never cease? not sure what the problem was earlier, but it was quite annoying. anyway, if it lets me log into the account with the dedicated xda e-mail address, that's the one i'll use in future. username is renigade.
fly a kite said:
...
Click to expand...
Click to collapse
Hello @fly a kite @dorkus mallorcus @renigade
Please consult the inbox of your private messages. Thanks for your cooperation!
Stay safe and stay healthy!
Regards
Oswald Boelcke

Categories

Resources