Kernel/System Load Issues - General Questions and Answers

Hey guys,
I've used XDA for quite a while now as a resource for rooting and flashing my phones. After some trial and error, I finally got a custom rom and root onto my previous phone, the Samsung Galaxy Light (SGH-T399). However, I booted the T-MOBILE kernel, not MetroPCS, and got locked out. So I bought a Galaxy Core Prime, and after a bit decided to root that as well. But when I did some sort of permission modification and tried to make my extSD writeable, the phone crapped out. It would not load the kernel past the bootloader. I tried flashing everything and anything. It just would not allow it to write or mount properly.
So I went back and tried restoring the T399 until I sorted that out, and the same thing is happening. I even flashed ShabbyPenguins stock rom which never failed me before, to no avail . I was able however to successfully install TWRP again. Someone please help me out, I can't afford another phone at the moment. Im still a novice, but I know enough to know it's more than just a mistake in Odin or a file I didn't upload. I've tried searching for an answer to no avail.
P.S. -I'm 90% sure it's a partition issue of some sort, where the filesystem isn't being communicated with properly.

Related

Stuck on 4.0.4 Verizon

For the last year or so, I was using this rom, and I loved it, but I was curious to try the new KitKat version so I tried updating, and kept getting getting a recursive error when trying to flash the d2lte(supposedly all the S3 roms are unified now?) KitKat version. So after doing this, after /system was cleared, but I couldn't flash back to the backup I had made before hand because I was getting an md5 mismatch.
In response, I used Odin to flash Root66. Phone works, but its seriously lacking in terms of bells and whistles of a custom ROM. It says its rooted, but a lot of root apps would fail the permission test. No prompt was given. I used towelroot and started getting root access, but I still can't update CWM or Superuser binaries. Trying to flash any other ROM leads me to an infinite boot screen, forcing me to flash Root66 again.
I tried this as well, but it seemed to yield the same results.
So, I really would like get off Root66, but I'm at a loss as to how. Anyone have any ideas? I'm sure the answer is staring me in the face in one of those threads I linked, but I'd really appreciate it if someone could (at least try to) point me in the right direction. Apologizing in advance if this question has been asked before.
Thanks.

[Completed] Formatting Samsung S3 Problem

