Database Develop

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

[SOLVED] Am I bricked? PLEASE help me :(

Hi guys. I'm quite a noob, but have a good experience on flashing without be bricked (CM9, CM10, Crash, Paranoid...), but I have a problem.
I will explain to you step-by-step what I've done with my Note, so I wish some of you could help me.
1) I was running JB Crash ROM with PhilZ kernel.
2) Some apps got Force Close too often, so I went on Rom Manager and, after a look into the "Fix permissions" description ("It will fix some force closes" or something like that), I decided to give it a try and I tapped on it.
3) After that, my homescreen became unusable, because "TouchWiz Home" got EVERY TIME force closed without reason. Everything else worked fine, so I deciced to boot into CWM recovery to restore a nandroid backup of the same ROM.
4) Instead of tapping "restore", I tapped "backup" (my fault) and it started without possibility of get back. I got something like 200 Mb of free space, so in every case it will never have had success. My Note stucked at this point, so I decided to reboot manually (vol up+home+power) into recovery. Finally I tried to "restore" but I get this message: "ERROR WHILE RESTORING /SYSTEM".
5) I tried to reboot my Note, but it stucks at "Samsung Galaxy Note GT-N7000" screen without going on.
The good news is that it can go without problems into recovery and into download mode. What can I do? Flashing from CWM, for example, CM9 can fix this?
Please help me thanks!

1. Boot into CWM
2. Wipe data, dalvik and cache
3. Format system
4. Reflash your ROM
Don't use rom manager it's not compatible ....

friedje said:
1. Boot into CWM
2. Wipe data, dalvik and cache
3. Format system
4. Reflash your ROM
Don't use rom manager it's not compatible ....
Click to expand...
Click to collapse
After formatting /system, can I try to restore my nandroid backup? Or I have to necessary reflash my ROM? In that case, it's the same thing make it via CWM or via ODIN PC? I'm still on PhilZ recovery, which is safe I guess!
Anyway, thanks for your help

Via CWM or Odin, depends if you have your rom in the zip or the md5.tar format.
I would reflash to be clean. It's a bit more work in restoring your apps and data
afterwards, but at least you don't restore any messed up files.

if you can still access CMW and Download Mode then you probably are not brick... try fresh install through pc odin.. safe method no need to worry about bricking by fullwiping on unsafe kernel or raising triagle or binary counter whatsoever.. if you wanna play safe then PC ODIN and after that you can root your rom

Thank you guys, now I'm on stock ICS flashed via PC Odin and everything works fine I knew I was 99% not-bricked (still recovery and download mode avaiable), but I was a little scared too.
Thank you again!

glad you solved it.. :good:

Ace bootlooping with all cyanogenmod roms

I own a Samsung Galaxy Ace S5830 running on android 2.3.6 with build number GINGERBREAD.DDKQ8.I successfully rooted my device(SU icon in the app drawer), flashed cwm5.0.2.6 with no error.
I flashed gingercruzt 2.2, cm 7.1,7.2,9,10 with the following instructions:
1) Wipe data/factory reset
2) Wipe cache partition
3) Under advanced, wipe dalvik cache
4) Flashed the rom.
After rebooting for the first time, this happens(for every rom I tried):
The phone boots into the rom(the capacitive buttons get turned on) -> setup window is reached -> then the phone starts booting again->in further boots it reaches cm logo only and keeps on booting again and again.
I tried wiping data, cache partition, dalvik cache and reboot. None of it worked.
I flashed the roms again .But still stuck at bootloop.
Ps : I randomly took my sim out and did a complete wipe and the roms work fine!!!.
But with sim again, the same problem persists.
PLEASE HELP.THANKS IN ADVANCE.

If you have installed any custon rom previous than i suggest you to first flash fresh ddkq8 stock and than try to install ur custom rom..
It might be happening because of previous rom data !
Sent from my GT-S5830 using xda app-developers app

