Need Help asap. Maybe I need to re format - Verizon Samsung Galaxy Note II

Hello,
I posted this same question over at androidforums.com.
I rooted my phone and installed the rooted stock 4.3 from Beanstown " [Rom][I605VRUEMJ9][4.3] Stock Root Odex/Deodex [12/08/13]★ - xda-developers "
I installed the deodexed version.
I then followed the rest of the directions to fix the wifi, and also loaded the framework to gain wifi tether.
The phone was working fine for a few days.
Then I got the system UID error after the battery drained all the way over night.
I could no longer run / install certain apps and I would get random reboots. I tried deleting those apps from data/data. this did help with most of the apps but not all. Regardless the UID error would not go away.
SO I wiped the data . Factory reset. I wiped 3 or more times. Loaded the rom back. This time I didn't load the framework or the wifi fix. I believe those were still in effect because the wifi still worked and the wireless thether still worked.
Now a whole bunch of apps still would not install. Very frustrating. A few days later I got the system UID error again,
SO this morning I wiped the phone like 8 times. loaded the rom again. I still cant install certain apps.
I am so fed up with this phone right now. I used to love this phone before 4.3 . Now this phone is wasting my time. Im way too busy to be working on my phone every few days. This phone is supposed to assist me with work, not cause more work for me.
Can someone please please advise me what to do?
I think I need to re format. But I have no idea how to do that.

by the way I have CWM recovery.
I went into clock work and formatted my internal sd card. in CWM its called the external for some reason. there were a few options that I wasnt sure about. I chose ext to be 4096, swap to be 256 and the last was the file structure. I choose 3 .
Im still having the same issues.
I just want my phone working again

Im going to use Odin to to the PIT and flash the stock vram3. Then Re root... Maybe I should just stick with 4.1.2 .

OK so that worked!
I returned to stock.
THen re rooted with Casual. Im going to stay here and avoid 4.3. 4.3 is a terrible terrible experience. Ill miss some of the added features like "blocking mode" but Ill live without.

The mistake was that joke 4.3 beanstown rom. Can I reccomend http://forum.xda-developers.com/showthread.php?t=2603295
Mean bean is by far the best i605 rom in my eyes. I loved mikeys 4.1 build and the new 4.3 mean bean is incredible.
Sent from my SCH-I605 using Tapatalk

I had similar issues with CM11 latest nightly until I wiped all partitions with latest TWRP recovery then copied CM11 (Android 4.4.2) and gapps over via adb push. So, I think the key is wiping all partitions including data, cache, dalvik, system, internal sdcard and external sdcard.

Related

TNTLite 4.4 issues

