Develop Bugs

Stuck in bootloop after messing with framework-res.apk

I was in the process of replacing framework-res.apk and missed the step of changing the permissions before replacing it. I found several threads on how to unbrick the phone by flashing a new ROM but I was hoping I can somehow fix the permissions on the framework file and be done. I installed adb and I already had the LG USB drivers installed but when I run adb devices it doesn't list anything. Windows 7 shows "LG AndroidNet Phone" and a removable disk under "Safely Remove Hardware" so I think I have the right drivers.
Is there hope that I can fix the file permissions?
BTW, I'm a newb so I may be missing something. And also scared of having to flash a ROM
I need help.

do you have CWM in the phone ? if so boot into that and run adb devices and see if it finds it their

No, I don't. Other than using DooMLoRD zergrush to root the phone a few months ago, I have not messed with anything else.

gabcon73 said:
No, I don't. Other than using DooMLoRD zergrush to root the phone a few months ago, I have not messed with anything else.
Click to expand...
Click to collapse
unless your phone will boot normaly to the home screen or you have CWM on it you will haveto flash the koren rom theirs no way to get it into recovery that i know of ... have you tryed a factory reset ?

I replied to you at another thread, so I'll repeat here.
What you need to do is re-root while it's looping. It might take you 100 tries before it succeed , but eventually it should succeed.
After that you can try fix the permissions, but if the new .apk file is not copied successfully first time it might get you in boot loop again, so I'd recommend at that point push the .apk again and then change the permissions.
I found that zergrush dated 2011-10-21 has more chances to succeed, because it has more retries before it gives up, the new version tries only few times and gives up too quickly.
I've attached the root I was using with 3 versions of zergrush.
Open CMD window and execute root.bat, let it copy all needed files to the phone. If it fails, try execute loop.bat, it will just execute zergrush indefinitely , so you can go do other stuff. You can check if root succeeded by opening another CMD window and type: adb shell
then, if it shows sign "$" type su, if it shows "#" you are good to go.
P.S.
This method only works with AT$T stock rom, if you are on LU6200 you are probably out of luck, as their root requires wifi and user interaction...
Having CWM is very handy in such situations, not only because you can restore backups, but because you'll have root access.

Thanks [email protected], I'll give it a try. And yes, I have the stock ROM.
I'm having problems downloading root.zip, I've tried two computers and different browsers, it only downloads 554 bytes.

Yeah, for some reason it was downloading 404 page...
I reuploaded it.

I let the loop.bat run overnight without success so I decided to call AT&T and have it replaced under warranty. The new phone arrived today and I've been busy reinstalling and reconfiguring. I may install CWM just so I can easily recover from a backup in case I do some other stupid thing to the phone.
Thanks guys

