userdebug problem - Nexus S General

Looks like that some of the Nexus S got the wrong software that makes them at the moment not capable to get the 2.3.1 update neither manual nor as OTA. If you find under phone information "userdebug" you won't be able to update yet. It looks like Google just found out about this problem a couple of days ago. I got my phone today and this is not a good start with the Nexus S experience:-( I will wait a few days and otherwise this phone goes back to BestBuy.
Below is comment from Nick Kralevich who works for the Android security team:
"userdebug" versions of Android are intended for engineering use only. It contains additional debugging compared to "user" builds. The hardware is exactly the same. You'll never get an update for a userdebug version of Android, which is naturally bad.
You can find out if you have a userdebug build by going to "Settings > About Phone > Build number" and looking for a userdebug string.
We're still investigating how this happened, but we believe it to be extremely rare.
If you are running a userdebug build, can you please contact me directly at [email protected]? Please make sure the subject contains "Android userdebug problem" so I can find your e-mail more easily.
I would appreciate it if you could include the following information:
* Where did you buy the phone? Store location?
* IMEI (Available by going to Settings > About Phone > Status > IMEI)
* Your google account name used on the phone.
This will help me assemble a list of people affected by this bug.
Thanks!
Nick Kralevich
Android Security Team

mgymnop said:
Looks like that some of the Nexus S got the wrong software that makes them at the moment not capable to get the 2.3.1 update neither manual nor as OTA. If you find under phone information "userdebug" you won't be able to update yet. It looks like Google just found out about this problem a couple of days ago. I got my phone today and this is not a good start with the Nexus S experience:-( I will wait a few days and otherwise this phone goes back to BestBuy.
Below is comment from Nick Kralevich who works for the Android security team:
"userdebug" versions of Android are intended for engineering use only. It contains additional debugging compared to "user" builds. The hardware is exactly the same. You'll never get an update for a userdebug version of Android, which is naturally bad.
You can find out if you have a userdebug build by going to "Settings > About Phone > Build number" and looking for a userdebug string.
We're still investigating how this happened, but we believe it to be extremely rare.
If you are running a userdebug build, can you please contact me directly at [email protected]? Please make sure the subject contains "Android userdebug problem" so I can find your e-mail more easily.
I would appreciate it if you could include the following information:
* Where did you buy the phone? Store location?
* IMEI (Available by going to Settings > About Phone > Status > IMEI)
* Your google account name used on the phone.
This will help me assemble a list of people affected by this bug.
Thanks!
Nick Kralevich
Android Security Team
[email protected]
Click to expand...
Click to collapse
I dont have this problem but great find

Hi all
Count me in on this one. Good find, I was wondering why no OTA notification came up on my device...
Purchased mine at Best Buy @ Millenia Mall Orlando, FL

If you are having a phone having userdebug based firmware please contact [email protected], he has personally contacted me and gave me a solution. Google has taken customer service to a whole NEW level my friends.
I state again, anyone not being able to Update to 2.3.1 due to firmware version having "soju-userdebug 2.3 GRH55 79397 test-keys", "pre-released os" contact [email protected]

thanks mythamp.
does re-locking the bootloader after flashing allow me to get stock OTA updates? I read in another thread that when I flash CWM I loose the ability to update by OTA... thanks for any clarification!

I believe that firmware is completely stock and it even overrides the clockworkmod recovery with stock recovery. I have faith that this will receive OTA updates but I cannot test it and confirm until google sends out one!

I just exchanged my SNS against one with the normal software. It is so much faster now and I don't have problems installing applications from the market anymore. If you have a phone with the userdebug software running try to exchange it. I had no problems at BestBuy today.

Hi all,
For the most up to date information about this "userdebug" problem, please contact Google at [email protected].
Edited 2011-03-30 to use [email protected] instead of my personal e-mail address

Userdebug problem
What exactly was the solution for those of you with the problem?
I have emailed the people suggested but have had no response for two weeks so am just wondering whether there is another way to get a solution so i can get OTA updates or whether i should jump ship and get CM7.
Thanks

Related

Finding out the name of patch automatically sent to phone?

