Apologies if this is answered elsewhere but I've been looking around the forums and a lot of information/posts from people seem to conflict or the information is only valid for X kernel or Y kernel etc and it can still be a little overwhelming even after lots of nice people have posted guides.
I bought a German Note about a month ago and upgraded to 4.0.3 through the devices own update method (I have not flashed any ROMs on this device), leaving me on XX-LPY. I have since rooted the device, and did not perform any kinds of wipes doing this, this was the only time I even used CWM, I havent booted into CWM since (or used any of the normal recovery features).
The device has been working fine for around a week, I've restarted it several times without issue. However today after restarting it gets stuck on the Samsung logo and will not boot properly. The only thing I have used root for is to uninstall Kies and the SNS Push stuff (which seemed to save me a lot of battery life) and install ad-free android. I also installed the Carbon Tweaks app and applied the Carbon Booster stuff along with the Beats Audio and Bravia Engine stuff (nothing else).
I am able to get into recovery mode however I seem to be unable to put it into download mode (Edit: finally got it to do it once, wont do it every time though) so I have a few questions:
Can anyone tell me if its ruined or why its doing this?
Is it safe to just factory reset/wipe cache through normal android recovery (not CWM?).
Is it safe to try to flash another ROM through CWM (I'm on XX-LPY) and if so which one is safe for me to flash?
Is it safe to try to flash through Odin and if so which ROM should I flash?
I really dont care about the data on it or wiping it w/e. I just dont want to turn it into a paperweight if I can help it.
Thanks
Edit: Also if it makes any difference, this is the method I used to root the device:
http://forum.xda-developers.com/showpost.php?p=20963730&postcount=3
Nope, don't go around flashing stuff with CWM on that device.Also, you can't wipe as that may trigger the MMC_CAP_ERASE causing superbrick.Judging by what you say you've done, I'd say I don't know why it happened but it isn't ruined.
You can try to flash a stock GB rom of your country by following dr.ketan's guide in the dev section and then rooting it (if you want).Alternatively,you could just take it to a Samsung service center as there is no yellow triangle.But I'd try to flash the GB rom as flashing a stock kernel via PC Odin doesn't increase the flash counter.
Related
I bought a captivate 3 days ago (in Canada), and I had previously an HTC magic and did tons of tinkering (G1/MT3G have serious development.. kinda dying down sadly.. )
Obviously, I started looking into rooting captivate as well, and other stuff. Just wanted to ask people stuff if I can get them answered.
What is the purpose of ODIN other than flashing your phone back to stock? It is a great program, but I am used to just wiping data and flashing a new update.zip from recovery to get a flash a new ROM. Not wiping from 2.1 eclair to get to cognition kind of threw me off. Can I not use ODIN and go the traditional way and flash the update.zip's?
Also, from ODIN, what exactly is master clear? Does it wipe off everything in the phone? Why would this be preferred over a factory reset from recovery?
I tried googling/looking through captivate dev and couldn't find the answers. Thank you!!
koreancanuck said:
I bought a captivate 3 days ago (in Canada), and I had previously an HTC magic and did tons of tinkering (G1/MT3G have serious development.. kinda dying down sadly.. )
Obviously, I started looking into rooting captivate as well, and other stuff. Just wanted to ask people stuff if I can get them answered.
What is the purpose of ODIN other than flashing your phone back to stock? It is a great program, but I am used to just wiping data and flashing a new update.zip from recovery to get a flash a new ROM. Not wiping from 2.1 eclair to get to cognition kind of threw me off. Can I not use ODIN and go the traditional way and flash the update.zip's?
Also, from ODIN, what exactly is master clear? Does it wipe off everything in the phone? Why would this be preferred over a factory reset from recovery?
I tried googling/looking through captivate dev and couldn't find the answers. Thank you!!
Click to expand...
Click to collapse
Odin is a windows program leaked from samsung for flashing the galaxy s phone - can be used to flash kernel, firmware or modem or all three at once - NOT used to flash update.zip
Odin 3 one click is for flashing back to stock was made available by dg as a simple recovery method in case of a soft bricked phone or if you flashed your phone and wanted to get back to stock.
Master clear in odin wipes all or most all the data from your internal sd card - I believe factory reset just wipes user settings, cache and account info
with samsung update.zip are flashed via recovery as I am guessing is nearly the same way you have done on other phones
As you can tell there are multiple methods for flashing, spend time reading and learning about them until you have a good understanding about what you are doing with each
Of by the way there is also rom manager clockwork recovery (can get rom manager from the market and install once you are rooted) - don't get this confused with stock recovery
dayv said:
Odin is a windows program leaked from samsung for flashing the galaxy s phone - can be used to flash kernel, firmware or modem or all three at once - NOT used to flash update.zip
Odin 3 one click is for flashing back to stock was made available by dg as a simple recovery method in case of a soft bricked phone or if you flashed your phone and wanted to get back to stock.
Master clear in odin wipes all or most all the data from your internal sd card - I believe factory reset just wipes user settings, cache and account info
with samsung update.zip are flashed via recovery as I am guessing is nearly the same way you have done on other phones
As you can tell there are multiple methods for flashing, spend time reading and learning about them until you have a good understanding about what you are doing with each
Of by the way there is also rom manager clockwork recovery (can get rom manager from the market and install once you are rooted) - don't get this confused with stock recovery
Click to expand...
Click to collapse
So I'm understanding master clear doesn't wipe the actual ROM? Wouldn't master clear just be the same as just deleting all the stuff from the internal sd card via my laptop?
And thanks for your answers I never used clockwork till now, was using amon_RA recovery cuz it gave some problems to G1/MT3G users but it seems to work wonders on captivate.
I have two phones (one is wife's and that one is the problem - oh boy..) - they are the gt-i9000 and had firmware's XXJP2 (a July or August build 2010) and they worked badly. So I wanted to try MIUI and flashed my phone according to instructions and when doing the flash of the speedmod kernel I couldn't boot. The phone just gets to the first screen (the Samsung GT-i9000 words) and vibrates repeatedly: one vibration then a quick 3, repeat. I eventually got that phone to JVH and am pretty happy with it.
Then tried to do same on wife's. Couldn't use 3 button recovery so used ADB to get it in download mode (mistake - I know - I've learned alot since in my research to fix the resulting brick). Eventually got it into download mode again and tried installing MIUI using instructions: flashed the speedmod kernel and got the same vibrations on boot as my phone. So flashed the JVH and now it boot loops. Goes through the boot animation and noise over and over.
Before I bricked the phone I installed the galaxy_efs tar to try to back that up but it didn't get a chance since I bricked it on the speedmod flash (just got the phone-!-computer icons). Got past that. I also, before starting all this, used Titanium Backup to backup all user apps and data (think I didn't do system apps - maybe another error). I think it may have gone to Dropbox (haven't checked - it is her account).
So question: looks like I am supposed to reflash a Froyo 3 file plus .pit file to come out of this. I've downloaded both the JP2 firmware as well as a newer JPY which I thought I would try first. But before repartitioning and all that I'm hoping there is something I can try to get out of the bootloop without the 3 file flash. Hope to try to make sure there's still her data on there, maybe be sure to back up the efs file and stuff. Possible to just try clearing cache from recovery mode or something - has that worked?
Efs file: is that specific to phone or (if I lost hers) can I use the backup from mine since both phones were purchased at same time? I suspect it may be specific to phone but maybe there's a chance not.
Any thoughts on why the speedmod kernel didn't flash correctly on each phone - ending up with a vibrating non-booting phone? I used Odin 1.82. I would like to try MIUI but can't seem to get past that kernel step.
thanks, JD
Firstly I apologize for posting in Q&A's, due to the 10 post restriction I was unable to post in the rocket rom thread in android development and Q&A's seemed the second most ideal place.
After a day of horror, I tried merely flashing Abyss Kernel 4.2 but I ended up somehow in a soft brick accessing the recovery and download modes only. After ages I decided to try my luck installing Rocket rom v7 and it thankfully worked and my phone is up and running.
However, I have faced a couple of issues with it, of which the major one is the lack of response when hitting the home (center key) on my international version of the galaxy note. It doesn't work whatsoever, I've also noticed that the lock screen has disappeared too, so when I put the phone to sleep and wake it I get taken to the page I closed on rather than the lock screen. The latter I have fixed by using widgetlocker, although I am still oblivious as to how to fix the home key losing it's function.
Any advice etc? (especially if it's kept in layman terms, and nothing drastic... I despise flashing!!)
Moreover I was just wondering is there a set of instructions one could follow to return to a stock rom on the galaxy note via CWM?
Kind regards and thanks for your time
9009i said:
Firstly I apologize for posting in Q&A's, due to the 10 post restriction I was unable to post in the rocket rom thread in android development and Q&A's seemed the second most ideal place.
After a day of horror, I tried merely flashing Abyss Kernel 4.2 but I ended up somehow in a soft brick accessing the recovery and download modes only. After ages I decided to try my luck installing Rocket rom v7 and it thankfully worked and my phone is up and running.
However, I have faced a couple of issues with it, of which the major one is the lack of response when hitting the home (center key) on my international version of the galaxy note. It doesn't work whatsoever, I've also noticed that the lock screen has disappeared too, so when I put the phone to sleep and wake it I get taken to the page I closed on rather than the lock screen. The latter I have fixed by using widgetlocker, although I am still oblivious as to how to fix the home key losing it's function.
Any advice etc? (especially if it's kept in layman terms, and nothing drastic... I despise flashing!!)
Moreover I was just wondering is there a set of instructions one could follow to return to a stock rom on the galaxy note via CWM?
Kind regards and thanks for your time
Click to expand...
Click to collapse
on what rom did you flash v7 ?
iam currently running it no issues at all, everything works maybe you 'll have to do a clean install just flash abyss kernel full wipe with it and reflash the rocketrom v7 using it dont not reboot until you flash the ROM since you flash a GB kernel on an ICS system....... wont boot just softbrick. watch it!
sounds like the system files a corrupt somehow and btw if case you changed kernel let us know too....
REVERSiN said:
on what rom did you flash v7 ?
iam currently running it no issues at all, everything works maybe you 'll have to do a clean install just flash abyss kernel full wipe with it and reflash the rocketrom v7 using it dont not reboot until you flash the ROM since you flash a GB kernel on an ICS system....... wont boot just softbrick. watch it!
sounds like the system files a corrupt somehow and btw if case you changed kernel let us know too....
Click to expand...
Click to collapse
Ah yes sorry wasn't clearn.
I was firstly on ICS 4.0.3 stock rom XXLPY, I kept getting nagged about the kernel instability so I went and tried to flash Abyss kernel 4.2 (somehow stuffed it up ended up soft bricked). So I then flashed Rocket Rom v5 (after properly flashing Abyss kernel) via CWM. I think follow the steps to upgrade to v7.
Tbh I really do not want to mess with flashing and ODIN again >.> have become paranoid.
9009i said:
Ah yes sorry wasn't clearn.
I was firstly on ICS 4.0.3 stock rom XXLPY, I kept getting nagged about the kernel instability so I went and tried to flash Abyss kernel 4.2 (somehow stuffed it up ended up soft bricked). So I then flashed Rocket Rom v5 (after properly flashing Abyss kernel) via CWM. I think follow the steps to upgrade to v7.
Tbh I really do not want to mess with flashing and ODIN again >.> have become paranoid.
Click to expand...
Click to collapse
Grr couldn't find the post edit button, but tbh I do think it's a setting issue or so I am hoping I did play around with the rocket rom tweakbox and I imagine that may have been the cause of this issue or so I am hoping
Dont worry reboot to recovery and flash v7 again and reboot (no need to wipe or flash other kernels )
Sent from my GT-N7000 using Tapatalk 2
REVERSiN said:
Dont worry reboot to recovery and flash v7 again and reboot (no need to wipe or flash other kernels )
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Wouldn't that just give me 2 copies of rocket rom and cause issues? Or will it install missing files?
So I should just install zip from SD and that's all?
Ok I am redownloading now and going to give it a shot.
Moreover, I would love for any advice on how I can return to stock rom... any advice would be most welcome. I'd prefer only to use CWM.
Or if there is perhaps another fix the issue above? Any comments would be most appreciated!
First of all yes you can install zip from as and select v7 (no it won't harm it will overwrite all files Yes, I understand want have duplicates unless they are from another rom but again full wipe would have removed them from before so you are ok.
Well idunno about CWM stock rom I prefer you use either pc odin or mobile odin (recommended) just charge the phone to 100% and install mobile odin set you stick firmware on sdcard and select open file in mobile odin then in case you want the root keep options as they are and select wiping option both. In case you don't want root deselect the object superuser options and still check the willing one
About home key issue might be a script issue one of hardware files is messed up so I can't tell for sure which but mostly the files are at system/usr/
Sent from my GT-N7000 using Tapatalk 2
REVERSiN said:
First of all yes you can install zip from as and select v7 (no it won't harm it will overwrite all files Yes, I understand want have duplicates unless they are from another rom but again full wipe would have removed them from before so you are ok.
Well idunno about CWM stock rom I prefer you use either pc odin or mobile odin (recommended) just charge the phone to 100% and install mobile odin set you stick firmware on sdcard and select open file in mobile odin then in case you want the root keep options as they are and select wiping option both. In case you don't want root deselect the object superuser options and still check the willing one
About home key issue might be a script issue one of hardware files is messed up so I can't tell for sure which but mostly the files are at system/usr/
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for all your help REVERSiN, just to update you.
I tried re-installing v7 rocketrom and flashing however still faced the same issue of the home key etc. So I kept a stock rom in my external SD went to CWM recovery and did a full wipe, delvik cache wipe and cache wipe tried installing the stock rom however CWM had issues opening it and aborted. So I installed rocketrom v7 again and voila it works perfectly now and seems brilliant.
I think I still want to return to stock eventually, but I refuse to use Odin, I tried using odin twice and both times it froze the first on factorycs (although my phone wasn't bricked) and the second time yesterday on cache so yah I have had terrible luck with ODIN and I refuse to use it,.
Nonetheless if there is way to flash stock rom using CWM would be epic. However, until I am 100% sure on how to do it I'll be sticking to rocketrom.
Thanks again for all your help and time!
my sons sg i9000 was rooted with a custom rom but then started playing up, now when i've wiped it and tried put new rom on it, all it does it force crash everything that was existing on his phone, so it looks like it is not wiping the phone anymore for some reason, i've tried flashing rom by odin but still the same effect, is there anything out there that totally wipes the phone for sure and then will allow me to put phone back to stock and then reroot.
many thanks if anyone can help as i am totally stuck now and my son is without his phone.:fingers-crossed:
If you restock via odin, usually all datas are deleted and wipes are done.
In this thread you will find many usefull things, also slappys rescue kit, in Android rescue, Recovery Kits content, which I used often and helped me a lot of times: i9000 Rescue EzBase Rescue with CF Root & semaphore root by nitr8 & chainfire, repacked by slaphead20
btw: the problem you mention seems to me more that you probably flashed a wrong ROM, which is not compatible to your device, or something went wrong during the installation?
rodman01 said:
If you restock via odin, usually all datas are deleted and wipes are done.
In this thread you will find many usefull things, also slappys rescue kit, in Android rescue, Recovery Kits content, which I used often and helped me a lot of times: i9000 Rescue EzBase Rescue with CF Root & semaphore root by nitr8 & chainfire, repacked by slaphead20
btw: the problem you mention seems to me more that you probably flashed a wrong ROM, which is not compatible to your device, or something went wrong during the installation?
Click to expand...
Click to collapse
thank you for the advise i will try and see what i can do
still having trouble with the phone, every time i reflash stock rom with odin it keeps starting up but then i have a lot of force close box popping up saying about all his old apps and and setting force closing and then when it get to the start up wizard it says it has forced closed and then can not go any further, this is why i cant understand why when i wipe all data and system it is not wiping it for some reason,im waiting on a download recovery for it but if anyone can understand what i mean and no a fix i will be most grateful as i have spent many hours now searching through xda for a answer and can not find any.:fingers-crossed::fingers-crossed:
Could you give us some more information? What device do you have? And which ROMs did you try to flash? Which stock and which custom ROMS? And when do have the problems? After reboot from flashed stock rom or after flashing the custom rom? I think the stock rom you try to flash does not fit to your device?
i have tried the stock rom from samfirmware and my device is a galaxy s i9000, the custom rom was a old gingerbread rom, the problem comes when i have flashed the new stock rom with odin, it flashes with odin not a problem but then when it boots up and starts to go through the first 6 or 7 steps of the phones steps, ie ( keyboard use, packed data settings, wifi on or off and so on) it keeps popping up little dialog boxes saying sorry google play is not working force close and goes through a whole load of stuff saying the same thing for them all, hope this helps a little but is hard to describe
I would suggest to flash an other rom via odin. Try the rescue pack from slappy. Inside that pack, there should be a txt file, where additional infos are included how to use the different files. It could be that the sam firmware is not fully compatible with your phone or sometimes the download is corrupt or something else...
rodman01 said:
I would suggest to flash an other rom via odin. Try the rescue pack from slappy. Inside that pack, there should be a txt file, where additional infos are included how to use the different files. It could be that the sam firmware is not fully compatible with your phone or sometimes the download is corrupt or something else...
Click to expand...
Click to collapse
ok thank you i will try that,
thank you for all the help today but think the phone is knackered nothing will work anymore on it nothing will boot up properly :crying:
no problem and you welcome...better would have been if my proposals had worked...but perhaps you are right and there is a hardware defect or something else...perhaps even a fluid defect....or it is only stressed for today and tomorrow all is fine again ! So head up, and don't give up.
Hope you flashed Stock GB ROM with pit file and Re-partition ticked
Hi everyone
First of all a little history:I used this [PhilZ-cwm6][n7000] v4.93.6 Safe Stock Kernel+CWM6+Root+exFAT+ext4-LT4 to root my n7000 on 4.0.4 (I bought it with 4.0.4).
Then after some time Android wanted an upgrade to 4.1.2 and after some time I just tried it and it failed after booting into recovery mode, because it didnt find a the expected kernel, I think. But I had the chance to boot up again.
OK I then did the update with Kies-Software and everything worked again. Then I rooted the phone again using the same method as mentioned in the post above.
Now today the phone wanted to update again, I thought, OK, if it didnt fail completely the first time, it will fail in recovery mode and let me boot up again.
But...
This time it went into recovery mode and didnt let me boot up again. It just shows the robot with the crystal and the progress bar seems to move a little but then the screen goes black for a second and the robot returns and the progress bar moves a little and the same again.... I dont get into the recovery menu.
I tried samsung kies emergency recovery, it doesnt find my n7000.
I tried to flash the kernel with a newer version from the post above. (I am not allowed to post there). No change it gets stuck in broken recovery mode.
I can push volumedown power and home to get into the download mode.
My question is what can I do?
Is there any other chance to avoid a complete stock recovery (is that the right term/way)?
What do I have to flash and how?
I am a little worried about the brick issues and I dont know which version I have to flash to set it back completely...
Please help & thanks
drz
No worries, since your download mode is still working you can flash a stock Samsung ROM via odin. Download one from here and flash it in odin while in download mode. Latest at this point of time is LT4 http://forum.xda-developers.com/showthread.php?t=1424997
This will give you the stock JB Bootloader, Recovery, and ROM. Its completely unrooted though, and the phone will not be wiped in the process, so remember to do so after you flashed it.
cr0wnest said:
No worries, since your download mode is still working you can flash a stock Samsung ROM via odin. Download one from here and flash it in odin while in download mode. Latest at this point of time is LT4 http://forum.xda-developers.com/showthread.php?t=1424997
This will give you the stock JB Bootloader, Recovery, and ROM. Its completely unrooted though, and the phone will not be wiped in the process, so remember to do so after you flashed it.
Click to expand...
Click to collapse
Thanks a lot, crownest!
I sweated a bucket of blood and seat, because I couldnt wipe cache and data first, but it worked!!!
Everything looks like before!´the update!
Some more questions (sorry):
do you think I should wipe cache and data now?
Is a stock rom like the rom on internal usbcard only?
What about the update? Can I update safely now?
Thanks again for helping...
greetz
drz
Yup you should be able to wipe cache and dalvik with no issues now.
I believe all ROMs be it stock or custom installs to the NAND memory (Someone correct me if im wrong) and never on your internal/external SDcard
As for OTA updates via Kies, I dont see why not, but if the same issue does reoccur again then my suspicions would point to a possible NAND corruption on the device. Not sure if there is a fix for that, but its a risk you gotta take. Or you can always root the phone and flash custom ROMs as new builds get released, this way you'll never have to use OTA updates again.