Stuck on Welcome screen after Odin stock Flash - T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting

So my N910T is stuck on the Welcome screen after flashing back to stock. I flashed C0G2. I'm thinking maybe it was the update or something, but it's like 1.6gigs so I figured it's the full rom.
The reason I flashed back to stock in the first place is because I was messing around, trying different roms, when I ran across one that made my screen seem semi-unresponsive. Nothing I touched would respond. I would touch the screen and it would like up to the touch, but nothing else. If I sit there and play with it long enough I'll accidentally get a button to respond. When I pressed the power button I get the "power off/restart options, but when I press one the phone doesn't power down.
I'm downloading the NIH now (which is 4.4.4) and try flashing it. I don't know what else to do.

Wipe your data partition as well as caches. You can't downgrade and expect it to work like that.

Related

Bricked HD?

I recently synced my HD after having flashed the EVO Grid 1.8 ROM.
Since it took over half an hour I disconnected the phone from the computer during the sync process. Now the screen freezes as soon as the smart mobility screen shows up. I soft reset' the phone as well as I tried hard resets. Still the phone doesn't go beyond the smart mobility screen and freezes.Is there another option to get the phone back apart from resetting it? Or is it completely bricked now. I've always successfully flashed the roms, so it can't be connected to a wrong ROM flash.Thank you for a feedback.
What you can try is place an ROM on your memory card (BLACIMG.nbn) and flash it. (shut down phone, hold vol down and power up).
Maybe this will do the trick. Good luck
Can you still get the phone into bootloader mode (tricolor screen)? It's likely you can - then just re-flash the rom (although to be safe I'd download it again).
Did you follow this guide to initally flash rom? If not, I'd suggest you do. As pointed out above, if you can still get into bootloader your device is not bricked. Just follow guide and reflash rom
just do like "jontelfer" said go to 'bootloader' for getting 'Tricolor' by pressing 'Volume Down' and 'Power' 1 time. Then u can see 'tricolor' and re-flash what ever rom you want.
I had try 'Xannytech ROM Grid Leo 2.5 (Internal Rel. 4.2.5.202)' and found the same as your problem 2 times already.
Now I'd change to test others.
I would be tempted to flash it back to original SPL and ROM and then start again from scratch. This happened to me a few months back, I couldnt flash any cooked ROMS at all until I reverted back to stock and started again.
Yeah and do not forget to hard reset after flashing. It can sound useless but it really helped me when I got some problems with some roms...
- Bya -
Thanks everyone. I flashed to a different ROM and it's working again now.
It's tougher than I thought to find an innovative, graphically sophisticated and most of all stable ROM.
good to hear had this ones before and gladly figured out how to go back and flashed it again with a stable rom!!

[Q] whoops. i have nothing

ok so im new to rooting and looking back i shouldnt of touched it. but hey too late i already did but now im in deep crap. Apparently i didnt back anything up or save anything about back up in the right spot. my g1 has nothing in it. it wont boot. it goes right to the clockworkmod recovery screen. tried loading roms, no dice, wont work. tried several times. i did manage to install a different radio somehow. when i hold the camera button and start phone it says no image file. i tried flashing different roms all ended the same way. some verification error at the sam e line. im at the point where i just want my phone back but am willing to keep tryin. im just looking for the correct files to use. any and all help is appreciated. any other question just ask.
Put dream.nbh on your sd card in the root, hold camera and power and go from there.
That will put stock 1.6 back on your phone and fix your radio problem.
thanks for such a fast response but its not doing anyting. i loades the file pressed correct buttons and everything but its not doing anyting. just stayin at the screen dreaimg.nbh-
bootloader-
recovery-
boot-
splash-
system-
userdata-
radio-
press power button to start update
press action button to cancel update.
i pressed power and nothing happened
awesome. phones back but on 1.0. booo. guess its better than what i had. ok so now how i get this thing to run 2.2. haha. is it possible.
Do the rooting process again and follow all instructions.

[q] need help! Black screen on my verizon galaxy tab 7

