Related
As the topictitle says....
http://www.htc.com/member/DownloadAddress.aspx?dl_id=398&type=Drivers
seems a rom update for some device yet to be added... Its posted today and is after the tytn and cruise camera fix.
Will this be the long awaited rom update for us?
cheers
Installation Instructions
Please read the following before starting the upgrade:
Before you proceed, please confirm that this software upgrade is a newer version than what is currently installed on your device. If it is the same version and your device is operating normally, there is no need to reinstall the software.
To check what version is installed on your device, click Start > Settings > Device Information > Version tab, and note the ROM version, CPU, and Radio version.
Please see the image on the right.
Warning!
* This is a generic software update. Any additional software or settings provided by your mobile operator or company will be lost. If you require this customization, please contact your supplier first before upgrading.
* Please note that this upgrade will erase any data stored on the device.
Please back up your data first before upgrading your device. Before you run the ROM Upgrade Utility (RUU), make sure you check and do the following:
* The USB sync cable is connected to your device and PC. If your PC is running Windows XPR, ActiveSyncR will run automatically to establish a connection. If your PC is running Windows VistaTM, then Windows Mobile Device Center will establish the connection between your device and PC.
* All running applications on the device have been closed.
* Make sure that the battery level of the device is least 50% (tap Start > Settings > System tab > Power).
* The update will take up to 30 minutes, DO NOT interrupt the update process, make/receive phone calls, disconnect the device from the PC, or press any buttons until the process has been completed.
Once the RUU is downloaded, launch the application on your PC and follow the instructions.
Please check this box if you wish to download this software
Please Select
Please Select FTP HTC Europe HTC US HTC Asia
Click to expand...
Click to collapse
Doh you have to be some sort of member.
ChumleyEX said:
Doh you have to be some sort of member.
Click to expand...
Click to collapse
ditto, you do.
Can the post starter show us some mroe information?
Does it actually have a download link? I cant see why they would issue a whole rom update for the graphics fix, this is probably just the rom with the camera fix included.
knowing htc
if you can tell us what the image says about versions, I believe I have the most up to date official HTC rom available from late 2007.
flashy said:
ditto, you do.
Can the post starter show us some mroe information?
Does it actually have a download link? I cant see why they would issue a whole rom update for the graphics fix, this is probably just the rom with the camera fix included.
knowing htc
if you can tell us what the image says about versions, I believe I have the most up to date official HTC rom available from late 2007.
Click to expand...
Click to collapse
I've just tried but it appears that there's no download link at present (at least on my PC there isn't) . Just a box that says "Please Select" which normally lists the FTP locations (usually HTC US or HTC Europe) but it doesn't list any locations where the file can be downloaded from.
It also doesn't give any information as to what the file actually is.
Probably my works firewall blocking access - I've had this issue before where I can't download from HTC at work (although I can download from plenty of other sites). I'll try again when I'm home in about an hour.
Edited to add: I've just got home and tried again - still no download locations.
Got the same, 'Please select' box with no entries
Re
Me as well, no download option, but it wasnt there yesterday, and the text is speaking about a rom update....
end of march as promised...? so hopefully they ad a rom behind it soon
I have the same problem with the 'Please select' box...
I just called HTC Europe, but they said there was no new hotfix, and there aren't no phone software updates for the kaiser...
Hopefully, there they will at the locations fast
There's a few things wrong with that page - there's no image with the version number (which the text speaks of) either. It all looks pretty suspect to be honest - like it's just an empty template we were never meant to see.
Besides, the supposed March "fix" was reportedly just a cab file, not a full ROM update.
Checking the source code now;
Found one thing so far, this was commented out ( <!-- don't execute this code --> )
Code:
<!--<tr bgcolor="#ffffff" align="left">
<td align="left" class="plink"><img src="images/gfx/bulletLink_7x11.gif">
<a href='Download.aspx?dl_id=398&loc=us'>HTC US</a></td>
</tr>-->
Edit: TBH it looks like it's just a template
Camera fix
Hi all
I have the same problem (in Italy)!!
...but i downloaded it from here, you don't need the right language file, it will not change the default one!!!
Ciao
@[email protected] said:
Hi all
I have the same problem (in Italy)!!
...but i downloaded it from here, you don't need the right language file, it will not change the default one!!!
Ciao
Click to expand...
Click to collapse
Ehm, this isn't about the Photo Hot Fix
Btw in my opinion this is definitely a template file, but it isn't there to actually store the template. They obviously have some download ready that they will soon put online at that place.
Jasperrr said:
Ehm, this isn't about the Photo Hot Fix
Btw in my opinion this is definitely a template file, but it isn't there to actually store the template. They obviously have some download ready that they will soon put online at that place.
Click to expand...
Click to collapse
.... yes, you are right, sorry!!!
mybad!!!
Maybe they are waiting for the official wm 6.1 release.
Can't log into e-club now,somethining is wrong there, yet I was able to log in this morning and see all available downloads ?????
Mikulec said:
Maybe they are waiting for the official wm 6.1 release.
Click to expand...
Click to collapse
They said a couple of times that they'll be releasing an update before the end of march. And march is ending in 3 days.
shafez said:
Can't log into e-club now,somethining is wrong there, yet I was able to log in this morning and see all available downloads ?????
Click to expand...
Click to collapse
I can login, nothing updated afaik
I have check, but where is no download at all, but i'm purchase it whit Swedish language, so it might take some more days to release.
swiftgs said:
As the topictitle says....
http://www.htc.com/member/DownloadAddress.aspx?dl_id=398&type=Drivers
seems a rom update for some device yet to be added... Its posted today and is after the tytn and cruise camera fix.
Will this be the long awaited rom update for us?
cheers
Click to expand...
Click to collapse
I logged in e-club and found nothing new,but when i clicked on the link you provided it took me to the page you talk about.
which device is the update for as there is no indication for the device anywhere in the page?
Regards
shafez said:
I logged in e-club and found nothing new,but when i clicked on the link you provided it took me to the page you talk about.
which device is the update for as there is no indication for the device anywhere in the page?
Regards
Click to expand...
Click to collapse
I did and saw the same.....
Low_Down said:
I have check, but where is no download at all, but i'm purchase it whit Swedish language, so it might take some more days to release.
Click to expand...
Click to collapse
There's no download because it hasn't been added yet..
shafez said:
I logged in e-club and found nothing new,but when i clicked on the link you provided it took me to the page you talk about.
which device is the update for as there is no indication for the device anywhere in the page?
Regards
Click to expand...
Click to collapse
mchapman007 said:
I did and saw the same.....
Click to expand...
Click to collapse
Again, It's still an empty template
I tried again, and i found out that
http://www.htc.com/member/Download.aspx?dl_id=398&loc=us goes to
http://member.htc.com/downloadfiles/RomCode/HTC S620/
But i can't download anything, and i think is a rom for the S620, not the kaiser
Hi,
I am looking for a tablet for HAM radio / Shortwave listeners purposes.
One thing I need is a working OTG interface for attaching USB devices
to that tablet.
I read different/contradictionary informations about whether OTG works
with this tablet I am not sure, whether the tablets, they were talking about
were exactly the one I am on the way to buy.
So:
Does OTG work on a ASUS memopad 7 (ME176CX-1E041A) w/ Android 4.4 ?
And:
I read that Lollipop will install UEFI and will lock me out then, since there is
no rooting method....true?
Thank you very much for any help in advance!
Best regards,
tuxic
tuxic001 said:
Hi,
I am looking for a tablet for HAM radio / Shortwave listeners purposes.
One thing I need is a working OTG interface for attaching USB devices
to that tablet.
I read different/contradictionary informations about whether OTG works
with this tablet I am not sure, whether the tablets, they were talking about
were exactly the one I am on the way to buy.
So:
Does OTG work on a ASUS memopad 7 (ME176CX-1E041A) w/ Android 4.4 ?
And:
I read that Lollipop will install UEFI and will lock me out then, since there is
no rooting method....true?
Thank you very much for any help in advance!
Best regards,
tuxic
Click to expand...
Click to collapse
The rooting method for lollipop is only less noob-friendly, but for future I recommend you updating to lollipop. For rooting whether kitkat or lollipop (the better but a bit harder way), take a look at this thread: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
And OTG works quite good, even thumb drives work natively without some root using workaround.
Mis012 said:
The rooting method for lollipop is only less noob-friendly, but for future I recommend you updating to lollipop. For rooting whether kitkat or lollipop (the better but a bit harder way), take a look at this thread: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
And OTG works quite good, even thumb drives work natively without some root using workaround.
Click to expand...
Click to collapse
Hi Mis012,
thanks a lot for help me to start with all the things.
I want absolutely sure to understand what I am reading in all that tutorials and postings. Are there any "meta"-tutorials, which explain for example all these acronyms and abbreviations like
adb,odin,cvm,twpr,fastboot and a lot more? I want to learn, but what if I even dont understand the abbreviations of the tutorials and howtos? Lost?
Next:
I took a look at the rooting tutorial you linked (THX!) and didnt find my device in the list of supported devices? Out of luck? Or outdated informations? If outdated, how can I be sure, that
it still works?
(This is NO critism in any way, but I dont want "Just another brick in the wall"...
In this forum (or was it androidsforums? dont remember) I read postings of quite a few people who have created paper weights by upgrading to vanilla lollipop...
What are the benefits in comparision to kitkat to take the risk of an update?
Will lollipop fix the battery drain problem in standby of this nice device?
Can I attach a USBtoEthernet device to the usb port an get a net connection instead of using Wifi?
By the way: My ASUS mempad 7 is on the way to me....
Sorry for the bunch of question ... I am driven by a mix of curiosity and anxity...
Best regards and thank you very much for helping a newbie to get the road to
gain knowledge to help others in turn...
tuxic
tuxic001 said:
Hi Mis012,
thanks a lot for help me to start with all the things.
I want absolutely sure to understand what I am reading in all that tutorials and postings. Are there any "meta"-tutorials, which explain for example all these acronyms and abbreviations like
adb,odin,cvm,twpr,fastboot and a lot more? I want to learn, but what if I even dont understand the abbreviations of the tutorials and howtos? Lost?
Click to expand...
Click to collapse
adb - android debug bridge, gives you shell access to your device from computer and more. Search for Minimal ADB installer.
odin - Samsung flashing tool, has nothing to do with our tablet.
cwm - clockworkmod. custom recovery.
twrp - teamWin project recovery. has more functions, but refuses to work with our device
fastboot - something like adb, you use it for flashing partitions if you have unlocked bootloader
tuxic001 said:
Next:
I took a look at the rooting tutorial you linked (THX!) and didnt find my device in the list of supported devices? Out of luck? Or outdated informations? If outdated, how can I be sure, that
it still works?
(This is NO critism in any way, but I dont want "Just another brick in the wall"...
Click to expand...
Click to collapse
It should be in the supported devices list. It's me176cx. I can say it works.
tuxic001 said:
In this forum (or was it androidsforums? dont remember) I read postings of quite a few people who have created paper weights by upgrading to vanilla lollipop...
Click to expand...
Click to collapse
If you soft brick your device like me, you can just return to kitkat, or better go to store and want a rapair. I returned my to the store two days ago, hope they will give me a chance for lollipop. The update should work without problems on a new device.
tuxic001 said:
What are the benefits in comparision to kitkat to take the risk of an update?
Click to expand...
Click to collapse
First of all, it is lollipop vs kitkat - you can read on internet about why lollipop is better.
The best part - UEFI. with UEFI, you can install any computer OS (Windows, linux) on this tablet.
tuxic001 said:
Will lollipop fix the battery drain problem in standby of this nice device?
Click to expand...
Click to collapse
Maybe. there was some tutorial on xda how to fix it.
tuxic001 said:
Can I attach a USBtoEthernet device to the usb port an get a net connection instead of using Wifi?
Click to expand...
Click to collapse
If the OS will support it. I don't know if android can support this.
tuxic001 said:
By the way: My ASUS mempad 7 is on the way to me....
Sorry for the bunch of question ... I am driven by a mix of curiosity and anxity...
Best regards and thank you very much for helping a newbie to get the road to
gain knowledge to help others in turn...
tuxic
Click to expand...
Click to collapse
No problem.
DO NOT DO ANYTHING SUSPICIOUS WITH THE DEVICE UNTIL YOU GET LOLLIPOP!
Otherwise, you may end up with lollipop update not working > warranty or kitkat forever
And here are some links you should read (It' not that much of text, it only looks like that
https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/ - the autor should thank me, I recommend this article to everone here.
http://forum.xda-developers.com/showthread.php?t=2317790 - minimal ADB and fastboot (you do not need it for Temp CWM recovery, it includes it.
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 - Temp CWM recovery
http://forum.xda-developers.com/memo-pad-7/general/asus-memo-7-me176cx-t2814046 - general thread about this tablet
http://doesn't-exist-yet.sorry/ - I will make a nice step by step guide on how to dual boot lollipop and other OS as soon as I will have my tablet back from service and I will have lollipop so I will have UEFI)
Mis012 said:
adb - android debug bridge, gives you shell access to your device from computer and more. Search for Minimal ADB installer.
odin - Samsung flashing tool, has nothing to do with our tablet.
cwm - clockworkmod. custom recovery.
twrp - teamWin project recovery. has more functions, but refuses to work with our device
fastboot - something like adb, you use it for flashing partitions if you have unlocked bootloader
It should be in the supported devices list. It's me176cx. I can say it works.
If you soft brick your device like me, you can just return to kitkat, or better go to store and want a rapair. I returned my to the store two days ago, hope they will give me a chance for lollipop. The update should work without problems on a new device.
First of all, it is lollipop vs kitkat - you can read on internet about why lollipop is better.
The best part - UEFI. with UEFI, you can install any computer OS (Windows, linux) on this tablet.
Maybe. there was some tutorial on xda how to fix it.
If the OS will support it. I don't know if android can support this.
No problem.
DO NOT DO ANYTHING SUSPICIOUS WITH THE DEVICE UNTIL YOU GET LOLLIPOP!
Otherwise, you may end up with lollipop update not working > warranty or kitkat forever
And here are some links you should read (It' not that much of text, it only looks like that
https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/ - the autor should thank me, I recommend this article to everone here.
http://forum.xda-developers.com/showthread.php?t=2317790 - minimal ADB and fastboot (you do not need it for Temp CWM recovery, it includes it.
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 - Temp CWM recovery
http://forum.xda-developers.com/memo-pad-7/general/asus-memo-7-me176cx-t2814046 - general thread about this tablet
http://doesn't-exist-yet.sorry/ - I will make a nice step by step guide on how to dual boot lollipop and other OS as soon as I will have my tablet back from service and I will have lollipop so I will have UEFI)
Click to expand...
Click to collapse
Hi Mis012,
OH WHOW! This drives my curiosity up and my anxity DOWN! A BIG THANK YOU for your patience with a newbie (I have some experience with Linux and embedded devices (Beaglebone Black, AriettaG25(both ARM) though).
AND: My ASUS ME176CX has arrieved!!! YEAH!
And...strictly following your advice I just started to do the least suspicious with it: CHARGING! hahahaha!
Question (as you might already have expected :
The first thing I want to do is to lollipop my board.
Unfortunately there are two things to consider: I have to setup WLAN for my PC (yes, I am of the "generation copper" / Gentoo LInux. This will be some effort
but no unbeatable problem.
Next is: I am living in a house with LOT OF RF noise. My shortwave receiver sounds like an lawn mower when switched on indoors (that the reason for buying a mobile
PC to go outside and still have all decoders, frequency lists and informations available).
So I do not trust any broadcasted data stream that much...especially when it comes to firmware updates (IIIIIEEEEEKKKKSS!).
Is there any way to update via good ole files from a sdcard/internal flash in a non hackish, plain and secure way?
Earphone:
There neither a users manual nor Tech Specs inside the box.
And if I will insert an earphone into the earphone jack I may burn the output drivers of the audio chip inside,
if this earphone has a too low impedance. Mine has 14 Ohms.
Question:
What is the output impedance of the audio port?
Does it support a mic on the earphone (four contacts)?
Thank you very much in advance again for helping an old child to walk in new shoes!
Hopefully I will get around the hurdles in the beginning and can start to give answers.
Best regards,
tuxic
tuxic001 said:
Hi Mis012,
OH WHOW! This drives my curiosity up and my anxity DOWN! A BIG THANK YOU for your patience with a newbie (I have some experience with Linux and embedded devices (Beaglebone Black, AriettaG25(both ARM) though).
AND: My ASUS ME176CX has arrieved!!! YEAH!
And...strictly following your advice I just started to do the least suspicious with it: CHARGING! hahahaha!
Question (as you might already have expected :
The first thing I want to do is to lollipop my board.
Unfortunately there are two things to consider: I have to setup WLAN for my PC (yes, I am of the "generation copper" / Gentoo LInux. This will be some effort
but no unbeatable problem.
Next is: I am living in a house with LOT OF RF noise. My shortwave receiver sounds like an lawn mower when switched on indoors (that the reason for buying a mobile
PC to go outside and still have all decoders, frequency lists and informations available).
So I do not trust any broadcasted data stream that much...especially when it comes to firmware updates (IIIIIEEEEEKKKKSS!).
Is there any way to update via good ole files from a sdcard/internal flash in a non hackish, plain and secure way?
Earphone:
There neither a users manual nor Tech Specs inside the box.
And if I will insert an earphone into the earphone jack I may burn the output drivers of the audio chip inside,
if this earphone has a too low impedance. Mine has 14 Ohms.
Question:
What is the output impedance of the audio port?
Does it support a mic on the earphone (four contacts)?
Thank you very much in advance again for helping an old child to walk in new shoes!
Hopefully I will get around the hurdles in the beginning and can start to give answers.
Best regards,
tuxic
Click to expand...
Click to collapse
Really don't know anything anout earphones, but I think tablets have some kind of protection, the worst what can happen is you will drain your battery faster, or the sound volume might be lower. Theoreticaly.
About the update: sorry that I didn't mention it, the best what you can do is to download the lollipop firmware from asus support site for this tablet, put it on your sdcard and start it up, then there will be a notification saying somethinhg like "do you wanna update?" You will say that you want and that's it. And you can press thanks if you find my posts helpful, I will feel more like a big boss if I will have more thanks, and it pleases my heart If you need to know anything else, just say You would help us all if you could find someone interested in making cyanogenmod (12.1 would be best) for our device. Just share this link where I write how the locked bootloader can be safely ignored by replacing it with another one: http://forum.xda-developers.com/memo-pad-7/help/me176cxk013-how-cyanogen-mod-t3154917
Mis012 said:
Really don't know anything anout earphones, but I think tablets have some kind of protection, the worst what can happen is you will drain your battery faster, or the sound volume might be lower. Theoreticaly.
About the update: sorry that I didn't mention it, the best what you can do is to download the lollipop firmware from asus support site for this tablet, put it on your sdcard and start it up, then there will be a notification saying somethinhg like "do you wanna update?" You will say that you want and that's it. And you can press thanks if you find my posts helpful, I will feel more like a big boss if I will have more thanks, and it pleases my heart If you need to know anything else, just say You would help us all if you could find someone interested in making cyanogenmod (12.1 would be best) for our device. Just share this link where I write how the locked bootloader can be safely ignored by replacing it with another one: http://forum.xda-developers.com/memo-pad-7/help/me176cxk013-how-cyanogen-mod-t3154917
Click to expand...
Click to collapse
THANKS PRESSED! GREAT! I didn't saw that and it is the first forum I visit, which has this feature!
And downloading an update and THAN flashing it, makes me feel a lot more comfortable...WLAN is only "somehow" here...
Here:
http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+MeMO+Pad+7+(ME176C)
I found 1 firmware item to download:
Version WW_V12.10.1.17 (OS upgradesto Android Lollipop 5.0.1)
Now I am a little confused:
"Download device software and Update SOP (From “Manual” Item)" -- what the [] is a "SOP" ? I cannot find any SOP-Manual (or whatever SOP)
"Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW." ("SKU"? "WW"? "CN"? "TW"? ???? IEEEEKKKS! All this acronyms!!!
"Userfriendly" is definetly something completly different!
I need support for the ASUS support, I think
...Since I found in my ME176CX a software revision number starting with WW and the firmware also start with WW, I think I am ok.
I still dont know, what SKU is and I didnt find any SOP.
Will it be ok to put UL-K013-WW-12.10.1.17_KK-user.zip (unpacked???) onto my SDcard (where? The root dictionary of the card?) ,
put the SDcard into my tablet, and switch the tablet on (when fully charged) and "follow the instructions" ?
Sorry if doubling questions, but I feel better when asking question a second time than buying a tablet a second time...dont like Pink Floyd
at this point of my life...
Best regards,
tuxic
tuxic001 said:
THANKS PRESSED! GREAT! I didn't saw that and it is the first forum I visit, which has this feature!
And downloading an update and THAN flashing it, makes me feel a lot more comfortable...WLAN is only "somehow" here...
Here:
http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+MeMO+Pad+7+(ME176C)
I found 1 firmware item to download:
Version WW_V12.10.1.17 (OS upgradesto Android Lollipop 5.0.1)
Now I am a little confused:
"Download device software and Update SOP (From “Manual” Item)" -- what the [] is a "SOP" ? I cannot find any SOP-Manual (or whatever SOP)
"Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW." ("SKU"? "WW"? "CN"? "TW"? ???? IEEEEKKKS! All this acronyms!!!
"Userfriendly" is definetly something completly different!
I need support for the ASUS support, I think
...Since I found in my ME176CX a software revision number starting with WW and the firmware also start with WW, I think I am ok.
I still dont know, what SKU is and I didnt find any SOP.
Will it be ok to put UL-K013-WW-12.10.1.17_KK-user.zip (unpacked???) onto my SDcard (where? The root dictionary of the card?) ,
put the SDcard into my tablet, and switch the tablet on (when fully charged) and "follow the instructions" ?
Sorry if doubling questions, but I feel better when asking question a second time than buying a tablet a second time...dont like Pink Floyd
at this point of my life...
Best regards,
tuxic
Click to expand...
Click to collapse
I think that the description is some weird user-unfriendly way to describe what I said. Just do what I wrote, there should be no problem. I will stay tuned, crossed fingers for you.
Mis012 said:
I think that the description is some weird user-unfriendly way to describe what I said. Just do what I wrote, there should be no problem. I will stay tuned, crossed fingers for you.
Click to expand...
Click to collapse
I did it and: I GOT LOLLIPOP! YEAH!
I find you guilty for being the source of this success!
Is there a way to check, whether the update is complete, valid in whole working?
Are there critical points to check (certain applications/functions)?
Best regards,
tuxic
tuxic001 said:
I did it and: I GOT LOLLIPOP! YEAH!
I find you guilty for being the source of this success!
Is there a way to check, whether the update is complete, valid in whole working?
Are there critical points to check (certain applications/functions)?
Best regards,
tuxic
Click to expand...
Click to collapse
When you connect keyboard using OTG cable, and press F2 during startup, you should boot into UEFI. Did you encounter any problems with lollipop? Disabling "power saver" option in settings should give you smoother experiance, and solves problem with games playing slow. Anyways, I'm glad I could help. For further info, follow this thread: http://forum.xda-developers.com/memo-pad-7/general/asus-memo-7-me176cx-t2814046/page256
Mis012 said:
When you connect keyboard using OTG cable, and press F2 during startup, you should boot into UEFI. Did you encounter any problems with lollipop? Disabling "power saver" option in settings should give you smoother experiance, and solves problem with games playing slow. Anyways, I'm glad I could help. For further info, follow this thread: http://forum.xda-developers.com/memo-pad-7/general/asus-memo-7-me176cx-t2814046/page256
Click to expand...
Click to collapse
Hmmm....F2 does not work for me...
I also tried the easter egg...but I got a lollipop, but no game...
Furthermore I cannot connect the ME176CX to my computer in a way that the computer recognized it as storage device...
"Software version" say "5.0" and not "5.0.1" or anything higher. The firmware I downloaded was marked as "5.0.1"
Did I really got a FULL and VALID update?
Best regards,
tuxic
tuxic001 said:
Hmmm....F2 does not work for me...
I also tried the easter egg...but I got a lollipop, but no game...
Furthermore I cannot connect the ME176CX to my computer in a way that the computer recognized it as storage device...
"Software version" say "5.0" and not "5.0.1" or anything higher. The firmware I downloaded was marked as "5.0.1"
Did I really got a FULL and VALID update?
Best regards,
tuxic
Click to expand...
Click to collapse
It is 5.0.0 they have mistypen. As for the minigame, touching lollipop will change color, but holding will bring the minigame. Maybe F2 only works with powered hub, didn't try it as my tablet is still in service. Alternatively, you can try this:
1.connect usb keyboard with OTG cable
2.enter stock recovery (while powering on the tablet, hold volume down. In droidboot, select recovery using volume buttons and confirm with power button)
3.on the keyboard press and hold F2
4.select reboot to bootloader
5.on the keyboard press ENTER
steps may vary a bit, this method sounds weird to me but you can try. If it will not work, I will point you at a bit harder method.
Mis012 said:
It is 5.0.0 they have mistypen. As for the minigame, touching lollipop will change color, but holding will bring the minigame. Maybe F2 only works with powered hub, didn't try it as my tablet is still in service. Alternatively, you can try this:
1.connect usb keyboard with OTG cable
2.enter stock recovery (while powering on the tablet, hold volume down. In droidboot, select recovery using volume buttons and confirm with power button)
3.on the keyboard press and hold F2
4.select reboot to bootloader
5.on the keyboard press ENTER
steps may vary a bit, this method sounds weird to me but you can try. If it will not work, I will point you at a bit harder method.
Click to expand...
Click to collapse
Hi Mis012,
Ok, got the Lollipop game (just a test, what works -- just to validate my update).
Entered droidboot as a "exercise" only (for getting used to it).
Found my serial number is 012345678012345678 (or similiar counting up).
Does that mean, that someone sold me a refurbished device as a new one? I read of this
kind of "serial number" appearing on devices, which were sent for repair...
Currently I am download&installing (Gentoo installs a wrapper, which one calls to get the whole
thing installed) android_sdk/android_studio to my Linux PC. Oh damn! THAT'S a huge
thing to download...I started 4 hours before and it still downloads (no, I /am/ generation copper,
but I use DSL ... no modem
While that process slowly but surely will fill up my Linux harddisk I was searching for a
GPS app, which DOES NOT LOG me for others, dont read my contacts, and do other, non
purpose related things AND uses openstreetmap (or better: dont use google services),
is able to do all its functions offline and is GPLed.
I testinstalled three...
All claims suspicious rights of accessing for example the microphone.
I deleted all.
Damn!
I think I have to learn A LOT MORE, before feeling halfway comfortable with this kind
of "new world order"
And as always Mis012...thank you very much for your support and patience!
Best regards,
tuxic
PS: Next I will try F2 again...
tuxic001 said:
Hi Mis012,
Ok, got the Lollipop game (just a test, what works -- just to validate my update).
Entered droidboot as a "exercise" only (for getting used to it).
Found my serial number is 012345678012345678 (or similiar counting up).
Does that mean, that someone sold me a refurbished device as a new one? I read of this
kind of "serial number" appearing on devices, which were sent for repair...
Currently I am download&installing (Gentoo installs a wrapper, which one calls to get the whole
thing installed) android_sdk/android_studio to my Linux PC. Oh damn! THAT'S a huge
thing to download...I started 4 hours before and it still downloads (no, I /am/ generation copper,
but I use DSL ... no modem
While that process slowly but surely will fill up my Linux harddisk I was searching for a
GPS app, which DOES NOT LOG me for others, dont read my contacts, and do other, non
purpose related things AND uses openstreetmap (or better: dont use google services),
is able to do all its functions offline and is GPLed.
I testinstalled three...
All claims suspicious rights of accessing for example the microphone.
I deleted all.
Damn!
I think I have to learn A LOT MORE, before feeling halfway comfortable with this kind
of "new world order"
And as always Mis012...thank you very much for your support and patience!
Best regards,
tuxic
PS: Next I will try F2 again...
Click to expand...
Click to collapse
I hope you do not install sdk only because of adb, because you can get adb separetely and it has less the 10 MB.
About GPS, it looks like this tablet cannot fix location without being cannected to wi-fi.
About the serial number, it really seems weird, but you should be able to change it to something else if you want to.
And it looks there is a new OTA, I recommend not to install it, maybe it will remove UEFI acess or something. Now, it looks like a fix for lollipop problems some people had, but a lot of them have no problems after freezing the power saver app.
Mis012 said:
I hope you do not install sdk only because of adb, because you can get adb separetely and it has less the 10 MB.
About GPS, it looks like this tablet cannot fix location without being cannected to wi-fi.
About the serial number, it really seems weird, but you should be able to change it to something else if you want to.
And it looks there is a new OTA, I recommend not to install it, maybe it will remove UEFI acess or something. Now, it looks like a fix for lollipop problems some people had, but a lot of them have no problems after freezing the power saver app.
Click to expand...
Click to collapse
Hi Mis012,
No, no..(.the SDK is still downloading)...
I install the SDK cause I am curious and may (if TIME and BRAIN allows me) be I can
program something. I am on LINUX here (I mean: my PC is a GENTOO box), so often
tutorials are not that straight forward to read (and helper applications on PC side are
not running here).
GPS is only running when WIFI is connected? Holy CRAP...Google wants to be sure,
that tey are able to track """anonymously"""".
Software "problem"/"feature" which was installed with Lollipop or is it a hardware
restriction? Oh damn...one reason for buying this tablet has gone...
Next update will remove/close UEFI? Will be this the next feature, which I will loose?
But still the nice shiny glass surface will remain...(not without sarcasm... )
IF UEFI will be locked/removed...will we have a chance, to get full control over
this tablet again?
Who is checking for the sanity of this new update?
The droidboot/F2 hack does not work with my keyboard (KBtalking PURE 60).
I could reconnect my IBM model M keyboard of my PC to the tablet, but this
beauty will pull over 100mA through the USBtoPS2 converter....
Better not.
I have an USB hub here...will try that next.
Is there anything I definetly should NOT do, when booted into UEFI?
Will OTAs be available as files later or here or somewhere else?
Do you know of people having such a odd serial number AND have
a proofen new device?
Oh, why oh why one needs to check for everything these days???
Best reagards,
tuxic
tuxic001 said:
GPS is only running when WIFI is connected? Holy CRAP...Google wants to be sure,
that tey are able to track """anonymously"""".
Software "problem"/"feature" which was installed with Lollipop or is it a hardware
restriction? Oh damn...one reason for buying this tablet has gone...
Click to expand...
Click to collapse
It's working fine for me without WiFi, tested it last week. I've heard some people reporting problems with the GPS, can't reproduce them personally.
tuxic001 said:
Next update will remove/close UEFI? Will be this the next feature, which I will loose?
But still the nice shiny glass surface will remain...(not without sarcasm... )
IF UEFI will be locked/removed...will we have a chance, to get full control over
this tablet again?
Who is checking for the sanity of this new update?
Click to expand...
Click to collapse
I installed the update yesterday, it updated something in the BIOS or UEFI or however that it called, not completely sure if they patched that. I don't have an OTG adapter (?, the micro USB to USB adapter) yet (ordered one already) so can't say if they broke that. Will test once it has arrived.
tuxic001 said:
Will OTAs be available as files later or here or somewhere else?
Click to expand...
Click to collapse
You can download the latest OTA update from the link I posted it http://forum.xda-developers.com/showpost.php?p=61926393&postcount=2587 (scroll down a bit, the URL starting with fota.asus.com has the OTA update, can't post the link directly here for some reason) and install it using the temp CWM recovery for example. Not sure if you can also simply copy it to your sdcard, never tried that. Just keep in mind, I don't know what ASUS will do with your UEFI/bootloader with this update, it's generally working fine for me though. If you've disabled power saver in the previous lollipop version there is generally no big reason to update, there were only a few minor changes (I noticed nothing)...
tuxic001 said:
Do you know of people having such a odd serial number AND have
a proofen new device?
Click to expand...
Click to collapse
Just checked, I have the same serial number listed there. I don't know but I don't think it's the real serial number so I wouldn't worry about it. I've installed a few updates already and own the device for about a month already so can't tell for sure, but I'm pretty sure I wondered about this serial number already when I got the device a month ago.
tuxic001 said:
Hi Mis012,
No, no..(.the SDK is still downloading)...
I install the SDK cause I am curious and may (if TIME and BRAIN allows me) be I can
program something. I am on LINUX here (I mean: my PC is a GENTOO box), so often
tutorials are not that straight forward to read (and helper applications on PC side are
not running here).
GPS is only running when WIFI is connected? Holy CRAP...Google wants to be sure,
that tey are able to track """anonymously"""".
Software "problem"/"feature" which was installed with Lollipop or is it a hardware
restriction? Oh damn...one reason for buying this tablet has gone...
Next update will remove/close UEFI? Will be this the next feature, which I will loose?
But still the nice shiny glass surface will remain...(not without sarcasm... )
IF UEFI will be locked/removed...will we have a chance, to get full control over
this tablet again?
Who is checking for the sanity of this new update?
The droidboot/F2 hack does not work with my keyboard (KBtalking PURE 60).
I could reconnect my IBM model M keyboard of my PC to the tablet, but this
beauty will pull over 100mA through the USBtoPS2 converter....
Better not.
I have an USB hub here...will try that next.
Is there anything I definetly should NOT do, when booted into UEFI?
Will OTAs be available as files later or here or somewhere else?
Do you know of people having such a odd serial number AND have
a proofen new device?
Oh, why oh why one needs to check for everything these days???
Best reagards,
tuxic
Click to expand...
Click to collapse
About the UEFI acces removal I said maybe. Mayba not. But who knows these days?
And about the gps, it dit it on kitkat and someone said it does this on lollipop too. I would recommend booting in windows and trying then, if it will not work then it will never. But GPS apps for windows? Noooo, who would mess up with that? The next step would be Android-x86.
As for the UEFI, here comes the noob-unfriendly variant:
0. root the tablet (may not be needed, I haven't tried)
1. download the efibootmgr compiled for android http://forum.xda-developers.com/showpost.php?p=61108700&postcount=2083
2. place the file from inside the zip somewhere
3. using android termianl app, cd in folder with efibootmgr
4. with help of this file http://linux.dell.com/files/efibootmgr/efibootmgr-0.5.4/efibootmgr.txt set next boot to UEFI setup utility. You will most likely need root.
5. Power off the tablet and power it on again
6. You should be in UEFI setup utility. Now you may be able to browse the menus.
7. You will most likely still need a powered usb hub to connect keyboard and do anything.
I hope I will not need a powered usb hub, I do not have one.
Mis012 said:
About the UEFI acces removal I said maybe. Mayba not. But who knows these days?
And about the gps, it dit it on kitkat and someone said it does this on lollipop too. I would recommend booting in windows and trying then, if it will not work then it will never. But GPS apps for windows? Noooo, who would mess up with that? The next step would be Android-x86.
As for the UEFI, here comes the noob-unfriendly variant:
0. root the tablet (may not be needed, I haven't tried)
1. download the efibootmgr compiled for android http://forum.xda-developers.com/showpost.php?p=61108700&postcount=2083
2. place the file from inside the zip somewhere
3. using android termianl app, cd in folder with efibootmgr
4. with help of this file http://linux.dell.com/files/efibootmgr/efibootmgr-0.5.4/efibootmgr.txt set next boot to UEFI setup utility. You will most likely need root.
5. Power off the tablet and power it on again
6. You should be in UEFI setup utility. Now you may be able to browse the menus.
7. You will most likely still need a powered usb hub to connect keyboard and do anything.
I hope I will not need a powered usb hub, I do not have one.
Click to expand...
Click to collapse
Hi Mis012,
UEFI:
Thanks for the deeply-hack-mode-variant!
But I will wait with my experiments until it is clear whether we will still have full access to our beloved ME176CX or not.
Here is a little bit of knowledge, which I can give back:
I had asked on xda-developers whether and how it is possible to mount the tablet as storage device.
Now I found a way to do so on Linux.
You need to install on Linux (this is Gentoo notation...other distros may
have similiar nameings)
dev-lang/go-1.4.2
dev-libs/go-usb-9999
dev-libs/go-fuse-0_p20150422
media-libs/libmtp-1.1.8
On the tablet switch off PTP and switch on MTP.
Connect the device with you Gentoo box and start (as root)
go-mtpfs <mountpunt>
(YES! No device name is required here).
After that the mountpoint contains two directories:
drwxr-xr-x 0 root root 0 1970-01-01 01:00 Internal storage
drwxr-xr-x 0 root root 0 1970-01-01 01:00 SD card
which which is, is obvious.
It is ok, that the command "hangs" ... works as designed.
It stops hanging after the umnount (see below).
Now you can add files into these directories as root.
To umount use (again as root)
umount <mntpoint>
This way there is no need of WiFi transfers or fiddling with this
tiny memory chips.
Best regards,
tuxic
tuxic001 said:
Hi Mis012,
UEFI:
Thanks for the deeply-hack-mode-variant!
But I will wait with my experiments until it is clear whether we will still have full access to our beloved ME176CX or not.
Here is a little bit of knowledge, which I can give back:
I had asked on xda-developers whether and how it is possible to mount the tablet as storage device.
Now I found a way to do so on Linux.
You need to install on Linux (this is Gentoo notation...other distros may
have similiar nameings)
dev-lang/go-1.4.2
dev-libs/go-usb-9999
dev-libs/go-fuse-0_p20150422
media-libs/libmtp-1.1.8
On the tablet switch off PTP and switch on MTP.
Connect the device with you Gentoo box and start (as root)
go-mtpfs <mountpunt>
(YES! No device name is required here).
After that the mountpoint contains two directories:
drwxr-xr-x 0 root root 0 1970-01-01 01:00 Internal storage
drwxr-xr-x 0 root root 0 1970-01-01 01:00 SD card
which which is, is obvious.
It is ok, that the command "hangs" ... works as designed.
It stops hanging after the umnount (see below).
Now you can add files into these directories as root.
To umount use (again as root)
umount <mntpoint>
This way there is no need of WiFi transfers or fiddling with this
tiny memory chips.
Best regards,
tuxic
Click to expand...
Click to collapse
On my Arch Linux system with Gnome/Cinnamon and on Linux Mint/Ubuntu (with a few hacks) it is mounting the device automatically without root or any command, I simply connect it to USB and the device is showing up in the file explorer.
cyandro said:
On my Arch Linux system with Gnome/Cinnamon and on Linux Mint/Ubuntu (with a few hacks) it is mounting the device automatically without root or any command, I simply connect it to USB and the device is showing up in the file explorer.
Click to expand...
Click to collapse
Yes, there are distros out there, which has setup the udev-rules and mtp-mimic already.
Gentoo leaves all that as a task (and exercise) for the user.
Unfortunately I received no reply to my question how to access the ME176CX via usb storage.
So I found it myself...
Now I know, how it works
By the way: Is there any way to disable this [CENSORED] auto completion and word guessing "feature"
of the build-in keyboard. I disabled all suspicous settings under "Language and Input" -- but it
does not help.
"cat /proc/cpuinfo" will instantly be corrected to "cat /proc/Clinton"
which does not work in this case
For programming and system peeking purposes this is a total NO GO!
Help me please with the settings...I am over 30 !
Best regards,
tuxic
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.
proag said:
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.
Click to expand...
Click to collapse
Thank you. I didn't notice the extra zero and didn't think it was unoffical.
Sincerely
John
jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You are on an un-official modefied version.
The fake version is 7.2.4.0.0 <- your version.
The real official and supported by Xiaomi version is 7.2.4.0
Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!
androFRUST said:
Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!
Click to expand...
Click to collapse
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all
TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
Thanks for the reply! Before proceeding, I actually received the SMS to unlock the bootloader but im still at work so I cant go back and attempt the unlock. So just trying to manage my expectations here.
Is it safe to assume that all I need to do now is log in to the unlock tool by miui and unlock? because im still on 7.2.4.0.0 (the unofficial discontinued rom) and I have no way of flashing it to any other roms. My last attempt last night was again, stuck at 52% after a nights worth of wait! TT
---------- Post added at 03:01 AM ---------- Previous post was at 02:49 AM ----------
xtachix said:
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all
Click to expand...
Click to collapse
Thanks for the help. I will attempt this as a last resort. I just received the SMS to unlock my bootloader. Hopefully its as simple as logging in and unlocking so I can get rid of this pesky 7.2.4.0.0 supposed "Global" rom.
i have successfully flashed to global rom!!! but now i have no audio coming from the speakers!!!! is it just my luck!!!??? and after reflashing again.. its completely dead.. its goes into the sign in to miui welcome page and just goes insane.. like to the point where i cant even select options and and random menu sounds keep coming up.. cant even turn off i had to reboot to fastboot.. is a goner? sighs..
7.2.4.0.0 to Resurrection Remix (CM13)
- unlock bootloader
- flash TWRP with fastboot
- install Resurrection Remix
- install GApps
- reboot, now it's say Google play stopped.
- go back to TWRP
- wipe data
- reboot and everything is working
Hi,
I'd love to know if someone has already rooted'n'rommed this phone.
Please let us know! :fingers-crossed:
TT TT said:
Hi,
I'd love to know if someone has already rooted'n'rommed this phone.
Please let us know! :fingers-crossed:
Click to expand...
Click to collapse
Hi, on russian site they have already done it
ttp://4pda.ru/forum/index.php?showtopic=749517&st=560#entry51150598
Add "h" in the beginning (I don't have permission to publish links )
And use google translate
PS. Don't forget to create backup before all manipulations. Especially IMEI
HoboMoe said:
Hi, on russian site they have already done it
ttp://4pda.ru/forum/index.php?showtopic=749517&st=560#entry51150598
Add "h" in the beginning (I don't have permission to publish links )
And use google translate
PS. Don't forget to create backup before all manipulations. Especially IMEI
Click to expand...
Click to collapse
Nice!!
Good reason to practice my Russian :victory:
Thanks a lot, Sir!
altrom also has a rom can be installed via TWRP. Not sure how legit it is though.
TT TT said:
Hi,
I'd love to know if someone has already rooted'n'rommed this phone.
Please let us know! :fingers-crossed:
Click to expand...
Click to collapse
I finally made it to flash TWRP with a flash tool I found via a doogee-blog, a official doogee Q&A site and a blog on doogeemobile.
Why do I have to verify so often?
EDIT: I had a look at my documents, got the flash tool from dogeemobile.com and the TWRP 3.0.2 from needrom. You have to pay attention that you use ROMs for the particular processor of the maxpro (MT6737 M). SU from here of course. :good:
HTH
Why do I have no verification to do any more??
still cant do it
messing around for a week and still no sucess.
flash tool says !sucessful! but i reboot and get stock recovery - not what i expect (twrp)...
also cpu-z says is mt6735- but if i try that one i get :
chip type not match
targetef use value 0xA4020000
but it works with mt6737 - it just dont reboot into that other loader....
any ideas
mlcrip co uk/DooGee/i1.jpg
also tried both x5pro and x5maxpro...
(TWRP-Doogee-X5-MAX-PRO.zip)
(TWRP_Recovery_X5_Pro.rar)
dev enabled, usb debugging, oem unlocking on,
also yes, i do imediately go for bootloader (volume up while turning on)- doesnt work no matter what.
UPDATE:
DooGee X5Max_Pro MT6737M (Android 6.0, 20161123, kernel 3.18.19+)
i sorted it. turns out i had to use x32TWRP (fund it here somewhere on this site)
MT6737M_Android_scatter.txt (plus image come with it)
SuperSU-v2.78-SR3-.zip
also i randomly went for adb commandline to 'unlock rom' not sure if it was necessary, but wont hurt.
so if any noob wanna easy way,
1. 'minimal adb and fast boot' to unlock rom (few cmd commands and you done)
2. start flash tool, set CORRECT scatter file (MT6xxx- if you set wrong model it will give you error popup)
3. set DOWNLOAD ONLY' on drop down box. press DOWNLOAD button.
4.REMOVE BATTERY off your phone. Plug usb cable. youll get 'sucess' pop up window. close the flash tools. disconnect phone but keep it OFF!
5.pop in the battery. press volume up+on button.
at this point you should get some proper user interface, not the black screen with some letters (stock bootloader) something went wrong.
what you should see imediately once you turn it on- just google TWRP images lol.
techbeasts.com/wp-content/uploads/2014/10/TWRP-Recovery.bmp
also all files needed (incl flash tool) i dropped here:
one by one (in case if someone needs scatter file or something)- or inside 'all' folder- all tools compressed into rar
mlcrip.co.uk/android/rooting/files/
Or as bricked as these Qualcomm devices CAN be?
Hey all,
The TL;DR is basically where the list starts
I was running Blu's TWRP v45, the latest PureFusion, Blu's latest Custom kernel, had OB15 firmware underneath. I had been SO USED to simply downloading the newest firmware from kamilmirza's AFH page and just flashing it + it being totally fine that I did it without thinking for OB16. I wasn't too worried because about a week ago I had flashed the unofficial Oreo Lineage and it worked just fine! Plus, I just assumed if it died I could just restore a backup or re-flash the older OB. But as soon as I flashed the new firmware/modem by itself this time on an otherwise perfectly running device, I only saw the OnePlus splash screen. No booting, no access to recovery, no NOTHIN.
I tried flashing the beta TWRP version afterward via fastboot but no dice. Also tried temporary booting via fastboot to it, flashing Blu's again, booting to that. Everything the same result. Splash screen & nothing more. I then went to the extent of trying to format all the partitions and flash a boot.img or do a "-w update" or "flashall" command via fastboot. Because everything out in the universe is a recovery-flashable-zip, it seems like there's no way I can flash the necessary OTA stuff to bring it back to life!
My only remaining idea is getting this damn unbrick tool to work (duhh). I can see the Qualcomm HS-USB QDLoader 9008 in device manager after doing the Vol Up (only) and plugging the cable in. BUT the MSMDownloadTool just cannot see the device. Not in bootloader, not in the weird Vol-Up/cable state. [This is with Qualcomm drivers QUD.WIN.1.1 Installer-10037.3 Setup.exe, the official OnePlus drivers, ADB & Fastboot installed.]
Sorry for long explanation. In the end, what I'm left with is:
Blank formatted partitions (I hope... I'm not even positive they wound up formatted from the fastboot commands)
Fastboot is detected, but no ADB devices are found
Can get to bootloader, but nothing else
No recovery access - Flashing beta akhilnarang Oreo recovery does nothing. Flashing stock recovery does nothing. Flashing Blu_Spark recovery does nothing. (The fastboot commands succeed though each time somehow)
So far the only suggestion I've received is trying the MSMDownloadTool/unbrick process on another computer.
Does anyone have ANY ideas? From my experience, it seems like what might help me would be if a folder with the specific partition images existed for the OTAs, like how Google offers. (boot.img, recovery.img, user-data.img, system and so on). Am I wrong in thinking that? OnePlus has told me this simply does not exist and cannot give me anything like that (don't know why, when they already offer all the OTA flashables...)
PS - OnePlus support just absolutely refuses to even let me communicate to a "level 2" representative to ask a couple of the more technical questions about it. I can't understand why. They are insisting I start an RMA and send it for repair. They even initially scheduled a time for me to talk to higher level rep and then thought up a reason to cancel it via email an hour or so later...
Edit: Just in case the thread gets large and people don't read further posts, this is using:
Windows 10 Pro 64-bit
Test mode for the driver signing is enabled. Have the watermark bottom right of desktop
It's with the stock DASH cable
Tried multiple ports
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times
Tried starting the tool BEFORE the device is plugged in, as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
HOW IT GOT SOLVED:
At the end of the day, I had to fight and convince OnePlus support to grant me a remote session with Level 2 Support.
(Attached final image) These two password protected RAR files had almost identical tools as the Unbrick tutorial on XDA.
The major difference was that MSMDownloadTool was version 3.0.8 ***does anyone have this version??*** I can't get into these RARs. The 3.0 tool circulating did not work for me. We might need the newer version as time goes on?? Otherwise, the process was identical.
Unfortunately, the image they used was for 7.1.1. I had to unlock the bootloader and after doing that and getting OB15 & the RR build I wanted, etc, I then realized my phone was force-encrypted as well.
The only toolkit that worked for force decrypting once everything else worked was:
OnePlus_3_3T_5_64bit_TOOLKIT_by_Neisor
Finally, something like 3 clean flashes later, we Gucci.
Thanks for the attempted help to those that did! Hopefully this can help someone else.
Which Windows do you have? Have you tried MSMtool in safe mode? Or disabling Driver Signature Verification (any Windows after XP). I have got my phone so messed up that it was showing many lines with red "failed" text nearly on everything. No OS, no recovery, no boot, I think even modem was failed. This screen but I had way more fails https://forums.oneplus.net/attachments/win_20160928_21_31_49_pro-jpg.459494/
As long as you can turn your phone off and on, it's doable. But you need to do that USB plugging + volume up thing while phone is totally off (you can hear Windows making bling when you connect it while pressing volume up, but phone itself stays screen off). And there shouldn't be anything on the screen before/while MSMtool do its job.
You can try different USB ports too.
Eremitus said:
Which Windows do you have? Have you tried MSMtool in safe mode? Or disabling Driver Signature Verification (any Windows after XP). I have got my phone so messed up that it was showing many lines with red "failed" text nearly on everything. No OS, no recovery, no boot, I think even modem was failed. This screen but I had way more fails https://forums.oneplus.net/attachments/win_20160928_21_31_49_pro-jpg.459494/
Click to expand...
Click to collapse
Hahaha yes...... That's why I made this post though! It SEEMS like it should be possible to recover from this since fastboot commands + bootloader work! It SEEMED like it would be easy to recover from if anything went wrong... But, here I am.
Oh yeah forgot to mention ~
Windows 10 Pro 64-bit
Test mode for the driver signing is enabled. That part of the process went totally fine with BIOS and installing stuff, etc.
Also, shot in the dark but might @Funk Wizard have any ideas? Sorry to call out for this
Hopefully someone knows better how to solve this. For me the MSMtool part is always the hardest part too, usually it finds the phone, but throws some strange "Sahara communication failed" error. I noticed that even different USB cable can be a problem, but since your Windows finds "Qualcomm HS-USB QDLoader 9008" I guess that's not the case. Does it say something after that "Qualcomm 9008" -thing? For me it shows (COM3 or COM4 depending on which port it's in).
btw, I messed up my phone in nearly similar case, flashing wrong firmware when using leaked H2OS ROM.
Eremitus said:
Hopefully someone knows better how to solve this. For me the MSMtool part is always the hardest part too, usually it finds the phone, but throws some strange "Sahara communication failed" error. I noticed that even different USB cable can be a problem, but since your Windows finds "Qualcomm HS-USB QDLoader 9008" I guess that's not the case. Does it say something after that "Qualcomm 9008" -thing? For me it shows (COM3 or COM4 depending on which port it's in).
Click to expand...
Click to collapse
Yeah sorry again for not being more clear lol
It's with the stock DASH cable
Tried multiple ports (but no USB 2 ports hmm)
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times.
Also tried starting the tool BEFORE device plugged in as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
If I find a solution I'll definitely put it in OP for others
purplepenguin said:
Yeah sorry again for not being more clear lol
It's with the stock DASH cable
Tried multiple ports (but no USB 2 ports hmm)
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times.
Also tried starting the tool BEFORE device plugged in as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
If I find a solution I'll definitely put it in OP for others
Click to expand...
Click to collapse
Hmm, ok.
Stock dash cable works, so that part is ok. Also usb3.0 ports should work too, atleast for me. So everything else seems to be ok except the MSMtool itself
Try different cable, bin there done that!!
purplepenguin said:
Yeah sorry again for not being more clear lol
It's with the stock DASH cable
Tried multiple ports (but no USB 2 ports hmm)
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times.
Also tried starting the tool BEFORE device plugged in as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
If I find a solution I'll definitely put it in OP for others
Click to expand...
Click to collapse
I hope you find a solution, since my experience sounds similar to yours Ill share it and maybe you can find something to help out.
I was exactly where you are for about 3 hours last night.
Boot would always get stuck at the splash screen. Could boot into Fastboot, tried using the Skipsoft tool to fastboot flash a stock image but it kept failing.
As far as the Unbrick Tutorial goes, I know the first thing I kept messing up was thinking I needed to press the power button while holding the volume up and connecting to the PC
Also when I tried to manually update the driver on "Qualcomm 9088" it said it was already up to date.
Then I just ran the MSMTool it flashed 6.0.1 back on my phone and I was back in business.
Im sure this is the guide you followed: Here
I found another on the oneplus forums that is essentially the same but goes into a little more detail in the steps: Here
Since I was back completely Stock including Recovery I went ahead and sideloaded OB16 to get the firmware and modem then went about rooting, unencrypting etc...
Lost a few days worth of files but I'm back running LunuxOS Oreo right now.
Good luck I know how you feel. :good:
I've got it revived! I'll update OP. Sadly, it required OnePlus's intervention.
Hi. Trying to do brute force to get the passowrd here, don't you know how many characters that was? It will take days in my machine to search from 3 to 9 characters...
I think it is impossible to you to know, but if you know if they used only letters or something like that, it would be very useful
guilhermeferrari said:
Hi. Trying to do brute force to get the passowrd here, don't you know how many characters that was? It will take days in my machine to search from 3 to 9 characters...
I think it is impossible to you to know, but if you know if they used only letters or something like that, it would be very useful
Click to expand...
Click to collapse
Sorry man. The OnePlus guy was ready an hour early before our appointment time. So I didn't have time to set up screen recording or anything
if I had to narrow it down more itd only be like 4-9 chars lol I know that's not much help... Definitely let me know if you get it open though please! It would probably help a lot of us!
purplepenguin said:
Sorry man. The OnePlus guy was ready an hour early before our appointment time. So I didn't have time to set up screen recording or anything
if I had to narrow it down more itd only be like 4-9 chars lol I know that's not much help... Definitely let me know if you get it open though please! It would probably help a lot of us!
Click to expand...
Click to collapse
Well, I know the password. It's 10 character long. 7+3(7english small latter with 3 Numbers).
L2 Driver password is very very very very very loooooooong. can't even count accurately.
namefaisal said:
Well, I know the password. It's 10 character long. 7+3(7english small latter with 3 Numbers).
L2 Driver password is very very very very very loooooooong. can't even count accurately.
Click to expand...
Click to collapse
Jeez so wait you got it open or not?? Confused lol
Got the newer download tool ??
Yeah, I got it open
purplepenguin said:
Jeez so wait you got it open or not?? Confused lol
Got the newer download tool ??
Click to expand...
Click to collapse
Yeah it's the new 3.08 msmdownloadtool. OnePlus3T_28_A.57_171012.zip
I know the password and I won't share that but I will upload an UNLOCKED zip on google drive tonight. L2 Drivers too.
New Files without Password
namefaisal said:
Yeah it's the new 3.08 msmdownloadtool. OnePlus3T_28_A.57_171012.zip
I know the password and I won't share that but I will upload an UNLOCKED zip on google drive tonight. L2 Drivers too.
Click to expand...
Click to collapse
Latest 3.08 msmdownloadtool re-archived without password from OnePlus3T_28_A.57_171012.zip
https://drive.google.com/file/d/1kp2SBmhAByydol97o0yVlurVue9Ow8Aq/view?usp=sharing
And the L2+ driver.zip re-archived without password
https://drive.google.com/file/d/1JL_sRg86CczUeZ2cfw8GY6rxc43myif8/view?usp=sharing
@Sam Nakamura
namefaisal said:
Latest 3.08 msmdownloadtool re-archived without password from OnePlus3T_28_A.57_171012.zip
https://drive.google.com/file/d/1kp2SBmhAByydol97o0yVlurVue9Ow8Aq/view?usp=sharing
And the L2+ driver.zip re-archived without password
https://drive.google.com/file/d/1JL_sRg86CczUeZ2cfw8GY6rxc43myif8/view?usp=sharing
Click to expand...
Click to collapse
This totally worked for me. Yes it put me back on 7.1.1 but I have been having issues trying to flash Oxygen ROMS and getting them to take. Phone is back to bone stock which I wanted for now and is working great. Thank you for sharing,
cdorrell12000 said:
This totally worked for me. Yes it put me back on 7.1.1 but I have been having issues trying to flash Oxygen ROMS and getting them to take. Phone is back to bone stock which I wanted for now and is working great. Thank you for sharing,
Click to expand...
Click to collapse
You are most welcome.
Sadly everyone gets unbricked with these files but My device didn't. I have to send the device to the service center now. It seems my case is a hardware issue. Tough luck
namefaisal said:
Latest 3.08 msmdownloadtool re-archived without password from OnePlus3T_28_A.57_171012.zip
https://drive.google.com/file/d/1kp2SBmhAByydol97o0yVlurVue9Ow8Aq/view?usp=sharing
And the L2+ driver.zip re-archived without password
https://drive.google.com/file/d/1JL_sRg86CczUeZ2cfw8GY6rxc43myif8/view?usp=sharing
Click to expand...
Click to collapse
thanks a lot saved my day !!
purplepenguin said:
@Sam Nakamura
Click to expand...
Click to collapse
Sorry, I just saw your mentioning somehow I missed it, happy you got your phone back already, unfortunately not independent for big OP, did you guys already share this new 3.08 MSM-download-tool to the well established threads or did you I missed this too? This information and according files should be shared with the community and easy to find for those poor souls who unintentionally killed their beloved device...
---------
Edit: further sharing isn't necessarily needed, you did already a pretty good job by naming the thread and describing the situation thoroughly, only suggestion could be to link the updated MSM-download-tool download to the first post with some hint, just an idea though...
Cheers
Sent from my OnePlus 3T using XDA Labs