Database Develop

[Q] Stuck in bootloop - What should I do?

Good evening guys!
So I'm stuck in a bootloop, and it doesn't look that I will come out of it. I'm running ROCKET ROM V22, and the Abyss3.9 kernel.
So what do you recomend me to do?
I'll now over the night keep my phone on, to try to get out of the bootloop. But I would need som advice what I shall do.
The problem is that the phone won't mount as a storage device in the computer. And I have no backup in my phone, only on the computer, so I can't restore it easy.
Help me! *said with panic on my voice*
Best regards MinnesotaVikings1961

Hi there,
Bootloops happen every now and then, if something collides or is misconfigured.
In my very own experience most boot loops happen to be script related.
This is why you should´t worry too much.
You still can enter CWM?
If so enter CWM and wipe completely (factory, cache, dalvik) and after that (NO REBOOT!!!) just reflash the ROM which just didn´t happen to work properly.
If it still is in boot loop there might be something wrong with the ROM.
> Rom is guarantied completet? No broken Download?
> Rom is really for the exact telephone model you got? (Galaxy S for example has several submodels which slightly differ from original)
In case you do not have a rooted device without CWM only thing you can do, is to begin from scratch by flashing an official ROM from Samsung via odin.
With that you should flash a kernel with CWM next time, cause it much easier to recover your device including you´ll keep all your private stuff.
Flashing the Samsung-Rom via odin will kill anything saved but the external SD.
hope this helps
# Rodger #

DJ-Tumor said:
Hi there,
Bootloops happen every now and then, is somethine collides or is misconfigured.
In my very own experience most boot loops happen to be skript related.
This is why you should´t worry too much.
You still can enter CWM?
If so Enter CWM, wipe completely (factory, cache, dalvik) and after that (NO REBOOT!!!) just reflash the ROM which just didn´t happen to work properly.
If ist still is in bootloop there might be something wrong with the ROM.
> Rom is guarantied completet? No broken Download?
> Rom is really for the exact telephone model you got? (Galaxy S for example has several submodel which slightly differ from originall)
In case do not have a rooted device without CWM only thing you can do, is to begin from scrath by flashing an official ROM from Samsung via odin.
With that you should flash a kernel with CWM next time, cause it much easier to recover your device incl. you keep all your private stuff.
Flashing the Sasmung-Rom via odin will kill anything saved but the external SD.
hope this helps
# Rodger #
Click to expand...
Click to collapse
Have done as you said, but still problems.
One of the problems maybe can be that it isn't CWM but RedPill.
Yes, I did download the whole file, so no strange abort of the download.
And this is the correct ROM for the Galaxy Note.
If I still have this problems in 24 hours I will contact my store and let them know what I think. I want my money back. I can also add that I'm studying law, so I let the lawbook speek for itself.
But thanks for a fast answer!

Well sad to hear that. Laws have to be different from those in germany
You´re obviously trying to flash inofficial stuff on your own. There is no way the shop could be made resposible for.
So take my advice and reflash official ROM before you return the device.
That will help enormously.
But before runnign too fast, try to give some more information to us here:
What ROM are you trying to flash?
What ROM is installed before trying to flash?
What Kernel is used to flash?
Are you using mobile Odin?
Try to answer questiones I just dind´t think of

