Database Develop

What was wrong ? Mini CM9 on Xperia X8

Hi everybody,
I tried yesterday to flash my phone with the new mini CM9 + nAa 04 kernel... It did not work resulting in a soft brick.
I solved this problem by flashing back to the stock rom + kernel using flashtool. My device is now working as before.
After many unfruitful research on the forum, i'm forced to ask you what wrong did I do...
My phone was (and is) configured as follow :
Kernel : stock 2.6.2.9
Rom : Android 2.1
Base Band Version : M76XX-TSNCJOLYM-53404015
Built : 2.1.1.C.0.0
Rooted
Bootloader : unlocked
Today I installed xRecovery (which is not needed if I use the Kernel E15_nAa-ics-04_2.6.29.6-nAa-ics-04).
Is it problematic if I want to use the mini CM9 rom ?
How did I do :
I started by flashing the kernel using flashtool and with the latest version kernel E15_nAa-ics-04_2.6.29.6-nAa-ics-04.
The manipulation was successful and kernel was working well.
Then, after having backed up all my settings, apps, contacts, rom and wiped off the data factory settings, I started to flash the rom with CWM (the rom had been stored before on my SD card).
Once the installation finished, the phone reboot... and reboot .... and reboot, etc...
It was only able to display the nAa kernel screen (boot loop), but nothing more.
Finally, I flashed it back to stock version to use it again... OUff
I was a bit scared by the idea of having a hard brick but finally it was just a soft brick.
What do you think about my experience ? I know many of you think that people who do not have necessary skills to do it should not do it ^^ but I want to learn and to make my phone a bit more flexible and fast.
Thank you in advance !
Nico

P'titbateau said:
Hi everybody,
I tried yesterday to flash my phone with the new mini CM9 + nAa 04 kernel... It did not work resulting in a soft brick.
I solved this problem by flashing back to the stock rom + kernel using flashtool. My device is now working as before.
After many unfruitful research on the forum, i'm forced to ask you what wrong did I do...
My phone was (and is) configured as follow :
Kernel : stock 2.6.2.9
Rom : Android 2.1
Base Band Version : M76XX-TSNCJOLYM-53404015
Built : 2.1.1.C.0.0
Rooted
Bootloader : unlocked
Today I installed xRecovery (which is not needed if I use the Kernel E15_nAa-ics-04_2.6.29.6-nAa-ics-04).
Is it problematic if I want to use the mini CM9 rom ?
How did I do :
I started by flashing the kernel using flashtool and with the latest version kernel E15_nAa-ics-04_2.6.29.6-nAa-ics-04.
The manipulation was successful and kernel was working well.
Then, after having backed up all my settings, apps, contacts, rom and wiped off the data factory settings, I started to flash the rom with CWM (the rom had been stored before on my SD card).
Once the installation finished, the phone reboot... and reboot .... and reboot, etc...
It was only able to display the nAa kernel screen (boot loop), but nothing more.
Finally, I flashed it back to stock version to use it again... OUff
I was a bit scared by the idea of having a hard brick but finally it was just a soft brick.
What do you think about my experience ? I know many of you think that people who do not have necessary skills to do it should not do it ^^ but I want to learn and to make my phone a bit more flexible and fast.
Thank you in advance !
Nico
Click to expand...
Click to collapse
Your hardware and software seems alright to me.
Steps: Don't bother about xRecovery. From stock 2.1...
Root again
Flash nAa-ics kernel
Install MiniCM9 and Gapps from first post of MiniCM9 thread
FULL WIPE -- YOU MUST DO THIS
WIPE DALVIK-CACHE TOO
Reboot and have fun
Sent from my X8 using Tapatalk 2

Flash the latest baseband ans try again
Sent from my E15 using Tapatalk 2

Full Wipe will solve the problem.
Sent from my E15i using xda app-developers app

