[Q] SGS Rooting Problems - Galaxy S I9000 General

I'm having problems trying to root my SGS, i get to the stage of having the update.zip file installing in recovery mode – but it just looks like it is installing for a couple of seconds then stops and boots into the phone normally – resulting in phone still not being rooted.. I have tried many times all with the same result.
I am running 2.1 and am trying to apply the lag fix, any suggestions???

If the update.zip method doesnt work then try the PC method.
P.S : Do it at your own risk, I am mealy suggesting an alternative.

Related

Need serious help: Bricked Phone (G900A)

Hey guys,
Was a little schwasted last night and decided to play around with my phone. I was trying to root it and install a custom ROM, but I just ended up bricking the damn thing instead.
Needless to say, I will not be trying to root this thing anymore but please help me fix it by tonight.
I've been up all night trying to fix it, and I've done pretty much everything possible and it's starting to get very frustrating. I've downloaded the stock ROM .zip file and loaded it into Odin, where it installs successfully. Then I boot it into recovery mode, do a factory reset, wipe the cache, and reboot. No difference - the Custom Bootloader still shows up and then it displays a few seconds of the Samsung animation before freezing and eventually turning black (blue light on top left is still on though).
Please help.
Just did the same thing three more times. Send the .zip file through adb sideload. Nothing.
............
You shouldn't be using a zip with Odin, it should be a tar file.

What changed? Why could I root before, but not now?

I've spent a full day on this and no further ahead.
This is my wife's phone. A few months back (after Lollipop update) she was running into problems that I needed root to solve. I was lazy and tried Kingo Root and it worked on the first shot. Golden.
No problem but I screwed something up by being overzealous with deleting system apps and her cell data stopped working.
No biggie, I unrooted and did a factory reset and all seemed fine. But now I go to root it and... can't. Kingo Root fails.
Why?
But beyond that, I've followed every other tutorial on various other methods and every attempt ends in failure (stalls at startup screen, pre-animation. I've waited >1hr). I've had to reflash stock ROM several times.
In the stock bootloader under Check Root it says the bootloader is locked.
I've put on TWRP no problem, but that's what seems to stall the boot. I've read that TWRP is problematic with this phone and to use CWR (?) instead, but every link is dead, every tutorial regarding it is sketchy.
Advice?

S5 reboot issues

Hello, i will try to be as elaborate as I can cause I know you guys here are really knowledgeable when it comes to smartphones. So, here are the issues I am currently experiencing with my G900F phone. Just a background, everything in my phone is stock (rom, recovery, kernel) no changes done yet. It currently runs MM with a security patch of February 2017. As of now, I can't boot into the phone.
1. . I was able to successfully root it with CF auto root.
2. I started experiencing random restarts. I tried obtaining the last kmsg however it does not exist.
3. I tried flashing a new ROM thinking maybe there is some rare bug in the stock rom i currently have. I flashed TWRP via Odin, to be able to flash a new ROM. Odin successfully flashed the recovery however when i proceed to install a new ROM through TWRP the phone gets stuck in a bootloop. I do not experience this in the stock recovery
4. I was able to restore the phone through Smart Switch device intialisation. However, with everything stock I still experience the random reboots.
Bottomline: Is there anyway I can fix this on the software side (e.g. flash/update this or that)? And if not, do you think this is a hardware problem? Worth mentioning it's got a yellow screen bug but if i press hard on the back of the phone it disappears. Also, I can boot into stock recovery and download mode without any problems.
Thanks and sorry for the long post really need your insights.
Sorry you are having issues. I apologize if I missed this, but have you tried downloading the official firmware for your device from sammobile or similar sites, then flash that through Odin?

Phone stops working within 1-2 days after flashing.. tried both custom and stock roms

Hi,
My phone just stopped working without any physical or water damage. It got stuck on the logo. I flashed stock rom using SP flash and it started working fine. But after 2 days, it again got into boot loop. I starts like this
step1 - phone will get slow
step2 - apps will stop working
step3 - phone stops detecting simcard
step4 - phone will restart and will get into boot loop
So I rooted it and installed custom roms , but problem is still there. It stops working after 2 days. I have tried 5-6 custom roms available on forum e.g RR, lineage, AOSP, xenon HD. I even tried with older stock roms like S219 and sS57 without any luck.
What can be the possible reason? I'm not even installing any heavy app. can it be a memory leak issue? not expert here.. just guessing.
Have you use SP flash tool??
Use SP flash tool to get back in stock stage(stock recovery,stock boot,stock everything)
razorrzr1 said:
Use SP flash tool to get back in stock stage(stock recovery,stock boot,stock everything)
Click to expand...
Click to collapse
I have already tried that multiple times with all version of stock roms .. from s147 to s232. It just stops working after 1-2 days.
It automatically goes into boot loop. Is it possible that some sectors of internal memory are corrupt so whenever system tries to access it , it goes into boot loop? I'm saying this because this used to happen with my laptop.

[Help!] N910T3 Strange Crashing/Bootloop - Crashes even while in Recovery

Hey guys, I've encountered a thorny problem on my wife's N910T3, and am running out of ideas about what this could be... so, could really use some help.
Some background: The phone's been working fine for over a year of ownership, mostly on the stock ROM, which gets pretty laggy at times. A few weeks ago I installed a custom ROM (the Acapolypse-X N7 port) to improve performance, and for the past few weeks it's been working perfectly fine on the custom ROM no problem.
Today, when my wife went to check Twitter, the phone crashed and started bootlooping. I had seen a similar issue on my Note 3 before (which turned out to be a specific issue with the kernel I was using), so I figured I would just go into recovery, flash a different kernel or at worst, do a clean install of the ROM.
That's when things started getting weird: The phone would crash while INSIDE recovery during ROM installation (I've never seen a phone crash inside recovery before...) After failing to successfully flash a ROM or, even in cases when it succeeds, fails to boot, I decided to do a full flash back to the latest unmodified stock ROM (since I couldn't find an ODIN-flashable image to download, I used Samsung Kies for this - typically this resolves any kind of left over from previous installations).
On the first attempt, it succeeded - the phone booted into the stock ROM and I was able to start customizing settings. Figuring the issue has been resolved, I went ahead and attempted to root by flashing TWRP through ODIN, and that's when the phone went back to rapidly bootlooping again (it reboots every 2 seconds, I can't even get into recovery when this is occuring). The only way I can return to Recovery is by flashing it again in ODIN (typically this trick will only work once; upon rebooting the phone after that it is prone to start bootlooping again).
Based on the symptoms I suspected the NAND going bad. However, I receive no emmc read/write errors during flashing - all write operations in ODIN results in success and my friend even ran a full storage check via ADB and this phone just doesn't seem to have any bad sectors (I almost wish it were since that would resolve the mystery).
Anyone have any ideas what may be the problem? I have a decent amount of experience installing custom roms on my phones and troubleshooting installation issues, but I've never seen anything like this (crashing/bootlooping directly inside recovery).

Categories

Resources