Database Develop

Galaxy Mini Stuck at bootloop!

Guys i've bricked my phone once already with this damned app called ROM manager, luckily the samsung guys replaced the motherboard, but it was loaded with dreaded stock 2.2 FW after much thought i decided to upgrade it back to 2.3(i've done it many times) but suddenly somethin went wrong! Odin displayed pass message but my galaxy mini won't boot beyond the samsung logo!
i cleaned cache through recovery console but no use, reflashed with the same firmware damn it didn't work either. Finally i collected the courage to wipe data/factory reset through the recovery console n guess what it worked!!
bit i rele wanna know what caused the bootloop in the first place??

Sorry but wipe the base after the flash.
I am not surprised that he fell in bootloop. Me too this happened if I did wipe.

just reflash the firmware...if it doesnt work, try a different firmware...
i tried the asian version of gingerbread on my phone...and i had the same problem...but the european version worked for me...

try to wipe data/reset and wipe cache partition and also dalvik cache

After and before all ROM flashes you must wipe your data and cache. Everybody knows that.
You don't need to make useless threads that you fixed your problems or something, we don't need to know that.

SwankyShaan said:
Guys i've bricked my phone once already with this damned app called ROM manager, luckily the samsung guys replaced the motherboard, but it was loaded with dreaded stock 2.2 FW after much thought i decided to upgrade it back to 2.3(i've done it many times) but suddenly somethin went wrong! Odin displayed pass message but my galaxy mini won't boot beyond the samsung logo!
i cleaned cache through recovery console but no use, reflashed with the same firmware damn it didn't work either. Finally i collected the courage to wipe data/factory reset through the recovery console n guess what it worked!!
bit i rele wanna know what caused the bootloop in the first place??
Click to expand...
Click to collapse
It was because of your previous data and cache.... Wiping both data and cache solves the problem.

yagya said:
It was because of your previous data and cache.... Wiping both data and cache solves the problem.
Click to expand...
Click to collapse
If you read the first post, you'll see that he solved it himself.

he has asked the question because he clearly has not made the association between what he has done to fix the issue with what caused the issue.

SwankyShaan said:
Guys i've bricked my phone once already with this damned app called ROM manager, luckily the samsung guys replaced the motherboard, but it was loaded with dreaded stock 2.2 FW after much thought i decided to upgrade it back to 2.3(i've done it many times) but suddenly somethin went wrong! Odin displayed pass message but my galaxy mini won't boot beyond the samsung logo!
i cleaned cache through recovery console but no use, reflashed with the same firmware damn it didn't work either. Finally i collected the courage to wipe data/factory reset through the recovery console n guess what it worked!!
bit i rele wanna know what caused the bootloop in the first place??
Click to expand...
Click to collapse
That bootloop was caused because of errors that came when 2.2 data or cache was trying to load in 2.3. I might be wrong, but what else can it be?

SwankyShaan
Yeah it happened with the Asian version, we're supposed to clear the cache afta the upgrade right?
then I don't think its related with the cache it has to be with 2.2 redundant data I feel either way its such a pain clearing all the apps n data:-(

Hi
Mine is Gingerbread 2.3.4 on H3G.
First I rooted it, then installed CWM Recovery via Odin method, it gave PASS and things went ok.
Today morning going thru some threads came across the similar thread for CWM Recovery where it said to Wipe Data after install CWM Recovery, so I went in Recovery mode and wiped data and partition cache as well.
Now the problem started when I restarted the phone, it just wont pass Samsung logo and then back to 3 animation.
whats gone wrong, what should I do now.
thanks

Guys i've bricked my phone once already with this damned app called ROM manager\
ROM MANAGER DOESN'T BRICK IF YOU USE IT OVER CWM!!!!!!!

Stuck at "touch the android to begin"

This concerns my galaxy note n7000. I had a rooted checkrom v4 working on my note. I tried to install criskelorom v2 and got bootloops. I then tried to go back to stock via odin and flashed stock N7000 KL3 ROM which i had earlier used, I had to go to stock because after bootloop even recovery was not working. now after flashing stock i am getting a strange problem of the phone getting stuck at the welcome to gt-n7000 screen . "touch the android to begin" . nothing is happening after touching the android on the screen although i can change the language etc and even the pull down notification is also working but the phone is stuck at the initial stage. I have a nandroid backup of my initial checkrom in my internal sd card but cannot restore it before installing a rom with root and cwm. Kindly help . Thanks.

