Finally managed to get my phone working again...But can someone tell me what went wrong?
I was running JB NEATROM with SIYAH 4.1.5 Kernel. Strde I flashed GS2Wiper and then Dorimanx 9.42 kernel, then flashed CM 10.2. Booted and found all normal. went back and flashed Gapps system showing google maps , playstore error . Unable to use phone. Tried back flashing CM 10.2 and Slimbeam Rom working fine, but when flashing Gapps system gets stuck in booting logo.
Finally flashed old siyah kernel 4.1.5 and flashed NEATROM and to my big relief system operational. I want to update to JB 4.3 .Can someone please advice
are you doing a wipe and factory reset after all the different roms you are trying?
You can often avoid bootloops by following the developers ibstructions to the letter.
Then again, if certain ROM-Kernel combo is known for having this issue you could check that same custom ROM thread for support/fix.
That's pretty much how all of these flashing works.
Sent from the little guy
gastonw said:
You can often avoid bootloops by following the developers ibstructions to the letter.
Then again, if certain ROM-Kernel combo is known for having this issue you could check that same custom ROM thread for support/fix.
That's pretty much how all of these flashing works.
Sent from the little guy
Click to expand...
Click to collapse
Gaston, good to see you mate! Been stuck in another book for a few weeks?
@ OP: Beautiful summary by gastonw right here. Read the OP of the thread 2-3 times before flashing. You want to make sure it's compatible with your device, other mods/firmware, and that you know what you're doing during the install process.
Hey hopper, no, it's the UFC era now
Sent from the little guy
Related
Hi all, and thanks for reading this tread,
I have some issues and I'm hoping someone here could help shed some light on.
I was on ICS 4.0.3 and avoiding 4.0.4 due to brickbug issues. but I guess I couln't resist anymore and decided to give it a try. I tried to stay far away from buggy kernel so I used mobile odin to flash I9100XWLPT plus siyah 3.5.2 on one go
the result was a failure however, kernel flashed but firmware wiped (S2 logo was appearing but nothing else / softbrick ?).
Then I said oh well its not (hard)bricked or anything so I decided to use odin to flash I9100XWLPT, than siyah. It went ok but I lost mtp connectivity, tried s3 ported ui... didn't fly as well . Maybe something wrong with siyah 3.5.2 I thought, so tried an older siyah which I did not have an issue with h4.0.3. Situation did not improve however.
Then I flashed my old 4.0.3 and wiped, all ok mtp ok, upgraded to 4.0.4, all go, mtp ok.
Flashed siyah 3.5.2, mtp fails again. Tried android's own factory reset (not the on the boot menu, one on the personalization menu). Ended up with soft brick again (no boot only charging animation and odin mode). Flashed 4.0.4 again.
But this trial and eror process is going more dangerous by the minute I guess, so I decided to ask for support.
Do I do anything wrong? I want to upgrade to 4.0.4 everything as close as possible to stock, plus root and tocuhwiz from s3. its not too much to ask I guess.
Any suggestions and any explanations are very welcome also,
I'll thank any useful comments
kind regards,
I have 4.0.4 since 4th July with its stock kernel and it works perfectly well, I upgraded from 4.0.3 but I never did any wipes just updated on top of 4.0.3 and booted the phone, rooted from chainfires CF root thread, try it that way, worked for me and still is working.
ag4751 said:
I have 4.0.4 since 4th July with its stock kernel and it works perfectly well, I upgraded from 4.0.3 but I never did any wipes just updated on top of 4.0.3 and booted the phone, rooted from chainfires CF root thread, try it that way, worked for me and still is working.
Click to expand...
Click to collapse
Thanks If all else fails I'll try that, but siyah is a good kernel and it seems to be more battery efficient too.
If its a problem I failed to check with siyah I can go 4.0.4 kernel way but it makes me nervous to run a buggy kernel.
emk2z said:
Thanks If all else fails I'll try that, but siyah is a good kernel and it seems to be more battery efficient too.
If its a problem I failed to check with siyah I can go 4.0.4 kernel way but it makes me nervous to run a buggy kernel.
Click to expand...
Click to collapse
Totally agree Siyah is good I used it on 4.0.3 but it seems to fail on 4.0.4 at the moment I have not actually tried the latest one so it may well be good but I am looking to upgrade to SG3 next week so just want to keep my phone going for the time being no more playing around with this one until I have my new one.
I am using LQ5 which is reported as the buggiest but I can honestly say I have not had any problems at all, battery life appears good enough to me, depends how much you use it I guess.
Try speedmod k30 kernel, completely safe, fast and battery efficient
Sent from my GT-I9100 using xda app-developers app
Hayth said:
Try speedmod k30 kernel, completely safe, fast and battery efficient
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks, pardon me if I'm being paranoid but I just read a tread about nand corruption so, this isn't something like that I assume. (Odin flash failed and left me with soft brick out of the blue). Did not notice anything about siyah 3.5.2 either so the problem may be with my phone memory.
P.S Prior sentence reads as "Please prove me wrong"
I switched to speedmod kernel, and figured siyah had MTP problems with either 4.0.4 ics or 3.5.2
I asked same questions to those kernels' respective topics & thus this tread fulled it's purpose. Thanks kindly for anyone who read & replied
Sent from my GT-I9100 using xda app-developers app
Thread closed
Question answered, thread closed per OP's request
Unfortunately I cannot ask questions in specific thread, so I would like to do it now.
I have a problem after flashing LS8, specifically Wanamlite v.14. For some time phone works perfectly, until it suddenly switches off. I am able to power it up, but it freezes on the first screen with logo and model number. I am however able to access recovery.
And so I did - accessed recovery, flashed rom again, unfortunately, the only thing that worked was to do a full factory reset.
It worked... for a while. Then the story repeated itself. This time I did exactly the same, but started digging: some reported, that it might be a problem with kernel, which is Philz newest 4.00 b22. So I changed kernel: Dorimanx 7.44 - got serious overheating problems and the same probem. Jeboo 1.2 - the same. I then discovered, that eg. Jeboo has something from Philz kernel, so I flashed earlier version of Jeboo 1.1f. I am currently at this stage. Oh, btw. my chip is insane, if it changes anything.
Can anyone please tell me if you had similar problems, maybe not only users of Wanamlite, but other roms (which would confirm problems with kernel)? Can anyone tell me if there is any solution? Or at least does anyone knows what is happening? It is getting really weird, as I have been reading post of people reporting identical problem as I have, but devs seem to avoid the topic... Or maybe you guys are working hard to find out what is the problem - in that case a simple one line statement "we are aware. working on it" will suffice. Please, I am starting to be desperate here...
Regards.
Try Siyah kernel v6 beta4. I am also using WannamLite and have no issues at all.
Odp: [Q] Black Logo Screen problem
Thank you for the tip. I found the kernel elsewhere, however is there a thread about siyah v6 somewhere here, on xda-developers?
I will test it against problems I encountered and report for future readers.
The question still stays: what happened to me and all these other people?
Sent from my GT-I9100 using xda app-developers app
clawz71 said:
Thank you for the tip. I found the kernel elsewhere, however is there a thread about siyah v6 somewhere here, on xda-developers?
I will test it against problems I encountered and report for future readers.
The question still stays: what happened to me and all these other people?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yes it is, try to always download from xda.
You've experienced conflict between ROM & Kernel. Always check the custom ROM thread and read it upside down so you can spot potential issues regarding this kinda conflict.
Odp: [Q] Black Logo Screen problem
gastonw said:
Yes it is, try to [U/]always[/U] download from xda.
Click to expand...
Click to collapse
Could you point me in its direction? I have been using search extensively without any results.
gastonw said:
You've experienced conflict between ROM & Kernel. Always check the custom ROM thread and read it upside down so you can spot potential issues regarding this kinda conflict.
Click to expand...
Click to collapse
I did it, however, which is weird, only some of people reported it and dev, who in this case is Wanam, did not reply.
And I know, that it seems to be a conflict between rom and kernel, but how is it possible that not everyone had this issue while flashing Wanamlite with factory reset and kernel included in the rom? Nevertheless, I am sticking with Siyah for the while and see what happens.
Sent from my GT-I9100 using xda app-developers app
I have the same issue, it seems with LS8 whenever I reboot, there's a 50-50 chance my phone will "die" and I'll need a complete wipe and rom install
If I do a hot boot within Titanium Backup, guaranteed my phone will brake.
This happens with Siyah, PhilZ and Jeboo, it's not really a kernel issue, now a Wanamlite's issue since people on NEATROM also said they suffered the same issue, there's some problem with the firmware, seems that whenever the phone doesn't shut down properly, it won't start again.
Wish I could provide a log, but since phone totally dies, I don't know how to retrieve it.
@op: you got a siyah q&a thread sticked in the Q&A section.
Why don't you guys flash stock while you sort this out?
Custom ROMs will be updated soon now that ls8 is out. Therefore kernels will be updated as well.
Sent from the little guy
I'm having the same problem too. I have been using the Stock LS8 and Philz Kernel (4.00 b22-b30). I stopped using Siyah b4 in the previous JB Stock Leak because I had isues with the camera freezing.
Any suggestion?
clawz71 said:
Unfortunately I cannot ask questions in specific thread, so I would like to do it now.
I have a problem after flashing LS8, specifically Wanamlite v.14. For some time phone works perfectly, until it suddenly switches off. I am able to power it up, but it freezes on the first screen with logo and model number. I am however able to access recovery.
And so I did - accessed recovery, flashed rom again, unfortunately, the only thing that worked was to do a full factory reset.
It worked... for a while. Then the story repeated itself. This time I did exactly the same, but started digging: some reported, that it might be a problem with kernel, which is Philz newest 4.00 b22. So I changed kernel: Dorimanx 7.44 - got serious overheating problems and the same probem. Jeboo 1.2 - the same. I then discovered, that eg. Jeboo has something from Philz kernel, so I flashed earlier version of Jeboo 1.1f. I am currently at this stage. Oh, btw. my chip is insane, if it changes anything.
Can anyone please tell me if you had similar problems, maybe not only users of Wanamlite, but other roms (which would confirm problems with kernel)? Can anyone tell me if there is any solution? Or at least does anyone knows what is happening? It is getting really weird, as I have been reading post of people reporting identical problem as I have, but devs seem to avoid the topic... Or maybe you guys are working hard to find out what is the problem - in that case a simple one line statement "we are aware. working on it" will suffice. Please, I am starting to be desperate here...
Regards.
Click to expand...
Click to collapse
reading threads + trial & error.
Sent from the little guy
Odp: [Q] Black Logo Screen problem
gastonw said:
reading threads + trial & error.
Sent from the little guy
Click to expand...
Click to collapse
We do it. We read threads and do trial and error. I even started a separate thread to report our trials to the community. This one
Thank you for your input.
pedroren said:
I'm having the same problem too. I have been using the Stock LS8 and Philz Kernel (4.00 b22-b30). I stopped using Siyah b4 in the previous JB Stock Leak because I had isues with the camera freezing.
Any suggestion?
Click to expand...
Click to collapse
Well I am still on siyah v6.b4. So far so good. But I am not too happy with battery life... You might try jeboo 1-1f, as some reported it doesn't cause any problems. I had jeboo 1-2 for a while but out generated the same bootloop...
Sent from my GT-I9100 using xda app-developers app
Odp: [Q] Black Logo Screen problem
gastonw said:
Custom ROMs will be updated soon now that ls8 is out. Therefore kernels will be updated as well
Click to expand...
Click to collapse
What do you mean by that? We are discussing here ls8 kernels, aren't we? Newest Phillz is a stock one based on ls8, afaik.
Sent from my GT-I9100 using xda app-developers app
[Sorry for double post, I thought it merges automatically]
I truly don't know what was being discussed here, If I posted that is because I must think that all ls8 kernels are in beta.
Man, I really gotta get some sleep
Sent from the little guy
Hey there,
I've been using Cyanogen mod 10 for about a year now (actually probably 10 for 6 months and then moved to 10.1 as soon as it came out). But just today I decided to update to the latest version of the OS through cyanogens update feature on the phone. I was updating to 10.2 FROM 10.1, but I didn't realise the latest version was 10.2 until I checked after. Now my phone restarts by itself every 20 mins and my 3G is doing weird things :/
But the main problem is that I CAN'T boot to recovery mode anymore! I don't know why?! If I could, then I could fix everything :/
Any help would be much appreciated thanks. I can provide any further details if needed. I hope to get this fixed soon as I use it quite a lot! xD
Obviously broke recovery. You could try flashing an Odin version of a custom kernel, but this may not work (might as well try it tho). If it were me I'd go back to stock via Odin, re-root & restore nandroid backup or reflash rom/kernel & start again from scratch (tho I wouldn't need to do this because I make regular nandroids).
Personally speaking, I wouldn't use that update from the phone feature in future. Flash updates/nightlies from recovery. Takes a few extra minutes, but saves you a lot of grief.
MistahBungle said:
Obviously broke recovery. You could try flashing an Odin version of a custom kernel, but this may not work (might as well try it tho). If it were me I'd go back to stock via Odin, re-root & restore nandroid backup or reflash rom/kernel & start again from scratch (tho I wouldn't need to do this because I make regular nandroids).
Personally speaking, I wouldn't use that update from the phone feature in future. Flash updates/nightlies from recovery. Takes a few extra minutes, but saves you a lot of grief.
Click to expand...
Click to collapse
Thanks for the quick reply and tip! For now on I will definitely install from recovery only.
I tried reflashing the Clockwork recovery thing but it didn't seem to fix it.
So I was thinking about flashing the Siyah kernel? Is this a good idea? I flash just the PDA file only right?
Sorry for not knowing much about this flashing stuff xD
Yeah, you might as well try the Odin version of Siyah even tho it probably won't work. Can't hurt put it that way. Yep, flash it in the PDA section of Odin. If that doesn't work flash a stock rom with Odin as I mentioned (also in the PDA section). If you get stuck, look for Hopper8's 'Odin won't flash' thread.
MistahBungle said:
Yeah, you might as well try the Odin version of Siyah even tho it probably won't work. Can't hurt put it that way. Yep, flash it in the PDA section of Odin. If that doesn't work flash a stock rom with Odin as I mentioned (also in the PDA section). If you get stuck, look for Hopper8's 'Odin won't flash' thread.
Click to expand...
Click to collapse
Ok I tried flashing Siyah and didn't work :/ Ok I will give flashing a stock rom a try. I presume that puts it back to the way it is? Then I have to re root etc?
Thanks!
Yep.
MistahBungle said:
Yep.
Click to expand...
Click to collapse
Reflashed to a pre-release version of JB from Samsung Thanks heaps for your help! Appreciate it. Will probably go back to Cyanogen tomorrow.
One question though. Is Cyanogen 10.1 supposed to be quite stuttery? I know it's a nightly build and all. But using this official pre-release from Samsung, it's JUST SOOOOO MUCH MORE SMOOTHER! But I expect Cyanogen to be a lot faster :/ Maybe my kernel was just having problems the whole time?
Thanks!
Good man Can't comment on CM10 as I've never used it, used CM9 for ages & got fed up with various things not working as they should/being flaky & have never bothered with CM10 as a result, I'm sure someone else will be able to answer those queries.
I'm guessing you flashed the 0824 nightly of 10.2. According to the discussion thread, anybody who uses this nightly will experience the broken recovery....they've posted a link to a kernel + recovery which needs to be flashed before the phone is rebooted for the first time in order to replace the broken recovery. Concerning the stability of the ROMs.........
10.2.....IMO...NOT stable enough for daily use....
10.1.....fast and smooth, and no bugs that make me want to stop using it.......
10.0.....not as fast as 10.1 but just as smooth but with the same lack of noticeable bugs as 10.1.....
JB Firmware.....obviously the most stable, but simply not as fast.....even if rooted and debloated......
Back to 10.1 for now.....
keithross39 said:
I'm guessing you flashed the 0824 nightly of 10.2. According to the discussion thread, anybody who uses this nightly will experience the broken recovery....they've posted a link to a kernel + recovery which needs to be flashed before the phone is rebooted for the first time in order to replace the broken recovery. Concerning the stability of the ROMs.........
10.2.....IMO...NOT stable enough for daily use....
10.1.....fast and smooth, and no bugs that make me want to stop using it.......
10.0.....not as fast as 10.1 but just as smooth but with the same lack of noticeable bugs as 10.1.....
JB Firmware.....obviously the most stable, but simply not as fast.....even if rooted and debloated......
Back to 10.1 for now.....
Click to expand...
Click to collapse
Sorry about the late reply.
Yes that was the exact build! xD
Oh well I am actually quite happy with the official JB firmware from Samsung atm. It's A LOT SMOOTHER than 10.1 for some reason :/ I don't know why. Just is. I had lots of problems with 10.1. At times the RAM seemed to leak so much I would have to restart it otherwise it would just be so stuttery. ESPECIALLY with Swift Keyboard and Facebook heads xD It's ashame because I really liked Cyanogen. Missed some of the features.
Hello everyone, I was using ultimarom till now and it worked like a charm. Today I thought hey lets upgrade to android 4.4 so I found temasek's rom and it seemed fine. After flashing the rom, it got stuck on boot screen. So I reflashed the stock rom (btw I wiped everything as required) and it was working. So I retried flashing the Temasek's rom and it booted this time, only thing is that my touch screen was not responding. The capacitive buttons are working also the touch screen is showing everything but not responding to anything. I searched a little bit, and it might be possible that my digitizer is broken which I hope is not since I am in a different country and it will be a pain to do it here. Also I read that if you tried to install Note 2 kernel/rom this might happen but I know that temasek's rom is definitely for s3 so it shouldnt be the case for me. Any help would be appreciated.
Thanks
Bektas
Darrier said:
Hello everyone, I was using ultimarom till now and it worked like a charm. Today I thought hey lets upgrade to android 4.4 so I found temasek's rom and it seemed fine. After flashing the rom, it got stuck on boot screen. So I reflashed the stock rom (btw I wiped everything as required) and it was working. So I retried flashing the Temasek's rom and it booted this time, only thing is that my touch screen was not responding. The capacitive buttons are working also the touch screen is showing everything but not responding to anything. I searched a little bit, and it might be possible that my digitizer is broken which I hope is not since I am in a different country and it will be a pain to do it here. Also I read that if you tried to install Note 2 kernel/rom this might happen but I know that temasek's rom is definitely for s3 so it shouldnt be the case for me. Any help would be appreciated.
Click to expand...
Click to collapse
have you changed your recovery?
if you flash now another rom or restore your old one does the screen still not work?
Darkened_Sky said:
have you changed your recovery?
if you flash now another rom or restore your old one does the screen still not work?
Click to expand...
Click to collapse
I tried with both stock and temasek once again and the touch screen still does not respond. I always used cwm for recovery though, and did a factory reset on the stock recovery once to see if that works. I can flash ultima as well I suppose but I am not sure if that will fix it.
Edit: I tried to flash ultima but the installation steps required the use of touch screen so I could not proceed.
Are you sure that you download Temasek's rom for I9300 not for another model? Because Temasek supports more devices.
And on Temasek's thread I didn't find any user complaining about touch screen issue after installing it,so I think that you flashed it for different model.
Darrier said:
Hello everyone, I was using ultimarom till now and it worked like a charm. Today I thought hey lets upgrade to android 4.4 so I found temasek's rom and it seemed fine. After flashing the rom, it got stuck on boot screen. So I reflashed the stock rom (btw I wiped everything as required) and it was working. So I retried flashing the Temasek's rom and it booted this time, only thing is that my touch screen was not responding. The capacitive buttons are working also the touch screen is showing everything but not responding to anything. I searched a little bit, and it might be possible that my digitizer is broken which I hope is not since I am in a different country and it will be a pain to do it here. Also I read that if you tried to install Note 2 kernel/rom this might happen but I know that temasek's rom is definitely for s3 so it shouldnt be the case for me. Any help would be appreciated.
Thanks
Bektas
Click to expand...
Click to collapse
Flash back to stock with odin if problem is still there then it is hardware issue....
I rechecked and it is temasek for I9300. I restocked ofc with odin and it is no use tbh. I mean it is weird as the first time I flashed stock rom the touch screen was not working for 30 seconds or sth than it started working so I was really happy for a second.. After another flash it was not working and I was like yea it will work soon, but it didnt. I tried with loads of roms and kernels and it is still no use.
Any help? I have no idea how to fix this! I may have to send my phone for replacement which will be costly I suppose.. Any little tip will be appreciated.
Darrier said:
Any help? I have no idea how to fix this! I may have to send my phone for replacement which will be costly I suppose.. Any little tip will be appreciated.
Click to expand...
Click to collapse
Didn't u install the new version of Cwm? I'm using ultimarom v16 & I try to use Android v4.4.2... It seemed good to me
Sent from my GT-I9300 using Tapatalk
Solution
Hey dude, I couldnt find any solution to that problem. What I did was to send it in for replacement but with warranty. For that you need to triangle away your phone and also install the official firmwares. I had to use a mouse in order to do that but you will need a usb to micro usb converter, which is not that hard to find( and also cheap). They couldnt tell that I installed unofficial firmware, I replaced my screen flawlessly. You can find how to triangle away your phone in this forum and also sammobile is the place to look for official firmware.
Cheers
wanerza77 said:
Didn't u install the new version of Cwm? I'm using ultimarom v16 & I try to use Android v4.4.2... It seemed good to me
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Ive tried installing the 4.4.2 ROM Achidroid N7000 on my phone using TWRP but it skipped the MD5 check and said "Installation failed/aborted....". I then tried an AOSP 4.4.2 ROM but it said the same error message. After that, I gave up and tried to use the phone. When it booted up, it froze on the Samsung logo and wouldnt boot up completely. Ive tried doing a FDR through the custom recoveries but still the same thing happens. I really dont know what to do. I have an i9300 under 4.3.
Any help would be appreciated. Thank you.
Follow the guide in general forum on how to flash a stock firmware, download the latest one for your country from sammobile.com.
Factory reset after flashing in recovery.
Sent from my GT-I9300 using Tapatalk
jheayahr said:
Ive tried installing the 4.4.2 ROM Achidroid N7000 on my phone using TWRP but it skipped the MD5 check and said "Installation failed/aborted....". I then tried an AOSP 4.4.2 ROM but it said the same error message. After that, I gave up and tried to use the phone. When it booted up, it froze on the Samsung logo and wouldnt boot up completely. Ive tried doing a FDR through the custom recoveries but still the same thing happens. I really dont know what to do. I have an i9300 under 4.3.
Any help would be appreciated. Thank you.
Click to expand...
Click to collapse
I dun think archi developed any rom for the N7000. At least I didn't see any when googling. But if you flashed a N7000 rom on ur phone, even if u finally unbrick it, I bet there will be some hardware issues.
JellyYogurt said:
I dun think archi developed any rom for the N7000. At least I didn't see any when googling. But if you flashed a N7000 rom on ur phone, even if u finally unbrick it, I bet there will be some hardware issues.
Click to expand...
Click to collapse
That should be a typo its n7100 which is the port for our s3 from international note 2
Sent from my GT-i9300
The first page alr said tat the rom is VERY buggy and is in the experimental state. Many things are not working in tat rom. So I have no idea why some one would wan it as their daily driver rom.
Issue Solved
Thank you guys. I was able to flash the ROM properly using PHILZ recovery.