Database Develop

[Q] Stuck after boot animation. No Recovery/Download

Hi guys,
I think I finally managed to brick my phone. Everything was working perfectly fine, until today when decided to try GB's Steam kernel.
So a little background first, to make things quicker:
- I was able to open download and recovery mode before, even after doing a odin3 one click restore twice.
- I've tried a Cognition and moved to DarkyYtt3r. Went from 7.0.1 to 7.5 to 7.8 to 8.0.1, no issues.
- Changed the kernel and modem several times. The last one I tried was glitterball's uc/ov stable (no charging death).
- Current set up before this mess:
-- ROM: DarkyYtter v8.0.1 > http://forum.xda-developers.com/showthread.php?t=890429
-- Kernel: gb-reorient-fixed-ocuv-f-cwm.zip > http://forum.xda-developers.com/showthread.php?t=887315
-- Modem: TLJL3 I think.
Everything working beautifully.
Today I saw this thread: http://forum.xda-developers.com/showthread.php?t=903238 ... gb's steam kernel. since no one was having major issues, I made a backup of my current rom using CWNand decided to install the kernel using SGS Kernel flasher, according to instructions.
Cool. I've flashed kernels before a few times. No big deal. And I figured, I'm able to get into Recovery or worst case scenario into download mode. I flashed the kernel, reboot, got into Steam's recovery. Looked around. Activated a couple of tweaks although I don't remember which ones.
Rebooted and this is where the issues began. I got the "intro" window you get with i9000 roms (keyboard intro, syncing, etc). A lot of apps were force closing, including facebook, twitter, rom manager, ADW Launcher, etc.
Ok, so I rebooted to Steam recovery and deleted the cache. Went back and the same problem. At least I was able to boot the system.
I said, oh well, let's go back to our backup. Booted Steam's recovery, and tried to recover from the last backup.
It worked for one boot. Not sure what I did, I don't remember, but after trying to boot again, the phone displays the AT&T screen, the GT-I900 screen and then the Galaxy S screen. I then feel the force close vibration, and the screen goes black. I can touch the softkeys and they blink, but I feel the FC vibration every 10 or 15 seconds.
Somewhere along the line something bad happened.... but here is what's bothering me. I cannot get back into download or recovery mode anymore. Been there all day trying to make it work with no luck at all.
So, more importantly, somewhere along the line, between rom flashes, or something, I lost the ability to get into recovery or download mode. I've heard that I900 roms have different button combos, but nothing works
I'll buy a few resistor packs tomorrow, and some cables just in case. I'm afraid that I won't be able to boot into download mode this way either.
also, adb is not detecting the phone. tried both windows and linux. if I could only get it even for one second so I can send a adb reboot download... but no
Do you guys have any ideas?
Thanks!

