Database Info

Samsung vibrant help needed.

I flashed back to stock 2.1 on my samsung vibrant.
the phone boots up fine at first, then all of a sudden i get a wierd screen and the phone reboots automatically. i dont know what the problem is. can anyone please help me with this problem.
the phone is continuously rebooting for the past half and hour. and i have no idea what to do now.
PLEASE HELP ME WITH THIS.
im posting a photo of the "wierd" screen below. the quality is crappy, but i cant help it.

Were you coming from a GB rom? Be sure your not mixing bootloaders...Not sure what that is but if you flash just the stock kernel in ODIN, with the phone off (pull the battery)and using the button combo try and get into DOWNLOAD mode. you might recover it....or flash the Bali kernel and then try going back to stock again.

erad1 said:
Were you coming from a GB rom? Be sure your not mixing bootloaders...Not sure what that is but if you flash just the stock kernel in ODIN, with the phone off (pull the battery)and using the button combo try and get into DOWNLOAD mode. you might recover it....or flash the Bali kernel and then try going back to stock again.
Click to expand...
Click to collapse
yes i did try flashing a 2.3 ROM,but it didnt work properly, so i tried flashing the stock 2.1 again using ODIN...it got installed, but later all these things started happening.
i even flashed the 512 PIT file that came along with the stock 2.1, but still no use.
can u please post the link to the kernel you are talking about and also how should i flash the kernel?
thanks for your reply.

hey the problem is solved. i installed eugene's 2.2 leaked build and my phone is back to normal now...!!!!
thanks for all your help. i really appreciate it...!!!

Glad to hear you got it...just be careful to know which bootloaders you are on, GB or FROYO... unless you have alot of problems with a ROM its not really necessary to ever flash back to stock...I flash rom to rom without any issue as long as you:
1. wipe cache partition,
2. then wipe dalvik cache and then
3. factory reset all from CWM...
4.then flash whatever .zip ROM you like.
Flashing back to stock FROYO/ECLAIR from GB with an odin rom you must be sure the stock rom either includes both PBL and SBL or no bootloaders at all and then your good.

Need Help Fixing Someone's Cappy

Ok so yesterday I received a cappy from someone on here that I told them I would try and fix. I am not charging them anything and am actually paying shipping back to them. When I received it and turned it on it was stuck at the end of the cornkernel bootlogo. I thought hey this will be easy and flashed the heimdall version of I897UCKK4 Stock, Wipe, with options to install Bootloaders, Param,and Re-partition-One-Click. Phone rebooted and is now stuck at the att logo. So I flash cornkernel, its stuck at the end of cornkernel bootup. So I decided on a whim to try and flash this kernel Devil3_1.1.3_HB_cappy_CFS_BLN_VC_20120807, luckily that got me into recovery, so I did a full backup of all the stuff on his internal storage and completely wiped the phone, wipe data/factory reset, wipe dalvik cache, format boot, format system, format sdcard, format cache, format data, format datadata (yes I know I wiped some things twice) . Then I flashed my rom, it just reboots to recovery after the flash, still reboots after a reflash of the rom. I then wiped everything again and tried flashing CM9's latest nightly to see if I could get it to boot up. Still reboots to recovery. So far all together I have flashed I897UCJI6-OCD-REV02-Low-designgears, i897uckk4 Odin One Click CONTAINS Bootloaders, Re-partition, Full Wipe, I897UCKF1_withBL,SGH-I897_I897UCKJ3, KK4-SE-One-Click, JF6 With Bootloaders, SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click Followed By I897UCKK4 Stock, Wipe, with options to install Bootloaders, Param,and Re-partition-One-Click both are heimdall. All of those either left it stuck at att or kernel screen after I flashed a kernel. Anyone got any ideas? I am almost to my wits end.

Try the Odin version of this... Stock KK4 one click...it will do ya a full wipe and repartition for sure.
Sent from my SGH-I897 using xda premium

4-2ndtwin said:
Try the Odin version of this... Stock KK4 one click...it will do ya a full wipe and repartition for sure.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Already have that is my go to file actually and I tried that before going the heimdall route. Thanks Anyways.

You should try the Rogers stock gingerbread with boot loaders. Worked for me when I was using the AT&T and not getting past recovery...
Sent from my cm_tenderloin using xda premium