Hi,
Thanks for your replies.
So I don't understand what was wrong as I completely wiped the system prior to flash the Rom.
I proceeded exactly like that :
1.Wipe data factory
2.Wipe cache
3.Wipe dalvik-cache
4.Format system
5.Format cache
6.Format data
7.Rom installation
8.Flash Gapps
I think I have done all the necessary steps to make it working ...
I was maybe not enough patient after installation ?
I'm going to try again today (now I know how to recover from a soft brick ).
Thank you all again.

P'titbateau said:
Hi,
Thanks for your replies.
So I don't understand what was wrong as I completely wiped the system prior to flash the Rom.
I proceeded exactly like that :
1.Wipe data factory
2.Wipe cache
3.Wipe dalvik-cache
4.Format system
5.Format cache
6.Format data
7.Rom installation
8.Flash Gapps
I think I have done all the necessary steps to make it working ...
I was maybe not enough patient after installation ?
I'm going to try again today (now I know how to recover from a soft brick ).
Thank you all again.
Click to expand...
Click to collapse
Good job dude!
just try and try lolZ
maybe you miss something like flash or root..

libera powaemm
It works ! My phone is now booting and I see the CM9 blue droid :highfive:
Special thanks to developers who allow us to have better software !
And thank you for the support you brought me.

congratulation!

P'titbateau said:
It works ! My phone is now booting and I see the CM9 blue droid :highfive:
Special thanks to developers who allow us to have better software !
And thank you for the support you brought me.
Click to expand...
Click to collapse
well well!
enjoy it! :laugh::laugh:

having the same problem
P'titbateau said:
It works ! My phone is now booting and I see the CM9 blue droid :highfive:
Special thanks to developers who allow us to have better software !
And thank you for the support you brought me.
Click to expand...
Click to collapse
So, what step u miss? I also having the same problem. Can tell me your steps? dying for CM9 in my X8 too T-T

slyzerx said:
So, what step u miss? I also having the same problem. Can tell me your steps? dying for CM9 in my X8 too T-T
Click to expand...
Click to collapse
just do what spyder-x said dude!
:laugh::laugh:

Same problem... when i try to install it again I get an error and it says my device is 16i insted of 15i ...
Then I had to flash different rom 3 times to get it working...
Didn't wipe cashe and it worked : )

first instal minicm 3.0.4
after that install minicm 3.0.5(or any nightlie) without any wiping!.

[Q] Galaxy Note logo brick

Hi guys :laugh: i'm new here... and i have a big problem: my galaxy note stays bricked on the initial logo (Samsung galaxy n7000) ..... i tried to flash with odin a stock gingerbread rom but it stucks at factory.fs
i tried to to flash it with cmw but it still stucks at the initial logo
i ve tried everything...... can you please help me?
p.s i can still enter in download mode odin

I think if u can search a thread where dr ketan has given expert advice
Also if u cud post how did u brick ur phone it will help experts in solving ur prblm
Edit see this http://forum.xda-developers.com/showthread.php?t=1912417
Sent from my GT-N7000 using xda premium

razorgtr14 said:
Hi guys :laugh: i'm new here... and i have a big problem: my galaxy note stays bricked on the initial logo (Samsung galaxy n7000) ..... i tried to flash with odin a stock gingerbread rom but it stucks at factory.fs
i tried to to flash it with cmw but it still stucks at the initial logo
i ve tried everything...... can you please help me?
p.s i can still enter in download mode odin
Click to expand...
Click to collapse
yeah ... as sitanshu91 asked,,,
u need to let us know what u did before it got stuck at the LOGO ?

razorgtr14 said:
Hi guys :laugh: i'm new here... and i have a big problem: my galaxy note stays bricked on the initial logo (Samsung galaxy n7000) ..... i tried to flash with odin a stock gingerbread rom but it stucks at factory.fs
i tried to to flash it with cmw but it still stucks at the initial logo
i ve tried everything...... can you please help me?
p.s i can still enter in download mode odin
Click to expand...
Click to collapse
Hi there, did you try to flash on an unsafe kernel? Please read the numerous posts on Safe / Unsafe kernels, then consult Chasmodo's excellent Kernel Repository.
Before flashing a ROM, I would suggest you download the Abyss 4.2 kernel (tar file), you can search and find this on XDA.
Connect your Note to Odin and flash the Abyss 4.2 tar file. This will install a safe (Gingerbread) kernel. Again there are posts on how to do this.
Enter Recovery and flash your ROM of choice.
Remember to ALWAYS flash on a safe kernel. If you are not sure, please check.
I hope this helps. Please hit THANKS if it did.