Hi everyone,
I have just purchased a Vodafone-branded Magic/Sapphire. Android prompts me to install an 4.2 MB large update called "Android Update 1.5" with this message:
Please install this update from Google. It contains a security fix.
Now, what really confuses me is that Android 1.5 is already installed - at least according to the settings menu, where this information is shown:
Model number: HTC Magic
Firmware version: 1.5
Kernel version: 2.6.27-00392-g8312baf [email protected] #72
Build number: CRB17
Accordingly, I have three questions:
The phone says that the update as already been downloaded (most likely in the background), but not yet installed. Is it possible, using a terminal program/shell-prompt, to browse the phone's filesystem and check the filename of the update before you install it on an un-rooted phone? If so, where do I look for the update package?
Why does the phone want to install an Android 1.5-update? According to the phone Android 1.5 is already installed?
Can someone please tell me what the 4.2 MB update does? I have been googling for Android OTA Update "4.2 MB", but it seems that nothing is known about this update anywhere (there are, however, other updates within the 4 MB-range but none of them are precisely 4.2 MB in size).
I'd very much appreciate any help to sort this out (moderators, I hope I havn't created this thread in the wrong subforum; if I have, I apologize).
1. Run ddms/logcat to see the URL of the update.
2. 1.5 is the OS version.
3. It's most probably a security patch (of 1.5).
Its CRC1 and already "leaked"
Amon_RA said:
1. Run ddms/logcat to see the URL of the update.
Click to expand...
Click to collapse
Thank you. I'll do it as soon as the phone is fully charged again (as the manual says the battery will perform at its best after completing a few full charge/recharge cycles, I don't want to disturb it - pseudo-science, I know ).
Is the ddms/logcat stored locally on the Magic/Sapphire by default, or is it just part of the SDK-package?
maxisma said:
Its CRC1 and already "leaked"
Click to expand...
Click to collapse
Woah, one step at a time mister . I'm a total Android-newbie (although trying to catch up browsing various forums).
What is "CRC1"?
Will installing this patch prevent me to root the phone at some later stage?
Is there a proper changelog available somewhere?
Focusyn said:
Woah, one step at a time mister . I'm a total Android-newbie (although trying to catch up browsing various forums).
What is "CRC1"?
Will installing this patch prevent me to root the phone at some later stage?
Is there a proper changelog available somewhere?
Click to expand...
Click to collapse
It's security updates. I'd recommend getting the update from here (xda) rather than attempting to install it from the carrier.

[Q] naming of update files is confusing ! Help!

