Related
Hey Guys, did anyone else get the update for the new android 2.0.1 notification on their phone.
I just got it and i started downloading it...
Really? post the log so we can get the download link
http://i6.photobucket.com/albums/y225/Makaveli6924_7/2009-12-29-144007.jpg
How do i get the log?
Why put this in this section?
why does it say for motorola droid??
This thread is putting my BS meter into overdrive. Of course, its also putting my stupidity meter into overdrive too LOL
~DM
That's why i posted my question here to see if anyone else got the notification, it's weird man.. what do you think is happening, i have a rooted phone also?
What rom did you have when you received the update notfication?
I have the first 1.6 root, i can't remember who made the rom.
http://i6.photobucket.com/albums/y225/Makaveli6924_7/2009-12-29-153540.jpg
I might not too sure then. You could try it and see if it works and check if the camera works. Although I can't be held responsible if anything goes wrong. Try and look up on how to get a log so we can also get a link to the ota update.
Not really possible if you ask me. It's from Verizon, which shouldn't hit your phone unless you're on their network from what I understand and that isn't possible because Dreams don't support CDMA.
As for the update, it would be much larger than 10.2MB, which means what you're downloading is the update to go from 2.0 on a DROID to 2.0.1.
M..N said:
I might not too sure then. You could try it and see if it works and check if the camera works. Although I can't be held responsible if anything goes wrong. Try and look up on how to get a log so we can also get a link to the ota update.
Click to expand...
Click to collapse
if he has root, he shouldn't be getting ota updates, should he?
it makes me suspicious because it gives the verizon site and refers to the phone as "your Motorola DROID"
I wouldn't touch that "update" with a 10ft pole! Either fake, he forced the download, or something seriously messed up is going on, but that does not look to be a legit update for the G1.
grandomegabosses said:
if he has root, he shouldn't be getting ota updates, should he?
it makes me suspicious because it gives the verizon site and refers to the phone as "your Motorola DROID"
Click to expand...
Click to collapse
You can still get OTA updates with root, it just depends on what ROM you use. I believe very old CyanogenMOD and other ROMs had OTA still turned on.
OP - While you're posting pictures, can we see a picture from under Settings > About Phone? Be sure to include firmware version :]
My guess would be that his build.trout.prop has the droid fingerprint/keys/device id in it, or he is using a droid build.prop and he will most likely soft brick his device. I hope there is no radio update, so it doesn't get true bricked.
jerhoyet said:
You can still get OTA updates with root, it just depends on what ROM you use. I believe very old CyanogenMOD and other ROMs had OTA still turned on.
OP - While you're posting pictures, can we see a picture from under Settings > About Phone? Be sure to include firmware version :]
Click to expand...
Click to collapse
you're not supposed to be getting them. weird. i haven't gotten one ota update notification ever since i rooted. and that was more than a year ago. pre-cupcake.
Ok guys i got bad news, the stupid update didn't do anything to my phone. Once the download completed, I restarted the phone and still was running my rooted 1.6. Also I checked the system update and it is still shows the Android 2.0.1 update.
afghanali said:
Ok guys i got bad news, the stupid update didn't do anything to my phone. Once the download completed, I restarted the phone and still was running my rooted 1.6. Also I checked the system update and it is still shows the Android 2.0.1 update.
Click to expand...
Click to collapse
Are you sure you're running a 1.6 ROM?
Can we see a screenshot or picture from Settings > About Phone?
Has anyone else received this update?
Not here.
Los Angeles, CA
lol figures once i get root an update starts rolling out, it probably enables wifi n like they released for the EVO today.
1.22.605.2 is the software version i have (rooted)
It adds 3G Mobile hotspot and fixes the signal issue, im in a pickle now though lol. cant remove superuser
Not exactly a pickle - just don't do the upgrade, wait for someone else to take the OTA download and make it root-safe.
where did you confirm this info as to what the update offers?
I guess i am confused, what would happen if we did the update with our rooted phones?
Nothing. Because with rooted phones you won't see the OTA Update...but if you were to manually upgrade without it being root proofed....you'd loose root.
Wait - weren't we already at 1.22.605.2? That's what rev I'm running, and I haven't taken an OTA since the first few days after launch.
giantcrazy said:
Wait - weren't we already at 1.22.605.2? That's what rev I'm running, and I haven't taken an OTA since the first few days after launch.
Click to expand...
Click to collapse
Incredible OTA Update 1.65.605.2
I'm confused to, so if you are rooted, you won't see this update? or you will see it and if you do it, you lose root? I have the stock rom, which is what I thought disabled your OTA's is this an incorrect thinking?
giantcrazy said:
Wait - weren't we already at 1.22.605.2? That's what rev I'm running, and I haven't taken an OTA since the first few days after launch.
Click to expand...
Click to collapse
The name of this post is Incredible OTA Update 1.65.605.2 so even though we are at 1.22.605.2 that is not 1.65.605.2
Thats the thing, i was rooted and did get the OTA update notifications, hit accept for the update by mistake. And the only reason why i confirmed that info is because i have it on my inc.
P.S sorry lol made a type in the title of the post, its 1.35.605.2
So if you updated as root, did you lose your Root? It is not guaranteed that you would loose it, just likely is all. I feel like they released it to break our Root, and nothing more... but maybe they fixed a few issues too... we have the same screen grounding issue the EVO had, and the recent update fixed theirs... but who knows...
EDIT: Posted an article to an outdated update. Oops...
so i assume you lost root?
Yes i did.
I haven't seen it yet. <-- OHIO
have you tried redoing root? did you loose recovery?
I havent tried redoing the root process again, but how is that going to work? isn't the root process based off of the original software? the baseband is different as well.
Haven't seen it yet either <-- Rhode Island
Didn't find any information on it either. Was their a "more info" link included with yours? as with other OTA updates. Changelog, etc.?
Better question would be, do you have a screen shot of your About Phone page (baseband, software version, etc.)
somebody who gets the update needs to upload the file so a dev can do something with it.
Im just wondering because I have not seen or heard anything in a while.
note crazy said:
Im just wondering because I have not seen or heard anything in a while.
Click to expand...
Click to collapse
May be there is no point any more to do this. Samsung will issue a new update with a patched bootloader and the custom one won't work again. I read on "General Note 3" forum even "towelroot" doesn't work after official update to 4.4.3.
jondoe27 said:
May be there is no point any more to do this. Samsung will issue a new update with a patched bootloader and the custom one won't work again. I read on "General Note 3" forum even "towelroot" doesn't work after official update to 4.4.3.
Click to expand...
Click to collapse
Yes true but if you do not take the update you will be fine I would think most people that have got root will not give it up without a fight I feel as if there is a point to unlock the bootloader because its not there phone its are phone and I want to do whatever I want with a phone I bought I froze the ota updater with titanium back up i will no long allow att to tell me what I can do with my phone . They cant patch something I dont allow and thats that
guys, i have issue while reverting back to factory image with Apr update in the face unlock (Face enrolment didn't work)
i had to go back to factory image with Mar update to get face unlcok working
as of now, face unlock is working either with Mar or DP3 and not working anymore with Apr factory image.
i even tried to update to Apr after flashing Mar factory image through OTA (with working face unlock), and after update to Apr, face unlock will stop working and giving the following error (Can't verify face. Hardware not available).
i am now stucked with Mar update to have face unlock working, and can not update to Apr.
any advise? thanks
I didn't have any problem going back from dp3 to April. Maybe you didn't flash the full rom?
fuarkgl3 said:
I didn't have any problem going back from dp3 to April. Maybe you didn't flash the full rom?
Click to expand...
Click to collapse
i am sure, using Flash-all command with platform tools ver 3.0
dont know what i am missing, i tried to flash Apr few times and the same issue happening.
Adnansaeedhamed said:
i am sure, using Flash-all command with platform tools ver 3.0
dont know what i am missing, i tried to flash Apr few times and the same issue happening.
Click to expand...
Click to collapse
Deleted
The exact same thing has happened to me! I've reflashed the stock April q image like 3 times and face unlock is totally borked. Can't get it to work no matter what I do. Wtf did google do!?
Did you find a solution yet?
CodeFox said:
The exact same thing has happened to me! I've reflashed the stock April q image like 3 times and face unlock is totally borked. Can't get it to work no matter what I do. Wtf did google do!?
Did you find a solution yet?
Click to expand...
Click to collapse
Flashing etc won't solve it, I think the fix needs to come from Google. All other software versions work so I'm assuming the May update will solve it in a weeks time.
If you contact Google they'll want you to boot into safe mode and test it that way but that also doesn't work . They'll offer a replacement handset once you've tried that.
I am on Mar for the moment to get face unlock working, waiting for may update after 10 days
I went onto google chat for support they just want me to go down the warranty claim route... lol...
CodeFox said:
I went onto google chat for support they just want me to go down the warranty claim route... lol...
Click to expand...
Click to collapse
try recovery wipe and side load april ota
alwynjoshy said:
try recovery wipe and side load april ota
Click to expand...
Click to collapse
Doesn't work
alwynjoshy said:
try recovery wipe and side load april ota
Click to expand...
Click to collapse
Done it all mate.
I even fastboot erased every single partition and then flashed April factory image.
It's like dp3 touched some firmware **** for faceunlock IR. Strange it works on march update but not April though and i went back to dp3 and it worked.
It's a shame dp3 is an unstable mess compared to dp2.
Will just wait for may update and fingers crossed that sorts it. Otherwise it looks like Google are sending me a new phone haha.
guys, i have created this post on Google help community, pls upvote there to let google knows about the issue to release a fix
https://support.google.com/pixelphone/thread/42635648?hl=en&dark=0&msgid=42635648
https://www.reddit.com/r/android_be...sue_when_reverting_back_to_apr_factory_image/
Thanks
Adnansaeedhamed said:
guys, i have created this post on Google help community, pls upvote there to let google knows about the issue to release a fix
https://support.google.com/pixelphon...msgid=42635648
https://www.reddit.com/r/android_be...sue_when_reverting_back_to_apr_factory_image/
Thanks
Click to expand...
Click to collapse
The links don't seem to go anywhere mate.
I had the same issue from returning from DP3 to April update. I'm currently staying on DP3.
Google support also wanted me to go down the warranty route, I prefer to keep my phone of course. I am happy I am not alone in this, as this means it's more likely to be addressed by Google.
CodeFox said:
The links don't seem to go anywhere mate.
Click to expand...
Click to collapse
try now, it should work
beache said:
I had the same issue from returning from DP3 to April update. I'm currently staying on DP3.
Google support also wanted me to go down the warranty route, I prefer to keep my phone of course. I am happy I am not alone in this, as this means it's more likely to be addressed by Google.
Click to expand...
Click to collapse
i purchased my Pixel 4 from Google store via freight forwarder to me in Kuwait, to make a return will take ages
Thinking about it I tried Android 11 when it first came out and ever since I can't update past Feb patch. Anything past Feb causes my camera to crash constantly (tries to access libraries that dont exist). I tried everything (different roms, kernels, no root etc..). If the next patch doesn't work I'm going to send it back.
I've decided just to send mine back. My speakers have been a bit strange as of late too, crackly.
It becomes a situation where you have to decide if what you get is worth what you're going to take getting it. I bailed on these things a while back, stock is so good now it isn't like I'm waiting for some killer feature to drop in preview and sample it. It's kinda strange really; I was there on day one with Android and it wasn't long before the roms took off. For quite a while I was getting a new phone every so many months and at times would install new roms daily, sometimes I would try several in an evening. Now I'm sitting here thinking the dev-preview isn't worth the hassle. Not quite sure what I'm trying to say here, I just feel like something has been lost in this game.
krabman said:
It becomes a situation where you have to decide if what you get is worth what you're going to take getting it. I bailed on these things a while back, stock is so good now it isn't like I'm waiting for some killer feature to drop in preview and sample it. It's kinda strange really; I was there on day one with Android and it wasn't long before the roms took off. For quite a while I was getting a new phone every so many months and at times would install new roms daily, sometimes I would try several in an evening. Now I'm sitting here thinking the dev-preview isn't worth the hassle. Not quite sure what I'm trying to say here, I just feel like something has been lost in this game.
Click to expand...
Click to collapse
I relate to this on many levels mate. Within the last year I’ve had a note 9, pixel 3xl, note 10+ and now pixel 4xl. I’ve lost interest in the whole scene really. I only flashed DP3 because a friend of mine asked if I tried it and now here I am sat using an iPhone because my pixel is on its way to a repair centre in Poland. Stock life forever. Not worth the hassle
I really wanted to root my old phone. I did a factory reset and am now on version 6 of android. Any help would be appreciated thank you.
I don't have anything to add but have been working for a few hours trying to get a custom ROM on a LS991ZVI and it is somehow comforting to see another person in 2023 working on this lol.