-SGA- said:
You should try the Rogers stock gingerbread with boot loaders. Worked for me when I was using the AT&T and not getting past recovery...
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
Thanks for the idea. It didn't work tho. I am still at the same spot, phone keeps rebooting to recovery.

have to wonder,,has the phone had the EU bug? might try flashing the rom with datadata ( I believe thats it) on the external sd

stayintwisted said:
have to wonder,,has the phone had the EU bug? might try flashing the rom with datadata ( I believe thats it) on the external sd
Click to expand...
Click to collapse
Not that I know of, It isn't my phone so I do not know the history other than him saying it didn't boot past the kernel screen and receiving it and seeing that and then what I have done. Normally the sd card data from what I have seen is wiped when the eu bug happens from what I have read, maybe I am wrong, but since I backed up his data off the sdcard that is why I do not believe it has had the eu bug.

Anyone have any more ideas, I tried the EU Bug Instructions @ http://forum.xda-developers.com/showthread.php?t=1447303&page=85 Replacing the vold.fstab in the rom and also flashing it with CWM without luck. I am still stuck with it rebooting to recovery. I am still waiting on him to tell me his address again so I can mail it back to him since at this point I am lost. I told him MobileTechVideos would more than likely be his best shot at getting it fixed though.

cbalt said:
Anyone have any more ideas, I tried the EU Bug Instructions @ http://forum.xda-developers.com/showthread.php?t=1447303&page=85 Replacing the vold.fstab in the rom and also flashing it with CWM without luck. I am still stuck with it rebooting to recovery. I am still waiting on him to tell me his address again so I can mail it back to him since at this point I am lost. I told him MobileTechVideos would more than likely be his best shot at getting it fixed though.
Click to expand...
Click to collapse
Long story short, recovery is iffy at best for me. I went through something similar to this when trying to go from CM10 back to CM9 for the first time. Ever since then recovery has not been right.
What I did was
Install a stock one-click with bootloaders, used odin to flash speedmod kernel and then used that recovery to flash CM9 in three successions wiping everything each time. Somehow it took, and now I am no longer a crack flasher because I have the same kernel splash screen problem every time.
So,
Use this http://www.mediafire.com/?5rcofbzusoor6mv
PDA button in Odin3 1.7: http://forum.xda-developers.com/attachment.php?attachmentid=566807&d=1302623831
Boot into recovery.
Flash your ROM
Wipe /system, /data, and dalvik.
reboot recovery.
Flash again.
Wipe /system, /data, and dalvik.
reboot recovery.
Flash again.
Try to boot normally.

Thanks for the idea, but it's a no go, Phone just stops at Galaxy S SGH-I897 Kernel Screen. I can't even get to recovery. Only way I have got to recovery with this phone was flashing an ICS kernel.

There is a place that has rogers stock roms
cbalt said:
Thanks for the idea, but it's a no go, Phone just stops at Galaxy S SGH-I897 Kernel Screen. I can't even get to recovery. Only way I have got to recovery with this phone was flashing an ICS kernel.
Click to expand...
Click to collapse
There is a place that has rogers stock Roms the one click Odin's back to 2.2 is my go to for all problems the i can't get to recovery. I know you said you tried rogers stock roms but try the one-clicks for some reason they have always saved me. It will re-install everything and you will be on stock recovery if it works but from there its easy to get CWM and your on your way

sunfirestorm said:
There is a place that has rogers stock Roms the one click Odin's back to 2.2 is my go to for all problems the i can't get to recovery. I know you said you tried rogers stock roms but try the one-clicks for some reason they have always saved me. It will re-install everything and you will be on stock recovery if it works but from there its easy to get CWM and your on your way
Click to expand...
Click to collapse
I have already tried all three of the Rogers One Clicks with none of them actually doing anything more than the Captivate One Clicks, It still doesn't boot past the first screen. Thanks for the input though.