I tried a flash and think i messed my tab...now its just a black screen with a faint light in the background like its on but its no images.......my battery icon pops up then distorts away and thats it ....can get into download mode but not recovery.....tried holding all 3 buttons got this lil android dude in the corner with a sign sayin something about power reset but cant select nothing......help me please......
Put it in d/l mode and flash one of the stock roms with Heimdall.
D
i tried a stock flash with heimdall it flashed successfully but i still get the SAMSUNG logo that flashes and go away,buttons light up at the bottom,can go in download mode but not reboot mode,phone stay on with a faint light ,so i assume that its on somehow.....help
Did you follow this exactly?
http://forum.xda-developers.com/showthread.php?t=967175
One thing I missed here before was to wipe data and cache. Otherwise I go into boot loop.
how to get recovery mode
i cant wipe nothing because i cant get to recovery,just download mode
done it step by step
i followed evrything it flashed successfully but when it rebooted i turned off.and tried recovery but nothing......
chubbyflood said:
i followed evrything it flashed successfully but when it rebooted i turned off.and tried recovery but nothing......
Click to expand...
Click to collapse
Use UnBrickable Mod
http://forum.xda-developers.com/showthread.php?t=1341753
Although you get a black screen on boot, it might still be working....
Chubbyflood,
If you are in the same situation as I am then the tab is still working, you are just getting black screen on boot up. It played tricks on me for ages when I was first rooting by tablet; but it turned out it is just the boot up screen that isn't showing.
This is my situation:
-Press and hold Power button to turn on.
-I see the Galaxy Tab / Samsung initial boot image for about 1 second, and also hear the "boot chime"
-Then the screen goes completely blank (but you can tell it is still on with a little light showing.
-The four "hard button" lights will light up briefly a couple times
-Wait approximately 30 seconds to a minute (to be safe and give the tablet time to boot up - it is actually booting up)
-Tab the Power button once, to turn the tablet off (now the screen is clearly off)
-Tab the Power button again, and the tablet will be up and running as normal.
I am guessing the boot animation / images are failing in some way, but the tablet is booting up as normal.
I've just learned to live with it, because I haven't had a chance to figure out what's going on, but it honestly took me a good hour or so, and a few (unnecessary) flashes, before I realized the thing was up and running fine, it just need to have the button pressed on and off.
One final thing to mention; don't have the tablet plugged into anything. I seem to remember leaving it plugged into the PC didn't help (I think).
Hope that makes sense.
Cheers
Ed.
Has your situation been resolved?
I am in the same boat. What I have done to temporarily fix this was to Flash a ROM that uses Hemdall and it will boot as flukebu stated but only with the Galaxy Cubed ROM.
I cannot get the factory files to boot as you have stated.
I have continually tried to return to stock using the files provided on this forum and all "unbrick" posts.
While flashing the stock images everything completes and works well. The device reboots and the Samsung Splash screen appears. Once it appears it disappears and scrambles the screen. I believe it then goes into a bootloop which easily enough I could access factory recovery to correct but when I do attempt to access factory recovery the screen is as posted above (black but illuminated).
Once I flashed Galaxy Cubed ROM and it booted I hit the power button and the locksreen appeared. I can tell you I was excited but there are some issues with that ROM I have not tried to correct yet because my main goal is to return to stock.
Even with this ROM working correctly I have attempted to access CWM once installed to complete a Data Wipe and that does not show up either.
I would really like to find a solution to this I want to return to stock and not have this custom ROM running.
Juiced_RL said:
Has your situation been resolved?
I am in the same boat. What I have done to temporarily fix this was to Flash a ROM that uses Hemdall and it will boot as flukebu stated but only with the Galaxy Cubed ROM.
I cannot get the factory files to boot as you have stated.
I have continually tried to return to stock using the files provided on this forum and all "unbrick" posts.
While flashing the stock images everything completes and works well. The device reboots and the Samsung Splash screen appears. Once it appears it disappears and scrambles the screen. I believe it then goes into a bootloop which easily enough I could access factory recovery to correct but when I do attempt to access factory recovery the screen is as posted above (black but illuminated).
Once I flashed Galaxy Cubed ROM and it booted I hit the power button and the locksreen appeared. I can tell you I was excited but there are some issues with that ROM I have not tried to correct yet because my main goal is to return to stock.
Even with this ROM working correctly I have attempted to access CWM once installed to complete a Data Wipe and that does not show up either.
I would really like to find a solution to this I want to return to stock and not have this custom ROM running.
Click to expand...
Click to collapse
Have you found a resolution to this? Mine tab is doing the exact same thing as yours after the cubed rom.

[Q] Custom Rom -> Tried to put in Stock. Now Soft Bricked [FIXED!]

I'm completely stumped on this. I'm new to Custom Roms.
So a long time (a little over year aprox) I bought an GT-N7000 from an at-the-time friend (no longer friends)
He factory reset and installed a custom rom (Paranoid Android) on it. (Such a nice gesture..)
Now, speed forth Christmas last year, I bought a Galaxy Note 3 for myself, and I then sold off the N7000 to my older brother.
Now my brother comes to me and tells me that his phone is acting weird.
I take a look and notice that the phone has apparently partitioned itself into several drives, making the phone run incredibly slow and he keeps getting an annotation going "There's way too little space left!"
Now, as I mentioned I'm new to custom roms and that kind of stuff, but my initial "brilliant" idea was to simply factory reset it, and install the Stock Rom on it.
I grabbed a Stock rom from Sammobile that had a country that at least was english in nature (UK) I unfortunately live in Denmark, and so therefor it was impossible to find a Stock rom that fits it.
I grabbed it, loaded it onto ODIN3 and went into Recovery Download Mode. And I started installing it. Everything went smoothly.
Then when the phone restarted it started boot looping.
I looked and searched everywhere for fixes. Problem was, looking at the first few fixes I've seen include links to .PIT files that are either dated or ancient in nature.
androidayos.com and android.gs both had a fix, but their links was either out dated or not helpful for my specific case.
And so I beseech thee oh mighty XDA Developers.
Have you a solution/help that might be what I need.
I've read that I should go into a recovery mode that allows me to look at the files. (Read that I could do so by holding the Home Button + Power button when it turned on. But such a function didn't seem to work on the N7000.)
I've also tried looking at installing Paranoid Android again, but that requires access into the Recovery Mode. Which I, again, do not have.
PIT files are dated because they never change. They have been the same since device manufacturing date.
So did you reset before odin install? Recovery mode is by pressing the power + vol up + home together.
nokiamodeln91 said:
PIT files are dated because they never change. They have been the same since device manufacturing date.
So did you reset before odin install? Recovery mode is by pressing the power + vol up + home together.
Click to expand...
Click to collapse
Well, I had to flash in phillz to actually get a recovery mode to work.
But I managed to do just that, and then whipe the caches and I could then get the stock rom flashed onto it.
Which then got the phone to work properly.
No failures to report yet.
So for the moment a full-on success story!

