I'm using a SEA N7105.
first and foremost:
ROM: CM10.2 Nightlies
Kernel: Stock CM
Baseband: XXDMD1
So here's how it goes. Initially the phone got rooted and yeah, subsequently it was flashed Xylon, then to WanamLite 1.3. so after that, I flashed to CM10.2. and from now on, the device just stucks on the bootsplash screen whenever I reboot and will require a wiping data (I must wipe the internal storage also, in order for it to even boot) in recovery. It seems as if the data folder is corrupted. Initially I thought that the eMMC chip caused the issue but the eMMC was diagnosed without the syndrome. So now, I'm wondering if anyone has met this issue before. Please help me
Thanks in forward.
Sent from my GT-N7105 using Tapatalk 2
bump
Sent from my LG-P990 using Tapatalk 2
Then flash another rom from recovery
Or at least try to flash stock rom from odin :thumbup:
Related
First a little background. I am not new to the android world whatsoever. I don't post much but have been lurking for years. I had a Verizon GS3 and just recently switched to T-Mobile a few days ago and obviously bought a T-Mobile GS3. My vzw phone had no problems. But for some reason my T-Mobile phone will not boot any kernel I try to flash. Roms flash fine but when I flash a kernel everything goes fine in recovery but my phone won't boot past the splash and I end up having to restore a backup. I know I'm flashing the right kernels. I am on touchwiz based ROMs and haven't tried any aosp Rom because for the first time ever I actually prefer an OEM skin to aosp. So basically am I missing something obvious. Anyone else having thus problem. On Verizon I had to root and unlock the bootlosder. From what I understand tmobiles bootliader was not locked down and all I had to do was root. Like I said. I've tried every touch wiz Rom and every touch wiz kernel with each Rom and none will boot past the splash screen. I always wipe dalvik and cache but even tried wiping data every time too and keep getting the same result. Any input would be appreciated. . Thanks in advance.
Sent from my SGH-T999 using xda premium
Shouldn't need to do any wiping of any kind. I only use AOSP/AOKP, though. May I ask why you even bother with custom kernels? They honestly seem like a waste of time to me.
Im just flash happy. Like to try them out. I've been on Verizon for many Years and am used to the developers over there. I'm still getting used to the devs over here. Don't know any of there work. I'm sure its all good though. Been using imoseyons lean kernel since the thunderbolt back in the day and have stuck with them. Just my personal preference. I'd like to try some of tmobolrs kernel devs work but like I said I can't get a single one to boot.
Sent from my SGH-T999 using xda premium
What kernels have you tried to flash? There are a couple that have ICS builds. Also, what version of CWM are you using?
I've tried all the tw kernels. Every single one with 2 different ICS tw ROMs. I'm not using the leaked jb tw. I'm stickung with the more stable ICS ROMs for now. I just don't understand. I've tried every one. I've been flashing a long time and don't get it. Im kinda new to Samsung though. First Samsung was the galaxy nexus. Didn't ever use Odin with it. Does anyone flash kernels with Odin. Maybe I should try that. And to answer your question I've tried twrp and the latest version of cwm from rom manager. And of course I'm using the ICS TW version of the kernels im trying.
Sent from my SGH-T999 using xda premium
It could just be your phone doesn't like them. There is another guy on CM10 and AOKP that can't get custom kernels to boot either.
Sent from my Nexus 7 using Tapatalk 2
The kernel source code was never released for any build from UVALH2 and beyond. So most of our kernels will only work with UVALEM and UVALG1 builds.
We got kind of lucky I think and ktoonsez att kernel was brought over and works. I think there's one or two others that work now too.
As far as described here go I think we've got some of the best! For an outstanding rom you should try FreeGS3. It works with most of the kernels and is an awesome stable rom. If you want a later build try wildcards XquiziT v70 based on UVALH2. Use ktoonsez kernel with it.
And just to note, the stock kernel is surprisingly good. So give it a fair shot as well. Though I can definitely see some potential advantages of custom ones as well.
Sent from my SGH-T999 using xda app-developers app
Thanks for all the info. But now I can't even get any other ROMs to boot. I don't get it. I keep having to restore my Xquizit v20 back up. Its driving me nuts
Sent from my SGH-T999 using xda premium
jasonpantuliano said:
Thanks for all the info. But now I can't even get any other ROMs to boot. I don't get it. I keep having to restore my Xquizit v20 back up. Its driving me nuts
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Have you done full Wiping?
Wipe Data/Factory Settings
Wipe cache and dalvik
Flash Rom
Fix Permission
Reboot and don't touch it for 10 minutes
Reboot.
Wipe cache and dalvik
Flash Kernel (Must be compatible with ROM)
Fix Permission
Reboot and don't touch it for 10 minutes
Reboot.
See if this will work. Sometimes you have to let it breathe so it can adjust itself.
Have you tried uding odin to flash MrRobinsons root66 UVALH2? This will take you to fresh full stock plus root. Then try roms again.
Sent from my SGH-T999 using xda app-developers app
Whatever you do................
Be sure to double check before you flash that kernel. Had my first SGS3 for 12 days before hard brick set in. Terrible disease it is.......! I had to adopt a replacement shortly after to cope with the pain of the loss. Back on my feet again now though and soarin' higher than giraffe vagina on the things I learned in my days off for mourning. I can tell ya I've personally flashed the lean kernel and kt-747 with no issues. My problems were with siya mainly.
Guys, I have a serious problem.
It's similar to the one of the thread-opener.
The diference is that I cant get ANY ROM to boot, WITH the stock kernel.
And i do like the guide says: wipe/factory reset, wipe chache, wipe dalvik cache and then flash the ROM.
Everything works fine til the ROM finished flasing and runs a reboot.
My S3 shuts down screen, then turns screen on with the "Samsung Galaxy SIII-GT-I9300" and then thats it!
All i can do is to go in download mode or recovery mode. I can also flash CWM and so on, but after flashing ROMs it won't boot!
Is it possible that i broke the device by formating internal sd-card with the stock recovery tool?
Did it, after I tried to install Wickedv6 ROM and after both times when it rebooted it just reinstalled stock ROM. So i thought, ok delete the internal sd-card, so no stock ROM on it any more.
Also tried this ROM: http://forum.xda-developers.com/showthread.php?t=1875923
Same problem.
Also tried to fix the problem by rooting and then flashing ROM. No help.
Please help guys!
Best regards
ke-ironman said:
Guys, I have a serious problem.
It's similar to the one of the thread-opener.
The diference is that I cant get ANY ROM to boot, WITH the stock kernel.
And i do like the guide says: wipe/factory reset, wipe chache, wipe dalvik cache and then flash the ROM.
Everything works fine til the ROM finished flasing and runs a reboot.
My S3 shuts down screen, then turns screen on with the "Samsung Galaxy SIII-GT-I9300" and then thats it!
All i can do is to go in download mode or recovery mode. I can also flash CWM and so on, but after flashing ROMs it won't boot!
Is it possible that i broke the device by formating internal sd-card with the stock recovery tool?
Did it, after I tried to install Wickedv6 ROM and after both times when it rebooted it just reinstalled stock ROM. So i thought, ok delete the internal sd-card, so no stock ROM on it any more.
Also tried this ROM: http://forum.xda-developers.com/showthread.php?t=1875923
Same problem.
Also tried to fix the problem by rooting and then flashing ROM. No help.
Please help guys!
Best regards
Click to expand...
Click to collapse
This isn't the I9300 forum, but if you flashed a T999 rom, you bricked your phone.
Aerowinder said:
This isn't the I9300 forum, but if you flashed a T999 rom, you bricked your phone.
Click to expand...
Click to collapse
Wow, you scared the **** out of me
But i just tried to flash stock ROM: http://forum.xda-developers.com/showthread.php?t=1646610
It worked out!
What is the right forum for my GT-I9300 to post then?
And why isn't any other ROM working?
The forum you got that stock rom from is the international one. This is the US Tmobile T999 forum. The two phones are NOT compatible.
Only flash, well...anything, from that forum. Our roms will brick yours and vice versa.
Sent from my SGH-T999 using xda app-developers app
Hi, this morning I encountered something which I haven't seen before in my 3 years or so of flashing roms on Android phones. The scenario was the standard process: Root with Odin > Install CWM with Odin > Copy Rom / gapps package to sdcard > Wipe & Install rom with CWM.
I rooted my Note II using CF Auto Root, all went fine, I flashed the latest Phil's touch CWM recovery using Odin which was also successful.
I had root access and was able to do a titanium backup of apps and messages/call logs. I successfully did a Nandroid backup of the stock rom.
After wiping data through CWM as per normal, I flashed the latest Utacka ParanoidAndroid and gapps. The flash was successful, but after rebooting, the 'Samsung Note II' splash screen only appeared briefly, then the image sheared and distorted and the screen went black, in less than three seconds.
I restored my nandroid backup and repeated the process, this time also formatting system, and installing CM10.1 nightly instead of PA. Again, I got a distorted splash screen then a black screen when trying to boot.
Can anyone think of a reason why my phone does not seem to be able to boot a custom rom?
Many thanks
I read on the forum someone else had a similar issue with cm as well
Sent from my GT-N7100 using xda app-developers app
koalauk said:
I read on the forum someone else had a similar issue with cm as well
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Really? I've tried searching xda, google and the CM forums and havent found anything relevant.
I had this problem recently and after some nice guys helping me out we conclude that the solution is to flash RedPill kernel as the culprit for this glitch is the stock kernel you previously had.
I had such issue with my Note2 too. I was advised to flash Thor kernel 0.15 too after flashing cm10.1 and gapps. And problem was solved. Now cm10.1 boots normal on my Note2.
Sent from my GT-N7100 using xda premium
Did you do a factor reset.
Sent from my GT-N7100 using xda app-developers app
Hey all,
I've been flashing roms for past two years and decided to change the kernel on my Samsung s3 which was running CM10.1 RC5. I had decided to go with Fauxs kernel and did follow steps outlined in the thread below.
http://forum.xda-developers.com/showthread.php?t=1785472
Now, upon rebooting the device I only get the Samsung logo and that's about it. When I plugged the phone into my computer the green light comes on and the touch bottons light up. I also can't seem to get into recovery to reflash my rom and go about my business. Is my phone bricked?
Any advice would be appreciated!
Can you get download mode?
Sent from my SGH-T999L using xda premium
This isn't meant for 3.4...pretty sure that's the issue. .
Current rom/kernel: Liquid Smooth 2.5/ktoonsez
Lack of reading messed up your phone. Just reboot into recovery via hardware keys, restore backup.
T-Mobile SGS III
I agree witg mt3g. Maybe do a wipe cache and dalvik cache.
Sent from my SGH-T999 using Tapatalk 4 Beta
Unless that kernel was retreived from some where other then XDA cause his latest on his site is Mar-13 which is 3.0 kernel before the latest merges and stuff for 3.4 which is what the latest AOSP roms run after Mar-17... so ya you flashed a kernel that isn't up to date. Your phone is fine, just read more before doing.
I love it when people blame the devs for not RTFM.
I've been looking for help and can't find any
Does anybody know why android 4.3 will not start back up after a reboot, it just stays on the Samsung boot screen but never boots up.
I've tried wiping both cache and full wipe the system everything I can think of
can someone plz Help me
Sent from my GT-N7105 using Tapatalk 2
vwpro177 said:
I've been looking for help and can't find any
Does anybody know why android 4.3 will not start back up after a reboot, it just stays on the Samsung boot screen but never boots up.
I've tried wiping both cache and full wipe the system everything I can think of
can someone plz Help me
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
I've got the same problem. Totally clean installs but upon reboot, I'm stuck at the note 2 screen. 4.2.2 ROMs boot. Probam roms mentioned having an unlocked bootloader but i thought that was a prerec to being rooted?
No problems here. One thing on 4.3 roms is the su binary needs to be updated usually. Supersu from the play store addresses this. I'm running the cm 4.3 9-1 nightly.
Sent from my SGH-T889 using Tapatalk 2
vwpro177 said:
I've been looking for help and can't find any
Does anybody know why android 4.3 will not start back up after a reboot, it just stays on the Samsung boot screen but never boots up.
I've tried wiping both cache and full wipe the system everything I can think of
can someone plz Help me
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
Which recovery are you using to flash it?
Twrp
Sent from my SGH-T889 using Tapatalk 2
Clockwordmod superuser app was the key! After the first boot, I ran the app and even though it always wanted to be updated (even after it went through its process) 4.3 ROMs would reboot! I tried probam and pacrom. Each time I flashed new, I had to re update the su or else no reboot. Thanks for your help!
Stuck at cyanogenmod screen on t0ltetmo 10.2 Need help
I'm having the same problem, I had stock new 4.1.2 t0ltetmo. Rooted/TWRP recovery booted fine. Loaded RomManager booted into recovery flashed 10.2 nightly from 9/9/2013 then flashed 4.3 GAPPS, Wiped cache, now it's just sitting at the cyanogeMod screen does not boot. I've installed a lot of roms w/o issue but am a novice.
How do I get back into recovery? What is my course of action? HELP!! Thanks
I was using the latest alpha of CM11, then i i wanted to get back to CM10.2, i did all i had to do (wipes, and stuff) and when starting up, the phone frezees and keep on doing this...
I also have searched about this issue and found no answer.
tpag02 said:
I was using the latest alpha of CM11, then i i wanted to get back to CM10.2, i did all i had to do (wipes, and stuff) and when starting up, the phone frezees and keep on doing this...
I also have searched about this issue and found no answer.
Click to expand...
Click to collapse
Have you tried booting to recovery, then doing an advanced wipe (system/data/cache/dalvik) and reflashing rom/gapps?
What version of recovery are you using?
Almite said:
Have you tried booting to recovery, then doing an advanced wipe (system/data/cache/dalvik) and reflashing rom/gapps?
What version of recovery are you using?
Click to expand...
Click to collapse
yes, i have. I also got back to stock, used an older recover, flashed with an older version of CM and nothing. I first was using CWM 6.0.3.7., after that I used 6.0.4.3, then an older version of TWRP but nothing. I also tried booting to system without flashing gapps.
With stock ROM everything works just fine.
Just wipeout internal and external card once and than install with twrp 2.6.1.0. And don't forget to say thanks
Sent from my SGH-T989 using xda app-developers app
iamdofus said:
Just wipeout internal and external card once and than install with twrp 2.6.1.0. And don't forget to say thanks
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Well, thank you, but it didn´t work.
it happened to me the same thing months ago. never had solution. still in waiting. attempt internal and external SD format. and followed the same. I hope someday they can come up with the solution! : (
i have the same problem too
I try to install multiple ROM 4.2.2 and I could only install one version AOKP Milstone JB1. I also worked the other. however all 4.1.2 rom if I worked. I could not install any 4.3 and 4.4 now does not know what is the problem but I've tried everything! anyone found the solution yet but I see I'm not the only one! (excuse my bad English, not my language )
Well you all are right, I am also using shadow mastery (stock rooted rom). Just because I had the same problem sometimes stucking and rebooting and sometimes after going in gallery. Even I can't use 4.3 and 4.4 roms. Anyone have to contact with room developer or someone who know about this problem.
Sent from my SGH-T989 using xda premium
You might want to find an Official T-Mobile or Telus 4.1.2 or 4.0.3/4.0.4 rom that is Odin flashable, not one that has been custom made/flashable from recovery - then just start over after getting back to true stock, change to TWRP or CWM recovery that is 4.3+ compatiable, root and then flash rom/gapps etc.