I'm having the exact problem. I'm hoping we can create a soft brick sticky thread. I walked away from my phone last night because I was getting frustrated.
My attempts to flash stock ROM via Odin resulted in the "not responding" message in windows. I can get to both CWM and download mode, however any ROM flashed via CWM results in the behavior described by the OP. fortunately I have access to another Samsung phone, so I can double check driver installation (although it worked for flashing previously).
I'm continuing a search through the forums to find some alternate methods for unbricking. Hope someone has an idea.
Thanks!

It seems that the stock roms i was trying to flash were nonwipe ones so i flashed xxla3 which is a wipe rom and was able to boot . I then flashed the earlier kl3 rom over this rom because kl3 is rootable. I then rooted and installed cwm booted into recovery and restored my earlier nandroid backup. I think the situation arises because the nonwipe rom was unable to clear the cache , user data etc

Thank you for the information. I had exactly the same problem. What did you use to root KL3 ?

Just wipe both cash and user data, and reboot.

reboot to recovery mode -> mount and storage -> format system, format cache, format data.
and do a factory reset and wipe cache.
problem should be solved cause that's what i did

Flo1389 said:
Just wipe both cash and user data, and reboot.
Click to expand...
Click to collapse
Thanks

liewkingyan said:
reboot to recovery mode -> mount and storage -> format system, format cache, format data.
And do a factory reset and wipe cache.
Problem should be solved cause that's what i did
Click to expand...
Click to collapse
daaamnnn!!! I'm scared to dead because of this!! Thanks dude!!!, no more **** ass ics

I had an issue like this once or twice.
http://www.youtube.com/watch?v=L5XjF6sPef4
This skips the that screen. then I cleared some things like google framework and it all was peachy

But its not wroking for me

[Q] P1000N in unstable state

Device
PT1000N 2.3.3 (Kies upgrade) then rooted using ODIN (several months ago, do not remember which process)
Starting problem
I was using go launcher and frozen samsung home apps using root uninstaller pro. Then installed a driver companion, tablet hung. After reset:
"Sorry The application Samsung Home (process com.sec.android.app.twlauncher) has stopped unexpectedly. Please try again."
What I did
tried to flash back to 2.3.3 using heimdall, no fail messages (first)
hard reset
What I get now
It takes 1 hours aprox (no kidding) then displays error messages for loading swipe, system and other apps. Runs VERY slow and hangs at some point.
Once showed message "UUIDs inconsistent" or something alike ...
Also notice that all installed apps and eve my google credentials are still on the system. Such info should be erased by hard reset (I suppose).
Tried other rooms, tried flashing with ODIN
Big Question:
What can be done ?
TIA

What happened when you try odin? what error msg did you get?
Did you do a full wipe(factory reset, data cache, and dalvik) in recovery after flash?
Side note: for future reference, you should try freeze command in gemini app manager first before uninstalling any systemapps.
You should have done a nandroid backup from CWM before tweaking any sytem apps or data. You would have been able to restore from cwm.
EDIT: May we know whicb ROM and kernel you flashed?

yappoe said:
What happened when you try odin? what error msg did you get?
Did you do a full wipe(factory reset, data cache, and dalvik) in recovery after flash?
EDIT: May we know whicb ROM and kernel you flashed?
Click to expand...
Click to collapse
No errors with odin nor in heidmall when flashing.
Flashing Stock Ginger 2.3.3
Thanks for the tip, should have been more careful when dealing with system sutff

valter.espindola said:
No errors with odin nor in heidmall when flashing.
Flashing Stock Ginger 2.3.3
Thanks for the tip, should have been more careful when dealing with system sutff
Click to expand...
Click to collapse
There are plenty of GB 2.3.3 and most of them are for P1000.
Are you sure yours is for P1000N?
GB 2.3.3 for P1000N should read: P1000NUBJP7
how about yours?
Please check it at Settings > About Device
Download your firmware from http://www.sammobile.com/firmware/ you will have a choice of 2.3.5 or 2.3.6 even.
But word of warning.. it's not easy to root 2.3.5 or 2.3.6.