cumanzor said:
Hi guys,
I think I finally managed to brick my phone. Everything was working perfectly fine, until today when decided to try GB's Steam kernel.
So a little background first, to make things quicker:
- I was able to open download and recovery mode before, even after doing a odin3 one click restore twice.
- I've tried a Cognition and moved to DarkyYtt3r. Went from 7.0.1 to 7.5 to 7.8 to 8.0.1, no issues.
- Changed the kernel and modem several times. The last one I tried was glitterball's uc/ov stable (no charging death).
- Current set up before this mess:
-- ROM: DarkyYtter v8.0.1 > http://forum.xda-developers.com/showthread.php?t=890429
-- Kernel: gb-reorient-fixed-ocuv-f-cwm.zip > http://forum.xda-developers.com/showthread.php?t=887315
-- Modem: TLJL3 I think.
Everything working beautifully.
Today I saw this thread: http://forum.xda-developers.com/showthread.php?t=903238 ... gb's steam kernel. since no one was having major issues, I made a backup of my current rom using CWNand decided to install the kernel using SGS Kernel flasher, according to instructions.
Cool. I've flashed kernels before a few times. No big deal. And I figured, I'm able to get into Recovery or worst case scenario into download mode. I flashed the kernel, reboot, got into Steam's recovery. Looked around. Activated a couple of tweaks although I don't remember which ones.
Rebooted and this is where the issues began. I got the "intro" window you get with i9000 roms (keyboard intro, syncing, etc). A lot of apps were force closing, including facebook, twitter, rom manager, ADW Launcher, etc.
Ok, so I rebooted to Steam recovery and deleted the cache. Went back and the same problem. At least I was able to boot the system.
I said, oh well, let's go back to our backup. Booted Steam's recovery, and tried to recover from the last backup.
It worked for one boot. Not sure what I did, I don't remember, but after trying to boot again, the phone displays the AT&T screen, the GT-I900 screen and then the Galaxy S screen. I then feel the force close vibration, and the screen goes black. I can touch the softkeys and they blink, but I feel the FC vibration every 10 or 15 seconds.
Somewhere along the line something bad happened.... but here is what's bothering me. I cannot get back into download or recovery mode anymore. Been there all day trying to make it work with no luck at all.
So, more importantly, somewhere along the line, between rom flashes, or something, I lost the ability to get into recovery or download mode. I've heard that I900 roms have different button combos, but nothing works
I'll buy a few resistor packs tomorrow, and some cables just in case. I'm afraid that I won't be able to boot into download mode this way either.
also, adb is not detecting the phone. tried both windows and linux. if I could only get it even for one second so I can send a adb reboot download... but no
Do you guys have any ideas?
Thanks!
Click to expand...
Click to collapse
Did you ever get this problem fixed? The reason I ask is because I'm in this same situation.

We seem to be having the same problem also... Nothing has worked for me so far
http://forum.xda-developers.com/showthread.php?t=960419

Pull your battery, pull your sd card, hold the volume button and plug in the usb cord, this will get you into download
Sent from my GT-I9000 using XDA App

Keep hope alive glaze!
Sent using XDA App

Im going to get a jig hopefully all goes well.

[Q] Galaxy S Plus - Stuck in Reboot loop

Hi
I got a rooted Samsung galaxy plus 9001.
I installed font changer and busy box.
With the font changer i chose a ttf font from the internal memory card, and after applying it, i got the pop up menu reboot now.
After clicking on reboot now my phone stuck in reboot loop.
I can access android recovery menu, i treid wipe all user data but still stuck in reboot loop.
Please help me guys.

