Database Users

Snowy Screen on Boot

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

[Q]stuck on google logo

Hi my nexus 4 is stuck on the google logo screen ,i noticed the nexus logo appear when i wasnt using the phone ,then the google logo appeared and i thought it was rebooting however it then wouldnt do anything else, i can get to the recovery screen but recovery mode and start just instantly bring up the google logo again
i did once see the android screen with the red triangle and no command written though i have no idea how i came to that screen as i was just playing with it
i have not installed or attempted to flash anything on this phone ,its exactly as i recieved it
when ive left it on the google logo for any length of time it does appear to heat up a bit
forgive me for being a complete noob to this sort of thing but some of the other threads ive read may as well of been written in elvish
any help gratefully recieved

nazarineo said:
Hi my nexus 4 is stuck on the google logo screen ,i noticed the nexus logo appear when i wasnt using the phone ,then the google logo appeared and i thought it was rebooting however it then wouldnt do anything else, i can get to the recovery screen but recovery mode and start just instantly bring up the google logo again
i did once see the android screen with the red triangle and no command written though i have no idea how i came to that screen as i was just playing with it
i have not installed or attempted to flash anything on this phone ,its exactly as i recieved it
when ive left it on the google logo for any length of time it does appear to heat up a bit
forgive me for being a complete noob to this sort of thing but some of the other threads ive read may as well of been written in elvish
any help gratefully recieved
Click to expand...
Click to collapse
Same thing here. I flashed a new CM. Did a full wipe including cache then flashed a new GAPPS, and now I'm stuck at the Google screen. I can get into fast boot, recovery etc but cannot get my phone to boot. Any ideas?

1. wipe factory
2. wipe dalvik
3. wipe cache
4. flash cm then gapps then kernel

Thanks zephiK. Problem is I don't have a ROM on my sdcard mount. How can I copy a ROM to my phone without getting into android? Thanks for any help!

If you can get into recovery (CWM) then you can use ADB to push the file. Look through some of the PINNED threads for the commands. Very helpful info.
I found that my data partition was not able to MOUNT once and nothing I could do via ADB shell would change to it to R/W so I just locked and unlocked my bootloader and all was well again.

you can either use fastboot to push the files to your phone or flash stock. if you dont know how to use fastboot try wugs toolkit

nexus 4 stuck at loading screen

Hey there,
I'm stuck with the nexus 4 at the "X" loading screen. I've been trying all things I can to fix it: flash an older OS (back to 4.2.2), and just now I did the guide described here to so call "unbrick" the phone.
During the last guide everything went succesfully - however I still am stuck at the "X". There are two remarkable things though:
-During the guide you flash a developer image (that you can't use as you don't have the password)
-Just when the batteries drop dead (and it shows "powering off") I actually see the correct screen (welcome, first time settings etc).
How can I fix it? LG doesn't want to do anything as it is now "rooted" apparently..

s7 Edge problems after flashing

First and foremost, I have searched but cannot find someone who has experienced a similar issue as myself.
I have followed the instructions on stechguide (cannot link as I am too new) to flash TWRP onto my s7 edge (Exynos).
However, after booting into recovery, I get a blue screen with an android spinning around saying "installing system update"
and then shortly after that I get a dead android dreaming of a big "!" warning symbol.
It then loads Android Recovery:
MMB29K.G935FXXU1APF2
Samsung/hero2ltexx/hero2lte
6.0.1
giving me the usual samsung recovery options. I am too scared to try anything else (brand new phone) so I just opt to reboot the phone..
The phone still seems to boot fine, however the fact that TWRP is not working and the warning symbol when trying to access recovery is bothering me. Also, when the phone starts, it seems to default to showing me my samsung registration information. Strange
Does anyone know why this might be? Flahsed twrp-3.0.2-2 img tar file, using odin 3.10.7 with these USB driers SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe (downloaded through the Verizon link)
any help appreciated
thanks for your time.

I have now resolved my problem. I needed to hold the recovery buttons immediately after flashing. Mods please delete this thread.

Soft Bricked Device - I've tried every suggestion on every thread

So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance!

Looks like you are trying hard to find a solution. I think it may be helpful if you try to manually install the o/s rather that using Wugfresh and report back any errors. See
https://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/ At step 11 I would flash the individual image files and also follow the instructions re erasing and flashing userdata.
AFAIK you will not see an Android device when using Fastboot - Android hasn't loaded at this stage.

Thanks peterk-1. Unfortunately, this does not work. I followed the steps, with the exception of the radio file as my Nexus 10 is wi-fi only. It goes through the stock image update perfectly fine and reboots itself. At that point, it's back to the moving android at the 'erasing' screen.
One thing to note with the link you provided; no where does it indicate flashing a recovery, stock or custom. Now, I've tried flashing stock, TWRP and CWM and none seem to work. TWRP comes closest with the black/blue splash screen, but will not open further.
Any other suggestions would be appreciated.

You did go to the posted link? I quote:
Step 8: We now want to wipe the device. Use the following commands in order:
........
fastboot erase recovery
............
Step 11: We will now flash the system, boot, and recovery ..........................................
fastboot flash recovery recovery.img

Unfortunately, same result...