LG Watch Urbane 2nd Edition Android Wear 2.0 Developer Preview (on AT&T) - LG Watch Urbane 2

Anyone have any luck getting the Google Android Wear 2.0 Developer Preview loaded on the LG Watch Urbane 2nd Edition for AT&T using the instructions at https://developer.android.com/wear/preview/downloads.html
I can get the watch to reboot into the bootloader mode, but the unlock seems to be failing...looking at the very tiny text on the bootloader about "Secure Boot" and enabled.
Does this mean that AT&T has locked the bootloader and we can't load the developer preview?
Any help would be appreciated...the features in Android Wear 2.0 look fantastic!

morgej said:
Anyone have any luck getting the Google Android Wear 2.0 Developer Preview loaded on the LG Watch Urbane 2nd Edition for AT&T using the instructions at https://developer.android.com/wear/preview/downloads.html
I can get the watch to reboot into the bootloader mode, but the unlock seems to be failing...looking at the very tiny text on the bootloader about "Secure Boot" and enabled.
Does this mean that AT&T has locked the bootloader and we can't load the developer preview?
Any help would be appreciated...the features in Android Wear 2.0 look fantastic!
Click to expand...
Click to collapse
I was able to get it installed, but I rolled it back as W2 has WAY too many issues yet. I was getting force closes on AW all over the place. Did you issue the "fastboot oem unlock"?

morgej said:
Anyone have any luck getting the Google Android Wear 2.0 Developer Preview loaded on the LG Watch Urbane 2nd Edition for AT&T using the instructions at https://developer.android.com/wear/preview/downloads.html
I can get the watch to reboot into the bootloader mode, but the unlock seems to be failing...looking at the very tiny text on the bootloader about "Secure Boot" and enabled.
Does this mean that AT&T has locked the bootloader and we can't load the developer preview?
Any help would be appreciated...the features in Android Wear 2.0 look fantastic!
Click to expand...
Click to collapse
Sure, I got it loaded on my new AT&T LG/U/2ndEd. about two hours ago. Looks good, I guess. Don't really have a reference since I loaded the Dev Preview as soon as I had enough charge to do it.
To unlock I typed "fastboot oem unlock" in the command window.

dotnetguyaz said:
I was able to get it installed, but I rolled it back as W2 has WAY too many issues yet. I was getting force closes on AW all over the place. Did you issue the "fastboot oem unlock"?
Click to expand...
Click to collapse
I did try "fastboot oem unlock" which hung at waiting for device. I'll give it another go, maybe from a different computer
Given the issues mentioned, and some of the bugs I saw listed in the official bug tracker, it does sound like it's still a bit early for a daily driver
Sent from my SM-N910V using Tapatalk

wrong bootloader version NEMOZ10r
I have an AT&T unlocked LG Urbane 2nd edition (purchased ~4 weeks ago)
When I try and flash with the Android Wear 2.0 preview image, I see this:
$ ./flash-all.sh
target reported max download size of 268435456 bytes
sending 'bootloader' (1867 KB)...
OKAY [ 0.170s]
writing 'bootloader'...
FAILED (remote: not supported in locked device)
finished. total time: 0.173s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
target reported max download size of 268435456 bytes
sending 'radio' (36897 KB)...
OKAY [ 1.274s]
writing 'radio'...
FAILED (remote: not supported in locked device)
finished. total time: 1.277s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
Creating filesystem with parameters:
Size: 3064987648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 11692
Label:
Blocks: 748288
Block groups: 23
Reserved block group size: 183
Created filesystem with 11/187312 inodes and 24558/748288 blocks
Creating filesystem with parameters:
Size: 67108864
Block size: 4096
Blocks per group: 32768
Inodes per group: 4096
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 16384
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/4096 inodes and 1294/16384 blocks
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
wiping userdata...
wiping cache...
--------------------------------------------
Bootloader Version...: NEMOZ10r
Baseband Version.....: M8926-4.0.06.0.09
Serial Number........: 603KPSL029398
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
FAILED
Device version-bootloader is 'NEMOZ10r'.
Update requires 'NEMOZ20c'.
finished. total time: 0.019s

morgej said:
I did try "fastboot oem unlock" which hung at waiting for device. I'll give it another go, maybe from a different computer
Given the issues mentioned, and some of the bugs I saw listed in the official bug tracker, it does sound like it's still a bit early for a daily driver
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Try "fastboot devices" & see if you have a good connection

roebling said:
Try "fastboot devices" & see if you have a good connection
Click to expand...
Click to collapse
Thank you very much!
I ran "fastboot oem unlock" and was able to flash the Wear 2.0 Preview!
As an Android developer I am very interested to check this out..

LeeHounshell said:
Thank you very much!
I ran "fastboot oem unlock" and was able to flash the Wear 2.0 Preview!
As an Android developer I am very interested to check this out..
Click to expand...
Click to collapse
Ditto here. Shall we make this the place for posting issues with this watch & with developing on it? I haven't found anyplace else on xda-developers

I installed Chrome on this preview and it works pretty damn good

"Cellular network not available"
About noon today my phone quit making calls, reporting "Cellular network not available." After an hour on (another) phone with one of AT&T's top customer service reps, Abdul in Schratchassistan, we were able to determine absolutely nothing. He did suggest, several times, that I needed to buy more time. I am three days into their $45-a-month, unlimited talk & text plan. But, to AT&T and Abdul in Schratchassistan, three days is about how long a month's subscription should last.
I was just wondering, has anyone else been disconnected since upgrading to the new Android Wear?
Edit 0525: I left the watch off overnight &, when I turned it on the next morning, it worked.

Anyone know why my att prepaid sim isn't working? I just got the watch and have had zero luck getting it to activate the cellular

WARNING! I tried Wear 2.0 Preview and went back to the stock firmware provided by Google. My watch battery is drained 2-3 times faster now than before!!!