You'll have to reinstall the rom you were using... that should get you out of bootloop. If that doesn't work, do factory defaults (you'll lose all apps and settings!) and install the original rom again (or for instance XXKPS).
One more tip: always make a (cwm/feamod) backup before changing system defaults
Regards,
Nika.

Thank you.. Thanks alot

nikagl said:
You'll have to reinstall the rom you were using... that should get you out of bootloop. If that doesn't work, do factory defaults (you'll lose all apps and settings!) and install the original rom again (or for instance XXKPS).
One more tip: always make a (cwm/feamod) backup before changing system defaults
Regards,
Nika.
Click to expand...
Click to collapse
any link to step by step instructions on how to do this available anywhere?
i have similar boot loop problem.

I doubt anyone has created that. How did you get into the loop?
Sent from my GT-I9001 using xda premium

Boot Loop
When you are stuck in the boot loop:
1. Take out the battery and re-insert it.
2. Put the phone in download mode (using 3-button combo - down+home+power)
3. Open Odin, and reinstall the stock firmware (using all 3 md5 files: PDA, CSC and PHONE); you will be able to find the files in the stock firmware 2.3.5 from the post in XDA-stock gingerbread roms for i9000.
4. After you have done this, root your phone, install custom kernel, and then install custom firmware through custom recovery menu.
Thats the way i did it....i dunno if there is a short cut to it.
Hope it helps!

I also find bootloop can be resolved by going into download as stated by puneetgandhi and flash a VOODOO KERNEL using ODIN (it goes on PDA).
Then booting to recovery and turning off all lags.

Link to the stock firmware page i was referring to:
Link to the stock firmware page i was referring to:
http://forum.xda-developers.com/showthread.php?t=846913

nikagl said:
I doubt anyone has created that. How did you get into the loop?
Click to expand...
Click to collapse
No idea, it has been going in and out of boot loops a few times already for last few months works fine for ages. All of a sudden it would starts lagging on an app or when texting and reboots into a loop
although i never had the problem on froyo only in gingerbread (a few week or so after i got my phone back from repair shop, they upgraded it to gingerbread without my notification, but since i had voodoo on before on froyo i don't know, maybe they updated it wrongly ).
First time i fixed it with a fix on here about transferring a system file through odin.
second time it fixed itself after i left it for a day as i didn't have time to fix it .
this time i finally fixed it with a factory reset for the 4th or 5th time in a row, after wiping cache and so on, didn't work first few times.
So not sure whats causing it, could be a failing internal memory card i suppose or overheating corrupting the memory, hoping its a software issue that the factory reset will permanently fix (but doubt it).

If you were on Froyo, please look or create another thread for I9000 Samsung Galaxy S. This thread is about Samsung Galaxy S plus I9001... That's the device I own, and stuff like Voodoo and Froyo do not exist on SGS+ (and I have no experience with - probably other with an I9000/SGS do).

[Q] Q - CM7.2.0 RC 1 - Random Reboots while charging into recovery menu

Hi,
Im using Cm7.2.0 RC1.
Every night during charge my OB reboots into the recovery mode. I didn't experience this problem with Zeus 4.02b or stock rom (shipped 2.2.0 and updated V20o).
It's a PITA, cause I use my phone as my alarm clock
Is there something like an error log? Does anybody already know a solution?
Tried google and this forum, no results

I had the same problem in an entirely different device but I know of some ways to possibly fix it. Check to see if you have the cyanogenmod tenkian kernel. Do this by opening up settings and scrolling down to the very bottom and hitting about phone. My other device randomly rebooted due to a problem with a kernel. What version of clockwork mod recovery do you have? Open up rom manager and update to the latest possible recovery by hitting "flash clockwork mod" at the top. If that doesn't fix it, boot into recovery and clear/wipe data (pain but usually fixes it) clear cache partition, and clear dalvik cache, then bootup and see. You can make a "logcat" file which gives details to devs about exactly what was happening when your device went wonky. I hope this helps
Sent from my LG-P970 using XDA, or something

vagubunt said:
Hi,
Im using Cm7.2.0 RC1.
Every night during charge my OB reboots into the recovery mode. I didn't experience this problem with Zeus 4.02b or stock rom (shipped 2.2.0 and updated V20o).
It's a PITA, cause I use my phone as my alarm clock
Is there something like an error log? Does anybody already know a solution?
Tried google and this forum, no results
Click to expand...
Click to collapse
reflash the file baby or the cm7 RC1 file babe

[Q] Boot lopp w/ AP, Plz help.

Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!

I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.

I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?

Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....

Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.

[GUIDE]How to convert to F2FS (Flash Friendly File system)

For information on what F2FS is see the link here: https://en.wikipedia.org/wiki/F2FS
http://www.xda-developers.com/f2fs-put-to-the-test-against-ext4/
Basically F2FS is a newish file system and was designed by Samsung purely for flash memory devices. It is significantly faster in write speed and therefore yields benefits when used on partitions like DATA and CACHE.
However the SYSTEM partition is read only and therefore would not benefit from F2FS as EXT4 is capable of high speed read. Not only that Ext4 adds benefits of data integrity due to being a journaling file system.
As the system partition is not being touched, any Rom can be used, stock or custom.
This guide will explain how to convert to the F2FS file system.
1. The first step is to convert the DATA and CACHE partition to F2FS.
For this a custom Recovery with F2FS support is required. I have already built modified versions of TWRP which fully support F2FS which can be found here: http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
2. Install then boot to TWRP then make a backup of the DATA partition to your EXTERNAL SD CARD
Next select WIPE > ADVANCED WIPE then select CACHE then REPAIR OR CHANGE SYSTEM > CHANGE FILE SYSTEM > F2FS. Finally SWIPE TO CHANGE.
This will then format to F2FS, do the same for the DATA partition.
PLEASE NOTE THIS WILL COMPLETELY WIPE THE INTERNAL STORAGE, SO BACK UP ANY FILES YOU NEED TO THE PC OR EXTERNAL SD CARD!
3. Once the format is complete reboot TWRP by selecting the 'Recovery' option under the REBOOT tab.
4. Once rebooted to TWRP restore the backup of the DATA partition that was made earlier.
Ignore the warning about the backup being created with Ext4.
5. When that completes reboot to DOWNLOAD mode.
Next load up the relevant kernel below for your particular device in ODIN, put it in the AP slot then hit START.
SM-T805 BOCC KERNEL
SM-T800 BOCC KERNEL (confirmed working by godsfilth)
SM-T700 BOCC KERNEL(needs testing)
If the above kernels don't work because you have updated your rom to a later base you may need the updated kernels below. I have also added ext4 support in case anyone wants to switch back:
SM-T700 BOE6 KERNEL
SM-T705 BOE6 KERNEL
SM-T800 BOE6 KERNEL
SM-T805 BOE6 KERNEL
NOTE: the kernels provided are for Lollipop ONLY and is completely stock built from Samsung Sources except for the F2FS modifications. Also the kernel will allow Permissive mode to be set but is Enforcing by default( I think it should be the users decision and not forced permissive)
To change modes use SELinux mode changer http://forum.xda-developers.com/showthread.php?t=2524485
I wanted this kernel to be as untouched and stable as possible, so as not to introduce any issues. If you wish to have a custom kernel ask your kernel developer to add F2FS support.
6. Once the flashing process is complete with ODIN the tablet should boot. It may take a good while for the tablet to boot as its sets itself up and you will see the normal SAMSUNG logo, so don't worry if you have to wait a while.
Once booted further reboots will boot as normal and infact will probably notice quicker startups. I notice almost 5-10 seconds faster and a quicker tablet overall.
Have tested this thoroughly for days and has been stable with no issues.
IF ANYONE WANTS TO TRY THIS OUT AND THEN RETURN TO EXT4, ITS A SIMPLE MATTER OF FOLLOWING THE SAME PROCEDURE, BUT CHOOSING EXT4 IN TWRP.
Source code
GOOD LUCK AND PLEASE GIVE FEEDBACK.
.

T800 kernel added. Not tested as I don't have the T800, so can someone confirm it works?

ashyx said:
T800 kernel added. Not tested as I don't have the T800, so can someone confirm it works?
Click to expand...
Click to collapse
thanks loved f2fs on my N7 i'm making a backup now not sure if I'll be able to test before work or if I'll have to wait till tomorrow

so it seems the T800 doesn't boot.
after a minute or two logcat starts running but seems to my untrained eye to loop to the same things every few minutes.
i can still force a reboot into recovery so no harm done, if you have any ideas ill test them out, ill try again sometime tomorrow maybe my sleep deprived brain missed something

godsfilth said:
so it seems the T800 doesn't boot.
after a minute or two logcat starts running but seems to my untrained eye to loop to the same things every few minutes.
i can still force a reboot into recovery so no harm done, if you have any ideas ill test them out, ill try again sometime tomorrow maybe my sleep deprived brain missed something
Click to expand...
Click to collapse
How far does it boot and how long did you wait, do you see the second multicoloured Samsung logo?
It does boot on my t805 fine as do all t800 kernels, so seems strange it doesn't on your t800.
I will post another boot.img for you to try.
Can you try booting again then send me the kernel log.
cat /proc/last_kmsg > /sdcard/last_kmsg.txt

ashyx said:
How far does it boot and how long did you wait, do you see the second multicoloured Samsung logo?
It does boot on my t805 fine as do all t800 kernels, so seems strange it doesn't on your t800.
I will post another boot.img for you to try.
Can you try booting again then send me the kernel log.
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
Click to expand...
Click to collapse
boots to the "samsung galaxy tab s" splash screen then dims a little and stays there left it for 10 minutes while i figured out where adb pull and windows 10 had decided the kmsg file should go as well as while i typed this.
i did see an error in recovery when formatting data as f2fs it said something along the line of "mount -o bind /data/media/sdcar0 error=255" pretty sure it was longer than that ill get the whole message if you want.
kmsg should be attached let me know if you need anything else

godsfilth said:
boots to the "samsung galaxy tab s" splash screen then dims a little and stays there left it for 10 minutes while i figured out where adb pull and windows 10 had decided the kmsg file should go as well as while i typed this.
i did see an error in recovery when formatting data as f2fs it said something along the line of "mount -o bind /data/media/sdcar0 error=255" pretty sure it was longer than that ill get the whole message if you want.
kmsg should be attached let me know if you need anything else
Click to expand...
Click to collapse
That error message is normal because you've formatted the data partition, it's just a warning it can't mount sdcard/0.
Did you make sure that you formatted both cache and data to f2fs?
Also the kernel log you posted is from recovery not boot. To get the boot kernel log, boot as normal, give it a minute then immediately restart to recovery. Then run the command in the twrp terminal or adb.

ok so now that the kernel is working and i've played with it for a little while its definitely snappier at startup compared to ext4, noticeably so also apps seem to be a quicker as well ill play around with it some more and see but definitly plan on keeping it f2fs and swapping my girlfriends over as well

Any idea if apps like FolderMount that mount internal storage folders (like OBB) to the external card?

i am going to install the T700 and see how it goes...

All good on T805 (T805XXU1BOE3) (using other f2fs enabled kernel). Thank you!

I would like to tell @ashyx a very enthusiastic THANK YOU for taking the time to put this guide and F2FS kernel together. We need more developers like you man. I'm happy I do not have to give up F2FS just because I got a new device, so thank you for this.
I would like to ask anyone who has not thanked ashyx, to please take the time and hit his thanks button. He deserves it :good:

Much appreciated, thanks for the feedback. :thumbup:

ashyx said:
Much appreciated, thanks for the feedback. :thumbup:
Click to expand...
Click to collapse
Your most welcome. Going to test this on stock 5.0.2 on my T700 here soon.

Updated the kernel sources in op.

ashyx said:
Updated the kernel sources in op.
Click to expand...
Click to collapse
After flashing the new T700 kernel it does not boot for me. Saw the Samsung logo as usual for about 5 minutes maybe, but then the logo disappeared and then nothing. Seems to have shut down. The power button no longer worked to boot up either. However, it goes into Download Mode just fine.
Going to flash it again. BRB with some news. Thanks
EDIT: Flashed a second time and still the same, ROM will not boot on the BOE6 kernel. Thanks again

SkOrPn said:
After flashing the new T700 kernel it does not boot for me. Saw the Samsung logo as usual for about 5 minutes maybe, but then the logo disappeared and then nothing. Seems to have shut down. The power button no longer worked to boot up either. However, it goes into Download Mode just fine.
Going to flash it again. BRB with some news. Thanks
EDIT: Flashed a second time and still the same, ROM will not boot on the BOE6 kernel. Thanks again
Click to expand...
Click to collapse
Which firmware base are you running?

ashyx said:
Which firmware base are you running?
Click to expand...
Click to collapse
I was running CarbonROM 5.1.1.
I can no longer boot system, and it wont boot to recovery either. What is the button combo for recovery again? Maybe I have it wrong.
I thought I had downloaded a zip for stock 5.0.2, but I cant find the darn thing now, lol. I have a TWRP backup of 4.4.2 and 5.0.2 (I think), but I'm on 5.0.2 Bootloader. Plus I need TWRP mode in order to even restore the backups.
is there a ODIN tar of 5.0.2, preferably rooted? I found TWDetox, but its a zip for TWRP to install. Damn it, lol I know for fact I found a tar for 5.0.2 but now I can't find it. I need to find a RedBull maybe that will help me locate it. LOL

POWER + VOL DOWN + HOME as soon as it restarts quickly change to VOL UP whilst still holding the other buttons.

ashyx said:
POWER + VOL DOWN + HOME as soon as it restarts quickly change to VOL UP whilst still holding the other buttons.
Click to expand...
Click to collapse
Hmm, thanks I have not seen that combo mentioned anywhere on the internet yet. You rock dude, it worked... :good: