Develop Bugs

ITL41F update link

Got a notification for a system update. Pulled the link from logcat:
http://android.clients.google.com/p....signed-yakju-ITL41F-from-ITL41D.11bbbccb.zip
Sorry if this has already been posted.

Many thanks - I also got the update when I checked it

It downloaded a zip file to my phone. What do I do with it?
Thanks.
Rik.
Sent from my Galaxy Nexus using Tapatalk

Just had my notification for the update

Just downloaded, its only 960k?
Edit
Am on custom rom is why its a zip. Only can be used on stock I guess.
Sent from my Galaxy Nexus using xda premium

aindow said:
It downloaded a zip file to my phone. What do I do with it?
Thanks.
Rik.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Flash it from ClockworkMod recovery
Use this guide to root:
http://forum.xda-developers.com/showthread.php?p=19465384&posted=1#
Install RomManager from the market then flash ClockworkMod recovery from there and flash the .zip from there
Or just wait for it to come OTA

spences10 said:
Flash it from ClockworkMod recovery
Click to expand...
Click to collapse
You tried?
Sent from my Galaxy Nexus using xda premium

The Gingerbread Man said:
Just downloaded, its only 960k?
Click to expand...
Click to collapse
yes it's only 960kb

spences10 said:
Flash it from ClockworkMod recovery
Use this guide to root:
http://forum.xda-developers.com/showthread.php?p=19465384&posted=1#
Install RomManager from the market then flash ClockworkMod recovery from there and flash the .zip from there
Or just wait for it to come OTA
Click to expand...
Click to collapse
Thanks am rooted and got cwm. Guess we loose root after flashing
Sent from my Galaxy Nexus using xda premium

oscillik said:
yes it's only 960kb
Click to expand...
Click to collapse
Just seems rather small,: had a look through and looks to be a lot of things. Thought could be a bad download.
Sent from my Galaxy Nexus using xda premium

The Gingerbread Man said:
Just seems rather small,: had a look through and looks to be a lot of things. Thought could be a bad download.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
screenshots showing update size
from all accounts so far, the update has only really made changes to the kernel. so the update would only be small.

I'm stock so I just applied it and it seems fine. No obvious changes. I tried a USB game controller and it still didn't work so I think its just the volume bug fix (although there are alot of patch files in the zip).
I don't know how to apply it manually I'm afraid now we don't have the /sdcard partition accessible via USB mass storage. Could try renaming to update.zip, putting in the root of MTP storage, booting into recovery (hold vol down and power) and see if it can be applied?

footboydog said:
Got a notification for a system update. Pulled the link from logcat:
http://android.clients.google.com/p....signed-yakju-ITL41F-from-ITL41D.11bbbccb.zip
Sorry if this has already been posted.
Click to expand...
Click to collapse
Thanks for posting this!

footboydog said:
I'm stock so I just applied it and it seems fine. No obvious changes. I tried a USB game controller and it still didn't work so I think its just the volume bug fix (although there are alot of patch files in the zip).
I don't know how to apply it manually I'm afraid now we don't have the /sdcard partition accessible via USB mass storage. Could try renaming to update.zip, putting in the root of MTP storage, booting into recovery (hold vol down and power) and see if it can be applied?
Click to expand...
Click to collapse
i've already tried that, it doesn't work unfortunately

The Gingerbread Man said:
Just seems rather small,: had a look through and looks to be a lot of things. Thought could be a bad download.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yeah you loose root, but that guide didn't take five minutes to get back root again, when you flash it from cwmr there is a lot of updates going on

Just downloaded from my stock GN, 0.94mb and when I try to open it says Cannot open file. Ah well, guess I have to wait for tommorow.

spences10 said:
Yeah you loose root, but that guide didn't take five minutes to get back root again, when you flash it from cwmr there is a lot of updates going on
Click to expand...
Click to collapse
Will probably wait and hope the roms are updated tomorrow. If I didn't have work at 6.30am id go and root again tonight but really can't be assed right now lol
Sent from my Galaxy Nexus using xda premium

Whats needed here if we rooted with Superboot R3?

Evostance said:
Whats needed here if we rooted with Superboot R3?
Click to expand...
Click to collapse
Rom manager, then to flash cwm recovery through that and then root again (optional)
Sent from my Galaxy Nexus using xda premium

CWM won't work if you have encrypted your device. Damn...

[HOW-TO] CMW on LTE Version through Rom Manager

If you have any questions, concerns or problems, please post in the CDMA post because I will no longer be checking here.

