Hey guys, so I am on samfail v2.5, TWIZtd rom 2.2, with the AQK5 build(U2 BL) and ever since I did a backup&restore with safestrap I've been getting kernel panics randomly at times and 100pct anytime I attempt to flash ANYTHING - either from flashfire or safestrap TWRP. I've already flashed the stock kernel in Odin which seemed to have worked initially (was going into panic within 2-3min everytime I booted up prior to stock kernel flash) not as random as before but still making it near impossible to use my phone as normal.
I've posted in the thread for safestrap, got the advice to reflash stock kernel and while it's helped, hasn't fixed the issue completely. Only thing I can think of is to wipe phone(don't want to if I don't need to) and re root, etc, etc. Here is a log from one of the kernel panics. Main msg it gave was "kernel stack is corrupted in ffff". Any help is greatly appreciated as I need to have device functioning normally.
https://drive.google.com/file/d/1edA_sYJ5wIXfQ7Ot8tSs7msU3Gz-iRXp/view?usp=drivesdk
EDIT - 2 DAYS LATER, PERFORMED A FULL WIPE AND HAVE FULL FLASHING ABILITIES BACK WITHOUT KERNEL PANIC =) ALTHOUGH I DID NOT REINSTALL SAFESTRAP.
Related
I have two phones (one is wife's and that one is the problem - oh boy..) - they are the gt-i9000 and had firmware's XXJP2 (a July or August build 2010) and they worked badly. So I wanted to try MIUI and flashed my phone according to instructions and when doing the flash of the speedmod kernel I couldn't boot. The phone just gets to the first screen (the Samsung GT-i9000 words) and vibrates repeatedly: one vibration then a quick 3, repeat. I eventually got that phone to JVH and am pretty happy with it.
Then tried to do same on wife's. Couldn't use 3 button recovery so used ADB to get it in download mode (mistake - I know - I've learned alot since in my research to fix the resulting brick). Eventually got it into download mode again and tried installing MIUI using instructions: flashed the speedmod kernel and got the same vibrations on boot as my phone. So flashed the JVH and now it boot loops. Goes through the boot animation and noise over and over.
Before I bricked the phone I installed the galaxy_efs tar to try to back that up but it didn't get a chance since I bricked it on the speedmod flash (just got the phone-!-computer icons). Got past that. I also, before starting all this, used Titanium Backup to backup all user apps and data (think I didn't do system apps - maybe another error). I think it may have gone to Dropbox (haven't checked - it is her account).
So question: looks like I am supposed to reflash a Froyo 3 file plus .pit file to come out of this. I've downloaded both the JP2 firmware as well as a newer JPY which I thought I would try first. But before repartitioning and all that I'm hoping there is something I can try to get out of the bootloop without the 3 file flash. Hope to try to make sure there's still her data on there, maybe be sure to back up the efs file and stuff. Possible to just try clearing cache from recovery mode or something - has that worked?
Efs file: is that specific to phone or (if I lost hers) can I use the backup from mine since both phones were purchased at same time? I suspect it may be specific to phone but maybe there's a chance not.
Any thoughts on why the speedmod kernel didn't flash correctly on each phone - ending up with a vibrating non-booting phone? I used Odin 1.82. I would like to try MIUI but can't seem to get past that kernel step.
thanks, JD
Apologies if this is answered elsewhere but I've been looking around the forums and a lot of information/posts from people seem to conflict or the information is only valid for X kernel or Y kernel etc and it can still be a little overwhelming even after lots of nice people have posted guides.
I bought a German Note about a month ago and upgraded to 4.0.3 through the devices own update method (I have not flashed any ROMs on this device), leaving me on XX-LPY. I have since rooted the device, and did not perform any kinds of wipes doing this, this was the only time I even used CWM, I havent booted into CWM since (or used any of the normal recovery features).
The device has been working fine for around a week, I've restarted it several times without issue. However today after restarting it gets stuck on the Samsung logo and will not boot properly. The only thing I have used root for is to uninstall Kies and the SNS Push stuff (which seemed to save me a lot of battery life) and install ad-free android. I also installed the Carbon Tweaks app and applied the Carbon Booster stuff along with the Beats Audio and Bravia Engine stuff (nothing else).
I am able to get into recovery mode however I seem to be unable to put it into download mode (Edit: finally got it to do it once, wont do it every time though) so I have a few questions:
Can anyone tell me if its ruined or why its doing this?
Is it safe to just factory reset/wipe cache through normal android recovery (not CWM?).
Is it safe to try to flash another ROM through CWM (I'm on XX-LPY) and if so which one is safe for me to flash?
Is it safe to try to flash through Odin and if so which ROM should I flash?
I really dont care about the data on it or wiping it w/e. I just dont want to turn it into a paperweight if I can help it.
Thanks
Edit: Also if it makes any difference, this is the method I used to root the device:
http://forum.xda-developers.com/showpost.php?p=20963730&postcount=3
Nope, don't go around flashing stuff with CWM on that device.Also, you can't wipe as that may trigger the MMC_CAP_ERASE causing superbrick.Judging by what you say you've done, I'd say I don't know why it happened but it isn't ruined.
You can try to flash a stock GB rom of your country by following dr.ketan's guide in the dev section and then rooting it (if you want).Alternatively,you could just take it to a Samsung service center as there is no yellow triangle.But I'd try to flash the GB rom as flashing a stock kernel via PC Odin doesn't increase the flash counter.
Hi Everyone,
I have a GT-N7000 - it's been working great since I bought it 9 months ago. I was running RocketRom on it for months. I've been using RR 11 (I didn't like 12) and haven't had a problem with it. The CWM that comes with it appears to be 6.0.1.2 and I kept the stock kernel (OneNote??). Lately, my sms messages were being sent sporadically and I kept getting this same SMS pop-up over and over (every time I sent an SMS). I know it's probably a carrier issue but I thought I would boot into recovery and wipe the cache and Dalvik. I've done this several times in the past without problems.
I first wiped the cache, then I did Dalvik. For Dalvik, I got the error E:\ unavailable (I recall seeing this in the past). I select "Reboot" and the phone booted back into CWM. I've tried removing the battery and same thing.
I ended up trying to flash back to the pre-rooted GB using Odin. The flash completes and the phone reboots but, yep you guess it, CWM comes up. It's the same version. So apparently this is not being updated by Odin??? I read somewhere that this is a CW bug that does not clear a flag to boot back into Android but the fix seems overly complex and worries me (I'm not afraid of doing it if it will fix it).
I'm entertaining the idea of using Kies to do a "Firmware Upgrade" which looks like it will install the latest ICS. It successfully downloads the new firmware then asks me to connect the phone. Before I do this, I wanted to check here to see if this is my only (best) option. Or if I should try something else? Also, Kies says system and data will be initialized so will my sms logs, photos, etc be deleted as well? Not a huge issue since I save the photos to the external sd. I just want to know if the USB storage will be wiped too.
[EDIT] I wanted to add that I TRIED to install Abyss from CWM and it hangs. Same ting with installing RR again. It appears that the file system is locked or something. Pretty much nothing works in CWM. I even tried mounting the various partitions then installing Abyss. It just hangs on "installing." I suspect the problem occured when I wiped the cache or Dalvik. I just don't know what
I appreciate any input.
Thanks!
dont use abyss... try other like hydracore or speedmod 3-15
Im a noob and im afraid i may have this also..
Try to download Philz kernel for your built number, and flash the philz zip file from recovery.
or if can't flash from recovery, try to download the ODIN file for philz kernel (TAR file).
It should re-injected the CWM.
Sent from the corner of this rounded earth.
Dear friends,
Little background. I was on CM10 stable, but decided to I update to CM10.1 M1, After the update, had no market, however, so I tried to downgrade to CM10 stable and it bricked. So .. back to stock it is! Now I am having trouble getting out of stock. I am not new to flashing, but I never had this kind of a persistent problem.
The short summary of what I get no matter what I try is: Every kernel that is not the stock Eclair kernel has boot-animation messed up (random lines of color on screen), and I cannot enter recovery - I sometimes can boot sometimes cannot.
Steps I have taken
I went back to stock Eclair rom + non-root kernel (LINK).
I rooted (LINK)
But when I tried to update kernel to allow CWM, it bricked my phone. So back to stock, again!
I tried this a few times. Now, the latest attempt, I tried the stock 2.3.5 rom + rooted, CWM kernel (LINK... I get the phone running, but I cannot get into recovery, and no utility that has "reboot to recovery" has managed to get me into recovery.
The plea
All I want is CWM, so I can install what I want. Without it, I am stuck with Odin one-click and Odin flashable packages (Heimdall does not want to work right for me - the drivers are messed up - and trying to fix those brkeas my Odin drivers).
I have no data on the phone at the moment, I can reinstall everything if need be .. but I am out of ideas besides keep trying different roms and kernels until something gives me CWM and I am free again.
I have AT&T GB bootloaders.
thanks for any help, I will try to provide any additional info I can.
dozyaustin said:
Dear friends,
Little background. I was on CM10 stable, but decided to I update to CM10.1 M1, After the update, had no market, however, so I tried to downgrade to CM10 stable and it bricked. So .. back to stock it is! Now I am having trouble getting out of stock. I am not new to flashing, but I never had this kind of a persistent problem.
The short summary of what I get no matter what I try is: Every kernel that is not the stock Eclair kernel has boot-animation messed up (random lines of color on screen), and I cannot enter recovery - I sometimes can boot sometimes cannot.
Steps I have taken
I went back to stock Eclair rom + non-root kernel (LINK).
I rooted (LINK)
But when I tried to update kernel to allow CWM, it bricked my phone. So back to stock, again!
I tried this a few times. Now, the latest attempt, I tried the stock 2.3.5 rom + rooted, CWM kernel (LINK... I get the phone running, but I cannot get into recovery, and no utility that has "reboot to recovery" has managed to get me into recovery.
The plea
All I want is CWM, so I can install what I want. Without it, I am stuck with Odin one-click and Odin flashable packages (Heimdall does not want to work right for me - the drivers are messed up - and trying to fix those brkeas my Odin drivers).
I have no data on the phone at the moment, I can reinstall everything if need be .. but I am out of ideas besides keep trying different roms and kernels until something gives me CWM and I am free again.
I have AT&T GB bootloaders.
thanks for any help, I will try to provide any additional info I can.
Click to expand...
Click to collapse
Messed up screen = wrong bootloaders. Flash Odin KK4 with bootloaders
From there, follow this link.
Finally, you can get back up on CM10.1 - Btw, you had no market cause you didn't flash their Gapps.
UPDATE .. ugh that took a while:
1) From the master list LINK, wet back to 2.1, I897UCJF6
2) From the same thread installed I897UCKF1 with bootloaders
3) rooted: LINK (I know -not XDA)
4) removed the 3e recovery lock (LINK) - this did not seem to work, but I did do it.
5) installed Speedmod kernel from here LINK - this did not boot, but it did install CWM
6) installed CM10.0 Stable from SD cadr - twice
7) installed gapps
8) just did my first boot to CM10.
This is both a record for myself for later, and for anyone else that may find this useful.
BWolf56 said:
Messed up screen = wrong bootloaders. Flash Odin KK4 with bootloaders
From there, follow this link.
Finally, you can get back up on CM10.1 - Btw, you had no market cause you didn't flash their Gapps.
Click to expand...
Click to collapse
Ooooh. I learn something new every day! Thanks.
Sent from my SGH-I897 using xda app-developers app
Hey!
I've flashed kernel and firmware on my Note successfully several times, but now I encountered a problem:
I'm on Asylum_CM10.1_20130311_n7000 ROM and was using Asylum_CM10.1_20130311_n7000 kernel, all working fine.
Then I flashed a new kernel, HydraCoreNirvana Kernel for Galaxy Note GT-N7000. After this I've been in hell, every time I try to start/boot the phone, it jams on the Asylum startup animation. I tried both from the SD and when the phone wouldn't start, via Odin. Then I tried flashing back to the working kernel above, no help. Now I'm stuck with two non-working kernels and a useless phone. I hope I haven't ruined it already...
I was flashing with the instructions @ rootgalaxynote. com
Any help would be greatly appreciated!
-Larson
larson80 said:
Hey!
I've flashed kernel and firmware on my Note successfully several times, but now I encountered a problem:
I'm on Asylum_CM10.1_20130311_n7000 ROM and was using Asylum_CM10.1_20130311_n7000 kernel, all working fine.
Then I flashed a new kernel, HydraCoreNirvana Kernel for Galaxy Note GT-N7000. After this I've been in hell, every time I try to start/boot the phone, it jams on the Asylum startup animation. I tried both from the SD and when the phone wouldn't start, via Odin. Then I tried flashing back to the working kernel above, no help. Now I'm stuck with two non-working kernels and a useless phone. I hope I haven't ruined it already...
I was flashing with the instructions @ rootgalaxynote. com
Any help would be greatly appreciated!
-Larson
Click to expand...
Click to collapse
Please, I'm drunk and freaking out with this phone (I know 1st world problems).
Do a wipe data in recovery (if u can go to) or ODIN. Then try to see if the phone boots, if it doesn't you can do a clean install of Asylum ROM again. If nothing works(!) Go back to flash a stock ROM via ODIN and then use Philz kernel to re-root.
Varad297 said:
Do a wipe data in recovery (if u can go to) or ODIN. Then try to see if the phone boots, if it doesn't you can do a clean install of Asylum ROM again. If nothing works(!) Go back to flash a stock ROM via ODIN and then use Philz kernel to re-root.
Click to expand...
Click to collapse
Tried all that (went straight to stock). No help, I guess somethings gone wrong with the boot sequence, I flashed Philz kernel and now it loops on the samsung animation. Before, it sometimes showed "Android is upgrading 1/83 (or something similar), the number would go up a while, then the start-up animation again and all over again from 1/83. It always seems to jam on the ****ing animation... Gonna jump off the roof.
larson80 said:
Tried all that (went straight to stock). No help, I guess somethings gone wrong with the boot sequence, I flashed Philz kernel and now it loops on the samsung animation. Before, it sometimes showed "Android is upgrading 1/83 (or something similar), the number would go up a while, then the start-up animation again and all over again from 1/83. It always seems to jam on the ****ing animation... Gonna jump off the roof.
Click to expand...
Click to collapse
I got the phone working again. Did a factory reset from recovery and after that the phone started up. After that installed the HydraCoreNirvana Kernel again and now it works just fine. Thanks very much for the help!