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.

Looking for STOCK battery

Hello. You are my last hope. I have ICL53F Galaxy Nexus with stock ROM and try to flash %battey mod, so i lost all soft keys and status bar. But the problem - i forget to make a backup ((((
Please, anybody - can you do me a favor and send to flash through the recovery STOCK battery ? I think this must be no problems for you.
Thank you!

goodcovv said:
Hello. You are my last hope. I have ICL53F Galaxy Nexus with stock ROM and try to flash %battey mod, so i lost all soft keys and status bar. But the problem - i forget to make a backup ((((
Please, anybody - can you do me a favor and send to flash through the recovery STOCK battery ? I think this must be no problems for you.
Thank you!
Click to expand...
Click to collapse
I don't understand what you want? Stock battery?
Sent from my Galaxy Nexus

I want battery, which i have before flash %. But I can't wipe/reset data throught recovery - there is important info. So i guess - yes stock battery from ICS 4.0.2
and if it possible - can you pack it to *.zip so i can flash it without changing.

Please, anybody help me. I have broken phone and can't do nothing with it. Can you post stastus bar+soft key from original ICL53F?

Do you have a GSM or CDMA nexus?
Sent from my Galaxy Nexus using xda premium

GSM Nexus
p.s. not LTE not operator's edition if it helps.

goodcovv said:
GSM Nexus
p.s. not LTE not operator's edition if it helps.
Click to expand...
Click to collapse
Have you considered flashing a rom over what you have? Ahrd is basically stock with improvements. Flashing it over yours will restore your soft keys and status bar
Sent from my Galaxy Nexus using xda premium

But i think it will erase all data, isn't it? That is why i ask anybody to catch everything about battery/soft keys from original and post it here if it possible.

just flash it. the only data you'll lose is SMS and anything thats in /data. your pictures and ringtones and wallpapers should still be there

Wait. I know what to do and you wont lose any data. Give me a minute.
If you don't have zip with your ROM, download this one.
Open that zip with 7zip, go in /system/app/ and drag "SystemUI.apk" on your desktop.
You have rooted GN so I guess you have ADB. Run cmd and enter those commands:
Code:
adb devices
Code:
adb remount
Code:
adb push <full path to the extracted SystemUI.apk> /system/app/SystemUI.apk
Reboot and you should be OK.
Let me know, if it works

1) I think my stock ROM must be the same as
this one
So can i grab systemUI.apk from this one?
2) There is other ways to do it without using ADB?
I FIND HOW IT CAN BE DONE!!
I do everything that you said, but i using ROOTexplorer directly on my phone. THANK YOU! you the best!

goodcovv said:
1) I think my stock ROM must be the same as
this one
So can i grab systemUI.apk from this one?
2) There is other ways to do it without using ADB?
I FIND HOW IT CAN BE DONE!!
I do everything that you said, but i using ROOTexplorer directly on my phone. THANK YOU! you the best!
Click to expand...
Click to collapse
Glad to hear that
Next time do a NANDROID before flashing anything. It's a powerful tool!

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.

[HOWTO] Root Android 4.3 on samsung galaxy nexus

This rooting technique Finally worked you will need three files
1) SDK TOOLS from
2) recovery.img from
3)MRKREHANROOT from
you should have unlock boot loaders USB drivers installed and should be on android 4.3
copy mrkrehanrehanroot3.1.zip in sdcard
be in fastboot mode ie switch off your device and hold both volume up and down and power button together and keep your device connected to PC
Extract the sdktools and place the revovery.img in that folder
then with one finger on shift key right click in an empty space in the folder and select open command window here
then type fastboot flash recovery recovery.img
it will flash recovery to your device
in recovery no need wipe anything install the zip mrkrehanroot3.1.zip
and reboot
download any app that requires root access and check for example root explorer
it should ask root acess
in this way you have rooted your device
Keep the thanks rolling and follow me on

Is that real android 4.3?
Sent from my Galaxy Nexus using Tapatalk 2

imam.krismanto said:
Is that real android 4.3?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
(Y)

imam.krismanto said:
Is that real android 4.3?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
sure from google :angel:

Much Appreciate
I installed the factory image wasn't able to get it to root with mskip'stool soo I gave this a try worked like a champ -Thank you kind sir :laugh:

Not to diss this method of root, but Chainfire's root method works perfectly fine.
https://plus.google.com/113517319477420052449/posts/WqS2E9kkN1L

X_N_ said:
Not to diss this method of root, but Chainfire's root method works perfectly fine.
https://plus.google.com/113517319477420052449/posts/WqS2E9kkN1L
Click to expand...
Click to collapse
I use that method, cannot restore any app with TB or install Busybox, for some reason it's root but not completely.

This thread shouldn't be in dev section, and there were bunch of root method threads/posts that could be easily found.

http://download.chainfire.eu/340/SuperSU/SuperSU-JWR66N-S005-130625-1.41.zip
try this, somebody tried and it works!

_Drifter_ said:
I use that method, cannot restore any app with TB or install Busybox, for some reason it's root but not completely.
Click to expand...
Click to collapse
Read description:
Titanium Backup is an example of such an app. It may incorrectly detect the path to your internal storage for backups, and thus crash on backup/restore. You can fix this by going into preferences and selecting a folder under /storage/emulated/legacy as backup/restore path, not under /storage/emulated/0.
Click to expand...
Click to collapse

msip said:
Read description:
Click to expand...
Click to collapse
No busybox from the apps don't install correctly with chainfire's root. I have the same problem.
Sent from my Galaxy Nexus using xda premium

finally did it

Mohhamad Rehan said:
finally did it
Click to expand...
Click to collapse
Is it posted?
Sent from my Galaxy Nexus using xda premium

checck the thread out buddy

prowede said:
http://download.chainfire.eu/340/SuperSU/SuperSU-JWR66N-S005-130625-1.41.zip
try this, somebody tried and it works!
Click to expand...
Click to collapse
"Please do not mirror this download, do not repost the file elsewhere. Link to this post on G+, not the download."
https://plus.google.com/+Chainfire/posts/WqS2E9kkN1L

ALUOp said:
"Please do not mirror this download, do not repost the file elsewhere. Link to this post on G+, not the download."
https://plus.google.com/+Chainfire/posts/WqS2E9kkN1L
Click to expand...
Click to collapse
OK bro if you say I did thank to u but if u had it you should have shared it first and should have had a guide of it and u should have shared I did it because I spent my whole night flashing recovery and finding proper ways to root it finally did it when I found the file so I flashed the recovery the mini SDK tool they are mine but I did not know who to thank for the root so I just mirrored it but I put up a guide here so its not my fault I am sorry that I hurt the sentiments
Sent from my Galaxy Nexus using xda premium

imam.krismanto said:
Is that real android 4.3?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes it is
Sent from my Galaxy Nexus using xda premium

ALUOp said:
"Please do not mirror this download, do not repost the file elsewhere. Link to this post on G+, not the download."
https://plus.google.com/+Chainfire/posts/WqS2E9kkN1L
Click to expand...
Click to collapse
and as u say buddy its mentions its for S4 and i was brave enough to check it out by editing some scripts and lines and flash it on my devices so i did not copy it fully but i did it on my own risk to check it on my devices and name it after me so if u have any problem with that so be it but i did it i am not chainfire but the day is not so long when i will be like him one day so kindly check it out

Mohhamad Rehan said:
and as u say buddy its mentions its for S4 and i was brave enough to check it out by editing some scripts and lines and flash it on my devices so i did not copy it fully but i did it on my own risk to check it on my devices and name it after me so if u have any problem with that so be it but i did it i am not chainfire but the day is not so long when i will be like him one day so kindly check it out
Click to expand...
Click to collapse
dude relaxy, if you get worked up everytime someone says that there is another way of doing what you are saying you wont get very far cuz honestly there are always multiple ways to stuff... however i do agree with you chainfire clearly said on g+ that the root method is specifically for the s4 leak.. anyway its upto the users they can either use your method or chainfires.. i will try your method once i flash 4.3 :good:

Khizar said:
dude relaxy, if you get worked up everytime someone says that there is another way of doing what you are saying you wont get very far cuz honestly there are always multiple ways to stuff... however i do agree with you chainfire clearly said on g+ that the root method is specifically for the s4 leak.. anyway its upto the users they can either use your method or chainfires.. i will try your method once i flash 4.3 :good:
Click to expand...
Click to collapse
Thank buddy it will be grateful and one more thing u can use the mini SDK tool to flash 4.3 too
Sent from my Galaxy Nexus using xda premium