Database Develop

Please help! Galaxy S plus I9001 stuck booting into recovery *Fixed* :)

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.

bootloop after battery removed (LT5)

Firstly : my note get its usb outlet broken
So I can't charge it neither send data trhough the usb
I can't use Odin
I'm on the latest LT5 stock rom, never flashed any mod (none to date)
I've installed this rom with Mobile Odin 3 days ago, with no problem at all
Yet, I just take out the battery (after having turned off the phone) and set another one
And my phone became to bootloop..
So I entered the recovery mode (which is not a fully custom recovery, there was not Nandroid backup mode...)
After a cache wipe : still bootlooping
So i've done a Factory Reset / full wipe and the phone restarted normally
But I loss all my data
What to do ? I don't want this to happen again...
sorry for bad english

Always take a backup using an app like Titanuim backup and copy the back-up files to the PC. Make sure you flash ROMs and kernels properly according to the thread.

But I've flashed nothing !!
I've just turned it off then on...

you flashed LT5 stock ROM, there must have been some issue there, flash it safely again with proper procedure. bootloop is mostly due to incorrect flashing. i advise you to flash the ROM on PC ODIN. I had installed a kernel some days back with mobile ODIN and had gotten into a bootloop which vanished after i flashed a new ROM. So better get the USB port work and flash using PC ODIN as far as possible.

I can't flash via odin, as my usb output is dead

that's what we call "Bootloop Bug" on official JB...simply flash any custom kernel for JB4.1.2.. try philz kernel,

Thanks, I will try

[Q] NANDROID restores: TWRP won't boot, CWM corrupts data