Thanks for posting you all,
I was flashing a new rom with cwm and suddently appeared an error: E: can't...
I took off the battery and put it again and reboot it again...
And so it stucked at the initial logo.
P.S: i had a cooked rom before that happened

razorgtr14 said:
Thanks for posting you all,
I was flashing a new rom with cwm and suddently appeared an error: E: can't...
I took off the battery and put it again and reboot it again...
And so it stucked at the initial logo.
P.S: i had a cooked rom before that happened
Click to expand...
Click to collapse
But, what new ROM were you flashing and what were you on prior? You have to explain yourself better. Did you do a factory reset/wipe data on a PURELY STOCK ROM or did you use philz kernel or a CM9/10 variant or something else?

razorgtr14 said:
Thanks for posting you all,
I was flashing a new rom with cwm and suddently appeared an error: E: can't...
I took off the battery and put it again and reboot it again...
And so it stucked at the initial logo.
P.S: i had a cooked rom before that happened
Click to expand...
Click to collapse
Sounds to me as if you flashed from an unsafe kernel. You must ALWAYS check the kernel is safe before you flash.
I would recommend you flash a safe kernel (via Recovery or Odin - there are guides on both methods). Abyss 4.2 is my personal choice.
Then, when the kernel has been flashed, reboot back to Recovery before flashing a ROM. Do not got straight to ROM flash.
These steps should help.