The battery drain is probably from an app or watch face. I have my brightness cranked to 9 and I've had great battery life so far.
On another note:
UC Mini works fantastic Honestly never imagined I'd be scrolling around websites on a watch so much...
Sky maps works if you get a location in maps first, kinda cool using it on a watch. Some of the functions are obviously impossible to use but you can move your wrist around and check out the stars.
Sent from my STV100-1 using XDA-Developers mobile app

smatofu said:
WARNING! I tried Wear 2.0 Preview and went back to the stock firmware provided by Google. My watch battery is drained 2-3 times faster now than before!!!
Click to expand...
Click to collapse
This is all I wanted to know, thanks. I guess I will wait for at least a beta.

smatofu said:
WARNING! I tried Wear 2.0 Preview and went back to the stock firmware provided by Google. My watch battery is drained 2-3 times faster now than before!!!
Click to expand...
Click to collapse
Coming from a Samsung Gear S, I'm loving battery life on my new LG Urbane 2nd LTE. And, yes, I put Android Wear 2.0 on it as soon as I got it home.
Did have an issue with the AT&T prepaid service that AT&T sold me. Two hours on AT&T's "Customer Service", first with robo-tech & then with Abdul in Skretchassistan did nothing to help. Left it turned off overnight & in the morning it was "healed". Makes calls without being tethered to my smart phone now, and the battery lasts a day and a half.

Only thing I'm really having issues with so far is the LG health app, otherwise i haven't ran into any issues at all. Also i love the new keyboard.
Sent from my LG Watch Urbane using XDA-Developers mobile app

Have you solved the draining issue? I had too flashed the stocked firmware after un satisfaction from wear 2.0 and now battery couldn't get through a day

Carrot0080 said:
Have you solved the draining issue? I had too flashed the stocked firmware after un satisfaction from wear 2.0 and now battery couldn't get through a day
Click to expand...
Click to collapse
I tried Wear 2.0, then I restored 'stock' firmware provided by Google twice. My battery life is half of what it was before. Big regrets for going through the 2.0 Preview.

So you guys think jumping to the preview is a bad idea? What have you the poor experience? Apps not working or performance?
Sent from my Nexus 6 using XDA Free mobile app

So I flashed the preview.. honestly I have no gripes. In a little more than a day only crashed on me once. And all the apps I use work fine.
Sent from my Nexus 6 using XDA Free mobile app

Related

[Q] What kernel and WebOS ver. Are you using?.