theboo7 said:
This is a guide on how to get ClockWorkMod onto your LTE Galaxy Nexus through Rom Manager
Go to market, search "Clockworkmod"
Install Rom Manager*
Open up Rom Manager and select "Flash ClockworkMod Recovery"
A pop-up will come up called "Confirm Phone Model," of course choose "Google Galaxy Nexus CDMA"
Now let it install etc, then with a File Manager** with SU access, Go to system, click "Mount R/W"(if using Root Explorer) and then scroll down until you see "recovery-from-boot.p" and rename it to "recovery-from-boot.p.bak"
Close out off your File Manager and go to Rom Manager and select "Reboot into Recovery"
There you go
You should be able to boot into CWM
* Free version works
**I used Root Explorer
Click to expand...
Click to collapse
For starters that file doesnt exist under the directory "system"

jgrimberg1979 said:
For starters that file doesnt exist under the directory "system"
Click to expand...
Click to collapse
By "that file" I'm assuming you are referring to "recovery-from-boot.p" ?

jgrimberg1979 said:
For starters that file doesnt exist under the directory "system"
Click to expand...
Click to collapse
Could be because you are on a custom ROM. I am on Android Revolution HD and I don't see it at all as well. I also can directly boot from ROM Manager directly into CWM. I never touched this file at all and I never looked for it.

staticx57 said:
Could be because you are on a custom ROM. I am on Android Revolution HD and I don't see it at all as well. I also can directly boot from ROM Manager directly into CWM. I never touched this file at all and I never looked for it.
Click to expand...
Click to collapse
I'm on stock 4.0.2
updated OP to reflect the OS version I'm talking about.
Accidental thanks btw

theboo7 said:
I'm on stock 4.0.2
updated OP to reflect the OS version I'm talking about.
Accidental thanks btw
Click to expand...
Click to collapse
I had to do this same thing on stock to keep the stock recovery from restoring.

jermaine151 said:
I had to do this same thing on stock to keep the stock recovery from restoring.
Click to expand...
Click to collapse
Yeah it's a known bug, that's hopefully getting worked on.

Thank you for this! Now one question if I didn't do this and the stock recovery booted what would be the steps too get this recovery installed?
Sent from my Galaxy Nexus using Tapatalk

dc iz 2 legit said:
Thank you for this! Now one question if I didn't do this and the stock recovery booted what would be the steps too get this recovery installed?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Then you would follow the steps in the OP

What are the benefits to doing this final part. Is it necessary? Some say they didn't do this? Now on the Thunderbolt I didn't have to have rom manager installed and I could still boot into recovery. Is this the same? If I rename that file (which is in my system directory) will I be able to boot into cwm at any point?
Thanks I have done everything with the exception to this. Wondering if its necessary?
Edit: I guess I should have waited for a response because I went ahead and followed the steps in the OP and it came up with an android with a red triangle. Pulled that battery and booted up ok. Any info I need to be aware of? I wasn't able to boot into recovery from rom manager at first. I can now boot into recovery after reflashing CWM recovery but cannot do anything once I am in it?

Xirix12 said:
What are the benefits to doing this final part. Is it necessary? Some say they didn't do this? Now on the Thunderbolt I didn't have to have rom manager installed and I could still boot into recovery. Is this the same? If I rename that file (which is in my system directory) will I be able to boot into cwm at any point?
Thanks I have done everything with the exception to this. Wondering if its necessary?
Edit: I guess I should have waited for a response because I went ahead and followed the steps in the OP and it came up with an android with a red triangle. Pulled that battery and booted up ok. Any info I need to be aware of? I wasn't able to boot into recovery from rom manager at first. I can now boot into recovery after reflashing CWM recovery but cannot do anything once I am in it?
Click to expand...
Click to collapse
Flashing through ROM Manager is just a simpler way to get CWM. And I'm not sure why you would have gotten the red triangle, unless you didn't rename/delete the file in system. And I haven't heard anyone say the couldn't do anything in recovery, so I'm not sure what the problem is there.

When I try and change the file name it says insufficient permissions??
I have root...
Cwm doesn't stick though. I always have to boot reflash recovery and then boot into recovery through from manager..
Any suggestion?
Sent from my Galaxy Nexus using XDA App

civicsisedan said:
When I try and change the file name it says insufficient permissions??
I have root...
Cwm doesn't stick though. I always have to boot reflash recovery and then boot into recovery through from manager..
Any suggestion?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Your file manager doesn't have root privileges, so until you rename/delete the file you won't be able to reboot into CWM

