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!.
Related
Hi!
I had a problem with my smart (if you call me, it reboot, something reboot automatically). I was using GingerDX v21 and v22. I downgraded to 2.1 via PC Companion but doesn't works.
So, I decided to use MiniCM7. I followed this tuto http://forum.xda-developers.com/showthread.php?t=1068553 and the bootloader unlock tuto too http://forum.xda-developers.com/showthread.php?t=1254225
Well, I did everything correctly, I guess. I see the nAa logo when I turn on my smart and I can enter in CWM-Recovery.
I have installed the MiniCM7-2.1.8-shakira, MiniCM7-2.1.7-shakira, MiniCM7-2.1.6-X8, GingerXperiaRay_V004 and PrimeHD20 but I can't pass of boot (bootlooping).
I don't know if I did something wrong. I had instaled too E15_nAa-09_2.6.29.6-nAa-09 and E15_nAa-06b_2.6.29.6-nAa-06b (first I tried v10). I everytime wipe all data.
If I install the original kernel and rom it works normally. I don't know what I can do. I do the same process three times, wiping all, installing, etc. and nothing!
What I'm doing wrong? There are some possibilities of my smart don't support it?
read this first http://forum.xda-developers.com/showthread.php?t=1011071 to go back to 2.1...
then root, install xrecovery,unlock bootloader,flash nAa kernel you need ,and then
install MiniCM7...
try this method
1.root
2.unlock bootloader
3.flash nAa v10
4.then your phone will have CWM and flash the rom minicm7.218
5.flash google gapps gb
6.reboot and see it bootloop or not??
Sent from my E15i using xda premium
Thanks for all replies.
Well, I did the @kostas_grevena3 method, but I'll do again. Maybe I forget to apply baseband 015! :O Hum...
What I'm doing now:
1. Flashing: Flashtool + X8 Shakira E15i_2.1.1.A.0.6_generic.ftf (success!)
2. Flashing: Flashtool + X8i_2.1.1.A.0.6_Baseband_015.ftf (success!)
3. Drivers yet installed from last tries. (success!)
4. Flashing: Flashtool + E15_nAa-10_2.6.29.6-nAa-10.ftf (success!)
5. Turn on smart, CWM and wipe all (success!)
6. Flashing: CWM + MiniCM7-2.1.8-shakira.zip (success!)
7. Flashing: CWM + gapps-gb-20110828-signed.zip (success!)
8. Rebooting for first time and...
MOTHER
OF
ANDROID!
Thanks you guys!
Feeling like a hacker now haha jk jk
Thanks!
try this.
1. boot in recovery
2. Factury Reset
3. mount/storage format system and sdext if you had an ext partiton
4. flash cm7 rom
5. boot now first complete to rom
6. Reboot to Recovery
7. Now you flash gapps
will it work now?
i remeber an error with odexed roms when i flash another zip before i boot in rom.
edit: oh sorry i see it sloved haha, have fun with your new x8
david.proweb said:
Thanks for all replies.
Well, I did the @kostas_grevena3 method, but I'll do again. Maybe I forget to apply baseband 015! :O Hum...
What I'm doing now:
1. Flashing: Flashtool + X8 Shakira E15i_2.1.1.A.0.6_generic.ftf (success!)
2. Flashing: Flashtool + X8i_2.1.1.A.0.6_Baseband_015.ftf (success!)
3. Drivers yet installed from last tries. (success!)
4. Flashing: Flashtool + E15_nAa-10_2.6.29.6-nAa-10.ftf (success!)
5. Turn on smart, CWM and wipe all (success!)
6. Flashing: CWM + MiniCM7-2.1.8-shakira.zip (success!)
7. Flashing: CWM + gapps-gb-20110828-signed.zip (success!)
8. Rebooting for first time and...
MOTHER
OF
ANDROID!
Thanks you guys!
Feeling like a hacker now haha jk jk
Thanks!
Click to expand...
Click to collapse
is this working?
First of all i would like to thanks all the Developers for their Incredible work on this site. I am using this site for a long time it helped me in solving many issues. I flashed many Custom ROMS on My X8 & X10 never had big issues so there was no need to post just becuase there was already so much of information here. But from last 4 days i am messing with my X8 when i tried flashing Jelly Bean Rom. Previously i was using 2.3.7 in my x8.I cant say i am very good but i am not new to these Roms. I actually searched alot but failed so i am here for help. In order to use Jelly Bean my x8 is having Bootloop issue. I follow all the instructions from http://forum.xda-developers.com/showthread.php?t=1789713 regarding Kernel http://forum.xda-developers.com/showthread.php?t=2136211. I follow each guidelines but still Bootloop . Not only that i cant use any other custom rom now everytime bootloop. SESU repair my phone but i cant use 2.1 now after using custom roms in x8 for longtime, It feels pathetic Now i dnt want Jelly Bean in x8 anymore i ll be more than happy if i get 2.3.7 back :angel:
I tried different Roms , Kernels but everytime same result "Bootloop"
Rooting fine, Flashing Kernel fine,, Rom instalation fine. Had doubt regarding Unlocking Bootloader ( Whether its properly unlocked or not). so Flashtool says Its "unlocked" but it also said it cant be "unlocked officially". So i tried another way to with s1 tools from this link http://forum.xda-developers.com/showpost.php?p=23680742&postcount=1 and r is smaller too RUNNING S1_EROM VER "r8A029". Now i am really confuse. tired and fed up 4 days GingerXperia, JellyBread.Jelly Bean everything failed
But i want to add 1 thing which is related to BLU because i cant dial *#*#7378423#*#* service menu from my x8 is that the clue or issue. Plz members help me out. Thanks in Advance.
Please Help
Damn ..
I have tried many times with naa kernel to flash rooms, but stuck in bootlop.
After I found this tread, flashed baseband 15 (I have selected only baseband to flash), flashed again nAa kernel and then custom ROM and phone is working.
Thanks
HI
I UPDATE 4.0.4 MY SGN FEW DAYS AGO
YESTERDAY I ROOT IT USING SPEEDMODE KERNAL (FLASH WITH PC ODIN)
TO I WANT TO DOWNGRADE IT TO GB SO I FLASH GB USING PC ODIN
AFTER FIRST ROOT ITS GIVE ERROR LIKE
Unfortunately, the process com.android.phone has stopped.
AND
Unfortunately, the TWLAUNCHERandroid.phone has stopped.
AFTER THIS I FLASH ICS 4.0.3 BUT SAME PROBLEM THERE
THERE IS NO NETWORK SIGNAL AND PHONE NOT WORKING
CAN I RESET MY PHONE
ITS TOO SLOW I TRYING TO RESET AND SETTING OPEN AFTER 7-8 MINUTES
WHAT S WRONG WITH ME PLS TELL ME
do not wipe your phone on ics...if you have you done a factory reset on rooted ics ...you could be in trouble
flash stock gb rom with odin ...boot up ..check that you are indeed on gb ...then fully wipe system
can you give some more info about where you are at now
@denny said:
do not wipe your phone on ics...if you have you done a factory reset on rooted ics ...you could be in trouble
flash stock gb rom with odin ...boot up ..check that you are indeed on gb ...then fully wipe system
can you give some more info about where you are at now
Click to expand...
Click to collapse
thanx
i install ics now 4.0.3
from baddi (h.p.)
9882220001
gurjit98 said:
thanx
i install ics now 4.0.3
from baddi (h.p.)
9882220001
Click to expand...
Click to collapse
What he saying you?
he says dont wipe on ICS, still you want to install ICS?
You need GB to wipe OR at least safe kernel to solve your problem.
Read again this
http://forum.xda-developers.com/showthread.php?t=1829078
what i said you? you have to wipe cache and data just after flashing GB ROM. All your error was just due to that. Just dont flash and flash without understanding, you have already bricked one time.
Really Read more before doing anything.
dr.ketan said:
What he saying you?
he says dont wipe on ICS, still you want to install ICS?
You need GB to wipe OR at least safe kernel to solve your problem.
Read again this
http://forum.xda-developers.com/showthread.php?t=1829078
what i said you? you have to wipe cache and data just after flashing GB ROM. All your error was just due to that. Just dont flash and flash without understanding, you have already bricked one time.
Really Read more before doing anything.
Click to expand...
Click to collapse
THANX FOR UR REPLY
dear, when i install gb then its stuck on setup screen
error is
Unfortunately, the process com.android.phone has stopped
Unfortunately, the process com.android.setup has stopped (error like this)
but when i flash ics 4.0.3 then some apps working (tooooo slow)
i also try factory reset (from phone setting)
but after restore same problem
i tried to download file LR6 but my slow internet is problem and hot file link is not resume able
gurjit98 said:
i tried to download file LR6 but my slow internet is problem and hot file link is not resume able
Click to expand...
Click to collapse
I put 3 Stock ICS ROMs in the torrent thread (one LR6 from India). Maybe you could try with this.
gurjit98 said:
THANX FOR UR REPLY
dear, when i install gb then its stuck on setup screen
error is
Unfortunately, the process com.android.phone has stopped
Unfortunately, the process com.android.setup has stopped (error like this)
but when i flash ics 4.0.3 then some apps working (tooooo slow)
i also try factory reset (from phone setting)
but after restore same problem
i tried to download file LR6 but my slow internet is problem and hot file link is not resume able
Click to expand...
Click to collapse
Those error was normal after flashing GB ROM, that i told you earlier too, at that time you didn't follow instruction, you have to wipe that time.
Now again you wiped on ICS?? Even after you already bricked one time.
dr.ketan said:
those error was normal after flashing gb rom, that i told you earlier too, at that time you didn't follow instruction, you have to wipe that time.
Now again you wiped on ics?? Even after you already bricked one time.
Click to expand...
Click to collapse
no i did not wipe data on any rom
Factory reset is same as wipe data.
Sent from my GT-N7000 using xda premium
gurjit98 said:
thanx
i install ics now 4.0.3
from baddi (h.p.)
9882220001
Click to expand...
Click to collapse
i gave up after this reply ...you clearly dont listen or read and youve already bricked once...dammmm...get an iphone
Experience the same thing as the thread starter but what I did was flash using Abyss Kernel then I wiped factory data - cache then installed KJ1 Gingerbread ROM. Then once Im at the GB rom I again re-flash the Abyss Kernel just to fix the static blank screen (dunno if thats normal). Then after im able to access the phone restart to recovery and flash the ICS rom that I want to install.
@denny love your comment about the iphone
Do you know how to use PC Odin to flash Roms ?
If it so then just download a GB rom from ketans thread and put your phone in download mode.
Connect it to your PC and flash it.After flashing go to Recovery and wipe cache.
That is all I can suggest you in this situation.
Just add one more thing to sahil's note.
If successfully flash gb.
And keep away from any flashing till you dont fully understand basics.
Sent from my GT-N7000 using xda premium
Hi All,
Hope I am in the good place to present my problem (i'm new in the forum and I'm just learning the "how to").
Yesterday I've rooted my Gnote (GTN7000 XXLPT - ICS just installed from OTA update). It was the paradise before i decide to instal "DPI change" ...
I set the DPI from 160 to 240 and then save + reboot ... Till that moment, my GNote stuck on the launching logo (Samsung Galaxy Note N7000).
I'm not an expert of Android (the proof ...) and I'm looking for the safest and easiest (step by step) solution to revive my GNote.
I know that XDA is an expert forum and therefore I please every of you that will see my request to help me ...
Ps: A part from the root I have applied no other manipulation on the phone (even the setup of the debuger mode).
Your kind help with this will be saving for me, given that there is no repair / after sale service available in my country.
Flash a safe kernel (speedmod),enter recovery and wipe data.
tibosee said:
Flash a safe kernel (speedmod),enter recovery and wipe data.
Click to expand...
Click to collapse
Thank you for your reply Tibosee,
However, I wonder how I can flash the kernel (a little step by step tutorial will be welcome).
Please help with this.
Regards.
I´d recommend flashing this kernel (HydraCore) http://forum.xda-developers.com/showthread.php?t=1749863
Kernel Installation
Install either through CWM or PC/Mobile ODIN in the usual manner. Wiping Cache and Dalvik Cache is unnecessary and wont make any difference. Flash only with 25% or more charge on the phone
Click to expand...
Click to collapse
If you had searched you would have known that you shouldn't use the app to change the DPI. Once you have reflashed a ROM or installed a new kernel, then use Rom Toolbox instead or edit the build.prop manually to change the DPI.
evilspyre said:
If you had searched you would have known that you shouldn't use the app to change the DPI. Once you have reflashed a ROM or installed a new kernel, then use Rom Toolbox instead or edit the build.prop manually to change the DPI.
Click to expand...
Click to collapse
Don't be to hard on him its not stupid to think that an app on market will work as advertised
Sent from my GT-N7000 using xda premium
Dont use apps to change dpi.. it wont work mostly.. i had the same problem on my note.. change it manually via your build prop..
Sent from my GT-I9300 using Tapatalk 2
Chillz88 said:
Dont use apps to change dpi.. it wont work mostly.. i had the same problem on my note.. change it manually via your build prop..
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Rom toolbox works if you don't want to mess with build prop but evilspyre already mentioned that
Sent from my GT-N7000 using xda premium
Rivan_92 said:
I´d recommend flashing this kernel (HydraCore) http://forum.xda-developers.com/showthread.php?t=1749863
Click to expand...
Click to collapse
Dears,
Thanks a lot for all assistance with this. Google play will never lies me as long as XDA will be there !
From your various explanations I've drawn the process below (please confirm that my comprehension is correct):
1 - Download and install Mobile Odin (Please provide a link to the safest version); Dont know if Odin will see the phone since i've not activated the debuger mode when the phone parameters was accessible.
2 - Download and install Hydracore Kernel;
3 - Connect the phone on the PC and run Odin (at this step I am not sure to know what to do);
4 - Flash and enjoy (Hope I'll reach this step)
May be the procedure with CWM will be more practicable, especially in case Odin do not see the phone ... But I really not know how to handle it. That's the reason why I was asking a Step by Step assistance.
Thanks and Regards
PatrickNkamgnia said:
Dears,
Thanks a lot for all assistance with this. Google play will never lies me as long as XDA will be there !
From your various explanations I've drawn the process below (please confirm that my comprehension is correct):
1 - Download and install Mobile Odin (Please provide a link to the safest version); Dont know if Odin will see the phone since i've not activated the debuger mode when the phone parameters was accessible.
2 - Download and install Hydracore Kernel;
3 - Connect the phone on the PC and run Odin (at this step I am not sure to know what to do);
4 - Flash and enjoy (Hope I'll reach this step)
May be the procedure with CWM will be more practicable, especially in case Odin do not see the phone ... But I really not know how to handle it. That's the reason why I was asking a Step by Step assistance.
Thanks and Regards
Click to expand...
Click to collapse
You only use one of the two applications; Mobile Odin or PC Odin. You don't have to use them together. Since your phone doesn't boot, then I assume Mobile Odin is out of the question. I'm gonna write a quick guide to use PC Odin.
1- Download PC Odin from this link: http://ul.to/xt4607xx (you can search the forum, you will find many download links for Odin 1.85)
EDIT: Here's another link, the 1st one doesn't want to work anymore. http://k0nane.info/rom/odin-185.zip You can google "odin 1.85" and open the first link (it should be an xda forums attachment)
2- Download the standard tar file of the Hydracore 3.5 kernel from this thread: http://forum.xda-developers.com/showthread.php?t=1749863
3- Open PC Odin and click on PDA and choose your kernel tar file downloaded from step 2.
4- Remove all check marks and leave only Auto Reboot and F. Reset Time CHECKED.
5- Turn your phone off and remove the battery and reinsert it.
6- Turn your phone on by pressing and holding the Power button + Menu button + Volume Down button (to get into Download mode).
7- Connect the phone to the USB cable and connect it to the computer. Odin should show a yellow box.
8- Press Start in PC Odin. The yellow box will turn green which means a successful flash.
9- Now you can wipe data safely (never wipe data using stock ICS kernel btw).
How is flashing the kernel going to solve the problem of a b0rked build.prop? Get out of here people.
The only solution to his problem is to flash a custom Rom.
" 9- Now you can wipe data safely (never wipe data using stock ICS kernel btw). :)" [/QUOTE said:
Joey_oggie, thanks a lot for your step by step tutorial, it is realy clear now. I'll try it and revert to tou with the status of the phone.
Just a quick one, regardind the end of your post, you mentioned that I should not wipe a stock rom. My understanding is that stock rom = official samsung rom. Therefore it seems my rom was a stock one (GTN7000 XXLPT - rom updated from GB to ICS - OTA update), since I never change it.
Should I wathever do the wipe as mentioned in your post?
Click to expand...
Click to collapse
chasmodo said:
How is flashing the kernel going to solve the problem of a b0rked build.prop? Get out of here people.
The only solution to his problem is to flash a custom Rom.
Click to expand...
Click to collapse
Hi Chasmodo,
I was just about to flash the Kernel of my GNote following Joey's + others advices above.
Please why do you think flashing the Kernel is not advisable? ... Do you think the phone will thereafter completely brick?
Please answer these two questions as quick as you can ... My finger is on the "red bouton" just waiting for you.
Could you also provide a link to a step by step tutorial in case the solution proposed by Joey is safe but comes unsuccessful ?
Thank you for your contribution.
Regards.
If your build.prop is corrupted/broken, flashing a new kernel won't fix it because it won't replace your build.prop.
As Chas said, the easiest fix would be to flash a custom ROM, as this will replace your build.prop.
Regards,
Dave
Sent from my GT-N7000 using Tapatalk 2
chasmodo said:
How is flashing the kernel going to solve the problem of a b0rked build.prop? Get out of here people.
The only solution to his problem is to flash a custom Rom.
Click to expand...
Click to collapse
Well, to flash a new ROM, he needs to be on a safe kernel...
And anyway, I thought wiping data = factory reset. Isn't that right? If so, then wouldn't the wipe fix his problem? I'm new to this stuff so excuse me if that's completely wrong.
PatrickNkamgnia said:
Joey_oggie, thanks a lot for your step by step tutorial, it is realy clear now. I'll try it and revert to tou with the status of the phone.
Just a quick one, regardind the end of your post, you mentioned that I should not wipe a stock rom. My understanding is that stock rom = official samsung rom. Therefore it seems my rom was a stock one (GTN7000 XXLPT - rom updated from GB to ICS - OTA update), since I never change it.
Should I wathever do the wipe as mentioned in your post?
Click to expand...
Click to collapse
Well, from what I read, most (if not all) Samsung stock ICS kernels have a bug which would corrupt the data partition when you wipe on any of them. The problem would appear when you wipe ON them, and not wipe them.
PatrickNkamgnia said:
Hi Chasmodo,
I was just about to flash the Kernel of my GNote following Joey's + others advices above.
Please why do you think flashing the Kernel is not advisable? ... Do you think the phone will thereafter completely brick?
Please answer these two questions as quick as you can ... My finger is on the "red bouton" just waiting for you.
Could you also provide a link to a step by step tutorial in case the solution proposed by Joey is safe but comes unsuccessful ?
Thank you for your contribution.
Regards.
Click to expand...
Click to collapse
I would wait till he replies to be on the safe side. In the meantime, try to burn some time and read some of the threads in the Note's android development section.
Sent from my GT-N7000 using xda app-developers app
Also flashing the stock Samsung ROM would also solve the problem as it would replace the wrongly edited build.prop with the stock build.prop.
Assuming you have the stock ROM downloaded on your PC, flash it using PC ODIN as explained in an earlier post.
Everything downloading, installing and rooting the stock ROMs is explained here by Dr Ketan
Once that is done, you can root your stock ROM and install mobile odin. You can then flash any custom kernel which is safe and has the brick bug covered. Factory wipe using a safe custom kernel wont brick your phone then.
I am not sure if flashing a safe custom kernel and doing a factory reset would replace the faulty build.prop file with a stock one directly. Chasmodo could explain more....
Flashing a stock ROM would surely replace everything with stock. So you have a clean stock state from which you can play around (rooting, custom kernels/ROMS, etc)
joey_oggie said:
And anyway, I thought wiping data = factory reset. Isn't that right? If so, then wouldn't the wipe fix his problem? I'm new to this stuff so excuse me if that's completely wrong.
Click to expand...
Click to collapse
Wiping /data won't touch /system where build.prop is
Sent from my GT-N7000 using xda premium
---------- Post added at 09:04 AM ---------- Previous post was at 08:55 AM ----------
PatrickNkamgnia said:
Hi Chasmodo,
I was just about to flash the Kernel of my GNote following Joey's + others advices above.
Please why do you think flashing the Kernel is not advisable? ... Do you think the phone will thereafter completely brick?
Please answer these two questions as quick as you can ... My finger is on the "red bouton" just waiting for you.
Could you also provide a link to a step by step tutorial in case the solution proposed by Joey is safe but comes unsuccessful ?
Thank you for your contribution.
Regards.
Click to expand...
Click to collapse
Xda is full of instructions on how to use odin search it. Flashing a kernel won't fix your problem. Best to do as previously advised and flash a new rom, stock or custom either will do
AND DON'T PANIC take it slow and don't do anything before you understand the process your phone is currently in no danger what so ever but a faulty flash can definitely brick it
Sent from my GT-N7000 using xda premium
apurvapatel said:
Also flashing the stock Samsung ROM would also solve the problem as it would replace the wrongly edited build.prop with the stock build.prop.
Assuming you have the stock ROM downloaded on your PC, flash it using PC ODIN as explained in an earlier post.
Everything downloading, installing and rooting the stock ROMs is explained here by Dr Ketan
Once that is done, you can root your stock ROM and install mobile odin. You can then flash any custom kernel which is safe and has the brick bug covered. Factory wipe using a safe custom kernel wont brick your phone then.
I am not sure if flashing a safe custom kernel and doing a factory reset would replace the faulty build.prop file with a stock one directly. Chasmodo could explain more....
Flashing a stock ROM would surely replace everything with stock. So you have a clean stock state from which you can play around (rooting, custom kernels/ROMS, etc)
Click to expand...
Click to collapse
Thank you all,
Really hope that this issue will help all GNote users when solved. Sure we are approaching the solution ...
I read in Dr Ketan tutorial the following:
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
Yesterday, after my GNote freezed on the "Samsung Galaxy Note N7000" image I tried to hard reset by wiping user data via ICS recovery (just after rooting the phone with CWM.
Does it means that my GNote is now bricked?
If it is the case shoud I anyway continue to follow Dr. Ketan tutorial to flash my GNote with a stock rom?
Regards.
PatrickNkamgnia said:
Yesterday, after my GNote freezed on the "Samsung Galaxy Note N7000" image I tried to hard reset by wiping user data via ICS recovery (just after rooting the phone with CWM.
Does it means that my GNote is now bricked?
If it is the case shoud I anyway continue to follow Dr. Ketan tutorial to flash my GNote with a stock rom?
Regards.
Click to expand...
Click to collapse
Very sorry to say buddy, your Note most likely is bricked. I hope I am wrong.
Try installing a stock ROM, preferrably Ginger Bread ROM via PC ODIN. If it fails, most likely, at FactoryFS write, then your phone is surely bricked.
Let us know how it goes, we can guide you further accordingly.
PatrickNkamgnia said:
Thank you all,
Really hope that this issue will help all GNote users when solved. Sure we are approaching the solution ...
I read in Dr Ketan tutorial the following:
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
Yesterday, after my GNote freezed on the "Samsung Galaxy Note N7000" image I tried to hard reset by wiping user data via ICS recovery (just after rooting the phone with CWM.
Does it means that my GNote is now bricked?
If it is the case shoud I anyway continue to follow Dr. Ketan tutorial to flash my GNote with a stock rom?
Regards.
Click to expand...
Click to collapse
see if you can still go to download mode and reflash a stock GB on your device. If it's successful then your good to go... if not, then look for the thread here to revive a brick phone.. note down the errors your getting (if there are any errors at all) when your going to reflash it again.
Hello, since I don't really like my custom rom (remics 1.4) I would like to install back my stock rom (normally the latest gingerbread since I couldn't do any update). But on sammobile I can't find any roms for my country, I'm from belgium. My phone isn't simlocked, I don't know if it has any use to know that?
Btw, my phone is a galaxy s plus (GT-i9001)
Sorry for the double post
abdelbachir said:
Btw, my phone is a galaxy s plus (GT-i9001)
Sorry for the double post
Click to expand...
Click to collapse
Here is a collection of an official Samsung released Roms:
Tutorial how to flash them HERE.
Thanks man, that's really helpful. So I can flash any of those roms without worying about being belgian or anything?
Should i format my phone before flashing those roms?
From my experience you should do a wipe/factory reset before Odin the stock Rom.
I have Odin a stock Rom without wipe and it didn't boot so I cf-root, wipe from recovery and booted.
Sent from my GT-I9100 using xda app-developers app
Ok, so if I understand i should do : Wipe Data, Wipe Cache, Wipe Dalvik Cache and hop, I turn off my phone, go into download mode and flash the stock rom immediatly?
abdelbachir said:
Ok, so if I understand i should do : Wipe Data, Wipe Cache, Wipe Dalvik Cache and hop, I turn off my phone, go into download mode and flash the stock rom immediatly?
Click to expand...
Click to collapse
Exactly!:laugh:
Thanks man, you're a beast, really fast answer
sorry to bother you a bit more, but I prefer to be cautious with all of this, these roms, more precisely the XXKPU one (last in the list) is I think from poland? Does it have any importance? Since I am belgian, i need the french language haha
Oi, guys, I really need help please!! I did wipe data/factory reset in clockworkmod, then i closed my phone and flashed the stock rom (XXKPU) with Odin. But now my phone isn't booting! Or more precisely, It's just the sequence with the "S" appearing that comes over and over again!! What did I do wrong and what can I do please??
abdelbachir said:
Oi, guys, I really need help please!! I did wipe data/factory reset in clockworkmod, then i closed my phone and flashed the stock rom (XXKPU) with Odin. But now my phone isn't booting! Or more precisely, It's just the sequence with the "S" appearing that comes over and over again!! What did I do wrong and what can I do please??
Click to expand...
Click to collapse
Boot into cwm and either wipe data again or your are going to have to flash the stock again. I have had to do that in the past
Sent From My YP-G1 running ICS build 3.5
I tried booting in cwm but I can't, failed like 5 times. A few tries, I got an android robot with some sort of opened box next to him.
abdelbachir said:
I tried booting in cwm but I can't, failed like 5 times. A few tries, I got an android robot with some sort of opened box next to him.
Click to expand...
Click to collapse
This is your WIKI http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001 it contains everything you need to help you, get a better understanding of your phone
1) 19001 uses Odin 4.43
2) need AriesVe.ops file for flashing
3) IF CWM failed flash CWM 6.0
4) If boot failed flash a i9001 boot loader ( look in My Android collections , link below or use your WIKI)
Thanks a lot man, flashed the cwm in the phone, did a wipe data/factory reset and it works like a charm now. I'll defenitly do a bit of reading to understand my phone a looot better!
Hi,
I was redirected to this part of the forum. A friend of mine rooted my samsung mobile Galaxy S I9000 with a android 2.2 version. I cannot contact him anymore to help me with the update and I am really a newbie in this rooting world. So, I am coming on this forum to have some advice. I read information on rooting your device, in which everything is explained very well, but could not find information on how to update once a device was rooted (probably I did not search in the right place). What I did so far is:
1) Taking backup of my pics (by manually drag and drop the folder on my pc), SMS and call logs (with sms backup + app), syncronized my contacts with gmail so that I can recover them later on and backup the music folder. I installed backup Titanium to back up my apps on my SD card.
But now, I am stuck with some questions (could you guide me where to find the information?):
1) Which most recent version of Android is supported on the device I have? Which version will work best?
2) Is there important information that I forgot to back up? + I have a problem with the backup Titanium app. It could reach my root in the beginning, but then the Superuser app updated the binary and from then on my titanium app got stuck when getting access to the root. Any idea how to solve this? Install an older version of the bin.file? How to do that exactly? thanks! => I could fix this problem by installing an older version of superuser in CW recovery. If others have problems with this issue, I can provide help from now on
3) Is there a guide with step by step procedure on which files I have to download on my pc and which procedure to follow? Or could you advice me some useful links?
thanks!
1) there is android 4.2.2 available for this amazing device
2) you propably forgot to backup efs folder
3)
- 1) follow this guide to get android 2.3.6 to your device: http://www.darkyrom.com/index.php?threads/odin-darkyrom-10-2-resurrection-gt-i9000.4272/
- 2) follow this guide to get android 4.2.2 (cm 10.1) to your device after: http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd
- 3) now you can flash most of the roms you find in i9000 android development forum. i personally use slimrom
copy /efs! backup ur imei n md5 in efs first! copy da whole efs file! or do nandroid backup.
READ N FOLLOW CAREFULLY here
http://forum.xda-developers.com/showthread.php?t=2149455
considering u already done flashing Sammy n CF
prepare for ROM & kernel(optional) hunt! go to dev section and choose which JB u wanted.download it together with cm9.1.0 n copy to root of internal sd.
n make sure to flash cm9.1.0 stable from cyanogenmod website (galaxymtd) first from 2.3.6, first flash will bootloop, go back to recovery with 3 combo button. flash again n dont leave recovery.
after done flashing twice (if flash ended too quick, then flash again). direct flash 4.1/4.2 chosen rom, twice (first flash will come up with error, juz ignore it flash again (bootloop) recovery again n flash again
Sent from my GT-I9000 using xda premium
A bit off topic, but i didnt want to start a new thread for that...
My question is: is there an android 4.0 version with full touchwiz?
I mean the whole tweaks as slide the contact to message/call and so on
I only foubd CM 9 based ROMs which are themed to look like touchwiz and had the launcher...but i miss the sms app interface, smilies, slide to call things
Is there a port from the SGS2?
Greets Vauvenal7
Sent from my SGS i9000
Vauvenal7 said:
A bit off topic, but i didnt want to start a new thread for that...
My question is: is there an android 4.0 version with full touchwiz?
I mean the whole tweaks as slide the contact to message/call and so on
I only foubd CM 9 based ROMs which are themed to look like touchwiz and had the launcher...but i miss the sms app interface, smilies, slide to call things
Is there a port from the SGS2?
Greets Vauvenal7
Sent from my SGS i9000
Click to expand...
Click to collapse
maybe nope, but try mod urself by searching on theme n app section
Sent from my GT-I9000 using xda premium
Thanks guys!! Will have a look at your suggestions! I guess both explanations are more or less equivalent !! Right?
mogwai123 said:
Thanks guys!! Will have a look at your suggestions! I guess both explanations are more or less equivalent !! Right?
Click to expand...
Click to collapse
yap, its da same, but do some reading first
Sent from my GT-I9000 using xda premium
when I copy my efs folder, I see that it is empty. any idea? I should not proceed further? What should I do?
UPDATE: phone still finds my IMEI number when dialing *#06#
if ur imei intact, then leave it, i dont know which ROM ur using but try to see /efs with option show hidden in rooted file explorer
Sent from my GT-I9000 using xda premium
I followed the guide you mentioned here:
http://forum.xda-developers.com/show....php?t=2149455
in which they install that JVU ROM... then they say at the end that you have to unmount SD card (but that option was gray in my case) and wipe the USB storage and then reboot in recovery and do those 4 wipes, what I did, and then he mentioned that you could install your custom ROM, so I put the version of slimrom 4.2.2 on my sd card and launched it for installation.
However, the procedure started, but after a few seconds already my phone rebooted and now it is stuck at the logo of Semaphore...
What did I wrong? And what should I do?
mogwai123 said:
I followed the guide you mentioned here:
http://forum.xda-developers.com/show....php?t=2149455
in which they install that JVU ROM... then they say at the end that you have to unmount SD card (but that option was gray in my case) and wipe the USB storage and then reboot in recovery and do those 4 wipes, what I did, and then he mentioned that you could install your custom ROM, so I put the version of slimrom 4.2.2 on my sd card and launched it for installation.
However, the procedure started, but after a few seconds already my phone rebooted and now it is stuck at the logo of Semaphore...
What did I wrong? And what should I do?
Click to expand...
Click to collapse
Should I shut down my phone and try to put it in download mode again to put the JVU rom on it again via odin? is that the best strategy? Or should I do something else? and if that would work, what is then the best procedure to avoid such situations again?
nope, u did rite, but also wrong, ok, read carefully here....
flashing for upgrade is easy if u follow carefully, when in GB, after flashing CF ROOT, flashing to 4.0 (cm9) first (take da zip from cyanogenmod website) but luckily ur on 2.3.6 JVU (if u follow da link i gave), so it will be safe (safe procedure will be GB-ICS-JB), first flash will bootloop, second flash (sometimes) will occur error n third flash will succeed, which means u hav to flash twice or thrice or maybe 4 times! if its bootloop, go to recovery back by 3 button combo (its da matter of when u release da combo button, release it rite after u see da first white bootsplash)
bootloop cause by changing da partition tp ext4, its common
but if u already try to reach recovery n failed most times, u need to flash back firmware n cf root.
Sent from my GT-I9000 using xda premium
compacity said:
nope, u did rite, but also wrong, ok, read carefully here....
flashing for upgrade is easy if u follow carefully, when in GB, after flashing CF ROOT, flashing to 4.0 (cm9) first (take da zip from cyanogenmod website) but luckily ur on 2.3.6 JVU (if u follow da link i gave), so it will be safe (safe procedure will be GB-ICS-JB), first flash will bootloop, second flash (sometimes) will occur error n third flash will succeed, which means u hav to flash twice or thrice or maybe 4 times! if its bootloop, go to recovery back by 3 button combo (its da matter of when u release da combo button, release it rite after u see da first white bootsplash)
bootloop cause by changing da partition tp ext4, its common
but if u already try to reach recovery n failed most times, u need to flash back firmware n cf root.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Ok, thanks!!!! this worked!!! I justed flashed cm9 and it works. So, if I understand well now, I can just return in recovery mode and install from zip from sd card to cm10 and then for instance to slimrom? Or between 'two' flashes, I need to follow the last part of the procedure in the link you gave me? So:
"Now, what I do now is go into :
Settings > SD Card and Storage > Unmount SD and Wipe that and then at the bottom Wipe Format USB Storage
Enable USB Debugging > Plug in Phone
Window should open up showing your phone Directory..
Copy over your ROM that you want
Shut Down Phone
Reboot into Recovery (Vol UP - Menu - Power)
Wipe the 4 things (probably know these... you should do)
Data / Factory Reset
Cache Partition
Go to Advanced > OK
Dalvik Cache
Battery Stats
Go Back > OK
To move Up or Down > Use the Left Side Volume Rocker Switches with Menu to OK Action
Install your Custom ROM from Zip Card that you want..."
OR: can I just go to recovery mode and do install from zip without doing that procedure with "wipe" etc?
Just to know, as I am just a newbie in these things!!! But I want to thank you once again for the clear explanations and the good help!!!!
juz flash mate , its easy, da important thing is to follow da sequence, thats all, juz flash, wiping cache or resetting juz for changing ROM. not upgrading
juz FLASH it
GB-ICS (twice)(do not leave recovery after second flash)-(any custom JB ROM u choose(twice or thrice))(make sure u already put da zip file in internalsd). dont need any wiping.
but FLASH AT UR OWN RISK,remember that.
n yes, recovery need hardbutton except TWRP recovery.
Sent from my GT-I9000 using xda premium
---------- Post added at 10:57 AM ---------- Previous post was at 10:34 AM ----------
here info
updating ROM from firmware (juz flash)
changing from custom ROM to any custom ROM (wipe ALL cache, factory reset, wipe dalvik n mount system n format system)
changing/flashing inbetween custom kernel (wipe cache n wipe dalvik cache)
fone slowing down (reboot or fix permission)
changing/flashing/applying tweak (wipe dalvik cache)
Sent from my GT-I9000 using xda premium
compacity said:
juz flash mate , its easy, da important thing is to follow da sequence, thats all, juz flash, wiping cache or resetting juz for changing ROM. not upgrading
juz FLASH it
GB-ICS (twice)(do not leave recovery after second flash)-(any custom JB ROM u choose(twice or thrice))(make sure u already put da zip file in internalsd). dont need any wiping.
but FLASH AT UR OWN RISK,remember that.
n yes, recovery need hardbutton except TWRP recovery.
Sent from my GT-I9000 using xda premium
---------- Post added at 10:57 AM ---------- Previous post was at 10:34 AM ----------
here info
updating ROM from firmware (juz flash)
changing from custom ROM to any custom ROM (wipe ALL cache, factory reset, wipe dalvik n mount system n format system)
changing/flashing inbetween custom kernel (wipe cache n wipe dalvik cache)
fone slowing down (reboot or fix permission)
changing/flashing/applying tweak (wipe dalvik cache)
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Thanks!!!! Just one small question. I just flashed CM10 in recovery mode and first flash gave error, second went well. Then while still being in recovery mode I directly flashed slimrom and that went well from the first time. Do you always flash a second time to make sure that things went well or this is ok then?
mogwai123 said:
Thanks!!!! Just one small question. I just flashed CM10 in recovery mode and first flash gave error, second went well. Then while still being in recovery mode I directly flashed slimrom and that went well from the first time. Do you always flash a second time to make sure that things went well or this is ok then?
Click to expand...
Click to collapse
as i already said, flash more than 2 times when upgrading, juz upgrading process. GB-ICS-JB (CM7-CM9-CM10/10.1) is upgrading process.
changing ROM not necessarily need double flashing, but u can do it if ur not satisfy whether da ROM already flashed or not
Sent from my GT-I9000 using xda premium
ok, thanks!!! no, everything is working fine with this slimrom, except for google play that does not seem to open once I install it. It opens and closes directly... but I guess there are persons that had the same problem. will have to check the forum for a solution
mogwai123 said:
ok, thanks!!! no, everything is working fine with this slimrom, except for google play that does not seem to open once I install it. It opens and closes directly... but I guess there are persons that had the same problem. will have to check the forum for a solution
Click to expand...
Click to collapse
Hmmm, is probably because I get this error when starting slimrom: invalid IMEI number...I flashed it a second time, but it gave me the same error...
Which gapps have you flashed? Slimbean needs a special package, you find it under slimroms.net.
Sent from my GT-I9000 using xda app-developers app
wget21 said:
Which gapps have you flashed? Slimbean needs a special package, you find it under slimroms.net.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
I will have a look there for that google play problem.
More problematic is that problem of IMEI. When I flashed from CM 9 to CM10 I did not do that wipe of cache and data as suggested above (the reply came later on), and then I flashed slimrom. That I forgot to wipe between CM9 and CM10, can that be the cause of wrong IMEI now? Is the solution now, to wipe cache and data, to flash again CM 10 and to flash then slimrom again?
Or should I just leave everything like that and do a recovery of my efs folder? If yes, any link for this?