You've been using a one click with 2.3.3 bootloaders, they're are 2.3.5 bootloaders available that have solved certain peoples sleepdeath issues, including mine. I've done this procedure on several captivates to take them from mangled and non-bootable to latest bootloaders and working recovery to flash whatever rom I need to from there on.
Use this one click that includes the 2.3.5 bootloaders - http://fohdeesha.com/data/other/android/i897uckk4 with latest BL.zip
After that goes through and you have stock gingerbead, use this odin package to flash the included devil kernel package, that will give you the latest CWM recovery
http://fohdeesha.com/data/other/android/uckk4 CWM recovery.zip
After that, if you still can't boot into recovery, you have a hardware issue
edit: looks like you already did this more or less.......try it once more in this order? Then once you do this and boot into recovery, flash a rom and see if it will work

fohdeesha said:
You've been using a one click with 2.3.3 bootloaders, they're are 2.3.5 bootloaders available that have solved certain peoples sleepdeath issues, including mine. I've done this procedure on several captivates to take them from mangled and non-bootable to latest bootloaders and working recovery to flash whatever rom I need to from there on.
Use this one click that includes the 2.3.5 bootloaders - http://fohdeesha.com/data/other/android/i897uckk4 with latest BL.zip
After that goes through and you have stock gingerbead, use this odin package to flash the included devil kernel package, that will give you the latest CWM recovery
http://fohdeesha.com/data/other/android/uckk4 CWM recovery.zip
After that, if you still can't boot into recovery, you have a hardware issue
edit: looks like you already did this more or less.......try it once more in this order? Then once you do this and boot into recovery, flash a rom and see if it will work
Click to expand...
Click to collapse
I'm going to do your steps again which is more or less what I have already done. I am waiting to hear back from the person so I can ship him the phone back and he can send it to MTV or someone or just junk it, its his phone and his choice. At this point I would say it needs Jtag or Unbrickable mod + repair. Although I am still trying ideas of mine and anyone elses lol.
EDIT: Still A No Go. Doesn't Boot Past ATT Screen After Flashing The Odin 1 Click, After Flashing Kernel then wiping and flashing rom, it just reboots to recovery

Well if the one clicks are successfully writing primary and secondary bootloaders and it's still not working, a jtag isn't going to do anything else. It almost sounds like the memory has a few corrupt blocks, but I can't say until you flash 2.3.5 BL's and see what happens
---------- Post added at 07:39 PM ---------- Previous post was at 07:37 PM ----------
cbalt said:
EDIT: Still A No Go. Doesn't Boot Past ATT Screen After Flashing The Odin 1 Click, After Flashing Kernel then wiping and flashing rom, it just reboots to recovery
Click to expand...
Click to collapse
Oh jeez looks like the memory is failing then

Cant restore backup

I made a backup on my phone in TWRP and wanted to restore it to get some contact info that I forgot to upload to my Google account. Anywho, I go into recovery and wipe me squeeky clean then restore the backup. It goes through like normal and I boot up but it doesn't get bassed the HTC splash screen. It turns to a black screen that occasionally has a white/grey bar at the top. I loaded a different backup I had and am running fine, but I still need that contact info.
Any ideas as to get the back up to work or if it is no use?

KungPow90 said:
I made a backup on my phone in TWRP and wanted to restore it to get some contact info that I forgot to upload to my Google account. Anywho, I go into recovery and wipe me squeeky clean then restore the backup. It goes through like normal and I boot up but it doesn't get bassed the HTC splash screen. It turns to a black screen that occasionally has a white/grey bar at the top. I loaded a different backup I had and am running fine, but I still need that contact info.
Any ideas as to get the back up to work or if it is no use?
Click to expand...
Click to collapse
What hboot do you have?
If its 1.14 and you're switching ROMS (your backup is of a different ROM to the last ROM you were using) you might have to fastboot flash the boot.img of the ROM you're recovering.

i think it is a kernel issue
I had to downgrade from jb to ics and I wiped clean, I run into the same problem, I realized jb uses a different kernel, wipe clean flash your choosen Rom kernel update first and then your Rom, it worked for me hopefully works for you

ilirium said:
I had to downgrade from jb to ics and I wiped clean, I run into the same problem, I realized jb uses a different kernel, wipe clean flash your choosen Rom kernel update first and then your Rom, it worked for me hopefully works for you
Click to expand...
Click to collapse
where can i get the stock boot.img or the stock one x 2.20 image to extract the boot.img?
thanks!