N7000 Stuck at samsung ):

Hi guys. Recently I have been using my phone and it hit 1% battery then went dead.
I charged it and rebooted it but it was stuck on the samsung logo.
I cleared my cache and dalvic but no luck ):
I also tried to Go back to GB stock and when I did it it works but keeps saying android something as crashed and every time I hit OK, It just popped up again.
I tried using Odin on my PC to go back to ICS but STILL stuck on the logo.
Made a NANDROID backup but still no luck...
Please help me!

are you on ICS now? if so, install philz kernel from recovery , reboot into recovery and perform a wipe data / factory reset. this should boot up the phone. if on GB, just go into recovery and do a factory reset

nokiamodeln91 said:
are you on ICS now? if so, install philz kernel from recovery , reboot into recovery and perform a wipe data / factory reset. this should boot up the phone. if on GB, just go into recovery and do a factory reset
Click to expand...
Click to collapse
Hi, I did a factory reset. Although it was my final resort.
Do you think my phone will still be stuck when I recover from NANDROID?

if the nandroid has bad data then it will. but still worth a try as you can do a factory wipe to get booted again

nokiamodeln91 said:
if the nandroid has bad data then it will. but still worth a try as you can do a factory wipe to get booted again
Click to expand...
Click to collapse
Ok I will give it a try thank you I will report back if anything is gone wrong.
+1 thanks

this happened with me a month ago , i installed an app from store and it asked to reboot my device , when i did so , my note lagged on the shining samsung logo .
All what i did is flashing my note with original stock firmware using Odin , and the device still working perfectly till now ..
** my device version is ICS .
** most devices won't loss their data using this method , 'cuz it's like a software update ..
best of luck
Momen Sars

[Q] Help me understand whats going on.

okay, first of all i will say that im sorry if what im writing is full on faulty language. enlgish isnt my best. aaaanuslut i got my brothers old gt n7000 with a broken touchpad and screen for free. i repaired that with 160€ and my brother said that the phone was rooted. i found out he had allso overclocked the device. But after a few restarts to the phone it just said something what i think was in spanish or something "bla bla bla dos sistema". After that came not your old samsung logo, but purple blueish circles just circling. Ant thats it, it would not start. So i read about bricked devices, and as much as i understood i had a soft brick. so i was looking aroun the forum for some easy fixes becasue im totally stranger to this kind of hacking. i finaly found this http://www.youtube.com/watch?v=F97qo1moAR4 and i downloaded custom jb N7000XXLSZ_N7000OPSLS6_N7000XXLSO_HOME.tar. it did work but again after i tried to restart the phone it was stuck.
So since i dont want any custom stuff i think to my self why not stock rom. so i found this http://forum.xda-developers.com/showthread.php?t=1424997. But since i dont like JB as much as ICS i will try ICS. Her is the question: i allready did the factory reset and cache wipe but this instruction says not to FROM ICS.
Warning :
Don't wipe anything from stock ICS recovery
Don't factory reset/Hard reset on stock ICS.
Don't flash any Wipe version of ICS ROM
Does that mean that i have allready gone wrong or does that mean that you have to have ICS on youre phone and then you cant do any of those things? its really confusing and i dont want to fk up my phone.

Did you make a wipe on stock ICS recovery?

zai89 said:
Did you make a wipe on stock ICS recovery?
Click to expand...
Click to collapse
My brother said that he had custom ice cream on it when i first made the wipe and tried jelly

orizont said:
My brother said that he had custom ice cream on it when i first made the wipe and tried jelly
Click to expand...
Click to collapse
can your phone boot to recovery mode now?

zai89 said:
can your phone boot to recovery mode now?
Click to expand...
Click to collapse
Yes i can

