Hi,
I've totally buggered my Note 3.
The only stage I can boot into something very similar to the attached photo.
I tried installing philz_touch_6.12.8-i9500.tar.md5 using Odin but when it reboots it just hangs at the boot logo screen.
TBH, I'm probably making it worse because it did have TWRP (see link below) but it coudln't install any ROM whatsoever, it just kept rebooting to the logo screen after a few seconds.
This all began when I followed this chap to letter but obviously didn't work out as expected:
https://www.youtube.com/watch?v=-i6DsGKTsJc
Would someone please point me in the right direction on how to bring my phone back to life or let me know if you can tell it's permanently screwed.
Thanks very much and really hope (pray!) you can help.
Just to say, I have sorted it.
Used the stock ROM via ODIN3.
Case closed.
Related
I was attempting to run this lag fix on my Vibrant and now my phone does not boot past the large S, it just sits there with the center of the S glowing every few seconds, then the screen goes black. I can then click the Home key and the keys all light up but screen stays black and the lighted keys never turn off.
I can also hold volume keys and power at this point and boot to Android system recovery screen but can't do much there because either a reinstall packages or reboot causes same issue at the big S. Is there any way to replace the update.zip (for lag fix) sitting on the internal memory so I can reload stock?
Note: I got to the part of that lag fix where it tells you to choose the top option in the MCL Scripting program (6:45 in thee video), while it was in there running the phone rebooted at some point and was extremely slow booting up. I was able to get to a "power-off" prompt there and since then have been stuck at the big S ever since.
Thanks for any help.
I was able to get back to the phone running again by doing a wipe (unfortunately) but now after booted I get an error like so:
Sorry!
------------
The application Web (process com.android.browser) has stopped unexpectedly. Please try again.
dumpstate_app_201008192123_com_android_browser.log has been saved. Use *#9900# to copy out log.
How can I flash my Vibrant back to stock now? I think this is kinda hosed the way it is now. Thanks!
Odin and stock kernel is your option.
Did you make a nandroid backup before you ventured into the lag fix?
EDIT: it should not be in this section
Took me a bit of time but I figured out how to use Odin and boot the phone in download mode and flash it with the stock kernel. Thanks for your help!
mgiusto said:
Took me a bit of time but I figured out how to use Odin and boot the phone in download mode and flash it with the stock kernel. Thanks for your help!
Click to expand...
Click to collapse
can you please help a noob out and give me detailed steps on how you did this =]
if you want to learn to use odin read some of the faq threads there one in each of the galaxy s variants development forums just follow the instructions and it should work
Starting to get frustrated. When I got the Galaxy Tab 10.1 from I/O it originally had a severe back-light bleed which I described in this thread:
http://forum.xda-developers.com/showthread.php?t=1076349
Samsung Level 3 Support was quite awesome and sent out a replacement. The back-light bleed is still somewhat present, but not nearly as bad. So a few weeks have passed and ran into another major issue: it entered a infinite reboot loop.
I have only about 10 apps or so installed from the "Featured" section in the Android Market. I have never bothered rooting this, dealing with custom ROMs, or anything of that sort.
I just get white text on the display with a black background which says:
Entering upload mode...
Upload_Cause: undefined
Holding down the power button again just takes the tablet into a infinite reboot loop. I see the start up animation and the Samsung logo, then it repeats over and over.
Samsung just set up a RMA to get this re-flashed. Anyone else have this issue? Is there an easy solution to solve this without having to send it back in?
Thanks!
And I have the same issue here any help guys!!
same issue, looking for a solution
exact same issue. Any solution or suggestions?
I have the I/O tab, unrooted. I had the exact same issue. Just overnight the tablet went bonkers. The tablet would continually load the Samsung Splash screen over and over. If I tried to wipe the table, I got Entering upload mode, Upload undefined error. I sent my tab in after pulling my hair out trying to get a fix. I couldn't even work on the tablet because it would not hold a battery charge. Some process was constantly draining the battery. I personally wish thye would just give me a production tablet. I'm afraid that when I get it back, the problem will re-occur.
I have the regular retail version. I've had it for about 9 days and have used it every single day. Last night I downloaded 2 movies onto it and everything was fine. Today it would not power on one bit! I charge it over night so the battery shouldn't have drained. Anyone experience this before???
Nevermind: Fixed my problem by doing the following!
Press and hold the on button.
At the same time, keep a finger on the screen.
Keep watching and you might see a slight change of color on the screen.
Hold it down for 15 seconds or more. Be patient.
IO Boot Loop
same issue for me - working great then all of a sudden it froze, i rebooted and got stuck in boot loop
tried:
ODIN flash recovery - still boot loop
NVFLASH recovery - installed but cannot get into recovery mode -only fastboot and ODIN
FASTBOOT mode - adb not seeing device even though ODIN sees it - installed PDANet to get Android USB driver - still not seeing device
any thoughts?
sINCE THE release of touchwiz roms, a bootloader file is included as bootloader.tar.md5. Flashing this (repartition unselected in odin) gives you retail like options in boot screen with keys combo viz. recovery and odin. Try extracting and flashing the bootloader file from stock roms I uploaded.
COUNT:5 repetitions of this solution!Gladly, though one should bother to search!Or check the similar threads suggested when starting a thread.
thanks mughalgxt - where might this bootloader.tar.md5 be downloaded? To clarify did you mean by the extracting comment below that the bootloader you provided already contains this update?
also as for repetition - since i am still looking for a solution and some of those thread have the same symptoms (boot loop) but different solution methods (nvflash, odin, fastboot) - i thought it might make sense to add my description to my issue to apply additional context/clues
mughalgxt said:
sINCE THE release of touchwiz roms, a bootloader file is included as bootloader.tar.md5. Flashing this (repartition unselected in odin) gives you retail like options in boot screen with keys combo viz. recovery and odin. Try extracting and flashing the bootloader file from stock roms I uploaded.
COUNT:5 repetitions of this solution!Gladly, though one should bother to search!Or check the similar threads suggested when starting a thread.
Click to expand...
Click to collapse
I had uploaded a stock euro rom(check under arabic rom topic in development section), courtesy of samfirmware.com. You can extract the bootloader.tar.md5 file from the rom rar file. This will help you to force key into recovery as the boot options will be replaced from fastboot to recovery. Just make sure you don't select repartition while flashing with odin as that'd leave you bootloader locked!
Hope this clears up! Once in recovery, the options are endless!
lost2030 said:
I have the regular retail version. I've had it for about 9 days and have used it every single day. Last night I downloaded 2 movies onto it and everything was fine. Today it would not power on one bit! I charge it over night so the battery shouldn't have drained. Anyone experience this before???
Nevermind: Fixed my problem by doing the following!
Press and hold the on button.
At the same time, keep a finger on the screen.
Keep watching and you might see a slight change of color on the screen.
Hold it down for 15 seconds or more. Be patient.
Click to expand...
Click to collapse
WORKED like a charm!
Hello Everyone
Let me start by saying bought 2 verizon Galaxy tabs (SCH-I800 model) i got one to cm9 the other is giving me trouble. Here is what i did. This Tab was Running 2.2.3 and it was running good. I used Heimdall To put the Cubed 3 2.3.5 rooted Rom following these instuctions on this page
http://forum.xda-developers.com/showthread.php?t=1325469
Heimdall finished sucessfully then the device rebooted. When it came back up the sumsung logo appeared for a sec then something that looked like snow started on the screen (I think it is the samsung logo all garbled up). The snow continues for about 1 min then it goes to a black screen and sits there. I can boot into download mode without the garbled screen but if i power it off and plug in the charger the batter indicator shows up for a sec then the image goes garbled. I AM STUMPED!
I have tried reflashing it to the Stock rom folling these guides without success.
[Tutorial] How To Restore Verizon Galaxy Tab Back To Stock
[Guide][CDMA][Stock rom] Thanks Goes For {boodafli}
*Guide* Root CDMA VZW Galaxy Tab Using [ROM][CDMA/VZW][2.3.5]Stock+Root Vanilla*
All of the flashes with heimdall finish successfully but the same snowy screen appears on boot then goes to black screen. I would apperciate a push in the right direction of if anyone has encountered this before a way to fix this thing.
Thanks for any help!!!!!!
[Edit]
Ok Since no one has responded to me I assume that either no one knows or that no one understands the problem. Either way i have made a video showing the problem. Please watch it and see if you can help me out with this issue. Please Note that before i started flashing the roms the Tab was working with Android Ver 2.2 and the display was fine and this develpoed because i flashed it. Also the the screen doesn't get messed up in the download screen. The Download screen is perfectly ok. Can someone please lead me in the right direction or point me to someone who may be able to help me.
Here is the link to video. http://www.youtube.com/watch?v=Kyo8GNbOTLI&feature=plcp
I may have gotten the OS to work
OK here is an update to the situation:
I continued to look online and i found a Rom that was for this tablet but it is marked for US Cellular. I flashed it in using the US cellular install. When it came up it was still snowy on boot but I discoverered that if i push the Power Button twice the OS comes up. It is 2.3.5 that was flashed into it. I want to be able to use clockwork mod recovery to flash other roms into it the problem is that with the snowy boot i can't. I have provided a video demonstation of what the tablet does and the working OS below.
Video of the snowy boot to android 2.3.5
if anyone wants to see what it did originally the video is in the previous post or Here.
Can anyone point me in the right direction to get this problem fixed. To me it seems like some type of bootloader problem.
you might be right, it seems to be boot loader.
You may need a complete rom that has boot.bin and Sbl.bin so you can flash it completely with --primary-boot ./boot.bin --secondary-boot ./Sbl.bin
be careful though because the only way to brick the tab is by screwing up boot loader.
Sounds great! Anyone have any idea where i can get a complete rom or even just the bootloader files. Also since I have 2 of the same tablet can I make a boot.bin and a Sbl.bin from the other tablet. If so how would i do that. Also would i use Heimdall to flash them to the broken tablet?
I don't know how to extract.
Must be just some dd command on the right partition.
Ibdont know any cdma rom that has bootloader files.
Sent from my GT-P1000 using xda app-developers app
So I had Alliance ROM on my phone to begin with and I downloaded this http://www.alliance-rom.com/communit...able-nd7.9054/ and installed it in safestrap recovery mode. After the file was finished installing the phone turned off. (I thought it was going to restart and well that never happened, The phone doesn't even turn on. I've taken the battery out and tried to power it on, I've tried taking the SIM and SDCard out and turning it on. I've left it plugged in and charging and tried turning it on, I'v plugged it into a computer and tried it that way. Nothing that I have tried has worked. If anyone can please help me get this working I would HIGHLY APPRECIATE IT!! I use this phone for work and to keep in touch with my Daughter. Thank you ahead of time for any ideas that may or may not work.
First thing, the link you posted doesn't work. There's dots in the middle. Second, if it won't even boot to the Galaxy S5 screen before the boot animation that could be one of two things. A. It installed a custom boot loader not meant for your device that could be fixed if you could boot to download mode, which you can't. Or b. your phone is physically broken and you'd need to take it to Verizon to get fixed. Right now it's probably the second, but I have little clue as to the ROM you installed.
This has been pretty much answered for you in your other thread. You put a rom meant for note 2 on your S5 , probably not going to be fixable. But your ONLY chance is to get the phone into Download mode. Then odin a stock S5 ROM. No longer any need to panic you have brick so...At this point remain calm and move slowly so you don't make another mistake hope you get lucky.
Hello everyone,
Long time reader for time poster. I have this device that is stumping me, and I was hoping with your help I can get to the bottom of its issue.
i am not going to describe everything that I had done as that would take pages and pages, but there is one aspect that I feel might be the crux of the problem so I will start with that and see if it leads us anywhere.
Basically this device was working, sat in a drawer for a while, the battery dried up, and since it wasn't able to boot into android, it always gets stuck at the htc logo screen.
I have tried flashing it using the sd card method, with the newest corresponding zip that I could find, it started doing its thing, then at some point restarted, got stuck again, and I ended up with an unknown radio and dsp (looking at the infos in download/recovery modes)
I don't know the history of the device, but i don't believe usb debugging or oem unlocking were turned on. and obviously I can't check or modify them as I can't get into the device. and it is currently locked and S ON.
Currently, I can boot into recovery/download no problem:
- I can easily detect and interact with the phone through fastboot, but not through adb.
- clearing cache and factory resetting go through fine, no errors, but again after restarting the device it gets stuck at the htc logo.
- if I try to flash through the SD card, it starts normally, then restarts and gets stuck at the htc logo.
- if I try to flash anything through fastboot, I get an error telling me the device is still locked, which it is.
- if I try unlocking using fastboot (following the official htc method), once again it starts normally, but then restarts and gets stuck at the htc logo again.
Correct me if I am wrong, but it feels to me like this is a software issue, that for the hell of me I can't seem to be able to get around.
I tried to keep the post simple, so if any additional information is needed, or tests you'd want me to run please don't hesitate to ask.
Thank you for your help, much appreciated!
Hello again, just a little bump. As I am stuck and any ideas would help.