yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] stratosk:
Do you mean that it never boot in recovery? This is very interesting!
[Galaxy S I9000 Android Development] shaarky:
Exactly - just boot loop, never went to recovery - I attached also logs I've found under /data, one of that had timestamp from the previous boot loop occurrence. Maybe you will find there something ?

Anyway, now I have to sleep...after 4 hours of sleep I will drive 2x230km...

*edit* very interesting - I again put back init.d content of the EliteROM maker back (as I would like to find guilty init.d script), again was booting for 10min (on boot-animation). So I went back to CWM, cleared again init.d and - again bootloop ;-)
[Galaxy S I9000 Android Development] stratosk:
Thanks for testing it.

Have a good night.
[Galaxy S I9000 Android Development] raunakchopra:
ok.. so plez if anyone can help me.. i have lost recovery and the phone is not being detected by windows getting 'USB device not recognized' error.. so what do i do now..

i was on DK 5.5 and just rebooted normally .. and fresh full wipe install it was..
[Galaxy S I9000 Android Development] -MaD-:
Sorry not at home, but search for Samsung USB driver for your PC. Got same problem once...

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] mialwe:
The combined initramfs idea sounds very good to me. I din't know if it will help the loop issues but I was thinking about an Odin/Heimdall flashable version ov ICS kernels a lot since I switched to ICS. As real life is keeping me busy for the last weeks I don't have enough time for experiments but if I can be of any help please let me know. If I find the time I'll look into the ICS/GB init process, too.

"Today I smashed my phone" - yes, I know that feeling :)

"I want SGS3" - no, not unless it's available in black. A used SGS2 would be enough for me.

I think it's true as soon as the ICS kernel has been flashed + device has rebooted (new kernel = new mounts). Then the CM9 install has to be initiated again via CWM to reach the next installation stage un updater.sh:

# if a cyanogenmod.cfg exists, then this is a first time install
# let's format the volumes and restore radio and efs

# remove the cyanogenmod.cfg to prevent this from looping
/tmp/busybox rm -f /sdcard/cyanogenmod.cfg

# unmount and format system (recovery seems to expect system to be unmounted)
/tmp/busybox umount -l /system
/tmp/erase_image system

# unmount and format cache
/tmp/busybox umount -l /cache
/tmp/erase_image cache

if /tmp/busybox test -e /sdcard/cyanogenmod.cm7upd ; then
# this is an upgrade from CM7 with changed MTD mapping for /system and /cache
# so return to updater-script after formatting these two

/tmp/busybox rm -f /sdcard/cyanogenmod.cm7upd

exit 0
fi

# unmount and format data
/tmp/busybox umount /data
/tmp/make_ext4fs -b 4096 -g 32768 -i 8192 -I 256 -a /data $DATA_PART

# unmount and format datadata
/tmp/busybox umount -l /datadata
/tmp/erase_image datadata

updater.sh will finish the complete initial CM9 installation and the return to CWM.

This is for a first CM9 install only, if we are updating an existing install this part is skipped.
[Galaxy S I9000 Android Development] shaarky:
Only FYI - I got again bootloop today (after I restarted using Widgetsoid my phone while connected via USB). I tried again Semaphore_recovery.tar - this time it wasn't stuck, but was again continuing in boot loop.
[Galaxy S I9000 Android Development] franklin01:
Ok, it definitly seems to be a partition problem.

About getting bootloop after a reboot with usb cable connected it comes from the kernel, basically when you boot without a cable it starts normally, but if the phone is plugged the init sequence is not the same and that could lead to bootloop.

Solution is to update kernel code to ignore boot code when plugged in so it boot normally. (or fix this part)

About bootloop when installing/updating a rom, what about using redbend_ua to write directly partitions on the phone without worrying about mountpoint or copy error?

This is an insane idea, but it could be a breakthrough if done properly as we could even flash sammyrom this way and possibly kinda dual boot...