Blu R1 HD Soft Brick

I have a Blu R1 HD that I have been on again off again fiddling with for a few months that is soft bricked. It will turn on but it will hang on the second "Bold like us" splash screen after the animation ends. It had no recovery installed to it prior to the bricking, I have attempted flashing a stock rom to it with SPFT but It gets interrupted less then 3 seconds in. From my reading It seems like I have the 6.6 preloader that stopped spft from working.
Is there anything that could be done with this to get it working once again?
kamikazisolly said:
I have a Blu R1 HD that I have been on again off again fiddling with for a few months that is soft bricked. It will turn on but it will hang on the second "Bold like us" splash screen after the animation ends. It had no recovery installed to it prior to the bricking, I have attempted flashing a stock rom to it with SPFT but It gets interrupted less then 3 seconds in. From my reading It seems like I have the 6.6 preloader that stopped spft from working.
Is there anything that could be done with this to get it working once again?
Click to expand...
Click to collapse
Depends on few things.
Do you know what was last thing done before this brick?
Have you tried holding volume up when powering on, to enter recovery(stock, i know you mentioned no custom recovery installed)?
It goes to and past the animation , so i don't think it is a secure boot type of failure. But maybe a bad data problem. See above statement about recovery.
mrmazak said:
Depends on few things.
Do you know what was last thing done before this brick?
Have you tried holding volume up when powering on, to enter recovery(stock, i know you mentioned no custom recovery installed)?
It goes to and past the animation , so i don't think it is a secure boot type of failure. But maybe a bad data problem. See above statement about recovery.
Click to expand...
Click to collapse
I have gone into the stock recovery menu, And i have attempted factory data reset, clearing the cache, and a root integrity check. The integrity check says one item fails the check and that is "/system/lib/libLLVM.so"
The last thing that I recall happening is that I had a pop up saying that an app had stopped working, But it reappeared immediately after closing it again several times. I thought rebooting it would stop whatever was happening, but it never came back to the OS.
The device has a small crack on the bottom right hand side of the screen that happened when it fell from my pocket on top of a ladder. A family member who also works with electronics as a hobby thinks that may have something to do with it but the phone worked for weeks after the break happened.
kamikazisolly said:
I have gone into the stock recovery menu, And i have attempted factory data reset, clearing the cache, and a root integrity check. The integrity check says one item fails the check and that is "/system/lib/libLLVM.so"
The last thing that I recall happening is that I had a pop up saying that an app had stopped working, But it reappeared immediately after closing it again several times. I thought rebooting it would stop whatever was happening, but it never came back to the OS.
The device has a small crack on the bottom right hand side of the screen that happened when it fell from my pocket on top of a ladder. A family member who also works with electronics as a hobby thinks that may have something to do with it but the phone worked for weeks after the break happened.
Click to expand...
Click to collapse
I do not know if there will be any way forward with this.
As you are not bootloader unlocked, sp flash refuses to connect, and only thing that can be done on stock is "factory reset" did not help, you might be done , other that see if can send to Blu.
mrmazak said:
I do not know if there will be any way forward with this.
As you are not bootloader unlocked, sp flash refuses to connect, and only thing that can be done on stock is "factory reset" did not help, you might be done , other that see if can send to Blu.
Click to expand...
Click to collapse
Sending to blu isnt an option. Out of waranty period, And I also opened it to make sure there was nothing obviously physically wrong.
I also tried using the dirty cow tool, But i cant seem to see the device in ADB. Fast boot however, can see it.
Update over ADB/SD in the stock recovery wouldn't lead me anywhere would they?

Categories

Resources