gb2793 said:
I own a Samsung Galaxy Ace S5830 running on android 2.3.6 with build number GINGERBREAD.DDKQ8.I successfully rooted my device(SU icon in the app drawer), flashed cwm5.0.2.6 with no error.
I flashed gingercruzt 2.2, cm 7.1,7.2,9,10 with the following instructions:
1) Wipe data/factory reset
2) Wipe cache partition
3) Under advanced, wipe dalvik cache
4) Flashed the rom.
After rebooting for the first time, this happens(for every rom I tried):
The phone boots into the rom(the capacitive buttons get turned on) -> setup window is reached -> then the phone starts booting again->in further boots it reaches cm logo only and keeps on booting again and again.
I tried wiping data, cache partition, dalvik cache and reboot. None of it worked.
I flashed the roms again .But still stuck at bootloop.
Ps : I randomly took my sim out and did a complete wipe and the roms work fine!!!.
But with sim again, the same problem persists.
PLEASE HELP.THANKS IN ADVANCE.
Click to expand...
Click to collapse
Problem could be your simcard? How is that even possible. Try flashing with your sim out then insert it after the rom is installed.

SuperAce609 said:
Problem could be your simcard? How is that even possible. Try flashing with your sim out then insert it after the rom is installed.
Click to expand...
Click to collapse
I tried this after discovering the sim "problem" but it didn't work out.

bhumit22 said:
If you have installed any custon rom previous than i suggest you to first flash fresh ddkq8 stock and than try to install ur custom rom..
It might be happening because of previous rom data !
Sent from my GT-S5830 using xda app-developers app
Click to expand...
Click to collapse
When i flashed my first custom rom(cm 7.1), i was on fresh ddkq8 stock rom. But the problem still occured.
Though i will give it a try again.

gb2793 said:
When i flashed my first custom rom(cm 7.1), i was on fresh ddkq8 stock rom. But the problem still occured.
Though i will give it a try again.
Click to expand...
Click to collapse
It would be a great advisable idea if you flash stock rom via odin every time when you want to switch from one cusom rom to other...
Sent from my GT-S5830 using xda app-developers app

bhumit22 said:
It would be a great advisable idea if you flash stock rom via odin every time when you want to switch from one cusom rom to other...
Sent from my GT-S5830 using xda app-developers app
Click to expand...
Click to collapse
as told by you, I flashed stock rom and then rooted my phone, installed cwm and then flashed cm9.
I am still stuck on the boot loop...
PLZ HELP

gb2793 said:
as told by you, I flashed stock rom and then rooted my phone, installed cwm and then flashed cm9.
I am still stuck on the boot loop...
PLZ HELP
Click to expand...
Click to collapse
Did you mount the /system? Sometimes you have to do this.
Boot into CWM, mounts and storage > mount /system
Check to see that everything is mounted, sd-ext may or may not work, don't worry about it, it's a big in most CM9 ROMs

[Q] bootloop after factory reset

Hi
I wanted to update my 5830, so I flashed firmware via ODIN to the newest, all was good since I wanted to give my phone to my wife, and I needed to do factory reset... after that my phone stuck in bootloop, cant go more than samsung logo, sometimes animation, and its blinking and restarting again. What can I do? I performed new flash with new rom - all going good, but I'm trying to factory reset it again, and its bootlooping again...
can some1 help me back my phone to good condition with factory reset possibility?

hexen88 said:
Hi
I wanted to update my 5830, so I flashed firmware via ODIN to the newest, all was good since I wanted to give my phone to my wife, and I needed to do factory reset... after that my phone stuck in bootloop, cant go more than samsung logo, sometimes animation, and its blinking and restarting again. What can I do? I performed new flash with new rom - all going good, but I'm trying to factory reset it again, and its bootlooping again...
can some1 help me back my phone to good condition with factory reset possibility?
Click to expand...
Click to collapse
brother after flashing new roms you should
1 factory reset
2 wipe cache partition
both are necessary
i think you did not wiped cache partition
do it and phone will boot
good luck :good::good:

aditya rathee said:
brother after flashing new roms you should
1 factory reset
2 wipe cache partition
both are necessary
i think you did not wiped cache partition
do it and phone will boot
good luck :good::good:
Click to expand...
Click to collapse
Exactly! Try that aditya said to you