Sorry for this being lengthy, I wanted to make sure I gave enough info.
Neither of the two most popular recovery tools are working for me. They both state the backups are successful but the restores have flaws. Is anyone experiencing the problems I am? If so, does anyone know what to do about them?
CWM Recovery Touch (and non-touch): Data restores leave certain things not working. I'm not sure what processes are stopping because it flashes and disappears to fast. I know that it causes the ROM Manager for CWM, Titanium Backup Pro, Google Play, and likely more to crash (disappear) immediately upon opening. Chrome browser *might* bright up the keyboard on the first click but it won't work then it will disappear and not come back (but the keyboard does work in other areas, I use Swype Keyboard). I've tried clearing cache and/or data on all 3, uninstalling them then re-installing via APK and various other things. This occurs regardless of whether a factory reset (data/cache) wipe is performed before the restore. However, if I restore with CWM Recovery *then* do a factory reset, Google Play will work and nothing crashes, nor are their long delays.
TWRP does not boot after a restore. It will pass the initial screen showing the phone model, the phone carrier splash screen, then sit on Samsung with the LED solid bright blue and hang.
My goal is to simply trust my backups. The CWM Recovery problem is workable in a terrible situation since my Titanium backups will get my phone *almost* to where it was (barring widgets, which are pain to re-setup, and a few other things).
Titanium Backup Pro question: Is it normal when you remove a system app with Titanium Backup Pro, then do a restore in CWM for that app to still be gone? Since I use the Swype keyboard I removed the other once, did a restore with CWM, had the problem so I did a factory reset and my stock keyboard was missing still (I think it's a Samsung keyboard)
App Details:
CWM Recovery Touch 6.0.4.7 (for Samsung Galaxy S3 LTE (GT-I9305))
TWRP 2.6.3.0 (for Samsung Galaxy S3 LTE (International i9305))
Phone Details:
Carrier: T-Mobile (Germany)
Model number: GT-I9305
Android Version: 4.3 (stock from Kies, so I do have Knox and it's disabled via SuperSU 1.91 from chainfire)
Baseband version: I9305XXUEMK1
Kernel version: 3.0.31-2051278
Build number: JSS15J.I9305XXUEML5

Titanium Backup Pro question: Is it normal when you remove a system app with Titanium Backup Pro, then do a restore in CWM for that app to still be gone?
No a Nandroid backup wipes the phone .
make a Nandroid then in recovery format system sdcard data cache .
You now have an empty phone and restoring the Nandroid should return exact same state .
All this reads as you are doing something wrong .

JJEgan said:
All this reads as you are doing something wrong .
Click to expand...
Click to collapse
I hope it is as simple as that. I'm booting up in recovery mode (Volume Up + Home + Power) choosing the backup or restore option, then backing up to the External SD card. Then on the restore I'm doing the same except selecting restore from the SD card (I've re-created the CWM problem 5 times, once was with advanced restore of just data the rest were basic restores doing everything). I'm not really sure what I could be doing wrong.
I have the 4.3 stock ROM before I did any custom stuff to the phone (which installed KNOX). I used chainfire's tar.md5 auto root image with Odin 3.09 in download mode when I root the phone, and I've installed CWM Recovery with ROM Manager and with an Odin tar flash in download mode. The install of TWRP was from an Odin 3.09 tar flash in download mode too.
With regard to the TWRP and CWM Recovery, I'm not really sure how easy it is for me to have messed up that part. Do you have this same model phone? Is it possible KNOX is involved in my issues? Maybe I should downgrade one of the recovery tools?

Downgrade your recovery and try again.

jonesjw362 said:
Downgrade your recovery and try again.
Click to expand...
Click to collapse
That's what I was thinking might be the best solution. Since the flaw in the restores with CWM Recovery are workable for me, I figured I may just wait until I have a need to restore to do that though. Once I do, I'll probably do a bunch of tests until I find something that works solid.
I've already restored my backups and widgets etc. a couple of times and don't really want to do it over again only to test. If there's a way to restore all of that without my having to set it up myself then I'll do it. Right now my Titanium restores don't include wallpaper (except lock screen), most of my widgets (maybe all, can't remember), and I think there was one other thing.

Advanced restore in recovery restore data only .

JJEgan said:
Advanced restore in recovery restore data only .
Click to expand...
Click to collapse
I tried that once, that's why I believe the CWM Recovery issue to be specifically with data. I'm going to do it again right now though and if things are messed up again I'm going to try jonesjw362's suggestion.

Downgrading didn't help (6.0.3.6 had a constant barrage of 4-5 apps re-crashing over and over again during the process).
I tried the following with CWM Recovery Touch 6.0.3.6, 6.0.4.5 and 6.0.4.7:
Factory reset wipe, open and test Google Play (more things break but that's the one I chose to test). Reboot into recovery mode and backup to the SD Card (not the external). Immediately advance restored data only (no wipe). Booted up, Google Play crashed, rebooted back into recovery and factory reset (data/cache) and advance restored data again with the same result.
I didn't try a downgraded version of TWRP (probably won't for now). I'm back to 6.0.4.7 and restoring my backups to get my phone back fully. Hopefully CWM Recovery comes out with a new version sometime in the near future that works for me or someone has some insight into what I can do to fix it with the existing (I'm out of ideas).

Issue Samsung stock 4.3 ROM
I ended up switching to CM 10.1.3 (was going to hold off until 11 was stable) but the Samsung stock 4.3 ROM was destroying my battery. After switching, I tested a NANDROID backup and restore with CWM Recovery Touch 6.0.4.7 (same version I was having problems with). The restore worked as it should, no problems.
End Result: As far as I can tell, the cause of the CWM Recovery data partition problem is due to the Samsung 4.3 ROM.
Edit: I was going to mark the post Resolved but I can't seem to find the drop down to do so (at least not in the same place I thought it was).

[Q] zips and backups gone from TWRP file manager

please help me I am a newbie but I am NOT a dummy I rooted with towel route installed twrpcustom recovery as I was flashing last night when I did my wipe I look down and all my files were gone and all the zips all the backups and now I don't know what to do I got a guy on the way to buy the phone and I've got to restore it I have no computer help me .please. I can still get into twrp recovery. I just don't have a computer. I used flashyfi to install recovery.. And I can install SuperSU. But there is no is. Pleeeeeassse help..

If you don't have a computer I would recommend using a thumb drive and otg cable if you have one and use that to flash the ROM again.

xposed modules resulted in a bootloop - cant restore my nandroid either

hi all, i made an xda account because i really cant understand whats going on with my phone
HTC One M8 running Android 6.0 (rooted)
so after rooting my phone, i proceeded to install xposed.
i flashed the zip - no problem
i installed the apk, and after choosing 4/5 modules that i wanted, i went ahead and enabled them all and rebooted to activate them.
this is where the problems started. my phone booted, however it kept on flashing a screen with the deafult One M8 wallpaper at me. after a few seconds, it came up with an error "com.android.systemui has stopped"
not sure what was going on, i went to twrp and directly restored my nandroid backup, but after waiting for 15 mins, i realised my phone was in bootloop, so i went back to twrp and did a factory reset and restored my nandroid. but again, it went into bootloop. i tried factory resetting and restoring 3 times before giving up.
my phone isnt connecting to my laptop anymore either, but if i need to flash anything i can do it with my sd card.
im not a complete noob but im still learning and ive never not been able to restore my nandroid.
thanks in advance for any help i can get

chaitra26 said:
hi all, i made an xda account because i really cant understand whats going on with my phone
HTC One M8 running Android 6.0 (rooted)
so after rooting my phone, i proceeded to install xposed.
i flashed the zip - no problem
i installed the apk, and after choosing 4/5 modules that i wanted, i went ahead and enabled them all and rebooted to activate them.
this is where the problems started. my phone booted, however it kept on flashing a screen with the deafult One M8 wallpaper at me. after a few seconds, it came up with an error "com.android.systemui has stopped"
not sure what was going on, i went to twrp and directly restored my nandroid backup, but after waiting for 15 mins, i realised my phone was in bootloop, so i went back to twrp and did a factory reset and restored my nandroid. but again, it went into bootloop. i tried factory resetting and restoring 3 times before giving up.
my phone isnt connecting to my laptop anymore either, but if i need to flash anything i can do it with my sd card.
im not a complete noob but im still learning and ive never not been able to restore my nandroid.
thanks in advance for any help i can get
Click to expand...
Click to collapse
*. Flash xposed uninstaller zip and try booting your device. Link here - http://dl-xda.xposed.info/framework/uninstaller/
-->> use this» make a full wipe from recovery, then restore nandroid backup.
*.While restoring nand. from recovery, make a full wipe like wipe system etc.. Then restore your nand. Then you're good to go.

thanks a ton for your reply
i already tried flashing the uninstaller - didnt work
but ill try your second method. thanks once again

chaitra26 said:
thanks a ton for your reply
i already tried flashing the uninstaller - didnt work
but ill try your second method. thanks once again
Click to expand...
Click to collapse
Hey, the 1st one won't works, Cuz you'd already did a factory data reset, so that's gonna be won't work. And you'd tried restoring nandroid over that, so that's failed.
I hope second one will works.

sachin n said:
*. Flash xposed uninstaller zip and try booting your device.
-->> use this» make a full wipe from recovery, then restore nandroid backup.
*.While restoring nand. from recovery, make a full wipe like wipe system / data etc.. Then restore your nand. Then you're good to go.
Click to expand...
Click to collapse
Um i think i seriously screwed up - i deleted everything including system and data and stuff - but now my nandroid is gone
what can i do now i dont even have a nandroid!
oh my god my phone doesnt have an os anymore... what have i done wrong?????

chaitra26 said:
Um i think i seriously screwed up - i deleted everything including system and data and stuff - but now my nandroid is gone
what can i do now i dont even have a nandroid!
Click to expand...
Click to collapse
Deym!!
So, look at the One m8 forums, you'll get the workarounds.
I've found one here - https://forum.xda-developers.com/ht...k-twrp-t3086860?_e_pi_=7,PAGE_ID10,5801529172
@chaitra26, either DL any custom ROMs and flash it via custom recovery [Twrp].
Look here for custom ROMs - https://forum.xda-developers.com/htc-one-m8/development?
Regarding that '' no OS installed'' error, that's common when you try to reboot your device from twrp without installing any system images /ROMs.
FYI - when you full wipe your device and tries to power up you'll get the same warning.