Related
Hello guys, I've updated my SG+ to the latest firmware (XXKQ1) using ODIN over my old firmware (I didn't want to lose any settings/apps, sorry noob). My phone just started giving me forced app ending errors and now it's stuck in the bootloop (animation).
Any sugestion would be helpful! I would love a solution that would not require a total wipe of my settings/pics/etc.
try to get in download mode again by pressing volume button down, home button and power button. Open Odin select the firmware you downloaded as onepackage file and flash again but i think your pics and stuff like that will be gone.
Usually it should boot normally after a flash, without resetting anyway. But it helps in 90% to reset your device, maybe it doesn't boot up because you didn't resetted it. So im sorry to say that but I think you have to do that, or flash the firmware you had before..
For resetting you can go into the recovery mode (by pressing vol+ and power button, then when the "android out of the box" appears release these buttons and press the menu softbutton), then choose wipe data/factory reset or something like this. ^^
This doesn't seems to be solved.
I have the same problem, I did factory reset, formatted /system, wipe cache, dalvik, after updating I fixed permissions, but the phone is still on bootloop.
I did: RemICS 1.3 and CyanogenMod 9 with CWM 5.5.0.4. Always bootloop.
http://forum.xda-developers.com/showthread.php?t=1735976
Any help?
The only ROM that is working is the original one from samfirmware.com.
I'm sorry for post under the post, but I wanted to go this topic to the top, so anybody with this issue would see it.
I have tested one solution and it help with me:
Before uploading CWM into the Phone, format external sdcard. After that upload on external sdcard the zip archive with ROM and upload CWM with Odin.
After going to recovery mode and installing the ROM (I uploaded RemICS 1.3a), everything work just fine.
bootloop
Check this out ....androidtuition.com/fix-boot-into-recovery-problem-after-flashing-twrp-galaxy-s-plus-i9001
i was able to fix the cwm bootloop issue using ODIN and the boot tar file from the link above.
sridhar2malladi said:
Check this out ....androidtuition.com/fix-boot-into-recovery-problem-after-flashing-twrp-galaxy-s-plus-i9001
i was able to fix the cwm bootloop issue using ODIN and the boot tar file from the link above.
Click to expand...
Click to collapse
I still have the same problem after flashing the boot_loader.tar using ODIN
Since about a week I'm having the following problems:
It is extremely difficult to get my phone running ICS. I tried like 10 different ROMs, the only one currently working is Dark Knight. In between I managed to run CM9 Nighlty (2 days) and Infinitum 2.2 (3 days)
Why is it so difficult? Well - I believe, I'm doing all the correct steps: Flashing JVZ with Odin, rebooting, flashing CF Root, rebooting. Enter CWM, wipe data, cache, dalvik, format system -> Install any ICS rom
Currently, CM9 doens't work at all, I get boot loops after the initial reboot and can't enter recovery
Well, when I finally manage to install any rom (method: install Dark Knight - 5.5 atm - install any rom afterwards - my phone boots up correctly and is perfectly usable
But: Whenever I reboot, I keep getting boot loops with no chance of entering recovery. None of the usual methods work.
Stupid thing: I don't need to reboot. But every other day the phone tends to reboot itself (at least that is what I experienced and sorta guess)
Result: I take it out of my pocket or look at it on my desk and see boot loops after 2 or 3 days
What can I do, why is that? I don't want to run Gingerbread
I am not a noob - I have been running any rom before for one and a half years without problems and flashed mostly without any problems
Believe me - I have tried everything for several days. Flashing the recovery fix with Odin doens't help either. Afterwards I am a able to boot intro recovery but can't install any rom due to build.prop errors. However, I can flash a kernel... Result: boot loop. Solution: Start over with Gingerbread and Odin
The more I think about it, the more I belive there could be an underlying hardware problem. Maybe something with the internal NAND?
I am greatful for any help or new ideas which I haven't tried so far... Thanks a lot in advance!
I know it's a long shot, but maybe you have issues with datadata folder? Use root explorer and see how much free space you have there...
Maybe try this:
After Odin, When in CWM, flash first a new kernel (try devil.072). Make sure to mount folders with CWM before. After flushing, go to advanced and reboot recovery. Now you have a new version of CWM (which supports screen tuch...). Now, from mounts and storage, format everything. Now flush the rom you want - in this case, I recommend Slim 3.4. Don't install anything yet - just let it run after flushing. Just login to your google account.
See if it works.. hope it helps
Thanks a lot! Unfortunately, it didn't work.
I tried your method which didn't even end up in a bootloop but in recovery after every flash/try to reboot.
/edit: Speaking of reboots - I tried to install CM9 afterwards/instead -> boot loop
Hmmm u have a interesting problem. Do u wipe everything and have u tried starting from a different stock gb
If you like my posts hit thanks
Rom: Dark knight 4
Kernel: Devil Kernel
Keep it ANDROID!!!!!!!!
Yes, I wipe everything and tried JVZ and JVU as a starting point. Are there any other recommendations?
which firmware are you odining? maybe bad download?
Bara2 said:
Thanks a lot! Unfortunately, it didn't work.
I tried your method which didn't even end up in a bootloop but in recovery after every flash/try to reboot.
/edit: Speaking of reboots - I tried to install CM9 afterwards/instead -> boot loop
Click to expand...
Click to collapse
Just try it again but do NOT select reboot recovery. It is a common bug that you won't be able to leave recovery again. Just reboot the phone and be sure to quickly press 3 button combo again to get into recovery again. You should then be able to format / reflash and so on. Just make sure you never select reboot recovery when you just came the long way from odin. In doubt just do as I stated: normal reboot and press 3 button combo quickly.
Good luck!
shaharofir said:
which firmware are you odining? maybe bad download?
Click to expand...
Click to collapse
I agree many try a firmware from stock firmware from xda
If you like my posts hit thanks
Rom: Dark knight 4
Kernel: Devil Kernel
Keep it ANDROID!!!!!!!!
swent said:
Just try it again but do NOT select reboot recovery. It is a common bug that you won't be able to leave recovery again. Just reboot the phone and be sure to quickly press 3 button combo again to get into recovery again. You should then be able to format / reflash and so on. Just make sure you never select reboot recovery when you just came the long way from odin. In doubt just do as I stated: normal reboot and press 3 button combo quickly.
Good luck!
Click to expand...
Click to collapse
Ok, That shall be my next try Btw: Another strange effect: I flashed Dark Knight 5.5, did nothing but click through the setup assistant rebooted - and voilà - boot loop.
Will report back in a few minutes Thanks a lot, guys!
/Edit: Well - a litte success... I was able to boot into the system. First thing I did was change lcd density and rebooted - everything was fine. As I didn't have wifi or data connection I wanted to flash another kernel (devil) and hit reboot recovery from the power menu.
--> Boot loop again.
To the other guys: I tried JVU and JVZ with different downloads and two different laptops. Which starting base should I try next?
/Edit2: I'm going to stay on Gingerbread for the day. I need my phone and intend to enjoy the fantastic weather for the rest of the day... Will be back this evening. I am glad for further feedback and ideas
Bara2 said:
Ok, That shall be my next try Btw: Another strange effect: I flashed Dark Knight 5.5, did nothing but click through the setup assistant rebooted - and voilà - boot loop.
Will report back in a few minutes Thanks a lot, guys!
/Edit: Well - a litte success... I was able to boot into the system. First thing I did was change lcd density and rebooted - everything was fine. As I didn't have wifi or data connection I wanted to flash another kernel (devil) and hit reboot recovery from the power menu.
--> Boot loop again.
To the other guys: I tried JVU and JVZ with different downloads and two different laptops. Which starting base should I try next?
Click to expand...
Click to collapse
Umm well I use jvu and have no problems. This might sound stupid but when I had a similar prob (I flashed a kernel on dark knight 4 and got into a bootloop and couldn't enter recovery) I did a factory restset after backing up my SD card data and flashing jvu, then I reflashed jvu. Rooted, wiped rebooted recovery, wiped again, rebooted recovery again, then I flashed dk 3 then dk 4 without a wipe, the restored my apps and copyed my SD data back - I hadn't been able to flash a rom since the bootloop I got it working with dk 3 but then I got no boot animation and I just stopped there, the above process worked for me I know u on dk 5.5 but try dk 3 you should find the link in the dk thread around April 12-16 this year.
If you like my posts hit thanks
Rom: Dark knight 4
Kernel: Devil Kernel
Keep it ANDROID!!!!!!!!
You may flash the new kernel right away after flashing the desired rom. Maybe that would stabilize everything... can't make any more sense of it right now, sorry :/ Maybe you could try to use the ultimate kernel cleaning script AFTER flashing the rom and BEFORE flashing the new kernel (with no reboot in between).
Script is somewhere out there, I'm gonna search it right now...
/EDIT: Wasn't really hard to find after all, there you go: Ultimate Kernel Cleaning Script
try this firmware for odin:
https://www.sugarsync.com/pf/D6246658_3937073_82911
Hi folks,
I tried updating my S plus to ICS today by following the instructions listed here:
theandroidsoul.com/galaxy-s-plus-i9001-ice-cream-sandwich-update-install-cyanogenmod-9-cm9-pretty-good-and-working-rom
I read through the instructions and it looked pretty simple. I successfully installed Team Win recovery, performed a backup, wiped, and then installed the CM9 rom.
After the installation, the phone just boots back into Team Win recovery. I tried reverting to the backup, but it still just boots to recovery every time.
Now that I'm stuck in TeamWin recovery, I'm at a loss on what to try next .
Does anyone have any insight on how I can fix the problem?
Thanks,
Evan
Sometimes when you flash new Recovery (usually when replacing stock recovery with modified recovery for the first time) you get stuck at bootloop. It means /boot partition was damaged. After flashing TWRP did you restart your phone and it booted correctly, or did you install everything (TWRP, got backup, wipe and install new ROM) at once?
There is a guide for i9001 bootloops
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001#Boot-loop
divibyzero said:
Sometimes when you flash new Recovery (usually when replacing stock recovery with modified recovery for the first time) you get stuck at bootloop. It means /boot partition was damaged. After flashing TWRP did you restart your phone and it booted correctly, or did you install everything (TWRP, got backup, wipe and install new ROM) at once?
There is a guide for i9001 bootloops
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001#Boot-loop
Click to expand...
Click to collapse
So is reflashing in Odin what you are suggesting? Sorry if I'm misunderstanding.
And yes, after I flashed TWRP it booted fine, the 2nd time I went into recovery, performed the backup, wiped, then flashed the rom. I've tried wiping both the cache's with no success. I've also tried reflashing the rom, wiping the cache's, restoring with the backup, wiping cache's again... nothing seems to be working
What would be different if I had installed everything (TWRP, backup, wipe, rom) at the same time?
*Edit* Reflashed through Odin and it worked great! Thanks for the help, I'm a little scared to start messing with the phone again, but ICS is tempting...
Got the rom working with a fresh backup after fixing the bootloop. Thanks again for the link divibyzero, the troubleshooting steps solved the problem, whatever it was, and now its running ICS
These Samsungs S+'s seem to be a little more finiky than my HTC.
I am still stuck in CWM Recovery mod ! When I start Download mode, I dont have ODIN option ..only Download mod start screen! Can anybody help me?
Dapper SRB said:
I am still stuck in CWM Recovery mod ! When I start Download mode, I dont have ODIN option ..only Download mod start screen! Can anybody help me?
Click to expand...
Click to collapse
What do you mean by "don't have ODIN option"?
Is bootloader.tar which used to repair bootloop problem usable on ICS roms for SGS+??
alireza7991 said:
Is bootloader.tar which used to repair bootloop problem usable on ICS roms for SGS+??
Click to expand...
Click to collapse
yup, you can use bootloader or http://forum.xda-developers.com/showpost.php?p=32655216&postcount=17 CWM with AriesVe.ops
evan8683 said:
Hi folks,
I tried updating my S plus to ICS today by following the instructions listed here:
theandroidsoul.com/galaxy-s-plus-i9001-ice-cream-sandwich-update-install-cyanogenmod-9-cm9-pretty-good-and-working-rom
I read through the instructions and it looked pretty simple. I successfully installed Team Win recovery, performed a backup, wiped, and then installed the CM9 rom.
After the installation, the phone just boots back into Team Win recovery. I tried reverting to the backup, but it still just boots to recovery every time.
Now that I'm stuck in TeamWin recovery, I'm at a loss on what to try next .
Does anyone have any insight on how I can fix the problem?
Thanks,
Evan
Click to expand...
Click to collapse
Hello guys,
I think have the same problem, this morning I installed the Team Win recovery and after a reboot my phone come into recovery mode and even after a furthr reboot I'm blocked in a bootloop that leads me always on Team Win recovery.
I tried to wipe cache, dalvik cache, factory reset and even a wipe of the system but nothing happen.
I reinstalled rom but without success.
There is a way to fix this through adb?
Advanced thanks for help
Max.
krisslake said:
Hello guys,
I think have the same problem, this morning I installed the Team Win recovery and after a reboot my phone come into recovery mode and even after a furthr reboot I'm blocked in a bootloop that leads me always on Team Win recovery.
I tried to wipe cache, dalvik cache, factory reset and even a wipe of the system but nothing happen.
I reinstalled rom but without success.
There is a way to fix this through adb?
Advanced thanks for help
Max.
Click to expand...
Click to collapse
You didn't specify, so I'll assume you have an i9001, if this is not the case, you probably shouldn't follow these instructions
Just reflash the bootloader as explained here (http://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330) and you'll be fine. I had the exact same problem when I had installed CWM on my own device. It's not with adb, but it's not like you have to do a lot of effort to get Odin or anything and it will fix your device.
Marshian said:
You didn't specify, so I'll assume you have an i9001, if this is not the case, you probably shouldn't follow these instructions
Just reflash the bootloader as explained here (http://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330) and you'll be fine. I had the exact same problem when I had installed CWM on my own device. It's not with adb, but it's not like you have to do a lot of effort to get Odin or anything and it will fix your device.
Click to expand...
Click to collapse
Luckily I found a windows system
Istructions you report was perfect for my case...seem I solved my problem...thanks again.
There is some i need to do for report I solved my problem ?
Bye Max.
[Boot-Loop] Can I use dd to flash bootloader?
Guys, has anyone tried to use dd to flash bootloader partition?
I assume dd if=boot.img of=/dev/block/mmcblk0p8 bs=512 should work
Can somebody attach boot.img taken with dd so I could test?
error - can t acces system csc/cnx/system
hello. I have a problem. I had installed on the phone cm10. Now I switched to cm 9 but since we locked in botloader and I returned with odin. recowery mode now you did not have the option install from sd / card only update. My problem is that now go phone but I can not install gapps. ie install it says the installation is complete, restart give when I see me many times with yellow writing including my error appears so: can t access system csc / CNX / system. and after I start the application from google. to say you've tried many variations and if you try recovery-clockwork-5.5.0.4-phone crashes every time. Please help ... (I tried many variations of gapps). thanks in advance.back with another caveat: any clockwork I try to install say installation aborted. and in the recovery mode screen down to write I / / / status = 0 / / /
evan8683 said:
So is reflashing in Odin what you are suggesting? Sorry if I'm misunderstanding.
And yes, after I flashed TWRP it booted fine, the 2nd time I went into recovery, performed the backup, wiped, then flashed the rom. I've tried wiping both the cache's with no success. I've also tried reflashing the rom, wiping the cache's, restoring with the backup, wiping cache's again... nothing seems to be working
What would be different if I had installed everything (TWRP, backup, wipe, rom) at the same time?
*Edit* Reflashed through Odin and it worked great! Thanks for the help, I'm a little scared to start messing with the phone again, but ICS is tempting...
Click to expand...
Click to collapse
Hi Evan which release of Odin did you use I am also facing the same problem for the past 28 hours and not been able to resolve it. The problem is thay the Com Port does not pop up basically the phone is not being recognised by the computer.
Please help.
sunbaj said:
The problem is thay the Com Port does not pop up basically the phone is not being recognised by the computer. Please help.
Click to expand...
Click to collapse
You must properly install Samsung mobile drivers on your PC, kill Samsung Kies process (or even better: uninstall Kies) and enable USB debugging on your phone. Then it will work.
tetakpatak said:
You must properly install Samsung mobile drivers on your PC, kill Samsung Kies process (or even better: uninstall Kies) and enable USB debugging on your phone. Then it will work.
Click to expand...
Click to collapse
The problem was that I was using Windows 8. I was able to resolve the issue after doing it on Windows XP.
Okay so I searched on this forum to see is there a post similar to mine, but couldn't find a fix to my problem..
So, three weeks ago I rooted my device, installed cwm and everything that was needed, and I did it. The same day somehow i rebooted with ROM Manager, and I couldn't get out of clockworkmod, and I don't know how (probably by some other tutorial on this forum for rooting, I flashed clockworkmod-jena.5.2.0.8.tar.md5 via Odin3 v1.85 , instead of clockworkmod-5.0.2.8.tar.md5 , and i somehow managed to get into normal mode again... Everything was working till today, when I got a notification about some software update, and when I pressed the Reboot button, it booted into recovery and I can't get out of cwm for three hours now.. I tried the stuff i did the last time - no result. I restored data from my previous backup, still no result. I formatted data and cache, again no result. Downloaded a Stock Backup.zip file, and again it boots in cwm. I really need your help about this, I don't know what I'm doing and I don't wanna do something bad and brick my phone..
Thanks, I hope I'll get a reply :S
download official stock firmware from http://www.sammobile.com and flash it via odin, and don't use cwm manager again:good:
Hi everyone
First of all a little history:I used this [PhilZ-cwm6][n7000] v4.93.6 Safe Stock Kernel+CWM6+Root+exFAT+ext4-LT4 to root my n7000 on 4.0.4 (I bought it with 4.0.4).
Then after some time Android wanted an upgrade to 4.1.2 and after some time I just tried it and it failed after booting into recovery mode, because it didnt find a the expected kernel, I think. But I had the chance to boot up again.
OK I then did the update with Kies-Software and everything worked again. Then I rooted the phone again using the same method as mentioned in the post above.
Now today the phone wanted to update again, I thought, OK, if it didnt fail completely the first time, it will fail in recovery mode and let me boot up again.
But...
This time it went into recovery mode and didnt let me boot up again. It just shows the robot with the crystal and the progress bar seems to move a little but then the screen goes black for a second and the robot returns and the progress bar moves a little and the same again.... I dont get into the recovery menu.
I tried samsung kies emergency recovery, it doesnt find my n7000.
I tried to flash the kernel with a newer version from the post above. (I am not allowed to post there). No change it gets stuck in broken recovery mode.
I can push volumedown power and home to get into the download mode.
My question is what can I do?
Is there any other chance to avoid a complete stock recovery (is that the right term/way)?
What do I have to flash and how?
I am a little worried about the brick issues and I dont know which version I have to flash to set it back completely...
Please help & thanks
drz
No worries, since your download mode is still working you can flash a stock Samsung ROM via odin. Download one from here and flash it in odin while in download mode. Latest at this point of time is LT4 http://forum.xda-developers.com/showthread.php?t=1424997
This will give you the stock JB Bootloader, Recovery, and ROM. Its completely unrooted though, and the phone will not be wiped in the process, so remember to do so after you flashed it.
cr0wnest said:
No worries, since your download mode is still working you can flash a stock Samsung ROM via odin. Download one from here and flash it in odin while in download mode. Latest at this point of time is LT4 http://forum.xda-developers.com/showthread.php?t=1424997
This will give you the stock JB Bootloader, Recovery, and ROM. Its completely unrooted though, and the phone will not be wiped in the process, so remember to do so after you flashed it.
Click to expand...
Click to collapse
Thanks a lot, crownest!
I sweated a bucket of blood and seat, because I couldnt wipe cache and data first, but it worked!!!
Everything looks like before!´the update!
Some more questions (sorry):
do you think I should wipe cache and data now?
Is a stock rom like the rom on internal usbcard only?
What about the update? Can I update safely now?
Thanks again for helping...
greetz
drz
Yup you should be able to wipe cache and dalvik with no issues now.
I believe all ROMs be it stock or custom installs to the NAND memory (Someone correct me if im wrong) and never on your internal/external SDcard
As for OTA updates via Kies, I dont see why not, but if the same issue does reoccur again then my suspicions would point to a possible NAND corruption on the device. Not sure if there is a fix for that, but its a risk you gotta take. Or you can always root the phone and flash custom ROMs as new builds get released, this way you'll never have to use OTA updates again.