is this it?
would this work?
http://forum.xda-developers.com/showthread.php?t=1812459
if i download the odexed stock rooted rom and extract the boot.img, i can flash that to boot, and then run twrp restore to my backed up stock rooted rom, right?
my stock rooted rom was at&t 2.20 firmware.

Hoping I understood you correct, you basically need to flash a kernel first, so I am guessing you can use flar kernel,
http://forum.xda-developers.com/showthread.php?t=1967897
and that should be the stock kernel on steroids, however if that were not to work he has a kernel for jb phones, so I would start by these first.
I really had this issue where I could see my phone in a brick state mode then flashed the right kernel for the right rom, and boom it worked like a charm.
nespid said:
would this work?
http://forum.xda-developers.com/showthread.php?t=1812459
if i download the odexed stock rooted rom and extract the boot.img, i can flash that to boot, and then run twrp restore to my backed up stock rooted rom, right?
my stock rooted rom was at&t 2.20 firmware.
Click to expand...
Click to collapse

[Q] Random reboots on all AOSP roms.

I much prefer AOSP over TW; however, it is hard to tolerate due to random reboots. What exactly can be causing this? I tried different CPU governors and everything. To my knowledge, this started occuring after I got my new battery, the gorilla gadgets 4500 mah.

If you only started seeing the reboots after the battery then I would look at that if I were you.
Also, what AOSP roms are you using? I've been on CM 10.1, both official and builds I have compiled myself and haven't had a random reboot in months. Last one I remember having was a few weeks after the switchover to the 3.4 kernel.

Chris123NT said:
If you only started seeing the reboots after the battery then I would look at that if I were you.
Also, what AOSP roms are you using? I've been on CM 10.1, both official and builds I have compiled myself and haven't had a random reboot in months. Last one I remember having was a few weeks after the switchover to the 3.4 kernel.
Click to expand...
Click to collapse
I reverted to stock battery. I had a random reboot again. The roms I used are XenonHD, CM10.1, PAC Man, LiquidSmooth. Reboots on all of them.

LegoFarmer said:
I reverted to stock battery. I had a random reboot again. The roms I used are XenonHD, CM10.1, PAC Man, LiquidSmooth. Reboots on all of them.
Click to expand...
Click to collapse
Should I try updating my bootloader? This was rooted and unlocked back in October, so it may not flash modern (4.2.2) roms correctly. What do you think?

Flash the MF1 firmware in recovery, get it here:
http://invisiblek.org/sch-i535/firmware/d2vzw_VRBMF1_firmware.zip
that's more than likely the cause of your reboots, CM doesn't like being on the earlier firmware anymore.

Chris123NT said:
Flash the MF1 firmware in recovery, get it here:
http://invisiblek.org/sch-i535/firmware/d2vzw_VRBMF1_firmware.zip
that's more than likely the cause of your reboots, CM doesn't like being on the earlier firmware anymore.
Click to expand...
Click to collapse
Thanks, I have a bigger problem now, though. I wiped and just tried to re-do everything. I installed jellybean factory and get bootlooped. Used this guide, cannot enter recovery either.
http://forum.xda-developers.com/showthread.php?p=43850592#post43850592

LegoFarmer said:
Thanks, I have a bigger problem now, though. I wiped and just tried to re-do everything. I installed jellybean factory and get bootlooped. Used this guide, cannot enter recovery either.
http://forum.xda-developers.com/showthread.php?p=43850592#post43850592
Click to expand...
Click to collapse
Can you get into download mode? If so try to ODIN back to stock, re-unlock, re-root, and flash back to CM.
Why did you try flashing that anyway?

Chris123NT said:
Can you get into download mode? If so try to ODIN back to stock, re-unlock, re-root, and flash back to CM.
Why did you try flashing that anyway?
Click to expand...
Click to collapse
That's what I tried doing. I had my aosp rom running and decided to start from scratch. I tried using odin to go back to the jellybean ota, when it boots, I stay at boot animation, I can get in download mode though. If I go in recovery, it is just black.