[Q] Wont flash :(

My phone is currently stuck on the boot screen after i mistakenly removed Apex launcher (when it was messed up on monday) whilst forgetting that i had removed the stock launcher
Annoying as i may be, all my stuffs on memory card or on my google account.... so no real loss. I know i can sort it by flashing, but i just couldn't get it to work. Downloaded the latest generic ftf file & (what appears to be) the latest version of flashtool (0.7.0.0 iirc). But whenever i try flashing, it very quickly tells me that its failed.
I think i know the answer to this, but if possible i would really like to retreive the txts that are on the phone. Is there something i can do before flashing..... or do i have to consider them lost
Any help on either of those questions would be very greatfully received!

Not sure where you got your flashtool from, but obviously not the page in the dev section. Try flashing with the latest flashtool and report back. I take it your boot loader isn't unlocked?

You don't need to flash, if you can get into recovery. There mount usb storage, copy Apex.apk onto it, unmount storage, mount sdcard, mount system, and then move Apex.apk into /system/app.
in cmd/terminal:
Code:
adb shell
su
cd /
cp /sdcard/Apex.apk /system/app
that should do the trick. If you cant access recovery, flash with generic files, look for the flashtool in this forum, there should be some links, and tutorials too.

issak42 said:
You don't need to flash, if you can get into recovery. There mount usb storage, copy Apex.apk onto it, unmount storage, mount sdcard, mount system, and then move Apex.apk into /system/app.
in cmd/terminal:
Code:
adb shell
su
cd /
cp /sdcard/Apex.apk /system/app
that should do the trick. If you cant access recovery, flash with generic files, look for the flashtool in this forum, there should be some links, and tutorials too.
Click to expand...
Click to collapse
If that works it would be great. I have tried to get into recovery mode but with no luck..... however that could be the keypress combo i was using. Have found talk of lots of different ways, not necessarily saying what handset its for.
What is the confirmed keypress combo / method for the arc s?
which flashtool works with the latest generic firmware, as i thought i got this but it wouldn't work

mattshaw4 said:
My phone is currently stuck on the boot screen after i mistakenly removed Apex launcher (when it was messed up on monday) whilst forgetting that i had removed the stock launcher
Annoying as i may be, all my stuffs on memory card or on my google account.... so no real loss. I know i can sort it by flashing, but i just couldn't get it to work. Downloaded the latest generic ftf file & (what appears to be) the latest version of flashtool (0.7.0.0 iirc). But whenever i try flashing, it very quickly tells me that its failed.
I think i know the answer to this, but if possible i would really like to retreive the txts that are on the phone. Is there something i can do before flashing..... or do i have to consider them lost
Any help on either of those questions would be very greatfully received!
Click to expand...
Click to collapse
OK, this worked for me when I did something very similar...
start up the phone, and plug it into the computer.
After a while the light on the phone comes on, and the boot animation keeps looping...
The thing is that adb works now so you can install your launcher through adb!
to do this you type in this command on the windows command prompt
Code:
adb install Trebuchet.apk
some notes: -
you may need to type in the path to your copy of adb.exe if you get a "Command not recognised" error.
I used the launcher from CM10 - Trebuchet in the code snippet. You can extract your launcher's apk file from the rom (look in "system/apk"). Then use your launcher's apk name when you type out the command
Good Luck

An update guys.... spent a couple of hours on this only to find a very simple fix......
Using Flashtool in flashmode (?green light)..... noticed the icon for "install apk".... so found a free launcher apk, hit the button & my phone sprung back into life, text messages & all!!!!

Cannot connect to mobile network???

Hello, this is really weird. In fact, when I insert the SIM to my Note 2 N7100 and turn it on, it allows me to make emergency call, but I cannot use it to make any others and it doesn't show the carrier name (it shows Emergency call only). And when I try to use it to make normal phone calls, it says that I am not registered to a mobile network. I try to factory reset my phone, but the problem remains. I then try to remove the SIM card, and it says that I need to insert a SIM card (that means that it is not a hardware problem since it recognizes the card). I then try to go to the mobile network setting to try to connect to the network manually, it connects me but it shows me a warning which says that the mobile network service is not available (and the Emergency call only label remains). However, I am sure that this is not the problem of the card neither since when I insert the card to my Moto MB860, I can make calls as usual. So, what is the problem ??? It seems to me that the problem happens spontaneously since it works perfectly until yesterday. And all other wireless function works fine including wifi , Bluetooth and GPS and the only thing goes wrong is 3g and 2g.
Additional information:
ROM: Omega v.16
Carrier: Fido Canada (as you can see)
Thanks.

First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...

Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore

jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
I tried a simple way which is format everything and flash another ROM but the problem remains.

TRS_80 said:
Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore
Click to expand...
Click to collapse
I don't know that we are in the same situation since at home I often got a good signal and this happened to me only since yesterday.

jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.

Dan Law 001 said:
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.
Click to expand...
Click to collapse
Results..??
Sent from my GT-I9001 using xda premium

jabrif said:
Results..??
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
I need to get the firmware first... since I already passed the download quota for today... need to wait until tomorrow...

Mmm... I heard that you mentioned clearing the EFS in your given procedure, but I do not think that I modified that folder... However, about few days ago, since I want to gain better control on the volume on my headphone remotes, I did modify the file called Generic.kl in system/usr/keylayout, but I restore it after since it didn't work. However, I don't think that this modification will trigger something in the efs folder since it has different directory. By the way, I did some research online and they say that the efs contains information about the carrier on the phone, so will there's a greater chance that the problem is caused by the possible modification on the efs than any other factor and will there also something else that possibly trigger the similar effects?
Sent from my GT-N7100 using xda premium

Still nothing

[Q] /data/log/dumpstate_ril_RESET_BY_CP_SILENTRESET

I'm tired of this, the only ROM i can use is a stock-based, everytime i try to install an AOSP based rom, in a day (sometimes in a few hours), all my internal memory run out, i can't open any app because it crashes.
It seems it's a problem with /data/log folder...
That's exactly what happens:
I tried all but i don't have a solution. If i give 444 permissions to "log" folder, the permissions will be reseted so i can't do anything but deleting the logs everytime.
I tried too to run a script on boot, to delete anything in the "log" folder then give 444 permissions (to avoid generating more logs), but even if the system doesn't generate logs anymore, it tries, so the phone can't enter in Deep Sleep and the battery draining is huge.
There's no way to disable the logs? I spend my last week investigating but still without a solution and i'm getting crazy, because it seems that i'm the only one with this problem. Everybody is flashing AOSP roms in their Note 2 N7100, and almost nobody has this problem.
My phone is an international N7100 Note2 (Samsung).
There's two posts with exactly my problem...
http://android.stackexchange.com/qu...internal-storage-has-run-out-of-space-message
http://android.stackexchange.com/questions/48279/what-are-these-dumpstate-logs

FINALLY, THE RESULT OF WEEKS OF INVESTIGATION!
The "dumpstate_ril_RESET_BY_CP_SILENTRESET" log files on /data/log are created when your EFS partition is modified by a "new" firmware. It's recomended to backup your EFS before flashing a new firmware, because if your EFS is modified, the older modems won't recognize the partition and you will get a corrupted IMEI (or, in AOSP, no IMEI). I didn't care because for now i'm not using my N7100 as a phone.
The modem controls the "connectivity" field, (that means it controls the RIL, Radio Layer Interface). I guess the RIL couldn't recognize the baseband, and then was crashing everytime, generating this annoying logs every few seconds.
The solution, at least for me, was flashing any N7100 new firmware, flash PhilZ Recovery, restore my EFS (sadly, the modified one) backup, and then flashing the N7100XXDME4 modem.
Then i installed an AOSP rom and... NO MORE LOGS! FINALLY!
I post this because i was getting mad searching a solution and, if there's someone who has the same problem, here's the solution.

Help! android.systemui not working after flashing FML Omnirom

I just flashed FML OMNIROM ([ROM][4.4.4/KTU84P][OMNIROM][LINARO/OPTIMIZED] FML: Fork My Life (10/15/2014)) on my Verizon Galaxy Nexus. I followed instructions on the rom page, including the recommended pa gapps. I was sure to clear /system, /cache, and /delvik. After rebooting, I got to the initial setup, but part way through, the notifications bar closed and I got repeated messages of "Unfortunatly com.android.systemui has stopped". Rebooting the device did not help. Now I also get errors of android search has stopped. As soon as one notification is closed, another one opens. I did make a nandroid, but was wondering if there was something I did wrong, and if I would be able to get OMNI, since my previous Shiny Rom was extremely sluggish.
Edit:
I wanted to add that my SuperSU is a version or two old, in case that may be part of the problem.
Edit 2:
For now I am going to restore old nandroid.

glorygeek said:
I just flashed FML OMNIROM ([ROM][4.4.4/KTU84P][OMNIROM][LINARO/OPTIMIZED] FML: Fork My Life (10/15/2014)) on my Verizon Galaxy Nexus. I followed instructions on the rom page, including the recommended pa gapps. I was sure to clear /system, /cache, and /delvik. After rebooting, I got to the initial setup, but part way through, the notifications bar closed and I got repeated messages of "Unfortunatly com.android.systemui has stopped". Rebooting the device did not help. Now I also get errors of android search has stopped. As soon as one notification is closed, another one opens. I did make a nandroid, but was wondering if there was something I did wrong, and if I would be able to get OMNI, since my previous Shiny Rom was extremely sluggish.
Edit:
I wanted to add that my SuperSU is a version or two old, in case that may be part of the problem.
Edit 2:
For now I am going to restore old nandroid.
Click to expand...
Click to collapse
You can fix this in recovery. Use the file manager built into TWRP (or aroma's flash zip) to navigate to these directories: /data/data/com.android.systemui, /data/data/com.android.contacts, /data/data/com.android.providers.contacts. Delete the contents except for the "lib" link in each directory. That should fix your problem.

I tried that...
7175 said:
You can fix this in recovery. Use the file manager built into TWRP (or aroma's flash zip) to navigate to these directories: /data/data/com.android.systemui, /data/data/com.android.contacts, /data/data/com.android.providers.contacts. Delete the contents except for the "lib" link in each directory. That should fix your problem.
Click to expand...
Click to collapse
So I got AMORA's on a usb drive, which I plugged into my phone with OTG, was able to get into the FS, but anytime I tried to delete something it got stuck on "please wait". Any ideas?