Anyone using the new 1.17.40.1234 update please post your impressions and more particularly any bugs encountered.
Overheating, system slowdown and poor battery life have been mentioned by a number of users on other sites.
phone is overheating whenever I am using whatsapp or simply playing games. Is there anyway to rollback to W1.16.40.763 ?
souravipc53 said:
phone is overheating whenever I am using whatsapp or simply playing games. Is there anyway to rollback to W1.16.40.763 ?
Click to expand...
Click to collapse
Do you have 1.17.40.1234 or 1.17.40.1106 ?
I think that they might have corrected the issues with the 1234 version.
If you want to rollback just copy the update in the phone renaming it with a upper version, for example 1.18.40.763, remember that the procedure is at your own risk.
reddevilx said:
Do you have 1.17.40.1234 or 1.17.40.1106 ?
I think that they might have corrected the issues with the 1234 version.
If you want to rollback just copy the update in the phone renaming it with a upper version, for example 1.18.40.763, remember that the procedure is at your own risk.
Click to expand...
Click to collapse
On the asus forums a number of users said the latest 1234 update made the overheating and battery much worse.
reddevilx said:
If you want to rollback just copy the update in the phone renaming it with a upper version, for example 1.18.40.763, remember that the procedure is at your own risk.
Click to expand...
Click to collapse
.
method doesn't work. Even though updater notifies me about new update but fails . Shows older version cannot be used or something like that.
souravipc53 said:
.
method doesn't work. Even though updater notifies me about new update but fails . Shows older version cannot be used or something like that.
Click to expand...
Click to collapse
From the asus forum try this:
1. Download the firmware to your PC
2. Rename it to MOFD_SDUPDATE, enable the view extension of the files option and check that the file has only .zip, .zip.zip is not accepted and the procedure will fail. (you should have MOFD_SDUPDATE.zip)
3. Now format the sd card in windows with default settings (fat32)
4. Copy the MOFD_SDUPDATE.zip on the newly formatted sd card
5. Shut down your phone and insert the sd card
6. To boot in recovery mode you need to:
a. Hold the power button and volume down key all together
b. When the first Asus logo appears, release the keys.
7. Go to update from sd card and located the MOFD_SDUPDATE.zip
8. Then flash
9. You can format the cache partition if you like (recommended)
cheers
heywheelie said:
From the asus forum try this:
1. Download the firmware to your PC
2. Rename it to MOFD_SDUPDATE, enable the view extension of the files option and check that the file has only .zip, .zip.zip is not accepted and the procedure will fail. (you should have MOFD_SDUPDATE.zip)
3. Now format the sd card in windows with default settings (fat32)
4. Copy the MOFD_SDUPDATE.zip on the newly formatted sd card
5. Shut down your phone and insert the sd card
6. To boot in recovery mode you need to:
a. Hold the power button and volume down key all together
b. When the first Asus logo appears, release the keys.
7. Go to update from sd card and located the MOFD_SDUPDATE.zip
8. Then flash
9. You can format the cache partition if you like (recommended)
cheers
Click to expand...
Click to collapse
Tried this method. Doesnt work. Better use cyanogen mod and TWRP
Or try this:
1.0 [Preparation of your PC]
Download the ADB Tool HERE.
Click on the setup executable and type in "Y" for all the entries. (for the prompt on driver installation, simply click "Next", "Install", followed by "Finish").
1.1
Download the ASUS Software Update HERE.
Once completed, move the update file to C:\adb (where C: is the root drive where the ADB Tool was installed at).
2.0 [Preparation of Device]
Turn off your phone.
Press the "Volume Down" button followed by the "Power" button.
Keep holding the two buttons until the recovery screen appears, then release both AT THE SAME TIME.
Plug your phone into the PC.
On your phone, press the "Volume Down" button to select the option "apply update from adb".
Then, press the "Power" button once to select.
3.0 [Flashing]
Open the command prompt (Windows Key + R, type in "CMD" and enter).
Type in cd C:\adb (take note).
Then, type in adb sideload "downloaded file name".zip
4.0 [Finish]
Upon completion, make sure that the option "reboot system now" is selected on your phone.
Then, press the "Power" button once.
Is anyone using this update that is not experiencing any problems especially battery and heating?
No feedback anyone?
Sent from my GT-S7582 using Tapatalk
Seems that very few have updated to this firmware. I haven't and won't until a stable update comes out. In the meantime I'm happy with 1.16.40.763
heywheelie said:
Seems that very few have updated to this firmware. I haven't and won't until a stable update comes out. In the meantime I'm happy with 1.16.40.763
Click to expand...
Click to collapse
I downgraded to V1.16 due to bugs and lag on v1.1.7.40.1234
Posted using a calculator and delayed by AT&T.
---------- Post added at 01:31 PM ---------- Previous post was at 01:29 PM ----------
shubham41 said:
No feedback anyone?
Sent from my GT-S7582 using Tapatalk
Click to expand...
Click to collapse
Mine keeps on overheating and it lags very bad. I downgraded mine to v1.16.
Posted using a calculator and delayed by AT&T.
shubham41 said:
No feedback anyone?
Sent from my GT-S7582 using Tapatalk
Click to expand...
Click to collapse
I've only been using it for a week on my ZOOTD but I haven't noticed any overheating or significant loss of battery life
UPDATE: I don't know if it was caused by the update or not but I was on a call and the flashlight came on and Firefox and Settings opened.
willcall said:
I've only been using it for a week on my ZOOTD but I haven't noticed any overheating or significant loss of battery life
Click to expand...
Click to collapse
Thanks. I wonder if the overheating and battery life problems only affects the Z00LD?
heywheelie said:
Seems that very few have updated to this firmware. I haven't and won't until a stable update comes out. In the meantime I'm happy with 1.16.40.763
Click to expand...
Click to collapse
Judging by the fact that a new update has not been released for quite some time now, the next update *should and hopefully, be marshmallow.
Sent from my ASUS_Z00LD using XDA-Developers mobile app
heywheelie said:
Anyone using the new 1.17.40.1234 update please post your impressions and more particularly any bugs encountered.
Overheating, system slowdown and poor battery life have been mentioned by a number of users on other sites.
Click to expand...
Click to collapse
No issues on my ze550kl, no heating issue, no major bugs on 1.17.40.1234. But it becomes warm when I don't close any game and tap home button but that's normal.
1.17.40.1234 came with Wi-Fi and carrier network improvements. I guess people from certain region might be facing heating issue due to changes in modem. I am from India. No issues for me
I can confirm there is an issue. I just got the phone and immediately updated it the latest firmware. I am getting abysmal battery life and the phone does get quite warm at times. I charged my phone last night and when I went to bed it was at 95% battery. When I woke up the battery was at 33%. I looked at the battery logs and the flashlight app and cell standby consumed 22% each. I have no clue why the flashlight app would be using battery for no reason.
dominati said:
I can confirm there is an issue. I just got the phone and immediately updated it the latest firmware. I am getting abysmal battery life and the phone does get quite warm at times. I charged my phone last night and when I went to bed it was at 95% battery. When I woke up the battery was at 33%. I looked at the battery logs and the flashlight app and cell standby consumed 22% each. I have no clue why the flashlight app would be using battery for no reason.
Click to expand...
Click to collapse
Try using the auto-start manager and making sure the flashlight app does not start automatically then reboot the phone. High standby usage can sometimes be caused by a faulty microsd card. If you have one, try unmounting and then remountiing it and see if that helps. If it doesn't try reformatting it.
Related
{Disclaimer} This is the method I used and it worked on two different phones. if you mess yours up it was your choice to root not mine!
This method I am about to show you will only give you root on stock nothing more nothing less
1) Ok first things first if your device is on ... TURN IT OFF then holding the vol+ button press power you should get a black screen saying "incoming download mode" on top then a continuous cycle of "polling, get oemsbl_mode = 1"
2) Plug it into your computer and the new drive folder will open (or however you have it set up) inside this new "USB" device should be a folder called "Images" open that
NOW MAKE A COPY OF EACH OF THESE FILES AND MAKE SURE YOU PLACE THEM SOMEWHERE SAFE!!!!!
3) Now take this file http://dl.dropbox.com/u/5734432/recovery.img.zip rename it to the simple recovery.img and overwrite the original
4) Download this set of su binaries and superuser.apk along with busybox installed properly
http://dl.dropbox.com/u/5734432/su-2...fgh-signed.zip
place this on the root or first folder of the sd card
5) Now you will have to pull the battery but make sure you remove the usb cable first and then put the battery back in and hold Vol+ AND Vol- at the same time and press and hold power until you feel the vibrate then and only then let go of the power continue to hold the Vol+- until the clockworkmod recovery loads
6) Using the up and down volume select install zip from sd by pressing the search button then choose zip from sd card again and scroll down to the "su-2.3.6.3-efgh-signed.zip" and select it let it do its thing then once its done reboot and you have a Rooted device my friends
PLEASE ONLY DO THIS IF YOU UNDERSTAND WHAT ROOT IS AND CAN DO TO BENEFIT YOU BECAUSE I'M NOT SURE HOW PRONE THESE THINGS ARE TO BRICK BUT I HAVE MOVED MANY GAPPS TO MY SYSTEM TO SAVE SPACE ON DATA IE: MAPS, GMAIL, YOUTUBE ETC...
As soon as I can get some assistance from the cm team or anyone for that matter i want to get this integrated into the nightlies for CM7+ as this phone is amazing fast a very good rival to the MT4G aka Glacier except no bulky sense boots very fast if you haven't noticed
If you should need further assistance hit me on twitter @snakebitezz or write back on this thread and BTW this is my guide for us English speaking folk so not any of this is my work except the write-up I would cite the site if I could find it again
this a new device from Cincinnati Bell the Huawei Ascend X 4G aka U9000-81!! but still the same as any other in this thread
snakebitezz said:
{Disclaimer} This is the method I used and it worked on two different phones. if you mess yours up it was your choice to root not mine!
This method I am about to show you will only give you root on stock nothing more nothing less
1) Ok first things first if your device is on ... TURN IT OFF then holding the vol+ button press power you should get a black screen saying "incoming download mode" on top then a continuous cycle of "polling, get oemsbl_mode = 1"
2) Plug it into your computer and the new drive folder will open (or however you have it set up) inside this new "USB" device should be a folder called "Images" open that
NOW MAKE A COPY OF EACH OF THESE FILES AND MAKE SURE YOU PLACE THEM SOMEWHERE SAFE!!!!!
3) Now take this file http://dl.dropbox.com/u/5734432/recovery.img.zip rename it to the simple recovery.img and overwrite the original
4) Download this set of su binaries and superuser.apk along with busybox installed properly
http://dl.dropbox.com/u/5734432/su-2...fgh-signed.zip
place this on the root or first folder of the sd card
5) Now you will have to pull the battery but make sure you remove the usb cable first and then put the battery back in and hold Vol+ AND Vol- at the same time and press and hold power until you feel the vibrate then and only then let go of the power continue to hold the Vol+- until the clockworkmod recovery loads
6) Using the up and down volume select install zip from sd by pressing the search button then choose zip from sd card again and scroll down to the "su-2.3.6.3-efgh-signed.zip" and select it let it do its thing then once its done reboot and you have a Rooted device my friends
PLEASE ONLY DO THIS IF YOU UNDERSTAND WHAT ROOT IS AND CAN DO TO BENEFIT YOU BECAUSE I'M NOT SURE HOW PRONE THESE THINGS ARE TO BRICK BUT I HAVE MOVED MANY GAPPS TO MY SYSTEM TO SAVE SPACE ON DATA IE: MAPS, GMAIL, YOUTUBE ETC...
As soon as I can get some assistance from the cm team or anyone for that matter i want to get this integrated into the nightlies for CM7+ as this phone is amazing fast a very good rival to the MT4G aka Glacier except no bulky sense boots very fast if you haven't noticed
If you should need further assistance hit me on twitter @snakebitezz or write back on this thread and BTW this is my guide for us English speaking folk so not any of this is my work except the write-up I would cite the site if I could find it again
this a new device from Cincinnati Bell the Huawei Ascend X 4G aka U9000-81!! but still the same as any other in this thread
Click to expand...
Click to collapse
One criticism about this post if you want to provide uploads do so within the xda-developers posting interface. The links in the quoted post don't work anymore so is useless. the add attachment icon looks like a paperclip and will provide a QR code.
Thanks
Just used the guide I already wrote with working links but thanks for fixing
WORKS
Thank you, both. Works like a charm. Rooted u9000-81
JUGOMAN said:
Thank you, both. Works like a charm. Rooted u9000-81
Click to expand...
Click to collapse
No Problem, BTW To thank people click the thanks button.
dropbox links dead
perern said:
dropbox links dead
Click to expand...
Click to collapse
Yes that is why I posted the second message.
snakebitezz said:
{Disclaimer} This is the method I used and it worked on two different phones. if you mess yours up it was your choice to root not mine!
This method I am about to show you will only give you root on stock nothing more nothing less
1) Ok first things first if your device is on ... TURN IT OFF then holding the vol+ button press power you should get a black screen saying "incoming download mode" on top then a continuous cycle of "polling, get oemsbl_mode = 1"
2) Plug it into your computer and the new drive folder will open (or however you have it set up) inside this new "USB" device should be a folder called "Images" open that
NOW MAKE A COPY OF EACH OF THESE FILES AND MAKE SURE YOU PLACE THEM SOMEWHERE SAFE!!!!!
3) Now take this file http://dl.dropbox.com/u/5734432/recovery.img.zip rename it to the simple recovery.img and overwrite the original
4) Download this set of su binaries and superuser.apk along with busybox installed properly
http://dl.dropbox.com/u/5734432/su-2...fgh-signed.zip
place this on the root or first folder of the sd card
5) Now you will have to pull the battery but make sure you remove the usb cable first and then put the battery back in and hold Vol+ AND Vol- at the same time and press and hold power until you feel the vibrate then and only then let go of the power continue to hold the Vol+- until the clockworkmod recovery loads
6) Using the up and down volume select install zip from sd by pressing the search button then choose zip from sd card again and scroll down to the "su-2.3.6.3-efgh-signed.zip" and select it let it do its thing then once its done reboot and you have a Rooted device my friends
PLEASE ONLY DO THIS IF YOU UNDERSTAND WHAT ROOT IS AND CAN DO TO BENEFIT YOU BECAUSE I'M NOT SURE HOW PRONE THESE THINGS ARE TO BRICK BUT I HAVE MOVED MANY GAPPS TO MY SYSTEM TO SAVE SPACE ON DATA IE: MAPS, GMAIL, YOUTUBE ETC...
As soon as I can get some assistance from the cm team or anyone for that matter i want to get this integrated into the nightlies for CM7+ as this phone is amazing fast a very good rival to the MT4G aka Glacier except no bulky sense boots very fast if you haven't noticed
If you should need further assistance hit me on twitter @snakebitezz or write back on this thread and BTW this is my guide for us English speaking folk so not any of this is my work except the write-up I would cite the site if I could find it again
this a new device from Cincinnati Bell the Huawei Ascend X 4G aka U9000-81!! but still the same as any other in this thread
Click to expand...
Click to collapse
Any way to root Ascend U9200 (aka Ascend P1)?
okty2k said:
Any way to root Ascend U9200 (aka Ascend P1)?
Click to expand...
Click to collapse
YGPM....
hit Thanks if i've helped you...
okty2k said:
Any way to root Ascend U9200 (aka Ascend P1)?
Click to expand...
Click to collapse
for easy way just only use super1click
okty2k said:
Any way to root Ascend U9200 (aka Ascend P1)?
Click to expand...
Click to collapse
ok sadly i know very little about the phone other than a co-worker has one and he wont let me "play" with it lol Giggity
no super1click did it work for you? because the U9000-81 wouldnt root any other way besides the recovery method trust me tried it soooooooooo many times!!
Welcome to the CM10.1 for the Lenovo Ideapad K1
Legal disclaimer: I'm not responsible if you brick your tablet, or have other damages in the process.
Features:
Multi User support (max. 5 User)
WIFI
Overclocking ( max. 1,4 GHz)
GPS
Bluetooth
Camera front/back
HD video/audio
externe SD-Card
USB-Stick support
Gyro
Auto brightness (bugy)
Hardware / Software Rotation Lock
VPN Support
3G support
Home button
CWM 6.0.3.3
Install Procedure 1
You come from CM10, no wipe needed
1. Download Update and Gapps and save to SD card
2. Reoboot into Recovery Mode
3. Once in recovery, select the update file to be flashed
4. select the gapps file to be flashed
5. Reboot
Install Procedure 2
You come from a stock or other CM version
Full Wipe, all data will be gone
1. Download the nvflash and save it on your PC
2. Power down and enter APX mode on your tablet, with the USB cable connected to the PC
3. Run flash-win.bat or flash-linux.sh (depending on what your PC runs)
4. After table has booted, enter settings and select about tablet. touch 7 time on build number. Your developer option are visible.
5. Go to settings, Developer options and select Advanced reboot
7. connect your tablet to the pc and save gapps on your sd card. Or download gapps via liink.
6. Go in Recovery via long press of Power, and select "Reboot" then "Recovery"
5. Flash the gapps package that you downloaded in step 1.
6. Reboot
Downloads:
First update 3G Version or
NVFlash 3G or Mirror
First Update Wifi Version or
NVFlash Wifi or Mirror
Important. Only that Gapps version will work !!!
Google Apps alias GApps or Mirror
Current Releases (date 2013-09-26):
Wifi Version
3G Version
Bugs:
light sensor (never worked correct)
Wifi (works just with "keep Wi-Fi on during sleep, always")
Headset detection
Credits:
KHanning
Krook1
Breeder (Testing)
Koshu
and finally Codeworkx for so many tips !!! :good:
Info / Tips
- Developer settings: go in settings and select about tablet. Press 7 times on build number
Recovery Update
The Recovery will be updated with nightly version of the 18-07-2013.
Awesome work buddy !!. Downloading it. But will flash over the weekend.
Thanks for continuing work on this device.
Nice work! I've flashed it yesterday when you posted it on goo.im and it's running nice so far. Got sod but I put wifi to always on, anyways it doesn't seem to drain too much battery. Also maybe you should update the recovery as this one cause 0 folder nesting when flashing(I got emulated/0/0/0...) and this is repaired with newer recovery, I don't remind wich number. Everything else seem to be working perfectly, some little strange thing but I think it's due to CM nighlties and could be working correctly later. I'll thank you so much for keeping our device alive. Keep it going.
Edit: The recovery issue is fixed since cwm 6.0.2.3 and we got 6.0.1.1 so that's why it's nesting but that isn't dangerous or anything, it can be deleted and the data are simply at the bottom of the 0 folders tree.
kaschemme said:
Welcome to the CM10.1 for the Lenovo Ideapad K1
Click to expand...
Click to collapse
Thank you, kaschemme! Will download and flash when I get home as my tablet does not have too much data. THANK YOU!!!
ti-pich said:
Nice work! I've flashed it yesterday when you posted it on goo.im and it's running nice so far. Got sod but I put wifi to always on, anyways it doesn't seem to drain too much battery. Also maybe you should update the recovery as this one cause 0 folder nesting when flashing(I got emulated/0/0/0...) and this is repaired with newer recovery, I don't remind wich number. Everything else seem to be working perfectly, some little strange thing but I think it's due to CM nighlties and could be working correctly later. I'll thank you so much for keeping our device alive. Keep it going.
Edit: The recovery issue is fixed since cwm 6.0.2.3 and we got 6.0.1.1 so that's why it's nesting but that isn't dangerous or anything, it can be deleted and the data are simply at the bottom of the 0 folders tree.
Click to expand...
Click to collapse
Where can I get this recovery file to flash on my tablet? Thanks! :good:
Mordred69 said:
Where can I get this recovery file to flash on my tablet? Thanks! :good:
Click to expand...
Click to collapse
It isn't made for our device yet so we can't flash it. It need to be updated and compiled from the rom source then it can be flashed so for now we have to live with this version.
Way to go!!
On goo.im for devs/kaschemme/nvflash/nvflash_CM10.1_Wifi_Kaschemme_v1.zip
"The file you requested was not found. Lets see if we can find that for you..."
Mordred69 said:
On goo.im for devs/kaschemme/nvflash/nvflash_CM10.1_Wifi_Kaschemme_v1.zip
"The file you requested was not found. Lets see if we can find that for you..."
Click to expand...
Click to collapse
There isn't nvflash folder in kaschemme. For me kaschemme/CM10/nvflash/nvflash_CM10.1_Wifi_Kaschemme_v1.zip download without any issue.
Hey, kaschemme, thanks so much for the update! I am looking forward to giving it a try, although I do use the USB Storage function a lot (it's the easiest way to copy movies onto my K1), so I might wait until after my vacation to do the update. I'd also like to see how the GPS functions are working, since I use my K1 a lot when I go geocaching. But it's wonderful to see that the K1 is still moving forward! :good:
K1Andy said:
Hey, kaschemme, thanks so much for the update! I am looking forward to giving it a try, although I do use the USB Storage function a lot (it's the easiest way to copy movies onto my K1), so I might wait until after my vacation to do the update. I'd also like to see how the GPS functions are working, since I use my K1 a lot when I go geocaching. But it's wonderful to see that the K1 is still moving forward! :good:
Click to expand...
Click to collapse
USB connection to a computer do work for me on ubuntu 13.04 better than it ever worked. I think by USB storage he is meaning USB OTG, like plugging a usb key directly in the K1 with the almost inexistant lenovo adapter.
ti-pich said:
USB connection to a computer do work for me on ubuntu 13.04 better than it ever worked. I think by USB storage he is meaning USB OTG, like plugging a usb key directly in the K1 with the almost inexistant lenovo adapter.
Click to expand...
Click to collapse
Right, USB host support (attaching a USB flash drive to the K1) is exactly what I mean, and what I use. I was fortunate enough to get one of those non-existent adapters.
ti-pich said:
There isn't nvflash folder in kaschemme. For me kaschemme/CM10/nvflash/nvflash_CM10.1_Wifi_Kaschemme_v1.zip download without any issue.
Click to expand...
Click to collapse
The problem is the NVFlash links.
The file is not at http://goo.im/devs/kaschemme/nvflash/nvflash_CM10.1_Wifi_Kaschemme_v1.zip
The file is at http://goo.im/devs/kaschemme/cm10/nvflash/nvflash_CM10.1_Wifi_Kaschemme_v1.zip
Means it is inside the CM10 directory (linkage truncates whole sentence)
Thanks, ti-pich! Thanks Kaschemme!
K1Andy said:
Right, USB host support (attaching a USB flash drive to the K1) is exactly what I mean, and what I use. I was fortunate enough to get one of those non-existent adapters.
Click to expand...
Click to collapse
You are really lucky then, this is probably the only thing missing on this tablet, and that's why I'm waiting for google to release their nexus 7 full hd with a regular micro usb. Anyway, sorry I misunderstood what you said.
Kaschemme,
nvflash_CM10.1_Wifi_Kaschemme_v1.zip is corrupt. Downloaded 4 times.
Great job Kaschemme!
So far all my apps that I have reloaded are working. Thanks for your hard work.
Mordred69 said:
Kaschemme,
nvflash_CM10.1_Wifi_Kaschemme_v1.zip is corrupt. Downloaded 4 times.
Click to expand...
Click to collapse
I downloaded it, and it does appear to have the correct MD5 hash signature, but if I try to open or extract it using Windows Explorer, I also get a message that it is invalid or corrupted. However, if I use 7-Zip, it seems to open and extract with no problem. Perhaps it was built using some type of zip compression that isn't supported by the built-in Windows compression tools?
K1Andy said:
I downloaded it, and it does appear to have the correct MD5 hash signature, but if I try to open or extract it using Windows Explorer, I also get a message that it is invalid or corrupted. However, if I use 7-Zip, it seems to open and extract with no problem. Perhaps it was built using some type of zip compression that isn't supported by the built-in Windows compression tools?
Click to expand...
Click to collapse
Thank you. I was using winrar which is what I always use. In any case, I flashed this rom's cwm version over krook1's nvflash starter v2 and it worked, but gives me the same errors as krook1's version 6.1, which are random apps closing with no explanation whatsoever... Not even a "sorry, xyz app has forced closed" message. Keep in mind this is a fresh install.
This flash also started complaining that email had closed right from the start, too. I hope this helps you guys...
hei Kaschemme.
thanks u so much!!!
this rom run so well.. the performance got better from the previous one.
i dont found any bug yet, but i read ur first post, that there is a bug on Headset detection...
let me try when i got home
anyway, great job!
Edited :
i just try to plug my headset on my K1..
And it works well..
So up to now, i dont found a bug yet...
Cool!
Mordred69 said:
Thank you. I was using winrar which is what I always use. In any case, I flashed this rom's cwm version over krook1's nvflash starter v2 and it worked, but gives me the same errors as krook1's version 6.1, which are random apps closing with no explanation whatsoever... Not even a "sorry, xyz app has forced closed" message. Keep in mind this is a fresh install.
This flash also started complaining that email had closed right from the start, too. I hope this helps you guys...
Click to expand...
Click to collapse
Take a nandroid backup and try doing a clean flash (factory reset then flash), in case you did a dirty flash.
Mordred69 said:
Thank you. I was using winrar which is what I always use. In any case, I flashed this rom's cwm version over krook1's nvflash starter v2 and it worked, but gives me the same errors as krook1's version 6.1, which are random apps closing with no explanation whatsoever... Not even a "sorry, xyz app has forced closed" message. Keep in mind this is a fresh install.
This flash also started complaining that email had closed right from the start, too. I hope this helps you guys...
Click to expand...
Click to collapse
Would you please let me know which version of 7-zip you used to extract the files from nvflash archive?
I tried 9.20 and 9.30alpha and both give me 'unsupported compression method'
Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
Hello,
I've already sent my device back to Asus, where they did absolutely nothing and just sent it right back to me. Complete waste of $16 shipping.
anyway, a while back I received a notification to update firmware. It downloaded, but then the install failed. About 2 weeks later, it prompted me again, and once again it downloaded but then failed to install on the restart. I decided to download the latest firmware on the Asus website, but I have no option to install by SD Card once I'm in Droidboot. My only options are:
1. REBOOT
2. REBOOT DROIDBOOT
3. RECOVERY
4. POWER OFF
Can someone please help? Asus has been absolutely no help, as I just spent another hour yesterday "chatting" with the rep who knew absolutely nothing!
Thanks in advance, cheers!
Well, I guess I stumped everyone in here as well. I just sent the device back to Asus for the second time in 2 weeks. Let's see if they do anything more than just power on the device, deem it "working properly" and promptly send it back to me.
Shaundiesel said:
Hello,
I've already sent my device back to Asus, where they did absolutely nothing and just sent it right back to me. Complete waste of $16 shipping.
anyway, a while back I received a notification to update firmware. It downloaded, but then the install failed. About 2 weeks later, it prompted me again, and once again it downloaded but then failed to install on the restart. I decided to download the latest firmware on the Asus website, but I have no option to install by SD Card once I'm in Droidboot. My only options are:
1. REBOOT
2. REBOOT DROIDBOOT
3. RECOVERY
4. POWER OFF
Can someone please help? Asus has been absolutely no help, as I just spent another hour yesterday "chatting" with the rep who knew absolutely nothing!
Thanks in advance, cheers!
Click to expand...
Click to collapse
I have (2) K01A MemoPad 170CX's, less than 30-days old. Both updated to 4.4.2 via OTA method running software Image Version: V11.2.3.27. (2014-12-23)
On one all of the sudden (and it may be a case the camera never worked) is when the camera is activated the cam app comes up for (3) seconds with the still icon lit up, then the video icon lights up as well for a (1) second then app exits to desktop with a "No Camera is found" error message.
I've been all over the net trying to find into on how to manually flash it.
According to the very cryptic info on ASUS website step # states:
"2. Download device software and Update SOP (From “Manual” Item)"
Googling for info on SOP, you download firmware in zip format, then do (1) extraction of the contents to a MicroSD card formated FAT32 to the root of the card. (After extraction there is a zip file named ifwi.zip that contains (4) *.bin files that remain inside the zip, you don't extract that zip.)
According to info on SOP, with device powered fully up inserting the sd card is supposed to bring up a prompt, a icon on the taskbar/, you click the prompt and the update process begins.
I'm not seeing that.
All I see when the SD card is inserted is a notification the SD is being prepared for use.
When trying to update via DROIDBOOT (W Fastboot wording at bottom of screen), with SD card inserted the DROIDBOOT menu isn't coming up, when I fire up DROIDBOOT without the SD card inserted and insert it DROIDBOOT does not recognize any change has occurred.
Wanted to try re-flashing WW_V11.2.3.27 as I've read in cases the camera gets the No camera found error message the camera firmware gets corrupted somehow. when you hit the return to home-screen icon too fast, I guess when app is in process of opening and it's closed before it initializes fully.
If that doesn't work, trying Version WW_V11.2.3.28 as I for sure don't want to have to send the device back to ASUS when a simple reflash of the firmware would get the camera working again.
Q: Are / were you getting the same results?
(I guess you didn't try SOP method?)
Q: I guess "Fastboot" means "neutered"? Is there a way to bypass? /enable all functions ASUS would not be able to detect if I have to send in unit for service?
Tried copying the contents of the removable SD card to the internal SD card folder...
Nada, zip, nothing.
ASUS needs to provide info on how to run the flash, I've never had this much trouble flashing a device.
WeAreNotAlone said:
I have (2) K01A MemoPad 170CX's, less than 30-days old. Both updated to 4.4.2 via OTA method running software Image Version: V11.2.3.27. (2014-12-23)
On one all of the sudden (and it may be a case the camera never worked) is when the camera is activated the cam app comes up for (3) seconds with the still icon lit up, then the video icon lights up as well for a (1) second then app exits to desktop with a "No Camera is found" error message.
I've been all over the net trying to find into on how to manually flash it.
According to the very cryptic info on ASUS website step # states:
"2. Download device software and Update SOP (From “Manual” Item)"
Googling for info on SOP, you download firmware in zip format, then do (1) extraction of the contents to a MicroSD card formated FAT32 to the root of the card. (After extraction there is a zip file named ifwi.zip that contains (4) *.bin files that remain inside the zip, you don't extract that zip.)
According to info on SOP, with device powered fully up inserting the sd card is supposed to bring up a prompt, a icon on the taskbar/, you click the prompt and the update process begins.
I'm not seeing that.
All I see when the SD card is inserted is a notification the SD is being prepared for use.
When trying to update via DROIDBOOT (W Fastboot wording at bottom of screen), with SD card inserted the DROIDBOOT menu isn't coming up, when I fire up DROIDBOOT without the SD card inserted and insert it DROIDBOOT does not recognize any change has occurred.
Wanted to try re-flashing WW_V11.2.3.27 as I've read in cases the camera gets the No camera found error message the camera firmware gets corrupted somehow. when you hit the return to home-screen icon too fast, I guess when app is in process of opening and it's closed before it initializes fully.
If that doesn't work, trying Version WW_V11.2.3.28 as I for sure don't want to have to send the device back to ASUS when a simple reflash of the firmware would get the camera working again.
Q: Are / were you getting the same results?
(I guess you didn't try SOP method?)
Q: I guess "Fastboot" means "neutered"? Is there a way to bypass? /enable all functions ASUS would not be able to detect if I have to send in unit for service?
Tried copying the contents of the removable SD card to the internal SD card folder...
Nada, zip, nothing.
ASUS needs to provide info on how to run the flash, I've never had this much trouble flashing a device.
Click to expand...
Click to collapse
I tried everything under the sun....I extracted the zip, nothing. I left it as a zip, nothing. I went to recovery, nothing. You name it, I did it. So, I sent back to Asus for the second time in 2 weeks. I just checked the status of my RMA with Asus, and it states that "No trouble found." I'm not sure how NO TROUBLE IS FOUND when I can't even update to Asus latest firmware for their device? In addition, I do not get the options to try to manually update (Not that I should even have to go that route when it should be OTA). I will never own another Asus product. I've only had my tablet for 4 months, 2 1/2 months of which it sat in my desk, unused. Asus is garbage.
Did you remove any system files or freeze them? Did you root?
lvnatic said:
Did you remove any system files or freeze them? Did you root?
Click to expand...
Click to collapse
No I did not remove any system files or freeze them, that I know of. I rooted shortly after purchasing this, but unrooted the device about 2 weeks later.
Thoughts?
lvnatic said:
Did you remove any system files or freeze them? Did you root?
Click to expand...
Click to collapse
If you are talking to me in which camera(s) both seem to not be found by the OS ME170 is STOCK, STOCK, STOCK.
Contacted the vendor TigerDirect, noticed that they claim they will NOT do exchanges due to "manufacturers polices". While I realize it costs vendor (TigerDirect) to handle exchanges that wording could also indicate they have run the numbers and don't want to be bothered.
Reading about ASUS service, and my interaction with ASUS when I contacted them does not insipre incidence so I'm hoping to be able to flash the device and cameras will start functioning again.
In regards to the customer being able to flash a device (Which I done numerous times on other brands)
I know ASUS is a Asian based manufacturer and sells worldwide but they really need to have persons who can write in better ENGLISH.. ASUS needs to publish detailed instructions on how to flash device, additionally they need to update support pages with any drivers, tools to do so vs just posting the firmware with vaque reference to SOP.
Q: How long after firmware updates appears on ASUS site does OTA update get pushed?
..
Just an update....
Just received my memo pad back, and it appears to be finally fixed. It took sending it back twice, and escalating to a supervisor, but it looks good now. I've actually received 3 firmware updates in 2 days, so it was REALLY behind! What firmware are you all running right now? I have WW-3.2.23.201.
I think 201 is the latest. Mine is still on 199 though and it won't try to update again since it failed a couple of weeks ago.
Hello everyone,
Some Italian guys asked me for this guide because they did not find anything complete and detailed. Thanks to the XDA members' publications I could put together the pieces and write it down. I apologize for my English but I'm not very good, especially for technical terms. I hope I can help someone.
BACK TO ANDROID WEAR 1.5 FROM 2.0(COMPLETE GUIDE)
1. Download the software ADB installer 1.4.3 from this link compatible with Windows 10: http://uploadboy.com/tsp1bpbe9gtj/1082/zip
From here you can download an older version 1.3 for Windows 7: https://forum.xda-developers.com/showthread.php?t=2588979
2. Open the .exe file already downloaded with administrator privileges and follow the installation procedure to install the drivers
3. Download the three image files of the build "M1D65H" (boot, recovery, system) that you find here: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
4. Insert the files into the folder that created the ADB Installer that is normally the path "c:\adb"
5. Download tool "WinDroid Toolkit" from here (some antivirus swapping it for threat and eliminating it, in this case turn it off momentarily) :
https://forum.xda-developers.com/devdb/project/dl/?id=17244
6. Start with administrator privileges "WinDroid Toolkit"
7. Follow the instructions for installing the drivers required by the tool and select the model of the clock
8. Activate developer options on the clock: (Settings> System) by clicking "build number" repeatedly until unlocking the menu that will be among the main options
9. In the developer options menu, activate the "debug ADB"
10. Turn off the clock
11. With the clock off, hold down the physical key and in the meantime repeatedly tap your finger on the screen from minute 55 to 25 until the watch has entered the mode fastboot
12. Connect the clock to PC usb port via cable and charging base
13. Now "WinDroid Tool" should recognize the clock and below you will see that the "Offline" script becomes "Fatboot"
14. Click on "Unlock Bootloader" and proceed by accepting the various message from the tool
15. A confirmation message appears on the clock display, click on the right arrow and then on the central button to continue
Now the bootloader of the clock is unlocked and we can continue to install the three previously downloaded files. Close "Windroid Tool"
16. In the "adb" folder at the "c:\adb" path, click on a drop-down menu at any point in the chain and right-click and shift at the same time. Click on "Open command window here"
17. In the newly opened window, give the following commands one at a time and wait for each one to complete the operation:
1) fastboot -w
2) fastboot flash boot M1D65H_boot.img
3) fastboot flash recovery M1D65H_recovery.img
4) fastboot flash system M1D65H_system.img
Finally, to restart the clock, use the following command:
5) fastboot reboot
N.B. Before pairing the watch on the cellphone again remove the link, inside the Android wear app, clock and uninstall and reinstall the app.
Finished!
ELIMINATE THE PERSISTENT UPDATE NOTIFICATION
1. Download the .zip file containing the custom recovery and root to this address:
http://www.mediafire.com/file/qllnc7...+R+Utility.zip
2. Unzip the .zip file and insert the "twrp-3.0.0-0-lenok+squashfs.img" file into the "c:\adb" folder
3. In the Clock Developer Options menu, activate the "Debug ADB" (to enable them to follow the procedure above)
4. Connect the clock to the pc via the cable and charging base
5. Open "WinDroid Tool", go to the "Commands" tab and click on "push file". Select the file "SR1-SuperSU-v2.78-SR1-20160915123031.zip", wait for the procedure to complete and disconnect the clock from the PC.
6. Turn off the clock
7. With the clock off, hold down the physical key and in the meantime crawl your finger repeatedly on the screen from minute 55 to minute 25 until the clock has entered fastboot mode
8. Connect the clock to the pc
9. In the "adb" folder at the "c: \ adb" path, click on a drop-down menu at any point in the chain and right-click and shift at the same time. Click on "Open command window here"
10. In the window just open, give the following command and wait for the completion:
-) fastboot flash recovery twrp-3.0.0-0-lenok+squashfs.img
11. From the clock using the arrows and the confirmation button down to start the "recovery mode"
12. Accept the warning message and after selecting the language click on "install" and select, with the touchscreen, the .zip file "SR1-SuperSU-v2.78-SR1-20160915123031.zip", wait for the procedure to complete.
13. Restart the system and wait for the clock to turn on.
14. In the previously opened command window, give the following commands one at a time and wait for them to complete and complete:
1) adb shell
2) su
3) pm disable com.google.android.gms/.update.SystemUpdateService
4) pm disable com.google.android.gsf/.update.SystemUpdateService
Finished!
Many thanks riccardo423
I have managed to rollback my lg g watch r to android wear 1.5 AND suppress those pesky update notifications using your guide. I noticed your mediafire link to the custom recovery file is broken. There is an alternative download at http://www.mediafire.com/file/qllnc77jtdqxtdl/Lg+Watch+R+Utility.zip (posted by Dettofatto in a previous xda thread) which also contains the two additional required files.
Luigino1
Hello, thanks for inserting a working link. I've modified the text of the guide by entering your link. I'm glad to have helped you.
Riccardo423
For step 3 if I click the link it says the post does not exist. Anyway here's where I found the images if anyone needs it: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
BTW: Thank you for the complete guide, step by step, i was able to go back to 1.5 and disable the persistent notification thank you very much!
Hi, thank you for inserting the working link. I'm glad to have helped you. Riccardo423
After downgrade from 2.0 to 1.5, I don't received Facebook messenger notifications on watch. Other notifications work fine (Gmail, sms etc). Anyone know what's going on?
Hi I have never had this problem I think I can depend on your Facebook app. Which version of Facebook and which cell phone?
Latest version of Facebook app from Google store. Phone - Samsung Galaxy S6 with Latest Marshmallow updates
szczurx said:
Latest version of Facebook app from Google store. Phone - Samsung Galaxy S6 with Latest Marshmallow updates
Click to expand...
Click to collapse
You've already tried uninstalling and reinstalling the app?
The app wear permissions are unlocked for notifications?
Android wear app reinstalled twice. Even made watch factory reset. On Phone in settings/apps, Android Wear app have permissions for everything possible
Thanks for this Riccardo ( or grazie, from a fellow italian )!
Can't believe I managed to do the entire procedure without making a mess of it, lol. Everything appears to be working again, I'm so happy! Really hated AW 2.0. Hope the notification does not come back, I'll keep an eye out for it in the coming days.
hello, can anyone answer me why these commands dont work
pm disable com.google.android.gsf/.update.SystemUpdateService
and why superSu crashes on watch
Thank you Riccardo423 for great manual, it works great for my watch. No AW2 anymore!
riccardo423 said:
3. Download the three image files of the build "M1D65H" (boot, recovery, system) that you find here: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
charging base
Click to expand...
Click to collapse
Noob question: why the "M1D65H" versión? Is the last with AW 1.5? The NXG47C version is for 2.0?
LionheartSilver said:
Noob question: why the "M1D65H" versión? Is the last with AW 1.5? The NXG47C version is for 2.0?
Click to expand...
Click to collapse
Yes, it's the last AW1.5 version. However, perhaps it was due to something I didn't made correctly during the downgrade but this M1D65H version had not a good battery performance on my watch (battery was drained in less than 40 hours).
It's why I have used the M1D64Y version which is perfect in terme of battery performance (>48 hours) and applications responsiveness.
pidobeuliou said:
Yes, it's the last AW1.5 version. However, perhaps it was due to something I didn't made correctly during the downgrade but this M1D65H version had not a good battery performance on my watch (battery was drained in less than 40 hours).
It's why I have used the M1D64Y version which is perfect in terme of battery performance (>48 hours) and applications responsiveness.
Click to expand...
Click to collapse
Really? ... hmmm i see.... mine has always lasted less than 40 hrs... did you install any mod for the watch? core enablers or smth?
LionheartSilver said:
Really? ... hmmm i see.... mine has always lasted less than 40 hrs... did you install any mod for the watch? core enablers or smth?
Click to expand...
Click to collapse
Nothing specific, just installed the basic factory image + root . I have installed about 16 apps (including Watchmaker with a quite "sophisticated" watchface, wear messenger, WearMail, Wear Battery stats, Feel the Wear, Runtastic, ...) but mainly I have deactivated Google Fit which is a true battery killer app on both the Smartwatch and the Smartphone!.
mediafire link is dead (twrp) - please, reupload it!
Thanks so much for this, it worked perfectly! So great to have my watch back!
Hi, I have problem connecting in ADB mode to PC - when I plug in craddle nothing is happening Win10 not even play a sound, not trying to find drivers etc. Is it connected with new version NXG47C/LENOKZ22b ??
In fastboot mode there is green "secure boot" enabled, lock state - locked and bootloader in Z22b version. Is it possible to connect ADB in this case? Im stucked witn AW2 and there is nothing I can do for now Please help.
the stable version is out.
N960NKSU3DSLC
you can download from sammobile or frija.
Update:
I installed successfully all the 3 files using the links provided in this thread, using adb.
• Installation guide ( credits goes to @Arteush):
• With ADB :
- Download and extract SDK Platform Tools
- Rename the downloaded .bin file to update.zip
- Copy it to the same folder where you previously extracted SDK Platform Tools
- Reboot your phone in recovery mode (Hold power+bixby+volume up buttons while rebooting)
- Select Apply update from ADB
- Plug the phone to your computer and start a terminal in the folder containing the update.zip and the SDK Platform Tools
- Execute the command ./adb sideload update.zip
- It will start the update and reboot your phone once it finish
• With a microSD :
- Rename the downloaded .bin file to update.zip
- Copy it to your microSD
- Reboot your phone in recovery mode (Hold power+bixby+volume up buttons while rebooting)
- Select Apply update from SD card
- Navigate and select the previously copied update.zip
- It will start the update and reboot your phone once it finish
this is the link to Arteush thread:
this is the link to the main beta file to be flashed first and than download from the links provided from our friend Pichai.
Download link - beta 1 from CSJ1 to ZSK6
donwload link - beta 1 Hotfix only
download link - beta 2 ZSKH
Its seams that we are quite behind from the international model in the beta updates-with links provided for manual updates.
I did some research and i didn't found the fota links for update 3/4... i have to postpone my research because i have some exams but feel free to post it here if you come by those links.
Beta 2: http://fota-secure-dn.ospserver.net...1SZzx7N8HbHdc=&px-nb=UGtezEZ854jbmFcvWGxLEA==
Beta 3:http://fota-secure-dn.ospserver.net...1SZzx7N8HbHdc=&px-nb=UGtezEZ854jbmFcvWGxLEA==
pichai said:
Beta 2: http://fota-secure-dn.ospserver.net...1SZzx7N8HbHdc=&px-nb=UGtezEZ854jbmFcvWGxLEA==
Beta 3:http://fota-secure-dn.ospserver.net...1SZzx7N8HbHdc=&px-nb=UGtezEZ854jbmFcvWGxLEA==
Click to expand...
Click to collapse
Thanks so much my friend.
Even thought you posted only the 2 last betas i was able to find the main beta link using your link.
Thanks again.
Thank you for sharing firmwares! Waiting for Beta 3 to Beta 5!
dahyuk0413 said:
Thank you for sharing firmwares! Waiting for Beta 3 to Beta 5!
Click to expand...
Click to collapse
me too, i keep searching but until now no luck.
ubejd said:
me too, i keep searching but until now no luck.
Click to expand...
Click to collapse
Is the latest beta uploaded here good enough for daily driver or is it too buggy?
imkentoy said:
Is the latest beta uploaded here good enough for daily driver or is it too buggy?
Click to expand...
Click to collapse
I did installed in my note 9, until now everything works fine, i noticed a little freezes once or twice a day, besides that every thing seams fine.
My battery is better.
The phone seems to respond faster.
Just to be careful I did remove my locks from my phone because there were some bugs reported ( i dodnt know in which beta) that made you restore your phone because you weren't able to unlock your phone.
ubejd said:
I did installed in my note 9, until now everything works fine, i noticed a little freezes once or twice a day, besides that every thing seams fine.
My battery is better.
The phone seems to respond faster.
Just to be careful I did remove my locks from my phone because there were some bugs reported ( i dodnt know in which beta) that made you restore your phone because you weren't able to unlock your phone.
Click to expand...
Click to collapse
Thanks. I didn't remove the passwords/pins and it seems working on my end. Looking forward for the beta 3 4 5 links. :laugh:
Stable Android 10 for Note 9 has been released as per Sammobile. For india beta testers for now.
Any updates?
Pse e hapni kot forumin kur nuk ktheni përgjigje dhe as nuk jepni informacion!?
Taulant Datja said:
Pse e hapni kot forumin kur nuk ktheni përgjigje dhe as nuk jepni informacion!?
Click to expand...
Click to collapse
if any update cames out i will post it right away, but we had no luck until now.
( in the end this is a community that tries to help each others, so dont ask like we own you ).
No updates yet!
Samsung Forum Korea, note9(https://r1.community.samsung.com/t5/질문/운영자-노트9베타나정식버전-업뎃언제/m-p/3067158#M712)!
---------- Post added at 06:06 AM ---------- Previous post was at 05:56 AM ----------
Steps to make dual card on Samsung Galaxy Note 9 N960N:
*
1.Open your phone and go to Settings> Developer Options and enable OEM unlock and USB debugging
2. Open Chimera Phone Utility and connect Note 9 to your computer. When prompted, remember to check the "Always allow from this computer" option
Click Restart> Read Certificate
3. After successfully reading the Cert, you need to refresh the TWRP recovery.
4. When finished, press the power + volume down button to turn off the phone. Next, immediately quickly press Bixby + Volume + + Power button to start TWRP recovery.
5. Click Wipe> Format Data and enter yes. The computer will immediately detect your phone's internal storage.
6. All you need now is to copy the custom ROM to your phone and flash it.
7. When finished, just restart your phone. Install Root Explorer to check root access. If your Galaxy Note 9 is not yet ROOT, you should delete or update Magisk on your phone
8. Open Root explorer => set permissions => Root => EFS => find PROP and edit.
9. Original:
ro.multisim.simslotcount = 1
ro.vendor.multisim.simslotcount = 1
persist.radio.multisim.config = SS
Edited as:
ro.multisim.simslotcount = 2
ro.vendor.multisim.simslotcount = 2
persist.radio.multisim.config = DSDS
*
10. Connect the phone to the computer again. When you see "SIM card has been transferred", please use it alone, do not restart the phone.
11. Re-open Chimera => tick on Imei 2 => write certificate, this is what I read before
12. The tool will warn you with some notifications. Just ignore it and click OK => OK => Write ...
I use a dual SIM card on the N960N, so I can't go back to the official system, he will invalidate my second sim! If you are interested, you can also use two sim cards on N960N!
Today l received android 10 official update through OTA update. Very smooth :laugh:
Taulant Datja said:
Today l received android 10 official update through OTA update. Very smooth :laugh:
Click to expand...
Click to collapse
Thats great news.
How to upgrade from beta to final now?
SkyZ0ro said:
How to upgrade from beta to final now?
Click to expand...
Click to collapse
you will have to go to latest pie version with odin, and then use odin(or check for update in the app if you havent root your phone) again to update to andorid 10.
Hello everyone! After android 10 stable update, does anyone have bugs with the pop-up view. For example what's up, when messages arrive, sometimes shows on pop-up view sometimes not, most of the time l have to manually open to pop-up view. Does anyone know how to fix this? Thank you
I upgard my phone but i lose the seconde sum
My phone whille be single sim. Help me
cheikoooo said:
I upgard my phone but i lose the seconde sum
My phone whille be single sim. Help me
Click to expand...
Click to collapse
if you have an n960n dual sim that means that your phone had a custom rom/was rooted, and when you returned to stock you lost your dual sim, just root your phone and flash again a custom rom with dual sim support.