Hey, so basically I'm in a situation where I have no idea what to do.
I recently just got a new phone, and am going to give my Samsung Galaxy S3, SGH-T999V model - from Wind Mobile to my Dad. Basically, when I first got the phone - a couple months after, I decided to try Rooting it, and I did, successfully. Since I didn't really know what to do with my rooted phone, I decided to unroot it - then tried rooting it again some months later, but it didn't work successfully. Basically my phone wasn't rooted, but I had the "Team-Win" recovery on it.
I wanted to bring my phone back to it's original state - and have the stock recovery on it. After some Googling, my solution seemed to be to flash the stock rom for the SGH-T999V model onto my phone using Odin. And I did that - and it worked successfully. But I still couldn't check for OTA updates or anything, it said my phone had still been modified in an unauthorized way.
Now that I need to give the phone to my Dad, I have to format the device and erase everything. This is where my problem starts. When I try to format it (using the Stock recovery), I see a bunch of error messages, with the Android logo falling down in a kind of dead way. I reboot my device, and nothing changes.
It still has all my data, and everything on it.
Sorry if this is the wrong area to post this (I'm relatively new to the forum), and if my problem doesn't make much sense - I've tried being as detailed as possible. Could anyone help?
Hi, thank you for using XDA Assist. Flashing the stock firmware should show you to get ota's. This should have everything you need,http://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125. Also, you can ask further questions here,http://forum.xda-developers.com/galaxy-s3/help/help-thread-galaxy-s3-question-t2690307
Thread closed

[Q] Verizon Galaxy S3- Me Messing up

As the title of this suggests, I messed up BIG TIME when attempting to get Cyanogenmod on my Verizon Galaxy S3.
Long story short, I tried putting CWM on my phone without looking up things about it, like whether or not the bootloader was locked for 4.4.2 Kitkat, which it was, and has been since 4.3 Jellybean, which I did not know at the time I tried screwing with my device (which was around a week ago), and I started trying to mess with the phone without knowing what the hell I was doing, since the last time I tried modding a GS3 was over two years ago.
Long story, well, long, I tried installing CWM via the ROM Manager app, and, upon installing it, I screwed up the recovery mode on the phone. It wasn't a big deal, until I decided I wanted to put the latest version of Cyanogenmod on it, instead of using the stock Touchwiz interface.
Well, a couple days ago, I stuck Safestrap on it, and was able to use that as a recovery mode, since the normal recovery mode was locked off, entirely.
I figured that, tonight, I would look up ways to stick Cyanogenmod on my GS3.
I found a couple ways to do so, downloaded the gapps file I needed, the SU binary update, as well as an unofficial version of Cyanogenmod to let me use 5.1 Lolipop.
Well, I wiped the cache on the phone, as well as the dalvik cache, and factory reset the thing, ad went to the folder I put the gapps, SU binary update, and CM files in, and tried installing them.
Well, the SU update went fine.
gapps won't install.
The CM file I'm using SAYS it's installed, but the phone doesn't have an OS, which is confusing me.
I don't know if the phone is bricked, I just know that I did something stupid, and I don't know how to put an operating system back on the phone, either through Kies or Odin (I can't install anything from the SD card in the phone, because now I can't access it, since when I boot it up, there's no OS, and I need one to access the files on the device).
Whenever I try using Odin to put either a stock firmware version on it, it fails.
My phone, in DL mode, says: "SECURE CHECK FAIL : RECOVERY"
I don't know what this means, but I think it means I'm pretty well screwed.
I need to get rid of CWM and Safestrap via my computer, THEN reinstall the stock recovery mode on my computer, too.
I NEED to know how to do this.
If there is ANYONE out there who can help me out, or direct me to some other thread, that would be amazing, and GREATLY appreciated.

Bricked? This shouldn't be happening.

Here's a basic rundown of what happened. I completely rooted my Galaxy S III i535 on 4.4.2, and i installed SafeStrap (A Version of TWRP) since the Verizon S3 has a locked bootloader.
So here's what I tried to do. Using SafeStrap, I backed up my stock rom. And i selected another ROM slot. Using this, i tried experimenting by installing a ROM for another Carrier (They say not to do this, but i have in the past with success, so i thought it mightve worked)
(KEEP IN MIND, THE STOCK OS WAS STILL INSTALLED AND I EVEN HAD A BACKUP)
So, it didnt work and stopped halfway. I rebooted the phone, and Hard bricked.
Doesnt boot up, does not turn on, will not boot recovery or download, or any sign of some boot at all.
And, i get the qhsusb_dload sign on my pc.
Can anyone point me in the right direction, or at least tell me the cause of this problem? Thanks.
CrimsonKatsuro said:
Here's a basic rundown of what happened. I completely rooted my Galaxy S III i535 on 4.4.2, and i installed SafeStrap (A Version of TWRP) since the Verizon S3 has a locked bootloader.
So here's what I tried to do. Using SafeStrap, I backed up my stock rom. And i selected another ROM slot. Using this, i tried experimenting by installing a ROM for another Carrier (They say not to do this, but i have in the past with success, so i thought it mightve worked)
(KEEP IN MIND, THE STOCK OS WAS STILL INSTALLED AND I EVEN HAD A BACKUP)
So, it didnt work and stopped halfway. I rebooted the phone, and Hard bricked.
Doesnt boot up, does not turn on, will not boot recovery or download, or any sign of some boot at all.
And, i get the qhsusb_dload sign on my pc.
Can anyone point me in the right direction, or at least tell me the cause of this problem? Thanks.
Click to expand...
Click to collapse
The solution may be a debrick image. They are designed to boot the phone from an external sdcard and from there reinstall the stock rom/firmware. I haven't searched yet, but check the general and development threads, possibly the stickied summary thread.
Check this thread

Wiped phone, Trying to get a Firmware on it, Failing miserably.

Yo, I've been trying to fix the damned phone for ages now. I accidentally wiped it by being a dumb idiot. Now I'm trying to fix the situtaton. So, I've tried installing a stock firmware and just flashing it with Odin. After trying this with like three different Firmwares, and sequential failures, I moved on to trying to flash it with a custom rom using adb, as the s6 doesn't have a removable sd. So I tried this, It said it worked. I used an installer and everything. But after I reboot, it still says there's no os and I cant find the zip anywhere on my phone to install. I'm not sure what to do. I'm a noob with this hence why my phone is in this state. Help MUCH obliged, S6 edge Sprint
http://forum.xda-developers.com/showthread.php?t=3219484

Categories

Resources