Related
I have an i9000M running UGKG3, rooted. I still have the stock kernel and have no modifications. I'm trying to get a CWM or 2e recovery that will let me install update.zip files that aren't signed.
I have tried kernel after kernel, getting bootloops with every one.
I tried signing the CWM update.zip myself but it only managed to remove one of the two errors I get about it not being signed in 3e Recovery. I tried signing it multiple ways, nothing.
I tried replacing some of the recovery files with Root Explorer, to no avail.
I also tried flashing JVQ and JVR so I could use CF-ROOT, but they didn't even get to the "Galaxy S" boot logo before it looped.
Does anyone have a solution?
Anything that works, really. A signed update.zip, a i9000m compatible kernel, a successful replacement method, anything that will install a usable recovery.
Thanks in advance,
Getinaf
I'm in the same situation as you. I have UGKG3 installed, with the rooted stock kernel via Odin. I have tried almost every custom kernel I can think of, and they all boot loop. I've tried Rom Manager to install CWM, and it doesn't work either. I haven't tried any JVR roms yet, but from what I read they should work, so I'm surprised you're getting bootloops there too.
I guess there is something different with gingerbread compared to froyo that makes the kernel more picky. On froyo I had the stock JL2 rom, and was able to install the speedmod k13e kernel to get CWM without any problems at all.
I guess we'll have to beg and plea for a dev to make a modified KG3 kernel with root and CWM recovery. I would be happy with that. I don't care about lagfixes or any other mods to the kernel. I just want root and CWM
I totally agree, that or I'll try and cook us one. I hear there are tutorials for things like root and cwm. I'm really actually trying to install juwe's smart rom, and for the life of me nothing is working. I'm sure there are more people like us out there too, it will be worth it to find a solution.
Sent from my GT-I9000M using XDA App
Getinaf said:
I totally agree, that or I'll try and cook us one. I hear there are tutorials for things like root and cwm.
Click to expand...
Click to collapse
I am very tempted to make own kernel. Nice and simple: root, and cwm. That's it. Now to find a tutorial
has anyone figured this out yet?i'm in the same situation...
Just flash this kernel on top of whatever you have, it'll work... trust me!
http://forum.xda-developers.com/showthread.php?t=1112908
I've been running that kernel for months back then when I was still running official Gingerbread KG3 from Bell and it's the best one there is.
Installation steps :
- Download kernel
- Start Odin, make sure Kies' services are all shut down
- Select Kernel as PDA in Odin
- Put phone in download mode
- Connect through USB ... Odin should detect phone
- Hit start, reboot phone
- Enjoy, you're done!
If you have problems like FC after that:
- reboot to recovery
- "wipe cache"
- Advanced menu --> Wipe Dalvik cache
- reboot (be patient, it'll take a few minutes to reconstruct dalvik cache)
- you're done!
Did all this and nOw in a boot loop. Can't reflash as debugging is off. I flashed first tIme frOm mObile Odin ?
What ROM did you have installed when you flashed Semaphore kernel?
Please help
HiKsFiles said:
Just flash this kernel on top of whatever you have, it'll work... trust me!
http://forum.xda-developers.com/showthread.php?t=1112908
I've been running that kernel for months back then when I was still running official Gingerbread KG3 from Bell and it's the best one there is.
Installation steps :
- Download kernel
- Start Odin, make sure Kies' services are all shut down
- Select Kernel as PDA in Odin
- Put phone in download mode
- Connect through USB ... Odin should detect phone
- Hit start, reboot phone
- Enjoy, you're done!
If you have problems like FC after that:
- reboot to recovery
- "wipe cache"
- Advanced menu --> Wipe Dalvik cache
- reboot (be patient, it'll take a few minutes to reconstruct dalvik cache)
- you're done!
Click to expand...
Click to collapse
Hi,
Please help... i have samsung i9000 and had stock rooted the phone. Tried to install the above kernel and now the phone is stuck on the bootloop, not booting up... Please help
Hi,
I have many times tried to flash CM7, but always happens weird thing.
I have stock 2.3.5 XXJVS with Semaphore 2.5.0 kernel
1.I boot into CWM
2.I wipe cache then wipe data/factory reset then i go advanced and choose wipe Dalvik cache
3.Choose .zip from sd card
4.I choose update-cm7.1.0-GalaxyS-signed.zip
5.My phone flashes it
6.It reboots
7.Normal Galaxy S GT-i9000 then Galaxy S
Cyanogen Mod
8.It goes to recovery and posts text very fast then reboots again
9.It repeats everything what it does from section 7.
Im very confused so please help!
Have you tried flashing it again?
redo step 3 and onwards,
sometimes you just need to flash twice.
It seems like a corrupted download... Are you flashing from internal or external? Have you mounted before?
i tried to flash from internal
What version of CWM recovery do you have? Maybe flash a different ROM just to update CWM, and then flash the rom you want?
I had the same, or atleast a similar problem whilst trying to flash CM9. I fixed it by flashing the rom again.
You also might want to redownload the file incase it's corrupt.
i have CWM 5.0.2.7 and i downloaded the CyanogenMod file again so i try to flash it again
Any luck with your efforts this far?
yes, i succesfully installed CM9 about 3 months ago.
I'm not sure which build it was but it was the newest build
I was running "TheMIDTeam 1.3" ROM & decided to upgrade to version 1.4 using the so call "safe" method using the "restore" method in CWM. unfortunatly this failed making my phone un bootable but I could still get into "download" mode.
I then thought I'd flash a stock ROM using odin and go from there. I chose the Taiwan N7000ZSLPF_N7000OZSLPF_OZS ROM. This all went OK & everything seem fine. I then relised this was not the ROM for me as it didn't contain "English Australian" amoungst other things. So I thought, no problem, I'l just flash something else more suitable, but no matter what else I flash with odin I keep getting "Force Close" continually once the phone has booted up. I tried many different ROMS from Gingerbread to ICS & keep getting the "Force Close" error.
I then flashed back the Taiwan ROM & it works fine but I am now stuck with that ROM.
The only difference with the Taiwan ROM that I can see was that it contained not just the PDA file like most ROM's but it had a PIT & BOOTLOADER & PDA & PHONE & CSC files. I think this may be where i've gone wrong. Maybe if I could find the stock international versions of all these files I may be able to flash these & get back to stock & start again.
Any help would be greatly appreciated
Anyone know where I can get the stock PIT & BOOTLOADER & PDA & PHONE & CSC
files so I can get back to stock?
I was also confused about the pit & bootloader files. I have used N7000XXLC1 open Europe with PC Odin. I have just sellected PDA file and everything went ok. Now I'm on stock GB without any problems
have you already tried to flash any stock rom trough mobile odin?
jpsb said:
have you already tried to flash any stock rom trough mobile odin?
Click to expand...
Click to collapse
I have tried flashing 2 stock ICS ROMs & 3 different stock Gingerbread ROMs using PC odin only. They all give me continious "Force Close" error messages after bootup making the phone unusable.
If I flash back the Taiwan ROM all seems OK but I;m stuck with this ROM.
If I were you I would get a working version of the taiwan rom on the phone. Then flash a suitable CF kernel. Push a choice custom rom on your Sd card. And then flas that rom from CWM recovery. Only wiping cache and dalvik cache.
Just go into recovery and wipe all caches and factory reset and it will load fine it did it to me until I wiped all caches kept saying Google frame work has stopped
Sent from my GT-N7000 using xda premium
Well.... for quite obvious reasons I wouldnt recommend doing a factory reset on an official ICS kernel.
Something lile sssssuperbrick comes to mind.
This superbrick stuffs is getting on my tits how many people are wiping on there galaxy note using superbrick kernels and having no problems thousands?? hundreds of thousands??? but 20 people brick there phones and it's like Osama bin laden has created this emmc bug in the kernel to get us all.. We all know the dangers people could brick there phones using safe kernels because people make mistakes and or don't follow instructions
Sent from my GT-N7000 using xda premium
Belfia said:
If I were you I would get a working version of the taiwan rom on the phone. Then flash a suitable CF kernel. Push a choice custom rom on your Sd card. And then flas that rom from CWM recovery. Only wiping cache and dalvik cache.
Click to expand...
Click to collapse
Sonic1981 said:
Just go into recovery and wipe all caches and factory reset and it will load fine it did it to me until I wiped all caches kept saying Google frame work has stopped
Click to expand...
Click to collapse
Thanks for the replys.
The Taiwan ROM that works is a ICS ROM, N7000ZSLPF_N7000OZSLPF_OZS.
I have thought of doing a full wipe via CWM but I'm afarid of the "SuperBrick" issue. In fact I was think maybe there is some coruption in the emmc partition already causing the "Force Close" errors I keep getting
KTM690 said:
Thanks for the replys.
The Taiwan ROM that works is a ICS ROM, N7000ZSLPF_N7000OZSLPF_OZS.
I have thought of doing a full wipe via CWM but I'm afarid of the "SuperBrick" issue. In fact I was think maybe there is some coruption in the emmc partition already causing the "Force Close" errors I keep getting
Click to expand...
Click to collapse
Just clear your caches after each flash back from gb to ics vice versa and it will work fine
Here is your salvation installation
Dear KTM690 :
No need To Panic, here is your solution :
Let's suppose you are on the Stock LPF now :
1- Download the corresponding Rooted Kernel by Chainfire : I got it for you : http://download.chainfire.eu/176/CF-Root/SGN/CF-Root-SGN_ZS_OZS_LPF-v5.6-CWM5.zip
2- Extract it, you will have a tar file, Flash it with PC odin.
3- Reboot, now you are rooted and you have cwm recovery at the same time
4- Download the AbyssKernel V4.2 only : http://www.mediafire.com/?c65mndvpk6ocbaa
5- Put the zip file on your sdcard, don't extract it
6- Choose what ever ICS rom you like, let's say the TMT v1.4 that you wanted.
7- Put the zip file on your Sdcard.don't extract it
8- now shut off your phone, Press the Vol Up, Power and the Home Buttons at the same time, and you will be into cwm recovery mode.
9- Don't wipe anything, and Flash the AbyssKernel v4.2.
10- Don't reboot the phone, still in cwmr, go to advanced and choose reboot recovery.
11- You are now in recovery mode again, but with the Abyss Kernel instead of the rooted LPF one by chainfire.(now you have cwm touch recovery, tap with your finger now)
12- So It is totally safe now : wipe everything : data, cache, go to advanced and wipe dalvick cache, and battery stat, choose also Fix permissions while you are there.
13- choose back to go to the first screen,
Now you have Options, depending on what you have dowloaded as a Rom file...
14- If you want to flash the backup zip file from TMTv1.4 : choose backup and restore, and choose restore from internal sdcard, and look for your downloaded TMT zip file. (It should be clockworkmod/backup/TMT1.4...... Folder), I suppose you already have done it.!
15- If you have dowloaded the flashable TMT zip file, then choose install zip file, and choose file from internal sdcard..
In either cases : Reboot and you are done.
This is the cleanest installation you could have done, just don't skip any step !!!!
If this Helped, The thanks Button is next to you, ....and check my MOD : the 15 toggles in case .....
http://forum.xda-developers.com/showthread.php?t=1620625.
Good Luck.
Okay just flash whatever ROM you want (even if there are FCs), go into stock recovery (volume up home and power) and wipe data and cache. Reboot. This solved all the FCs for me when I had the same problem. Worth trying!
Sent from my GT-N7000 using XDA
kimifender said:
Dear KTM690 :
No need To Panic, here is your solution :
Let's suppose you are on the Stock LPF now :
1- Download the corresponding Rooted Kernel by Chainfire : I got it for you : http://download.chainfire.eu/176/CF-Root/SGN/CF-Root-SGN_ZS_OZS_LPF-v5.6-CWM5.zip
2- Extract it, you will have a tar file, Flash it with PC odin.
3- Reboot, now you are rooted and you have cwm recovery at the same time
4- Download the AbyssKernel V4.2 only : http://www.mediafire.com/?c65mndvpk6ocbaa
5- Put the zip file on your sdcard, don't extract it
6- Choose what ever ICS rom you like, let's say the TMT v1.4 that you wanted.
7- Put the zip file on your Sdcard.don't extract it
8- now shut off your phone, Press the Vol Up, Power and the Home Buttons at the same time, and you will be into cwm recovery mode.
9- Don't wipe anything, and Flash the AbyssKernel v4.2.
10- Don't reboot the phone, still in cwmr, go to advanced and choose reboot recovery.
11- You are now in recovery mode again, but with the Abyss Kernel instead of the rooted LPF one by chainfire.(now you have cwm touch recovery, tap with your finger now)
12- So It is totally safe now : wipe everything : data, cache, go to advanced and wipe dalvick cache, and battery stat, choose also Fix permissions while you are there.
13- choose back to go to the first screen,
Now you have Options, depending on what you have dowloaded as a Rom file...
14- If you want to flash the backup zip file from TMTv1.4 : choose backup and restore, and choose restore from internal sdcard, and look for your downloaded TMT zip file. (It should be clockworkmod/backup/TMT1.4...... Folder), I suppose you already have done it.!
15- If you have dowloaded the flashable TMT zip file, then choose install zip file, and choose file from internal sdcard..
In either cases : Reboot and you are done.
This is the cleanest installation you could have done, just don't skip any step !!!!
If this Helped, The thanks Button is next to you, ....and check my MOD : the 15 toggles in case .....
http://forum.xda-developers.com/showthread.php?t=1620625.
Good Luck.
Click to expand...
Click to collapse
Thanks for you advise kimifender & everyone else.
I carried this out and now everything is back to normal.
I was just too worried about wiping everything because of the SuperBrick bug.
KTM690 said:
Thanks for you advise kimifender & everyone else.
I carried this out and now everything is back to normal.
I was just too worried about wiping everything because of the SuperBrick bug.
Click to expand...
Click to collapse
Glad for you
Hey Guys,
I have this problem where i cant seem to flash to any new roms in CWM with the new roms in zip files on my SD card.
I have tried flashing to new kernels but it doesn't seem to change anything.
The last rom i flashed was Criskelo v7 and i haven't changed because i cant every time i try to flash something new in CWM it seems like it only just starts to do it then freezes and i leave it because it might be working and it always end up rebooting and then i find I'm back on Criskelo v7 as if its a fresh install and it need my google account / full setup as if its new but no new rom.
I have also tried updating CWM with odin it works to update odin but it still cant flash any new roms.
Am i doing something wrong? please if anyone has any idea let me know.
Sorry if this has been covered but i really did try and find similar problems.
Thanks
What does the screen read? Error 7?
Sent from my GT-N7000 using xda app-developers app
Flash ANy ROMS
Dr_Rag
if you want to flash any roms using cwm,
1. Flash Safe kernels like Hydracore (http://forum.xda-developers.com/showthread.php?t=1749863) or Philz Kernel (http://forum.xda-developers.com/showthread.php?t=1877270).
2. Reboot in recovery
3. Do all 3 wipes (wipe data, wipe cache partition & wipe dalvik cache)
4. Flash romzip
5. Reboot
If you want to flash XXLS7 TW JB Dump Based Roms , then
1. Flash Safe kernels like Hydracore (http://forum.xda-developers.com/showthread.php?t=1749863) or Philz Kernel (http://forum.xda-developers.com/showthread.php?t=1877270).
2. Reboot in recovery
3. Do all 3 wipes (wipe data, wipe cache partition & wipe dalvik cache)
4. Format /system & /preload in mount and storage
5. Flash romzip
6. Reboot
BTW what rom you are going to install
I had a similar issue and it was a root issue.
To see if it is the same for you, if you have SuperSU, open it, and press 'Continue' if prompted to update binary. If this fails, your problem is root related, the solution of which is below. Unfortunately I don't know how else to test if you don't have SuperSU or if the update prompt doesn't appear.
Below is how I fixed the problem. It may not work for you, and if it doesn't, it's not my fault.
Also note this method will fix the issue no matter what caused it, and wipes data, so backup what you need. It also assumes your ROM is flashable.
1 Put your ROM anywhere in /storage/sdcard0 on your phone.
2 Go to hotfile.com/dl/155490069/c7932d4/N7000XXLPY_N7000OXALPY_DBT.zip.html on your computer to download N7000XXLPY_N7000OXALPY_DBT.
4 Extract this to produce N7000XXLPY_N7000OXALPY_N7000XXLPT_HOME.tar.md5.
5 Flash this through Odin.
6 After your phone reboots (you can't get into the actual OS so you must do this in the Samsung boot animation), enter recovery.
7 Wipe data and cache.
8 Enter download mode.
9 Go to puu.sh/1q5mJ to download GL_NOTECORE_HYDRACORE_v4-3b_STD.tar.
10 Flash this through Odin.
11 After your phone reboots (you don't need to wait to get into the actual OS - you can do it in the Samsung boot animation), enter recovery.
12 Flash your ROM.
So I am able to flash dynamickat, hyperdrive, & jovy's deodex stock perfectly fine and they boot up normal and everything. However, when I try darthstalker or skyfall I get bootloops on both. They flash fine but I never make it past the boot animation. It'll be on for a few minutes and then reboot itself. I tried wiping data afterwards but nothing happens. I've downloaded the roms on different pcs, my phone, the md5 was correct, I flashed from my internal sd & external, I formatted everything (even my internal sd to see if that would help for some odd reason), I flashed a different kernel & I also odin'd back to stock and I still have no luck. I am on a t-mobile note 4 & twrp 2.8.1.1. I have no clue what to do anymore & this is becoming pretty frustrating
re: try this
xoxo_xdagirl91 said:
So I am able to flash dynamickat, hyperdrive, & jovy's deodex stock perfectly fine and they boot up normal and everything. However, when I try darthstalker or skyfall I get bootloops on both. They flash fine but I never make it past the boot animation. It'll be on for a few minutes and then reboot itself. I tried wiping data afterwards but nothing happens. I've downloaded the roms on different pcs, my phone, the md5 was correct, I flashed from my internal sd & external, I formatted everything (even my internal sd to see if that would help for some odd reason), I flashed a different kernel & I also odin'd back to stock and I still have no luck. I am on a t-mobile note 4 & twrp 2.8.1.1. I have no clue what to do anymore & this is becoming pretty frustrating
Click to expand...
Click to collapse
I have read your posts in the development thread about the issue you are having.
Give this a try
#1: Do a full wipe including Wipe System, Data, Cache, Dalvik and
last but not least to a factory reset in twrp recovery.
#2: Flash Jovy23's, stock rooted deodexed rom again.
#3: Copy Darthstalker zip file rom to your computer's desktop.
#4: Open Darthstalker zip file rom and remove/delete "boot.img"
from the zip file using winrar or winzip (or other archiver).
#5: Once "boot.img" is no longer in the Darthstalker zip file rom
copy it back to your phone's internal sdcard.
#6: Flash the Darthstalker zip file rom but do NOT wipe anything this time.
If this works for you then that means that for whatever reason your
phone has issues with the original kernel file (boot.img) which was in
the darthstalker zip file before you removed/deleted it,.
Doing it using the above step by step you will be using the kernel (boot.img)
from jov23's stock rooted rom.
If it works for you can open jovy23's stock rooted zip file rom and copy
the boot.img from it to your desktop then close the zip file.
Then open darthstalker zip file rom and copy jovy23's stock boot.img
from your desktop into darthstalker zip file rom.
The darthstalker zip file rom which has no boot.img in it since you have
already deleted and removed it.
Then copy the modified darthstalker zip file rom into your internal sdcard
over-writing the one already there.
Then if you like you can do a full wipe again and flash the modified
darthstalker zip file rom which has jovy23's kernel (boot.img) in it
and it should work fine.
Good luck!
xoxo_xdagirl91 said:
So I am able to flash dynamickat, hyperdrive, & jovy's deodex stock perfectly fine and they boot up normal and everything. However, when I try darthstalker or skyfall I get bootloops on both. They flash fine but I never make it past the boot animation. It'll be on for a few minutes and then reboot itself. I tried wiping data afterwards but nothing happens. I've downloaded the roms on different pcs, my phone, the md5 was correct, I flashed from my internal sd & external, I formatted everything (even my internal sd to see if that would help for some odd reason), I flashed a different kernel & I also odin'd back to stock and I still have no luck. I am on a t-mobile note 4 & twrp 2.8.1.1. I have no clue what to do anymore & this is becoming pretty frustrating
Click to expand...
Click to collapse
When I built the N4 rom, I was having serious qmg boot animation issues, I disabled them, and the rom booted normal, we may have a issue with the new roms and the animations. Just a thought.
re:
AxAtAx said:
When I built the N4 rom, I was having serious qmg boot animation issues, I disabled them, and the rom booted normal, we may have a issue with the new roms and the animations. Just a thought.
Click to expand...
Click to collapse
If that's the case then perhaps it might be a good idea for her to
remove all the qmg files in the system/media folder just to see
if it resolves her bootloop issues before trying anything else.
(I have not had any bootloop issues)
But then why don't all the users of the rom have the bootloop issue?
Misterjunky said:
If that's the case then perhaps it might be a good idea for her to
remove all the qmg files in the system/media folder just to see
if it resolves her bootloop issues before trying anything else.
(I have not had any bootloop issues)
But then why don't all the users of the rom have the bootloop issue?
Click to expand...
Click to collapse
Thanks for trying to help! I did what you said and flashed the stock rom but got an error when flashing darthstalker afterwards when I removed the boot.img but I still went ahead and added the boot.img from the stock rom to to the darthstalker zip and that didn't work. Still bootloops. And that's what I don't understand how it works fine on everyone else's phone and not mine I mean it's not all roms but it's still very weird and I want to know why it's happening. On another note when I do flash the stockrom, hyperdrive, & dynamickat right before it boots I get android system upgrading.. optimizing app 200 out of 200 or so, does that happen with anyone else? is that suppose to happen? does that happen on darthstalker or skyfall?
re: updating apps
xoxo_xdagirl91 said:
Thanks for trying to help! I did what you said and flashed the stock rom but got an error when flashing darthstalker afterwards when I removed the boot.img but I still went ahead and added the boot.img from the stock rom to to the darthstalker zip and that didn't work. Still bootloops. And that's what I don't understand how it works fine on everyone else's phone and not mine I mean it's not all roms but it's still very weird and I want to know why it's happening. On another note when I do flash the stockrom, hyperdrive, & dynamickat right before it boots I get android system upgrading.. optimizing app 200 out of 200 or so, does that happen with anyone else? is that suppose to happen? does that happen on darthstalker or skyfall?
Click to expand...
Click to collapse
The upgrading apps is NOT supposed to happen or appear at all unless you have NOT done a FULL
and complete wipe before flashing.
It's normal for it to upgrade a lot of apps during boot if you decided or have not done a full and
complete wipe which includes Factory Reset, Wipe System, Data, Cache and Dalvik cache.
In your case you need to do a full and complete clean flash and the only way to do that is by doing
a full and complete wipe.
If you keep seeing the "updating apps" after flashing any rom it means you have not done a full wipe.
When you have finally done a full and complete wipe before flashing you will no longer see the
phone doing the "upgrading apps" counting the number of apps to be upgraded during bootup
at all when the phone is actually wiped clean before flashing any roms.
(I am assuming that you're using twrp recovery to wipe and flash roms).
Good luck!
Misterjunky said:
The upgrading apps is NOT supposed to happen or appear at all unless you have NOT done a FULL
and complete wipe before flashing.
It's normal for it to upgrade a lot of apps if you decided or have not done a full and complete wipe
including Factory Reset, Wipe System, Data, Cache and Dalvik cache.
In your case you need to do a full and complete clean flash and the only way to do that is by doing
a full and complete wipe.
If you keep seeing the "updating apps" after flashing any rom it means you have not done a full wipe.
When you have finally done a full and complete wipe before flashing you will no longer see the
phone doing the "upgrading apps" counting the number of apps to be upgraded during bootup
at all when the phone is actually wiped clean.
Good luck!
Click to expand...
Click to collapse
I am doing a full wipe though?