OK, after reading a bunch of posts today, I'm dizzy as h3ll, and very confused.
We have two updates that came out OTA in the past couple of days.
1.139.04_4.010.40_COM_GEN1
And then we have
1.141.07_4.010.13_COM_GEN2
I bought my Tablet at Walmart in Watertown, NY, and it was a GEN1 with HC 3.01 on it.
Now some are saying that Acer switched over to GEN2 for US tablets as of the 3.1 update. (I'm not naming names).
I've run multiple custom ROMs on my tablet, and recently went back to see how stable the Acer releases have been. I downloaded both of the files listed above, (actually 11 GEN2 then OTA update to 13).
One person stated that the GEN1 was an Australian release, and that the GEN 2 was the US release. I can confirm what someone else said, that they both have GPS.conf files for north America, not Europe, nor Australia. Now I've seen many custom ROMS with different GPS.conf files in them ie: Europe, North America, etc.
Here's my question, how can we know for certain #1 which update is indeed for which country, as they're both seemingly configured for use in North America, unless Acer is really messing things up and issuing updates for Australia with the GPS configured for north America, and it certainly wouldn't surprise me.
And #2, which update is the newest, as someone else stated that the prefix with the highest number is the latest version, and yet another said it was the one with the higher end number is the latest!
If someone knows the real answer to these two questions, please stand up!
Otherwise it's going to get very confusing when trying to give advice to others asking questions about updates if they don't like waiting on Acer to get their act together.
TIA
XBoxD00D said:
OK, after reading a bunch of posts today, I'm dizzy as h3ll, and very confused.
We have two updates that came out OTA in the past couple of days.
1.139.04_4.010.40_COM_GEN1
And then we have
1.141.07_4.010.13_COM_GEN2
I bought my Tablet at Walmart in Watertown, NY, and it was a GEN1 with HC 3.01 on it.
Now some are saying that Acer switched over to GEN2 for US tablets as of the 3.1 update. (I'm not naming names).
I've run multiple custom ROMs on my tablet, and recently went back to see how stable the Acer releases have been. I downloaded both of the files listed above, (actually 11 GEN2 then OTA update to 13).
One person stated that the GEN1 was an Australian release, and that the GEN 2 was the US release. I can confirm what someone else said, that they both have GPS.conf files for north America, not Europe, nor Australia. Now I've seen many custom ROMS with different GPS.conf files in them ie: Europe, North America, etc.
Here's my question, how can we know for certain #1 which update is indeed for which country, as they're both seemingly configured for use in North America, unless Acer is really messing things up and issuing updates for Australia with the GPS configured for north America, and it certainly wouldn't surprise me.
And #2, which update is the newest, as someone else stated that the prefix with the highest number is the latest version, and yet another said it was the one with the higher end number is the latest!
If someone knows the real answer to these two questions, please stand up!
Otherwise it's going to get very confusing when trying to give advice to others asking questions about updates if they don't like waiting on Acer to get their act together.
TIA
Click to expand...
Click to collapse
Wow no answers to this post. Especially with everyone knowing everything in other threads.....amazing!
Here we go...This is from Acer's patch documents and best shows the current separate code trains...
A. Countries: UK/France/Italy/Spain
- Affected OS versions:
Acer_A500_4.010.22_COM_GEN1
Acer_A500_4.010.30_COM_GEN1
- After installing the update, you are advised to update your tablet’s operating system to:
Acer_A500_4.010.38_COM_GEN1
Acer_A500_4.010.38_7.006.01_COM_GEN1 (3.2)
B. Country: USA
- Affected OS versions:
Acer_A500_4.010.07_COM_GEN2
Acer_A500_4.010.08_COM_GEN2
Acer_A500_4.010.09_COM_GEN2
- After installing the update, you are advised to update your tablet’s operating system to:
Acer_A500_4.010.10_COM_GEN2
Acer_A500_4.010.11_COM_GEN2
Acer_A500_4.010.13_COM_GEN2 NEW
C. Countries: Singapore/Malaysia/Thailand/Philippines/India/Vietnam/
Indonesia/Australia/New Zealand
- Affected OS versions:
Acer_A500_4.010.12_COM_GEN1
Acer_A500_4.010.24_COM_GEN1
- After installing the update, you are advised update your tablet’s operating system to:
Acer_A500_4.010.40_COM_GEN1
Acer_A500_4.010.40_7.006.03_COM_GEN1 (3.2)
D. Countries: Taiwan/Hong Kong
- Affected OS version:
Acer_A500_4.010.23_COM_GEN1
- After installing the update, you are advised to update your tablet’s operating system to:
Acer_A500_4.010.39_COM_GEN1
Acer_A500_4.010.41_COM_GEN1
Acer_A500_4.010.41_7.006.01_COM_GEN1
I'm trying to sort through them to perhaps find/explain some differences.... other than the wifi driver (different countries allow different channels).
The one thing I can tell you is that no matter which rom i've looked at, all of the roms have the following lines in build.prop..
ro.product.locale.language=en
ro.product.locale.region=US
That said, we can add LAZY to the description of ACER. The thing that makes this most murky is the fact the people like us are more inclined to find instant gratification. That is, we download the newest version of the rom (or so we think) rather than the newest regional version. If you look at the above listings and you are on one of the lower versions for any of the above regions, looking for the OTA on the tablet itself will lead you through the upgrade paths listed for each region.
In all honesty we should have a mod sticky a thread for this so all inbound noobs can see it and avoid some grief.
dottat said:
In all honesty we should have a mod sticky a thread for this so all inbound noobs can see it and avoid some grief.
Click to expand...
Click to collapse
I agree! It's tough enough as it is helping ppl with the current naming process by Acer, or lack thereof!
Should, could, would, good luck!
Moving to Q&A.
PS: Every Q? thread should be posted in Q&A.
Of course the naming convention is only confusing if you're going off the rails with your tab - those of us who just leave them stock and install OTA's don't particularly care or pay attention to the update names.
Buy tablet > use tablet > get incremental > use tablet > get 3.1 > use tablet > get incremental > use tablet...
I'm waiting until the life cycle on this puppy nears its end before I do any ROM'ming. I'm a little paranoid that way but mostly I'm happy with vanilla. I also get confused by all the different steps - update, backup, clear this, clear that, install this, then update with that... I know, it can't be that complicated but I'm easily ditractac....
Oh look, a butterfly!
...
As I was saying, when you spread the peanut butter over the toast you could have added the honey first, thereby eliminating the danger or bread-breakage and...
gammaRascal said:
Of course the naming convention is only confusing if you're going off the rails with your tab - those of us who just leave them stock and install OTA's don't particularly care or pay attention to the update names.
Buy tablet > use tablet > get incremental > use tablet > get 3.1 > use tablet > get incremental > use tablet...
I'm waiting until the life cycle on this puppy nears its end before I do any ROM'ming. I'm a little paranoid that way but mostly I'm happy with vanilla. I also get confused by all the different steps - update, backup, clear this, clear that, install this, then update with that... I know, it can't be that complicated but I'm easily ditractac....
Oh look, a butterfly!
...
As I was saying, when you spread the peanut butter over the toast you could have added the honey first, thereby eliminating the danger or bread-breakage and...
Click to expand...
Click to collapse
Yeah bro, you best stick to OTA, you don't want to get too confused, and overtax yourself lol
Now... if we could get custom rom devs to make a couple different versions we'd be in business too...
Please tell me where to get the kernel module tun.ko 2.6.36.3Hoeyillian-3.4 +
shurpa said:
Please tell me where to get the kernel module tun.ko 2.6.36.3Hoeyillian-3.4 +
Click to expand...
Click to collapse
I wouldn't try to get that as a standalone file unless you *really* know what you are doing, like an experienced linux sysadmin/developer. The simplest thing to do would be to just install the latest HoneyVillain kernel, currently at 3.6.
Frankly, I'd like to see something (preferably from Acer) about what each update actually provides us PRIOR to accepting the OTA. Heck, I can't even find that information when upgrading custom ROMs from like v3.2 to v3.2.1. I'm the type of person who always waited to see how much (for example) SP3 would break Windows XP before installing it myself.
are these ics or hc if they are ics check out my article on how to unbrick your tablet(also how to manually update to ics) PS: if you have already upgraded to ics via custom rom or acer you probably wont be able to go back to HC
http://forum.xda-developers.com/showthread.php?t=1699277
using custom rom is more simple.
Advice for interested Newbies for updating
gammaRascal said:
Of course the naming convention is only confusing if you're going off the rails with your tab - those of us who just leave them stock and install OTA's don't particularly care or pay attention to the update names.
Buy tablet > use tablet > get incremental > use tablet > get 3.1 > use tablet > get incremental > use tablet...
I'm waiting until the life cycle on this puppy nears its end before I do any ROM'ming. I'm a little paranoid that way but mostly I'm happy with vanilla. I also get confused by all the different steps - update, backup, clear this, clear that, install this, then update with that... I know, it can't be that complicated but I'm easily ditractac....
Oh look, a butterfly!
.....
Click to expand...
Click to collapse
Pretty Butterflies.
Seriously, I took the same tact with you use stock...use stock..., however, I broke down about a month ago, after installing android 4.2 on my wife's HP Playbook (the dead Palm version...)
I got jealous, so used afterOTA to install a new recovery ROM, and root the tablet (also used blackthunder's ap500apx flashing tool), and between the two of them got jb (4.1.2 up and running very smoothly). Now that I installed the skrillex clockwork mod 9.x I now have a great recovery tool, and just installed
4,2.2 on my tablet, with less then 30 minutes to take care of it.
updating rules:
a) read the ENTIRE thread (use multiple tabs.
a1) use a new window for each new topic or sw you investigate.
a2) download all the sw to ONE folder so you can find it.
b) READ the ENTIRE thread (oh, did I say that already?... I mean REALLY read EVERY thread to the END!!
b1) open the first page. open the last page in a new tab, or work your way backwards. yes, 42 pages of updated discussion is difficult, but so is
repairing a bricked tablet.​
anyway that's my 25cents worth.
good luck
need to reinstall original os A500
XBoxD00D said:
OK, after reading a bunch of posts today, I'm dizzy as h3ll, and very confused.
It was during an update (and my forgetting pattern) when my A500 failed. I am also dizzy from all this and Acer isn't any help AT ALL. Just added insult to injury as far as I'm concerned. One has to jump hoops just to find a contact number or email.
So, vent over, does anyone have the original OS for the A500 that I can easily (with instructions) get my tablet up and going with again? I did learn that when using the paperclip method, one has to release the power switch and repress again. Just looking for some assistance yet once again. Thanks - if there were a pill for this, I'd take it.
Click to expand...
Click to collapse
ivibre said:
OK, after reading a bunch of posts today, I'm dizzy as h3ll, and very confused.
It was during an update (and my forgetting pattern) when my A500 failed. I am also dizzy from all this and Acer isn't any help AT ALL. Just added insult to injury as far as I'm concerned. One has to jump hoops just to find a contact number or email.
So, vent over, does anyone have the original OS for the A500 that I can easily (with instructions) get my tablet up and going with again? I did learn that when using the paperclip method, one has to release the power switch and repress again. Just looking for some assistance yet once again. Thanks - if there were a pill for this, I'd take it.
Click to expand...
Click to collapse
I'm having the same problem and really will do anything to get it working again. You can use timmy dean's rollback tool, if you can get the 7z open. Neither lubuntu nor Windows XP will open it. So far I flashed a V8 bootloader, but I can't use blackthunder's tool for some stupid reason, and when I contacted Acer (more like called them out on Facebook with a rant for thousands of people to see) they said they'd fix it under warranty conditions even though mine ran out.
They then proceeded to tell me when I went to double check that the case would be valid before I sent it to them, they said it expired and that I would have to pay $160 just to send it to them and not including parts. About a year before it stopped working, I sent it in to get the light board fixed (it was broken when I woke up one day) and I never opened the back of before. Three days ago I opened the back only to see that a cord was unplugged (promptly plugged it back in) and that multiple screws were missing. I nearly "contacted" them again, but decided to continue my search for a solution on here.

