Last night I softbricked installing a rom. The device was being very weird and would not boot correctly. The device started showing the big GALAXY S4 splash screen instead of the usuall plain SAMSUNG sometimes says custom unlock sometimes not depending on the rom/kernal being used. Now even with Kernals that used to say SAMSUNG custom all it says is the big only GALAXY S4 splash screen. The device seems to take alot longer to get past this screen as well. Any suggestions on this??
Recovery would flash roms and device would boot once but would not boot after reset. SO F-it just Odin back to stock, root, recovery, done.
everything is working now except I still have the GALAXY S4 splash scren instead of the SAMSUNG and takes forever to boot/load past splash screen.
Is this stored in the kernal? Ive tired different kernals and all have stayed the same. I have completly ODIN back to stock wiped any and everything on this device.
QUESTION Summary::: Whats up with this splash screen VS the other one, why cant i get it to go back to the way it was before even after ODIN stock img, and why does it take longer to load and 1/2 the time not load at all.
Is there a BIOS that is not wiped... I think I broke it.
EDIT: Just sat on the SAMSUNG GALAXY S4 for 20 minutes before starting after fresh rom install... what a pain.
mrlaigle said:
Last night I softbricked installing a rom. The device was being very weird and would not boot correctly. The device started showing the big GALAXY S4 splash screen instead of the usuall plain SAMSUNG sometimes says custom unlock sometimes not depending on the rom/kernal being used. Now even with Kernals that used to say SAMSUNG custom all it says is the big only GALAXY S4 splash screen. The device seems to take alot longer to get past this screen as well. Any suggestions on this??
Recovery would flash roms and device would boot once but would not boot after reset. SO F-it just Odin back to stock, root, recovery, done.
everything is working now except I still have the GALAXY S4 splash scren instead of the SAMSUNG and takes forever to boot/load past splash screen.
Is this stored in the kernal? Ive tired different kernals and all have stayed the same. I have completly ODIN back to stock wiped any and everything on this device.
QUESTION Summary::: Whats up with this splash screen VS the other one, why cant i get it to go back to the way it was before even after ODIN stock img, and why does it take longer to load and 1/2 the time not load at all.
Is there a BIOS that is not wiped... I think I broke it.
EDIT: Just sat on the SAMSUNG GALAXY S4 for 20 minutes before starting after fresh rom install... what a pain.
Click to expand...
Click to collapse
yes the boot.img is held in the kernel....flash back to stock and reroot your device dont take any chances...hopefully you have some backups on an external sd card....this happened to me as well and i could only get to download mode so i flashed back to stock and rerooted my device everything is peachy....dont dont dont take any chances with this phone the security measures in this phone are insane and if you keep messing around with having the device "sometimes boot with custom samsung screen and sometimes not" there is something wrong with the partition....youre best bet is to flash stock and reroot....if you have a backup on an external sd card then youre set otherwise start over or you will have a $700 paper weight....let me know if you have any questions reverting back to stock or anything else good luck dude
Yeah I restored started from Odin stock last night. I thought that would take out anything that I flashed that caused the issue. But it didn't fix it.
I odin'ed back installed root recovery and still having issues where it will not boot after 2 or 3 resets. Hangs on thats galaxy s4 splash screen for more than 30 and never boots.
I would think that when it was odin'ed it would have over written the boot IMG and any thing else it might be but its not.
Sent from my SCH-I545 using Tapatalk 2
mrlaigle said:
Yeah I restored started from Odin stock last night. I thought that would take out anything that I flashed that caused the issue. But it didn't fix it.
I odin'ed back installed root recovery and still having issues where it will not boot after 2 or 3 resets. Hangs on thats galaxy s4 splash screen for more than 30 and never boots.
I would think that when it was odin'ed it would have over written the boot IMG and any thing else it might be but its not.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
when you did odin back to stock did you do a factory reset...NOT FROM RECOVERY....from settings>>backup and restore>>factory data reset? ......theres a couple of things to look for here....Odin back to stock and boot in the STOCK recovery....try wiping the cache and dalvik partitions...if they fail then the partitions are corrupted....boot normally and go to settings>>backup and restore>>factory data reset....try that...if that doesnt work then try a factory reset from the stock recovery...if all of that STILL doesnt work then the partitions are corrupted I would ask for a replacement device
Related
I got myself a bricked Vibrant from someone and trying to fix it.
I'm guessing the dude tried to flash captivate stuff on it, because the boot image is AT&T.
Anyway, I was able to odin back to stock 2.1, which seemed to make the power button work again because it would start up and show the AT&T logo but that's it.
Then I tried odin'ing a vibrant bootloader, which got me to replace the AT&T logo with a green andy logo, but same thing, stuck.
So I tried reflashing 2.1 with odin again. Now the boot logo is back to the stock i9000 > Vibrant, but then it stops here. I can't seem to be able to enter the 2e(or 3e?) stock recovery.
Any idea on what else I can try flashing to it?
Update: I tried flashing the froyo bootloader, which did get me to the stock recovery, but again - i can't seem to get this phone past this stage, doesn't boot into the OS.
wonshikee said:
I got myself a bricked Vibrant from someone and trying to fix it.
I'm guessing the dude tried to flash captivate stuff on it, because the boot image is AT&T.
Anyway, I was able to odin back to stock 2.1, which seemed to make the power button work again because it would start up and show the AT&T logo but that's it.
Then I tried odin'ing a vibrant bootloader, which got me to replace the AT&T logo with a green andy logo, but same thing, stuck.
So I tried reflashing 2.1 with odin again. Now the boot logo is back to the stock i9000 > Vibrant, but then it stops here. I can't seem to be able to enter the 2e(or 3e?) stock recovery.
Any idea on what else I can try flashing to it?
Update: I tried flashing the froyo bootloader, which did get me to the stock recovery, but again - i can't seem to get this phone past this stage, doesn't boot into the OS.
Click to expand...
Click to collapse
So what is your desired ROM after flash?
I suggest that you should flash it to LidDroid with Vibrant bootloader. From that, you can upload the phone to 2.3, 3.0 or ICS 4.0 ROM.
On mobile now so I cannot giive you the download links for needed files. If you need them, just post a reply in the thread.
Thanks, I tried LidDroid
http://forum.xda-developers.com/showthread.php?t=1058802
And flashed Froyo and GB bootloaders, nothing is working. It just shows boot screen then still shuts down.
Update: Well I'm not sure what the issue is, I was able to get it to boot to the lock screen once, but then it shut down right after. Now I can only get it back to boot image before shutting down.
The thing I noticed is that the phone gets hot really fast, so maybe it's drawing too much power somewhere and its shutting down as a protection. Also the stock batteries don't seem to work for it, just this particular battery that it came with, which the contacts on the battery are flush with the edge of the battery instead of indented like the stock ones.
What you should do is take out your sim card and external sd card if you have one, use odin to flash back to stock rom (either 2.1 or 2.2), wait for it to load up as it might take a few minutes after you see the Vibrant logo (just be patient). If you get this far and you see the operating system, flash clockwork recovery on it.
If you can get this far, let us know then we'll talk about custom roms. The main purpose now is to get it running stock, we can worry about the custom stuff later.
Here's a couple of links to help:
http://forum.xda-developers.com/showthread.php?t=848737 -- try this one first!
http://forum.xda-developers.com/showthread.php?t=954509
So I updated to the newest software MI5. Went from that and did the root which was sucessfully. I had put on OUDHS Touch CWM-based Recovery thru ODIN which was sucessful as well. After doing all of that, I downloaded Josh Beach's Jellybomb test rom. The steps I did was booted into recovery which is the one above, factory data reset, wiped cache, and wiped dalvik, then flashed the zip. The zip looked to flash ok but when i went to reboot, it just keeps getting stuck at the samsung galaxy note 3 screen, then it will reboot then go to the same screen. Did I do something incorrect? This happened to me on this ROM and the stock MI5 ROM rooted.
Might want to read through this thread...
http://forum.xda-developers.com/showthread.php?t=2473036
Process system isn't responding
Sent from my Note 3 on Android
runner77 said:
Might want to read through this thread...
http://forum.xda-developers.com/showthread.php?t=2473036
Process system isn't responding
Sent from my Note 3 on Android
Click to expand...
Click to collapse
so it sounds like i cant flash any custom roms right now? Just odin back to stock and root it and leave it at that?
this probably wont help for this particular problem, or maybe it will.. but for anyone else getting a bootloop..
i just now had a bootloop experience that i got out of.. and here's how it started - i have not rooted my note 3 (i have rooted my galaxy gear though, but i don't think that would affect the note 3).. anyway, i use the nova launcher as my main launcher.. and just before i got stuck in a loop, i had been playing with a new launcher called Themer... i just started it without setting it as default.. then i went back to my main launcher and i noticed that almost all ram was used up and i thought i might as well do a restart as it has been a while... and then it just would not start.. i got to the lock screen image, and then it would restart again and again, with no sound for the animated logo.... it eventually booted up ok, but i have no idea how i got it to work... however, i held down the power button for a while longer and it would "force" a new restart and basically abort the one already in progress, and if i did that, the boot up sound would come back... i continued doing that a couple of items and then it finally worked.
use twrp or phones as of right now dont like cwm recovery...found this out the hard way
odin back to stock rom non root wipe phone using default recovery odin back to stock again root your phone use twrp to flash whatever rom u want
lunchboxVA said:
use twrp or phones as of right now dont like cwm recovery...found this out the hard way
odin back to stock rom non root wipe phone using default recovery odin back to stock again root your phone use twrp to flash whatever rom u want
Click to expand...
Click to collapse
And when flashing make sure to wipe dalvik/caché several times for good measure.
Sent from my SM-N900P using Tapatalk
checking in to add that i found a new solution to my own problem here.... it "magically" started the last time just by me keeping on rebooting.. but that's not really a good solution and i don't think it lasts
and for me it didn't... as today i did a new restart, and it got the same stuck in a loop again, however, i followed the first mentioned workaround in this link here and it worked perfectly.. it was really that simple in my case it seems, i have done several restarts now and the bootloop is gone!...
oops, seems i cant post any links for not having enough posts yet...
i'll just add the steps mentioned instead
1 . Remove the battery and the SD card.
2. Put the battery back in and turn on the device.
3. Try Menu > Settings > Wi-Fi > Menu > Advanced and uncheck Always allow scanning.
4. Now you should be able to turn the device off and reinsert the SD card.
5. Boot it up and your problem might be gone
i have no idea how it works though as i personally don't understand the connection between then external sd card and the setting you turn off in the wifi advanced options..
cheers!
I was running a custom firmware before i went to go restore it back to stock (going to exchange it for credit at a store). I made sure everything important i needed was backed up, then i booted it to Download mode like i would to flash it back to stock with Odin, everything worked fine. It finished and after it rebooted, it just started flashing the samsung galaxy note 2 white text for a quarter of a second then shuts off and just does that until i take the battery out. I tried going into recovery mode but it doesn't. I can get to download mode and try reflashing the firmware but it fails everytime.
What can i do to fix it? In my 5 years of using custom ROMs iv'e never had this issue. is my phone bricked?
ryanskeltis said:
I was running a custom firmware before i went to go restore it back to stock (going to exchange it for credit at a store). I made sure everything important i needed was backed up, then i booted it to Download mode like i would to flash it back to stock with Odin, everything worked fine. It finished and after it rebooted, it just started flashing the samsung galaxy note 2 white text for a quarter of a second then shuts off and just does that until i take the battery out. I tried going into recovery mode but it doesn't. I can get to download mode and try reflashing the firmware but it fails everytime.
What can i do to fix it? In my 5 years of using custom ROMs iv'e never had this issue. is my phone bricked?
Click to expand...
Click to collapse
In the stock recovery do a full wipe as well. The wipe is more comprehensive than the custom recoveries. Perhaps that will help with the booting.
Which version did you try flashing? Mj9? More recent?
ryanskeltis said:
I was running a custom firmware before i went to go restore it back to stock (going to exchange it for credit at a store). I made sure everything important i needed was backed up, then i booted it to Download mode like i would to flash it back to stock with Odin, everything worked fine. It finished and after it rebooted, it just started flashing the samsung galaxy note 2 white text for a quarter of a second then shuts off and just does that until i take the battery out. I tried going into recovery mode but it doesn't. I can get to download mode and try reflashing the firmware but it fails everytime.
What can i do to fix it? In my 5 years of using custom ROMs iv'e never had this issue. is my phone bricked?
Click to expand...
Click to collapse
I understand you are probably panicking a bit over the trouble you have gotten yourself into with your Note, but I think you've been around long enough to know where to start this sort of topic. If you posted in the correct sub-forum, then you'd get better results. Right? :good:
Anyway, I wish you the best of luck fixing your phone.
I was running a custom firmware before i went to go restore it back to stock (going to exchange it for credit at a store). I made sure everything important i needed was backed up, then i booted it to Download mode like i would to flash it back to stock with Odin, everything worked fine. It finished and after it rebooted, it just started flashing the samsung galaxy note 2 white text for a quarter of a second then shuts off and just does that until i take the battery out. I tried going into recovery mode but it doesn't. I can get to download mode and try reflashing the firmware but it fails everytime.
What can i do to fix it? In my 5 years of using custom ROMs iv'e never had this issue. is my phone bricked?
ryanskeltis said:
I was running a custom firmware before i went to go restore it back to stock (going to exchange it for credit at a store). I made sure everything important i needed was backed up, then i booted it to Download mode like i would to flash it back to stock with Odin, everything worked fine. It finished and after it rebooted, it just started flashing the samsung galaxy note 2 white text for a quarter of a second then shuts off and just does that until i take the battery out. I tried going into recovery mode but it doesn't. I can get to download mode and try reflashing the firmware but it fails everytime.
What can i do to fix it? In my 5 years of using custom ROMs iv'e never had this issue. is my phone bricked?
Click to expand...
Click to collapse
What image did you flash in Odin? Also, when you flashed it did you use the pit file with it?
I have tried a few different stock ROMs and each time I get a pass in Odin the phone reboots I get the splash screen then it just hangs at the glowing SAMSUNG screen. Not sure what I am missing. I was attempting to remove root. I loaded a the same stock ROm last night with success everything was fine then came a OTA update and it went through several updating android scfreens with several reboots when It was done it was stuck at this same screen. I thought I could just start over and ignore the OTA but I cant get past this screen? Please help.
CZuber said:
I have tried a few different stock ROMs and each time I get a pass in Odin the phone reboots I get the splash screen then it just hangs at the glowing SAMSUNG screen. Not sure what I am missing. I was attempting to remove root. I loaded a the same stock ROm last night with success everything was fine then came a OTA update and it went through several updating android scfreens with several reboots when It was done it was stuck at this same screen. I thought I could just start over and ignore the OTA but I cant get past this screen? Please help.
Click to expand...
Click to collapse
You need to boot into stock recovery and perform a factory reset once Odin passes.
Sent from my SM-N910P using Tapatalk 2
Thanks. That did it. Man I have re installed several ROMS. a 1000X Thanks