DJ-Tumor said:
Well sad to hear that. Laws have to be different from those in germany
You´re obviously trying to flash inofficial stuff on your own. There is no way the shop could be made resposible for.
So take my advice and reflash official ROM before you return the device.
That will help enormously.
But before runnign too fast, try to give some more information to us here:
What ROM are you trying to flash?
What ROM is installed before trying to flash?
What Kernel is used to flash?
Are you using mobile Odin?
Try to answer questiones I just dind´t think of
Click to expand...
Click to collapse
The laws are maybe a little bit diffrent. For example, the first 6 months, the seller or shop needs to prove that the product was working when the sold it. Something that they have very hard to prove.
I'm trying to install the ROCKET ROM V22 for SGN.
I had the MidNote V2.0
The Abyss3.9 kernel (I think that it's the correct way of spelling it).
No, I'm not using mobile Odin.
Edit: Can I install a stocket ROM, with my phone in bootloop, and non mountin as a drive in the computer?

MinnesotaVikings1961 said:
Good evening guys!
So I'm stuck in a bootloop, and it doesn't look that I will come out of it. I'm running ROCKET ROM V22, and the Abyss3.9 kernel.
So what do you recomend me to do?
I'll now over the night keep my phone on, to try to get out of the bootloop. But I would need som advice what I shall do.
The problem is that the phone won't mount as a storage device in the computer. And I have no backup in my phone, only on the computer, so I can't restore it easy.
Help me! *said with panic on my voice*
Best regards MinnesotaVikings1961
Click to expand...
Click to collapse
You need to flash rocket rom v20 before v22 that i belive is or problem if u can mount sdcard to computer u may have to take sdcard out of your phone and put in something else to load the program on the card then put back on phone and then flash v20 of rocket rom and then see if it boots up if it dose then u can flash v22
Sent from my GT-N7000 using XDA Premium HD app

Edit: Can I install a stocket ROM, with my phone in bootloop, and non mountin as a drive in the computer?[/QUOTE]
U could in download mode with odin pc
Sent from my GT-N7000 using XDA Premium HD app

Quick google search shows boot loops are pretty well known with this rom.
No you only can flash original rom with odin.
If there are important data on the device connect it cia usb and boot into cwm.
Now wath what happens. If you´re lucky mass storage mode is enables in the kernel and you got your storage mounted automated.
If not it´s time to cross fingers and search for an option to mount by hand.
I´m completely new to NOTE - all my knowledge comes from my i9000 which is a mega active community compared to the one of the NOTE
There is have the choice between 5 different ICS kernels alone
Each one has it´s abilities, so does one have the option to mount storage by hand.
This option can be found in "advanced". Hope this menu option is present in your rom
good luck!
# Rodger #

MinnesotaVikings1961 said:
The laws are maybe a little bit diffrent. For example, the first 6 months, the seller or shop needs to prove that the product was working when the sold it. Something that they have very hard to prove.
I'm trying to install the ROCKET ROM V22 for SGN.
I had the MidNote V2.0
The Abyss3.9 kernel (I think that it's the correct way of spelling it).
No, I'm not using mobile Odin.
Edit: Can I install a stocket ROM, with my phone in bootloop, and non mountin as a drive in the computer?
Click to expand...
Click to collapse
Yeah you can. Just go to this thread. Get a rootable rom downloaded. Just follow the instructions to the word of how to flash via odin. And you will have stock rom. And you can again root and install custom rom!! No need to run back to store !
Links-
Roms and guide- http://forum.xda-developers.com/showthread.php?t=1424997
Rooting and odin - http://forum.xda-developers.com/showthread.php?t=1329360

Midnote 2, as in ICS Midnote? You couldn't have been on AbyssNote 3.9, because it's a gingerbread kernel.
Perhaps it was Angelom's stock ICS rooted kernel?
Or did you flash AbyssNote 3.9 from Recovery, trying to go back to GB?

chasmodo said:
Midnote 2, as in ICS Midnote? You couldn't have been on AbyssNote 3.9, because it's a gingerbread kernel.
Perhaps it was Angelom's stock ICS rooted kernel?
Or did you flash AbyssNote 3.9 from Recovery, trying to go back to GB?
Click to expand...
Click to collapse
Well, I had been using ICS MidNote for a short time, due to a friend mine wanted to see ICS for the Note.
Now I tried to get back to my regular GB ROM.
/ Jimmy

You have me utterly confused here...What is the latest rom you were on before this bootloop? Midnote 2 or RR 22?
If Midnote 2 (ICS) with Angelom's kernel, and you did a factory reset at some point, there's hardly anything you can do except take your phone to Samsung service. If you had CF--Root ICS kernel, then try to follow this little set of instructions:
http://forum.xda-developers.com/showpost.php?p=22758543&postcount=6

chasmodo said:
You have me utterly confused here...What is the latest rom you were on before this bootloop? Midnote 2 or RR 22?
If Midnote 2 (ICS) with Angelom's kernel, and you did a factory reset at some point, there's hardly anything you can do except take your phone to Samsung service. If you had CF--Root ICS kernel, then try to follow this little set of instructions:
http://forum.xda-developers.com/showpost.php?p=22758543&postcount=6
Click to expand...
Click to collapse
Sorry for being confusing you!
Before this bootloop I was running MidNote V2.0, ICS. I then tried to flash ROCKET ROM, V22. And when I started up, this bootloop came up, and isn't solved in writing moment, very many hours later.
/ Jimmy

Case closed
I can now say that the case is closed. What I did is very simple. In fact, so simple I never thinked about it. The only thing I did was to unroot my phone using Odin.
But thanks for all tips and support!
/ Jimmy

What did I do wrong? N7000 bricked.

Good evening!
I've around with Androids for quite some time, and today, I finally got my N7000 to replace my I9100.
I've played around quite a lot with my I9100 and was happy with the CM9 nightlies for it.
I got my N7000 today and did the following:
1. Rooted it with this method: http://forum.xda-developers.com/showthread.php?t=1501719t=1501719
2. Decided to install the latest CM9 nightly. I booted the same CWM from the tutorial above, chose install zip from SD card and... It hang. I left it for about 5 minutes and nada, nothing. I decided to shut if off and...
3. Nada. Black screen, no recovery, no battery charging, no download mode, no nada, nothing. Dead!
I'll take it this week to the nearest Samsung repair center and check how much it's gonna cost to get it fixed (if they can get it fixed at all). I don't intend to use any warranty whatsoever since I know even tough I have not voided the warranty flashing a different kernel, I did messing with it.
I just wish to know what was my mistake, so I do not do it again in the future. AFAIK I did not mess with the bootloader, so I was supposed to be safe, right?
Do I have ANY hope of getting it resurrected?
Any opinion helps!
Thanks!

marcelo.ellmann said:
Good evening!
I've around with Androids for quite some time, and today, I finally got my N7000 to replace my I9100.
I've played around quite a lot with my I9100 and was happy with the CM9 nightlies for it.
I got my N7000 today and did the following:
1. Rooted it with this method: http://forum.xda-developers.com/showthread.php?t=1501719t=1501719
2. Decided to install the latest CM9 nightly. I booted the same CWM from the tutorial above, chose install zip from SD card and... It hang. I left it for about 5 minutes and nada, nothing. I decided to shut if off and...
3. Nada. Black screen, no recovery, no battery charging, no download mode, no nada, nothing. Dead!
I'll take it this week to the nearest Samsung repair center and check how much it's gonna cost to get it fixed (if they can get it fixed at all). I don't intend to use any warranty whatsoever since I know even tough I have not voided the warranty flashing a different kernel, I did messing with it.
I just wish to know what was my mistake, so I do not do it again in the future. AFAIK I did not mess with the bootloader, so I was supposed to be safe, right?
Do I have ANY hope of getting it resurrected?
Any opinion helps!
Thanks!
Click to expand...
Click to collapse
ALWAYS flash a GB Kernel or ROM BEFORE flashing a CUSTOM ICS ROM.

Okay. Lesson learned, trust me.
Now here's the part where I feel very stupid: what's a GB kernel? Why is that a requirement for ICS ROMs? Was it not for Gingergread ROMs?
And now here's the second part where I feel even stupidier: doesn't the kernel reside on the ROM/OS part of Android? Why would the kernel, which comes AFTER the bootloader, affect the boot of the Android? Wouldn't it just screw my phone, but wouldn't it still give me the chance of flashing another ROM?
Thanks for the help.

marcelo.ellmann said:
Okay. Lesson learned, trust me.
Now here's the part where I feel very stupid: what's a GB kernel? Why is that a requirement for ICS ROMs? Was it not for Gingergread ROMs?
And now here's the second part where I feel even stupidier: doesn't the kernel reside on the ROM/OS part of Android? Why would the kernel, which comes AFTER the bootloader, affect the boot of the Android? Wouldn't it just screw my phone, but wouldn't it still give me the chance of flashing another ROM?
Thanks for the help.
Click to expand...
Click to collapse
Because of an eMMC brick bug!
Anyways to round up, my way of flashing ROMS is flashing a GB Kernel called Abyss 4.2 and then reboot recovery, from then I wipe everything then flash any custom ICS Roms. I've had my Note for almost a week now and found no problems in flashing! But it did take me 2hrs to root doing heavy research but it paid off!
The guide I followed is from here take a few moments to read and understand then you will have no troubles in rooting/flashing again!

hing98 said:
Because ICS has not been officially released on the Galaxy Notes therefore we use a GB Kernel or ROM before we flash any custom ICS ROM.
Yes it was confusing at the start but to avoid bricking you must alwaysfollow the guides given by the Developer!
Anyways to round up, my way of flashing ROMS is flashing a GB Kernel called Abyss 4.2 and then reboot recovery, from then I wipe everything then flash any custom ICS Roms. I've had my Note for almost a week now and found no problems in flashing! But it did take me 2hrs to root doing heavy research but it paid off!
Click to expand...
Click to collapse
You may want to recheck your facts....ICS has actually been officially released in many countries......
Sent from my GT-N7000 using xda premium

stoney73 said:
You may want to recheck your facts....ICS has actually been officially released in many countries......
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Sorry was reading from another guide. Your right
---------- Post added at 01:12 PM ---------- Previous post was at 12:23 PM ----------
hing98 said:
Sorry was reading from another guide. Your right
Click to expand...
Click to collapse
Anyways its a bug that bricks your device,
you can find more information here
Cheers

I had a galaxy S where flashing process was different Wen u flash CM9 roms and if you want to get back to GB roms only way out was PC Odin and moreover you can wipe on ICS roms and install other roms. But wen i got the note the procedure was slightly different Brickin problems and moreover wen you are in ICS you can get back to GB with GB kernel only no need for PC odin. Just keep a copy of Abyss kernel 4.2 in your sd card and be sure to flash it when changing roms.....

Doesn't Franco rev3+ solve the brick bug?
Hi all,
since you're saying we have *always* to flash a GB kernel before having a factory reset, are you talking about those having the CF/Stock kernel?
I'll make it clear: as far as I know, Franco made a kernel that should avoid the brickage since its 3rd version (thread here --> http://forum.xda-developers.com/showthread.php?t=1491428). Who installed this kernel could just wipe from ICS and install any ICS ROM. Am I wrong? If so, please explain the whys.

UNBRICKED!
I too bricked my phone but after reading this guide (ABD wouldn't recognise my device so I couldn't follow it) I understood the partitions had become messed up.
I read somewhere about the PIT files.
I ODINed the ABYSS Kernal and PIT (Q1_20110914_16GB-patched) for my 16gb n7000 ticked the repartition box. It booted into CWM recovery and I used the restore and bingo.

How to (backup/)restore with CWM?

I am currently using the latest RocketROM V7.
I wanna know... if I am to backup and restore a ROM with ClockworkMod Recovery... how should I do it?
I flash Abyss Kernel 4.2, reboot recovery (so I am in the CWM modified by Abyss), backup the ROM... and when I wanna restore, I do the same?
If that's the way to go, when I restore, I'll have Abyss Kernel 4.2, and not the one that the ROM has... Erm... Can somebody shed some light?
I'm asking because I'm aware of all this talk about the eMMC bug (and the fact that it actually exists), and since CWM formats the internal memory... it'd result in a hard brick, haha...

if you backup on Abyss kernel you will be on Abyss kernel AFTER the restore, So ideally you should flash abyss BEFORE restoring, and then change the kernel AFTER (if you want to)
The brickbug is not to be taken lightly, Its a serious issue, so if you have to do things a certain way (I have a ritual for wiping lol) and it takes a little longer, So be it, at least you know you will be safe.......ish

azzledazzle said:
if you backup on Abyss kernel you will be on Abyss kernel AFTER the restore, So ideally you should flash abyss BEFORE restoring, and then change the kernel AFTER (if you want to)
The brickbug is not to be taken lightly, Its a serious issue, so if you have to do things a certain way (I have a ritual for wiping lol) and it takes a little longer, So be it, at least you know you will be safe.......ish
Click to expand...
Click to collapse
Hmm... so... forget about RocketROM for now.
Let's say I am on Half-Illusion, which has two kernels (optionally) : CM and AOKP.
-flash jBroid's Kernel Cleaning Script.
-flash Abyss 4.2 kernel.
-reboot recovery.
-backup.
When I restore, I do this :
-flash jBroid's Kernel Cleaning Script.
-flash Abyss 4.2 kernel.
-reboot recovery.
-restore.
-flash desired kernel.
azzledazzle said:
The brickbug is not to be taken lightly
Click to expand...
Click to collapse
You don't say . First time I heard about it and was about to wipe/flash for the first time, I was like http://www.youtube.com/watch?v=Y9KyBdPeKHg
-----
What's your wiping ritual? Could it better than mine ? Hope it doesn't involve summoning a lightning strike or anything like that...

Formhault said:
Hmm... so... forget about RocketROM for now.
Let's say I am on Half-Illusion, which has two kernels (optionally) : CM and AOKP.
-flash jBroid's Kernel Cleaning Script.
-flash Abyss 4.2 kernel.
-reboot recovery.
-backup.
When I restore, I do this :
-flash jBroid's Kernel Cleaning Script.
-flash Abyss 4.2 kernel.
-reboot recovery.
-restore.
-flash desired kernel.
You don't say . First time I heard about it and was about to wipe/flash for the first time, I was like http://www.youtube.com/watch?v=Y9KyBdPeKHg
-----
What's your wiping ritual? Could it better than mine ? Hope it doesn't involve summoning a lightning strike or anything like that...
Click to expand...
Click to collapse
HAHAHAAAA That video is epic, I can imagine you saying that lol, I too was like that.
And my ritual is similar to yours, Only for TW ROMs
Dont forget that your backup will be a GB ROM, so you cannot restore it if you venture on to TW ICS ROMs ! But im sure you knew that anyway !
Other than that, Your steps are spot on !

azzledazzle said:
And my ritual is similar to yours, Only for TW ROMs
Dont forget that your backup will be a GB ROM, so you cannot restore it if you venture on to TW ICS ROMs ! But im sure you knew that anyway !
Click to expand...
Click to collapse
Erm... what? Lol, explain.
What do you mean it will be a GB ROM? You mean the KERNEL, right?
What do you mean I can't restore it if I venture on to TW ICS ROMs (like RocketROM, for example)?

azzledazzle said:
HAHAHAAAA That video is epic, I can imagine you saying that lol, I too was like that.
Click to expand...
Click to collapse
Actually, it was like this.
So I first hear about the brick bug. http://tinyurl.com/69cc7we http://tinyurl.com/buvmsep
I decide oh well, can't stick with stock ROM. http://tinyurl.com/2at2ad4
So I go on with the wiping / flashing process. http://tinyurl.com/bmoff37
And once it was all done... http://tinyurl.com/4h7lp8q

Formhault said:
Actually, it was like this.
So I first hear about the brick bug. http://tinyurl.com/69cc7we http://tinyurl.com/buvmsep
I decide oh well, can't stick with stock ROM. http://tinyurl.com/2at2ad4
So I go on with the wiping / flashing process. http://tinyurl.com/bmoff37
And once it was all done... http://tinyurl.com/4h7lp8q
Click to expand...
Click to collapse
What I mean is, if your now on a gb rom such as cm9 or aokp And you create a nandroid backup, that backup is going to be a complete clone of your current set up. So you cannot restore that nandroid on a Samsung ics rom you can only restore it on a gb rom
Sent from my GT-N7000 using Tapatalk 2

azzledazzle said:
What I mean is, if your now on a gb rom such as cm9 or aokp And you create a nandroid backup, that backup is going to be a complete clone of your current set up. So you cannot restore that nandroid on a Samsung ics rom you can only restore it on a gb rom
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I didn't know AOKP had GB builds, too...
Anyway. I know what a CWM backup is, I've been in the Android world since exactly 13 months.
What do you mean I can't restore that NANDROID on a Samsung ICS ROM? As far as I know, a CWM restore erases all the contents (system, data, cache) and restores the respective data from the backup... so it's not like it would OVERWRITE on the current TW ICS ROM, for example.
What I wanna know is... I can back up everything, except for the kernel (since I'd flash Abyss 4.2 w/ recovery), and when I restore, I flash the kernel manually. That's all there is to it... right?!

When you are creating a backup...just drop into CWM and create backup. When restoring the backup you can flash the Abyss kernel first > reboot recovery > and then restore. So now when the restoring happens the kernel which was in your rom will automatically get restored and abyss will vanish once rebooted.
@azzledazzle CM9 is ICS and not a GB rom I know you know this and u just slipped your fingers while typing ...but just correcting so that no confusion arises to other readers
And if you are on any CM9 based rom or any AOKP based rom which is based on CM kernel then you dont require Abyss at all. Just forget about it when on any of the roms.
Hope this helps!
Cheers!

Yeah I know its an ICS ROM, But dont you have to be on GB to flash it ? What I mean is you cant flash it from Stock Samsung ICS can you? (thats how i understand it anyway)
And I didnt know CWM erases partitions, I thought it just overwritten the existing ones, Hence why I said dont restore a GB (AOSP ICS) on Samsung ICS (if that makes sense?)
But I guess ive learned something new from you Hopefully I can pass this new found knowledge onto someone else lol

azzledazzle said:
Yeah I know its an ICS ROM, But dont you have to be on GB to flash it ? What I mean is you cant flash it from Stock Samsung ICS can you? (thats how i understand it anyway)
Click to expand...
Click to collapse
Yeah you cant directly flash the CM9 or AOKP based on CM kernel directly over the Stock Samsung ICS. Its a sure shot brick you have in your hand if you do that. The stock ICS kernels cannot handle the "format" command in the updater script, CM is working on trying to use delete_recursive instead but still its not complete fixed. Hence you have to be on GB or on GB kernel (like Abyss) if you want to flash the CM9 based rom.

abhisahara said:
When you are creating a backup...just drop into CWM and create backup. When restoring the backup you can flash the Abyss kernel first > reboot recovery > and then restore. So now when the restoring happens the kernel which was in your rom will automatically get restored and abyss will vanish once rebooted.
Click to expand...
Click to collapse
Oh... you're right, lol. Backing up doesn't format/wipe anything. Only restoring does .
But... the CWM I have right now (was flashed among with RocketROM) is a different version, non-touch-driven, than the CWM that is included in Abyss 4.2 kernel (touch-driven). Are backups compatible?
abhisahara said:
And if you are on any CM9 based rom or any AOKP based rom which is based on CM kernel then you dont require Abyss at all. Just forget about it when on any of the roms.
Click to expand...
Click to collapse
So... you're saying that both CM9 and AOKP kernels have the eMMC thing removed, so wiping data when using those kernels is safe?
-----
Thanks for joining, abhi

abhisahara said:
Yeah you cant directly flash the CM9 or AOKP based on CM kernel directly over the Stock Samsung ICS. Its a sure shot brick you have in your hand if you do that. The stock ICS kernels cannot handle the "format" command in the updater script, CM is working on trying to use delete_recursive instead but still its not complete fixed. Hence you have to be on GB or on GB kernel (like Abyss) if you want to flash the CM9 based rom.
Click to expand...
Click to collapse
Bottom line... Better flash Abyss 4.2 before any full wipe .
-----
This thing in the Samsung ICS kernels... this brick bug... Is Samsung aware of it? Is a fix on the way? Or nobody knows?
Or perhaps it's been made on purpose
-----
Retorical question : WHY POSTS NO LONGER MERGE? -.- :headbang:

Formhault said:
Oh... you're right, lol. Backing up doesn't format/wipe anything. Only restoring does .
But... the CWM I have right now (was flashed among with RocketROM) is a different version, non-touch-driven, than the CWM that is included in Abyss 4.2 kernel (touch-driven). Are backups compatible?
The CWM you have with RocketRom comes from the kernel of ICS which is included in the rom. The Abyss 4.2 is a GB kernel hence it has it own touch recovery. Not sure what you meant by - "Are backups compatible?"
So... you're saying that both CM9 and AOKP kernels have the eMMC thing removed, so wiping data when using those kernels is safe?
Yeah its perfectly safe wiping data on these kernels.
-----
Thanks for joining, abhi
Click to expand...
Click to collapse
Formhault said:
Bottom line... Better flash Abyss 4.2 before any full wipe .
-----
This thing in the Samsung ICS kernels... this brick bug... Is Samsung aware of it? Is a fix on the way? Or nobody knows?
Or perhaps it's been made on purpose
They know. They might be fixing it. Not date from them.
-----
Retorical question : WHY POSTS NO LONGER MERGE? -.- :headbang:
Click to expand...
Click to collapse
Hope the above helps!! In bold are the answers

abhisahara said:
Hope the above helps!! In bold are the answers
Click to expand...
Click to collapse
Yup. Thanks.
What I meant by "Are backups compatible" was... are backups made with the CWM that comes with RocketROM (not touch-driven) compatible with the CWM that is included in Abyss 4.2 (touch-driven)? I mean... can I restore the backups made with one CWM, using ANOTHER CWM?
I always forget their versions...
-----
They KNOW? Good. Oh well, they also know their SAMOLED screens suck, but didn't do anything to fix it... Let's hope they're gonna fix this brick bug soon; although it seems highly unlikely... I mean, we already got 4.0.4, and that didn't fix it. The next update is probably going to be JellyBean (if we even get that officially!), some 5+ months from now on :/
This brick bug is utmost retarded. I mean... on the Note, and recently, on the SGS2 as well... they're either stupid, either it was on purpose - to prevent at least some devs on working on those devices...

Formhault said:
Yup. Thanks.
What I meant by "Are backups compatible" was... are backups made with the CWM that comes with RocketROM (not touch-driven) compatible with the CWM that is included in Abyss 4.2 (touch-driven)? I mean... can I restore the backups made with one CWM, using ANOTHER CWM?
I always forget their versions...
-----
They KNOW? Good. Oh well, they also know their SAMOLED screens suck, but didn't do anything to fix it... Let's hope they're gonna fix this brick bug soon; although it seems highly unlikely... I mean, we already got 4.0.4, and that didn't fix it. The next update is probably going to be JellyBean (if we even get that officially!), some 5+ months from now on :/
This brick bug is utmost retarded. I mean... on the Note, and recently, on the SGS2 as well... they're either stupid, either it was on purpose - to prevent at least some devs on working on those devices...
Click to expand...
Click to collapse
Yeah you can restore backup made with some other CWM while using another CWM.

Intrestin ^^
Sent from my GT-N7000 using XDA Premium App

[Q] eMMC brick Bug question

Hi Folks
Im a new proud owner of a Note, just got it today and loving it so far, waiting for JB in March though .
Ive checked and my Note has the "YES insane chip", however, i only flash Stock roms through odin and use Stock recovery after each flash, so am I right in reading that its only custom ROMS and Kernels that can brick it, so I never have to worry about it bricking or is there something i should be careful of when flashing stock roms as well.
Thanks

No, if you wipe your data through a factory reset there is a high chance in bricking the device.

XxPixX said:
No, if you wipe your data through a factory reset there is a high chance in bricking the device.
Click to expand...
Click to collapse
Oh.. wow, how can Sammy release hardware like this then, thats pretty bad. I take it the New S3s and Note 2s dont have thiese chips then.
Cheers

Samsung claims, that recent stock recoveries are safe, no one knows for sure if that's true.
If you want to be absolutely safe, use a recent custom kernel, those are known to be safe, since they completely disable the broken erase function.

guv. said:
Samsung claims, that recent stock recoveries are safe, no one knows for sure if that's true.
If you want to be absolutely safe, use a recent custom kernel, those are known to be safe, since they completely disable the broken erase function.
Click to expand...
Click to collapse
I did a factory reset > wipe Cache earlier and it booted ok thankfully. Im on UK XXLRK 404 (July 2012) so how recent do Samsung mean, but it seems to be on all 404 Roms (s2/Note), but thanks for the heads up... can I just say though that I would Never "Factory Reset" through Settings because im not sure if it wipes the cache or does much really, also the next and only update ill be doing will be JB 412 in March, if it arrives
Cheers

Can I just ask, when JB comes out in a few weeks, would you recommend to flash a safe kernel first, then update to JB.. or because Im Updating, should I just flash straight to stock JB in ODIN, then reset through Stock Recovery.
EDIT:
Also, Im new to this device so could anyone recommend a safe fast kernel to use with a stock 404 Rom.. Unrooted
Thanks

speedmod, Philz, hydracore.. all are safe
if you are not rooted then update via kies. or via odin.. dont do reset in stock recovery of ICS... or JB yet as not yet confirmed safe.. may be after the sources come out.. one of the devs can confirm it

I was trying my hands on ubuntu from paranoid, but flashed ics, and mistakely i didnt wipe anything before flashing,so i did wipe on ics kernel, so it was stuck on bootloop ,but i could enter recovery and download. so i first flashed philz kernel and did a wipe and downgraded to gb. So i want to know is this the emmc brick bug or a soft brick..

so if your phone is working you were lucky..

nokiamodeln91 said:
so if your phone is working you were lucky..
Click to expand...
Click to collapse
Ya my phone is working but what kind of brick was this. i have read about emmc brick bug but couldnt get what is it.

A soft brick
Sent from my GT-N7000 using Tapatalk 2

[Q] Howto: Fresh and clean install of official 4.1.2

Hi,
I own a Galaxy Note GT-N7000.
I never rooted it, just used two official updates provided by Samsung and then flashed the original 4.1.2 using Odin.
I have rooted my older Android phones (San Francisco) and used to try all kinds of ROM's on many Windows Mobile phones - I am not a exactly a noob, I just did not mess with my Note, because I am happy with it just like it is and because it is my work phone, which needs to be 100% working.
However, battery life is getting shorter (so I just ordered a new original Samsung battery) and, worse, the phone is getting more and more unresponsive.
This is the real problem: whenever I want to do something, it takes like 1-2 seconds, if not longer, before the phone reacts. This is very annoying. I don't have that many apps installed (I just stick with my preferred ones, instead of betting on sheer quantity). Still, the other day, the phone complained that there is no free space to install upgrades of some apps.
To make it short: how can I install a clean original 4.1.2 as if my phone was just purchased, i.e. with a clean flash?
Before you flame me and tell me I should spend the next month reading the forum: I already did!
I am afraid of the brick bug, so I guess that doing a wipe of the flash is not an option, as i guess that the bug has not been fixed by Samsung on 4.1.2. On the other hand, I do not want to root my phone, to install some custom kernel, to then wipe the flash and revert to the official ROM, risking to activate the counter, etc. Not that I don't know my way around flashing, soldering, building the flash dongle or even JTAG - I just don't have the time and nerve.
So my simple question: How do I securely wipe the flash and install a clean official 4.1.2 ROM on my phone, getting rind of 2 years of garbage files and God knows what else is slowing down my phone.
Many thanks for those guiding my way - I don't want to believe that there is a planned obsolescence in course, like Samsung building a timer that makes the phone get slower and slower...
Cheers,
vma

If you really want to enjoy the speed of your phone, IMO, you should go ahead and try CM /AOSP roms. They will give you some time out of the "slowness".
Just saying. On the other had if you want to be on the stock TW 4.1.2 rom, then doing a factory reset from the recovery will do the job. JB kernels for 4.1.2 seems to be safe to do a reset as there has not been cases of bricking on stock JB kernel.
But what my method would be to...
1. Install Philz kernel for JB using recovery and boot into recovery again... to get CWM recovery this time
2. Choose wipe data/factory reset ----> Clean for new rom install. (this will delete the current rom, data and cache)
3. Mounts and Storage -> Format Internal storage.
4. Mount USB storage and connect to PC... delete all files
5. Go to advanced menu and choose reboot download.
6. connect to PC and flash stock rom JB using odin,

Thanks for your reply.
However, you say:
nokiamodeln91 said:
On the other had if you want to be on the stock TW 4.1.2 rom, then doing a factory reset from the recovery will do the job. JB kernels for 4.1.2 seems to be safe to do a reset as there has not been cases of bricking on stock JB kernel.
Click to expand...
Click to collapse
While in another post it says:
"Warning :
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"
(http://forum.xda-developers.com/showthread.php?t=1424997)
This is what I don't get... Is it safe or not? Does this warning only apply to ICS, while JB is safe?
Cheers,
vma

Its applies only to ICS stock kernels. There is no evidence to prove that JB is safe. but Samsung seems to have suppressed the bug on JB kernels.

nokiamodeln91 said:
Its applies only to ICS stock kernels. There is no evidence to prove that JB is safe. but Samsung seems to have suppressed the bug on JB kernels.
Click to expand...
Click to collapse
Thank you for your kind help!
I will probably work on my Note this weekend.
Cheers,
vma