Hi guys, I'm acquiring a new xt890 and I just want to be sure that I can update it from 4.0.4 (ICS) to Omar's ROM directly, without flashing stock 4.1.2 via RSD Lite.
Basically, the procedure would be as follows:
1) Unlock bootloader
2) Install custom recovery
3) Format everything via recovery (/data, /system, /cache)
4) Install latest Omar's build
5) Reboot
On my actual phone I have flashed stock JB after installing a custom ROM and now I would like to avoid this step, but first I need to be sure that it won't produce a hard brick.
So, I hear your suggestions.
Thanks in advance!
It can be a hit or miss! I originally had ICS and flashed Omar's Moto JB last year, but started to encounter a few problems after a few months of flashing, such as disappearing apps and root problems.
I then used RSD Lite to flash the latest JB and it managed to fix everything. (Downside = Annoying 'Unlocked Bootloader' boot logo)
The problem now is that it can be a hit or miss flashing certain ROMs... Either they will flash, or the won't. As Hazou mentioned in this post, there may be some differences between all our phones.
I've decided to keep the stock ROM, debloat it and use Omar's Gamma Kernel.
waj3k said:
It can be a hit or miss! I originally had ICS and flashed Omar's Moto JB last year, but started to encounter a few problems after a few months of flashing, such as disappearing apps and root problems.
I then used RSD Lite to flash the latest JB and it managed to fix everything. (Downside = Annoying 'Unlocked Bootloader' boot logo)
The problem now is that it can be a hit or miss flashing certain ROMs... Either they will flash, or the won't. As Hazou mentioned in this post, there may be some differences between all our phones.
I've decided to keep the stock ROM, debloat it and use Omar's Gamma Kernel.
Click to expand...
Click to collapse
Thanks! I've used RSD to flash a stock JB Firmware before going to Omar's ROM. Everything goes fine this way, but, as Hazou says on the post you linked, I can't use TWRP to install it with the 'format line' in it. So I'm using CWM 6.0.1.9 and no problem so far.
Related
Hi there,
coming from SGS2, for last three weeks I was a happy user of SGN. Rooted, went through a couple of GB roms, and now I tempted myself with KingDroid ICS NoteMania Edition v2.0. I followed the procedure, installing Abyss kernel, rebooting recovery and doing wipes, but afer installation system won't load (reboots on boot screen) and I am pretty much sure I lost root, because I tried to flash it again (without wiping in CWM, 'cause I heard it may brick the device) and stuck at "opening package".
Now I have only one question - I don't care whether I will be back on GB or move to ICS, I just want to get out of this pretty messy situation - having no working rom, probably no root as well, so I can't reflash Abyss Red Pill I've got on my SD card. Any hints?
UPDATE: I flashed CF ZS_OZS_LPF-v5.3 via Odin and tried to flash Abyss 4.2, but still it freezes on "Installing package".
Am I done for?
Thanks in advance!
roshi87 said:
Hi there,
coming from SGS2, for last three weeks I was a happy user of SGN. Rooted, went through a couple of GB roms, and now I tempted myself with KingDroid ICS NoteMania Edition v2.0. I followed the procedure, installing Abyss kernel, rebooting recovery and doing wipes, but afer installation system won't load (reboots on boot screen) and I am pretty much sure I lost root, because I tried to flash it again (without wiping in CWM, 'cause I heard it may brick the device) and stuck at "opening package".
Now I have only one question - I don't care whether I will be back on GB or move to ICS, I just want to get out of this pretty messy situation - having no working rom, probably no root as well, so I can't reflash Abyss Red Pill I've got on my SD card. Any hints?
UPDATE: I flashed CF ZS_OZS_LPF-v5.3 via Odin and tried to flash Abyss 4.2, but still it freezes on "Installing package".
Am I done for?
Thanks in advance!
Click to expand...
Click to collapse
Hopefully can help u.
1. Download prerooted rom from bodivas thread. ( unzip it. You can see 3 files. Just need the largest file about 884mb)
2. Open pc odin.
3.connect your phone to pc.
4.In pda please select the largest files.
5.press start and enjoy.
Good luck
Sent from my GT-N7000 using xda premium
Thanks. Seems like I am left with no other options. Current ICS build won't load and I lost root, so flashing GB with Odin looks like the way to do something about it. Or does anybody else has another solution?
UPDATE
I managed to flash pre-rooted GB LC1 via Odin, than flashed Speedmod with CWM and now I'm back on my Chrack LC1 GB. My only question remains - how do I know if my Note is now affected with eMMC bug and my /data partition isn't damaged? Is there any way to check it out? Thanks in advance for your help!
Hi,
I as of yet, am not going close to any ICS build till the issue gets solved by someone.
so I am experimenting with different gb roms. i was using checkrom v6 but didnt like it, so followed steps to install darkyrom/alliancerom extreme edition. i followed the steps as I was told to install allianceota and flash the rom through there. it didnt work. so instead using cmw i flashed through recovery, it did flash but there no root.
so now, i reflashed a stock la6 rooted rom from here; http://forum.xda-developers.com/showthread.php?t=1535025
this went smoothly with no problems, so i installed allianceota as normal, this time when i try to flash the following messages come up:
Installing Multi-CSC
Can't access to '/system/CSC/KOR/system/'
Successfully applied multi CSC"
and then it gives me the option to reboot, wipe cache and a few other options, not full recovery mode.
shall i just reflash the rom through recovery, or am I doing something wrong? and does the slight error above mean I have a problem with my note?
cheers in advance.
Let me just say that almost every ICS ROM out there now has disabled the MMC_CAP_ERASE code in the kernel that activates the eMMc bug and bricks your phone. If you want stock ICS, you can use SpeedMod or Franco kernels. If you want AOKP, there is that now. If you want CM9, there's a bunch of variations plus the official CM9 nightly. If you read through the OP and stickies, you will be okay.
Are you on stock recovery still? It sounds like it from the error you are getting. Try flashing CWM recovery and installing the GB rom with that. Follow Drketan's thread in Android Development.
hmmm, so would you advise me to use ics? is it much better? i dont want to use cm9 builds as i need the spen apps and so on. i have looked into kingdroid or alba.
I'll have to think hard about this. i may give it a shot soon though..
oh and btw, I fixed the problem, yep it was to do with cwm it wasn't installed with the stock rooted rom. as for allianceota, it still didnt flash the rom, i had to flash the rom through cwm manually.
cheers anyhow.
salespalace said:
hmmm, so would you advise me to use ics? is it much better? i dont want to use cm9 builds as i need the spen apps and so on. i have looked into kingdroid or alba.
I'll have to think hard about this. i may give it a shot soon though..
oh and btw, I fixed the problem, yep it was to do with cwm it wasn't installed with the stock rooted rom. as for allianceota, it still didnt flash the rom, i had to flash the rom through cwm manually.
cheers anyhow.
Click to expand...
Click to collapse
I love ICS a lot more than GB. If you want to use stock ICS, I would just use Franco or Speedmod kernels with it and be safe. Read both of their forums and decide what you want to do.
I had the same problem with rom deodex i had flash with odin 1.85 firmware gingerbread here ; http://www.hotfile.com/dl/152168378/f76281c/N7000XXLC1_N7000OXXLB3_ATO.zip.html... then i made wipe cache and cache dalvick .
I've just flashed AlBa repack latest one on xxlq2, I did it by following the steps,
I thought i had broken my phone, because when the flashing finished and i was rebooting, at the beginning when it welcome to galaxy note n7000 and then goes to the bootup video, it restarted that several times, then after like a few minutes it loaded the homescreen and startup.
salespalace said:
I've just flashed AlBa repack latest one on xxlq2, I did it by following the steps,
I thought i had broken my phone, because when the flashing finished and i was rebooting, at the beginning when it welcome to galaxy note n7000 and then goes to the bootup video, it restarted that several times, then after like a few minutes it loaded the homescreen and startup.
Click to expand...
Click to collapse
-Flash a stock GB rom with pc odin
-Root it
-Go to cwm and wipe all (factory reset,cache and dalvik and then Install the ics rom that you like
-Reboot system and now it should work
Sent from my GT-N7000 using Tapatalk 2
I will try to be as detailed as possible. I have been long time user here, but this is the first time I'm posting. I usually read the instructions and posts and that usually suffices my needs. I was on a rooted galaxy note running chasmodo's assylum rom for quite some time now. For Flashing a new rom, I used to go to recovery mode, flash abbysnote kernel (v 3.9) and install a new rom. A few days ago i tried to flash Ezaechiel XXLT6 KM edition - V2.1. I guess I should have checked md5 of the downloaded rom coz after flashing it, my phone refused to boot up. It always took me to the recovery mode screen where i tried to install abyssnote kernel and reinstall assylum. but it didn't work. So I went to dr. ketan's post and tried to flash a pre rooted rom (SGN_XX_OXA_KJ1_FACTORYFS.zip) using pc odin. Now my phone works fine but i'm on ginger bread. I tried to flash new roms using recovery mode (abbyssnote kernel method) but no new rom can be installed. Everytime I try to install a new rom i face boot loop or get stuck on the setup screen. So I follow the PC odin method to flash the same pre rooted rom (SGN_XX_OXA_KJ1_FACTORYFS.zip) to get my phone working again. I would like to go back to assylumrom because i got used to aosp jellybean so much now. Anybody who has faced a similar problem in the past, please help
Use one of PhilZ kernels and then in his recovery prepare your device for a clean install (there is an option that does more than only "factory reset". With the old ones you didn't clean /preload.
Then follow the instructions to install your preferred Rom.
Thanks
ThaiDai said:
Use one of PhilZ kernels and then in his recovery prepare your device for a clean install (there is an option that does more than only "factory reset". With the old ones you didn't clean /preload.
Then follow the instructions to install your preferred Rom.
Click to expand...
Click to collapse
Thanks for the quick reply thaidai. I will try the method and get back to you I used to do a clean wipe every time.
Mate first upgrade your stock ROM to ICS or JB. The ROMs like Asylum aren't supposed to be installed in GB, so first upgrade, then root and do a full wipe (data,cache,preload,dalvik) and get back to flash the ROM. No need to flash the Abyssnote every time, why do you do that?
Varad297 said:
Mate first upgrade your stock ROM to ICS or JB. The ROMs like Asylum aren't supposed to be installed in GB, so first upgrade, then root and do a full wipe (data,cache,preload,dalvik) and get back to flash the ROM. No need to flash the Abyssnote every time, why do you do that?
Click to expand...
Click to collapse
I tried installing Cassies Xtraliterom XLC1 after the PC odin method. Got boot loop. What I'm basically saying is, after trying the PC odin method to rescue the device, I can't seem to install any other rom on it using the recovery mode route. Not even other GB roms. What am I to do??
Varad297 said:
Mate first upgrade your stock ROM to ICS or JB. The ROMs like Asylum aren't supposed to be installed in GB, so first upgrade, then root and do a full wipe (data,cache,preload,dalvik) and get back to flash the ROM. No need to flash the Abyssnote every time, why do you do that?
Click to expand...
Click to collapse
I started using abyssnote kernel to install new roms after the "brick scare" of last year after which a lot of developers started recommending the method. I used to change between GB, ICS and JB roms easily using the abyssnote kernel. Don't know why it's not working anymore.
Firstly, I must say that bought my i9000 with Mackay rom (4.1.2 then) on it, and that I was very satisfied with it. Since then, I've changed several roms on my SGS.
But, I've been using a new 4.0.1 Mackay KK rom, and still not completely satisfied with some missing options, so I wanted to go back to JB, but I came across some issues. I did exactly how the developer wrote, but no luck. I've been trying to install rom with twrp, but it fails. OK, the developer mentioned it could happen, so I tried to flash again, as said, but still no luck. After that, I tried to flash old kernel, the one for JB, but failed again. TWRP now won't flash anything. Just to mention, the phone isn't bricked. I can power it up, and it works fine.
How can i flash back to old kernel, so I could flash JB again? Or, there is some trick to flash back to JB with kernel 0.600?
Thank U in advance,
filipidis
EDIT: I succeeded in going back to JB. I was somehow able to flash cyancore kernel over TWRP. Then I flashed it again with Mackay kernel, and flashed JB 4.3.
Now, waiting for stable version of Mackay KK.
Hi everyone,
I'm new here and this is my first post. First of all I would like to thanks pawitp and kasper_h for giving new life for our old device SGS i9000. I just wanted to share my experience installing Mackay ROM and wanted to know why my device freeze upon boot after flashing this ROM.
Steps done:
1. Coming from SlimBean (4.3), flashed CM 10.2
2. Do a factory data reset, wipe system/data/dalvik/cache
3. Flash Mackay ROM and GApps
4. Upon restart; freeze on Samsung device logo, waited for a long time but did not continue to kernel/boot/anim.
5. Tried to boot recovery, but still just freeze on Samsung device logo
6. Boot into Download Mode and flash Semaphore kernel from Cyanogen using heimdal tool
7. Flash Mackay ROM then Mackay Kernel then GApps
8. Successful boot!
I've been following Mackay ROM development and very satisfied with it, but every time I will flash/update Mackay ROM, I must remember to flash also the corresponding Mackay Kernel over it, otherwise I'll have to go through steps 4 to 7 above to fix the boot freeze.
Now, my question is, why my device freeze on boot? Isn't Mackay ROM already include the kernel?
I wanted to help in development even by just testing the ROM, but newbies are not allowed to post on development tread...
c-droid said:
Hi everyone,
I'm new here and this is my first post. First of all I would like to thanks pawitp and kasper_h for giving new life for our old device SGS i9000. I just wanted to share my experience installing Mackay ROM and wanted to know why my device freeze upon boot after flashing this ROM.
Steps done:
1. Coming from SlimBean (4.3), flashed CM 10.2
2. Do a factory data reset, wipe system/data/dalvik/cache
3. Flash Mackay ROM and GApps
4. Upon restart; freeze on Samsung device logo, waited for a long time but did not continue to kernel/boot/anim.
5. Tried to boot recovery, but still just freeze on Samsung device logo
6. Boot into Download Mode and flash Semaphore kernel from Cyanogen using heimdal tool
7. Flash Mackay ROM then Mackay Kernel then GApps
8. Successful boot!
I've been following Mackay ROM development and very satisfied with it, but every time I will flash/update Mackay ROM, I must remember to flash also the corresponding Mackay Kernel over it, otherwise I'll have to go through steps 4 to 7 above to fix the boot freeze.
Now, my question is, why my device freeze on boot? Isn't Mackay ROM already include the kernel?
I wanted to help in development even by just testing the ROM, but newbies are not allowed to post on development tread...
Click to expand...
Click to collapse
Hi, im new too
Which Mackay ROM are you taling about? Because i had the same problem flashing Mackay rom 3.99-the last one and i couldnt had flashed it unless i did a dirty flash but even then i had many problems. So i dont know. Currently im using OMNI Mackay -the latest build-and im very satisfied with it, there are only few issues... but in the end its way fastest rom for me before it i had been using Gamerzrom 4.0 for half a year and it was way the best for android 4.2.2
lulek01 said:
Hi, im new too
Which Mackay ROM are you taling about? Because i had the same problem flashing Mackay rom 3.99-the last one and i couldnt had flashed it unless i did a dirty flash but even then i had many problems. So i dont know. Currently im using OMNI Mackay -the latest build-and im very satisfied with it, there are only few issues... but in the end its way fastest rom for me before it i had been using Gamerzrom 4.0 for half a year and it was way the best for android 4.2.2
Click to expand...
Click to collapse
I'm using this Mackay ROM 4.1.7
I also wanted to try the OMNI build, but there's no separate kernel for it yet.
I've only successfully using Mackay ROM 4.1.7 by flashing the ROM then before I reboot I also flash the corresponding Mackay kernel 0.605, if I don't flash the separate kernel then when I restart, my phone freeze on Samsung device boot logo, which I'm wondering since as far as I know Mackay ROM package is already complete, I'm also sure that the ZIP file I downloaded is not corrupted cause I already downloaded it twice and tested it on WinRAR.
c-droid said:
I'm using this Mackay ROM 4.1.7
I also wanted to try the OMNI build, but there's no separate kernel for it yet.
I've only successfully using Mackay ROM 4.1.7 by flashing the ROM then before I reboot I also flash the corresponding Mackay kernel 0.605, if I don't flash the separate kernel then when I restart, my phone freeze on Samsung device boot logo, which I'm wondering since as far as I know Mackay ROM package is already complete, I'm also sure that the ZIP file I downloaded is not corrupted cause I already downloaded it twice and tested it on WinRAR.
Click to expand...
Click to collapse
Have you tried going back to stock android 2.3.6? Maybe that would work for you
@c-droid
@lulek01
Guys, which was your last stock ROM installed before using custom ROMs?
Froyo or Gingerbread?
As I've said on my OP, step no.1 I came from SlimBean, then since its recommended on Mackay ROM development thread I flashed CM 10.2 first before finally going to Mackay ROM.
Even now that I'm on Mackay ROM, when updating to new version using Mackay's TWRP, I still have to flash the separate Mackay kernel after Mackay ROM before restarting, otherwise my phone will freeze on Samsung device logo upon boot.
tetakpatak said:
@c-droid
@lulek01
Guys, which was your last stock ROM installed before using custom ROMs?
Froyo or Gingerbread?
Click to expand...
Click to collapse
My last stock ROM was GB
lulek01 said:
My last stock ROM was GB
Click to expand...
Click to collapse
OK, then we know at least that your phone has a proper bootloader.
For people who upgrade directly from Froyo is very important to flash a GB bootloader, as all newer custom ROMs suppose that GB bootloader was already installed.
---------- Post added at 07:57 PM ---------- Previous post was at 07:55 PM ----------
c-droid said:
As I've said on my OP, step no.1 I came from SlimBean, then since its recommended on Mackay ROM development thread I flashed CM 10.2 first before finally going to Mackay ROM.
Even now that I'm on Mackay ROM, when updating to new version using Mackay's TWRP, I still have to flash the separate Mackay kernel after Mackay ROM before restarting, otherwise my phone will freeze on Samsung device logo upon boot.
Click to expand...
Click to collapse
You didn't get it mate.... I meant: which was your last stock ROM.... Froyo or Gingerbread?
Oh... sorry...
so... before I've flash the custom ROM SlimBean...
damn... I've already forgot, all I remember was I've waited for the phone's warranty to end before trying out custom ROMs, but I knew I've downloaded and installed all the OTAs before, just forgot the last version I've received...
Anyway, do you know how can I update ONLY the bootloader? without doing a factory data reset / wiping system/data...
c-droid said:
Oh... sorry...
Click to expand...
Click to collapse
no problem
so... before I've flash the custom ROM SlimBean...
I knew I've downloaded and installed all the OTAs before, just forgot the last version I've received...
Anyway, do you know how can I update ONLY the bootloader? without doing a factory data reset / wiping system/data...
Click to expand...
Click to collapse
Yep, probably you do have a Gingerbread bootloader then (2.3.x), after all the updates.
Froyo firmweres were 2.2.x
If not sure, here you can see it in my i9000 thread (also with video) how to flash only a bootloader and there you can download all the files.
Make sure to read whole the step-by-step guide for flashing with Odin under section 2 as flashing a bootloader shouldn't go wrong.
Thanks tetakpatak,
I've read your thread, specially the warning regarding flashing bootloader that one mistake could hard brick the phone.
So, I wanted to clarify some things before I proceed on flashing the bootloader...
1. The baseband of the bootloader attached on your thread is XWJVU while my phone is XXJVK, should I search for bootloader the same as mine or the one on your thread is fine?
2. On your thread, the text guide says to choose the bootloader file under "PDA", but on the video, you choose it under "BOOTLOADER", I assume the video is correct as I can see the phone successfully boots...
3. I couldn't see clearly on the video and also not specifically stated on your text guide if I have to choose on Odin the "i9000Boot_XWJVU.zip" file or I have to extract first the "i9000Boot_XWJVU.tar" inside it and choose that one...
Sorry if I asked too much, not that I'm skeptical with your giude, just following your warning...
I was about to try tetakpatak guide on flashing only the bootloader, but I don't know why my phone was not detected by Odin?
I run Odin as administrator, choose the bootloader file, tick the "Phone Bootloader Update" and uncheck "Auto Reboot", then turn-on the phone to download mode, connect to PC, Windows detected the phone as "Gadget Serial device", but did not appear on Odin...