theboo7 said:
Your file manager doesn't have root privileges, so until you rename/delete the file you won't be able to reboot into CWM
Click to expand...
Click to collapse
This. I was using astro but changed to root explorer and changed file name. Turned phone off and went into fast boot and then recovery and it worked.
To be clear, I was able to go into recovery before. I would have to open from manager, reflash cwm and boot into recovery.
I was just unable to power phone off and boot into recovery manually. Now I can.
Sent from my Galaxy Nexus using XDA App

civicsisedan said:
This. I was using astro but changed to root explorer and changed file name. Turned phone off and went into fast boot and then recovery and it worked.
To be clear, I was able to go into recovery before. I would have to open from manager, reflash cwm and boot into recovery.
I was just unable to power phone off and boot into recovery manually. Now I can.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Okay, so glad that you got it sorted out
Sent from my Galaxy Nexus using XDA App

this step by step process was incredibly easy. thank you!!!

reflekt2099 said:
this step by step process was incredibly easy. thank you!!!
Click to expand...
Click to collapse
Your welcome
Sent from my Galaxy Nexus using XDA App

Thanks for the reply. I did rename it the file to .bak following the script to the t! I don't know what happened either. Since then I deleted the file entirely this time and reflashed the cwm seems to work a little better than before an now I can do things in cwm recovery. Hope nothing else goes crazy.
Sent from my Galaxy Nexus using Tapatalk

Xirix12 said:
Thanks for the reply. I did rename it the file to .bak following the script to the t! I don't know what happened either. Since then I deleted the file entirely this time and reflashed the cwm seems to work a little better than before an now I can do things in cwm recovery. Hope nothing else goes crazy.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Yeah, that file can cause problems with CWM on LTE, although it's a quick fix, I'm sure it's being worked on for future editions. And since you've been able to flash things, when you use the volume keys to high light options, does it skip one or two every now and then? That's only problem I seem to be having.

theboo7 said:
when you use the volume keys to high light options, does it skip one or two every now and then? That's only problem I seem to be having.
Click to expand...
Click to collapse
Same here. You gotta go slow. I selected the wrong option many times.

JB OTA won't install- says install untrusted zip? in cwm

I started doing the Google framework force stop and clear cache today while on wifi and was prompted after 5 or 6 tries. It downloaded, verified download, rebooted and TRIED to install. About 15% through, it said untrusted zip and cwm screen popped up top and asked 'install untrusted zip?' Of course I hit yes.. why isn't it trusted? Its straight from the carrier. Anyway it immediately said installation aborted. I repeated this process again and got the same results. Please someone help. Now that JB is finally here my phone won't take it???
Sent from my Galaxy Nexus using xda app-developers app

Your phone is rooted? If yes you can't install OTA updates

I'm rooted yes. So what do I do? Unroot?
Sent from my Galaxy Nexus using xda app-developers app

htc_woe_is_me said:
I started doing the Google framework force stop and clear cache today while on wifi and was prompted after 5 or 6 tries. It downloaded, verified download, rebooted and TRIED to install. About 15% through, it said untrusted zip and cwm screen popped up top and asked 'install untrusted zip?' Of course I hit yes.. why isn't it trusted? Its straight from the carrier. Anyway it immediately said installation aborted. I repeated this process again and got the same results. Please someone help. Now that JB is finally here my phone won't take it???
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
If you have CWM flashed, you have to manually flash the update -- it won't install over-the-air. If you want to install it over-the-air, flash back the stock recovery then accept the update.
polimeno said:
Your phone is rooted? If yes you can't install OTA updates
Click to expand...
Click to collapse
Not true. Root makes no difference.

efrant said:
If you have CWM flashed, you have to manually flash the update -- it won't install over-the-air. If you want to install it over-the-air, flash back the stock recovery then accept the update.
Not true. Root makes no difference.
Click to expand...
Click to collapse
So either way I will lose all my settings, home screens and what not?
I used Galaxy Nexus Toolkit to do all of my rooting, installing CWM and all-- is there a way to accomplish what I need to on there?

efrant said:
If you have CWM flashed, you have to manually flash the update -- it won't install over-the-air. If you want to install it over-the-air, flash back the stock recovery then accept the update.
Not true. Root makes no difference.
Click to expand...
Click to collapse
It's exact. But root can only be done if you have bootloader unlocked, and with unlocked bootloader can not install OTA updates

htc_woe_is_me said:
So either way I will lose all my settings, home screens and what not?
Click to expand...
Click to collapse
No, updating using an OTA update file will NOT make you lose anything.
htc_woe_is_me said:
I used Galaxy Nexus Toolkit to do all of my rooting, installing CWM and all-- is there a way to accomplish what I need to on there?
Click to expand...
Click to collapse
I can't help you out with the toolkit, but have a look at my signature for some useful links on doing things without a toolkit.