[Q] Towelroot no longer works... ideas?

I'm pretty new to the Android phones. I bought a Samsung Galaxy Note 8 tablet about a year ago, and I absolutely love it -- which was the only reason why I considered an Android phone when it came time to upgrade. That might have been a mistake.
The phone I chose was a Galaxy S5 from AT&T.
For many reasons I won't go into (and that many of you probably know) Kitkat is awful. Removing SD card access removed one of the most important reasons that I bought the phone. So, I decided to root the thing.
I read a bunch of info on how to root, and, eventually downloaded and tried to use towelroot only to discover that AT&T/Google have blocked all functionality of that program. My build is, unfortunately, the latest build -- July 22 2014 (or there abouts).
Now, I'm not sure if the phone was given to me with that update -- I only got the thing on Sunday. Maybe it was, maybe not. Dunno. So I have a couple of questions.
If I were to factory reset the phone, would that roll back these "Security" OTA updates that were pushed onto the phone? I'm pretty sure there was at least one after I got the thing. I've spent a fair amount of time setting the phone up, but I'll do it again if a factory reset would allow me to root the phone and return the SD card functions.
Is there a way to push an earlier version of the ROM onto the phone. I'm guessing not, since I think I read that AT&T helpfully locked the bootloader.
Finally, does anyone know of any way to root this device if neither of the two paths I presented above will work?
Thanks for any help. If I can't restore the SD card functionality, I'll probably just return the phone. That would be a bummer because I was really excited about it.
CKR83 said:
I'm pretty new to the Android phones. I bought a Samsung Galaxy Note 8 tablet about a year ago, and I absolutely love it -- which was the only reason why I considered an Android phone when it came time to upgrade. That might have been a mistake.
The phone I chose was a Galaxy S5 from AT&T.
For many reasons I won't go into (and that many of you probably know) Kitkat is awful. Removing SD card access removed one of the most important reasons that I bought the phone. So, I decided to root the thing.
I read a bunch of info on how to root, and, eventually downloaded and tried to use towelroot only to discover that AT&T/Google have blocked all functionality of that program. My build is, unfortunately, the latest build -- July 22 2014 (or there abouts).
Now, I'm not sure if the phone was given to me with that update -- I only got the thing on Sunday. Maybe it was, maybe not. Dunno. So I have a couple of questions.
If I were to factory reset the phone, would that roll back these "Security" OTA updates that were pushed onto the phone? I'm pretty sure there was at least one after I got the thing. I've spent a fair amount of time setting the phone up, but I'll do it again if a factory reset would allow me to root the phone and return the SD card functions.
Is there a way to push an earlier version of the ROM onto the phone. I'm guessing not, since I think I read that AT&T helpfully locked the bootloader.
Finally, does anyone know of any way to root this device if neither of the two paths I presented above will work?
Thanks for any help. If I can't restore the SD card functionality, I'll probably just return the phone. That would be a bummer because I was really excited about it.
Click to expand...
Click to collapse
For rooting, go there http://forum.xda-developers.com/showthread.php?t=2696537
or there http://forum.xda-developers.com/showthread.php?t=1980683
Follow tuto or ask here.
You have to give more info (S5 model, firmware...)
Good luck
Franky
Rooting Help?
fgth90 said:
For rooting, go there http://forum.xda-developers.com/showthread.php?t=2696537
or there http://forum.xda-developers.com/showthread.php?t=1980683
Follow tuto or ask here.
You have to give more info (S5 model, firmware...)
Good luck
Franky
Click to expand...
Click to collapse
I see that there are tutes here, and am wading through the 50+ pages of forum posts to find what I need. However, my worry is that none of this stuff will work because of the new firmware. Here is all the info that I have on my phone:
Galaxy S5 AT&T US version (SAMSUNG-SM-900A)
Android 4.4.2
kernel version 3.4.0-2178781 [email protected] #1 Tuesday July 22
Build # KOT49H.G900AUCU2ANG3
SE for Android Status
Enforcing SEPF_SAMSUNG-SM-G900A_4.4.2_0018 Tuesday July 22
Security Software version:
MDF v1.0 Release 3
VPN v1.4 Release 1
Thanks all the pertinent info, I think.
Because the update was so new, I don't think there's a way to root this anymore. People keep telling me to use ODIN and to download an earlier ROM (and I now have ODIN and an earlier ROM -- hopefully from a good source, but I have no idea if it is), but my impression is that this latest AT&T "security" update keeps you from reflashing the ROM because of the bootloader lockout.
Any further help would be appreciated.
Thanks
CKR83 said:
...
Any further help would be appreciated.
Thanks
Click to expand...
Click to collapse
Hello,
As I told you, the only method working for me (because of towelroot non working) is cf auto root.
Check periodicaly here http://autoroot.chainfire.eu/ to see if your model is listed.
I had just a look and it's not listed yet.
If it is, flash by odin and look if root works.
If not, you've got to flash by odin the same rom again (keep your original file on pc), you'll loose nothing, and report this fails on chainfire to test other solution.
Good luck
Franky
CKR83 said:
Here is all the info that I have on my phone:
Galaxy S5 AT&T US version (SAMSUNG-SM-900A)
Android 4.4.2
kernel version 3.4.0-2178781 [email protected] #1 Tuesday July 22
Build # KOT49H.G900AUCU2ANG3
SE for Android Status
Enforcing SEPF_SAMSUNG-SM-G900A_4.4.2_0018 Tuesday July 22
Security Software version:
MDF v1.0 Release 3
VPN v1.4 Release 1
Click to expand...
Click to collapse
Not only build number and kernel version, you need to check your Bootloader version with Phone INFO ★Samsung★ app (in the FIRMWARE INFO section).
Bootloader version is one of the important info to check when you are going to root or flashing custom rom.
vndnguyen said:
Not only build number and kernel version, you need to check your Bootloader version with (in the FIRMWARE INFO section).
Bootloader version is one of the important info to check when you are going to root or flashing custom rom.
Click to expand...
Click to collapse
Hey that looks like a great utility. Thanks! The bootloader is G900AUCU2ANG3
Does that help any? People keep telling me I need to use ODIN and flash this, that or the other thing. Those comments would probably be more helpful if I knew more about this stuff, but my reading has lead me to believe that ODIN won't work with certain version of the bootloader. Or is that wrong?
CKR83 said:
Hey that looks like a great utility. Thanks! The bootloader is G900AUCU2ANG3
Did you every get your post July 2014 AT&T GS5 rooted?
If so, please drop me an email.
Thanks
TPG
Click to expand...
Click to collapse
No unfortunately not....
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app