This thread is for see What Kernel and WebOS version are you using, how buggy is it.
I use WebOS ver. 2.1.0. And I'm using SR71 Blackbird Kernel. I have to make resets every 2/3 days, and sometimes when i'm playing music it gets freeze!.
Patches: 25
App Installed: 34
Linux App: 13
Web Server running over 3G.
Windows 95/98 on Sleep mode.
Booting time: 2.4 mins complete.
Temp.: 22º-45º (Normally 31º)
Now let's see your WebOS Device
I've got webOS 1.4.5. I don't know what kernel, default one for my Pre- I guess. I reset only to swap to my spare battery, not because of freezes. I think that's usually once a week, although it has been every day at times of heavy usage.
Patches: 29
App Installed: 46
Linux App: 5
Booting time:
Temp.: 30ºC
Jive Turkey said:
I've got webOS 1.4.5. I don't know what kernel, default one for my Pre- I guess. I reset only to swap to my spare battery, not because of freezes. I think that's usually once a week, although it has been every day at times of heavy usage.
Patches: 29
App Installed: 46
Linux App: 5
Booting time:
Temp.: 30ºC
Click to expand...
Click to collapse
Nice!. I know someone who never reset his Pre Minus like for a year.
Palm Pre + (at&t)
WebOS ver 1.4.5
UberKernel
Govnah 1.03 @ 720-1ghz 27-40
Preware 1.7.0
Patches: 8
Theme: Stickers
I dont need to reset, but i do once a week just habit.
Would like to try 2.0, but seems like a big hassle for very little improvement.
Love WebOS! still waiting patiently for the Pre3
Cptnjarhead said:
Palm Pre + (at&t)
WebOS ver 1.4.5
UberKernel
Govnah 1.03 @ 720-1ghz 27-40
Preware 1.7.0
Patches: 8
Theme: Stickers
I dont need to reset, but i do once a week just habit.
Would like to try 2.0, but seems like a big hassle for very little improvement.
Love WebOS! still waiting patiently for the Pre3
Click to expand...
Click to collapse
Nice =). My mom's Pre plus, she do a reset like monthly. And you should try WebOS 2.x.x, but well is your selection , Have a nice day.
Thanks
I would like to try 2.x.x but, according to internals, my pre + would still be registered as a 1.4.5 so i couldnt download apps for 2.x.x unless they were homebrew. I just read an article today about HP locking out palm devices upgraded to 2.x.x from accessing the cloud, back up, restore and other functions. I think i will wait for the pre3.
I will be getting a TP in the next month. very excited.
Cptnjarhead said:
Thanks
I would like to try 2.x.x but, according to internals, my pre + would still be registered as a 1.4.5 so i couldnt download apps for 2.x.x unless they were homebrew.
Click to expand...
Click to collapse
We're working on a solution to that.
-- Rod
i figured as much.
i dont know if i will be able to wait for my contract to be up, to get a Pre3.
Rumor is the end of August.. i have to wait till next year
TravisAntonio said:
This thread is for see What Kernel and WebOS version are you using, how buggy is it.
I use WebOS ver. 2.1.0. And I'm using SR71 Blackbird Kernel. I have to make resets every 2/3 days, and sometimes when i'm playing music it gets freeze!.
Patches: 25
App Installed: 34
Linux App: 13
Web Server running over 3G.
Windows 95/98 on Sleep mode.
Booting time: 2.4 mins complete.
Temp.: 22º-45º (Normally 31º)
Now let's see your WebOS Device
Click to expand...
Click to collapse
palm pre minus
webOS 1.4.5
kernel F105 thunder chief ( worked good for a while but then i couldnt connect to the sprint network) ( but when i went back to the default palm webOS 1.4.5 kernel WiFi doesn't work, but i had the sprint network back)
app installed: 131
linux app: 4
patch :32
boot time: 4 min
when you say "reset" do you mean with webOS doctor or just doing a reboot?
Just a reboot

[SC-04E] Japan NTT DoCoMo Galaxy S 4 Users

Mod edit: This thread is for the country specific hardware relase of S4 in Japan. The hardware is different and there are couple of things which require different treatment regards rooting, flashing etc.
No trolling/flaming shall be tolerated here. Users of this thread are requested to report posts and avoid engaging in such.
I will try to update this original post as often as I can with information once that information is deemed reliable and working.
[Root Guide SC-04E]
See post #3 below for all the rooting details.
[Tips, Tricks & Tweaks SC-04E]
Use Tasker to auto connect to Wi-Fi without using GPS - http://forum.xda-developers.com/showthread.php?p=41757436
Turn your volume rocker into a track selector.
[Themes for the SC-04E]
Reserved
[ROMs for the SC-04E]
Some cooked ROMs for you to test out.
Remember, install these at your own risk. We are not responsible if you mess up your phone.
SQ3.0dotJP said:
https://www.dropbox.com/s/ptcgciylssqxjef/JP_SC04E_JB_mr1_Illusion-Complete.zip
no, cam but video works, strange right? not sure if its the ROM wich is an alpha 1 or if I should run it through the new cooker, i cooked this with that last version of the cooker. but ive been running it for like a week and dont miss the cam
http://forum.xda-developers.com/showthread.php?t=2316308
all credit to @itsmikeramsay and his team
Heres revolt, cooked, https://www.dropbox.com/s/o8kezcpp7r8g4or/JP_SC04E_JB_revolt_Complete.zip
Click to expand...
Click to collapse
i cooked a little ROM called Xylon....it is pretty freakin sweet...i was kinda bummed about loosing nfc and the samsung camera but the pics the aosp cam on this are pretty darn good, and there is away to get the nfc working just haven't fully tracked it down...the ROM is small and really quick...it also included Halo, Pie and Ribbons....heres the link to the thread...im going to upload the ROM here for the OP but you also have to download and flash the specific gapps posted in the original thread....
http://forum.xda-developers.com/showthread.php?t=2320997
[Accessories for the SC-04E]
Reserved
[Cancelling Docomo paid apps like NOTTV for the SC-04E]
I just figured out how to cancel NOTTV -
Just so you know - when you sign up for Docomo service they throw anywhere from 5-10 apps that they you have to add in order for the contract to go into effect or something like that.
Anyways, a day or two after you sign your contract, you can cancel all of the apps without any problem and never have to worry about them again. Of course, with the exception of NOTTV. You actually have to go into dMenu (Docomo menu) to start this cancellation process.
Here are the instructions in Japanese if you understand them -
Japanese instructions to turn off/cancel NOTTV
The English instructions are as follows:
First open the above link as that page actually has images that I'm not going to post here that show the procedure.
Just go to this link - on your phone using the stock browser. http://sp.nottv.jp/support/help/#procedure or Click here
Once on that page you will see the following Japanese text 各種手続きについて - it's the 2nd Pink heading down the page.
Near the bottom of that you will see the following Japanese text NOTTVの解約方法について教えてほしい。(How to cancel NOTTV is basically what it says.) then you will see a list of instructions open up and near the bottom of those instructions there will be a link in Japanese text that says 2. NOTTVスマートフォンサイトからこちらから. Click that link on your phone - the link won't work here.
Then when the next page opens on the bottom will be a black button - click it.
Then a page with two black buttons on it will appear. Click the top one that says in Japanese text ドコモケータイ払い.
This will take you to your docomo login page on which you must login your phone number and docomo password.
Then it will take you to the payment page and you will see a transaction number at the top and a big black button that says in Japanese text 解約.
Once you click that you will be cancelled. It will ask you to fill out some survey. If my English steps do not work please have a Japanese friend walk you through the other site's walk-through.
Hope this helps anyone who needed it.
A little more info if you have trouble is here.
[Root guide for Docomo Samsung Galaxy S4 SC-04E]
Everyone's favorite topic.
There are a few members working on this now.
Some have used other methods that have worked but nothing foolproof that always works has been done yet.
If you have the MF1 update and want to root then use the gs4eXT method posted further down into this forum.
It does appear that you can also root using that method with the MF2 update but it is a very limited root. Titanium Backup won't work, you can't flash any other ROMs, maybe other things too. So for me, rooting at this time is not yet an option.
I'm sure this will change soon. Somebody will figure something out.
[ML2 update root guide]
coming soon...
[MF2 update root guide]
I'm on MF2. Root works. Titanium Backup works.
Here are the exact steps that I took:
1. Restore factory image (MF2 in my case)
2. Install Android Terminal Emulator.
3. Install GS4eXT (paid)
4. Opened Android Terminal Emulator. Left it at that.
5. Hit menu, then went to open GS4eXT
6. f**k the device. Yes. Yes.
7. When the process finished, my last message was only "sorry too much. [email protected]:/$"
My phone did NOT display "Please reboot manualy operation."
8. I pressed the power button, and clicked on Restart.
9. System restarted, and then a message popped up in Japanese asking if I wanted to install Superuser. Yes. Open.
10. Back to the Play Store, I then installed Super SU. Open. Super SU will say that there are other programs using root access, and will ask to uninstall those other programs. Hit Cancel.
11. Installed Titanium Backup.
Notice: Titanium was granted root via SU via Superuser. So Superuser is granting Super SU root. And in turn, Super SU granted Titanium root. Sounds weird, but you'll see what I mean.
Test Conducted: Installed a backed up app and data from my last phone. Success! All my saved files were included in the restoration process.
I restarted my phone. It booted as normal.
Opened my restored app. Everything worked as normal.
Opened up Titanium, but had it was looking for root access. I had to open Super SU back up again. After that, I went back to Titanium, and root access was granted once again.
After I uninstall all my bloatware, I'm going to try updating the phone and see if it keeps root (or see if I can root again after the update).
Thanks a million!
Another root guide from cezeff
Flashed the CM 4.4.1 and having no problems...cam and video working fine...one thing i found out is to be on the super safe side be sure to flash in order...
1. be rooted on either a rooted stock or another aosp rom
2. ensure you have the cwm 6.0.4.5 flashed as your recovery....its easy, just flash the tar via Odin
3. download and copy the 4.3 slimbean, CM11 and/or AOSP 4.4.2 to and sd card and place in your phone...just do this before you boot into recovery.
4. i advise downloading the gapps provided by pa and copy that you your sc card too....you can choose from either the full, core or bare minimal gapps...plus you can flash the cam separate too with photosphere... http://forum.xda-developers.com/showthread.php?t=2397942 theres the link
5.boot into recovery, do a full wipe
6. install 4.3 Slim Bean
7. wipe again... then install either CM11 or AOSP, then flash the gapp package
8. wipe cache, and davilk then reboot
9. let sit for 10 minutes reboot
i had flashed the 4.4.2 but ran into reboot problems...probably because i jumped ahead and didnt flash in order....this is just a rough guide....
Another ROM
SeeYou has released a stable 4.4.2 CM 11.0 ROM. I have flashed it and have experienced no issues.
http://bbs.shendu.com/thread-2661689-1-1.html
I just got a normal black tpu case off of ebay with a screen protector. Nothing fancy check the link below.
http://www.ebay.com/itm/Black-Grip-...t=US_Cell_Phone_PDA_Cases&hash=item4172b06d3e
rushter said:
Starting this today. I ordered my S4 from Docomo yesterday.
Click to expand...
Click to collapse
Thanks for starting this.
Ordered mine last week too, looking forward to Thursday when I pick it up - currently on the SC-02C.
As for root, the Motochopper exploit should work I guess...
SC-04E has only Felica secure element internally, but is being supplied with an NFC-A secure element on the (pink) SIM card.
This is sneaky shibari lock-in on Docomo's part - it forces you to keep your Docomo SIM in when overseas if you want to do contactless payment on the Mastercard NFC-A terminals. Well played Docomo, well played...
I'm still on the wall on whether or not to get it, feels uncomfortable in my hands (too wide) and the SO-04E Xperia A (which will be sold elsewhere as the ZR) feels so much better.
evildave_666 said:
SC-04E has only Felica secure element internally, but is being supplied with an NFC-A secure element on the (pink) SIM card.
This is sneaky shibari lock-in on Docomo's part - it forces you to keep your Docomo SIM in when overseas if you want to do contactless payment on the Mastercard NFC-A terminals. Well played Docomo, well played...
I'm still on the wall on whether or not to get it, feels uncomfortable in my hands (too wide) and the SO-04E Xperia A (which will be sold elsewhere as the ZR) feels so much better.
Click to expand...
Click to collapse
Every phone feels different though with a case on it as well. It feels the same to me as my gs3 ,so no complaints from me.
Swaf said:
Every phone feels different though with a case on it as well. It feels the same to me as my gs3 ,so no complaints from me.
Click to expand...
Click to collapse
S3 without case is same width as my S2 with case, which already feels too big for my hand.
Got it!
Ok, picked it up this morning. :good:
Very nice, its a touch bigger but curved enough to not feel too big.
Will set it up tonight. Pulled the SIM out and stuck it back in the S2 for now (used a 90YEN Sim Card adapter to make it fit) good to know that even after changing to the contract to use the Xi (LTE) network it still works fine in the S2 - Though now I have a 3GB monthly limit on data... (chose the 3GB lite plan for now)
Dothraki said:
Ok, picked it up this morning. :good:
Very nice, its a touch bigger but curved enough to not feel too big.
Will set it up tonight. Pulled the SIM out and stuck it back in the S2 for now (used a 90YEN Sim Card adapter to make it fit) good to know that even after changing to the contract to use the Xi (LTE) network it still works fine in the S2 - Though now I have a 3GB monthly limit on data... (chose the 3GB lite plan for now)
Click to expand...
Click to collapse
Cool! Hopefully we get a root soon. Yeah I switched to the 3gb data plan a while back since I barely even use 1 gb a month. Wish they had smaller plans ,but owell.
Anyone tried the unlock method from here (through service menu)? Success or fail?
So I picked mine up today. The amount of bloat on the thing annoys me quite a bit. I can't wait for the bootloader to be cracked wide open so I can flash to stock.
I have a simple use question though that I'm a little confused on. I've got Mobile Suica installed now and I've never used it before, since my last phone was a S2. Do I have to have an app running when I touch it to the readers? Does the Reader/Writer, P2P setting need to be turned on to use it?
evildave_666 said:
Anyone tried the unlock method from here (through service menu)? Success or fail?
Click to expand...
Click to collapse
Be a bit more specific. Lol. I'll try it.
DoCoMo Unlimited Plan not Unlimited [Fix]
OK I got my phone today, now what?
I hate the new data plans, just setting up my phone used 500mb in data alone today.
So I found a solution that works without rooting the phone to help us former "unlimited-plan" users still think we are on an unlimited plan.
It's super easy but, unfortunately, not free. Most of the Android users I know already know about this app.
Basically, I set it to automatically turn on the WiFi and connect to your home network without using GPS. And also when you leave home it shuts WiFi off and puts you back on data.
One you learn how to use it for one location, you'll start doing it for every location you go to that has a free WiFi connection (i.e. - Starbucks, etc.)
If anyone gets the app or already has it, let me know and I'll post further instructions
https://play.google.com/store/apps/details?id=net.dinglisch.android.taskerm
But well worth the $2.99.
#confirmed
CF autoroot for i9505 works, i just did it, now to remove this bloat
http://forum.xda-developers.com/showthread.php?t=2219803
looks like you will lose NFC and stock recoveryfunctions though. SU wont update the binary but apps requiring root access like TiBu read as rooted. will update with more info after more playing if i find out anything else.
edit: Well seems more not rooted than rooted. while some apps function many do not or only work partially. guess ill wait around for the stock image and restore unless somone finds something out before then
rushter said:
Be a bit more specific. Lol. I'll try it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2282683
---------- Post added at 09:44 AM ---------- Previous post was at 09:37 AM ----------
rushter said:
OK I got my phone today, now what?
I hate the new data plans, just setting up my phone used 500mb in data alone today.
So I found a solution that works without rooting the phone to help us former "unlimited-plan" users still think we are on an unlimited plan.
It's super easy but, unfortunately, not free. Most of the Android users I know already know about this app.
Basically, I set it to automatically turn on the WiFi and connect to your home network without using GPS. And also when you leave home it shuts WiFi off and puts you back on data.
One you learn how to use it for one location, you'll start doing it for every location you go to that has a free WiFi connection (i.e. - Starbucks, etc.)
If anyone gets the app or already has it, let me know and I'll post further instructions
https://play.google.com/store/apps/details?id=net.dinglisch.android.taskerm
But well worth the $2.99.
Click to expand...
Click to collapse
Another good alternative is to use NFC tags to trigger things like that.
anyone pull a stock image of the ROM yet?
@SQ3.0dotJP the flashing process went just fine but when I go into try to use SU and update the binary, it fails to update and Root checker shows my device is not rooted....were you able to get yours fully rooted?....we should send a message in the Auto-Root form to try and be sure we get officially supported....
Can the O.P. start modifying this thread to reflect to create a rooting/rom flashing guideline as was done with the SC-06D on this page .... http://forum.xda-developers.com/showthread.php?p=41770156#post41770156
Thanks!
cezeff said:
anyone pull a stock image of the ROM yet?
@SQ3.0dotJP the flashing process went just fine but when I go into try to use SU and update the binary, it fails to update and Root checker shows my device is not rooted....were you able to get yours fully rooted?....we should send a message in the Auto-Root form to try and be sure we get officially supported....
Can the O.P. start modifying this thread to reflect to create a rooting/rom flashing guideline as was done with the SC-06D on this page .... http://forum.xda-developers.com/showthread.php?p=41770156#post41770156
Thanks!
Click to expand...
Click to collapse
i just tried to update the binary and got the same error, weird because TB works and other apps requiring root..so far. did you mail the dev for CF, looks like a partial root if anything. but I havent lost any functionality aside from the normal osaifu and 1seg like with the GS3. i wont attempt a recovery install until the stock image gets posted on sammobile
Are you asking for a sub forum thread in here about rooting?
Sent from my SC-04E using XDA Premium HD app
I chose that same plan for now but when I set the phone up yesterday, I used 20 percent of that limit in one day. Lol.
Sent from my SC-04E using XDA Premium HD app
Dothraki said:
Ok, picked it up this morning. :good:
Very nice, its a touch bigger but curved enough to not feel too big.
Will set it up tonight. Pulled the SIM out and stuck it back in the S2 for now (used a 90YEN Sim Card adapter to make it fit) good to know that even after changing to the contract to use the Xi (LTE) network it still works fine in the S2 - Though now I have a 3GB monthly limit on data... (chose the 3GB lite plan for now)
Click to expand...
Click to collapse
I chose that same plan for now but when I set the phone up yesterday, I used 20 percent of that limit in one day. Lol.
Sent from my SC-04E using XDA Premium HD app

New P8 Max 3/32 Gb.

Finally received my New P8 Max DEV-703L....
Last week looking forward for the pkg. to arrive from China
I was reading very concerned every post every thread every comment
How to Root how to flash new ROM how to UnLock Bootloader etc. etc. etc. ......
Will i be able to make it work ???
So far it arrived boot on in seconds installed with P028 ROM with Google Play Store
Perfect working, disabeling some Chinese apps. installing my apps. every function perfect.
Few moments after connecting to Wi Fi an UPDATE version alert shows on beeing prepared
for a "forced update" with the "update.app" in the "dload folder" on the root of a 32 Gb. class 10
formated Sandisk SD card i took the chance to perform the OTA update knowing i am going to "brick" it .....
Surprize BIG surprize !!! it downloaded some 61Mb. from some slow server rebooted updated and booted on,
everything working NoW it is on B029 hopping some day it will go to Android 6.X.X .....
Thanks to all firends / members for theirs work
Michael M. Marcus.
Hi, may i know after the OTA (i assumed yours are 703L), did the Play store & multi language remain?
retaliate said:
Hi, may i know after the OTA (i assumed yours are 703L), did the Play store & multi language remain?
Click to expand...
Click to collapse
Yes it is 703L, after OTA to B029 all GAPPS and multilanguage working perfect There is only one function stuck to Chinese "Data Traffic Management" on settings it does not show my real data provider but only Chinese towns and Providers although it is displaying the real data consumed.
After about 10 days of intensive use i am happy choosing P8 Max it is working very good special in multi tasking not even one failure (need to reboot or shut down).....
mmarcus10 said:
Yes it is 703L, after OTA to B029 all GAPPS and multilanguage working perfect There is only one function stuck to Chinese "Data Traffic Management" on settings it does not show my real data provider but only Chinese towns and Providers although it is displaying the real data consumed.
After about 10 days of intensive use i am happy choosing P8 Max it is working very good special in multi tasking not even one failure (need to reboot or shut down).....
Click to expand...
Click to collapse
Can you please comment on the black/color on the display? Are they really black/deep? Also, how is the frame/refresh rate?
gideonMorrison said:
Can you please comment on the black/color on the display? Are they really black/deep? Also, how is the frame/refresh rate?
Click to expand...
Click to collapse
All colors look perfect no complains on frame refresh rate

Mate 9 Pro Daydream

I've updated my L29-c636 to the latest 181 version. I see that daydream vr been installed, so I bought the Daydream View headset. Went through the setup process, only to find that I get a black screen when I'm told to put the phone in the vr headset. Daydream seems to be working partially as I can hear some birds from the phone's speakers. I can increase or decrease the volume using the remotre, and there is an x and settings cog in either of the upper corners. Other than that though, nothing, nada: black screen only.
Anyone else have a similar experience?
I have LON-L29C721 and no update available Anybody else ?
Try firmware finder, it seems like 181 is authenticated.
I used firmware finder app to upgrade to LON-L29C636B181 (still on locked bootloader), which worked fine. No Daydream VR controller yet, so couldn't get past the controller pairing menu.
Cool, if you do get one, see if you can view something. Btw, I read someone had used another phone to simulate the controller, not sure if it's genuinely possible though.
drdino said:
I've updated my L29-c636 to the latest 181 version. I see that daydream vr been installed, so I bought the Daydream View headset. Went through the setup process, only to find that I get a black screen when I'm told to put the phone in the vr headset. Daydream seems to be working partially as I can hear some birds from the phone's speakers. I can increase or decrease the volume using the remotre, and there is an x and settings cog in either of the upper corners. Other than that though, nothing, nada: black screen only.
Anyone else have a similar experience?
Click to expand...
Click to collapse
how did you get 181 to download with firmware finder?
I only see 2 OTA's for 181, not a full file..
thanks
With firmware finder proxy. Selected the ota, changed the proxy settings as the app dictates and used the phone's menu to search for an update. As soon as it started downloading, I removed the proxy settings.
thanks; I didn't think of switching to the "system" update option once it started to download, but I did, and now its downloaded it and it installed B181 perfectly!..thanks again:good::good::good:
LON-C636 here. I tried both OTA updates on Firmware Finder and them both gave me "Authentication failed" dialog
Seems that it's rolling out in phases again
yfnew said:
LON-C636 here. I tried both OTA updates on Firmware Finder and them both gave me "Authentication failed" dialog
Seems that it's rolling out in phases again
Click to expand...
Click to collapse
Same here... and its annoying to have to keep trying it and fail - chewing up heaps of bandwidth... i guess im just impatient lol. My FF shows 3 different updates.. one that says "FullOTA-MF" which is 2.353gb and then two smaller ones (509mb and 615mb) which just say "OTA-MF".. its strange they have 2 differing smaller ones.. either way I have tried all 3 of these, and none work yet.
Called Huawei UK support and they said that all updates including the daydream support rols out in CHINA followed by USA, followed by Western Europe and then all others. There can be up to 7 days delay between regions. Ah well..
Ok, i tested LON-L29C636B181 with Daydream view and saw the same result as drdino, aka: everything looks good up to the point when it asks to insert the phone into the viewer. The background just stays black and does not start to show the video. Foreground is just the white separator bar, X and settings icon.
If i quickly switch off/on the phone, then i will see a quick blink of the VR video, so this seems to be some rendering problem.
Not sure what i could still do myself - except factory reset. But i do not dare because right now i do depend a lot on the phone (no good backup phone at the moment).
Given how i have an overseas model, i have not yet found a way to effectively complain to Huawei. I had contacted Huawei on the US once about the mate 9 pro (different issue), but they refused politely given how they do not sell it.
I did open a case with google though, not sure if that helps. Daydream app -> Settings (VR Settings) -> Help -> Contact Us -> Call
Google promised to send me an email about the case i opened with them, but i have not yet received any email. Maybe others here with the same problem on the Mate 9 Pro could also call up google, maybe someone will succeed bringing this problem to someones attention.
Same here, I chatted with Google for about an hour, and reached the same result, i.e. they will email me.
I think it's a display rendering issue, as I can see the momentary flicker as well.
An additional issue that I discovered is that the phone's nfc reader is on top, above the camera, whereas the headset's nfc tag is in the middle of the flap. For what it's worth, I copied an nfc tag and stuck it on the leftmost side of the flap but got the same result.
To replicate the flicker, you can try sticking the phone on top of the headset's nfc tag, it's reproducible maybe 4/10 times.
buntyji said:
Called Huawei UK support and they said that all updates including the daydream support rols out in CHINA followed by USA, followed by Western Europe and then all others. There can be up to 7 days delay between regions. Ah well..
Click to expand...
Click to collapse
I am not even aware of any official USA or north-america versions of Mate 9 Pro or Mate 9 Porsche. All i can see are just overseas versions. This article https://www.androidheadlines.com/2017/03/huaweis-mate-9-pro-finally-supports-daydream.html also claims "Google also reiterates that the Mate 9 Pro and the Mate 9 Porsche Design are both available in the U.S., the UK, Germany, Australia, and Canada". WTF ?!
drdino said:
An additional issue that I discovered is that the phone's nfc reader is on top, above the camera, whereas the headset's nfc tag is in the middle of the flap. For what it's worth, I copied an nfc tag and stuck it on the leftmost side of the flap but got the same result.
Click to expand...
Click to collapse
Interesting. I did not even knew that the VR viewer has an NFC chip . Yeah, playing around with it, the reader in the mate 9 pro can not read it when it is inside the viewer, but only when you match up the locations of the reader and the chip. Funny.
te36 said:
I am not even aware of any official USA or north-america versions of Mate 9 Pro or Mate 9 Porsche. All i can see are just overseas versions. This article https://www.androidheadlines.com/2017/03/huaweis-mate-9-pro-finally-supports-daydream.html also claims "Google also reiterates that the Mate 9 Pro and the Mate 9 Porsche Design are both available in the U.S., the UK, Germany, Australia, and Canada". WTF ?!
Click to expand...
Click to collapse
LOL think that article is misinformed.. we definitely do NOT have the Mate 9 Pro for sale here in Australia, and when people asked on the Official Twitter / Facebook pages, Huawei AU responded to say it would not be sold. The Porsche Design however, did make a minor appearance here in Australia - Huawei AU did a Auction to raise funds for a charity, in which case they auctioned off 1 (yes ONE) "Limited Edition" Porsche Design Mate 9. We only have the Mate 9 as officially sold here in AU. Believe the same in USA? (or possibly you get the PD there in USA too?)
On Firmware Finder's website I found LON-L29C721B180 where the changelog says that "This update adds Daydream and optimizes system performance and stability." Not sure if this version is authenticated yet, however.
yfnew said:
On Firmware Finder's website I found LON-L29C721B180 where the changelog says that "This update adds Daydream and optimizes system performance and stability." Not sure if this version is authenticated yet, however.
Click to expand...
Click to collapse
LON-L29C721B180 is for PD.
Believe some users have mentioned on PD forums they have managed to install it, and some others failed to install (auth failed).. But as per posts above the Daydream maybe not work and gets black screen when they try to add the device into the VR headset - would think the PD would have the same issue...
buntyji said:
Called Huawei UK support and they said that all updates including the daydream support rols out in CHINA followed by USA, followed by Western Europe and then all others. There can be up to 7 days delay between regions. Ah well..
Click to expand...
Click to collapse
It's very interesting to see people just get this issue after B181 OTA. I am using LON-AL00C00B175 and found this issue since updated. So it's like couple weeks ago when Google hasn't announced M9P is daydream ready. Also, my friend in Huawei dev team told me Chinese version of M9P wouldn't get daydream support soon. So let's wait and see.
It was B181 that brought daydream support to the International Mate 9 Pro.

[Donate to k4y0z and xyz`] BL UNLOCK, TWRP image for Fire HD10 (2019, Maverick)

We donated to @k4y0z and @xyz` to create a TWRP images, exploit packages for bootloader hacking to unlock and rooting with Magisk. The exploit packages file is amonet-maverick.zip or kamakiri-maverick.zip (only works on patched Linux distributions).
Fire HD 10 2019 specs/bug status:
- Android: 9 Pie, SDK 28
- USB-C (with UART pin)
- Generation: 9th
- Model: KFMAWI
- Codename: Maverick
- CPU/SoC: MediaTek MT8183 Octa-core
- Test points: Nothing to show. Post the picture of the Fire HD 10 test points
- ADB debugging: Working, Fastboot not working on USB-C adapter
- Developer Options unlocked: Gets unlocked
- Bootloader unlock/TWRP (Hack): Not tried
- Mtk-su temporary root from @diplomatic: Tried, it's blocked.
- LauncherHijack/Launcher Replacement: LauncherHijack (modified package name) is working fine but delays at the Fire Launcher in few seconds to goes into selected launchers when pressing home button. We recommend to unblock the original LauncherHijack by uninstalling Arcus Android Client app (com.amazon.nimh)
- Benchmarking: Benchmarked with AnTuTu (crahing sometimes because is the bloatware), 3DMark, Geekbench
- Android System/framework-res.apk modifications: Not tried
- Google Services installition: Working fine
- Google Sound Amplifier: Not tried
- Google Assistant: Working fine
- Tools from @Datastream33: Created
- Digital Wellbeing: Not tried
- Adaptive battery: Not tried
Please post the bug tests because isn't tried.
Updated in 12/04/2019
FYI - I got $10 for an oldddddd Fire 7 trade-in AND a $20 coupon on a new tablet. So new Fire 10 could be as low as $120.
murph said:
FYI - I got $10 for an oldddddd Fire 7 trade-in AND a $20 coupon on a new tablet. So new Fire 10 could be as low as $120.
Click to expand...
Click to collapse
And if you wait a month till Black Fri, it will be $100!
I got one. LauncherHijacker works (use the renamed one), however it seems that Amazon's new battery system kills it after a while. I use FNG and set a swipe up to take me to nova launcher rather home. Widgets can be enabled without any work arounds. Google Play services can be sideloaded. Google Assistant can replace Alexa natively via developer settings.
CPVideoMaker said:
I got one. LauncherHijacker works (use the renamed one), however it seems that Amazon's new battery system kills it after a while. I use FNG and set a swipe up to take me to nova launcher rather home. Widgets can be enabled without any work arounds. Google Play services can be sideloaded. Google Assistant can replace Alexa natively via developer settings.
Click to expand...
Click to collapse
I've had limited success with the renamed LauncherHijacker. My bluetooth keyboard stops working when it's enabled and it seems a little off when hitting the home button. Whenever I hit mine, it goes to the normal fire launcher, sits for a few seconds then launches nova. Maybe lag or if it's having to cold start the launcher?
Installed the latest google play packages. Also installed Youtube Vanced. Had to use not the newest release but the second newest release. Whenever installing MicroG w/ Youtube Vanced, whenever it tries to interact w/ the google accounts it crashed almost immediately. Installing the previous version I got everything working.
Nemesis02 said:
I've had limited success with the renamed LauncherHijacker. My bluetooth keyboard stops working when it's enabled and it seems a little off when hitting the home button. Whenever I hit mine, it goes to the normal fire launcher, sits for a few seconds then launches nova. Maybe lag or if it's having to cold start the launcher?
Installed the latest google play packages. Also installed Youtube Vanced. Had to use not the newest release but the second newest release. Whenever installing MicroG w/ Youtube Vanced, whenever it tries to interact w/ the google accounts it crashed almost immediately. Installing the previous version I got everything working.
Click to expand...
Click to collapse
Yeah I had the issues with volume and such, so I got rid of it. For microG, you need to disable the battery optimizing from settings.
Loading greatness....
I can't wait for TWRP to come out for this tablet. I personally haven't bought one yet until TWRP Recovery is out. I also am waiting for Black Friday and Cyber Monday for this tablet to go on sale, then I'll buy one and wait for @Kaijones23 and @ggow to release a LineageOS.
digitalTARDIS said:
I can't wait for TWRP to come out for this tablet. I personally haven't bought one yet until TWRP Recovery is out. I also am waiting for Black Friday and Cyber Monday for this tablet to go on sale, then I'll buy one and wait for @kaijones23 and @ggow to release a LineageOS.
Click to expand...
Click to collapse
@Kaijones23 and @ggow to create an unofficial LineagesOS 16 (Android 9 Pie) for Fire HD10 Maverick
@k4y0z and @xyz` have gone off the grid recently. Did the guys burn out??? The last time I pm'ed @xyz` , he was not interested in donations, and neither he had it set up. Has anything changed?
I might get the new HD10 on sale for Black Friday, and keep it in storage until root (if ever).The new HD10 has decent specs overall (1080p screen and cpu) for $100 (BF price!!!), but low on RAM.
What else can you get for $100 these days? For example, Dragon Touch K10 Tablet (10") is currently at $85 (usually $100), stock Android 9, BUT !!! 720p screen Easy MTK root, and no issues making it stick with the Magisk hack by @diplomatic.
I guess, the new HD10 with all its pros and cons is either for Amazon loyalists, or committed renegades, like most of us here
bibikalka said:
@k4y0z and @xyz` have gone off the grid recently. Did the guys burn out??? The last time I pm'ed @xyz` , he was not interested in donations, and neither he had it set up. Has anything changed?
I might get the new HD10 on sale for Black Friday, and keep it in storage until root (if ever).The new HD10 has decent specs overall (1080p screen and cpu) for $100 (BF price!!!), but low on RAM.
What else can you get for $100 these days? For example, Dragon Touch K10 Tablet (10") is currently at $85 (usually $100), stock Android 9, BUT !!! 720p screen Easy MTK root, and no issues making it stick with the Magisk hack by @diplomatic.
I guess, the new HD10 with all its pros and cons is either for Amazon loyalists, or committed renegades, like most of us here
Click to expand...
Click to collapse
I indeed do not accept donations (I don't know what's up with this thread), and I don't plan on working on this device due to lack of time and interest.
bibikalka said:
What else can you get for $100 these days? For example, Dragon Touch K10 Tablet (10") is currently at $85 (usually $100), stock Android 9, BUT !!! 720p screen Easy MTK root, and no issues making it stick with the Magisk hack by @diplomatic.
I guess, the new HD10 with all its pros and cons is either for Amazon loyalists, or committed renegades, like most of us here
Click to expand...
Click to collapse
I have moved on to the Onn product line distributed by Walmart. Still enjoy my older Amazon gizmos but probably won't be adding any Fire branded devices to portfolio anytime soon.
https://forum.xda-developers.com/wa...-to-unlock-root-xposed-onn-8-walmart-t3945284
BTW the donation thing turned sour after folks hijacked the original intent for their own selfish interests.
So this thread is basically something implying that people will help without consent of the Developers mentioned. How about asking for help, if you ( @AmznUser444 Dev ) don't have anything to contribute please don't volunteer others to help without their consent. What are your credentials @AmznUser444 Dev ? You seem to post alot of random BS that could brick peoples devices. Are you trying to help or what? This is basically people volunteering their free time to experiment and free us from vendors. Respect the process.... Sorry to complain, but request help and get approval. This is what stops progress.
Michajin said:
So this thread is basically something implying that people will help without consent of the Developers mentioned. How about asking for help, if you ( @AmznUser444 Dev ) don't have anything to contribute please don't volunteer others to help without their consent. What are your credentials @AmznUser444 Dev ? You seem to post alot of random BS that could brick peoples devices. Are you trying to help or what? This is basically people volunteering their free time to experiment and free us from vendors. Respect the process.... Sorry to complain, but request help and get approval. This is what stops progress.
Click to expand...
Click to collapse
I will not be able to work on this device Because my main focus is getting pie stable on karnak but I won't be able to afford to get this device and deal with some issues and testing because I have school and work each day and my daily life is busy..
Sent from my Pixel 3a XL using Tapatalk
Has anyone tried the OEM bootloader unlock in developers options to see it it actually unlocks it?
Nevermind just tried. It allows you to hit it, gives you warnings then just turns itself off. Sorry if this has already been tried and discussed.
@k4y0z, are you stared to create a bootloader exploit and TWRP image for Fire HD10 2019.
AmznUser444 Dev;80987585 [user=7104332 said:
@k4y0z[/user], are you stared to create a bootloader exploit and TWRP image for Fire HD10 2019.
Click to expand...
Click to collapse
At what point did @k4y0z commit to doing this? Must have missed the memo.
beeree7 said:
Has anyone tried the OEM bootloader unlock in developers options to see it it actually unlocks it?
Nevermind just tried. It allows you to hit it, gives you warnings then just turns itself off. Sorry if this has already been tried and discussed.
Click to expand...
Click to collapse
Can Fire HD 10's bootloader will be cracked when OEM unlock is enabled.
Connect your Fire tablet to PC (USB debugging in developer options is enabled.
Code:
adb reboot bootloader
//Now in fastboot mode. Type in terminal on your PC.
fastboot oem unlock
AmznUser444 Dev said:
Can Fire HD 10's bootloader will be cracked when OEM unlock is enabled.
Connect your Fire tablet to PC (USB debugging in developer options is enabled.
Code:
adb reboot bootloader
//Now in fastboot mode. Type in terminal on your PC.
fastboot oem unlock
Click to expand...
Click to collapse
When attempting to reboot bootloader it just says =>fast boot mode on the screen. In terminal it says <waiting for device>
Every time adb reboot bootloader is done it says the device not recognized. I have driver installed.
ILoveLamp2234 said:
Can Fire HD 10's bootloader will be cracked when OEM unlock is enabled.
Connect your Fire tablet to PC (USB debugging in developer options is enabled.
When attempting to reboot bootloader it just says =>fast boot mode on the screen. In terminal it says <waiting for device>
Every time adb reboot bootloader is done it says the device not recognized. I have driver installed.
Click to expand...
Click to collapse
No - this won't work (regardless of the fastboot connectivity/driver problem you are experiencing). Pay no attention to the rubbish posted earlier in this thread and elsewhere; dude is clueless.
DB126 said:
No - this won't work (regardless of the fastboot connectivity/driver problem you are experiencing). Pay no attention to the rubbish posted earlier in this thread and elsewhere; dude is clueless.
Click to expand...
Click to collapse
Hold down the power button + volume down to go to recovery mode and select Reboot to bootloader.
Just try to use another USB-C cable with full size USB 3.0 or 3.1

Categories

Resources