(more info on flashing using redbend_ua on the dualboot thread)
[Galaxy S I9000 Android Development] ghul21:
Hehehe

Today i only wipe cache + dalvic aaaaaaand what?? Bootloop without recovery .....

With the Devil kernel. My butt was saved by semaphore 2.7.4 and bows here for Stratosk :D

Surprise me because I'm using the razer theme that automatically cleans Dalvic and cache.

After that I never have problems. Only after manual cleaning..
[Galaxy S I9000 Android Development] cereal86:
Here's a solution, worked with me:

flash midnight kernel with odin

flash devil kernel with cwm

clear dalvik cache, user data, etc

flash any ics custom rom
[Galaxy S I9000 Android Development] shiyingwong:
I'm using this androiddicasbrasil ROM, built 31 recently because I found built 34 have language problem for me. And sometimes after I used Titanium Backup then do a reboot to recovery, the bootloop will happen. Should not be the problem of TB, but somethings happened when I try to get into Recovery to do a backup. It'll keep rebooting, can't access to recovery mode. So I used odin every time.
[Galaxy S I9000 Android Development] stratosk:
Mialwe and myself, after a discussion for the bootloop issue, decided to work in common and investigate the possibility to flash an ICS kernel through Heimdall/ODIN in order to help an easier recovery when a phone goes to bootloop.

In order to achieve this, we built a new unified initramfs along with an installation of kernel dependencies (modules) procedure that will allow flashing a kernel through Heimdall/ODIN. The same initramfs approach can also be used for CWM zip flashables.

We hope that he new unified initramfs will bring a more robust, safe and faster booting and maybe can help for less bootloop issues and easier recovery when this happens.

Attached is a Heimdall/ODIN flashable full working Semaphore kernel (of course, there is also a full working Midnight kernel that Mialwe will publish at his convenience).

This is a version that will help us to test the new initramfs and the Heimdall/ODIN flashing.

Please for your feedback and report if the new initramfs helps to recover from bootloops or if it prevents(?) bootloops.
[Galaxy S I9000 Android Development] malcho:
Good job my friend.

I will try it tommorow.Basically you want to try is there dalvik cache vipe situation solved?

Because most of people report that.

Tommorow i want to try new rom(aokp) and i will flash this.
[Galaxy S I9000 Android Development] stratosk:
Actually we want to test normal boot, recovery boot, dalvik/cache wiping. We also need reports if this can help to recover the phone after flashing it through ODIN when in bootloop.

Although, Mialwe and myself tested the new initramfs, we couldn't reproduce a real boot loop situation to test it.
[Galaxy S I9000 Android Development] malcho:
S version is for patched rom right?

Ok i will try tommorow and let you know how it goes.

Many regards
[Galaxy S I9000 Android Development] saszseb:
When I flash Glitch over Devil I lose my recovery. Have you tried it?

Sent from IMM76K.
[Galaxy S I9000 Android Development] stratosk:
Yes, 's' is for huge memory patched ROMs.
[Galaxy S I9000 Android Development] malcho:
Ok just to make sure;)

I will play with it tommorow.
[Galaxy S I9000 Android Development] stratosk:
No, personally I didn't test it.

Please for your feedback if you'll do this.
[Galaxy S I9000 Android Development] Bejda:
Had bootloops but no luck with Semaphore 1.1.2s.tar,it kept bootlooping with auto-reboot unticked/ticked.
[Galaxy S I9000 Android Development] saszseb:
CM7 initial kernel will help you.

Sent from IMM76K.
[Galaxy S I9000 Android Development] mdv53:
i can't get into recovery mode with Semaphore 1.1.2s.tar
[Galaxy S I9000 Android Development] stratosk:
Can you please post some more details? Which ROM do you use?

Did you try to enter to recovery with 3 button combo? The phone boots normally? If yes, please post the boot.txt (located in / ) after your boot.

Mialwe, added many useful debug information in the new initramfs.
[Galaxy S I9000 Android Development] Bejda:
Do you really get what we're taking about here? Thanks for helping but i'm used to get my recovery back with cm7 initial .tar,we're trying to identify how it happens/prevents this.

@Stratosk,

Bejda said:

"Had bootloops but no luck with Semaphore 1.1.2s.tar,it kept bootlooping with auto-reboot unticked/ticked."

Auto-reboot unticked: no access to recovery with 3 button combo (keep bootlooping).

Auto-reboot ticked: Didn't boot keep bootlooping.

Was on Anarkia aokp rom after a theme flash that works cause initial cm7 .tar then Devil (the same I was using when it happened) and it booted fine.

What informations could i get while in cm7 cwm menu,mounted sdcard and adb connected?
[Galaxy S I9000 Android Development] mdv53:
I use cm9 last build 08-05-2012, i use the 3 button to get into recovery mode but nothing happend. Only what works, is download mode. The phone doesn't boot normally.

The only thing what works for me, i did a clean install with odin(jvu firmware), install a kernel with cwm recovery.
[Galaxy S I9000 Android Development] stratosk:
One more question:

Did this test version caused the bootloops or you already had the issue?
[Galaxy S I9000 Android Development] mdv53:
I already had the issue, i install the normal semaphore kernel. After a while, the phone reboot and i lost my recovery. Than i use the odin(.tar) version but no luck
[Galaxy S I9000 Android Development] mialwe:
Done :).

In case MNICS users do want to test his: http://xdaforums.com/showpost.php?p=25875892&postcount=900
[Galaxy S I9000 Android Development] franklin01:
Seriously this is awesome !

I got stuck in a bootloop and lost recovery, then I flash 1.1.2s tar trough odin and I got back the recovery.

What happened:

Rom -> ICS333 RC1.1

Kernel -> semaphore 1.1.0s

Modem -> JVU

I flashed modem KF1, cleared dalvik cache and fixed permission.

Everything is fine.

I flashed modem KB3, cleared dalvik cache and fixed permission, then bootloop no recovery.

I flashed semaphore 1.1.2s tar, still bootloop but I got the recovery.

I flashed the rom upon it (I always got 3 or 4 cwm rom on my SD just in case, I am a serial flasher) and everything is fine.

The strange thing is that I had KB3 modem last week and it was fine, I went back to JVU to test connection speed but changing again was too much maybe.

Any idea about what happened here?

Anyway thanks a lot for this fix, I was watching the thread since some time and suddenly I have to use it.

Keep it up guys.
[Galaxy S I9000 Android Development] Bejda:
We're still living what seems to be random behaviors,semaphore .tar didn't get my recovery back but initial cm7 yes as always.Just had to flash any ics kernel zip after and reboot to get back to my starting point (+the theme that "gaves" me bootloops,so clearly wasn't his fault).

By the way i always get recovery back with cm7 one but never successful with fixrecovery.tar.

Is there differences in the way they are build?
[Galaxy S I9000 Android Development] miquelsayeras:
Good! semaphore 1.1.2s works for my bootlop and lost recovery problem.

My rom was slim 3.5, the botloop begans after wrong update process to 3.6, i wipe dalvik-cache, and cache and after that I wrogly restart without flash 3.6 new slim rom (base+essentials). After that botloop appears

The solution that works for me:

flash semaphore 1.1.2s

remove battery

start recovery (now works!!)

wipe all and flash 3.6 slim rom

All ok
[Galaxy S I9000 Android Development] Bejda:
Not sure you had to do the last "wipe all and reflash slim" step,seing that recovery was back just reboot could have been enough.

That's one of the point of those semaphore and mnics .tar versions:not having to reflash another kernel after recovery's back like with initial cm7 or fixrecovery.tar and consult their logs.
[Galaxy S I9000 Android Development] Bejda:
Hey there's something strange i had two times now,it seems i'm going into bootloops with lost recovery but finally boot...

The second time happened just now,i was trying desperatly to test semaphore or mnics .tar ;) then i did dalvik-cache wipe and reboot.

This is how it goes:samsung galaxy s logo>devil boot image...>back to sgs logo (yeah i got my bootloops! :p )>Devil boot image>....surprise!bootanimation starts...

The last-kmsg talk about this,i hope there's something that can help:

http://db.tt/hHmivID7
[Galaxy S I9000 Android Development] Mr0czny:
eh and another bootloop

phone on AOKP m5 and Devil 0.79 XL, upgraded to b35... system starts on Glitch kernel, reboot to recovery and flash devil again... bootloop,

Instaling JW5 via ODIN, semaphore 2.7.4 kernel everything went OK, back to CMW installin AOKP b35, bootloop on glitch...
[Galaxy S I9000 Android Development] Pungi:
Flash the new midnight with odin.

Inviato dal mio GT-I9000 usando Tapatalk 2 Final
[Galaxy S I9000 Android Development] hadess18:
Best Solution!!

Hello guys! After lots of research i've finally found the best solution for this problems. It works with any kernel, in the ZIP version also

THE SOLUTION IS HAIMDALL:

get it here : http://www.glassechidna.com.au/products/heimdall/

1.get your favorite kernel, the zip archive. Open it and extract boot.img

2. Install Heimdall.

3. Start your Galaxy in Download Mode

4. Run zadig.exe and install the correct drivers.

5. Put boot.img in Heimdall file.

6. Open cmd.exe, go to c:\heimdall (or where you put it)

type :

heimdall flash --kernel boot.img

This will overcome the bootloops and you will NOT loose any information on the phone, such as apps etc.

Hope it is useful!
[Galaxy S I9000 Android Development] habylab:
Trying this out for you for the hope of the improved boot time that mialwe mentioned!
[Galaxy S I9000 Android Development] shaarky:
What is the difference then flashing with Odin?

And of there is really difference, does anyone has experience with flashing from Virtualbox?
[Galaxy S I9000 Android Development] hadess18:
with odin you can't flash only the boot.img(this is the part involved in the bootloops). And yes, i'm flashing from vmware virtual maschines, is working perfectly!
[Galaxy S I9000 Android Development] greasyguy:
another bootloop coming from Teufel

Ok guys, here is another bootlooping device:

onecosmics rc4.2

devils 2.0.79

After wiping cache and dalvik, bang! Bootloop.

Tried to flash new midnight via odin but still got bootloops.

Had to flash fix.recovery via odin and devils kernel afterwards.

Now its all good. :cool:

EDIT:

Maybe this helps in some way

http://dl.dropbox.com/u/16538237/last_kmsg.txt.bak.zip

http://dl.dropbox.com/u/16538237/last_kmsg.txt.zip
[Galaxy S I9000 Android Development] stratosk:
I can't check the logs right now, but I have on question:

Did you have access to recovery after flashing midnight?
[Galaxy S I9000 Android Development] greasyguy:
Tried about three times an no go :(
[Galaxy S I9000 Android Development] Bejda:
If it helps they should appear as "in-Web". txt that way:

http://db.tt/G3Tmbwup

.bak:

http://db.tt/xQnVeenl
[Galaxy S I9000 Android Development] Mangus_U*RA:
tried but it did not help...

Still have bootloops :(

no recovery access.
[Galaxy S I9000 Android Development] Bejda:
@ Mangus_U*RA,

Didn't help me too (semaphore one) the last time i had bootloops but they've been positives reports too... seems we're still living randoms behaviors even with new initramfs at least for the "recover from btloops" side.
[Galaxy S I9000 Android Development] hadess18:
I would sugest you guys to use the boot.img from the same rom you have previousely installed .

Just unzip the rom or just the kernel zip file and you will find the boot.img inside. Then usebthe procedure described by me here to flash the boot.img file. It shouldbwork
[Galaxy S I9000 Android Development] stratosk:
Hmm, I don't think that there are random behaviors.

I believe that there are different cases from bootloops and different interpretations from people about bootloops.

But I'm optimistic that finally we will find the cause.
[Galaxy S I9000 Android Development] mialwe:
Please remember that flashing a boot.img only does not install the correct kernel modules. One would have to flash an CWM zip or one of the new Odin/Heimdall flashables to get 1) kernel and 2) matching kernel modules.
[Galaxy S I9000 Android Development] Bejda:
We could say the real thing to be investigated is when bootloops (device boot>kernel boot>device boot>etc...) with no more recovery access (we should really state a shorter name to describe this :) ) happens on a simple reboot without any system changes (init.d, wipe or whatever).

This could includes reboot to recovery or flash something that sure works cause we can boot fine with it after recovery recover process (new initramfs or cm7 initial or fix recovery. tar followed by another or even same kernel that did have bootloops).

It's just the wipe dalvik-cache that gives btloops greater probability that is unclear for me as it could be an independent from our concerned phenomena?

But it's still the better working way to produce what seems to be same or closest btloops process (at least we have same consequences).

On another-other side i'm still wondering if that case couldn't be in any way related to our concern :o

At least the log says something, don't know what but...
[Galaxy S I9000 Android Development] stratosk:
I don't know, but I had the feeling (maybe I'm wrong) that we are not looking for 1 issue only...

Since, I could not reproduce a bootloop with a specific procedure I can't be sure what is happening.

I checked the log you sent but I didn't respond because I couldn't explain the error message there.
[Galaxy S I9000 Android Development] pbecks1963:
How about cwmless kernelloop? (or cl-kl for short)
[LG Nitro HD] Namuna:
Since the issue has officially been acknowledge, I thought this subject warranted a new thread.

In a nutshell, our Nitro's built-in Compass is screwed-up (at least a bunch of us Nitro owners). It was reported to LG in their official Forum and it seems they've finally official acknowledged the issue exists AND they've been able to reproduce it.

Now, some folks might dismiss this saying they don't do any hiking so the compass isn't that important an issue...BUT you should know the compass does a LOT more than just points an arrow north on a compass app!! Not the least of which is giving you a heading in your GPS app while you're not moving. Or if you like the Google Sky app, it's pretty much hosed without a properly working compass

LG's Official Forum page:

http://support.lgforum.com/lg/topics/lg_nitro_hd_compass_doesnt_work

Here's a previous thread on the matter:

http://xdaforums.com/showthread.php?t=1407840
[LG Nitro HD] zed011:
My telus optimus lte p935 has the problem too
[LG Nitro HD] hereric:
I hope they come up with something soon... either give us all Optimus LTE 2's, or our money back :P
[LG Nitro HD] zed011:
It's LG, they'll do nothing :o
[LG Nitro HD] typhoonk:
any update yet?

is it a software issue? or HW?
[LG Nitro HD] mast3rvo:
I had the weird compass issue too (it was always spinning in circles)

I just downloaded the app: GPS Status & Toolbox from the Google Play store and used its "compass calibration" and "pitch and roll calibration" tools. Now my compass works fine :)

Note: You might have to do the compass calibration more than once. What I had to do was: compass calibration, pitch and roll calibration, and then compass calibration one last time. Was connected to GPS also if that makes a difference. YMMV
[LG Nitro HD] typhoonk:
still doesn't work.

calibrate and it work ok for a couple of minutes - then it's back to being 120 to 180degrees off, which makes for a use less compass, very anouying gps (keeps redirecting because of wrong pointing direction), and other apps that use this. just sucks.

thought the new Telus update would fix it, but it kinda made it worse. So I think it is indeed a hardware fault.
[LG Nitro HD] nightlimits:
Tried the app and it worked for me. Still testing to see if it sticks but its worth a shot.
[Asus  Eee Pad Transformer Prime] chivas228:
I have a 4G Clear mobile USB stick. I am wondering how to make use of this device so I don't have to tether my cellphone's 3G connection. Is there some sort of configuration I have to do to make it work? Is this configuration also universal for A500? My uncle has the A500 and would also be interested in doing it with his since his tablet has a usb built into the tablet. Thanks in advance!
[Galaxy Tab Q&A, Help & Troubleshooting] mattyhank:
Hello everyone, I have been scouring the internet/forums for a fix for this and can't find one yet. Somehow something got messed in my CM9 when i tried updating(was working great for some time). I am trying to get back to stock but this error message (see link below) keeps coming up. I have tried odining and heimdalling every stock rom I can find with both repartitioning and without, but i keep getting this screen. If I hit home it acts like it is going to boot (sprint splash and Samsung glow) but it just loops. Any help would be MUCH appreciated.
[Galaxy Tab Q&A, Help & Troubleshooting] davidgar:
I'm on the same boat

let me just add that after trying to flash a rom from teamovercom

I bricked my tab,

yes bricked, did not get the battery icon anymore

so I had to load bootloader thru JTAG

then I reloaded stock EA24 from one-click heimdall but got back to the exact same spot,

my tab keeps looping

not sure what to do anymore

hope someone can help :(
[Galaxy Tab Q&A, Help & Troubleshooting] zackdakiss22:
SO IM VERY VERY NEW TO THE FORUM AND IT IS FOR THIS SAME EXACT REASON... I CANT SEEM TO GET PAST THE BOOT LOOP THAT IM STUCK IN FOR MORE THAN A WEEK NOW...

i am using a SPRINT Samsung Galaxy Tab 7.1 model#: SPH-P100... im sure it had all the stock info on it and maybe a regular update or two, but it has never been rooted or flashed until i started trying to mess with it.

THE ERROR MESSAGE I GET IS:::

E: can't mount/dev/block/mmcblk0p1

(no such file or directory)

E:can't mount CACHE:log/recovery.log

e:can't open CACHE:log/recovery'log

E:can't mount /dev/block/mmcblk0p1

(no such file or directory)

i have used both ODIN and HEIMDALL and i havent gotten any further than the samsung screen flashing...

here are some of the tools that i have used over and over again until i couldnt tell you what is now flashed on the Tab, but i know its not working!!!

heimdall-suite-1.1.1-win32

heimdall-suite-1.3.2-win32

ODIN 1.7 (3 different versions)

Odin3 v 1.85

odin ef17 GINGERBREAD

here are some of the ROMS i have used as well:::

SPH-P100.EF17.SECURE.REV07-FULL

tab_sprint_noModem_20101226

etv-rom-v7-1-20111203-sprint-cdma

Quens_P100_EF17_ROOTED_PDA

Sprint Galaxy Tab EA24 Flasher Odin

stock-ef17-odin-tar-pkg

stock-ef17-kernel-root-cwm-v2

i have the drivers for SAMSUNG composite device and i also got Zadig drivers for when i use Heimdall...

i have tried all of the following post to help me but it seems none of them can get me on the right path as well as with alot of these post being older and files uploaded to multiupload.com and so now i cant get some of the other files that may be needed so if you could please assist me... i would highly appreciate it!!
[Galaxy Tab Q&A, Help & Troubleshooting] yappoe:
Please do another flash using ODIN to a ROM that you are familiar with, with these additional steps:

1. Download a pit file for your ROM (look around you will find one, if not use the pitfile attached with ODIN when you downloaded it).

2. download dbdata.rfs.rar (look around on XDA you will find one).

3. Flash your rom putting the rar (or md5) on PDA, and put your downloaded PIT file on PIT field. this will automatically check the re-partition option and that's what you want to have.

Click on Start.

4. After flashed, you will still be stuck on Samsung logo,.. go to download mode again, connect to ODIN, put your dbdata.rfs.rar to PDA field, click on Start.

once you are done, reboot to recovery mode, wipe cache and factory reset.

you should be all set.