Database Develop

Fastboot success?

Can everyone who unlocked via fastboot method please post the firmware they used here, in 234 I get security error with adb but in fastboot I get option to unlock, trouble is nothing happens when I do. I want to try this with all roms in case a loophole exists somewhere, its the only thing left I can think of, if this doesn't work I'm swapping s3 with GF when she upgrades
Sent from my rooted P880

@non4 said:
Can everyone who unlocked via fastboot method please post the firmware they used here, in 234 I get security error with adb but in fastboot I get option to unlock, trouble is nothing happens when I do. I want to try this with all roms in case a loophole exists somewhere, its the only thing left I can think of, if this doesn't work I'm swapping s3 with GF when she upgrades
Sent from my rooted P880
Click to expand...
Click to collapse
If you want to try with all roms its your problem.
You should know better how bootloader unlock works.
All the roms are out there fore you to try them.
To be honest, I don't know how your "thanks meter" grow so much once that you speculate more than you help or give something wortheful.
Life is made of options that we need to deal with... if your happy good, if you're not, your problem, change device, do whatever you want.
Just don't post like if the world is yours and your option will affect all of us.
This "ship" have doors open. Its up to you to stay or to leave. If you leave, I wish you a happy journey and all the best but, choose!!!
Or you stay and deal with it, or leave and leave us with our "issues".
S3 looks like a good device. Go for it and good luck :good:

I'm a deep thinker, and merely ask some input. I've learned quite a lot about android, but still have a lot more to learn. Would be nice for you to give me some insight into how bl unlock works, heard some stuff about fuse but its vague. I love this phone but this is a must for me. A fair few people report success based on what they flashed. I ask questions to learn, and I ask in the appropriate section, so please don't question my thanks meter, I've been around a while but always had an easy unlock solution, or in case of moto defy a very good bypass. This whole region specific stuff is strange to me, I don't pretend to know everything and that's why I ask questions! Don't hate please I've always thought XDA was very unfriendly to noobs, but the longer I've been here the more I realize even seasoned users get burned! I don't have the time to try every rom out there, I have a job to go to, and besides, what's the point of trying something if someone else has already? That's the point of my question
Sent from my rooted P880

@non4 said:
I'm a deep thinker, and merely ask some input. I've learned quite a lot about android, but still have a lot more to learn. Would be nice for you to give me some insight into how bl unlock works, heard some stuff about fuse but its vague. I love this phone but this is a must for me. A fair few people report success based on what they flashed. I ask questions to learn, and I ask in the appropriate section, so please don't question my thanks meter, I've been around a while but always had an easy unlock solution, or in case of moto defy a very good bypass. This whole region specific stuff is strange to me, I don't pretend to know everything and that's why I ask questions! Don't hate please
Sent from my rooted P880
Click to expand...
Click to collapse
Far from me to hate other user or other user issues.
Things are how they are... Its not easy to deal with nvidia security or LG policies...
You think that if some one had some answer for you (not only) wouldn't give it to?...
I would like to tell you «follow this procedure»... but, I can't!
Take it easy and try to deal with it, or, solve the problem, or wait for a solution... or, change device and you'll be done.

RuedasLocas said:
Far from me to hate other user or other user issues.
Things are how they are... Its not easy to deal with nvidia security or LG policies...
You think that if some one had some answer for you (not only) wouldn't give it to?...
I would like to tell you «follow this procedure»... but, I can't!
Take it easy and try to deal with it, or, solve the problem, or wait for a solution... or, change device and you'll be done.
Click to expand...
Click to collapse
Yes that is true. I'm not expecting an answer to just appear. But people have had success, even 234-000, I've seen the photos. It's possible, there's no doubt in my mind and that is why I try everything I can. Maybe it is just luck but then again I don't think something as precise as a software can be based on luck? All the unlocked users have abandoned the discussions now that cm10.1 is out and it is a little annoying I must admit, so I'm doing everything I can including getting everyone signing that thread I sent to LG (close to 100 btw). I'm sure you aren't hating, just the "that's your problem" and the thanks meter question was a little disrespectful imo. But I know your opinion comes from a good place, I've seen how bad the forum gets spammed and if my post turns out useless I don't care if it's trashed. But like I say, you don't know if you don't try
Sent from my rooted P880

I have an idea that should work but I can't try , it may fully-brick the device .
Any EUR-xxx user can backup his bootloaders (x-loader/u-boot) in an *.img file :-
Code:
su ; dd if=/dev/block/mmcblk0p* of=/mnt/sdcard/x-loader.img
And the same for u-boot .. until know I don't know the partition name but it's easy to know it .
x-loader loads before the u-boot , and check for security & hardware (as I remember) and then the u-boot which will load the kernel ,, after that the kernel loads the modems , RIL , display ...
We can flash the bootloaders by fastboot by :-
Code:
fastboot flash x-loader ***.img
fastboot flash u-boot ***.img
And it can be in a *.bin file type .
But maybe this will full brick the phone which means can't enter download mode . Then we will need a *.blob file to nvflash mode to earse the recovery & kernel partitions to force the phone into fastboot .
#------------------------------------------
echo "Sender.product.model=LG-P880" # (O4X) .
if [ $thanks -eq $pressed ] ; then
thanks_meter=$((${thanks_meter} + 1)) ; fi #Press it

My next attempt (when official JB for UK will be released) is to capture all USB traffic with this:
sourceforge.net/projects/usbsnoop/
Hopefully we could then try to decipher what's the protocol used.
If with the UK version we don't get an unlocked boot loader, I will probably give this phone to my gf and I'll buy a Chinese one, at least they are cheap and I don't need a too powerful phone (I'm not a gamer).
Sent from my Nexus 7 using Tapatalk 2

pierg75 said:
My next attempt (when official JB for UK will be released) is to capture all USB traffic with this:
sourceforge.net/projects/usbsnoop/
Hopefully we could then try to decipher what's the protocol used.
If with the UK version we don't get an unlocked boot loader, I will probably give this phone to my gf and I'll buy a Chinese one, at least they are cheap and I don't need a too powerful phone (I'm not a gamer).
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Good idea, but is it not worth trying that with euro open to save waiting? I have too many shifts with work to try atm or I would, plus I wouldn't know what the output would mean
Sent from my rooted P880

@non4 said:
Good idea, but is it not worth trying that with euro open to save waiting? I have too many shifts with work to try atm or I would, plus I wouldn't know what the output would mean
Click to expand...
Click to collapse
I Guess I could, but in this period I'm quite busy as well (work and courses) so I don't have one day to dedicate to this task.
Hopefully after the next 2 weeks I'll have more time and I could try (but using windows annoys me so much ).

[Q&A] Collection

Disclaimer: I try my best to produce valid answers, but if you have no idea what you're doing, don't do it.
Terms and Definitions
NVflash / APX mode
This is the lowest level of software that can talk to an Nvidia Tegra device. Basically this is the Holy Grail of memory modification, which can even fix a damaged bootloader.
To use it, one boots the tablet with [Vol +] + [Power]. This will lead to the PC detecting an "APX" device. The screen stays blank.
This is no working solution for anything yet, as not only there is no leaked NVflash binary yet, but also the communication is encrypted via an unique 128bit AES key. This key is at no stage accessible, but can be used to encrypt data during boot. This is where the wheelie tool for previous transformers was of help. The Communication itself happens via a protocol called nv3p, which actually is open source, but as long as the key is unreachable, that's not a lot of use. NOTE: I will create an extra post with a lot more details about this.
Fastboot
The Android Bootloader.
This is the essential part of software which loads Android/a Recovery image/rooting ramfs/etc.
This is the most delicate part in the Android boot process, as fastboot is the lowest level of communication we have so far. In other words: The only way to fix a damaged bootloader would be NVflash, which is not yet available for this device.
Generally the Bootloader is locked as a method to prevent unauthorized access to data stored on the device. A locked Bootloader means no Fastboot.
Bootloader unlocking
To gain access to fastboot devices, the Bootloader needs to be unlocked. This can be as simple as installing an APK provided by the manufacturer or running "fastboot unlock".
Unlocking the Bootloader always leads to three resulting actions: Fastboot now works, all data on the device is wiped, the device's warranty is now void.
Unlocking the bootloader via unlock app can require you to have internet access and a valid google account. This can be problematic in the case of one-time-passwords, as the normal password will possibly not work (and you'll wonder why the heck it doesn't run).
Bootloader locking
This is (at least currently) not possible. Warranty void remains permanent.
RamFS
Simple file system in a file, which gets loaded into RAM. We use this for rooting.
Boot image
A file generally called "boot.img". This contains the kernel.
Recovery image
A partition image that contains a bootable linux kernel and file system, which server the purpose of creating and restoring nandroid backups and perform related tasks.
Brick - general
A device with messed up software, not being able to boot let alone perform any higher task other than being a brick.
Soft brick
A device not booting, which still responds to fastboot queries.
Hard brick / Brick
Fastboot doesn't work anymore. Maybe a visible boot loop, maybe nothing. The only point in which this differs from scrap is the ability to get into APX mode.
Chances are, there will be a way to use NVflash to fix this sometime.
Unbrick
Fixing a bricked device. Currently only soft bricked devices can be unbricked.
Root
General term for having super user abilities on a linux powered device. This can be used for reading/writing/executing restricted files, modifying things, loading custom ROMs etc.
Also having Root can mean "running with scissors", as there's not much left to prevent you from deleting important files and bricking your device.
Remember: Having Root is a very useful device, but with power comes responsibility. Also there is Android malware, which specifically targets rooted devices.
Rooting
The process of gaining Root. In early methods this generally starts with unlocking the device's Bootloader, then booting a Kernel with a purposely prepared ramfs to install and modify certain files.
As always, unlocking the Bootloader means all data will be wiped. By chance at some point someone will figure out a way to do this without unlocking.
ROM
A stock or custom Android ROM image. This contains everything needed for a running system. Custom ROMs contain tweaks, themes, improvements, styles, preloaded apps etc. Also more often than not, a load of bloat ware will be removed.
Bloat ware
Apps nobody needs/many fail to understand what they actually do/bring new ways to crash your device/sniff your precious data/revive long fixed and forgotten security leaks/the manufacturer adds to promote sales ("hey look, we've got an app for that pre installed").
Most importantly, cannot be removed from your device without Root.
Stock
A mint Android ROM, just like what the device gets shipped with.
Guides
Rooting
Requirements: Currently none
Compatible versions: anything > 10.14.1.47
Method: Booting custom Kernel and ramfs
Status: Proven
Link: http://forum.xda-developers.com/showthread.php?t=2516215
Recovery
Creator: Drgravy
Version: 6.0.3.7
Status: Abandoned but functional
Requirements: Bootloader <= 10.14.1.47 (this will not work with 10.26.1.7. Trying to do so will not work, but still boot Android as usual.)
Link: http://forum.xda-developers.com/showthread.php?t=2524401
Recovery
Creator: lpdunwell
Version: 6.0.4.5
Status: Experimental, WIP
Requirements: Bootloader >= 10.26.1.7
Link: http://forum.xda-developers.com/showthread.php?t=2556944
Various information
Hardware assembly date
On the box, rear side label.
Partition information / Unbricking
Link: http://forum.xda-developers.com/showthread.php?t=2546941
Keyboard key remapping
The physical keyboard has custom keys, with functions of debatable value. Here's how to remap them to suit your needs.
Note: This also works for other ASUS Transformers.
Warning: Backup any file you attempt to edit!
Method: The keyboard mapping is described in /system/usr/keylayout/asuspec.kl. The structure is pretty straight forward.
After saving the file, reboot the device.
Code:
Key: Function: Key number: Text:
lock Delete 142 "key 142 FORWARD_DEL WAKE UNLOCK"
search ALT 217 "key 217 ALT_LEFT WAKE UNLOCK"
HDMI configuration
The HDMI resolution can be adjusted. This can be handy under certain circumstances, although results may vary.
Method: Via terminal; disable frame buffer 1, change resolution, enable frame buffer 1
Info: To get a list of valid settings, run "cat /sys/class/graphics/fb0/modes".
This will reset at reboot.
This example enforces 1920x1200 @ 59Hz, in my case to force a HP Compaq monitor to keep running (without this it'll go to sleep for whatever reason).
Code:
echo 0 > /sys/class/graphics/fb1/device/enable
echo "D:1920x1200p-59" > /sys/class/graphics/fb1/mode
echo 1 > /sys/class/graphics/fb1/device/enable
Teardown
Teardown with two images and a brief description of the process: http://forum.xda-developers.com/showthread.php?t=2564143
Q&A
Q: "I have never rooted anything before. Can you send me some fairy dust to fix my bricked tablet if anything goes wrong?"
A: No. And if you are not absolutely sure of what you're doing, there's a fair chance you'll mess it up. Been there, done that.
Q: "What are known causes of bricked TF701?"
A:
Failed upgrade
Flashing incompatible boot.img and blob
Flashing something other than blob to staging
Removal of important files after rooting
Q: "I had a quick look at your instructions for xxx and I don't understand..."
A: Tough luck.
Q: "I re-read your instructions for xxx, searched the forum and I still cannot understand..."
A: Check if there's a matching thread. If there isn't create one with a diagnostically conclusive title. Use as much detail as possible.
Final notes
I hope this helps. As always, updates will follow.
Want to see your tutorial/guide/etc. here? Send me a detailed PM with the subject "TF701 Q&A extension".
You can help making this even better!
Found a mistake or believe I'm wrong about something? Let's discuss it.
Has this helped you? Consider clicking thanks.

THANK YOU for the hack to get a forward delete on the keyboard! That has been bugging me for a year!
Works just the same on the TF700 keyboard, btw.

Ask the mod to make it sticky, then it will always be at the top of the main thread.
Sent from my superfast Asus Infinity TF701with Dock

Snah001 said:
Ask the mod to make it sticky, then it will always be at the top of the main thread.
Sent from my superfast Asus Infinity TF701with Dock
Click to expand...
Click to collapse
he is retired .... Doesnt reply to any request ...

berndblb said:
THANK YOU for the hack to get a forward delete on the keyboard! That has been bugging me for a year!
Works just the same on the TF700 keyboard, btw.
Click to expand...
Click to collapse
yeah, the keymapping crap...
I found tons of "unpack this apk, edit soandso..." but I wanted to have it changed on a lower level. the remapping should work on most if not all transformers, and be easily portable to anything that has a hardware keyboard...

Rikodu said:
he is retired .... Doesnt reply to any request ...
Click to expand...
Click to collapse
Huh? Wut?????
Considering this is the first "Q & A" post, I will sticky it.
Provided the OP updates and maintains it.
MD

I'm pretty sure the resolution hack can be improved, but it's all I needed for now...
anybody write an app for that?

Moscow Desire said:
Huh? Wut?????
Considering this is the first "Q & A" post, I will sticky it.
Provided the OP updates and maintains it.
MD
Click to expand...
Click to collapse
go for it, it's sinking...
cheers

lpdunwell said:
go for it, it's sinking...
cheers
Click to expand...
Click to collapse
Seeing if you were paying attention..... :good:

lol

Maybe you could explain where to see the build date.
As far as I know its in the serial number after the characters. But in my case (and maybe others) I can´t see a date in 160074 .

done

hard bricked tf701t
Dear lpdunwell,
I have a bricked tf701, only asus logo available and loopboot, fastboot menu is broken as well. Only APX mode working, but I could not find appropriate nvflash for my pad (s I see there is no nvflash currently available for my tab)
In your explanation about bricked device, you wrote that there is possibility to recover tf701?
Please describe what nvflash version should I use to succeed?
Thanks in advance,
stream1313

stream1313 said:
Dear lpdunwell,
I have a bricked tf701, only asus logo available and loopboot, fastboot menu is broken as well. Only APX mode working, but I could not find appropriate nvflash for my pad (s I see there is no nvflash currently available for my tab)
In your explanation about bricked device, you wrote that there is possibility to recover tf701?
Please describe what nvflash version should I use to succeed?
Thanks in advance,
stream1313
Click to expand...
Click to collapse
Sorry mate we don't have nvflash and it is too late for you now anyway If you only have access to APX you are hard bricked. Best to sell it for parts and move on.... Or if you want to revive it send it to Asus to fix at a cost or source a replacement mainboard and do it yourself.

sbdags said:
Sorry mate we don't have nvflash and it is too late for you now anyway If you only have access to APX you are hard bricked. Best to sell it for parts and move on.... Or if you want to revive it send it to Asus to fix at a cost or source a replacement mainboard and do it yourself.
Click to expand...
Click to collapse
Hi man.. Why do you think I have to forget about my toy.. It was my Christmas (New Year in Tbilisi, Georgia, opposite planet side) present to myself But it is all the lyric only
Pls explain - do you really think that for ex., several weeks / months later, smb will create the nvflash or any similar SW which will be able to fix my problem? Actually I believe that until all electronic components are ok, device is not "dead" forever... Why you so pessimistic exactly for 701 transformer tab? Pls if you have time reply me
Kind regards,
Stan

stream1313 said:
Hi man.. Why do you think I have to forget about my toy.. It was my Christmas (New Year in Tbilisi, Georgia, opposite planet side) present to myself But it is all the lyric only
Pls explain - do you really think that for ex., several weeks / months later, smb will create the nvflash or any similar SW which will be able to fix my problem? Actually I believe that until all electronic components are ok, device is not "dead" forever... Why you so pessimistic exactly for 701 transformer tab? Pls if you have time reply me
Kind regards,
Stan
Click to expand...
Click to collapse
the way nv flash works is you need to flash the special bootloader to extract your device blobs and device specific keys. As you haven't been able to do it and you CANNOT do it once you have bricked you will have no chance. How are you going to flash a bootloader that you need fastboot for?
Sorry to bring bad news but if you only have APX with no saved nv flash files (which is not yet avail for our device) then you currently have 0% chance of recovering.

sbdags said:
the way nv flash works is you need to flash the special bootloader to extract your device blobs and device specific keys. As you haven't been able to do it and you CANNOT do it once you have bricked you will have no chance. How are you going to flash a bootloader that you need fastboot for?
Sorry to bring bad news but if you only have APX with no saved nv flash files (which is not yet avail for or device) then you currently have 0% chance of recovering.
Click to expand...
Click to collapse
Thanks a lot for reply (as well as for my another, initial thread reply) I have only CWM backup of my tab, on the MD card. But I do not know, does this backup contain all needed stuff? At list, I did not found there saved nv flash or blob files. Just "blobgenerator" (462Kb) and "blobtester" (370Kb), also some system files with "nv" in the name. But I do not have Idea, does CWM saving the low level loader files, at list I was not able to recognize them there...
my apologize for too many questions as well as for my poor English - it is not my native lang
Kind regards,
Stan

stream1313 said:
Thanks a lot for reply (as well as for my another, initial thread reply) I have only CWM backup of my tab, on the MD card. But I do not know, does this backup contain all needed stuff? At list, I did not found there saved nv flash or blob files. Just "blobgenerator" (462Kb) and "blobtester" (370Kb), also some system files with "nv" in the name. But I do not have Idea, does CWM saving the low level loader files, at list I was not able to recognize them there...
my apologize for too many questions as well as for my poor English - it is not my native lang
Kind regards,
Stan
Click to expand...
Click to collapse
No having CWM backups saved won't help you as you have no way of getting to the bootloader which would then be used to open the recovery so you could restore. WIthout a working bootloader you can't proceed. NV Flash uses APX mode to restore the blobs via the wheelie binary. You haven't captured the blobs to restore and as they are encrypted to your device you can't use anyone elses.
It's a new main board or nothing I'm afraid.

sbdags said:
No having CWM backups saved won't help you as you have no way of getting to the bootloader which would then be used to open the recovery so you could restore. WIthout a working bootloader you can't proceed. NV Flash uses APX mode to restore the blobs via the wheelie binary. You haven't captured the blobs to restore and as they are encrypted to your device you can't use anyone elses.
It's a new main board or nothing I'm afraid.
Click to expand...
Click to collapse
I see, everything is clear. Thanks for your time man. But I beleive that Asus has some kind of "backdoor" for such cases, for internal usage, of course. Asus manifest about "mainboard replacement" probably just for business, normally must be some way to crack this protection. I hope somebody from Asus will share some useful info or even software for public usage... Maybe it's my dreams only, I'm realistic (I'm working as IT/IS/GSM/WCDMA, but I'm so far from programming..)
Again, thank you. Pls notify me in case of any news about K00C hack

Problems flashing CWM recovery
stream1313 said:
I see, everything is clear. Thanks for your time man. But I beleive that Asus has some kind of "backdoor" for such cases, for internal usage, of course. Asus manifest about "mainboard replacement" probably just for business, normally must be some way to crack this protection. I hope somebody from Asus will share some useful info or even software for public usage... Maybe it's my dreams only, I'm realistic (I'm working as IT/IS/GSM/WCDMA, but I'm so far from programming..)
Again, thank you. Pls notify me in case of any news about K00C hack
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------
Sorry I am not yet familiar with how to ask questions.
I recently bought a TF701T having used a TF700T now for two years and before that the TF101, TF201 and TF300T.
All these tabs I installed a recovery: CWM or TWRP and flashed the best ROM I could find. Usually Cyanomod or CROMi-X.
Everything worked fine so I was very excited when I got hold of the TF701T with its incredible Q-ratings and smoothness.
Unlocking worked just fine but installing CWM just does not work: flashing with Fastboot works OK but when I boot into recovery the little green man falls down and stays there
FYI: I am on the latest BL: 10.26.1.28, so newer than the mentioned 10.26.1.18 !
Please could anyone respond ?
Regards, JOTX10 from the Netherlands.

Any other way to root this device on 4.3 without unlocking it?

Seems like that I would never make it to unlock it.:crying:

super0dd said:
Seems like that I would never make it to unlock it.:crying:
Click to expand...
Click to collapse
No not right now.
Remind me where you are getting stuck?
The tricky part is updating to 4.3 if you are on 4.2.2 and then you unlock, but if you are locked on 4.2.2 then just upgrade to 4.3 and then unlock, fastboot flash cwm and use my superuser zip to root. Easy!

sbdags said:
No not right now.
Remind me where you are getting stuck?
The tricky part is updating to 4.3 if you are on 4.2.2 and then you unlock, but if you are locked on 4.2.2 then just upgrade to 4.3 and then unlock, fastboot flash cwm and use my superuser zip to root. Easy!
Click to expand...
Click to collapse
All right, just let me tell you my whole story.
Someday I seemed to overcharge my tablet and thus broke the power management chip on the motherboard and then I found it stuck on the boot screen and was only able to boot to recovery. After I finally surrendered to it, I went to have Asus's guy replaced it a new motherboard, which took me like 230 bucks(much close to a new nexus 7).When I got my tablet back, it was already on 4.3 (10.26.1.18 CN), then I found it incapable to be unlocked. But I still want to root it anyway since the stock Chinese firmware is not even with GApps and lacks a lot of features that others possess. At least, I need Play Store!
Problem1: I am not sure if Asus's server records the existence or S/N of the current motherboard, which is most likely to incapacitate the unlock process.
Problem 2:
Code:
Unknown error occured, which may a network error
Please try later
That's the problem I meet all the time. I don't know if the official unlock tool is available for 4.3(the official webpage says that it is for 4.2.2 only and I can't find any other similar unlock tool for even ME302c:crying, as the firmware version is already 4.3 when I got it and it doesn't seem to be feasible fo downgrade it.
Problem 3: I have tried every root tools I know, and failed. Not possible to use the masterkey…
Thank you anyway.:victory:

super0dd said:
All right, just let me tell you my whole story.
Someday I seemed to overcharge my tablet and thus broke the power management chip on the motherboard and then I found it stuck on the boot screen and was only able to boot to recovery. After I finally surrendered to it, I went to have Asus's guy replaced it a new motherboard, which took me like 230 bucks(much close to a new nexus 7).When I got my tablet back, it was already on 4.3 (10.26.1.18 CN), then I found it incapable to be unlocked. But I still want to root it anyway since the stock Chinese firmware is not even with GApps and lacks a lot of features that others possess. At least, I need Play Store!
Problem1: I am not sure if Asus's server records the existence or S/N of the current motherboard, which is most likely to incapacitate the unlock process.
Problem 2:
Code:
Unknown error occured, which may a network error
Please try later
That's the problem I meet all the time. I don't know if the official unlock tool is available for 4.3(the official webpage says that it is for 4.2.2 only and I can't find any other similar unlock tool for even ME302c:crying, as the firmware version is already 4.3 when I got it and it doesn't seem to be feasible fo downgrade it.
Problem 3: I have tried every root tools I know, and failed. Not possible to use the masterkey…
Thank you anyway.:victory:
Click to expand...
Click to collapse
Ah OK - the issue is Asus have replaced your motherboard so the mac address you are now supplying does not match the serial number of the device that they have in their database.
The ONLY way to proceed is to contact asus and get them to update their database with your new mac address - stating that you can't use their online web services like device tracking etc until they do so. They will eventually do it but if you can hold of a rep in Taiwan that will speed things up.
There is no other way.

sbdags said:
Ah OK - the issue is Asus have replaced your motherboard so the mac address you are now supplying does not match the serial number of the device that they have in their database.
The ONLY way to proceed is to contact asus and get them to update their database with your new mac address - stating that you can't use their online web services like device tracking etc until they do so. They will eventually do it but if you can hold of a rep in Taiwan that will speed things up.
There is no other way.
Click to expand...
Click to collapse
Uh, do Asus guys have my MAC address? I am not sure.
Okay, I'll phone them tomorrow. It's quite a warm Sunday night now in China.
Thanks a lot.

super0dd said:
Uh, do Asus guys have my MAC address? I am not sure.
Okay, I'll phone them tomorrow. It's quite a warm Sunday night now in China.
Thanks a lot.
Click to expand...
Click to collapse
Of course they do - it is tied to your wifi hardware.

[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

Android on Alcatel Idol 4S Windows edition

Hi everyone!
I was wondering if it's possible to flash android on the Alcatel Idol 4s Windows edition. The reason why i am asking is because i noticed that the TCL 950 (android smartphone) shares exactly the same SOC and specs with the Alcatel Idol 4s and it is actually made by the exact same company (TCL). It is basically the exact same phone, with a different brand on it and a different OS.
So i was wondering, would it be possible to flash the TCL 950 firmware on the Idol 4S windows in order to install Android on it? If yes, did any of you guys had the chance to find the firmware for the TCL 950? Cause i searched for it but didn't have any luck...
Thank you so much in advance!
I saw also that @compu829 commented a while back on the argument

steinwayer said:
Hi everyone!
I was wondering if it's possible to flash android on the Alcatel Idol 4s Windows edition. The reason why i am asking is because i noticed that the TCL 950 (android smartphone) shares exactly the same SOC and specs with the Alcatel Idol 4s and it is actually made by the exact same company (TCL). It is basically the exact same phone, with a different brand on it and a different OS.
So i was wondering, would it be possible to flash the TCL 950 firmware on the Idol 4S windows in order to install Android on it? If yes, did any of you guys had the chance to find the firmware for the TCL 950? Cause i searched for it but didn't have any luck...
Thank you so much in advance!
I saw also that @compu829 commented a while back on the argument
Click to expand...
Click to collapse
I still haven't found the firmware myself. As long as it was signed with the same certificate and windows phone, it should be possible.

compu829 said:
I still haven't found the firmware myself. As long as it was signed with the same certificate and windows phone, it should be possible.
Click to expand...
Click to collapse
After doing some heavy research i managed to find it!! Here it is, the TCL 950 firmware
http://pan.baidu.com/s/1geDBRnt
It is the official firmware directly from TCL i managed to talk with their assistance in China
@compu829 how can i flash this firmware now on my idol 4s??
Thank you so much in advance

@steinwayer I will need to download and extract it. I'll take a look later today.

Thanks @compu829
Did you find anything interesting ?

I'm interested in the possibilities here too. Thanks for your research and sharing it!

steinwayer said:
Thanks @compu829
Did you find anything interesting ?
Click to expand...
Click to collapse
I can't download it. Can you? If so can you put it somewhere like mega.co.nz?
I was able to download the package and re-upload it to mega with some help from my friends. Here is the link: https://mega.nz/#!ITJhjYIS!R_iUZhGZMcslAK_u1wdsJ-7q-0D5ma_KrHl4pu2CPqo
I took a quick look, and it is pretty much all mbn files that the factory would flash during assembly, so you will (most likely) need a copy of QPST. We may also be able to use WDRT to flash it. In either case, flashing will fail miserably if the certificates don't match.

So how would you suggest to do this @compu829?

steinwayer said:
So how would you suggest to do this @compu829?
Click to expand...
Click to collapse
compu829 said:
... In either case, flashing will fail miserably if the certificates don't match.
Click to expand...
Click to collapse
^^^ You probably won't be able to easily. At this point, no one here knows, but as @compu829 stated, if the certificates don't match (which they most likely don't), then you're not going to be flashing it at this point.

Would it not be possible to "force" the flashing of that image? Afer all the devices are exactly the same from an hardware perspective..

steinwayer said:
Would it not be possible to "force" the flashing of that image? Afer all the devices are exactly the same from an hardware perspective..
Click to expand...
Click to collapse
Same hardware != same implementation. There's mechanisms that will only allow certain things to be flashed, while all protections are still enabled on the device. Since it's a newer phone, I imagine qualcomm's security mechanisms are stepped up as opposed to how they are on older SoC implementations.
If anything, it will NOT be an easy feat to accomplish, so I will say no to a way of "forcing" it to flash at the moment.

It makes perfect sense
What i was thinking tho is that probably the two devices have even a different bootloader. Meaning that it would be a total wipe of the entire disk including swap partition and try to flash that rom.
I was thinking: imagine a bricked device, sometimes is possible to wipe out completely the memory on it and just flash the right rom. Sadly i do not habe much experience in mobile devices.. been developing only for desktops for years.
But if you guys manage to accomplish that it would be great.
The alcatel idol 4s is a great phone for both specs and design and is currently EXTREMELY cheap to. Buy on ebay (you can even find it at 100 bucks) mainly because of its OS
Being able to turn it into an Android phone would be an amazing feat

snickler said:
Same hardware != same implementation. There's mechanisms that will only allow certain things to be flashed, while all protections are still enabled on the device. Since it's a newer phone, I imagine qualcomm's security mechanisms are stepped up as opposed to how they are on older SoC implementations.
If anything, it will NOT be an easy feat to accomplish, so I will say no to a way of "forcing" it to flash at the moment.
Click to expand...
Click to collapse
Also, a very important factor is that the phones are made by the same shenzhen manufacturer most likely in the same plant. The only thingthey really change is the logo on the back, which comes later on, and the OS.from aanufacturing perspective it would not make much sense to lock with certificates the devices,slowing quite a bit he manufacturing process.it would have sense if the two devices were to be released in the same country, but in this case, tcl 950 is just available in asia, where idol 4s isnot. How can we verify this certificate thing @compu829 ? We have an Idol 4s

hello @snickler do you think that doing this: https://www.youtube.com/watch?v=Iwkx5CFRFKo
would give me a chance of success?
Also, in case of failure for differente certificates, do you think the process would not even start or would it start and brick my device?
Thanks

Update: I am trying to let QFIL to see my device.
First i put my device in flash mode by shutting it down and then immediately pressing and holding the volume up key. It goes in flash mode. I launch QFIL , connect the phone over the USB port, but the tool does not see my device.. i tried installing several qualcomm usb drivers, but till now no luck.
You guys have any suggestions??
@snickler @compu829 ?
Thanks in advance

It won't work. This is for phones stuck in QDLoader 9008 mode (DEAD MODE) and DLOAD mode. The Sahara protocol only accepts signed programmers that are stored in the UEFI. You also need the exact flashers for the particular phone for it to work as it's specific to the phone's bootloader (which is definitely signed)

snickler said:
It won't work. This is for phones stuck in QDLoader 9008 mode (DEAD MODE) and DLOAD mode. The Sahara protocol only accepts signed programmers that are stored in the UEFI. You also need the exact flashers for the particular phone for it to work as it's specific to the phone's bootloader (which is definitely signed)
Click to expand...
Click to collapse
Which method would you suggest me to try??

steinwayer said:
Update: I am trying to let QFIL to see my device.
First i put my device in flash mode by shutting it down and then immediately pressing and holding the volume up key. It goes in flash mode. I launch QFIL , connect the phone over the USB port, but the tool does not see my device.. i tried installing several qualcomm usb drivers, but till now no luck.
You guys have any suggestions??
@snickler @compu829 ?
Thanks in advance
Click to expand...
Click to collapse
I don't know what QFIL is, but vol up and power will put the windows phone in a flash mode that is compatible with WDRT. This mode is completely different than the Qualcomm mode. You most likely need to intentionally brick your device to enable Qualcomm recovery mode.

steinwayer said:
Which method would you suggest me to try??
Click to expand...
Click to collapse
No method. It's probably not best to randomly try things without understanding the underlying mechanisms and the implications of what could happen in the end.
Honestly, IMO, if you want Android then buy an Android phone. I understand that it would be cool to be able to swap out, but the likelihood of this happening right now is close to zero.

snickler said:
No method. It's probably not best to randomly try things without understanding the underlying mechanisms and the implications of what could happen in the end.
Honestly, IMO, if you want Android then buy an Android phone. I understand that it would be cool to be able to swap out, but the likelihood of this happening right now is close to zero.
Click to expand...
Click to collapse
If only i could put my hands on the software they use at tcl to flash their devices...
This is oje of the reasons why smartphones are still way behind computers. Not much freedom of choice and yet theorically it would be more than possible to allow a certain level of freedom on it