flash via recovery phils kernel, (a newer one) reboot in recovery and perform the wipe for new rom option.
That should clean your device good.
Then flash what you want. After that download an emmc check app and check. Shouldnt be needed, but its nice to check.
Sent from my GT-N7000 using Tapatalk 2

baz77 said:
flash via recovery phils kernel, (a newer one) reboot in recovery and perform the wipe for new rom option.
That should clean your device good.
Then flash what you want. After that download an emmc check app and check. Shouldnt be needed, but its nice to check.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Allright, thankyou, since i am new to all this stuff i will try to locate a tutorial. i dont have any idea for instance, what is recovery phils kernel.

at own risk, here http://forum.xda-developers.com/showthread.php?t=1901191. Download zip, keep zipped and put on external sd. Reboot recovery and flash via install from sd option.
Since we are going to wipe latest version will do fine. However if you plan to reflash the original Samsung rom one that is same or likewise version is best to quickly root after flashing rom, so you can flash speedmod kernel (better battery life) after. Find in original dev thread of this forum.
Remember, via factory format on phills kernel recovery(reboot in recovery) you have the option to do a wipe for new rom.
Otherwise on Phills kernel recovery do factory, cache wipe. In advanced dalvik cache, in mounts all(warning take out external sd before so you dont wipe that)
Then your phone is clean, you shouldnt have to wipe efs anyway, so dont tick that option ever in pc odin when flashing rom with odin.
This is the cleanest way to get rid of All leftovers and generally the way to go before flashing any new rom. However risk of loosing photos and whatever you have not backed up. In general backing up is bad as old files/db/etc are put back (risk of unforeseen stuff happening) Check one of my 5 threads for what backups there are. Via my profile you find them
Enjoy!
Sent from my GT-N7000 using Tapatalk 2

Okay, im thankful for all this information, useful stuff, got the PhilZ-cwm6-XXLT6-XSA-5.06.1-signed.zip.

let us know how it went, ok?

OOOKAY! so i finaly did what baz77 described. and rooted with another phils kernel witch i chose after my downloaded rom. Did root it, and after powering down and waiting about 3-5 sec. i started it, and it worked, no more getting stuck on gt n7000 screen and so on. and i also downloaded emmc check app, but unfortunatley it said. Brick bug: YES. Insane Chip.

sorry for double post, how do i delete? all i can do is use edit/delete button but it only edits the post, how can i delte it?

You cant but thats ok.
all n7000 have the brickbug to my knowledge, the test should state if the bug has been triggered, if not then super, if it has, best to secure the broken emmc sectors. Tricky.
I think having it clean now should eliminate earlier issues Enjoy your n7000

Thank you, i will, lately my n7000 has been rebooting randomly, any fix or know issue why this occures?

orizont said:
Thank you, i will, lately my n7000 has been rebooting randomly, any fix or know issue why this occures?
Click to expand...
Click to collapse
not sure how that is happening. Maybe a logcat (logfiles) shows whats happening when it happens. Could be app. Maybe rom issue. Method of elimination counts here.
On safe kernel, try dalvik cache, cache wipes and fix permissions in recovery, reboot and check if reoccurs.
Otherwise, updated versions, clean install I would recommend.
You can check also before with that emmc app if there are bad sectors. I dont expect it but you never know

Okay, its been a long time since i did that stuff. And it worked allirght. i got my phone working and rooted. Great stuff here

Sorry for updating old topic. Since people who have helped me with my phone allready are familiar with my case. I was wisiting a friend of mine in england and after i returned home my phone is f**ked. Everything works okay, but when i turn on mobile data or wifi it instantly freezes. Takes about 15-20 sec. and then phone does an automatic restart which restarting gets into boot loop. I have to hold down bower button to reboot again. When it asks me for sim unlock code, i have to be quick when im inserting it because i need to turn off mobiledata/wifi as soon as ia get my phone running again, otherwise it will freeze and crash again. Can it be somekind of virus or something? Is it most likely that i have to again format and install philz kernel and all that stuff? Thanks in advance.

that would be the best way to start..IMO

I really dont have the time or opportunity to format and reflash, but i guess its really difficult, near imbossible to tell whats wrong with my samsung. Bust still, any other suggestions?