Hello all
I attempted to root and CWM my Mega and that seemed to go fine..
I can run CWM 6032 without issues
So I proceeded to install a custom rom I firstly did full wipe / cache and dalvik then installed the rom.
It boots to samsung logo and just hangs..
So I went back to the drawing board..Dled fresh tar img flashed with odin just had auto reboot and F.reset time ticked but the phone is still stuck at the samsung logo and not doing anything else..
I just got this amazing phone and its bricked already
Starting to panic
Please help
Jonny
OK After a good nights sleep things dont seem so bad
I got stock firmware loaded but I had to go into the stock recovery after the flash and do another factory reset / cache wipe
Jonny
:laugh:
Jonny5isalivetm said:
OK After a good nights sleep things dont seem so bad
I got stock firmware loaded but I had to go into the stock recovery after the flash and do another factory reset / cache wipe
Jonny
:laugh:
Click to expand...
Click to collapse
Good for you
I remember my first few flashes, with the little bootloop panic...
Usually, if one takes the time too pause and read and think (very probably someone had the issue, and the answer is here in the forums), then all those little issues can be fixed without too much trouble
hi man :>
i have flashed other phones before but noone gave me as much trouble as the mega..
glad she is running now
Real smooth atm with silentnight rom + an app off the store to decrease cpu speed..currently at 700mhz and i cant tell the difference!
Thanks for reply man
Yeah, every phone has its way.
I used to have HTC phones, and those seem to be the most annoying ones, with software updates locking the bootloader and such annoyances.
It might have changed now, though
I always make nandroid backup before flashing new rom, just in case things happen
Sent from my GT-I9152 using XDA Premium 4 mobile app
Bricked sgh-1527m
Hi,
I am wondering if you have any tips or info on unbricking my phone.
I seem to be having this same problem.
It has to do with a knox update i believe.
you mention a bootloader lock..is their some method to unlock so that it will allow me to flash the rom again.
any information would be greatly appreciated..I am getting a crash course in this trying to get my phone back up and running
thanks
Chris
kipue said:
Yeah, every phone has its way.
I used to have HTC phones, and those seem to be the most annoying ones, with software updates locking the bootloader and such annoyances.
It might have changed now, though
Click to expand...
Click to collapse
Jonny5isalivetm said:
Hello all
I attempted to root and CWM my Mega and that seemed to go fine..
I can run CWM 6032 without issues
So I proceeded to install a custom rom I firstly did full wipe / cache and dalvik then installed the rom.
It boots to samsung logo and just hangs..
So I went back to the drawing board..Dled fresh tar img flashed with odin just had auto reboot and F.reset time ticked but the phone is still stuck at the samsung logo and not doing anything else..
I just got this amazing phone and its bricked already
Starting to panic
Please help
Jonny
Click to expand...
Click to collapse
can you tell me how u root ur GT-I9205 ?? my attempts to root have made my samsung galaxy mega goes into a condition where...
1) when it boots up, there are sounds but no logo
2)i tried the custom recoveries,, it works fine
3) i tried the download mode,, there is only black screen,,,
please help me as a fellow gt-i9205 ...
Related
I recently updated my phone from 2.3.3 to Cyanogenmod 7.1 I believe and went to overclock the phone, Unfortunately, I overclocked it too much and now it is stuck in an endless loop on the boot screen..
Phone is obviously a Galaxy Ace, Network carrier is Vodafone UK.
I have been trying for the last two hours to look for answer's on how to fix this and I haven't found anything, So I thought the best idea was to come to here.. Any help would be appreciated, I have also tried to install other ROM's on to the phone to correct it but it look's like the CPU is still at the overclocked setting and because of that, Won't boot up.
thanks.
Dan.
go to recovery and wipe data+cache and try to boot..
if still no luck --> ODIN
madman_amit said:
go to recovery and wipe data+cache and try to boot..
if still no luck --> ODIN
Click to expand...
Click to collapse
I tried wiping everything before but will give ODIN a try. Thank you. I really like the phone and am trying my best to get it working again. lol
So, I downloaded ODIN and I have absolutely no idea what I am doing.. I don't want to risk breaking the phone anymore.. The only tut on how to use ODIN is for the Galaxy 3..
I have never done anything like this before so it's all new to me.. :/
Ok, I used ODIN and I have the original ROM that came with the phone, But still in an endless loop on the Samsung boot screen.. :/ I am totally stuck now.. I have tried all I know to get it to work
I managed to sort the problem, the "One Package" on ODIN didn't work, Luckily I had the 4 seperate files needed on my laptop, So all is workign now.
Th3GrimRipp3r said:
I managed to sort the problem, the "One Package" on ODIN didn't work, Luckily I had the 4 seperate files needed on my laptop, So all is workign now.
Click to expand...
Click to collapse
Excellent work having a backup on your laptop. First thing now do a full backup on your phone before you think about further experiment. If overclocking make sure "set at boot" is not ticked. Finally read up a little on xda before you do anything - a good place to start is "Tutorial" on top of dev section and the "q & a " thread here.
I hope this works for You.
You've a one packege STOCK Rom?
so open ODIN 4.38
Untick Reset Time
Choose your one package file.
choose OPS; attatched here.
press start.
to sum up: you have this ticked only:One package, auto reboot, protect OPS
if doesnot work go to recovery and try factory reset& cache wipe.
if doesnot work, try flshing CWM and install any backed up rom, if you want one. just PM and i will upload backed up stock rom.
I really hope it helps because I got the same issue after flshing a stock from ODIN, but been removed from wipe data& factory reset.
_________________________________________________
If I've helped you in any way, Press THANKS
Hey guys first of all you have to know that im German and a student so sorry for my english.
My device: Samsung galaxy s3 (intl.)
I booted my phone and flashed my kernel some days ago and everything worked fine, then with the 4.2 update samsung hided the developer options on the devices. I knew that, and `activated` the dev. options again. Then i was scrolling around there and i enabled simulate secondary displays or something like that.. after doing that my Device rebooted on and on. It hanged upwhen i had to fill in my pin. At that point it booted again and again. Couldn´t do anything. I can get in cwm.
So my Problem now is that i `full wiped` my phone which i think means i wiped data/factory reset, then i wiped cache, then wiped delvik cache,then i formated /system AND i think data.. after that i installed cm and gapps again but my Phone stucks at the booting screen i really don´t know what to do. Please help me.
I can´t find the correct Version of the Stuck Rom too.. i think its not available for German devices or something.
Thanks :crying::crying:
mietzemaunz said:
Hey guys first of all you have to know that im German and a student so sorry for my english.
My device: Samsung galaxy s3 (intl.)
I booted my phone and flashed my kernel some days ago and everything worked fine, then with the 4.2 update samsung hided the developer options on the devices. I knew that, and `activated` the dev. options again. Then i was scrolling around there and i enabled simulate secondary displays or something like that.. after doing that my Device rebooted on and on. It hanged upwhen i had to fill in my pin. At that point it booted again and again. Couldn´t do anything. I can get in cwm.
So my Problem now is that i `full wiped` my phone which i think means i wiped data/factory reset, then i wiped cache, then wiped delvik cache,then i formated /system AND i think data.. after that i installed cm and gapps again but my Phone stucks at the booting screen i really don´t know what to do. Please help me.
I can´t find the correct Version of the Stuck Rom too.. i think its not available for German devices or something.
Thanks :crying::crying:
Click to expand...
Click to collapse
sammobile.com for stock roms.
rootSU said:
sammobile.com for stock roms.
Click to expand...
Click to collapse
i know but my rom for my device isn´t there.. I reseted it to stuck with an Stuck rom from another surce it keeeps stucking at the samsung galaxy s3 booting screen
You have installed a leaked beta, not an update from Samsung.
Follow the guide in general stickies on how to return your phone to stock. Sammobile does have firmware for i9300 in Germany.
Hmm I think it's more CM or gapps issue if you can't boot up your phone with these things.
If you can go into download mode you can try to flash Stock Rom using Odin.
And always remember before flashing custom roms make a backup of the stock one.
Simonna said:
Hmm I think it's more CM or gapps issue if you can't boot up your phone with these things.
If you can go into download mode you can try to flash Stock Rom using Odin.
And always remember before flashing custom roms make a backup of the stock one.
Click to expand...
Click to collapse
i got it work again but my wifi doesnt works.. i installed cm and gapps a few times new but i just dont want to work..
someone got a soultion
Just take it back to stock.
Sent from my GT-I9300 using Tapatalk 4
Greeting Devs & thanks in advance.
My t959 got bricked where it wouldn't go passed the vibrant screen, found a post called ** [GUIDE] FIX AND RESCUE YOUR VIBRICK + ODIN SUPPORT! N00b Friendly ** followed instructions on it to take it back to stock with Odin, rigth now my phone is running Android 2.1 eclair, rooted and with CWM Recovery version 2.5.1.2. im trying to flash a custom rom and when i go into recovery mode and try to do it, the progress bar at the bottom comes up and when it is at about 10% the phone reboots back to the vibrant screen and wont go passed it so i have to take the battery out put it back in and get the phone into download mode to retake it back to stock using ODIN, so i guess is safe to say that my phone gets bricked whenever i try to install a custom rom so im stuck with eclair wich blows specially after having 4.2.2
my phone got bricked the first time when i was trying to update the rom from SlimBean 4.2.2 Build 7 to Build 8 (had done the process many times and never had a problem) did the usual, put the Rom and the Gapps .rar files in the sd card and performed wipe data/ factory reset only this time i went into mounts and storage and wiped everything that was under there as well (dont know why) so when went to flash the rom it was no longer on the sd card (cause i wiped it) so rebooted my phone and it got stuck on the vibrant screen with i fixed already and my problem now is the one mentioned above
i have browsed the different forums and have tried many different methods to try to fix it for example: have brought it back to stock with Odin also with AIO Vibrant Toolbox and even tried UVKB5_Stock_Heimdall-One-Click wich is a froyo 2.2 that comes with CWM recovery with voodoo lag fix and root. even though all these methods work as far as bringing the phone back to stock i still get the same problem when trying to flash a rom, i also have installed CWM through Rom manager and also through the update.zip file i think im doing everything right and have tried multiple forums yet havent been able to find a forum about this specific issue so decided to create this thread as a last resource
this is my first post and id really appreciate any assitance and if any additional information is needed ill be happy to provide it, thanks in advance
This worked for me
elpromo01 said:
Greeting Devs & thanks in advance.
My t959 got bricked where it wouldn't go passed the vibrant screen, found a post called ** [GUIDE] FIX AND RESCUE YOUR VIBRICK + ODIN SUPPORT! N00b Friendly ** followed instructions on it to take it back to stock with Odin, rigth now my phone is running Android 2.1 eclair, rooted and with CWM Recovery version 2.5.1.2. im trying to flash a custom rom and when i go into recovery mode and try to do it, the progress bar at the bottom comes up and when it is at about 10% the phone reboots back to the vibrant screen and wont go passed it so i have to take the battery out put it back in and get the phone into download mode to retake it back to stock using ODIN, so i guess is safe to say that my phone gets bricked whenever i try to install a custom rom so im stuck with eclair wich blows specially after having 4.2.2
this is my first post and id really appreciate any assitance and if any additional information is needed ill be happy to provide it, thanks in advance
Click to expand...
Click to collapse
Mine would remove the root when I rebooted it not allowing me to install a rom also. I used the Super One Click and the root stuck. I suggest you give it a try.
Super One Click
seerenr since
Devil-Dog said:
Mine would remove the root when I rebooted it not allowing me to install a rom also. I used the Super One Click and the root stuck. I suggest you give it a try.
Super One Click
Click to expand...
Click to collapse
my problem is not really with rooting the phone, it is rooted i just cant flash roms. whenever i try to flash a rom it reboots and gets stuck on the vibrant screen (bricked) so i have to take it back to stock
thanks though
elpromo01 said:
Greeting Devs & thanks in advance.
My t959 got bricked where it wouldn't go passed the vibrant screen, found a post called ** [GUIDE] FIX AND RESCUE YOUR VIBRICK + ODIN SUPPORT! N00b Friendly ** followed instructions on it to take it back to stock with Odin, rigth now my phone is running Android 2.1 eclair, rooted and with CWM Recovery version 2.5.1.2. im trying to flash a custom rom and when i go into recovery mode and try to do it, the progress bar at the bottom comes up and when it is at about 10% the phone reboots back to the vibrant screen and wont go passed it so i have to take the battery out put it back in and get the phone into download mode to retake it back to stock using ODIN, so i guess is safe to say that my phone gets bricked whenever i try to install a custom rom so im stuck with eclair wich blows specially after having 4.2.2
my phone got bricked the first time when i was trying to update the rom from SlimBean 4.2.2 Build 7 to Build 8 (had done the process many times and never had a problem) did the usual, put the Rom and the Gapps .rar files in the sd card and performed wipe data/ factory reset only this time i went into mounts and storage and wiped everything that was under there as well (dont know why) so when went to flash the rom it was no longer on the sd card (cause i wiped it) so rebooted my phone and it got stuck on the vibrant screen with i fixed already and my problem now is the one mentioned above
i have browsed the different forums and have tried many different methods to try to fix it for example: have brought it back to stock with Odin also with AIO Vibrant Toolbox and even tried UVKB5_Stock_Heimdall-One-Click wich is a froyo 2.2 that comes with CWM recovery with voodoo lag fix and root. even though all these methods work as far as bringing the phone back to stock i still get the same problem when trying to flash a rom, i also have installed CWM through Rom manager and also through the update.zip file i think im doing everything right and have tried multiple forums yet havent been able to find a forum about this specific issue so decided to create this thread as a last resource
this is my first post and id really appreciate any assitance and if any additional information is needed ill be happy to provide it, thanks in advance
Click to expand...
Click to collapse
What version of android are the ROMs you are flashing?
are they above or below android 2.3?
and on the same note, do you know what bootloader you have?
some roms 2.3 and above require gingerbread bootloaders.
(an easy way to find out is by figuring out which button combo you have to use to get to recovery)
you might also try re-flashing recovery.
firefly6240 said:
What version of android are the ROMs you are flashing?
are they above or below android 2.3?
and on the same note, do you know what bootloader you have?
some roms 2.3 and above require gingerbread bootloaders.
(an easy way to find out is by figuring out which button combo you have to use to get to recovery)
you might also try re-flashing recovery.
Click to expand...
Click to collapse
i have re-flashed recovery multiple times i wish there was another type of recovery i could install
on another note im trying to install android 4.2.2 SlimBean and 4.3.3 and i dont know what bootloader i have nor how to check it, id appreciate it if u could show me how to check wich one i have and how to up it
thanks
firefly6240 said:
What version of android are the ROMs you are flashing?
are they above or below android 2.3?
and on the same note, do you know what bootloader you have?
some roms 2.3 and above require gingerbread bootloaders.
(an easy way to find out is by figuring out which button combo you have to use to get to recovery)
you might also try re-flashing recovery.
Click to expand...
Click to collapse
the combo i have to do for recovery is volume up and down and the power button simultaniosly
elpromo01 said:
the combo i have to do for recovery is volume up and down and the power button simultaniosly
Click to expand...
Click to collapse
Try flashing a 2.2 rom or below.
if that works you probably just need to flash GB bootloaders before flashing the 4.2 rom (See Below)
if that doesn't work I wouldn't worry about the step below until we figure out why its not working.
To flash GB bootloaders go here: http://forum.xda-developers.com/showthread.php?t=1117990
firefly6240 said:
Try flashing a 2.2 rom or below.
if that works you probably just need to flash GB bootloaders before flashing the 4.2 rom (See Below)
if that doesn't work I wouldn't worry about the step below until we figure out why its not working.
To flash GB bootloaders go here: http://forum.xda-developers.com/showthread.php?t=1117990
Click to expand...
Click to collapse
ok so i installed GB bootloader following the instructiones as shown in the forum, went ahead an tried to flash Slimbean 4.2.2 build 8 and the same thing happened my phone is stock at the boot screen only different is that instead of the vibrant screen im getting a semaphore screen (i guess is because of the gb bootloader) anyway flashed back to stock using Odin and im back where i started so it doesnt seem to be a bootloader related issue
thanks anyway
elpromo01 said:
ok so i installed GB bootloader following the instructiones as shown in the forum, went ahead an tried to flash Slimbean 4.2.2 build 8 and the same thing happened my phone is stock at the boot screen only different is that instead of the vibrant screen im getting a semaphore screen (i guess is because of the gb bootloader) anyway flashed back to stock using Odin and im back where i started so it doesnt seem to be a bootloader related issue
thanks anyway
Click to expand...
Click to collapse
Flash the rom again instead of going back to stock when it hangs. You have to flash JB roms twice most of the time when you are on stock 2.1, the first flash simply upgrades your recovery mode. Pull the battery after the first flash and boot back into recovery (should be blue now) and flash the rom again.
Sent from my SGH-T959 using Tapatalk 2
iTz KeeFy said:
Flash the rom again instead of going back to stock when it hangs. You have to flash JB roms twice most of the time when you are on stock 2.1, the first flash simply upgrades your recovery mode. Pull the battery after the first flash and boot back into recovery (should be blue now) and flash the rom again.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
i just fixed, i tried to flash CM10.1 and it crashed during the process only this time instead of getting stuck on the Vibrant screen it rebooted back into the recovery mode wich is now blue and version 6.0.2.1 intead of 2.5.1.2.
im running CM10.1 right now and so far everything looks good :laugh: only thing different now is that it say Galaxy S GT-I9000 and is the t959, doesnt really bother me as long as the phone behaves im just sayin
thanks to everyone that took their time to help, never give up on a Vibrant cause it will never give up on you :good:
elpromo01 said:
i just fixed, i tried to flash CM10.1 and it crashed during the process only this time instead of getting stuck on the Vibrant screen it rebooted back into the recovery mode wich is now blue and version 6.0.2.1 intead of 2.5.1.2.
im running CM10.1 right now and so far everything looks good :laugh: only thing different now is that it say Galaxy S GT-I9000 and is the t959, doesnt really bother me as long as the phone behaves im just sayin
thanks to everyone that took their time to help, never give up on a Vibrant cause it will never give up on you :good:
Click to expand...
Click to collapse
Glad you figured it out. Just so you you know, your phone says GT-I9000 because you flashed gingerbread bootloaders. They provide better button combinations to recovery and download modes, much easier than stock combos.
Sent from my SGH-T959 using Tapatalk 2
Good to know, thanks!!
Sent from my SGH-T959 using xda app-developers app
I was replacing a screen for my friend and the phone (sprint sph-L600) was working just fine. Then it stated there was an update, I selected ok. Since then the phone has been looping Samsung Mega and vibrating 2 times over and over. I downloaded odin and flashed 4.4.2 and still the same issue. I can not get into samsung recovery as it does the same reboot over and over. I flash it with a different recovery, and then could get into the recovery mode,once I flash the stock rom, I'm back to square one, rebooting and no recovery. Before I did a flash recovery I did notice the KNOX was 0x1, which I'm not sure why. Any help would be great or I'm out some money for trying to be nice... thanks in advance!
Anyone please!
Have you tried philz recovery?
bensey said:
Anyone please!
Click to expand...
Click to collapse
I have this phone and updated few days ago with 4.4 version. Philz recovery for meliusrlts works with it without any problem. Bro can you make a debrick img from your phone? I have bricked my phone.
IHelp, Bricked Phone SGH-L600
ashikrobi said:
I have this phone and updated few days ago with 4.4 version. Philz recovery for meliusrlts works with it without any problem. Bro can you make a debrick img from your phone? I have bricked my phone.
Click to expand...
Click to collapse
I am having the same problem, only i am stuck on the Mega Galaxy logo screen, i rooted my device ans updated the newest firmware and i cannot figure out how to get it to work. I tried everything. I also can get into the recovery but it reads there is no operating system on my phone are you sure you want to reboot, GOD what can i do am going nuts as i rely on my phone 100 percent job related purposes, please! someone HELP!!!!
Its not a hard brick dont worry
dreamgirl2011 said:
I am having the same problem, only i am stuck on the Mega Galaxy logo screen, i rooted my device ans updated the newest firmware and i cannot figure out how to get it to work. I tried everything. I also can get into the recovery but it reads there is no operating system on my phone are you sure you want to reboot, GOD what can i do am going nuts as i rely on my phone 100 percent job related purposes, please! someone HELP!!!!
Click to expand...
Click to collapse
Dont worry its not a hard brick. Try to flash the stock rom with odin. It will solve the problem.
im using cm12 archidroid 3.5.14 and decided to update to 3.5.15 version last night. but the update didnt went well, something went wrong and i got 'recursive' error, and it started to boot loops.
i tried so many solutions, i odin this and that and nothing worked. i downloaded cwm 6.0.0.47 i think, and managed to install the AD rom, but now im stuck at languange selection, i cant select anything because screen support isnt working
what do i do now?
Samsung S3 i9300
You did "odin this and that"? That's never a good idea. Just saying...
I would try to flash latest AD again but with a proper up-to-date recovery e.g. latest TWRP after making a nandroid backup.
Hawaiihemd said:
You did "odin this and that"? That's never a good idea. Just saying...
I would try to flash latest AD again but with a proper up-to-date recovery e.g. latest TWRP after making a nandroid backup.
Click to expand...
Click to collapse
thanks for the reply Hawaiihemd
i downloaded the stock firmware of i9300 and odin that .tar.md5. Now it just stuck at samsung logo
I would try to flash latest AD again but with a proper up-to-date recovery
Click to expand...
Click to collapse
how do i do that? where do i get latest uptodate recovery? at least point me to right directions thanks so much
ricvai7 said:
thanks for the reply Hawaiihemd
i downloaded the stock firmware of i9300 and odin that .tar.md5. Now it just stuck at samsung logo
how do i do that? where do i get latest uptodate recovery? at least point me to right directions thanks so much
Click to expand...
Click to collapse
Well then, if you already flashed stock rom via odin, your data is already gone. Make sure your phone is working on stock first now. Please be aware that the first boot after each rom flash might take up to 15 min or so because the cache has to be built at first boot!
You can find the link to TWRP recovery in my signature (see My Gadgets). I suggest your read the tutorials that are linked there also for more information.
thanks again, glad to hear there's still hope. i will do as you advised.
So, in order to get stock firmware flashed and running, can i use twrp-2.8.6.1-i9300.tar from your signature?
1st i odin the twrp-2.8.6.1-i9300.tar, and then reboot into download mode, and odin firmware stock?
in that order? i havent done this in a long time, i've been using AD for so long without any problem, i dont really exactly remember how. i just concern about the touch screen not functioning, i really hope no hardware failures. i never experience anything like this, even in recovery mode, the touch screen doesnt work, i had to flash entire process using up/down and power button
right now i havent done anything since the last attempt ( flashed stock rom, and stuck at samsung logo )
currently., im charging the battery, will try get it up and running after the battery is full
thanks mate
ricvai7 said:
thanks again, glad to hear there's still hope. i will do as you advised.
So, in order to get stock firmware flashed and running, can i use twrp-2.8.6.1-i9300.tar from your signature?
1st i odin the twrp-2.8.6.1-i9300.tar, and then reboot into download mode, and odin firmware stock?
in that order? i havent done this in a long time, i've been using AD for so long without any problem, i dont really exactly remember how. i just concern about the touch screen not functioning, i really hope no hardware failures. i never experience anything like this, even in recovery mode, the touch screen doesnt work, i had to flash entire process using up/down and power button
right now i havent done anything since the last attempt ( flashed stock rom, and stuck at samsung logo )
currently., im charging the battery, will try get it up and running after the battery is full
thanks mate
Click to expand...
Click to collapse
i've managed to odin stock rom. everything is ok now
the problem remain is no touch screen. how can i fix it?
FYI i sent my phone to replaced the screen 4-5 days ago , but everything was ok, no problem until i failed flashed rom it started to lose touch screen. how can i fix this?
thanks !
ricvai7 said:
i've managed to odin stock rom. everything is ok now
the problem remain is no touch screen. how can i fix it?
FYI i sent my phone to replaced the screen 4-5 days ago , but everything was ok, no problem until i failed flashed rom it started to lose touch screen. how can i fix this?
thanks !
Click to expand...
Click to collapse
i havent solved the problem with touch screen. can anybody help?