LegoFarmer said:
Thanks, I have a bigger problem now, though. I wiped and just tried to re-do everything. I installed jellybean factory and get bootlooped. Used this guide, cannot enter recovery either.
http://forum.xda-developers.com/showthread.php?p=43850592#post43850592
Click to expand...
Click to collapse
LegoFarmer said:
That's what I tried doing. I had my aosp rom running and decided to start from scratch. I tried using odin to go back to the jellybean ota, when it boots, I stay at boot animation, I can get in download mode though. If I go in recovery, it is just black.
Click to expand...
Click to collapse
Get back into download mode and ODIN again. Once you finish ODIN you're gonna have to get into recovery to wipe data/clear cache so the stock ROM will boot, otherwise it will get stuck at the boot screen.

Chris123NT said:
Get back into download mode and ODIN again. Once you finish ODIN you're gonna have to get into recovery to wipe data/clear cache so the stock ROM will boot, otherwise it will get stuck at the boot screen.
Click to expand...
Click to collapse
What happens is I use the recovery hotkeys, but the screen is black unless I release the hotkeys, in which it just boots normally

Fixed lol. I had to let go of the power button after it vibrated. I can take it from here, thanks, man!!!

[Q] I have a Tab that was partially restored from the ICS flashing brick. Advice?

I have a GT-P6210 from Canada (No IR) and back when it was Honeycomb I had no problems with it.
When the ICS rom appeared I installed it and it worked for a while. However, I accidentally wiped from the stock recovery, which we now all know causes a brick. At the time, CWM was only a temporary recovery and it wouldn't accept my HC backups (different partitions?) so I went crazy trying to fix it.
I tried:
To flash ICS again. It didn't really work out for me.
To flash CM9. It got stuck at the CM9 bootlogo.
To flash a patched .pit and ICS.
I was able to flash a patched .pit but I couldn't complete the ICS flashing. It booted... to a screen saying that the "encryption" failed. I sent the tab to my uncle and he was able to flash ICS. This restored the tablet to a mostly working condition
However, because of the patched .pit I flashed earlier, it only has ~800MB of internal storage.
Now, I was thinking about my next step. Should I try to reflash the original .pit and Honeycomb then hope that I get lucky while wiping with stock HC recovery? Should I try to flash JB? Should I use the original .pit and flash JB? Should I just try to live with the fact that I'll be stuck with this problem until I get a new tablet in a few years? Please advice.
EDIT: If I use Mobile ODIN to flash, say, HC from ICS, will that work?
EDIT 2: When I flashed a patched .pit I didn't use emmc_find_brick_start.zip and emmc_find_brick_end.zip and I just randomly went with a patched .pit for the device.
EDIT 3: Say if I flash PA in the tab's current state, will it crash and go boom or I'll have a ~800MB PA experience?

gio32999 said:
I have a GT-P6210 from Canada (No IR) and back when it was Honeycomb I had no problems with it.
When the ICS rom appeared I installed it and it worked for a while. However, I accidentally wiped from the stock recovery, which we now all know causes a brick. At the time, CWM was only a temporary recovery and it wouldn't accept my HC backups (different partitions?) so I went crazy trying to fix it.
I tried:
To flash ICS again. It didn't really work out for me.
To flash CM9. It got stuck at the CM9 bootlogo.
To flash a patched .pit and ICS.
I was able to flash a patched .pit but I couldn't complete the ICS flashing. It booted... to a screen saying that the "encryption" failed. I sent the tab to my uncle and he was able to flash ICS. This restored the tablet to a mostly working condition
However, because of the patched .pit I flashed earlier, it only has ~800MB of internal storage.
Now, I was thinking about my next step. Should I try to reflash the original .pit and Honeycomb then hope that I get lucky while wiping with stock HC recovery? Should I try to flash JB? Should I use the original .pit and flash JB? Should I just try to live with the fact that I'll be stuck with this problem until I get a new tablet in a few years? Please advice.
EDIT: If I use Mobile ODIN to flash, say, HC from ICS, will that work?
EDIT 2: When I flashed a patched .pit I didn't use emmc_find_brick_start.zip and emmc_find_brick_end.zip and I just randomly went with a patched .pit for the device.
EDIT 3: Say if I flash PA in the tab's current state, will it crash and go boom or I'll have a ~800MB PA experience?
Click to expand...
Click to collapse
i experienced this with my tab,What I did was going back to stock HC and do full wipe, then flash ics using heimdall not odin then flash jb using odin..
Sent from my GT-P6200 using xda app-developers app