Viper The Ripper said:
Exactly! Try that aditya said to you
Click to expand...
Click to collapse
thanks for praising sir
also can you update link to aosp ics by olddroid its link does not work anymore

aditya rathee said:
brother after flashing new roms you should
1 factory reset
2 wipe cache partition
both are necessary
i think you did not wiped cache partition
do it and phone will boot
good luck :good::good:
Click to expand...
Click to collapse
I'v done this several times, by cwm and by stock recovery - same result. Finally I've installed branded rom and it's working perfectly to the moment I wanted to uninstall operator apps by titanium backup. Sometimes at the finishing of uninstall phone reboots... but working.

hexen88 said:
I'v done this several times, by cwm and by stock recovery - same result. Finally I've installed branded rom and it's working perfectly to the moment I wanted to uninstall operator apps by titanium backup. Sometimes at the finishing of uninstall phone reboots... but working.
Click to expand...
Click to collapse
yeah n between uninstalling system apps system boots but thats not a problem as those apps which you wanna remove get removed even if your phone gets rebooted

Did you also wipe dalvik? Try to flash a stock (old) firmware via odin and do this steps.
1.reboot to recovery
2.wipe data /factory reset
3.wipe cache partition
4.reboot
İt has to boot normally in 2-3 minutes. İf doesnt tou gotta make a Jtag operation which you cannot do without the RiffBox.
Sent from my Nokia 3310

You should flash a multi package firmware when rolling back from custom roms.XXKPH is one such rom,then you can flash latest update afterwards.Cache etc never matter for me

side_effect said:
You should flash a multi package firmware when rolling back from custom roms.XXKPH is one such rom,then you can flash latest update afterwards.Cache etc never matter for me
Click to expand...
Click to collapse
1st XXKPH, then what? Is that with Polish language?

Xxkph is eastern europe version. İnstall it and make factory reset after first succesful boot
Sent from my Nokia 3310

[Q] OMNI AsylumKANG Rom flash problems

Hey,
I got little problem and I need some help. I wanted to falsh OMNI AsylumKANG (from thread http://forum.xda-developers.com/showthread.php?t=2591479 ) , but my n7000 failed to start system. Instead after samsung logo it restarted into twrp screen.My version number is N7000XXLT9. These are steps I made:
1. using stock recovery I flashed PhilZ-cwm6-XXLT9-ORA-5.11.2-signed
2. then launched and rebooted into PhilZ recovery
3. flashed raw_kernel_r4_j43 and reboot into recovery
4. wiped data, cache partition and dalvik cache
7. flashed AsylumKANG_4.4.2_n7000_Build2.2
8. flashed pa_gapps-modular-mini-4.4.2-20140111-signed
9. flashed UPDATE-SuperSU-v1.86
10. reboot
Afterwards as I said phoned showed samsung logo and rebooted itself to twrp recovery
What is problem here?
Thanks for help.

Should reflash Philz. Go to wipe/factory reset menu, then choose clean to install rom. Then go to advanced, wipe dalvik cache. Then reflash raw5, then flask rom.
Sent from my phone.

forest1971 said:
Should reflash Philz. Go to wipe/factory reset menu, then choose clean to install rom. Then go to advanced, wipe dalvik cache. Then reflash raw5, then flask rom.
Sent from my phone.
Click to expand...
Click to collapse
Thanks for idea but I didn't help I flashed stock rom, then Philz then clean to install rom, wipe dalvik cache and the rest is just like from step 3 down. Same issue. I flashed once again stock rom and Philz, but this time installed paranoid android 3+ (pa_n7000-3.99-RC2-20131012). It worked. Maybe I just wait for more kitkat 4.4 based rom releases and then try.

After flash r5 you need to boot into recovery before proceed with lashing rom. Make sure you have done that step.
Sent from my phone.

forest1971 said:
After flash r5 you need to boot into recovery before proceed with lashing rom. Make sure you have done that step.
Sent from my phone.
Click to expand...
Click to collapse
After flash r4 i boot into recovery. You're saying to flash r5 instead of r4?