Greetings-
I used the Cyanogenmod procedures to compile an image for my Note 3. The first time I installed it, the imaged booted up but I got a message about nfcservice not working. I do not recall the exact words, but it implied that nfcservice has an issue. I then, went into recovery and recovered an earlier image. The initial recovery try did not go well, and it was stuck. The last message was about the modem. But my next try worked. I had to use a backup I had from my stock firmware. Then I tried to install my unofficial image again. This time the phone went into download mode after I flashed my image. This keeps repeating, and I don’t know where to begin to troubleshoot this issue. Are there any logs I can look through? Aside from factory reset, I tried to clear all the other data; everything except the internal memory which holds my backups. But this did not fix anything. Do you have any advice for me? Oh, btw, this image is patched with seek-for-android patches. And I went through a lot to get it to work, since they did not support version 11. Thanks in advance.
RE
In my experience trying to troubleshoot something like this can be way more time consuming then un-rooting doing a factory reset back to stock OEM rom and then re-rooting and flashing the image again.
Related
Hey all.
So just a few hours ago, I was running rooted stock, as per the guide in the development section. I then installed twrp, and attempted to flash a ROM, which resulted in my phone not booting.
Since then, I got into recovery, attempted a factory reset (which didn't work), and ended up using Odin to restore to stock.
So now I'm sitting on the stock image, unsure if I have root. Everything seems to work fine, but is slow. Also, I cannot enable wifi (the switch goes on for a split second, then back to off).
Is there a way I can uninstall twrp, and go back to complete and total stock?
If it's relevant, I get a constant "This device has detected an application attempting unpermitted actions..." error.
Thanks guys!!!
UPDATE: It still has root access.
UPDATE 2: I'm finding some similar issues people were having with the T-Mobile version (http://androidforums.com/t-mobile-g...connect-wifi-prevention-information-help.html) though I'm not sure whether I can follow those solutions. I will wait until someone can advise me on this.
It sounds like you didn't installed the complete stock image, that the stocked rooted image is installed. Have you done factory reset?
wolfgrrl said:
It sounds like you didn't installed the complete stock image, that the stocked rooted image is installed. Have you done factory reset?
Click to expand...
Click to collapse
I tried the factory reset option from within twrp recovery, which doesn't fix any of these issues I'm having with constant security alerts or Wifi.
Got it fixed by doing this:
http://forum.xda-developers.com/showthread.php?t=2301259
So last night I was using my phone when it froze, so I rebooted it and it got stuck on the boot animation. I tried restarting it and no luck. I then decided to go into recovery mode, and I backed up my data before wiping it to see if that was the problem. I then flashed some roms. One was the Ajk kernel, and another was gapps. Still no luck. I then began to search for a system rom to flash so I could at least boot it. I tried a few I had downloaded before, but I always received a getprop error (status 7) . Then I tried flashing an old version of JellyBam and for some reason, recovery mode didn't show any code or signs of progress nor failure, so I rebooted it and tried going back to my backup I made earlier, and it told me I had no backup data. I then went to browse for a zip to flash,and found that that JellyBam rom had completely wiped both my sd card and internal memory completely. So long story short, I lost all of my data. Also when I try to boot up normally, I'm not able to type anything because AOSP keyboard is not responding, so I cannot work on anything with my google account. I might just go back to stock and go into AT&T to see if they can do anything about it, because I needed to get it replaced anyway for some cosmetic damage. Is there anything I can do about this? Can I get my data back?
Jackson8r said:
So last night I was using my phone when it froze, so I rebooted it and it got stuck on the boot animation. I tried restarting it and no luck. I then decided to go into recovery mode, and I backed up my data before wiping it to see if that was the problem. I then flashed some roms. One was the Ajk kernel, and another was gapps. Still no luck. I then began to search for a system rom to flash so I could at least boot it. I tried a few I had downloaded before, but I always received a getprop error (status 7) . Then I tried flashing an old version of JellyBam and for some reason, recovery mode didn't show any code or signs of progress nor failure, so I rebooted it and tried going back to my backup I made earlier, and it told me I had no backup data. I then went to browse for a zip to flash,and found that that JellyBam rom had completely wiped both my sd card and internal memory completely. So long story short, I lost all of my data. Also when I try to boot up normally, I'm not able to type anything because AOSP keyboard is not responding, so I cannot work on anything with my google account. I might just go back to stock and go into AT&T to see if they can do anything about it, because I needed to get it replaced anyway for some cosmetic damage. Is there anything I can do about this? Can I get my data back?
Click to expand...
Click to collapse
Practically everything in your post screams of confusion: AJK is a kernel, not a rom, and gapps are system app packages for AOSP-based ROM's, not ROM's themselves.
Stay away from Jellybam because they have been banned from XDA and are NOT supported by anyone here.
Because you've somehow jacked up your system, your best bet is probably to ODIN back to stock and start all over again. You could grab a ROM from Development and factory reset/wipe caches in a proper recovery (ie. one of the kernels packaged with an i777 ROM) and be fine, but in your case I would suggest the ODIN method to avoid any holdovers, and start again with a guaranteed clean system.
Buddy, I wish you a lot of luck.
Based on what you said, you've screwed it up pretty bad. I don't know how to recover your data but first, care to bring up your phone.
You should start from SCRATCH and before that, do some research of which ROM you want to use and which gapps should go along with it. Ignore the kernel for now.
---------- Post added at 02:34 PM ---------- Previous post was at 02:33 PM ----------
Buddy, I wish you a lot of luck.
Based on what you said, you've screwed it up pretty bad. I don't know how to recover your data but first, care to bring up your phone.
You should start from SCRATCH and before that, do some research of which ROM you want to use and which gapps should go along with it. Ignore the kernel for now.
since you have already used recovery software and failed to get back your lost data. As per my knowledge I suggest one utility named as Remo Recover because I have already used this utility. Hope it will be helpful for you to recover your data. Just go for this utility.
Galaxy S II GT-i9100 was running on OXYGEN for a while (don't even remember the exact version). Now stuck at boot screen (green "flickering OXYGEN" screen, for those who are familiar with this ROM) after a routine battery change. Can boot into recovery fine, but recent backup was done long time ago... so looking for a solution with minimum data loss. Did anybody run into anything like this before?
I'm not sure if the problem is phone or ROM specific, but posting it here first anyway. Could be a general Android problem/solution, I guess...
Would appreciate any advice or references! Can help?
stuck at boot screen, OXYGEN, worked before, broke after a while, GT-i9100
The only things you can try other than a factory reset are:-
*A dirty flash of the rom you're running (unlikely to work, but try it anyway)
*Flash a stock rom with Odin. No, this will not wipe your phone/cause data loss. This has a fair chance of working but you still might end up with bootloop after & need to do a factory reset regardless. In that case, you're losing data; no way around it.
... more details
Thanks for the quick and constructive advice, but after tinkering with it a bit more tonight, it's clear that the problem is with the "data", and not with the "system" or "boot" itself. I can get the phone to boot by recovering only the "'data" part of the previous backup, using the advanced recovery option in the CWM recovery. Also I can back up the "frozen" latest configuration and then restore it to reproduce the problem.
Any additional suggestions/ideas based on this? Could it be, for example, that SMS app or any other app crossed some kind of limit storing its data and cannot initialize anymore? Is there a way to "'repair" the data.tar file from the CWM backup?
Additional details:
CWM-based recovery v5.5.0.4
Android v4.0.4
Oxygen v3-20120501-SNAPSHOT-SGS2
kERNEL V3.0.30...
Been searching around and imagine the answer is out there but hopefully I can be pointed right direction.
ISSUE:
When i attempt a recovery I perform a factory reset when I reboot nothing has changed. Manually wiped everything except internal an ext-sd. No difference. Also have try to restore back-up same, no change boots to current ROM. And tried to install different ROM no change.
Backstore:
I was in TWRP 2.3, I was on a stock ROM and grabbed JB one (PacMan). Perform install and came up fine but started doing odd thing. Buttons started becoming unresponsive, couldn't pull keyboard up for SMS, could not access setting menu in several apps. So i went to restore and that is when I did some research and they seemed to indicate you needed to be using 2.6 or higher when going to 4.3 or higher ROM. Something about changing up the partitions (not really sure about that).
What I have tried:
Upgraded to TWRP 2.7 Same issue
Downgraded to TWPR 2.6.3 Same issue
Something I notice I when performing any function in TWRP I see the "Simulating Actions" not sure what that means. Also attempting fixing permission and that lock up the phone. Searching around for log but don't seem to have any.
Any guidance would be greatly appreciate.
.
Hello,
I tried flashing a custom ROM on my samsung galaxy S7 (by the way I've already done this successfully, although I clearly don't know as much as I should).
Firstly I was getting the Error 7 and "your device is ." I did fix that by deleting lines in the updater-script of the ROM. It seems that this has worked, but I couldn't get out of twrp to test it. At first I thought it was an error with my ROM, so I just tried loading the backup I'd made before, but I still couldn't get out of twrp. And there I am, I can't go in download mode, or even power off, it just puts me back in twrp.
I tried updating twrp from a .img but it just didn't work and I'm still in 3.3.1-0. Very strange.
I don't know much of the science behind this, please explain me, I don't want to brick my phone...
Thanks to anyone who tries to help.
Nevermind ?, I just did an adb reboot, got out of recovery, and my backup was applied so... I guess I won't install that custom ROM. I don't know why I had this problem, but I solved it anyway.