Related
I'm running CM9, before that CM7, and before that I had a problem with my 3-button recovery I believe I was on stock 2.2 I had used a fix somewhere in the forum for the 3 button fix and it worked. But now for example if I flash a different modem and or Google apps it does flash but then I get Power Reset or Unknown Upload Mode error screen. I have to pull the battery out and it will reboot. I think this may have something to due to the boot loaders? Any help would be helpful thanks.
I think it's a product of that 3 bottom fix, which you should never flash again. To be sure, you should probably just get on gingerbread bootloaders
Sent from my CM9 ICS i897 Captivate
Reminder, probably can't flash bootloaders while on cm/ics. I think the framework difference in that and Samsung causes problems. Also, try reformatting your internal memory sd card, just back everything you want to keep up first.
Lookup any Heimdall one click GB ROMs and enable bootloaders update. Apex ROM one of them.
is there a way i can just flash the boot loaders without going back to stock?
dave1977nj said:
is there a way i can just flash the boot loaders without going back to stock?
Click to expand...
Click to collapse
You technically can, but you won't be able to boot without flashing to stock from there. So don't do it
Sent from my CM9 ICS i897 Captivate
Well it was a pain in the a$$ went to stock UCKK4 2.3.5 had to root that then had to change the kernel to corn for CWM recovery and flahed CM9 back. Took me like 2 hours the problem is now fixed
dave1977nj said:
Well it was a pain in the a$$ went to stock UCKK4 2.3.5 had to root that then had to change the kernel to corn for CWM recovery and flahed CM9 back. Took me like 2 hours the problem is now fixed
Click to expand...
Click to collapse
You can root from corn. It's really easy
Sent from my CM9 ICS i897 Captivate
I flashed my captivate out of box having 3-button issue and installed cyanogen mod 9 which did not detect my PC so I tried to downgrade to cm_captivatemtd_full-179 from which I could not boot. Its continuously rebooting from bootloaders screen. Can you please help me fixing it..?
sriram_mech86 said:
I flashed my captivate out of box having 3-button issue and installed cyanogen mod 9 which did not detect my PC so I tried to downgrade to cm_captivatemtd_full-179 from which I could not boot. Its continuously rebooting from bootloaders screen. Can you please help me fixing it..?
Click to expand...
Click to collapse
To clarify, are you only seeing the white AT&T World Phone screen?
Sent from my CM9 ICS i897 Captivate
I can see the At&T white screen....after that its goes into cyanogen mod screen and then cwm mode pops and again restating...
sriram_mech86 said:
I can see the At&T white screen....after that its goes into cyanogen mod screen and then cwm mode pops and again restating...
Click to expand...
Click to collapse
Boot into recovery, do a factory reset, wipe dalvik cache, then install from SD card.
cant go back to stock rom galaxy i897 at&t
hello can someone help me please? i have a samsung i897 captivate it turns on but dont starts logo at&t pass google logo pass then a multicolor image appears and thats all, i try with the hard reset but fail the only thing that appears its this,
modem booting...
end modem booting.
now start usb upload.
an android image Power reset or UNKNOWN UPLOAD MODE,
i only want the stock rom from at&t help me please
Hey guys I an using lpy ROM
As some people said This official rom also having emmc bug and they said it can break phone in cwm9 recovery and In factory reset
So tell me how can I check that my phone also having that bug ?
As cwm and emmc command can be gived on only rooted phone and the break problem happens to the peoples who had upgraded from mobile odin and having phone rooted... So tell me will.my phone can be also break ?
-My phone is un rooted
-I flashed ics through PC odin
-I haven't done Any factory reset and also I don't have to do it.. Cox I don't need to do
-I transferred 100-500mb files from my laptop to phone...
-also I deleted 1 800mb folder from my phone
Tell me please how can I check that bug ?
Sent from my GT-N7000 using XDA
sjshubham said:
Hey guys I an using lpy ROM
As some people said This official rom also having emmc bug and they said it can break phone in cwm9 recovery and In factory reset
So tell me how can I check that my phone also having that bug ?
As cwm and emmc command can be gived on only rooted phone and the break problem happens to the peoples who had upgraded from mobile odin and having phone rooted... So tell me will.my phone can be also break ?
-My phone is un rooted
-I flashed ics through PC odin
-I haven't done Any factory reset and also I don't have to do it.. Cox I don't need to do
-I transferred 100-500mb files from my laptop to phone...
-also I deleted 1 800mb folder from my phone
Tell me please how can I check that bug ?
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
you should be fine if you don't wipe data in recovery or do factory data reset!
you can't really check that bug, it is present in kernels for ICS ROMs
ALL ICS kernels are affected except those built from CM9 source (ROMs like: Asylum ICS, MIUI ROM and the new Paranoidandroid ROM)
If you don't want to do any wiping or flashing through recovery, you can stay for now on LPY ROM, but I suggest that you flash a safe ICS ROM with safe kernel as soon as it becomes available!
HI mix, thanks for the reply...
Bro I don't wanna use any other ROM.... I want to use stock ROM only... Cox I got this phone after allot struggle and I don't wanna give it for even 1 hour to Samsung CC
They won't care of na phone I love it
Can you tell me is there any stock ROM available which is fully safe ? Bug free....
Sent from my GT-N7000 using XDA
Stock gingerbread is safe, and has good battery life. But if you are already on ICS, i would advise to stick with it for now, until devs figure out the brick bug fix. And if you really want flashing back to gb, search the forum for guide and read carefully. I upgraded to ics and went back to gb twice without any problem using Pc Odin. But that's just me.
Sent from my GT-N7000 using Tapatalk 2
Hi ltd.
I, am also thinking to stick with ics
But the doubt entered in my mind
Tell me if the phone get beaked than Samsung will ask me for money ?
My phone is new... I baught it previous month
And flashed with ics before a weak...
And my friend who also flashed ics... he had done factory reset 2 times... And not got a single problem !
What's your opinion? Will phone won't break if it had flashed through PC ics ?
And what about Germany users? Who had officially upgraded it from kies ?
Have they also got the bug ?
Sent from my GT-N7000 using XDA
It doesnt matter how you flash Ics. There is still a bug in the kernel which makes wipe/flash operation dangerous, and could potentially damage your eMMC. I said potentially because there are a lot of users that succesfully flash and wipe without problem, but some wasnt so lucky.
If you dont do any wipe/flash with LPY kernel, then you are safe. Dont worry. I used ics german rom just fine, smoother,faster app loading and various improvement over GB. However battery life was hit and miss. The phone couldnt enter deep sleep state.
If you brick your Note, just bring it to the shop. Tell them you left it to charge overnight and found it dead in the morning. They probally give a replacament. This depends on where you live and waranty conditions though.
Sent from my GT-N7000 using Tapatalk 2
Ok that's grate..... I had backed up my not
And I don't think so it will get break
But bro you saying I can't flash also ! So now when the Indian ics will available than how I will be able to upgrade with that ? it will also need to upgrade by flashing ?
and what the hell happens when phone gets break ?
Sent from my GT-N7000 using XDA
Ok,i'm on LPY German + CFroot + done wipe cache twice(using Mobile odin to flash ICS & CFroot from Rocketrom GB v23) & TOTALLY scared to revert back to GB or superbrick my GNote. Here's what EXACTLY i do,happened & my opinions:
1.Download Abyss 4.2 kernel, Prerooted GB XXLC1 from bodivas thread,ODIN1.85,RocketRom GB V23 & put it into single folder (unzip prerooted GB rom-3 files & unzip ODIN1.85).Put Abyss4.2&Rocketrom GB v23 to phone internal memory. ODIN&Pre-rooted stay in my pc(in case Abyss&Rocketrom FAILED & Gnote not brick).
2.Backup & shutdown my GNote.
3.Get into CWM (combo button -Volume up,home & power)
4.Flash Abys4.2 kernel successfully & go to Advanced in CWM - Reboot Recovery & wait till GNote reboot & get into Redpil Recovery.
5. Still in Redpill Recovery - wipe data/factory reset,cache & dalvik - STAY IN REDPIL RECOVERY,DONT REBOOT!!!
6. Still in redpil - flash Rocketrom GB v23 - success & Reboot System.
7. MY GNOTE STUCKED IN ROCKETROM BOOT ANIMATION & SCREEN ARE BLANK/BLACK & NO RESPONSE!!!!Try reflash Rocketrom & still same FAILED result!!
Okay,here's what i do next:
1.Take out battery - put my Gnote to Download Mode (Combon buttons - Volume Down,Home & Power).
2. Start Odin1.85 & I just followed instructions in Bodivas thread using Prerooted ROM that i download before...unzip & have 3 files.
3. Connect GNote(still in Download Mode) to my laptop (while odin still running) & green in odin (detect & added).
4. Put 3 files to PDA,Modem & CSC.
5. DOuble check....again&again (dont repartition!!!)
6. START.
7. Gnote Autoreboot & continue installation in Gnote....and reboot GNote again.
8. Gingerbread started & successfully reach the settings..the one "Touch Logo to Settings"......fuhh!!!!! WHAT A RELIEF!!!!!
My opinions:
1. If you on Stock German LPY & STILL NO CF ROOT - the easiest,safe & simplest way is FLASH with ODIN using Prerooted GB (Full-wipe prefered) rom.
2. If you on Stock German LPY + CFRoot & no wipe at all OR Stock Grm LPY + CF ROOT + Wipe Cache - the SAFEST is using Abyss4.2 kernel,Custom GB rom & if failed...use ODIN. Abyss4.2 kernel is important if u failed..u're stil in GB Kernel & can use ODIN (GNOte still can get into CWM or DOnwload Mode).
Anyway,thats myexperience & opinions...maybe dont apply to your GNote....just want to share to all.
Hello XDA,
I Need some help with My galaxy note n7000, its was purchased from Kogan, and was in German when I first got it,
I have not been able to find anything on this Forum yet so;
I Had ICS 4.0.4 installed, Stock, and wanted to try CM9
so after rooting and installing CWM I backed up my device, and flashed the "Safe" CM9 kernal with Odin,
My device now hangs on the Boot up screen, and All I can do is the Download files from Odin, I have tried flashing many different kernels and re installing the Stock Rom (it says leaving CS?), without any Luck,
I am wondering if I need a different Rom, and am currently trying to download the Gingerbread roms in an attempt to roll back,
Any help would be appreciated guys and gals.
Nexus
Nexusomega486 said:
Hello XDA,
I Need some help with My galaxy note n7000, its was purchased from Kogan, and was in German when I first got it,
I have not been able to find anything on this Forum yet so;
I Had ICS 4.0.4 installed, Stock, and wanted to try CM9
so after rooting and installing CWM I backed up my device, and flashed the "Safe" CM9 kernal with Odin,
My device now hangs on the Boot up screen, and All I can do is the Download files from Odin, I have tried flashing many different kernels and re installing the Stock Rom (it says leaving CS?), without any Luck,
I am wondering if I need a different Rom, and am currently trying to download the Gingerbread roms in an attempt to roll back,
Any help would be appreciated guys and gals.
Nexus
Click to expand...
Click to collapse
did u wipe in cmw when u were in ics??
if yes... sorry to inform u that u may have bricked ur device
try this link to revive ur device http://forum.xda-developers.com/showthread.php?t=1667886...
if this also fails u ll have to go to samsung service center to get it repaired...
after flashing CM9 kernel your device will not boot up, its natural , a TW rom will not boot with CM9 kernel
you should have entered recovery with three button treatment and done your wipes and flashed CM9 and gapps.
i dont know at what point you are right now,
try flashing a rootable GB rom with pc odin in download mode, then root it ...then get into recovery and flash CM9 etc etc
if you are bricked your flash will stop at factory fs in pc odin..... (fingers crossed)
A cm9 kernel for TW, of all the poor luck!
Sent from my GT-N7000 using xda app-developers app
Install cm9 rom thru cwm and wipe cache / dalvik. Try rebooting now.. Good luk.
Sent from my GT-N7000 using xda app-developers app
Hey all,
Quite confused here, taking the advice from the older threads I flashed using odin the stock firmware which I got from samfirmware and followed the instructions. Everything installed correctly however the phone will not boot :S
I ticked only PDA in which I entered the md5 file.
Came from cm9 nightly and flashed United Kingdom (Carphone Warehouse) 2012 July 4.0.4 N7000XXLRK N7000CPWLP5
Any help is appreciated and needed urgently - Thank you.
-Shaizer
did you make a nandroid?
if you could get into recovery, (and you still have CWM) it would imply that you did not successfully flash the tw-based kernel.
no tw-based kernel means that a TW-based rom will not boot (unless you had hydracore)
buut... if you do have the stock ICS kernel on there, and try to flash anything, you could brick.
so best bet is to flash GB via odin, then flash CWM, SU, and then flash a custom ROM with a safe kernel in it.
pretty dangerous to even use stock ICS rom
when u say phone will not boot? is it blank or stuck on GT N7000 logo or the Samsung glowing logo?
Its stuck on glowing Samsung logo, I'm in download mode now - what is the best option for me? Might just flash GB rom
guitarplayerone said:
did you make a nandroid?
if you could get into recovery, (and you still have CWM) it would imply that you did not successfully flash the tw-based kernel.
no tw-based kernel means that a TW-based rom will not boot (unless you had hydracore)
buut... if you do have the stock ICS kernel on there, and try to flash anything, you could brick.
so best bet is to flash GB via odin, then flash CWM, SU, and then flash a custom ROM with a safe kernel in it.
pretty dangerous to even use stock ICS rom
Click to expand...
Click to collapse
How can I go into recovery to check that? I only know how to get into download mode.
Shaizer said:
Its stuck on glowing Samsung logo, I'm in download mode now - what is the best option for me? Might just flash GB rom
Click to expand...
Click to collapse
getting into recovery is the opposite of getting into download mode. use power button/ volume up/ home instead of power button/volume down/home
but IMO safest thing to do at all is to just get yourself onto a safe kernel before doing anything else.
flash yourself a stock pre-rooted GB ROM via odin.
http://forum.xda-developers.com/showthread.php?t=1535025
then read this
http://forum.xda-developers.com/showthread.php?t=1424997
this way you will ensure that you are on a safe kernel.
from there get yourself a working version of CWM and move on to whatever ROM you want.
are you trying to flash stock ICS for a service request for the phone, etc? you might be much better off with any stock-based ICS rom.
if after this you REALLY REALLY want a stock ICS rom, then use mobile odin to flash the ROM but use a 'safe' stock kernel with mmc_cap_erase disabled.
this is the closest you can get to bone stock but safe. (this will not even get you rooted).
another advantage of starting with pre-rooted GB stock and going from there is no raised flash counter either.
guitarplayerone said:
getting into recovery is the opposite of getting into download mode. use power button/ volume up/ home instead of power button/volume down/home
but IMO safest thing to do at all is to just get yourself onto a safe kernel before doing anything else.
flash yourself a stock pre-rooted GB ROM via odin.
http://forum.xda-developers.com/showthread.php?t=1424997
this way you will ensure that you are on a safe kernel.
from there get yourself a working version of CWM and move on to whatever ROM you want.
are you trying to flash stock ICS for a service request for the phone, etc? you might be much better off with any stock-based ICS rom
Click to expand...
Click to collapse
Doing this now, hope it works - using the GB rom from when I first rooted (from GB) so hopefully should work
its just a matter of doing a wipe cache and wipe dalvik and data wipe. but as u on ics u can't. unless u install a safe kernel. If you installing gb, then after that reboot into recovery
vol up + pwr + home and then do a data factory reset, wipe cache and all should be good
Shaizer said:
Doing this now, hope it works - using the GB rom from when I first rooted (from GB) so hopefully should work
Click to expand...
Click to collapse
it's possible, but quite unlikely, that you have already hardbricked your phone between flashing stock ICS via odin and the boot.
more likely than not you are fine.
next time remember to make a nandroid. and never flash stock ICS kernels (or especially flash anything while already on a stock ICS kernel). these are the top 2 rules of having an n7000. if you follow them in teh future you will never have any problems
and please thank me if my posts helped
FWIW there were reports of hard bricks using the new stock JB kernel too, as Samsung decided to patch the bug 'their own way', which didn't seem to work. so only thing which is 100% safe is when mmc_cap_erase is disabled
Ah Relief - Finally got the phone booted into GB rom. How can I now install the Stock unrooted ICS room? Can't I just upgrade using OTA? I'm selling the note on ebay so need it to be fresh ICS.
as the phone is in the boot loop its clear indication that it's a data corruption problem and not a brick at all. Just need that wipes after ics install on a safe kernel
guitarplayerone said:
getting into recovery is the opposite of getting into download mode. use power button/ volume up/ home instead of power button/volume down/home
but IMO safest thing to do at all is to just get yourself onto a safe kernel before doing anything else.
flash yourself a stock pre-rooted GB ROM via odin.
http://forum.xda-developers.com/showthread.php?t=1535025
then read this
http://forum.xda-developers.com/showthread.php?t=1424997
this way you will ensure that you are on a safe kernel.
from there get yourself a working version of CWM and move on to whatever ROM you want.
are you trying to flash stock ICS for a service request for the phone, etc? you might be much better off with any stock-based ICS rom.
if after this you REALLY REALLY want a stock ICS rom, then use mobile odin to flash the ROM but use a 'safe' stock kernel with mmc_cap_erase disabled.
this is the closest you can get to bone stock but safe. (this will not even get you rooted).
another advantage of starting with pre-rooted GB stock and going from there is no raised flash counter either.
Click to expand...
Click to collapse
nokiamodeln91 said:
as the phone is in the boot loop its clear indication that it's a data corruption problem and not a brick at all. Just need that wipes after ics install on a safe kernel
Click to expand...
Click to collapse
Thanks for this, you're right it wasn't a brick - I'm now on a safe GB rom but really want this note to be in a stock unrooted ICS rom for the person buying it off me.
Connect to kies and update. If not use the same ics rom and flash it using odin. This time phone will start.
Before that while on gb do a factory reset.. connect to pc and format internal storage for you to get rid of all data
edit:
post removed.
if you are selling it, then I guess bone stock (without even safe kernel) is the way to go
just bear in mind with my method it is possible to get onto stock unrooted ICS but with a kernel without the bug.
I am not 100% certain if the phone will update OTA with that kernel though, so I guess use the other method
guitarplayerone said:
with all due respect- this is not true.
yes, in the general case, this is a sign of a softbrick. and if he never mentioned a stock ROM, it would definitely be a soft brick
however, there have been folks with hard bricks who have had /system and /data partitions screwed up who have even booted all the way into the OS. yes HARD brick. implying that there are actual corrupted partitions.
updating to stock ICS rom will put the affected kernel right back on his phone.
flashing another kernel from the affected kernel brings chance of a hard brick. (yes even though hypothetically you are only flashing /boot. but would you really take that chance with /boot? there have been reports of other partitions besides /data and /system being messed up, FYI)
it makes much more sense to flash the ROM via mobile odin, which gives you the option to flash a safe kernel at the same time.
this way OP is never on an unsafe kernel.
just because very few people bricked from flashing a safe kernel off off stock ICS doesn't mean that it isn't possible.
Click to expand...
Click to collapse
So if I use the OTA install method, there is a risk of bricking my device? I really don't think the person buying my phone will fiddle around with roms and kernels - so what do you reckon I should do? Does mobile Odin download a safe kernel for me?
give it in stock gb only.. let. him upgrade
nokiamodeln91 said:
give it in stock gb only.. let. him upgrade
Click to expand...
Click to collapse
this
nokiamodeln91 said:
give it in stock gb only.. let. him upgrade
Click to expand...
Click to collapse
Hmmm this current GB rom is rooted though so you reckon its better to unroot it and just sell as GB? I didn't specify GB or ICS
Shaizer said:
Hmmm this current GB rom is rooted though so you reckon its better to unroot it and just sell as GB? I didn't specify GB or ICS
Click to expand...
Click to collapse
Flash stock GB over odin.
if you wanted to be nice to the user, you could flash a ROM with a CSC corresponding to whatever region they are located in. That way you can factory reset and it will show up in the language they are used to.
If he is on stock, it will automatically go look for updates and tell him he could update
guitarplayerone said:
Flash stock GB over odin.
if you wanted to be nice to the user, you could flash a ROM with a CSC corresponding to whatever region they are located in. That way you can factory reset and it will show up in the language they are used to.
If he is on stock, it will automatically go look for updates and tell him he could update
Click to expand...
Click to collapse
Might actually have to do that, this phone is european so it starts in German...since when did German become the EU language right?! We won the war
(sorry for my English )
the thing is that my Samsung S wont starts ,when i click the power button its starts in CWM RECOVERY and when i press "reboot system now" it enters a boot loop (the logo keeps running over and over and the phone)
before this happened i originally had the stock ROM of my cellular carrier (2.3.3
then i decided to install another rom and kernel (cyanogenmod 10) so i installed first a clean stock rom (2.3.6) via odin
and then the cyanogenmod rom and kernel (up to now its all fine)
after that i wanted to change and install other rom so i installed again the clean stock rom 2.3.6 via odin...and from then it started to boot loop.
i thought that if i will install the kernel again it will be OK ,but it wont..
and now im in the situation that i have described above..
help SOMEONE please=]
LCPD said:
(sorry for my English )
the thing is that my Samsung S wont starts ,when i click the power button its starts in CWM RECOVERY and when i press "reboot system now" it enters a boot loop (the logo keeps running over and over and the phone)
before this happened i originally had the stock ROM of my cellular carrier (2.3.3
then i decided to install another rom and kernel (cyanogenmod 10) so i installed first a clean stock rom (2.3.6) via odin
and then the cyanogenmod rom and kernel (up to now its all fine)
after that i wanted to change and install other rom so i installed again the clean stock rom 2.3.6 via odin...and from then it started to boot loop.
i thought that if i will install the kernel again it will be OK ,but it wont..
and now im in the situation that i have described above..
help SOMEONE please=]
Click to expand...
Click to collapse
it is because the latest CM10 is based on a different partitioning layout than the stock one.. after flashing CM10 once when you go in a boot loop.. go to CWM recovery by using the three button combo and flash CM10 again.. . this time your rom will boot:good:
replay
ishangoyal said:
it is because the latest CM10 is based on a different partitioning layout than the stock one.. after flashing CM10 once when you go in a boot loop.. go to CWM recovery by using the three button combo and flash CM10 again.. . this time your rom will boot:good:
Click to expand...
Click to collapse
I installed the kernel and then the stock rom again but now its just bootlooping without getting load up to CWM recovery
so how can i get into CWM recovery????
(i tried VolumeUP+HOME+POWER but it just get into regular recovery...)
pull out your battery for a couple of minutes then replace battery
;hold three button forever or until it goes into recovery if that doesnt work
reflash through odin and do it again or check out darkyrom 10. re this gets flashed through odin
LCPD said:
I installed the kernel and then the stock rom again but now its just bootlooping without getting load up to CWM recovery
so how can i get into CWM recovery????
(i tried VolumeUP+HOME+POWER but it just get into regular recovery...)
Click to expand...
Click to collapse
flash darkyrom 10.2 Resurrection edition using odin.. this will give you a GB rom with root
flash CM10 through CWM recovery
reboot.. (you may not be able to boot as of now)
go to CWM recovery again using 3 button combo
flash CM10 again
reboot
this should do the trick
THANK YOU TWO
the Darkys rom 10.2 re was great --- it starts now hahah
i Will try now another rom (not cyagonmod but PilotX)
thank you very muchhhhhhhhhhhhhhhhhhhhhhhhhhhhhh