Mission Accomplished: Flashing European ROM on the Chinese Mate 9 w/ Locked Bootloade

I've been working at this non-stop for the past week, and I've finally found a way. I am not able to flash a European ROM on the Chinese Mate 9.
I came very close to bricking my device, so I'm currently making sure of the method. Here is what it looks like:
http://imgur.com/a/1ONOF
(I am long-pressing the home button to show it's fully google-ized, in both pictures, but I took my hand out of the picture for paranoia purposes)
So, how is it done? Through eRecovery. I will release the full method once I have tested it enough for public consumption, because I don't want people bricking their devices.
How does it work? It's... interesting.
The version showing up on the phone is the last Chinese firmware which was installed. It doesn't update to show what version it is. In the imgur picture, for instance, it says B109SP01, but it's actually B115 running on it. The phone still thinks it's a Chinese phone, so if you try to get an OTA, you'll probably be getting a Chinese OTA which will not work correctly. So in that sense, it's a bastardized version, and OTAs/updates will not work normally -- You'll have to flash them through a different method.
The positive side is, Google works. Completely. It comes installed out of the gate with account sync, and so on. Other than being Google-fied, some other differences include the permissions menu, the keyboard (SwiftKey is default), and a few other things here and there. The default theme looks strange, and I think it has to do with the cust partition not matching the actual model. This is something I'm currently looking into before release. I'm also looking into using version B122 (or newer if it becomes available) instead of 115.
I'm sure many of you want to get your hands on the European firmware and the method to install it. If you're interested in testing despite one-day-old pre-beta status, shoot me a PM, and I'll try to get you hooked up. In the future, because this method will require a lot of data transfer, I'm considering charging some money to people who download it, and setting up a proper server.
Anyway, for now, know that it's possible, and if you want to do it right away, get in touch with me and I'll try to help!
Update: I have now verified that it's possible to go back to the Chinese ROM. I should have something for those who contacted me wanting to test tomorrow. Since this is a LOT of work, priority will be given to those willing to make a donation.
Although I don't have a Chinese M9 I appreciate your efforts as this opens up the way to flashing other stock and maybe even custom ROM's. Well done!
blackspp said:
Although I don't have a Chinese M9 I appreciate your efforts as this opens up the way to flashing other stock and maybe even custom ROM's. Well done!
Click to expand...
Click to collapse
Unfortunately, I think that custom ROMs will not work with this method, because they're not signed by Huawei.
Wow, That's great news.
I really appreciate your efforts.
I think that you can get a little bit of money in return for your efforts.
I would like to participate in this plan.
Please notify me when the procedure is completed.
Thanks again!
So, here's where we are at right now:
We can flash the system partition of a European firmware, no problem. There's seemingly no issue there.
Where we get the issue is when we look at the cust partition. Because we can't change the actual region of the phone from all/cn to hw/eu, for example, the cust partition has issues. What I mean by issues is, you don't get any of the default themes, various software might be missing features, and so on. Your phone's model number also appears to change from MHA-AL00 to M300-AL00 if you flash the non-Chinese cust partition. When this happens, things go crazy, and you cannot see a proper version number, build number, or model number.
I am looking into making a 'bastardized' version of something to flash, using a Chinese cust partition with an international system rom. Theoretically, this could fix the issues to an extent. It will, however, probably give you a warning upon boot-up that the system has been tampered with, and so on. I will have more information later tonight, Japan time, when I get a chance to work on it some more.
The programs which go missing on a flash of the European firmware are the following:
AutoInStallAPKFromMcc HPLegacyPlugin HwPhoneService PlayGames
Books HwCloudDrive_Local LatinImeGoogle PlusOne
ChromeHomePage HwID Newsstand PredefinedEapSim
GameBoxGlobal HwOUC OMACP talkback
Appmanager HwBetaClub Instagram_Stub Todoist
Booking HwHealthPlatform_OVE Installer Todoist_ntp
DisableTodoistReceiver HwLogUploadService NewsRepublic Twitter
Facebook_Stub HwOUCBeta ProjectMenuAct WPS
Along with all the included themes, and the auto-installer which mounts via USB when you plug the phone in.
Obviously, some of these files are more important than others. All of the things really vital to being able to use the phone can likely be loaded via a Chinese cust partition, but the versions are probably different from the european versions.
Update:
I've obtained a server and am currently setting things up to bring this to the public. The first stage will be a private test. I'm still willing to take some testers who are willing to put their phones in the line of fire! I don't think the private test will launch today, because a new International B126 ROM just came out, so I'm going to base my work off of that for now.
After all the kinks are worked out, I will develop some kind of system for the general public to use. Eventually, this system will be one where you configure your DNS to my server, log into a website, choose what firmware you want to flash, then use eRecovery and that firmware will flash to your phone. I will have to customize all of the international firmware to work perfectly on Chinese devices, and I've yet to do that, but will be working on it. If there's a need, I can expand this system to other Huawei phones. It's exciting times for Mate 9 owners.
Hi duraraa
I have just received my 128g mate 9 in France. I will be happy tomake a donation and participate to the test. Please let me know.
v.kuo said:
Hi duraraa
I have just received my 128g mate 9 in France. I will be happy tomake a donation and participate to the test. Please let me know.
Click to expand...
Click to collapse
Sure, thank you for your interest. In the meantime, if you are currently on a version like B115 or higher, please downgrade to B106 / B109SP01 so you are familiar with the process.
Update: Now that we can install Google framework on the Chinese latest firmware, I have decided to cancel this project for now. I may keep a server alive to upload to unsupported/beta firmwares, but trying to get the European firmware working well on the Chinese Mate 9 is no longer a priority.
Which version of the firmware Duraraa ?
duraaraa said:
Update: Now that we can install Google framework on the Chinese latest firmware, I have decided to cancel this project for now. I may keep a server alive to upload to unsupported/beta firmwares, but trying to get the European firmware working well on the Chinese Mate 9 is no longer a priority.
Click to expand...
Click to collapse
Hi Duraaraa.
i might have missed something... how to put the framework on? Thanks so much - looking soo much forward to have Google on my AL00 phone.
weiaoli said:
Hi Duraaraa.
i might have missed something... how to put the framework on? Thanks so much - looking soo much forward to have Google on my AL00 phone.
Click to expand...
Click to collapse
Just search for GMS in the HiApp store. Huawei released a google framework installer.
But the app twin functionality in Chinese handset only allows QQ and wechat. Please continue with finding out how we can install European Rom on Chinese handset so we can have twin app functionality for whatsapp.
ewijaya74 said:
But the app twin functionality in Chinese handset only allows QQ and wechat. Please continue with finding out how we can install European Rom on Chinese handset so we can have twin app functionality for whatsapp.
Click to expand...
Click to collapse
If I flash the European rom on the Chinese handset, it's still QQ and wechat. Strange, eh?
Yes very strange....But there must be a way to fix this right?
Mate 9 from Taiwan
Hi everyone, keeping an eye on the market I found a very tempting offer on the 64GB version - HUAWEI Mate 9 64GB 4G Dual Sim SIM FREE/ UNLOCKED .
Now, my knowledge of ROM flashing is "level: what is a ROM?", but I am reading lots on the subject , but a couple of months ago I bought a P9 for my wife, chinese Al00 version, no problems to install Google Play but still many things are in chinese, the language correction for english or other EU languages sucks. That is why I decided not to go for Chinese versions unless there were exaustive guides on how to flash the mobile to an international or better european ROM.
Said all that, I wonder if anyone has found an easy way to solve the above mentioned issues - I assume everyone with a chinese version will have similar problems - and if you solved them otherwise.
Thanks for any information you might provide, and sorry if I missed key info to have this question properly addressed, but I will be happy to add it if asked.
Cheers,
Daniele

Trying to install a rom on 950F

hi..
i recently got a 950F, but it seems i can't update it as it says "your current software version isn't supported current version G950FXXU3DSC7"
more importantly it doesn't seem to detect my hardware keyboard.
so my question is, what kind of rom can i use to install on it, that would detect the keyboard correctly
I've been using Alexis ROM for years. From my experience is the most reliable ROM for our device.
[Alexis Rom 9.3_DUD1_04/2021 Patches][13/05/2021][Ported S10 Stuffs & S9Wallpapers]
[Alexis Rom 9.1_DTJ1_10/2020 Patches][27/10/2020][Ported S10 Stuffs & S9Wallpapers] DISCLAIMER I will be aware of your problems caused by root like tripped knox... When you flash something like this you may know about the risks you are going...
forum.xda-developers.com
Rmark1086 said:
I've been using Alexis ROM for years. From my experience is the most reliable ROM for our device.
[Alexis Rom 9.3_DUD1_04/2021 Patches][13/05/2021][Ported S10 Stuffs & S9Wallpapers]
[Alexis Rom 9.1_DTJ1_10/2020 Patches][27/10/2020][Ported S10 Stuffs & S9Wallpapers] DISCLAIMER I will be aware of your problems caused by root like tripped knox... When you flash something like this you may know about the risks you are going...
forum.xda-developers.com
Click to expand...
Click to collapse
thanks, but it would seem i actually have a brand new problem, where 2 new phones, don't seem to have OEM unlock field available
emaayan said:
thanks, but it would seem i actually have a brand new problem, where 2 new phones, don't seem to have OEM unlock field available
Click to expand...
Click to collapse
Via an xda post on Google.
open the Settings, Go to General management, Date and time, Untick Automatic date and time.
New options should appear. Tap Set date and select any date from the last month, so that you can trick the system into thinking you've had the device for more than 7 days.
Back out. In Settings, go to About phone >Software information,Tap on Build number 7 times to activate Developer options. Back out. In Settings, go to the newly added Developer options;Untick Auto update system.
Back out. Go to Software update, Untick Download updates automatically.
Tap on ‘Download updates manually. An error may appear... Disregard if one does. Reboot your device. OEM unlock should be available in the Developer options.
Links posted below should help you. Start with the first one.
https://forum.xda-developers.com/t/...ll-twrp-on-exynos-samsung-after-2018.3747535/
]https://forum.xda-developers.com/ga...x-data-mount-fix-s8-twrp-oreo-t3769254/page27[/URL

Categories

Resources