efrant said:
No, updating using an OTA update file will NOT make you lose anything.
I can't help you out with the toolkit, but have a look at my signature for some useful links on doing things without a toolkit.
Click to expand...
Click to collapse
OK, so the best thing would be to flash the stock recovery? Sorry for all the questions, and I really appreciate all your help. I swear I used to know how to do this crap on my Dinc, but it's been years since I did all that.

htc_woe_is_me said:
OK, so the best thing would be to flash the stock recovery? Sorry for all the questions, and I really appreciate all your help. I swear I used to know how to do this crap on my Dinc, but it's been years since I did all that.
Click to expand...
Click to collapse
Go to the Google page with all the images and download the mysid IMM76K image, extract the recovery.img from within, and flash it using fastboot: fastboot flash recovery recovery.img

efrant said:
Go to the Google page with all the images and download the mysid IMM76K image, extract the recovery.img from within, and flash it using fastboot: fastboot flash recovery recovery.img
Click to expand...
Click to collapse
OK, I'm trying this now... I downloaded the images from Google.. extracted its contents... found the recovery image file. Do I need to put that file into a zip file?

htc_woe_is_me said:
OK, I'm trying this now... I downloaded the images from Google.. extracted its contents... found the recovery image file. Do I need to put that file into a zip file?
Click to expand...
Click to collapse
Gnex Toolkit wasn't working because of some missing file... re-installed it and flashed the stock recovery via Gnex Toolkit (I think). Is there a way to check which recovery is running? Anyway, if it is indeed stock, I just got prompted again for the OTA JB update.. it's installing now.... fingers crossed!!!
..OK so now it rebooted... started installing, got about halfway through.. paused, then it went to the stock recovery screen and stayed with a red triangle around an exclamation point! What is happening here?!
I have now re-locked the bootloader and received the prompt for OTA again....

Still won't work for me. I've tried even flashing the stock image and it won't install at all. Actually nothing is installing.
I've never done anything to the phone besides unlocking the BL and rooting and switching to CWM. It seems to have something to do with the SD mount.. nut then again I have no idea.
Where's all the Android gurus at?
Sent from my Galaxy Nexus using xda app-developers app

htc_woe_is_me said:
Still won't work for me. I've tried even flashing the stock image and it won't install at all. Actually nothing is installing.
I've never done anything to the phone besides unlocking the BL and rooting and switching to CWM. It seems to have something to do with the SD mount.. nut then again I have no idea.
Where's all the Android gurus at?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Follow the instructions in the "update" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2

Guys i am having this EXACT problem, except on a S4 (I337M to be exact)
Here is my thread with the details
http://forums.androidcentral.com/as...t-update-ota-failure-using-triangle-away.html
But basically, im just wondering how i can get stock recovery back and get this ota to work!!!
Thanks!

att fusion 2 / u8665

Hello so I am new to these forums but have used them in the past for assistance. I have been trying to root a att fusion 2 aka u8665 ive seen a couple posts on here about how to and someone said they were successful but vauge steps cause frustration.
http://forum.xda-developers.com/showthread.php?t=1920528
http://forum.xda-developers.com/showthread.php?t=1976657
As i said i have been trying for a while and basically tried everything listed in those two posts, also the post where they said they managed to attain root through fastboot confused me. From what i understood fastboot needs root to be able to operate, otherwise the steps in the post about using adb i just keep running into permission issues where i cant mount anything to root it.

I had trouble myself, but figured it out. I recompiled all the files posted by RFE.
https://www.dropbox.com/s/lm11rrn3z5c2j6v/Huawei-Fusion-2-Recovery-Root.zip
Sent from my NookColor using xda app-developers app

still stuck
thank you for the quick response, but see the issue i was having is that fastboot is installed through the adb, yet i cant get it to recognize my device. but again thanks for the quick reply but one last thing this recovery.img is it a pre rooted image?

gm4n1989 said:
thank you for the quick response, but see the issue i was having is that fastboot is installed through the adb, yet i cant get it to recognize my device. but again thanks for the quick reply but one last thing this recovery.img is it a pre rooted image?
Click to expand...
Click to collapse
were you able to root?
and yes, the recovery.img installs SuperSu on reboot
Sent from my NookColor using xda app-developers app

fastboot not seeing device
RoboticBuddy said:
were you able to root?
and yes, the recovery.img installs SuperSu on reboot
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
not yet i am going to try again in a bit here though, still running into issues where fastboot will not recognize the device. im guessing a driver issue, except not sure why they wont work.