Hi everyone,
First time poster but have been reading and browsing for a couple month now and have been able to find fixes for all the issues on my own. I have however had this one issue from the beginning and have not found any fixes or even the issue being mentioned (been using TnTLite the entire time, going up the versions from early 3's to now 4.4).
When my Gtab goes to sleep or even sits idle for a while my WiFi just stops working. The connection is still there and Gtab thinks it's connected but I can't access the net until I turn Wifi off and on and then it works until I let it sit or the screen shuts off. This is annoying at the least and I would love to fix it, even if I have to go to a different ROM (but I do like TnTLite above others).
Does anyone find version 4.4 more laggy than 4.2.5? Gtab is just not as responsive and I seem to have a Flash issue where net videos crash after working for 1-15min.
Also I have CWM 0.8 and when I try to flash with a MicroSD I keep going back into CWM. I changed SDCARD to SDCARD2 in the common file but still my card is not being read. Basically if I want to install the stock ROM and nothing else I can't cause it only boots into CWM and not the SD card. I do have the card formated in FAT32 at 2048. Am I missing something, do I need to uninstall CMW first somehow?
If you re-read the first post in the TnT Lite 4.4 thread, you'll see that you can toggle the CWM back to stock recovery with some built in commands.
Yeah, I saw that as one of the options but I want to be able to patch via the micro SD card and CWM seems to be interfering with that. I mean if I revert to stock with CWM I will still have CWM installed. I want the true original state but more than that I want the MicroSD card recovery to work.
Switching to stock recovery removes CWM and will allow you to use the MicroSD to install. All you have to do is put a file named "command" in the recovery folder on your MicroSD card with the following contents:
--update_package=SDCARD2:/update.zip
When you reboot into recovery it will find that command and execute the update.zip on your MicroSD card.
Thank you!
It was my suspicion that CWM is interfering but I also had recovered from the SD card a couple times even with CWM installed, at least I think so, but it is good to know. I'm also still having issues with net video crashing now and again. The screen goes white and I have to reboot. Started when I installed 4.4 and now that I reverted back to 4.2.5 it is much better but still I had it happen just now and it never did before 4.4. The upgrade to 4.4 also slowed the tablet down which did improve as I went back to 4.2.5.
Try going into CWM and wipe dalvik cache and also do fix permissions, usually cures most of those problems after going from one version to another.
What exactly am I loosing when I wipe delvik cache, do you know? And thanks for the suggestion, haven't tried that yet.
Vigilantys said:
What exactly am I loosing when I wipe delvik cache, do you know? And thanks for the suggestion, haven't tried that yet.
Click to expand...
Click to collapse
Here is a post that explains it
http://forum.xda-developers.com/showpost.php?p=3844295&postcount=5

[Q] flush-179:0 eating CPU (and battery)

Hi,
My EVO 4G LTE is S-OFF. I've been running FreshROM 5.3.1 since it was released without issue. Last Thursday I started getting a lot of backround app crashes. Not a big deal, I wiped, reloaded the ROM, then restored everything via Titanium Backup pro. All was well for a couple of days.
Yesterday, my battery died within about 3 hours. Normally, I go over 16 hours. After some investigation and I found a process 'flush-179:0' eating CPU (and battery). I've wiped, flashed again, even flashed different ROMs. It's still there; every time.
I found one post on XDA where someone said it was caused by a performance tweak app (http://forum.xda-developers.com/showthread.php?t=2016993). Their fix was to flash stock, radios, etc. then root again. I haven't used any apps to tweak anything. So, if it's a similar cause...data/config corruption?
Has anyone else seen this? Does anyone know of a fix?
Thanks!
I'm not familiar with this specific issue but you mentioned that you restored everything using titanium backup. If you are experiencing problems I would strongly recommend NOT restoring all data as you may be restoring that very same issue. If you don't want to have to start all over then at least only restore just apps and data. Never system data.
Sent from my EVO using Tapatalk 2
eddy0090 said:
I'm not familiar with this specific issue but you mentioned that you restored everything using titanium backup. If you are experiencing problems I would strongly recommend NOT restoring all data as you may be restoring that very same issue. If you don't want to have to start all over then at least only restore just apps and data. Never system data.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Of course, the problem is that it's there when I wipe and flash a new ROM (Fresh, Rejuvenated, etc.). Even before I load my data via TB.
zisix said:
Hi,
My EVO 4G LTE is S-OFF. I've been running FreshROM 5.3.1 since it was released without issue. Last Thursday I started getting a lot of backround app crashes. Not a big deal, I wiped, reloaded the ROM, then restored everything via Titanium Backup pro. All was well for a couple of days.
Yesterday, my battery died within about 3 hours. Normally, I go over 16 hours. After some investigation and I found a process 'flush-179:0' eating CPU (and battery). I've wiped, flashed again, even flashed different ROMs. It's still there; every time.
I found one post on XDA where someone said it was caused by a performance tweak app (http://forum.xda-developers.com/showthread.php?t=2016993). Their fix was to flash stock, radios, etc. then root again. I haven't used any apps to tweak anything. So, if it's a similar cause...data/config corruption?
Has anyone else seen this? Does anyone know of a fix?
Thanks!
Click to expand...
Click to collapse
u should try mean rom 6.5 ICS.. if your still on the old base.. or flash new firmwear and radio in bootloader then flash a new jelly bean rom if u want to try the new base out
evo401 said:
u should try mean rom 6.5 ICS.. if your still on the old base.. or flash new firmwear and radio in bootloader then flash a new jelly bean rom if u want to try the new base out
Click to expand...
Click to collapse
I think I will; this seems to fit with the latest info I just figured out.
I flashed Fresh again, and suddenly started getting the warning about the SD card being damaged and to format it (as we know, that's not the external SD card). No matter how many times I format it, the error comes back. From some other searching, the 'flush-179:0' process seems to have something to do with storage, maybe because it can't read that partition it's causing issues.
I updated the firmware and radio, still no luck.
So I tried loading another ROM (I went with Mean Bean). That fixed the issue with the SD Card partition being unreadable/unformatable. Maybe that was caused by multiple flashes
But, the flush-179:0 process is still eating CPU and battery.
zisix said:
I updated the firmware and radio, still no luck.
So I tried loading another ROM (I went with Mean Bean). That fixed the issue with the SD Card partition being unreadable/unformatable. Maybe that was caused by multiple flashes
But, the flush-179:0 process is still eating CPU and battery.
Click to expand...
Click to collapse
?? i never heard of that flush-197:0?? could it be an app u downloaded maybe.. if u flash meanbean over abd dont install any app does is that flush-179 still there or it it there after u install yoir apps?
evo401 said:
?? i never heard of that flush-197:0?? could it be an app u downloaded maybe.. if u flash meanbean over abd dont install any app does is that flush-179 still there or it it there after u install yoir apps?
Click to expand...
Click to collapse
As far as I can tell, it's part of Fresh 5.3.1 and other ROMs I had on my SDCard that are based on the old OTA. The latest Mean Bean doesn't have the same issue after wipe & flash.
I emailed flipz (the Fresh dev), though who knows if/when he'll get back to me. For now, I'm thinking about running MeanBean for a while.
You really can't go wrong with mikeyxda and his mean series of ROM's. That man consistently puts out quality work. No doubt about it.
zisix said:
I flashed Fresh again, and suddenly started getting the warning about the SD card being damaged and to format it (as we know, that's not the external SD card). No matter how many times I format it, the error comes back. From some other searching, the 'flush-179:0' process seems to have something to do with storage, maybe because it can't read that partition it's causing issues.
Click to expand...
Click to collapse
You nailed it. I was having issues with the flush-179 system process taking up 100% of my CM10's (JB) CPU time. It got so bad that I couldn't even reboot or shutdown without pulling the battery, which of course caused other problems. Initially I thought the "System" process was just out in the weeds, but by using OS Monitor and unchecking "Hide System Process", I was able to find the flush-179 culprit.
My first clue that it might be SD card-related was obtained after opening a terminal window and typing 'mount'. The line for /mnt/sdcard showed (paraphrased):
# mount
...
/dev/block/vold/179:65 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,...
...
Realizing that a "flush" process probably had something to do with filesystem caching and seeing the "179" in the mount output, I focused on my SD card. After pulling the card, backing it up, formatting, and restoring it in Windows, I am happy to report that my little Android has been fast, snappy, and problem-free for several days now.
- Dave

DNA "phone storage unavailable" and other woes...

Hi all,
I didn't find any relevant threads through searches, so I'm reduced to asking for help. Please!
My DNA's been running great on Newt's ROM. I'm S-OFF, rooted, using CM, and all's been great. I'm on T-Mo. I installed the most recent patch on the OP page and, now, my phone won't connect to wifi and in settings>storage it shows "unavailable" for storage.
I've wiped cache and dalvik, done a factory reset, and everything I can think of to get things right - but to no avail so far. When connected to my PC, the phone shows up fine and I can see and delete phone files. But, I cannot copy to the phone so I can't put the ROM zip there to start anew. And, since wifi is in a perpetual "turning on" (but never does) I cannot download directly to the phone.
My phone works fine for calls and texts and data, but I can't install apps or get wifi working.
So, gang, any ideas or suggestions?
Thanks much,
Ross
EDIT to add more detail: I just realized that I cannot even access storage through CM recovery. I may be totally hosed, right? I tried to use the install zip and restore functions in CM, but it reports no files found. And if I go to Gallery, for example, on the phone it says "install SD card". I clearly have some serious memory issue (on my phone too...). Help?
You try flashing back to the original ROM before the patch?
fr4nk1yn said:
You try flashing back to the original ROM before the patch?
Click to expand...
Click to collapse
No, I was already running Newt's NOS ROM and I just flashed the patch/update zip for GSM. I didn't do anything else.
rossvtaylor said:
Hi all,
I didn't find any relevant threads through searches, so I'm reduced to asking for help. Please!
My DNA's been running great on Newt's ROM. I'm S-OFF, rooted, using CM, and all's been great. I'm on T-Mo. I installed the most recent patch on the OP page and, now, my phone won't connect to wifi and in settings>storage it shows "unavailable" for storage.
I've wiped cache and dalvik, done a factory reset, and everything I can think of to get things right - but to no avail so far. When connected to my PC, the phone shows up fine and I can see and delete phone files. But, I cannot copy to the phone so I can't put the ROM zip there to start anew. And, since wifi is in a perpetual "turning on" (but never does) I cannot download directly to the phone.
My phone works fine for calls and texts and data, but I can't install apps or get wifi working.
So, gang, any ideas or suggestions?
Thanks much,
Ross
EDIT to add more detail: I just realized that I cannot even access storage through CM recovery. I may be totally hosed, right? I tried to use the install zip and restore functions in CM, but it reports no files found. And if I go to Gallery, for example, on the phone it says "install SD card". I clearly have some serious memory issue (on my phone too...). Help?
Click to expand...
Click to collapse
Ok, what you're probably going to want to try to do is get rid of CWM Recovery - it has proven short sighted in comparison to TWRP. Do the following;
1. Flash TWRP for the DNA (via GooManager or grab the flashable zip and flash via fastboot)
2. Wipe EVERYTHING - Davik, Cache, Data, System.
3. TWRP Main > Advanced > Sideload
4. Use the 'sideload' command via ADB to flash whichever ROM that you'd like to be running.
5. Reboot System (If it tells you no OS installed, click install from the main and install sideload.zip, normally sideloading the ROM will install aswell, but not always.)
With this method, you start with fresh radios, fresh kernels and a fresh storage.
Hopefully this helps get you back where you'd like to be. I had to do this when I switched from NEWT's NOS 4.3 GPE back to NEWT's NOS MY S5 ROM.
Mushroomhead, thanks. I'm up and alive again!
EDIT to add detail, in case someone else encounters this:
I've not ever used sideload before, but I now understand why it exists. I followed the guidance above, with the exception of changing from CWM to TWRP. I may, indeed, do that and give it a try. But I was unable to download any app - or, for that matter, take any photos or access the Play store or do anything which accessed memory. I couldn't even access my backup files. So, I forged ahead with ClockWorkMod Recovery, using sideload to install the original Newt NOS ROM I had. That worked great.
rossvtaylor said:
Mushroomhead, thanks. I'm up and alive again!
EDIT to add detail, in case someone else encounters this:
I've not ever used sideload before, but I now understand why it exists. I followed the guidance above, with the exception of changing from CWM to TWRP. I may, indeed, do that and give it a try. But I was unable to download any app - or, for that matter, take any photos or access the Play store or do anything which accessed memory. I couldn't even access my backup files. So, I forged ahead with ClockWorkMod Recovery, using sideload to install the original Newt NOS ROM I had. That worked great.
Click to expand...
Click to collapse
Glad to hear it! I've been in the modding game since the G1 was released. I know a bit or two about tons of phones. HTC & RUU. Samsung and ODIN. LG and BLEH (don't ever by an LG device). Glad that it worked out for you man, keep on keeping on.

[Q] CWM Wipe cache - huge problem

Alright, I hope I have this in the right place. I just recently flashed the TerraSilent Kernel for the Galaxy Player 4.0 US version. The Flash went fine, but my device was running extremely slowly. A re-flash didn't solve it either. I figured that wiping the cache partition might solve the problem - I decided to do this before running a backup, since no important data is stored in the cache (...right?), and since I was worried that backing up while I had this problem could make things worse - so I went ahead into CWM and did just that. Then, it reboots, and I nearly get a heart attack. The stock wallpaper is back, it's using the default launcher again (I had LauncherPro installed), and pretty much only system apps work, all the others have an icon with an SD card on it, and when clicked on, it says something like "application not installed". I did some searching, and it seemed like a reboot might help (although I didn't find anyone with a problem like mine anywhere). The reboot didn't do anything, so now I have it shut down, so that nothing can happen. The odd thing is, it doesn't seem to me like the system messed up and did a full wipe instead, either, because a couple of things I have are still there - for example, some of my bookmarks I made on the homescreen while still using the default launcher are still there. I'm really confused because I have wiped the cache partition before, when I was still on an unmodified stock kernel, and everything stayed the same, the way I thought it was supposed to. And now this happens. What do I do now? I exported my absolute most important data (Astrid Tasks and Calendar) before I installed TerraSilent (but I obviously wasn't able to do a full backup because I wasn't rooted, I figured installing TerraSilent would root it), so my absolute most important data is on my computer. I also did a simple file backup of the internal USB storage and external SD card to another computer before flashing TerraSilent. However, there is still a good deal of data still need, and a lot of data that would just be a pain in the rear to recreate, not to mention my (valuable to me) game data. What did I do wrong - or did something in the system mess up? And - what do I do to get back to where I was before?
It happened to me when I was on gingerbread with terrasilent. It's a known issue with this kernel. In fact, you didn't wipe the data, but the recovery contain a bug wich format the data as soon as you do an operation wich mount the data partition(I think it's this but I can't remind) but it doesn't wipe the system or anythin else, so the icon, setting and everything else stay there but without anything attach to them. I don't remind what was causing it, I only stopped using cwm with this kernel unless I wanted to flash something or to wipe everything. Sorry but I can't help you more as I don't remind everything, it's been a while since I've been on gingerbread.
ti-pich said:
It happened to me when I was on gingerbread with terrasilent. It's a known issue with this kernel. In fact, you didn't wipe the data, but the recovery contain a bug wich format the data as soon as you do an operation wich mount the data partition(I think it's this but I can't remind) but it doesn't wipe the system or anythin else, so the icon, setting and everything else stay there but without anything attach to them. I don't remind what was causing it, I only stopped using cwm with this kernel unless I wanted to flash something or to wipe everything. Sorry but I can't help you more as I don't remind everything, it's been a while since I've been on gingerbread.
Click to expand...
Click to collapse
Wasn't that problem solved with a later version of the kernel though?
And, assuming that's what happened (what you describe sounds pretty much like what happened to me), would that mean that the only way to try and get it back would be by trying to recover the formatted data?
trainman261 said:
Wasn't that problem solved with a later version of the kernel though?
And, assuming that's what happened (what you describe sounds pretty much like what happened to me), would that mean that the only way to try and get it back would be by trying to recover the formatted data?
Click to expand...
Click to collapse
It was said to be resolved, but it happened to some peoples even thought. Maybe you can recover some of your data with your computer and some tools that let you get the erased data, but I can't guarantee the integrity of your data and you would need to replace every bit of data that was there before to get it running nicely. The easiest way would be to try to recover some of your important data, put it on your computer then wipe your player and start from scratch (wipe data/factory reset) and reinstall your apps. Then put back the save, or setting or files that you got back in your apps. Hope this help, I'm not a proffessional with data recovering or where to put it back after you got it, maybe someone else could further help you with this.
And the conclusion...
ti-pich said:
It was said to be resolved, but it happened to some peoples even thought. Maybe you can recover some of your data with your computer and some tools that let you get the erased data, but I can't guarantee the integrity of your data and you would need to replace every bit of data that was there before to get it running nicely. The easiest way would be to try to recover some of your important data, put it on your computer then wipe your player and start from scratch (wipe data/factory reset) and reinstall your apps. Then put back the save, or setting or files that you got back in your apps. Hope this help, I'm not a proffessional with data recovering or where to put it back after you got it, maybe someone else could further help you with this.
Click to expand...
Click to collapse
OK, my reply is late, but thanks for your help. I managed to copy the partition with all the deleted contents over to the computer, and I'll have to study the contents some other time, because I've spent about 24+ hours on this problem in total, and need my device for more important purposes - those for which the data I managed to copy before the custom kernel and everything else. For those of you who have a similar issue, this is how I managed to save (or that is I am 95% sure this will have saved at least some, as I said I haven't studied it yet) what I hope is a good chunk of my data.
Have you tried flashing a different kernel? Terrasilent also gave me some weird in that after a few days my device would boot into recovery by itself then wipe all my data in that only my system apps would remain. So it's a little different than what's happened to you. I ended up using klin's R3 kernel or Steven's kernel that fixed the issue.
Sent from my YP-G1 using xda app-developers app
obscuresword said:
Have you tried flashing a different kernel? Terrasilent also gave me some weird in that after a few days my device would boot into recovery by itself then wipe all my data in that only my system apps would remain. So it's a little different than what's happened to you. I ended up using klin's R3 kernel or Steven's kernel that fixed the issue.
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
I've got huge issue with steve's kernel. You can get into recovery, but once you booted in it will simply bootloop. Then you have to flash back with odin. So if you go with steve's kernel, don't boot into recovery. As for klin's kernel, I've never tried it, and will probably never as we have some really nice jellybean rom that I recommend you.
I never got that issue with steve's kernel.
Sent from my YP-G1 using xda app-developers app
obscuresword said:
Have you tried flashing a different kernel? Terrasilent also gave me some weird in that after a few days my device would boot into recovery by itself then wipe all my data in that only my system apps would remain. So it's a little different than what's happened to you. I ended up using klin's R3 kernel or Steven's kernel that fixed the issue.
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
Actually, with my problem, my system apps did remain, so it's almost the same problem, only my device didn't boot into recovery on its own (seriously, it booted into recovery on its own and wiped the data? ). I only installed the terrasilent kernel to be able to upgrade to JB, so I'm now on JB, running into different problem (the wrong settings are being backed up from google backup, they're restoring from my galaxy mini 2), but thanks anyway. I am really not having any luck at all with this whole update . But ti-pich, I agree with you, that JB rom is awesome
trainman261 said:
Actually, with my problem, my system apps did remain, so it's almost the same problem, only my device didn't boot into recovery on its own (seriously, it booted into recovery on its own and wiped the data? ). I only installed the terrasilent kernel to be able to upgrade to JB, so I'm now on JB, running into different problem (the wrong settings are being backed up from google backup, they're restoring from my galaxy mini 2), but thanks anyway. I am really not having any luck at all with this whole update . But ti-pich, I agree with you, that JB rom is awesome
Click to expand...
Click to collapse
Yes it did, after 1 week. I was like ???. I reflashed it again and it did the same exact thing, and it happened to me while I was at my college too.
I also had that same issue where it was restoring from the wrong device. I just had to reflash the rom, and install stuff manually because it was making my device horribly slow.
obscuresword said:
Yes it did, after 1 week. I was like ???. I reflashed it again and it did the same exact thing, and it happened to me while I was at my college too.
I also had that same issue where it was restoring from the wrong device. I just had to reflash the rom, and install stuff manually because it was making my device horribly slow.
Click to expand...
Click to collapse
Wow that is some scary stuff, now I know why every kernel/ROM/mod has a disclaimer at the beginning ... I'm glad I'm off that now and on a stable JB build now. I found a way to have it restore at least some of the stuff from when it was on gingerbread (mostly apps and appdata, no WiFi passwords or other settings - at least I'm pretty sure, I'm still working on getting all the stuff up and running) - go into a terminal, and type
Code:
bmgr list sets
It will probably have two different sets, one for when it was on GB and one for JB - or that is, if you had the problem, there will probably be a third set for a different device (maybe more). Then, choose the one you want to restore from, and type
Code:
bmgr restore xxxxxxxxxxxxxxxx
and replace xxxxxxxxxxxxxxxx with the apropriate ID from the command before. I'm having to type it several times in order to get it to work - I type it once, it restores some apps, then stops, I type it again, and it restores some more - but I'm hoping it gets as much possible onto the JB build. I guess this won't help you much, I've seen you saying on the ICS and JB threads that you've upgraded a while ago, but I guess if someone else comes along with the same problem, I hope it will help
trainman261 said:
Wow that is some scary stuff, now I know why every kernel/ROM/mod has a disclaimer at the beginning ... I'm glad I'm off that now and on a stable JB build now. I found a way to have it restore at least some of the stuff from when it was on gingerbread (mostly apps and appdata, no WiFi passwords or other settings - at least I'm pretty sure, I'm still working on getting all the stuff up and running) - go into a terminal, and type
Code:
bmgr list sets
It will probably have two different sets, one for when it was on GB and one for JB - or that is, if you had the problem, there will probably be a third set for a different device (maybe more). Then, choose the one you want to restore from, and type
Code:
bmgr restore xxxxxxxxxxxxxxxx
and replace xxxxxxxxxxxxxxxx with the apropriate ID from the command before. I'm having to type it several times in order to get it to work - I type it once, it restores some apps, then stops, I type it again, and it restores some more - but I'm hoping it gets as much possible onto the JB build. I guess this won't help you much, I've seen you saying on the ICS and JB threads that you've upgraded a while ago, but I guess if someone else comes along with the same problem, I hope it will help
Click to expand...
Click to collapse
hmmm. I'm about to try Terrasilent with my YP-G1 (US version) running 2.3.6. This is giving me second thoughts. Does this kernel still cause issues with SGP 4.0s running GB 2.3.6?? Maybe I should try the old Steves Kernel? I just want to use voodoo sound - thats really the only reason I want to root and get these kernels.

Phone is bootlooping after attempted ROM update

I was running AOKP 4.3 and downloaded the latest 10/30 update. I flashed in CWM recovery and everything took as normal. I wiped cache and dalvik and then rebooted. Apps updated as normal and lockscreen presented. I unlocked and immediately received two force closes (timely & swype) if I click them or not, if I unlock or not, the phone will crash and reboot every 6 or so seconds. Luckily, if I'm quick, I can reboot into recovery. I am in CWM but my external SD card won't mount so I can't load anything onto it and attempt a new flash and the only rom file on my internal SD is the one that got me in trouble here. I've gone back into recovery and attempted to wipe data/factory reset/etc. and nothing changes. Internal storage won't mount when I'm connected to my computer with a cable.
I don't mind losing everything and starting from scratch. I've tried to seek out my own info but there is SOO many threads and videos and I don't know where to start. Can someone please tell me the most efficient way to get back to a clean start? I was on JellyBeans from 1-22 and looking back that was probably more my speed. I shouldn't have tried to switch to 4.3 at all. I was able to run AOKP for about two months without issue but I seem to be out of my element here.
Can anyone smarter than me please take pity on me here? Sorry to waste your time as well.
Try just wiping the system, reflash rom and gapps. I think this keeps your apps in tact, if just not just use tb and restore. Otherwise full wipe sounds necessary, but not horrible. Just restore everything with tb

Categories

Resources