Related
Hi,
user paugustin posted a link to a new ICS leak ROM (http://forum.xda-developers.com/showpost.php?p=28357252&postcount=630).
Someone has already tried it ?
I'm not rooted so I fear that if something goes wrong (boot loop, freeze, brick...) I cannot recover/unbrick my tablet...
Thanks.
Ok, I see that user civato has prepared new rooted rom 1.054.00 based (original and deodexed) this means that leak rom is working...
So I took courage and installed it and everything goes right, tablet is still working...
I don't see evident differences, nor speed increase...
In settings/info the items different are:
Image version: AV041_A500_RV17RC03_WW_GEN1
Build version: 1.054.00
Image P/N: FM.S14A0.01Y
Wipe or no wipe update?
It was like an ota update...no wipe.
fblasot said:
Hi,
user paugustin posted a link to a new ICS leak ROM (http://forum.xda-developers.com/showpost.php?p=28357252&postcount=630).
Someone has already tried it ?
I'm not rooted so I fear that if something goes wrong (boot loop, freeze, brick...) I cannot recover/unbrick my tablet...
Thanks.
Click to expand...
Click to collapse
Thank you for the heads up, as i was having problems with the first ICS update and i hope this will fix my problem, flash with out problem and so far working great, just waiting now to see if my screen problem happens again.
Oh yeah don't forget to rename the .zip file to update.zip and copy file to external sd card to flash, guess who forgot to do this.
Still 4.0.3 then?
Yes, same android and kernel versions.
I'm glad to see that Acer is still working on updates.
illicitporpoises said:
I'm glad to see that Acer is still working on updates.
Click to expand...
Click to collapse
I've tried it and it feels more laggy, both on browser or on any doc viewer. tried wiping also. still laggy, at least on my device.
Nexus S Jelly Bean Factory Images Now Available For "soju" and "sojua" versions
https://developers.google.com/android/nexus/images
If you prefer to do a clean install of Jelly Bean, or would like to avoid the hassle that may be involved to get the OTA update to work, here is your chance. I am very curious to see if the factory image of the Nexus S includes the old browser, so I will be checking that out a bit later.
I have been waiting for them. Thanks.
Yep I'd quite like to know if the old browser is still in there!
powerarmour said:
Yep I'd quite like to know if the old browser is still in there!
Click to expand...
Click to collapse
Stock browser is there.
I need to get rid of my CDMA phone, so sick of all you GSM users coming first
Goodbye Sprint -_-
How do I know if I'm a "soju" or "sojua"? My baseband is i9020AUCKF1.
DroidChin said:
How do I know if I'm a "soju" or "sojua"? My baseband is i9020AUCKF1.
Click to expand...
Click to collapse
I believe it's under i9020a and you download the 4.1.1 Rom
Sent from my Nexus S
Do the stock images have better battery life than the ota versions?
Just flashed the factory image onto my Nexus S, and it does seem better than the OTA for some reason, as I used to have an issue with creating new folders on the home screen (and a couple of other random glitches) even after doing a factory reset from the OTA.
So yeah, definitely worth doing if anyone is still having odd glitches with the OTA, and it's running great so far and battery life is good :good:
Mudblood69 said:
Do the stock images have better battery life than the ota versions?
Click to expand...
Click to collapse
I don't know how bad the battery was on the OTA, but I'm using the stock image and it's not particularly great on my 1 year old Nexus S. I don't have proper tests, but it doesn't seem like it can go the whole day. I think Google Now is very taxing.
Mudblood69 said:
Do the stock images have better battery life than the ota versions?
Click to expand...
Click to collapse
I think they're pretty much the same thing that came with the OTA.
if YES, is there a way to install it manually to our N7.2?
Someone will probably post it in this thread once the link gets discovered :fingers-crossed:
After that, just flash back the original boot.img and system.img from KRT16S if you are on a custom kernel or have modified any system files, and then flash the OTA, either from a custom recovery or sideload it from the stock recovery
giank30 said:
if YES, is there a way to install it manually to our N7.2?
Click to expand...
Click to collapse
Check here for the factory image.
https://developers.google.com/android/nexus/images
I use the WugFresh tool kit for easy flashing of stock images.
Android 4.1.1 KitKat is rolling out in stages available for N5, N7LTE, N4 but not yet for N7WiFi also factory images for 4.1.1 won't be available till next week. So we have to wait for somebody to get the OTA and grab the link.
it is out. below the llink
http://plus.url.google.com/url?sa=z....90745e15.zip&usg=mrEFavEhbtdgK5R5ZeUD2qSQuyM.
use the THANKS button!
giuvilas said:
it is out. below the llink
http://plus.url.google.com/url?sa=z....90745e15.zip&usg=mrEFavEhbtdgK5R5ZeUD2qSQuyM.
use the THANKS button!
Click to expand...
Click to collapse
Isn't this for the Nexus 7 2013 LTE Version??
http://www.androidpolice.com/2013/12/06/download-android-4-4-1-kot49e-for-the-2013-wifi-nexus-7/
Is there a changeog anywhere?
This feels so weird, i had HTC Desire for like 3 years, and the last OTA i have seen was like 2 years ago.
Now with N7 it's OTA's overload. :laugh:
Aizukaori said:
Is there a changeog anywhere?
Click to expand...
Click to collapse
Don't know. I've heard it's focused on Nexus 5 camera issues. I'm not getting my panties in a wad to install it.
Summit1 said:
Don't know. I've heard it's focused on Nexus 5 camera issues. I'm not getting my panties in a wad to install it.
Click to expand...
Click to collapse
That's pretty much my feel on it. I just installed those dalvik patches yesterday, I don't want to have to flash the stock libraries, wipe cache, and then flash 4.4.1 just for an extremely minor incremental update that isn't even focused on our device.
Summit1 said:
Don't know. I've heard it's focused on Nexus 5 camera issues. I'm not getting my panties in a wad to install it.
Click to expand...
Click to collapse
I believe that there's more to it. 50MB is not that small for a patch, perhaps they ironed out some bugs(there's a hidden wifi bug in 4.4 that I would like to see fixed).
Stability and optimization improvements are always welcome too...
im on Nexus 7 v2 LTE rom 4.4.0 rooted. any body that can help me go to 4.4.1, i tryed adb sideload but gives me error i use wugfresh toolkit
Please continue in this dedicated thread for your updates.
Thank you and thread closed.
Hey guys, I've been having A LOT of issues with the new updates. First the 4.4 and then the 4.4.2 that didn't solve a thing. I've installed them via OTA but after that i've already did:
- factory reset
- installed via fastboot 4.3, then updated via OTA to 4.4.2
- installed via fastboot 4.4, then updated via OTA to 4.4.2
- factory reset AGAIN - installed via fastboot 4.4.2.
I don't know what do to anymore! I can't take pictures because nexus just turns off the moment i take one. I can't install facebook, twitter or instagram and another random apps... And btw, is it normal that in 10 minutes the battery charges to 1% to 50%? i think i never noticed that...
BUT WHAT DO I DO? PLEASE HELP!
UPDATE:
This problem is solved, it was the battery. I've changed the screen recently and it needed a new battery too. Thanks to everyone that tried to help me
just flash the factory images for 4.4.2 via fastboot
Sent from my Nexus 4 using XDA Premium 4 mobile app
saifulh2304 said:
just flash the factory images for 4.4.2 via fastboot
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
how do I do that? sorry but I'm a little noob.
maznex said:
how do I do that? sorry but I'm a little noob.
Click to expand...
Click to collapse
follow the guide here: http://rirozizo.blogspot.com/2013/11/guide-how-to-flash-factory-images-from.html
maznex said:
how do I do that? sorry but I'm a little noob.
Click to expand...
Click to collapse
If you don't know how to use fastboot, use the Wugfresh toolkit, makes life very easy. It has the drivers, downloads recoveries, root files and the factory images. Really is easy with that.
Riro Zizo said:
follow the guide here: rirozizo.blogspot.com/2013/11/guide-how-to-flash-factory-images-from.html
Click to expand...
Click to collapse
maritimesbob said:
If you don't know how to use fastboot, use the Wugfresh toolkit, makes life very easy. It has the drivers, downloads recoveries, root files and the factory images. Really is easy with that.
Click to expand...
Click to collapse
Guys, like I said I used fastboot to install 4.4.2, it still didn't work. I followed this guide googlenexusforum.com/forum/nexus-4-roms/4046-guide-flash-stock-option-using-android-sdk-tools.html
Hey, guys, I haven't updated it to 4.4.2 yet cause my phone is rooted so I'm asking is it worth to go through all the process again? And if yes can anyone state the new features? ☺ thx a lot!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Looks like a hardware issue to me. Probably your battery is faulty... Could explain the shut downs and trying to use the camera usually drains more battery so again that could it be. Could you be more specific about the other errors that you get?
Sent from my Nexus 4 using xda app-developers app
evdrmr said:
Looks like a hardware issue to me. Probably your battery is faulty... Could explain the shut downs and trying to use the camera usually drains more battery so again that could it be. Could you be more specific about the other errors that you get?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Hardware? It started to happen only when I updated the first time via OTA to 4.4.
I open the camera, I try to take a picture, the flash goes on and then the phone goes off. Sometimes I can turn it on and the battery it's the same, sometimes I can't turn it on without connecting to the charger because it goes off when I go to insert the PIN.
Well, after I understood that the problem was that apps, when I turned the WI-FI on, the phone immediately turned off after that I unistalled that apps and when I turned the WI-FI on I could go on Chrome and Play Store, and installed some apps (like n7 player) and everything was OK.
One time I installed Twitter and I used it for a bit and everything seemed fine but then I installed Facebook and the phone crashed again so I unistalled both. Same with Instagram.
I don't know how much more specific I can be... I really need help :s
it's not hardware. anyone who had this phone running pre 4.3 aosp will remember the camera issues and the clicking noises that went along with the focusing and then the reboots. the battery charging is also a widely experienced issue as well as going from a full charge to 50% in a few minutes. I'm getting the camera bug again on 4.4.2 hope a .3 build pops up soon to deal with it. I'm also 100% stock no root
aaronrw said:
it's not hardware. anyone who had this phone running pre 4.3 aosp will remember the camera issues and the clicking noises that went along with the focusing and then the reboots. the battery charging is also a widely experienced issue as well as going from a full charge to 50% in a few minutes. I'm getting the camera bug again on 4.4.2 hope a .3 build pops up soon to deal with it. I'm also 100% stock no root
Click to expand...
Click to collapse
exactly this is happening but on 4.4.2
BTW, when I'm charging the phone, none of this problems happens. I can install and use all apps and use the camera.
maznex said:
exactly this is happening but on 4.4.2
BTW, when I'm charging the phone, none of this problems happens. I can install and use all apps and use the camera.
Click to expand...
Click to collapse
if I were having all those issues I'd try installing the Factory Image again or maybe try 4.4.1 and then use the OTA to update. BUT there is definitely some bugs in the latest KK release
aaronrw said:
if I were having all those issues I'd try installing the Factory Image again or maybe try 4.4.1 and then use the OTA to update. BUT there is definitely some bugs in the latest KK release
Click to expand...
Click to collapse
I did all of that as I refered in the beggining... I will try to install 4.4.1 though, that was the only thing I didn't do, but I doubt it's gonna work, because installing 4.4 and 4.4.2 didn't solve a thing
sorry about the double post but there isn't the factory image for 4.4.1 here... https://developers.google.com/android/nexus/images#occamkot49h .
I tried to flash 4.4.2 following this guide http://rirozizo.blogspot.pt/2013/11/guide-how-to-flash-factory-images-from.html and when I turned it on I had no signal.. what does that mean? I guess it didn't worked..
maznex said:
sorry about the double post but there isn't the factory image for 4.4.1 here... https://developers.google.com/android/nexus/images#occamkot49h .
I tried to flash 4.4.1 following this guide http://rirozizo.blogspot.pt/2013/11/guide-how-to-flash-factory-images-from.html and when I turned it on I had no signal.. what does that mean? I guess it didn't worked..
Click to expand...
Click to collapse
The latest factory images are 4.4.2, that's why you didn't see 4.4.1 on Google's server. When you flash factory images, your radio will also be updated. When you flash a custom ROM, your radio doesn't get updated, that's why you had problem with cell signal. Or flash the appropriate radio for the ROM.
taodan said:
The latest factory images are 4.4.2, that's why you didn't see 4.4.1 on Google's server. When you flash factory images, your radio will also be updated. When you flash a custom ROM, your radio doesn't get updated, that's why you had problem with cell signal. Or flash the appropriate radio for the ROM.
Click to expand...
Click to collapse
The phone asked me to insert PIN and then I had cell signal again.. Should I flash 4.4.2 again flashing the radio too? Because I have the feeling that this will not solve my problem. Like I said in the beggining I followed another guide to flash my phone, and in that guide it said to flash radio and "bootloader-mako..." (not sure what that is) and the cell signal problem still happened and then I couldnt install Facebook or Twitter or had my location on or using the camera without the phone turning off or rebooting...
EDIT: The phone just turned off when updating Google apps, so yeah... Didn't work :s
maznex said:
The phone asked me to insert PIN and then I had cell signal again.. Should I flash 4.4.2 again flashing the radio too? Because I have the feeling that this will not solve my problem. Like I said in the beggining I followed another guide to flash my phone, and in that guide it said to flash radio and "bootloader-mako..." (not sure what that is) and the cell signal problem still happened and then I couldnt install Facebook or Twitter or had my location on or using the camera without the phone turning off or rebooting...
EDIT: The phone just turned off when updating Google apps, so yeah... Didn't work :s
Click to expand...
Click to collapse
You said that when a PIN is input, the phone has signal again which means it's not a radio issue. Did you set up a PIN in the security section in your phone?
taodan said:
You said that when a PIN is input, the phone has signal again which means it's not a radio issue. Did you set up a PIN in the security section in your phone?
Click to expand...
Click to collapse
No this is just something that started to happen along with the other problems... Sometimes the phone loses signal for no reason and goes to the PIN input screen.
maznex said:
No this is just something that started to happen along with the other problems... Sometimes the phone loses signal for no reason and goes to the PIN input screen.
Click to expand...
Click to collapse
Which radio are you using? It should be .98 if you are on KitKat 4.4.2. You can flash a standalone radio zip file in recovery.
taodan said:
Which radio are you using? It should be .98 if you are on KitKat 4.4.2. You can flash a standalone radio zip file in recovery.
Click to expand...
Click to collapse
I don't know I will check later because now I'm not home. But when can I find that zip file and if I flash that it will only solve the cell signal thing right?
The camera won't connect anymore, Wi-Fi won't turn on and the SD card wont mount. How did this get approved by google??
Edit:
To get the OTA to work properly and flash the correct kernal, your CID must be changed to GOOGL001. If you have the GPE device, you don't need to do anything, but if you have a converted GPE then you must change your CID if you want OTA's. This was not made clear in the RUU thread, it was mentioned that changing your CID was optional if you had one of the listed CID's, but it is not optional, but a requirement if you want the OTA's to work.
Everyone that has changed there CID's reflashed the OTA and everything flashed fine, whereas anybody that had not modified there CID had the problem with the kernal.
Psosmith82 said:
The camera won't connect anymore, Wi-Fi won't turn on and the SD card wont mount. How did this get approved by google??
Click to expand...
Click to collapse
maybe you had a bad download?
HRodMusic said:
maybe you had a bad download?
Click to expand...
Click to collapse
I used the download linked from the discussion thread. Put on phone storage, rebooted into recovery and applied the update from phone storage.
Same results with OTA.
Sent from space.
Psosmith82 said:
I used the download linked from the discussion thread. Put on phone storage, rebooted into recovery and applied the update from phone storage.
Click to expand...
Click to collapse
Checked the MD5 before?
Extremer2903 said:
Checked the MD5 before?
Click to expand...
Click to collapse
Used the OTA provided by graffixnyc
Extremer2903 said:
Checked the MD5 before?
Click to expand...
Click to collapse
The signature verification wouldn't apply the update if it saw mismatches.
Archon810 said:
The signature verification wouldn't apply the update if it saw mismatches.
Click to expand...
Click to collapse
Odd.. I had no problems using the OTA zip.. Did you guys try wiping data?
graffixnyc said:
Odd.. I had no problems using the OTA zip.. Did you guys try wiping data?
Click to expand...
Click to collapse
I tried wiping data, still had the same problem. I am reflashing the RUU and will try the ota again. If it doesn't work after the 2nd try, i will just wait for google to send the OTA to me. Wiping data sucks, have to redo everything
Psosmith82 said:
The camera won't connect anymore, Wi-Fi won't turn on and the SD card wont mount. How did this get approved by google??
Click to expand...
Click to collapse
I wonder if this is also being experienced by any other users or if this is specific to your software config and/or some glitch while writing the firmware. I assume you haven't yet tried wiping your /data partition, right?
willverduzco said:
I wonder if this is also being experienced by any other users or if this is specific to your software config and/or some glitch while writing the firmware. I assume you haven't yet tried wiping your /data partition, right?
Click to expand...
Click to collapse
I wiped data and still had problems. I'm working on starting over right now
Then problem should be wiped/not wiped, I think. Anyway, trying with this error stuff is always an excited challenge with me, try to deal with it like that to reduce percentage of throwing your devices away .
Also you need to be FULLY stock.. that includes the stock kernel. If you are running a custom kernel some kernels flash libs and modules. EVERYTHING NEEDS TO BE STOCK
graffixnyc said:
Also you need to be FULLY stock.. that includes the stock kernel. If you are running a custom kernel some kernels flash libs and modules. EVERYTHING NEEDS TO BE STOCK
Click to expand...
Click to collapse
Mine is fully stock. I have an unlocked HTC one, and i flashed the GPE conversion RUU. Does the CID need to be changed to the Google CID
Psosmith82 said:
Mine is fully stock. I have an unlocked HTC one, and i flashed the GPE conversion RUU. Does the CID need to be changed to the Google CID
Click to expand...
Click to collapse
that's a really good question Psosmith
Only thing I can think of on my example is I had 'CF.lumen' installed... Other than that, I had (your) completely stock GPE conversion.
Troubleshooting...
Sent from space.
Is the problem from the update zip or ota+
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Android The Greek said:
Is the problem from the update zip or ota+
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I figured out the problem. I flashed the new RUU that graffix posted with 4.4.3. The Kernal in the OTA is not updating like it should, it stays on the kernal that was made in March. The new Kernal has a date of Thursday May 22nd. So for whatever reason, the OTA is not flashing the new Kernal, which is why all those things were broken. If you use the RUU update, it will flash the new kernal, and everything works as it should.
You'll know right off the bat at first boot. With the OTA, the boot animation hangs and it hangs on the home screen. With the RUU flash, everything is buttery smooth.
Something tells me this problem is occurring for people who actually have a retail M8 that they dirty-flashed using a GPE RUU.
Does anyone with an honest-to-God GPE that was purchased from Google have this problem? If so, this is huge.
Android The Greek said:
Is the problem from the update zip or ota+
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The update worked fine on my device and I used it for the conversion RUU. odd.. I used that very same OTA file. very odd...