Related
Hi guys, I am having an issue i cant seem to resolve on my razr i. apologies if this has already been covered in another thread (or 10, which is usually the way with these things because nobody reads the other threads) I have been through a load of other threads but cannot seem to resolve my issue so i started my own.
Right, I have switched from iphone to razr and am not stupid when it comes to jailbreaking etc so thought rooting the razr wouldnt be a problem. when trying to root it it failed and i am stuck at the fastboot menu, however, everything on the menu is disabled so i cant use it. i get the usual message:
fastboot reason: flash failure
fastboot max download size: 100mb
usb connected
if i try to use anything on the menu i get the following message:
fastboot menu disabled.
my phone is not unlocked and not rooted. i have barely done anything to it other than install a couple of free apps. i am unable to progress past this screen. the phone is GB and is on 4.0.4
any help you guys can give would be greatly appreciated. again, apologies if this has already been covered, none of the solutions i found were able to resolve my issue. as i said, i had no problems jailbreaking my old iphone, i am a bit of a n00b when it comes to droids...
AW: [Q] razr i problems - fastboot menu
Are you able to run fastboot commands ? Cause in that case you might be able To unlock bootloader and reflash the software .
Sent from my XT890 using xda premium
xX_Alex_Xx said:
Are you able to run fastboot commands ? Cause in that case you might be able To unlock bootloader and reflash the software .
Sent from my XT890 using xda premium
Click to expand...
Click to collapse
I am not able to do anything. if i scroll to any of the options on the menu as soon as i hit the volume up key it just returns a message advising the fastboot menu is disabled.
**edit
ah commands not menu options. not sure how i go about doing that. i am 100% new to droid...
ged flanders said:
Hi guys, I am having an issue i cant seem to resolve on my razr i. apologies if this has already been covered in another thread (or 10, which is usually the way with these things because nobody reads the other threads) I have been through a load of other threads but cannot seem to resolve my issue so i started my own.
Right, I have switched from iphone to razr and am not stupid when it comes to jailbreaking etc so thought rooting the razr wouldnt be a problem. when trying to root it it failed and i am stuck at the fastboot menu, however, everything on the menu is disabled so i cant use it. i get the usual message:
fastboot reason: flash failure
fastboot max download size: 100mb
usb connected
if i try to use anything on the menu i get the following message:
fastboot menu disabled.
my phone is not unlocked and not rooted. i have barely done anything to it other than install a couple of free apps. i am unable to progress past this screen. the phone is GB and is on 4.0.4
any help you guys can give would be greatly appreciated. again, apologies if this has already been covered, none of the solutions i found were able to resolve my issue. as i said, i had no problems jailbreaking my old iphone, i am a bit of a n00b when it comes to droids...
Click to expand...
Click to collapse
Had the same problem, I used the recommendation in this thread, 5th post and it worked, but afterwards need to re-download apps from PlayStore:
http://forum.xda-developers.com/showthread.php?p=36612151
Follow the instructions exactly - you need the drivers and RSD lite on Windows PC, then connect the phone via usb cable that came with it; and you'll need a full unzip program (cost) so you can move the unzipped files into RSD lite. Get the right flash file though - there's a list in the linked post if you don't want GB retail which I used. Important: this only works for ICS 4.0.4 and don't try to downgrade to an earlier version than what's currently on your phone e.g. v.39 to v.31, for example.
Good luck.
AW: [Q] razr i problems - fastboot menu
If the solution from mervluk does not work (It didn't work for me either) , you should try if you are able to use the fast boot commands .
To do that simply connect your phone to the PC. Then download fast boot , if you do not already have that. It is in the .zip from the RAZR I root thread.
The go to the downloaded folder. There hold shift and perform a right mouse click. Then choose" start a command prompt here "or something similar (don't know how the option is called in English).
Then type in
fastboot reboot
When the phone reboots you might be able to unlock your phone and flash the software.
BUT BE AWARE! YOU WILL LOSE YOUR WARRANTY!!
So you better try the other solution first. This should be your last option.
If you don't know how to unlock the bootloader look in the RAZR I forum or pn me .
Alex
Sent from my XT890 using xda premium
mervluk said:
Had the same problem, I used the recommendation in this thread, 5th post and it worked, but afterwards need to re-download apps from PlayStore:
http://forum.xda-developers.com/showthread.php?p=36612151
Follow the instructions exactly - you need the drivers and RSD lite on Windows PC, then connect the phone via usb cable that came with it; and you'll need a full unzip program (cost) so you can move the unzipped files into RSD lite. Get the right flash file though - there's a list in the linked post if you don't want GB retail which I used. Important: this only works for ICS 4.0.4 and don't try to downgrade to an earlier version than what's currently on your phone e.g. v.39 to v.31, for example.
Good luck.
Click to expand...
Click to collapse
thanks buddy. i will give this a whirl and let you know how i get on. fingers crossed!
mervluk - your advice worked a treat. i got it working again. thanks !
now i am working again, what cool tricks do people advise. is it worth rooting it ? what can i do once it is rooted? am i able to network unlock it myself ?
ged flanders said:
mervluk - your advice worked a treat. i got it working again. thanks !
now i am working again, what cool tricks do people advise. is it worth rooting it ? what can i do once it is rooted? am i able to network unlock it myself ?
Click to expand...
Click to collapse
Glad about that. This phone can be a bit of a so-and-so. ics is being updated ota to Jelly Bean 4.1.2, which I've avoided so far to keep fm (although not activated on the supplied software). I did succeed with unlocking the bootloader (loose warranty - important) following the whole complicated procedure on Moto's website - but couldn't myself use the shortcuts on here. (Then had to set up again and re-download everything from the PlayStore). It required the Moto-supplied key. I then rooted, though I think the JB ota download unroots again? You can't use RSD lite with JB.
With JB the procedures are different, and a modified JB European (not for use with GB) firmware is now available on another thread which is impressing some posters. But I think just be a bit cautious as there does not appear to be any fix for the "service code corrupt" bootloader error yet. Looks like the options are very restricted whilst no-one understand the interaction between Google Android and the intel atom chipset.
I have a network unlock key from one of the commercial suppliers (cellunlocker.net), but haven't needed to try and use it yet!
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
Hey, I can't update my SM-G925A to marshmallow 6.0.1, probably because it's unlocked. I thought about Odin but I couldn't find the right ROM online. Can someone help me find the right ROM or help me update it in another way? Thanks
Marshmallows is not available yet for G925A. Maybe will get it 2 years from now.
Sent from my SAMSUNG-SM-G925A using XDA-Developers mobile app
Marshmallow was just released for the G925A today, G920A yesterday. I've been calling AT&T every ****ing day for the past three weeks. FINALLY, the update is here. I'm still waiting for it to hit my region though. I would love a firmware file.
If that's true, super happy here.
Sent from my SAMSUNG-SM-G925A using XDA-Developers mobile app
At this point, I'm honestly not sure. Probably called AT&T over 20 times just today and each rep seems to be more stupid than the last. Some say it's out, others have no clue. As a new member, I'm not allowed to post the link, but it says on samsungs website that the AT&T S6 (non edge) is running Android 6.0.1 Marshmallow. If you'd like to see for yourself, go to samsung.com, in the search box type "g925a marshmallow" and click on the one that says something like "what software is my Galaxy s6 running?"
I am so done with this carrier. Never will I buy a phone locked to AT&T again.
Sent from my SM-T710 using Tapatalk
---------- Post added at 04:01 AM ---------- Previous post was at 03:55 AM ----------
Just got off the phone with a rep that seemed to know what he was talking about. He did confirm that the S6 has started rolling out, but the edge has not. He also said that if the s6 is out, the edge shouldn't be more than a week behind. He told me he'd call me as soon as it's released and as soon as I get the news, I'll update you guys. I know how frustrating this is!
Sent from my SM-T710 using Tapatalk
G925AUCU3CPC2 saw it on a site called thunderztech but no link yet...
vicobh said:
G925AUCU3CPC2 saw it on a site called thunderztech but no link yet...
Click to expand...
Click to collapse
Saw the same page you're talking about. Sounds like the OTA should be rolling out in the next couple of days.
Instructions on how to get 6.01 on G925A
1. YOU MUST HAVE OJ9 update on your phone.
2. Check "about devices" under baseband version.
3. Download all files from this link
https://drive.google.com/open?id=0B04l-XMi07VKdkY0ZExzeEVHcFk
4. Open adb fastboot (MAKE SURE YOUR PHONE IS CONNECTED TO YOUR PC)
5. Put this file (SS-G925AUCU3BOJ9-to-U3CPD6-UP) in your main PC directory C:\ and change the name
SS-G925AUCU3BOJ9-to-U3CPD6-UP to OTA and place a copy of OTA in your phone main directory.
6. Shutdown phone.
7. Restart phone by holding down the POWER, HOME, and UP button at the same time. DONT release until you get an UPDATE LOGO on your phone.
8. Go to your computer in the adb fastboot and type adb devices
9. Then type adb sideload DO NOT HIT ENTER YET!!
10. Go to your main directory on your computer where you put the OTA file and drag it on the
adb fastboot after adb sideload and hit ENTER.
11. This process will take 1hr so be patient and let the phone reboot.
12. Once the phone reboot, you will have 6.01!!!!!
Tried both ways (Instructions on thread and attached to file) and no luck as of yet. I will retry this afternoon. has anyone else tried this yet?
Seems dumb but the only thing that I needed to do to get it to accept the ota.zip was to reboot. My guess is that windows has to be rebooted after installing adb/fastboot.
gmccowan1 said:
1. YOU MUST HAVE OJ9 update on your phone.
2. Check "about devices" under baseband version.
3. Download all files from this link
https://drive.google.com/open?id=0B04l-XMi07VKdkY0ZExzeEVHcFk
4. Open adb fastboot (MAKE SURE YOUR PHONE IS CONNECTED TO YOUR PC)
5. Put this file (SS-G925AUCU3BOJ9-to-U3CPD6-UP) in your main PC directory C:\ and change the name
SS-G925AUCU3BOJ9-to-U3CPD6-UP to OTA and place a copy of OTA in your phone main directory.
6. Shutdown phone.
7. Restart phone by holding down the POWER, HOME, and UP button at the same time. DONT release until you get an UPDATE LOGO on your phone.
8. Go to your computer in the adb fastboot and type adb devices
9. Then type adb sideload DO NOT HIT ENTER YET!!
10. Go to your main directory on your computer where you put the OTA file and drag it on the
adb fastboot after adb sideload and hit ENTER.
11. This process will take 1hr so be patient and let the phone reboot.
12. Once the phone reboot, you will have 6.01!!!!!
Click to expand...
Click to collapse
For some reason it doesnt work for me
like its still stuck in 5.1.1
Worked perfectly for me had no problems what so ever........Thanks a bunch
if i do this update, will my phone be still remain unlocked or it will get locked again after this update ?
Hi, would like to know if this will lock my phone back to AT&T?
G925AUCU3BOI2 flash with G925AUCS5DPJ1
adrianneedshelpplease said:
For some reason it doesnt work for me
like its still stuck in 5.1.1
Click to expand...
Click to collapse
my s6 edge build number G925AUCU3BOI2 with Android V5.1.1, but i want to have Marshmallow update for this build. this is AT&T unlocked phone so OTA not available. and i have not found any stock files for this build. can i flash with build G925AUCS5DPJ1 stock files? will that works in my phone?
Reply ASAP. i am waiting on this
Samsung Experience Kiosk is a No-Go
AT&T unlocked my Samsung S6 Edge, at my request. They offered me an out last February when
they changed the DATA plan pricing structure. When Marshmallow was released I took my phone
the AT&T store where I purchased it (with the receipt) for the update. They would not touch my
phone since I was no longer a customer. So I called Samsung Corporate several times and was told
that since the phone was out of warranty, there was nothing they could(would) do. The last
Samsung rep I spoke to suggested that I take it to a Samsung Experience Kiosk in Best Guy for the
update. I took it to Kiosks in two different states and both refused to touch the phone for fear of
being sued should they "Brick" it. I finally got it updated by refusing to let them service any other
customers until it was done. It seems that the Kiosks are sub-contractors and not store employees.
The store manager got involved because I was costing him sales. To make a long story short, I now
have Marshmallow but have not gotten any security patches in a year. If you decide to try a Samsung
Experience Kiosk, be prepared to stand your ground - even then its a coin toss whether you get the
update.
.
Brand new here, looking to unlock, root and then flash a standard Android build or custom DeGoogled ROM for my new device. I was looking to find a way to unlock the bootloader to start and found that Huawei have stopped giving out unlock codes and that the info around unlocking wasn't great so I made a note of all my steps as below.
Please let me know if this works for you and if you have any issues, please also read and follow the guidelines carefully as there are lots of things like using all the applications as an administator and changing directories that are important.
I am also looking for a way to install TWRP or another recovery thing on this device so I don't brick it, as I want to root the tablet and muck around with it. Has anyone got any experience of doing this successfully and does anyone have links to methods to create a cloned backup of the standard OS?
This was done on a brand new Mediapad M3 Lite 8 (the Wifi version, not LTE) with Android 7.0, EMUI 5.1, CPN-W09, build CPN-W09C100B251 - BUT will probably work on the LTE version, the non-lite version and the 7 and 10 inch models.
IMPORTANT: This costs money and is done through the DC Unlocker tool, it costs 4 credits (4 euros/dollars) for the Mediapad M3 Lite 8 (Wifi, not LTE) as Huawei now do not offer the bootloader code AT ALL . I have copied/streamlined the steps below that were found as guides originally at the dc unlocker website, check their site guides to find originals.
Step 1 - Developer Options enable
Go to settings, about tablet, tap build number 7 times to unlock developer options
Go to developer options, enable OEM unlock, enable USB debugging
Step 2 - Enable manufacture mode
If your phone has a dialpad, enter dial pad code *#*#2846579#*#*
IF your phone doesn't have a dialpad, go to calculator and enter ()()2846579()()=
This willl take you to a developer menu, select "Project Menu", "Background settings", "USB ports settings", "Manufacture mode".
Step 3 - Install drivers
Connect your Android device to your PC with a usb cable and either install Hisuite from the connected drive that will attach, or download it from the Huawei website by searching for Huawei Hisuite and going to their official website.
To check this has worked, go to Device Manager on your PC and look for Modems - there should be an entry called Android Adapter Modem - if this is not present try disconnecting/reconnecting your device and restarting Hisuite.
Step 4 - Read bootloader code
Download the latest DC Unlocker tool from dc-unlocker dot com and extract it, then AS AN ADMINISTRATOR (right click and Run as Administrator) run the client.exe (was called dc-unlockerclient2.exe)
Click Select Manufacturer dropdown and change to Huawei Phones, not Modems, press the magnifier/search icon at bottom left and your phone info should be found. This should also
Step 5 - Buy credits from the dc unlocker site as a new user, try 4 credits first and then login with these new user details in the dc unlocker application on your PC, this will show your credits and the phone connected as well as the cost. Click the Unlocking icon on the top right and click Read botloader code to get your code. Make a note of this/copy it somewhere.
Step 6 - Go back to the folder that dc unlocker is in
Go into the unzipped folder and then copy the location of this folder by clicking on the address bar in File Explorer and copying this location, you'll have something similar to
C:\Users\ExampleUser\Downloads\dc-unlocker2client_1.00.1403
Step 7 - Turn off your phone and turn it back on holding the Vol down and Power buttons to enter fastboot mode, connect your device to your PC
Step 8 - Open cmd by searching for cmd in windows, right click cmd and open it as administrator, you'll get the black and white windows terminal
In the terminal type "cd C:\Users\ExampleUser\Downloads\dc-unlocker2client_1.00.1403" (or the path for the latest version of the dc unlocker you have downloaded) without the quotation marks and with YOUR directory path as described above. The command cd just changes directory to the one you give. Your terminal should now show the above directory as the path in which it now sends commands, i.e the > mark is now displayed after the directory path we copied
Step 9 - Type "adb devices" without quotation marks to start the adb daemon
Step 10 - Type "fastboot devices" without quotation marks and you should see a device number with the word fastboot next to it.
Step 11 - Now type "fastboot oem unlock" without the quotation marks, followed by a space and then your bootloader unlock code i.e
fastboot oem unlock XYZ123456789
Step 12 - Your device should show a screen asking you to accept the unlock, then onto another screen where you should press the power key to continue onto booting your factory reset unlocked device.
Step 13 - You might have to disconnect the USB cable and reboot your device now, and you'll set up the device from scratch again - but now the bootloader unlocked, allowing you to load stuff like TWRP if you can find the right version - which I can't right now! :good:
I have also now been able to install TWRP by using the TWRP image specifically for BAH-W09 found on page 17 of the "TWRP (greatslon mod)" in the link provided by pitapart
thread. I can't post links yet which is why I'm typing to source....
I have been trying to flash SuperSU using the latest 2.82 zip but keep getting the error "Extracting Ramdisk - Failure, aborting", which is the same error I'm getting when trying to root using SRKtool, both the 2.1 universal version and the 2.0 Huawei version, using option 1 for Mate P8 or option 6 for systemless.
I've downloaded a system root version of SuperSU (google "supersu system mode", first XDA thread) and flashed using TWRP, it says it has installed but the SuperSU app doesn't show root, and typing "su" in TWRP console doesn't show I can do commands in superuser mode. Can anyone help?
I recently have been purchased the LTE version of this device. Although I cannot try this out currently, I probably will in the future so please keep us updated about your experiments for reference!
avkjbl5bak said:
I have also now been able to install TWRP by using the TWRP image specifically for BAH-W09 found on page 17 of the "TWRP (greatslon mod)" in the link provided by pitapart
thread. I can't post links yet which is why I'm typing to source....
I have been trying to flash SuperSU using the latest 2.82 zip but keep getting the error "Extracting Ramdisk - Failure, aborting", which is the same error I'm getting when trying to root using SRKtool, both the 2.1 universal version and the 2.0 Huawei version, using option 1 for Mate P8 or option 6 for systemless.
I've downloaded a system root version of SuperSU (google "supersu system mode", first XDA thread) and flashed using TWRP, it says it has installed but the SuperSU app doesn't show root, and typing "su" in TWRP console doesn't show I can do commands in superuser mode. Can anyone help?
Click to expand...
Click to collapse
Hi,
Were you ever able to get your Mediapad M3 Lite 8 rooted? I really like this tablet but, need the 5 Ghz wifi band which requires root from everything I have read.
Thanks
howgies said:
Hi,
Were you ever able to get your Mediapad M3 Lite 8 rooted? I really like this tablet but, need the 5 Ghz wifi band which requires root from everything I have read.
Thanks
Click to expand...
Click to collapse
I have my Mediapad M3 Lite rooted by magisk.
I followed the unlock guide and unlocked the bootloader.
I couldn't find my exact firmware I downloaded the most recent one I could find.
I extracted the boot.img with Huawei Update extractor and copied it to my phone.
I download and installed latest magisk app.
I opened the magic app-> install -> install -> patch the boot image file which I then flashed through fastboot.
I then opened magisk -> install -> Direct install.
Everything works but like me you take a risk in not using the exact boot.img.
I tried and installed TWRP which worked but the volume keys would let me run the script I was trying to rebrand the phone. In the end it isn't necessary to root the phone.
sd26 said:
I followed the unlock guide and unlocked the bootloader.
I couldn't find my exact firmware I downloaded the most recent one I could find.
I extracted the boot.img with Huawei Update extractor and copied it to my phone.
Click to expand...
Click to collapse
Very bad idea and advice:
- people often uses wrong firmware or wrong version;
- a boot from a different version can be incompatible, you can be sure only too late!
The right thing is to boot to TWRP then in the console, using "dd" command do a copy of original boot!
nicolap8 said:
Very bad idea and advice:
- people often uses wrong firmware or wrong version;
- a boot from a different version can be incompatible, you can be sure only too late!
The right thing is to boot to TWRP then in the console, using "dd" command do a copy of original boot!
Click to expand...
Click to collapse
Very poor reply, you did not read my post properly, just jumped in to demonstrate your superciliousness. No advice was given and you missed the word risk. More productive use of replying would have been to include the actual command required anyway which is:
dd if=/dev/block/boot-device/by-name/boot of=boot.img
Helping wasn't the point your trying to make.
sd26 said:
Very poor reply, you did not read my post properly, just jumped in to demonstrate your superciliousness. No advice was given and you missed the word risk. More productive use of replying would have been to include the actual command required anyway which is:
dd if=/dev/block/boot-device/by-name/boot of=boot.img
Helping wasn't the point your trying to make.
Click to expand...
Click to collapse
if my reply is too poor, report it to mods...
A post like your IS an advice because people read and follow it. What is wrong is not that you write or my opinion but people behaviour
I read the "risk" word but a lot of people would not. This is also the reason I don't wrote the dd command: search and learn! Most of the messages you read here are of people who have broken their own terminal because just followed a post like your, without knowing what are doing.
N
sd26 said:
Everything works but like me you take a risk in not using the exact boot.img.
Click to expand...
Click to collapse
I see in your first screenshot the fingerprint-id menuentry is gone.... does your fingerprint-sensor working properly ?
I rooted my mediapad m3 lite 10 in the same way, but my boot-image is the right version. ( installed is BAH-W09C100B257, firmware downloaded with the huawei firmware finder app is exactly BAH-W09C100B257) . My fingerprint menuentry is gone too.....and the sensor doesnt work (with the working registered fingerprint before the rooting)
Marc
#marcg# said:
I see in your first screenshot the fingerprint-id menuentry is gone.... does your fingerprint-sensor working properly ?
I rooted my mediapad m3 lite 10 in the same way, but my boot-image is the right version. ( installed is BAH-W09C100B257, firmware downloaded with the huawei firmware finder app is exactly BAH-W09C100B257) . My fingerprint menuentry is gone too.....and the sensor doesnt work (with the working registered fingerprint before the rooting)
Marc
Click to expand...
Click to collapse
I did not have the fingerprint option activated so I checked it and found my sensor also does not work with the patched boot.img on. I could search and find the fingerprint menu entry but could not get it to operate. Reflashing the stock boot.img returned the sensor menu and fingerprint to normal but of course you lose root. More searching for solutions required.
Also I'm using the TWRP-3.2.1-bah-20180627.img recovery. The volume keys don't work so the hurupdater script I'd like to use aborts. Anyone got any other recovery for a CPN-W09C128B006?.
sd26 said:
I did not have the fingerprint option activated so I checked it and found my sensor also does not work with the patched boot.img on. I could search and find the fingerprint menu entry but could not get it to operate. Reflashing the stock boot.img returned the sensor menu and fingerprint to normal but of course you lose root. More searching for solutions required.
Also I'm using the TWRP-3.2.1-bah-20180627.img recovery. The volume keys don't work so the hurupdater script I'd like to use aborts. Anyone got any other recovery for a CPN-W09C128B006?.
Click to expand...
Click to collapse
I have
avkjbl5bak said:
Brand new here, looking to unlock, root and then flash a standard Android build or custom DeGoogled ROM for my new device. I was looking to find a way to unlock the bootloader to start and found that Huawei have stopped giving out unlock codes and that the info around unlocking wasn't great so I made a note of all my steps as below.
Please let me know if this works for you and if you have any issues, please also read and follow the guidelines carefully as there are lots of things like using all the applications as an administator and changing directories that are important.
I am also looking for a way to install TWRP or another recovery thing on this device so I don't brick it, as I want to root the tablet and muck around with it. Has anyone got any experience of doing this successfully and does anyone have links to methods to create a cloned backup of the standard OS?
This was done on a brand new Mediapad M3 Lite 8 (the Wifi version, not LTE) with Android 7.0, EMUI 5.1, CPN-W09, build CPN-W09C100B251 - BUT will probably work on the LTE version, the non-lite version and the 7 and 10 inch models.
IMPORTANT: This costs money and is done through the DC Unlocker tool, it costs 4 credits (4 euros/dollars) for the Mediapad M3 Lite 8 (Wifi, not LTE) as Huawei now do not offer the bootloader code AT ALL . I have copied/streamlined the steps below that were found as guides originally at the dc unlocker website, check their site guides to find originals.
Step 1 - Developer Options enable
Go to settings, about tablet, tap build number 7 times to unlock developer options
Go to developer options, enable OEM unlock, enable USB debugging
Step 2 - Enable manufacture mode
If your phone has a dialpad, enter dial pad code *#*#2846579#*#*
IF your phone doesn't have a dialpad, go to calculator and enter ()()2846579()()=
This willl take you to a developer menu, select "Project Menu", "Background settings", "USB ports settings", "Manufacture mode".
Step 3 - Install drivers
Connect your Android device to your PC with a usb cable and either install Hisuite from the connected drive that will attach, or download it from the Huawei website by searching for Huawei Hisuite and going to their official website.
To check this has worked, go to Device Manager on your PC and look for Modems - there should be an entry called Android Adapter Modem - if this is not present try disconnecting/reconnecting your device and restarting Hisuite.
Step 4 - Read bootloader code
Download the latest DC Unlocker tool from dc-unlocker dot com and extract it, then AS AN ADMINISTRATOR (right click and Run as Administrator) run the client.exe (was called dc-unlockerclient2.exe)
Click Select Manufacturer dropdown and change to Huawei Phones, not Modems, press the magnifier/search icon at bottom left and your phone info should be found. This should also
Step 5 - Buy credits from the dc unlocker site as a new user, try 4 credits first and then login with these new user details in the dc unlocker application on your PC, this will show your credits and the phone connected as well as the cost. Click the Unlocking icon on the top right and click Read botloader code to get your code. Make a note of this/copy it somewhere.
Step 6 - Go back to the folder that dc unlocker is in
Go into the unzipped folder and then copy the location of this folder by clicking on the address bar in File Explorer and copying this location, you'll have something similar to
C:\Users\ExampleUser\Downloads\dc-unlocker2client_1.00.1403
Step 7 - Turn off your phone and turn it back on holding the Vol down and Power buttons to enter fastboot mode, connect your device to your PC
Step 8 - Open cmd by searching for cmd in windows, right click cmd and open it as administrator, you'll get the black and white windows terminal
In the terminal type "cd C:\Users\ExampleUser\Downloads\dc-unlocker2client_1.00.1403" (or the path for the latest version of the dc unlocker you have downloaded) without the quotation marks and with YOUR directory path as described above. The command cd just changes directory to the one you give. Your terminal should now show the above directory as the path in which it now sends commands, i.e the > mark is now displayed after the directory path we copied
Step 9 - Type "adb devices" without quotation marks to start the adb daemon
Step 10 - Type "fastboot devices" without quotation marks and you should see a device number with the word fastboot next to it.
Step 11 - Now type "fastboot oem unlock" without the quotation marks, followed by a space and then your bootloader unlock code i.e
fastboot oem unlock XYZ123456789
Step 12 - Your device should show a screen asking you to accept the unlock, then onto another screen where you should press the power key to continue onto booting your factory reset unlocked device.
Step 13 - You might have to disconnect the USB cable and reboot your device now, and you'll set up the device from scratch again - but now the bootloader unlocked, allowing you to load stuff like TWRP if you can find the right version - which I can't right now! :good:
Click to expand...
Click to collapse
Did you ever get and answer to your question about cloning or getting the original factory images. I've been trying on and off for 9months. I have unlocked the bootloader and backed up using TWRP (from the 10inch model), but when I relocked the bootloader everything fell apart... unstable boot loops, etc. not sure if I had to wipe recovery I burned with TWRP or what. Also TWRP does not back-up the data partition I think due to encryption (from other posts I read). My goal was to rebrand a pile of the Chinese version tablets I have to US because we use them in our product, and the US are not available, so rebranding would give me more time before to find a replacement. Any clues would help!!!
sd26 said:
I did not have the fingerprint option activated so I checked it and found my sensor also does not work with the patched boot.img on. I could search and find the fingerprint menu entry but could not get it to operate. Reflashing the stock boot.img returned the sensor menu and fingerprint to normal but of course you lose root. More searching for solutions required.
Also I'm using the TWRP-3.2.1-bah-20180627.img recovery. The volume keys don't work so the hurupdater script I'd like to use aborts. Anyone got any other recovery for a CPN-W09C128B006?.
Click to expand...
Click to collapse
I successfully rooted my CPN-L09 without loosing fp sensor, have a look here: https://forum.xda-developers.com/mediapad-m3/help/to-patch-boot-img-magisk-v17-3-t3938629
Hi
im a new member but have been using the site for ages.
my mediapad m3 is also wifi only and im trying to get the code for the bootloader to be unlocked except for the fact that my calculator app isn't scientific enough (lol) to include brackets.
what do I do to get the code or update my calc app?
alex
bigprat9 said:
Hi
im a new member but have been using the site for ages.
my mediapad m3 is also wifi only and im trying to get the code for the bootloader to be unlocked except for the fact that my calculator app isn't scientific enough (lol) to include brackets.
what do I do to get the code or update my calc app?
alex
Click to expand...
Click to collapse
You have to use the calculator in landscape mode (turn on auto-rotate) and then the bracket buttons will appear.
So I finally got around to installing this on my stock version. I found 16GB was too limiting and I was hoping to use the SD card to expand the space so I could use it for a few more years. I purchased the code from DC_unlocker.
A couple of things I noticed while following the guide. To enter fastboot mode, holding down the volume down and power button doesn't seem to work. What you to do is while it's off, hold down the volume down button and plug in the microusb cable, while continuing to hold it down. You could also enter fastboot using an ADB command.
Also I couldn't wipe anything before installing the new roms, I got error messages. I'm not sure what that means. Anyways after installing android 9, it seemed to take a very long time to first boot. The graphic animation is going, but I wasn't sure if it was working so I hard reset once, tried to boot again and then waited again, hard reset again and put it down thinking I would have to look into the error messages and when I came back it was up and running.
Hi, I'm hoping someone can help me out here.
A few days ago, I followed the instructions unlocking the bootloader of my Mediapad M3 lite 8 (CPN-W09) and sure enough, I successfully unlocked the bootloader. However I've now run into another problem - I cannot get the FRP on the tablet to be unlocked!
Nothing I've tried seems to get it to unlock. The (only) Google account used on the tablet has been my own, and it's been no problem signing back into my account when factory resetting the tablet. One time when investigating it, after a factory reset it did say that it was "restricted" but again, adding my Google account details on the setup was no issue, but even after then deleting the account (which, if I'm right, should set FRP to "unlocked") when I enter into fastboot mode it still shows FRP as locked! And it shows it no matter what I do, wherever the Google account is "active" on the tablet or not, and the last four or five times I've did a factory reset with both data and cache partition wipes done and nothing budges. I think I'm at a lost cause here - the "OEM Unlock" option in the developer settings is totally greyed out. ?
Of course, the tablet is still "usable" but there is no way to carry out special functions after unlocking the bootloader, like rooting, install TWRP, custom ROM etc. and it just kinds of stands in a limbo.
I've tried searching here on XDA and the web in general, high and low, to see if this problem has affected anyone else, and strangely it doesn't seem to happen to anyone else!
For the record, I've also tried hardreset.info's FRP unlock tool which claimed to be successful, but it clearly wasn't!
I hope someone out there might have a solution to my woe - as I think I've partially crippled by M3 Lite 8 otherwise by trying to unlock the bootloader.
lawhec said:
Hi, I'm hoping someone can help me out here.
A few days ago, I followed the instructions unlocking the bootloader of my Mediapad M3 lite 8 (CPN-W09) and sure enough, I successfully unlocked the bootloader. However I've now run into another problem - I cannot get the FRP on the tablet to be unlocked!
Nothing I've tried seems to get it to unlock. The (only) Google account used on the tablet has been my own, and it's been no problem signing back into my account when factory resetting the tablet. One time when investigating it, after a factory reset it did say that it was "restricted" but again, adding my Google account details on the setup was no issue, but even after then deleting the account (which, if I'm right, should set FRP to "unlocked") when I enter into fastboot mode it still shows FRP as locked! And it shows it no matter what I do, wherever the Google account is "active" on the tablet or not, and the last four or five times I've did a factory reset with both data and cache partition wipes done and nothing budges. I think I'm at a lost cause here - the "OEM Unlock" option in the developer settings is totally greyed out. ?
Of course, the tablet is still "usable" but there is no way to carry out special functions after unlocking the bootloader, like rooting, install TWRP, custom ROM etc. and it just kinds of stands in a limbo.
I've tried searching here on XDA and the web in general, high and low, to see if this problem has affected anyone else, and strangely it doesn't seem to happen to anyone else!
For the record, I've also tried hardreset.info's FRP unlock tool which claimed to be successful, but it clearly wasn't!
I hope someone out there might have a solution to my woe - as I think I've partially crippled by M3 Lite 8 otherwise by trying to unlock the bootloader.
Click to expand...
Click to collapse
You could try to lock bootloader back, and before to unlock bootloader again, first just unlock OEM .
surdu_petru said:
You could try to lock bootloader back, and before to unlock bootloader again, first just unlock OEM .
Click to expand...
Click to collapse
I did try this at the time, and I couldn't get it to work. But I had another try at it yesterday and I managed to get the bootloader locked again, toggle OEM unlock to "off" and unlocked the bootloader once more and it worked!
So after doing this, I tried to get TWRP 3.3.1-1 flashed but it would stay frozen on the screen - I then read that I needed to install TWRP 3.2.0-0 first, install the August 2019 Lineage 16 firmware, then go back to the bootloader, flash TWRP 3.3.1-0, check everything was OK and then return to bootloader to finally flash TWRP 3.3.1-1. Success! I then flashed the latest Lineage OS 17.1 firmware along with Open Gapps (ARM64, Android 10, nano) and so far everything has worked OK. I just need to download all my apps again, but I'm sure it will give my CPN-W09 a new lease of life!
I used to do some rooting previously with Android handsets in the past, but the last time was two years ago (rooting & upgrading an Alcatel handset to Android 6.0) and FRP was new to me, throwing me off.
I've donated some Euros to you as an appreciation for your work & advice. Merci beaucoup!
lawhec said:
I did try this at the time, and I couldn't get it to work. But I had another try at it yesterday and I managed to get the bootloader locked again, toggle OEM unlock to "off" and unlocked the bootloader once more and it worked!
So after doing this, I tried to get TWRP 3.3.1-1 flashed but it would stay frozen on the screen - I then read that I needed to install TWRP 3.2.0-0 first, install the August 2019 Lineage 16 firmware, then go back to the bootloader, flash TWRP 3.3.1-0, check everything was OK and then return to bootloader to finally flash TWRP 3.3.1-1. Success! I then flashed the latest Lineage OS 17.1 firmware along with Open Gapps (ARM64, Android 10, nano) and so far everything has worked OK. I just need to download all my apps again, but I'm sure it will give my CPN-W09 a new lease of life!
I used to do some rooting previously with Android handsets in the past, but the last time was two years ago (rooting & upgrading an Alcatel handset to Android 6.0) and FRP was new to me, throwing me off.
I've donated some Euros to you as an appreciation for your work & advice. Merci beaucoup!
Click to expand...
Click to collapse
Thank you very much too
Hello
I followed the steps here to unlock the bootloader with my btv-dl09, that worked fine even its not lite.. :fingers-crossed:
but now, any clues? may i ll try the way of lawhec with
lawhec said:
So after doing this, I tried to get TWRP 3.3.1-1 flashed but it would stay frozen on the screen - I then read that I needed to install TWRP 3.2.0-0 first, install the August 2019 Lineage 16 firmware, then go back to the bootloader, flash TWRP 3.3.1-0, check everything was OK and then return to bootloader to finally flash TWRP 3.3.1-1. Success! I then flashed the latest Lineage OS 17.1 firmware along with Open Gapps (ARM64, Android 10, nano) and so far everything has worked OK. I just need to download all my apps again, but I'm sure it will give my CPN-W09 a new lease of life!
Click to expand...
Click to collapse
but cant find the TWRP 3.3.1-1?
may u Mean
[Recovery][Official] TWRP 3.3.1-10 [G97*0][Snap][3.Jan.20]
[Recovery][Official] TWRP 3.3.1-12 Snapdragon [N97x0][10.Nov.19]
[RECOVERY][ROOT]TWRP 3.3.1-1 Galaxy J6+/J610F/FN/G/DS
???
if so, why u choose one of these? No Clue for me^^ plz let me know
greetz
ADD: just found
Developed By :letschky
twrp-3.1.1-1-next.img
Jul 13, 2017 | 03:32PM
maybe these? looks pretty old but still working? Oo
The Alcatel 5033T (Telstra) I have is Telstra-locked to the point that most online unlock-code providers can't get a code to free it up. The only places which say they can do it require you to bring it in (they're in other states) or they want you to install Teamviewer (!) and they'll do it remotely.
I'm sure this is a FAQ on other phone models, but I see nothing for the Alcatel 1 here yet. What are the chances someone with past experience on ADB can figure out how to get this working with a non-Telstra SIM?
Did you manage to sort this
How to mount sd card
saw someone posted this, any Guru can verify the steps? or make it clearer?
**********************************************************************************
On the 5033T fastboot will flash only the system.img not the boot or recovery
image,so Magisk or TWRP cannot be flashed via fastboot. Also to flash via SPflashtool for the MT6739 you now need a custom DA and Auth file for that phone.
The downloaded edited 5033D system image will give you root access but install
RootCheckerBasic app to check as sometimes the root access disappears.
The phone modem is in the vendor.img partition and so should be unaltered as you
have flashed the system.img partition only.Your bands should be unaltered. Install the MTK Engineering Mode apk and use the bandmode function to see the bands. (Phone Developer option must be on(Tap build number untill developer options appear)).
Now that you have root access you can now network unlock the phone. Using ES File Explorer or Root Explorer. In the phone /vendor/protect_f/md you will see a file ST33_004. This file determines whether the phone is network locked.
If you get this file from an unlocked phone and put it in place of the one
in the locked phone the phone will be then unlocked and vice versa.
Download the 5033A firmware from the Needrom site. From the download get the protect1.img (in another files). Download to your PC the Ext4Unpacker tool.
Use the tool to extract the ST33_004 file from the 5033A protect1.img .
This is the unlocked ST33_004.
Using ES or Root Exp rename the existing ST33_004 in the phone as ST33_004bac
and copy the new ST33_004 file into the directory. The phone will now accept
non Telstra/Boost SIMs .
Also download the Mobile Upgrade S Gotu2 v5.3.5 tool to your PC. This is the TCL(i.e.=Alcatel) official firmware upgrade tool. It replaces the firmware in
your phone with the latest version on their server for your phone. For a stock
phone it will upgrade to their latest stock version.
For the 5033T+5033D 'hybrid' ,when started the tool appears to be downloading
the 5033T firmware from the server, so it seems that the tool could be used
to return the phone to stock, but this not tried or tested yet.
bmscott said:
The Alcatel 5033T (Telstra) I have is Telstra-locked to the point that most online unlock-code providers can't get a code to free it up. The only places which say they can do it require you to bring it in (they're in other states) or they want you to install Teamviewer (!) and they'll do it remotely.
I'm sure this is a FAQ on other phone models, but I see nothing for the Alcatel 1 here yet. What are the chances someone with past experience on ADB can figure out how to get this working with a non-Telstra SIM?
Click to expand...
Click to collapse
saw someone posted this, any Guru can verify the steps? or make it clearer?
Click to expand...
Click to collapse
Where'd you find this? I'm willing to try 'cos it'll let me get my son off Telstra's overpriced plan and onto something affordable like Jeenee (which the rest of us are on). I've had this Telstra SIM for years so I was hoping they'd unlock the phone for me - after all, it was sent as a replacement for an older phone that'll be out of service when they retire some of the towers in our area - but when I call in to have them do that, they say they'll have to call me back and (of course) never do...
Found the post from ozbargain forum with this 5033D link
https://yadi.sk/d/_-dnrtKS499rww
The 5033A you need to get it from needrom
Any luck someone? I am unable to root it using kingroot
Yes
The Ozbargain thread now has a lot more info than it did a few months ago - I'm still working through it myself, but here's the link: https://www.ozbargain.com.au/node/446160