Ok, first of I was wondering what odin and the jb bootloaders do?
Im running baked blackbean 6 jb4.12 with the new devil kernel...followed instructions to a t, odined to stock eho3 pit, gb bootloaders, worked for a bit perfectly n got stuck in a bootloop from hell, although I think my bit animation may have caused it. So back to Odin, stock, ect, but didn't do the gb bootloaders, n all works fine, seems a bit slower and the splash screen from the kernel no longer shows up, and room control will no longer boot into recovery
Can I odin the bootloaders after the rom is already installed or do I need to start from scratch? If I do start from scratch will a nandroid still work with the new bootloaders installed?
Onto titanium backup, I have all user only apps backed up and created an update.zip file with them..No system data at all...if I have the update zip can I delete all the backups n just use that? Save memory on the sd I'm assuming you just flash it as an update in recovery as opposed to a reg zip? Then all my apps should be back?...
I'm really out of date with the fassy last thing I had was skunkworks aokp m6...and I never flashed any bootloaders, just started from stock, and this update zip thing is new to me...just trying to get it all stable for my son...I've also noticed when I go to the homescreen it takes a while to show anything n I have it kept in memory, don't think bootloaders would affect that though correct?
One last thing...if I keep the stock kernel I get an md5 error when I try to do a backup...but once I switch it to devil it's fine...anyone else have this? That was with and without bootloaders...but all in all the gb bootloaders are the main thing I want to find out about being I've never used them before....
Thanks!
Sent from my blackened liquid galaxy
I've actually always flashed the GB bootloaders separately with Odin after the ROM/Kernel was installed (twice in total) and never had a problem.
I tried the update.zip with TiBu once and it didn't work... never tried it again. I'm just sticking to the regular method.
Bootloaders have no effect after you boot so no, that wouldn't cause your home screen issue.
Not sure about the md5 thing as I don't do nandroids.
Hope this helped
The update.zip that you create is just titanium backup, not your apps. When you flash it, it allows you to run tibu and install your apps without signing into google. You'll still need the folder with all your app backups.
Related
I have a quite larger problem, I installed the JP3 rom from Eugene and Bionix. Well I revereted back to a nandroid of Vibrant9, thats where my problems began. After the nandroid was finished I seen the GTI9000 screen and it stayed there so I tried to revert back to stock with odin. I havedone every stock 2.1 odin they have posted and they go into a bootloop boot all the way up for about 20 seconds and then reboot. So I managed to get my update.zip pushed to my internal and without having to reroot the phone I got into clockwork mod installed Franken Twiz it works great other than the new problems. My signal either shows to be all or nothing no more individual bars being full, and my market place with download maybe 5 apps and wont download anything else after that. Did I do something wrong I followed all directions to a T help is needed Please.
KellyLewis3985 said:
I have a quite larger problem, I installed the JP3 rom from Eugene and Bionix. Well I revereted back to a nandroid of Vibrant9, thats where my problems began. After the nandroid was finished I seen the GTI9000 screen and it stayed there so I tried to revert back to stock with odin. I havedone every stock 2.1 odin they have posted and they go into a bootloop boot all the way up for about 20 seconds and then reboot. So I managed to get my update.zip pushed to my internal and without having to reroot the phone I got into clockwork mod installed Franken Twiz it works great other than the new problems. My signal either shows to be all or nothing no more individual bars being full, and my market place with download maybe 5 apps and wont download anything else after that. Did I do something wrong I followed all directions to a T help is needed Please.
Click to expand...
Click to collapse
I would revert back to an older nandroid of your system.
Tried that I even tried to revert to stock using oden and it goes into a bootloop and when I do manage to get a rom installed and loaded my market place starts trying to download a **** ton of apps that im nt trying to like i got a virus from either one of the root methods or from one of the stock oden roms off this website
KellyLewis3985 said:
Tried that I even tried to revert to stock using oden and it goes into a bootloop and when I do manage to get a rom installed and loaded my market place starts trying to download a **** ton of apps that im nt trying to like i got a virus from either one of the root methods or from one of the stock oden roms off this website
Click to expand...
Click to collapse
You could try downloading lookout from the market. It will scan the apps you have. I personally havent seen a virus but im careful what I load.
not to be rude but in the OP it states that my market place no longer works becase of this. none of the antivirus apps actually work they have never been tested with a real virus. if someone can post the apk for a zip file containing that apk for lookout we can test to see if it really works
I had zero problems when rooting and flashing my G1, but now with my Vibrant I am not sure what I did.
A few excellent stickies at the top but I seem to not be making any progress.
Here are the steps I took.
I had a stock Vibrant running 2.1
I downloaded ROM Manager, installed clockwork mod.
Did a backup of my current system ( was I supposed to do a clockwork AND nandroid?)
Downloaded and successfully installed a ROM called Blackhole 1.0
it runs ok but didn't give me the option to switch from 3G to EDGE data, and then I couldn't get internet access at all so i decided to restore my original stock vibrant system.
So I rebooted into recovery, selected restore (my phone won't go into recovery anymore for some reason) and waited, it took a while, then I rebooted (forgot to wipe), but it just got stuck on the Vibrant screen. So I booted into recovery mode again and wiped just user data not cache and rebooted, same thing stuck at Vibrant.
Now i keep hearing about something called ODIN, what I can tell it is some kind of flasher program for ROMS, nobody seems to give any kind of link or anything, is it greymarket or something?
So where am I now? I think the excellent noob guide needs to be updated a bit more.
My phone can get into download mode (whatever it is for i don't know) but it won't get into recovery mode anymore.
Everything you need is here: http://forum.xda-developers.com/showthread.php?t=771111
i think what happened to you is you flashed a 2.2 ROM then tried to revert back to 2.1 without doing the proper downgrading steps i.e. you did not flash a 2.1 kernel first.
but since you can get to download mode.. just flash stock JFD or JI6 through ODIN and you should be good.
good luck
Once you get back to stock don't give up on the 2.2 toms. Try axura or nero. They might have a few minor bugs but its way better then stock 2.1.
Powered by Axura with a dash of Voodoo
I have done the samething as you, coming from a nexus one it seemed easier to flash roms without worrying about downgrading kernels or what not. Recently I was on Nero froyo and flashed to a different rom, and tried to revert back but ended up stuck at the vibrant screen. Think it has something to do with voodoo lag.
Anyways I had to use Odin with the no brick froyo off ebproductions. Ran that and uploaded clockwork, reinstalled voodoo lag fix and was able to nandroid back to my Nero set up. Somewhat of a pain but once you've done it, no need to worry about bricking
xtone said:
Everything you need is here: http://forum.xda-developers.com/showthread.php?t=771111
i think what happened to you is you flashed a 2.2 ROM then tried to revert back to 2.1 without doing the proper downgrading steps i.e. you did not flash a 2.1 kernel first.
but since you can get to download mode.. just flash stock JFD or JI6 through ODIN and you should be good.
good luck
Click to expand...
Click to collapse
So the steps that are in this page?
http://forum.xda-developers.com/showthread.php?t=734475
GreggoryD502 said:
Once you get back to stock don't give up on the 2.2 toms. Try axura or nero. They might have a few minor bugs but its way better then stock 2.1.
Powered by Axura with a dash of Voodoo
Click to expand...
Click to collapse
Well as long as I can use Odin if I f-up royally like above then I might give it a shot.
Need to read about downgrading kernals or whatever. Might just wait for Cyanogen 6.1
Just so you know, the backup utility in Rom Manager (clockwork) is really just shortcut to a nandroid backup.
The way I have things set up for backups, and this is just for my personal convenience, is as follows...
I have a stock JFD ODIN rom to flash in case anything goes wrong. (A lot of people here will tell you to flash this whenever flashing a new rom. It is safer, and cleaner to do it this way, but not absolutely necessary)
I make a nandroid of my last stable rom (I only keep one at a time cause the files are huge) and keep a backup of that on my PC.
I backup all my apps and a few other things (call logs, bookmarks, sms) through Titanium backup. If you get the pro version, you can load it up after flashing a new rom and have it automatically restore all your apps in one click (system settings can be dangerous to restore when going from rom to rom, so be careful with those.) I also keep a backup of this on my PC.
I will also occasionally backup both of the sd cards to the PC.
Maybe overkill, but you probably wont ever lose anything forever.
thegreatcity said:
Just so you know, the backup utility in Rom Manager (clockwork) is really just shortcut to a nandroid backup.
The way I have things set up for backups, and this is just for my personal convenience, is as follows...
I have a stock JFD ODIN rom to flash in case anything goes wrong. (A lot of people here will tell you to flash this whenever flashing a new rom. It is safer, and cleaner to do it this way, but not absolutely necessary)
I make a nandroid of my last stable rom (I only keep one at a time cause the files are huge) and keep a backup of that on my PC.
I backup all my apps and a few other things (call logs, bookmarks, sms) through Titanium backup. If you get the pro version, you can load it up after flashing a new rom and have it automatically restore all your apps in one click (system settings can be dangerous to restore when going from rom to rom, so be careful with those.) I also keep a backup of this on my PC.
I will also occasionally backup both of the sd cards to the PC.
Maybe overkill, but you probably wont ever lose anything forever.
Click to expand...
Click to collapse
OK I will just do the long way from now on. I use this phone on AT&T, I was worried that I flushed $500 down the toilet but ever since i modded my first phone way back in the day i've been addicted.
Running Odin and my phone is in download mode, about to flash this b**ch.
wish me luck.
I flashed Odin on my phone to revert to stock. Re-Rooted it but now I can't flash Clockworkmod. Please help D:
use the update.zip posted here. You want B.
Hi, all. Relative noob here. Fascinate, Stock ED04 OTA, Rooted, modified stock kernel to "stick" CWM, Bloat frozen using TB.
I want to take the next step of flashing a ROM, and am doing (I feel) due dilligence by reading everything possible in this forum. However, I think I'm starting to suffer from information overload, and confusion has set in.
I used Odin to flash CWM 3.0.2.8x.ti. Immediately after selecting backup and restore/backup, I get "Error while backing up boot image". I see a few posts with the same statement, but no resolution. Flashed back to CWM 2.5; and backup appears to complete successfully. However, the date of the backup is 2000-01-01; and this is consistent on repeated attempts. The time and date on my phone (when booted) is correct.
Am I missing something? Any help would be greatly appreciated.
dhartman977 said:
Hi, all. Relative noob here. Fascinate, Stock ED04 OTA, Rooted, modified stock kernel to "stick" CWM, Bloat frozen using TB.
I want to take the next step of flashing a ROM, and am doing (I feel) due dilligence by reading everything possible in this forum. However, I think I'm starting to suffer from information overload, and confusion has set in.
I used Odin to flash CWM 3.0.2.8x.ti. Immediately after selecting backup and restore/backup, I get "Error while backing up boot image". I see a few posts with the same statement, but no resolution. Flashed back to CWM 2.5; and backup appears to complete successfully. However, the date of the backup is 2000-01-01; and this is consistent on repeated attempts. The time and date on my phone (when booted) is correct.
Am I missing something? Any help would be greatly appreciated.
Click to expand...
Click to collapse
i have had the same thing happen every time i try and backup. I'm wondering if it has anything to do with the newer recovery b.c when i had 2.5 i had no issues with it. Anybody have an answer for this?
I was in the same boat as you: rooted and bloat frozen via TB since the first week, and just added the modified kernel with CWM 3 earlier this past week. Haven't had any problems with it. I used Heimdall to flash CWM and the kernel. Now I'm running Evil Fascination with the LG Alternate Launcher. Tried ComRom but didn't care for it, though the default wallpaper was very pretty.
Back to the point, after I flashed the kernel and CWM I restarted the phone, let it boot, then rebooted into recovery to backup, instead of unplugging it and immediately booting Recovery.
Honestly, you've made it this far, you want to get a new ROM, I say download one and follow the directions (read them three times top-to-bottom) before flashing, and you should be good.
Yeah - I think Evil is where I want to end up until CM7 is fully functional (just spent all morning reading the CM7 waiting room thread).
Unfortunately, I'm apprehensive about flashing a new ROM until I can get a good backup image. I'm not sure why I'm getting the erroneous date on the backups. I could certainly be doing something wrong; just not sure what (if anything).
Maybe I need to use a different CWM? 2.5.1 and 3.0.2.8. don't seem to have worked for me. Also, If I understand what eulipion2 said, I have already fully booted, then powered down and rebooted into CWM to do a backup. 3.0.2.8 fails and 2.5.1 gives be incorrect dates.
Going to do a few hours of reading on CWM, I guess!
I'm using the first kernel listed in this thread from times_infinity. I initially flashed ComRom, didn't like it, kept this recovery, and flashed EF. Works great so far.
Give the Nandroid a go with this Recovery and see if it works for you.
hey i figured out how to get the back up to work. you have to enable voodoo and then it will work
Hey guys. Thanks for the suggestions. Tried the CWM 3 link from above, still no dice. I suspect I may need to have a voodoo kernel installed to actually enable the voodoo and try the backup again. Makes sense I guess.
Getting frustrated.
Success! Flashed a voodoo kernel, and was able to get (what appears to be) a successful nandroid backup with 3.0.2.8 (red). Never did get 2.5.1 (yellow) working. Strange, but irrelevant. CM7 build 7 is looking like it's ready for a test drive.
I'm wondering how I can get CWM back on my stock gingerbread fascinate now... I used the speedmod kernel to root, which had CWM built in. Then I replace it with stock GB kernel.. which has 3e recovery.
When I run ROM manager now with gingerbread the fascinate don't come up in the list no more.. there are 2 i9000's, one of those is a MTD... and 2 others. 4 in total.
I have the update.zip file which I downloaded from Rom Manager when I was on Froyo. Will that work? I'm afraid to try.
I've also seen methods of ADB pushing the recovery.bin over the current 3e. I just really not to sure which is the best way to do it, and I've done so much reading now it's got me confused.
Thx
Maniac
MrManiacNF said:
I'm wondering how I can get CWM back on my stock gingerbread fascinate now... I used the speedmod kernel to root, which had CWM built in. Then I replace it with stock GB kernel.. which has 3e recovery.
When I run ROM manager now with gingerbread the fascinate don't come up in the list no more.. there are 2 i9000's, one of those is a MTD... and 2 others. 4 in total.
I have the update.zip file which I downloaded from Rom Manager when I was on Froyo. Will that work? I'm afraid to try.
I've also seen methods of ADB pushing the recovery.bin over the current 3e. I just really not to sure which is the best way to do it, and I've done so much reading now it's got me confused.
Thx
Maniac
Click to expand...
Click to collapse
Second that - in the same boat.
As I understand it, it's a bootloader issue to install CM7 on Gingerbread. Downgrade to 2.2 and flash away!
Rabid_Gypsy said:
As I understand it, it's a bootloader issue to install CM7 on Gingerbread. Downgrade to 2.2 and flash away!
Click to expand...
Click to collapse
I don't want CM, I want to get clockwork recovery on my stock gingerbread.
I'm also in the same Boat. It would be nice to get clockwork recovery installed.
I have successfully rooted Gingerbread, part of the process is to flash the the Speedmod kernel first. With the Speedmod kernel, it has clockwork on it which you can boot into but unfortunately your phone cannot normally boot with that kernel.
I'm loving Gingerbread right now, it is so much smoother then 2.2, there is no way I want to go back to 2.2.
iwebsource said:
I'm also in the same Boat. It would be nice to get clockwork recovery installed.
I have successfully rooted Gingerbread, part of the process is to flash the the Speedmod kernel first. With the Speedmod kernel, it has clockwork on it which you can boot into but unfortunately your phone cannot normally boot with that kernel.
I'm loving Gingerbread right now, it is so much smoother then 2.2, there is no way I want to go back to 2.2.
Click to expand...
Click to collapse
Right there with you - so much better than 2.2 EVEN with lagfix running - was very thankful for ROOT but would love CWM recovery back - very useful tool.
I don't know if it was this thread I made the post, but something I did mention that I did was...
When I used the speedmod kernel to root the phone, I made a nandroid backup. Then I flashed the stock kernel back. I'm assuming if I wanted to restore my phone with the backup I could just flash the speedmod kernel back, restore by backup, then flash the stock kernel back again.
I don't know if clockwork is programmed to backup certain partitions, or if its dynamic, but I'm tempted to try my restore, but at the same time I don't want to go through all the updating agan.
Another thing, I have the 3 ODIN CWM file, the purple, blue, and no color ones you find on here. If you extract those you get a recovery.bin file, and there is no zimage (kernel). If you take one of those clockworkmods with no kernel and overwrite the stock recovery.bin in the phone, shouldn't that work?
I'm still new to android, first time I laid hands on one was this june, I'm still new, but I'm a fast learner too, but I want to figure this one out.
-Maniac
MrManiacNF said:
I don't know if it was this thread I made the post, but something I did mention that I did was...
When I used the speedmod kernel to root the phone, I made a nandroid backup. Then I flashed the stock kernel back. I'm assuming if I wanted to restore my phone with the backup I could just flash the speedmod kernel back, restore by backup, then flash the stock kernel back again.
I don't know if clockwork is programmed to backup certain partitions, or if its dynamic, but I'm tempted to try my restore, but at the same time I don't want to go through all the updating agan.
Another thing, I have the 3 ODIN CWM file, the purple, blue, and no color ones you find on here. If you extract those you get a recovery.bin file, and there is no zimage (kernel). If you take one of those clockworkmods with no kernel and overwrite the stock recovery.bin in the phone, shouldn't that work?
I'm still new to android, first time I laid hands on one was this june, I'm still new, but I'm a fast learner too, but I want to figure this one out.
-Maniac
Click to expand...
Click to collapse
Hey MrManiacNF,
Thanks for the idea, I guess it is a work around for now until we are able to get CWM installed on Gingerbread.
I ended up flashing the speedmod kernal back on, booted into CWM and made a full nandroid backup. Reflashed the stock gingerbread kernal back and booted up as normal.
Yea I do the same thing, I mean you can't make a backup without a pc to flash with, but a backup is better then none.
No love from ROM Manager
Saw ROM Manager had a few updates, but still seeing the limited device selection when trying to create a custom recovery, and still fails with the unsigned zip.
Just wanted to post that if anyone was wondering if recent updates corrected anything, as they have not (at least for me).
I can also confirm, actually no new phones added to the list. I've also tried an app call Root Toolbox Pro. It has options to backup your recovery or flash another. I tried flashing the fascinate-3.0.0.8.zip that I had from Rom Manager from Froyo. No luck, just hung at boot. Had to re-flash stock kernel in odin to fix.
Hi all - the weirdest thing is happening to me and it is definitely something I've done but I haven't the slightest what it is.
I've got CMX right now, and I've tried to go to a couple of ICS ROMs (Task, Sonic). They flash just fine, but on the new system if the screen goes to sleep the video flickers on screen wakeup. I have tried to remedy this by flashing an ICS kernel but haven't had any luck whatsoever. So today I thought I'd go back to my Nandroid backup that I took on CWM 5.0.2.7 way back on the 1st before I rooted my tab. I was on (and prefer) TWRP so I used Odin to re-flash the original recovery, wiped everything (including format /system from the Mounts menu to wipe the ROM) and restored the backup. Everything seemed fine. But to my horror, I locked the screen and woke it up to find the same flickering!!!!
I rebooted back into recovery and flashed TWRP back on so I could restore my CMX backup and I'm back to normal again. But now I feel like I'm stuck here, and the only way I'm going to be able to fix this issue is by using Odin to flash a stock firmware package. I really don't want to have to do that if I don't have to but will if I need to of course...
The one thing I haven't been able to get an answer on is before blowing everything away is what I'm asking now...in thinking about it, I had taken the backup before flashing a bootloader to fix my "rolling recovery screen" issue. Could the cause of this type of problem be a bootloader that the ROM doesn't like, or is this a crazy assumption?
OK I'm going to bump this thread with a simple to-the-point question - hoping for an answer as I work out my theories.
For those of you who have flashed ICS and custom recovery with no "rolling/flickering" issues - are you using an unlocked bootloader?
For the bootloader you just hit the point my friend,the bootloader that we use to fix rolling recovery problem has issues with most kernels except Pershoot's HC or CM9...
For your problem you should think of grabbing the official ICS or HC(just for getting rid of screen flicker),and in addition to flashing it you should extract it's stock bootloader,make a. tar.md5 out of it and keep it for future similar problems...
Note that the bootloader can only be flashed using Odin in PC and CWM or even stock flashing using MobileOdin can't make changes to it(or recover it)
For now there is not a proper fix for that but I think the best way is to have the stock bootloader and use ROMmanager or MobileOdin for flashing(since the recovery rolls with stock bootloader)...
Yeah I flashed stock ICS and rooted yesterday. I am just going to fight through the rolling recovery for now and stick with ICS until we can do more.
Thanks for the response!
some trick:you can rename the zip files you're going to flash so that their name starts with "Z",it's then easy to navigate to them(just press vol down twice)
Yep! That works, and you can also rename files as update.zip and use that option I believe. It's time to think outside of the box a bit with regard to flashing some ROMs...thats the bottom line. i am sure there are a few devs on this site that would appreciate it if we did more of that lol!
guys im really getting the same problem now... and i dont know what to do
would you be able to help me please?