RoboticBuddy said:
were you able to root?
and yes, the recovery.img installs SuperSu on reboot
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
ok so i got to where i need to use the actual flash command but it returns a error " cannot determine image filename for 'recover.img' "

RoboticBuddy said:
were you able to root?
and yes, the recovery.img installs SuperSu on reboot
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
thank you all rooted now

RoboticBuddy said:
I had trouble myself, but figured it out. I recompiled all the files posted by RFE.
https://www.dropbox.com/s/lm11rrn3z5c2j6v/Huawei-Fusion-2-Recovery-Root.zip
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
If anyone else would like to contribute please do. I've had 5 attempts at registering this type of device without triggering a call-home. I've swapped out 90% of all the components that brand the phone AT&T (including huawei-hardware-extensions & mobile phone "care"??). When using Titanium Backup you will notice that some of the specially protected APK files cannot be removed or "found" - you will get the message "APK file not found." The only way to get around this is to use fastboot and pull the file from the device before removing it. If you remove the wrong system APK your phone won't be bricked, but it will give you infinite android.acore force close loops and other nasty crippling bugs (such as no touch-keys backlight). If you want to be sure that you are not doing any damage, do a full reboot and cache clear after uninstalling any of the AT&T prepaid system components. Many of the system components can not be removed or replaced with other versions until their dependencies are replaced or removed as well. Titanium Backup once again comes in handy and lets you select an android ID or "profile" which is a UID that is tied to your Google Play / Android Market account. You will have to create a new random Android ID after you have have replaced all the apps. Make sure you remove any files like Twitter that have been specially made for this phone & include a long unique ID like Twitter-3-6-0-(123456)--00000_V300_001.APK - the phone is incredibly fast without any google or ATT stuff on it.

[Q] Updating from JWR66N to JSS15R forcibly

I've recently purchased a Nexus 7 (2013) tablet and it turned out to be all faulty - it constantly reboots and the home button doesn't work. Within the next 2 days that I'm staying in the US I have to make a decision whether to return the device to Google (because returning it from my part of the world would cost more than the nexus itself). But prior to that I'd like to update it to see if it fixes the issues. My device's build number is JWR66N but I've heard that the latest build is JSS15R. Going to settings and checking for updates manually doesn't show any OS updates available and the OS says it is up to date. How do I update the device from JWR66N to JSS15R forcibly? Thanks in advance.

Try to clear data of download manager, Google services framework and reboot. Do that 1-3 times and you should get notification about ota.
Sent from my Nexus 7 (2013) using Tapatalk 4

Muikkuman said:
Try to clear data of download manager, Google services framework and reboot. Do that 1-3 times and you should get notification about ota.
Sent from my Nexus 7 (2013) using Tapatalk 4
Click to expand...
Click to collapse
Sorry about my ignorance, but how to do that?

mikhailitsky said:
Sorry about my ignorance, but how to do that?
Click to expand...
Click to collapse
Go to settings -> apps -> then swipe to "all" and find the apps in the list :thumbup:
Sent from my Nexus 7 (2013) using Tapatalk 4

Muikkuman said:
Go to settings -> apps -> then swipe to "all" and find the apps in the list :thumbup:
Click to expand...
Click to collapse
Thank you, Muikkuman, this helped to detect the update.

I had mine rooted and it prompted an update but when I reboot to install, it brought me to twrp recovery. Any idea how to I bypass that?

fkfs9 said:
I had mine rooted and it prompted an update but when I reboot to install, it brought me to twrp recovery. Any idea how to I bypass that?
Click to expand...
Click to collapse
Anybody?

Just download the OTA manually, place on your virtual sdcard, and choose install in TWRP.

sfhub said:
Just download the OTA manually, place on your virtual sdcard, and choose install in TWRP.
Click to expand...
Click to collapse
Errrrr where can I download the ota from?

http://forum.xda-developers.com/showthread.php?t=2448015
fkfs9 said:
Errrrr where can I download the ota from?
Click to expand...
Click to collapse

tried with no luck?
I tried your recommendation several times with no luck, I am still stuck on JWR66N. Do you have any other thoughts as to how to get this update on my tablet?
Thanks!

vulcaninvt said:
I tried your recommendation several times with no luck, I am still stuck on JWR66N. Do you have any other thoughts as to how to get this update on my tablet?
Thanks!
Click to expand...
Click to collapse
Not sure what you tried or what problems you ran into.
If you want to force JSS15R onto your tablet I would suggest this:
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279