thanks for your help but there s still a problem... if a flash a rom with odin it stucks at factory.fs..
i did everything and at last i used the adb program and i removed the old partition like factory.fs and created new one..... after that i converted them in ext4 by going in (cwm recovery) mounts and storage and check format /data and format /system...
after that i installed the cm 9 Nightlies and the phone worked again =D
so...after that.... i installed odin mobile pro and Odin Flash Kernel for GT-N7000 ...then i downloaded a stock rom ics (N7000XXLRG_N7000DBTLRG_DBT) and i flashed it with odin mobiel pro =)
everything was working fine until it stopped at installing or updating (i don't know) the new applications like kies,Smemo ecc.....
and now i don't know what to do...
Can you help me please? i don't want to throw away a galaxy note......

razorgtr14 said:
thanks for your help but there s still a problem... if a flash a rom with odin it stucks at factory.fs..
i did everything and at last i used the adb program and i removed the old partition like factory.fs and created new one..... after that i converted them in ext4 by going in (cwm recovery) mounts and storage and check format /data and format /system...
after that i installed the cm 9 Nightlies and the phone worked again =D
so...after that.... i installed odin mobile pro and Odin Flash Kernel for GT-N7000 ...then i downloaded a stock rom ics (N7000XXLRG_N7000DBTLRG_DBT) and i flashed it with odin mobiel pro =)
everything was working fine until it stopped at installing or updating (i don't know) the new applications like kies,Smemo ecc.....
and now i don't know what to do...
Can you help me please? i don't want to throw away a galaxy note......
Click to expand...
Click to collapse
Flash back to cm base. If you have damaged emmc its likely you won't be able to run stock roms anymore because of the damaged space. ie. Stock rom 600-800mb, cm based 150mb
Sent from my GT-N7000 using xda premium

Thanks for your replay....
uau...so i can't use stock roms anymore.... but i can still flash other cooked roms like crash rom or king rom?

razorgtr14 said:
Thanks for your replay....
uau...so i can't use stock roms anymore.... but i can still flash other cooked roms like crash rom or king rom?
Click to expand...
Click to collapse
He is saying you can use any CM based ROM. Crash and such are still based on stock Samsung and pretty big in size. Maybe try something like SlimBean.

[Q] [Help] Boots only to CWM...

Hello,
I have flashed the latest thunderzap kernel and I reboot to CWM. Then I made a backup with CMW en reboot again. I can reboot only to CWM now...
Can someone help me?

Одг: [Q] [Help] Boots only to CWM...
Rauwerdinho said:
Hello,
I have flashed the latest thunderzap kernel and I reboot to CWM. Then I made a backup with CMW en reboot again. I can reboot only to CWM now...
Can someone help me?
Click to expand...
Click to collapse
TZ have broken driver that is used for reboot recovery option.
Try to pull out battery, or flash stock kernel wifh odin. You can find it in my signature. Then reflash any custom kernel you want.
Sent from Galaxy S Advance

shut_down said:
TZ have broken driver that is used for reboot recovery option.
Try to pull out battery, or flash stock kernel wifh odin. You can find it in my signature. Then reflash any custom kernel you want.
Sent from Galaxy S Advance
Click to expand...
Click to collapse
Thanks!!
I have flashed Q4
It worked!!

[SOLVED] no Boot after semaphore 3.3.0s (cm10.2nightly)

I am in latest 10.2 nightly. Wanted to go to semaphore 3.3.0s +hughemem libs. I was on sema3.3.0. Flashed sema3.3.0s via cwm --> stuck on boot.
Flashed 3.3.0s.gar via Odin --> starts, but after restart my phone did not Boot.
So i reflashed 3.3.0 via Odin.
What is wrong with it?
Sent from my GT-I9000 using xda app-developers app
Update:
s3icc0 said:
lordlambda said:
s3icc0 said:
lordlambda said:
s3icc0 said:
lordlambda said:
s3icc0 said:
lordlambda said:
s3icc0 said:
lordlambda said:
s3icc0 said:
lordlambda said:
s3icc0 said:
lordlambda said:
Hello,
i am not able to ask in semaphore channel...so i want to ask you.
I falshed latest cm10.2 nightly, semaphore 3.3.0s and last but not least the hugemem libs via CWM.
after this my phone stucked on boot. Maybe you know the problem?
Many thanks in advance!!
Lordlambda
Click to expand...
Click to collapse
hugemem libs are not required, so the problem has nothing to do with hugemem libs (you only won't be able to record 720p video), but the fact you are stuck on boot maybe connected with something else ... from what firmware you were flashing? can you describe me your whole procedure (or just try to simply flash CM several times until it will boot and then reboot and instal semaphore ...)
Click to expand...
Click to collapse
I was on cm 10.2 (5.12.) and on kernel 3.3.0. Then i wanted to test the 3.3.0s kernel. so i downloaded it, go to recovery and flashed itvia cwm (Kernel is on external SD). There are no problems with the "normal" kernal version. Only by flashing the "s" my phone stuck on boot. In addition, i clean dalvik and normal cache.
And ofcause, i want to flash hugemem libs if the "s" version will boot normaly.
Many Thanks!
Click to expand...
Click to collapse
Strange, maybe try to reflash from internal storage (u can use file manager in cwm, or mount the phone to pc over usb from recovery to upload the files) and make sure you have the right files (as flashing CM11 accidentally with recovery from semaphore 3.3.0 will not boot). I recommend to redownload carefully both files, place on internal and reflash ... should be fine then.
Click to expand...
Click to collapse
My phone can boot, i falshed 3.3.0.tar via odin....thats not the problem. but i try to flash 3.3.0.s from internal storage. Maybe i have to mound or cleare something more than dalvik and normal cache? mound the sd?
Many Tanks!
Click to expand...
Click to collapse
no ... leave everything default in recovery ... so maybe try flashing 3.3.0s via odin too??? there should be no problem switching between standard and "s" kernel ... make sure you have the same size and MD5 version as in the semaphore topic ...
Click to expand...
Click to collapse
I checkes md5 summ....if i flash 3.3.0s via Odin phone starts but in Nest restart i stuck in Boot too.(in sumsung s screen, cant geht to recovery) same behavior AS after flashing "s" in cwm.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
So try to flash CM only .. boot with CM ... remove semaphore app, then reboot to cwm, install "s" version, turn off the phone (dont reboot system from cwm), boot to recovery adn reflash "s" version again, reboot system, instal semaphore app ...
Click to expand...
Click to collapse
I will give it a try after visiting my dentist. Thank you!
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
np, until I will have ideas I'd like to help
Click to expand...
Click to collapse
install cm10.2, deinstall semaphore app, insatll 3.3.0.s, turn off phone---no chance to get back in cwm
Click to expand...
Click to collapse
strange ... can you send me the locations were you downloaded the 3.3.0s (link to the file)
Click to expand...
Click to collapse
http://78.46.194.137/kernels/Semaphore_JB_3.3.0s.zip
Click to expand...
Click to collapse
sorry, I can't help you more, better to ask in the thread ... as it must be something else in your phone .... or if you don't mind loosing all your data I would recommend to go through odin from stock samsung, just to be sure (that is what I will do in this situation ... complete reinstalation ...) - it will take no more than 30 minutes to get back to stock and back to CM10.2
Click to expand...
Click to collapse
Solution: Flashing 3.3.0s.tar 3times via Odin. After each Flash i let the phone reboot!

Thanks for the info ...but it is strange ...in my 10.2-time i flashed Sema-Kernel only via Odin and it was never a problem ...
Amazing technology sometimes it works perfect and sometimes it doesn`t ...
Good to hear that it works now ...
lordlambda said:
I am in latest 10.2 nightly. Wanted to go to semaphore 3.3.0s +hughemem libs. I was on sema3.3.0. Flashed sema3.3.0s via cwm --> stuck on boot.
Flashed 3.3.0s.gar via Odin --> starts, but after restart my phone did not Boot.
So i reflashed 3.3.0 via Odin.
What is wrong with it?
Sent from my GT-I9000 using xda app-developers app
Update:
Solution: Flashing 3.3.0s.tar 3times via Odin. After each Flash i let the phone reboot!
Click to expand...
Click to collapse

Keeps rebooting to cwm after installing CM

Here is what I did with the phone:
- Flashed JVU via odin
- Flashed CF-Root with CWM via odin
- Wipe EVERYTHING
- Flashed semaphore kernel for 4.3 via CWM
- Rebooted to CWM
- Flashed CM 10.2 stable via CWM
- Flashed semaphore again
- Flashed gapps
And now the phone keeps rebooting to CWM everytime I power it on. It never goes to Android, it always boots to CWM. Any ideas?
Of course, i tried to flash CM / semaphore / gapps again but it keeps doing the same. Flashing only CM does not work either

same problem with my i9000 back year..U have lost you internal memory..it can work if u take you phone into download mode for 5 minutes and then start it it will work..
Sent from my GT-I9300 using xda app-developers app

[email protected] said:
same problem with my i9000 back year..U have lost you internal memory..it can work if u take you phone into download mode for 5 minutes and then start it it will work..
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
What do you mean exactly? ;_;
By the way it seems to work after flashing a samsung stock ROM but it does the same everytime I try to install CM. And I have done it before, I don't understand this ;_; (I decided to start over again because I was having trouble to downgrade from 4.4)

Have you find a solution? I faced the same problem and after reading half of the day on this forum I managed to find a solution to go back to stock and restore the phone functionality. Now I only have to flash CWM/TWRP and start to flash custom ROMs again
Let me know if you still need help.

The correct procedure to come to any ROM is from GB>ICS>JB>KK. So make sure that you are following the correct procedure
Sent from my GT-I9000 using Tapatalk 2

roccatgaming said:
Have you find a solution? I faced the same problem and after reading half of the day on this forum I managed to find a solution to go back to stock and restore the phone functionality. Now I only have to flash CWM/TWRP and start to flash custom ROMs again
Let me know if you still need help.
Click to expand...
Click to collapse
Hi,
I have the same problem, device keeps rebooting.
I did a rooting through Odin 3 and I got the green box saying PASS and now the device keeps rebooting. how can i fix it. Looks like you did the fix on your device.
Can you please tell me step by step how to fix my device.
Your help would be appreciated
Thanks
FLDS